
From daedulus@btconnect.com  Fri Feb  1 01:28:58 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F2A21F879B for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 01:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level: 
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[AWL=-0.800, 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 O8cAOe+8daYY for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 01:28:58 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) by ietfa.amsl.com (Postfix) with ESMTP id D341721F8464 for <ietf@ietf.org>; Fri,  1 Feb 2013 01:28:57 -0800 (PST)
Received: from mail132-ch1-R.bigfish.com (10.43.68.230) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Feb 2013 09:28:56 +0000
Received: from mail132-ch1 (localhost [127.0.0.1])	by mail132-ch1-R.bigfish.com (Postfix) with ESMTP id A52AA3001DF; Fri,  1 Feb 2013 09:28:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371I936eI542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL17326ah8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail132-ch1 (localhost.localdomain [127.0.0.1]) by mail132-ch1 (MessageSwitch) id 135971093541951_31753; Fri,  1 Feb 2013 09:28:55 +0000 (UTC)
Received: from CH1EHSMHS005.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.248])	by mail132-ch1.bigfish.com (Postfix) with ESMTP id F291622028E;	Fri,  1 Feb 2013 09:28:54 +0000 (UTC)
Received: from AMSPRD0710HT003.eurprd07.prod.outlook.com (157.56.249.85) by CH1EHSMHS005.bigfish.com (10.43.70.5) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Feb 2013 09:28:53 +0000
Received: from DBXPRD0210HT005.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.255.160.166) with Microsoft SMTP Server (TLS) id 14.16.263.1; Fri, 1 Feb 2013 09:28:49 +0000
Message-ID: <002101ce005e$23f04dc0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: SM <sm@resistor.net>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20130131073013.0aa87df0@resistor.net>
Subject: Re: Reducing time to publication: was Re: FW: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC
Date: Fri, 1 Feb 2013 09:24:01 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.181]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 09:28:58 -0000

----- Original Message -----
From: "SM" <sm@resistor.net>
To: "t.p." <daedulus@btconnect.com>
Cc: <ietf@ietf.org>
Sent: Thursday, January 31, 2013 4:51 PM


> Hi Tom,
> At 04:04 31-01-2013, t.p. wrote:
> >Time to publication of an RFC can be reduced by cutting out the
pauses,
> >which could achieved by highlighting when they occur.
>
> [snip]
>
> >Such a list would shine a light on what is moving and what is not.
This
> >in turn would encourage, motivate, spur those on whom the draft is
> >waiting to progress it (and anyone else who could contribute).
>
> There was an interesting quote from #overlyhonestmethods.  I cannot
> locate it right now as the web site is whaling out.
>
> There is a Daily Dose web page (see http://tools.ietf.org/dailydose/
> ).  The web page provides a snapshot of what's being "published" in
> the IETF.  However, it does not provide a view of what is moving and
> what is not moving.  I don't have a view of what an area or what a
> working group is up to.
>
> Sometimes it come as a surprise when working group participants hear
> that their working group is being shut down.  It is possible to tell
> whether a working group might be shut down.  It is possible to
> identify some of the issues which can delay publication.  The data
> for what you suggested is available from the datatracker.  The data
> to identify WG activity is also available.  I don't know how to
> assess progress though.

Yes, this is all available on the datatracker (which is the home page on
my web browser) but it takes me several minutes to go there and absorb
the content, repeated for every Working Group in which I am involved.
The datatracker has too much information, I have to scroll up and down,
since each entry takes 5 or 10 lines.  My idea is a one line summary for
each I-D, in a defined sort order (I-D name).  And I know how much more
productive I am when I get gentle prompts about what is going on, be
they via SMS, e-mail or whatever.  Sensible organisations, from
libraries to garages, are making the most of this technology - we should
do the same.

Tom Petch

> Regards,
> -sm
>
>



From daedulus@btconnect.com  Fri Feb  1 01:28:58 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B826221F8464 for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 01:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.266
X-Spam-Level: 
X-Spam-Status: No, score=-4.266 tagged_above=-999 required=5 tests=[AWL=-0.667, 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 3N2Y4s2af8mg for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 01:28:58 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe001.messaging.microsoft.com [216.32.181.181]) by ietfa.amsl.com (Postfix) with ESMTP id 24C1121F875F for <ietf@ietf.org>; Fri,  1 Feb 2013 01:28:58 -0800 (PST)
Received: from mail168-ch1-R.bigfish.com (10.43.68.230) by CH1EHSOBE008.bigfish.com (10.43.70.58) with Microsoft SMTP Server id 14.1.225.23; Fri, 1 Feb 2013 09:28:57 +0000
Received: from mail168-ch1 (localhost [127.0.0.1])	by mail168-ch1-R.bigfish.com (Postfix) with ESMTP id C9A9F3206E3; Fri,  1 Feb 2013 09:28:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -20
X-BigFish: PS-20(zz98dI9371I542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail168-ch1 (localhost.localdomain [127.0.0.1]) by mail168-ch1 (MessageSwitch) id 1359710934733021_14843; Fri,  1 Feb 2013 09:28:54 +0000 (UTC)
Received: from CH1EHSMHS005.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.252])	by mail168-ch1.bigfish.com (Postfix) with ESMTP id A68311400C5;	Fri,  1 Feb 2013 09:28:54 +0000 (UTC)
Received: from AMSPRD0710HT003.eurprd07.prod.outlook.com (157.56.249.85) by CH1EHSMHS005.bigfish.com (10.43.70.5) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 1 Feb 2013 09:28:52 +0000
Received: from DBXPRD0210HT005.eurprd02.prod.outlook.com (157.56.253.181) by pod51017.outlook.com (10.255.160.166) with Microsoft SMTP Server (TLS) id 14.16.263.1; Fri, 1 Feb 2013 09:28:49 +0000
Message-ID: <002001ce005e$23ad2a40$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: John C Klensin <john-ietf@jck.com>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net> <BF1522A80586ED2AB0D22150@JcK-HP8200.jck.com>
Subject: Re: Reducing time to publication: was Re: FW: Last Call:	<draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running	Code) to Experimental RFC
Date: Fri, 1 Feb 2013 09:17:07 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.181]
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 09:28:58 -0000

----- Original Message -----
From: "John C Klensin" <john-ietf@jck.com>
To: "t.p." <daedulus@btconnect.com>
Cc: "ietf" <ietf@ietf.org>
Sent: Thursday, January 31, 2013 2:44 PM
>
> --On Thursday, January 31, 2013 12:04 +0000 "t.p."
> <daedulus@btconnect.com> wrote:
>
> > Time to publication of an RFC can be reduced by cutting out
> > the pauses, which could achieved by highlighting when they
> > occur.
> >
> > This can be done by a tool which, for every active Working
> > Group, runs monthly and, for every draft adopted by the
> > Working Group, records whether or not there has been a change
> > and posts this list as an e-mail to the list of the Working
> > Group.  Where a new version has been submitted to Tools, then
> > this new version is listed with the date of submission.  Where
> > the status has changed, as recorded in the tracker (AD Review,
> > IETF LC, Publication Approved etc), then the new status is
> > listed with the date of change.  Where nothing has changed,
> > then this is listed with the date of the last change.
> >...
>
> Tom,
>
> This is interesting but could also introduce a pathology in
> which drafts are generated too frequently to encourage (or even
> permit) healthy discussion.  If one were going to do this, also
> collecting some statistics on how much (or whether) a given
> draft was being discussed on a WG mailing list might be very
> important.  New drafts and indications of motion like status
> changes may be good clues but what really counts for measures of
> progress and consensus is whether real discussion is going on.

Yes, drafts might be produced more often just to 'game' the system but
we have something like that anyway.  I often see drafts produced with no
changes simply because the previous version has expired.  Usually the WG
Chair or editor posts a note to that effect; if not, someone on the list
may ask and so the reason emerges.

Yes, a measure of discussion would be better, that might be the gold
standard, whereas my idea is only silver or bronze.  But I don't know
how to measure discussion in an automated way, one that places no
additional burden on such as WG Chairs or ADs.  So I see this as a step
in the right direction upon which others might build.

Tom Petch

>   john
>



From sm@resistor.net  Fri Feb  1 02:34:24 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B08121F879D for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 02:34:24 -0800 (PST)
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 rm4wkOFak5JK for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 02:34:22 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D454921F881E for <ietf@ietf.org>; Fri,  1 Feb 2013 02:34:09 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r11AXlFR015818; Fri, 1 Feb 2013 02:33:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359714837; bh=dM2yKajMMwwUTwygvNGsm+SlBt6qiDcPh2G1C2S9Q/Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NJsSxwfQn/yhDct8uYv3VFX8/Qa3KvmhHqpBiE5BSVbPjfR5+gmjX7IvqfAPN/PjC k0bPaN2hHiV6X5/RCMRdK9pZiyaKMNS9SDczQZOnRIRjUTvNJszgNDtSewIZPBfjSn zoPuK71re1oCJvazFngPerdU9CrJjOWXmSgtptIA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359714837; i=@resistor.net; bh=dM2yKajMMwwUTwygvNGsm+SlBt6qiDcPh2G1C2S9Q/Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rMmFPIP/vmy+sTCvgcmaByVgoLmqSaNXLscZXnv1nfoioTCHy5AXfPhYZ6c/PK2fU 5Wsa9IDSlSydX1Y0MiSb1rzvWMGSlrsWya0Kq6VCitokl9WQoi6Syem0cd7u8NYnrL ai8K/3WIJg6MEYGXTF3zpNeMYzRwvTb1Jb8voNCo=
Message-Id: <6.2.5.6.2.20130201000341.09ae1080@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 01 Feb 2013 02:23:41 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC with Running Code) to Experimental RFC]
In-Reply-To: <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.g mail.com>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net> <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, Bernard Aboba <bernarda@microsoft.com>, Dave Crocker <dcrocker@bbiw.net>, John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Barry Leiba <barryleiba@computer.org>, "Lakshminath Dondeti <ldondeti@qualcomm.com> 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, 01 Feb 2013 10:34:24 -0000

At 16:25 31-01-2013, Barry Leiba wrote:
>We often pick on every suggested change and point out every possible
>flaw, with different people holding out behind different flaws, and we
>get stuck there.  There seems to be some assumption, when we do this,
>that our current process doesn't also have significant flaws.  But the
>very reason we're trying to change something is that we *already* have
>a process with flaws.
>
>We know that no process we ever come up with will be perfect, and
>agreeing to change is a question of deciding what the flaw balance is.
>  We need to allow ourselves to move from one (known, "comfortable")
>set of flaws to a new set, *if* we can come to a reasonable agreement
>that we've improved things in a useful way.

I missed RFC 5111 which was a 3933 experiment.  The success metrics were:

   "Progress on the basic milestones is measured by whether they are
    completed within the time-frame specified in the initial
    Exploratory Group Charter  ..."

   "an Exploratory Group whose mailing list shows minimal traffic would
    probably not be a good candidate for milestone extension."

There is also RFC 4633 about long-term suspensions.  There isn't any 
success metric.  The following is worth highlighting:

   "In no event shall a suspension last for more than six months nor shall any
    suspension last beyond the end of the RFC 4633 experiment."

The following are selective quotes:

   "During the Gen Area meeting today, it was asserted that if this
    experiment is successful, this document might become a BCP essentially
    as written."

   "I think the spirit of RFC 3933 is to get things tried out quickly,
    so I don't buy this. The community has been discussing related topics
    in the recent past. Of course, if many comments come in during LC,
    Sam would need to rethink."

   'I see "going back to BCP83" as so unpleasant to IESG members that the
    "experiments" will be extended.'

There are things that were said which were never done.  There are 
things that were predicted and that never happened.  Maybe it is 
because of process flaws.  Maybe it is because it is easier to give 
up instead of trying.

Regards,
-sm 


From housley@vigilsec.com  Fri Feb  1 08:16:16 2013
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4948C21E8044 for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 08:16:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.11
X-Spam-Level: 
X-Spam-Status: No, score=-101.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBnl6nMmujwp for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 08:16:15 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 9662021E8039 for <ietf@ietf.org>; Fri,  1 Feb 2013 08:15:50 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 078289A402F for <ietf@ietf.org>; Fri,  1 Feb 2013 11:15:52 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id tPOR212Q8WAI for <ietf@ietf.org>; Fri,  1 Feb 2013 11:15:45 -0500 (EST)
Received: from v150.vpn.iad.rg.net (v150.vpn.iad.rg.net [198.180.150.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 204689A4025 for <ietf@ietf.org>; Fri,  1 Feb 2013 11:15:49 -0500 (EST)
Subject: Re: Internet Hall of Fame Celebrates Internet Leaders: Second Annual Induction Ceremony Set for June 2013 in Istanbul, Turkey
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
X-Priority: 3 (Normal)
In-Reply-To: <102489A7-1F1E-4D5E-ADDF-9D3E4C761F9F@vigilsec.com>
Date: Fri, 1 Feb 2013 11:15:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B301C7A1-AD2E-411D-A81A-CCC8F06EF602@vigilsec.com>
References: <102489A7-1F1E-4D5E-ADDF-9D3E4C761F9F@vigilsec.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 16:16:16 -0000

The Internet Hall of Fame nominations are now open.  Please provide your =
nominations here: http://internethalloffame.org/nominations.=20

Thanks.
  Russ


> =
http://www.internetsociety.org/news/internet-hall-fame-celebrates-internet=
-leaders-second-annual-induction-ceremony-set-june-2013
>=20
> You may know someone that deserves to be nominated ...
>=20
> Russ
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D
>=20
> Internet Hall of Fame Celebrates Internet Leaders: Second Annual =
Induction Ceremony Set for June 2013 in Istanbul, Turkey=20
>=20
> Inductee Nominations Open January 11
>=20
> [Washington, D.C. and Geneva, Switzerland] =96 Building on the =
historic foundation it established earlier this year, the Internet Hall =
of Fame will once again help make history in 2013 when it honors =
individuals who have been important to the Internet=92s open development =
and growth. The Internet Society today announced that nominations for =
the second annual awards will open on January 11, and the 2013 inductees =
will be announced and honored at a ceremony held June 26, 2013 in =
Istanbul, Turkey.=20
>=20
> This year=92s Internet Hall of Fame will continue the important =
tradition of celebrating Internet visionaries, innovators, and leaders =
from around the world who have made significant contributions to the =
development and advancement of the open, global Internet.=20
>=20
> This year=92s nomination process is open to the public and the =
nomination form will be available on the Internet Hall of Fame website, =
www.internethalloffame.org, starting January 11, 2013. Nominees are =
considered for induction into one of the three categories:=20
>=20
> * Pioneers Circle: recognizing individuals instrumental in the early =
design and development of the Internet.
>=20
> * Innovators: recognizing individuals who made outstanding =
technological, commercial, or policy advances and helped to expand the =
Internet=92s reach.
>=20
> * Global Connectors: recognizing individuals who have made major =
contributions to the growth, connectivity, and use of the Internet, =
either on a global scale or within a specific region or community.
>=20
> =93The Internet Hall of Fame recognizes the extraordinary people who =
have helped to shape the Internet into the most successful global =
platform for communication, social, and economic development ever seen,=94=
 said Internet Society President and CEO Lynn St. Amour. =93We look =
forward to the second year and recognizing individuals from across the =
world for their passions, innovations, and commitments to the Internet =
and its role in making their communities =96 and the world =96 a better =
place.=94
>=20
> The inaugural Internet Hall of Fame inductees were announced in April =
2012 in Geneva, Switzerland, in conjunction with the Internet Society=92s =
20th anniversary celebration and Global INET event, which brought =
together Internet experts and enthusiasts to discuss the Internet=92s =
future. The Internet Hall of Fame will be held annually on a global =
rotation. The 2013 Internet Hall of Fame ceremony will be co-located =
with several other Internet Society regional events in Istanbul, Turkey, =
June 25-26, 2013.
>=20


From hartmans@mit.edu  Fri Feb  1 08:23:23 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B922521E8093 for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 08:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 c2F9b8rhEa6G for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 08:23:20 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 5661E21E8030 for <ietf@ietf.org>; Fri,  1 Feb 2013 08:23:20 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.101]) (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 752D120183; Fri,  1 Feb 2013 11:19:12 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 52EE343FD; Fri,  1 Feb 2013 11:23:10 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: SM <sm@resistor.net>
Subject: Re: When is a 3933 experiment necessary?
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <5109680A.1040400@dcrocker.net> <CAC4RtVCipnE2q-91eVJq0aEt_sr+J5DmgQQWH5qkE+QmTvoscw@mail.gmail.com> <6.2.5.6.2.20130201000341.09ae1080@resistor.net>
Date: Fri, 01 Feb 2013 11:23:10 -0500
In-Reply-To: <6.2.5.6.2.20130201000341.09ae1080@resistor.net> (sm@resistor.net's message of "Fri, 01 Feb 2013 02:23:41 -0800")
Message-ID: <tslpq0krok1.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org, Bernard Aboba <bernarda@microsoft.com>, Dave Crocker <dcrocker@bbiw.net>, John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Barry Leiba <barryleiba@computer.org>, "Lakshminath Dondeti <ldondeti@qualcomm.com> 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, 01 Feb 2013 16:23:23 -0000

>>>>> "SM" == SM  <sm@resistor.net> writes:


    SM> There are things that were said which were never done.  There
    SM> are things that were predicted and that never happened.  Maybe
    SM> it is because of process flaws.  Maybe it is because it is
    SM> easier to give up instead of trying.

Perhaps it's because the process works well enough these days that some
of us involved in process work in the past believe things are working
well enough now that the risk of change is greater than any likely
benefit.  That's generally my attitude these days. I generally haven't
supported process change proposals lately because I think things are
working quite well and I think the proposed improvements aren't worth
the risk.  For the most part I've stayed quiet because I think the risk
of harm is not huge either and if people can get together enough effort
to make a change it's probably not that horrible.  A few times I've
spoken up because something seemed like a really bad idea.  Fewer times
I've spoken up because something seemed like a really good idea.
In general though I'd like to be counted as a voice for the status quo;
I consider that a relatively well-considered opinion.

From sm@resistor.net  Fri Feb  1 09:00:18 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73E6B21E80AD for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 09:00:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 ujkw3J3Z7zPg for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 09:00:16 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8858021E80B1 for <ietf@ietf.org>; Fri,  1 Feb 2013 09:00:16 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r11H07vM029775; Fri, 1 Feb 2013 09:00:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359738013; bh=ZlNv1vS4+63NSSgQanMiBMd+akR5Arh0eUWJN92bJDE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WhTEoiO4OujtdbpLWLZPHPQfO/HcLdffjV0P2NquSzSC+Z6JeSjm2Xs7cP76xzP8u W+loGlss11mLbZmOACIoq8hCpJ/NLzh20dDfx84ljMo+hrucCdWFTRk6WHXtsSlsew PRZQOX9w5Pn9z+H0F9Y5AOroadHRPDBEh1jbqvDM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359738013; i=@resistor.net; bh=ZlNv1vS4+63NSSgQanMiBMd+akR5Arh0eUWJN92bJDE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vF+oFca9zisbW7bORztNaV82O8JeXLhRXAw6yFL8y1cSrVWiGUGOySsrNaIaXEqMF pV5rEKOWT1BFml0BXkjtgze0yw47nd1k8glMUw+X4f6l2cjXsBpaw8oDWibSoeeXKy AY+/jHrpJnKiQELtbFjGRw9mCcXyRV7hzID03yF4=
Message-Id: <6.2.5.6.2.20130201080531.0a251560@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 01 Feb 2013 08:49:47 -0800
To: "t.p." <daedulus@btconnect.com>
From: SM <sm@resistor.net>
Subject: Re: Reducing time to publication: was Re: FW: Last Call:  <draft-farrell-ft-03.txt> (A Fast-Track way toRFCwith Running Code) to Experimental RFC
In-Reply-To: <002101ce005e$23f04dc0$4001a8c0@gateway.2wire.net>
References: <20130125213624.E984F1A495@ld9781.wdf.sap.corp> <51030B76.2070401@cs.tcd.ie> <00c401cdfc80$2bcbc380$4001a8c0@gateway.2wire.net> <004901cdffac$1e04c7e0$4001a8c0@gateway.2wire.net> <6.2.5.6.2.20130131073013.0aa87df0@resistor.net> <002101ce005e$23f04dc0$4001a8c0@gateway.2wire.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 17:00:19 -0000

Hi Tom,
At 01:24 01-02-2013, t.p. wrote:
>Yes, this is all available on the datatracker (which is the home page on
>my web browser) but it takes me several minutes to go there and absorb
>the content, repeated for every Working Group in which I am involved.
>The datatracker has too much information, I have to scroll up and down,
>since each entry takes 5 or 10 lines.  My idea is a one line summary for
>each I-D, in a defined sort order (I-D name).  And I know how much more
>productive I am when I get gentle prompts about what is going on, be
>they via SMS, e-mail or whatever.  Sensible organisations, from
>libraries to garages, are making the most of this technology - we should
>do the same.

I was not suggesting that you should go to the datatracker web page. :-)

The data for what you suggested is already available.  It should be 
possible to write a script which picks up the relevant information 
and send emails that to the relevant working groups automatically 
(the tool you suggested).

Regards,
-sm 


From abdussalambaryun@gmail.com  Fri Feb  1 17:34:59 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 811D721F8E05 for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 17:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKVDGKy2BXq8 for <ietf@ietfa.amsl.com>; Fri,  1 Feb 2013 17:34:59 -0800 (PST)
Received: from mail-we0-x229.google.com (we-in-x0229.1e100.net [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id DBD6A21F8E02 for <ietf@ietf.org>; Fri,  1 Feb 2013 17:34:58 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id t11so3616513wey.28 for <ietf@ietf.org>; Fri, 01 Feb 2013 17:34:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=EyqNPc1m8VmQ/ypywQx4Msy5WB1hrypR69r2zbHJNr4=; b=RnD60d7qPVfJJ0XZ9XZho6/DNyyqyOV9ydgj88H6GYExynHHVLchaHUARStjg3hupQ WXYTbmMpUVBI+rP8xivJp5asbur3dRzpoaJBzh+uBtmoXH2qnH0+wdtuidHe5NSL7Czu v8/m5bK5ugHm+Ilo0ft4D5vSL40Djv5BevbBFLGXENoOyn0h+jSX0zgR+FNJFE4IaDVN E+pOaxSm6xqQbvAUKboX6ZqW1eIIci1dTJj3kMPs3B4rpwFQFD4qj0vrzeU5TxaEQbF9 EdeD7Sl1ymfnueGSXc0i2AHmGwEnEzmtUvjUSgV/DG5P9BlBmTzRw+rEHTxXeoXxKkxD EobA==
MIME-Version: 1.0
X-Received: by 10.194.90.242 with SMTP id bz18mr5191552wjb.24.1359768898061; Fri, 01 Feb 2013 17:34:58 -0800 (PST)
Received: by 10.180.14.33 with HTTP; Fri, 1 Feb 2013 17:34:57 -0800 (PST)
Date: Sat, 2 Feb 2013 02:34:57 +0100
Message-ID: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com>
Subject: History of protocol discussion or process in WG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Feb 2013 01:34:59 -0000

I recommend that IETF WGs consider start an initial historical I-D
including their memories of important process or design of protocols,
at least each 20 years WG participants could document their technical
involvement history within WG work.

AB

From nick@inex.ie  Sat Feb  2 01:49:44 2013
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3BC521F907A for <ietf@ietfa.amsl.com>; Sat,  2 Feb 2013 01:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  BAYES_00=-2.599, 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 kEJJHRQiNalr for <ietf@ietfa.amsl.com>; Sat,  2 Feb 2013 01:49:44 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id F184521F9078 for <ietf@ietf.org>; Sat,  2 Feb 2013 01:49:42 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org ([IPv6:2001:4d68:2002:100::110]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id r129lAV5039112 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 2 Feb 2013 09:47:15 GMT (envelope-from nick@inex.ie)
Message-ID: <510CE12E.8060206@inex.ie>
Date: Sat, 02 Feb 2013 09:49:34 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: History of protocol discussion or process in WG
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com>
In-Reply-To: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com>
X-Enigmail-Version: 1.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Feb 2013 09:49:45 -0000

On 02/02/2013 01:34, Abdussalam Baryun wrote:
> I recommend that IETF WGs consider start an initial historical I-D
> including their memories of important process or design of protocols,
> at least each 20 years WG participants could document their technical
> involvement history within WG work.

The IETF is a bottom up process, so if you want to volunteer for this I'm
sure everyone would be very pleased.

Nick


From swb@internet2.edu  Sat Feb  2 05:15:40 2013
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F396521F9082 for <ietf@ietfa.amsl.com>; Sat,  2 Feb 2013 05:15:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.949
X-Spam-Level: 
X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[AWL=-1.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 j90MMPizOBNb for <ietf@ietfa.amsl.com>; Sat,  2 Feb 2013 05:15:39 -0800 (PST)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id 43BBD21F907C for <ietf@ietf.org>; Sat,  2 Feb 2013 05:15:39 -0800 (PST)
Received: from mail13-db3-R.bigfish.com (10.3.81.253) by DB3EHSOBE007.bigfish.com (10.3.84.27) with Microsoft SMTP Server id 14.1.225.23; Sat, 2 Feb 2013 13:15:37 +0000
Received: from mail13-db3 (localhost [127.0.0.1])	by mail13-db3-R.bigfish.com (Postfix) with ESMTP id 57D3F300396; Sat,  2 Feb 2013 13:15:37 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.149; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0810HT001.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 0
X-BigFish: S0(zzbb2dI98dI1432Izz1d77h1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzz8275bhz2dh2a8h668h839h93fhd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h1155h)
Received: from mail13-db3 (localhost.localdomain [127.0.0.1]) by mail13-db3 (MessageSwitch) id 1359810935425254_28578; Sat,  2 Feb 2013 13:15:35 +0000 (UTC)
Received: from DB3EHSMHS019.bigfish.com (unknown [10.3.81.247])	by mail13-db3.bigfish.com (Postfix) with ESMTP id 52343260068; Sat,  2 Feb 2013 13:15:35 +0000 (UTC)
Received: from CH1PRD0810HT001.namprd08.prod.outlook.com (157.56.245.149) by DB3EHSMHS019.bigfish.com (10.3.87.119) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sat, 2 Feb 2013 13:15:30 +0000
Received: from CH1PRD0810MB395.namprd08.prod.outlook.com ([169.254.11.166]) by CH1PRD0810HT001.namprd08.prod.outlook.com ([10.255.145.164]) with mapi id 14.16.0263.000; Sat, 2 Feb 2013 13:15:30 +0000
From: Scott Brim <swb@internet2.edu>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: History of protocol discussion or process in WG
Thread-Topic: History of protocol discussion or process in WG
Thread-Index: AQHOAOWHVPIARZMEpUaQh5FzMUQEaphmOSAA
Date: Sat, 2 Feb 2013 13:15:30 +0000
Message-ID: <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com>
In-Reply-To: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.145.132]
Content-Type: text/plain; charset="utf-8"
Content-ID: <640A3622C74107468E5E92249D67102C@namprd08.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: internet2.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Feb 2013 13:15:40 -0000

T24gMDIvMDEvMTMgMjA6MzQsICJBYmR1c3NhbGFtIEJhcnl1biIgPGFiZHVzc2FsYW1iYXJ5dW5A
Z21haWwuY29tPg0KYWxsZWdlZGx5IHdyb3RlOg0KDQo+SSByZWNvbW1lbmQgdGhhdCBJRVRGIFdH
cyBjb25zaWRlciBzdGFydCBhbiBpbml0aWFsIGhpc3RvcmljYWwgSS1EDQo+aW5jbHVkaW5nIHRo
ZWlyIG1lbW9yaWVzIG9mIGltcG9ydGFudCBwcm9jZXNzIG9yIGRlc2lnbiBvZiBwcm90b2NvbHMs
DQo+YXQgbGVhc3QgZWFjaCAyMCB5ZWFycyBXRyBwYXJ0aWNpcGFudHMgY291bGQgZG9jdW1lbnQg
dGhlaXIgdGVjaG5pY2FsDQo+aW52b2x2ZW1lbnQgaGlzdG9yeSB3aXRoaW4gV0cgd29yay4NCj4N
Cj5BQg0KPg0KPg0KDQpXaGF0PyAgSG93IGFib3V0IFJGQyA1MjE4Pw0KDQpUaGlzIGlzIGRvbmUg
YWxsIHRoZSB0aW1lIHRocm91Z2ggdGhlIFdHIHByb2Nlc3MsIGFuZCBpdCBjaGFuZ2VzIGFsbCB0
aGUNCnRpbWUgdG9vLCB3aGljaCBpcyBhcHByb3ByaWF0ZS4NCg0K


From abdussalambaryun@gmail.com  Sun Feb  3 04:17:05 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D5621F863A for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 04:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HV6JoSqkDS3e for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 04:17:05 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 331F621F8630 for <ietf@ietf.org>; Sun,  3 Feb 2013 04:17:05 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id k14so4003380wer.25 for <ietf@ietf.org>; Sun, 03 Feb 2013 04:17:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mImiUOq/ePzjsMTOKqPNDriQMN174iIeI0vdBBoJ2AY=; b=Lm0rRJ2mswZxV4cbQODD8FdG72nvk3xRDcUzg7jj5pPwsXqmFrBiYJ57weSqFgBH0Q FDjDnM9NY+86E9kzHBFGKO4VNxqTxzlOjCbsFnUPbK+qagBxFVIyVKhTGvr+bzI8wFbR VRCi86HJSADqr/KQqb0UZg0f6we0NNHySYiv6sj3zAujLT6vZf8jpXk4axp83GvEdYzh 6lKsKQWtLSBq/ZmoxHsbnT6F/Ybpw2Wv3HDdrq4DLtucYRJOdzuO5hH44SQjxqNSQnHn rEg78uTkm0ijN9Au8+89S0QDclJbOleH7VTAPnZEqk469vHgZ7dYgBOx+CNOvZByzWFG TSBA==
MIME-Version: 1.0
X-Received: by 10.180.73.80 with SMTP id j16mr5677162wiv.5.1359893824186; Sun, 03 Feb 2013 04:17:04 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 3 Feb 2013 04:17:03 -0800 (PST)
In-Reply-To: <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com>
Date: Sun, 3 Feb 2013 13:17:03 +0100
Message-ID: <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com>
Subject: Re: History of protocol discussion or process in WG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Scott Brim <swb@internet2.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 12:17:06 -0000

On 2/2/13, Scott Brim <swb@internet2.edu> wrote:
> What?  How about RFC 5218?
>
> This is done all the time through the WG process, and it changes all the
> time too, which is appropriate.

Many WG open and close in IETF with no history-ID/report of such
efforts including success or failur issues. If documents produced, new
generation can benefit from these IDs

AB

From lixia@cs.ucla.edu  Sun Feb  3 08:29:39 2013
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 244D321F8573 for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPOcGH6uUCin for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:29:38 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id B946621F8200 for <ietf@ietf.org>; Sun,  3 Feb 2013 08:29:38 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 1AA3239E8108; Sun,  3 Feb 2013 08:29:38 -0800 (PST)
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 V5YvJ3AQF+JV; Sun,  3 Feb 2013 08:29:37 -0800 (PST)
Received: from [10.0.1.3] (cpe-76-174-95-149.socal.res.rr.com [76.174.95.149]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 5BD8B39E8105; Sun,  3 Feb 2013 08:29:37 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: History of protocol discussion or process in WG
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com>
Date: Sun, 3 Feb 2013 08:29:37 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 16:29:39 -0000

On Feb 3, 2013, at 4:17 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> On 2/2/13, Scott Brim <swb@internet2.edu> wrote:
>> What?  How about RFC 5218?
>>=20
>> This is done all the time through the WG process, and it changes all =
the
>> time too, which is appropriate.
>=20
> Many WG open and close in IETF with no history-ID/report of such
> efforts including success or failur issues. If documents produced, new
> generation can benefit from these IDs
>=20
> AB

+1

5218 is a general document; I believe what AB suggested is a historical =
record specifically for each WG: what you started with, what you went =
through, how you ended, what you have learned, both principles and =
lessons.

Lixia=

From john-ietf@jck.com  Sun Feb  3 08:43:24 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B667421F882A for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 SOzEOpbCRQfy for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:43:23 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 41B8C21F8635 for <ietf@ietf.org>; Sun,  3 Feb 2013 08:43:12 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1U22em-000As2-I4; Sun, 03 Feb 2013 11:43:04 -0500
X-Vipre-Scanned: 03EFBF27002C3103EFC074-TDI
Date: Sun, 03 Feb 2013 11:43:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'Spencer Dawkins' <spencer@wonderhamster.org>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC]
Message-ID: <19AA382FDB4F7503FF73D4FE@[192.168.1.128]>
In-Reply-To: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2013 16:43:24 -0000

--On Wednesday, January 30, 2013 09:15 +0000 Adrian Farrel
<adrian@olddog.co.uk> wrote:

>...
> So, my conclusion: it would be good to have more process
> experiments if people feel the process needs to change.
> However, it would appear that such experiments need:
> - Thorough debate on an appropriate mailing list first
>    Do we need a "process experiments" mailing list?
> - Very clear expression of the purpose of the experiment
>    and how it will be evaluated
> - Very tight scoping to a portion of the IETF or of the IETF's
>    work so that the risk of the experiment simply changing
>    the IETF's process by default is removed

For whatever it is worth, I agree with this summary and
especially with the third point (which is where I think this
effort may have gotten into trouble).  I also agree with Dave's
observation about getting a "committed core" together.  I also
think it is useful to differentiate between the elements of the
experiment that constitutes a process variation and hence makes
community approval desirable and possibly necessary and the
elements that can be tested within the discretion of ADs, WG
Chairs, etc., and make that differentiation clear.  In some
cases, one of those categories will be unpopulated but I note
that one of the things that complicated the recent discussion
was a lot of "nothing is new here, why not just do it on a
selective basis and report back" comments.

All of this could be summarized as "it is better to have one's
ducks lined up before starting a community-wide discussion".

Re Spencer's analysis...

>> I was John's co-author on RFC 3933
>> (http://tools.ietf.org/html/rfc3933). When we were working on
>> the draft, the problem I thought we were solving, was that
>> the IESG needs to update the IETF's BCP processes from time
>> to time, but (1) it was like 32 simultaneous root canals to
>> actually get community consensus to modify the IETF's process
>> BCPs including untried changes that might be improvements, so
>> (2) the IESG was using informal IESG statements developed
>> with much less community involvement than was expected for
>> process BCP changes, in order to get anything done at all.
>> 
>> I (and, I think, John as well) saw RFC 3933 process
>> experiments as a middle path between lightweight IESG
>> decisions and full process BCP revisions. That's what I
>> thought Section 2 of RFC 3933 was trying to say.

Yes.  And I (and I think Spencer) hoped that the IESG would use
this mechanism in preference to simply ignoring a BCP process
provision that had become outdated.  To be a bit more explicit
about the language in 3933 on that subject, I (at least) felt
that there was always going to be a need for IESG judgment on
when statements were appropriate and when 3933 was needed.
Trying to write rules to establish a precise boundary seemed
impossible and likely to lead to more trouble.  What 3933
doesn't say explicitly, but could have, is that, if the
community disagrees with the pattern of the IESG's judgments of
such things, that ought to be a matter for discussion with the
Nomcom (or, at least in theory, appeals or recalls for specific
egregious cases).

>> I had assumed that if the IESG clearly had discretion to do
>> something under the current process BCPs, and thought it was
>> the right thing to do, they would just do it, rather than set
>> up a process experiment.

I assumed that too.  See comment above about differentiating a
3933 experiment (or 3933 part of a larger experiment) from a
discretionary one.  Interestingly, one of the things that has
changed since we wrote what because 3933 is that, at the time,
the IESG typically issued statements without prior community
discussion.  In more recent years, and for matters where a
statement has been more than the IESG telling the community how
it is doing things, such statements have more often been exposed
to community comment before taking effect.  So, where we had
three possibilities when 3933 was adopted, more or less:

	* IESG Prouncement
	* 3933 Experiment
	* BCP

We now have "IESG Statement after soliciting and considering
community opinions" as another possibility for which there are
worked examples.  That may reasonably narrow the number of cases
in which 3933 is necessary.

best,
   john


From dhc@dcrocker.net  Sun Feb  3 08:56:03 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033E021F8622 for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:56:03 -0800 (PST)
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 e1arTsZVpyY8 for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 08:56:02 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9AF21F8506 for <ietf@ietf.org>; Sun,  3 Feb 2013 08:56:02 -0800 (PST)
Received: from [172.17.100.106] (rrcs-24-43-241-82.west.biz.rr.com [24.43.241.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r13Gu1WD006044 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Feb 2013 08:56:01 -0800
Message-ID: <510E9695.9060008@dcrocker.net>
Date: Sun, 03 Feb 2013 08:55:49 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: When is a 3933 experiment necessary? [Was: Last Call: <draft-farrell-ft-03.txt> (A Fast-Track way to RFC	with Running Code) to Experimental RFC]
References: <008501cdfeca$59a77cd0$0cf67670$@olddog.co.uk> <19AA382FDB4F7503FF73D4FE@[192.168.1.128]>
In-Reply-To: <19AA382FDB4F7503FF73D4FE@[192.168.1.128]>
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, 03 Feb 2013 08:56:02 -0800 (PST)
Cc: adrian@olddog.co.uk, 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: Sun, 03 Feb 2013 16:56:03 -0000

On 2/3/2013 8:43 AM, John C Klensin wrote:
> All of this could be summarized as "it is better to have one's
> ducks lined up before starting a community-wide discussion".


for the IETF, you mean cats shepherded, not ducks lined up...

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From hartmans@mit.edu  Sun Feb  3 10:28:13 2013
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE8FF21F85FC for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 10:28:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level: 
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybYx9l5lHltu for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 10:28:13 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4866021F8519 for <ietf@ietf.org>; Sun,  3 Feb 2013 10:28:11 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (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 B780E20393; Sun,  3 Feb 2013 13:24:08 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 3143343FD; Sun,  3 Feb 2013 13:28:07 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: History of protocol discussion or process in WG
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu>
Date: Sun, 03 Feb 2013 13:28:07 -0500
In-Reply-To: <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> (Lixia Zhang's message of "Sun, 3 Feb 2013 08:29:37 -0800")
Message-ID: <tslip69jlqg.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>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 18:28:13 -0000

>>>>> "Lixia" == Lixia Zhang <lixia@cs.ucla.edu> writes:


    Lixia> 5218 is a general document; I believe what AB suggested is a
    Lixia> historical record specifically for each WG: what you started
    Lixia> with, what you went through, how you ended, what you have
    Lixia> learned, both principles and lessons.

I'm not sure I've ever been involved with a WG where you could have
gotten consensus on any of the above enough to publish it.  Nor can I
think of many WGs that have the excess energy to do this work.  Even
getting consensus on a summary of where you ended up is quite
tricky. Because of who I'm responding to I'm imagining getting consensus
on a summary of where the RRG ended up on the discussion of well
whatever it is that they were discussing regarding id/loc split and all
that stuff.
WGs aren't particularly easier in this regard.
You could probably get consensus on which set of documents a WG
published in most cases, but if you added any context, say a discussion
about whether those documents are still good ideas, it becomes a lot
harder.

This has value. I've supported certain aspects of the ISD proposals, of
some things coming out of newtrk, etc. One aspect I've always disagreed
with is proposals of this type that proposed to be generally applicable
across the IETF.
I agree that writing down where we were, where we are, what happened in
between can be valuable. However it is quite expensive, and we need to
balance that.

From dhc@dcrocker.net  Sun Feb  3 10:39:13 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC31921F8581 for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 10:39:12 -0800 (PST)
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 T3iIhdktb9lK for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 10:39:10 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E7A3621F8495 for <ietf@ietf.org>; Sun,  3 Feb 2013 10:39:10 -0800 (PST)
Received: from [172.17.100.106] (rrcs-24-43-241-82.west.biz.rr.com [24.43.241.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r13IcwXk007099 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Feb 2013 10:39:02 -0800
Message-ID: <510EAEB7.9060703@dcrocker.net>
Date: Sun, 03 Feb 2013 10:38:47 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: History of protocol discussion or process in WG
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu>
In-Reply-To: <tslip69jlqg.fsf@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]); Sun, 03 Feb 2013 10:39:02 -0800 (PST)
Cc: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.edu>
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, 03 Feb 2013 18:39:13 -0000

On 2/3/2013 10:28 AM, Sam Hartman wrote:
> I'm not sure I've ever been involved with a WG where you could have
> gotten consensus on any of the above enough to publish it.  Nor can I
> think of many WGs that have the excess energy to do this work.  Even
> getting consensus on a summary of where you ended up is quite
> tricky.


Getting consensus on the details of a history is much more difficult 
than on a technical spec...

So don't try.

What I think /is/ possible, however, is to establish a "history of" 
wiki, to which participants can contribute their views.

Moderate it, to limit the noise.  Solicit and vet contributions from 
principals, to seed the data with credible material.

Then let historians worry about synthesizing this source data into 
something more coherent (and biased, and ...)

But at least the raw narrative of motivated principals will have been 
captured.

In terms of administrative overhead, there isn't much, other than 
creating a separate page for each activity.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From rbarnes@bbn.com  Sun Feb  3 11:13:41 2013
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 C309721F84E2; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0Gom1g8l1WI; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 4311121F8472; Sun,  3 Feb 2013 11:13:41 -0800 (PST)
Received: from [128.89.253.237] (port=51500) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1U250R-000MCE-OU; Sun, 03 Feb 2013 14:13:35 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
Date: Sun, 3 Feb 2013 14:13:36 -0500
Message-Id: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Cc: draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 19:13:41 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer =
for this draft (for background on Gen-ART, please =
seehttp://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-ccamp-lmp-behavior-negotiation-10
Reviewer: Richard Barnes
Review Date: 2013-02-02
IETF LC End Date: 2012-01-21
IESG Telechat date: 2012-02-07

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

Comment:

Overall, this document seems very clear and readable.  Thanks!  The one =
concern I have is over the use of "likely" in the discussion of backward =
compatibility; I would like to see more precise language there.

Section 2.1.  Would be helpful to either include the old formats and/or =
say explicitly what is changing.=20

Section 2.2. =20
"Nodes which support" -> "nodes that support" =20
"Ordering of CONFIG objects" -> "... With different C-type values"

Section 3.1.MBZ. Might help to clarify that this means that the number =
of bits MUST be a multiple of 32. (I got a little confused between bits =
and bytes here.)

Section 4. "Likely"
Is it possible for a 4204-compliant implementation to not do one of =
these?  If so then remove "likely".  If not, then why happens on the =
exceptional case?=

From swb@internet2.edu  Sun Feb  3 13:04:41 2013
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E825B21F881E for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.774
X-Spam-Level: 
X-Spam-Status: No, score=-5.774 tagged_above=-999 required=5 tests=[AWL=0.825,  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 l+K9LOr+2vaK for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:04:41 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe003.messaging.microsoft.com [65.55.88.13]) by ietfa.amsl.com (Postfix) with ESMTP id E847721F8629 for <ietf@ietf.org>; Sun,  3 Feb 2013 13:04:40 -0800 (PST)
Received: from mail139-tx2-R.bigfish.com (10.9.14.243) by TX2EHSOBE002.bigfish.com (10.9.40.22) with Microsoft SMTP Server id 14.1.225.23; Sun, 3 Feb 2013 21:04:40 +0000
Received: from mail139-tx2 (localhost [127.0.0.1])	by mail139-tx2-R.bigfish.com (Postfix) with ESMTP id EC305600A6; Sun,  3 Feb 2013 21:04:39 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.149; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0810HT005.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 1
X-BigFish: S1(zzbb2dI98dIzz1d77h1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h93fhe5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h1155h)
Received: from mail139-tx2 (localhost.localdomain [127.0.0.1]) by mail139-tx2 (MessageSwitch) id 1359925478353624_18074; Sun,  3 Feb 2013 21:04:38 +0000 (UTC)
Received: from TX2EHSMHS023.bigfish.com (unknown [10.9.14.238])	by mail139-tx2.bigfish.com (Postfix) with ESMTP id 4874D160489; Sun,  3 Feb 2013 21:04:38 +0000 (UTC)
Received: from CH1PRD0810HT005.namprd08.prod.outlook.com (157.56.245.149) by TX2EHSMHS023.bigfish.com (10.9.99.123) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 3 Feb 2013 21:04:38 +0000
Received: from CH1PRD0810MB395.namprd08.prod.outlook.com ([169.254.11.23]) by CH1PRD0810HT005.namprd08.prod.outlook.com ([10.255.145.168]) with mapi id 14.16.0263.000; Sun, 3 Feb 2013 21:04:37 +0000
From: Scott Brim <swb@internet2.edu>
To: Lixia Zhang <lixia@cs.ucla.edu>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: History of protocol discussion or process in WG
Thread-Topic: History of protocol discussion or process in WG
Thread-Index: AQHOAOWHVPIARZMEpUaQh5FzMUQEaphmOSAAgAHV1ICAAEaRgP//+QAA
Date: Sun, 3 Feb 2013 21:04:37 +0000
Message-ID: <CD343ABF.51B5%swb@internet2.edu>
In-Reply-To: <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.145.132]
Content-Type: text/plain; charset="utf-8"
Content-ID: <DA9D2E68E0FBBC4985E0FD13DAEEB549@namprd08.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: internet2.edu
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 21:04:42 -0000

T24gMDIvMDMvMTMgMTE6MjksICJMaXhpYSBaaGFuZyIgPGxpeGlhQGNzLnVjbGEuZWR1PiBhbGxl
Z2VkbHkgd3JvdGU6DQoNCj5JIGJlbGlldmUgd2hhdCBBQiBzdWdnZXN0ZWQgaXMgYSBoaXN0b3Jp
Y2FsIHJlY29yZCBzcGVjaWZpY2FsbHkgZm9yIGVhY2gNCj5XRzogd2hhdCB5b3Ugc3RhcnRlZCB3
aXRoLCB3aGF0IHlvdSB3ZW50IHRocm91Z2gsIGhvdyB5b3UgZW5kZWQsIHdoYXQgeW91DQo+aGF2
ZSBsZWFybmVkLCBib3RoIHByaW5jaXBsZXMgYW5kIGxlc3NvbnMuDQoNCjkwJSBvZiB0aGF0IGlz
IG1lZXRpbmcgbm90ZXMuICBFdmVyeW9uZSBrZWVwcyBnb29kIG1lZXRpbmcgbm90ZXMsIHJpZ2h0
Pw0KKDotcCkuICBUaGUgcmVzdCwgd2VsbCwgdGhlIGNoYWlycyBjb3VsZCB3cml0ZSBpdCBhdCBX
RyBjbG9zdXJlIGFuZA0KcHJvYmFibHkgbm90IGdldCBhbnkgc2lnbmlmaWNhbnQgY29tcGxhaW50
cy4NCg0K


From joelja@bogus.com  Sun Feb  3 13:17:56 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20DA321F853E for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:17:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 XRRChMlz0NQO for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:17:55 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id A7FFF21F84E6 for <ietf@ietf.org>; Sun,  3 Feb 2013 13:17:55 -0800 (PST)
Received: from joels-MacBook-Air.local (96.sub-70-199-78.myvzw.com [70.199.78.96]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r13LHiJG046187 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 3 Feb 2013 21:17:45 GMT (envelope-from joelja@bogus.com)
Message-ID: <510ED3F4.2090807@bogus.com>
Date: Sun, 03 Feb 2013 13:17:40 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Scott Brim <swb@internet2.edu>, Lixia Zhang <lixia@cs.ucla.edu>, Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: History of protocol discussion or process in WG
References: <CD343ABF.51B5%swb@internet2.edu>
In-Reply-To: <CD343ABF.51B5%swb@internet2.edu>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 03 Feb 2013 21:17:46 +0000 (UTC)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 21:17:56 -0000

On 2/3/13 1:04 PM, Scott Brim wrote:
> On 02/03/13 11:29, "Lixia Zhang" <lixia@cs.ucla.edu> allegedly wrote:
>
>> I believe what AB suggested is a historical record specifically for each
>> WG: what you started with, what you went through, how you ended, what you
>> have learned, both principles and lessons.
> 90% of that is meeting notes.  Everyone keeps good meeting notes, right?
> (:-p).  The rest, well, the chairs could write it at WG closure and
> probably not get any significant complaints.
Having responded to an appeal associated with handling of a WG document, 
there can easily be 2000k worth of messages sitting in the archives 
arcoss multiple lists for a given document.


From nick@inex.ie  Sun Feb  3 13:23:59 2013
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15EDE21F886A for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.574
X-Spam-Level: 
X-Spam-Status: No, score=-2.574 tagged_above=-999 required=5 tests=[AWL=0.026,  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 tV2iI7Y8xBpH for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 13:23:56 -0800 (PST)
Received: from mail.acquirer.com (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 7943A21F884A for <ietf@ietf.org>; Sun,  3 Feb 2013 13:23:52 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from cupcake.foobar.org (twinkie.foobar.org [87.192.56.84]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id r13LLEE3049315 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 3 Feb 2013 21:21:20 GMT (envelope-from nick@inex.ie)
Message-ID: <510ED55C.1090405@inex.ie>
Date: Sun, 03 Feb 2013 21:23:40 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: History of protocol discussion or process in WG
References: <CD343ABF.51B5%swb@internet2.edu> <510ED3F4.2090807@bogus.com>
In-Reply-To: <510ED3F4.2090807@bogus.com>
X-Enigmail-Version: 1.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=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: Sun, 03 Feb 2013 21:23:59 -0000

On 03/02/2013 21:17, joel jaeggli wrote:
> Having responded to an appeal associated with handling of a WG document,
> there can easily be 2000k worth of messages sitting in the archives arcoss
> multiple lists for a given document.

I forsee many phds for future anthropologists and social historians.

Nick


From joelja@bogus.com  Sun Feb  3 14:04:49 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3FB21F88AE for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 14:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSS5x4gioAWI for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 14:04:49 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2FE8621F8428 for <ietf@ietf.org>; Sun,  3 Feb 2013 14:04:49 -0800 (PST)
Received: from joels-MacBook-Air.local (96.sub-70-199-78.myvzw.com [70.199.78.96]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r13M4lI6046777 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 3 Feb 2013 22:04:48 GMT (envelope-from joelja@bogus.com)
Message-ID: <510EDEFB.9090407@bogus.com>
Date: Sun, 03 Feb 2013 14:04:43 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
Subject: Re: History of protocol discussion or process in WG
References: <CD343ABF.51B5%swb@internet2.edu> <510ED3F4.2090807@bogus.com> <510ED55C.1090405@inex.ie>
In-Reply-To: <510ED55C.1090405@inex.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 03 Feb 2013 22:04:49 +0000 (UTC)
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 22:04:49 -0000

On 2/3/13 1:23 PM, Nick Hilliard wrote:
> On 03/02/2013 21:17, joel jaeggli wrote:
>> Having responded to an appeal associated with handling of a WG document,
>> there can easily be 2000k worth of messages sitting in the archives arcoss
>> multiple lists for a given document.
> I forsee many phds for future anthropologists and social historians.
I know somebody who reconsidered the wisdom of doing a master's thesis 
that involved the RSVP WG process.
> Nick
>


From lixia@cs.ucla.edu  Sun Feb  3 15:56:39 2013
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 942E321F8871 for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 15:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWx4leldSJ+C for <ietf@ietfa.amsl.com>; Sun,  3 Feb 2013 15:56:39 -0800 (PST)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 1F00821F886A for <ietf@ietf.org>; Sun,  3 Feb 2013 15:56:39 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id EC81039E8105; Sun,  3 Feb 2013 15:56:38 -0800 (PST)
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 1bEkgjgoVrc9; Sun,  3 Feb 2013 15:56:38 -0800 (PST)
Received: from [10.0.1.3] (cpe-76-174-95-149.socal.res.rr.com [76.174.95.149]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 5954339E8008; Sun,  3 Feb 2013 15:56:38 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: History of protocol discussion or process in WG
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <tslip69jlqg.fsf@mit.edu>
Date: Sun, 3 Feb 2013 15:56:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E9AD225B-31A6-41CE-986A-B0864EB2B8B5@cs.ucla.edu>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu>
To: ietf list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
Cc: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Feb 2013 23:56:39 -0000

got several quick replies!
a few points:

1/ there seem 2 separable issues:
- whether AB's suggestion is something worth considering doing
- whether one believes it is feasible to do it.

Lets not mix the two.

2/ there seems an implicit assumption that, if a history record is =
written, it'd only document one view (hence all the concerns about not =
being able to agree)?

Maybe it is best to document different opinions if different opinions =
exist?  Some time down the road IETF can look back, not only see which =
opinion has a better match to the reality (or even none of them), but =
also (hopefully!) understand better where our thought has gone =
right/wrong.

3/ no question that doing this would take time and effort, just like =
anything else that is worth doing. So the real question is: would this =
be worth trying?

Lixia
PS: would very much like to, but probably wont be able to keep up with =
this discussion (and will miss next IETF to chat with people in person)


On Feb 3, 2013, at 10:28 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:

>>>>>> "Lixia" =3D=3D Lixia Zhang <lixia@cs.ucla.edu> writes:
>=20
>=20
>    Lixia> 5218 is a general document; I believe what AB suggested is a
>    Lixia> historical record specifically for each WG: what you started
>    Lixia> with, what you went through, how you ended, what you have
>    Lixia> learned, both principles and lessons.
>=20
> I'm not sure I've ever been involved with a WG where you could have
> gotten consensus on any of the above enough to publish it.  Nor can I
> think of many WGs that have the excess energy to do this work.  Even
> getting consensus on a summary of where you ended up is quite
> tricky. Because of who I'm responding to I'm imagining getting =
consensus
> on a summary of where the RRG ended up on the discussion of well
> whatever it is that they were discussing regarding id/loc split and =
all
> that stuff.
> WGs aren't particularly easier in this regard.
> You could probably get consensus on which set of documents a WG
> published in most cases, but if you added any context, say a =
discussion
> about whether those documents are still good ideas, it becomes a lot
> harder.
>=20
> This has value. I've supported certain aspects of the ISD proposals, =
of
> some things coming out of newtrk, etc. One aspect I've always =
disagreed
> with is proposals of this type that proposed to be generally =
applicable
> across the IETF.
> I agree that writing down where we were, where we are, what happened =
in
> between can be valuable. However it is quite expensive, and we need to
> balance that.


From barryleiba.mailing.lists@gmail.com  Mon Feb  4 05:00:47 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E97821F8682; Mon,  4 Feb 2013 05:00:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.009
X-Spam-Level: 
X-Spam-Status: No, score=-103.009 tagged_above=-999 required=5 tests=[AWL=-0.032, 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 Eha3VHC58Gyx; Mon,  4 Feb 2013 05:00:46 -0800 (PST)
Received: from mail-ve0-f182.google.com (mail-ve0-f182.google.com [209.85.128.182]) by ietfa.amsl.com (Postfix) with ESMTP id 31B7421F8615; Mon,  4 Feb 2013 05:00:46 -0800 (PST)
Received: by mail-ve0-f182.google.com with SMTP id ox1so3820079veb.13 for <multiple recipients>; Mon, 04 Feb 2013 05:00:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=s2b/oz2taF8OGQKtwLXBs/ILisbzCjg4+3Xsl1eajoc=; b=CqUIbL6cEiJSjFV2yHwCLBFXpFsRKNYr5YVBrmQNhDgECSbPbS0g1kq4cmHghYYGRd lOWodA2Q32kpTVcxJc0dd1eJrN+DwIY7MIj74n/T1gKXb97ZGxHxje0HRH2q4LV3icPE 1aFX4rGgqrK2umtQlau9xVxNBMaE63HXUb7x+gEOvoz9fhxrs4C53ZnGTihtEgoD/9L1 BwvlKUNTgMDJYG/Jk1xmGZOASCANubHR/CGFXIR02M6pbDlDJ7OieIO4iiynfc+Mb1XZ N+yJbhl03O/abeYAIgw3fYvq2fqKSqzFk6voGdd6f53ANQ4G4shx9TMIAcKgSN6mG4bP U73w==
MIME-Version: 1.0
X-Received: by 10.52.67.133 with SMTP id n5mr19187451vdt.24.1359982845629; Mon, 04 Feb 2013 05:00:45 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 4 Feb 2013 05:00:45 -0800 (PST)
In-Reply-To: <20130123160445.29483.85902.idtracker@ietfa.amsl.com>
References: <20130123160445.29483.85902.idtracker@ietfa.amsl.com>
Date: Mon, 4 Feb 2013 22:00:45 +0900
X-Google-Sender-Auth: GPNO5wv2Q_WeB5KBPKFcpOp_eTI
Message-ID: <CAC4RtVBgPS0aOPsM5h1WcqfBnuV+-B=g1C-AeegdKP67u1-LwA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: draft-ietf-mpls-tp-security-framework.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: mpls@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 13:00:47 -0000

> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'MPLS-TP Security Framework'
>   <draft-ietf-mpls-tp-security-framework-07.txt> as Informational RFC

Some Last Call comments in advance of IESG Evaluation:

-- Abstract --
   This document is built on RFC5920 "MPLS and GMPLS MPLS and
   GMPLS security framework"

Bit of a stuttering typo there.

-- General --

There are lots of abbreviations throughout here that aren't expanded.
You do send us to documentation (the last paragraph of Section 1), so
I wonder how much we should expect every one to be expanded on first
use.  But I see OAM, GMPLS, PWE3, PE (with and without S- and T-),
GAL, G-ACh, BFD, DoS, LSP.

On the other hand, I'm not sure we want to clutter things up with a
lot of expansions that anyone who reads the document will already
know.  So I'll just leave this as a passing comment.

-- Sections 2.1 and 2.2 --

It's a small point, but the diagrams for security reference models
1(b), 2(a), 2(b), and 2(c) aren't labelled exactly as the text states.
 The bad ones are 2(a) and (b), where the diagrams have "SPE1" and the
text has "S-PE".  In the others, it's just a question of a "-" in the
text and none in the diagram.  As I say, it's a small point, but I'd
prefer it if the text and the diagrams matched exactly; removing the
dashes in the text seems easiest (and fixing the "1" in the text for
the two "S-PE" cases).

-- Section 3 --

   This section discuss various network security threats which are to
   MPLS-TP and may endanger MPLS-TP networks.

Is this missing the word "new" somewhere?  (And make it "discusses",
while you're fixing that.  We'll let the RFC Editor do the
"which"->"that" change; they need something to do.)

   A successful attack on a particular MPLS-TP network or on a SP's
   MPLS-TP infrastructure may cause one or more adverse effects.

Yes, that would sort of be the definition of a successful attack, I
should think.  (You might consider deleting this paragraph.)

      - GAL or BFD label manipulation, which includes insertion of false
      labels, messages modification, deletion, or replay.

To make the list clearer, I suggest this:

NEW
      - GAL or BFD label manipulation, which includes insertion of false
      labels and modification, deletion, or replay of messages.
END

      - DoS attack through in-band OAM G-ACh/GAL and BFD messages.

You mean *excessive*, unproductive messages, of course.  Is there a
good way to say this that can help someone detect when these messages
become a DoS attack, or otherwise give some more information?  (Maybe
there isn't...)

   When a NMS is used for LSP setup, the attacks to NMS can cause the
   above effect as well. Although this is not unique to MPLS-TP, but
   MPLS-TP network can be particularly venerable as static provisioning
   through NMS is a commonly used model.

"Vulnerable", not venerable.  But I don't understand why the fact that
static provisioning through NMS causes any greater vulnerability than
otherwise.  Can you expand on that a bit?

   Observation (including traffic pattern analysis), modification, or
   deletion of a provider's or user's data, as well as replay or
   insertion of inauthentic data into a provider's or user's data
   stream.

This isn't a complete sentence, so I'm not sure what you're trying to
say.  Are you just saying that these are security threats?  Again,
that seems clear, and rather obvious.  Can you perhaps split these up,
and say a bit more about some of them?  The observation part seems
particularly interesting: I'd like to know what can be observed that
causes security issues.  And you've given one example, but haven't
said much about it.  What is it that traffic pattern analysis can
reveal in MPLS-TP that is sensitive?  What other things can be
observed that might be sensitive?

(The other points don't need expansion, I guess, and you cover defense
in the next section.  But see below for a comment about that.)

   The threats may be resulting from malicious behavior or accidental
   errors. For example: Users of the MPLS-TP network may attack the
   network or other users; employees of the MPLS-TP operators,
   especially people who operate the NMS, attackers who obtain physical
   access to a MPLS-TP SP's site; Other SPs in the case of MPLS-TP
   inter-provider connection.

I find this paragraph hard to follow: I don't know what to do with the
semicolon-separated list.  I think you're giving me a list of examples
of how malicious behaviour or accidental errors.  And what I see is
this:

1. Users of the MPLS-TP network may attack the network or other users.

--- Yep... got that.

2. Employees of the MPLS-TP operators, especially people who operate
the NMS, attackers who obtain physical access to a MPLS-TP SP's site.

--- I can't parse that, and don't know what you're trying to say.

3. Other SPs in the case of MPLS-TP inter-provider connection.

--- That's just a subject with no verb, and, again, I'm not sure what
you want to say.

-- Section 4 --

   The techniques discussed here include [...long list...]

I expected to see those techniques discussed here.  Then I saw, "Where
these techniques apply to MPLS and GMPLS in general, they are
described in Section 5.2 of [RFC5920]." That's fine, but then please
don't say "The techniques discussed here".  Maybe "Techniques to
defend against the security threats in Section 4 include
[...list...]."

   Thisis one way to protect the infrastructure used for support of
   MPLS-TP to separate the resources for support of MPLS-TP services
   from the resources used for other purposes. For example, in security
   model 2 (Section 2.2), the potential risk of attacks on the S-PE or
   T-PE in the trusted zone may be reduced by using non-IP-based
   communication paths.

The first sentence is confused and hard to understand.  Please re-write it.

In the second sentence (I'm not an MPLS guy, so please bear with me
and educate me if I'm completely off base here), is the point really
about non-IP-based communication paths, in particular?  Or is it more
generally that the communication paths in the trusted zone are not
accessible outside the zone?  If so, adding that would help ("...by
using non-IP-based communication paths, so that the paths in the
trusted zone...").

   Note that the
   connectivity verification are now developed for general MPLS networks
   as well.

Is there a word missing here?  Connectivity verification tools?
Techniques?  Something else?

In the last paragraph, items 3 and 4 are the same.  I think this list
would benefit from being shown as a regular numbered list, rather than
grouped together in a paragraph.

In general, in this section I expected to see what defensive
techniques could be used with the specific threats in Section 3.
Instead, I have to try to match them up, and maybe they're not very
matchable.  Given the brevity of Section 3, I think a better
arrangement of this document would have one section that had a list of
threats along with the defense against each threat.  Something like
this:

Threat: GAL or BFD label manipulation, which includes insertion of
        false labels and modification, deletion, or replay of messages.
Defense: [Whatever]

Threat: DoS attack through in-band OAM G-ACh/GAL and BFD messages.
Defense: [Whatever else]

Perhaps you thought this would be a longer document, so you arranged
it this way, but with most things applying to MPLS in general, and not
being specific to MPLS-TP, you have the opportunity to arrange it more
directly.  Is it possible to do that?

Barry

From barryleiba.mailing.lists@gmail.com  Mon Feb  4 06:04:48 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE36B21F857B; Mon,  4 Feb 2013 06:04:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.895
X-Spam-Level: 
X-Spam-Status: No, score=-102.895 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIDU7U-S7cRT; Mon,  4 Feb 2013 06:04:47 -0800 (PST)
Received: from mail-vb0-f47.google.com (mail-vb0-f47.google.com [209.85.212.47]) by ietfa.amsl.com (Postfix) with ESMTP id C126B21F8585; Mon,  4 Feb 2013 06:04:46 -0800 (PST)
Received: by mail-vb0-f47.google.com with SMTP id e21so3884034vbm.34 for <multiple recipients>; Mon, 04 Feb 2013 06:04:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HkXgMs9XoXVVq5TJC5HDyTtFzD6rsmuD49Dnlh8n/qM=; b=jitVkVOmH83cvhxdmsEu/bMRJi0Lm7/LpxFao0d8JMu3eE4DXjb3DHsDPxcP7glbWm q2xDK6Dddk79IL5nXGJxvtunDymoK4npY1sSqCJ0+LooVxo7LDitjbJO/NK67dNFQQgf Hskq+w+RaLpwbTbTBFmQAK98qZEQ6ytYSV7DPP2eNirbuznB41v4ihPOM4/GHZUqc9Mu occ8wJo78FKb5bODPdauQ03Yo2y47V7qKRc+uHBpISkRf2w1QpTdobKGfIuXTj0ZArSh 06SFoUrkvanTgt/be3exMXB5S+fU8LLRb8gILxU/lvQmwvovo46a4F9FjnMU8GuNan+p XYyg==
MIME-Version: 1.0
X-Received: by 10.58.117.229 with SMTP id kh5mr18575171veb.27.1359986686053; Mon, 04 Feb 2013 06:04:46 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 4 Feb 2013 06:04:45 -0800 (PST)
In-Reply-To: <20130201132421.6136.92013.idtracker@ietfa.amsl.com>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com>
Date: Mon, 4 Feb 2013 23:04:45 +0900
X-Google-Sender-Auth: UPzow3U0m3vFRf43cyHebtfOS_I
Message-ID: <CAC4RtVAMUceP5Zry_faM_jjsy05BvHZwonfsvcrM5SyW=HC+CA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: draft-ietf-paws-problem-stmt-usecases-rqmts.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: paws@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 14:04:48 -0000

> The IESG has received a request from the Protocol to Access WS database
> WG (paws) to consider the following document:
> - 'Protocol to Access White Space (PAWS) Database: Use Cases and
>    Requirements'
>   <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> as Informational
> RFC

Some Last Call comments, in advance of IESG Evaluation:

-- General --

It's completely a non-starter that there's no email address for
Anthony Mancuso; this has to be added.  He won't get any of the IESG
Evaluation messages this way, and the RFC Editor won't be able to
contact him during the publication process.

Abstracts should not contain citations, so the "[1]" citation should
be removed.  But perhaps more to the point, the Abstract is too long;
the first paragraph can be trimmed after the second sentence (clipping
everything beginning with "An obvious requirement", which doesn't need
to be in the abstract (but should be and is in the Introduction)).

The first and third references need to be in RFC reference form, and
not simply as URIs.  They should look something like this:

[1] V. Chen, S. Das, Z. Lei, J. Malyar, P. McCann, "Protocol to
Access Spectrum Database", draft-ietf-paws-protocol-01 (work in
progress), December 2012

[3] National Imagery and Mapping Agency, "Department of Defense
World Geodetic System 1984, Its Definition and Relationships with
Local Geodetic Systems", NIMA TR8350.2 Third Edition Amendment 1,
January 2000,
<http://earth-info.nga.mil/GandG/publications/tr8350.2/tr8350_2.html>

For the second reference: the RFC Editor will not generally accept
Wikipedia as a reference, because its contents are unstable.  Perhaps
you could use something like <http://fcc.gov/oet/cognitiveradio/>
instead?

Just an alert: the RFC Editor will probably add hyphens when "white
space" is used as an adjective, as in "white-space spectrum".  This is
particularly notable when you have "non-white space spectrum", which
looks like space that is non-white (as opposed to "non-white-space
spectrum").  You may feel free to wait for them to do that.  Or you
can do it.

-- Section 1.1 --

The first paragraph seems overlong, and could do with splitting.
Perhaps start a new paragraph with "An obvious requirement", and then
another with "Academia and industry".

-- Section 3.1 --

It looks like a lot of stuff in these earlier sections used to have
2119 language, and got Peted.  You missed one: the "MUST" in the
second sentence should be "must".

-- Section 3.2 --

Does Figure 1 actually show anything useful or interesting?  It says
it illustrates a registration requirement, but I don't see it.

I'd say that "most current and up-to-date information" is redundant
(this also shows up in 6.3).  And anyway, step 1 isn't a step -- you
don't *do* anything there.

-- Section 4.1 --

   Figure 2 (Figure 2) depicts the general architecture such a simple
   master-slave network

You're missing an "of".  And is there a reason for "Figure 2 (Figure
2)" (and with other figures) that I don't understand?

Bullet 3: There is no Section 4.1.1 to see.

Bullet 4: It's not really optional (which implies that it's at the
option of the master).  It's required if the database requires it, but
not all databases require it.  Can you re-word?  (And there is no
Section 4.1.2, either.)

Bullet 5: The part beginning "Note that" is out of place here, but
that's OK, because it's repeated where it belongs, in bullet 6.  I
suggest you just remove it from here.

-- Section 5 --

   The databases may be regulatory specific
   since the available spectrum and regulations may vary, but the
   fundamental operation of the protocol should be regulatory
   independent.

Is "should be" appropriate?  I should think "has to be".

   In Figure 11, note that there could be multiple databases serving
   white space devices.

There is no Figure 11.  You mean 7?

   The databases are locale specific since the
   regulations and available spectrum may vary.

I think you mean "location-specific"; in the App world "locale" has a
particular meaning that I don't think you mean (in other words, this
is not an issue of local language).  This applies to the use of
"locale" elsewhere in the document as well.

-- Section 5.1 --

Bullet 3 confuses me.  First it says that it's possible for the device
to know what rules are applicable, because it knows its location.
Then it says to note that even though it knows its location, it may
not be able to know what rule set to use.  Is that not contradictory,
or am I misunderstanding?  Then it gives an important requirement
that's buried at the end.

I suggest putting the requirement earlier, and then following it with
the extended explanation of the need for it.

-- Section 5.2 --

   The device needs to
   determine the location of the specific database to which it can send
   queries in addition to registering itself for operation and using the
   available spectrum.

I'm having a lot of trouble parsing this sentence, and I'm still not
sure I understand what it means.  Can you try rephrasing it?

-- Section 6.1 --

         The Data Model MUST support WGS84 (see NGA: DoD World Geodetic
         System 1984 [3]).

I think this statement makes that reference normative.

      D.3  The Data Model MUST support device description data that
         identifies a device (serial number, certification IDs, etc.)
         and describes device characteristics, such as or device class
         (fixed, mobile, portable, indoor, outdoor, etc.), Radio Access
         Technology (RAT), etc.

Is the "or" in there a stray, or is there something else wrong?

-- Section 6.2 --

   P.9  The protocol MUST support an available spectrum request from the
      master device to the database.  These parameters MAY include any
      of the parameters and attributes required to be supported in the
      Data Model Requirements.

"These parameters" implies that you've mentioned parameters before,
but you haven't.  What parameters?  (Same comment for P.10 and P.11.)

-- Section 6.3 --

   O.5  The master device MAY register with the database according to
      local regulatory policy.

As above: this is not a correct use of MAY, because it's not at the
option of the master device.  In fact, as you say later in this
requirement, it MUST register when it's required to.  Please re-word
this.

  (O.6)
      Parameters provided to the database
      MAY include device location, accuracy of the location

Again... are these parameters provided purely at the option of the
requestor (in which case "MAY" is fine), or are they provided because
they're required by the database (in which case "MAY" is not right)?

   O.8  According to local regulator policy, a master device MAY inform
      the database of the actual frequency usage

   O.10  According to local regulatory policy, the master device MAY
      query the database with parameters received from the slave device.

More of the same about the "MAY".

-- Section 8 --

         It is assumed that both the master device and the white space
         database have NOT been compromised from a security standpoint.

      Threat 1: User modifies a device to masquerade as another valid
      certified device

Here's how I read these two adjacent paragraphs: (1) It is assumed
that the device is not compromised; (2) Threat 1: A user compromises
the device.

Am I completely misunderstanding?  (I also find the explanation below
that to be convoluted.  Can you work on it, and try to un-convolute
it?)

         A master device MAY
         need to identify itself to the database and be authorized to
         obtain information about available spectrum.

Totally wrong "MAY"; make it "might".  Remember that "MAY" means that
something is entirely optional.  "MAY need to" is pretty much always
wrong.

Threat 4:
         The available spectrum
         information or transmit power allowed type of parameters
         carried in the response could be modified by the attacker
         resulting in the master device using spectrum that is not
         available at a location or transmitting at a greater power
         level than allowed resulting in interference to the primary
         user of that spectrum.

That's quite a sentence.  Please unravel it and re-word.

Threat 6: Expand "MiM".

   The security requirements arising from the above threats are captured
   in the requirements of Section 6.1 (Section 6.1).

There's that duplication again: "Section 6.1 (Section 6.1)"

-- Section 9 --

This section is entirely unnecessary, and you should remove it.
There's no need to repeat what you've already said.

Barry

From sm@resistor.net  Mon Feb  4 09:21:23 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B24021F8A99; Mon,  4 Feb 2013 09:21:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.458
X-Spam-Level: 
X-Spam-Status: No, score=-102.458 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zblPgety+kVe; Mon,  4 Feb 2013 09:21:22 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7362721F8A7E; Mon,  4 Feb 2013 09:21:22 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r14HLGPP020340; Mon, 4 Feb 2013 09:21:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1359998481; bh=RsIHZkGiFeM7WBl4ktLKdH1vtt5r9yaRLd6j4MPFttA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=aOkiI/rp/vVi3EbvaZQZAynywbD3ASfbBjQ9YgIx9T4fCmjqWW8s1d1s7y3M14SrS Mt66G6RllMuOEbw+2FWTJx4dQ4hhXoEvf3hQRkMDL8b5HOS5hBLMo5SFqX8UXDSyMq A8jpa4rkUo+XAuMF/o6a/SYGiZs0Xxvm6muip3mA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1359998481; i=@resistor.net; bh=RsIHZkGiFeM7WBl4ktLKdH1vtt5r9yaRLd6j4MPFttA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QNKaiUt0biSuw5m3kwemLnEbNbDk6Vnvz04jq/dPJlcxgSPNwKzXykTN6SGOtuYoq Z6KWGvVYDvQ7vHCNB38V2bOXXCxhG2TOKrh1wxv1tafFMoA0Bydc4Q70Pak15bnVvI q/DTWHSq3MZa04hnUb1Cirp7lTdmntSIOXswPGeI=
Message-Id: <6.2.5.6.2.20130204064015.09261fa0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 04 Feb 2013 09:18:18 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
In-Reply-To: <20130201132421.6136.92013.idtracker@ietfa.amsl.com>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: paws@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 17:21:23 -0000

At 05:24 01-02-2013, The IESG wrote:
>The IESG has received a request from the Protocol to Access WS database
>WG (paws) to consider the following document:
>- 'Protocol to Access White Space (PAWS) Database: Use Cases and
>    Requirements'
>   <draft-ietf-paws-problem-stmt-usecases-rqmts-12.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 2013-02-15. Exceptionally, comments may be

I read the draft.  I am okay with whatever the working group decides.

In Section 1.1:

   "Academia and Industry have studied multiple cognitive radio [2]
    mechanisms for use in such a scenario."

The reference seemed odd.  It took me some time to understand that it 
was put in to address a comment.  However, the first (external) 
reference that defines that is a 404.

There are two occurrences of the RFC 2119 boilerplate in the draft.

In Section 3.1:

   "Before the master device can transmit in white space spectrum, it MUST
    obtain the address of a trusted white space database, which it will
    query for available white space spectrum."

Why is this a MUST?

In Section 4.2:

   "A simplified operation scenario of offloading content, such as video
    stream, from the a metered Internet connection to the a WS connection
    consists of the following steps:"

What is a metered Internet connection?

In Section 4.4:

   "To set up a replacement network, spectrum needs to be quickly
    cleared and reallocated to the crisis response organization."

Is that what P.15 is about?  BTW, O.17 uses a "should" for this.

In Section 6.2:

   "P.3  The protocol MUST provide the ability for the database to
      authenticate the master device."

   "P.5  The messages sent by the master device to the database and the
       messages sent by the database to the master device MUST support
       integrity protection."

   "P.6  The protocol MUST provide the capability for messages sent by
       the master device and database to be encrypted."

This sounds like the usual IETF security stuff.

   "P.8  The protocol MUST support a registration acknowledgement
       indicating the success of failure of the master device
       registration."

The "success of failure" might need fixing.

   "P.14  The protocol MUST support a validation response from the
       database to the master to indicate if the slave device is
       validated by the WSDB.  The validation response MUST indicate the
       success or failure of the validation request."

What is WSDB?

In Section 6.3:

   "O.1  The database and the master device MUST be connected to the
       Internet."

What is the Internet?

   "O.2  A master device MUST be able to determine its location including
       uncertainty and confidence level."

Does the working group plan to build its deliverables upon the GEOPRIV work?

I found the draft easy to read.  The draft goes into extraneous 
details in some parts.  As an off-topic comment I see that the 
working group had the usual JSON versus XML discussion [1]. :-)  I 
understood the concept of white spaces as discussed in the draft.  If 
I understood correctly the usage of database is related to the data 
model in Section 6.  On seeing Figure 7 it seemed to me that what was 
missing is an architecture document which provides a high-level view 
of how all this is supposed to work.  I am not suggesting a 
reorganization of the draft as it may end up as too much work.  The 
draft attempts to convince the reader about the importance of white 
spaces and its use cases.  It's basically about database queries.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/apps-discuss/current/msg07261.html  


From hsantos@isdg.net  Mon Feb  4 10:28:26 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D14621F8A64 for <ietf@ietfa.amsl.com>; Mon,  4 Feb 2013 10:28:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.638
X-Spam-Level: 
X-Spam-Status: No, score=-101.638 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71EqoI5yYF1C for <ietf@ietfa.amsl.com>; Mon,  4 Feb 2013 10:28:25 -0800 (PST)
Received: from catinthebox.net (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 72F7121F8A5F for <ietf@ietf.org>; Mon,  4 Feb 2013 10:28:25 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1410; t=1360002494; h=Received:Received: Message-ID:From:To:Subject:Date:Organization:List-ID; bh=Ml1b0Kn d6bqcD9Mccr+PefyvBGg=; b=Vd++YYbY2tVa+b5babAAft7UqHk0b21ujzBIqrH nPSVdnnnwTRK27I9E9LWUAsEx9mk2z1DqnS5a5DaQZLSIh4YkR3R/VagSFJGk0Dv nRm0goNCooQrQLm6ukF6DbbpHaGcOWX59yyUIlOTwEQnSVRAjAH6Q+R5riM5bIxK JW0A=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 04 Feb 2013 13:28:14 -0500
Received: from main2 ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3139227259.23948.3392; Mon, 04 Feb 2013 13:28:13 -0500
Message-ID: <8B30D6E8A9B04576A4D7AF64EFE06BA6@addom.santronics.com>
From: "Hector Santos" <hsantos@isdg.net>
To: <dcrocker@bbiw.net>, "Sam Hartman" <hartmans-ietf@mit.edu>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com><824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com><CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com><377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu><tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net>
Subject: Re: History of protocol discussion or process in WG
Date: Mon, 4 Feb 2013 13:26:47 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.4657
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4721
Cc: Lixia Zhang <lixia@cs.ucla.edu>, ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 18:28:26 -0000

----- Original Message -----=20
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
Cc: "Abdussalam Baryun" <abdussalambaryun@gmail.com>; "ietf" =
<ietf@ietf.org>; "Lixia Zhang" <lixia@cs.ucla.edu>
Sent: Sunday, February 03, 2013 1:38 PM
Subject: Re: History of protocol discussion or process in WG


> What I think /is/ possible, however, is to establish a "history of"=20
> wiki, to which participants can contribute their views.
>=20
> Moderate it, to limit the noise.  Solicit and vet contributions from=20
> principals, to seed the data with credible material.

IMO, thats the problem. This "Judging" (and editing) is subjective and =
increasingly conflictive, and quite often by the same suite of people =
who don't have the same views as others, especially when there is =
legitimate technical and engineering conflicts.  The last thing the IETF =
should seek is filtering of engineering views.  It can defeat the =
purpose of learning from the difficult conflicts so that hopefully, the =
IETF can better evolve.

I suggest a "standard" (and easy to complete) WG survey for anyone to =
complete. I'm sure there are a set of survey questions that can be =
deemed very useful and can be used to extract "value" information about =
a WG process just completed.   As a side note, this may have to be =
offered with anonymous input as well.

--
HLS


From weiler@watson.org  Mon Feb  4 11:08:20 2013
Return-Path: <weiler@watson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B364F21F86E3; Mon,  4 Feb 2013 11:08:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nTGH+Hv+6IiZ; Mon,  4 Feb 2013 11:08:20 -0800 (PST)
Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC1421F86D6; Mon,  4 Feb 2013 11:08:19 -0800 (PST)
Received: from fledge.watson.org (localhost.watson.org [127.0.0.1]) by fledge.watson.org (8.14.5/8.14.5) with ESMTP id r14J8JaK079199; Mon, 4 Feb 2013 14:08:19 -0500 (EST) (envelope-from weiler@watson.org)
Received: from localhost (weiler@localhost) by fledge.watson.org (8.14.5/8.14.5/Submit) with ESMTP id r14J8ICg079194; Mon, 4 Feb 2013 14:08:18 -0500 (EST) (envelope-from weiler@watson.org)
X-Authentication-Warning: fledge.watson.org: weiler owned process doing -bs
Date: Mon, 4 Feb 2013 14:08:18 -0500 (EST)
From: Samuel Weiler <weiler@watson.org>
To: secdir@ietf.org, iesg@ietf.org, ietf@ietf.org, draft-ietf-mmusic-sdp-cs-17.all@tools.ietf.org
Subject: secdir review of draft-ietf-mmusic-sdp-cs-17
Message-ID: <alpine.BSF.2.00.1302011241020.47827@fledge.watson.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.3 (fledge.watson.org [127.0.0.1]); Mon, 04 Feb 2013 14:08:19 -0500 (EST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 19:08:20 -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 allows SIP endpoints to negotiate the use of a 
circuit-switched (e.g. PSTN) channel.  It presents a mechanism for 
correlating an incoming circuit-switched connection with a given 
SDP/SIP session by sending a nonce or a static string.

Summary: I would like to see a stronger authentication mechanism
defined to replace the static string or "plaintext password" nonce.

I am content with the analysis of security weaknesses: an attacker
could trick someone into initiating a potentially expensive PSTN call,
and the correlation mechanism is weak.

I am not content with the use of a mere nonce or static string for 
correlation.  That is the equivalent of sending plaintext passwords, 
and I suspect we have better mechanisms available that could allow for 
mutual endpoint authentication, making it statistically unlikely for a 
man-in-the-middle to participate successfully in the correlation 
exchange.  The document makes a case for using short strings/nonces 
(e.g. a caller-ID string or 10 DTFM digits).  I suspect both that 
those lengths could be extended without great pain and that some 
stronger authentication mechanisms could work with such short strings, 
especially given the ability to send longer keying material in the 
packet-switched SDP session.

Non-security observation: I'm worried that the architecture of the 
current correlation mechanism will have some unintended consequences. 
>From section 5.2.3:

    The endpoints should be able to correlate the circuit-switched bearer
    with the session negotiated with SDP in order to avoid ringing for an
    incoming circuit-switched bearer that is related to the session
    controlled with SDP (and SIP).

As I understand it, some of the defined variants of the correlation
scheme require answering the call (e.g. the DTMF scheme) before
knowing whether or not the channel corresponds to a SIP session.  If
it does not, then what?  The call is already answered, which gives a
surprising user experience.  Feel free to tell me I'm off base with
this one.

-- Sam


From barryleiba.mailing.lists@gmail.com  Mon Feb  4 14:18:02 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C457621F8B2E; Mon,  4 Feb 2013 14:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.892
X-Spam-Level: 
X-Spam-Status: No, score=-102.892 tagged_above=-999 required=5 tests=[AWL=-0.142, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnvVl61agJ1b; Mon,  4 Feb 2013 14:18:02 -0800 (PST)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by ietfa.amsl.com (Postfix) with ESMTP id B803721F8B1A; Mon,  4 Feb 2013 14:18:01 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id cz10so1995152veb.7 for <multiple recipients>; Mon, 04 Feb 2013 14:18:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=mwk6Dtt0fP0JgbsiWlZ/0+h9i6f9diGOtbPlyfWCmyU=; b=J9dvIzWpnE23CSIiANjp6ddNpLOByqI32TQxhqF3u4Z/IEH3KDAwn09yIvEgmQh6Ki DbbMafHW+JT7SPkVJN4Q1okpY47PvGK0UxS0Mh7Y8CaNph0hldUSF3OKqO9dLfxrcs3H oih+cJFG92fZ9mOOtzZ2Nym0u9ImVwMX5SidamNB1OlXPPJgSSUQBnjxhKK/OiNWf6Fy kKLPKabVkRftzWJ6dGd/2NObSfyPR942vTzdG3f67lHADGGglGXu9bucDzhamH0rgfD3 GoglfbL6+7Moo4LdlpWEXgzE0i6Q0A/b2QmErGKXtXJSSRmGggAy5jZQJ3LXmIOizC1P Aq3A==
MIME-Version: 1.0
X-Received: by 10.52.91.142 with SMTP id ce14mr21563805vdb.84.1360016281063; Mon, 04 Feb 2013 14:18:01 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 4 Feb 2013 14:18:00 -0800 (PST)
In-Reply-To: <CAC4RtVAMUceP5Zry_faM_jjsy05BvHZwonfsvcrM5SyW=HC+CA@mail.gmail.com>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com> <CAC4RtVAMUceP5Zry_faM_jjsy05BvHZwonfsvcrM5SyW=HC+CA@mail.gmail.com>
Date: Tue, 5 Feb 2013 07:18:00 +0900
X-Google-Sender-Auth: 9c9M6aWeyIVFz7eI_Ek9PhK09Sc
Message-ID: <CAC4RtVCx8wjrtE5n6s5+cnS9c9b+UEb2f82aXB5LMqKLMXDeLg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: draft-ietf-paws-problem-stmt-usecases-rqmts.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: paws@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Feb 2013 22:18:02 -0000

>> The IESG has received a request from the Protocol to Access WS database
>> WG (paws) to consider the following document:
>> - 'Protocol to Access White Space (PAWS) Database: Use Cases and
>>    Requirements'
>>   <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> as Informational
>> RFC
>
> Some Last Call comments, in advance of IESG Evaluation:

Sorry: one that I forgot to include.

-- Section 5.1 --

Bullet 1 says "Radio/air interface agnostic", but seems to be talking
about the messaging between the master and the DB, which will not
necessarily be over an air interface.  Please re-word this bullet,
being careful to make the distinction between white-space usage (which
will of course be over the air) and DB access (which could be over any
network interface).

Barry

From daedulus@btconnect.com  Tue Feb  5 01:50:05 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF6A521F879D for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 01:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.17
X-Spam-Level: 
X-Spam-Status: No, score=-4.17 tagged_above=-999 required=5 tests=[AWL=-0.571,  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 ZP8VULV4NhmY for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 01:50:03 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 7A10C21F8804 for <ietf@ietf.org>; Tue,  5 Feb 2013 01:50:03 -0800 (PST)
Received: from mail50-am1-R.bigfish.com (10.3.201.231) by AM1EHSOBE016.bigfish.com (10.3.207.138) with Microsoft SMTP Server id 14.1.225.23; Tue, 5 Feb 2013 09:50:01 +0000
Received: from mail50-am1 (localhost [127.0.0.1])	by mail50-am1-R.bigfish.com (Postfix) with ESMTP id 2E4D7220298; Tue,  5 Feb 2013 09:50:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.254.181; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0711HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zzbb2dI98dI9371I542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail50-am1 (localhost.localdomain [127.0.0.1]) by mail50-am1 (MessageSwitch) id 1360057799688752_27703; Tue,  5 Feb 2013 09:49:59 +0000 (UTC)
Received: from AM1EHSMHS011.bigfish.com (unknown [10.3.201.252])	by mail50-am1.bigfish.com (Postfix) with ESMTP id A587E3A004A; Tue,  5 Feb 2013 09:49:59 +0000 (UTC)
Received: from DBXPRD0711HT001.eurprd07.prod.outlook.com (157.56.254.181) by AM1EHSMHS011.bigfish.com (10.3.207.111) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 5 Feb 2013 09:49:59 +0000
Received: from DBXPRD0611HT002.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.255.178.34) with Microsoft SMTP Server (TLS) id 14.16.263.1; Tue, 5 Feb 2013 09:49:56 +0000
Message-ID: <005701ce0385$bd7de040$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <dcrocker@bbiw.net>, Sam Hartman <hartmans-ietf@mit.edu>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com><824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com><CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com><377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu><tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net>
Subject: Re: History of protocol discussion or process in WG
Date: Tue, 5 Feb 2013 09:46:44 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.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, 05 Feb 2013 09:50:05 -0000

----- Original Message -----
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Sam Hartman" <hartmans-ietf@mit.edu>
Cc: "Abdussalam Baryun" <abdussalambaryun@gmail.com>; "ietf"
<ietf@ietf.org>; "Lixia Zhang" <lixia@cs.ucla.edu>
Sent: Sunday, February 03, 2013 6:38 PM
>
> On 2/3/2013 10:28 AM, Sam Hartman wrote:
> > I'm not sure I've ever been involved with a WG where you could have
> > gotten consensus on any of the above enough to publish it.  Nor can
I
> > think of many WGs that have the excess energy to do this work.  Even
> > getting consensus on a summary of where you ended up is quite
> > tricky.
>
>
> Getting consensus on the details of a history is much more difficult
> than on a technical spec...
>
> So don't try.

There is an I-D in IDR which recorded a substantial part of the history
but it was the AD, and the WG, that was not happy with it so it is
currently in - well, I don't know what state (now if we had a summary of
the status of I-Ds adopted by a WG published each month, as was recently
suggested on this list, well, then, I would have the status off pat:-)

Tom Petch

>





> What I think /is/ possible, however, is to establish a "history of"
> wiki, to which participants can contribute their views.
>
> Moderate it, to limit the noise.  Solicit and vet contributions from
> principals, to seed the data with credible material.
>
> Then let historians worry about synthesizing this source data into
> something more coherent (and biased, and ...)
>
> But at least the raw narrative of motivated principals will have been
> captured.
>
> In terms of administrative overhead, there isn't much, other than
> creating a separate page for each activity.
>
>
> d/
>



From daedulus@btconnect.com  Tue Feb  5 02:27:08 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C797D21F886A for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 02:27:08 -0800 (PST)
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 dHWfpI9yFELj for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 02:27:08 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 035ED21F8862 for <ietf@ietf.org>; Tue,  5 Feb 2013 02:27:07 -0800 (PST)
Received: from mail51-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE007.bigfish.com (10.7.40.11) with Microsoft SMTP Server id 14.1.225.23; Tue, 5 Feb 2013 10:27:07 +0000
Received: from mail51-va3 (localhost [127.0.0.1])	by mail51-va3-R.bigfish.com (Postfix) with ESMTP id 1A3BFA0320; Tue,  5 Feb 2013 10:27:07 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.69; KIP:(null); UIP:(null); IPV:NLI; H:AMXPRD0711HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: PS-21(zzbb2dI98dI9371I542I1432Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz8275ch1033IL8275bh8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail51-va3 (localhost.localdomain [127.0.0.1]) by mail51-va3 (MessageSwitch) id 1360060024511712_10297; Tue,  5 Feb 2013 10:27:04 +0000 (UTC)
Received: from VA3EHSMHS001.bigfish.com (unknown [10.7.14.244])	by mail51-va3.bigfish.com (Postfix) with ESMTP id 7866214005B; Tue,  5 Feb 2013 10:27:04 +0000 (UTC)
Received: from AMXPRD0711HT003.eurprd07.prod.outlook.com (157.56.250.69) by VA3EHSMHS001.bigfish.com (10.7.99.11) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 5 Feb 2013 10:27:04 +0000
Received: from DBXPRD0611HT002.eurprd06.prod.outlook.com (157.56.254.85) by pod51017.outlook.com (10.242.9.164) with Microsoft SMTP Server (TLS) id 14.16.263.1; Tue, 5 Feb 2013 10:27:00 +0000
Message-ID: <024f01ce038a$eb842800$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: t.p. <daedulus@btconnect.com>, <dcrocker@bbiw.net>, Sam Hartman <hartmans-ietf@mit.edu>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com><824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com><CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com><377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu><tslip69jlqg.fsf@mit.edu><510EAEB7.9060703@dcrocker.net> <005701ce0385$bd7de040$4001a8c0@gateway.2wire.net>
Subject: Re: History of protocol discussion or process in WG
Date: Tue, 5 Feb 2013 10:23:55 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.85]
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.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, 05 Feb 2013 10:27:08 -0000

Whoops, I lost a 'not'
Tom Petch

> ----- Original Message -----
> From: "Dave Crocker" <dhc@dcrocker.net>
> To: "Sam Hartman" <hartmans-ietf@mit.edu>
> Cc: "Abdussalam Baryun" <abdussalambaryun@gmail.com>; "ietf"
> <ietf@ietf.org>; "Lixia Zhang" <lixia@cs.ucla.edu>
> Sent: Sunday, February 03, 2013 6:38 PM
> >
> > On 2/3/2013 10:28 AM, Sam Hartman wrote:
> > > I'm not sure I've ever been involved with a WG where you could
have
> > > gotten consensus on any of the above enough to publish it.  Nor
can
> I
> > > think of many WGs that have the excess energy to do this work.
Even
> > > getting consensus on a summary of where you ended up is quite
> > > tricky.
> >
> >
> > Getting consensus on the details of a history is much more difficult
> > than on a technical spec...
> >
> > So don't try.

 There is an I-D in IDR which recorded a substantial part of the history
but it was the AD, and NOT the WG, that was not happy with it so it is
currently in - well, I don't know what state (now if we had a summary of
the status of I-Ds adopted by a WG published each month, as was recently
suggested on this list, well, then, I would have the status off pat:-)

Tom Petch
>
> > What I think /is/ possible, however, is to establish a "history of"
> > wiki, to which participants can contribute their views.
> >
> > Moderate it, to limit the noise.  Solicit and vet contributions from
> > principals, to seed the data with credible material.
> >
> > Then let historians worry about synthesizing this source data into
> > something more coherent (and biased, and ...)
> >
> > But at least the raw narrative of motivated principals will have
been
> > captured.
> >
> > In terms of administrative overhead, there isn't much, other than
> > creating a separate page for each activity.
> >
> >
> > d/
> >
>
>
>



From lear@cisco.com  Tue Feb  5 03:38:31 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4CA21F882F for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 03:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.572
X-Spam-Level: 
X-Spam-Status: No, score=-110.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 OZAninnf-V+X for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 03:38:31 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 0714921F880B for <ietf@ietf.org>; Tue,  5 Feb 2013 03:38:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1109; q=dns/txt; s=iport; t=1360064311; x=1361273911; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=FGjmT9e8IqhHTf9vDny+Wl7weydtcOTd5HR+jQoeygU=; b=X4D6Z2Ee/Tw5/5cWKKhRS8DlTAiMvvIuP9yy941/BvNWwLLbUlvmwiEL hoNthBS/Up4W9N7BkUMxkslfOQvR+VuuHH8QiklFrJ6aNo+ebIXMPD/j4 vQ40hSRXfFai/pMlnT+t+eoANRC1z9tMOuqA44VszMggbyVGJhi1Fho9R g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFACPuEFGQ/khM/2dsb2JhbABFhki1OINeFnOCHwEBAQQjVQEQCxgCAgUWCwICCQMCAQIBRRMBBwEBiA2oP4JAkCeBI40OghaBEwOWIZBRgn0
X-IronPort-AV: E=Sophos;i="4.84,602,1355097600"; d="scan'208";a="11596312"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 05 Feb 2013 11:38:29 +0000
Received: from dhcp-10-61-107-168.cisco.com (dhcp-10-61-107-168.cisco.com [10.61.107.168]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r15BcTwT024364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2013 11:38:29 GMT
Message-ID: <5110EF35.4090807@cisco.com>
Date: Tue, 05 Feb 2013 12:38:29 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: History of protocol discussion or process in WG
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net>
In-Reply-To: <510EAEB7.9060703@dcrocker.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Lixia Zhang <lixia@cs.ucla.edu>, Sam Hartman <hartmans-ietf@mit.edu>, ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 11:38:31 -0000

On 2/3/13 7:38 PM, Dave Crocker wrote:
>
>
> On 2/3/2013 10:28 AM, Sam Hartman wrote:
>> I'm not sure I've ever been involved with a WG where you could have
>> gotten consensus on any of the above enough to publish it.  Nor can I
>> think of many WGs that have the excess energy to do this work.  Even
>> getting consensus on a summary of where you ended up is quite
>> tricky.
>
>
> Getting consensus on the details of a history is much more difficult
> than on a technical spec...
>
> So don't try.

+1.  In fact in the ITU context they will sometimes spend half a day on
a meeting report.  I really don't think we want to go there.


What I would like not to have happen is that we spend any time bickering
over who said what, especially if it detracts from the business of
developing excellent standards.  I think your point, Dave, about
synthesis being left to historians is a good one, and I might go
farther, and say that the whole endeavor should be.  But having at least
a record from individauls about what *they* said or meant is, I suppose,
not unreasonable.

Eliot

From abdussalambaryun@gmail.com  Tue Feb  5 04:58:05 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CDA21F868D for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 04:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.499,  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 V7BRI+++LHqP for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 04:58:04 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 6673221F8619 for <ietf@ietf.org>; Tue,  5 Feb 2013 04:58:03 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id o1so141615wic.5 for <ietf@ietf.org>; Tue, 05 Feb 2013 04:58:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=AHOQPCykvH1LfyAp3WUx9PGr3PnJMvBSecaat2oTsN0=; b=eE1g6ALZ1DM/e2HNboi6p/k8FNUd4xJ6kdf9utdxlcQYzxHDhaQm6+65aL577SoAAS PFJevj5bckPXF0F+3ph4H/TUZv/ZbFf+QxvfHVyJuahDkKtaOgn6XW7zUxcfc2o9x1JP 6pPvtuxnKO+8gKI8qID1ObXE8n0iGn5sNUZaGfBGHqgeXpPVkuAKstpC7cz9ns6noDfT WW+iA//6Z3U4KaAKR+wI7o1X88+4/Gck/AkBFDN7hBCKiXqhgxvGjXDOMTGE/kVnYTje hfPQpfWpQ8N4KFhJrVmD5vYXuyHD1zsB54BFT3qSjJ5pEZJVVvFwz768TBkgo8q2wqKL MEFQ==
MIME-Version: 1.0
X-Received: by 10.180.87.98 with SMTP id w2mr16944817wiz.30.1360069082505; Tue, 05 Feb 2013 04:58:02 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Tue, 5 Feb 2013 04:58:02 -0800 (PST)
In-Reply-To: <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com>
Date: Tue, 5 Feb 2013 12:58:02 +0000
Message-ID: <CADnDZ88KXY0ozsgVOAOKAN=smaq2Ssjq2ikWGGExb_z4nPykCw@mail.gmail.com>
Subject: Re: History of protocol discussion or process in WG
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d0418261688613904d4f9c20d
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 12:58:05 -0000

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

The best engineering practice while making new technologies/procedures is
that they look/read into all world current, past, and
future related-knowledge  [1] [2], all information phases are important for
producing reasonable; I-Ds, RFCs, standards, BCP, etc.

In IETF meetings and discussions there is not way we can ignore the past
discussions [3][4]. The IETF is documenting/recording meetings (not
reporting attendance size [5]), I-D versions related to RFCs, discussions
on the IETF lists, but I think that each WG in IETF after a period of time
(about 20 years) can work out an I-D of issues related to RFCs that will be
read by IETF next generation engineers (hopefully written by WG RFCs
editors before we loose them).

>From my experience in reading IETF WGs lists, some authors and WG
discussions don't go into reasons of update version of I-Ds, but the reason
is only known if a participant asked for it. Some I-Ds authors discuss the
change outside the IETF, that is why I suiggested [6].

Please note that many I-Ds and RFC are not perfect described, understood or
interpreted [7], because while discussing an I-D in meetings or on
lists the interpretation changes by IETF participants (not all readers of
that I-D). Therefore, I think there is a need for more historic RFCs in
IETF as suggested before [8], but in both procedural and technical
IETF works/efforts. I am happy to find [9] in IETF documenting processes
(need to be updated) and hoping to see more past engineering helpful
experience in I-Ds.

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

[2] http://www.ietf.org/mail-archive/web/manet/current/msg14896.html

[3] http://www.ietf.org/mail-archive/web/ietf/current/msg76941.html

[4] http://www.ietf.org/mail-archive/web/ietf/current/msg76942.html

[5] http://www.ietf.org/mail-archive/web/ietf/current/msg74755.html

[6] http://www.ietf.org/mail-archive/web/ietf/current/msg74750.html

[7] http://www.ietf.org/mail-archive/web/ietf/current/msg76940.html

[8] http://www.ietf.org/mail-archive/web/ietf/current/msg76040.html

[9] http://trac.tools.ietf.org/misc/outcomes/

My opinion to make the IETF life easier and linked :)

AB

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

<div>The best engineering practice while making=A0new technologies/procedur=
es is that=A0they look/read into all world current,=A0past, and future=A0re=
lated-knowledge=A0<font size=3D"3" face=3D"Times New Roman">

[1] [2],</font><font size=3D"3" face=3D"Times New Roman"> all</font> inform=
ation phases are important for producing reasonable;=A0I-Ds, RFCs, standard=
s, BCP, etc.</div><div>=A0</div><div>In IETF meetings and discussions there=
 is not way we can ignore the past discussions=A0[3][4]. The IETF is docume=
nting/recording meetings (not reporting attendance size [5]), I-D versions =
related to RFCs, discussions on the IETF lists, but I think that each WG in=
 IETF after a period of time (about 20 years) can work out an I-D of issues=
 related to RFCs=A0that will be read by IETF next generation engineers (hop=
efully written by WG RFCs editors before we loose them).</div>
<div>=A0</div><div>From my experience in reading IETF WGs lists, some autho=
rs and WG discussions don&#39;t go into reasons of update version of I-Ds, =
but the reason is only known if a participant asked for it. Some I-Ds autho=
rs discuss the change outside the IETF, that is why I suiggested [6].</div>
<div>=A0</div><div>Please note that many I-Ds and RFC are not perfect descr=
ibed, understood or interpreted=A0[7], because while discussing an I-D=A0in=
 meetings or on lists=A0the interpretation changes by IETF participants (no=
t all readers of that I-D).=A0Therefore, I think there is a need for more h=
istoric RFCs in IETF as suggested before [8], but=A0in both procedural and =
technical IETF=A0works/efforts.=A0I am happy to find [9] in IETF documentin=
g processes (need to be updated) and hoping to see more past engineering he=
lpful experience in I-Ds.</div>
<div>=A0</div><div>[1] <a href=3D"http://www.ietf.org/mail-archive/web/ietf=
/current/msg76967.html"><font face=3D"Calibri">http://www.ietf.org/mail-arc=
hive/web/ietf/current/msg76967.html</font></a></div><div><div>=A0</div><div=
>[2] <a href=3D"http://www.ietf.org/mail-archive/web/manet/current/msg14896=
.html">http://www.ietf.org/mail-archive/web/manet/current/msg14896.html</a>=
</div>
<div><div>=A0</div><div>[3] <a href=3D"http://www.ietf.org/mail-archive/web=
/ietf/current/msg76941.html">http://www.ietf.org/mail-archive/web/ietf/curr=
ent/msg76941.html</a></div></div></div><div>=A0</div><div>[4] <a href=3D"ht=
tp://www.ietf.org/mail-archive/web/ietf/current/msg76942.html">http://www.i=
etf.org/mail-archive/web/ietf/current/msg76942.html</a></div>
<div>=A0</div><div>[5] <a href=3D"http://www.ietf.org/mail-archive/web/ietf=
/current/msg74755.html">http://www.ietf.org/mail-archive/web/ietf/current/m=
sg74755.html</a></div><div>=A0</div><div>[6] <a href=3D"http://www.ietf.org=
/mail-archive/web/ietf/current/msg74750.html">http://www.ietf.org/mail-arch=
ive/web/ietf/current/msg74750.html</a></div>
<div><div>=A0</div><div>[7] <a href=3D"http://www.ietf.org/mail-archive/web=
/ietf/current/msg76940.html">http://www.ietf.org/mail-archive/web/ietf/curr=
ent/msg76940.html</a></div></div><div>=A0</div><div>[8] <a href=3D"http://w=
ww.ietf.org/mail-archive/web/ietf/current/msg76040.html">http://www.ietf.or=
g/mail-archive/web/ietf/current/msg76040.html</a></div>
<div>=A0</div><div>[9] <a href=3D"http://trac.tools.ietf.org/misc/outcomes/=
">http://trac.tools.ietf.org/misc/outcomes/</a></div><div>=A0</div><div>My =
opinion to make the IETF life easier and linked :)=A0</div><div>=A0</div><d=
iv>AB</div>

--f46d0418261688613904d4f9c20d--

From john-ietf@jck.com  Tue Feb  5 05:49:24 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A8521F879D for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 05:49:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.676
X-Spam-Level: 
X-Spam-Status: No, score=-102.676 tagged_above=-999 required=5 tests=[AWL=-0.077, 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 wrrJ7Cs3j+jG for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 05:49:23 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B4D6721F8778 for <ietf@ietf.org>; Tue,  5 Feb 2013 05:49:23 -0800 (PST)
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 1U2itc-000ETk-UC; Tue, 05 Feb 2013 08:49:12 -0500
Date: Tue, 05 Feb 2013 08:49:07 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, dcrocker@bbiw.net
Subject: Re: History of protocol discussion or process in WG
Message-ID: <C6D7C89EFA41941F73E4AFE0@JcK-HP8200.jck.com>
In-Reply-To: <5110EF35.4090807@cisco.com>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net> <5110EF35.4090807@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Abdussalam Baryun <abdussalambaryun@gmail.com>, Sam Hartman <hartmans-ietf@mit.edu>, ietf <ietf@ietf.org>, Lixia Zhang <lixia@cs.ucla.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, 05 Feb 2013 13:49:24 -0000

--On Tuesday, February 05, 2013 12:38 +0100 Eliot Lear
<lear@cisco.com> wrote:

>> So don't try.
> 
> +1.  In fact in the ITU context they will sometimes spend half
> a day on a meeting report.  I really don't think we want to go
> there.
> 
> 
> What I would like not to have happen is that we spend any time
> bickering over who said what, especially if it detracts from
> the business of developing excellent standards.  I think your
> point, Dave, about synthesis being left to historians is a
> good one, and I might go farther, and say that the whole
> endeavor should be.  But having at least a record from
> individauls about what *they* said or meant is, I suppose, not
> unreasonable.

One additional and complementary observation:  It has often been
observed that we (and many other bodies and contexts) get better
results when no one worries about taking credit (IIR, someone
(Fred Baker?) even had a signature line to that effect for a
while).  One might even suggest that one of the reasons early
ARPANET/ Internet developments worked better than the IETF
process of today is that there was wide recognition that it was
necessarily a collaborative effort with many people contributing
ideas and no one wanting to seize credit.  I cringe every time
we, or the RFC Editor, get into an argument about numbers of
authors, company names and/or titles in various places, etc.

Trying to do contemporary history (or other oxymorons) on IETF
work that identifies the specific evolution of protocols and
ideas would, IMO, tend to reinforce those impulses toward
identification of inventors and claiming of credit.  If it did,
it would almost certainly be damaging to efficiency and/or
quality independent of the resource and other problems.

    best,
    john




From lberger@labn.net  Tue Feb  5 06:24:44 2013
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DF621F88EA for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:24:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.078
X-Spam-Level: 
X-Spam-Status: No, score=-98.078 tagged_above=-999 required=5 tests=[AWL=-2.774, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMif-2a5a23M for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:24:43 -0800 (PST)
Received: from oproxy1-pub.bluehost.com (oproxy1-pub.bluehost.com [66.147.249.253]) by ietfa.amsl.com (Postfix) with SMTP id B9EED21F85BC for <ietf@ietf.org>; Tue,  5 Feb 2013 06:24:43 -0800 (PST)
Received: (qmail 15246 invoked by uid 0); 5 Feb 2013 14:24:21 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy1.bluehost.com with SMTP; 5 Feb 2013 14:24:21 -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=j2CE59lLdBV/ivgjzSltcmQgrZSSSXTMAxBRAcaaHnY=;  b=Ej9LlQlZoOa9MctnozsH7pPcQTFr0DLd+1p7bmolnwZArX7UCaKaGDseKPc/ANW7mkttu2LVn/4BmH69hoWxGkWG83FGvNvr3cs5w+9fW8LPuoHQwuOqJ97SHGktyy0T;
Received: from box313.bluehost.com ([69.89.31.113]:43566 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1U2jRd-0003uC-83; Tue, 05 Feb 2013 07:24:21 -0700
Message-ID: <51111613.7070300@labn.net>
Date: Tue, 05 Feb 2013 09:24:19 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Lidan (Dan)" <huawei.danli@huawei.com>, Richard Barnes <rbarnes@bbn.com>
Subject: Re: =?GB2312?B?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jYw==?= =?GB2312?B?YW1wLWxtcC1iZWhhdmlvci1uZWdvdGlhdGlvbi0xMA==?=
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
In-Reply-To: <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=GB2312
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: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 14:24:44 -0000

Dan/Richard,
	

On 2/4/2013 10:05 PM, Lidan (Dan) wrote:
> Hi Richard,
> 
> Thanks for the review of this draft!
> 
>> Section 2.1.  Would be helpful to either include the old formats
>> and/or say explicitly what is changing.

> Added the original format of Config, ConfigAck and ConfigNack
> messages which are defined in RFC4204.
> 

I personally think it's a mistake to repeat definitions in non-bis RFCs.
 I think this increases the possibility of mistakes and confusion (e.g.,
when the text isn't copied properly or when the original document is
replaced).

My original thought was to propose text to follow Richard's suggestion
of explicitly saying what has changed, but I see such text is there at
the start of section 2:

   LMP Config, ConfigNack and ConfigAck messages are modified by this
   document to allow for the inclusion of multiple CONFIG objects. The
   Config and ConfigNack messages were only defined to carry one CONFIG
   object in [RFC4204]. The ConfigAck message, which was defined
   without carrying any CONFIG objects in [RFC4204], is modified to
   enable explicit identification of negotiated configuration
   parameters. The inclusion of CONFIG objects in ConfigAck messages is
   triggered by the use of the BehaviorConfig object (defined below) in
   a received Config message.

Richard,

Is this text sufficient?  Alternatively, this text can be moved to
immediately proceed the BNF.

Much thanks
Lou
(document co-author)

From ajs@anvilwalrusden.com  Tue Feb  5 06:30:24 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0304421F87BB for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:30:24 -0800 (PST)
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 6phxUxmB6IMn for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:30:23 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 8A8D421F85FD for <ietf@ietf.org>; Tue,  5 Feb 2013 06:30:23 -0800 (PST)
Received: from mx1.yitter.info (69-196-144-227.dsl.teksavvy.com [69.196.144.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A8FA88A031 for <ietf@ietf.org>; Tue,  5 Feb 2013 14:30:22 +0000 (UTC)
Date: Tue, 5 Feb 2013 09:30:20 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: History of protocol discussion or process in WG
Message-ID: <20130205143020.GA26875@mx1.yitter.info>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net> <5110EF35.4090807@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5110EF35.4090807@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 14:30:24 -0000

On Tue, Feb 05, 2013 at 12:38:29PM +0100, Eliot Lear wrote:
> farther, and say that the whole endeavor should be.  But having at least
> a record from individauls about what *they* said or meant is, I suppose,
> not unreasonable.

Indeed.  And this (and the rest of the posts in this thread) in fact
provide such a record, automatically.

Historians overwhelmingly prefer primary sources, and the IETF (at
least in recent years) is obliging: we have minutes of meetings, full
recordings of the audio streams, and long and well-maintained mailing
list archives.  Historians who wish to figure out the history of some
bit of protocol have ample resources.  I see no reason whatever for
WGs to produce a self-congratulatory (or soul-searching) documents
talking about how they managed to do something.  An obsession with
meta-meta-meta-process is a sure sign of organizational morbidity. 

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From lberger@labn.net  Tue Feb  5 06:53:58 2013
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF45221F88E1 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.516
X-Spam-Level: 
X-Spam-Status: No, score=-101.516 tagged_above=-999 required=5 tests=[AWL=0.749, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6LIQ8nO1aru for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 1B9C321F88B0 for <ietf@ietf.org>; Tue,  5 Feb 2013 06:53:57 -0800 (PST)
Received: (qmail 20318 invoked by uid 0); 5 Feb 2013 14:53:31 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by cpoproxy3.bluehost.com with SMTP; 5 Feb 2013 14:53:31 -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=Zp/lg88axpdkqgMzJIPHgbhQmWfOAxKzzPMhW9VJ3l0=;  b=f+dvtRQio8Dzg27E2nABalxNQJdlAXTN24yXWc5Rj7+f69KplZG7BbSuI/iAX3nSk8+jCMMg4xZ68vSGtpmf2QLNOYzyJpFXgtzifjaoRuuKPbjKxTvJnMzi51mIuP0J;
Received: from box313.bluehost.com ([69.89.31.113]:48237 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1U2jtq-0003zi-Q2; Tue, 05 Feb 2013 07:53:31 -0700
Message-ID: <51111CE8.2060204@labn.net>
Date: Tue, 05 Feb 2013 09:53:28 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
In-Reply-To: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
X-Enigmail-Version: 1.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: draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 14:53:58 -0000

Richard,
	Thank you for the review.  I have one additional question/response on
your comments:

On 2/3/2013 2:13 PM, Richard Barnes wrote:
> I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please seehttp://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-ccamp-lmp-behavior-negotiation-10
> Reviewer: Richard Barnes
> Review Date: 2013-02-02
> IETF LC End Date: 2012-01-21
> IESG Telechat date: 2012-02-07
> 
> Summary:  Ready, with a couple of minor questions / clarifications.
> 
> Comment:
> 
> Overall, this document seems very clear and readable.  Thanks!  The one concern I have is over the use of "likely" in the discussion of backward compatibility; I would like to see more precise language there.
> 
> Section 2.1.  Would be helpful to either include the old formats and/or say explicitly what is changing. 
> 
> Section 2.2.  
> "Nodes which support" -> "nodes that support"  
> "Ordering of CONFIG objects" -> "... With different C-type values"
> 
> Section 3.1.MBZ. Might help to clarify that this means that the
> number of bits MUST be a multiple of 32. (I got a little confused
> between bits and bytes here.)
> 

I think you're right.  The current text can easily result in confision
between the size of the MBZ field and the setting of the length field
define in RFC4204.  It's probably best to just remove the reference to
the length field. How about this:

OLD
The number of bits present is based on the Length field of the LMP
object header and MUST include enough bits so the Length field MUST be
at least 8, and MUST be a multiple of 4.

NEW
This field MUST be sized to ensure 32 bit alignment of the object.

Lou
(co-author)

> Section 4. "Likely"
> Is it possible for a 4204-compliant implementation to not do one of these?  If so then remove "likely".  If not, then why happens on the exceptional case?
> 
> 
> 

From derhoermi@gmx.net  Tue Feb  5 07:05:45 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E3BE21F88FB for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 07:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[AWL=-1.600, 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 infe3btR8ILA for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 07:05:44 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 9F94221F88B2 for <ietf@ietf.org>; Tue,  5 Feb 2013 07:05:44 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.12]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MB0kk-1UCfit1tUC-009yJB for <ietf@ietf.org>; Tue, 05 Feb 2013 16:05:43 +0100
Received: (qmail invoked by alias); 05 Feb 2013 15:05:41 -0000
Received: from p5B062596.dip.t-dialin.net (EHLO netb.Speedport_W_700V) [91.6.37.150] by mail.gmx.net (mp012) with SMTP; 05 Feb 2013 16:05:41 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+lomY1KEqljrA+pC0svEI870TL6cZMxf9tMtVToO IHL17GP9TcoUiU
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Yakov Shafranovich <ietf@shaftek.org>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
Date: Tue, 05 Feb 2013 16:05:37 +0100
Message-ID: <k072h8hsk0jhvl4sjdmgn2c8ahhb6e1g12@hive.bjoern.hoehrmann.de>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de> <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com>
In-Reply-To: <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 15:05:45 -0000

* Yakov Shafranovich wrote:
>[...]

I am interested in this situation:

  -> Someone wants to publish database contents or schema
  -> Use DB-specific dumping tool to create .sql file
  -> Puts .sql file on web server
  -> Server associates .sql with proposed media type

  -> Someone else downloads this resource
  -> Checks IANA registry for the media type
  -> Finds proposed specification

Note that there is no step "publisher of .sql file ensures that the dump
tool generates US-ASCII encoded text, or otherwise makes sure the text's
in a single character encoding and makes sure the web server includes
the character encoding label in the `charset` header of the Content-Type
header when serving the .sql file". Experience suggests that respones
will include no or an incorrect label and downloaders are likely to ig-
nore the charset parameter even if correctly specified. However, reading
the draft the person in the sceanrio above would assume that he has got
US-ASCII encoded text, even though that's fairly unlikely, especially in
the future given "international text" and using UTF-8 without escapes is
becoming increasingly common.

Similarily, the draft would tell him to check some ISO standard for "the
Structured Query Language", even though most likely he should instead
identify which database software generated the file and check the manual
for that software to find out about all the files. As a simple example,
the dumps from <http://dumps.wikimedia.org/> read like this:

  -- MySQL dump 10.13  Distrib 5.1.66, for debian-linux-gnu (x86_64)
  --
  -- Host: 10.0.6.76    Database: frrwiki
  -- ------------------------------------------------------
  -- Server version	5.1.53-wm-log
  
  /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
  /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
  /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
  /*!40101 SET NAMES utf8 */;
  ...
  --
  -- Table structure for table `category`
  --
  
  DROP TABLE IF EXISTS `category`;
  /*!40101 SET @saved_cs_client     = @@character_set_client */;
  /*!40101 SET character_set_client = utf8 */; 
  ...

They do not currently use the proposed type, but if they did, you will
have to know the format of "MySQL dump" files and what the codes in the
comments here mean to conclude that these are actually UTF-8 encoded
files. Google will find other examples with `character_set_client` for
other character encodings like "latin1". The ISO standard, as far as I
am aware, will not help you there, and neither does the US-ASCII default
proposed in the draft.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From rlb@ipv.sx  Tue Feb  5 07:08:59 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82E721F892D for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 07:08:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCabkyLsZvf7 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 07:08:59 -0800 (PST)
Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by ietfa.amsl.com (Postfix) with ESMTP id 7720F21F88B2 for <ietf@ietf.org>; Tue,  5 Feb 2013 07:08:52 -0800 (PST)
Received: by mail-lb0-f181.google.com with SMTP id gm6so307907lbb.12 for <ietf@ietf.org>; Tue, 05 Feb 2013 07:08:51 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=A0UaT9ZPmbRhi/3wCO7S4Z5Du3GC46guabChV+BxHZc=; b=Zc9yj7UamfN6Eer4G/KghJU+U+tftLWkcDwhwoggNuId59uJBydofnbN0B5sb9X5H1 mu2onzHdEESAomdrZJmqubvBnnXpXB2e435W96s5W5xO/y/GBeZTdpZ9AxoJzaA6X8d1 ehWM5vSIhgN46xLvbXybyDN74hS3ZVIaauMDTCNgb6t3tKs8tse+h+9nglyWqrF+0Hqh H+qBAf5cqeYojb/Odm6ACb6V5+1t9yKGaJiiLkCQHm1kSNQ+HvdXX/jgo5nvm8nIGtfl 0PA9e4iWXORngM08yTIF1fhrqIUMJCZzc5MTfhqC6J7DJnbfRb6y+g8Iozml8pg9UoM6 tAZA==
MIME-Version: 1.0
X-Received: by 10.152.127.202 with SMTP id ni10mr23324677lab.6.1360076930915;  Tue, 05 Feb 2013 07:08:50 -0800 (PST)
Received: by 10.112.142.170 with HTTP; Tue, 5 Feb 2013 07:08:50 -0800 (PST)
X-Originating-IP: [155.212.214.60]
In-Reply-To: <51111613.7070300@labn.net>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com> <51111613.7070300@labn.net>
Date: Tue, 5 Feb 2013 10:08:50 -0500
Message-ID: <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
Subject: =?UTF-8?B?UmU6IOetlOWkjTogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAtYg==?= =?UTF-8?B?ZWhhdmlvci1uZWdvdGlhdGlvbi0xMA==?=
From: Richard Barnes <rlb@ipv.sx>
To: Lou Berger <lberger@labn.net>
Content-Type: multipart/alternative; boundary=f46d042c6aeb559dba04d4fb9641
X-Gm-Message-State: ALoCoQnlmjEjikRfzQUJi1fqUKZNiMU8zFvUyYc6TjYTU5y/i1NosIeKNk94b7dgVN/GPvPtYYw7
Cc: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "Lidan \(Dan\)" <huawei.danli@huawei.com>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 15:09:00 -0000

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

Hey Lou,

That text looks fine to me!

--Richard


On Tue, Feb 5, 2013 at 9:24 AM, Lou Berger <lberger@labn.net> wrote:

> Dan/Richard,
>
>
> On 2/4/2013 10:05 PM, Lidan (Dan) wrote:
> > Hi Richard,
> >
> > Thanks for the review of this draft!
> >
> >> Section 2.1.  Would be helpful to either include the old formats
> >> and/or say explicitly what is changing.
>
> > Added the original format of Config, ConfigAck and ConfigNack
> > messages which are defined in RFC4204.
> >
>
> I personally think it's a mistake to repeat definitions in non-bis RFCs.
>  I think this increases the possibility of mistakes and confusion (e.g.,
> when the text isn't copied properly or when the original document is
> replaced).
>
> My original thought was to propose text to follow Richard's suggestion
> of explicitly saying what has changed, but I see such text is there at
> the start of section 2:
>
>    LMP Config, ConfigNack and ConfigAck messages are modified by this
>    document to allow for the inclusion of multiple CONFIG objects. The
>    Config and ConfigNack messages were only defined to carry one CONFIG
>    object in [RFC4204]. The ConfigAck message, which was defined
>    without carrying any CONFIG objects in [RFC4204], is modified to
>    enable explicit identification of negotiated configuration
>    parameters. The inclusion of CONFIG objects in ConfigAck messages is
>    triggered by the use of the BehaviorConfig object (defined below) in
>    a received Config message.
>
> Richard,
>
> Is this text sufficient?  Alternatively, this text can be moved to
> immediately proceed the BNF.
>
> Much thanks
> Lou
> (document co-author)
>

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

<div dir=3D"ltr">Hey Lou,<div><br></div><div>That text looks fine to me!</d=
iv><div><br></div><div style>--Richard</div></div><div class=3D"gmail_extra=
"><br><br><div class=3D"gmail_quote">On Tue, Feb 5, 2013 at 9:24 AM, Lou Be=
rger <span dir=3D"ltr">&lt;<a href=3D"mailto:lberger@labn.net" target=3D"_b=
lank">lberger@labn.net</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">Dan/Richard,<br>
<div class=3D"im"><br>
<br>
On 2/4/2013 10:05 PM, Lidan (Dan) wrote:<br>
&gt; Hi Richard,<br>
&gt;<br>
&gt; Thanks for the review of this draft!<br>
&gt;<br>
&gt;&gt; Section 2.1. =A0Would be helpful to either include the old formats=
<br>
&gt;&gt; and/or say explicitly what is changing.<br>
<br>
&gt; Added the original format of Config, ConfigAck and ConfigNack<br>
&gt; messages which are defined in RFC4204.<br>
&gt;<br>
<br>
</div>I personally think it&#39;s a mistake to repeat definitions in non-bi=
s RFCs.<br>
=A0I think this increases the possibility of mistakes and confusion (e.g.,<=
br>
when the text isn&#39;t copied properly or when the original document is<br=
>
replaced).<br>
<br>
My original thought was to propose text to follow Richard&#39;s suggestion<=
br>
of explicitly saying what has changed, but I see such text is there at<br>
the start of section 2:<br>
<br>
=A0 =A0LMP Config, ConfigNack and ConfigAck messages are modified by this<b=
r>
=A0 =A0document to allow for the inclusion of multiple CONFIG objects. The<=
br>
=A0 =A0Config and ConfigNack messages were only defined to carry one CONFIG=
<br>
=A0 =A0object in [RFC4204]. The ConfigAck message, which was defined<br>
=A0 =A0without carrying any CONFIG objects in [RFC4204], is modified to<br>
=A0 =A0enable explicit identification of negotiated configuration<br>
=A0 =A0parameters. The inclusion of CONFIG objects in ConfigAck messages is=
<br>
=A0 =A0triggered by the use of the BehaviorConfig object (defined below) in=
<br>
=A0 =A0a received Config message.<br>
<br>
Richard,<br>
<br>
Is this text sufficient? =A0Alternatively, this text can be moved to<br>
immediately proceed the BNF.<br>
<br>
Much thanks<br>
Lou<br>
(document co-author)<br>
</blockquote></div><br></div>

--f46d042c6aeb559dba04d4fb9641--

From chair@ietf.org  Tue Feb  5 08:04:48 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1024121F88FB; Tue,  5 Feb 2013 08:04:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jJ3hw1ID9M3F; Tue,  5 Feb 2013 08:04:47 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 1D02C21F8552; Tue,  5 Feb 2013 08:04:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 15E371244BA; Tue,  5 Feb 2013 08:04:40 -0800 (PST)
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 RkpVKKwY1wyM; Tue,  5 Feb 2013 08:04:39 -0800 (PST)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 751C71244B6; Tue,  5 Feb 2013 08:04:39 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Remote Participation Services
Mime-Version: 1.0 (Apple Message framework v1085)
From: IETF Chair <chair@ietf.org>
Date: Tue, 5 Feb 2013 11:04:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: IAOC <iaoc@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 16:04:48 -0000

Please see the attached report on the current status of remote =
participation in the IETF meeting.  Please notice at the end a call for =
potential experiments to explore ways that we can improve remote =
participation.

Russ Housley
IETF Chair

Bob Hinden
IAOC Chair


=3D =3D =3D =3D =3D =3D =3D =3D =3D=20


Status of Remote Participation Services in the IETF Today

                      Russ Housley
                     1 February 2013

1.  Introduction

   For more than a decade, the IETF has tried to make it easier for=20
   remote attendees to participate in regular and interim face-to-face
   meetings.  At the same time, some IETF Working Groups (WGs) have
   started to conduct virtual interim meetings.

   The IETF's current remote participation system ("RPS") consists of a
   outbound real-time audio stream for each session carried to remote
   attendees over HTTP, textual multi-user chat carried over XMPP
   (commonly called Jabber), and posting of slides prior to the WG
   session so that they can be downloaded from the IETF web site.

   WebEx and Meetecho are experimentally supported, offering outbound
   real-time audio stream synchronized to the slides for the remote
   participant.  Meetecho displays the Jabber Room on the screen with
   slides, and it can also be used to replay the audio and slides from
   a recording.
  =20
   Some WGs also employ ad-hoc tools, such as Skype for two-way audio =
and
   video conferencing and Etherpad for shared document editing.

2. Regular and Interim IETF Meetings

   Today, it is easy to remotely observe IETF sessions, but it is very
   difficult to participate in discussions.  However, several tools are
   used to accommodate remote participants.  To the greatest extent
   possible, these tools rely on IETF or other open standards, and they
   embrace both IPv4 and IPv6 without network address translation.

2.1. Audio

   Anyone can use a web browser to receive real-time audio of the IETF
   meeting sessions.  The URLs for the audio are announced in advance,
   and the audio recording becomes part of the session proceedings.

   It is quite difficult for a remote participant to have their voice
   heard in the session.  The WebEx and Meetecho systems can accommodate
   this with advance setup and testing.  However, allowing arbitrary
   remote participants to speak does not work well.  Connecting to the
   audio system in the meeting facility is quite problematic.  Further,
   a WG Chair would need sophisticated controls to maintain order if
   arbitrary remote participants were able to speak at any time.
   While WebEx and Meetecho provide some participation management
   features, but integration with in-room participation is needed.

2.2. Video

   In the 1990s as part of the multicast experiment, multicast video was
   made available, but this experiment has ended without evolving into a
   production service.

   As part of a separate experiment, some sessions use Meetecho to make
   video available to anyone with a web browser.  WG Chairs must request
   this coverage.  When Meetecho is used, the URLs are announced in
   advance, and the recording becomes part of the session proceedings.

2.3. Multi-User Chat

   Multi-user chat (MUC) is used both as a remote participation tool as
   well as a communication tool for local attendees, to raise and =
resolve
   issues without intruding on the presentation.  Each WG has a Jabber
   Room for Multi-User Chat, which employs the XMPP Standards Foundation
   (XSF) XEP-045 specification.  These Jabber Rooms can can be used at
   any time, not just during the IETF meetings.  During the session,
   remote participants that are listening to the audio are able to ask
   questions by typing them in the Jabber Room, and then someone in the
   physical room reads the question at the mic.  This is called
   MUC-to-Mic Relay.  The Jabber Room log becomes part of the session
   proceedings.

2.4. Slide Sharing

   Anyone can use a web browser to fetch the session slides.  WG Chairs
   are responsible for posting the slides prior to the session, and the
   slides (in PDF format) become part of the session proceedings.

   When Meetecho is used, the audio or video is presented in a
   synchronized fashion along with the jabber room and slides.

2.5. Remote Presenter

   When a presenter cannot attend, someone else usually presents their
   slides.  Some WG Chairs have tried remote presentations using WebEx
   and Meetecho.  Neither system is ideal, and the audio can include
   squeals and echos.  Both systems require advance setup and testing.

   The projection of the remote presenter's face as well as their slides
   seems to improve the experience for the people in the room, but we
   have only done this successfully a few times.  An extra projector and
   screen are needed for this to work well.

2.6.  Shared Text Document Editing

   In some sessions, there is an attempt to edit a text document with
   input from the local and remote attendees.  This is most often done
   for minutes and proposed WG charter changes.  Etherpad is the most
   popular tool for this purpose.  There has been no attempt to
   standardize the tools or protocols used for this function.

2.7.  Participant Management

   A typical meeting discussion takes place by people that want to speak
   forming a line at the microphone, and the presenter replies to each
   person in turn.  However, sometimes someone will jump the queue to
   contribute to a particular discussion point.  This mechanism does not
   provide a natural means for including remote participants.  WebEx and
   Meetecho do have a feature for noting a request to speak, but this
   is not visible to in-room participants.  Hence the burden of managing
   remote participation falls to the WG Chair or their designee.

3. Virtual WG Meeting and Leadership Teleconferences

   For a virtual meeting, all participants are remote; there is no
   physical meeting room.  A virtual WG meeting is usually held to =
tackle
   a very small number of open issues.  Hence, all of the remote
   participation tools must be interactive, permitting any participant =
to
   contribute.  The primary tool for these meetings is WebEx, in a
   conference-call mode, with no queuing of speakers.  The WG Chair's
   ability to manage discussion becomes challenging as the size of the
   virtual meeting grows.

   The teleconferences held by bodies like the IESG, IAOC, and IAB are
   somewhat like an virtual WG meeting, except they are held more often
   and size of the meeting is constrained.  The fact that all
   participants know each other facilitates the use of a more informal
   process than is typically possible for an open virtual WG meeting.
   Again, all of the participants are remote.

3.1. Audio

   For virtual WG meeting, access is open, as for regular IETF meetings.
   For leadership teleconferences, access is limited to those who are
   invited.  In recent years, WebEx has been used.  WebEx supports
   telephone dial-in as well as VoIP for the audio, although it may not
   be totally aligned with the IETF standards in this area.  Skype and
   similar systems can be used to dial into WebEx.  Sometimes issues =
with
   an echo take time to resolve, but the quality is generally quite =
good.

3.2. Video

   So far, there has been no need for video.  When someone accidentally
   turns on the WebEx video, they are asked to turn it off so that
   bandwidth is available for quality audio.

3.3. Multi-User Chat

   A jabber room or the WebEx built-in chat is used among the
   participants.  The scribes often find this useful for capturing
   accurate minutes.

3.4. Slide Sharing

   Slides are often sent by email in advance of the meeting.
  =20
   WebEx allows the slides and desktop applications to be viewed by the
   remote participants.  These are controlled by the presenter.  The
   presenter can be shifted from participant to participant as needed.

3.5. Remote Presenter

   WebEx allows the slides to be controlled by the presenter.

3.6.  Shared Text Document Editing

   Some scribes use Etherpad for minutes.  This allows participants to
   review and even correct the minutes as the meeting takes place.

4. Improvements

   The IETF has always used the Internet to do its work, and remote
   participation is no exception.  The IETF wants to improve the tools
   provided in the RPS tools; a better RPS would allow remote IETF
   attendees to participate more effectively.

   The IETF is seeking improvements that allow remote participants to
   more naturally contribute to in-room discussion and allow meeting
   management to integrate local and remote participants into a common
   queue.

   RPS technologies are not yet mature enough to create a production
   service for the IETF, but these technologies are developing rapidly.
   The IETF will be conducting more experiments in order to achieve
   these improvements as early as possible.  To this end, the IAOC is
   soliciting suggestions for experiments.  If you have suggestions for
   experiments, please tell the IAOC:

      (1)  What hardware and software is needed?
      (2)  What people resources are needed in the meeting?
      (3)  What are the expected benefits to the IETF participants?


From daedulus@btconnect.com  Tue Feb  5 08:05:48 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2B0921F88EA for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 08:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.543
X-Spam-Level: 
X-Spam-Status: No, score=-5.543 tagged_above=-999 required=5 tests=[AWL=1.056,  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 y-JwvL6e1IUQ for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 08:05:48 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id 518FB21F8933 for <ietf@ietf.org>; Tue,  5 Feb 2013 08:05:47 -0800 (PST)
Received: from mail141-co9-R.bigfish.com (10.236.132.238) by CO9EHSOBE032.bigfish.com (10.236.130.95) with Microsoft SMTP Server id 14.1.225.23; Tue, 5 Feb 2013 16:05:46 +0000
Received: from mail141-co9 (localhost [127.0.0.1])	by mail141-co9-R.bigfish.com (Postfix) with ESMTP id A2C832C02DA; Tue,  5 Feb 2013 16:05:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.250.181; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0711HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz9371I542I1418Izz1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h304l1155h)
Received: from mail141-co9 (localhost.localdomain [127.0.0.1]) by mail141-co9 (MessageSwitch) id 1360080344637760_9961; Tue,  5 Feb 2013 16:05:44 +0000 (UTC)
Received: from CO9EHSMHS024.bigfish.com (unknown [10.236.132.227])	by mail141-co9.bigfish.com (Postfix) with ESMTP id 9074B1E004C; Tue,  5 Feb 2013 16:05:44 +0000 (UTC)
Received: from AMSPRD0711HT002.eurprd07.prod.outlook.com (157.56.250.181) by CO9EHSMHS024.bigfish.com (10.236.130.34) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 5 Feb 2013 16:05:41 +0000
Received: from DBXPRD0411HT003.eurprd04.prod.outlook.com (157.56.253.165) by pod51017.outlook.com (10.242.14.163) with Microsoft SMTP Server (TLS) id 14.16.263.1; Tue, 5 Feb 2013 16:05:32 +0000
Message-ID: <01d501ce03ba$355cd600$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <iab@iab.org>
References: <4A7BEACC-2BC7-45DE-8780-024ED5C6D540@iab.org>
Subject: Re: Call for Comment: "Issues in Identifier Comparison for SecurityPurposes"
Date: Tue, 5 Feb 2013 16:02:18 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.165]
X-OriginatorOrg: btconnect.com
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 16:05:48 -0000

>From the title, I was expecting something a little deeper; I find this
I-D strong on current detail, less so on the underlying, perhaps
more lasting issues.

For example, as has been pointed out on these lists before, identifiers
refer to an identity and an object may have multiple identities in
different contexts and each identity may have multiple identifiers.  (Is
an SSN a different identifier to the same identity as a passport number,
or to a different identity? DISCUSS).  This I-D seems to skate over this
issue seeming to assume for the most part that there is one identity and
one identifier.  I think the I-D should at least mention to this
underlying complexity.

Equally, in the discussion of tests, the I-D rightly points out the
concepts of false negative and false positive but could go further.  The
gold standard test, one that is always right, is a fine concept that
does not exist in our engineered world.  Rather, most, if not all, tests
can be modified to increase the probability of false positives and
decrease the probability of false negatives, or vice versa; and which
outcome  is better depends on the context.  (The example of this last I
see quoted is a test for a serious disease, when a false (positive)
diagnosis is usually seen as the preferred outcome).  Again, this is the
sort of background I would expect to see some reference to.

The distinction between host names and domain names is also one that
surfaces regularly here.  Section 3.1 alludes to this but, for me, is
not clear enough about the definitions thereof that the IETF has made;
this recurs in section 3.4.  This last section seems imprecise about
e-mail addresses; RFC5321 is specific -  "The local-part of a mailbox
MUST BE treated as case sensitive" - so I think that that could be
brought out more strongly here.  There is a more general issue
underlying this, that a body such as the IETF produces a precise
specification but manufacturers, or other SDOs or even later WGs within
the IETF, then make it looser, with local  variations, which may in time
come to be taken as the standard.  In this case, a sharper distinction
could be drawn between an e-mail address, as the IETF has specified, and
an e-mail-like address, as used in other contexts.

Tom Petch

----- Original Message -----
From: "IAB Chair" <iab-chair@iab.org>
To: <ietf-announce@ietf.org>
Sent: Wednesday, January 09, 2013 8:42 PM

This is an announcement of an IETF-wide Call for Comment on 'Issues in
Identifier Comparison for Security Purposes'.

The document is being considered for publication as an Informational RFC
within the IAB stream, and is available for inspection here:
http://tools.ietf.org/html/draft-iab-identifier-comparison

The Call for Comment will last until February 10, 2013. Please send
comments to iab at iab.org or submit them via TRAC (see below).
===============================================================
Submitting Comments via TRAC
1. To submit an issue in TRAC, you first need to login to the IAB site
on the tools server:
http://tools.ietf.org/wg/iab/trac/login

2. If you don't already have a login ID, you can obtain one by
navigating to this site:
http://trac.tools.ietf.org/newlogin

3. Once you have obtained an account, and have logged in, you can file
an issue by navigating to the ticket entry form:
http://trac.tools.ietf.org/wg/iab/trac/newticket

4. When opening an issue:
a. The Type: field should be set to "defect" for an issue with the
current document text, or "enhancement" for a proposed addition of
functionality (such as an additional requirement).
b. The Priority: field is set based on the severity of the Issue. For
example, editorial issues are typically "minor" or "trivial".
c. The Milestone: field should be set to milestone1 (useless, I know).
d. The Component: field should be set to the document you are filing the
issue on.
e. The Version: field should be set to "1.0".
f. The Severity: field should be set to based on the status of the
document (e.g. "In WG Last Call" for a document in IAB last call)
g. The Keywords: and CC: fields can be left blank unless inspiration
seizes you.
h. The Assign To: field is generally filled in with the email address of
the editor.

5. Typically it won't be necessary to enclose a file with the ticket,
but if you need to, select "I have files to attach to this ticket".

6. If you want to preview your Issue, click on the "Preview" button.
When you're ready to submit the issue, click on the "Create Ticket"
button.

7. If you want to update an issue, go to the "View Tickets" page:
http://trac.tools.ietf.org/wg/iab/trac/report/1

Click on the ticket # you want to update, and then modify the ticket
fields as required.



From yakov@shaftek.org  Tue Feb  5 17:11:48 2013
Return-Path: <yakov@shaftek.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 E41D221F89D5 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 17:11:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.702
X-Spam-Level: 
X-Spam-Status: No, score=-1.702 tagged_above=-999 required=5 tests=[AWL=-1.275, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, 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 RF3Hf2lwNxjr for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 17:11:48 -0800 (PST)
Received: from mail-ie0-x230.google.com (ie-in-x0230.1e100.net [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 06B5E21F89E9 for <ietf@ietf.org>; Tue,  5 Feb 2013 17:11:36 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id k13so1140843iea.35 for <ietf@ietf.org>; Tue, 05 Feb 2013 17:11:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:content-transfer-encoding:x-gm-message-state; bh=QviYsDKQn6WAtTd0FxC21nDk9L2eiNwpwCXakw6ds5Y=; b=Z5csfWd5CoqWJpwp1zlJPVyB1Bz3Fg3Hdc1kvngPt4HuNjGXPi4oKKJ+5fl7UMMytm FSlkwtoECD3I86GPRiOAiN5dpUD+AvTCLwhNWyWYkvwPiF54NHpC5X7+jy3DvmPdv1xc 9OiTK1hShy25EkZSEvXmIC8vJ//8DkRykRTE2mMQCtzAzRZeENAvASShnCCGCTrKAVvT 183NTyNraCIvXwz8btN8K74t0Z0qo2VzJf5Ex2pEljIEfHOO74kkV9StinLBqW5zd9vA Nwd5Aa54skVAR+xQ2sW67NY8uB8yYUaqVrLeMDfapia/COXkFOhppt/3jYP1c8Gn5kFV wseQ==
X-Received: by 10.50.135.105 with SMTP id pr9mr2383642igb.6.1360113096302; Tue, 05 Feb 2013 17:11:36 -0800 (PST)
MIME-Version: 1.0
Sender: yakov@shaftek.org
Received: by 10.64.126.232 with HTTP; Tue, 5 Feb 2013 17:11:06 -0800 (PST)
X-Originating-IP: [98.140.248.199]
In-Reply-To: <k072h8hsk0jhvl4sjdmgn2c8ahhb6e1g12@hive.bjoern.hoehrmann.de>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de> <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com> <k072h8hsk0jhvl4sjdmgn2c8ahhb6e1g12@hive.bjoern.hoehrmann.de>
From: Yakov Shafranovich <ietf@shaftek.org>
Date: Tue, 5 Feb 2013 20:11:06 -0500
X-Google-Sender-Auth: -f-AU7-Cj8pGuQvgGS-4gLvMpzE
Message-ID: <CAPQd5oRrqNPuJm_RnFKS0X=BCpvjMs8DhMX-RNSRVcnWetDRdw@mail.gmail.com>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQk6uCfRLu7gRL8nS1bReP47txY40e+Cg1sTtDE2pKEdwGEtEYH2WTIgSGfqmuxVcJ17xqPF
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 01:11:49 -0000

I would agree that in this scenario the ISO standard would not help
since it would only govern how the SQL client talks to the db server,
not when it is placed on a web server.

I think the situation is actually very similar to the one described in
RFC 6657 where there maybe a conflict between the charset parameter on
the outside and inside the payload:

  In order to improve interoperability with deployed agents, "text/*"
   media type registrations SHOULD either

   a.  specify that the "charset" parameter is not used for the defined
       subtype, because the charset information is transported inside
       the payload (such as in "text/xml"), or

   b.  require explicit unconditional inclusion of the "charset"
       parameter, eliminating the need for a default value.

   In accordance with option (a) above, registrations for "text/*" media
   types that can transport charset information inside the corresponding
   payloads (such as "text/html" and "text/xml") SHOULD NOT specify the
   use of a "charset" parameter, nor any default value, in order to
   avoid conflicting interpretations should the "charset" parameter
   value and the value specified in the payload disagree.

While this is in the "application/*" tree, going with choice A would
essentially drop the "charset" parameter and in your example, would
have the implementors trying to figure out the charset from the
payload itself.

The question is what happens when the SQL file itself carries no
charset information, such as when using "mysql-dump" with the
"--skip-set-charset" option. According to MYSQL, UTF-8 would be used
in v5.1+ and ASCII in versions prior to that. Perhaps, we should leave
"charset" as an optional parameter for cases like these, and just take
out the default value.

Yakov

On Tue, Feb 5, 2013 at 10:05 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote=
:
> * Yakov Shafranovich wrote:
>>[...]
>
> I am interested in this situation:
>
>   -> Someone wants to publish database contents or schema
>   -> Use DB-specific dumping tool to create .sql file
>   -> Puts .sql file on web server
>   -> Server associates .sql with proposed media type
>
>   -> Someone else downloads this resource
>   -> Checks IANA registry for the media type
>   -> Finds proposed specification
>
> Note that there is no step "publisher of .sql file ensures that the dump
> tool generates US-ASCII encoded text, or otherwise makes sure the text's
> in a single character encoding and makes sure the web server includes
> the character encoding label in the `charset` header of the Content-Type
> header when serving the .sql file". Experience suggests that respones
> will include no or an incorrect label and downloaders are likely to ig-
> nore the charset parameter even if correctly specified. However, reading
> the draft the person in the sceanrio above would assume that he has got
> US-ASCII encoded text, even though that's fairly unlikely, especially in
> the future given "international text" and using UTF-8 without escapes is
> becoming increasingly common.
>
> Similarily, the draft would tell him to check some ISO standard for "the
> Structured Query Language", even though most likely he should instead
> identify which database software generated the file and check the manual
> for that software to find out about all the files. As a simple example,
> the dumps from <http://dumps.wikimedia.org/> read like this:
>
>   -- MySQL dump 10.13  Distrib 5.1.66, for debian-linux-gnu (x86_64)
>   --
>   -- Host: 10.0.6.76    Database: frrwiki
>   -- ------------------------------------------------------
>   -- Server version     5.1.53-wm-log
>
>   /*!40101 SET @OLD_CHARACTER_SET_CLIENT=3D@@CHARACTER_SET_CLIENT */;
>   /*!40101 SET @OLD_CHARACTER_SET_RESULTS=3D@@CHARACTER_SET_RESULTS */;
>   /*!40101 SET @OLD_COLLATION_CONNECTION=3D@@COLLATION_CONNECTION */;
>   /*!40101 SET NAMES utf8 */;
>   ...
>   --
>   -- Table structure for table `category`
>   --
>
>   DROP TABLE IF EXISTS `category`;
>   /*!40101 SET @saved_cs_client     =3D @@character_set_client */;
>   /*!40101 SET character_set_client =3D utf8 */;
>   ...
>
> They do not currently use the proposed type, but if they did, you will
> have to know the format of "MySQL dump" files and what the codes in the
> comments here mean to conclude that these are actually UTF-8 encoded
> files. Google will find other examples with `character_set_client` for
> other character encodings like "latin1". The ISO standard, as far as I
> am aware, will not help you there, and neither does the US-ASCII default
> proposed in the draft.
> --
> Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehr=
mann.de
> Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld=
.de
> 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev=
.de/

From abdussalambaryun@gmail.com  Tue Feb  5 18:14:49 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7696221F8769; Tue,  5 Feb 2013 18:14:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8y+F4+3HMZ+b; Tue,  5 Feb 2013 18:14:49 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A58B321F8691; Tue,  5 Feb 2013 18:14:48 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id k14so720522wer.11 for <multiple recipients>; Tue, 05 Feb 2013 18:14:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=LWg+6M632ETn3VOvadoEFnhPJyrvFAwn5NFonOWYsf0=; b=0jLK35IbidKQeQLzJrQ6GZpnTXCJbaNPQIl2CpEBddETBqYwqecUzZ/F7xCAPjc0AG Ge/FaeWxKRQtkdhiqWe+uMxkw3QpWgA9G9HfdVvwX/aNDLE92oWa6t25wfnUxhSg60qa dr+gfmQXMtL5cTTErpT8gS4RO7POdgUDG2R4kju18/zc/SmPvj/DpNn5J+2dx78QlO8W IQSVIH5N6Khfne2KW3yBsgKrL7tp3lN10/Q1qUqIzASLPQuoUeN7oCWdS/fmUcvJPcFV Uh+hdBz/q5pMJvgrwh2E2EOhsZIb9SfcruUCfXQRniNAcEiU+pSUj8RZSfKg9kmCnLFt Vkhw==
MIME-Version: 1.0
X-Received: by 10.180.86.36 with SMTP id m4mr1855562wiz.5.1360116887897; Tue, 05 Feb 2013 18:14:47 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Tue, 5 Feb 2013 18:14:47 -0800 (PST)
Date: Wed, 6 Feb 2013 03:14:47 +0100
Message-ID: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.gmail.com>
Subject: Re: Remote Participation Services
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: chair@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 02:14:49 -0000

Dear IETF Chair,

In the previous ietf meeting in July, I have submitted an I-D in one
WG but had no chance to present my participation remotely, as you
mention in 2.5. I would like the solution and that I will be able to
present remotely. I asked the WG if someone can present for me but
only WG darfts are done the way mentioned in 2.5,

Please amend the [1] to include that there is difference process in
IETF participation remotely for WG I-Ds and Individual I-Ds,

If I misundertood or if there is a solution that I don't know about
please advise,

AB
++
Please see the attached report on the current status of remote
participation in the IETF meeting.  Please notice at the end a call
for potential experiments to explore ways that we can improve remote
participation.

Russ Housley
IETF Chair

Bob Hinden
IAOC Chair


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

From barryleiba.mailing.lists@gmail.com  Tue Feb  5 18:15:29 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E153221F8625 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 18:15:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.002
X-Spam-Level: 
X-Spam-Status: No, score=-103.002 tagged_above=-999 required=5 tests=[AWL=-0.025, 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 x0UsRpo5cv7l for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 18:15:29 -0800 (PST)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3EA1921F861A for <ietf@ietf.org>; Tue,  5 Feb 2013 18:15:29 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id fy27so519812vcb.7 for <ietf@ietf.org>; Tue, 05 Feb 2013 18:15:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=e84jVg/J0q63lVhJZzgJbRG/KuhLsmyT2S9BfMox8aU=; b=UVuY1U+ib8daY2U+/ZwvVew3al5lTQ6E2lPJ2WC8tOxwyediA0Tc6kE5bEiCqQhZkc 942L5xyidGI+aecY0M/oiObe1XZBFtzMpgpaQKsCyYtKofn5LZ4t3t/xuaq6DXrHS++c sWOLyKVS6H3CjTTvvYCdvNe1DBAElt0xf6tL2i8XKJc+EA9Z9wFXRwGJAQFatYpUZdlG +XQ2ZI7swv1smNjWAv1VA4Ez6lD6EcuTJdkvA4+eaWUx/4qzyB60ika0TrgZO0tS0BDZ 4EQzPss51kQAhUelrz6HVuSuUqMMhy46g6HGL3ITEOrihlV6Yj5aWhEIXElnvTmK9uDT blvg==
MIME-Version: 1.0
X-Received: by 10.58.196.196 with SMTP id io4mr26977783vec.22.1360116928553; Tue, 05 Feb 2013 18:15:28 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Tue, 5 Feb 2013 18:15:28 -0800 (PST)
In-Reply-To: <CAPQd5oRrqNPuJm_RnFKS0X=BCpvjMs8DhMX-RNSRVcnWetDRdw@mail.gmail.com>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de> <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com> <k072h8hsk0jhvl4sjdmgn2c8ahhb6e1g12@hive.bjoern.hoehrmann.de> <CAPQd5oRrqNPuJm_RnFKS0X=BCpvjMs8DhMX-RNSRVcnWetDRdw@mail.gmail.com>
Date: Wed, 6 Feb 2013 10:15:28 +0800
X-Google-Sender-Auth: Xi3uoPq8MMf9kxvxZe09fOBjg_U
Message-ID: <CAC4RtVA1pxGq-z85tx+gj7QgHrF86VhmcMRYMduCWPT7+cO16w@mail.gmail.com>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
From: Barry Leiba <barryleiba@computer.org>
To: Yakov Shafranovich <ietf@shaftek.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 02:15:30 -0000

> The question is what happens when the SQL file itself carries no
> charset information, such as when using "mysql-dump" with the
> "--skip-set-charset" option. According to MYSQL, UTF-8 would be used
> in v5.1+ and ASCII in versions prior to that. Perhaps, we should leave
> "charset" as an optional parameter for cases like these, and just take
> out the default value.

That sounds to me like the way to go.  Perhaps a "MUST use" the
charset parameter when the SQL file carries no charset information,
"MUST NOT use" otherwise?

Barry

From abdussalambaryun@gmail.com  Tue Feb  5 18:16:31 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F35E21F8950 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 18:16:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.099
X-Spam-Level: 
X-Spam-Status: No, score=-3.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OoWaqSRqy2sT for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 18:16:29 -0800 (PST)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7D721F8769 for <ietf@ietf.org>; Tue,  5 Feb 2013 18:16:29 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id 8so694362wgl.6 for <ietf@ietf.org>; Tue, 05 Feb 2013 18:16:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=QsCk8pyBQPZJvC9zSti0bYzwaje1YsphIdKzwIR3Q4w=; b=QxxQxCAUyaFftHmQiRii0TQIO7cLy3ObyirMeLE09JmjIXdsYHe2GLuPJwB3cE5YSY 9XEtikFB7KH6fzEIEee3FCEAMA/B56117YbF5+eOadeoseivSNmznaFuCk2uhAE4YYON b1Epe2LahNISxR8iYc53ljlXL9avjkMl9IaBXPsIms770uRmZ2aGfBxcdfIOyQ9GVs+7 xyrODUmjD89tyiYcA9SpDb8oX+1nRPinPyXSJeWqpyPngotyciyk9JoQr4OhQ0DRHFiP MaWyB3AsBrUbojb8eEz7rzAAzZU/tSlYev5TBR0xQGNhgn7oZsgcpBBeLXlZs4uCTe7k HYRA==
MIME-Version: 1.0
X-Received: by 10.194.20.231 with SMTP id q7mr46520141wje.44.1360116985445; Tue, 05 Feb 2013 18:16:25 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Tue, 5 Feb 2013 18:16:25 -0800 (PST)
In-Reply-To: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.gmail.com>
References: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.gmail.com>
Date: Wed, 6 Feb 2013 03:16:25 +0100
Message-ID: <CADnDZ898TjCxZeMu8Mwrtr6+cZbRn8Y0sMoj6s8GB1LwJ1pBAA@mail.gmail.com>
Subject: Re: Remote Participation Services
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 02:16:31 -0000

On 2/6/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Please amend the [1] to include that there is difference process in
> IETF participation remotely for WG I-Ds and Individual I-Ds,

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

From yakov@shaftek.org  Tue Feb  5 19:43:24 2013
Return-Path: <yakov@shaftek.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 5428421F8900 for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 19:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.276
X-Spam-Level: 
X-Spam-Status: No, score=-1.276 tagged_above=-999 required=5 tests=[AWL=-0.850, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, 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 laPEhcQC4uzI for <ietf@ietfa.amsl.com>; Tue,  5 Feb 2013 19:43:23 -0800 (PST)
Received: from mail-ie0-x22f.google.com (ie-in-x022f.1e100.net [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B403221F8625 for <ietf@ietf.org>; Tue,  5 Feb 2013 19:43:23 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id c12so1268397ieb.20 for <ietf@ietf.org>; Tue, 05 Feb 2013 19:43:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:x-originating-ip:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type:x-gm-message-state; bh=TvRazLsnDPeMEybr3jxE8Ln3fQyaeVv63adIjdaDMGM=; b=ZogP0nBSFNiC0vZ/VIkzHm+lX0tipve87G5N3Cnsmg/uyrF/IQO7UtdjuqYg4h0Uz9 z6RgjuGLVG9AWoGiu6WbstkaSAnUgxIR7cqXr/ekDaFSLYk++HwjQasZol1eRvdxP5vo zD3cI69RYtlsLNCMt1r1ry5FOaVcNMgsY5zTbfpHoD6xjskEDbNUzgfSNHcc+GAj0djr hiEV1a2iwHX06YRA2pAZ78ZLdzrQ75VUsXJm/oZzPRVPdCe1E0Yi6459UQtWjJI+k/44 ux51yzcLMWABfdRxp3Ki12gW/wX4B20J/n4vSzyXl8CpeLooDeHLmJuPcDluUvAj+KAB kmxg==
X-Received: by 10.50.100.170 with SMTP id ez10mr3096413igb.27.1360122203295; Tue, 05 Feb 2013 19:43:23 -0800 (PST)
MIME-Version: 1.0
Sender: yakov@shaftek.org
Received: by 10.64.126.232 with HTTP; Tue, 5 Feb 2013 19:42:53 -0800 (PST)
X-Originating-IP: [98.140.248.199]
In-Reply-To: <CAC4RtVA1pxGq-z85tx+gj7QgHrF86VhmcMRYMduCWPT7+cO16w@mail.gmail.com>
References: <1ah0g8p99e7rljhvndsmqi7qp8ujoj4ije@hive.bjoern.hoehrmann.de> <CAPQd5oTW7w7gaNzGc1TP9C_yD2ODEec5RvzHKbt=nK04+PRzvA@mail.gmail.com> <k072h8hsk0jhvl4sjdmgn2c8ahhb6e1g12@hive.bjoern.hoehrmann.de> <CAPQd5oRrqNPuJm_RnFKS0X=BCpvjMs8DhMX-RNSRVcnWetDRdw@mail.gmail.com> <CAC4RtVA1pxGq-z85tx+gj7QgHrF86VhmcMRYMduCWPT7+cO16w@mail.gmail.com>
From: Yakov Shafranovich <ietf@shaftek.org>
Date: Tue, 5 Feb 2013 22:42:53 -0500
X-Google-Sender-Auth: Lx56SKfAivFluCntPqRxYq_-HiE
Message-ID: <CAPQd5oT0dXq4fQq0hcVS8gNU3qRH2CYWZA1q5Co=iygTkS5ijA@mail.gmail.com>
Subject: Re: Comments on draft-shafranovich-mime-sql-03
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnXJo5bxor+PY9sw9lb8vVdv6WWU6RmmplmGNA/O0dA3ZznwuwZi4M39tP0S9qaKIdTlmRA
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 03:43:24 -0000

On Tue, Feb 5, 2013 at 9:15 PM, Barry Leiba <barryleiba@computer.org> wrote:
>> The question is what happens when the SQL file itself carries no
>> charset information, such as when using "mysql-dump" with the
>> "--skip-set-charset" option. According to MYSQL, UTF-8 would be used
>> in v5.1+ and ASCII in versions prior to that. Perhaps, we should leave
>> "charset" as an optional parameter for cases like these, and just take
>> out the default value.
>
> That sounds to me like the way to go.  Perhaps a "MUST use" the
> charset parameter when the SQL file carries no charset information,
> "MUST NOT use" otherwise?
>

MUST may be an overkill, especially in cases where the web server has
no way of knowing what the charset is or whether it is present. I
would think that SHOULD USE and SHOULD NOT USE maybe a better
alternative.

Yakov

From ron.even.tlv@gmail.com  Wed Feb  6 00:24:25 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4858A21F8519; Wed,  6 Feb 2013 00:24:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.508
X-Spam-Level: 
X-Spam-Status: No, score=-2.508 tagged_above=-999 required=5 tests=[AWL=1.090,  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 8s1lYFxDA0AQ; Wed,  6 Feb 2013 00:24:24 -0800 (PST)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA87321F84BB; Wed,  6 Feb 2013 00:24:23 -0800 (PST)
Received: by mail-ea0-f172.google.com with SMTP id f13so503194eaa.3 for <multiple recipients>; Wed, 06 Feb 2013 00:24:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=WqNAAcEuHiWtFOLLA5Xr1SspU1xX4g5+u2Tudj3B5Xs=; b=lavP4YRMzaC359LZrl2EdB163JpXd+AkhS4ZJECY4ECTYFGkk1SsJ3C4O9SQRim46M Cmw/GEW4buDgZ22if5FvPIUZqJBh/EsMzCi7hl5NFBnEuB4pyvgfxvQplo4tE+PDm2Zd nO448JMbTw+EF/2Oca54FAgvipJEF99VjrC6aBvOcj6R2L7t/qLtKxSHeeWmqHhKFLPJ vKUxVEjYFiGdSk0sMhRouO7TC3Hcr0Gd+o2kgEgZD2hQeaodm1atIk/EGGsTNRAC0nZu Y4UWOnK4Ax1o47bVbJLF5MdoeFYAKkJPe76b/mtu24LDkZMEG7c9CIxJlt1PTuaoHjp/ FTFw==
X-Received: by 10.14.225.133 with SMTP id z5mr95973865eep.15.1360139063117; Wed, 06 Feb 2013 00:24:23 -0800 (PST)
Received: from RoniE (bzq-79-181-179-229.red.bezeqint.net. [79.181.179.229]) by mx.google.com with ESMTPS id q42sm26226087eem.14.2013.02.06.00.24.20 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 06 Feb 2013 00:24:22 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-harkins-brainpool-ike-groups.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-harkins-brainpool-ike-groups-04
Date: Wed, 6 Feb 2013 10:21:30 +0200
Message-ID: <04d701ce0442$f9a81d20$ecf85760$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04D8_01CE0453.BD318960"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac4EQvd90NNKeCsHSXq8kAsBI8lTsg==
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, 06 Feb 2013 08:24:25 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04D8_01CE0453.BD318960
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-harkins-brainpool-ike-groups-04

Reviewer: Roni Even

Review Date:2013-2-13

IETF LC End Date: 2013-2-28

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

 


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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New","serif"'>draft-harkins-brainpool-ike-groups-04</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;2&#8211;13<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-2&#8211;28<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_04D8_01CE0453.BD318960--


From sm@resistor.net  Wed Feb  6 01:12:55 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DB021F8563 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 01:12:55 -0800 (PST)
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 nTdXBMOIevJ0 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 01:12:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D21E21F84FC for <ietf@ietf.org>; Wed,  6 Feb 2013 01:12:53 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r169CUTf017153; Wed, 6 Feb 2013 01:12:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360141957; bh=2E4TpFJeXKtFDL8OFJbniqGfpDY+CQqlgDKuZgpgbDw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=sw2LyYkZ4+zTMgt08Phw4aidMF/tPT69WmXC/Zk3fCz7tyqL5dlm9iO9rKQkBYueK /U5QItDo5g5syQngwHQOXjn5UH/8gKpL4ChGONayVSjAFL8ewl43d/ZNjNQTBmxJ9Z tXbKAZX9G9/auSRXnXoEw1OAcJW7YOi+2QwxNvMk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360141957; i=@resistor.net; bh=2E4TpFJeXKtFDL8OFJbniqGfpDY+CQqlgDKuZgpgbDw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=b6GV7heI3Jezd3QjQR2yfdVEDru9vlfGDtAXWWZRvmv85aCb4ff9CLFsydNXdkpjK ZZciq+Aj2pCji+MNS/d+PAP4J7xkhZfTYFoa+ZJ5nedondrykjK/BkMxd2C3YJVyjp ESKtCqZGAcp+WHiSmnPHXWpWwAietzA4dkrKOefw=
Message-Id: <6.2.5.6.2.20130206005433.0ab301a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Feb 2013 01:11:13 -0800
To: Eliot Lear <lear@cisco.com>
From: SM <sm@resistor.net>
Subject: Re: History of protocol discussion or process in WG
In-Reply-To: <5110EF35.4090807@cisco.com>
References: <CADnDZ8-mnwBgHXCPXuyhg+abV24Za7Svu67+H1Fg_RJpsSJGHg@mail.gmail.com> <824CBBAF26EC8E428BE32C12F75F93690172AEB1@CH1PRD0810MB395.namprd08.prod.outlook.com> <CADnDZ88u6duHzDSEdupdMAe_agDZQWe2pobf+sVW4m_VqsRVDw@mail.gmail.com> <377EA38E-94AC-46CE-9E95-5ECC5A56A83E@cs.ucla.edu> <tslip69jlqg.fsf@mit.edu> <510EAEB7.9060703@dcrocker.net> <5110EF35.4090807@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: dcrocker@bbiw.net, Abdussalam Baryun <abdussalambaryun@gmail.com>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org, Lixia Zhang <lixia@cs.ucla.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, 06 Feb 2013 09:12:55 -0000

Hi Eliot,
At 03:38 05-02-2013, Eliot Lear wrote:
>What I would like not to have happen is that we spend any time bickering
>over who said what, especially if it detracts from the business of
>developing excellent standards.  I think your point, Dave, about

Yes.

>synthesis being left to historians is a good one, and I might go
>farther, and say that the whole endeavor should be.  But having at least
>a record from individauls about what *they* said or meant is, I suppose,
>not unreasonable.

I post the draft of the minutes to the mailing list.  There have been 
cases where what was meant came out differently in writing.  The 
person suggested text to clarify that.  The working group did not 
object.  The minutes were added to the record (proceedings).

Regards,
-sm 


From derhoermi@gmx.net  Wed Feb  6 03:40:54 2013
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3CC21F89A4 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 03:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOaHzJlNrcYG for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 03:40:53 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEEB21F8999 for <ietf@ietf.org>; Wed,  6 Feb 2013 03:40:53 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.10]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M3xlc-1UtN4g2n4M-00rWZn for <ietf@ietf.org>; Wed, 06 Feb 2013 12:40:52 +0100
Received: (qmail invoked by alias); 06 Feb 2013 11:40:50 -0000
Received: from unknown (EHLO netb) [89.204.154.85] by mail.gmx.net (mp010) with SMTP; 06 Feb 2013 12:40:50 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18Sek17icMSPmx5z8i5gyE2op1p5lkS/ZmAfMuPFW K0PiD4KAI3CRNN
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf@ietf.org
Subject: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
Date: Wed, 06 Feb 2013 12:40:42 +0100
Message-ID: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: draft-eastlake-additional-xmlsec-uris@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, 06 Feb 2013 11:40:54 -0000

Hi,

  In http://www.ietf.org/id/draft-eastlake-additional-xmlsec-uris-08.txt
the References have to be checked and updated. For example, the document
has a normative reference to http://www.w3.org/TR/2002/WD-xptr-20020816/
which is a "Superceded" work-in-progress that's over 10 years old. Also,
it references "RFC Errata, Errata ID 191, RFC 4051" without linking the
errata item, and does so normatively even though the document as a whole
would Obsolete RFC 4051. Just to illustrate, I did not review them all
myself.

The Abstract does not english.

I don't think it's a good idea to have the Acknowledgements precede even
the Introduction as an exception while most other documents put it near
the end.

The "XCANON" reference does not work, "xml-enc-c14n-20020718" is perhaps
meant to be "xml-exc-c14n-20020718" ("enc" vs "exc"). I've not checked
other references.

The document makes reference to Canonical XML 1.0 without referencing,
e.g. http://www.w3.org/TR/C14N-issues/ (and RFC 3076 does not seem to
have any Errata filed to hint at the problems with it). I'm not sure
that's a problem, but it might be better to mention the problems with
Canonical XML 1.0 in some form.

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From spromano@unina.it  Wed Feb  6 06:02:43 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26F1021F858E; Wed,  6 Feb 2013 06:02:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJJKh0Koy6dH; Wed,  6 Feb 2013 06:02:41 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id E1C4C21F848B; Wed,  6 Feb 2013 06:02:37 -0800 (PST)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r16E2YcI006686 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 6 Feb 2013 15:02:35 +0100
Subject: Re: Remote Participation Services
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_973752B9-4A1A-41AF-AFB4-C79F39DD6754"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
Date: Wed, 6 Feb 2013 15:02:33 +0100
Message-Id: <31F19A79-076F-424C-957E-B563F960E549@unina.it>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
To: IAOC <iaoc@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 14:02:43 -0000

--Apple-Mail=_973752B9-4A1A-41AF-AFB4-C79F39DD6754
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

some time ago I proposed an experiment associated with moderation in the =
presence of both remote and local participants (point 2.7 below):

http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project

You can find the related IETF mail announcement here:

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

Just for the logs.

Cheers,

Simon



Il giorno 05/feb/2013, alle ore 17:04, IETF Chair ha scritto:

> Please see the attached report on the current status of remote =
participation in the IETF meeting.  Please notice at the end a call for =
potential experiments to explore ways that we can improve remote =
participation.
>=20
> Russ Housley
> IETF Chair
>=20
> Bob Hinden
> IAOC Chair
>=20
>=20
> =3D =3D =3D =3D =3D =3D =3D =3D =3D=20
>=20
>=20
> Status of Remote Participation Services in the IETF Today
>=20
>                      Russ Housley
>                     1 February 2013
>=20
> 1.  Introduction
>=20
>   For more than a decade, the IETF has tried to make it easier for=20
>   remote attendees to participate in regular and interim face-to-face
>   meetings.  At the same time, some IETF Working Groups (WGs) have
>   started to conduct virtual interim meetings.
>=20
>   The IETF's current remote participation system ("RPS") consists of a
>   outbound real-time audio stream for each session carried to remote
>   attendees over HTTP, textual multi-user chat carried over XMPP
>   (commonly called Jabber), and posting of slides prior to the WG
>   session so that they can be downloaded from the IETF web site.
>=20
>   WebEx and Meetecho are experimentally supported, offering outbound
>   real-time audio stream synchronized to the slides for the remote
>   participant.  Meetecho displays the Jabber Room on the screen with
>   slides, and it can also be used to replay the audio and slides from
>   a recording.
>=20
>   Some WGs also employ ad-hoc tools, such as Skype for two-way audio =
and
>   video conferencing and Etherpad for shared document editing.
>=20
> 2. Regular and Interim IETF Meetings
>=20
>   Today, it is easy to remotely observe IETF sessions, but it is very
>   difficult to participate in discussions.  However, several tools are
>   used to accommodate remote participants.  To the greatest extent
>   possible, these tools rely on IETF or other open standards, and they
>   embrace both IPv4 and IPv6 without network address translation.
>=20
> 2.1. Audio
>=20
>   Anyone can use a web browser to receive real-time audio of the IETF
>   meeting sessions.  The URLs for the audio are announced in advance,
>   and the audio recording becomes part of the session proceedings.
>=20
>   It is quite difficult for a remote participant to have their voice
>   heard in the session.  The WebEx and Meetecho systems can =
accommodate
>   this with advance setup and testing.  However, allowing arbitrary
>   remote participants to speak does not work well.  Connecting to the
>   audio system in the meeting facility is quite problematic.  Further,
>   a WG Chair would need sophisticated controls to maintain order if
>   arbitrary remote participants were able to speak at any time.
>   While WebEx and Meetecho provide some participation management
>   features, but integration with in-room participation is needed.
>=20
> 2.2. Video
>=20
>   In the 1990s as part of the multicast experiment, multicast video =
was
>   made available, but this experiment has ended without evolving into =
a
>   production service.
>=20
>   As part of a separate experiment, some sessions use Meetecho to make
>   video available to anyone with a web browser.  WG Chairs must =
request
>   this coverage.  When Meetecho is used, the URLs are announced in
>   advance, and the recording becomes part of the session proceedings.
>=20
> 2.3. Multi-User Chat
>=20
>   Multi-user chat (MUC) is used both as a remote participation tool as
>   well as a communication tool for local attendees, to raise and =
resolve
>   issues without intruding on the presentation.  Each WG has a Jabber
>   Room for Multi-User Chat, which employs the XMPP Standards =
Foundation
>   (XSF) XEP-045 specification.  These Jabber Rooms can can be used at
>   any time, not just during the IETF meetings.  During the session,
>   remote participants that are listening to the audio are able to ask
>   questions by typing them in the Jabber Room, and then someone in the
>   physical room reads the question at the mic.  This is called
>   MUC-to-Mic Relay.  The Jabber Room log becomes part of the session
>   proceedings.
>=20
> 2.4. Slide Sharing
>=20
>   Anyone can use a web browser to fetch the session slides.  WG Chairs
>   are responsible for posting the slides prior to the session, and the
>   slides (in PDF format) become part of the session proceedings.
>=20
>   When Meetecho is used, the audio or video is presented in a
>   synchronized fashion along with the jabber room and slides.
>=20
> 2.5. Remote Presenter
>=20
>   When a presenter cannot attend, someone else usually presents their
>   slides.  Some WG Chairs have tried remote presentations using WebEx
>   and Meetecho.  Neither system is ideal, and the audio can include
>   squeals and echos.  Both systems require advance setup and testing.
>=20
>   The projection of the remote presenter's face as well as their =
slides
>   seems to improve the experience for the people in the room, but we
>   have only done this successfully a few times.  An extra projector =
and
>   screen are needed for this to work well.
>=20
> 2.6.  Shared Text Document Editing
>=20
>   In some sessions, there is an attempt to edit a text document with
>   input from the local and remote attendees.  This is most often done
>   for minutes and proposed WG charter changes.  Etherpad is the most
>   popular tool for this purpose.  There has been no attempt to
>   standardize the tools or protocols used for this function.
>=20
> 2.7.  Participant Management
>=20
>   A typical meeting discussion takes place by people that want to =
speak
>   forming a line at the microphone, and the presenter replies to each
>   person in turn.  However, sometimes someone will jump the queue to
>   contribute to a particular discussion point.  This mechanism does =
not
>   provide a natural means for including remote participants.  WebEx =
and
>   Meetecho do have a feature for noting a request to speak, but this
>   is not visible to in-room participants.  Hence the burden of =
managing
>   remote participation falls to the WG Chair or their designee.
>=20
> 3. Virtual WG Meeting and Leadership Teleconferences
>=20
>   For a virtual meeting, all participants are remote; there is no
>   physical meeting room.  A virtual WG meeting is usually held to =
tackle
>   a very small number of open issues.  Hence, all of the remote
>   participation tools must be interactive, permitting any participant =
to
>   contribute.  The primary tool for these meetings is WebEx, in a
>   conference-call mode, with no queuing of speakers.  The WG Chair's
>   ability to manage discussion becomes challenging as the size of the
>   virtual meeting grows.
>=20
>   The teleconferences held by bodies like the IESG, IAOC, and IAB are
>   somewhat like an virtual WG meeting, except they are held more often
>   and size of the meeting is constrained.  The fact that all
>   participants know each other facilitates the use of a more informal
>   process than is typically possible for an open virtual WG meeting.
>   Again, all of the participants are remote.
>=20
> 3.1. Audio
>=20
>   For virtual WG meeting, access is open, as for regular IETF =
meetings.
>   For leadership teleconferences, access is limited to those who are
>   invited.  In recent years, WebEx has been used.  WebEx supports
>   telephone dial-in as well as VoIP for the audio, although it may not
>   be totally aligned with the IETF standards in this area.  Skype and
>   similar systems can be used to dial into WebEx.  Sometimes issues =
with
>   an echo take time to resolve, but the quality is generally quite =
good.
>=20
> 3.2. Video
>=20
>   So far, there has been no need for video.  When someone accidentally
>   turns on the WebEx video, they are asked to turn it off so that
>   bandwidth is available for quality audio.
>=20
> 3.3. Multi-User Chat
>=20
>   A jabber room or the WebEx built-in chat is used among the
>   participants.  The scribes often find this useful for capturing
>   accurate minutes.
>=20
> 3.4. Slide Sharing
>=20
>   Slides are often sent by email in advance of the meeting.
>=20
>   WebEx allows the slides and desktop applications to be viewed by the
>   remote participants.  These are controlled by the presenter.  The
>   presenter can be shifted from participant to participant as needed.
>=20
> 3.5. Remote Presenter
>=20
>   WebEx allows the slides to be controlled by the presenter.
>=20
> 3.6.  Shared Text Document Editing
>=20
>   Some scribes use Etherpad for minutes.  This allows participants to
>   review and even correct the minutes as the meeting takes place.
>=20
> 4. Improvements
>=20
>   The IETF has always used the Internet to do its work, and remote
>   participation is no exception.  The IETF wants to improve the tools
>   provided in the RPS tools; a better RPS would allow remote IETF
>   attendees to participate more effectively.
>=20
>   The IETF is seeking improvements that allow remote participants to
>   more naturally contribute to in-room discussion and allow meeting
>   management to integrate local and remote participants into a common
>   queue.
>=20
>   RPS technologies are not yet mature enough to create a production
>   service for the IETF, but these technologies are developing rapidly.
>   The IETF will be conducting more experiments in order to achieve
>   these improvements as early as possible.  To this end, the IAOC is
>   soliciting suggestions for experiments.  If you have suggestions for
>   experiments, please tell the IAOC:
>=20
>      (1)  What hardware and software is needed?
>      (2)  What people resources are needed in the meeting?
>      (3)  What are the expected benefits to the IETF participants?
>=20
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_973752B9-4A1A-41AF-AFB4-C79F39DD6754
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>some time ago I proposed an experiment =
associated with moderation in the presence of both remote and local =
participants (point 2.7 below):</div><div><br></div><div><a =
href=3D"http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project">http://i=
etf83.conf.meetecho.com/index.php/UMPIRE_Project</a></div><div><br></div><=
div>You can find the related IETF mail announcement =
here:</div><div><br></div><div><a =
href=3D"http://www.ietf.org/mail-archive/web/vmeet/current/msg00394.html">=
http://www.ietf.org/mail-archive/web/vmeet/current/msg00394.html</a></div>=
<div><br></div><div>Just for the =
logs.</div><div><br></div><div>Cheers,</div><div><br></div><div>Simon</div=
><div><br></div><div><br></div><div><br><div><div>Il giorno 05/feb/2013, =
alle ore 17:04, IETF Chair ha scritto:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>Please =
see the attached report on the current status of remote participation in =
the IETF meeting. &nbsp;Please notice at the end a call for potential =
experiments to explore ways that we can improve remote =
participation.<br><br>Russ Housley<br>IETF Chair<br><br>Bob =
Hinden<br>IAOC Chair<br><br><br>=3D =3D =3D =3D =3D =3D =3D =3D =3D =
<br><br><br>Status of Remote Participation Services in the IETF =
Today<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Russ Housley<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1 February 2013<br><br>1. =
&nbsp;Introduction<br><br> &nbsp;&nbsp;For more than a decade, the IETF =
has tried to make it easier for <br> &nbsp;&nbsp;remote attendees to =
participate in regular and interim face-to-face<br> =
&nbsp;&nbsp;meetings. &nbsp;At the same time, some IETF Working Groups =
(WGs) have<br> &nbsp;&nbsp;started to conduct virtual interim =
meetings.<br><br> &nbsp;&nbsp;The IETF's current remote participation =
system ("RPS") consists of a<br> &nbsp;&nbsp;outbound real-time audio =
stream for each session carried to remote<br> &nbsp;&nbsp;attendees over =
HTTP, textual multi-user chat carried over XMPP<br> =
&nbsp;&nbsp;(commonly called Jabber), and posting of slides prior to the =
WG<br> &nbsp;&nbsp;session so that they can be downloaded from the IETF =
web site.<br><br> &nbsp;&nbsp;WebEx and Meetecho are experimentally =
supported, offering outbound<br> &nbsp;&nbsp;real-time audio stream =
synchronized to the slides for the remote<br> &nbsp;&nbsp;participant. =
&nbsp;Meetecho displays the Jabber Room on the screen with<br> =
&nbsp;&nbsp;slides, and it can also be used to replay the audio and =
slides from<br> &nbsp;&nbsp;a recording.<br><br> &nbsp;&nbsp;Some WGs =
also employ ad-hoc tools, such as Skype for two-way audio and<br> =
&nbsp;&nbsp;video conferencing and Etherpad for shared document =
editing.<br><br>2. Regular and Interim IETF Meetings<br><br> =
&nbsp;&nbsp;Today, it is easy to remotely observe IETF sessions, but it =
is very<br> &nbsp;&nbsp;difficult to participate in discussions. =
&nbsp;However, several tools are<br> &nbsp;&nbsp;used to accommodate =
remote participants. &nbsp;To the greatest extent<br> =
&nbsp;&nbsp;possible, these tools rely on IETF or other open standards, =
and they<br> &nbsp;&nbsp;embrace both IPv4 and IPv6 without network =
address translation.<br><br>2.1. Audio<br><br> &nbsp;&nbsp;Anyone can =
use a web browser to receive real-time audio of the IETF<br> =
&nbsp;&nbsp;meeting sessions. &nbsp;The URLs for the audio are announced =
in advance,<br> &nbsp;&nbsp;and the audio recording becomes part of the =
session proceedings.<br><br> &nbsp;&nbsp;It is quite difficult for a =
remote participant to have their voice<br> &nbsp;&nbsp;heard in the =
session. &nbsp;The WebEx and Meetecho systems can accommodate<br> =
&nbsp;&nbsp;this with advance setup and testing. &nbsp;However, allowing =
arbitrary<br> &nbsp;&nbsp;remote participants to speak does not work =
well. &nbsp;Connecting to the<br> &nbsp;&nbsp;audio system in the =
meeting facility is quite problematic. &nbsp;Further,<br> &nbsp;&nbsp;a =
WG Chair would need sophisticated controls to maintain order if<br> =
&nbsp;&nbsp;arbitrary remote participants were able to speak at any =
time.<br> &nbsp;&nbsp;While WebEx and Meetecho provide some =
participation management<br> &nbsp;&nbsp;features, but integration with =
in-room participation is needed.<br><br>2.2. Video<br><br> =
&nbsp;&nbsp;In the 1990s as part of the multicast experiment, multicast =
video was<br> &nbsp;&nbsp;made available, but this experiment has ended =
without evolving into a<br> &nbsp;&nbsp;production service.<br><br> =
&nbsp;&nbsp;As part of a separate experiment, some sessions use Meetecho =
to make<br> &nbsp;&nbsp;video available to anyone with a web browser. =
&nbsp;WG Chairs must request<br> &nbsp;&nbsp;this coverage. &nbsp;When =
Meetecho is used, the URLs are announced in<br> &nbsp;&nbsp;advance, and =
the recording becomes part of the session proceedings.<br><br>2.3. =
Multi-User Chat<br><br> &nbsp;&nbsp;Multi-user chat (MUC) is used both =
as a remote participation tool as<br> &nbsp;&nbsp;well as a =
communication tool for local attendees, to raise and resolve<br> =
&nbsp;&nbsp;issues without intruding on the presentation. &nbsp;Each WG =
has a Jabber<br> &nbsp;&nbsp;Room for Multi-User Chat, which employs the =
XMPP Standards Foundation<br> &nbsp;&nbsp;(XSF) XEP-045 specification. =
&nbsp;These Jabber Rooms can can be used at<br> &nbsp;&nbsp;any time, =
not just during the IETF meetings. &nbsp;During the session,<br> =
&nbsp;&nbsp;remote participants that are listening to the audio are able =
to ask<br> &nbsp;&nbsp;questions by typing them in the Jabber Room, and =
then someone in the<br> &nbsp;&nbsp;physical room reads the question at =
the mic. &nbsp;This is called<br> &nbsp;&nbsp;MUC-to-Mic Relay. =
&nbsp;The Jabber Room log becomes part of the session<br> =
&nbsp;&nbsp;proceedings.<br><br>2.4. Slide Sharing<br><br> =
&nbsp;&nbsp;Anyone can use a web browser to fetch the session slides. =
&nbsp;WG Chairs<br> &nbsp;&nbsp;are responsible for posting the slides =
prior to the session, and the<br> &nbsp;&nbsp;slides (in PDF format) =
become part of the session proceedings.<br><br> &nbsp;&nbsp;When =
Meetecho is used, the audio or video is presented in a<br> =
&nbsp;&nbsp;synchronized fashion along with the jabber room and =
slides.<br><br>2.5. Remote Presenter<br><br> &nbsp;&nbsp;When a =
presenter cannot attend, someone else usually presents their<br> =
&nbsp;&nbsp;slides. &nbsp;Some WG Chairs have tried remote presentations =
using WebEx<br> &nbsp;&nbsp;and Meetecho. &nbsp;Neither system is ideal, =
and the audio can include<br> &nbsp;&nbsp;squeals and echos. &nbsp;Both =
systems require advance setup and testing.<br><br> &nbsp;&nbsp;The =
projection of the remote presenter's face as well as their slides<br> =
&nbsp;&nbsp;seems to improve the experience for the people in the room, =
but we<br> &nbsp;&nbsp;have only done this successfully a few times. =
&nbsp;An extra projector and<br> &nbsp;&nbsp;screen are needed for this =
to work well.<br><br>2.6. &nbsp;Shared Text Document Editing<br><br> =
&nbsp;&nbsp;In some sessions, there is an attempt to edit a text =
document with<br> &nbsp;&nbsp;input from the local and remote attendees. =
&nbsp;This is most often done<br> &nbsp;&nbsp;for minutes and proposed =
WG charter changes. &nbsp;Etherpad is the most<br> &nbsp;&nbsp;popular =
tool for this purpose. &nbsp;There has been no attempt to<br> =
&nbsp;&nbsp;standardize the tools or protocols used for this =
function.<br><br>2.7. &nbsp;Participant Management<br><br> &nbsp;&nbsp;A =
typical meeting discussion takes place by people that want to speak<br> =
&nbsp;&nbsp;forming a line at the microphone, and the presenter replies =
to each<br> &nbsp;&nbsp;person in turn. &nbsp;However, sometimes someone =
will jump the queue to<br> &nbsp;&nbsp;contribute to a particular =
discussion point. &nbsp;This mechanism does not<br> &nbsp;&nbsp;provide =
a natural means for including remote participants. &nbsp;WebEx and<br> =
&nbsp;&nbsp;Meetecho do have a feature for noting a request to speak, =
but this<br> &nbsp;&nbsp;is not visible to in-room participants. =
&nbsp;Hence the burden of managing<br> &nbsp;&nbsp;remote participation =
falls to the WG Chair or their designee.<br><br>3. Virtual WG Meeting =
and Leadership Teleconferences<br><br> &nbsp;&nbsp;For a virtual =
meeting, all participants are remote; there is no<br> =
&nbsp;&nbsp;physical meeting room. &nbsp;A virtual WG meeting is usually =
held to tackle<br> &nbsp;&nbsp;a very small number of open issues. =
&nbsp;Hence, all of the remote<br> &nbsp;&nbsp;participation tools must =
be interactive, permitting any participant to<br> =
&nbsp;&nbsp;contribute. &nbsp;The primary tool for these meetings is =
WebEx, in a<br> &nbsp;&nbsp;conference-call mode, with no queuing of =
speakers. &nbsp;The WG Chair's<br> &nbsp;&nbsp;ability to manage =
discussion becomes challenging as the size of the<br> =
&nbsp;&nbsp;virtual meeting grows.<br><br> &nbsp;&nbsp;The =
teleconferences held by bodies like the IESG, IAOC, and IAB are<br> =
&nbsp;&nbsp;somewhat like an virtual WG meeting, except they are held =
more often<br> &nbsp;&nbsp;and size of the meeting is constrained. =
&nbsp;The fact that all<br> &nbsp;&nbsp;participants know each other =
facilitates the use of a more informal<br> &nbsp;&nbsp;process than is =
typically possible for an open virtual WG meeting.<br> =
&nbsp;&nbsp;Again, all of the participants are remote.<br><br>3.1. =
Audio<br><br> &nbsp;&nbsp;For virtual WG meeting, access is open, as for =
regular IETF meetings.<br> &nbsp;&nbsp;For leadership teleconferences, =
access is limited to those who are<br> &nbsp;&nbsp;invited. &nbsp;In =
recent years, WebEx has been used. &nbsp;WebEx supports<br> =
&nbsp;&nbsp;telephone dial-in as well as VoIP for the audio, although it =
may not<br> &nbsp;&nbsp;be totally aligned with the IETF standards in =
this area. &nbsp;Skype and<br> &nbsp;&nbsp;similar systems can be used =
to dial into WebEx. &nbsp;Sometimes issues with<br> &nbsp;&nbsp;an echo =
take time to resolve, but the quality is generally quite =
good.<br><br>3.2. Video<br><br> &nbsp;&nbsp;So far, there has been no =
need for video. &nbsp;When someone accidentally<br> &nbsp;&nbsp;turns on =
the WebEx video, they are asked to turn it off so that<br> =
&nbsp;&nbsp;bandwidth is available for quality audio.<br><br>3.3. =
Multi-User Chat<br><br> &nbsp;&nbsp;A jabber room or the WebEx built-in =
chat is used among the<br> &nbsp;&nbsp;participants. &nbsp;The scribes =
often find this useful for capturing<br> &nbsp;&nbsp;accurate =
minutes.<br><br>3.4. Slide Sharing<br><br> &nbsp;&nbsp;Slides are often =
sent by email in advance of the meeting.<br><br> &nbsp;&nbsp;WebEx =
allows the slides and desktop applications to be viewed by the<br> =
&nbsp;&nbsp;remote participants. &nbsp;These are controlled by the =
presenter. &nbsp;The<br> &nbsp;&nbsp;presenter can be shifted from =
participant to participant as needed.<br><br>3.5. Remote =
Presenter<br><br> &nbsp;&nbsp;WebEx allows the slides to be controlled =
by the presenter.<br><br>3.6. &nbsp;Shared Text Document Editing<br><br> =
&nbsp;&nbsp;Some scribes use Etherpad for minutes. &nbsp;This allows =
participants to<br> &nbsp;&nbsp;review and even correct the minutes as =
the meeting takes place.<br><br>4. Improvements<br><br> &nbsp;&nbsp;The =
IETF has always used the Internet to do its work, and remote<br> =
&nbsp;&nbsp;participation is no exception. &nbsp;The IETF wants to =
improve the tools<br> &nbsp;&nbsp;provided in the RPS tools; a better =
RPS would allow remote IETF<br> &nbsp;&nbsp;attendees to participate =
more effectively.<br><br> &nbsp;&nbsp;The IETF is seeking improvements =
that allow remote participants to<br> &nbsp;&nbsp;more naturally =
contribute to in-room discussion and allow meeting<br> =
&nbsp;&nbsp;management to integrate local and remote participants into a =
common<br> &nbsp;&nbsp;queue.<br><br> &nbsp;&nbsp;RPS technologies are =
not yet mature enough to create a production<br> &nbsp;&nbsp;service for =
the IETF, but these technologies are developing rapidly.<br> =
&nbsp;&nbsp;The IETF will be conducting more experiments in order to =
achieve<br> &nbsp;&nbsp;these improvements as early as possible. =
&nbsp;To this end, the IAOC is<br> &nbsp;&nbsp;soliciting suggestions =
for experiments. &nbsp;If you have suggestions for<br> =
&nbsp;&nbsp;experiments, please tell the IAOC:<br><br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(1) &nbsp;What hardware and software is =
needed?<br> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(2) &nbsp;What people =
resources are needed in the meeting?<br> =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(3) &nbsp;What are the expected benefits =
to the IETF participants?<br><br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_973752B9-4A1A-41AF-AFB4-C79F39DD6754--

From mcr@sandelman.ca  Wed Feb  6 07:58:26 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E16C21F897A for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 07:58:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 z8O2qcTIvkUh for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 07:58:25 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 66CA721F85CB for <ietf@ietf.org>; Wed,  6 Feb 2013 07:58:25 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id B17F52016D for <ietf@ietf.org>; Wed,  6 Feb 2013 11:04:18 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E4A6263769; Wed,  6 Feb 2013 10:57:20 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D38DB636C5 for <ietf@ietf.org>; Wed,  6 Feb 2013 10:57:20 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Remote Participation Services
In-Reply-To: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 06 Feb 2013 10:57:20 -0500
Message-ID: <10047.1360166240@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 15:58:26 -0000

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


For the question at the end, I'd like to suggest that making an effort
to normalize some of the use of the tools that we have would be most
helpful.   It's not just a technology problem.

>>>>> "IETF" =3D=3D IETF Chair <chair@ietf.org> writes:
    IETF> 2.4. Slide Sharing

    IETF>    Anyone can use a web browser to fetch the session slides.
    IETF> WG Chairs are responsible for posting the slides prior to the
    IETF> session, and the slides (in PDF format) become part of the
    IETF> session proceedings.

Slides are regularly late, and regularly not in PDF format.
They get updated at the last minute, so slide numbers fail.
I think that this presents too rosy a picture of getting slides.

    IETF> 2.6.  Shared Text Document Editing

    IETF>    In some sessions, there is an attempt to edit a text
    IETF> document with input from the local and remote attendees.  This
    IETF> is most often done for minutes and proposed WG charter

I wish we would do this more often, particularly for "HUMs"

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



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

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

iQCVAwUAURJ9YIqHRg3pndX9AQKkGgP9GIOs+MZHygQrVaajqFtCWh73vVChG6oG
9vL6gecVWUcqHEZnFIuDzfqPGF1oQt6f/Efakpo4UVP4Pgie3CTpbZYK8652Y1hJ
P1Bitb67Az5sOo7J3dkWqNZdwU48igdyf6rTwDn2k63fIXt2CTMSLmXqL/jQSDOW
DAL29sPGFT4=
=ZJzm
-----END PGP SIGNATURE-----
--=-=-=--

From huawei.danli@huawei.com  Mon Feb  4 19:05:45 2013
Return-Path: <huawei.danli@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 AF43C21F88EA; Mon,  4 Feb 2013 19:05:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.732
X-Spam-Level: *
X-Spam-Status: No, score=1.732 tagged_above=-999 required=5 tests=[AWL=-1.056,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339,  MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5gHeUWnxkkO; Mon,  4 Feb 2013 19:05:45 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id ACD2821F88E8; Mon,  4 Feb 2013 19:05:43 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APK98078; Tue, 05 Feb 2013 03:05:42 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 03:04:43 +0000
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 5 Feb 2013 03:05:38 +0000
Received: from szxeml555-mbx.china.huawei.com ([169.254.1.229]) by szxeml403-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.007; Tue, 5 Feb 2013 11:05:35 +0800
From: "Lidan (Dan)" <huawei.danli@huawei.com>
To: Richard Barnes <rbarnes@bbn.com>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Subject: =?gb2312?B?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAt?= =?gb2312?Q?behavior-negotiation-10?=
Thread-Topic: Gen-ART review of draft-ietf-ccamp-lmp-behavior-negotiation-10
Thread-Index: AQHOAkKfFPU9gjEKO0O3gq+ZfCNfU5hqkSYw
Date: Tue, 5 Feb 2013 03:05:34 +0000
Message-ID: <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
In-Reply-To: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.73.151]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 06 Feb 2013 08:42:02 -0800
Cc: "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 03:05:45 -0000

SGkgUmljaGFyZCwNCg0KVGhhbmtzIGZvciB0aGUgcmV2aWV3IG9mIHRoaXMgZHJhZnQhDQoNCj4g
U2VjdGlvbiAyLjEuICBXb3VsZCBiZSBoZWxwZnVsIHRvIGVpdGhlciBpbmNsdWRlIHRoZSBvbGQg
Zm9ybWF0cyBhbmQvb3Igc2F5IGV4cGxpY2l0bHkgd2hhdCBpcyBjaGFuZ2luZy4NCkFkZGVkIHRo
ZSBvcmlnaW5hbCBmb3JtYXQgb2YgQ29uZmlnLCBDb25maWdBY2sgYW5kIENvbmZpZ05hY2sgbWVz
c2FnZXMgd2hpY2ggYXJlIGRlZmluZWQgaW4gUkZDNDIwNC4NCg0KPiBTZWN0aW9uIDIuMi4gIA0K
PiAiTm9kZXMgd2hpY2ggc3VwcG9ydCIgLT4gIm5vZGVzIHRoYXQgc3VwcG9ydCIgIA0KPiAiT3Jk
ZXJpbmcgb2YgQ09ORklHIG9iamVjdHMiIC0+ICIuLi4gV2l0aCBkaWZmZXJlbnQgQy10eXBlIHZh
bHVlcyINClVwZGF0ZWQgdGhlIHRleHQgYXMgc3VnZ2VzdGVkLg0KDQo+IFNlY3Rpb24gMy4xLk1C
Wi4gTWlnaHQgaGVscCB0byBjbGFyaWZ5IHRoYXQgdGhpcyBtZWFucyB0aGF0IHRoZSBudW1iZXIg
b2YgYml0cyBNVVNUIGJlIGEgbXVsdGlwbGUgb2YgMzIuIChJIGdvdCBhIGxpdHRsZSBjb25mdXNl
ZCBiZXR3ZWVuIGJpdHMgYW5kIGJ5dGVzIGhlcmUuKQ0KT0xEOg0KVGhlIHJlbWFpbmluZyBiaXRz
IGluIHRoZSBmbGFncyBmaWVsZCBNVVNUIGJlIHNldCB0byB6ZXJvICgwKS4gVGhlIG51bWJlciBv
ZiBiaXRzIHByZXNlbnQgaXMgYmFzZWQgb24gdGhlIExlbmd0aCBmaWVsZCBvZiB0aGUgTE1QIG9i
amVjdCBoZWFkZXIgYW5kIE1VU1QgaW5jbHVkZSBlbm91Z2ggYml0cyBzbyB0aGUgTGVuZ3RoIGZp
ZWxkIE1VU1QgYmUgYXQgbGVhc3QgOCwgYW5kIE1VU1QgYmUgYSBtdWx0aXBsZSBvZiA0Lg0KTkVX
Og0KVGhlIHJlbWFpbmluZyBiaXRzIGluIHRoZSBmbGFncyBmaWVsZCBNVVNUIGJlIHNldCB0byB6
ZXJvICgwKS4gVGhlIG51bWJlciBvZiBiaXRzIHByZXNlbnQgaXMgYmFzZWQgb24gdGhlIExlbmd0
aCBmaWVsZCBvZiB0aGUgTE1QIG9iamVjdCBoZWFkZXIgYW5kIE1VU1QgaW5jbHVkZSBlbm91Z2gg
Yml0cyBzbyB0aGUgTGVuZ3RoIGZpZWxkIE1VU1QgYmUgYXQgbGVhc3QgOCwgYW5kIHRoZSBudW1i
ZXIgb2YgYml0cyBNVVNUIGJlIGEgbXVsdGlwbGUgb2YgMzIuDQoNCj4gU2VjdGlvbiA0LiAiTGlr
ZWx5Ig0KPiBJcyBpdCBwb3NzaWJsZSBmb3IgYSA0MjA0LWNvbXBsaWFudCBpbXBsZW1lbnRhdGlv
biB0byBub3QgZG8gb25lIG9mIHRoZXNlPyAgSWYgc28gdGhlbiByZW1vdmUgImxpa2VseSIuICBJ
ZiBub3QsIHRoZW4gd2h5IGhhcHBlbnMgb24gdGhlIGV4Y2VwdGlvbmFsIGNhc2U/DQpUaGVyZSBp
cyBubyBvdGhlciBleGNlcHRpb24sIHNvIEkganVzdCByZW1vdmVkIHRoZSB3b3JkICJsaWtlbHki
Lg0KDQpJIHdpbGwgaG9sZCB0aGUgbmV3IHZlcnNpb24gdW50aWwgSSBnZXQgdGhlIGZ1cnRoZXIg
aW5zdHJ1Y3Rpb24gZnJvbSBteSBkb2N1bWVudCBzaGVwaGVyZCBvciBBRC4NCg0KQmVzdCByZWdh
cmRzLA0KDQpEYW4NCg0KDQotLS0tLdPKvP7Urbz+LS0tLS0NCreivP7IyzogUmljaGFyZCBCYXJu
ZXMgW21haWx0bzpyYmFybmVzQGJibi5jb21dIA0Kt6LLzcqxvOQ6IDIwMTPE6jLUwjTI1SAzOjE0
DQrK1bz+yMs6IGlldGZAaWV0Zi5vcmc7IFRoZSBJRVNHDQqzrcvNOiBkcmFmdC1pZXRmLWNjYW1w
LWxtcC1iZWhhdmlvci1uZWdvdGlhdGlvbkB0b29scy5pZXRmLm9yZzsgZ2VuLWFydEBpZXRmLm9y
Zw0K1vfM4jogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAtYmVoYXZpb3It
bmVnb3RpYXRpb24tMTANCg0KSSBoYXZlIGJlZW4gc2VsZWN0ZWQgYXMgdGhlIEdlbmVyYWwgQXJl
YSBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQgKGZvciBiYWNr
Z3JvdW5kIG9uIEdlbi1BUlQsIHBsZWFzZSBzZWVodHRwOi8vd3d3LmFsdmVzdHJhbmQubm8vaWV0
Zi9nZW4vYXJ0L2dlbi1hcnQtRkFRLmh0bWwpLg0KDQpQbGVhc2Ugd2FpdCBmb3IgZGlyZWN0aW9u
IGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZCBvciBBRCBiZWZvcmUgcG9zdGluZyBhIG5ldyB2
ZXJzaW9uIG9mIHRoZSBkcmFmdC4NCg0KRG9jdW1lbnQ6IGRyYWZ0LWlldGYtY2NhbXAtbG1wLWJl
aGF2aW9yLW5lZ290aWF0aW9uLTEwDQpSZXZpZXdlcjogUmljaGFyZCBCYXJuZXMNClJldmlldyBE
YXRlOiAyMDEzLTAyLTAyDQpJRVRGIExDIEVuZCBEYXRlOiAyMDEyLTAxLTIxDQpJRVNHIFRlbGVj
aGF0IGRhdGU6IDIwMTItMDItMDcNCg0KU3VtbWFyeTogIFJlYWR5LCB3aXRoIGEgY291cGxlIG9m
IG1pbm9yIHF1ZXN0aW9ucyAvIGNsYXJpZmljYXRpb25zLg0KDQpDb21tZW50Og0KDQpPdmVyYWxs
LCB0aGlzIGRvY3VtZW50IHNlZW1zIHZlcnkgY2xlYXIgYW5kIHJlYWRhYmxlLiAgVGhhbmtzISAg
VGhlIG9uZSBjb25jZXJuIEkgaGF2ZSBpcyBvdmVyIHRoZSB1c2Ugb2YgImxpa2VseSIgaW4gdGhl
IGRpc2N1c3Npb24gb2YgYmFja3dhcmQgY29tcGF0aWJpbGl0eTsgSSB3b3VsZCBsaWtlIHRvIHNl
ZSBtb3JlIHByZWNpc2UgbGFuZ3VhZ2UgdGhlcmUuDQoNClNlY3Rpb24gMi4xLiAgV291bGQgYmUg
aGVscGZ1bCB0byBlaXRoZXIgaW5jbHVkZSB0aGUgb2xkIGZvcm1hdHMgYW5kL29yIHNheSBleHBs
aWNpdGx5IHdoYXQgaXMgY2hhbmdpbmcuIA0KDQpTZWN0aW9uIDIuMi4gIA0KIk5vZGVzIHdoaWNo
IHN1cHBvcnQiIC0+ICJub2RlcyB0aGF0IHN1cHBvcnQiICANCiJPcmRlcmluZyBvZiBDT05GSUcg
b2JqZWN0cyIgLT4gIi4uLiBXaXRoIGRpZmZlcmVudCBDLXR5cGUgdmFsdWVzIg0KDQpTZWN0aW9u
IDMuMS5NQlouIE1pZ2h0IGhlbHAgdG8gY2xhcmlmeSB0aGF0IHRoaXMgbWVhbnMgdGhhdCB0aGUg
bnVtYmVyIG9mIGJpdHMgTVVTVCBiZSBhIG11bHRpcGxlIG9mIDMyLiAoSSBnb3QgYSBsaXR0bGUg
Y29uZnVzZWQgYmV0d2VlbiBiaXRzIGFuZCBieXRlcyBoZXJlLikNCg0KU2VjdGlvbiA0LiAiTGlr
ZWx5Ig0KSXMgaXQgcG9zc2libGUgZm9yIGEgNDIwNC1jb21wbGlhbnQgaW1wbGVtZW50YXRpb24g
dG8gbm90IGRvIG9uZSBvZiB0aGVzZT8gIElmIHNvIHRoZW4gcmVtb3ZlICJsaWtlbHkiLiAgSWYg
bm90LCB0aGVuIHdoeSBoYXBwZW5zIG9uIHRoZSBleGNlcHRpb25hbCBjYXNlPw0K

From david.black@emc.com  Tue Feb  5 11:34:41 2013
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E484E21F8651; Tue,  5 Feb 2013 11:34:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLfQ4VOTfmAb; Tue,  5 Feb 2013 11:34:41 -0800 (PST)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7868C21F85DB; Tue,  5 Feb 2013 11:34:39 -0800 (PST)
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 r15JYbrA032541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Feb 2013 14:34:37 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd05.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 5 Feb 2013 14:34:23 -0500
Received: from mxhub27.corp.emc.com (mxhub27.corp.emc.com [10.254.110.183]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id r15JYNou021000; Tue, 5 Feb 2013 14:34:23 -0500
Received: from mx15a.corp.emc.com ([169.254.1.210]) by mxhub27.corp.emc.com ([10.254.110.183]) with mapi; Tue, 5 Feb 2013 14:34:23 -0500
From: "Black, David" <david.black@emc.com>
To: "Black, David" <david.black@emc.com>, "dinmohan@hotmail.com" <dinmohan@hotmail.com>, "nabil.n.bitar@verizon.com" <nabil.n.bitar@verizon.com>, "sajassi@cisco.com" <sajassi@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Tue, 5 Feb 2013 14:34:22 -0500
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-07
Thread-Topic: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-07
Thread-Index: Ac1/QFqQF9gPSsZLRYeNSY3JGwq32iElzE2w
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7128800E87E@MX15A.corp.emc.com>
References: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
In-Reply-To: <7EB1738E-2545-4A33-B5C0-548630347568@mimectl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_"
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Wed, 06 Feb 2013 08:41:59 -0800
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Feb 2013 19:34:42 -0000

--_000_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The -07 version of this draft addresses all of the nits noted in the Gen-AR=
T
review of the -06 version.

This draft is ready for publication as a Proposed Standard RFC.

Thanks,
--David

From: Black, David
Sent: Monday, August 20, 2012 9:58 PM
To: dinmohan@hotmail.com; nabil.n.bitar@verizon.com; sajassi@cisco.com; gen=
-art@ietf.org
Cc: Black, David; pwe3@ietf.org; ietf@ietf.org
Subject: Gen-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06

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/GenArtfaq>.

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

Document: draft-ietf-pwe3-mpls-eth-oam-iwk-06
Reviewer: David L. Black
Review Date: August 20, 2012
IETF LC End Date: August 20, 2012

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



This draft covers defect behavior for Ethernet pseudowires,

including defect state mapping and PE defect reporting behavior.

The draft is generally in good shape.  I found a few minor nits.



1) The draft uses a lot of acronyms - while each acronym appears to

be expanded on first use, an additional section near the start of the

draft listing all of them would be helpful.



2) There's a typo in the first paragraph of section 2:



     covers the following Ethernet OAM (Opertaions, Administration and



Opertaions -> Operations.



3) The following normative reference is incomplete - please add additional

information that will enable a reader to locate the referenced document:



     [MEF16] "Ethernet Local Management Interface", MEF16, January 2006.



4) idnits 2.12.13 did not like the pagination:



  =3D=3D The page length should not exceed 58 lines per page, but there was=
 22
     longer pages, the longest (page 1) being 61 lines

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<mailto:david.black@emc.com>        Mobile: +1 (978) 394=
-7754
----------------------------------------------------

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:black;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>The -07 version of t=
his draft addresses all of the nits noted in the Gen-ART<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courie=
r New";color:black'>review of the -06 version.<o:p></o:p></span></p><p clas=
s=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";col=
or:black'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New";color:black'>This draft is ready =
for publication as a Proposed Standard RFC.<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'><o:p>&nbsp;</o:p></span></p><div><div><p class=3DMsoNormal><span s=
tyle=3D'font-size:10.0pt;font-family:"Courier New";color:black'>Thanks,<br>=
--David</span><span style=3D'font-size:11.0pt;font-family:"Courier New";col=
or:black'><o:p></o:p></span></p></div></div><p class=3DMsoNormal><span styl=
e=3D'font-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o=
:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;paddin=
g:0in 0in 0in 4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4D=
F 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'f=
ont-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span st=
yle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Black, David <b=
r><b>Sent:</b> Monday, August 20, 2012 9:58 PM<br><b>To:</b> dinmohan@hotma=
il.com; nabil.n.bitar@verizon.com; sajassi@cisco.com; gen-art@ietf.org<br><=
b>Cc:</b> Black, David; pwe3@ietf.org; ietf@ietf.org<br><b>Subject:</b> Gen=
-ART review of draft-ietf-pwe3-mpls-eth-oam-iwk-06<o:p></o:p></span></p></d=
iv></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNorma=
l><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>I =
am the assigned Gen-ART reviewer for this draft. For background on Gen-ART,=
 please<br>see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please resolve these comments along w=
ith any other Last Call comments you may receive.<br><br>Document: </span><=
span lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:bl=
ack'>draft-ietf-pwe3-mpls-eth-oam-iwk-06</span><o:p></o:p></p></div><div><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
";color:black'>Reviewer: David L. Black<br>Review Date: August 20, 2012<br>=
IETF LC End Date: August 20, 2012<br><br>Summary:<br>This draft is basicall=
y ready for publication, but has nits that<br>should be fixed before public=
ation.</span><o:p></o:p></p></div><p>&nbsp;<o:p></o:p></p><p><span style=3D=
'font-size:10.0pt;font-family:"Courier New";color:black'>This draft covers =
defect behavior for Ethernet pseudowires,</span><o:p></o:p></p><p><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>including def=
ect state mapping and PE defect reporting behavior.</span><o:p></o:p></p><p=
><span style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>The=
 draft is generally in good shape.&nbsp; I found a few minor nits.</span><o=
:p></o:p></p><p>&nbsp;<o:p></o:p></p><p><span style=3D'font-size:10.0pt;fon=
t-family:"Courier New"'>1) The draft uses a lot of acronyms - while each ac=
ronym appears to</span><o:p></o:p></p><p><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New"'>be expanded on first use, an additional section ne=
ar the start of the</span><o:p></o:p></p><p><span style=3D'font-size:10.0pt=
;font-family:"Courier New"'>draft listing all of them would be helpful.</sp=
an><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><p><span style=3D'font-size:10.0p=
t;font-family:"Courier New"'>2) There's&nbsp;a typo in the first paragraph =
of section 2:</span><o:p></o:p></p><p>&nbsp;<o:p></o:p></p><div><p><span la=
ng=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&n=
bsp;&nbsp;&nbsp; &nbsp;covers the following Ethernet OAM (Opertaions, Admin=
istration and </span><span lang=3DEN style=3D'font-size:10.0pt;color:black'=
><o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;color:b=
lack'>&nbsp;<o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.=
0pt;font-family:"Courier New";color:black'>Opertaions&nbsp;-&gt; Operations=
.</span><span lang=3DEN style=3D'font-size:10.0pt;color:black'><o:p></o:p><=
/span></p><p><span lang=3DEN style=3D'font-size:10.0pt;color:black'>&nbsp;<=
o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-fami=
ly:"Courier New";color:black'>3) The following normative reference is incom=
plete - please add additional</span><span lang=3DEN style=3D'font-size:10.0=
pt;color:black'><o:p></o:p></span></p><p><span lang=3DEN style=3D'font-size=
:10.0pt;font-family:"Courier New";color:black'>information that will enable=
 a reader to locate the referenced document:</span><span lang=3DEN style=3D=
'font-size:10.0pt;color:black'><o:p></o:p></span></p><p><span lang=3DEN sty=
le=3D'font-size:10.0pt;color:black'>&nbsp;<o:p></o:p></span></p><p><span la=
ng=3DEN style=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&n=
bsp;&nbsp;&nbsp; &nbsp;[MEF16] &quot;Ethernet Local Management Interface&qu=
ot;, MEF16, January 2006.<o:p></o:p></span></p><p><span lang=3DEN style=3D'=
font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp;<o:p></o:p></=
span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>4)&nbsp;idnits 2.12.13 did not like the pagination:<o:p><=
/o:p></span></p><p><span lang=3DEN style=3D'font-size:10.0pt;font-family:"C=
ourier New";color:black'>&nbsp;<o:p></o:p></span></p><p><span lang=3DEN sty=
le=3D'font-size:10.0pt;font-family:"Courier New";color:black'>&nbsp; =3D=3D=
 The page length should not exceed 58 lines per page, but there was 22<br>&=
nbsp;&nbsp;&nbsp;&nbsp; longer pages, the longest (page 1) being 61 lines</=
span><span style=3D'color:black'><o:p></o:p></span></p></div><div><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Courier New"'>Thanks,</span><o:p></o=
:p></p></div><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font=
-family:"Courier New"'>--David</span><o:p></o:p></p></div><div><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"'>-------=
---------------------------------------------<br>David L. Black, Distinguis=
hed Engineer<br>EMC Corporation, 176 South St., Hopkinton, MA&nbsp; 01748<b=
r>+1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; FAX: +1 (508) 293-7786<br><a href=3D"mailto:david.black@em=
c.com" target=3D"_blank">david.black@emc.com</a>&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Mobile: +1 (978) 394-7754<br>------------------------------=
----------------------</span><span style=3D'font-family:"Courier New"'><o:p=
></o:p></span></p></div></div></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE7128800E87EMX15Acorpemccom_--

From huawei.danli@huawei.com  Tue Feb  5 16:52:26 2013
Return-Path: <huawei.danli@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 8522221F85D2; Tue,  5 Feb 2013 16:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.092
X-Spam-Level: *
X-Spam-Status: No, score=1.092 tagged_above=-999 required=5 tests=[AWL=-1.358,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pVzy2ghkhyP; Tue,  5 Feb 2013 16:52:25 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5650A21F8596; Tue,  5 Feb 2013 16:52:23 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AOE80256; Wed, 06 Feb 2013 00:52:21 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 00:51:22 +0000
Received: from SZXEML406-HUB.china.huawei.com (10.82.67.93) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.1.323.7; Wed, 6 Feb 2013 00:52:20 +0000
Received: from szxeml555-mbx.china.huawei.com ([169.254.1.229]) by szxeml406-hub.china.huawei.com ([10.82.67.93]) with mapi id 14.01.0323.007; Wed, 6 Feb 2013 08:52:15 +0800
From: "Lidan (Dan)" <huawei.danli@huawei.com>
To: Richard Barnes <rlb@ipv.sx>, Lou Berger <lberger@labn.net>
Subject: =?gb2312?B?tPC4tDogtPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft?= =?gb2312?Q?p-lmp-behavior-negotiation-10?=
Thread-Topic: =?gb2312?B?tPC4tDogR2VuLUFSVCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1sbXAt?= =?gb2312?Q?behavior-negotiation-10?=
Thread-Index: AQHOAkKfFPU9gjEKO0O3gq+ZfCNfU5hqkSYwgAA9MICAAAxwAIABKJCg
Date: Wed, 6 Feb 2013 00:52:14 +0000
Message-ID: <92A1F6CF27D54D4DA5364E59D892A02A38851F2B@szxeml555-mbx.china.huawei.com>
References: <543BED18-B326-4649-A35C-0BFB2FAA2E35@bbn.com> <92A1F6CF27D54D4DA5364E59D892A02A388518AA@szxeml555-mbx.china.huawei.com> <51111613.7070300@labn.net> <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
In-Reply-To: <CAL02cgTosa9Y1R4UOyPXZAwOZ_X7KRrDEdJ3p98uGD3XHKaYsw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.73.151]
Content-Type: multipart/alternative; boundary="_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 06 Feb 2013 08:42:02 -0800
Cc: The IESG <iesg@ietf.org>, Richard Barnes <rbarnes@bbn.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-ccamp-lmp-behavior-negotiation@tools.ietf.org" <draft-ietf-ccamp-lmp-behavior-negotiation@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, 06 Feb 2013 00:52:26 -0000

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64

T2ssIHRoZSBvbGQgZm9ybWF0cyBvZiBDb25maWcvQ29uZmlnQWNrL0NvbmZpZ05hY2sgYXJlIG5v
dCBuZWNlc3NhcnkgdG8gYmUgcmVwZWF0ZWQgaW4gdGhpcyBkcmFmdC4gSSB3aWxsIGNsZWFuIHRo
ZSB0ZXh0Lg0KDQpUaGFua3MsDQoNCkRhbg0KDQoNCreivP7IyzogUmljaGFyZCBCYXJuZXMgW21h
aWx0bzpybGJAaXB2LnN4XQ0Kt6LLzcqxvOQ6IDIwMTPE6jLUwjXI1SAyMzowOQ0KytW8/sjLOiBM
b3UgQmVyZ2VyDQqzrcvNOiBMaWRhbiAoRGFuKTsgUmljaGFyZCBCYXJuZXM7IGRyYWZ0LWlldGYt
Y2NhbXAtbG1wLWJlaGF2aW9yLW5lZ290aWF0aW9uQHRvb2xzLmlldGYub3JnOyBnZW4tYXJ0QGll
dGYub3JnOyBpZXRmQGlldGYub3JnOyBUaGUgSUVTRw0K1vfM4jogUmU6ILTwuLQ6IEdlbi1BUlQg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtbG1wLWJlaGF2aW9yLW5lZ290aWF0aW9uLTEwDQoN
CkhleSBMb3UsDQoNClRoYXQgdGV4dCBsb29rcyBmaW5lIHRvIG1lIQ0KDQotLVJpY2hhcmQNCg0K
T24gVHVlLCBGZWIgNSwgMjAxMyBhdCA5OjI0IEFNLCBMb3UgQmVyZ2VyIDxsYmVyZ2VyQGxhYm4u
bmV0PG1haWx0bzpsYmVyZ2VyQGxhYm4ubmV0Pj4gd3JvdGU6DQpEYW4vUmljaGFyZCwNCg0KDQpP
biAyLzQvMjAxMyAxMDowNSBQTSwgTGlkYW4gKERhbikgd3JvdGU6DQo+IEhpIFJpY2hhcmQsDQo+
DQo+IFRoYW5rcyBmb3IgdGhlIHJldmlldyBvZiB0aGlzIGRyYWZ0IQ0KPg0KPj4gU2VjdGlvbiAy
LjEuICBXb3VsZCBiZSBoZWxwZnVsIHRvIGVpdGhlciBpbmNsdWRlIHRoZSBvbGQgZm9ybWF0cw0K
Pj4gYW5kL29yIHNheSBleHBsaWNpdGx5IHdoYXQgaXMgY2hhbmdpbmcuDQoNCj4gQWRkZWQgdGhl
IG9yaWdpbmFsIGZvcm1hdCBvZiBDb25maWcsIENvbmZpZ0FjayBhbmQgQ29uZmlnTmFjaw0KPiBt
ZXNzYWdlcyB3aGljaCBhcmUgZGVmaW5lZCBpbiBSRkM0MjA0Lg0KPg0KSSBwZXJzb25hbGx5IHRo
aW5rIGl0J3MgYSBtaXN0YWtlIHRvIHJlcGVhdCBkZWZpbml0aW9ucyBpbiBub24tYmlzIFJGQ3Mu
DQogSSB0aGluayB0aGlzIGluY3JlYXNlcyB0aGUgcG9zc2liaWxpdHkgb2YgbWlzdGFrZXMgYW5k
IGNvbmZ1c2lvbiAoZS5nLiwNCndoZW4gdGhlIHRleHQgaXNuJ3QgY29waWVkIHByb3Blcmx5IG9y
IHdoZW4gdGhlIG9yaWdpbmFsIGRvY3VtZW50IGlzDQpyZXBsYWNlZCkuDQoNCk15IG9yaWdpbmFs
IHRob3VnaHQgd2FzIHRvIHByb3Bvc2UgdGV4dCB0byBmb2xsb3cgUmljaGFyZCdzIHN1Z2dlc3Rp
b24NCm9mIGV4cGxpY2l0bHkgc2F5aW5nIHdoYXQgaGFzIGNoYW5nZWQsIGJ1dCBJIHNlZSBzdWNo
IHRleHQgaXMgdGhlcmUgYXQNCnRoZSBzdGFydCBvZiBzZWN0aW9uIDI6DQoNCiAgIExNUCBDb25m
aWcsIENvbmZpZ05hY2sgYW5kIENvbmZpZ0FjayBtZXNzYWdlcyBhcmUgbW9kaWZpZWQgYnkgdGhp
cw0KICAgZG9jdW1lbnQgdG8gYWxsb3cgZm9yIHRoZSBpbmNsdXNpb24gb2YgbXVsdGlwbGUgQ09O
RklHIG9iamVjdHMuIFRoZQ0KICAgQ29uZmlnIGFuZCBDb25maWdOYWNrIG1lc3NhZ2VzIHdlcmUg
b25seSBkZWZpbmVkIHRvIGNhcnJ5IG9uZSBDT05GSUcNCiAgIG9iamVjdCBpbiBbUkZDNDIwNF0u
IFRoZSBDb25maWdBY2sgbWVzc2FnZSwgd2hpY2ggd2FzIGRlZmluZWQNCiAgIHdpdGhvdXQgY2Fy
cnlpbmcgYW55IENPTkZJRyBvYmplY3RzIGluIFtSRkM0MjA0XSwgaXMgbW9kaWZpZWQgdG8NCiAg
IGVuYWJsZSBleHBsaWNpdCBpZGVudGlmaWNhdGlvbiBvZiBuZWdvdGlhdGVkIGNvbmZpZ3VyYXRp
b24NCiAgIHBhcmFtZXRlcnMuIFRoZSBpbmNsdXNpb24gb2YgQ09ORklHIG9iamVjdHMgaW4gQ29u
ZmlnQWNrIG1lc3NhZ2VzIGlzDQogICB0cmlnZ2VyZWQgYnkgdGhlIHVzZSBvZiB0aGUgQmVoYXZp
b3JDb25maWcgb2JqZWN0IChkZWZpbmVkIGJlbG93KSBpbg0KICAgYSByZWNlaXZlZCBDb25maWcg
bWVzc2FnZS4NCg0KUmljaGFyZCwNCg0KSXMgdGhpcyB0ZXh0IHN1ZmZpY2llbnQ/ICBBbHRlcm5h
dGl2ZWx5LCB0aGlzIHRleHQgY2FuIGJlIG1vdmVkIHRvDQppbW1lZGlhdGVseSBwcm9jZWVkIHRo
ZSBCTkYuDQoNCk11Y2ggdGhhbmtzDQpMb3UNCihkb2N1bWVudCBjby1hdXRob3IpDQoNCg==

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_
Content-Type: text/html; charset="gb2312"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dgb2312">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:=CB=CE=CC=E5;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@=CB=CE=CC=E5";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:=CB=CE=CC=E5;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"ZH-CN" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ok, the ol=
d formats of Config/ConfigAck/ConfigNack are not necessary to be repeated i=
n this draft. I will clean the text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks,<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Dan<o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:10.5pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt">=B7=A2=BC=FE=C8=
=CB<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"fo=
nt-size:10.0pt"> Richard Barnes [mailto:rlb@ipv.sx]
<br>
</span><b><span style=3D"font-size:10.0pt">=B7=A2=CB=CD=CA=B1=BC=E4<span la=
ng=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"font-size:10.=
0pt"> 2013</span><span style=3D"font-size:10.0pt">=C4=EA<span lang=3D"EN-US=
">2</span>=D4=C2<span lang=3D"EN-US">5</span>=C8=D5<span lang=3D"EN-US"> 23=
:09<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> Lou Berger<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Lidan (Dan); Richard Barnes; draft-ietf-ccamp-lmp-behavior-negotiation@to=
ols.ietf.org; gen-art@ietf.org; ietf@ietf.org; The IESG<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Re: </span>=B4=F0=B8=B4<span lang=3D"EN-US">: Gen-ART review of draft-iet=
f-ccamp-lmp-behavior-negotiation-10<o:p></o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hey Lou,<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">That text looks fine to me!<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">--Richard<o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<o:p>&nbsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">On Tue, Feb 5, 2013 at 9:24 AM,=
 Lou Berger &lt;<a href=3D"mailto:lberger@labn.net" target=3D"_blank">lberg=
er@labn.net</a>&gt; wrote:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dan/Richard,<o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
<br>
<br>
On 2/4/2013 10:05 PM, Lidan (Dan) wrote:<br>
&gt; Hi Richard,<br>
&gt;<br>
&gt; Thanks for the review of this draft!<br>
&gt;<br>
&gt;&gt; Section 2.1. &nbsp;Would be helpful to either include the old form=
ats<br>
&gt;&gt; and/or say explicitly what is changing.<br>
<br>
&gt; Added the original format of Config, ConfigAck and ConfigNack<br>
&gt; messages which are defined in RFC4204.<br>
&gt;<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">I personally think it's a mista=
ke to repeat definitions in non-bis RFCs.<br>
&nbsp;I think this increases the possibility of mistakes and confusion (e.g=
.,<br>
when the text isn't copied properly or when the original document is<br>
replaced).<br>
<br>
My original thought was to propose text to follow Richard's suggestion<br>
of explicitly saying what has changed, but I see such text is there at<br>
the start of section 2:<br>
<br>
&nbsp; &nbsp;LMP Config, ConfigNack and ConfigAck messages are modified by =
this<br>
&nbsp; &nbsp;document to allow for the inclusion of multiple CONFIG objects=
. The<br>
&nbsp; &nbsp;Config and ConfigNack messages were only defined to carry one =
CONFIG<br>
&nbsp; &nbsp;object in [RFC4204]. The ConfigAck message, which was defined<=
br>
&nbsp; &nbsp;without carrying any CONFIG objects in [RFC4204], is modified =
to<br>
&nbsp; &nbsp;enable explicit identification of negotiated configuration<br>
&nbsp; &nbsp;parameters. The inclusion of CONFIG objects in ConfigAck messa=
ges is<br>
&nbsp; &nbsp;triggered by the use of the BehaviorConfig object (defined bel=
ow) in<br>
&nbsp; &nbsp;a received Config message.<br>
<br>
Richard,<br>
<br>
Is this text sufficient? &nbsp;Alternatively, this text can be moved to<br>
immediately proceed the BNF.<br>
<br>
Much thanks<br>
Lou<br>
(document co-author)<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_92A1F6CF27D54D4DA5364E59D892A02A38851F2Bszxeml555mbxchi_--

From lufang@cisco.com  Tue Feb  5 21:55:02 2013
Return-Path: <lufang@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B2921F852B; Tue,  5 Feb 2013 21:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cy9VUZ0FpTaz; Tue,  5 Feb 2013 21:55:00 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 7666D21F8510; Tue,  5 Feb 2013 21:55:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13150; q=dns/txt; s=iport; t=1360130100; x=1361339700; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=y3xhPpN3sUaU+vCPenwU16rSW0G897603DXurXcnBxc=; b=kc5zbWwM5BGZIYwXUxARyOr+O6gYjOUMLZfdq0K7wJ/KteiJf286G7Bc CTojCCBqyj3+XNxftyaqvVoLF3zELmkuA+6sndSkVMCdF/SqxQAJ20i7f Nxj944wMup9Etuzc0X2xsybyixTBahpXBO3+sx6DVbbIORl2OmMz9oZZA o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAAnvEVGtJV2d/2dsb2JhbAA8Cb9rFnOCHwEBAQMBAQEBJBM0AwgFBwYBCBEDAQILFAUyCx0IAgQBDQUIAYgCBgy7IY0RCYNgYQOmc4J+gWYHNw
X-IronPort-AV: E=Sophos;i="4.84,613,1355097600"; d="scan'208";a="173869599"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-5.cisco.com with ESMTP; 06 Feb 2013 05:54:59 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id r165swrs007125 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Feb 2013 05:54:58 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.232]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.02.0318.004; Tue, 5 Feb 2013 23:54:58 -0600
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: Barry Leiba <barryleiba@computer.org>, "draft-ietf-mpls-tp-security-framework.all@tools.ietf.org" <draft-ietf-mpls-tp-security-framework.all@tools.ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
Thread-Index: AQHOAtesnHNAYy4WRES71p6tt/rJzJhsaA8A
Date: Wed, 6 Feb 2013 05:54:58 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD931027941B@xmb-rcd-x03.cisco.com>
In-Reply-To: <CAC4RtVBgPS0aOPsM5h1WcqfBnuV+-B=g1C-AeegdKP67u1-LwA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.21.144.9]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8952C1293BF4704596011903D43C2D90@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 06 Feb 2013 08:42:02 -0800
Cc: "mpls@ietf.org" <mpls@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, 06 Feb 2013 05:55:02 -0000

Hi Barry,

Thank you very much for your review and detailed comments/suggestions, and
thanks for your discussion.
I uploaded the new version that addressed all your comments, as well as
Dan's Gen-ART review comments, and acknowledged your help.

http://www.ietf.org/internet-drafts/draft-ietf-mpls-tp-security-framework-0
8.txt


Please see in-line.


-----Original Message-----
From: Barry Leiba <barryleiba@computer.org>
Date: Monday, February 4, 2013 5:00 AM
To: "draft-ietf-mpls-tp-security-framework.all@tools.ietf.org"
<draft-ietf-mpls-tp-security-framework.all@tools.ietf.org>
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: [mpls] Last Call:
<draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security
Framework) to Informational RFC

>> The IESG has received a request from the Multiprotocol Label Switching
>>WG
>> (mpls) to consider the following document:
>> - 'MPLS-TP Security Framework'
>>   <draft-ietf-mpls-tp-security-framework-07.txt> as Informational RFC
>
>Some Last Call comments in advance of IESG Evaluation:
>
>-- Abstract --
>   This document is built on RFC5920 "MPLS and GMPLS MPLS and
>   GMPLS security framework"
>
>Bit of a stuttering typo there.

[luyuan] Fixed.=20

>
>-- General --
>
>There are lots of abbreviations throughout here that aren't expanded.
>You do send us to documentation (the last paragraph of Section 1), so
>I wonder how much we should expect every one to be expanded on first
>use.  But I see OAM, GMPLS, PWE3, PE (with and without S- and T-),
>GAL, G-ACh, BFD, DoS, LSP.

[luyuan] We initially had terminology section, it was taken out during the
last call discussion. Based on the comments from you and Dan for Gen-ART,
I added the term section back with a new list of terms that are relevant
to this document.


>
>On the other hand, I'm not sure we want to clutter things up with a
>lot of expansions that anyone who reads the document will already
>know.  So I'll just leave this as a passing comment.
>
>-- Sections 2.1 and 2.2 --
>
>It's a small point, but the diagrams for security reference models
>1(b), 2(a), 2(b), and 2(c) aren't labelled exactly as the text states.
> The bad ones are 2(a) and (b), where the diagrams have "SPE1" and the
>text has "S-PE".  In the others, it's just a question of a "-" in the
>text and none in the diagram.  As I say, it's a small point, but I'd
>prefer it if the text and the diagrams matched exactly; removing the
>dashes in the text seems easiest (and fixing the "1" in the text for
>the two "S-PE" cases).

[luyuan] Fixed all.
>
>-- Section 3 --
>
>   This section discuss various network security threats which are to
>   MPLS-TP and may endanger MPLS-TP networks.
>
>Is this missing the word "new" somewhere?  (And make it "discusses",
>while you're fixing that.  We'll let the RFC Editor do the
>"which"->"that" change; they need something to do.)

[luyuan] Fixed.
New text: This section discusses various network security threats that are
unique to MPLS-TP and may endanger MPLS-TP networks.


>
>   A successful attack on a particular MPLS-TP network or on a SP's
>   MPLS-TP infrastructure may cause one or more adverse effects.
>
>Yes, that would sort of be the definition of a successful attack, I
>should think.  (You might consider deleting this paragraph.)

[luyuan] Removed.

>
>      - GAL or BFD label manipulation, which includes insertion of false
>      labels, messages modification, deletion, or replay.
>
>To make the list clearer, I suggest this:
>
>NEW
>      - GAL or BFD label manipulation, which includes insertion of false
>      labels and modification, deletion, or replay of messages.
>END

[luyuan] Used suggested text.
>      - DoS attack through in-band OAM G-ACh/GAL and BFD messages.
>
>You mean *excessive*, unproductive messages, of course.  Is there a
>good way to say this that can help someone detect when these messages
>become a DoS attack, or otherwise give some more information?  (Maybe
>there isn't...)

[luyuan] New text:
DoS attack through in-band OAM by generating excessive G-ACh/GAL and BFD
messages which consume significant bandwidth and potentially cause
congestion.
>
>   When a NMS is used for LSP setup, the attacks to NMS can cause the
>   above effect as well. Although this is not unique to MPLS-TP, but
>   MPLS-TP network can be particularly venerable as static provisioning
>   through NMS is a commonly used model.
>
>"Vulnerable", not venerable.  But I don't understand why the fact that
>static provisioning through NMS causes any greater vulnerability than
>otherwise.  Can you expand on that a bit?

[luyuan] New text:
When a NMS is used for LSP setup, the attacks to NMS can cause the above
effect as well. Although this is not unique to MPLS-TP, MPLS-TP network
can be particularly vulnerable to NMS attack due to the fact that static
provisioning
through NMS is a commonly used model. In the static provisioning model, a
compromised NMS can potentially be comparable to a comprised control plane
plus a comprised management plane in the dynamic controlled network model.

>
>   Observation (including traffic pattern analysis), modification, or
>   deletion of a provider's or user's data, as well as replay or
>   insertion of inauthentic data into a provider's or user's data
>   stream.
>
>This isn't a complete sentence, so I'm not sure what you're trying to
>say.  Are you just saying that these are security threats?  Again,
>that seems clear, and rather obvious.

[luyuan] Adding the following text at the beginning of the paragraph:
There are other more generic security threat, such as:


> Can you perhaps split these up,
>and say a bit more about some of them?  The observation part seems
>particularly interesting: I'd like to know what can be observed that
>causes security issues.  And you've given one example, but haven't
>said much about it.  What is it that traffic pattern analysis can
>reveal in MPLS-TP that is sensitive?  What other things can be
>observed that might be sensitive?

[luyuan] The following is a sub-section in RFC5920 that explains
observation, so I added a pointer to RFC5920.

"4.2.1.  Unauthorized Observation of Data Traffic

    This refers to "sniffing" provider or end user packets and examining
    their contents.  This can result in exposure of confidential
    information.  It can also be a first step in other attacks (described
    below) in which the recorded data is modified and re-inserted, or
    simply replayed later."


>
>(The other points don't need expansion, I guess, and you cover defense
>in the next section.  But see below for a comment about that.)
>
>   The threats may be resulting from malicious behavior or accidental
>   errors. For example: Users of the MPLS-TP network may attack the
>   network or other users; employees of the MPLS-TP operators,
>   especially people who operate the NMS, attackers who obtain physical
>   access to a MPLS-TP SP's site; Other SPs in the case of MPLS-TP
>   inter-provider connection.
>
>I find this paragraph hard to follow: I don't know what to do with the
>semicolon-separated list.  I think you're giving me a list of examples
>of how malicious behaviour or accidental errors.  And what I see is
>this:
>
>1. Users of the MPLS-TP network may attack the network or other users.
>
>--- Yep... got that.
>
>2. Employees of the MPLS-TP operators, especially people who operate
>the NMS, attackers who obtain physical access to a MPLS-TP SP's site.
>
>--- I can't parse that, and don't know what you're trying to say.
>
>3. Other SPs in the case of MPLS-TP inter-provider connection.
>
>--- That's just a subject with no verb, and, again, I'm not sure what
>you want to say.

[luyuan] New text:
The threats may be resulting from malicious behavior or accidental errors.
Example 1: Attack from users: Users of the MPLS-TP network may attack the
network infrastructure or attack other users.
Example 2: Attack from insiders: Employees of the operators may attack the
MPLS-TP network, especially through NMS.
Example 3: Attack from inter-connecting SPs or other partners: Other SPs
may attack the MPLS-TP network, particularly through the inter-provider
connections.
Example 4: Attack as the result of operation errors: Operation staff may
fail to follow the operational procedures or make operational mistakes.


>
>-- Section 4 --
>
>   The techniques discussed here include [...long list...]
>
>I expected to see those techniques discussed here.  Then I saw, "Where
>these techniques apply to MPLS and GMPLS in general, they are
>described in Section 5.2 of [RFC5920]." That's fine, but then please
>don't say "The techniques discussed here".  Maybe "Techniques to
>defend against the security threats in Section 4 include
>[...list...]."
>
>   Thisis one way to protect the infrastructure used for support of
>   MPLS-TP to separate the resources for support of MPLS-TP services
>   from the resources used for other purposes. For example, in security
>   model 2 (Section 2.2), the potential risk of attacks on the S-PE or
>   T-PE in the trusted zone may be reduced by using non-IP-based
>   communication paths.
>
>The first sentence is confused and hard to understand.  Please re-write
>it.

[luyuan] New text:
One way to protect the MPLS-TP infrastructure network is to use dedicated
network resources for MPLS-TP transport services.


>
>In the second sentence (I'm not an MPLS guy, so please bear with me
>and educate me if I'm completely off base here), is the point really
>about non-IP-based communication paths, in particular?  Or is it more
>generally that the communication paths in the trusted zone are not
>accessible outside the zone?  If so, adding that would help ("...by
>using non-IP-based communication paths, so that the paths in the
>trusted zone...").

[luyuan] New text:
For example, in security model 2 (Section 2.2), the potential risk of
attacks on the S-PE1 or T-PE1 in the trusted zone may be reduced by using
non-IP-based communication paths, so that the paths in the trusted zone
cannot be reached from the outside via IP.

>
>   Note that the
>   connectivity verification are now developed for general MPLS networks
>   as well.
>
>Is there a word missing here?  Connectivity verification tools?
>Techniques?  Something else?

[luyuan] Added "tools".


>
>In the last paragraph, items 3 and 4 are the same.  I think this list
>would benefit from being shown as a regular numbered list, rather than
>grouped together in a paragraph.
[luyuan] Fixed.
>
>In general, in this section I expected to see what defensive
>techniques could be used with the specific threats in Section 3.
>Instead, I have to try to match them up, and maybe they're not very
>matchable.  Given the brevity of Section 3, I think a better
>arrangement of this document would have one section that had a list of
>threats along with the defense against each threat.  Something like
>this:
>
>Threat: GAL or BFD label manipulation, which includes insertion of
>        false labels and modification, deletion, or replay of messages.
>Defense: [Whatever]
>
>Threat: DoS attack through in-band OAM G-ACh/GAL and BFD messages.
>Defense: [Whatever else]
>
>Perhaps you thought this would be a longer document, so you arranged
>it this way, but with most things applying to MPLS in general, and not
>being specific to MPLS-TP, you have the opportunity to arrange it more
>directly.  Is it possible to do that?

[luyuan] The draft was much longer before. We shortened it based on AD's
review comments, and now focusing on threat and defense that are unique to
MPLS-TP. At this point, we would prefer to keep it this way without new
structure change. But I added the text to address your points on matching
the defense technique to the treat talked in Section 3.

New text:

Authentication is the primary defense technique to mitigate the risk of
the  MPLS-TP security threat "GAL or BFD label manipulation", and "DoS
attack through in-band OAM" discussed in Section 3. Authentication refers
to methods to ensure that message sources are properly identified by the
MPLS-TP devices with which they communicate. Authentication includes
entity authentication for identity verification, encryption for
confidentiality, management system authentication, peer-to-peer
authentication, message integrity and replay detection to ensure the
validity of message streams, network-based access controls such as packet
filtering and firewalls, host-based access controls, isolation,
aggregation, protection against denial of service, and event logging.
Where these techniques apply to MPLS and GMPLS in general, they are
described in Section 5.2 of [RFC5920].

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


Thanks,
Luyuan



From sm@resistor.net  Wed Feb  6 11:22:06 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6BF21F8A41 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 11:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 zTSWDL1jEQRT for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 11:22:03 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9457121F8A40 for <ietf@ietf.org>; Wed,  6 Feb 2013 11:21:58 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r16JLkLL019828; Wed, 6 Feb 2013 11:21:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360178511; bh=EZXdGY4s8VK4QX5GTlHfC/Oi6lit3IZFEtmYVvelKAU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rITfiwsVmEeUXA6yUGooFEGA2fHRzAd9yGOkxA5KXrz6t4Dn6DaPL9Pjo1b0vlrHJ RpbsDujWv/qUyHbSwi8pGsmTjtAcvJExdpOFnXiwjKa3yIF7rFsMEJxwpcI8KVXFyw bgJoUGlVxxZ06a9Wg8hLwB4WAUvdRWFZgqVK9YfQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360178511; i=@resistor.net; bh=EZXdGY4s8VK4QX5GTlHfC/Oi6lit3IZFEtmYVvelKAU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GjgN0sUnUQ/XD4dh3g/dSEpz6nYwvF3aeIAkOYjuBANztDTdkRmygq1gJnyw6yCwV sWoHFv6lnmY+S7pdp61nVKPf9fa5pr8if83tdHSzUxKcJDZxa4wcOWLJFEetwzjlYx 4NWZLp1mEZ6Ryd61KRmwESWWDnemO36l3LwZgHvk=
Message-Id: <6.2.5.6.2.20130206105058.098105a8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Feb 2013 11:09:18 -0800
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Remote Participation Services
In-Reply-To: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.g mail.com>
References: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 19:22:07 -0000

Hi Abdussalam,
At 18:14 05-02-2013, Abdussalam Baryun wrote:
>In the previous ietf meeting in July, I have submitted an I-D in one
>WG but had no chance to present my participation remotely, as you
>mention in 2.5. I would like the solution and that I will be able to
>present remotely. I asked the WG if someone can present for me but
>only WG darfts are done the way mentioned in 2.5,
>
>Please amend the [1] to include that there is difference process in
>IETF participation remotely for WG I-Ds and Individual I-Ds,

I read a review written by Allison Mankin [1].  I doubt that anyone 
can get a review of that quality in an IETF meeting.

It was mentioned previously on this mailing list that meetings were 
about discussing issues and not about presenting I-Ds.  If I have a 
chance to present my I-D either in person or remotely, what's do the 
people in the room gain from it?

Regards,
-sm

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


From joelja@bogus.com  Wed Feb  6 13:25:54 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B61B21F85D6; Wed,  6 Feb 2013 13:25:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.504
X-Spam-Level: 
X-Spam-Status: No, score=-102.504 tagged_above=-999 required=5 tests=[AWL=0.095, 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 mEzpn0rflw6R; Wed,  6 Feb 2013 13:25:53 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id AE9CC21F8534; Wed,  6 Feb 2013 13:25:53 -0800 (PST)
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 r16LPrSf096292 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 6 Feb 2013 21:25:53 GMT (envelope-from joelja@bogus.com)
Message-ID: <5112CA5B.8080208@bogus.com>
Date: Wed, 06 Feb 2013 13:25:47 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: IAOC <iaoc@ietf.org>, IETF Announce <ietf-announce@ietf.org>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
In-Reply-To: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@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.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 06 Feb 2013 21:25:53 +0000 (UTC)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Feb 2013 21:25:54 -0000

On 2/5/13 8:04 AM, IETF Chair wrote:
> Please see the attached report on the current status of remote participation in the IETF meeting.  Please notice at the end a call for potential experiments to explore ways that we can improve remote participation.
Thank(s) for doing the summary,  I believe understanding what is 
currently done and what has been done in the past is an important point 
for dicussion to jump off from.

An important consideration imho when the services were volunteer 
supported (as meetecho still is) is that they were relatively scalable 
relative to some previous iterations. audio streaming for all meeting(s) 
in parallel can be run by one person who has other responsibilities and 
little involvement from inroom participants. bidrectional conferencing 
typically involves more effort.
>
> 2.2. Video
>
>     In the 1990s as part of the multicast experiment, multicast video was
>     made available, but this experiment has ended without evolving into a
>     production service.
The service was offered really in two phases,  one in which 
bidirectional workstation concerning tools were used on both ends

vic/vat/sdr/wd

and bidirectional participation was possible. (archives were in rtp format)

and a phase through approximately the end of 2004 where streams were 
sourced in one direction.

in either case the potential audience was limited by the availability of 
ip multicast at a location.

expired version of the draft covering that time was:

http://www.watersprings.org/pub/id/draft-jaeggli-ietftv-ng-01.txt
>     As part of a separate experiment, some sessions use Meetecho to make
>     video available to anyone with a web browser.  WG Chairs must request
>     this coverage.  When Meetecho is used, the URLs are announced in
>     advance, and the recording becomes part of the session proceedings.
>


From barryleiba@gmail.com  Wed Feb  6 13:47:26 2013
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5087921F84CE; Wed,  6 Feb 2013 13:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQZb37XdM+RI; Wed,  6 Feb 2013 13:47:26 -0800 (PST)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7121421F8470; Wed,  6 Feb 2013 13:47:25 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id fo12so1941148lab.0 for <multiple recipients>; Wed, 06 Feb 2013 13:47:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0quh1cqSn4NYE18ATVJp5XdD9nF02WmkD2OjMW4zmwM=; b=dI7ptWpVcfC09+1A4zgR4+67KGx8Xrn4mcvnScZAiPtwGVdfSD3IKORl6ryh34nm8R UMHqRED9H9rccJmC1hJRixzWrQsqVeUVTX9n7/s/NdyVqPK4OFqJ7LUmzJ2c3q61cLwB 5bDklm6ilNZrOQHHQb30oa9iyx7ZvubfwJnZUkRj73G1Wqq2SuGfX/nXfF+l6e4lIBGk Iqa76PuSXMEAVgPnrPWzVYM4LT+ayKvdyYYwZSJBqX26S4E9hQSK9ZuVuxpJm2ZMUiU6 ML6ZXZ0E51XkDMeR7Wu6lgqwnYsDa3g/D9d8NYRo85MAh5ngJNWC5gspZqLrrUm79ZT/ 2avQ==
MIME-Version: 1.0
X-Received: by 10.112.47.168 with SMTP id e8mr11968046lbn.46.1360187242839; Wed, 06 Feb 2013 13:47:22 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.112.47.168 with HTTP; Wed, 6 Feb 2013 13:47:22 -0800 (PST)
In-Reply-To: <0DB8F45437AB844CBB5102F807A0AD931027941B@xmb-rcd-x03.cisco.com>
References: <CAC4RtVBgPS0aOPsM5h1WcqfBnuV+-B=g1C-AeegdKP67u1-LwA@mail.gmail.com> <0DB8F45437AB844CBB5102F807A0AD931027941B@xmb-rcd-x03.cisco.com>
Date: Thu, 7 Feb 2013 05:47:22 +0800
X-Google-Sender-Auth: _Iwt2q0OGp6wUKpCnGDFKXAPQ4o
Message-ID: <CALaySJJVs=GTwLytseEJZh+As+hCLp5ehM3dwfdjKH2CbtmvMg@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: "Luyuan Fang (lufang)" <lufang@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "draft-ietf-mpls-tp-security-framework.all@tools.ietf.org" <draft-ietf-mpls-tp-security-framework.all@tools.ietf.org>, "mpls@ietf.org" <mpls@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, 06 Feb 2013 21:47:26 -0000

> Thank you very much for your review and detailed comments/suggestions, and
> thanks for your discussion.
> I uploaded the new version that addressed all your comments, as well as
> Dan's Gen-ART review comments, and acknowledged your help.

Thanks for the reply, Luyuan.  I'm happy with all the resolutions.

Barry

From d3e3e3@gmail.com  Wed Feb  6 18:48:36 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE27421F84E4 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 18:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.317
X-Spam-Level: 
X-Spam-Status: No, score=-103.317 tagged_above=-999 required=5 tests=[AWL=0.282, 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 WT9BV9hG5N+H for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 18:48:36 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id CE14621F84DC for <ietf@ietf.org>; Wed,  6 Feb 2013 18:48:35 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id h1so2331431oag.31 for <ietf@ietf.org>; Wed, 06 Feb 2013 18:48:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=E77YLJiEXXufNXgTi5w6gw5THKadSdUBiEey4HhGZvY=; b=LwkLPXEM6n1vZym4/kgvZp13XNg6+5OGiFj8qol8qjYXIiHIPADlSHcDr8Muzxwd1P thByqVNRgvgaX7YgsmUATycn+6Sspk0ipvoE02SrgWzcOc0JB9r19JhsyWkJAIA6kr1e ZTNHf9Z+J9oebaFsZyozaJlEQoSNpMrcIunEffMdLWtEgrDpseyN9pTsPRePlsXunnSN VkocU6E5MWYnwXq0wHPS+zPgsf9vlaHI590oMx9Rz52gdZgognO8jmgOvf960r8dZCdD y1QRsUezR3K2cjN1j5hHlyWLeIBffnR5ZfhBS9eI3ypp1vwk0app/1Nyoqzr13HHei0f KKwA==
X-Received: by 10.182.54.102 with SMTP id i6mr22776963obp.67.1360205315265; Wed, 06 Feb 2013 18:48:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Wed, 6 Feb 2013 18:48:15 -0800 (PST)
In-Reply-To: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 6 Feb 2013 21:48:15 -0500
Message-ID: <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 07 Feb 2013 02:48:36 -0000

Hi Bjoern,

Thanks for your review and comments.

See below.

On Wed, Feb 6, 2013 at 6:40 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> Hi,
>
>   In http://www.ietf.org/id/draft-eastlake-additional-xmlsec-uris-08.txt
> the References have to be checked and updated. For example, the document
> has a normative reference to http://www.w3.org/TR/2002/WD-xptr-20020816/
> which is a "Superceded" work-in-progress that's over 10 years old. Also,

Well, the reference is to the most recent document with the title "XML
Pointer Language (XPointer)". After that it seems to have fissioned
into a few different documents The only more recent XPointer things
are only from 2003 and seem to be "XPointer element() Scheme",
"XPointer Framework", and "XPointer xmlns() Scheme". What do you think
this reference should point to?

> it references "RFC Errata, Errata ID 191, RFC 4051" without linking the
> errata item, and does so normatively even though the document as a whole

I'm not sure exactly what you mean here. The errata does appear in the
references  as

   [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
         editor.org

I have been told by an Area Director that this it the format that the
RFC Editor likes. You can certainly find the Errata starting with that
link and by just linking to the main ref-editor.org web page, it does
not constrain the other structure of that web site.

> would Obsolete RFC 4051. Just to illustrate, I did not review them all
> myself.

OK. I will move the Errata to the Informational references.

> The Abstract does not english.

How about the following change:

OLD
   This document expands and updates the list of URIs specified in RFC
   4051 and intended for use with XML Digital Signatures, Encryption,
   Canonicalization, and Key Management. These URIs identify algorithms
   and types of information. This document obsoletes RFC 4051.
NEW
   This document obsoletes RFC 4051, expanding and updating the list
   of URIs intended for use with XML Digital Signatures, Encryption,
   Canonicalization, and Key Management. These URIs identify
   algorithms and types of information.

> I don't think it's a good idea to have the Acknowledgements precede even
> the Introduction as an exception while most other documents put it near
> the end.

I disagree. I believe acknowledgments are very important and should be
at the front. I commonly (but not always) put them there in my drafts.
I am also not aware of any IETF rule prescribing where
Acknowledgements go in Internet Drafts. It is true that the RFC Editor
always move them to the end, but that's the way it goes.

> The "XCANON" reference does not work, "xml-enc-c14n-20020718" is perhaps
> meant to be "xml-exc-c14n-20020718" ("enc" vs "exc"). I've not checked
> other references.

http://www.w3.org/TR/REC-xml-enc-c14n-20020718/ is still there from
RFC 4051 which this document obsoletes. Reference should be

   http://www.w3.org/TR/2002/REC-xml-exc-c14n-20020718/

> The document makes reference to Canonical XML 1.0 without referencing,
> e.g. http://www.w3.org/TR/C14N-issues/ (and RFC 3076 does not seem to
> have any Errata filed to hint at the problems with it). I'm not sure
> that's a problem, but it might be better to mention the problems with
> Canonical XML 1.0 in some form.

Well, I would have thought that the issues in C14N-issues would be
resolved in Canonical XML 1.1 which is dated later. In any case,
problems in Canonical XML 1.0 seem irrelevant to this document which
is just about what URIs represent what algorithms or data items.

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

> regards,
> --
> Bj=F6rn H=F6hrmann =B7 mailto:bjoern@hoehrmann.de =B7 http://bjoern.hoehr=
mann.de
> Am Badedeich 7 =B7 Telefon: +49(0)160/4415681 =B7 http://www.bjoernsworld=
.de
> 25899 Dageb=FCll =B7 PGP Pub. KeyID: 0xA4357E78 =B7 http://www.websitedev=
.de/

From sm@resistor.net  Wed Feb  6 23:26:03 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD0C21F8715 for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 23:26:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 shuj6ogjU4DD for <ietf@ietfa.amsl.com>; Wed,  6 Feb 2013 23:26:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC97E21F84E3 for <ietf@ietf.org>; Wed,  6 Feb 2013 23:26:01 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r177PbSp027817; Wed, 6 Feb 2013 23:25:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360221945; bh=fLGwZbTLNzigAHHkDDolbxzrKCjrdFgpGjklDmbMd/M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YODTaRgljEPxlKr4bOr+mgwcC8+mFDnt1jRFV6SIOnY/WDNzZK0fJKxT6azDuAxMB EauyWscqbAc/PgYJ0QrKby4iIZVarJsAmRhBeT0yIJJv7pm7TIGFdFLAsKROAXJTIw AEiQhdsMJ2mPjTwcWrwk6yvYxWMLYq4NlCHyCg3E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360221945; i=@resistor.net; bh=fLGwZbTLNzigAHHkDDolbxzrKCjrdFgpGjklDmbMd/M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fmcBRmCnjiQolD3VClPbkXCMWBaKIAGsohSalnJJUfIM00ON1c4abxeGaXpr3L/tE Ledwd1PhhM34cTUCuDvhO7afvUR/5zzHwuDMW+bDte8uTu61T8shJA36d0u9unVBgD 6aBJBBlFjLfjqS6mSfUaMXHB7SHlE+pgb8l28CBg=
Message-Id: <6.2.5.6.2.20130206224118.0b15d738@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 06 Feb 2013 23:25:33 -0800
To: Donald Eastlake <d3e3e3@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
In-Reply-To: <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.g mail.com>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 07 Feb 2013 07:26:03 -0000

Hi Donald,
At 18:48 06-02-2013, Donald Eastlake wrote:
>I'm not sure exactly what you mean here. The errata does appear in the
>references  as
>
>    [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
>          editor.org
>
>I have been told by an Area Director that this it the format that the
>RFC Editor likes. You can certainly find the Errata starting with that
>link and by just linking to the main ref-editor.org web page, it does
>not constrain the other structure of that web site.

[Errata191] was a normative reference.  Referencing errata in an 
intended Proposed Standard might be a trivial matter.  There are side 
effects to that.  That may only be apparent in the long term.  I hope 
that the RFC Editor does not plan to turn Standard Track RFCs into 
"living" standards.

>OK. I will move the Errata to the Informational references.

See above.

>I disagree. I believe acknowledgments are very important and should be
>at the front. I commonly (but not always) put them there in my drafts.
>I am also not aware of any IETF rule prescribing where
>Acknowledgements go in Internet Drafts. It is true that the RFC Editor
>always move them to the end, but that's the way it goes.

I noticed that you are one of the rare authors who has the 
Acknowledgements at the beginning of their document.  It was a 
practice followed in some of the three-digit RFCs.  There isn't any 
requirement in the RFC Style Guide which prohibits the 
Acknowledgements from being at the front of the document.

I don't know whether it is relevant but John Klensin mentioned this a 
few days ago:

   "One might even suggest that one of the reasons early
    ARPANET/ Internet developments worked better than the IETF
    process of today is that there was wide recognition that it was
    necessarily a collaborative effort with many people contributing
    ideas and no one wanting to seize credit."

Section 5 mentions that "This document requires no IANA 
actions".  However, there is another paragraph in the IANA 
Considerations section which is not even actionable by IANA folks.  I 
am not sure whether the text should go into that
section.

In Section 1:

   "Note that raising XML Digital Signature to Draft Standard [RFC3275]
    in the IETF required removal of any algorithms for which there was
    not demonstrated interoperability from the Proposed Standard
    document.  This required removal of the Minimal Canonicalization
    algorithm, in which there appears to be continued interest. The URI
    for Minimal Canonicalization was included in [RFC4051] and is
    included here."

That was the historic rationale for the different levels in the 
Standards Track.  Rumor has it that although the rationale was 
forgotten, whether intentionally or not, the "MUST" wars 
continued.  Dave Crocker once raised the question of complexity of a 
specification.  Advancement along the Standards could have been used 
to make a specification less complex by trimming stuff which has not 
been implemented (see quoted text above).

In Section 2.1.1:


   "The content of the DigestValue element shall be the base64 [RFC2045]
    encoding of this bit string viewed as a 16-octet octet stream."

RFC 4648 could be reference instead of RFC 2045.

Regards,
-sm



From narten@us.ibm.com  Thu Feb  7 06:47:07 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 472F721F841B for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 06:47:07 -0800 (PST)
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 33ipuS9dz4G6 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 06:47:06 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 5988221F843D for <ietf@ietf.org>; Thu,  7 Feb 2013 06:47:06 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 7 Feb 2013 09:47:03 -0500
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 7 Feb 2013 09:47:02 -0500
Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id C63076E801A; Thu,  7 Feb 2013 09:46:59 -0500 (EST)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r17El0Wr30146682; Thu, 7 Feb 2013 09:47:01 -0500
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id r17EkdCT032200; Thu, 7 Feb 2013 07:46:40 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-252-205.mts.ibm.com [9.65.252.205]) by d03av02.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r17EkZAY031319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Feb 2013 07:46:36 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r17EkUkm004849; Thu, 7 Feb 2013 09:46:30 -0500
Message-Id: <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: IAOC <iaoc@ietf.org>
Subject: Re: Remote Participation Services
In-reply-to: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
Comments: In-reply-to IETF Chair <chair@ietf.org> message dated "Tue, 05 Feb 2013 11:04:38 -0500."
Date: Thu, 07 Feb 2013 09:46:30 -0500
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13020714-7182-0000-0000-0000050D2D27
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 14:47:07 -0000

It is good to document what we have been doing. But the text seems to
focus on technology and tools...

IMO, what is missing is operational Best Practices. We seem to be
lacking them (are any written down?) And we don't follow them
consistently, especially from one WG to another. Many of the problems
I see with remote participation facilties have to do not with the
technology per se, but with lack of proper training and advance
testing. I get the general sense that getting the remote stuff to work
is a volunteer effort where each person tries it themselves with no
checklist of obvious things to do in advance, and no recourse if no
one in the room can get something working.

E.g., I was at an interim meeting last fall, where it looked like when
the meeting started, that was the the first that folk actually looked
at the facilities in the room (phone, microphones, etc.) to see how
best to allow remote participants to speak. The quick conclusion was
"can't be done". This should have been worked out (and tested) in
advance, not at the start of the meeting.

Thomas


From mary.ietf.barnes@gmail.com  Thu Feb  7 06:54:16 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3393A21F84DA; Thu,  7 Feb 2013 06:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJz9tlIb+H9M; Thu,  7 Feb 2013 06:54:15 -0800 (PST)
Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) by ietfa.amsl.com (Postfix) with ESMTP id EA0C921F8423; Thu,  7 Feb 2013 06:54:14 -0800 (PST)
Received: by mail-qe0-f54.google.com with SMTP id 1so1195853qeb.41 for <multiple recipients>; Thu, 07 Feb 2013 06:54:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=AEzjgq7LF4mqNQXEYDvAzALbCYyqpwUuDl8kekTBNyA=; b=IfghgN3h96YivwwHcusXLeAPXb2yXNLvOCgu5volseXMhsLkrAgcqd0iIAWdbSosL4 QH1rYX11Q7uZFGQSxCKT6y7BsPwgi8/ZqBo9w0PMF5XGL0hyUbzASSOUtacRy0+X3ebX 94m3FDpS92fDqhxtWUyXuWnkIc3vLeG3hob/3Q9Mau/77CzX+JNEcI6JZ91Ymcrvw/rK 2Q1c1M6w91NoI3SY1LleM5J3HVNwQvK/s7WoCIJ3uhA+JqFWhv1xGnv4b98/HM1wgPCA atZqrtY+vKSHukL2GPRo9bhilcTNm0fbkOsBmVcn6DZop6p16b8uvLHy7jAHqepiQPpm ZQ0A==
MIME-Version: 1.0
X-Received: by 10.224.42.130 with SMTP id s2mr821214qae.63.1360248854525; Thu, 07 Feb 2013 06:54:14 -0800 (PST)
Received: by 10.49.131.199 with HTTP; Thu, 7 Feb 2013 06:54:14 -0800 (PST)
In-Reply-To: <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
Date: Thu, 7 Feb 2013 08:54:14 -0600
Message-ID: <CAHBDyN5ww1p1fZEWTKnhb_8b82r991kJz=jpK7uF2BWR-a5PCw@mail.gmail.com>
Subject: Re: Remote Participation Services
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 14:54:16 -0000

This wikipage addresses some of the operational aspects you mention:
http://wiki.tools.ietf.org/group/wgchairs/wiki/RemoteParticipation

I would think that could be augmented to address some of the concerns
you raised.

Mary.

On Thu, Feb 7, 2013 at 8:46 AM, Thomas Narten <narten@us.ibm.com> wrote:
> It is good to document what we have been doing. But the text seems to
> focus on technology and tools...
>
> IMO, what is missing is operational Best Practices. We seem to be
> lacking them (are any written down?) And we don't follow them
> consistently, especially from one WG to another. Many of the problems
> I see with remote participation facilties have to do not with the
> technology per se, but with lack of proper training and advance
> testing. I get the general sense that getting the remote stuff to work
> is a volunteer effort where each person tries it themselves with no
> checklist of obvious things to do in advance, and no recourse if no
> one in the room can get something working.
>
> E.g., I was at an interim meeting last fall, where it looked like when
> the meeting started, that was the the first that folk actually looked
> at the facilities in the room (phone, microphones, etc.) to see how
> best to allow remote participants to speak. The quick conclusion was
> "can't be done". This should have been worked out (and tested) in
> advance, not at the start of the meeting.
>
> Thomas
>

From marc.blanchet@viagenie.ca  Thu Feb  7 06:57:22 2013
Return-Path: <marc.blanchet@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AF821F84DA; Thu,  7 Feb 2013 06:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.582
X-Spam-Level: 
X-Spam-Status: No, score=-102.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 D4p5nNgVcQmb; Thu,  7 Feb 2013 06:57:21 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [206.123.31.2]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7FD21F8423; Thu,  7 Feb 2013 06:57:21 -0800 (PST)
Received: from mb.lan (modemcable180.211-203-24.mc.videotron.ca [24.203.211.180]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 011BC40422; Thu,  7 Feb 2013 09:56:50 -0500 (EST)
Subject: Re: Remote Participation Services
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=windows-1252
From: Marc Blanchet <marc.blanchet@viagenie.ca>
In-Reply-To: <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
Date: Thu, 7 Feb 2013 09:56:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD8FA589-C5A2-4393-8D77-65A550A6CD91@viagenie.ca>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1283)
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 14:57:22 -0000

Le 2013-02-07 =E0 09:46, Thomas Narten a =E9crit :

> It is good to document what we have been doing. But the text seems to
> focus on technology and tools=85

I agree and disagree.

>=20
> IMO, what is missing is operational Best Practices. We seem to be
> lacking them (are any written down?) And we don't follow them
> consistently, especially from one WG to another. Many of the problems
> I see with remote participation facilties have to do not with the
> technology per se, but with lack of proper training and advance
> testing. I get the general sense that getting the remote stuff to work
> is a volunteer effort where each person tries it themselves with no
> checklist of obvious things to do in advance, and no recourse if no
> one in the room can get something working.

right. I for one had chaired a few working groups where the main =
contributors (and therefore presenters) were not on-site. I spent a =
significant amount of time in preparation, testing, etc=85 with the =
great help of Joel Jaeggli borrowing me the right cables. For most time, =
it worked. Sometimes it did not work well. And given that the meeting =
rooms are all occupied, it is very difficult to test a lot in advance, =
so I did in off hours, such as during lunch doing sound checks while an =
informal meeting was taking place and I was disturbing, but my chairing =
was the first session after lunch. =20

In summary, currently, bi-directionnal audio is not well supported (no =
criticism intended, just a fact), which does not help in having remote =
participation, specially for speakers.  So technology and tools, well =
tested, in production, supported, would help a lot, at least in the use =
cases I've been involved.

Having said that, your point of best practices is also relevant.

And also wg chairs doing more prep in advance of their meeting, unless =
we have paid support staff to take care of these.

Marc.


>=20
> E.g., I was at an interim meeting last fall, where it looked like when
> the meeting started, that was the the first that folk actually looked
> at the facilities in the room (phone, microphones, etc.) to see how
> best to allow remote participants to speak. The quick conclusion was
> "can't be done". This should have been worked out (and tested) in
> advance, not at the start of the meeting.
>=20
> Thomas


From d3e3e3@gmail.com  Thu Feb  7 07:38:03 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4DDF21F870E for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 07:38:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.336
X-Spam-Level: 
X-Spam-Status: No, score=-103.336 tagged_above=-999 required=5 tests=[AWL=0.263, 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 kBK9GKurIuHm for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 07:38:03 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id D4B2F21F8706 for <ietf@ietf.org>; Thu,  7 Feb 2013 07:38:02 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so2919195oag.28 for <ietf@ietf.org>; Thu, 07 Feb 2013 07:38:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=c0tsEqWTQnEiq4HzwJqHKVZAvoFoyaGVbXJFNEdCo+I=; b=lr/0merLFw7aPVsHtbUdnmPlq3Qt7kJFh6vnCZO2NYZ2rDnqXNwOv30Qhf10HykoRy doHx6QZNXLNGQ+egEMyZyHZy10Ms9q7jb2Mm7EEw2UpqSGcMvp0YUZU2/OIN95Kgqv/O mz5aoI92sNxsepMxPMCpbub/eCMgDNqQA34RgNA2simb0RKBR4d6J3Yl6gnA3EIzoB6V Zd5m0qkksHATKrnOjjkgeOof7dwk9TM08orDFP0DmHXIIitmZhm7Y6fum1Dmm5JHh45E xERodfvegaPmtLtCEJ3Xhv66isfysm8o3ttaCQR3+Xjk03G+GXMW8EI7ERF9GoZrRz82 F2pg==
X-Received: by 10.60.30.38 with SMTP id p6mr1394186oeh.2.1360251481738; Thu, 07 Feb 2013 07:38:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 7 Feb 2013 07:37:41 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130206224118.0b15d738@resistor.net>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <6.2.5.6.2.20130206224118.0b15d738@resistor.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 7 Feb 2013 10:37:41 -0500
Message-ID: <CAF4+nEFpZChc8sRE=uEEd4zYMd0jzZqn7rJ7sBSxR6OtosGGSQ@mail.gmail.com>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Heather Flanagan \(RFC Series Editor\)" <rse@rfc-editor.org>, ietf@ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, Frederick Hirsch <frederick.hirsch@nokia.com>, draft-eastlake-additional-xmlsec-uris@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 15:38:04 -0000

Hi,

Thanks for your comments.

See below.

On Thu, Feb 7, 2013 at 2:25 AM, SM <sm@resistor.net> wrote:
> Hi Donald,
>
> At 18:48 06-02-2013, Donald Eastlake wrote:
>>
>> I'm not sure exactly what you mean here. The errata does appear in the
>> references  as
>>
>>    [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
>>          editor.org
>>
>> I have been told by an Area Director that this it the format that the
>> RFC Editor likes. You can certainly find the Errata starting with that
>> link and by just linking to the main ref-editor.org web page, it does
>> not constrain the other structure of that web site.
>
> [Errata191] was a normative reference.  Referencing errata in an intended
> Proposed Standard might be a trivial matter.  There are side effects to
> that.  That may only be apparent in the long term.  I hope that the RFC
> Editor does not plan to turn Standard Track RFCs into "living" standards.
>
>> OK. I will move the Errata to the Informational references.
>
> See above.
>
>> I disagree. I believe acknowledgments are very important and should be
>> at the front. I commonly (but not always) put them there in my drafts.
>> I am also not aware of any IETF rule prescribing where
>> Acknowledgements go in Internet Drafts. It is true that the RFC Editor
>> always move them to the end, but that's the way it goes.
>
> I noticed that you are one of the rare authors who has the Acknowledgements
> at the beginning of their document.  It was a practice followed in some of
> the three-digit RFCs.  There isn't any requirement in the RFC Style Guide
> which prohibits the Acknowledgements from being at the front of the
> document.

As I say, although I frequently put them near the front of my Internet
Drafts, the RFC Editor always moves them to the end.

> I don't know whether it is relevant but John Klensin mentioned this a few
> days ago:
>
>   "One might even suggest that one of the reasons early
>    ARPANET/ Internet developments worked better than the IETF
>    process of today is that there was wide recognition that it was
>    necessarily a collaborative effort with many people contributing
>    ideas and no one wanting to seize credit."

I believe there may be some legal requirement to acknowledge those
whose contributions have resulted in change in the document, unless
they ask not to be listed. Anyway, my practice is not because anyone
has asked to be listed nearer the beginning of the document but
because I think they deserve to be so listed.

> Section 5 mentions that "This document requires no IANA actions".  However,
> there is another paragraph in the IANA Considerations section which is not
> even actionable by IANA folks.  I am not sure whether the text should go
> into that section.

Well, I could rename Section 5 to be "Allocation Considerations" and
provide two subsection, one "5.1 IANA Considerations" and one "5.2 W3C
Allocation Considerations" or the like and perhaps also move some of
the material at the beginning of Section 2 down to 5.2.

> In Section 1:
>
>   "Note that raising XML Digital Signature to Draft Standard [RFC3275]
>    in the IETF required removal of any algorithms for which there was
>    not demonstrated interoperability from the Proposed Standard
>    document.  This required removal of the Minimal Canonicalization
>    algorithm, in which there appears to be continued interest. The URI
>    for Minimal Canonicalization was included in [RFC4051] and is
>    included here."
>
> That was the historic rationale for the different levels in the Standards
> Track.  Rumor has it that although the rationale was forgotten, whether
> intentionally or not, the "MUST" wars continued.  Dave Crocker once raised
> the question of complexity of a specification.  Advancement along the
> Standards could have been used to make a specification less complex by
> trimming stuff which has not been implemented (see quoted text above).
>
> In Section 2.1.1:
>
>   "The content of the DigestValue element shall be the base64 [RFC2045]
>    encoding of this bit string viewed as a 16-octet octet stream."
>
> RFC 4648 could be reference instead of RFC 2045.

RFC4648 is Informational, so that would cause yet another downref. RFC
2045 has not bee obsoleted and seems fine to me for this purpose.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Regards,
> -sm

From julian.reschke@gmx.de  Thu Feb  7 08:23:02 2013
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 B231E21F88E8 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.018
X-Spam-Level: 
X-Spam-Status: No, score=-105.018 tagged_above=-999 required=5 tests=[AWL=-2.419, 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 Zcdl2BWx4V-S for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:23:02 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 5909D21F885C for <ietf@ietf.org>; Thu,  7 Feb 2013 08:23:00 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Laq3S-1UnaZ92WTo-00kR9b for <ietf@ietf.org>; Thu, 07 Feb 2013 17:22:59 +0100
Received: (qmail invoked by alias); 07 Feb 2013 16:22:59 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.102]) [217.91.35.233] by mail.gmx.net (mp028) with SMTP; 07 Feb 2013 17:22:59 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1830QIuXmA3/VHa9ABxVxe/iSF9R2XjSACiSBU6X1 6yJK3WrfbezKVK
Message-ID: <5113D4E0.1090201@gmx.de>
Date: Thu, 07 Feb 2013 17:22:56 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com>
In-Reply-To: <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 07 Feb 2013 16:23:02 -0000

On 2013-02-07 03:48, Donald Eastlake wrote:
> ...
>> it references "RFC Errata, Errata ID 191, RFC 4051" without linking the
>> errata item, and does so normatively even though the document as a whole
>
> I'm not sure exactly what you mean here. The errata does appear in the
> references  as
>
>     [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
>           editor.org
>
> I have been told by an Area Director that this it the format that the
> RFC Editor likes. You can certainly find the Errata starting with that
> link and by just linking to the main ref-editor.org web page, it does
> not constrain the other structure of that web site.
> ...

Indeed. But maybe it's time to restate that the "format the RFC Editor 
likes" is sub-optimal. The format *readers* like is a link that actually 
gets you directly to the erratum.

Best regards, Julian

From paul.hoffman@vpnc.org  Thu Feb  7 08:52:18 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCF921F84C6 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:52:18 -0800 (PST)
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 LrCMywR78DxD for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:52:18 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id A21BA21F862A for <ietf@ietf.org>; Thu,  7 Feb 2013 08:52:12 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-243.dsl.dynamic.sonic.net [50.1.98.243]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r17Gq5Hv045887 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Feb 2013 09:52:06 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <5113D4E0.1090201@gmx.de>
Date: Thu, 7 Feb 2013 08:52:05 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD030171-76F0-457D-A73E-E134D2F11937@vpnc.org>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <5113D4E0.1090201@gmx.de>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Julian Reschke <julian.reschke@gmx.de>, "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, 07 Feb 2013 16:52:19 -0000

On Feb 7, 2013, at 8:22 AM, Julian Reschke <julian.reschke@gmx.de> =
wrote:

> On 2013-02-07 03:48, Donald Eastlake wrote:
>> ...
>>> it references "RFC Errata, Errata ID 191, RFC 4051" without linking =
the
>>> errata item, and does so normatively even though the document as a =
whole
>>=20
>> I'm not sure exactly what you mean here. The errata does appear in =
the
>> references  as
>>=20
>>    [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
>>          editor.org
>>=20
>> I have been told by an Area Director that this it the format that the
>> RFC Editor likes. You can certainly find the Errata starting with =
that
>> link and by just linking to the main ref-editor.org web page, it does
>> not constrain the other structure of that web site.
>> ...
>=20
> Indeed. But maybe it's time to restate that the "format the RFC Editor =
likes" is sub-optimal. The format *readers* like is a link that actually =
gets you directly to the erratum.

Further, it is probably not correct to say that the RFC Editor "likes" =
it, just that they got used to using it. It would be better to submit =
the Internet Draft with the obviously-more-useful URL and then let them =
make it less useful, if they want.

--Paul Hoffman=

From mcr@sandelman.ca  Thu Feb  7 08:57:22 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B81E21F847C; Thu,  7 Feb 2013 08:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLwHTD8EsiBk; Thu,  7 Feb 2013 08:57:22 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id D71D321F844C; Thu,  7 Feb 2013 08:57:21 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id AE77B2016D; Thu,  7 Feb 2013 12:03:22 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id BBF6E14852; Thu,  7 Feb 2013 11:56:20 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id AC18124691; Thu,  7 Feb 2013 11:56:20 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Remote Participation Services
In-Reply-To: <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 07 Feb 2013 11:56:20 -0500
Message-ID: <4352.1360256180@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 16:57:22 -0000

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


>>>>> "Thomas" =3D=3D Thomas Narten <narten@us.ibm.com> writes:
    Thomas> IMO, what is missing is operational Best Practices. We seem
    Thomas> to be lacking them (are any written down?) And we don't
    Thomas> follow them consistently, especially from one WG to
    Thomas> another. Many of the problems I see with remote
    Thomas> participation facilties have to do not with the technology
    Thomas> per se, but with lack of proper training and advance
    Thomas> testing. I get the general sense that getting the remote

+5.

I am setting a deadline for slides for IETF86 for my WG, and I will be
doing a unified slide deck.  I might allow text on a slide to be
updated the day before... but no slides, no speak.


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



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

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

iQCVAwUAURPctIqHRg3pndX9AQK4igP+NanVvgyK8CuuCEkckE/4Fl6py5qL/MI8
CbWY9nx8+eSsMNqwZHAALh9ghaJDilPj+BInDgFi4aKApwxgB36G8ITR5bDqMnM0
yoddItDuofgQroZ0sCxfEQqI8Lm1HmQeveNTquEF/GIZvaNtZw0O2JU5bbPeQ7CW
3MeivaQBfNc=
=IDBp
-----END PGP SIGNATURE-----
--=-=-=--

From dougb@dougbarton.us  Thu Feb  7 09:05:11 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A6D21F87F7 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 09:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.57
X-Spam-Level: 
X-Spam-Status: No, score=-2.57 tagged_above=-999 required=5 tests=[AWL=0.030,  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 OMyr9vb2c8Wq for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 09:05:11 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id E755A21F87DF for <ietf@ietf.org>; Thu,  7 Feb 2013 09:05:10 -0800 (PST)
Received: from [IPv6:2001:470:d:5e7:407b:2909:39f6:db4] (unknown [IPv6:2001:470:d:5e7:407b:2909:39f6:db4]) by dougbarton.us (Postfix) with ESMTPSA id 4877F22BD4 for <ietf@ietf.org>; Thu,  7 Feb 2013 17:05:06 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1360256706; bh=kSECcvjkJ8kZqq8ovCnWX2/cXEl+Gicak9/X56D0NiM=; h=Date:From:To:Subject:References:In-Reply-To; b=a+yxj2KYoCimlGR7Sp8e/VxPYgAXu8J+oM5Gpwo314SHOyy2CI1s7NTgXW7Q2hJPV 0bwfs9qbz+/GPzb1g2GBBYWVP3rFdqTYFeofrA0YC817m6TWfz2/LtToQPOg/a5XXp sZ08HnMT3vsHHwNygmUB1HzibMsNnOPNIlWWqzOk=
Message-ID: <5113DEC2.70306@dougbarton.us>
Date: Thu, 07 Feb 2013 09:05:06 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com> <4352.1360256180@sandelman.ca>
In-Reply-To: <4352.1360256180@sandelman.ca>
X-Enigmail-Version: 1.4.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 17:05:11 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/07/2013 08:56 AM, Michael Richardson wrote:
| I am setting a deadline for slides for IETF86 for my WG, and I will
| be doing a unified slide deck.

Does that mean all slides from all presentations in 1 deck? If that's
offered as a bonus feature, no problem. But it's more likely than not
that people would be interested in saving the slides from some
presentations, but not all.

Doug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iQEcBAEBCAAGBQJRE97CAAoJEFzGhvEaGryEafcH/13D3qR8RVrpFNRoNy4IphlK
OUaOA1ynPd3iOzmscCPFwxUrGPYzMdsDpywEjZYeCPMxeUXrar9WHqpiGUoRSFmS
jVH4xQMe7Ac19chzo/xsNVUeb6RANEj6cvp5+Zq5WYIC+skq/8na8wFGfmQkL3Rb
leID9BBiW+37QvQZdKkTn7mUGETYZA8y6MW8BKxhc9xUu4qmfe/QVBPmm6iVNyxo
U2OrjShr53BGDRMs6GfwKJ4GylkSL0UOvHMnI4tDs6PkaL7AtlqU443dxmZX+5gY
C4GAlDYAVQCAdPSVC0PY5zFik6zU1Un6I4X9N+i6cJ41HQS4k93nnQQbuWK2G4Q=
=ZiyQ
-----END PGP SIGNATURE-----

From lear@cisco.com  Thu Feb  7 09:07:31 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49DB021F8439; Thu,  7 Feb 2013 09:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.576
X-Spam-Level: 
X-Spam-Status: No, score=-110.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AIp9V6CSVl1A; Thu,  7 Feb 2013 09:07:28 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 39AD821F8438; Thu,  7 Feb 2013 09:07:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1721; q=dns/txt; s=iport; t=1360256845; x=1361466445; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=f5f9DidPX3wwdvO/kkLnL2JP4/aauopkukBqMCadFUs=; b=BCHVxh9EnnoFX1HixqjPK+ldqgvVxs8IUAhkWH9zzBnkVDxKbIcxYFUk 818nXvVxWDwm/ec9b1Q+YpouE/A7YpkDYGVX5Dj/rJ/OuVwKhjbo05mXm I4kZnu7V/nFyCLinwjw1gnlF/X1Bc9+jNoS8mlLsEpaij5kmmQAmen9/m M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAGPcE1GQ/khM/2dsb2JhbABFhkm6HxZzgh8BAQEEIw8BRQEQCxgCAgUWCwICCQMCAQIBRQYNAQcBARiHdaxKklCBI48mgRMDliGQUoMB
X-IronPort-AV: E=Sophos;i="4.84,622,1355097600"; d="scan'208";a="11657566"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 07 Feb 2013 17:07:24 +0000
Received: from dhcp-10-55-87-156.cisco.com (dhcp-10-55-87-156.cisco.com [10.55.87.156]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id r17H7NKb012489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 7 Feb 2013 17:07:24 GMT
Message-ID: <5113DF4B.8060004@cisco.com>
Date: Thu, 07 Feb 2013 18:07:23 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
In-Reply-To: <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 17:07:31 -0000

Hi Thomas,

On 2/7/13 3:46 PM, Thomas Narten wrote:
> It is good to document what we have been doing. But the text seems to
> focus on technology and tools...
>
> IMO, what is missing is operational Best Practices. We seem to be
> lacking them (are any written down?) And we don't follow them
> consistently, especially from one WG to another. Many of the problems
> I see with remote participation facilties have to do not with the
> technology per se, but with lack of proper training and advance
> testing. I get the general sense that getting the remote stuff to work
> is a volunteer effort where each person tries it themselves with no
> checklist of obvious things to do in advance, and no recourse if no
> one in the room can get something working.
>
> E.g., I was at an interim meeting last fall, where it looked like when
> the meeting started, that was the the first that folk actually looked
> at the facilities in the room (phone, microphones, etc.) to see how
> best to allow remote participants to speak. The quick conclusion was
> "can't be done". This should have been worked out (and tested) in
> advance, not at the start of the meeting.
>

I appreciate this point of view, but at what point do we mean that a
face to face is really intended to be that?  That is- if you can get the
facilities going, great.  If not, let's recall how many people are on
the IETF payroll in this process, especially when it comes to interims. 
That having been said, I think it would be great to have a best
practices guide or checklist as you suggest.  Forgive me if this sounds,
crass- it's not intended to beâ€“ but sending some text to kick things off
would be very helpful.

Eliot

From lufang@cisco.com  Wed Feb  6 13:51:17 2013
Return-Path: <lufang@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9508B21E8048; Wed,  6 Feb 2013 13:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdnWtpTNUFu6; Wed,  6 Feb 2013 13:51:17 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id AFCB921E8044; Wed,  6 Feb 2013 13:51:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=878; q=dns/txt; s=iport; t=1360187476; x=1361397076; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=qGkLuxh+HOomRYPs4z7ifNeJnoIRHQi0j6B74X8XTpQ=; b=AxI5XEGGu0SrAWh4bXTU0ljDO494ZO1g26Njf0oS/ZwJOuqxB/0oBNY3 0iyAlBjeKIaCLNjUFvsV21wpuF1LMK5jxUNHCjyqnXognIY+i9MaTMw1h XIDPWWXBUbcp38tZ+StjZKrkfcdSP5RJXIAAxSp7/eYZLmsjXUSqexwUB Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkEFAF3PElGtJV2c/2dsb2JhbABFhgK6ThZzgh8BAQEDATo/DAYBCBEDAQILFAU9HQgCBA4FCIgDBrxkkHhhA6Zzgn6CJA
X-IronPort-AV: E=Sophos;i="4.84,617,1355097600"; d="scan'208";a="174199543"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-8.cisco.com with ESMTP; 06 Feb 2013 21:51:16 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r16LpGZe003486 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Feb 2013 21:51:16 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.232]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.02.0318.004; Wed, 6 Feb 2013 15:51:16 -0600
From: "Luyuan Fang (lufang)" <lufang@cisco.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security Framework) to Informational RFC
Thread-Index: AQHOAtesnHNAYy4WRES71p6tt/rJzJhsaA8AgAFd7QD//61AAA==
Date: Wed, 6 Feb 2013 21:51:15 +0000
Message-ID: <0DB8F45437AB844CBB5102F807A0AD931027A233@xmb-rcd-x03.cisco.com>
In-Reply-To: <CALaySJJVs=GTwLytseEJZh+As+hCLp5ehM3dwfdjKH2CbtmvMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [10.82.213.2]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <51189958A5B6D34AA3FB78933C60BEAD@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 07 Feb 2013 09:30:09 -0800
Cc: "draft-ietf-mpls-tp-security-framework.all@tools.ietf.org" <draft-ietf-mpls-tp-security-framework.all@tools.ietf.org>, "mpls@ietf.org" <mpls@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, 06 Feb 2013 21:51:17 -0000

Barry,

Thanks again for your help and support!
Luyuan

-----Original Message-----
From: Barry Leiba <barryleiba@computer.org>
Date: Wednesday, February 6, 2013 1:47 PM
To: Luyuan Fang <lufang@cisco.com>
Cc: "draft-ietf-mpls-tp-security-framework.all@tools.ietf.org"
<draft-ietf-mpls-tp-security-framework.all@tools.ietf.org>,
"mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
Subject: Re: [mpls] Last Call:
<draft-ietf-mpls-tp-security-framework-07.txt> (MPLS-TP Security
Framework) to Informational RFC

>> Thank you very much for your review and detailed comments/suggestions,
>>and
>> thanks for your discussion.
>> I uploaded the new version that addressed all your comments, as well as
>> Dan's Gen-ART review comments, and acknowledged your help.
>
>Thanks for the reply, Luyuan.  I'm happy with all the resolutions.
>
>Barry


From Frederick.Hirsch@nokia.com  Thu Feb  7 08:04:10 2013
Return-Path: <Frederick.Hirsch@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCF621F8735 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:04:10 -0800 (PST)
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 7+fiImkwBG2l for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 08:04:09 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 3800421F8733 for <ietf@ietf.org>; Thu,  7 Feb 2013 08:04:08 -0800 (PST)
Received: from vaebh102.NOE.Nokia.com (in-mx.nokia.com [10.160.244.23]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r17G43En004742; Thu, 7 Feb 2013 18:04:04 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.49]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 7 Feb 2013 18:04:04 +0200
Received: from 008-AM1MPN1-033.mgdnok.nokia.com ([169.254.3.155]) by 008-AM1MMR2-015.mgdnok.nokia.com ([65.54.30.49]) with mapi id 14.02.0318.003; Thu, 7 Feb 2013 16:04:03 +0000
From: <Frederick.Hirsch@nokia.com>
To: <d3e3e3@gmail.com>
Subject: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Topic: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Index: AQHOBUy/U6rD1f4ul0GMQQZ+u87w1Q==
Date: Thu, 7 Feb 2013 16:04:02 +0000
Message-ID: <1CB2E0B458B211478C85E11A404A2B270190987F@008-AM1MPN1-033.mgdnok.nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.30.252.41]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <06A482AD60ACCA4F856F4BE5FB3AACEA@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2013 16:04:04.0275 (UTC) FILETIME=[C054A830:01CE054C]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Thu, 07 Feb 2013 09:30:09 -0800
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Frederick.Hirsch@nokia.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, 07 Feb 2013 16:04:10 -0000

Donald=20

Some additional comments on draft http://tools.ietf.org/pdf/draft-eastlake-=
additional-xmlsec-uris-08.pdf

sorry about the delay getting these comments to you.

(1) We have defined different *informative* URIs for AES Key Wrap with Padd=
ing in XML Encryption 1.1 [http://www.w3.org/TR/xmlenc-core1/#sec-kw-aes-wi=
th-pad] which are different from those in the RFC, namely

http://www.w3.org/2009/xmlenc11#kw-aes-128-pad

http://www.w3.org/2009/xmlenc11#kw-aes-192-pad

http://www.w3.org/2009/xmlenc11#kw-aes-256-pad

I suggest we change this informative appendix of XML Encryption 1.1 (and th=
e Security Algorithms Cross-Reference) to match what is in the RFC draft. T=
homas, is there any problem with that at this PR stage?

Those in the RFC draft are:

http://www.w3.org/2007/05/xmldsig-more#kw-aes128-pad=20

http://www.w3.org/2007/05/xmldsig-more#kw-aes192-pad=20

http://www.w3.org/2007/05/xmldsig-more#kw-aes256-pad

(2) ConcatKDF fragment needs fixing in 4.1 and change log Appendix A due to=
 a typo

"2009/xmlenc11#ConctKDF [XMLENC]" should be "2009/xmlenc11#ConcatKDF [XMLEN=
C]"

"#ConctKDF," should be "#ConcatKDF,"

(3) To some degree the fragment index and URI index replicate the published=
 W3C Note, XML Security Algorithm Cross-Reference and could be incorporated=
 there.

(4) I suggest an update to the Introduction to mention XML Security 1.1 as =
follows

after "All of these standards and recommendations use URIs [RFC3986] to ide=
ntify algorithms and keying information types."

add

"The W3C has subsequently produced updated  XML Signature 1.1  [XMLDSIG11] =
and XML Encryption 1.1 [XMLENC11} versions as well as a new XML Signature P=
roperties specification [XMLDSIG-PROPERTIES].

(5) Typo in introduction

"Canoncialization" should be "Canonicalization"

(6) References

Add references to XML Signature 1.1, XML Encryption 1.1, XML Signature Prop=
erties, XML Security Algorithm Cross-Reference (all to be updated upon Reco=
mmendation publication)

Signature properties has added a namespace: xmlns dsp=3D"http://www.w3.org/=
2009/xmldsig-properties"

[XMLDSIG-CORE1]
D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. XML Signat=
ure Syntax and Processing Version 1.1. 24 January 2013. W3C Proposed Recomm=
endation. (Work in progress) URL:http://www.w3.org/TR/2013/PR-xmldsig-core1=
-20130124/

[XMLENC-CORE1]
J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. XML Encryption Syntax and P=
rocessing Version 1.1. 24 January 2013. W3C Proposed Recommendation. (Work =
in progress) URL:http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/

[XMLDSIG-PROPERTIES]
Frederick Hirsch. XML Signature Properties. 24 January 2013. W3C Proposed R=
ecommendation. (Work in progress.) URL: http://www.w3.org/TR/2013/PR-xmldsi=
g-properties-20130124/

[XMLSEC-ALGS] F Hirsch, T Roessler, K Yiu XML Security Algorithm Cross-Refe=
rence, 24 January 2013 W3C Working Group Note http://www.w3.org/TR/2013/NOT=
E-xmlsec-algorithms-20130124/


regards, Frederick

Frederick Hirsch, Nokia
Chair XML Security WG




From spromano@unina.it  Thu Feb  7 09:57:08 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BCB121F8845; Thu,  7 Feb 2013 09:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.384
X-Spam-Level: 
X-Spam-Status: No, score=-99.384 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_HEAD=1.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 Ap6iQcyWIM4a; Thu,  7 Feb 2013 09:57:07 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 4A06421F8842; Thu,  7 Feb 2013 09:57:06 -0800 (PST)
Received: from [1.32.16.48] ([37.102.46.238]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id r17HuwOv014279 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 7 Feb 2013 18:57:03 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <4352.1360256180@sandelman.ca>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com> <4352.1360256180@sandelman.ca>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----DX4VEZZ2UDJWX1CT5SGTY6B2KRX81O"
Subject: Re: Remote Participation Services
From: Simon Pietro Romano <spromano@unina.it>
Date: Thu, 07 Feb 2013 18:56:48 +0100
To: Michael Richardson <mcr+ietf@sandelman.ca>, Thomas Narten <narten@us.ibm.com>
Message-ID: <54248c5e-4589-416d-9fb7-ffaf679e2567@email.android.com>
Cc: IAOC <iaoc@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 17:57:08 -0000

------DX4VEZZ2UDJWX1CT5SGTY6B2KRX81O
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi Michael,

+1 for the deadline
- 1 for the unified slide deck: from my experience with Meetecho, this is not always a good idea, both because of the deck's dimensions and of the difficulties in automatically recognizing speakers' switches (e.g. for the recordings of the single presentations).

My 2 cents,

Simon

Michael Richardson <mcr+ietf@sandelman.ca> ha scritto:

>
>>>>>> "Thomas" == Thomas Narten <narten@us.ibm.com> writes:
>    Thomas> IMO, what is missing is operational Best Practices. We seem
>    Thomas> to be lacking them (are any written down?) And we don't
>    Thomas> follow them consistently, especially from one WG to
>    Thomas> another. Many of the problems I see with remote
>    Thomas> participation facilties have to do not with the technology
>    Thomas> per se, but with lack of proper training and advance
>    Thomas> testing. I get the general sense that getting the remote
>
>+5.
>
>I am setting a deadline for slides for IETF86 for my WG, and I will be
>doing a unified slide deck.  I might allow text on a slide to be
>updated the day before... but no slides, no speak.
>
>
>-- 
>Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works 

------DX4VEZZ2UDJWX1CT5SGTY6B2KRX81O
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<html><head/><body><html><head></head><body>Hi Michael,<br>
<br>
+1 for the deadline<br>
- 1 for the unified slide deck: from my experience with Meetecho, this is not always a good idea, both because of the deck&#39;s dimensions and of the difficulties in automatically recognizing speakers&#39; switches (e.g. for the recordings of the single presentations).<br>
<br>
My 2 cents,<br>
<br>
Simon<br><br><div class="gmail_quote">Michael Richardson &lt;mcr+ietf@sandelman.ca&gt; ha scritto:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px"><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #e9b96e; padding-left: 1ex;">"Thomas" == Thomas Narten &lt;narten@us.ibm.com&gt; writes:<br /></blockquote></blockquote></blockquote></blockquote></blockquote>Thomas&gt; IMO, what is missing is operational Best Practices. We seem<br />Thomas&gt; to be lacking them (are any written down?) And we don't<br />Thomas&gt; follo!
 w them
consistently, especially from one WG to<br />Thomas&gt; another. Many of the problems I see with remote<br />Thomas&gt; participation facilties have to do not with the technology<br />Thomas&gt; per se, but with lack of proper training and advance<br />Thomas&gt; testing. I get the general sense that getting the remote<br /><br />+5.<br /><br />I am setting a deadline for slides for IETF86 for my WG, and I will be<br />doing a unified slide deck.  I might allow text on a slide to be<br />updated the day before... but no slides, no speak.<br /><br /></pre></blockquote></div></body></html></body></html>
------DX4VEZZ2UDJWX1CT5SGTY6B2KRX81O--


From randy@psg.com  Thu Feb  7 10:06:38 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1630D21F8856 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 10:06:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zNIcgsrZKoE for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 10:06:37 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B843F21F8859 for <ietf@ietf.org>; Thu,  7 Feb 2013 10:06:37 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1U3Vro-000N6E-Gj; Thu, 07 Feb 2013 18:06:36 +0000
Date: Thu, 07 Feb 2013 10:06:36 -0800
Message-ID: <m2mwvg0zir.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Remote Participation Services
In-Reply-To: <4352.1360256180@sandelman.ca>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com> <4352.1360256180@sandelman.ca>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 18:06:38 -0000

> I am setting a deadline for slides for IETF86 for my WG, and I will be
> doing a unified slide deck.  I might allow text on a slide to be
> updated the day before... but no slides, no speak.

i know this will come as a shock to many, but some of us occasionally
choose to speak *without powerpoint*!!!!!

randy

From melinda.shore@gmail.com  Thu Feb  7 11:41:29 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBB321F88E8 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 11:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YnLFf74jhovv for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 11:41:28 -0800 (PST)
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) by ietfa.amsl.com (Postfix) with ESMTP id BD7D821F88DB for <ietf@ietf.org>; Thu,  7 Feb 2013 11:41:28 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id hz1so1569725pad.38 for <ietf@ietf.org>; Thu, 07 Feb 2013 11:41:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Ltv1cF8Hx9qm99pmJtst/wR8wB3vuKtyKnh0ulInHDM=; b=Ic2wYMdwxwO06xWgxjVQL9CNya5idjYyE0x3ConDhLW/Dw2pB0tQgSctJHQ6OYMjDU 9G2PWlr/uDC0zEFmAGmFZSnkV5TRLl8nV4SRtAL17EE5fgehHcPyt/msDa4DxJ0VlULs 8QQty/JE94VF00EH7JvjzP0MOpXUiOAnG20QpdHA54ofcF6vyJh5DzFkjAE1eSnBIsUZ 6iTvCbP6H49NeVo1AeGsReVtmMnPeJZVRS9TYZ5SuzAm7Q/HZMdArgDKZXEZQA1A4L25 ICjGi24SLLqILnZiwqdVMxi2u6/06mvJvwymdaHlqm2qXbxepO4lJz/g4nq115xLIq4w 7JIA==
X-Received: by 10.66.81.68 with SMTP id y4mr8694710pax.66.1360266088425; Thu, 07 Feb 2013 11:41:28 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id q4sm48199249paz.20.2013.02.07.11.41.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 07 Feb 2013 11:41:27 -0800 (PST)
Message-ID: <51140364.1080002@gmail.com>
Date: Thu, 07 Feb 2013 10:41:24 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <201302071446.r17EkUkm004849@cichlid.raleigh.ibm.com> <5113DF4B.8060004@cisco.com>
In-Reply-To: <5113DF4B.8060004@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 19:41:29 -0000

On 2/7/13 3:46 PM, Thomas Narten wrote:
> IMO, what is missing is operational Best Practices. We seem to be
> lacking them (are any written down?) 

I started a page on the working group chairs wiki, and I know that
at least one other person has edited it.  However, that may be too
informal for what you're asking.
http://wiki.tools.ietf.org/group/wgchairs/wiki/RemoteParticipation

Melinda



From sm@resistor.net  Thu Feb  7 12:22:54 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F068821F8467 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 12:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A7IzqGyFCvQN for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 12:22:52 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 657A521F8488 for <ietf@ietf.org>; Thu,  7 Feb 2013 12:22:52 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r17KMXO1026004; Thu, 7 Feb 2013 12:22:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360268561; bh=5MDWS6eXyMPhtyDN5xOOGRT9gLsLTqVrDVivofQ5Xjo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HMP0JftKrB8+MEstHYUXe8WJ+PHJrk52D8qHMn9luIzRPajQlx5/XVZy3TCnJoUUl mohNUXhahyF53l1s3bszaIjJC1N0bD21/32JFCOauFvXdWZaWWyr+gyuNLOvHnoJhT WyibssYseAGxTDRatUDM2mJ1tIvz5mPWoxS3scmk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360268561; i=@resistor.net; bh=5MDWS6eXyMPhtyDN5xOOGRT9gLsLTqVrDVivofQ5Xjo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Uo9sAzlm7a+YNLD9BSnQMGms2QNP6IdlL70KQwSe9fxNgJP1VxTdNiOcwHDLzaGW+ 8ByHKqQUfULUk1VHRiYgjpmUBPs7HLUIGASf3VCo3K9c49H32FoEE8UvTc63JFgZOj vpObAXvqV8+iU03/9B1XmDtbYwsd4zmiCRtLmUkw=
Message-Id: <6.2.5.6.2.20130207113006.0ac46b78@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 07 Feb 2013 12:19:42 -0800
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
From: SM <sm@resistor.net>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
In-Reply-To: <5113F9DD.20406@rfc-editor.org>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <6.2.5.6.2.20130206224118.0b15d738@resistor.net> <5113F9DD.20406@rfc-editor.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 07 Feb 2013 20:22:54 -0000

Hi Heather,
At 11:00 07-02-2013, Heather Flanagan (RFC Series Editor) wrote:
>The format for the reference is what the RFC Editor suggests, but it
>hasn't been properly documented yet.  There is still open discussion
>about what the appropriate URL should be which in turn impacts that part
>of the reference.  Having errata as normative references does not seem
>like a good idea to me, so I'm glad to see it has been shifted to an
>informative reference.  I admit, I am unclear what you mean by turning
>Standard Track RFCs in to "living" standards; think the process for
>updating RFCs as new information is developed by creating new RFCs to
>update or obsolete the older ones is a perfectly reasonable approach.

It does not matter that the format for the reference has not been 
properly documented as long as you know about it as I know about it. :-)

There was a discussion about errata in September 2008.  The RFC 
Editor posted a message about errata.  If I am not mistaken the 
original idea wasn't about having an erratum as a reference.  I 
suggest having a discussion on the relevant mailing list about 
whether they should be used a references.

There is a message which mentions "living" standard at 
http://www.ietf.org/mail-archive/web/ietf/current/msg75085.html  and 
the W3C angle at http://www.w3.org/QA/2012/09/the_flowing_standard.html

>This has been an area of personal confusion for me as I try to
>understand IETF culture, but I'll leave discussing it to a bar BoF or
>something.

Well, BoFs are meetings in disguise, bar BoFs are the real BoFs. 
:-)  IETF culture is confusing for me too.  It is a bit about 
extracting sun-beams out of cucumbers.

Regards,
-sm 


From d3e3e3@gmail.com  Thu Feb  7 14:27:35 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7FA21F841E for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 14:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.352
X-Spam-Level: 
X-Spam-Status: No, score=-103.352 tagged_above=-999 required=5 tests=[AWL=0.247, 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 jCAmQGZYCtb1 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 14:27:34 -0800 (PST)
Received: from mail-ob0-f171.google.com (mail-ob0-f171.google.com [209.85.214.171]) by ietfa.amsl.com (Postfix) with ESMTP id C71E121F8206 for <ietf@ietf.org>; Thu,  7 Feb 2013 14:27:34 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id x4so3155612obh.30 for <ietf@ietf.org>; Thu, 07 Feb 2013 14:27:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=7dz8NKmO6m9PGGSmE0jylTLZ7CqYIvAwteheOyotpLU=; b=PibFVOM8knbmBEb8QYmzdtHv1wK4wTNNsEuUuGYz42kaFdjFcChTQPMbSOL0T1khCP ODAO+pM2ta6xc2WL2Jc3WVkgzFWbibC1Jt474A3rG5lYzro3NhZOjcrFxRSJtLeCt8Qa YyIIRqeDByhX+yhGFUpy9CHsRCCUSR1Yt9a3X+VMvVy7ag+hPaKKugqVLLxT2sLV1Lga pvhUM/9jp1p91UPPK00vPiHpVtgSbrG9qeGsTCOAZpUVyHyVAxyJKgAZudbztIz+xhjs 3X7mWfXWYLgB8RF1V5IrFeKESX00+TVkGht2GYuZt+l1WCnlUOQJZYkA+HJdVaMbp2x1 tQ9A==
X-Received: by 10.60.30.38 with SMTP id p6mr2534699oeh.2.1360276054169; Thu, 07 Feb 2013 14:27:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Thu, 7 Feb 2013 14:27:13 -0800 (PST)
In-Reply-To: <1CB2E0B458B211478C85E11A404A2B270190A4C6@008-AM1MPN1-033.mgdnok.nokia.com>
References: <3679302F-114B-4319-B351-14DC3F813859@nokia.com> <1CB2E0B458B211478C85E11A404A2B270190A4C6@008-AM1MPN1-033.mgdnok.nokia.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 7 Feb 2013 17:27:13 -0500
Message-ID: <CAF4+nEHfd9DyG3urgPDvJMB+8Ys8oyf+4Jd02YO1BCUYz6UEJA@mail.gmail.com>
Subject: Re: IMPORANT: Comments on draft-eastlake-additional-xmlsec-uris-08
To: Frederick.Hirsch@nokia.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Feb 2013 22:27:35 -0000

Hi Frederick,

On Thu, Feb 7, 2013 at 4:24 PM,  <Frederick.Hirsch@nokia.com> wrote:
> Don
>
> I've received feedback from XML Security working group members that propo=
se you change the URIs in the draft RFC for AES Key Wrap with Padding to ma=
tch what is in XML Encryption 1.1, both because we are going to Recommendat=
ion and because there is code that currently uses those values.
>
> Can you please make the change, using the xmlenc11 URIs I listed below in=
 item 1?

Sure, I'll do that.

> Thanks
> regards, Frederick
>
> Frederick Hirsch
> Nokia
>
>
> On Feb 7, 2013, at 11:04 AM,  wrote:
>
>> Donald
>>
>> Some additional comments on draft http://tools.ietf.org/pdf/draft-eastla=
ke-additional-xmlsec-uris-08.pdf
>>
>> sorry about the delay getting these comments to you.
>>
>> (1) We have defined different *informative* URIs for AES Key Wrap with P=
adding in XML Encryption 1.1 [http://www.w3.org/TR/xmlenc-core1/#sec-kw-aes=
-with-pad] which are different from those in the RFC, namely
>>
>> http://www.w3.org/2009/xmlenc11#kw-aes-128-pad
>> http://www.w3.org/2009/xmlenc11#kw-aes-192-pad
>> http://www.w3.org/2009/xmlenc11#kw-aes-256-pad
>>
>> I suggest we change this informative appendix of XML Encryption 1.1 (and=
 the Security Algorithms Cross-Reference) to match what is in the RFC draft=
. Thomas, is there any problem with that at this PR stage?
>>
>> Those in the RFC draft are:
>>
>> http://www.w3.org/2007/05/xmldsig-more#kw-aes128-pad
>> http://www.w3.org/2007/05/xmldsig-more#kw-aes192-pad
>> http://www.w3.org/2007/05/xmldsig-more#kw-aes256-pad

As above, I'll change the draft to use the ...//2009/xmlenc11#... URIs.

>> (2) ConcatKDF fragment needs fixing in 4.1 and change log Appendix A due=
 to a typo
>>
>> "2009/xmlenc11#ConctKDF [XMLENC]" should be "2009/xmlenc11#ConcatKDF [XM=
LENC]"
>>
>> "#ConctKDF," should be "#ConcatKDF,"

OK.

>> (3) To some degree the fragment index and URI index replicate the publis=
hed W3C Note, XML Security Algorithm Cross-Reference and could be incorpora=
ted there.

If you would like to incorporate this information there, that seems
fine. But I'd like to leave it in the draft also.

>> (4) I suggest an update to the Introduction to mention XML Security 1.1 =
as follows
>>
>> after "All of these standards and recommendations use URIs [RFC3986] to =
identify algorithms and keying information types."
>>
>> add
>>
>> "The W3C has subsequently produced updated  XML Signature 1.1  [XMLDSIG1=
1] and XML Encryption 1.1 [XMLENC11} versions as well as a new XML Signatur=
e Properties specification [XMLDSIG-PROPERTIES].

OK.

>> (5) Typo in introduction
>>
>> "Canoncialization" should be "Canonicalization"

OK.

>> (6) References
>>
>> Add references to XML Signature 1.1, XML Encryption 1.1, XML Signature P=
roperties, XML Security Algorithm Cross-Reference (all to be updated upon R=
ecommendation publication)

The current draft does have references to XML Signature 1.1 and XML
Encryption 1.1. The RFC Reference format permits multiple document
under a single tag and both 1.0 and 1.1 are included under the
[XMLDSIG] and [XMLENC] tags.

I'll add the other two documents.

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

>> Signature properties has added a namespace: xmlns dsp=3D"http://www.w3.o=
rg/2009/xmldsig-properties"
>>
>> [XMLDSIG-CORE1]
>> D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. XML Sig=
nature Syntax and Processing Version 1.1. 24 January 2013. W3C Proposed Rec=
ommendation. (Work in progress) URL:http://www.w3.org/TR/2013/PR-xmldsig-co=
re1-20130124/
>>
>> [XMLENC-CORE1]
>> J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. XML Encryption Syntax an=
d Processing Version 1.1. 24 January 2013. W3C Proposed Recommendation. (Wo=
rk in progress) URL:http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/
>>
>> [XMLDSIG-PROPERTIES]
>> Frederick Hirsch. XML Signature Properties. 24 January 2013. W3C Propose=
d Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2013/PR-xml=
dsig-properties-20130124/
>>
>> [XMLSEC-ALGS] F Hirsch, T Roessler, K Yiu XML Security Algorithm Cross-R=
eference, 24 January 2013 W3C Working Group Note http://www.w3.org/TR/2013/=
NOTE-xmlsec-algorithms-20130124/
>>
>>
>> regards, Frederick
>>
>> Frederick Hirsch, Nokia
>> Chair XML Security WG

From sm@resistor.net  Thu Feb  7 17:44:14 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 751181F0D09 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 17:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G+eAMEt6sfEY for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 17:44:13 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 400501F0CFF for <ietf@ietf.org>; Thu,  7 Feb 2013 17:44:12 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r181huQv020049; Thu, 7 Feb 2013 17:43:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360287844; bh=lYHPbPiGZNanWoRe7usiZpvFvjJ+bt0m7tOVBUX7eZ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k2m1qyUTtY8GYFMv+wHXNLfR9Em+1YEDSYR+9/jfovO2AhHEuw1TpG4YqyPLWPI1E TRiZSxirHGt336ifPONV2I9qhhmTHbTFsAwhG13fsV/gnfktZqCPu1Ncjpci99XAjN nS4Y2yveaCUFtB+QgbF7+INUO8OcZjd09uuvhxAs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360287844; i=@resistor.net; bh=lYHPbPiGZNanWoRe7usiZpvFvjJ+bt0m7tOVBUX7eZ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HPxA74tJhHtW28yr86cdeQjFqReDbQ29fpAQPRCtg7808pyvqL5xsuOlTPY4zO8fd QRs7SSnWR7rq5dJdzopK7JkgfrPJ0AoSOLwJqtFx3ZOGiVWrV7l9gjmy2W9EXWjymP 6q5OaQDbSKJlAKj9zMxnSvIOcLk+ACtjLjNeDhFk=
Message-Id: <6.2.5.6.2.20130207173122.09a265f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 07 Feb 2013 17:41:48 -0800
To: Donald Eastlake <d3e3e3@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
In-Reply-To: <CAF4+nEFpZChc8sRE=uEEd4zYMd0jzZqn7rJ7sBSxR6OtosGGSQ@mail.g mail.com>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <6.2.5.6.2.20130206224118.0b15d738@resistor.net> <CAF4+nEFpZChc8sRE=uEEd4zYMd0jzZqn7rJ7sBSxR6OtosGGSQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 08 Feb 2013 01:44:14 -0000

Hi Donald,
At 07:37 07-02-2013, Donald Eastlake wrote:
>As I say, although I frequently put them near the front of my Internet
>Drafts, the RFC Editor always moves them to the end.

I understood. :-)

>they ask not to be listed. Anyway, my practice is not because anyone
>has asked to be listed nearer the beginning of the document but
>because I think they deserve to be so listed.

I like the practice.

>Well, I could rename Section 5 to be "Allocation Considerations" and
>provide two subsection, one "5.1 IANA Considerations" and one "5.2 W3C
>Allocation Considerations" or the like and perhaps also move some of
>the material at the beginning of Section 2 down to 5.2.

The IANA Considerations will be removed on publication.  You could 
move it to 5.2 and do the above.

>RFC4648 is Informational, so that would cause yet another downref. RFC
>2045 has not bee obsoleted and seems fine to me for this purpose.

I forgot about the Informational status.  It's easier to avoid the down-ref.

Regards,
-sm 


From narten@us.ibm.com  Thu Feb  7 21:53:10 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 075A621F88FB for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 21:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.449
X-Spam-Level: 
X-Spam-Status: No, score=-109.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sheh5u+hcDDg for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 21:53:09 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 2502F21F88C8 for <ietf@ietf.org>; Thu,  7 Feb 2013 21:53:09 -0800 (PST)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 8 Feb 2013 00:53:07 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 8 Feb 2013 00:53:05 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 16BA9C9001A for <ietf@ietf.org>; Fri,  8 Feb 2013 00:53:05 -0500 (EST)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r185r4HA262392 for <ietf@ietf.org>; Fri, 8 Feb 2013 00:53:04 -0500
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 r185tRcF008947 for <ietf@ietf.org>; Thu, 7 Feb 2013 22:55:27 -0700
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 r185tQ5B008935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 7 Feb 2013 22:55:27 -0700
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 r185r24N010855 for <ietf@ietf.org>; Fri, 8 Feb 2013 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r185r2Nt010810 for ietf@ietf.org; Fri, 8 Feb 2013 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201302080553.r185r2Nt010810@rotala.raleigh.ibm.com>
Date: Fri, 08 Feb 2013 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13020805-5806-0000-0000-00001F562724
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 05:53:10 -0000

Total of 78 messages in the last 7 days.
 
script run at: Fri Feb  8 00:53:02 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.26% |    8 |  9.28% |    58558 | sm@resistor.net
  6.41% |    5 |  7.15% |    45081 | barryleiba@computer.org
  6.41% |    5 |  6.86% |    43280 | daedulus@btconnect.com
  6.41% |    5 |  5.23% |    33011 | abdussalambaryun@gmail.com
  2.56% |    2 |  6.54% |    41242 | spromano@unina.it
  3.85% |    3 |  4.61% |    29101 | d3e3e3@gmail.com
  2.56% |    2 |  4.44% |    28009 | huawei.danli@huawei.com
  2.56% |    2 |  4.13% |    26062 | lufang@cisco.com
  3.85% |    3 |  2.75% |    17338 | joelja@bogus.com
  3.85% |    3 |  2.52% |    15871 | nick@inex.ie
  2.56% |    2 |  2.71% |    17085 | ietf@shaftek.org
  2.56% |    2 |  2.47% |    15590 | john-ietf@jck.com
  2.56% |    2 |  2.33% |    14725 | lberger@labn.net
  2.56% |    2 |  2.23% |    14074 | narten@us.ibm.com
  2.56% |    2 |  2.22% |    14036 | lear@cisco.com
  2.56% |    2 |  2.17% |    13701 | derhoermi@gmx.net
  2.56% |    2 |  2.16% |    13597 | lixia@cs.ucla.edu
  2.56% |    2 |  2.08% |    13095 | swb@internet2.edu
  2.56% |    2 |  2.02% |    12744 | hartmans-ietf@mit.edu
  2.56% |    2 |  1.95% |    12291 | mcr+ietf@sandelman.ca
  2.56% |    2 |  1.80% |    11341 | dhc@dcrocker.net
  2.56% |    2 |  1.63% |    10265 | randy@psg.com
  1.28% |    1 |  2.71% |    17127 | david.black@emc.com
  1.28% |    1 |  2.22% |    14000 | chair@ietf.org
  1.28% |    1 |  1.73% |    10887 | ron.even.tlv@gmail.com
  1.28% |    1 |  1.57% |     9928 | rlb@ipv.sx
  1.28% |    1 |  1.31% |     8254 | frederick.hirsch@nokia.com
  1.28% |    1 |  1.30% |     8187 | housley@vigilsec.com
  1.28% |    1 |  1.11% |     7016 | weiler@watson.org
  1.28% |    1 |  1.09% |     6848 | marc.blanchet@viagenie.ca
  1.28% |    1 |  1.08% |     6791 | hsantos@isdg.net
  1.28% |    1 |  1.03% |     6517 | mary.ietf.barnes@gmail.com
  1.28% |    1 |  0.98% |     6156 | paul.hoffman@vpnc.org
  1.28% |    1 |  0.94% |     5952 | julian.reschke@gmx.de
  1.28% |    1 |  0.93% |     5885 | dougb@dougbarton.us
  1.28% |    1 |  0.92% |     5814 | melinda.shore@gmail.com
  1.28% |    1 |  0.91% |     5764 | rbarnes@bbn.com
  1.28% |    1 |  0.89% |     5639 | ajs@anvilwalrusden.com
--------+------+--------+----------+------------------------
100.00% |   78 |100.00% |   630862 | Total


From rdroms.ietf@gmail.com  Fri Feb  8 07:53:32 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 525A821F8AB2; Fri,  8 Feb 2013 07:53:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.524
X-Spam-Level: 
X-Spam-Status: No, score=-103.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 JcCMYRUEytum; Fri,  8 Feb 2013 07:53:31 -0800 (PST)
Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by ietfa.amsl.com (Postfix) with ESMTP id 963AD21F86B6; Fri,  8 Feb 2013 07:53:31 -0800 (PST)
Received: by mail-ve0-f171.google.com with SMTP id b10so3445547vea.30 for <multiple recipients>; Fri, 08 Feb 2013 07:53:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=D3Usc/mLeKiH/8tN4PSKsOOjRIc2Pus8nilMc5q437k=; b=DGXSRNUFo9eWJxma7EyUIcundmxY5SBh+NOsfEkStAI3siPT5x+x1B4RR5haxq96dN 6snt75n7xIK8x8Eq5ZTAaqp5KrPBwoicpMTCqFE+ji3NUF0Q5Nz+TrHkYv1y9Kd0d/bD 5uRSWjkIHEVQ7Zq0jQGV5DTGw7IM60nR+eSjZW0abt/4ZL3vyFmM/1RT5iAhNKtqqFmz AHYa2qgKPs6hmKls6BA52iLqkSAANVKT0PP71e5JP+L6DyEQ2SvBucmmzACDf25lSrL5 CVrGdTuVA9TtKAKUE9mqLibf+IcwY7W/Hh9VG+4M7ftdCR+yFmXpe0Lmqe/k6Jxojaiq IR9A==
X-Received: by 10.220.154.66 with SMTP id n2mr7174195vcw.40.1360338811008; Fri, 08 Feb 2013 07:53:31 -0800 (PST)
Received: from ?IPv6:2001:420:2481:20:c9a8:311a:e6bb:eecc? ([2001:420:2481:20:c9a8:311a:e6bb:eecc]) by mx.google.com with ESMTPS id x9sm43976493vel.4.2013.02.08.07.53.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 07:53:30 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [ANCP] Last Call: <draft-ietf-ancp-pon-04.txt> (Applicability of Access Node	Control Mechanism to PON based Broadband Networks) to Informational RFC
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <20130205205722.8063.36744.idtracker@ietfa.amsl.com>
Date: Fri, 8 Feb 2013 10:53:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <541553B6-3033-421A-BA1C-368AA849DAC7@gmail.com>
References: <20130205205722.8063.36744.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1499)
Cc: ancp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 15:53:32 -0000

Note that this last call is a second last call, to gather comments on =
the publication of the document considering the IPR disclosures that =
were published late in the previous IETF last call.

- Ralph

On Feb 5, 2013, at 3:57 PM 2/5/13, The IESG <iesg-secretary@ietf.org> =
wrote:

>=20
> The IESG has received a request from the Access Node Control Protocol =
WG
> (ancp) to consider the following document:
> - 'Applicability of Access Node Control Mechanism to PON based =
Broadband
>   Networks'
>  <draft-ietf-ancp-pon-04.txt> as Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-19. 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
>     The purpose of this document is to provide applicability of the
>     Access Node Control mechanism to PON-based broadband access. The
>     need for an Access Node Control mechanism between a Network
>     Access Server (NAS) and an Access Node Complex (a combination of
>     Optical Line Termination (OLT) and Optical Network Termination
>     (ONT) elements) is described in a multi-service reference
>     architecture in order to perform QoS-related, service-related and
>     Subscriber-related operations. The Access Node Control mechanism
>     is also extended for interaction between components of the Access
>     Node Complex (OLT and ONT). The Access Node Control mechanism
>     will ensure that the transmission of information between the NAS
>     and Access Node Complex (ANX) and between the OLT and ONT within
>     an ANX does not need to go through distinct element managers but
>     rather uses a direct device-to-device communication and stays on
>     net. This allows for performing access link related operations
>     within those network elements to meet performance objectives.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   http://datatracker.ietf.org/ipr/1734/
>=20
>=20
>=20
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp


From rse@rfc-editor.org  Thu Feb  7 11:00:51 2013
Return-Path: <rse@rfc-editor.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 9A0DC21F875F for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 11:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ou-uOU8ncXXS for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 11:00:50 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id A415C21F86FB for <ietf@ietf.org>; Thu,  7 Feb 2013 11:00:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id EB67C1262FB; Thu,  7 Feb 2013 11:00:46 -0800 (PST)
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 c-YhCD5PB6KF; Thu,  7 Feb 2013 11:00:46 -0800 (PST)
Received: from Heathers-MacBook-Pro.local (unknown [98.125.190.183]) by c8a.amsl.com (Postfix) with ESMTPSA id 6A8331262F2; Thu,  7 Feb 2013 11:00:46 -0800 (PST)
Message-ID: <5113F9DD.20406@rfc-editor.org>
Date: Thu, 07 Feb 2013 11:00:45 -0800
From: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <6.2.5.6.2.20130206224118.0b15d738@resistor.net>
In-Reply-To: <6.2.5.6.2.20130206224118.0b15d738@resistor.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 08 Feb 2013 10:12:54 -0800
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.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, 07 Feb 2013 19:00:51 -0000

On 2/6/13 11:25 PM, SM wrote:
> Hi Donald,
> At 18:48 06-02-2013, Donald Eastlake wrote:
>> I'm not sure exactly what you mean here. The errata does appear in the
>> references  as
>>
>>    [Errata191] - RFC Errata, Errata ID 191, RFC 4051, http://www.rfc-
>>          editor.org
>>
>> I have been told by an Area Director that this it the format that the
>> RFC Editor likes. You can certainly find the Errata starting with that
>> link and by just linking to the main ref-editor.org web page, it does
>> not constrain the other structure of that web site.
>
> [Errata191] was a normative reference.  Referencing errata in an
> intended Proposed Standard might be a trivial matter.  There are side
> effects to that.  That may only be apparent in the long term.  I hope
> that the RFC Editor does not plan to turn Standard Track RFCs into
> "living" standards.
>
The format for the reference is what the RFC Editor suggests, but it
hasn't been properly documented yet.  There is still open discussion
about what the appropriate URL should be which in turn impacts that part
of the reference.  Having errata as normative references does not seem
like a good idea to me, so I'm glad to see it has been shifted to an
informative reference.  I admit, I am unclear what you mean by turning
Standard Track RFCs in to "living" standards; think the process for
updating RFCs as new information is developed by creating new RFCs to
update or obsolete the older ones is a perfectly reasonable approach.

>> OK. I will move the Errata to the Informational references.
>
> See above.
>
>> I disagree. I believe acknowledgments are very important and should be
>> at the front. I commonly (but not always) put them there in my drafts.
>> I am also not aware of any IETF rule prescribing where
>> Acknowledgements go in Internet Drafts. It is true that the RFC Editor
>> always move them to the end, but that's the way it goes.
>
> I noticed that you are one of the rare authors who has the
> Acknowledgements at the beginning of their document.  It was a
> practice followed in some of the three-digit RFCs.  There isn't any
> requirement in the RFC Style Guide which prohibits the
> Acknowledgements from being at the front of the document.

Since one of the broadest guidelines we work under states "make current
RFCs look like the previous ones", we do generally put the
Acknowledgements and Contributes towards the end of the document.   No,
it is not absolutely required but we do think it makes more sense.  The
guidance on section ordering is something that will be discussed as part
of the revised Style Guide.

>
> I don't know whether it is relevant but John Klensin mentioned this a
> few days ago:
>
>   "One might even suggest that one of the reasons early
>    ARPANET/ Internet developments worked better than the IETF
>    process of today is that there was wide recognition that it was
>    necessarily a collaborative effort with many people contributing
>    ideas and no one wanting to seize credit."
>

This has been an area of personal confusion for me as I try to
understand IETF culture, but I'll leave discussing it to a bar BoF or
something.

-Heather Flanagan, RSE

> Section 5 mentions that "This document requires no IANA actions". 
> However, there is another paragraph in the IANA Considerations section
> which is not even actionable by IANA folks.  I am not sure whether the
> text should go into that
> section.
>
> In Section 1:
>
>   "Note that raising XML Digital Signature to Draft Standard [RFC3275]
>    in the IETF required removal of any algorithms for which there was
>    not demonstrated interoperability from the Proposed Standard
>    document.  This required removal of the Minimal Canonicalization
>    algorithm, in which there appears to be continued interest. The URI
>    for Minimal Canonicalization was included in [RFC4051] and is
>    included here."
>
> That was the historic rationale for the different levels in the
> Standards Track.  Rumor has it that although the rationale was
> forgotten, whether intentionally or not, the "MUST" wars continued. 
> Dave Crocker once raised the question of complexity of a
> specification.  Advancement along the Standards could have been used
> to make a specification less complex by trimming stuff which has not
> been implemented (see quoted text above).
>
> In Section 2.1.1:
>
>
>   "The content of the DigestValue element shall be the base64 [RFC2045]
>    encoding of this bit string viewed as a 16-octet octet stream."
>
> RFC 4648 could be reference instead of RFC 2045.
>
> Regards,
> -sm
>
>


From Frederick.Hirsch@nokia.com  Thu Feb  7 13:24:54 2013
Return-Path: <Frederick.Hirsch@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CFEC21F88C8 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 13:24:54 -0800 (PST)
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 6MCWTgh8hdGB for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 13:24:53 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 541CD21F86AA for <ietf@ietf.org>; Thu,  7 Feb 2013 13:24:53 -0800 (PST)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-sa01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r17LOnU9021237; Thu, 7 Feb 2013 23:24:49 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.56]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 7 Feb 2013 23:24:49 +0200
Received: from 008-AM1MPN1-033.mgdnok.nokia.com ([169.254.3.155]) by 008-AM1MMR1-001.mgdnok.nokia.com ([65.54.30.56]) with mapi id 14.02.0318.003; Thu, 7 Feb 2013 21:24:47 +0000
From: <Frederick.Hirsch@nokia.com>
To: <d3e3e3@gmail.com>
Subject: IMPORANT: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Topic: IMPORANT: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Index: AQHOBXmOQN1lvM8iSkKXEQ8LZYxYOg==
Date: Thu, 7 Feb 2013 21:24:47 +0000
Message-ID: <1CB2E0B458B211478C85E11A404A2B270190A4C6@008-AM1MPN1-033.mgdnok.nokia.com>
References: <3679302F-114B-4319-B351-14DC3F813859@nokia.com>
In-Reply-To: <3679302F-114B-4319-B351-14DC3F813859@nokia.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.163.58.212]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FAEF769553E125468BB20555765929F2@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2013 21:24:49.0132 (UTC) FILETIME=[8F28CAC0:01CE0579]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 08 Feb 2013 10:12:54 -0800
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Frederick.Hirsch@nokia.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, 07 Feb 2013 21:24:54 -0000

Don

I've received feedback from XML Security working group members that propose=
 you change the URIs in the draft RFC for AES Key Wrap with Padding to matc=
h what is in XML Encryption 1.1, both because we are going to Recommendatio=
n and because there is code that currently uses those values.

Can you please make the change, using the xmlenc11 URIs I listed below in i=
tem 1?

Thanks

regards, Frederick

Frederick Hirsch
Nokia



On Feb 7, 2013, at 11:04 AM,  wrote:

> Donald=20
>=20
> Some additional comments on draft http://tools.ietf.org/pdf/draft-eastlak=
e-additional-xmlsec-uris-08.pdf
>=20
> sorry about the delay getting these comments to you.
>=20
> (1) We have defined different *informative* URIs for AES Key Wrap with Pa=
dding in XML Encryption 1.1 [http://www.w3.org/TR/xmlenc-core1/#sec-kw-aes-=
with-pad] which are different from those in the RFC, namely
>=20
> http://www.w3.org/2009/xmlenc11#kw-aes-128-pad
>=20
> http://www.w3.org/2009/xmlenc11#kw-aes-192-pad
>=20
> http://www.w3.org/2009/xmlenc11#kw-aes-256-pad
>=20
> I suggest we change this informative appendix of XML Encryption 1.1 (and =
the Security Algorithms Cross-Reference) to match what is in the RFC draft.=
 Thomas, is there any problem with that at this PR stage?
>=20
> Those in the RFC draft are:
>=20
> http://www.w3.org/2007/05/xmldsig-more#kw-aes128-pad=20
>=20
> http://www.w3.org/2007/05/xmldsig-more#kw-aes192-pad=20
>=20
> http://www.w3.org/2007/05/xmldsig-more#kw-aes256-pad
>=20
> (2) ConcatKDF fragment needs fixing in 4.1 and change log Appendix A due =
to a typo
>=20
> "2009/xmlenc11#ConctKDF [XMLENC]" should be "2009/xmlenc11#ConcatKDF [XML=
ENC]"
>=20
> "#ConctKDF," should be "#ConcatKDF,"
>=20
> (3) To some degree the fragment index and URI index replicate the publish=
ed W3C Note, XML Security Algorithm Cross-Reference and could be incorporat=
ed there.
>=20
> (4) I suggest an update to the Introduction to mention XML Security 1.1 a=
s follows
>=20
> after "All of these standards and recommendations use URIs [RFC3986] to i=
dentify algorithms and keying information types."
>=20
> add
>=20
> "The W3C has subsequently produced updated  XML Signature 1.1  [XMLDSIG11=
] and XML Encryption 1.1 [XMLENC11} versions as well as a new XML Signature=
 Properties specification [XMLDSIG-PROPERTIES].
>=20
> (5) Typo in introduction
>=20
> "Canoncialization" should be "Canonicalization"
>=20
> (6) References
>=20
> Add references to XML Signature 1.1, XML Encryption 1.1, XML Signature Pr=
operties, XML Security Algorithm Cross-Reference (all to be updated upon Re=
commendation publication)
>=20
> Signature properties has added a namespace: xmlns dsp=3D"http://www.w3.or=
g/2009/xmldsig-properties"
>=20
> [XMLDSIG-CORE1]
> D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. XML Sign=
ature Syntax and Processing Version 1.1. 24 January 2013. W3C Proposed Reco=
mmendation. (Work in progress) URL:http://www.w3.org/TR/2013/PR-xmldsig-cor=
e1-20130124/
>=20
> [XMLENC-CORE1]
> J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. XML Encryption Syntax and=
 Processing Version 1.1. 24 January 2013. W3C Proposed Recommendation. (Wor=
k in progress) URL:http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/
>=20
> [XMLDSIG-PROPERTIES]
> Frederick Hirsch. XML Signature Properties. 24 January 2013. W3C Proposed=
 Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2013/PR-xmld=
sig-properties-20130124/
>=20
> [XMLSEC-ALGS] F Hirsch, T Roessler, K Yiu XML Security Algorithm Cross-Re=
ference, 24 January 2013 W3C Working Group Note http://www.w3.org/TR/2013/N=
OTE-xmlsec-algorithms-20130124/
>=20
>=20
> regards, Frederick
>=20
> Frederick Hirsch, Nokia
> Chair XML Security WG
>=20
>=20
>=20


From Frederick.Hirsch@nokia.com  Thu Feb  7 14:52:34 2013
Return-Path: <Frederick.Hirsch@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C6221F8200 for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 14:52:33 -0800 (PST)
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 d7nHkLvf3kBU for <ietf@ietfa.amsl.com>; Thu,  7 Feb 2013 14:52:33 -0800 (PST)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 07F1721F8203 for <ietf@ietf.org>; Thu,  7 Feb 2013 14:52:32 -0800 (PST)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da01.nokia.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r17MqTcK023641; Fri, 8 Feb 2013 00:52:30 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.47]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 8 Feb 2013 00:52:28 +0200
Received: from 008-AM1MPN1-033.mgdnok.nokia.com ([169.254.3.155]) by 008-AM1MMR1-013.mgdnok.nokia.com ([2002:4136:1e2f::4136:1e2f]) with mapi id 14.02.0318.003; Thu, 7 Feb 2013 22:52:28 +0000
From: <Frederick.Hirsch@nokia.com>
To: <d3e3e3@gmail.com>
Subject: Re: IMPORANT: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Topic: IMPORANT: Comments on draft-eastlake-additional-xmlsec-uris-08
Thread-Index: AQHOBXmOQN1lvM8iSkKXEQ8LZYxYOphu+ZqAgAAHAgA=
Date: Thu, 7 Feb 2013 22:52:28 +0000
Message-ID: <1CB2E0B458B211478C85E11A404A2B270190A785@008-AM1MPN1-033.mgdnok.nokia.com>
References: <3679302F-114B-4319-B351-14DC3F813859@nokia.com> <1CB2E0B458B211478C85E11A404A2B270190A4C6@008-AM1MPN1-033.mgdnok.nokia.com> <CAF4+nEHfd9DyG3urgPDvJMB+8Ys8oyf+4Jd02YO1BCUYz6UEJA@mail.gmail.com>
In-Reply-To: <CAF4+nEHfd9DyG3urgPDvJMB+8Ys8oyf+4Jd02YO1BCUYz6UEJA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [70.42.157.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <970A9BCFCD4ABC47BB7AC8999404AB0A@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 07 Feb 2013 22:52:28.0852 (UTC) FILETIME=[CE325F40:01CE0585]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Fri, 08 Feb 2013 10:12:54 -0800
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Frederick.Hirsch@nokia.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, 07 Feb 2013 22:52:34 -0000

Thanks Donald

I missed the fact that the references were combined.

Please let me know the RFC # and info I need to update the W3C documents as=
 soon as it is clear.

regards, Frederick

Frederick Hirsch
Nokia



On Feb 7, 2013, at 5:27 PM, ext Donald Eastlake wrote:

> Hi Frederick,
>=20
> On Thu, Feb 7, 2013 at 4:24 PM,  <Frederick.Hirsch@nokia.com> wrote:
>> Don
>>=20
>> I've received feedback from XML Security working group members that prop=
ose you change the URIs in the draft RFC for AES Key Wrap with Padding to m=
atch what is in XML Encryption 1.1, both because we are going to Recommenda=
tion and because there is code that currently uses those values.
>>=20
>> Can you please make the change, using the xmlenc11 URIs I listed below i=
n item 1?
>=20
> Sure, I'll do that.
>=20
>> Thanks
>> regards, Frederick
>>=20
>> Frederick Hirsch
>> Nokia
>>=20
>>=20
>> On Feb 7, 2013, at 11:04 AM,  wrote:
>>=20
>>> Donald
>>>=20
>>> Some additional comments on draft http://tools.ietf.org/pdf/draft-eastl=
ake-additional-xmlsec-uris-08.pdf
>>>=20
>>> sorry about the delay getting these comments to you.
>>>=20
>>> (1) We have defined different *informative* URIs for AES Key Wrap with =
Padding in XML Encryption 1.1 [http://www.w3.org/TR/xmlenc-core1/#sec-kw-ae=
s-with-pad] which are different from those in the RFC, namely
>>>=20
>>> http://www.w3.org/2009/xmlenc11#kw-aes-128-pad
>>> http://www.w3.org/2009/xmlenc11#kw-aes-192-pad
>>> http://www.w3.org/2009/xmlenc11#kw-aes-256-pad
>>>=20
>>> I suggest we change this informative appendix of XML Encryption 1.1 (an=
d the Security Algorithms Cross-Reference) to match what is in the RFC draf=
t. Thomas, is there any problem with that at this PR stage?
>>>=20
>>> Those in the RFC draft are:
>>>=20
>>> http://www.w3.org/2007/05/xmldsig-more#kw-aes128-pad
>>> http://www.w3.org/2007/05/xmldsig-more#kw-aes192-pad
>>> http://www.w3.org/2007/05/xmldsig-more#kw-aes256-pad
>=20
> As above, I'll change the draft to use the ...//2009/xmlenc11#... URIs.
>=20
>>> (2) ConcatKDF fragment needs fixing in 4.1 and change log Appendix A du=
e to a typo
>>>=20
>>> "2009/xmlenc11#ConctKDF [XMLENC]" should be "2009/xmlenc11#ConcatKDF [X=
MLENC]"
>>>=20
>>> "#ConctKDF," should be "#ConcatKDF,"
>=20
> OK.
>=20
>>> (3) To some degree the fragment index and URI index replicate the publi=
shed W3C Note, XML Security Algorithm Cross-Reference and could be incorpor=
ated there.
>=20
> If you would like to incorporate this information there, that seems
> fine. But I'd like to leave it in the draft also.
>=20
>>> (4) I suggest an update to the Introduction to mention XML Security 1.1=
 as follows
>>>=20
>>> after "All of these standards and recommendations use URIs [RFC3986] to=
 identify algorithms and keying information types."
>>>=20
>>> add
>>>=20
>>> "The W3C has subsequently produced updated  XML Signature 1.1  [XMLDSIG=
11] and XML Encryption 1.1 [XMLENC11} versions as well as a new XML Signatu=
re Properties specification [XMLDSIG-PROPERTIES].
>=20
> OK.
>=20
>>> (5) Typo in introduction
>>>=20
>>> "Canoncialization" should be "Canonicalization"
>=20
> OK.
>=20
>>> (6) References
>>>=20
>>> Add references to XML Signature 1.1, XML Encryption 1.1, XML Signature =
Properties, XML Security Algorithm Cross-Reference (all to be updated upon =
Recommendation publication)
>=20
> The current draft does have references to XML Signature 1.1 and XML
> Encryption 1.1. The RFC Reference format permits multiple document
> under a single tag and both 1.0 and 1.1 are included under the
> [XMLDSIG] and [XMLENC] tags.
>=20
> I'll add the other two documents.
>=20
> 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
>=20
>>> Signature properties has added a namespace: xmlns dsp=3D"http://www.w3.=
org/2009/xmldsig-properties"
>>>=20
>>> [XMLDSIG-CORE1]
>>> D. Eastlake, J. Reagle, D. Solo, F. Hirsch, T. Roessler, K. Yiu. XML Si=
gnature Syntax and Processing Version 1.1. 24 January 2013. W3C Proposed Re=
commendation. (Work in progress) URL:http://www.w3.org/TR/2013/PR-xmldsig-c=
ore1-20130124/
>>>=20
>>> [XMLENC-CORE1]
>>> J. Reagle; D. Eastlake; F. Hirsch; T. Roessler. XML Encryption Syntax a=
nd Processing Version 1.1. 24 January 2013. W3C Proposed Recommendation. (W=
ork in progress) URL:http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/
>>>=20
>>> [XMLDSIG-PROPERTIES]
>>> Frederick Hirsch. XML Signature Properties. 24 January 2013. W3C Propos=
ed Recommendation. (Work in progress.) URL: http://www.w3.org/TR/2013/PR-xm=
ldsig-properties-20130124/
>>>=20
>>> [XMLSEC-ALGS] F Hirsch, T Roessler, K Yiu XML Security Algorithm Cross-=
Reference, 24 January 2013 W3C Working Group Note http://www.w3.org/TR/2013=
/NOTE-xmlsec-algorithms-20130124/
>>>=20
>>>=20
>>> regards, Frederick
>>>=20
>>> Frederick Hirsch, Nokia
>>> Chair XML Security WG


From gtw@gtwassociates.com  Fri Feb  8 13:07:57 2013
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 4696221F8B66; Fri,  8 Feb 2013 13:07:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_82=0.6, 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 hdid8I8yBfVs; Fri,  8 Feb 2013 13:07:56 -0800 (PST)
Received: from mail2.primary.net (mail2.primary.net [216.87.38.218]) by ietfa.amsl.com (Postfix) with ESMTP id 9C8D021F8B61; Fri,  8 Feb 2013 13:07:56 -0800 (PST)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:53004 helo=GTWPC) by mail2.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1U3vAn-00073Q-OE; Fri, 08 Feb 2013 15:07:55 -0600
Message-ID: <BD570AAF4D284CC29F5A4BB287A4BA71@GTWPC>
From: "GTW" <gtw@gtwassociates.com>
To: "Ralph Droms" <rdroms.ietf@gmail.com>, <ietf@ietf.org>
References: <20130205205722.8063.36744.idtracker@ietfa.amsl.com> <541553B6-3033-421A-BA1C-368AA849DAC7@gmail.com>
In-Reply-To: <541553B6-3033-421A-BA1C-368AA849DAC7@gmail.com>
Subject: Re: [ANCP] Last Call: <draft-ietf-ancp-pon-04.txt> (Applicability ofAccess Node	Control Mechanism to PON based Broadband Networks)to Informational RFC
Date: Fri, 8 Feb 2013 16:07:47 -0500
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
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3505.912
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: ancp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: GTW <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: Fri, 08 Feb 2013 21:07:57 -0000

Ralph, for clarification ... is there more than the one IP disclosure at 
http://datatracker.ietf.org/ipr/1734/  ?


The term  "disclosures" lead me to believe there may be more than one

George T. Willingmyre, P.E.
President GTW Associates

-----Original Message----- 
From: Ralph Droms
Sent: Friday, February 08, 2013 10:53 AM
To: ietf@ietf.org
Cc: ancp@ietf.org
Subject: Re: [ANCP] Last Call:  (Applicability ofAccess Node Control 
Mechanism to PON based Broadband Networks)to Informational RFC

Note that this last call is a second last call, to gather comments on the 
publication of the document considering the IPR disclosures that were 
published late in the previous IETF last call.

- Ralph

On Feb 5, 2013, at 3:57 PM 2/5/13, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the Access Node Control Protocol WG
> (ancp) to consider the following document:
> - 'Applicability of Access Node Control Mechanism to PON based Broadband
>   Networks'
>  <draft-ietf-ancp-pon-04.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-19. 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 purpose of this document is to provide applicability of the
>     Access Node Control mechanism to PON-based broadband access. The
>     need for an Access Node Control mechanism between a Network
>     Access Server (NAS) and an Access Node Complex (a combination of
>     Optical Line Termination (OLT) and Optical Network Termination
>     (ONT) elements) is described in a multi-service reference
>     architecture in order to perform QoS-related, service-related and
>     Subscriber-related operations. The Access Node Control mechanism
>     is also extended for interaction between components of the Access
>     Node Complex (OLT and ONT). The Access Node Control mechanism
>     will ensure that the transmission of information between the NAS
>     and Access Node Complex (ANX) and between the OLT and ONT within
>     an ANX does not need to go through distinct element managers but
>     rather uses a direct device-to-device communication and stays on
>     net. This allows for performing access link related operations
>     within those network elements to meet performance objectives.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>   http://datatracker.ietf.org/ipr/1734/
>
>
>
> _______________________________________________
> ANCP mailing list
> ANCP@ietf.org
> https://www.ietf.org/mailman/listinfo/ancp


From rdroms.ietf@gmail.com  Fri Feb  8 13:10:50 2013
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 785A121F8C0C; Fri,  8 Feb 2013 13:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.253
X-Spam-Level: 
X-Spam-Status: No, score=-103.253 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, J_CHICKENPOX_82=0.6, 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 Q9EwD2zPKvGK; Fri,  8 Feb 2013 13:10:49 -0800 (PST)
Received: from mail-vc0-f181.google.com (mail-vc0-f181.google.com [209.85.220.181]) by ietfa.amsl.com (Postfix) with ESMTP id 95B2521F8C09; Fri,  8 Feb 2013 13:10:49 -0800 (PST)
Received: by mail-vc0-f181.google.com with SMTP id d16so2619244vcd.40 for <multiple recipients>; Fri, 08 Feb 2013 13:10:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:x-priority :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=IyR4q93L3crh7t0HVidxhcBSbPAFTS4W5A+5nX1KwbA=; b=RsQl32p/zdUpbj5535dPMiPh7NcJ/1nRVr8mVpRhPGyFTp8k2/R1llq3xAHkq2uaOD wvAonVJkJO5RyuCm1Hc+XJUJTWTuKLJjI+jCBR65qEjLTlIC2MoBTsd69zmpoAJU6lH3 tRCyOLtv85/OwAvuZqeHMd820yERY+9ztbrDh1u+GoLH0ANcEvAyg6w8qP4UdhNX44Dk niKuIOpva4vr07Eo3Op1qDqOEpBMLcQtcQ0eMYaZoFv+hq+GHGKN7MTVA7K6FV+dfVAd yyg1JXll4sRkLfwzbi6E/Rn1cniU3ooD6kKaoFQpdQzk/5jDo6a7qG4LhbfnTEHA+oVJ jjCg==
X-Received: by 10.52.27.50 with SMTP id q18mr7678760vdg.20.1360357848985; Fri, 08 Feb 2013 13:10:48 -0800 (PST)
Received: from ?IPv6:2001:420:2481:20:6126:183e:6d24:bff? ([2001:420:2481:20:6126:183e:6d24:bff]) by mx.google.com with ESMTPS id p20sm45822359vdj.6.2013.02.08.13.10.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 13:10:48 -0800 (PST)
Subject: Re: [ANCP] Last Call: <draft-ietf-ancp-pon-04.txt> (Applicability ofAccess Node	Control Mechanism to PON based Broadband Networks)to Informational RFC
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Ralph Droms <rdroms.ietf@gmail.com>
X-Priority: 3
In-Reply-To: <BD570AAF4D284CC29F5A4BB287A4BA71@GTWPC>
Date: Fri, 8 Feb 2013 16:10:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <705E4078-2C8E-4132-8F14-F7055D0E6166@gmail.com>
References: <20130205205722.8063.36744.idtracker@ietfa.amsl.com> <541553B6-3033-421A-BA1C-368AA849DAC7@gmail.com> <BD570AAF4D284CC29F5A4BB287A4BA71@GTWPC>
To: "GTW" <gtw@gtwassociates.com>
X-Mailer: Apple Mail (2.1499)
Cc: ancp@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, 08 Feb 2013 21:10:50 -0000

On Feb 8, 2013, at 4:07 PM 2/8/13, "GTW" <gtw@gtwassociates.com> wrote:

> Ralph, for clarification ... is there more than the one IP disclosure =
at http://datatracker.ietf.org/ipr/1734/  ?
>=20
>=20
> The term  "disclosures" lead me to believe there may be more than one

Good catch.  Typo on my part.  There is just the one disclosure.

- Ralph

>=20
> George T. Willingmyre, P.E.
> President GTW Associates
>=20
> -----Original Message----- From: Ralph Droms
> Sent: Friday, February 08, 2013 10:53 AM
> To: ietf@ietf.org
> Cc: ancp@ietf.org
> Subject: Re: [ANCP] Last Call:  (Applicability ofAccess Node Control =
Mechanism to PON based Broadband Networks)to Informational RFC
>=20
> Note that this last call is a second last call, to gather comments on =
the publication of the document considering the IPR disclosures that =
were published late in the previous IETF last call.
>=20
> - Ralph
>=20
> On Feb 5, 2013, at 3:57 PM 2/5/13, The IESG <iesg-secretary@ietf.org> =
wrote:
>=20
>>=20
>> The IESG has received a request from the Access Node Control Protocol =
WG
>> (ancp) to consider the following document:
>> - 'Applicability of Access Node Control Mechanism to PON based =
Broadband
>>  Networks'
>> <draft-ietf-ancp-pon-04.txt> as Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2013-02-19. 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
>>    The purpose of this document is to provide applicability of the
>>    Access Node Control mechanism to PON-based broadband access. The
>>    need for an Access Node Control mechanism between a Network
>>    Access Server (NAS) and an Access Node Complex (a combination of
>>    Optical Line Termination (OLT) and Optical Network Termination
>>    (ONT) elements) is described in a multi-service reference
>>    architecture in order to perform QoS-related, service-related and
>>    Subscriber-related operations. The Access Node Control mechanism
>>    is also extended for interaction between components of the Access
>>    Node Complex (OLT and ONT). The Access Node Control mechanism
>>    will ensure that the transmission of information between the NAS
>>    and Access Node Complex (ANX) and between the OLT and ONT within
>>    an ANX does not need to go through distinct element managers but
>>    rather uses a direct device-to-device communication and stays on
>>    net. This allows for performing access link related operations
>>    within those network elements to meet performance objectives.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-ancp-pon/ballot/
>>=20
>>=20
>> The following IPR Declarations may be related to this I-D:
>>=20
>>  http://datatracker.ietf.org/ipr/1734/
>>=20
>>=20
>>=20
>> _______________________________________________
>> ANCP mailing list
>> ANCP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ancp
>=20


From abdussalambaryun@gmail.com  Fri Feb  8 19:11:53 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 408C021F8C99 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.516
X-Spam-Level: 
X-Spam-Status: No, score=-3.516 tagged_above=-999 required=5 tests=[AWL=0.083,  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 WEpSB4VtidOI for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:11:52 -0800 (PST)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7B44C21F8C9E for <ietf@ietf.org>; Fri,  8 Feb 2013 19:11:52 -0800 (PST)
Received: by mail-wi0-f171.google.com with SMTP id hn17so1545609wib.16 for <ietf@ietf.org>; Fri, 08 Feb 2013 19:11:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=QpPnUGLrOV6M/wFyngDsZXWz0+BnpktHuK31N4iIJ/4=; b=M7vmVGw8dSMGJaPze5PU2a4uxv1GV891Rg9c1Evu4s60fTyQptsqlTPtMPnBvNsZIA ppbTOoOvM1RsqoqSgziGLCPhZYh3TdbVokuVq8QUNfEUK6ZEZgPseEjdp/9c7ZbFJzdQ e5l+u2a3b8R/iuYLkMWDe/anMJJvQn4Jr35k0JygK9TIBf0Xm/owsu5rzaW79FTJr8vd etaFxG0wKqqA0G593HKUF6szt/xVI56XWiFLuaKTA2n8bpud+fFvxv+jwwknwW6HNq9d oHbpRMlbEAxuBaegp4ZC6ZgnEijLksxgBuDGV/c8ZPgDBxkoQXwwmJ1YZ+xXHAfNmf/e ufcw==
MIME-Version: 1.0
X-Received: by 10.194.118.166 with SMTP id kn6mr13291695wjb.18.1360379511725;  Fri, 08 Feb 2013 19:11:51 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Fri, 8 Feb 2013 19:11:51 -0800 (PST)
Date: Sat, 9 Feb 2013 04:11:51 +0100
Message-ID: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
Subject: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 03:11:53 -0000

Hi folks,

 I am wondering how author/ietf-editor fill in the acknowledgement
section in the RFCs or I-Ds. Does it make sense in IETF, or left for
author opinion? I am getting requests from IETF WGs, IESG, and IAB for
comments. My question is do you *make acknowledgements* in I-Ds or
just *take comments* for I-Ds?

IMO we get last call request for comments because RFC production is
all about getting volunteering comments from Internet community to
make I-Ds better, so does all I-Ds acknowledge (ACK) to any input
comment before the last call and after or it is only before last
call?, and if it gets submitted to IESG/IAB, and we comment does that
have no ACK in I-D?

 I sometimes feel discouraged to participate in any world work if the
process does not involve my existance, just used with ignoring ACK of
the reviewers. IMO any comment has value to the authors (e.g. some
think only experts' comments are important to ACK) and to IETF,
otherwise, we may delete valuable ACKs in IETF, which is not right.

Best Regards

AB
A participant that still did not complete a year working for IETF, but
trying to continue :)

From d3e3e3@gmail.com  Fri Feb  8 19:36:46 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD22D21F8C4C for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:36:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.38
X-Spam-Level: 
X-Spam-Status: No, score=-103.38 tagged_above=-999 required=5 tests=[AWL=0.219, 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 PlBiZCoyTJ3T for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:36:46 -0800 (PST)
Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com [209.85.214.170]) by ietfa.amsl.com (Postfix) with ESMTP id 53CB921F8C2A for <ietf@ietf.org>; Fri,  8 Feb 2013 19:36:46 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id wc20so4612511obb.1 for <ietf@ietf.org>; Fri, 08 Feb 2013 19:36:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=ZqLpAbnz6WuinBRam/XdZSSKI/FKuZv5VoLfk4edDpg=; b=r+f9IVbRmvoFIvy4HAHgim32JZIYaiPMhZUuDfgCTBheek1q0ccMBkqbPWm7CZIkpC vpIdR5hxDqYMQjsy8VTJeCXxbe4v0T+7caRgU2Ue37hAncow3JMwwVw2udeHq4K9aPLw 2496KjpYLBc5+CuVt9jNSENvTreoBa2p+cwlnp00th29WZIH4C7lsncEuQav4AUXL3qO DK1Oy1rpyTRcrVKTKfef8mWAyiyJXul6Rdj1uUs8qIlGpUn12UJs6kiHaOjxFiCVBTCg ucOsB8ZeucmJ3LPJaMOzoDONbes2/S36e9vWSzAb7jrXsnZ8TJmh9iQD8Vph50SeBwOD 7k+w==
X-Received: by 10.60.32.147 with SMTP id j19mr5925887oei.68.1360381005835; Fri, 08 Feb 2013 19:36:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Fri, 8 Feb 2013 19:36:24 -0800 (PST)
In-Reply-To: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 8 Feb 2013 22:36:24 -0500
Message-ID: <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 03:36:47 -0000

I try to include in the Acknowledgements section of any Internet
Drafts I edit the names of anyone who comments on the draft if (1) the
comment results in a change in the draft and (2) the commenter does
not request that they be left out. If you comment on some draft and
the draft is changed as a result and you want to be acknowledged and
you are not added to the acknowledgements list, you should complain to
the editor / author.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Fri, Feb 8, 2013 at 10:11 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Hi folks,
>
>  I am wondering how author/ietf-editor fill in the acknowledgement
> section in the RFCs or I-Ds. Does it make sense in IETF, or left for
> author opinion? I am getting requests from IETF WGs, IESG, and IAB for
> comments. My question is do you *make acknowledgements* in I-Ds or
> just *take comments* for I-Ds?
>
> IMO we get last call request for comments because RFC production is
> all about getting volunteering comments from Internet community to
> make I-Ds better, so does all I-Ds acknowledge (ACK) to any input
> comment before the last call and after or it is only before last
> call?, and if it gets submitted to IESG/IAB, and we comment does that
> have no ACK in I-D?
>
>  I sometimes feel discouraged to participate in any world work if the
> process does not involve my existance, just used with ignoring ACK of
> the reviewers. IMO any comment has value to the authors (e.g. some
> think only experts' comments are important to ACK) and to IETF,
> otherwise, we may delete valuable ACKs in IETF, which is not right.
>
> Best Regards
>
> AB
> A participant that still did not complete a year working for IETF, but
> trying to continue :)

From melinda.shore@gmail.com  Fri Feb  8 19:42:07 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 355E921F8C2A for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GkiOE3zBLxq for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:42:06 -0800 (PST)
Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by ietfa.amsl.com (Postfix) with ESMTP id B5FBB21F8BE2 for <ietf@ietf.org>; Fri,  8 Feb 2013 19:42:06 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id bg4so2347068pad.26 for <ietf@ietf.org>; Fri, 08 Feb 2013 19:42:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Nb1nA7AEa6UWuCM8i7f3BS8BrjxoaG/Q4LuB+7Lov/E=; b=kfXD5W5zHlUn1HMERTGjFWwZRwSC1G49lzQ/5U219qxc3cOwVjHsiZ5l+7gYCJH8LW VAQ3cgEnda1d4suAp/xiY21OAYt6yWkmXdtJ/NpQUJW/R7icgFY5rxNFvG6WAEeay8We xvVLV5d7pFsXK+FYCOqE2pfjVTMswUqu7zXjwA9tT9k2mx35uSNa2HuN0rLTtCwxpfVm g1VnTMXA/ciLNe5NqXZiTI3oPH85sArpavo7s+1mrs2ysJTKcvXXpuykzlXF8CyAMHLs sHq4w9mu06AAE/aIjY2xqxcX70jYbu1Nl98wf0+mf7y8G2zidHfgHB8qjZQCq7/TkdEd sLEA==
X-Received: by 10.68.55.233 with SMTP id v9mr473720pbp.102.1360381326531; Fri, 08 Feb 2013 19:42:06 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id p6sm183006pbc.39.2013.02.08.19.42.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 19:42:05 -0800 (PST)
Message-ID: <5115C58A.4000209@gmail.com>
Date: Fri, 08 Feb 2013 18:42:02 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
In-Reply-To: <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 03:42:07 -0000

On 2/8/13 6:36 PM, Donald Eastlake wrote:
> I try to include in the Acknowledgements section of any Internet
> Drafts I edit the names of anyone who comments on the draft if (1) the
> comment results in a change in the draft and (2) the commenter does
> not request that they be left out. If you comment on some draft and
> the draft is changed as a result and you want to be acknowledged and
> you are not added to the acknowledgements list, you should complain to
> the editor / author.

Really?  I only expect to be acknowledged when I've got text
included or have made some other significant contribution.

Melinda


From john-ietf@jck.com  Fri Feb  8 19:55:14 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC0A021F8C87 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.67
X-Spam-Level: 
X-Spam-Status: No, score=-102.67 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 bEQYxtCsK7oS for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 19:55:13 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AD0CA21F8C85 for <ietf@ietf.org>; Fri,  8 Feb 2013 19:55:13 -0800 (PST)
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 1U41Wy-000NYn-Sf; Fri, 08 Feb 2013 22:55:12 -0500
Date: Fri, 08 Feb 2013 22:55:07 -0500
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: The RFC Acknowledgement
Message-ID: <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
In-Reply-To: <5115C58A.4000209@gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <5115C58A.4000209@gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 03:55:15 -0000

--On Friday, February 08, 2013 18:42 -0900 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 2/8/13 6:36 PM, Donald Eastlake wrote:
>> I try to include in the Acknowledgements section of any
>> Internet Drafts I edit the names of anyone who comments on
>> the draft if (1) the comment results in a change in the draft
>> and (2) the commenter does not request that they be left out.
>> If you comment on some draft and the draft is changed as a
>> result and you want to be acknowledged and you are not added
>> to the acknowledgements list, you should complain to the
>> editor / author.
> 
> Really?  I only expect to be acknowledged when I've got text
> included or have made some other significant contribution.

Remembering that we've managed to get ourselves into a situation
in which there is a IPR policy-based requirement for some
acknowledgements, do we really need to debate this topic rather
than saying "author/editor discretion as long as the author or
editor is sensitive to requests for inclusion or exclusion and
to the IPR policy requirements about substantive Contributions".

My personal instincts as an author run somewhat closer to
Melinda's criterion than to Don's but my bigger concern is that
trying to make specific rules about this will result in an
extended rat hole tour that ends up with rules that don't work
well for edge cases we don't anticipate.

   john






From abdussalambaryun@gmail.com  Fri Feb  8 19:56:37 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 311D621F8C8C; Fri,  8 Feb 2013 19:56:37 -0800 (PST)
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 tqoHJydj5f3D; Fri,  8 Feb 2013 19:56:36 -0800 (PST)
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2396421F8C85; Fri,  8 Feb 2013 19:56:35 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id 15so3381148wgd.28 for <multiple recipients>; Fri, 08 Feb 2013 19:56:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=uk/WSJ54rio7QZNjsykrsef4gBPC7gYp0dwy8w0Pg6k=; b=WNTDgu8KLKU+O9YPeqpPekDfO36hr4nGINT6FNBqBHzOYl/t/HFvro5tkNwvavuJwA But2taWD6yNMZ8FSJ/BWB39DtGLvmWrma1YzIrM4jfl/W3/Zk0UtiBJQk/kfmGn8Ir4S guRoQaC+NwpE0I2btY786j4SwDrlyzSV/TYJgNoeWQtjIykdA/Icabjl6cmxhwfno9Y2 F5W1sC53heYnbs5HUDXHqMiByaf/wvlyV/mtV46bKQHYzZ/InczjUEGcdwksT491a/id 1Bxabcvx0rpYHyiCsNpgkrVTW2ujCxclZbofsIDarUeNWDcFgeVVlBaDfUSMi3uY6Dz4 kz7g==
MIME-Version: 1.0
X-Received: by 10.194.109.102 with SMTP id hr6mr13339262wjb.24.1360382195170;  Fri, 08 Feb 2013 19:56:35 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Fri, 8 Feb 2013 19:56:35 -0800 (PST)
Date: Sat, 9 Feb 2013 04:56:35 +0100
Message-ID: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com>
Subject: I-D affects another or work in ietf groups
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Feb 2013 03:56:37 -0000

Hi folks,

Related to one discussion with a participant about I-Ds affecting WGs,
I have a question after reading two real incidents. The following two
work process examples are to show the I-Ds/RFCs affects from
participants point of view;

1) I got an understanding from one expert participant that his I-D is
not related to one RFC, even though it does involve similar objectives
and use-case, which was strange to me. So I understood from him that
his I-D is not affected by that RFC, even though his I-D does not
mention to exclude that RFC. IMO, I disagree with such producing I-D
by separate review-approach unaffected by other related RFCs (i.e. not
mentioned RFCs).

2) While I was discussing within a WG about an I-D which is a second
version of one IETF prorocol, some participants thought that the I-D
obsolete the old version even if not mentioned in the I-D. It then was
requested to update and mention that it does not obsolete the older
version. New versions are related and can affect each other, or affect
people understanding, which requires more careful presentation for
such I-D.

I beleive that we have one source of producing RFCs, so all I-Ds and
RFCs are related some how, and they affect each other. So when I
review an item, I always like to consider all RFCs as much as I can to
make Internet better.

Is that approach right for review? please advise,

AB

From abdussalambaryun@gmail.com  Fri Feb  8 20:04:10 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E94CC21F8A4F for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLr5ZdNS2new for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:04:10 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 321C521F8886 for <ietf@ietf.org>; Fri,  8 Feb 2013 20:04:10 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id x8so3628120wey.34 for <ietf@ietf.org>; Fri, 08 Feb 2013 20:04:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=bpcAl1DcTAskHVZx/JWwc7lJoQUHS9FjJaabt+AA2u8=; b=R4LuwJJNXeL5dVrCTHb5TNLENsUbDRPduuGU4CYmcYQE08vyjfmIe/li4utfJr8ViM mY3ZnVWpoOaF3wxa1Az37t0cXpUZOqQc9iNHYUnj4Z1MK/nBdMcPq5CnjwquKst6TkRR VN2Hl/sRO0X9pHXSo7grskKSYbgVjWcjc9Vba8f/90MMvxuNDgceKKyqs/dMUy7C9AI1 W60srxpJEH4SYT0iSju6KOyv0HliBk9uvZNntnhyrDy4OPIxZnR3f5ztai+RrU1kOcPm Qt0JinBYQQeEBQE7CJF8OSoJJceazN2jXzFLPncmW7nKBigeaCCmBnoxsvRpyaBuRLDy AEUg==
MIME-Version: 1.0
X-Received: by 10.180.73.80 with SMTP id j16mr6016015wiv.5.1360382649355; Fri, 08 Feb 2013 20:04:09 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Fri, 8 Feb 2013 20:04:09 -0800 (PST)
In-Reply-To: <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
Date: Sat, 9 Feb 2013 05:04:09 +0100
Message-ID: <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 04:04:11 -0000

Hi Donald,

The problem is that most people don't complain or don't like to
complain, that is reality, they will leave such society easily. So
does the IETF have some kind of self check without the commentor
complaining. I suggest the WG chair to maintain the WG I-Ds, and if
individual I-D then the AD responsible to maintain that,

AB

On 2/9/13, Donald Eastlake <d3e3e3@gmail.com> wrote:
> I try to include in the Acknowledgements section of any Internet
> Drafts I edit the names of anyone who comments on the draft if (1) the
> comment results in a change in the draft and (2) the commenter does
> not request that they be left out. If you comment on some draft and
> the draft is changed as a result and you want to be acknowledged and
> you are not added to the acknowledgements list, you should complain to
> the editor / author.
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Fri, Feb 8, 2013 at 10:11 PM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>> Hi folks,
>>
>>  I am wondering how author/ietf-editor fill in the acknowledgement
>> section in the RFCs or I-Ds. Does it make sense in IETF, or left for
>> author opinion? I am getting requests from IETF WGs, IESG, and IAB for
>> comments. My question is do you *make acknowledgements* in I-Ds or
>> just *take comments* for I-Ds?
>>
>> IMO we get last call request for comments because RFC production is
>> all about getting volunteering comments from Internet community to
>> make I-Ds better, so does all I-Ds acknowledge (ACK) to any input
>> comment before the last call and after or it is only before last
>> call?, and if it gets submitted to IESG/IAB, and we comment does that
>> have no ACK in I-D?
>>
>>  I sometimes feel discouraged to participate in any world work if the
>> process does not involve my existance, just used with ignoring ACK of
>> the reviewers. IMO any comment has value to the authors (e.g. some
>> think only experts' comments are important to ACK) and to IETF,
>> otherwise, we may delete valuable ACKs in IETF, which is not right.
>>
>> Best Regards
>>
>> AB
>> A participant that still did not complete a year working for IETF, but
>> trying to continue :)
>

From ned+ietf@mauve.mrochek.com  Fri Feb  8 20:05:02 2013
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 2FF2D21F8A64 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gkdp-K5UjjJT for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:05:01 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id B080D21F8886 for <ietf@ietf.org>; Fri,  8 Feb 2013 20:05:01 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OPYNT5TB1C008LP8@mauve.mrochek.com> for ietf@ietf.org; Fri, 8 Feb 2013 20:00:00 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OPEL6ZTPUO00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 8 Feb 2013 19:59:58 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OPYNT46WUA00008S@mauve.mrochek.com>
Date: Fri, 08 Feb 2013 19:55:54 -0800 (PST)
Subject: Re: The RFC Acknowledgement
In-reply-to: "Your message dated Fri, 08 Feb 2013 22:36:24 -0500" <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: ietf <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 04:05:02 -0000

> I try to include in the Acknowledgements section of any Internet
> Drafts I edit the names of anyone who comments on the draft if (1) the
> comment results in a change in the draft and (2) the commenter does
> not request that they be left out. If you comment on some draft and
> the draft is changed as a result and you want to be acknowledged and
> you are not added to the acknowledgements list, you should complain to
> the editor / author.

That's exactly the policy Nathaniel Borenstein and I agreed to use for MIME.
I've used it ever since for all the documents I have edited, and it seems to
have worked well. (And apologies to anyone whose name I have omitted under that
policy - if I did that it was entirely inadvertent.)

The only time I've ever had an acknowledgments section has been when an author
or contributor is deceased. This very unfortunate situation is quite delicate
and merits handling on a case-by-case basis; IMO no specific policy could
possibly be written to accomodate it.

				Ned

From melinda.shore@gmail.com  Fri Feb  8 20:12:38 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB1921F8815 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WQXFk1rWk1P for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:12:38 -0800 (PST)
Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) by ietfa.amsl.com (Postfix) with ESMTP id 2130D21F85CB for <ietf@ietf.org>; Fri,  8 Feb 2013 20:12:38 -0800 (PST)
Received: by mail-pb0-f49.google.com with SMTP id xa12so21355pbc.22 for <ietf@ietf.org>; Fri, 08 Feb 2013 20:12:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lgAhlXfrDMAK/dbVYu2NJs0wszMrO3bZq2RRNLkAVic=; b=yRPHRBaxAKZ14gHU5QSN83iJ81QcZ58rgX0Av9ZmmVVIpysGvq6YPQRbzIV4Vz582F b9iwjKPE1nW1qtoQiN6fFHa3ML1LhWmSGjvgKoXq2LU6eM3TOLE8y8otg9S5rQ8D1XbE /WnFxvWET6KnortwVfg/o12xLP6be5i2f4pgxeRzHrfDCQahRZrZxetOJ/jyZedvxXdl RJtfhX4yJucPYg6rl95AFHoRiD7S7qxmETQjU0xfG7Qrppaxi9OSvCzhkoKM5SxbnLau GkCK8srRc0hSngyPFj1KVXNXyTUGQrqy8x1idxuhBeYzlR3pujxTnCSAYjtJ2sWcOHro 01Mg==
X-Received: by 10.66.82.67 with SMTP id g3mr23785953pay.58.1360383157833; Fri, 08 Feb 2013 20:12:37 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id wx2sm258487pbc.42.2013.02.08.20.12.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 20:12:36 -0800 (PST)
Message-ID: <5115CCB2.2050201@gmail.com>
Date: Fri, 08 Feb 2013 19:12:34 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <5115C58A.4000209@gmail.com> <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
In-Reply-To: <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 04:12:39 -0000

On 2/8/13 6:55 PM, John C Klensin wrote:
> Remembering that we've managed to get ourselves into a situation
> in which there is a IPR policy-based requirement for some
> acknowledgements, do we really need to debate this topic rather
> than saying "author/editor discretion as long as the author or
> editor is sensitive to requests for inclusion or exclusion and
> to the IPR policy requirements about substantive Contributions".

That's my sense as well, and I think it makes a lot of sense
in terms of process/overhead to just leave it up to the
discretion of chairs and editors.  The notion of acknowledging every
single person who stepped up to the mic and made any comment, or
who posted to a mailing list, seems a bit over-the-top to me.

Melinda



From fred@cisco.com  Fri Feb  8 20:27:31 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56A721F8C7A; Fri,  8 Feb 2013 20:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.371
X-Spam-Level: 
X-Spam-Status: No, score=-110.371 tagged_above=-999 required=5 tests=[AWL=0.228, 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 V8T7GGrkRXB8; Fri,  8 Feb 2013 20:27:31 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1F40921F8C74; Fri,  8 Feb 2013 20:27:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2103; q=dns/txt; s=iport; t=1360384048; x=1361593648; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ykuZO7kJWrm48oT1ETlEc3ciS+5Tf38whk3mRt00a6g=; b=VcGF3Qw6txfjV8H9Z/tL3VABsz4gcjtqq/qng53tEULxVO+LE04/NSHe ll4juRJ4iiUomXReT6NOSCzNuGzFmqxUhpZqbt6BA2olwRj2caMOPPQEO cMkqo5HMNRdKypL8qIOqhQQNOuR8aylHy5Gj4dCpyDju+SgIWUIw0F7m5 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAPfPFVGtJXG8/2dsb2JhbABFwRgWc4IfAQEBAwFrDgULAgEIIiQhESUCBA4FCId3AwkGtSENiVuMFoRlYQOIMIwbjRmFE4MAgiQ
X-IronPort-AV: E=Sophos;i="4.84,632,1355097600"; d="scan'208";a="175166735"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 09 Feb 2013 04:27:17 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r194RH2e024858 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 9 Feb 2013 04:27:17 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.149]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Fri, 8 Feb 2013 22:27:17 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: I-D affects another or work in ietf groups
Thread-Topic: I-D affects another or work in ietf groups
Thread-Index: AQHOBnl90gJTUhFqfU2Cd/0ffumNHJhxUxyA
Date: Sat, 9 Feb 2013 04:27:16 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B77476D@xmb-rcd-x09.cisco.com>
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com>
In-Reply-To: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <EC645D414292F346ACFF685BD630997C@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 04:27:32 -0000

Speaking for myself, I would say that an internet draft is relevant to work=
 in a working group if and only if it is covered by the charter of the work=
ing group. Anyone can claim anything to dodge the requirement that they ask=
 relevant groups to review it. That doesn't make the claim true.

In the event that you need a ruling, I would suggest discussing it with the=
 relevant chairs and, if necessary, ADs. Generally speaking, they will have=
 no axe to grind and can give you a reasonably objective answer.

On Feb 8, 2013, at 7:56 PM, Abdussalam Baryun <abdussalambaryun@gmail.com> =
wrote:

> Hi folks,
>=20
> Related to one discussion with a participant about I-Ds affecting WGs,
> I have a question after reading two real incidents. The following two
> work process examples are to show the I-Ds/RFCs affects from
> participants point of view;
>=20
> 1) I got an understanding from one expert participant that his I-D is
> not related to one RFC, even though it does involve similar objectives
> and use-case, which was strange to me. So I understood from him that
> his I-D is not affected by that RFC, even though his I-D does not
> mention to exclude that RFC. IMO, I disagree with such producing I-D
> by separate review-approach unaffected by other related RFCs (i.e. not
> mentioned RFCs).
>=20
> 2) While I was discussing within a WG about an I-D which is a second
> version of one IETF prorocol, some participants thought that the I-D
> obsolete the old version even if not mentioned in the I-D. It then was
> requested to update and mention that it does not obsolete the older
> version. New versions are related and can affect each other, or affect
> people understanding, which requires more careful presentation for
> such I-D.
>=20
> I beleive that we have one source of producing RFCs, so all I-Ds and
> RFCs are related some how, and they affect each other. So when I
> review an item, I always like to consider all RFCs as much as I can to
> make Internet better.
>=20
> Is that approach right for review? please advise,
>=20
> AB


From fred@cisco.com  Fri Feb  8 20:31:29 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEC6D21F8419 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.362
X-Spam-Level: 
X-Spam-Status: No, score=-110.362 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BeuZ4QLs6o6 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 20:31:28 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 9ACBD21F8200 for <ietf@ietf.org>; Fri,  8 Feb 2013 20:31:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=705; q=dns/txt; s=iport; t=1360384288; x=1361593888; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=GhBLxkn0kWYvROYNEaB+5J/h1wycP6y5wZF3YmBaTho=; b=NwdH5c/jEmuj0X9O6tybDpetDkM2VCBBf7+AjgIF5FO0jrfcWmxP0Qob d5ZhbcQax/LaaiXdIxOvh8Qcj1yYeDjJyF8iDO8Q1vchTs3FNcc5rRTSl 6ot3GR3WUSOA/R7rZdul0C2hUEV6yZz1mVmVZ/RmjRFqYUtQgBcLOD29q 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An0FAEXQFVGtJXHA/2dsb2JhbABFhga7EhZzgh8BAQEDATo/BQsCAQgiFBAyJQIEDgUIiAMGvwmQe2EDpneDAIIk
X-IronPort-AV: E=Sophos;i="4.84,632,1355097600"; d="scan'208";a="175209075"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-4.cisco.com with ESMTP; 09 Feb 2013 04:31:28 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r194VSrT009956 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 9 Feb 2013 04:31:28 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.149]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.004; Fri, 8 Feb 2013 22:31:15 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: The RFC Acknowledgement
Thread-Topic: The RFC Acknowledgement
Thread-Index: AQHOBnM/FFQPWohiuE6oCEzaxzTuiZhxRPMAgAABkwCAAAOogIAAChUA
Date: Sat, 9 Feb 2013 04:31:14 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B77478C@xmb-rcd-x09.cisco.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <5115C58A.4000209@gmail.com> <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
In-Reply-To: <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E964530096ED854180D2BC10ECB00674@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 04:31:30 -0000

On Feb 8, 2013, at 7:55 PM, John C Klensin <john-ietf@jck.com> wrote:

> My personal instincts as an author run somewhat closer to
> Melinda's criterion than to Don's but my bigger concern is that
> trying to make specific rules about this will result in an
> extended rat hole tour that ends up with rules that don't work
> well for edge cases we don't anticipate.

Yes. I tend to acknowledge comments on a draft, and to separately acknowled=
ge comments that included text or which resulted in large changes - I do bo=
th Don and Melinda's algorithms. The important thing is, though, to be libe=
ral in what one includes, and to be conservative in the application of lega=
listic rules.=

From brian.e.carpenter@gmail.com  Fri Feb  8 23:49:17 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566D621F8C86 for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 23:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.768
X-Spam-Level: 
X-Spam-Status: No, score=-99.768 tagged_above=-999 required=5 tests=[AWL=-0.847, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghlzEZ8HFKVN for <ietf@ietfa.amsl.com>; Fri,  8 Feb 2013 23:49:17 -0800 (PST)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id ACC6921F89FC for <ietf@ietf.org>; Fri,  8 Feb 2013 23:49:16 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id l13so1737271wie.0 for <ietf@ietf.org>; Fri, 08 Feb 2013 23:49:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=54feOoRSGhY0C94Nwoc6vmJg0Cz/B+RGsUyJzU75vNo=; b=zfipmLaTtoumoylpjU3A4CXuF7B1L3hqhdNqK46cYdKSr1q5RscwC77+pIzq6fhQdf L2S1039LFcJsZyTAURDpLA1j/dzURS/1PRrD3NkBu1bJcl2wmtaXr8uGdSTVWj4Hotyn Q5c07jwt8gJ3cv96Tgoa7Zqg9fnA0I2xTpdLWY0foGIdEKQyPJkS/x3qe92U6S7BvWZf quWQIdSxazOHsd2gtZ6wPGELeKQed7nkuOpd6IL5IY/a2UCJDHyMPuIWs9axiXxuR4Sc 2RgXdez6m4kaIrMniOFnQEUPzRYX17gFrJDm0A4NVAtuJZnRKU0hgOVST82aPqDdubz3 jPVA==
X-Received: by 10.194.236.233 with SMTP id ux9mr11218272wjc.36.1360396155871;  Fri, 08 Feb 2013 23:49:15 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-25.as13285.net. [2.102.219.25]) by mx.google.com with ESMTPS id e12sm19700843wiw.5.2013.02.08.23.49.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 08 Feb 2013 23:49:15 -0800 (PST)
Message-ID: <5115FF85.2090002@gmail.com>
Date: Sat, 09 Feb 2013 07:49:25 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>	<CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com>	<5115C58A.4000209@gmail.com> <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
In-Reply-To: <C3199FD591BFEB0B6F14688E@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 07:49:17 -0000

On 09/02/2013 03:55, John C Klensin wrote:
...
> My personal instincts as an author run somewhat closer to
> Melinda's criterion than to Don's but my bigger concern is that
> trying to make specific rules about this will result in an
> extended rat hole tour that ends up with rules that don't work
> well for edge cases we don't anticipate.

In complete violation of the spirit of draft-resnick-on-consensus,
I will limit my comment to +1.

Can we discuss something technical, please?

    Brian

From eburger-l@standardstrack.com  Sat Feb  9 04:13:05 2013
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 723A521F86C3 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 04:13:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2nCFJv6+B--Y for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 04:13:04 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9C14221F85D7 for <ietf@ietf.org>; Sat,  9 Feb 2013 04:13:04 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:53317 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1U49Ia-0004aL-LN; Sat, 09 Feb 2013 04:12:52 -0800
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: The RFC Acknowledgement
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
Date: Sat, 9 Feb 2013 07:13:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3EDB772E-A3FE-403C-B5EE-2ED69F7FDDBA@standardstrack.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 12:13:05 -0000

Abduussalam -
You probably have seen many responses to your message talking about who =
goes into the Acknowledgements section. However, I am not sure your =
original question was answered.

In short, it is the document editor that puts the acknowledgments =
section in. In most cases it will be obvious who gets listed there. That =
is the substance of the other messages on this thread.  In rare cases a =
work group chair may get involved.

As you are new, if you are a document editor, you can always ask your =
work group chair for guidance. Conversely, if you feel you should be in =
an acknowledgements section for your contributions, feel free to talk =
with the document editor (first) and work group chair (second)
- Eric

On Feb 8, 2013, at 10:11 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi folks,
>=20
> I am wondering how author/ietf-editor fill in the acknowledgement
> section in the RFCs or I-Ds. Does it make sense in IETF, or left for
> author opinion? I am getting requests from IETF WGs, IESG, and IAB for
> comments. My question is do you *make acknowledgements* in I-Ds or
> just *take comments* for I-Ds?
>=20
> IMO we get last call request for comments because RFC production is
> all about getting volunteering comments from Internet community to
> make I-Ds better, so does all I-Ds acknowledge (ACK) to any input
> comment before the last call and after or it is only before last
> call?, and if it gets submitted to IESG/IAB, and we comment does that
> have no ACK in I-D?
>=20
> I sometimes feel discouraged to participate in any world work if the
> process does not involve my existance, just used with ignoring ACK of
> the reviewers. IMO any comment has value to the authors (e.g. some
> think only experts' comments are important to ACK) and to IETF,
> otherwise, we may delete valuable ACKs in IETF, which is not right.
>=20
> Best Regards
>=20
> AB
> A participant that still did not complete a year working for IETF, but
> trying to continue :)


From eburger-l@standardstrack.com  Sat Feb  9 04:14:48 2013
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 1BB0B21F8AB6 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 04:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4sGbvfBKY-8t for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 04:14:47 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 9459D21F8AB4 for <ietf@ietf.org>; Sat,  9 Feb 2013 04:14:47 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:53322 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1U49KF-0005iy-NZ; Sat, 09 Feb 2013 04:14:35 -0800
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: I-D affects another or work in ietf groups
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B77476D@xmb-rcd-x09.cisco.com>
Date: Sat, 9 Feb 2013 07:14:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BD3383F0-508F-4803-A0D1-5F14C6CDF64A@standardstrack.com>
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> <8C48B86A895913448548E6D15DA7553B77476D@xmb-rcd-x09.cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 12:14:48 -0000

As well, if there is a conflict, it will certainly come out in IESG =
review or IETF Last Call.

On Feb 8, 2013, at 11:27 PM, Fred Baker (fred) <fred@cisco.com> wrote:

> Speaking for myself, I would say that an internet draft is relevant to =
work in a working group if and only if it is covered by the charter of =
the working group. Anyone can claim anything to dodge the requirement =
that they ask relevant groups to review it. That doesn't make the claim =
true.
>=20
> In the event that you need a ruling, I would suggest discussing it =
with the relevant chairs and, if necessary, ADs. Generally speaking, =
they will have no axe to grind and can give you a reasonably objective =
answer.
>=20
> On Feb 8, 2013, at 7:56 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
>=20
>> Hi folks,
>>=20
>> Related to one discussion with a participant about I-Ds affecting =
WGs,
>> I have a question after reading two real incidents. The following two
>> work process examples are to show the I-Ds/RFCs affects from
>> participants point of view;
>>=20
>> 1) I got an understanding from one expert participant that his I-D is
>> not related to one RFC, even though it does involve similar =
objectives
>> and use-case, which was strange to me. So I understood from him that
>> his I-D is not affected by that RFC, even though his I-D does not
>> mention to exclude that RFC. IMO, I disagree with such producing I-D
>> by separate review-approach unaffected by other related RFCs (i.e. =
not
>> mentioned RFCs).
>>=20
>> 2) While I was discussing within a WG about an I-D which is a second
>> version of one IETF prorocol, some participants thought that the I-D
>> obsolete the old version even if not mentioned in the I-D. It then =
was
>> requested to update and mention that it does not obsolete the older
>> version. New versions are related and can affect each other, or =
affect
>> people understanding, which requires more careful presentation for
>> such I-D.
>>=20
>> I beleive that we have one source of producing RFCs, so all I-Ds and
>> RFCs are related some how, and they affect each other. So when I
>> review an item, I always like to consider all RFCs as much as I can =
to
>> make Internet better.
>>=20
>> Is that approach right for review? please advise,
>>=20
>> AB
>=20


From ietf@thomasclausen.org  Sat Feb  9 05:48:52 2013
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFC2821F8971 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 05:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.268
X-Spam-Level: 
X-Spam-Status: No, score=-0.268 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_35=0.6, J_CHICKENPOX_42=0.6, 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 LWMcD8Fo1rqv for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 05:48:52 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 1327121F8955 for <ietf@ietf.org>; Sat,  9 Feb 2013 05:48:52 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id A24BBA5FDA for <ietf@ietf.org>; Sat,  9 Feb 2013 05:48:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 598791C07D1; Sat,  9 Feb 2013 05:48:51 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.137] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id ADD1A1C07A1; Sat,  9 Feb 2013 05:48:49 -0800 (PST)
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20130207132146.18387.62853.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-37073E97-FB9A-4A5D-9155-24BE817BEDA4
Content-Transfer-Encoding: 7bit
Message-Id: <8231E15A-9948-4CC8-980D-1961BAA88ADB@thomasclausen.org>
X-Mailer: iPad Mail (10B141)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
Date: Sat, 9 Feb 2013 14:48:48 +0100
To: "ietf@ietf.org" <ietf@ietf.org>
Cc: "draft-cardenas-dff@tools.ietf.org" <draft-cardenas-dff@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 13:48:53 -0000

--Apple-Mail-37073E97-FB9A-4A5D-9155-24BE817BEDA4
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello folks,

I'd humbly like to encourage publication of this document.

I have been aware of DFF for a while, and we have implemented & tested the m=
echanisms specified therein fairly exhaustively.=20

	1)	Testing DFF conjointly with a variety of (IETF and non-IETF)=
 routing, introducing
		DFF yielded - in our tests - moderate to impressive perform=
ance improvements.

	2)	We did not see any negative performance impacts, in our tes=
ts, from the use of DFF.
=09
	3)	During our implementation & tests, I've been  providing occ=
asional feed-back & reviews
		to the authors (clarifications, mainly), which has been wel=
l reflected by the authors=20
		(thanks!)

	4) 	Having reviewed this -09 version of the specification, I fi=
nd it to be very clearly and=20
		concisely written, and sufficiently detailed to permit stra=
ight-forward implementation.
		(Kudos!).

	5)	A couple of nits remain; I'll ad those to the end of this e=
mail. They are exclusively
		of editorial nature, so please do not hold up the document o=
n behest of those.

Concluding the above, I encourage that this document be published as RFC. It=
 seems to be a very good idea, which is well documented.=20

I understand the motivation for this document being published on the Experim=
ental track is, that we need more operational data. I also understand from R=
alph's emails to various WGs that he is AD sponsoring this document, since i=
t doesn't seem to fit anywhere, at the moment, in the IETF.

If I may be so bold, I would like to suggest that a path be identified for i=
f and when progressing towards std.track - it was coincidental that I came a=
cross the document (and I'm glad that I did).

Now, my few *editorial* nits from reviewing -09:

	Notation and Terminology:

		There is some inconsistency in the use of colon's, dash'es o=
r spaces after the term and
		before its definition, for example:

			Foo:  The definition of Foo
=09
			Bar -  The definition of Bar

			Foobar This specification uses Foobar

	Information Base Overview:

		Suggest the first sentence be something of the form:

		"The information base required on each router contains a si=
ngle=20
			set, the Processed Set"

		Or something, since otherwise the term "Information Base" s=
eems orphaned.

	Also, the document later (section 6) calls it "Information Sets". S=
uggest that section 6
	be "Information Base" instead (or otherwise rendering the terminolo=
gy consistent=20
	there)

	Section 8, would it be worth calling out if these parameters can be=
 varied, and need
	not be the same on all routers in a given network? I.e., if heterog=
eneous parameters=20
	across a network does not impede on interoperability?

	Section 16:=20
		"implies that any headers specific to DFF do not traverse t=
he boundaries
		of the routing domain"
	=09
		Should that not be "...specific to DFF MUST NOT traverse th=
e ..." to be prescriptive?

That's all!

Best,

Thomas


Sent from my iPad

On 7 f=C3=A9vr. 2013, at 14:21, The IESG <iesg-secretary@ietf.org> wrote:

>=20
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>  <draft-cardenas-dff-09.txt> as Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document specifies the "Depth-First Forwarding" (DFF) protocol
>   for IPv6 networks, a data forwarding mechanism that can increase
>   reliability of data delivery in networks with dynamic topology and/or
>   lossy links.  The protocol operates entirely on the forwarding plane,
>   but may interact with the routing plane.  DFF forwards data packets
>   using a mechanism similar to a "depth-first search" for the
>   destination of a packet.  The routing plane may be informed of
>   failures to deliver a packet or loops.  This document specifies the
>   DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>   addition also for LoWPAN "mesh-under" networks (as specified in
>   RFC4944).
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   http://datatracker.ietf.org/ipr/1645/
>   http://datatracker.ietf.org/ipr/1646/
>=20
>=20
>=20

--Apple-Mail-37073E97-FB9A-4A5D-9155-24BE817BEDA4
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><table id=3D"metatable" width=3D"100%"=
 style=3D"border: 0px; border-spacing: 0px; "><tbody><tr style=3D"vertical-a=
lign: top; "><td></td><td><span style=3D"-webkit-text-size-adjust: auto; ">H=
ello folks,</span></td></tr></tbody></table></div><div style=3D"-webkit-text=
-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size-adjust: auto=
; ">I'd humbly like to encourage publication of this document.</div><div sty=
le=3D"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text=
-size-adjust: auto; ">I have been aware of DFF for a while, and we have impl=
emented &amp; tested the mechanisms specified therein fairly exhaustively.&n=
bsp;</div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><div sty=
le=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" style=
=3D"white-space:pre">	</span>1)<span class=3D"Apple-tab-span" style=3D"wh=
ite-space:pre">	</span>Testing DFF conjointly with a variety of (IETF and n=
on-IETF) routing, introducing</div><div style=3D"-webkit-text-size-adjust: a=
uto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
	</span>DFF yielded - in our tests - moderate to impressive performance impr=
ovements.</div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><di=
v style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" s=
tyle=3D"white-space:pre">	</span>2)<span class=3D"Apple-tab-span" sty=
le=3D"white-space:pre">	</span>We did not see any negative performance impa=
cts, in our tests, from the use of DFF.</div><div style=3D"-webkit-text-size=
-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D=
"Apple-tab-span" style=3D"white-space:pre">	</span>3)<span class=3D"App=
le-tab-span" style=3D"white-space:pre">	</span>During our implementation &a=
mp; tests, I've been &nbsp;providing occasional feed-back &amp; reviews</div=
><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-sp=
an" style=3D"white-space:pre">		</span>to the&nbsp;authors (clarifi=
cations, mainly), which has been well reflected by the authors&nbsp;</div><d=
iv style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span"=
 style=3D"white-space:pre">		</span>(thanks!)</div><div style=3D=
"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size=
-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span>4)&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span>Having reviewed this -09 version of the&nbsp;specification, I find i=
t to be very clearly and&nbsp;</div><div style=3D"-webkit-text-size-adjust: a=
uto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
	</span>concisely written, and sufficiently detailed to permit straight-forw=
ard implementation.</div><div style=3D"-webkit-text-size-adjust: auto; "><sp=
an class=3D"Apple-tab-span" style=3D"white-space:pre">		</span>(Kud=
os!).</div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><div st=
yle=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" styl=
e=3D"white-space:pre">	</span>5)<span class=3D"Apple-tab-span" style=3D"wh=
ite-space:pre">	</span>A couple of nits remain; I'll ad those to the end of=
 this email. They are exclusively</div><div style=3D"-webkit-text-size-adjus=
t: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
	</span>of editorial nature, so please do not hold up the document on behest=
 of those.</div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><d=
iv style=3D"-webkit-text-size-adjust: auto; ">Concluding the above, I encour=
age that this document be published as RFC. It seems to be a very good idea,=
 which is well documented.&nbsp;</div><div style=3D"-webkit-text-size-adjust=
: auto; "><br></div><div style=3D"-webkit-text-size-adjust: auto; ">I unders=
tand the motivation for this document being published on the Experimental tr=
ack is, that we need more operational data. I also understand from Ralph's e=
mails to various WGs that he is AD sponsoring this document, since it doesn'=
t seem to fit anywhere, at the moment, in the IETF.</div><div style=3D"-webk=
it-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size-adjus=
t: auto; ">If I may be so bold, I would like to suggest that a path be ident=
ified for if and when progressing towards std.track - it was coincidental th=
at I came across the document (and I'm glad that I did).</div><div style=3D"=
-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size-=
adjust: auto; ">Now, my few *editorial* nits from reviewing -09:</div><div s=
tyle=3D"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-te=
xt-size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:=
pre">	</span>Notation and&nbsp;Terminology:</div><div style=3D"-webkit-te=
xt-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size-adjust: au=
to; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">		</s=
pan>There is some inconsistency in the use of colon's, dash'es or spaces aft=
er the term and</div><div style=3D"-webkit-text-size-adjust: auto; "><span c=
lass=3D"Apple-tab-span" style=3D"white-space:pre">		</span>befo=
re its definition, for example:</div><div style=3D"-webkit-text-size-adjust:=
 auto; "><br></div><div style=3D"-webkit-text-size-adjust: auto; "><span cla=
ss=3D"Apple-tab-span" style=3D"white-space:pre">			</s=
pan>Foo: &nbsp;The definition of Foo</div><div style=3D"-webkit-text-size-ad=
just: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">	</s=
pan></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"App=
le-tab-span" style=3D"white-space:pre">			</span>Bar - &nbsp;=
The definition of Bar</div><div style=3D"-webkit-text-size-adjust: auto; "><=
br></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Appl=
e-tab-span" style=3D"white-space:pre">			</span>Foobar This s=
pecification uses Foobar</div><div style=3D"-webkit-text-size-adjust: auto; "=
><br></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Ap=
ple-tab-span" style=3D"white-space:pre">	</span>Information Base Ove=
rview:</div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><div s=
tyle=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" sty=
le=3D"white-space:pre">		</span>Suggest the first sentence be someth=
ing of the form:</div><div style=3D"-webkit-text-size-adjust: auto; "><br></=
div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab=
-span" style=3D"white-space:pre">		</span>"The information bas=
e required on each router contains a single&nbsp;</div><div style=3D"-webkit=
-text-size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-spa=
ce:pre">			</span>set, the Processed Set"</div><div st=
yle=3D"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-tex=
t-size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:p=
re">		</span>Or something, since otherwise the term "Information B=
ase" seems orphaned.</div><div style=3D"-webkit-text-size-adjust: auto; "><b=
r></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple=
-tab-span" style=3D"white-space:pre">	</span>Also, the document later (se=
ction 6) calls it "Information Sets". Suggest that section 6</div><div style=
=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D=
"white-space:pre">	</span>be "Information Base" instead (or otherwise r=
endering the terminology consistent&nbsp;</div><div style=3D"-webkit-text-si=
ze-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span>there)</div><div style=3D"-webkit-text-size-adjust: auto; ">=
<br></div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"App=
le-tab-span" style=3D"white-space:pre">	</span>Section 8, would it be worth=
 calling out if these parameters can be varied, and need</div><div style=3D"=
-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"wh=
ite-space:pre">	</span>not be the same on all routers in a given network? I=
.e., if heterogeneous parameters&nbsp;</div><div style=3D"-webkit-text-size-=
adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span>across a network does not impede on interoperability?</div><div styl=
e=3D"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-=
size-adjust: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre=
">	</span>Section 16:&nbsp;</div><div style=3D"-webkit-text-size-adjus=
t: auto; "><span class=3D"Apple-tab-span" style=3D"white-space:pre">	=
	</span>"implies that any headers specific to DFF do not traverse the bounda=
ries</div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D"App=
le-tab-span" style=3D"white-space: pre; ">		</span>of the routi=
ng domain"</div><div style=3D"-webkit-text-size-adjust: auto; "><span class=3D=
"Apple-tab-span" style=3D"white-space:pre">		</span></div><div s=
tyle=3D"-webkit-text-size-adjust: auto; "><span class=3D"Apple-tab-span" sty=
le=3D"white-space:pre">		</span>Should that not be "...specific to D=
FF MUST NOT traverse the ..." to be prescriptive?</div><div style=3D"-webkit=
-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-size-adjust:=
 auto; ">That's all!</div><div style=3D"-webkit-text-size-adjust: auto; "><b=
r></div><div style=3D"-webkit-text-size-adjust: auto; ">Best,</div><div styl=
e=3D"-webkit-text-size-adjust: auto; "><br></div><div style=3D"-webkit-text-=
size-adjust: auto; ">Thomas</div><div style=3D"-webkit-text-size-adjust: aut=
o; "><br></div><div style=3D"-webkit-text-size-adjust: auto; "><br></div><di=
v style=3D"-webkit-text-size-adjust: auto; ">Sent from my iPad</div><div sty=
le=3D"-webkit-text-size-adjust: auto; "><br>On 7 f=C3=A9vr. 2013, at 14:21, T=
he IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.o=
rg</a>&gt; wrote:<br><br></div><blockquote type=3D"cite" style=3D"-webkit-te=
xt-size-adjust: auto; "><div><span></span><br><span>The IESG has received a r=
equest from an individual submitter to consider</span><br><span>the followin=
g document:</span><br><span>- 'Depth-First Forwarding in Unreliable Networks=
 (DFF)'</span><br><span> &nbsp;&lt;draft-cardenas-dff-09.txt&gt; as Experime=
ntal RFC</span><br><span></span><br><span>The IESG plans to make a decision i=
n the next few weeks, and solicits</span><br><span>final comments on this ac=
tion. Please send substantive comments to the</span><br><span><a href=3D"mai=
lto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-02-24. Exceptiona=
lly, comments may be</span><br><span>sent to <a href=3D"mailto:iesg@ietf.org=
">iesg@ietf.org</a> instead. In either case, please retain the</span><br><sp=
an>beginning of the Subject line to allow automated sorting.</span><br><span=
></span><br><span>Abstract</span><br><span></span><br><span></span><br><span=
> &nbsp;&nbsp;This document specifies the "Depth-First Forwarding" (DFF) pro=
tocol</span><br><span> &nbsp;&nbsp;for IPv6 networks, a data forwarding mech=
anism that can increase</span><br><span> &nbsp;&nbsp;reliability of data del=
ivery in networks with dynamic topology and/or</span><br><span> &nbsp;&nbsp;=
lossy links. &nbsp;The protocol operates entirely on the forwarding plane,</=
span><br><span> &nbsp;&nbsp;but may interact with the routing plane. &nbsp;D=
FF forwards data packets</span><br><span> &nbsp;&nbsp;using a mechanism simi=
lar to a "depth-first search" for the</span><br><span> &nbsp;&nbsp;destinati=
on of a packet. &nbsp;The routing plane may be informed of</span><br><span> &=
nbsp;&nbsp;failures to deliver a packet or loops. &nbsp;This document specif=
ies the</span><br><span> &nbsp;&nbsp;DFF mechanism both for IPv6 networks (a=
s specified in RFC2460) and in</span><br><span> &nbsp;&nbsp;addition also fo=
r LoWPAN "mesh-under" networks (as specified in</span><br><span> &nbsp;&nbsp=
;RFC4944).</span><br><span></span><br><span></span><br><span></span><br><spa=
n></span><br><span>The file can be obtained via</span><br><span><a href=3D"h=
ttp://datatracker.ietf.org/doc/draft-cardenas-dff/">http://datatracker.ietf.=
org/doc/draft-cardenas-dff/</a></span><br><span></span><br><span>IESG discus=
sion can be tracked via</span><br><span><a href=3D"http://datatracker.ietf.o=
rg/doc/draft-cardenas-dff/ballot/">http://datatracker.ietf.org/doc/draft-car=
denas-dff/ballot/</a></span><br><span></span><br><span></span><br><span>The f=
ollowing IPR Declarations may be related to this I-D:</span><br><span></span=
><br><span> &nbsp;&nbsp;<a href=3D"http://datatracker.ietf.org/ipr/1645/">ht=
tp://datatracker.ietf.org/ipr/1645/</a></span><br><span> &nbsp;&nbsp;<a href=
=3D"http://datatracker.ietf.org/ipr/1646/">http://datatracker.ietf.org/ipr/1=
646/</a></span><br><span></span><br><span></span><br><span></span><br></div>=
</blockquote></body></html>=

--Apple-Mail-37073E97-FB9A-4A5D-9155-24BE817BEDA4--

From brian.e.carpenter@gmail.com  Sat Feb  9 06:55:10 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1352E21F89B2 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 06:55:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.104
X-Spam-Level: 
X-Spam-Status: No, score=-101.104 tagged_above=-999 required=5 tests=[AWL=0.587, 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 8k90JZIy1FUI for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 06:55:09 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id 27A7021F8886 for <ietf@ietf.org>; Sat,  9 Feb 2013 06:55:08 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id ez12so1816050wid.6 for <ietf@ietf.org>; Sat, 09 Feb 2013 06:55:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:subject:content-type; bh=WEZx1QBKiuxWGHfRHfhlKu3NjMyGU3Jbe5Y7MGiTOlM=; b=U8y2ZH/PmxFIgPHsgD4lW8poxnKUOZ/XtUfTeLnRRfnEb/m5blCe8p3WVYJoNVzOIy vn+NrQ50RoTMN5c5CRuPI9YH+TOXWv58K4KIoDDD1EapWRA5FyTMhWiSjtCR0Wm9UwOA gfxaP4zz2nfaHt0/WwZ0Q19dg1HHQ1Z7aPM5sSMcNbqn0K8cfYb5TspSGy+IvHhNAwiD Ki84ZvuMO/l+Tx34q6d3vXpeikMbEPrtvdq52/3DNi4mXxrTXgR19/NuEO3tVPihiJmG mOdUQ8mQqdxBeQgRy61cCCKtZExNfiaPnLN2Uni42YKIEZUYLs+DTAp/+ryZAumY4wr2 0wXA==
X-Received: by 10.194.122.131 with SMTP id ls3mr15273221wjb.55.1360421708258;  Sat, 09 Feb 2013 06:55:08 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-219-25.as13285.net. [2.102.219.25]) by mx.google.com with ESMTPS id fg6sm1856391wib.10.2013.02.09.06.55.06 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 09 Feb 2013 06:55:07 -0800 (PST)
Message-ID: <5116635A.5070108@gmail.com>
Date: Sat, 09 Feb 2013 14:55:22 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: [Fwd: Gen-ART LC review of draft-arkko-iesg-crossarea-03.txt]
Content-Type: multipart/mixed; boundary="------------000801060002080207000201"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Feb 2013 14:55:10 -0000

This is a multi-part message in MIME format.
--------------000801060002080207000201
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

This review may be of general interest.

-------- Original Message --------
Subject: Gen-ART LC review of draft-arkko-iesg-crossarea-03.txt
Date: Sat, 09 Feb 2013 14:53:50 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
To: draft-arkko-iesg-crossarea.all@tools.ietf.org,  General Area Review Team <gen-art@ietf.org>

Please see attached review.

     Brian


--------------000801060002080207000201
Content-Type: text/plain;
 name="draft-arkko-iesg-crossarea-03-carpenter.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-arkko-iesg-crossarea-03-carpenter.txt"

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9y
IGJhY2tncm91bmQgb24NCkdlbi1BUlQsIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPGh0dHA6
Ly93aWtpLnRvb2xzLmlldGYub3JnL2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0K
DQpQbGVhc2UgcmVzb2x2ZSB0aGVzZSBjb21tZW50cyBhbG9uZyB3aXRoIGFueSBvdGhlciBM
YXN0IENhbGwgY29tbWVudHMNCnlvdSBtYXkgcmVjZWl2ZS4NCg0KRG9jdW1lbnQ6IGRyYWZ0
LWFya2tvLWllc2ctY3Jvc3NhcmVhLTAzLnR4dA0KUmV2aWV3ZXI6IEJyaWFuIENhcnBlbnRl
cg0KUmV2aWV3IERhdGU6IDIwMTMtMDItMDkNCklFVEYgTEMgRW5kIERhdGU6IDIwMTMtMDMt
MDYNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxMy0NCg0KU3VtbWFyeTogIE9uIHRoZSByaWdo
dCBsaW5lcw0KLS0tLS0tLS0NCg0KTWFqb3IgSXNzdWVzOiAgDQotLS0tLS0tLS0tLS0tDQoN
Cj4gQXJlYSBTaG9wcGluZw0KDQpJJ20gbm90IGVudGlyZWx5IGhhcHB5IHdpdGggdGhpcyBk
aXNjdXNzaW9uLiBGcm9tIHRoZSBwb2ludCBvZiB2aWV3IG9mIHRoZQ0KcGVyc29uIHRyeWlu
ZyB0byBpbnRyb2R1Y2luZyBhIG5ldyB0b3BpYyB0aGF0IGRvZXMgaW5kZWVkIGNyb3NzIGFy
ZWFzLCBpdCBpcw0KKmluZXZpdGFibGUqIHRvIGNvbW1pdCB0aGUgc2luIG9mIGFyZWEgc2hv
cHBpbmcuIDxzaG91dD5UaGlzIGlzIG5vdCBhIGZhdWx0IG9mDQp0aGUgc2hvcHBlcjsgaXQn
cyB0aGUgZmF1bHQgb2YgdGhlIElFVEYgZm9yIGhhdmluZyBhcmVhcyBpbiB0aGUgZmlyc3Qg
cGxhY2UuPC9zaG91dD4NCg0KSSBhZ3JlZSB0aGF0IGl0J3MgdGhlIElFU0cncywgYW5kIGFs
c28gdGhlIElBQidzLCBqb2IgdG8gcmVzb2x2ZSB0aGlzIHdoZW4NCml0IGFyaXNlcy4gQnV0
IHRoZSBjdXJyZW50IHRleHQgbWFrZXMgaXQgc291bmQgYXMgaWYgdGhlIHByb3RhZ29uaXN0
IGlzIHRvDQpibGFtZSBmb3IgYnJpbmdpbmcgYSBjcm9zcy1hcmVhIHByb2JsZW0gdG8gdGhl
IElFVEYuDQoNClRoZXJlIGFsc28gc2VlbXMgdG8gYmUgYSBtaXNzaW5nIHRvcGljLCBoZXJl
IGFuZCBpbiB0aGUgcmVjb21tZW5kYXRpb25zOg0KdGhlIGltcG9ydGFuY2Ugb2YgdGhlIEJP
RiAoYW5kIGJhciBCT0YpIHByb2Nlc3MsIGFuZCB0b3BpYyByZXZpZXcgYnkgdGhlDQpJQUIs
IGluIGlkZW50aWZ5aW5nIGNyb3NzLWFyZWEgdG9waWNzIGFuZCBjaGFydGVyaW5nIHRoZW0g
Y2FyZWZ1bGx5LiBUaGUNCndvcnN0IHRoaW5nIHRoYXQgY2FuIGhhcHBlbiBpcyB0byBCT0Yg
YW5kIGNoYXJ0ZXIgYSB0b3BpYyB3aXRoaW4gb25lIGFyZWEsDQpidXQgZGlzY292ZXIgbGF0
ZXIgdGhhdCBpdCBpcyBpbiBmYWN0IGEgY3Jvc3MtYXJlYSB0b3BpYy4gVGhlcmUgYXJlDQpy
ZWxldmFudCBSRkNzOiA1NDM0LCA2NzcxLg0KDQpNaW5vciBJc3N1ZXM6ICANCi0tLS0tLS0t
LS0tLS0NCg0KPiAyLiAgRXhhbXBsZXMgb2YgQ3Jvc3MtQXJlYSBXb3JrDQo+DQo+ICAgTWFu
eSBJRVRGIGVmZm9ydHMgY3Jvc3MgYXJlYSBib3VuZGFyaWVzLiAgU29tZSByZWNlbnQgZXhh
bXBsZXMgb2YNCj4gICBzdWNoIHdvcmsgaW5jbHVkZToNCj4NCj4gICBvICBUaGUgZGV2ZWxv
cG1lbnQgb2YgYSByb3V0aW5nLXByb3RvY29sIGJhc2VkIGJyaWRnaW5nIG1vZGVsLiAgVGhp
cw0KPiAgICAgIHdvcmsgaGFzIGJlZW4gZ29pbmcgb24gaW4gdGhlIFRSSUxMIFdHIG9uIHRo
ZSBJbnRlcm5ldCBBcmVhIGFuZCBpbg0KPiAgICAgIHBhcmFsbGVsIGluIHRoZSBJU0lTIFdH
IG9uIHRoZSBSb3V0aW5nIEFyZWEuDQoNCkEgdmVyeSBpbXBvcnRhbnQgYXNwZWN0IG9mIHRo
aXMgZXhhbXBsZSBpcyB0aGF0IGl0ICphbHNvKiBvdmVybGFwcyB3aXRoIElFRUUgd29yay4N
ClRoYXQgc2NlbmFyaW8gc2hvdWxkIHN1cmVseSBiZSBtZW50aW9uZWQsIGF0IGxlYXN0IGJ5
IGEgY3Jvc3MtcmVmZXJlbmNlIHRvIHRoZQ0KdmFyaW91cyBSRkNzIG9uIGxpYWlzb25zOiA0
MDUyLCA0MDUzLCA0NjkxLg0KDQo+ICAgbyAgVGhlIFJFTlVNIFdHIG9uIHRoZSBPcGVyYXRp
b25zIGFuZCBNYW5hZ2VtZW50IEFyZWEgaXMgYWRkcmVzc2luZw0KPiAgICAgIHJlbnVtYmVy
aW5nIGlzc3VlcywgYnV0IHdpbGwgaGF2ZSB0byB3b3JrIHdpdGggb3RoZXIgYXJlYXMgaWYN
Cj4gICAgICBjaGFuZ2VzIG9yIGV4dGVuc2lvbnMgdG8gc3BlY2lmaWMgcHJvdG9jb2xzIGFy
ZSByZXF1aXJlZC4NCg0KVGhlIFdHIG5hbWUgaXMgNlJFTlVNLiBJbiBmYWN0IGl0cyBjaGFy
dGVyIGlzIGV4cGxpY2l0IHRoYXQgcHJvdG9jb2wgd29yaw0Kd2lsbCAqbm90KiBiZSBkb25l
IGluIHRoZSBXRy4gKFRoZSBzYW1lIGlzIHRydWUgb2YgVjZPUFMuKSANCg0KPiAzLiAgUmF0
aW9uYWxlIGZvciBDcm9zcy1BcmVhIFdvcmsNCi4uLg0KPiAgIFRoZQ0KPiAgIGFjdHVhbCBz
b2x1dGlvbiB3b3JrIGlzIHRoZW4gdGFrZW4gdXAgYnkgdGhlIHJlbGV2YW50IHRlY2huaWNh
bA0KPiAgIGNvbW11bml0eSB0aGF0IHdvcmtzIG9uIHRoZSBwcm90b2NvbCB0aGF0IG5lZWRz
IHRvIGJlIGV4dGVuZGVkLg0KDQpJdCB3b3VsZCBiZSB1c2VmdWwgdG8gcmVmZXIgdG8gdGhl
IFJGQ3MgYWJvdXQgZXh0ZW5zaW9uczogNDc3NSwgNjcwOS4NCg0KTml0cw0KLS0tLQ0KDQpU
aGVyZSBhcmUgbnVtZXJvdXMgZXJyb3JzIGluIHRoZSBjaG9pY2Ugb2YgcHJlcG9zaXRpb25z
LCBlLmcuICJUaGUgTFdJRyBXRyBvbiB0aGUgDQpJbnRlcm5ldCBBcmVhIiwgdGhhdCBuZWVk
IHRvIGJlIGZpeGVkIGR1cmluZyBlZGl0aW5nLg==
--------------000801060002080207000201--

From jari.arkko@piuha.net  Sat Feb  9 07:02:23 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2D7C21F8887 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 07:02:23 -0800 (PST)
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 3WTes96KHolk for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 07:02:22 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id F1ADA21F884A for <ietf@ietf.org>; Sat,  9 Feb 2013 07:02:21 -0800 (PST)
Received: from [10.232.213.9] (37-219-38-211.nat.bb.dnainternet.fi [37.219.38.211]) by p130.piuha.net (Postfix) with ESMTPSA id B8A352CC3B; Sat,  9 Feb 2013 17:02:19 +0200 (EET)
Date: Sat, 09 Feb 2013 17:02:12 +0200
Subject: VS:  [Fwd: Gen-ART LC review of draft-arkko-iesg-crossarea-03.txt]
Message-ID: <hlm6fybmivg4kv2bhyy00p51.1360422132964@email.android.com>
From: Jari Arkko <jari.arkko@piuha.net>
To: IETF discussion list <ietf@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 15:02:23 -0000

VGhhbmsgeW91IGZvciB0aGUgcmV2aWV3LCBCcmlhbiEgTm93IHRoYXQgeW91IHJhaXNlIHRoZSAi
c2hvcHBpbmciIGlzc3VlIGluIGEgZGlmZmVyZW50IGxpZ2h0LCBJIGRvIGFncmVlLiBJIHdpbGwg
dGhpbmsgYWJvdXQgdGhlIGJlc3Qgd2F5IHRvIGNhcHR1cmUgdGhpcyBjb3JyZWN0bHkuCgpKYXJp


From adrian@olddog.co.uk  Sat Feb  9 07:51:54 2013
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FAAD21F89B5 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 07:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Z4zHF7wHkDa for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 07:51:53 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id D070321F89B3 for <ietf@ietf.org>; Sat,  9 Feb 2013 07:51:50 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r19Fpndl005642 for <ietf@ietf.org>; Sat, 9 Feb 2013 15:51:49 GMT
Received: from 950129200 (89-26-111-90.bruck.stat.salzburg-online.at [89.26.111.90]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id r19FplA5005629 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 9 Feb 2013 15:51:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
Date: Sat, 9 Feb 2013 15:51:45 -0000
Message-ID: <004e01ce06dd$5dfaf530$19f0df90$@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: Ac4G3OvIhXEem39ySbydaPLkA677vg==
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: Sat, 09 Feb 2013 15:51:54 -0000

Hi,

Here are some comments resulting from my reading of draft-arkko-iesg-crossarea.
I chose to review the -03 version.

Hope they are useful.

Adrian

===

In several places, this document is careful to state that the text
represents the personal view of the author (Section 4 "Process vs.
Substance", Section 5, Appendix 5).  This is fine as far as it goes, but
leads to three issues:

1. The filename gives the impression that this is an IESG document
   I don't believe there is any point in fixing this because once
   published as an RFC the I-D filename is almost completely forgotten.

2. The clarity about the document being the author's personal opinion is
   missing from the Abstract and Introduction making it hard for the
   reader to understand this fact. This is easily fixed.

3. It is not clear what it would mean to have IETF consensus on this
   document. Would it mean that the IETF agrees that this is the
   author's opinion? So, please be careful to not accidentally attach
   the "IETF consensus" boilerplate to this document if it is published
   as an RFC. (Actually, it would be good if the IETF last call for
   this type of document called out the "not seeking consensus" fact so
   that the community understands what type of review they are doing 
   and how their comments will be handled.) The action here is on the
   sponsoring AD and the IESG as the document goes for publication - it
   would be really good to put in an RFC Editor note early so that this
   does not get lost.

---

I would find it helpful if the Introduction gave some sort of management
summary: Who is supposed to read / act on this document? What actions
are they supposed to take?

For example (but with no intent to constrain the author), this could be
aimed at the wider IETF community with the intent of getting them to
understand that it means something special for a working group to be in
a particular area. Or it could be aimed at the IESG with a view to
getting them to consider the implications of cross-area work on the IETF
organisation.

---

Nit:
Several s/on the foo area/in the foo area/

---

I think that the description of LWIG in Section 2 is wrong to limit the
scope to "the TCP/IP stack and application protocols." The charter is
far wider than that and embraces routing and operations protocols as
well. (For some reason the security area escapes attention in the
charter although there is an I-D for TLS).

---

Section 2

I would suggest:

OLD
   o  The Routing Area, Transport Area, and Security Area have worked
      together on security mechanisms and key management tools necessary
      to secure BGP sessions carried on top of TCP.  For instance, the
      SIDR and KARP WGs are in the Routing Area, but they are clearly
      focused on topics that are generally found in the Security Area.
NEW
   o  The Routing Area, Transport Area, and Security Area have worked
      together on security mechanisms and key management tools necessary
      to secure routing protocols, including those carried on top of
      TCP.  For instance, the SIDR and KARP WGs are in the Routing Area,
      but they are clearly focused on topics that are generally found in
      the Security Area.
END

---

I think Section 2 should acknowledge RFC 2223 and RFC 3552 with respect
to how security crosses into all areas.  Similarly, you should mention
RFC 5706 with respect to how management and operations cross into all
areas.

I also think the example in the last bullet of section 2 is a bit weak.
You should probably also discuss the way that many protocol working
groups develop data models (e.g., MIB modules), yet NETMOD is developing
data models for protocols and entities in other areas. Similarly, you may
want to introduce I2RS.

Lastly, the same bullet is missing a discussion of OAM protocols worked
on in protocol working groups (such as MPLS and TRILL).

---

The start of Section 3 seems to contradict the discussion of splitting
work into different WGs either to share the load or to attract the right
area participants. You say:

   From an IETF participant's point of view, it is important that there
   is a working group where the technical topic that he or she is
   interested in can be discussed.  The area and the management
   structure matters little for this, as long as the working group can
   work on all of the relevant aspects.

---

Nit
Section 3

   Cross-area work is needed,
   of course, in any situation where a particular technical problem does
   not cleanly map to one organization.

s/organization/area/

---

I share some of Brian's views on "Area Shopping". The flip of what some 
may perceive as shopping is what the authors perceive as "Being pushed
from pillar to post without anyone taking proper responsibility for 
finding the correct home for the work." The IESG has a responsibility to
ensure that work that needs to be homed in the IETF is found a home. The
IESG equally has a responsibility to ensure that work that does not
belong in the IETF (for any of a number of reasons) or is not yet 
properly formed, does not "sneak in". The answer to this, I am afraid,
lies in proper communication and mutual trust within the IESG.

---

Suggestions for inclusion in Section 4 would be:

   Engineers Will be Engineers

   Observing that engineers will often look for an existing tool (for
   example, a hammer) to address a new problem (for example, a screw).

and

   Don't Break the Internet

   Some pieces of the Internet infrastructure may be considered a little
   fragile. This understanding does not always extend beyond the working
   group maintaining the associated technology, so there can be a real
   tension when a working group (usually in another area) decides to use
   the technology in a novel way without either proper discussion or
   proper separation.

---

The piece about cross-area review is important, but is hiding in "Rigid
Topic Ownership" in Section 4. There are three additional problems
associated with cross-area review:
1. It is not clear where to send cross-area review requests
2. Cross-area reviews, when requested, rarely happen
3. The ramp-up needed to achieve a cross-area review can often be huge

---

I suspect that the recommendations concerning scheduling, while
addressing the primary problem, do not recognise an underlying issue.
Thus, addressing the conflicts between meeting slots in order that, for
example, all appropriate routing experts could attend TRILL, would lead
to a longer IETF week with fewer parallel sessions.

An alternative, is to recognise that ADs are *not* the gate in
scheduling. It is not necessary for ADs to attend even all of the
working groups that they are responsible for. They may be interested in
attending other working groups as well, but it is not necessary for them
to be there.

Similarly, while there are some high-level conflicts to avoid (TRILL
against ISIS), other conflicts are a nuisance for a few people rather
than a major problem for the IETF.

---

I also think that one of the important aspects of managing cross-area
work goes beyond getting the language right in charters. Brian observes
that several of the OPS working groups have charter text explicitly 
stating that "protocol development will not be done in this WG", making
the WG responsible for problem statements, requirements, and
applicability, and placing the responsibility for protocol development 
in other WGs often in other areas. This is great if and only if the
charter is observed! By the time a protocol spec arrives at the IESG as
a publication spec, it is pointless to try to control what has happened -
the best that can be done is to send the document for wider review. What
clearly needs to happen is for working groups to observe their charters,
for working group chairs to be stricter, and for ADs to stay on top of
this type of issue.

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 06 February 2013 23:50
> To: IETF-Announce
> Subject: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from
Cross-
> Area Work at the IETF) to Informational RFC
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Experiences from Cross-Area Work at the IETF'
>   <draft-arkko-iesg-crossarea-02.txt> as Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-03-06. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.


From dhc@dcrocker.net  Sat Feb  9 08:32:09 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D481821F8886 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 08:32:09 -0800 (PST)
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 Zrf6OccZQDwA for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 08:32:09 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 47AE421F8863 for <ietf@ietf.org>; Sat,  9 Feb 2013 08:32:09 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r19GW880007437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 9 Feb 2013 08:32:08 -0800
Message-ID: <51167A03.8040804@dcrocker.net>
Date: Sat, 09 Feb 2013 08:32:03 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
References: <004e01ce06dd$5dfaf530$19f0df90$@olddog.co.uk>
In-Reply-To: <004e01ce06dd$5dfaf530$19f0df90$@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.0 (sbh17.songbird.com [72.52.113.17]); Sat, 09 Feb 2013 08:32:08 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2013 16:32:10 -0000

On 2/9/2013 7:51 AM, Adrian Farrel wrote:
> 3. It is not clear what it would mean to have IETF consensus on this
>     document. Would it mean that the IETF agrees that this is the
>     author's opinion?


This sort of document is probably better as an Independent submission, 
directly to the RFC Editor.

I think documents like this can be quite valuable.  And having IETF 
comment, such as your note, is a good thing.

But as you note, seeking any sort of IETF consensus about a statement of 
personal perspective does not make much sense.  Absent trying to make it 
an official IETF perspective, the debate and probable nit-picking, which 
accompanies an effort to get IETF consensus, actually would likely be 
counter-producive.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From sm@resistor.net  Sat Feb  9 11:38:26 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A32821F852C for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 11:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level: 
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.027, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fz8jLeZ-pcA1 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 11:38:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9096521F851C for <ietf@ietf.org>; Sat,  9 Feb 2013 11:38:25 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r19JcCcb000775 for <ietf@ietf.org>; Sat, 9 Feb 2013 11:38:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360438697; bh=7+BkKcLhW6dkMzaG9hz5NhOP3clbB79vuFMwCH4M754=; h=Date:To:From:Subject:In-Reply-To:References; b=fYkl9y98eeK2LLaWeuz8pZ3sqNf2SG5f9972CTSfGjFa7H/fLQMN8CdSq9fIvFqLH lHdBjllFvGXQWD++EWAQTlEAPymlUbYwOKtZNYKw2nCG4781E26pKwwol75mEm30gy Gvhyy7VwFCHbjELCppFQkjEeZlv76OLK/z48Zsss=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360438697; i=@resistor.net; bh=7+BkKcLhW6dkMzaG9hz5NhOP3clbB79vuFMwCH4M754=; h=Date:To:From:Subject:In-Reply-To:References; b=4mx0ZPLr9nqUR+eh1zO/romMitT9iewZonxC+ygtdm4nZAEQGGVLUTNbn0hCWVMet IjMZHC4xf0ruwMwrgYwajyTZHGkFMhwciHXuyV2DijD1DPsz3EFbsICDq6yg9A1SR0 baMK0wFaMPIkXeGTIMcC/SG2AudBdBA9kea/tYP8=
Message-Id: <6.2.5.6.2.20130209090616.0a22ba20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 09 Feb 2013 11:36:37 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
In-Reply-To: <20130206234933.11375.20586.idtracker@ietfa.amsl.com>
References: <20130206234933.11375.20586.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: Sat, 09 Feb 2013 19:38:26 -0000

At 15:49 06-02-2013, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Experiences from Cross-Area Work at the IETF'
>   <draft-arkko-iesg-crossarea-02.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-03-06. Exceptionally, comments may be

I read draft-arkko-iesg-crossarea-03 as I am trying to learn about 
the IETF.  In Section 2:

    "This work has been going on in the TRILL WG on the Internet Area
     and in parallel in the ISIS WG on the Routing Area."

There is an assumption that I know what "WG" means.

Editorial: I suggest within the area instead of on the area.

In Section 3:

   "Cross-area work is needed, of course, in any situation where a
    particular technical problem does not cleanly map to one
    organization."

Shouldn't that map to a working group?

In Section 4:

   "But it is also possible that concerns raised in one forum are
    not understood in another, and this can lead to an effort going
    forward after finding the "lowest bar" forum to take it up."

Brian Carpenter commented about Area Shopping in his Gen-ART 
review.  Scrolling back to Section 3, "from an IETF participant's 
point of view, it is important that there is a working group where 
the technical topic that he or she is interested in can be 
discussed.  The problem is how to identify that working group.  I 
went to http://datatracker.ietf.org/list/wg/  to find the working 
group where I can discuss about my solution to an IPv6 problem.  I 
found "IPv6 Maintenance".  I am not sure what that group does.  As 
the problem affects IPv6 operations I picked the "IPv6 Operations" 
working group.  I post a message to the mailing list.  There isn't 
any reply.  My solution does some DNS stuff.  I try the "Domain Name 
System Operations" working group.  I keep trying various mailing 
lists until I find the "right" venue.

The actual problem is finding out what's the main topic of the draft 
within an IETF context and identifying the proper working 
group.  There should also be someone to identify related topics which 
will be useful as input for the draft to progress.  The IESG part of 
the "process" is more about identifying which working groups should 
be chartered and in which area they should fall.  The Area Shopping 
heading looks at the problem from an IESG perspective.  The "lowest 
bar" is the IETF participant's perspective.

   "A more common issue is that the different organizations typically
    have different motivations."

The Abstract mentions "challenges for the organization of the 
IETF".  Although I think I understand what "Problem Ownership" is 
about, I suspect that the reader might be confused about what the two 
paragraphs discuss about.

   "For the regular participant it is difficult to find out where there
    are important documents that would deserve more review."

It's not a matter of important documents.  I would say that it is 
about the regular participant being able to find that document which 
he/she believes is important or the subject of discussion where 
his/her input would be helpful.

Recommendation 8 is about interaction between working groups.  It 
would be good if WG Chairs could reach out to other working groups 
when a topic relates to what's in their charter.  Recommendation 9 
looks at conflicts from an area point of view.  The current 
scheduling model is based on groups the participants would like to 
attend instead of conflicts which may prevent the topics being 
discussed from the cross-area participants.  Recommendation 10 comes 
out as having 10 in the list. :-)

It took me some time to understand that the draft was about how work 
is organized in the IETF.  I didn't really understand what area means 
except that Routing Area must have something to do with router and 
Security Area must have something to do with security.  I decided to 
read the Informational reference and I learned that it is a 
management division within the IETF.

I suggest having some text in Section 1 to introduce the areas.  The 
Abstract should be aligned with the Introduction Section.   Section 2 
provides examples of cross-area work.    There aren't any examples to 
illustrate the challenges except for the AD scheduling conflict.

Regards,
-sm 


From worley@shell01.TheWorld.com  Sat Feb  9 19:46:40 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F75A21F8467 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 19:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.664
X-Spam-Level: 
X-Spam-Status: No, score=-2.664 tagged_above=-999 required=5 tests=[AWL=0.316,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYUJJ7nGwjRi for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 19:46:40 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id E946821F845F for <ietf@ietf.org>; Sat,  9 Feb 2013 19:46:39 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1A3k4jS029092 for <ietf@ietf.org>; Sat, 9 Feb 2013 22:46:07 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1A3k4G01559822 for <ietf@ietf.org>; Sat, 9 Feb 2013 22:46:04 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1A3k4Ue1561926; Sat, 9 Feb 2013 22:46:04 -0500 (EST)
Date: Sat, 9 Feb 2013 22:46:04 -0500 (EST)
Message-Id: <201302100346.r1A3k4Ue1561926@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> (abdussalambaryun@gmail.com)
Subject: Re: I-D affects another or work in ietf groups
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 03:46:40 -0000

> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
> 
> I beleive that we have one source of producing RFCs, so all I-Ds and
> RFCs are related some how, and they affect each other. So when I
> review an item, I always like to consider all RFCs as much as I can to
> make Internet better.
> 
> Is that approach right for review? please advise,

If you are reviewing a document as an individual, you are free to
consider its interactions with anything that you consider relevant.  As
you say, "as much as I can to make the Internet better".

If you have been given a specific duty when reviewing a document, then
that duty may prescribe what interactions you should be considering.

In any case, if you are doing something incorrect in your review,
presumably people will call your attention to that fact, and explain
how you should change what you are doing and why you should change it.

Dale

From worley@shell01.TheWorld.com  Sat Feb  9 19:47:10 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1281521F84F8 for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 19:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.679
X-Spam-Level: 
X-Spam-Status: No, score=-2.679 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gloE7kc6IudG for <ietf@ietfa.amsl.com>; Sat,  9 Feb 2013 19:47:06 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 6B2AD21F84F3 for <ietf@ietf.org>; Sat,  9 Feb 2013 19:47:05 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1A3kvKJ000982; Sat, 9 Feb 2013 22:46:59 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1A3kvSq1559040; Sat, 9 Feb 2013 22:46:57 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1A3kvag1559644; Sat, 9 Feb 2013 22:46:57 -0500 (EST)
Date: Sat, 9 Feb 2013 22:46:57 -0500 (EST)
Message-Id: <201302100346.r1A3kvag1559644@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
In-reply-to: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> (abdussalambaryun@gmail.com)
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.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: Sun, 10 Feb 2013 03:47:10 -0000

> From: Abdussalam Baryun <abdussalambaryun@gmail.com>
> 
> I sometimes feel discouraged to participate in any world work if the
> process does not involve my existance, just used with ignoring ACK of
> the reviewers. IMO any comment has value to the authors (e.g. some
> think only experts' comments are important to ACK) and to IETF,
> otherwise, we may delete valuable ACKs in IETF, which is not right.

Hi Abdussalam,

I believe that you are examining this problem from the point of view
of a reviewer (and possible contributor) to a document, rather than
the point of view of a document author.  That is, your question is
"When can I expect a document author to include an Acknowledgment of
my review?"

In practice, that depends on the judgment the document author; does
the document author feel that you have made a "significant"
contribution to the document?

In general, even if an outside observer would say that you contributed
significantly to a document, it can appear impolite to explicitly
request that your name be added to the Acknowledgments section.

> A participant that still did not complete a year working for IETF, but
> trying to continue :)

My belief is that one must participate in the IETF fairly intensively
for six months to a year before one can gain a reputation as being a
knowledgeable contributor.  After all, most of the people authoring
documents have been participating for several years -- and they
already know each other.  Before you have gained that reputation, it
may be difficult to get people to pay attention to your contributions,
even if they are objectively valuable.  I describe the rule in the
IETF as "Everyone may speak; not everyone is listened to."  You need
to prove yourself to be a person worth listening to.

Much useful advice on this subject is contained in RFC 4144, "How to
Gain Prominence and Influence in Standards Organizations".

My experience is that one can learn how to get more respect in an
organization by occasionally asking more experienced people how to do
so.  One method that works in most organizations is to volunteer for
the "thankless tasks".  In any organization, there are tasks that are
acknowledged as necessary, they are unpleasant to do, and people who
do it are not rewarded commensurately for doing them.  (Reviewing
drafts is one of them in the IETF.)  However, if you develop a
reputation as a person who does these tasks, it will increase the
respect you receive.

Dale

From abdussalambaryun@gmail.com  Sun Feb 10 00:28:55 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA4C21F84DC for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 00:28:55 -0800 (PST)
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 8J92WsBRQLgv for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 00:28:54 -0800 (PST)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4504B21F84D0 for <ietf@ietf.org>; Sun, 10 Feb 2013 00:28:54 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id 8so3902744wgl.18 for <ietf@ietf.org>; Sun, 10 Feb 2013 00:28:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=2R0t0z7brY+wPuEBUh2XTDFb9vtRm8t/7u05uXpAQXk=; b=L9QJeQ/+a7X+EqoDna7meXVZxpYarA9f/vrwwYGzuWrvlyOql83YjA9uOxayil8YWL Hn3hnrLyYjSNuZv3I4X34WzYr0MVcq+NygLS7XxHFM7oJb8dC6VncnVeygPCHVjwiKjq wPWUaVki0AL+AbDlciPiaE/Goqm1e1B63Ib3EKJLoBtHXtf9XnkbZco97LpU6B7IQ+km xbO6luKbq2LHHO7p1KoHYpoYnZv3+LiCzxcCKJs5KUe7IaVpLhb5JXpY0O37Qm1E4hzw NekKq7op9aaZ3rNVTzm7EQVR6pSY1dKnEfMnBwa+QN09sugFmQpO9bMZc1oFwFaxb61p F1aA==
MIME-Version: 1.0
X-Received: by 10.180.78.137 with SMTP id b9mr10175528wix.30.1360484933134; Sun, 10 Feb 2013 00:28:53 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 10 Feb 2013 00:28:52 -0800 (PST)
In-Reply-To: <201302100346.r1A3kvag1559644@shell01.TheWorld.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <201302100346.r1A3kvag1559644@shell01.TheWorld.com>
Date: Sun, 10 Feb 2013 09:28:52 +0100
Message-ID: <CADnDZ89kbqcNtUhKNa-pDDrqn2SSaDW2zm1SBSdOOqo5EkftFQ@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 08:28:55 -0000

Hi Dale,

thanks for your feedback. some comment below,

On 2/10/13, Dale R. Worley <worley@ariadne.com> wrote:
> I believe that you are examining this problem from the point of view
> of a reviewer (and possible contributor) to a document, rather than
> the point of view of a document author.  That is, your question is
> "When can I expect a document author to include an Acknowledgment of
> my review?"

Yes, usually the I-D is always about the author's point of view
ignoring others, but only great authors want people feedback to have
doc communicate with the reader,
>
> In practice, that depends on the judgment the document author; does
> the document author feel that you have made a "significant"
> contribution to the document?

I agree that it is responsibility of owners or authors. In IETF the
I-D may be a WG I-D so the group work together to feel what is best,

>
> In general, even if an outside observer would say that you contributed
> significantly to a document, it can appear impolite to explicitly
> request that your name be added to the Acknowledgments section.

It depends on who is acknowledging (ACK), is it the authors or the WG,
or any....,
In the I-D ACK section, it can mention that IESG acknowledges smith,
the IETF acknowledge the ITU, the authors acknowledge RFC333 authors,
the WG acknowledge Saley, etc.

Also depend on *why* the acknowledge section. Authors don't only ACK
because of significant contributions, that is impolite too. In most
documents in the world authors may thank their son even if he had no
direct contribution but because the authors were working at home (a
volunteering space) they felt to ACK their son, because of his good
influences on work. In IETF it is all about discussions and comments
for its I-Ds and RFCs, new comers' participation make the discussions
valueable in my opinion,

>
>> A participant that still did not complete a year working for IETF, but
>> trying to continue :)
>
> My belief is that one must participate in the IETF fairly intensively
> for six months to a year before one can gain a reputation as being a
> knowledgeable contributor.  After all, most of the people authoring
> documents have been participating for several years -- and they
> already know each other.  Before you have gained that reputation, it
> may be difficult to get people to pay attention to your contributions,
> even if they are objectively valuable.  I describe the rule in the
> IETF as "Everyone may speak; not everyone is listened to."  You need
> to prove yourself to be a person worth listening to.

I agree, but we should n't ignore voices of new participants, and
don't ignore people that are listening and never participate.

>
> Much useful advice on this subject is contained in RFC 4144, "How to
> Gain Prominence and Influence in Standards Organizations".
>

Thanks for that advice,

> My experience is that one can learn how to get more respect in an
> organization by occasionally asking more experienced people how to do
> so.  One method that works in most organizations is to volunteer for
> the "thankless tasks".  In any organization, there are tasks that are
> acknowledged as necessary, they are unpleasant to do, and people who
> do it are not rewarded commensurately for doing them.  (Reviewing
> drafts is one of them in the IETF.)  However, if you develop a
> reputation as a person who does these tasks, it will increase the
> respect you receive.

Your right, however, just to add that I don't participate in IETF to
make reputation, because I think it is not a place for reputation, I
try to participate to volunteer in the Internet Community to add to my
Internet knowledge and others,


thanks alot for all your comments and advice :)

AB

From dave@cridland.net  Sun Feb 10 01:47:03 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10C3321F8540 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 01:47:03 -0800 (PST)
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 VzqkCcLGQJ9P for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 01:47:02 -0800 (PST)
Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by ietfa.amsl.com (Postfix) with ESMTP id 563DF21F84F9 for <ietf@ietf.org>; Sun, 10 Feb 2013 01:47:01 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id 16so5268114obc.33 for <ietf@ietf.org>; Sun, 10 Feb 2013 01:47:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=c5a6TUh31+hH6U2BvlxeBJ9uKe+4bCDD91+RkxBWJTk=; b=PAjpfSCBxL8lp6nrlNceG09KCjx2qO3ElZym5M83bd1GFh7+m3JwXLTDrDe+6jHGvK ZkHigJ3WoUy6aee61CxjetP14ytwIEb28p24ft6/Qnqnd2q0zR/YoBh6eeAZmTgllh3P pwxsSTRn+C/ekjdnCLCpwulO5HKyJD+arBPDM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=c5a6TUh31+hH6U2BvlxeBJ9uKe+4bCDD91+RkxBWJTk=; b=oMEFYmdYF3YFcwv3RfNOg2IXlKXT/mu/1+4XlK+fYO6dGUqBN8i9Bt9rLJc3/JlODb xeDHtWVUhvfNbFuhaGYNg0gDz4HbqbGLdUNc8fRM/QYUi2LIeeyGjHIOzVg6RZdszkLM Pac5pUXY5Qxb9lrqKEnyDf9G2kiZuNaixZmzzcNrVD7CVttsD2/T0srQKetUjlOQqsFI vqoqBiVjZQGeXyIvxy1qO2MR7tlCteZU72vUh/ly0qnB862hDjHZPzl9u6u4/CoBcu1I I8GESeBrhtNOoqihyP4EN90yZooiC7meHkNsupOH5I2KOB2wPk5TuFQE1BpXs77v7kDm Heqw==
MIME-Version: 1.0
X-Received: by 10.60.4.165 with SMTP id l5mr8332717oel.84.1360489621122; Sun, 10 Feb 2013 01:47:01 -0800 (PST)
Received: by 10.60.27.74 with HTTP; Sun, 10 Feb 2013 01:47:00 -0800 (PST)
Received: by 10.60.27.74 with HTTP; Sun, 10 Feb 2013 01:47:00 -0800 (PST)
In-Reply-To: <201302100346.r1A3k4Ue1561926@shell01.TheWorld.com>
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> <201302100346.r1A3k4Ue1561926@shell01.TheWorld.com>
Date: Sun, 10 Feb 2013 09:47:00 +0000
Message-ID: <CAKHUCzzhc2O7kO8W1bW0mqb4Noiq+qxEeo_ujmztpLsy+RBriQ@mail.gmail.com>
Subject: Re: I-D affects another or work in ietf groups
From: Dave Cridland <dave@cridland.net>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=e89a8ff1c2e8966e3004d55bac92
X-Gm-Message-State: ALoCoQmJtFzv0ilFHTW0hj/6AxHQyOL7AdrGi3kKAYWfc4UEOBFH9zb68om6VbzGxU/SUFxtif6l
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2013 09:47:03 -0000

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

On 10 Feb 2013 03:46, "Dale R. Worley" <worley@ariadne.com> wrote:
> In any case, if you are doing something incorrect in your review,
> presumably people will call your attention to that fact, and explain
> how you should change what you are doing and why you should change it.

And on this note, doing something wrong and being corrected is always a
better choice than not doing something.

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

<p dir="ltr"><br>
On 10 Feb 2013 03:46, &quot;Dale R. Worley&quot; &lt;<a href="mailto:worley@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br>
&gt; In any case, if you are doing something incorrect in your review,<br>
&gt; presumably people will call your attention to that fact, and explain<br>
&gt; how you should change what you are doing and why you should change it.</p>
<p dir="ltr">And on this note, doing something wrong and being corrected is always a better choice than not doing something.</p>

--e89a8ff1c2e8966e3004d55bac92--

From jari.arkko@piuha.net  Sun Feb 10 02:57:45 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27FA621F843D for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 02:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_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 fZnjqTzfSLop for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 02:57:44 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 0A21921F84F9 for <ietf@ietf.org>; Sun, 10 Feb 2013 02:57:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 5A07F2CC43; Sun, 10 Feb 2013 12:57:41 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xaYqCe_6jfBE; Sun, 10 Feb 2013 12:57:40 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A0CFB2CC3B; Sun, 10 Feb 2013 12:57:39 +0200 (EET)
Message-ID: <51177D22.3070904@piuha.net>
Date: Sun, 10 Feb 2013 03:57:38 -0700
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: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130209090616.0a22ba20@resistor.net>
In-Reply-To: <6.2.5.6.2.20130209090616.0a22ba20@resistor.net>
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: Sun, 10 Feb 2013 10:57:45 -0000

SM,

Many thanks for your feedback.

I will incorporate your suggestions and few other people's comments in a new version of the document.

Some further discussion on a couple of points that deserve it:

> I read draft-arkko-iesg-crossarea-03 as I am trying to learn about the IETF.  In Section 2:
>
>    "This work has been going on in the TRILL WG on the Internet Area
>     and in parallel in the ISIS WG on the Routing Area."
>
> There is an assumption that I know what "WG" means.
>
> The actual problem is finding out what's the main topic of the draft within an IETF context and identifying the proper working group.  There should also be someone to identify related topics which will be useful as input for the draft to progress.  The IESG part of the "process" is more about identifying which working groups should be chartered and in which area they should fall. The Area Shopping heading looks at the problem from an IESG perspective.  The "lowest bar" is the IETF participant's perspective. 
> It took me some time to understand that the draft was about how work is organized in the IETF.  I didn't really understand what area means except that Routing Area must have something to do with router and Security Area must have something to do with security.  I decided to read the Informational reference and I learned that it is a management division within the IETF.
>
> I suggest having some text in Section 1 to introduce the areas.

Admittedly, the document was written from the perspective of the IETF managers (ADs, WG chairs) but comments from you and Brian have led me to understand better that we need to include more about the participant aspect as well.

> In Section 3:
>
>   "Cross-area work is needed, of course, in any situation where a
>    particular technical problem does not cleanly map to one
>    organization."
>
> Shouldn't that map to a working group?

Normally, yes, but I could imagine topics that are wider than one working group but still within an area.

>
> In Section 4:
>
>   "But it is also possible that concerns raised in one forum are
>    not understood in another, and this can lead to an effort going
>    forward after finding the "lowest bar" forum to take it up."
>
> Brian Carpenter commented about Area Shopping in his Gen-ART review.  Scrolling back to Section 3, "from an IETF participant's point of view, it is important that there is a working group where the technical topic that he or she is interested in can be discussed.  The problem is how to identify that working group.  I went to http://datatracker.ietf.org/list/wg/  to find the working group where I can discuss about my solution to an IPv6 problem.  I found "IPv6 Maintenance".  I am not sure what that group does.  As the problem affects IPv6 operations I picked the "IPv6 Operations" working group.  I post a message to the mailing list.  There isn't any reply.  My solution does some DNS stuff.  I try the "Domain Name System Operations" working group.  I keep trying various mailing lists until I find the "right" venue.

The best place to find out what topics belong under a working group is within the charter page, e.g., http://tools.ietf.org/wg/<somewg>/charters (although for some working groups, particularly long-lived generic groups such as v6ops, 6man, dhc, etc. the charter usually does not outline the specific current work items). The working groups chairs are helpful and also usually quite knowledgeable about what is going on in the IETF even outside their own groups, and can help you find the right venue.

>   "For the regular participant it is difficult to find out where there
>    are important documents that would deserve more review."
>
> It's not a matter of important documents.  I would say that it is about the regular participant being able to find that document which he/she believes is important or the subject of discussion where his/her input would be helpful.

Right.

Jari



From abdussalambaryun@gmail.com  Sun Feb 10 03:08:07 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E4E421F8477; Sun, 10 Feb 2013 03:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mJPdSRD4tUV9; Sun, 10 Feb 2013 03:08:06 -0800 (PST)
Received: from mail-we0-x230.google.com (we-in-x0230.1e100.net [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id DBDD021F842D; Sun, 10 Feb 2013 03:08:05 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id s43so4027820wey.21 for <multiple recipients>; Sun, 10 Feb 2013 03:08:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=scUpXA3tdj74iU3gt/Z/s6ydRgKStWEb0KDFD5gEYx8=; b=uhbH/pkNeur9fOnFB9vDFYWa6aBujV7FMQ2DSuIu06jvnvESB1jjA251UX/MvlsBRi O2pCSSGDiK//FMN7tf6Z6PjHW+VxBgnS7eYczVhjiNBpbP3ITZ9JffmDLNEr+IbfKR3n vXzJOTl3nHVIFNF6TTDsNIxU/zRFhJ2ME7qJDKRg3qMUg9MsSSTdDdc4NX0Jirxqs2FB 4F3wJab79R79wqz5FE5bPRCTHUefiEX6eO6XT5Il6rPdMiZUxMBQrvsBYjoagTJ6q4Uu jOmBYadWZ/vYg3xqPLCQeT05rrCZADV/AiuVT+qWTRBU4/89GV3oTMshYytjm25qUsJW aljw==
MIME-Version: 1.0
X-Received: by 10.194.109.102 with SMTP id hr6mr18246851wjb.24.1360494484966;  Sun, 10 Feb 2013 03:08:04 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 10 Feb 2013 03:08:04 -0800 (PST)
In-Reply-To: <20130207132146.18387.62853.idtracker@ietfa.amsl.com>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com>
Date: Sun, 10 Feb 2013 12:08:04 +0100
Message-ID: <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-cardenas-dff@tools.ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 11:08:07 -0000

Reply to your request dated 07/02/2013
Also following AD advice.
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 10/02/2013

Reviewer Comment #AB1: Related to Aim and Terminology.
++++++++++++++++++++++++++++++++++++

Overall I support the work, but subject to amendments.

The Abstract is interesting but seem general

>    This document specifies the "Depth-First Forwarding" (DFF) protocol
>    for IPv6 networks,

AB> do you mean all IPv6 networks, if some please mention *some*

>    a data forwarding mechanism that can increase
>    reliability of data delivery in networks with dynamic topology and/or
>    lossy links.

AB> IPv6 considers dynamic topology, does the paragraph mean that some
networks are static topology. Suggest to clarify the dynamic
frequency. Also not clear what is missing with IPv6 protocol in such
nets that needs DFF.

>  The protocol operates entirely on the forwarding plane,
>    but may interact with the routing plane.

AB> amend> entirely on the forwarding plane,
           to; entirely within the forwarding plane,

>    The routing plane may be informed of
>    failures to deliver a packet or loops.

AB> Amend> routing plane may be informed
          to;   routing plane protocols may be informed

Terminology section>

AB> you need to define that all routers have the DFF protocol, even
though it is known by heart that any forwarder needs to run DFF but
you MUST mention that at least to the reader,

AB> you missed to define the Router, which is mentioned many times but
I don't know which one. I think it is a must because you refer to two
planes forwarding and routing planes. Please define the Forwarder as
well. I don't find any Forwarder action in the draft, why not while
you specify there is a forwarding plane!

AB> suggest that you explaine forwarding and routing in separate and
show where they join relating to your protocol.

This will not be the last, will continue,

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------



On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>   <draft-cardenas-dff-09.txt> as Experimental RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document specifies the "Depth-First Forwarding" (DFF) protocol
>    for IPv6 networks, a data forwarding mechanism that can increase
>    reliability of data delivery in networks with dynamic topology and/or
>    lossy links.  The protocol operates entirely on the forwarding plane,
>    but may interact with the routing plane.  DFF forwards data packets
>    using a mechanism similar to a "depth-first search" for the
>    destination of a packet.  The routing plane may be informed of
>    failures to deliver a packet or loops.  This document specifies the
>    DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>    addition also for LoWPAN "mesh-under" networks (as specified in
>    RFC4944).
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>    http://datatracker.ietf.org/ipr/1645/
>    http://datatracker.ietf.org/ipr/1646/
>
>
>
>

From jari.arkko@piuha.net  Sun Feb 10 03:40:40 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18CCB21F8919 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 03:40:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q4mL4kVRRXeb for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 03:40:39 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5F821F853D for <ietf@ietf.org>; Sun, 10 Feb 2013 03:40:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 38D232CC43; Sun, 10 Feb 2013 13:40:37 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0ActOTX4x7B; Sun, 10 Feb 2013 13:40:35 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 7DE612CC3B; Sun, 10 Feb 2013 13:40:34 +0200 (EET)
Message-ID: <51178731.2020109@piuha.net>
Date: Sun, 10 Feb 2013 04:40:33 -0700
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: adrian@olddog.co.uk
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
References: <004e01ce06dd$5dfaf530$19f0df90$@olddog.co.uk>
In-Reply-To: <004e01ce06dd$5dfaf530$19f0df90$@olddog.co.uk>
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: Sun, 10 Feb 2013 11:40:40 -0000

Adrian,

Many thanks for your careful review and thoughts. A couple of follow-ups inline:

> In several places, this document is careful to state that the text
> represents the personal view of the author (Section 4 "Process vs.
> Substance", Section 5, Appendix 5).  This is fine as far as it goes, but
> leads to three issues:
>
> 1. The filename gives the impression that this is an IESG document
>     I don't believe there is any point in fixing this because once
>     published as an RFC the I-D filename is almost completely forgotten.
>
> 2. The clarity about the document being the author's personal opinion is
>     missing from the Abstract and Introduction making it hard for the
>     reader to understand this fact. This is easily fixed.
>
> 3. It is not clear what it would mean to have IETF consensus on this
>     document. Would it mean that the IETF agrees that this is the
>     author's opinion? So, please be careful to not accidentally attach
>     the "IETF consensus" boilerplate to this document if it is published
>     as an RFC. (Actually, it would be good if the IETF last call for
>     this type of document called out the "not seeking consensus" fact so
>     that the community understands what type of review they are doing
>     and how their comments will be handled.) The action here is on the
>     sponsoring AD and the IESG as the document goes for publication - it
>     would be really good to put in an RFC Editor note early so that this
>     does not get lost.

Good points. There is a more general underlying issue, how do we publish informational documents (boilerplate, last call, etc) and in particular process-related documents. I think we'll end up discussing that in the IESG more generally. Thanks for raising the issue.

FWIW, this particular document started out a couple of years ago as a documentation of the experience that we had gained at the time. It is a "Considerations on X" -type document. There is no fundamental reason why it couldn't be achieve either IESG or even IETF consensus. However, I have at least not personally been focused on that. I've been more focused on documenting observations that might be useful for readers, and publishing them as a record of thinking at the time. But there is no claim that this is all there is to say about the topic. So, if we for some reason decided that we'd want to make the document header say this has the consensus of the IETF, I'd still want to avoid making too broad claims about the document's completeness and validity in all situations.

> I would find it helpful if the Introduction gave some sort of management
> summary: Who is supposed to read / act on this document? What actions
> are they supposed to take?
>
> For example (but with no intent to constrain the author), this could be
> aimed at the wider IETF community with the intent of getting them to
> understand that it means something special for a working group to be in
> a particular area. Or it could be aimed at the IESG with a view to
> getting them to consider the implications of cross-area work on the IETF
> organisation.

The document has been mostly aimed at ADs and WG chairs, though, as pointed out in recent list discussion, other contributors may be tackling the same issues but from a different angle (which area do I submit my work?). The next version wll try to make the intended readers clearer.

> I think that the description of LWIG in Section 2 is wrong to limit the
> scope to "the TCP/IP stack and application protocols." The charter is
> far wider than that and embraces routing and operations protocols as
> well.

Will fix.

> Section 2
>
> I would suggest:
>
> OLD
>     o  The Routing Area, Transport Area, and Security Area have worked
>        together on security mechanisms and key management tools necessary
>        to secure BGP sessions carried on top of TCP.  For instance, the
>        SIDR and KARP WGs are in the Routing Area, but they are clearly
>        focused on topics that are generally found in the Security Area.
> NEW
>     o  The Routing Area, Transport Area, and Security Area have worked
>        together on security mechanisms and key management tools necessary
>        to secure routing protocols, including those carried on top of
>        TCP.  For instance, the SIDR and KARP WGs are in the Routing Area,
>        but they are clearly focused on topics that are generally found in
>        the Security Area.
> END

Good. Thanks.

> I think Section 2 should acknowledge RFC 2223 and RFC 3552 with respect
> to how security crosses into all areas.  Similarly, you should mention
> RFC 5706 with respect to how management and operations cross into all
> areas.

Good points.

> I also think the example in the last bullet of section 2 is a bit weak.
> You should probably also discuss the way that many protocol working
> groups develop data models (e.g., MIB modules), yet NETMOD is developing
> data models for protocols and entities in other areas. Similarly, you may
> want to introduce I2RS.
>
> Lastly, the same bullet is missing a discussion of OAM protocols worked
> on in protocol working groups (such as MPLS and TRILL).

OK

> The start of Section 3 seems to contradict the discussion of splitting
> work into different WGs either to share the load or to attract the right
> area participants. You say:
>
>     From an IETF participant's point of view, it is important that there
>     is a working group where the technical topic that he or she is
>     interested in can be discussed.  The area and the management
>     structure matters little for this, as long as the working group can
>     work on all of the relevant aspects.

Hmm. I'll see what I can do.

> I share some of Brian's views on "Area Shopping". The flip of what some
> may perceive as shopping is what the authors perceive as "Being pushed
> from pillar to post without anyone taking proper responsibility for
> finding the correct home for the work." The IESG has a responsibility to
> ensure that work that needs to be homed in the IETF is found a home. The
> IESG equally has a responsibility to ensure that work that does not
> belong in the IETF (for any of a number of reasons) or is not yet
> properly formed, does not "sneak in".

Right.

> The answer to this, I am afraid,
> lies in proper communication and mutual trust within the IESG.

Definitely. And some hard work to determine what the topics really are about.

> Suggestions for inclusion in Section 4 would be:
>
>     Engineers Will be Engineers
>
>     Observing that engineers will often look for an existing tool (for
>     example, a hammer) to address a new problem (for example, a screw).
>
> and
>
>     Don't Break the Internet
>
>     Some pieces of the Internet infrastructure may be considered a little
>     fragile. This understanding does not always extend beyond the working
>     group maintaining the associated technology, so there can be a real
>     tension when a working group (usually in another area) decides to use
>     the technology in a novel way without either proper discussion or
>     proper separation.

Yep. This is a very good addition.

> The piece about cross-area review is important, but is hiding in "Rigid
> Topic Ownership" in Section 4. There are three additional problems
> associated with cross-area review:
> 1. It is not clear where to send cross-area review requests
> 2. Cross-area reviews, when requested, rarely happen
> 3. The ramp-up needed to achieve a cross-area review can often be huge

Yes.

> I suspect that the recommendations concerning scheduling, while
> addressing the primary problem, do not recognise an underlying issue.
> Thus, addressing the conflicts between meeting slots in order that, for
> example, all appropriate routing experts could attend TRILL, would lead
> to a longer IETF week with fewer parallel sessions.
>
> An alternative, is to recognise that ADs are *not* the gate in
> scheduling. It is not necessary for ADs to attend even all of the
> working groups that they are responsible for. They may be interested in
> attending other working groups as well, but it is not necessary for them
> to be there.

I certainly agree.

> I also think that one of the important aspects of managing cross-area
> work goes beyond getting the language right in charters. Brian observes
> that several of the OPS working groups have charter text explicitly
> stating that "protocol development will not be done in this WG", making
> the WG responsible for problem statements, requirements, and
> applicability, and placing the responsibility for protocol development
> in other WGs often in other areas. This is great if and only if the
> charter is observed! By the time a protocol spec arrives at the IESG as
> a publication spec, it is pointless to try to control what has happened -
> the best that can be done is to send the document for wider review. What
> clearly needs to happen is for working groups to observe their charters,
> for working group chairs to be stricter, and for ADs to stay on top of
> this type of issue.
>

Yes. Another good thing to talk about.

Jari


From barryleiba.mailing.lists@gmail.com  Sun Feb 10 05:54:43 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43BBE21F84C9 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 05:54:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.898
X-Spam-Level: 
X-Spam-Status: No, score=-102.898 tagged_above=-999 required=5 tests=[AWL=0.079, 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 L-eHwyHr0rXa for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 05:54:42 -0800 (PST)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFFA21F84B2 for <ietf@ietf.org>; Sun, 10 Feb 2013 05:54:42 -0800 (PST)
Received: by mail-vc0-f175.google.com with SMTP id fw7so3297686vcb.6 for <ietf@ietf.org>; Sun, 10 Feb 2013 05:54:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Z0U9Vek4kJuIVwoBnjFawXzMkkjJY9OsaQUmal75CyM=; b=h1ccIBVHvb+h+NFQsAutkx476IJuP3vcUqPHnHC2uoMWVERlizcYVr8o/hVYct1M5x 5N409ebndVQhb64OJJgforBx191BmR49JE6MOTnIZ8Hfwvg+UdD4XLqRw1CDaHE5BCWC KFA7cgyolHJWnLaHDilPPiHw1JQJ5cqvokfNXGleswjZIwd6zXihItAcRPpw9K7uaPg2 CDrwWjOhyZL+KOCFTugBaVekDDrNWErtH8Qv0uK6u+z/jd7fGZ73UYrKRtgio4ZBDbpy p+Oe2ZU3Oi0e+99hPbeTXTIwKNnExDY2UyFZpBTVfFI1qDN+iaD7FjE5fh2t8hpUFVcJ kilA==
MIME-Version: 1.0
X-Received: by 10.221.9.136 with SMTP id ow8mr14606985vcb.58.1360504481044; Sun, 10 Feb 2013 05:54:41 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Sun, 10 Feb 2013 05:54:40 -0800 (PST)
In-Reply-To: <CADnDZ89kbqcNtUhKNa-pDDrqn2SSaDW2zm1SBSdOOqo5EkftFQ@mail.gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <201302100346.r1A3kvag1559644@shell01.TheWorld.com> <CADnDZ89kbqcNtUhKNa-pDDrqn2SSaDW2zm1SBSdOOqo5EkftFQ@mail.gmail.com>
Date: Sun, 10 Feb 2013 08:54:40 -0500
X-Google-Sender-Auth: TKDGXKoYeyyzgGTbsn6Cw4jQlYQ
Message-ID: <CAC4RtVCXpP-eBJ=OWgN8JX=NU5mqcF9xneu-bgMhLbfnggoX0w@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Barry Leiba <barryleiba@computer.org>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
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: Sun, 10 Feb 2013 13:54:43 -0000

A couple of points here:

>> In practice, that depends on the judgment the document author; does
>> the document author feel that you have made a "significant"
>> contribution to the document?
>
> I agree that it is responsibility of owners or authors. In IETF the
> I-D may be a WG I-D so the group work together to feel what is best,

This actually varies.  Working groups will sometimes direct
authors/editors on what should be in the Acknowledgments section, but
more often it's left to the judgment of the authors/editors -- it's
their section.  And, yes, authors sometimes include family, departed
colleagues, and even software ("This document was prepared using
xml2rfc version x.y.z.").

> Also depend on *why* the acknowledge section. Authors don't only ACK
> because of significant contributions
...
> In IETF it is all about discussions and comments
> for its I-Ds and RFCs, new comers' participation make the discussions
> valueable in my opinion,

Read carefully what Dale said: he did not say "contributed significant
text", but "made a significant contribution".  We very often
acknowledge people who gave particularly useful reviews, had
particularly important roles in discussions, contributed ideas, and
such.  It's about how the document got to where it is, so, yes,
discussions and comments, and newbies as well as grey-beards.

>> My belief is that one must participate in the IETF fairly intensively
>> for six months to a year before one can gain a reputation as being a
>> knowledgeable contributor.  After all, most of the people authoring
>> documents have been participating for several years -- and they
>> already know each other.  Before you have gained that reputation, it
>> may be difficult to get people to pay attention to your contributions,
>> even if they are objectively valuable.  I describe the rule in the
>> IETF as "Everyone may speak; not everyone is listened to."  You need
>> to prove yourself to be a person worth listening to.
>
> I agree, but we should n't ignore voices of new participants, and
> don't ignore people that are listening and never participate.

Absolutely, and no one here purposefully ignores the voices of new
participants.  Dale is speaking not about what *should* happen, but
what our human nature is: we naturally pay closer attention to people
we already know and respect, whose contributions have previously been
shown to be valuable.  New participants who understand this and join
the community with an eye toward showing their value in that way (as
Dale noted, see RFC 4144) are accepted more quickly.  In an ideal
world, if the first word you post to a mailing list is useful, you
should be acknowledged, praised, and accepted.  Normal human social
interactions work against that, unfortunately.

> Your right, however, just to add that I don't participate in IETF to
> make reputation, because I think it is not a place for reputation, I
> try to participate to volunteer in the Internet Community to add to my
> Internet knowledge and others,

You aren't seeking reputation in the world at large, no... but you
must develop a good reputation among the other IETF participants --
that's what Dale's saying.  It's that human nature thing.

You want to get to a place where people say, "When AB says something,
pay attention, because he's usually right."  We all have people like
that in our areas of expertise, and we all know who they are.

Barry

From abdussalambaryun@gmail.com  Sun Feb 10 08:17:32 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ADCE21F83EF; Sun, 10 Feb 2013 08:17:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyl3pvscANhb; Sun, 10 Feb 2013 08:17:31 -0800 (PST)
Received: from mail-we0-x235.google.com (we-in-x0235.1e100.net [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2850F21F8319; Sun, 10 Feb 2013 08:17:30 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id t44so4186838wey.12 for <multiple recipients>; Sun, 10 Feb 2013 08:17:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=3x9xykwf8JugkInY2qRfLwR4DK7zqbXqRmY7d6KJq4o=; b=tso69nHvyHWQS8E63370QwQ4Aj9RXcOLZNhC29cnApth8uXtpGtvTWESSZLBMZG0cM eBg6VHq9b1WSrvRCDpvEZhMTKq3bF8GlWBmwdmr2SzV/zfxmhn5u/ydCz0obYH1XntTB eRI3V/bNzjALYD9uv6yftfoV/4lhqRhEumGXJFfTeXIZwgM3Dv2ZVz/dNX6KUK1KAeMa JdL7IpR4VklexlIbQB87FHEVxPsyZgccmb8ZBWYWwoy1Sjq9ersbbsmbfqIQjFjG9PIG 86V9hPCKXZVSMWXhr4IoEXHNxpUtBweDBi1ctvdQDG1ES6exHTLGQNHPP2Hp/6ZHqVdt 7Lfg==
MIME-Version: 1.0
X-Received: by 10.180.77.35 with SMTP id p3mr11614217wiw.18.1360513050259; Sun, 10 Feb 2013 08:17:30 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 10 Feb 2013 08:17:30 -0800 (PST)
In-Reply-To: <20130206234933.11375.20586.idtracker@ietfa.amsl.com>
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com>
Date: Sun, 10 Feb 2013 17:17:30 +0100
Message-ID: <CADnDZ8-ozePyTYQYVKncz3Bko6Bsg_19U59N1KqD_czHwduxMA@mail.gmail.com>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2013 16:17:32 -0000

Reply to your request dated 07/02/2013
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 10/02/2013

Reviewer Comment #AB1: I-D Overall Idea and Aim
++++++++++++++++++++++++++++++++++++
I support strongly the idea-work but not publication, the draft needs
to be completed (i.e. the aim was not targeted well). The work should
involve the IESG, or analysis of process procedures in IETF including
IESG. A survey of the IESG members' opinion will help the work value.

I don't think a description of the examples/problem/challenges and
giving recommendation is enough for this work. I recommend the draft
adds analysis of process of the IETF best practices. From the draft we
may understand that our best practices are not recommended, the author
does not mention related RFCs and other BCPs than RFC2026 (is it the
only related document?).

AB> the abstract should include that the draft is the authors opinion,
it was only mentioned in acknowledgement.
AB> Questions> What is missing in IESG? how they have no strategy?
very strange to me to read the section related to IESG without any
reference or history? Is the document based on the author's point of
view, not mentioned in Abstract how he evaluated the
processes/problem?

AB> The author should mention that he is a member of IESG and for how
long with dates at least. I recommend more referencing or reasons why
author beleives that. The reviewer does n't consider all the author
beleives only if reads the proof/reference reason.

This will not be the last message, will continue,

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------


On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Experiences from Cross-Area Work at the IETF'
>   <draft-arkko-iesg-crossarea-02.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-03-06. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This memo discusses the reasons for IETF work on topics that cross
>    area boundaries.  Such cross-area work presents challenges for the
>    organization of the IETF as well as on how interested parties can
>    participate the work.  The memo also provides some suggestions on
>    managing these challenges.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-arkko-iesg-crossarea/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-arkko-iesg-crossarea/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From hsantos@isdg.net  Sun Feb 10 08:28:09 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B10B21F8439 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 08:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.814
X-Spam-Level: 
X-Spam-Status: No, score=-101.814 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+BprKLt-1e4 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 08:28:08 -0800 (PST)
Received: from ntbbs.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 66AA121F8438 for <ietf@ietf.org>; Sun, 10 Feb 2013 08:28:08 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6778; t=1360513680; h=Received:Received: Message-ID:From:To:Subject:Date:Organization:List-ID; bh=OkoBOTX eFK+Tm73VQSqh+131uf4=; b=Q2dpSynlfOLmOuROS+iGgOMbKi7OEYN49eig5X9 6zLd2RW69lLfAIX5LCz4Hw7uGd06nwHxQkbHaAaCGxf+tTWrV04dzl2k2YRg4qnC mvLJZZJoBH8bhnQqE4/u4Fgp6pJ0krIP5sWHXZMvuWu4gZ+N3jC3uDgbW5ZOczxQ 80wY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 10 Feb 2013 11:28:00 -0500
Received: from main2 ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3650407170.28201.3024; Sun, 10 Feb 2013 11:27:59 -0500
Message-ID: <DA3655990F3544BEA0889227727DC303@addom.santronics.com>
From: "Hector Santos" <hsantos@isdg.net>
To: "Barry Leiba" <barryleiba@computer.org>, "Abdussalam Baryun" <abdussalambaryun@gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com><201302100346.r1A3kvag1559644@shell01.TheWorld.com><CADnDZ89kbqcNtUhKNa-pDDrqn2SSaDW2zm1SBSdOOqo5EkftFQ@mail.gmail.com> <CAC4RtVCXpP-eBJ=OWgN8JX=NU5mqcF9xneu-bgMhLbfnggoX0w@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
Date: Sun, 10 Feb 2013 11:26:25 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.3790.4657
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4721
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: Sun, 10 Feb 2013 16:28:09 -0000

Notice 4144 has no acknowledgements except for the RFC editor =
sponsorship. :)

Most I see is common sense, but my view, in my somewhat limited work =
areas I have participating in, it doesn't matter if the editor/author =
doesn't like you.  I guess that would be the exception. I think overall =
4144 doesn't quite consider the "part time" IETF warrior, such as =
myself. Even if you could practice 4414 (except maybe not attend IETF =
meetings yet which you have stated is basically required to get people =
to feel comfortable with you), be 100% instructmental in the genesis of =
getting work and even RFCs initiatiated and done and yet no =
acknowledgements (acks) of your input is recognized.  Again, not a big =
thing for me. I am not looking for a pat on the back (its already sore =
from my earlier years). Its not something I would normally expect to be =
thinking about. I'm an engineer first and normally just hope to avoid =
conflicts, including potential conflicts. To me, "Getting it right.... =
The First Time" is the most important quality to look for in work. But I =
have to say, I still not uset to the IETF competitive nature inherently =
has.  4144 touches base with some of this, in regards to making sure you =
can communicate with others. But I'm from a schoole where it should be a =
natural professional action of working with your peers at all levels, =
that basically dictates the work done.=20

Nonetheless, its all seems to be on the editor 99% of the time. =
Sometimes it seems random. Sometimes it intentionally and strategically =
prepared. I've seen acks where I never notice any input in a WG yet the =
name(s) was added most likely to add some "endorsement" value.  Which is =
not a bad idea - its what I will look for as well.  But to exclude =
critics is a questionable decision. I can understand why as well, but =
readers seeing the critics can often add weight to the higher level of =
review done.   Personally, if I didn't agree with an I-D or its =
direction, I have asked the Editor to remove my name. I've done that =
twice. Twice I have reminded editors; one added it and the other =
basically decided against the request. Can't worry about that. I feel it =
usually comes back to the person in some form or another.  Thats becomes =
a personal thing only which is probably not the norm when considering =
these things. Overall what the Editor/Author feels adds value to the =
document, and how it can help it reach the next stage, "SHOULD" be a big =
part of the considerations. Endorsement value should be a big part of =
it.  It helps readers to see respected technical people who have =
"reviewed" docs, including known critics whether you respect their =
credentials or not, are PITA or otherwise.  If the EDITOR needs to =
exclude input from critics, the doc probably has a problem in the first =
place. =20

----- Original Message -----=20
From: "Barry Leiba" <barryleiba@computer.org>
To: "Abdussalam Baryun" <abdussalambaryun@gmail.com>
Cc: "IETF discussion list" <ietf@ietf.org>
Sent: Sunday, February 10, 2013 8:54 AM
Subject: Re: The RFC Acknowledgement


>A couple of points here:
>=20
>>> In practice, that depends on the judgment the document author; does
>>> the document author feel that you have made a "significant"
>>> contribution to the document?
>>
>> I agree that it is responsibility of owners or authors. In IETF the
>> I-D may be a WG I-D so the group work together to feel what is best,
>=20
> This actually varies.  Working groups will sometimes direct
> authors/editors on what should be in the Acknowledgments section, but
> more often it's left to the judgment of the authors/editors -- it's
> their section.  And, yes, authors sometimes include family, departed
> colleagues, and even software ("This document was prepared using
> xml2rfc version x.y.z.").
>=20
>> Also depend on *why* the acknowledge section. Authors don't only ACK
>> because of significant contributions
> ...
>> In IETF it is all about discussions and comments
>> for its I-Ds and RFCs, new comers' participation make the discussions
>> valueable in my opinion,
>=20
> Read carefully what Dale said: he did not say "contributed significant
> text", but "made a significant contribution".  We very often
> acknowledge people who gave particularly useful reviews, had
> particularly important roles in discussions, contributed ideas, and
> such.  It's about how the document got to where it is, so, yes,
> discussions and comments, and newbies as well as grey-beards.
>=20
>>> My belief is that one must participate in the IETF fairly =
intensively
>>> for six months to a year before one can gain a reputation as being a
>>> knowledgeable contributor.  After all, most of the people authoring
>>> documents have been participating for several years -- and they
>>> already know each other.  Before you have gained that reputation, it
>>> may be difficult to get people to pay attention to your =
contributions,
>>> even if they are objectively valuable.  I describe the rule in the
>>> IETF as "Everyone may speak; not everyone is listened to."  You need
>>> to prove yourself to be a person worth listening to.
>>
>> I agree, but we should n't ignore voices of new participants, and
>> don't ignore people that are listening and never participate.
>=20
> Absolutely, and no one here purposefully ignores the voices of new
> participants.  Dale is speaking not about what *should* happen, but
> what our human nature is: we naturally pay closer attention to people
> we already know and respect, whose contributions have previously been
> shown to be valuable.  New participants who understand this and join
> the community with an eye toward showing their value in that way (as
> Dale noted, see RFC 4144) are accepted more quickly.  In an ideal
> world, if the first word you post to a mailing list is useful, you
> should be acknowledged, praised, and accepted.  Normal human social
> interactions work against that, unfortunately.
>=20
>> Your right, however, just to add that I don't participate in IETF to
>> make reputation, because I think it is not a place for reputation, I
>> try to participate to volunteer in the Internet Community to add to =
my
>> Internet knowledge and others,
>=20
> You aren't seeking reputation in the world at large, no... but you
> must develop a good reputation among the other IETF participants --
> that's what Dale's saying.  It's that human nature thing.
>=20
> You want to get to a place where people say, "When AB says something,
> pay attention, because he's usually right."  We all have people like
> that in our areas of expertise, and we all know who they are.
>=20
> Barry
>


From abdussalambaryun@gmail.com  Sun Feb 10 10:59:40 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565FC21F8694; Sun, 10 Feb 2013 10:59:40 -0800 (PST)
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 l5DgYsFyxDya; Sun, 10 Feb 2013 10:59:39 -0800 (PST)
Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) by ietfa.amsl.com (Postfix) with ESMTP id DCF8021F85C0; Sun, 10 Feb 2013 10:59:38 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id dr13so4259144wgb.14 for <multiple recipients>; Sun, 10 Feb 2013 10:59:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Ar2pydr0b31s3wqMcrAcOTZSfMWNhEmZRP+EPbdDEhI=; b=mRPCgpcKoGB/+rYCp/wUC3z+amIphk4iyJiEcPeqfg/+txBT8OcQP9eMi0chTC7UCQ W+Wr8mjl0X4WIGKfOSRDQ2su5/vRfzFxtVefmCYdh8UeqihHGn8h2lRjG9Ol9KOY5hff 8zZtsRRPiLcpIPrzmZr6KwJelMbrpVppORUvrpY96lQvS6ijxdBTbDKHKG1CbWtYbIv3 pQn0PBiq8kChnIhumVnWiOtRtrRE55sDYZ4QYYE8UjCWcZixTFS8GpoVoz6V7xh0VIva QQEzfCVZsXBta55lNEuUCHQ0uWJIOmZul06/8z4GXSycjlVhwILVYYo+KlHj39FGqU0H WtRw==
MIME-Version: 1.0
X-Received: by 10.180.87.98 with SMTP id w2mr12031326wiz.30.1360522777866; Sun, 10 Feb 2013 10:59:37 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 10 Feb 2013 10:59:37 -0800 (PST)
In-Reply-To: <CADnDZ8-ozePyTYQYVKncz3Bko6Bsg_19U59N1KqD_czHwduxMA@mail.gmail.com>
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com> <CADnDZ8-ozePyTYQYVKncz3Bko6Bsg_19U59N1KqD_czHwduxMA@mail.gmail.com>
Date: Sun, 10 Feb 2013 19:59:37 +0100
Message-ID: <CADnDZ8_ghuD5Vhqf6vyOxcavadYdyapjyRFg+YUEYi28utCiRw@mail.gmail.com>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2013 18:59:40 -0000

Reply to your request dated 07/02/2013
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 10/02/2013
Reviewed I-D -03 (latest)
Reviewer Comment #AB2: Rationale for Cross-Area Work
++++++++++++++++++++++++++++++++++++
The section 3 explains cross areas but involves the security which the
reviewer disagrees. Security is already discussed and examined in all
areas separately but in the Security Area it is discussed crossly or
specifically, we may think that security experts are already experts
of different areas in IETF. The reviewer beleive in IETF separate
areas as separated TCP/IP model layers, or Internet-Networks. However
comments for I-D's section 3 below;

>Section 3: Rationale for Cross-Area Work

>The area and the management structure matters little for this, as long as the working group can work on all of the relevant aspects.

AB> not sure why cross-area WG, why not Cross-area Area (e.g. for
Security we already have), it is more related to crossing areas, the
I-D is discussing cross areas not cross WGs. The cross-area Area can
have a general cross-area WG, and specific cross-WGs

>different groups of people at the IETF.

AB> different Working Groups, people in IETF are equal not different

>In other cases different types of individuals may have specific
expertise that is helpful to solve a problem.

AB> IETF has equal individuals, but they have different type of
experiences and different responsibilities.

>Another common example of a situation where two different areas of
expertise are needed is developing security features for a protocol.
The protocol specialists are needed to understand the application and
its requirements and the security specialists are needed to help with
understanding the possible security issues and potential solutions.
Such work is commonly not organized as cross-area work, however.

AB> outside the IETF structure, security concerns/issues are already
considering to crossing TCP/IP layers, however, I disagree that we
involve it as a cross-area WG, because IMHO in IETF the Security Area
SHOULD already be considering cross-ietf-areas.

AB> Why all Works/Documents in IETF MUST consider a Security Section?
It is already an IETF practice. The answer may be because this field
of experts is involved within all IETF Areas and future technologies.


Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------

> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Experiences from Cross-Area Work at the IETF'
>>   <draft-arkko-iesg-crossarea-02.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-03-06. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    This memo discusses the reasons for IETF work on topics that cross
>>    area boundaries.  Such cross-area work presents challenges for the
>>    organization of the IETF as well as on how interested parties can
>>    participate the work.  The memo also provides some suggestions on
>>    managing these challenges.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-arkko-iesg-crossarea/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-arkko-iesg-crossarea/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>

From mstjohns@comcast.net  Sun Feb 10 13:02:16 2013
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4A0921F87E1 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 13:02:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.437
X-Spam-Level: 
X-Spam-Status: No, score=-100.437 tagged_above=-999 required=5 tests=[AWL=0.000, 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 OQPomBVyTwVF for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 13:02:16 -0800 (PST)
Received: from qmta15.westchester.pa.mail.comcast.net (qmta15.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:228]) by ietfa.amsl.com (Postfix) with ESMTP id 11E2E21F87E0 for <ietf@ietf.org>; Sun, 10 Feb 2013 13:02:15 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta15.westchester.pa.mail.comcast.net with comcast id yk3Y1k0021uE5Es5Fl2F5Z; Sun, 10 Feb 2013 21:02:15 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta16.westchester.pa.mail.comcast.net with comcast id yl2E1k0112kB7pQ3cl2F13; Sun, 10 Feb 2013 21:02:15 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 10 Feb 2013 16:02:12 -0500
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, Donald Eastlake <d3e3e3@gmail.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: The RFC Acknowledgement
In-Reply-To: <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.g mail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1360530135; bh=5ra7qlIduro3IGj/mO5LbM0ePeVKaQkh5J/fvZ5zIJM=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=fk4F+om+4dowpBV/8CHDXJOQnc4I3BuxzBv5dtIyINm0lo6cyR6du8fAf7ypXv+sA hvj9lRqsTMGA05O9ob2VQI5mBEW5ixaFImwrdROEYi145LDi/53zmal4m6qHlP/BwW Eko8rq3BcP9xZWgdpz6zbgFx/fxw55fwc7aWAAfvJ2yYgIg2INw3JxDAy9nfXtiTTI I17EbscVaDZHlGkOxejDKXsR9BGcRkQ8SnFv7MkZ8dcNpnqjsBuKU+mp0bGho2r2pE yFDbTe6bxOWUpIx+HpGchcctzuxltKoCQuGqIEnUdZ2/vySJaCL9dBkRSqqU4+IYc0 LeOLPom+g0HOQ==
Message-Id: <20130210210216.11E2E21F87E0@ietfa.amsl.com>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 21:02:16 -0000

At 11:04 PM 2/8/2013, Abdussalam Baryun wrote:
>The problem is that most people don't complain or don't like to
>complain, that is reality, they will leave such society easily.

Are we talking about the same IETF?

Seriously, this group as a whole does not tend to shy away from making their issues known, and mostly doesn't take their bat and ball and leave if things don't go their way.  

I'm joining this thread a little late  (I have read the later comments) and I want to push back on pretty much any formal requirement or common model for including people in the acknowledgements sections.  I believe this needs to be left to the document editor and to the chair, and for individual contributions, never pushed to an AD for resolution.

I have been told anecdotally that some companies or organizations provide bonuses or bounties of different values for employees that get their names on a ID or RFC as document editor, author, co-author or contributor (in the acknowledgements section).   I'm not sure of the reality with respect to this anecdote, but I'd hate to find some sort of mandatory "thank you" being required which might result in additional comments that add little or nothing to the process simply so someone can get a bonus.  It's simply not the IETF way.


Mike





From sm@resistor.net  Sun Feb 10 13:31:26 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5748A21F8BCE for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 13:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level: 
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Redu7rG+BHZK for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 13:31:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DF0B021F8AB1 for <ietf@ietf.org>; Sun, 10 Feb 2013 13:31:24 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1ALVBSY027412; Sun, 10 Feb 2013 13:31:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360531877; bh=Xbej/H5wSOp6MTf6mEE8bCHIpJfcNpuv0t8+B9chl/E=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=cBfS2nT4978yfp/lJU6y4E6wWn+RvRt2V2z67pFyyG7d3vcnhnHYl/xgMVzQYSo0y K0RKVUNYOxI3UMTeMUicsUv2tw2GF74OAuorXP+Wb479Hg15SAY/cbOTl03CSbZu6M ahwgjVbSbm9THZdpTLpU/99xWpX1xH35o55XzZUw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360531877; i=@resistor.net; bh=Xbej/H5wSOp6MTf6mEE8bCHIpJfcNpuv0t8+B9chl/E=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=n+xin7WEhKrBotk4we2J5y9rXfmIKHayRrb+vC4mikPbKZLWDkumNC8PeSW/8DEMf 3647ivd4swuOnVD3ek6qPznzsENzNYQe6SJNQ3zDCX8FnCGFBpDTkbnPZzTgFMdoXV 6Mo4M4AxguzHxO2lyFFUMMkBe7ducdmZ4IMvarEs=
Message-Id: <6.2.5.6.2.20130210123335.0a1e04f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 10 Feb 2013 13:11:05 -0800
To: Jari Arkko <jari.arkko@piuha.net>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
In-Reply-To: <51177D22.3070904@piuha.net>
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130209090616.0a22ba20@resistor.net> <51177D22.3070904@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Barry Leiba <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 21:31:26 -0000

Hi Jari,
At 02:57 10-02-2013, Jari Arkko wrote:
>Admittedly, the document was written from the perspective of the 
>IETF managers (ADs, WG chairs) but comments from you and Brian have 
>led me to understand better that we need to include more about the 
>participant aspect as well.

It's difficult to reconcile the two aspects.  The draft can end up 
being less effective.  I think that it is your individual perspective 
which brings value to the document.

>Normally, yes, but I could imagine topics that are wider than one 
>working group but still within an area.

My opinion is that topics can be wider than one working group and 
they can spill over other areas (cross-area).

Regards,
-sm  


From sm@resistor.net  Sun Feb 10 14:08:28 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B70D21F84EB for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 14:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xtNgJGpZ8YyB for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 14:08:27 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B46F21F84C9 for <ietf@ietf.org>; Sun, 10 Feb 2013 14:08:27 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1AM8E0T023830; Sun, 10 Feb 2013 14:08:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360534100; bh=2YeAM4GsYfOFsTRo5LXQLuyClj53n7Aea/o/rBsZtd4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dIrSTJsY58/AVAsopu9PvdzMgzUxYoo9LnRKHE+7ohZOOmH9BYKzDPa+Kb+PGe2l0 xSd6bumZWhs3mSbwAARFCz6FmhRrKVc5korYU8WV1jwX8LusrHvJSHhUT8mSCaQlN8 qiZFvubN/tWdeNhzAZBgAxTrMKpPdjOBgHRCSSuE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360534100; i=@resistor.net; bh=2YeAM4GsYfOFsTRo5LXQLuyClj53n7Aea/o/rBsZtd4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=t5MJJVR6TvENk6AbeUxyoLkb1IFLusp1VsS1j+B5r8g6dYMS8J3Y+4yeS94F2GfUI KnzqudfTE0FudgdJGzkFDs1KxHqVQRlaMxDlpbbPV9TjkxWkqV9FTTnqm8b8X15aAs iei+hCSBk+NVdsouWkxipR4P5J/GyX6qv2Oi2k3c=
Message-Id: <6.2.5.6.2.20130210133122.0a0a1c00@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 10 Feb 2013 14:05:58 -0800
To: Dave Cridland <dave@cridland.net>
From: SM <sm@resistor.net>
Subject: Doing something wrong (was: I-D affects another or work in ietf groups)
In-Reply-To: <CAKHUCzzhc2O7kO8W1bW0mqb4Noiq+qxEeo_ujmztpLsy+RBriQ@mail.g mail.com>
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> <201302100346.r1A3k4Ue1561926@shell01.TheWorld.com> <CAKHUCzzhc2O7kO8W1bW0mqb4Noiq+qxEeo_ujmztpLsy+RBriQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Feb 2013 22:08:28 -0000

Hi Dave,
At 01:47 10-02-2013, Dave Cridland wrote:
>And on this note, doing something wrong and being corrected is 
>always a better choice than not doing something.

Agreed.

Regards,
-sm 


From abdussalambaryun@gmail.com  Sun Feb 10 23:47:40 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5277D21F8551 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 23:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.51
X-Spam-Level: 
X-Spam-Status: No, score=-3.51 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 S10UZB6J9ZE0 for <ietf@ietfa.amsl.com>; Sun, 10 Feb 2013 23:47:39 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 4794521F854E for <ietf@ietf.org>; Sun, 10 Feb 2013 23:47:39 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id fg15so4393808wgb.1 for <ietf@ietf.org>; Sun, 10 Feb 2013 23:47:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=zvDYkl/3/siPtu+nrT6fO10ibABfi9vzzwBg+hmFxHM=; b=hKpG3yY/3RzdZkjB/dHRp6r39qX338ttO8MQMs8Y5UuOMZLi9puFXUWZAYTPiwybfm Gpc6Ga+AtAY2zr4pbU28VK63bc+hBIv+tv/Yp1GWYQu5bNgjXc8wULm8mJg8OP3s3oYX b9pQjdD0qN2ZSR8h7reZ7Rlzm0s5kV3+eNsYFXagPqgKWKqtOmihvRiYhTlL46rkc0RH uhDmXSNjShh6k2/reFAg7ozBKOXTA06sx3lsV8Y9wFOiROy3hudzKs8wb6e8+WUsGCyv INGPSoiEhmpcV4rQEmonqzctx45IVfzpWrLmI4hmy7cRUrrshL0AeDBm3ULpCptdcXuj y+wg==
MIME-Version: 1.0
X-Received: by 10.180.78.137 with SMTP id b9mr13987299wix.30.1360568858277; Sun, 10 Feb 2013 23:47:38 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sun, 10 Feb 2013 23:47:38 -0800 (PST)
In-Reply-To: <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com>
Date: Mon, 11 Feb 2013 08:47:38 +0100
Message-ID: <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 07:47:40 -0000

On 2/10/13, Michael StJohns <mstjohns@comcast.net> wrote:
> At 11:04 PM 2/8/2013, Abdussalam Baryun wrote:
>>The problem is that most people don't complain or don't like to
>>complain, that is reality, they will leave such society easily.
>
> Are we talking about the same IETF?

Yes, IETF considers all inputs even if accidently are contributions,
read the NOTE WELL.

>
> Seriously, this group as a whole does not tend to shy away from making their
> issues known, and mostly doesn't take their bat and ball and leave if things
> don't go their way.

not leave if things don't go their way, they leave if things don't go
in the right/fare direction.

Do you mean all contributors in IETF (i.e. who discuss and make input
even if not significant) like to continue participating? people leave
only when they find out that their volunteering input things may go in
the ways of profit sectors.

>
> I'm joining this thread a little late  (I have read the later comments) and
> I want to push back on pretty much any formal requirement or common model
> for including people in the acknowledgements sections.  I believe this needs
> to be left to the document editor and to the chair, and for individual
> contributions, never pushed to an AD for resolution.

Then from your opinion to be fare, I RECOMMEND that the RFC-section
SHOULD be changed to *Authors' Acknowledgements*. Please note that the
RFC is owned by the IETF so the section of ACK should not be only
thanks of the authors or editors or Chairs, otherwise SHOULD be
mentioned in title. IETF considers all inputs related to I-D as a
contribution, please read the NOTE WELL. So do we understand that IETF
is impolite with some of its contributors/workers?

>
> I have been told anecdotally that some companies or organizations provide
> bonuses or bounties of different values for employees that get their names
> on a ID or RFC as document editor, author, co-author or contributor (in the
> acknowledgements section).   I'm not sure of the reality with respect to
> this anecdote, but I'd hate to find some sort of mandatory "thank you" being
> required which might result in additional comments that add little or
> nothing to the process simply so someone can get a bonus.  It's simply not
> the IETF way.
>

It is not about bonuses, it is about truth I-D's influences and the
way the IETF process and work progresses. Do you think an I-D
progresses only if experts comment and contribute? don't think so,
best ideas come from discussions of different level of experiences
including zero,  :-)

We are in the IETF which has a NOTE WELL, do you suggest to change it
or change the IETF ways of using others information? I don't want to
change that. IMO a *thank you* for IETF participants SHOULD be a good
practice for IETF and its outputs or documents, because it reflects
reality.

AB

From dean.willis@softarmor.com  Mon Feb 11 06:41:09 2013
Return-Path: <dean.willis@softarmor.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD5421F8826 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 06:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sqWOpWNFIMwx for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 06:41:07 -0800 (PST)
Received: from mail-oa0-f49.google.com (mail-oa0-f49.google.com [209.85.219.49]) by ietfa.amsl.com (Postfix) with ESMTP id 3A49121F8800 for <ietf@ietf.org>; Mon, 11 Feb 2013 06:41:06 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id j6so6174952oag.8 for <ietf@ietf.org>; Mon, 11 Feb 2013 06:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=softarmor.com; s=google; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=HY7BHjOjtWnRbfXWQsLeWERi1RUwxKpE8ca3EErxHy4=; b=Ftui2ZIWkrBgH/V5Clu9Tx5AoHsBTLJ1hgT6Lh/UnKwFrF7FyK7O1R/BL0z2xdINqM 7+WVgtZ+krUVW6KjQnfcfpOZ2mfiA6Q0vGAuFm+w2nTCRYvrKeh39x+Ip9cKRlE8Q21b ADR413jzVR5uISLbogzAEllV4P52upt5MIgRk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=HY7BHjOjtWnRbfXWQsLeWERi1RUwxKpE8ca3EErxHy4=; b=A1ZMEA2vxpxzv90IAu2TZLj9cgfhbpupH4JcYz1OzmX6s4g0Z/W7vr2evgJrngy6ue jGFwid7SR48PRVMihsnlHWrPuIPlYbjTKjNhDmH/+2Z3SMRxZ9wOQ6WY3JRXO4h8Ltpu L6pkBFtPa0BAfVl9pfVKLpa1UmEdeho0mHu0ZAJ782/G9jazp5djU8udqzqTj+yXAobQ qus7JeQJlWte1jauDBld3JnnJkp8Y6p9upLag8eDzGy8Ip7AYLB90afY/Wcqznt0zrke ci8739HwUdcbCMqlvvsXms3p+1RIiO34dwt6eOZ502DjbY80yssUZwMKzM4lB2/Pr1bS nGbQ==
X-Received: by 10.60.32.243 with SMTP id m19mr10953731oei.13.1360593666337; Mon, 11 Feb 2013 06:41:06 -0800 (PST)
Received: from [192.168.2.114] (cpe-72-181-157-19.tx.res.rr.com. [72.181.157.19]) by mx.google.com with ESMTPS id v8sm49157082obj.1.2013.02.11.06.41.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 06:41:05 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: The RFC Acknowledgement
From: Dean Willis <dean.willis@softarmor.com>
In-Reply-To: <20130210210216.11E2E21F87E0@ietfa.amsl.com>
Date: Mon, 11 Feb 2013 08:40:54 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED1BBF7D-714D-48CF-B313-8F8CC2FBDDE4@softarmor.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <20130210210216.11E2E21F87E0@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQmmNNlIMte8h+mOTwMJcPWh+PO8jW15CuOjpShhdSNYNFe/LBkkBv4LPn/PCrIsy6yPmSj1
Cc: ietf Discussion <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 14:41:10 -0000

On Feb 10, 2013, at 3:02 PM, Michael StJohns <mstjohns@comcast.net> =
wrote:
>=20
>=20
> I have been told anecdotally that some companies or organizations =
provide bonuses or bounties of different values for employees that get =
their names on a ID or RFC as document editor, author, co-author or =
contributor (in the acknowledgements section).   I'm not sure of the =
reality with respect to this anecdote, but I'd hate to find some sort of =
mandatory "thank you" being required which might result in additional =
comments that add little or nothing to the process simply so someone can =
get a bonus.  It's simply not the IETF way.
>=20

I agree with everything you've said, and would happily prepare a cover =
page with both our names so that I can share in the credit for having =
said so.

Seriously, commenting on drafts is just a part of the work process, a =
part of the "social contract" of the IETF. People making minor comments =
on a draft shouldn't expect to be acknowledged in the draft for that =
contribution to the draft, any more than the pigeons unloading on a park =
statue should get acknowledged on the plaque for their contribution to =
the sculpture.

There are plenty of RFCs out there for which I've made large investments =
of time (say, over 10 hours, perhaps as many as 200 hours) that don't =
mention me. That's OK. Usually, if I have to work that hard on a draft, =
it was so bad that I really don't want my name on the final product =
anyhow ;-). After all, the purpose of having a name on top of the draft =
is to know who to blame for the content, which helps in predicting the =
value of their future contributions. Anonymity can actually boost one's =
credibility in such circumstances.

--
Dean Willis=

From magnus.westerlund@ericsson.com  Mon Feb 11 06:44:36 2013
Return-Path: <magnus.westerlund@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 778F321F89EE; Mon, 11 Feb 2013 06:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.604
X-Spam-Level: 
X-Spam-Status: No, score=-105.604 tagged_above=-999 required=5 tests=[AWL=0.645, BAYES_00=-2.599, HELO_EQ_SE=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 76OqIP6z33gE; Mon, 11 Feb 2013 06:44:34 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id EE88621F8715; Mon, 11 Feb 2013 06:44:33 -0800 (PST)
X-AuditID: c1b4fb2d-b7f316d0000028db-b8-511903d0a77e
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id E8.82.10459.0D309115; Mon, 11 Feb 2013 15:44:32 +0100 (CET)
Received: from [127.0.0.1] (153.88.115.8) by esessmw0184.eemea.ericsson.se (153.88.115.82) with Microsoft SMTP Server id 8.3.279.1; Mon, 11 Feb 2013 15:44:32 +0100
Message-ID: <511903CF.4050007@ericsson.com>
Date: Mon, 11 Feb 2013 15:44:31 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Matt Mathis <mattmathis@google.com>
Subject: Re: Last Call: <draft-ietf-tcpm-initcwnd-06.txt> (Increasing TCP's Initial Window) to Experimental RFC
References: <20121126212940.20378.58186.idtracker@ietfa.amsl.com> <50C06CE6.40909@ericsson.com> <CAH56bmAC9tgC3JQV1mAAuDipDbTkY7wx08xvZ7g6wfgKQYE=kQ@mail.gmail.com>
In-Reply-To: <CAH56bmAC9tgC3JQV1mAAuDipDbTkY7wx08xvZ7g6wfgKQYE=kQ@mail.gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMLMWRmVeSWpSXmKPExsUyM+Jvje4FZslAg59zLSyebZzPYnH+3CVW i20n5zM5MHss2FTqsWTJT6YApigum5TUnMyy1CJ9uwSujK2XZjIXdKZXnHj9nb2BcWFwFyMn h4SAicTlN71MELaYxIV769m6GDk4hAROMkrs0eti5AIylzNKnGxrYwWp4RXQlnjzqpEZxGYR UJU4smUeC4jNJmAhcfNHIxuILSoQLLHh4ComiHpBiZMzn4DViAioS1x6fhCshllAQWLXtNdg c4QFCiXuNK5lgli2hFFi8ot5jCAJToFAifkfP7GAHCQhIC6x5g0HRK+exJSrLYwQtrxE89bZ YHOEgG5raOpgncAoNAvJ6llIWmYhaVnAyLyKkT03MTMnvdxwEyMwYA9u+a27g/HUOZFDjNIc LErivGGuFwKEBNITS1KzU1MLUovii0pzUosPMTJxcEo1MDY52unLmbzw0V2t6jVZO1Z/Qxzf p4LEF2Ic4lf1S222nljy66Heeu4dL9d2H4ux8d8kqO/15fw6Yw3lw81TBXiex98V2v1jf8q/ 2E4L9VB+x5vOaf/eLNzBMnmBLk/v/uqIzadc21neavYeNjoR6f/55obWh+/Y/5/wXs4y28Nq D1NTRfyNHiWW4oxEQy3mouJEAL1Jt3kmAgAA
Cc: tcpm@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, 11 Feb 2013 14:44:36 -0000

On 2013-01-24 23:35, Matt Mathis wrote:
> Magnus,
> 
> In behalf of the draft-ietf-tcpm-initcwnd authors I publicly address
> the comments in your IETF LC  review of draft-ietf-tcpm-initcwnd-06.
> 
> In regards to interactions between IW and real time traffic (your
> points 1&2 below and echoed in Robert Spark's DISCUSS):
> 
> By design TCP creates queues to measure the bottleneck bandwidth.
> Reducing the jitter for real time traffic is not a goal for TCP.
> Although there are a number of TCP centric approaches for reducing
> jitter, including reducing queue space, deploying AQM and limiting IW,
> none are general nor work in all situations.   Furthermore if you
> construct a scenario where one of these approaches seems to help, a
> slight variation on that scenario will fail.  In the case of IW,
> larger transactions will produce equally large queue occupancy later
> on during slowstart or during bulk transfers.
> 
> This observation is borne out by the work of Ilpo Jarvinen et al.  See
> http://www.tschofenig.priv.at/cc-workshop/irtf_iab-ccirtcpaper9.pdf
> and the tcpm slides from IETF 84
> http://www.ietf.org/proceedings/84/slides/slides-84-tcpm-11.
> 
> We have not attempted to measure IW10 impact on real time traffic,
> however we have investigated over one year of historical performance
> data for our Hangout/Talk application where we track both the startup
> delay of an audio/video call as well as a jitter metric. Our data
> shows no degradation in either metric as IW10 is deployed at Google
> and elsewhere.  In fact, we see a steady improvement in our metrics,
> even for the tail end of the users, which we attribute to generally
> better connectivity.
> 
> As you noted, the only real solution to controlling jitter is to put
> real time and throughput maximizing traffic into separate queues.
> All other solutions have the property that they force implementers to
> make tradeoffs between peak queuing delay and link utilization, and as
> such are just workarounds that don't actually solve the root problem.
> The real time community has finally come to understand this reality,
> as reflected in the RMCAT charter.
> 
> These workarounds can be characterized as protecting RT traffic by
> deliberately making TCP less aggressive than desired to quickly fill
> the network.   Continuing to use these workarounds widens the gap
> between actual application performance and raw network capacity.  This
> fact is not lost on application developers and users who often observe
> only slight application performance improvements after deploying
> expensive faster networks, unless they take things under their own
> control by opening multiple connections.  As we all know, this
> approach undermines TCP's ability to control congestion.
> 
> Trying to make TCP compensate for the lack of segregated queueing (a
> network problem) prevents correct solutions to problems caused by TCP
> itself, namely it being too timid for most of todays networks.   Given
> the wide discussion of bufferbloat and the need for traffic
> segregation to support important RT applications, it is fairly likely
> that the network problems will come to be solved and the solutions
> widely deployed in the next few years.  A side benefit of these
> changes to better support RT will be to further limit any possible
> impact of IW10 on other Internet traffic.

Thanks for providing some more investigation material. Even from a TCP
perspective I think it is important as the experiment continues that one
include measurement data on how the one-way delay is affected as also
TCP flows carries "real-time" data.

To be clear, your answer has resulted in my having the position that not
going forward with IW10 is probably worse for the Internet than to not
do it.

There is clearly work to be done dealing with buffer-bloat but also the
reactions in the growing heterogeneous behavior of Internet paths. This
is an encouragement to people doing active work on this to continue.


> 
> In regards to your point 3, about client domains that experience
> persistent problems with IW10.   We propose to add a sentence at the
> end of section 12 (Usage and Deployment Recommendation): "Resolution
> of these experiments and tighter specifications of the suggestions
> here might be grounds for a future standards track document on the
> same topic."

Ok, so you don't yet have even an experimental algorithm that you are
confident in auto performing this process yet. I think this is a bit
worrying, but consider the relative few that appears having such issues
according to your investigations I am willing to take the chance.

> 
> In regards to your point 4, clarify incentives in section 3 by
> replacing end of the 2nd paragraph: "A larger initial window will
> incentivize applications to use fewer concurrent TCP connections."
> With: "If a larger initial window causes harm to any other flows then
> local application tuning will reveal that fewer concurrent connections
> yields better performance for some users.   Any content provider
> deploying IW10 in conjunction with content distributed across multiple
> domains is explicitly encouraged to perform measurement experiments to
> detect such problems, and to consider reducing the number of
> concurrent connections used to retrieve their content."

As this was really a guess for the future which was difficult to act on
I think the above is as well as I can see you do anything about my issues.

>From my perspective I think this can be published as an experimental
with the proposed updates.

Cheers

Magnus

> 
> Other planned change to the draft as requested by IESG feedback:
> 
> Drop "Updates RFC 3390 and 5681" from the metadata.
> 
> This change answers the DISCUSSes posted by Brian Haberman and Ralph Droms.
> 
> I believe that together these chanes should address all of the IESG
> DISCUSS items.
> 
> Thanks,
> --MM--
> The best way to predict the future is to create it.  - Alan Kay
> 
> Privacy matters!  We know from recent events that people are using our
> services to speak in defiance of unjust governments.   We treat
> privacy and security as matters of life and death, because for some
> users, they are.
> 
> 
> On Thu, Dec 6, 2012 at 2:01 AM, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
>> Hi,
>>
>> I have reviewed draft-ietf-tcpm-initcwnd-06 and have some questions and
>> comments.
>>
>> 1) First of all the experiments done appear to cover the impact on other
>> applications, like measuring the RTT variations when using IW10 compared
>> to IW3. If one is interested in the impact this proposal have on
>> real-time traffic flows over a shared bottle-neck the variations in
>> queue time at the bottleneck combined with that flows seen loss rates
>> are the most important factors. As a sudden delay spike of sufficient
>> magnitude will most likely result in a real-time media packet being
>> late, i.e. late loss rather than being lost in the network there might
>> be significant impact on such traffic from these IW10 packet bursts.
>> Have I missed any material discussing this aspect?
>>
>> All the latency figures in the parts I was looking at was discussing
>> cases when the object transfer takes longer time. But it appear obvious
>> that even with a 100 ms increased one-way transfer time for a packet is
>> the end of the initial window the total transfer goes faster compared to
>> the delay caused by growing the window.
>>
>> 2) If I assume that most users are behind buffer-bloated links the
>> introduction of IW10 on wide scale will additionally disrupt interactive
>> applications and cause increased delay and possible late loss depending
>> on application. Especially in combination with domain sharding. For
>> example a Swedish newspaper's website front page results in that more
>> than 40 TCP connections are opened in a current browser. If these all
>> was using IW10, the amount of packets being sent initially will grow
>> roughly from 40*3 = 120 to 40*10 = 400. There are some distribution over
>> time but still this likely results in a larger delay spike.
>>
>> I don't quite know how I should consider this case. One stand point is
>> that the interactive application is anyway buggered and IW10 effects are
>> not making it significantly worse. The only remedy is queue separation
>> so that what ever happens with the web-downloads doesn't affect the
>> interactive traffic. Another is that it will make the existing situation
>> worse and we should try to avoid making it worse.
>>
>> I think I am more in the first camp, but still the second one is
>> worrying to me. But I dare to guess that the performance gains might be
>> worth the issues, but without real progress on mitigation of the buffer
>> bloat issues for interactive real-time traffic this will add
>> significantly to the issues real-time has to face.
>>
>>
>> 3) The documents talks in quite loose terms about what can be done to
>> avoid to continue cause issues for destinations which has issues with
>> IW10. However I think it is a bit unspecific here. I can see that a
>> content deliverer can have lists for destination address blocks that
>> they see issues with which configures the sending server side with a
>> lower IW value. It also talks about the clients can configure to keep
>> the window low initially to prevent an IW10 sender to clobber ones link
>> if that is known. My question here is if the recommendation for auto
>> detection and configuration can be made more explicit. Fortunately the
>> issues with misconfiguration in this cases is not that serious. But
>> otherwise there is commonly need to be quite careful with such auto
>> configs that affects the behavior.
>>
>> 4) I am also worried that the document is a bit to positive in regards
>> to that IW10 will reduce the domain sharding practice. I think the only
>> thing that can do is likely a new HTTP transport strata that shows that
>> significantly improved performance for multiple objects from the same
>> domain over fewer transport flows. Maybe SPDY + IW10 can provide such
>> incentive, but I don't think IW10 alone will do much.
>>
>> Cheers
>>
>> Magnus
>>
>> On 2012-11-26 22:29, The IESG wrote:
>>>
>>> The IESG has received a request from the TCP Maintenance and Minor
>>> Extensions WG (tcpm) to consider the following document:
>>> - 'Increasing TCP's Initial Window'
>>>   <draft-ietf-tcpm-initcwnd-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-12-10. Exceptionally, comments may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>    This document proposes an experiment to increase the permitted TCP
>>>    initial window (IW) from between 2 and 4 segments, as specified in
>>>    RFC 3390, to 10 segments, with a fallback to the existing
>>>    recommendation when performance issues are detected. It discusses the
>>>    motivation behind the increase, the advantages and disadvantages of
>>>    the higher initial window, and presents results from several large
>>>    scale experiments showing that the higher initial window improves the
>>>    overall performance of many web services without resulting in a
>>>    congestion collapse. The document closes with a discussion of usage
>>>    and deployment for further experimental purpose recommended by the
>>>    IETF TCP Maintenance and Minor Extensions (TCPM) working group.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-tcpm-initcwnd/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>>
>>
>>
>> --
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Multimedia Technologies, Ericsson Research EAB/TVM
>> ----------------------------------------------------------------------
>> Ericsson AB                | Phone  +46 10 7148287
>> Färögatan 6                | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM
----------------------------------------------------------------------
Ericsson AB                | Phone  +46 10 7148287
Färögatan 6                | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From yi.jiazi@gmail.com  Mon Feb 11 10:47:43 2013
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E1121F87BB; Mon, 11 Feb 2013 10:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftPn+mF6sc5Z; Mon, 11 Feb 2013 10:47:42 -0800 (PST)
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by ietfa.amsl.com (Postfix) with ESMTP id B7CB021F87B9; Mon, 11 Feb 2013 10:47:41 -0800 (PST)
Received: by mail-wi0-f180.google.com with SMTP id hi8so3499835wib.13 for <multiple recipients>; Mon, 11 Feb 2013 10:47:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to :x-mailer; bh=LoKYms5qDmvFztiT55JAXcUYvWxu5AtpBJsOpdASfH8=; b=H0CSFsa9ZQjrKYonMjBPnb+oWGBiSsX9btaoUEDhGrnoK9df17cenhJHv/19C9TGpg Pd70ailDTlmnjrDATqfVXL0hG3R+CJvMzzPrfvZ+pTJnrOhM+XmbpxsarIMPdoJVOh5r Y10FJdhnMU1yyF/einTyalsTZ8Sc8tiR+ysgrOGB2SMBWmF6oxDXt9KJTBPhNujB8fM6 oY/oQ7IHMmhfYkY7160/O9XV8yHPatSghuUklCCJURjgYxYTW7fvH2JExGnB5z0p1QLY TSo25jVqUYogZkIduvpEh8K9XAT6uDo8tiHlgjYWJlAEbcsalWSTQvkxfiarqPopJvZ/ oaWg==
X-Received: by 10.194.161.135 with SMTP id xs7mr26003218wjb.41.1360608460810;  Mon, 11 Feb 2013 10:47:40 -0800 (PST)
Received: from jy-mac-pro.home (vbo91-1-89-87-201-6.dsl.sta.abo.bbox.fr. [89.87.201.6]) by mx.google.com with ESMTPS id bf2sm23751366wib.6.2013.02.11.10.47.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 10:47:40 -0800 (PST)
Sender: Jiazi YI <yi.jiazi@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Jiazi Yi <ietf@jiaziyi.com>
In-Reply-To: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com>
Date: Mon, 11 Feb 2013 19:47:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, ietf@ietf.org, Ulrich Herberg <ulrich@herberg.name>, "manet@ietf.org List" <manet@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, 11 Feb 2013 18:47:43 -0000

Dear all,=20

I had a through review of dff-07 with detailed comments. In the new =
revision, my questions and concerns have been properly addressed -- =
thanks to all the authors.=20

The mechanism is well documented, and I have tested the protocol in the =
scenarios described in the applicability statement, which brings =
interesting performance improvement.=20

Therefore, I would like to encourage the publication of it.=20

Just one more comment:

	o In section 8 Protocol Parameters, it would be better to have =
some limitations or recommendations for those parameters. For =
P_HOLD_TIME, I think it's OK by saying "at least be MAX_HOP_LIMIT times  =
the expected time to send a Packet to a router on the same link.". It =
would be event better to give such limitations to MAX_HOP_LIMIT. A =
regular value related to NET_DIAMETER won't work, because DFF can have =
significant higher hop count and result in packet drop. Maybe we can =
have something like "it MUST NOT be higher than the number of routers in =
the DFF routing domain. If the number of routers is greater than 255, it =
is set to 255 by default."=20

best

Jiazi


On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

> draft-cardenas-dff is under consideration for publication as an =
AD-sponsored individual submission Experimental RFC.  I agreed to =
sponsor it for publication because it doesn't really fit in any existing =
working groups and the requested publication status is Experimental.  As =
part of the review process, the document is in a 2-week IETF last call.  =
The last call announcement is included below.  To ensure the quality of =
the document, it would be helpful to get reviews from manet WG =
participants (posted to the ietf@ietf.org discussion list).
>=20
> Thanks.
>=20
> - Ralph
>=20
>=20
> =3D=3D=3D=3D=3D
>=20
>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
> <draft-cardenas-dff-09.txt> as Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>  This document specifies the "Depth-First Forwarding" (DFF) protocol
>  for IPv6 networks, a data forwarding mechanism that can increase
>  reliability of data delivery in networks with dynamic topology and/or
>  lossy links.  The protocol operates entirely on the forwarding plane,
>  but may interact with the routing plane.  DFF forwards data packets
>  using a mechanism similar to a "depth-first search" for the
>  destination of a packet.  The routing plane may be informed of
>  failures to deliver a packet or loops.  This document specifies the
>  DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>  addition also for LoWPAN "mesh-under" networks (as specified in
>  RFC4944).
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>  http://datatracker.ietf.org/ipr/1645/
>  http://datatracker.ietf.org/ipr/1646/
>=20
>=20
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet


From dhc@dcrocker.net  Mon Feb 11 11:01:16 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55FE621F8886 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C828l78+ArZO for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:01:15 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AB03921F884B for <ietf@ietf.org>; Mon, 11 Feb 2013 11:01:15 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r1BJ1EkI021569 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 11 Feb 2013 11:01:15 -0800
Message-ID: <51193FFA.6050008@dcrocker.net>
Date: Mon, 11 Feb 2013 11:01:14 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Doing something wrong
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> <201302100346.r1A3k4Ue1561926@shell01.TheWorld.com> <CAKHUCzzhc2O7kO8W1bW0mqb4Noiq+qxEeo_ujmztpLsy+RBriQ@mail.gmail.com> <6.2.5.6.2.20130210133122.0a0a1c00@resistor.net>
In-Reply-To: <6.2.5.6.2.20130210133122.0a0a1c00@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 11 Feb 2013 11:01:15 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 19:01:16 -0000

>> And on this note, doing something wrong and being corrected is always
>> a better choice than not doing something.
>
> Agreed.


Well...

That claimed benefit is probably true, from a global perspective, but 
often not true from a local (personal) perspective.

Most of us do local optimization, seeking to avoid criticism. Let's not 
be distracted by the example of the few, cantankerous ones of us who 
appear to be impervious to attack.

What changes this counter-productive pressure to keep quiet is making 
the tone of things be supportive and constructive rather than frankly 
hostile.

Does anyone seriously think the typical IETF exchange displays this 
more-positive tone?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From scott@kitterman.com  Mon Feb 11 11:34:21 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62B4E21F8845 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5EMmUFXGj8n for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:34:20 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id F40EB21F8836 for <ietf@ietf.org>; Mon, 11 Feb 2013 11:34:19 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id A557620E40F9; Mon, 11 Feb 2013 14:34:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1360611258; bh=Cnd97sBWxfCbn+Si2hyuQ7PGHnvPD5npC7ZQTVYb0c4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lb5nvT2bz2818w0kqg4ErAgnxIuhPyMkcvZAqqHisBTKhIWpgQZicpCbIF/Rv86ZL DQzpP3vJGm90d58GazkpEBU8Y7X5GgBhF3cqd7oGpN45qGAq+RVv1iPthon4WvddE5 iVnxqdv1OKM9H6rqCwT/sWfQb04m0CJf+brx6WLg=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 5AD4120E40CD;  Mon, 11 Feb 2013 14:34:09 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org, dcrocker@bbiw.net
Subject: Re: Doing something wrong
Date: Mon, 11 Feb 2013 14:34:09 -0500
Message-ID: <1508448.Y9Vk07qtoo@scott-latitude-e6320>
User-Agent: KMail/4.9.4 (Linux/3.5.0-23-generic; KDE/4.9.4; i686; ; )
In-Reply-To: <51193FFA.6050008@dcrocker.net>
References: <CADnDZ883hHwFw2-aPhzx-KaGCzyEuOhjNf1=58DtiBP8rw0Z5g@mail.gmail.com> <6.2.5.6.2.20130210133122.0a0a1c00@resistor.net> <51193FFA.6050008@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 19:34:21 -0000

On Monday, February 11, 2013 11:01:14 AM Dave Crocker wrote:
> >> And on this note, doing something wrong and being corrected is always
> >> a better choice than not doing something.
> > 
> > Agreed.
> 
> Well...
> 
> That claimed benefit is probably true, from a global perspective, but
> often not true from a local (personal) perspective.
> 
> Most of us do local optimization, seeking to avoid criticism. Let's not
> be distracted by the example of the few, cantankerous ones of us who
> appear to be impervious to attack.
> 
> What changes this counter-productive pressure to keep quiet is making
> the tone of things be supportive and constructive rather than frankly
> hostile.
> 
> Does anyone seriously think the typical IETF exchange displays this
> more-positive tone?

I guess it all depends on what you're used to.  IETF discussions seem 
reasonably temperate to me.

Scott K

From ulrich@herberg.name  Mon Feb 11 11:49:35 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D57A21F87C3 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:49:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.706
X-Spam-Level: 
X-Spam-Status: No, score=-2.706 tagged_above=-999 required=5 tests=[AWL=0.271,  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 3Ae++oAP1u1N for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 11:49:34 -0800 (PST)
Received: from mail-ve0-f169.google.com (mail-ve0-f169.google.com [209.85.128.169]) by ietfa.amsl.com (Postfix) with ESMTP id 8F64321F879B for <ietf@ietf.org>; Mon, 11 Feb 2013 11:49:33 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id 15so5608553vea.28 for <ietf@ietf.org>; Mon, 11 Feb 2013 11:49:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=9qb1/w5Lrd1yXjhL0N4CRzCZ2ywyo6gSwLGppUHUc5w=; b=Z+Fc03JKBIH2FvLDPL1NHfjW6MrHTwWiXA0i6MuB4sJ8JmUYQy5lgJPjudkfpU/Exq NgVlguSvN03/0C0sEM9y/UnQxvPIYXSvnU60Bn/QC0QeAiPzZwynZMn2gDz2iZ9iOzHM H0OyZnlYQtLiFl/KmfqY30QSCXwZ895m/yhWo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=9qb1/w5Lrd1yXjhL0N4CRzCZ2ywyo6gSwLGppUHUc5w=; b=lsm3IXaqBMU2/FvScmMEoTYKgCavuo7tBAP5AElaXmFpDs16wLskB/yfci72x4VEZd 8ps4A/NbDv28sMbxUErnNyhN9+n1L6GB3b0WfOqdFl0VbZ6nU1AXMYhN2w0BKkdbBdn1 9Bvpq7W0CU66BJZlS0fqvL1KktqR3GjcXZ/7Ib8TWLr000en6U7Nd1VNFr4fWNj7gnAn r2puqU2zkSDYSX+bYIOER9GrdedGa61AYEehwgERnberljeskE2mbUkuPGXFOfwrf8oM Cp4DzZn15Vx9rzOOiZCo+6xaz65meUcm9xe7i7Nz8BwFznrZT2rAdGJsjQUreR7M825s a47w==
MIME-Version: 1.0
X-Received: by 10.52.32.230 with SMTP id m6mr17751738vdi.83.1360612172730; Mon, 11 Feb 2013 11:49:32 -0800 (PST)
Received: by 10.220.146.199 with HTTP; Mon, 11 Feb 2013 11:49:32 -0800 (PST)
In-Reply-To: <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com>
Date: Mon, 11 Feb 2013 11:49:32 -0800
Message-ID: <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com>
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Ulrich Herberg <ulrich@herberg.name>
To: Jiazi Yi <ietf@jiaziyi.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnMutXuZ15LQSxL+YmYyXvTFbl48imtog2sfi94QfPysdGDoQ1ZF6xAajZo8r/VKo22VHzi
Cc: "manet@ietf.org List" <manet@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, 11 Feb 2013 19:49:35 -0000

Jiazi,

thank you very much for your review. I am glad that the latest
revision addresses your previous concerns.

As to your suggestion, I agree that having some constraints is useful.
To your suggestion considering the number of routers in the DFF
domain, I think this would be difficult to use normative language, as
the number of routers may not be known (e.g. when not using a
proactive routing protocol). DFF does not mandate to have this
information at hand.
Another example of setting the value would be to depend on the
expected path length (e.g. based on information from the routing
protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
say, 50% longer than the distance in hops indicated by a routing
protocol. I think that it would be very interesting to find out
appropriate values as experiments for the protocol (given that the
document is Experimental).

How about adding the following text to MAX_HOP_LIMIT:

----- added text ------
Finding optimal values for MAX_HOP_LIMIT is part of experiments that
can be performed with the protocol proposed in this document.
For example, one possible experiment would be to set MAX_HOP_LIMIT to
different factors of the expected path length to the destination in
number of hops if provided by a routing protocol.
---------------------



Best regards
Ulrich


On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>
> Dear all,
>
> I had a through review of dff-07 with detailed comments. In the new revis=
ion, my questions and concerns have been properly addressed -- thanks to al=
l the authors.
>
> The mechanism is well documented, and I have tested the protocol in the s=
cenarios described in the applicability statement, which brings interesting=
 performance improvement.
>
> Therefore, I would like to encourage the publication of it.
>
> Just one more comment:
>
>         o In section 8 Protocol Parameters, it would be better to have so=
me limitations or recommendations for those parameters. For P_HOLD_TIME, I =
think it's OK by saying "at least be MAX_HOP_LIMIT times  the expected time=
 to send a Packet to a router on the same link.". It would be event better =
to give such limitations to MAX_HOP_LIMIT. A regular value related to NET_D=
IAMETER won't work, because DFF can have significant higher hop count and r=
esult in packet drop. Maybe we can have something like "it MUST NOT be high=
er than the number of routers in the DFF routing domain. If the number of r=
outers is greater than 255, it is set to 255 by default."
>
> best
>
> Jiazi
>
>
> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>
> > draft-cardenas-dff is under consideration for publication as an AD-spon=
sored individual submission Experimental RFC.  I agreed to sponsor it for p=
ublication because it doesn't really fit in any existing working groups and=
 the requested publication status is Experimental.  As part of the review p=
rocess, the document is in a 2-week IETF last call.  The last call announce=
ment is included below.  To ensure the quality of the document, it would be=
 helpful to get reviews from manet WG participants (posted to the ietf@ietf=
.org discussion list).
> >
> > Thanks.
> >
> > - Ralph
> >
> >
> > =3D=3D=3D=3D=3D
> >
> >
> > The IESG has received a request from an individual submitter to conside=
r
> > the following document:
> > - 'Depth-First Forwarding in Unreliable Networks (DFF)'
> > <draft-cardenas-dff-09.txt> as Experimental RFC
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may =
be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >  This document specifies the "Depth-First Forwarding" (DFF) protocol
> >  for IPv6 networks, a data forwarding mechanism that can increase
> >  reliability of data delivery in networks with dynamic topology and/or
> >  lossy links.  The protocol operates entirely on the forwarding plane,
> >  but may interact with the routing plane.  DFF forwards data packets
> >  using a mechanism similar to a "depth-first search" for the
> >  destination of a packet.  The routing plane may be informed of
> >  failures to deliver a packet or loops.  This document specifies the
> >  DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
> >  addition also for LoWPAN "mesh-under" networks (as specified in
> >  RFC4944).
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-cardenas-dff/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
> >
> >
> > The following IPR Declarations may be related to this I-D:
> >
> >  http://datatracker.ietf.org/ipr/1645/
> >  http://datatracker.ietf.org/ipr/1646/
> >
> >
> > _______________________________________________
> > manet mailing list
> > manet@ietf.org
> > https://www.ietf.org/mailman/listinfo/manet
>

From mrex@sap.com  Mon Feb 11 12:24:28 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A3BB21F883E for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.271
X-Spam-Level: 
X-Spam-Status: No, score=-10.271 tagged_above=-999 required=5 tests=[AWL=-0.022, 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 8SIdkZSCfT5J for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:24:27 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA4C21F8820 for <ietf@ietf.org>; Mon, 11 Feb 2013 12:24:19 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id r1BKO3s6026871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 11 Feb 2013 21:24:03 +0100 (MET)
Subject: Re: I-D affects another or work in ietf groups
In-Reply-To: <CAKHUCzzhc2O7kO8W1bW0mqb4Noiq+qxEeo_ujmztpLsy+RBriQ@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
Date: Mon, 11 Feb 2013 21:24:03 +0100 (CET)
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: <20130211202403.68A271A54A@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 20:24:28 -0000

Dave Cridland wrote:
>
> On 10 Feb 2013 03:46, "Dale R. Worley" <worley@ariadne.com> wrote:
> >
> > In any case, if you are doing something incorrect in your review,
> > presumably people will call your attention to that fact, and explain
> > how you should change what you are doing and why you should change it.
> 
> And on this note, doing something wrong and being corrected is always a
> better choice than not doing something.

If this is about disagreement about someone elses proposal and speaking up,
then that should be OK most of the time (but not always).

But otherwise, if you do something and rely entirely on others to
watch you, to notice when you're wrong and to tell you before it
becomes costly to fix or is too late to change, then you might be
acting irresponsibly.

-Martin

From sm@resistor.net  Mon Feb 11 12:31:56 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EAC121F8A99 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id No88ohnpmYqx for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:31:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A8FF21F892F for <ietf@ietf.org>; Mon, 11 Feb 2013 12:31:54 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1BKVbNl022297; Mon, 11 Feb 2013 12:31:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360614703; bh=eGgHSSQdtGlXv6GGoq5seWWyJMX0IutJW1+r1S3ICfg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XsPtn33TVPq0dZ9aBNoTsg4ysvbu7TAmte+JqSG9FkwghqdWpG2zzkDiY0ShbdglS AoP8cOtdA/XQh0IHAjW5pCseZRyAqd6TB1DZrEVUlt0+T9pdfTeYgvXXuR0tYtUBkM W9FHo8NZ9kM5+SHawg4INI9bbvw1dayqrcWjxcRY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360614703; i=@resistor.net; bh=eGgHSSQdtGlXv6GGoq5seWWyJMX0IutJW1+r1S3ICfg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=px3LnO9jwZa1H7772B4FPV63SlUdXSZCbsiGztk8VxbOXNsYxHWgloylx6koHFgwo ULLH7G/yJT1r1AhdiBuhR69y6iq5SO5Dg0yWWOix+jtuBAnGxdWpnlfRRoouBFrmEN oZbSYxONxilv04HhpIKAbajmTMjkiiMjiQhIqkk8=
Message-Id: <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 11 Feb 2013 12:28:04 -0800
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: The RFC Acknowledgement
In-Reply-To: <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.g mail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "Sandra L. Cespedes" <slcesped@bbcr.uwaterloo.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: Mon, 11 Feb 2013 20:31:56 -0000

Hi Abdussalam,

Eric Burger provided some information about acknowledgements in a 
message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg77076.html  Fred 
Baker shared his perspective in a message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg71104.html

At 23:47 10-02-2013, Abdussalam Baryun wrote:
>Then from your opinion to be fare, I RECOMMEND that the RFC-section
>SHOULD be changed to *Authors' Acknowledgements*. Please note that the
>RFC is owned by the IETF so the section of ACK should not be only
>thanks of the authors or editors or Chairs, otherwise SHOULD be
>mentioned in title. IETF considers all inputs related to I-D as a
>contribution, please read the NOTE WELL. So do we understand that IETF
>is impolite with some of its contributors/workers?

I don't see anything in RFCs to point to the fact that "the RFC is 
owned by the IETF".  The Note Well is about keeping the lawyers 
happy.  I don't see what it has to do with impolite.  If your name 
has been missed in the Acknowledgements Section you could send a 
message to the author, with a copy to the document shepherd, about that.

>It is not about bonuses, it is about truth I-D's influences and the
>way the IETF process and work progresses. Do you think an I-D
>progresses only if experts comment and contribute? don't think so,
>best ideas come from discussions of different level of experiences
>including zero,  :-)

This is what I saw in a draft: "The authors would like to thank 
Christian Jacquenet, Tim Winter, Pieter De Mil, David Meyer and 
Abdussalam Baryun for their valuable feed-back".  I note that there 
is only one person listed as an author.  If I suggest removing the 
"s" from author, should I be mentioned in the Acknowledgements Section?

There was a Last Call for draft-ietf-forces-lfb-lib-10.  There can be 
a DISCUSS on that draft because of an insignificant detail [1].  I 
don't really know whether it's worth an "acknowledgement".

Thomas Heide Clausen commented [2] about draft-cardenas-dff-09 
[4].  I don't know the person (zero reputation).  You also posted a 
review [3].  The first review is clearer.

Regards,
-sm

1. My guess is that the reviewer will catch it.
2. http://www.ietf.org/mail-archive/web/ietf/current/msg77078.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg77089.html
4. I glanced at the draft.  Section 2.2 is about 
terminology.  Section 14.1.1 also mentions terminology.  There are 
different definitions for "Address". 


From yi.jiazi@gmail.com  Mon Feb 11 12:37:19 2013
Return-Path: <yi.jiazi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD2C21F8923; Mon, 11 Feb 2013 12:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tg5+X+t1C+Or; Mon, 11 Feb 2013 12:37:18 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id 63D4821F891D; Mon, 11 Feb 2013 12:37:17 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id ez12so3616053wid.0 for <multiple recipients>; Mon, 11 Feb 2013 12:37:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer; bh=yWVGGPdYccTcmhTfGAhgvTtcxcfYl8vdk0RtqpKeAU0=; b=bJ7FeX/EgsE1mWIqdd43lsa9crXeBCD3mmkBU4Lp+WmVBeyIeoMbVQXjSlbIz/V9pN ScAqkgpuPrVrvFkBgIiSlrR3AOPj3tPM0dBcGC7/EtLp3ijmhYVAUmm6oSBf4bHKySdW jX48KQnscrUMnVngocwubBaKU/TT74k86qwgEDDQ6na5DxYjZP7yiamHCsaZskGiqoEH rs8H8kOLjmunFWWZiNjVFjglrC5ww61O9UG7CTmSAWU8vYNRgvkU4PR01V8tCGQFsnq1 HSyKB8ApPp0V4Wv8NsLGKd8ZvvXDOciqp1VaLTWsADmpQgb7wZtvq31IMiTelPRFBvgd U/7w==
X-Received: by 10.194.109.102 with SMTP id hr6mr26409640wjb.24.1360615036505;  Mon, 11 Feb 2013 12:37:16 -0800 (PST)
Received: from jy-mac-pro.home (vbo91-1-89-87-201-6.dsl.sta.abo.bbox.fr. [89.87.201.6]) by mx.google.com with ESMTPS id s8sm32942518wif.9.2013.02.11.12.37.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 12:37:15 -0800 (PST)
Sender: Jiazi YI <yi.jiazi@gmail.com>
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Jiazi Yi <ietf@jiaziyi.com>
In-Reply-To: <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com>
Date: Mon, 11 Feb 2013 21:37:13 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <53B9FC50-10C2-4D73-B281-562999E6347C@jiaziyi.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com> <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
X-Mailer: Apple Mail (2.1499)
Cc: "manet@ietf.org List" <manet@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, 11 Feb 2013 20:37:19 -0000

Hi,=20

I can imagine that it would be hard to set this parameter. According to =
my simulation results, even with the same network scenario, the hop =
count would be very different depending on if a routing protocol is =
used, or which protocol is used.=20

I think it's a good idea to indicate the experimental point, to =
encourage people to try it out, and give feedback.=20

best

Jiazi

On Feb 11, 2013, at 8:49 PM, Ulrich Herberg <ulrich@herberg.name> wrote:

> Jiazi,
>=20
> thank you very much for your review. I am glad that the latest
> revision addresses your previous concerns.
>=20
> As to your suggestion, I agree that having some constraints is useful.
> To your suggestion considering the number of routers in the DFF
> domain, I think this would be difficult to use normative language, as
> the number of routers may not be known (e.g. when not using a
> proactive routing protocol). DFF does not mandate to have this
> information at hand.
> Another example of setting the value would be to depend on the
> expected path length (e.g. based on information from the routing
> protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
> say, 50% longer than the distance in hops indicated by a routing
> protocol. I think that it would be very interesting to find out
> appropriate values as experiments for the protocol (given that the
> document is Experimental).
>=20
> How about adding the following text to MAX_HOP_LIMIT:
>=20
> ----- added text ------
> Finding optimal values for MAX_HOP_LIMIT is part of experiments that
> can be performed with the protocol proposed in this document.
> For example, one possible experiment would be to set MAX_HOP_LIMIT to
> different factors of the expected path length to the destination in
> number of hops if provided by a routing protocol.
> ---------------------
>=20
>=20
>=20
> Best regards
> Ulrich
>=20
>=20
> On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>>=20
>> Dear all,
>>=20
>> I had a through review of dff-07 with detailed comments. In the new =
revision, my questions and concerns have been properly addressed -- =
thanks to all the authors.
>>=20
>> The mechanism is well documented, and I have tested the protocol in =
the scenarios described in the applicability statement, which brings =
interesting performance improvement.
>>=20
>> Therefore, I would like to encourage the publication of it.
>>=20
>> Just one more comment:
>>=20
>>        o In section 8 Protocol Parameters, it would be better to have =
some limitations or recommendations for those parameters. For =
P_HOLD_TIME, I think it's OK by saying "at least be MAX_HOP_LIMIT times  =
the expected time to send a Packet to a router on the same link.". It =
would be event better to give such limitations to MAX_HOP_LIMIT. A =
regular value related to NET_DIAMETER won't work, because DFF can have =
significant higher hop count and result in packet drop. Maybe we can =
have something like "it MUST NOT be higher than the number of routers in =
the DFF routing domain. If the number of routers is greater than 255, it =
is set to 255 by default."
>>=20
>> best
>>=20
>> Jiazi
>>=20
>>=20
>> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:
>>=20
>>> draft-cardenas-dff is under consideration for publication as an =
AD-sponsored individual submission Experimental RFC.  I agreed to =
sponsor it for publication because it doesn't really fit in any existing =
working groups and the requested publication status is Experimental.  As =
part of the review process, the document is in a 2-week IETF last call.  =
The last call announcement is included below.  To ensure the quality of =
the document, it would be helpful to get reviews from manet WG =
participants (posted to the ietf@ietf.org discussion list).
>>>=20
>>> Thanks.
>>>=20
>>> - Ralph
>>>=20
>>>=20
>>> =3D=3D=3D=3D=3D
>>>=20
>>>=20
>>> The IESG has received a request from an individual submitter to =
consider
>>> the following document:
>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>> <draft-cardenas-dff-09.txt> as Experimental RFC
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>> final comments on this action. Please send substantive comments to =
the
>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments =
may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>> This document specifies the "Depth-First Forwarding" (DFF) protocol
>>> for IPv6 networks, a data forwarding mechanism that can increase
>>> reliability of data delivery in networks with dynamic topology =
and/or
>>> lossy links.  The protocol operates entirely on the forwarding =
plane,
>>> but may interact with the routing plane.  DFF forwards data packets
>>> using a mechanism similar to a "depth-first search" for the
>>> destination of a packet.  The routing plane may be informed of
>>> failures to deliver a packet or loops.  This document specifies the
>>> DFF mechanism both for IPv6 networks (as specified in RFC2460) and =
in
>>> addition also for LoWPAN "mesh-under" networks (as specified in
>>> RFC4944).
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>>=20
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>>=20
>>>=20
>>> The following IPR Declarations may be related to this I-D:
>>>=20
>>> http://datatracker.ietf.org/ipr/1645/
>>> http://datatracker.ietf.org/ipr/1646/
>>>=20
>>>=20
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>=20


From sob@harvard.edu  Mon Feb 11 12:43:13 2013
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 A055D21F884C for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:43:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWrVnMjy9Acr for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 12:43:12 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 182B721F883C for <ietf@ietf.org>; Mon, 11 Feb 2013 12:43:12 -0800 (PST)
Received: from exchange.university.harvard.edu (entwedge0000004.university.harvard.edu [10.35.202.51]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id AB246E945F for <ietf@ietf.org>; Mon, 11 Feb 2013 15:43:11 -0500 (EST)
Received: from ENTWHUBT0000004.university.harvard.edu (10.32.208.50) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 11 Feb 2013 15:43:03 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.172]) by ENTWHUBT0000004.university.harvard.edu ([10.32.208.50]) with mapi id 14.01.0355.002; Mon, 11 Feb 2013 15:43:11 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: IETF-Discussion list <ietf@ietf.org>
Subject: Re: The RFC Acknowledgement
Thread-Topic: The RFC Acknowledgement
Thread-Index: AQHOCJhneA7hEg56IUSzd3iH32hZJQ==
Date: Mon, 11 Feb 2013 20:43:10 +0000
Message-ID: <07BA7974-E715-4BE0-BD10-8884D92B6C6C@harvard.edu>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
In-Reply-To: <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B9DC34517C2BC740B86F8D9B8F156BA6@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 20:43:13 -0000

I have not followed all of this thread but, in case someone had not already=
 mentioned it, acknowledging major contributors
is required, but not lessor contributors (that is left up to the authors)

see RFC 3978 section 3.4. a

Scott

On Feb 11, 2013, at 3:28 PM, SM <sm@resistor.net> wrote:

> Hi Abdussalam,
>=20
> Eric Burger provided some information about acknowledgements in a message=
 at http://www.ietf.org/mail-archive/web/ietf/current/msg77076.html  Fred B=
aker shared his perspective in a message at http://www.ietf.org/mail-archiv=
e/web/ietf/current/msg71104.html
>=20
> At 23:47 10-02-2013, Abdussalam Baryun wrote:
>> Then from your opinion to be fare, I RECOMMEND that the RFC-section
>> SHOULD be changed to *Authors' Acknowledgements*. Please note that the
>> RFC is owned by the IETF so the section of ACK should not be only
>> thanks of the authors or editors or Chairs, otherwise SHOULD be
>> mentioned in title. IETF considers all inputs related to I-D as a
>> contribution, please read the NOTE WELL. So do we understand that IETF
>> is impolite with some of its contributors/workers?
>=20
> I don't see anything in RFCs to point to the fact that "the RFC is owned =
by the IETF".  The Note Well is about keeping the lawyers happy.  I don't s=
ee what it has to do with impolite.  If your name has been missed in the Ac=
knowledgements Section you could send a message to the author, with a copy =
to the document shepherd, about that.
>=20
>> It is not about bonuses, it is about truth I-D's influences and the
>> way the IETF process and work progresses. Do you think an I-D
>> progresses only if experts comment and contribute? don't think so,
>> best ideas come from discussions of different level of experiences
>> including zero,  :-)
>=20
> This is what I saw in a draft: "The authors would like to thank Christian=
 Jacquenet, Tim Winter, Pieter De Mil, David Meyer and Abdussalam Baryun fo=
r their valuable feed-back".  I note that there is only one person listed a=
s an author.  If I suggest removing the "s" from author, should I be mentio=
ned in the Acknowledgements Section?
>=20
> There was a Last Call for draft-ietf-forces-lfb-lib-10.  There can be a D=
ISCUSS on that draft because of an insignificant detail [1].  I don't reall=
y know whether it's worth an "acknowledgement".
>=20
> Thomas Heide Clausen commented [2] about draft-cardenas-dff-09 [4].  I do=
n't know the person (zero reputation).  You also posted a review [3].  The =
first review is clearer.
>=20
> Regards,
> -sm
>=20
> 1. My guess is that the reviewer will catch it.
> 2. http://www.ietf.org/mail-archive/web/ietf/current/msg77078.html
> 3. http://www.ietf.org/mail-archive/web/ietf/current/msg77089.html
> 4. I glanced at the draft.  Section 2.2 is about terminology.  Section 14=
.1.1 also mentions terminology.  There are different definitions for "Addre=
ss".=20


From aretana@cisco.com  Mon Feb 11 13:15:30 2013
Return-Path: <aretana@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 9932F21F8AB7; Mon, 11 Feb 2013 13:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 1iDyPgWm39te; Mon, 11 Feb 2013 13:15:29 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id A6E1821F890D; Mon, 11 Feb 2013 13:15:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3284; q=dns/txt; s=iport; t=1360617329; x=1361826929; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=a1Py4EaY96o5jDaOhxGfxf5qljf8W6c68Lh+5kgri/A=; b=EUfOfspUVTCiDuuxU9y7dE+16MWVqu357V3SyPhz9C799xq4/q3H8tv6 52vpQlDP9uX+/ZcmjcENJBC9eJpxq73VSI6DpRwcxTUq13bO3pLOjW/l+ EhtKG2zh/KaO8zAcTsTFHgIfwgkmqyvCQ5HO77SRqKa6cR+rbk7KTkCdE I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMNdGVGtJXG//2dsb2JhbAA6CsEkFnOCIQEEOj8SAQgUDhRCJQIEAQ0FCIgKDMAdjUeDZWEDkmqEV482gwaCJA
X-IronPort-AV: E=Sophos;i="4.84,644,1355097600"; d="scan'208";a="172902479"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-9.cisco.com with ESMTP; 11 Feb 2013 21:15:29 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1BLFTAX017510 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Feb 2013 21:15:29 GMT
Received: from xmb-aln-x15.cisco.com ([169.254.9.213]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.02.0328.009; Mon, 11 Feb 2013 15:15:28 -0600
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Ben Campbell <ben@nostrum.com>, Acee Lindem <acee.lindem@ericsson.com>, "Abhay Roy (akr)" <akr@cisco.com>
Subject: Re: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Topic: Gen-ART LC Review of draft-ietf-ospf-ospfv3-iid-registry-update-00
Thread-Index: AQHN9DdZ9OjrkRsEWE2bqOnRv2sH7Zh1YiiA
Date: Mon, 11 Feb 2013 21:15:28 +0000
Message-ID: <BBD66FD99311804F80324E8139B3C94ED42270@xmb-aln-x15.cisco.com>
In-Reply-To: <CD0EC318-1015-41ED-8E0B-045D6EB258F9@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.221.163]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F109AA3999EA91469817701ACBF6E83E@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org" <draft-ietf-ospf-ospfv3-iid-registry-update.all@tools.ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>, "ospf-chairs@tools.ietf.org" <ospf-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, 11 Feb 2013 21:15:30 -0000

On 1/16/13 5:17 PM, "Ben Campbell" <ben@nostrum.com> wrote:

Ben:

Hi!

Sorry for the delay, my filters put this in a different place..  I'm
explicitly adding the OSPF chairs.  Comments below.


>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
>
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document:  draft-ietf-ospf-ospfv3-iid-registry-update-00
>Reviewer: Ben Campbell
>Review Date: 2013-01-16
>IETF LC End Date: 2013-01-24
>
>Summary: This draft is not ready for publication as a proposed standard.
>There is a significant IANA registration issue described in the review
>body.
>
>Major issues:
>
>This draft carves out a significant part of a registry with an assignment
>policy of "standards action" for "private use". It offers very little
>motivation for the change. In my opinion, this sort of change should come
>with a clear justification.
>
>Specifically, the draft modifies the OSPFv3 Address Family Instance ID
>registry to carve out half of the unassigned space for "private use". The
>justification for this is a single sentence saying that some networks
>need to use IIDs to identify specific applications. I think that needs
>significant elaboration in order to motivate the change in a way that the
>reader can evaluate.
>
>My understanding from the OFPS list is that this is in support of
>draft-ietf-ospf-ipv4-embedded-ipv6-routing, which is an informational
>draft. I have to wonder why the draft under review was not simply the
>IANA considerations for that draft.
>
>I suggest one of two paths forward:
>
>1) If this change is in support of that draft in particular, then this
>draft should say that, and include a _normative_ reference. I recognize
>the normative downref would complicate things--but I think that
>complication is reasonable under the circumstances.
>
>2) If this change is to support a general need that goes beyond
>draft-ietf-ospf-ipv4-embedded-ipv6-routing, then this draft should
>describe that need in enough detail for people to think about it, perhaps
>with an informative reference to
>draft-ietf-ospf-ipv4-embedded-ipv6-routing as an _example_.

In short (from the shepherd write-up): "The new range is for applications
that do not justify a standards track OSPFv3 Instance ID allocation. An
example would be "Routing for IPv4-embedded IPv6 Packets"".

During pre-publication review, the WG chairs asked us to not include
explicit references to draft-ietf-ospf-ipv4-embedded-ipv6-routing as that
is just an example and not the only potential user/driver.  I don't have a
problem adding an example, but I want to get agreement/comments/guidance
from the chairs before adding the text.  Acee/Abhay??


>
>
>Minor issues:
>
>-- section 3:
>
>I don't think it's appropriate to use normative language for IANA
>requests. Especially not "MUST". (I think the strongest thing we can do
>here is a polite request :-)  )   I suggest recasting that to descriptive
>language, and removing section 2 and the RFC 2119 reference.

Yes, we already removed that in the -01 version.

Thanks!!

Alvaro.


From ulrich@herberg.name  Mon Feb 11 13:25:10 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A018721F8893 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.733
X-Spam-Level: 
X-Spam-Status: No, score=-2.733 tagged_above=-999 required=5 tests=[AWL=0.244,  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 3L-BRRrWLl1M for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:25:10 -0800 (PST)
Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by ietfa.amsl.com (Postfix) with ESMTP id DACD521F8831 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:25:09 -0800 (PST)
Received: by mail-ve0-f180.google.com with SMTP id jx10so5448203veb.39 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:25:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Sp1uJnjS2Qnz7VIX4Pyx1u2uB2C8Mv3mj62necnZ3aE=; b=rcXUB/UNkF695rpxuLtTgomA51RzvFMLRYJuxQu3edGZKpqnf9Kyh34SW58K53jQRW OnQsCDHLowCe6NC0jQi1l2hykizTtiELQ+6MlZbmPMgYWRWSgXjOyqOZ56FOlOMovj47 eIjWN/tt1wKAx5BTt92g0wQL++H5mwLApRsUE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=Sp1uJnjS2Qnz7VIX4Pyx1u2uB2C8Mv3mj62necnZ3aE=; b=cj4s5IZcalF6tK+71IZysjx3tada03TpJR2S1Emo9ksF6jST7KFbWiKEMgkRYU9d/q zESB6eywBJY4TM7hWRE+25gVzv2OICtgnAFQdxdtOqRzucDUDbq1rzNRzPfKn14mSY3j C4vXnmJ4SV5wIkSvFZkQXDC0S4q9+bP6vw1vII+rZqqgY9/x/18WH8AHdACyTqEX3mKo wQEOwYZtr/PNh1TnoUh/nDWAtZSCIqoBMtfrHaqWRyRbqQmbNNiYhsmiK3//U3swb65a 8ZMUMQMIaHP4kJ9MOJaDRMzv6W+b26Ky2OGZ/XvJxUIJ+aZqkPMcLmOAHkEBEuH9QZme 3zRg==
MIME-Version: 1.0
X-Received: by 10.220.149.81 with SMTP id s17mr21166547vcv.31.1360617909334; Mon, 11 Feb 2013 13:25:09 -0800 (PST)
Received: by 10.220.146.199 with HTTP; Mon, 11 Feb 2013 13:25:09 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
Date: Mon, 11 Feb 2013 13:25:09 -0800
Message-ID: <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Ulrich Herberg <ulrich@herberg.name>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlz6M3eBXXQn3HLd1b09ypmXNlwZNLHy81TBg7yew/3O2ChMoAIrcOj4MIdGqFjRiMM3uB9
Cc: "Sandra L. Cespedes" <slcesped@bbcr.uwaterloo.ca>, ietf@ietf.org, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 21:25:10 -0000

SM,

(it is generally appreciated in the IETF to use real first and last name).

Generally, I think the topic has been well summarized by Fred and
others, and I don't see how continuing it would generate new value.
See below:

On Mon, Feb 11, 2013 at 12:28 PM, SM <sm@resistor.net> wrote:
> [...]
> Thomas Heide Clausen commented [2] about draft-cardenas-dff-09 [4].  I don't know the person (zero reputation).  You also posted a review [3].  The first review is clearer.
> [...]
> 2. http://www.ietf.org/mail-archive/web/ietf/current/msg77078.html
> 3. http://www.ietf.org/mail-archive/web/ietf/current/msg77089.html
> 4. I glanced at the draft.  Section 2.2 is about terminology.  Section 14.1.1 also mentions terminology.  There are different definitions for "Address".

I am not sure what this is about because it does not seem related to
this discussion. But since I am the editor of the mentioned document,
I still wonder what you mean but "the person [has] zero reputation".
There is a related topic on this mailing list about the mentioned
draft, so I suggest sending your comments as reply to that thread.

Best
Ulrich

From ulrich@herberg.name  Mon Feb 11 13:26:09 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E265321F8A94 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:26:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.773
X-Spam-Level: 
X-Spam-Status: No, score=-2.773 tagged_above=-999 required=5 tests=[AWL=0.204,  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 ZBTpKrSpV+sQ for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:26:09 -0800 (PST)
Received: from mail-vb0-f47.google.com (mail-vb0-f47.google.com [209.85.212.47]) by ietfa.amsl.com (Postfix) with ESMTP id E298521F8A89 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:26:08 -0800 (PST)
Received: by mail-vb0-f47.google.com with SMTP id e21so4050330vbm.6 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:26:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=aUnfGnFh4JmTz0CjZ2BRR5UqLbtdEjQShCkxEzBmskQ=; b=z+b91mHM5i2y6L2qg8JEgJxdJne/aKva6tOagAg6ZhauMpPOR5u3tL7mTW4bFzYg/y 7MbXEQQ7df5gL7FAdpZ0k/7JkIDWlrPFSAVuUpcd5pTswVTu5nHF92ALC1EGoHC5n85h 0iT0x19iFDlCrpY3LlulQjETu7CaS7svimKoA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding :x-gm-message-state; bh=aUnfGnFh4JmTz0CjZ2BRR5UqLbtdEjQShCkxEzBmskQ=; b=pqj9P89PD2UKn+iMZPYHPQZZA6W2FzUjS3WKhQtOvlSLQ6LgYg549MWwt88Xzzgy1Q Ll7KuZ4RX2AeGK8SuyZBafb6sp9e5Aj472I8vqmdKX/O5WSywsqewiLZJnQjKrJq79g7 CaVToQgk7dJfCxDOwArcoVImcCv/rR7jnDEx2EoKq2xJ7LU/ZkDwQl297+I+fEkWQ/WL dL75mFvmQ9aFW+0UD+7XyxzjldHUWXVe+p7RzsbJBjnPMEIbcv+FdIHn1xswtNRA9Vpt PVFgeH+kKuPCU55YI4qawNoLPeKmoNWxEiAlul236+iM8b7qUGwaClejCozhjWCznmrq 4VMg==
MIME-Version: 1.0
X-Received: by 10.52.28.101 with SMTP id a5mr17886127vdh.92.1360617968313; Mon, 11 Feb 2013 13:26:08 -0800 (PST)
Received: by 10.220.146.199 with HTTP; Mon, 11 Feb 2013 13:26:08 -0800 (PST)
In-Reply-To: <53B9FC50-10C2-4D73-B281-562999E6347C@jiaziyi.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com> <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com> <53B9FC50-10C2-4D73-B281-562999E6347C@jiaziyi.com>
Date: Mon, 11 Feb 2013 13:26:08 -0800
Message-ID: <CAK=bVC_YVMDbuvWTvp9RZr_NBRg9rXm6aRW1oG0VwW42PmVKow@mail.gmail.com>
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Ulrich Herberg <ulrich@herberg.name>
To: Jiazi Yi <ietf@jiaziyi.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQlmLsbB7s+DagR3tvQZdu3jXW6BOnuRPAgf5bAH2+KMZat2D5KbXMUSMLm4D6t+l8/N0Ojc
Cc: "manet@ietf.org List" <manet@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, 11 Feb 2013 21:26:10 -0000

Hi Jiazi,

I agree with your observation. I will add the sentence.

Best
Ulrich

On Mon, Feb 11, 2013 at 12:37 PM, Jiazi Yi <ietf@jiaziyi.com> wrote:
> Hi,
>
> I can imagine that it would be hard to set this parameter. According to m=
y simulation results, even with the same network scenario, the hop count wo=
uld be very different depending on if a routing protocol is used, or which =
protocol is used.
>
> I think it's a good idea to indicate the experimental point, to encourage=
 people to try it out, and give feedback.
>
> best
>
> Jiazi
>
> On Feb 11, 2013, at 8:49 PM, Ulrich Herberg <ulrich@herberg.name> wrote:
>
>> Jiazi,
>>
>> thank you very much for your review. I am glad that the latest
>> revision addresses your previous concerns.
>>
>> As to your suggestion, I agree that having some constraints is useful.
>> To your suggestion considering the number of routers in the DFF
>> domain, I think this would be difficult to use normative language, as
>> the number of routers may not be known (e.g. when not using a
>> proactive routing protocol). DFF does not mandate to have this
>> information at hand.
>> Another example of setting the value would be to depend on the
>> expected path length (e.g. based on information from the routing
>> protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
>> say, 50% longer than the distance in hops indicated by a routing
>> protocol. I think that it would be very interesting to find out
>> appropriate values as experiments for the protocol (given that the
>> document is Experimental).
>>
>> How about adding the following text to MAX_HOP_LIMIT:
>>
>> ----- added text ------
>> Finding optimal values for MAX_HOP_LIMIT is part of experiments that
>> can be performed with the protocol proposed in this document.
>> For example, one possible experiment would be to set MAX_HOP_LIMIT to
>> different factors of the expected path length to the destination in
>> number of hops if provided by a routing protocol.
>> ---------------------
>>
>>
>>
>> Best regards
>> Ulrich
>>
>>
>> On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>>>
>>> Dear all,
>>>
>>> I had a through review of dff-07 with detailed comments. In the new rev=
ision, my questions and concerns have been properly addressed -- thanks to =
all the authors.
>>>
>>> The mechanism is well documented, and I have tested the protocol in the=
 scenarios described in the applicability statement, which brings interesti=
ng performance improvement.
>>>
>>> Therefore, I would like to encourage the publication of it.
>>>
>>> Just one more comment:
>>>
>>>        o In section 8 Protocol Parameters, it would be better to have s=
ome limitations or recommendations for those parameters. For P_HOLD_TIME, I=
 think it's OK by saying "at least be MAX_HOP_LIMIT times  the expected tim=
e to send a Packet to a router on the same link.". It would be event better=
 to give such limitations to MAX_HOP_LIMIT. A regular value related to NET_=
DIAMETER won't work, because DFF can have significant higher hop count and =
result in packet drop. Maybe we can have something like "it MUST NOT be hig=
her than the number of routers in the DFF routing domain. If the number of =
routers is greater than 255, it is set to 255 by default."
>>>
>>> best
>>>
>>> Jiazi
>>>
>>>
>>> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>>
>>>> draft-cardenas-dff is under consideration for publication as an AD-spo=
nsored individual submission Experimental RFC.  I agreed to sponsor it for =
publication because it doesn't really fit in any existing working groups an=
d the requested publication status is Experimental.  As part of the review =
process, the document is in a 2-week IETF last call.  The last call announc=
ement is included below.  To ensure the quality of the document, it would b=
e helpful to get reviews from manet WG participants (posted to the ietf@iet=
f.org discussion list).
>>>>
>>>> Thanks.
>>>>
>>>> - Ralph
>>>>
>>>>
>>>> =3D=3D=3D=3D=3D
>>>>
>>>>
>>>> The IESG has received a request from an individual submitter to consid=
er
>>>> the following document:
>>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>>> <draft-cardenas-dff-09.txt> as Experimental RFC
>>>>
>>>> The IESG plans to make a decision in the next few weeks, and solicits
>>>> final comments on this action. Please send substantive comments to the
>>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may=
 be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>
>>>> Abstract
>>>>
>>>>
>>>> This document specifies the "Depth-First Forwarding" (DFF) protocol
>>>> for IPv6 networks, a data forwarding mechanism that can increase
>>>> reliability of data delivery in networks with dynamic topology and/or
>>>> lossy links.  The protocol operates entirely on the forwarding plane,
>>>> but may interact with the routing plane.  DFF forwards data packets
>>>> using a mechanism similar to a "depth-first search" for the
>>>> destination of a packet.  The routing plane may be informed of
>>>> failures to deliver a packet or loops.  This document specifies the
>>>> DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>>>> addition also for LoWPAN "mesh-under" networks (as specified in
>>>> RFC4944).
>>>>
>>>>
>>>>
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>>>
>>>>
>>>> The following IPR Declarations may be related to this I-D:
>>>>
>>>> http://datatracker.ietf.org/ipr/1645/
>>>> http://datatracker.ietf.org/ipr/1646/
>>>>
>>>>
>>>> _______________________________________________
>>>> manet mailing list
>>>> manet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/manet
>>>
>

From barryleiba.mailing.lists@gmail.com  Mon Feb 11 13:49:04 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 160CC21F8696 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.902
X-Spam-Level: 
X-Spam-Status: No, score=-102.902 tagged_above=-999 required=5 tests=[AWL=0.074, 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 8JoWxMBvxSvk for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 13:49:03 -0800 (PST)
Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) by ietfa.amsl.com (Postfix) with ESMTP id 60EFA21F8671 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:49:03 -0800 (PST)
Received: by mail-vb0-f52.google.com with SMTP id fa15so3958387vbb.25 for <ietf@ietf.org>; Mon, 11 Feb 2013 13:49:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=cZe1ewjBa2YJO+xqvlACu7O2U4ShDy+v0ZH/Pih+iWU=; b=RObk6PEIn3ukDK5wBT/4zhIkAm5z7pOmY7TdENulI47xYnV5EyMlj40oZKSvMCX9OL XQ9tYL7ekzU6w3rv5zxQYR6uV3oxzqPE3EIPu7ottlYmLPeTJ5XOMY2Ek0pjjk9Pqm9J ztGj3mHEtUIizZy1Uw5H5U5Nz70EoIAD0rcXRVF8M7JofnpovlsGD3i4cWBTBt8cFrqm XsSkJDjawUZhoc67aaZ6hGUw7BpOGr1RqjbTlK/GlpfPe0EeD90mp6tzwKl3u3agKVt1 TRt7O3VnMGKOn5v1NDUJgnioF+15W93N7u7NJ6o2N2MrboYJfuHQk78BsySYJYUas+96 nQ1A==
MIME-Version: 1.0
X-Received: by 10.220.157.18 with SMTP id z18mr21081459vcw.72.1360619342819; Mon, 11 Feb 2013 13:49:02 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 11 Feb 2013 13:49:02 -0800 (PST)
In-Reply-To: <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com>
Date: Tue, 12 Feb 2013 05:49:02 +0800
X-Google-Sender-Auth: 2pd7ON_iCiqxQ3RsI2OuSPmzmpc
Message-ID: <CAC4RtVCy3JCROqDTqW9wU-RDUp0CQ_4kPtGLNCO_Tzx7E34FEQ@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Barry Leiba <barryleiba@computer.org>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: multipart/alternative; boundary=f46d043890ab9a723204d579e04f
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 21:49:04 -0000

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

> SM,
> (it is generally appreciated in the IETF to use real first and last name).

Hi, Ulrich.
This is actually a very cultural issue.  I'll point out that in U.S.
culture it's common for people named William to go by "Bill", or for people
to regularly use nicknames such as "Bud" or "Woody".  Do we call those
"real" names?  For south Asians, Thais, and others with very long names,
it's culturally common to use abbreviations -- someone named
"Gopalakrishnan" might be "Gopal", and use of initials is common.

SM is well known here by his initials, and switching to "Subramanian
Moonesamy" won't benefit anyone.  He knows the IETF culture as well as his
own, and "SM" is perfectly fine, and is what we know him by.

Does that help?

Barry

--f46d043890ab9a723204d579e04f
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;=A0SM,<br>&gt; (it is generally appreciated in the IETF to use real =
first and last name).</span></font><div><font><span style=3D"line-height:no=
rmal;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)">Hi, Ulrich.</span></font></div><div><font><span=
 style=3D"line-height:normal;background-color:rgba(255,255,255,0)">This is =
actually a very cultural issue. =A0I&#39;ll point out that in U.S. culture =
it&#39;s common for people named William to go by &quot;Bill&quot;, or for =
people to regularly use nicknames such as &quot;Bud&quot; or &quot;Woody&qu=
ot;. =A0Do we call those &quot;real&quot; names? =A0For south Asians, Thais=
, and others with very long names, it&#39;s culturally common to use abbrev=
iations -- someone named &quot;Gopalakrishnan&quot; might be &quot;Gopal&qu=
ot;, and use of initials is common.</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:norma=
l;background-color:rgba(255,255,255,0)">SM is well known here by his initia=
ls, and switching to &quot;Subramanian Moonesamy&quot; won&#39;t benefit an=
yone. =A0He knows the IETF culture as well as his own, and &quot;SM&quot; i=
s perfectly fine, and is what we know him by.</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:norma=
l;background-color:rgba(255,255,255,0)">Does that help?</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:norma=
l;background-color:rgba(255,255,255,0)">Barry<span></span></span></font></d=
iv>

--f46d043890ab9a723204d579e04f--

From abdussalambaryun@gmail.com  Mon Feb 11 14:34:32 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A221921F86CD for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 14:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.53
X-Spam-Level: 
X-Spam-Status: No, score=-3.53 tagged_above=-999 required=5 tests=[AWL=0.069,  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 XuLmobGVF+qC for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 14:34:31 -0800 (PST)
Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by ietfa.amsl.com (Postfix) with ESMTP id 57D5221F882C for <ietf@ietf.org>; Mon, 11 Feb 2013 14:34:31 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id 8so5041308wgl.18 for <ietf@ietf.org>; Mon, 11 Feb 2013 14:34:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=V/+zTmXOGzibFhzvAyTYAEDIb7sRrhdNTm4U3kibx1s=; b=Kkd8HEE6qLX4l8WY2HLC3sKwtkuZRQtylNer17fNVsNnQ1tNx/IVDjQkxkjz9dKGZX u7QDE2sXLZXl5wzCk3FXJ32GRnsHToUrVrrHmFM0nH+zs37B2xsJCYB9q6LH8UqO4+Md 4aEbtIaRZTZsYbu19IhQ8BETewUHUTVWTgKe40G0WbyMRxn/2cb6sSrR2CiVPeYFILDX mHdwvJ6Grz8808n5x9F7nZwR2H6pU7DlTXKS7ukrRb1HBwDdcGDpkBxyJ4RlZm9vN9mu ctH8v/Nt7aE8/qpeMLRBBe4w6zcUACfSXyWWSJhXhPP7RPfgnqcMRQ4RwpqDhosG1t0M KlTw==
MIME-Version: 1.0
X-Received: by 10.194.75.196 with SMTP id e4mr26873210wjw.44.1360622070357; Mon, 11 Feb 2013 14:34:30 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 14:34:30 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net>
Date: Mon, 11 Feb 2013 23:34:30 +0100
Message-ID: <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 22:34:32 -0000

Hi SM,

thanks for your email, my reply inline;

On 2/11/13, SM <sm@resistor.net> wrote:
> Hi Abdussalam,
>
> Eric Burger provided some information about acknowledgements in a
> message at
> http://www.ietf.org/mail-archive/web/ietf/current/msg77076.html  Fred
> Baker shared his perspective in a message at
> http://www.ietf.org/mail-archive/web/ietf/current/msg71104.html

I agree with them and never disagreed, I just gave a point of view,

> At 23:47 10-02-2013, Abdussalam Baryun wrote:
>>Then from your opinion to be fare, I RECOMMEND that the RFC-section
>>SHOULD be changed to *Authors' Acknowledgements*. Please note that the
>>RFC is owned by the IETF so the section of ACK should not be only
>>thanks of the authors or editors or Chairs, otherwise SHOULD be
>>mentioned in title. IETF considers all inputs related to I-D as a
>>contribution, please read the NOTE WELL. So do we understand that IETF
>>is impolite with some of its contributors/workers?
>
> I don't see anything in RFCs to point to the fact that "the RFC is
> owned by the IETF".  The Note Well is about keeping the lawyers
> happy.  I don't see what it has to do with impolite.  If your name
> has been missed in the Acknowledgements Section you could send a
> message to the author, with a copy to the document shepherd, about that.

Do you mean that IETF is producing what it does not own, or IETF has
no right to edit/amend a document that it is publishing? I
misunderstand your point,

>
>>It is not about bonuses, it is about truth I-D's influences and the
>>way the IETF process and work progresses. Do you think an I-D
>>progresses only if experts comment and contribute? don't think so,
>>best ideas come from discussions of different level of experiences
>>including zero,  :-)
>
> This is what I saw in a draft: "The authors would like to thank
> Christian Jacquenet, Tim Winter, Pieter De Mil, David Meyer and
> Abdussalam Baryun for their valuable feed-back".  I note that there
> is only one person listed as an author.  If I suggest removing the
> "s" from author, should I be mentioned in the Acknowledgements Section?

No you should not be acknowledged only because any author in world
will answer that in same way, and the one who suggest a changes
already knows as the author when an Ack is recommended.

>
> There was a Last Call for draft-ietf-forces-lfb-lib-10.  There can be
> a DISCUSS on that draft because of an insignificant detail [1].  I
> don't really know whether it's worth an "acknowledgement".

Yes I think it may be worth, because we want to encourage reviews and
discussions, we want to increase participation (please note that there
is very low participation in IETF per draft if you compare with number
of authors of drafts). I am not sure why people try to avoid thanking
others for their significant TIME given. Your reply and others are
concerned more about the details of significant of change in I-D but I
am more concerned of both.

>
> Thomas Heide Clausen commented [2] about draft-cardenas-dff-09
> [4].  I don't know the person (zero reputation).  You also posted a
> review [3].  The first review is clearer.

These reviews can be out of the authors' acknowledgement because
usually it was a reply to IESG-request, the IESG should Ack the
reviewers if they are following polite practices. In addition, thoes
reviews were  last-call review/input but if there was an amendment
resulted I recommend it will be nice to document it in Ack. Usually
authors (of WG I-Ds or Individual I-Ds) start asking participants to
review and give comments because they want draft-reputation (drafts
reputation is needed to be discovered not participants reputations),
so if there was one replying to an author to reveiw what do you think
the right think to do? The answer is to say thanks :)

 The Requester SHOULD ACK the Replier when the Requester receives the
message/action requested (Even Machines do ACK each other, when they
request).

Thanks for your feedback
AB

>
> 1. My guess is that the reviewer will catch it.
> 2. http://www.ietf.org/mail-archive/web/ietf/current/msg77078.html
> 3. http://www.ietf.org/mail-archive/web/ietf/current/msg77089.html
> 4. I glanced at the draft.  Section 2.2 is about
> terminology.  Section 14.1.1 also mentions terminology.  There are
> different definitions for "Address".
>
>

From ulrich@herberg.name  Mon Feb 11 14:48:39 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 952CE21F8873 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 14:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.1
X-Spam-Level: 
X-Spam-Status: No, score=-3.1 tagged_above=-999 required=5 tests=[AWL=0.498, 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 qnXKT8HtSJfZ for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 14:48:38 -0800 (PST)
Received: from mail-ve0-f170.google.com (mail-ve0-f170.google.com [209.85.128.170]) by ietfa.amsl.com (Postfix) with ESMTP id AFF6921F8869 for <ietf@ietf.org>; Mon, 11 Feb 2013 14:48:38 -0800 (PST)
Received: by mail-ve0-f170.google.com with SMTP id 14so5623943vea.1 for <ietf@ietf.org>; Mon, 11 Feb 2013 14:48:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type; bh=m6aEM5y/LJJnq+1qynLT4lQFS1+nYiwoqy5t+pB71lU=; b=mumVuLmjOvSDjFKYG1a1qZfUAdYR3MYu/gpA4xlEK8ZxUjHiJ09IJFOaotwGHQneW0 gsHt90EJIh2OwHKVHAaYeZGRopU8/YJZ63yItFdJxN6odw9zKTZ/d0Cr6HxXi60eJ1Pf L9xChVB1h449MK0I3gUUxhJnb5La/GntYOP64=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:from:mime-version:in-reply-to:date:message-id :subject:to:cc:content-type:x-gm-message-state; bh=m6aEM5y/LJJnq+1qynLT4lQFS1+nYiwoqy5t+pB71lU=; b=hiyMAqzDIBWt/MhYkI89r8DNPInWV2Wf3qaYX94TbF8bTenkFRinVdYKYQy34OilY9 aOvKqV0QhUHkC3dJF9vYRldVh8JtI3TOQBuQG7pfjIOzviwCtB9+RIsyAS7aUX71ABPO 8KckgxYMQE0C7NLTSCKth0gF76pJt0ceJ+diYYkWy4MieVqT8d+egQX5CGB1Z3DhJLDz 3S1SLtbCIAl+B216Y2PiUN4P/AYy648dWTGPWG7z7j1B8U+L2ogsKByEMZ8Oh0ESxsOM L9kOY33ucs6bdo7EBFav4R2H0lCUnmgsXg8Nkwj34yCdHeM2Hjx87jFEDEYRMa/C90DA NFXg==
X-Received: by 10.52.88.237 with SMTP id bj13mr18326167vdb.75.1360622917624; Mon, 11 Feb 2013 14:48:37 -0800 (PST)
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com> <CAC4RtVCy3JCROqDTqW9wU-RDUp0CQ_4kPtGLNCO_Tzx7E34FEQ@mail.gmail.com>
From: Ulrich Herberg <ulrich@herberg.name>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAC4RtVCy3JCROqDTqW9wU-RDUp0CQ_4kPtGLNCO_Tzx7E34FEQ@mail.gmail.com>
Date: Mon, 11 Feb 2013 14:48:37 -0800
Message-ID: <-7188438076852587393@unknownmsgid>
Subject: Re: The RFC Acknowledgement
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=bcaec50160d7ada2e004d57ab508
X-Gm-Message-State: ALoCoQny43vch2E6l0+xn2GSqmos1Oem++TKIuz64pMDiXsUFcjMtZyg3jo+/XDeBmueExrXUzPB
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 22:48:39 -0000

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

Alright,

it's not important for this discussion anyway; just ignore my comment.

Ulrich

Sent from my iPhone

On Feb 11, 2013, at 1:49 PM, Barry Leiba <barryleiba@computer.org> wrote:

> SM,
> (it is generally appreciated in the IETF to use real first and last name).

Hi, Ulrich.
This is actually a very cultural issue.  I'll point out that in U.S.
culture it's common for people named William to go by "Bill", or for people
to regularly use nicknames such as "Bud" or "Woody".  Do we call those
"real" names?  For south Asians, Thais, and others with very long names,
it's culturally common to use abbreviations -- someone named
"Gopalakrishnan" might be "Gopal", and use of initials is common.

SM is well known here by his initials, and switching to "Subramanian
Moonesamy" won't benefit anyone.  He knows the IETF culture as well as his
own, and "SM" is perfectly fine, and is what we know him by.

Does that help?

Barry

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

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=
=3Dutf-8"></head><body dir=3D"auto"><div>Alright,</div><div><br></div><div>=
it&#39;s not important for this discussion anyway; just ignore my comment.<=
/div>
<div><br></div><div>Ulrich<br><br>Sent from my iPhone</div><div><br>On Feb =
11, 2013, at 1:49 PM, Barry Leiba &lt;<a href=3D"mailto:barryleiba@computer=
.org">barryleiba@computer.org</a>&gt; wrote:<br><br></div><blockquote type=
=3D"cite">
<div><font><span style=3D"line-height:normal;background-color:rgba(255,255,=
255,0)">&gt;=A0SM,<br>&gt; (it is generally appreciated in the IETF to use =
real first and last name).</span></font><div><font><span style=3D"line-heig=
ht: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)">Hi, Ulrich.</span></font></div><div><font><span=
 style=3D"line-height:normal;background-color:rgba(255,255,255,0)">This is =
actually a very cultural issue. =A0I&#39;ll point out that in U.S. culture =
it&#39;s common for people named William to go by &quot;Bill&quot;, or for =
people to regularly use nicknames such as &quot;Bud&quot; or &quot;Woody&qu=
ot;. =A0Do we call those &quot;real&quot; names? =A0For south Asians, Thais=
, and others with very long names, it&#39;s culturally common to use abbrev=
iations -- someone named &quot;Gopalakrishnan&quot; might be &quot;Gopal&qu=
ot;, and use of initials is common.</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:norma=
l;background-color:rgba(255,255,255,0)">SM is well known here by his initia=
ls, and switching to &quot;Subramanian Moonesamy&quot; won&#39;t benefit an=
yone. =A0He knows the IETF culture as well as his own, and &quot;SM&quot; i=
s perfectly fine, and is what we know him by.</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:norma=
l;background-color:rgba(255,255,255,0)">Does that help?</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:norma=
l;background-color:rgba(255,255,255,0)">Barry<span></span></span></font></d=
iv>

</div></blockquote></body></html>

--bcaec50160d7ada2e004d57ab508--

From joelja@bogus.com  Mon Feb 11 15:04:05 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E73DF21F8873 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:04:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.503
X-Spam-Level: 
X-Spam-Status: No, score=-102.503 tagged_above=-999 required=5 tests=[AWL=0.096, 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 DlLTds4aS6yK for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:04:05 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 754DA21F883E for <ietf@ietf.org>; Mon, 11 Feb 2013 15:04:05 -0800 (PST)
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 r1BN426k084166 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 11 Feb 2013 23:04:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <511978DD.8000804@bogus.com>
Date: Mon, 11 Feb 2013 15:03:57 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, SM <sm@resistor.net>
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com>
In-Reply-To: <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 11 Feb 2013 23:04:03 +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: Mon, 11 Feb 2013 23:04:06 -0000

On 2/11/13 2:34 PM, Abdussalam Baryun wrote:
> Hi SM,
>
> thanks for your email, my reply inline;
>
> On 2/11/13, SM <sm@resistor.net> wrote:
>> Hi Abdussalam,
>>
>> Eric Burger provided some information about acknowledgements in a
>> message at
>> http://www.ietf.org/mail-archive/web/ietf/current/msg77076.html  Fred
>> Baker shared his perspective in a message at
>> http://www.ietf.org/mail-archive/web/ietf/current/msg71104.html
> I agree with them and never disagreed, I just gave a point of view,
>
>> At 23:47 10-02-2013, Abdussalam Baryun wrote:
>>> Then from your opinion to be fare, I RECOMMEND that the RFC-section
>>> SHOULD be changed to *Authors' Acknowledgements*. Please note that the
>>> RFC is owned by the IETF so the section of ACK should not be only
>>> thanks of the authors or editors or Chairs, otherwise SHOULD be
>>> mentioned in title. IETF considers all inputs related to I-D as a
>>> contribution, please read the NOTE WELL. So do we understand that IETF
>>> is impolite with some of its contributors/workers?
>> I don't see anything in RFCs to point to the fact that "the RFC is
>> owned by the IETF".  The Note Well is about keeping the lawyers
>> happy.  I don't see what it has to do with impolite.  If your name
>> has been missed in the Acknowledgements Section you could send a
>> message to the author, with a copy to the document shepherd, about that.
> Do you mean that IETF is producing what it does not own, or IETF has
> no right to edit/amend a document that it is publishing? I
> misunderstand your point,
>
Once an RFC number is issued  and the document published, the content of 
that RFC never changes.

See RFC 2200 section 2





From abdussalambaryun@gmail.com  Mon Feb 11 15:32:19 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68C021F8A99 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.537
X-Spam-Level: 
X-Spam-Status: No, score=-3.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 oPXyVKWhe8w0 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 15:32:19 -0800 (PST)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id 457FA21F8A61 for <ietf@ietf.org>; Mon, 11 Feb 2013 15:32:18 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id ez12so3785106wid.11 for <ietf@ietf.org>; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dddpy+MM0SoHMILrW1VSi++71JNSw0/4b0caAFOcpY0=; b=PJu/N6HnBNZ7XJef3tObrCM1Wx1oAbhm4lnmu2xcEwsw+75eZvoSuby9B3hsbodxQQ iiuQayAWzedPz56YmkiVCfBRZMQgBswJFuVKcqKcqY0aPMWYJUBZHgxtEyZCXX6TuWij 9Wd6KEMC2AWrRPvoLAloA2vj/Sqt/1RmHlUq55jRLBMqbeDSislEyIY9M1qFo9ggZg3l 5lP0PVkXYEs99GyYlRTS38Pahb7jmyxR0VbFtp5ym+cO4qOHvZD4h12VOueBTYrC4H9i 9KfFlqvhG8wfEerhZeAE6lWP7Pzzhl/OYzB70rvFSHAuuCZBEFAUVpVtdOsvuGk44a4N vOpQ==
MIME-Version: 1.0
X-Received: by 10.180.83.10 with SMTP id m10mr19079678wiy.5.1360625537392; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 15:32:17 -0800 (PST)
In-Reply-To: <511978DD.8000804@bogus.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com> <511978DD.8000804@bogus.com>
Date: Tue, 12 Feb 2013 00:32:17 +0100
Message-ID: <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
Subject: Re: The RFC Acknowledgement
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 23:32:20 -0000

On 2/12/13, joel jaeggli <joelja@bogus.com> wrote:
>> Do you mean that IETF is producing what it does not own, or IETF has
>> no right to edit/amend a document that it is publishing? I
>> misunderstand your point,
>>
> Once an RFC number is issued  and the document published, the content of
> that RFC never changes.
>
> See RFC 2200 section 2
>
I agree, but still IETF can update or obsolete any document,

The question ment to be:
Do you mean that IETF is producing what it does not own, or IETF has
no right to edit/amend a document that will be published?

AB

From rbarnes@bbn.com  Mon Feb 11 15:46:39 2013
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 0A24721F8856; Mon, 11 Feb 2013 15:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pSHPuzEX6z31; Mon, 11 Feb 2013 15:46:38 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5204521F8812; Mon, 11 Feb 2013 15:46:38 -0800 (PST)
Received: from [128.89.254.29] (port=58806) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1U5352-000HGK-U2; Mon, 11 Feb 2013 18:46:36 -0500
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART review of draft-ietf-mpls-tp-ethernet-addressing-05
Date: Mon, 11 Feb 2013 18:45:48 -0500
Message-Id: <BC955C38-4B9F-43FE-B5E7-014239B18B20@bbn.com>
To: "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-tp-ethernet-addressing@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Feb 2013 23:46:39 -0000

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

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

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

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

Comment:

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

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

From joelja@bogus.com  Mon Feb 11 16:00:49 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EECB21F8972 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:00:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.508
X-Spam-Level: 
X-Spam-Status: No, score=-102.508 tagged_above=-999 required=5 tests=[AWL=0.091, 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 J3JK-mI6ndqy for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:00:49 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2257021F8848 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:00:49 -0800 (PST)
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 r1C00kad084801 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 12 Feb 2013 00:00:46 GMT (envelope-from joelja@bogus.com)
Message-ID: <51198629.7040203@bogus.com>
Date: Mon, 11 Feb 2013 16:00:41 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: The RFC Acknowledgement
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com> <511978DD.8000804@bogus.com> <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 12 Feb 2013 00:00:47 +0000 (UTC)
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 00:00:49 -0000

On 2/11/13 3:32 PM, Abdussalam Baryun wrote:
> On 2/12/13, joel jaeggli <joelja@bogus.com> wrote:
>>> Do you mean that IETF is producing what it does not own, or IETF has
>>> no right to edit/amend a document that it is publishing? I
>>> misunderstand your point,
>>>
>> Once an RFC number is issued  and the document published, the content of
>> that RFC never changes.
>>
>> See RFC 2200 section 2
>>
> I agree, but still IETF can update or obsolete any document,
A consensus driven working group process can be used by IETF 
participants to produce a new RFC which updates or obsoletes an existing 
document. The existing document does not change.

ftp://ftp.ietf.org/rfc/rfc822.txt looks the same as in 1982.
>
> The question ment to be:
> Do you mean that IETF is producing what it does not own, or IETF has
> no right to edit/amend a document that will be published?
Authors grant rights under the terms of the provisions in force at the 
time of publication. Not some unspecified set of rules in the future. So 
variously none, 1310, 1602, 2026, 3978, 4748 and the IETF Trust 
Licensing Policy.
> AB
>


From sm@resistor.net  Mon Feb 11 16:11:58 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A333A21F8A66 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:11:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.575
X-Spam-Level: 
X-Spam-Status: No, score=-102.575 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4MdPwtnxPraT for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:11:56 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8455D21F8A61 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:11:56 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1C0Bbm9028861; Mon, 11 Feb 2013 16:11:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360627903; bh=MWusB7/vcn7P5szqejwkpingB3axGHSbrybshau6Qzs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NPYNUIuhxKGVTpCkqJHejeu6qLZ+vx6U9pdh+RMnClprQ5MlWk4YfjO2l1Omyqucm RUmfJVU7E+vPkQzjK4Yxsz/YIkbhRnnTSRc8Q2CQYmVcWSlLwrFWTO6PtlIucLJKE5 sYkDSRICRsi2hyf/ZYQhXJwQRGKBpwRjcMht0sio=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360627903; i=@resistor.net; bh=MWusB7/vcn7P5szqejwkpingB3axGHSbrybshau6Qzs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZKvblpp/P65p+GK73VLPH0Ks81R9lvlADvlG34Lfm++vG7TNJ8svHSy+ibZE0G/JP jZDo+ZFig8xQ7W60tUBwsaoWTpuDCPT+Wdtg3UZkmoky/U9as05zLcnzd4FSsQnKZA Vi/tMjdMJcJibpdR1QZLSn+QhLOAu5DOTWBlqJ4I=
Message-Id: <6.2.5.6.2.20130211143859.0956a928@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 11 Feb 2013 15:36:12 -0800
To: Ulrich Herberg <ulrich@herberg.name>
From: SM <sm@resistor.net>
Subject: Re: The RFC Acknowledgement (off-topic)
In-Reply-To: <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.g mail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "Sandra L. Cespedes" <slcesped@bbcr.uwaterloo.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: Tue, 12 Feb 2013 00:11:58 -0000

Hi Ulrich,
At 13:25 11-02-2013, Ulrich Herberg wrote:
>(it is generally appreciated in the IETF to use real first and last name).

Agreed.

Your comment reminded me of the message at 
http://www.ietf.org/mail-archive/web/domainrep/current/msg00085.html

>Generally, I think the topic has been well summarized by Fred and
>others, and I don't see how continuing it would generate new value.
>See below:

Agreed.

>I am not sure what this is about because it does not seem related to
>this discussion. But since I am the editor of the mentioned document,

It was a gentle note to one of the authors (see Note 4).

I pointed to two reviews about a draft and mentioned that the first 
one was clearer to me.

>I still wonder what you mean but "the person [has] zero reputation".
>There is a related topic on this mailing list about the mentioned
>draft, so I suggest sending your comments as reply to that thread.

I agree that it is better to stick to the topic.  I'll answer in here 
as to avoid generating two messages.  I meant that I have never 
interacted with the person through email or in person.  There is less 
bias [1].  The content of the message matters; it does not matter who wrote it.

Regards,
-sm

1. www.cs.utexas.edu/users/mckinley/notes/snodgrass-tods-2007.pdf 


From abdussalambaryun@gmail.com  Mon Feb 11 16:28:14 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8B0C21F87D4 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.543
X-Spam-Level: 
X-Spam-Status: No, score=-3.543 tagged_above=-999 required=5 tests=[AWL=0.056,  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 G6lky5EW8eIy for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:28:14 -0800 (PST)
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com [209.85.212.176]) by ietfa.amsl.com (Postfix) with ESMTP id 8711B21F87D2 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:28:13 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id hm14so3816011wib.15 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:28:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ldA9KCgLKxGvz1PeRBymeUr2h1ABbu3PL754KY32CXU=; b=NaJMxrJtjXeaBe185k8Klt/m0GsQPBt4QuvBRWihFOiku0217rAVBtBTkanWsCRHUs VKRzwvM7goWV/zdsEYHo+gcWD+Vx/GGp2M1N8xBq3C63zudHtecB1dd1BELegPg2mkNf ZQdoMyEs92xTdgaBxiFt17SSu6j19VgoipAqUdnr15WKqrCkiPElZbdcCLfpvhe1V/qW tgJbPa5cAL1hgoIDCxNB2mHkG4p8S33P21vcOazZdQYs1F0sauY0LnWJGlh7KbdRuF58 C91vdAVrA9IsS3mflddcjzGDuO1TguWqagSdW0NIAuneOFfBCc/vYp1uIdPoRAKI8d7T NXMA==
MIME-Version: 1.0
X-Received: by 10.194.118.166 with SMTP id kn6mr27352906wjb.18.1360628892041;  Mon, 11 Feb 2013 16:28:12 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 16:28:11 -0800 (PST)
In-Reply-To: <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com> <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com>
Date: Tue, 12 Feb 2013 01:28:11 +0100
Message-ID: <CADnDZ8_Vu9=f-=JwXJEMb6__YC7ub__zaoyHjgOvau8pF3y1iQ@mail.gmail.com>
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 00:28:14 -0000

Hi Ulrich,

I agree with Jiazi, that you need to provide values of parameters for
the experiment I-D, or some default recommendations. I think it is
important but your text proposed does not follow the request of
parameters values,

AB

On 2/11/13, Ulrich Herberg <ulrich@herberg.name> wrote:
> Jiazi,
>
> thank you very much for your review. I am glad that the latest
> revision addresses your previous concerns.
>
> As to your suggestion, I agree that having some constraints is useful.
> To your suggestion considering the number of routers in the DFF
> domain, I think this would be difficult to use normative language, as
> the number of routers may not be known (e.g. when not using a
> proactive routing protocol). DFF does not mandate to have this
> information at hand.
> Another example of setting the value would be to depend on the
> expected path length (e.g. based on information from the routing
> protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
> say, 50% longer than the distance in hops indicated by a routing
> protocol. I think that it would be very interesting to find out
> appropriate values as experiments for the protocol (given that the
> document is Experimental).
>
> How about adding the following text to MAX_HOP_LIMIT:
>
> ----- added text ------
> Finding optimal values for MAX_HOP_LIMIT is part of experiments that
> can be performed with the protocol proposed in this document.
> For example, one possible experiment would be to set MAX_HOP_LIMIT to
> different factors of the expected path length to the destination in
> number of hops if provided by a routing protocol.
> ---------------------
>
>
>
> Best regards
> Ulrich
>
>
> On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>>
>> Dear all,
>>
>> I had a through review of dff-07 with detailed comments. In the new
>> revision, my questions and concerns have been properly addressed -- thanks
>> to all the authors.
>>
>> The mechanism is well documented, and I have tested the protocol in the
>> scenarios described in the applicability statement, which brings
>> interesting performance improvement.
>>
>> Therefore, I would like to encourage the publication of it.
>>
>> Just one more comment:
>>
>>         o In section 8 Protocol Parameters, it would be better to have
>> some limitations or recommendations for those parameters. For P_HOLD_TIME,
>> I think it's OK by saying "at least be MAX_HOP_LIMIT times  the expected
>> time to send a Packet to a router on the same link.". It would be event
>> better to give such limitations to MAX_HOP_LIMIT. A regular value related
>> to NET_DIAMETER won't work, because DFF can have significant higher hop
>> count and result in packet drop. Maybe we can have something like "it MUST
>> NOT be higher than the number of routers in the DFF routing domain. If the
>> number of routers is greater than 255, it is set to 255 by default."
>>
>> best
>>
>> Jiazi
>>
>>
>> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>
>> > draft-cardenas-dff is under consideration for publication as an
>> > AD-sponsored individual submission Experimental RFC.  I agreed to
>> > sponsor it for publication because it doesn't really fit in any existing
>> > working groups and the requested publication status is Experimental.  As
>> > part of the review process, the document is in a 2-week IETF last call.
>> > The last call announcement is included below.  To ensure the quality of
>> > the document, it would be helpful to get reviews from manet WG
>> > participants (posted to the ietf@ietf.org discussion list).
>> >
>> > Thanks.
>> >
>> > - Ralph
>> >
>> >
>> > =====
>> >
>> >
>> > The IESG has received a request from an individual submitter to
>> > consider
>> > the following document:
>> > - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>> > <draft-cardenas-dff-09.txt> as Experimental RFC
>> >
>> > The IESG plans to make a decision in the next few weeks, and solicits
>> > final comments on this action. Please send substantive comments to the
>> > ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may
>> > be
>> > sent to iesg@ietf.org instead. In either case, please retain the
>> > beginning of the Subject line to allow automated sorting.
>> >
>> > Abstract
>> >
>> >
>> >  This document specifies the "Depth-First Forwarding" (DFF) protocol
>> >  for IPv6 networks, a data forwarding mechanism that can increase
>> >  reliability of data delivery in networks with dynamic topology and/or
>> >  lossy links.  The protocol operates entirely on the forwarding plane,
>> >  but may interact with the routing plane.  DFF forwards data packets
>> >  using a mechanism similar to a "depth-first search" for the
>> >  destination of a packet.  The routing plane may be informed of
>> >  failures to deliver a packet or loops.  This document specifies the
>> >  DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>> >  addition also for LoWPAN "mesh-under" networks (as specified in
>> >  RFC4944).
>> >
>> >
>> >
>> >
>> > The file can be obtained via
>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/
>> >
>> > IESG discussion can be tracked via
>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>> >
>> >
>> > The following IPR Declarations may be related to this I-D:
>> >
>> >  http://datatracker.ietf.org/ipr/1645/
>> >  http://datatracker.ietf.org/ipr/1646/
>> >
>> >
>> > _______________________________________________
>> > manet mailing list
>> > manet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/manet
>>
> _______________________________________________
> manet mailing list
> manet@ietf.org
> https://www.ietf.org/mailman/listinfo/manet
>

From ulrich@herberg.name  Mon Feb 11 16:33:25 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FCA321F8820 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.825
X-Spam-Level: 
X-Spam-Status: No, score=-2.825 tagged_above=-999 required=5 tests=[AWL=0.152,  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 AJRPe2qE0cnI for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:33:24 -0800 (PST)
Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) by ietfa.amsl.com (Postfix) with ESMTP id 486D721F8816 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:33:24 -0800 (PST)
Received: by mail-ve0-f175.google.com with SMTP id cy12so5611131veb.20 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:33:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=JH2JL3LhC49lE7sVs1gkjmvwSicenVkmAJeZuwD3eDI=; b=ccUH/yK4oUNZy4/4dym6wWlMogd2rY7OUHyWkh+XVyWsaVAapy8J2bJ1yoSZs9jBoz EmOWSjx0lo0w9qRmDDHiL0H/J2GLI7NNHS/h7LR7jFUPCTUXUwir6CFaX+1PoZmrw7dX VeZ227ZL8vnWqEwvvW8epx6q520AkqprkaaqE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=JH2JL3LhC49lE7sVs1gkjmvwSicenVkmAJeZuwD3eDI=; b=FFa0LwO4CYFl3a80nOWTUj8KvV/ukAUUaOU8cmlAkqmaEYVXiC/47VD1QjmynEjs3U R1xo+aKfkamnmBz7pPxoksdGFp5QWod3LahpIPXOJrqitXRRs741cuO09UQQDSJB0/Qf R+y25KiGPCU2H+fRF9Lm1xsJP0BPKFvIJzVvvmmUkOfFAildP1Bh+O1C4QqSlBAnIU2M 5x9YjCpfPZ8oR+bG/e/MQDBVnbaoJknEoA4s1AjI7wFJH+9E0ZRDn8QUahXog7P04UMq CxGoSGkHKgOtS41PiEUbdvS53FIl5DsuEgCb332OTWvJUq054sK6Y2uYEWbxXKv/7/N/ p/Lw==
MIME-Version: 1.0
X-Received: by 10.52.28.101 with SMTP id a5mr18403924vdh.92.1360629203549; Mon, 11 Feb 2013 16:33:23 -0800 (PST)
Received: by 10.220.146.199 with HTTP; Mon, 11 Feb 2013 16:33:23 -0800 (PST)
In-Reply-To: <CADnDZ8_Vu9=f-=JwXJEMb6__YC7ub__zaoyHjgOvau8pF3y1iQ@mail.gmail.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com> <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com> <CADnDZ8_Vu9=f-=JwXJEMb6__YC7ub__zaoyHjgOvau8pF3y1iQ@mail.gmail.com>
Date: Mon, 11 Feb 2013 16:33:23 -0800
Message-ID: <CAK=bVC9pUt4UqqKyaHCKqyyvbwae2quym0brqbUewZaPVzrwbQ@mail.gmail.com>
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Ulrich Herberg <ulrich@herberg.name>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQm8i2NGdEsgYgracUeslOPLiZm+KMOVW+m2CdAvbduk/IstIKuLuHrqIK62dTN7DV2w7cXX
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 00:33:25 -0000

AB,

as said to Jiazi, the text already has some recommendations of
constraints for the parameters (and I will add the sentence I
suggested to Jiazi). I am unsure what additional text you would like
to see.

Best regards
Ulrich

On Mon, Feb 11, 2013 at 4:28 PM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> Hi Ulrich,
>
> I agree with Jiazi, that you need to provide values of parameters for
> the experiment I-D, or some default recommendations. I think it is
> important but your text proposed does not follow the request of
> parameters values,
>
> AB
>
> On 2/11/13, Ulrich Herberg <ulrich@herberg.name> wrote:
>> Jiazi,
>>
>> thank you very much for your review. I am glad that the latest
>> revision addresses your previous concerns.
>>
>> As to your suggestion, I agree that having some constraints is useful.
>> To your suggestion considering the number of routers in the DFF
>> domain, I think this would be difficult to use normative language, as
>> the number of routers may not be known (e.g. when not using a
>> proactive routing protocol). DFF does not mandate to have this
>> information at hand.
>> Another example of setting the value would be to depend on the
>> expected path length (e.g. based on information from the routing
>> protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
>> say, 50% longer than the distance in hops indicated by a routing
>> protocol. I think that it would be very interesting to find out
>> appropriate values as experiments for the protocol (given that the
>> document is Experimental).
>>
>> How about adding the following text to MAX_HOP_LIMIT:
>>
>> ----- added text ------
>> Finding optimal values for MAX_HOP_LIMIT is part of experiments that
>> can be performed with the protocol proposed in this document.
>> For example, one possible experiment would be to set MAX_HOP_LIMIT to
>> different factors of the expected path length to the destination in
>> number of hops if provided by a routing protocol.
>> ---------------------
>>
>>
>>
>> Best regards
>> Ulrich
>>
>>
>> On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>>>
>>> Dear all,
>>>
>>> I had a through review of dff-07 with detailed comments. In the new
>>> revision, my questions and concerns have been properly addressed -- thanks
>>> to all the authors.
>>>
>>> The mechanism is well documented, and I have tested the protocol in the
>>> scenarios described in the applicability statement, which brings
>>> interesting performance improvement.
>>>
>>> Therefore, I would like to encourage the publication of it.
>>>
>>> Just one more comment:
>>>
>>>         o In section 8 Protocol Parameters, it would be better to have
>>> some limitations or recommendations for those parameters. For P_HOLD_TIME,
>>> I think it's OK by saying "at least be MAX_HOP_LIMIT times  the expected
>>> time to send a Packet to a router on the same link.". It would be event
>>> better to give such limitations to MAX_HOP_LIMIT. A regular value related
>>> to NET_DIAMETER won't work, because DFF can have significant higher hop
>>> count and result in packet drop. Maybe we can have something like "it MUST
>>> NOT be higher than the number of routers in the DFF routing domain. If the
>>> number of routers is greater than 255, it is set to 255 by default."
>>>
>>> best
>>>
>>> Jiazi
>>>
>>>
>>> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>>
>>> > draft-cardenas-dff is under consideration for publication as an
>>> > AD-sponsored individual submission Experimental RFC.  I agreed to
>>> > sponsor it for publication because it doesn't really fit in any existing
>>> > working groups and the requested publication status is Experimental.  As
>>> > part of the review process, the document is in a 2-week IETF last call.
>>> > The last call announcement is included below.  To ensure the quality of
>>> > the document, it would be helpful to get reviews from manet WG
>>> > participants (posted to the ietf@ietf.org discussion list).
>>> >
>>> > Thanks.
>>> >
>>> > - Ralph
>>> >
>>> >
>>> > =====
>>> >
>>> >
>>> > The IESG has received a request from an individual submitter to
>>> > consider
>>> > the following document:
>>> > - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>> > <draft-cardenas-dff-09.txt> as Experimental RFC
>>> >
>>> > The IESG plans to make a decision in the next few weeks, and solicits
>>> > final comments on this action. Please send substantive comments to the
>>> > ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may
>>> > be
>>> > sent to iesg@ietf.org instead. In either case, please retain the
>>> > beginning of the Subject line to allow automated sorting.
>>> >
>>> > Abstract
>>> >
>>> >
>>> >  This document specifies the "Depth-First Forwarding" (DFF) protocol
>>> >  for IPv6 networks, a data forwarding mechanism that can increase
>>> >  reliability of data delivery in networks with dynamic topology and/or
>>> >  lossy links.  The protocol operates entirely on the forwarding plane,
>>> >  but may interact with the routing plane.  DFF forwards data packets
>>> >  using a mechanism similar to a "depth-first search" for the
>>> >  destination of a packet.  The routing plane may be informed of
>>> >  failures to deliver a packet or loops.  This document specifies the
>>> >  DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>>> >  addition also for LoWPAN "mesh-under" networks (as specified in
>>> >  RFC4944).
>>> >
>>> >
>>> >
>>> >
>>> > The file can be obtained via
>>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>> >
>>> > IESG discussion can be tracked via
>>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>> >
>>> >
>>> > The following IPR Declarations may be related to this I-D:
>>> >
>>> >  http://datatracker.ietf.org/ipr/1645/
>>> >  http://datatracker.ietf.org/ipr/1646/
>>> >
>>> >
>>> > _______________________________________________
>>> > manet mailing list
>>> > manet@ietf.org
>>> > https://www.ietf.org/mailman/listinfo/manet
>>>
>> _______________________________________________
>> manet mailing list
>> manet@ietf.org
>> https://www.ietf.org/mailman/listinfo/manet
>>

From abdussalambaryun@gmail.com  Mon Feb 11 16:57:21 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EC721F8780 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.549
X-Spam-Level: 
X-Spam-Status: No, score=-3.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmJgxFnitRPL for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 16:57:20 -0800 (PST)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0D821F86CD for <ietf@ietf.org>; Mon, 11 Feb 2013 16:57:20 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id hi18so3804989wib.9 for <ietf@ietf.org>; Mon, 11 Feb 2013 16:57:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=D8vCWetAwmnWFMKRsJvL7ghRktFT8QWaaaTiWLfJ3HY=; b=K+EYO1e6BC3teieDGEj+CoMIROs8TpqHKjz7Yvhu1YdfQzXZsK23nbauWiHH8nW+2I 32Glujb1N1GwAv2Af9cVWEZEm0IZZDxTNBf6RhhT7nckrXQcYshtiSFytvaVLCvjOBtv 7/j8eXncXHguqj3RsmMl6P+106PzLp/t49HKfn1ENbKQOvF6g0+2EEJ2O7Rpi09shBJa N2arPqXloZtc3wz2SEZMDl98I82424U768GAC9TevJc4vTMznEkB6D+tf0DO4kirLlKe bS8cxuIruMKRrIPXaPWph3CXn5vuehyl7bMkx2VTYEio1VrZk6xIXNGndyTOGjazmCwm 3HKw==
MIME-Version: 1.0
X-Received: by 10.194.109.102 with SMTP id hr6mr27355973wjb.24.1360630639494;  Mon, 11 Feb 2013 16:57:19 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 16:57:19 -0800 (PST)
Date: Tue, 12 Feb 2013 01:57:19 +0100
Message-ID: <CADnDZ88AxFVC5bXmcVaJAD2XmV3wkrG99Q+L0aOKm3W9nUPkRQ@mail.gmail.com>
Subject: Changing the value of RFCs not numbers (was Re: The RFC Acknowledgement)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 00:57:21 -0000

Many said to me before as you do RFC don't change, it is already known
in any org that documents don't change when published. Even author's
drafts in IETF don't change but are updated by new versions or new
names, this is progress of doc process in IETF. The RFCs can be
rewritten and obsolete the old RFC, so no more use of the old one, we
use the new one for progress.

 My understanding is that the RFC-ideas and RFC-effects in the
Internet may change. The RFC-document is just a reference, what is
important is its specification usefulness and the reputation to be
used (some RFCs are not used). Therefore, in my point of view the
value of any RFC may change in future, but the number of RFC and
publications never changes,

AB
++
On 2/12/13, joel jaeggli <joelja@bogus.com> wrote:

> On 2/11/13 3:32 PM, Abdussalam Baryun wrote:
>> On 2/12/13, joel jaeggli <joelja@bogus.com> wrote:
>>>> Do you mean that IETF is producing what it does not own, or IETF has
>>>> no right to edit/amend a document that it is publishing? I
>>>> misunderstand your point,
>>>>
>>> Once an RFC number is issued  and the document published, the content of
>>> that RFC never changes.
>>>
>>> See RFC 2200 section 2
>>>
>> I agree, but still IETF can update or obsolete any document,

> A consensus driven working group process can be used by IETF
> participants to produce a new RFC which updates or obsoletes an existing
> document. The existing document does not change.
>
> ftp://ftp.ietf.org/rfc/rfc822.txt looks the same as in 1982.

>>
>> The question ment to be:
>> Do you mean that IETF is producing what it does not own, or IETF has
>> no right to edit/amend a document that will be published?

> Authors grant rights under the terms of the provisions in force at the
> time of publication. Not some unspecified set of rules in the future. So
> variously none, 1310, 1602, 2026, 3978, 4748 and the IETF Trust
> Licensing Policy.

>> AB
>>
>
>

From moore@network-heretics.com  Mon Feb 11 17:17:18 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C871221F86D3 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 17:17:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[AWL=-0.707, BAYES_20=-0.74, 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 ayrd3Y8uFFPx for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 17:17:18 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id EE83A21F86CE for <ietf@ietf.org>; Mon, 11 Feb 2013 17:17:17 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0436920961 for <ietf@ietf.org>; Mon, 11 Feb 2013 20:17:12 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 11 Feb 2013 20:17:12 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=dCvUPIJUg6brV95FeCPVaF USclQ=; b=nOCfEPvxiuOfLp742Ja5yuq5MmevK16Zy1z6YsDrszwDNexjni/2td 7Li7Jxh4CMtUg13lQ3VVcVUpKbkHx9INj9Ql68UALwSIC2lmMWi85mKJuyGZ2uVt lD9TqFUUDbfV8R2jQg6KuHRdYOC2bLn5lnVllUSHB/1fRKXSTmej0=
X-Sasl-enc: i4D2nXMV7PggTggRMWgIg0uCGVeoA9bLb99XyNdussP8 1360631831
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6CA858E098E; Mon, 11 Feb 2013 20:17:11 -0500 (EST)
Message-ID: <51199813.8060208@network-heretics.com>
Date: Mon, 11 Feb 2013 20:17:07 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org>
In-Reply-To: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@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, 12 Feb 2013 01:17:18 -0000

On 02/05/2013 11:04 AM, IETF Chair wrote:
> 3.4. Slide Sharing
>
>     Slides are often sent by email in advance of the meeting.
>     
>     WebEx allows the slides and desktop applications to be viewed by the
>     remote participants.  These are controlled by the presenter.  The
>     presenter can be shifted from participant to participant as needed.
>

Can we *please* discourage the habit of treating IETF WG meetings as one 
series of PowerPoint presentations after another?   This makes the 
meetings much less productive.

The notion that there are supposed to be slides for each presentation, 
is IMO, a huge error.

Keith


From abdussalambaryun@gmail.com  Mon Feb 11 17:18:55 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5872921F8777 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 17:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eYord5Q9-wBv for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 17:18:54 -0800 (PST)
Received: from mail-we0-x22a.google.com (we-in-x022a.1e100.net [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ED0B321F875C for <ietf@ietf.org>; Mon, 11 Feb 2013 17:18:53 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id z53so5603280wey.1 for <ietf@ietf.org>; Mon, 11 Feb 2013 17:18:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Ay1tB7XVNM9XBrIkXxpjGw2Jn2XfA1AB+WW7Ftbp1uI=; b=YWZCmuEcQjdOKPf+3t+hO6rAPcv0SujXSXc6kn62DvfJq6hPOCcDDjfeqwS8llh/z+ HQg5/8GbKje38M8Bi/5mHwCJ9yr90A1jX4g8BIqDBHc5qLo6B8CW6fjN45VA5FAyL+tI zoMlbQad705EYJqQ0IOmEvl6gq/zsfQsCmR8blc17haxz19Y7CjKT85LeDanFMj1yccH Dt/UZtKN//Bmkyvr2IHjbq8BlpMIuVlhDW9RKffbHRv6PJY6tMvaTNNk3K2LymEDEuj8 +NY+2bBK1+6N/QJQ6Tu8miy33s0O5NqDeanXjTuXRD3eDYXv9WHHC9YyS3iScZUilfEG laWw==
MIME-Version: 1.0
X-Received: by 10.194.118.166 with SMTP id kn6mr27557563wjb.18.1360631927915;  Mon, 11 Feb 2013 17:18:47 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Mon, 11 Feb 2013 17:18:47 -0800 (PST)
In-Reply-To: <CAK=bVC9pUt4UqqKyaHCKqyyvbwae2quym0brqbUewZaPVzrwbQ@mail.gmail.com>
References: <A909A1B2-FAE3-448A-9159-F19266823B7A@gmail.com> <0794B0E9-7309-4246-92A2-CFEA023DBBCD@jiaziyi.com> <CAK=bVC8naOhgfBMLh6qMGQAoP=JUCBsO=aqnu1fDtG4rj7TCmg@mail.gmail.com> <CADnDZ8_Vu9=f-=JwXJEMb6__YC7ub__zaoyHjgOvau8pF3y1iQ@mail.gmail.com> <CAK=bVC9pUt4UqqKyaHCKqyyvbwae2quym0brqbUewZaPVzrwbQ@mail.gmail.com>
Date: Tue, 12 Feb 2013 02:18:47 +0100
Message-ID: <CADnDZ8-EPHTC8axSjwKyFDu1NuWZ9=6_aOL7M-N7B2UD8Z_u9w@mail.gmail.com>
Subject: Re: [manet] IETF last call and review of draft-cardenas-dff-09.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ulrich Herberg <ulrich@herberg.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 01:18:55 -0000

Similar way of parameters in RFC6606 which I think can be related,
however, I will answer your question better in my review messages
(still not finished). Just wanted to support the idea of a
participant,

AB

On 2/12/13, Ulrich Herberg <ulrich@herberg.name> wrote:
> AB,
>
> as said to Jiazi, the text already has some recommendations of
> constraints for the parameters (and I will add the sentence I
> suggested to Jiazi). I am unsure what additional text you would like
> to see.
>
> Best regards
> Ulrich
>
> On Mon, Feb 11, 2013 at 4:28 PM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>> Hi Ulrich,
>>
>> I agree with Jiazi, that you need to provide values of parameters for
>> the experiment I-D, or some default recommendations. I think it is
>> important but your text proposed does not follow the request of
>> parameters values,
>>
>> AB
>>
>> On 2/11/13, Ulrich Herberg <ulrich@herberg.name> wrote:
>>> Jiazi,
>>>
>>> thank you very much for your review. I am glad that the latest
>>> revision addresses your previous concerns.
>>>
>>> As to your suggestion, I agree that having some constraints is useful.
>>> To your suggestion considering the number of routers in the DFF
>>> domain, I think this would be difficult to use normative language, as
>>> the number of routers may not be known (e.g. when not using a
>>> proactive routing protocol). DFF does not mandate to have this
>>> information at hand.
>>> Another example of setting the value would be to depend on the
>>> expected path length (e.g. based on information from the routing
>>> protocol). It may, e.g., be reasonable to set a MAX_HOP_LIMIT that is,
>>> say, 50% longer than the distance in hops indicated by a routing
>>> protocol. I think that it would be very interesting to find out
>>> appropriate values as experiments for the protocol (given that the
>>> document is Experimental).
>>>
>>> How about adding the following text to MAX_HOP_LIMIT:
>>>
>>> ----- added text ------
>>> Finding optimal values for MAX_HOP_LIMIT is part of experiments that
>>> can be performed with the protocol proposed in this document.
>>> For example, one possible experiment would be to set MAX_HOP_LIMIT to
>>> different factors of the expected path length to the destination in
>>> number of hops if provided by a routing protocol.
>>> ---------------------
>>>
>>>
>>>
>>> Best regards
>>> Ulrich
>>>
>>>
>>> On Mon, Feb 11, 2013 at 10:47 AM, Jiazi Yi <ietf@jiaziyi.com> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> I had a through review of dff-07 with detailed comments. In the new
>>>> revision, my questions and concerns have been properly addressed --
>>>> thanks
>>>> to all the authors.
>>>>
>>>> The mechanism is well documented, and I have tested the protocol in the
>>>> scenarios described in the applicability statement, which brings
>>>> interesting performance improvement.
>>>>
>>>> Therefore, I would like to encourage the publication of it.
>>>>
>>>> Just one more comment:
>>>>
>>>>         o In section 8 Protocol Parameters, it would be better to have
>>>> some limitations or recommendations for those parameters. For
>>>> P_HOLD_TIME,
>>>> I think it's OK by saying "at least be MAX_HOP_LIMIT times  the
>>>> expected
>>>> time to send a Packet to a router on the same link.". It would be event
>>>> better to give such limitations to MAX_HOP_LIMIT. A regular value
>>>> related
>>>> to NET_DIAMETER won't work, because DFF can have significant higher hop
>>>> count and result in packet drop. Maybe we can have something like "it
>>>> MUST
>>>> NOT be higher than the number of routers in the DFF routing domain. If
>>>> the
>>>> number of routers is greater than 255, it is set to 255 by default."
>>>>
>>>> best
>>>>
>>>> Jiazi
>>>>
>>>>
>>>> On Feb 8, 2013, at 7:22 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
>>>>
>>>> > draft-cardenas-dff is under consideration for publication as an
>>>> > AD-sponsored individual submission Experimental RFC.  I agreed to
>>>> > sponsor it for publication because it doesn't really fit in any
>>>> > existing
>>>> > working groups and the requested publication status is Experimental.
>>>> > As
>>>> > part of the review process, the document is in a 2-week IETF last
>>>> > call.
>>>> > The last call announcement is included below.  To ensure the quality
>>>> > of
>>>> > the document, it would be helpful to get reviews from manet WG
>>>> > participants (posted to the ietf@ietf.org discussion list).
>>>> >
>>>> > Thanks.
>>>> >
>>>> > - Ralph
>>>> >
>>>> >
>>>> > =====
>>>> >
>>>> >
>>>> > The IESG has received a request from an individual submitter to
>>>> > consider
>>>> > the following document:
>>>> > - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>>> > <draft-cardenas-dff-09.txt> as Experimental RFC
>>>> >
>>>> > The IESG plans to make a decision in the next few weeks, and solicits
>>>> > final comments on this action. Please send substantive comments to
>>>> > the
>>>> > ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments
>>>> > may
>>>> > be
>>>> > sent to iesg@ietf.org instead. In either case, please retain the
>>>> > beginning of the Subject line to allow automated sorting.
>>>> >
>>>> > Abstract
>>>> >
>>>> >
>>>> >  This document specifies the "Depth-First Forwarding" (DFF) protocol
>>>> >  for IPv6 networks, a data forwarding mechanism that can increase
>>>> >  reliability of data delivery in networks with dynamic topology
>>>> > and/or
>>>> >  lossy links.  The protocol operates entirely on the forwarding
>>>> > plane,
>>>> >  but may interact with the routing plane.  DFF forwards data packets
>>>> >  using a mechanism similar to a "depth-first search" for the
>>>> >  destination of a packet.  The routing plane may be informed of
>>>> >  failures to deliver a packet or loops.  This document specifies the
>>>> >  DFF mechanism both for IPv6 networks (as specified in RFC2460) and
>>>> > in
>>>> >  addition also for LoWPAN "mesh-under" networks (as specified in
>>>> >  RFC4944).
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > The file can be obtained via
>>>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>>> >
>>>> > IESG discussion can be tracked via
>>>> > http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>>> >
>>>> >
>>>> > The following IPR Declarations may be related to this I-D:
>>>> >
>>>> >  http://datatracker.ietf.org/ipr/1645/
>>>> >  http://datatracker.ietf.org/ipr/1646/
>>>> >
>>>> >
>>>> > _______________________________________________
>>>> > manet mailing list
>>>> > manet@ietf.org
>>>> > https://www.ietf.org/mailman/listinfo/manet
>>>>
>>> _______________________________________________
>>> manet mailing list
>>> manet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/manet
>>>
>

From mcr@sandelman.ca  Mon Feb 11 19:06:13 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCCC21F8703 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ol140WnLk76A for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:06:08 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id AD62721F86F8 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:06:08 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id EB19A2016D; Mon, 11 Feb 2013 22:12:23 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 4C1896376A; Mon, 11 Feb 2013 22:05:04 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 38216636C5; Mon, 11 Feb 2013 22:05:04 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Remote Participation Services
In-Reply-To: <51199813.8060208@network-heretics.com>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 11 Feb 2013 22:05:04 -0500
Message-ID: <18073.1360638304@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Keith Moore <moore@network-heretics.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 03:06:14 -0000

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


>>>>> "Keith" =3D=3D Keith Moore <moore@network-heretics.com> writes:
    Keith> Can we *please* discourage the habit of treating IETF WG
    Keith> meetings as one series of PowerPoint presentations after
    Keith> another?  This makes the meetings much less productive.

    Keith> The notion that there are supposed to be slides for each
    Keith> presentation, is IMO, a huge error.

It's not the slides that are the problem.=20=20
It's the "presentation" itself.


If we could, I would organize the rooms in circular style, but it doesn't
scale to several hundred people.

(If there are slides, we need to make sure that they are received early,
in a vendor-neutral archival happy format, and can be distributed in
advance.)


=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



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

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

iQCVAwUAURmxYIqHRg3pndX9AQKTwgP/TAfQzo0Ttw0XiEA3/rcrcadlg1JV9OcW
/dUJ6Nf5H+jQO7SinRA8BkVUcx1gsRHKL6VyICzoP3BRGcxhTXdfJIZoBS+ZzWZY
cwW+7iqiMINYJgzx6csBoHv8y7ruqdwGXRc+eTGlSrAEBBW2WQCNmDA64RzDLQsj
MI/V9a27hpY=
=FWoU
-----END PGP SIGNATURE-----
--=-=-=--

From ulrich@herberg.name  Mon Feb 11 19:08:40 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653A321F8891 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:08:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[AWL=-0.245, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 ekXSeYVhuu6n for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:08:33 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id B8D1721F8887 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:08:32 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id kp1so3391172pab.31 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:08:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to; bh=dUnE9V5uhcdqktyfIJYSlWypym03okRdJSIn1n7OUIc=; b=FFTllZEMtpLri6VLJ5slB9Lg3X5/ynzpstXRwy4A46gPmUrXiARAXq3ptn8FgoqEPF THJSlH11sjG6R/WOOnF8yBCPgzqgUdGV31N5bBhRcJf1Sqe0YTyp/h1elT1Kby8cA6Gk oMTTMQM0HQ//w5MuX05b2FfpGQkytu2oFlBoo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=dUnE9V5uhcdqktyfIJYSlWypym03okRdJSIn1n7OUIc=; b=pYtCiuhpJOaVXMVMCV69WF/NFcrzFbfel94OmYR7lyJeUYcexHSRHyay5cNynGRAlW KQ5lTzgPzWyTlLk/MRUK4SDTZxCHQ7wGQ7Wplm8lewJBG6ZfPVyWoTS8nrW9ij/UjcY6 ipU9KJoWxZbpQKWMYHdCC8UFqvdqZQCMuOV4UYuKEUK2bLHq/a/U6Ew3EF0XNniMHaYY LLcPQkh8xCXquUcSVky3ZkT4jdLKrjwLvOPo7ESGZh+UEzRIfXZCz+rTAILhL56yBXYQ Qi1aXDLKciINCAI4W43CAelNLe2bluTAilFcwFhqPLF6JUK35kVN0TCdL+k2BpFvxX+b HEeA==
X-Received: by 10.66.86.71 with SMTP id n7mr47334019paz.77.1360638512188; Mon, 11 Feb 2013 19:08:32 -0800 (PST)
Received: from ?IPv6:2601:9:3d00:65:f9fa:5bfa:ff3d:f4ff? ([2601:9:3d00:65:f9fa:5bfa:ff3d:f4ff]) by mx.google.com with ESMTPS id z6sm45137701pav.3.2013.02.11.19.08.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 19:08:31 -0800 (PST)
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CAK=bVC9=vmtTvdrj93gMtJA_7yih9BOzQbCURH-2zaVFuoHG7g@mail.gmail.com> <6.2.5.6.2.20130211143859.0956a928@resistor.net>
Mime-Version: 1.0 (1.0)
In-Reply-To: <6.2.5.6.2.20130211143859.0956a928@resistor.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBF1A71A-3476-4B86-BD5E-5646204F9A3E@herberg.name>
X-Mailer: iPad Mail (10A403)
From: Ulrich Herberg <ulrich@herberg.name>
Subject: Re: The RFC Acknowledgement (off-topic)
Date: Mon, 11 Feb 2013 19:08:31 -0800
To: SM <sm@resistor.net>
X-Gm-Message-State: ALoCoQmgDVHjJtCC3ZrMcWxCrhWmhLYYfNcM/xgrfCKUiM4dqwdNb3IjD359DmKaxMMI9PyzqJwz
Cc: "Sandra L. Cespedes" <slcesped@bbcr.uwaterloo.ca>, "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, 12 Feb 2013 03:08:40 -0000

Alright, thanks

Ulrich

On Feb 11, 2013, at 15:36, SM <sm@resistor.net> wrote:

> Hi Ulrich,
> At 13:25 11-02-2013, Ulrich Herberg wrote:
>> (it is generally appreciated in the IETF to use real first and last name)=
.
>=20
> Agreed.
>=20
> Your comment reminded me of the message at http://www.ietf.org/mail-archiv=
e/web/domainrep/current/msg00085.html
>=20
>> Generally, I think the topic has been well summarized by Fred and
>> others, and I don't see how continuing it would generate new value.
>> See below:
>=20
> Agreed.
>=20
>> I am not sure what this is about because it does not seem related to
>> this discussion. But since I am the editor of the mentioned document,
>=20
> It was a gentle note to one of the authors (see Note 4).
>=20
> I pointed to two reviews about a draft and mentioned that the first one wa=
s clearer to me.
>=20
>> I still wonder what you mean but "the person [has] zero reputation".
>> There is a related topic on this mailing list about the mentioned
>> draft, so I suggest sending your comments as reply to that thread.
>=20
> I agree that it is better to stick to the topic.  I'll answer in here as t=
o avoid generating two messages.  I meant that I have never interacted with t=
he person through email or in person.  There is less bias [1].  The content o=
f the message matters; it does not matter who wrote it.
>=20
> Regards,
> -sm
>=20
> 1. www.cs.utexas.edu/users/mckinley/notes/snodgrass-tods-2007.pdf=20

From joelja@bogus.com  Mon Feb 11 19:23:25 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E52321F88CA for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.454
X-Spam-Level: 
X-Spam-Status: No, score=-102.454 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KqAPOyIzZdUu for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:23:22 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB3021F889C for <ietf@ietf.org>; Mon, 11 Feb 2013 19:23:21 -0800 (PST)
Received: from joels-MacBook-Air.local (c-24-5-127-59.hsd1.ca.comcast.net [24.5.127.59]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1C3NGvT087014 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 12 Feb 2013 03:23:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <5119B59F.6080103@bogus.com>
Date: Mon, 11 Feb 2013 19:23:11 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com>
In-Reply-To: <51199813.8060208@network-heretics.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, 12 Feb 2013 03:23:18 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 03:23:25 -0000

On 2/11/13 5:17 PM, Keith Moore wrote:
> On 02/05/2013 11:04 AM, IETF Chair wrote:
>> 3.4. Slide Sharing
>>
>>     Slides are often sent by email in advance of the meeting.
>>         WebEx allows the slides and desktop applications to be viewed 
>> by the
>>     remote participants.  These are controlled by the presenter.  The
>>     presenter can be shifted from participant to participant as needed.
>>
>
> Can we *please* discourage the habit of treating IETF WG meetings as 
> one series of PowerPoint presentations after another?   This makes the 
> meetings much less productive.
>
> The notion that there are supposed to be slides for each presentation, 
> is IMO, a huge error.
If you have prepared materials for your segment of the agenda they 
should be available beforehand, full stop.

If you don't, then I imagine they won't be. you're depriving some of 
participants who may not be familiar with your work the opportunity to 
review what you want to discuss. but that's between you and your working 
group chairs.
>
> Keith
>


From melinda.shore@gmail.com  Mon Feb 11 19:28:16 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2351D21F88FD for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:28:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.332
X-Spam-Level: 
X-Spam-Status: No, score=-1.332 tagged_above=-999 required=5 tests=[AWL=-2.268, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,  RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEFlLVMBohVR for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:28:15 -0800 (PST)
Received: from mail-ia0-x22f.google.com (ia-in-x022f.1e100.net [IPv6:2607:f8b0:4001:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A366621F8786 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:28:15 -0800 (PST)
Received: by mail-ia0-f175.google.com with SMTP id r4so7007074iaj.6 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:28:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=WrG6/i2Dxy2THO0ygv8oNxCiby8vsTWB1mH0BVd/lQc=; b=KrK2WLZAER2+l41ESlo+uxEHHmhJ8DThxKchG7LzAbG29JYAq5Nt563lWAWkznGzbk hyl/1RXEzlGwlv3txBG4uZcB1J0I+R/z0bYPBU265ssR2fxfsf8Bv56ssKf5bIyzxFbq h3gkWURDm6nqJu3c5aqp2Z8FoI/1mddjhtencVOHkT+n74Alv+S0OHKJdbkWXtbH1Pzv XRQsUB2KW+4QA9gZSfTqDklXUpHoh84HOk3CrcPhvC0td6v+TKtCu1WoTfQvsnbWC6kl 2lEWPghK+USeeJqzRCJBtbBJ1OlovzGDwmGi1ybCAeS1gwxIB+2tE0TlIw7pgqvPk5K8 wKSA==
X-Received: by 10.42.126.133 with SMTP id e5mr20721598ics.17.1360639695229; Mon, 11 Feb 2013 19:28:15 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id qn10sm4970945igc.6.2013.02.11.19.28.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 19:28:14 -0800 (PST)
Message-ID: <5119B6C6.2010200@gmail.com>
Date: Mon, 11 Feb 2013 18:28:06 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <5119B59F.6080103@bogus.com>
In-Reply-To: <5119B59F.6080103@bogus.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: Tue, 12 Feb 2013 03:28:16 -0000

On 2/11/13 6:23 PM, joel jaeggli wrote:
> If you don't, then I imagine they won't be. you're depriving some of
> participants who may not be familiar with your work the opportunity to
> review what you want to discuss. but that's between you and your working
> group chairs.

In theory they should have read any drafts that are on the
agenda.  I used to agree with Keith but I'm drifting more
towards feeling that particularly for remote participants (and
I'm saying this as someone who's done the remote participation
thing upwards of a dozen times) it's helpful to have a
summary of the issues under discussion.  Not every slide set
contains material you should have gotten from reading the
draft.  Some contain material you should have gotten from
reading the mailing list, but even so a summary of issues needing
attention/resolution is useful.

Melinda



From bob.hinden@gmail.com  Mon Feb 11 19:46:44 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED6221F8A61 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:46:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.548
X-Spam-Level: 
X-Spam-Status: No, score=-101.548 tagged_above=-999 required=5 tests=[AWL=-1.596, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8IXEcjblKzJx for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:46:43 -0800 (PST)
Received: from mail-we0-x233.google.com (we-in-x0233.1e100.net [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id D6CEB21F8A67 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:46:42 -0800 (PST)
Received: by mail-we0-f179.google.com with SMTP id x43so5444860wey.24 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=yZYsq/hfjNigyvhV9sU1FdcUj3fOod4pthHYHjk7ydI=; b=TiOUZeQ4yamSRsKtBJ7Zk2eDyPgucIyqNxmWST1+dfdOthcMfPWFOUJwgC5kMKqjb/ hS+JfiVeZ2EboWGBvav6P4k58aFVNP5TdloVSYCMNJq27rugFioT6dCxBQaTJRZDEItk +uNWnkkExFwPQtvjdGEt/by1n4wbgJJhNs+9UWpVi0HPvFpjsi0YHD791nw1M5Pt51VC wBbgYxCsWsaqL2WhZ3iMS+YK6CDrKHDhQNnPXRDMW8ATHB9pJEf9+x0/2v0NpMdOZgxE ANuXe0ueBOum88iXEOcvK/MwCOmX1WydS9TrmbEUQnHmEYz4YHs6Qa303PHgMDLav0CK KluQ==
X-Received: by 10.180.85.97 with SMTP id g1mr293056wiz.29.1360640801911; Mon, 11 Feb 2013 19:46:41 -0800 (PST)
Received: from [10.0.0.23] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPS id n10sm37096571wia.0.2013.02.11.19.46.39 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 19:46:40 -0800 (PST)
Subject: Re: Remote Participation Services
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <51199813.8060208@network-heretics.com>
Date: Mon, 11 Feb 2013 19:46:36 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com>
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com>
To: Keith Moore <moore@network-heretics.com>
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, 12 Feb 2013 03:46:44 -0000

Keith,

On Feb 11, 2013, at 5:17 PM, Keith Moore wrote:

> On 02/05/2013 11:04 AM, IETF Chair wrote:
>> 3.4. Slide Sharing
>>=20
>>    Slides are often sent by email in advance of the meeting.
>>        WebEx allows the slides and desktop applications to be viewed =
by the
>>    remote participants.  These are controlled by the presenter.  The
>>    presenter can be shifted from participant to participant as =
needed.
>>=20
>=20
> Can we *please* discourage the habit of treating IETF WG meetings as =
one series of PowerPoint presentations after another?   This makes the =
meetings much less productive.
>=20
> The notion that there are supposed to be slides for each presentation, =
is IMO, a huge error.

I disagree.  The slides are a great help for non-native english =
speakers.

Bob



From bob.hinden@gmail.com  Mon Feb 11 19:51:16 2013
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C86D521F8ABA for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fuOFLjFi4yHU for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 19:51:16 -0800 (PST)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 2282221F8AB8 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:51:15 -0800 (PST)
Received: by mail-we0-f178.google.com with SMTP id x48so5408444wey.37 for <ietf@ietf.org>; Mon, 11 Feb 2013 19:51:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:subject:mime-version:content-type:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=px7/zGfj5MC+9O5XU3wNBftrCJhiLs2vEgtVh9ck3FI=; b=Agfnd1IAofigXZo79ziVYtP9xMQqnrbzG5zlfoA/H8ljCUMIDCstjAnL/HL81S0a5P 6Y26qgqYus82LsCVQH5pCUz0Ij9NYz/2P8nKT7Om+YvbAcriD3EAqTu4W0T+J0lrW1m1 eiiT1B6zEiojAFrQ7hDURlr8w08l5f+ngek1qEoFZ98EKGEvz/3p0R1vMsjkbABcJgKB ToMiIiK4OTAoGq4/wvE61yKnCb/cVe77jppjzZFyaAQbOLEJaLf63kM2jYcaH4EEj2NQ 4AckgwsyFs6+x1ocy7WHjqfzS+cXJ3rx057qdNK8UyEoq0KOqapvah3gpwIYvVaTDdhM RdDg==
X-Received: by 10.194.238.5 with SMTP id vg5mr27885577wjc.40.1360641074137; Mon, 11 Feb 2013 19:51:14 -0800 (PST)
Received: from ?IPv6:2601:9:4080:10:e568:dcf9:2190:5f24? ([2601:9:4080:10:e568:dcf9:2190:5f24]) by mx.google.com with ESMTPS id q13sm35310662wie.0.2013.02.11.19.51.11 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 19:51:13 -0800 (PST)
Subject: Re: The RFC Acknowledgement
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
Date: Mon, 11 Feb 2013 19:51:07 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E7A0793-9896-4A5B-9037-3DA768F72A37@gmail.com>
References: <CADnDZ8_E-cDqhXWV-f3MjoDo9hFeCVAdVTmRQ+McA--_3smyJQ@mail.gmail.com> <CAF4+nEFGdiwFiRkVtUQLR6b89c3SdpVcOmHULe35hwd+wg8CsA@mail.gmail.com> <CADnDZ8_wCFNsWXdQv29RpVrFnzZLeuBybaBEPR63OvUxw-ieyQ@mail.gmail.com> <51180ad8.0727dc0a.7e34.ffffeb5cSMTPIN_ADDED_MISSING@mx.google.com> <CADnDZ89ckeZzVzU7d_ru=9U9qdhQ=R6rmJRteHDj0SwDw+jv6g@mail.gmail.com> <6.2.5.6.2.20130211104011.0b8299d0@resistor.net> <CADnDZ88eH+uYCP7+qnYQ_Tiq=W7xpq1SrB-TzZ-z0tFO=xvySA@mail.gmail.com> <511978DD.8000804@bogus.com> <CADnDZ8-9M_ye1Q7xi=ZjSkj3XNm9eOxviCn-=GJTNW8ZHZs=nQ@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
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, 12 Feb 2013 03:51:17 -0000

AB,

On Feb 11, 2013, at 3:32 PM, Abdussalam Baryun wrote:

> On 2/12/13, joel jaeggli <joelja@bogus.com> wrote:
>>> Do you mean that IETF is producing what it does not own, or IETF has
>>> no right to edit/amend a document that it is publishing? I
>>> misunderstand your point,
>>>=20
>> Once an RFC number is issued  and the document published, the content =
of
>> that RFC never changes.
>>=20
>> See RFC 2200 section 2
>>=20
> I agree, but still IETF can update or obsolete any document,
>=20
> The question ment to be:
> Do you mean that IETF is producing what it does not own, or IETF has
> no right to edit/amend a document that will be published?

The IETF has the right to make derivative works.  That is, use the =
contents of an RFC to publish a new one.

We can also file errata, declare an RFC historic, etc.

Bob



From melinda.shore@gmail.com  Mon Feb 11 20:22:53 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DA321F86D8 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.212
X-Spam-Level: 
X-Spam-Status: No, score=-1.212 tagged_above=-999 required=5 tests=[AWL=-2.148, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, FH_HOST_EQ_D_D_D_DB=0.888, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877,  RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b137YXfyPWOM for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:22:52 -0800 (PST)
Received: from mail-ia0-x233.google.com (mail-ia0-x233.google.com [IPv6:2607:f8b0:4001:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id CBE6721F86CB for <ietf@ietf.org>; Mon, 11 Feb 2013 20:22:52 -0800 (PST)
Received: by mail-ia0-f179.google.com with SMTP id x24so7101977iak.24 for <ietf@ietf.org>; Mon, 11 Feb 2013 20:22:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Uphz6R7fFWUNQ5pBuJjh2Gj5/hdS3o3Z37NAfh/hH5E=; b=Mtd5AMNye/nSxSqkHrD+8CZpgDMv2EAHCBluIz2tuadhvSJm50tl7irmjog3bjzNfx oXMsbEZGAsu4mwnGzMmkW93CCzb8qm7XjptqnMr/+nowFXAJDDmv+ysvECHCOCiUVvY5 lEgUzRccb15R4sSqCA1tcZdueZZdrliWxXsx16PIS1H7XBVorZQCvhurjQta2Vp/r21F gCB738F3uavYOEHlBSIW8LRVb5L+uDhaPomk007mWy0EWWDruHDld/3Lga5BccGMFHn6 LXXq8Afwjdavrghetanp8pWGxq1azxpxAEiTlabTuYRQfuFZMAZTiuiGMd23+S7EWcr6 xm1A==
X-Received: by 10.43.117.136 with SMTP id fm8mr21218721icc.33.1360642972415; Mon, 11 Feb 2013 20:22:52 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id eg7sm29733803igc.7.2013.02.11.20.22.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Feb 2013 20:22:51 -0800 (PST)
Message-ID: <5119C399.8040400@gmail.com>
Date: Mon, 11 Feb 2013 19:22:49 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com>
In-Reply-To: <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 04:22:53 -0000

On 2/11/13 6:46 PM, Bob Hinden wrote:
> I disagree.  The slides are a great help for non-native english
> speakers.

For better or worse I think that in this century slides have
become a medium for documentation rather than just presentation,
and so it's useful to be clear which is which.  Documentation is
good, presentation is generally (but not always) not a good use
of meeting time.

Melinda


From moore@network-heretics.com  Mon Feb 11 20:29:52 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEBBA21F8B1D for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:29:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.276
X-Spam-Level: 
X-Spam-Status: No, score=-3.276 tagged_above=-999 required=5 tests=[AWL=0.323,  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 pKVsPERJp8mW for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:29:51 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 39CA021F8AEA for <ietf@ietf.org>; Mon, 11 Feb 2013 20:29:51 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id CE5BE20B3C; Mon, 11 Feb 2013 23:29:50 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Mon, 11 Feb 2013 23:29:50 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=VgyeWE14nFGqnGYERtkYj2 g+jNE=; b=tCypNH+XC18UK9Jx4RWDreNbfwG1QZ1jR/TzU047gg10ZkkNFCeg6l tA1o+sa2aUNtol58jyZAVDWKHSgghM/99/Lezt374r4CZs91cF/6kuSngykI06Yw QxPxZfM20TR3H4jUhVJepmXE8sgo1dKAgWqSMqoAr9eETz8TEwmMI=
X-Sasl-enc: aznjc9MrEi0xn9bu8duiSDNYFsi/+wXkIbKqhNMma5U6 1360643390
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id E84838E099A; Mon, 11 Feb 2013 23:29:49 -0500 (EST)
Message-ID: <5119C53A.803@network-heretics.com>
Date: Mon, 11 Feb 2013 23:29:46 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <5119B59F.6080103@bogus.com>
In-Reply-To: <5119B59F.6080103@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 04:29:52 -0000

On 02/11/2013 10:23 PM, joel jaeggli wrote:
> On 2/11/13 5:17 PM, Keith Moore wrote:
>> On 02/05/2013 11:04 AM, IETF Chair wrote:
>>> 3.4. Slide Sharing
>>>
>>>     Slides are often sent by email in advance of the meeting.
>>>         WebEx allows the slides and desktop applications to be 
>>> viewed by the
>>>     remote participants.  These are controlled by the presenter.  The
>>>     presenter can be shifted from participant to participant as needed.
>>>
>>
>> Can we *please* discourage the habit of treating IETF WG meetings as 
>> one series of PowerPoint presentations after another?   This makes 
>> the meetings much less productive.
>>
>> The notion that there are supposed to be slides for each 
>> presentation, is IMO, a huge error.
> If you have prepared materials for your segment of the agenda they 
> should be available beforehand, full stop.

Agree.   But perhaps "slides" are not, in general, the best kind of 
preparation?    Perhaps some brief notes consisting of a summary of the 
discussion topic and the major points to be made (perhaps from multiple 
points of view), with pointers to I-Ds or other relevant background 
documents, would be more appropriate?

Perhaps instead of talking about "presentations", this document should 
talk about "discussions"?

And perhaps instead of "Slide Sharing" the section should read something 
like:

3.4. Sharing of Briefing Material

Each speaker is strongly encouraged to prepare material to brief meeting 
participants about the topic to be discussed during his or her meeting 
segment.   Such a briefing should generally be less than two pages in 
length, and contain a summary of the topic to be discussed.   If there 
are multiple points-of-view that need to be reconciled, the briefing 
should attempt to capture these. When appropriate, the briefing should 
also include URLs of background material, such as RFCs or 
Internet-Drafts, that discussion participants should be familiar with.

Both local and remote meeting participants are strongly encouraged to 
download and read such material prior to the meeting.

Such materials should be in a format that everyone can read, e.g. HTML, 
or PDF.

If "slides" are used to provide visual aids for the discussion, these 
should also be made available for download prior to the meeting, in PDF 
format.



From moore@network-heretics.com  Mon Feb 11 20:34:32 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F07FE21F8B2B for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.316
X-Spam-Level: 
X-Spam-Status: No, score=-3.316 tagged_above=-999 required=5 tests=[AWL=0.283,  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 WOQk+p6NQHo3 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:34:32 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 65AA321F8B26 for <ietf@ietf.org>; Mon, 11 Feb 2013 20:34:32 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id DC5EA20A7B; Mon, 11 Feb 2013 23:34:31 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute4.internal (MEProxy); Mon, 11 Feb 2013 23:34:31 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=ep5330wWl7MtadwEOXTht4 YZuiQ=; b=WBTJPTjlHYQ7sU9VNlXCsYzCDgEsI6leXeF6rCyIU5lt6SkJUaqBf/ qE1thK1h5CduqKjnSgN+MjXB4nXtQY7X04eZiFAjovRwLdpiAhyBSo+Kbb6Ai6bp a6bK7aQmm4m7PlyBSt+haDjaKHDK9XqSsOBTgMOTzIC7Qw4kemj5c=
X-Sasl-enc: nET7LDMaRG6S8zm4GnZoZFAEAfmrc0hcLEIuMSQXIq0z 1360643671
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 31F278E0994; Mon, 11 Feb 2013 23:34:31 -0500 (EST)
Message-ID: <5119C653.8070903@network-heretics.com>
Date: Mon, 11 Feb 2013 23:34:27 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com>
In-Reply-To: <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 04:34:33 -0000

On 02/11/2013 10:46 PM, Bob Hinden wrote:
> Keith,
>
> On Feb 11, 2013, at 5:17 PM, Keith Moore wrote:
>
>> On 02/05/2013 11:04 AM, IETF Chair wrote:
>>> 3.4. Slide Sharing
>>>
>>>     Slides are often sent by email in advance of the meeting.
>>>         WebEx allows the slides and desktop applications to be viewed by the
>>>     remote participants.  These are controlled by the presenter.  The
>>>     presenter can be shifted from participant to participant as needed.
>>>
>> Can we *please* discourage the habit of treating IETF WG meetings as one series of PowerPoint presentations after another?   This makes the meetings much less productive.
>>
>> The notion that there are supposed to be slides for each presentation, is IMO, a huge error.
> I disagree.  The slides are a great help for non-native english speakers.
>
Let me back up a bit, because I don't think I stated my case strongly 
enough.

WG meetings should not, in general, be used for presentations.  They 
should primarily be used for discussions.   Presentations are largely a 
waste of precious WG time.

It is sometimes possible to prepare slides to help facilitate 
discussions.  But more often than not, the exercise of preparing slides 
encourages the speaker to fill up most or all of the available time with 
presentation material, leaving insufficient time for discussion of 
important questions.

I certainly agree that when presentations are made, the slides can be 
helpful to those who aren't so fluent in English.   My point is that 
presentations should be made only rarely.

Keith


From jmh@joelhalpern.com  Mon Feb 11 20:46:10 2013
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44F6B21F8A49 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:46:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.261
X-Spam-Level: 
X-Spam-Status: No, score=-102.261 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXM85V56nE84 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:46:09 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id B165D21F8B2E for <ietf@ietf.org>; Mon, 11 Feb 2013 20:46:09 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 5AE50A395C for <ietf@ietf.org>; Mon, 11 Feb 2013 20:46:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id D56BA1C088B; Mon, 11 Feb 2013 20:46:06 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.104] (pool-70-106-134-125.clppva.east.verizon.net [70.106.134.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 309A21C088A; Mon, 11 Feb 2013 20:46:06 -0800 (PST)
Message-ID: <5119C905.9060603@joelhalpern.com>
Date: Mon, 11 Feb 2013 23:45:57 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com> <5119C653.8070903@network-heretics.com>
In-Reply-To: <5119C653.8070903@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 04:46:10 -0000

Keith, you seem to be asking for something (discussion, wit no 
presentation), that has never happened in the WGs I have attended in the 
last 20 years.  Even the WG sessions that had the best, most useful, 
discussions, generally started with a presentation of the topic and issue.

Such initial presentation is usually strongly helped by clear bullets 
that everyone can follow to keep straight what is being discussed.

yes, many of the briefings (here and elsewhere) are people reading their 
slides.  yes, Powerpoint seems to make this worse in the way the tool is 
designed.  But the issues seems to me not to e slides.

If I had to guess, it is a combination of folks lacking confidence to 
discuss their material, folks doing what they have seen, and the 
patterns the tools encourage.  There almost certainly are other factors.

If you could assume that all 10 people you were talking to were fully up 
to speed on the topic, and had not lost context to the other 10 WG 
sessions they have been preparing for, and if we knew how to hold 
conversations effectively in rooms with 50+ people, and ...

Yes, we should be looking for encouraging, and thanking / rewarding, 
those people who use their slots to briefly present and then engage in 
conversation with the WG.

But lets not invent a fictional past in which this was some how natural, 
or even the norm.

Yours,
Joel

On 2/11/2013 11:34 PM, Keith Moore wrote:
> On 02/11/2013 10:46 PM, Bob Hinden wrote:
>> Keith,
>>
>> On Feb 11, 2013, at 5:17 PM, Keith Moore wrote:
>>
>>> On 02/05/2013 11:04 AM, IETF Chair wrote:
>>>> 3.4. Slide Sharing
>>>>
>>>>     Slides are often sent by email in advance of the meeting.
>>>>         WebEx allows the slides and desktop applications to be
>>>> viewed by the
>>>>     remote participants.  These are controlled by the presenter.  The
>>>>     presenter can be shifted from participant to participant as needed.
>>>>
>>> Can we *please* discourage the habit of treating IETF WG meetings as
>>> one series of PowerPoint presentations after another?   This makes
>>> the meetings much less productive.
>>>
>>> The notion that there are supposed to be slides for each
>>> presentation, is IMO, a huge error.
>> I disagree.  The slides are a great help for non-native english speakers.
>>
> Let me back up a bit, because I don't think I stated my case strongly
> enough.
>
> WG meetings should not, in general, be used for presentations.  They
> should primarily be used for discussions.   Presentations are largely a
> waste of precious WG time.
>
> It is sometimes possible to prepare slides to help facilitate
> discussions.  But more often than not, the exercise of preparing slides
> encourages the speaker to fill up most or all of the available time with
> presentation material, leaving insufficient time for discussion of
> important questions.
>
> I certainly agree that when presentations are made, the slides can be
> helpful to those who aren't so fluent in English.   My point is that
> presentations should be made only rarely.
>
> Keith
>
>

From moore@network-heretics.com  Mon Feb 11 20:57:21 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F05121F8B48 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level: 
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[AWL=0.251,  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 ZcRxJw1K9JoS for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 20:57:20 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id BBF5C21F8B1A for <ietf@ietf.org>; Mon, 11 Feb 2013 20:57:20 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 45C65207F2; Mon, 11 Feb 2013 23:57:20 -0500 (EST)
Received: from frontend2.nyi.mail.srv.osa ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 11 Feb 2013 23:57:20 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=7YRQngco1oSul2DuaYGPbd q83xU=; b=J7nLF4MMPKgAFelzTg/qtbE1fDT9LCgRZ+itoLQ+JtQDm2h91B9NjC FrQ1L32OnIOtFzFUBhpNqVFp5QDPwtq+ML1T5TKO5cV4vvdr0QRCIR2fdGbx5RGV XGyQ31tZcyFThNjqymB3JAQEAwON5WmxUWkVqt92wb61IUrGfwX08=
X-Sasl-enc: hRjwI6sHBfasl5g52Gq5enfSmFUkxRnyz3FEM+5LwpRl 1360645039
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 78EEB4825F4; Mon, 11 Feb 2013 23:57:19 -0500 (EST)
Message-ID: <5119CBAB.7060401@network-heretics.com>
Date: Mon, 11 Feb 2013 23:57:15 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com> <5119C653.8070903@network-heretics.com> <5119C905.9060603@joelhalpern.com>
In-Reply-To: <5119C905.9060603@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 04:57:21 -0000

On 02/11/2013 11:45 PM, Joel M. Halpern wrote:
> Keith, you seem to be asking for something (discussion, wit no 
> presentation), that has never happened in the WGs I have attended in 
> the last 20 years.  Even the WG sessions that had the best, most 
> useful, discussions, generally started with a presentation of the 
> topic and issue.
>
> Such initial presentation is usually strongly helped by clear bullets 
> that everyone can follow to keep straight what is being discussed.
>
> yes, many of the briefings (here and elsewhere) are people reading 
> their slides.  yes, Powerpoint seems to make this worse in the way the 
> tool is designed.  But the issues seems to me not to e slides.
>
> If I had to guess, it is a combination of folks lacking confidence to 
> discuss their material, folks doing what they have seen, and the 
> patterns the tools encourage.  There almost certainly are other factors.
>
> If you could assume that all 10 people you were talking to were fully 
> up to speed on the topic, and had not lost context to the other 10 WG 
> sessions they have been preparing for, and if we knew how to hold 
> conversations effectively in rooms with 50+ people, and ...
>
> Yes, we should be looking for encouraging, and thanking / rewarding, 
> those people who use their slots to briefly present and then engage in 
> conversation with the WG.
>
> But lets not invent a fictional past in which this was some how 
> natural, or even the norm.
>
I remember IETF before PowerPoint.

Yes, people wrote topics or drew diagrams on transparencies that were 
projected for viewing within the room.   But (perhaps because preparing 
such materials was laborious) I don't recall the majority of WG time 
being devoted to reading things from those slides.  I do recall lots of 
fruitful discussions.

Keith

p.g. Admittedly, there were other differences when I first started 
participating in IETF.  e.g.  Most people didn't have laptops, and the 
rooms didn't have wireless Internet, so you didn't see meeting rooms 
full of people playing solitare, reading email, and/or browsing the web 
and not paying attention.


From dougb@dougbarton.us  Mon Feb 11 22:15:34 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B91721F8C07 for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 22:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.021,  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 xqb7RszG2hLo for <ietf@ietfa.amsl.com>; Mon, 11 Feb 2013 22:15:33 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id AE24021F8C04 for <ietf@ietf.org>; Mon, 11 Feb 2013 22:15:33 -0800 (PST)
Received: from [IPv6:2001:470:d:5e7:6d9c:9b05:e0e1:ccfc] (unknown [IPv6:2001:470:d:5e7:6d9c:9b05:e0e1:ccfc]) by dougbarton.us (Postfix) with ESMTPSA id 27B1222B1C for <ietf@ietf.org>; Tue, 12 Feb 2013 06:15:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1360649733; bh=1otRCYP7COzNn5QIRjN/vrvkHBCSKx+xbB47NHdA7p8=; h=Date:From:To:Subject:References:In-Reply-To; b=Oyxg8STv6AsnfVhEw71nBCzB+YtSaERraD0yRD7CvP9kLXkK8N6JWE0twx45FWGF8 IK0nIAxTCDUZUsa4vNyinakw8VQu2Wzdoe95OM81BC/OxhOnVTGcpBIVTkGkT29aOL ELn3YOU6KdOnma1bexbYmsnOKw1pCANflUxviAZM=
Message-ID: <5119DE03.8020105@dougbarton.us>
Date: Mon, 11 Feb 2013 22:15:31 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <D7FBA242-71F6-40C3-97D0-6084B67A4424@gmail.com> <5119C653.8070903@network-heretics.com>
In-Reply-To: <5119C653.8070903@network-heretics.com>
X-Enigmail-Version: 1.4.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 06:15:34 -0000

On 02/11/2013 08:34 PM, Keith Moore wrote:
>
> WG meetings should not, in general, be used for presentations.  They
> should primarily be used for discussions.   Presentations are largely a
> waste of precious WG time.
>
> It is sometimes possible to prepare slides to help facilitate
> discussions.  But more often than not, the exercise of preparing slides
> encourages the speaker to fill up most or all of the available time with
> presentation material, leaving insufficient time for discussion of
> important questions.
>
> I certainly agree that when presentations are made, the slides can be
> helpful to those who aren't so fluent in English.

So what you're arguing for is better slides, more time devoted to 
discussion, and WG leaders taking a more active role in making sure that 
those 2 things happen.

In other words, the same 3 conclusions we came to the last several times 
this topic has been discussed.

So how about the people who are interested in this topic put their 
effort into helping to make those things happen instead of rehashing the 
discussion again.

Doug


From ron.even.tlv@gmail.com  Mon Feb 11 22:49:10 2013
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBBEB21F8C2C; Mon, 11 Feb 2013 22:49:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.821
X-Spam-Level: 
X-Spam-Status: No, score=-2.821 tagged_above=-999 required=5 tests=[AWL=0.777,  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 P5kG57EVULoe; Mon, 11 Feb 2013 22:49:10 -0800 (PST)
Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by ietfa.amsl.com (Postfix) with ESMTP id 526C821F8C12; Mon, 11 Feb 2013 22:49:09 -0800 (PST)
Received: by mail-ee0-f54.google.com with SMTP id c41so3563353eek.27 for <multiple recipients>; Mon, 11 Feb 2013 22:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:to:cc:subject:date:message-id:mime-version :content-type:x-mailer:thread-index:content-language; bh=XBthy7qHCa6rhqGH+C+0GyMPmEeCpAk5C/dTz+Jn4gE=; b=cH2WXBXwabozYGONA7Akt+GuBz7+KIb8o0J2w+i7SGohv0E+7mzv6RbbwBDQTwVaae hCMbq/S0BIleoL6+jvZ7PljLKGD/X0KgAvPRHEdpCQBCa3sTni45S/UryE+RtCz6K9s4 qQG9q6oHKZa/yJmqaJEs4xG7zPKGrxl5wWgGsvuon6aMhXaxwplSu5BuL8vSwgZe2PPv +SX5MvYrQxVwhmCTbro2TnRUhgZ855xMch7N1/LwvZtm3AOIW3fBfGBvRyHF+VY0DHyW bHLsUCTzYlAxqUdOiOhMb7hxepTNUBTxV8u/Kum5ObtM26tQ0FtPVpsk2Ep9WCmPo2ft 6lFg==
X-Received: by 10.14.174.73 with SMTP id w49mr59825819eel.17.1360651748422; Mon, 11 Feb 2013 22:49:08 -0800 (PST)
Received: from RoniE (bzq-79-181-179-229.red.bezeqint.net. [79.181.179.229]) by mx.google.com with ESMTPS id m46sm2040420eeo.16.2013.02.11.22.49.05 (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 11 Feb 2013 22:49:07 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-ancp-pon.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-ancp-pon-04
Date: Tue, 12 Feb 2013 08:46:16 +0200
Message-ID: <06da01ce08ec$a9fc9590$fdf5c0b0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06DB_01CE08FD.6D8601D0"
X-Mailer: Microsoft Outlook 14.0
thread-index: Ac4I7KgEW1ueTd0DSHaPAhSPsbanHA==
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, 12 Feb 2013 06:49:11 -0000

This is a multipart message in MIME format.

------=_NextPart_000_06DB_01CE08FD.6D8601D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

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

Document: draft-ietf-ancp-pon-04

Reviewer: Roni Even

Review Date:2013-2-12

IETF LC End Date: 2013-2-19

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	OMCI is expanded very late in the document and not on the first
usage.

 


------=_NextPart_000_06DB_01CE08FD.6D8601D0
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;}
@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:296448786;
	mso-list-type:hybrid;
	mso-list-template-ids:1423221754 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New","serif"'>draft-ietf-ancp-pon-04<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2013&#8211;2&#8211;12<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2013-2&#8211;19<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as an Informational RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>OMCI is =
expanded very late in the document and not on the first =
usage.<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_06DB_01CE08FD.6D8601D0--


From abdussalambaryun@gmail.com  Tue Feb 12 00:32:42 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2244421F895B for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 00:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.554
X-Spam-Level: 
X-Spam-Status: No, score=-3.554 tagged_above=-999 required=5 tests=[AWL=0.045,  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 XvvQqPm5py-D for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 00:32:41 -0800 (PST)
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) by ietfa.amsl.com (Postfix) with ESMTP id 054B621F8958 for <ietf@ietf.org>; Tue, 12 Feb 2013 00:32:40 -0800 (PST)
Received: by mail-wi0-f173.google.com with SMTP id hq4so4091627wib.0 for <ietf@ietf.org>; Tue, 12 Feb 2013 00:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=eOlIxbwsToJcnCWqVrMMLsRQumBxPFMszZw043z9N9A=; b=o99P8/egTsQDR8m9dWNmIPX1pEZlmC7MJYcYXx0IBqldhjcnocAgQLlOM8bOtZSdGl Y7IcWgCH70kiAl5T96NMhdYQYFaiem9a0Xb03pBbu+EaZICb2CmjO0ibqk4LcT9/9pcr 4vVtFrRVMvjYrF+5aaHbonP/GBg6lT+7IjFOALW9xXq5Ib6J01WAHMXaVbUoMXG/qoD5 kkBOUJDt16g4xuuog2nx1zzKjJ7cme2b3oscTl0PXXJEffr9A7ucm8O4PXEqKOiJ8lbE sUKcDYmC1pl2jLfaD9blkETto/O86HsOQoW8QSWAg7YIJ15AfR92eVcmydO66JB9mNhc MBwA==
MIME-Version: 1.0
X-Received: by 10.194.75.196 with SMTP id e4mr29032782wjw.44.1360657960162; Tue, 12 Feb 2013 00:32:40 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Tue, 12 Feb 2013 00:32:39 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130206105058.098105a8@resistor.net>
References: <CADnDZ8_JWzp-P_Dk5wcu0OkMY7EWO21i_NmZ05aBQ4qqrGt0Yw@mail.gmail.com> <6.2.5.6.2.20130206105058.098105a8@resistor.net>
Date: Tue, 12 Feb 2013 09:32:39 +0100
Message-ID: <CADnDZ8_=Qtd93wQBAvEL9SN3UWsJ8JwU+mCojTfaPO8WzK8kKQ@mail.gmail.com>
Subject: Re: Remote Participation Services
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 08:32:42 -0000

I agree with Michael and SM, the importance is what is gained from the
face to face (F2F) meeting, if presentation is needed then do it. As I
am usually remote participant I see that Chairs are different in
handling the meetings, and there may be many reasons I don't know
about, however, it is the chair that should guide for the best gain
for the participants in the room and whom are remotely. Piriority of
presentations or/and specific issues that need to be solved, to
encourage progress of the WG in its active works and future work.

Keith is right, we should not spend time much on presenting drafts (
5minutes MAX, inputs from room is more important, which should
encourage inputs on mail-list), info is already there in IETF, but
slides are valuable for showing performance-results, graphs, plans,
scenarios for readers/commenters. We have a large time of discussion
available if we continue participate on lists as well, which should be
encouraged.

IMHO, F2F meetings in IETF sometimes lack inputs from inplementors or
users in industry/market which we want to hear; what does these
companies/end-users think about the I-D or WG performance/direction?
The interaction/feedbacks between IETF and companies/community using a
standard or future standard, is the main purpose I think from F2F
meeting. Our IETF I-Ds don't go much into details of applicability
(i.e. they try to make their work general, which may not be real),
which is good to show scenarios/case-studies by slides and
presentations.

AB

On 2/11/13, Michael Richardson wrote:
>>>>> "Keith" == Keith Moore <moore at network-heretics.com> writes:
    Keith> Can we *please* discourage the habit of treating IETF WG
    Keith> meetings as one series of PowerPoint presentations after
    Keith> another?  This makes the meetings much less productive.

    Keith> The notion that there are supposed to be slides for each
    Keith> presentation, is IMO, a huge error.

It's not the slides that are the problem.
It's the "presentation" itself.


If we could, I would organize the rooms in circular style, but it doesn't
scale to several hundred people.

(If there are slides, we need to make sure that they are received early,
in a vendor-neutral archival happy format, and can be distributed in
advance.)


-- 
Michael Richardson <mcr+IETF at sandelman.ca>, Sandelman Software Works


On 2/6/13, SM <sm@resistor.net> wrote:
> Hi Abdussalam,
> At 18:14 05-02-2013, Abdussalam Baryun wrote:
>>In the previous ietf meeting in July, I have submitted an I-D in one
>>WG but had no chance to present my participation remotely, as you
>>mention in 2.5. I would like the solution and that I will be able to
>>present remotely. I asked the WG if someone can present for me but
>>only WG darfts are done the way mentioned in 2.5,
>>
>>Please amend the [1] to include that there is difference process in
>>IETF participation remotely for WG I-Ds and Individual I-Ds,
>
> I read a review written by Allison Mankin [1].  I doubt that anyone
> can get a review of that quality in an IETF meeting.
>
> It was mentioned previously on this mailing list that meetings were
> about discussing issues and not about presenting I-Ds.  If I have a
> chance to present my I-D either in person or remotely, what's do the
> people in the room gain from it?
>
> Regards,
> -sm
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg76903.html
>
>

From ynir@checkpoint.com  Tue Feb 12 00:55:22 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEAAC21F8C51 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 00:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 D1Gin1ioxFzp for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 00:55:22 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id F37AE21F8C54 for <ietf@ietf.org>; Tue, 12 Feb 2013 00:55:21 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r1C8svVr007502; Tue, 12 Feb 2013 10:54:57 +0200
X-CheckPoint: {5119FF54-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.18]) by DAG-EX10.ad.checkpoint.com ([169.254.3.103]) with mapi id 14.02.0328.009; Tue, 12 Feb 2013 10:54:57 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Changing the value of RFCs not numbers (was Re: The RFC Acknowledgement)
Thread-Topic: Changing the value of RFCs not numbers (was Re: The RFC Acknowledgement)
Thread-Index: AQHOCLv6qoYb2m+keU+z/Qr/+OIZFZh1ykEA
Date: Tue, 12 Feb 2013 08:54:57 +0000
Message-ID: <4613980CFC78314ABFD7F85CC3027721119A4731@IL-EX10.ad.checkpoint.com>
References: <CADnDZ88AxFVC5bXmcVaJAD2XmV3wkrG99Q+L0aOKm3W9nUPkRQ@mail.gmail.com>
In-Reply-To: <CADnDZ88AxFVC5bXmcVaJAD2XmV3wkrG99Q+L0aOKm3W9nUPkRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [91.90.139.159]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <37F7AF858D6E8C47AFB6104AAA525318@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SM <sm@resistor.net>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 08:55:23 -0000

On Feb 12, 2013, at 2:57 AM, Abdussalam Baryun <abdussalambaryun@gmail.com>=
 wrote:

> Many said to me before as you do RFC don't change, it is already known
> in any org that documents don't change when published.

I think the reason this keeps coming up, is that the IETF documents are usu=
ally referenced by number rather than title. So you'd say that your system =
is compliant with RFC 5280 rather than saying that it is compliant with "In=
ternet X.509 Public Key Infrastructure Certificate and Certificate Revocati=
on List (CRL) Profile".

In other organizations, like the W3C, documents are referred to by name. So=
 "Content Security Policy 1.0" is called that when it's proposed, when it's=
 discussed, and when it's published. Even a later revision might be called =
"Content Security Policy 1.1", so version numbers, while they exist and are=
 accessible, are mostly hidden from the users.

Yoav


From sm@resistor.net  Tue Feb 12 01:22:34 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6DDE21F8C48; Tue, 12 Feb 2013 01:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aj13ey9hrQdS; Tue, 12 Feb 2013 01:22:32 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0CAF21F8AE7; Tue, 12 Feb 2013 01:22:31 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1C9MOiU024439; Tue, 12 Feb 2013 01:22:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360660950; bh=dDNqH9+0uQVO9GOirOifYKBiriLKW2oQSsMPHsjFYPw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=r63c0eZ7GEiAxOPny0jC59+WNakyRnDj/qs7ZouIOcXnkd1ltCgNFCoy9HPlUWc3a vPSTpCGH2PAi69gXLRJYAU7dcfjkBms4yx/0fW12BVMLaWgOuycEx2pRz0zS/I9mCY q+oq4W0BtwskEhs/tmW6TJwFQBSgbqANuWulxlmQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360660950; i=@resistor.net; bh=dDNqH9+0uQVO9GOirOifYKBiriLKW2oQSsMPHsjFYPw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=GgTuMFJ5BuA5b5mDTLz4J+cABshpR0lvabIXtpY93V+ma2MDLQHlThx389GtirrZG 8VIgVsurZduKpxi/b5hB4N87L+fn4y+DjLtbvTQsoQXXygAX/xLkL6jP8fuBmZh0Ro ewbfrfXUo5YeIo56IUqz/cnKGrEKdSwf6KL/+Ozc=
Message-Id: <6.2.5.6.2.20130211222756.0b8a9540@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 12 Feb 2013 01:08:12 -0800
To: iaoc@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Sunday IAOC Overview Session
In-Reply-To: <20130211225402.13757.92479.idtracker@ietfa.amsl.com>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Tue, 12 Feb 2013 09:22:35 -0000

At 14:54 11-02-2013, The IAOC wrote:
>Please let us know ahead of time if you have specific questions you would like
>to see discussed.

The latest minutes posted by the IAB is dated January 9, 2013.  The 
latest minutes posted by the IESG is dated January 24, 2013.  The 
latest minutes posted by the IETF Trust is dated November 12, 
2012.  The latest minutes posted by the IAOC is dated November 7, 2012.

The IETF Trust stated previously that the "Trustees are fully in 
agreement with this requirement for openness, transparency, and 
accountability, and are making a conscious effort to increase their 
reporting and community interaction".  I leave it to the reader to 
assess the results of that effort.

There were more than three financial statements posted yearly by the 
IAOC in 2009 and 2010.  There are only three yearly after 2010.

According to a RFP posted in May 2012 "Any Agreement negotiated with 
a Vendor, excluding cost, will be made public after execution".  I 
don't see the agreement at http://iaoc.ietf.org/contracts.html  The 
latest contract for the Secretariat is dated 2006.

During a past IETF meeting someone mentioned that "BCP 101 does not 
specify this [transparency requirements] level of detail".  From 
Section 7 of BCP 101:

   "Transparency: The IETF community shall have complete visibility into
      the financial and legal structure of the ISOC activities that are
      related to, but not part of, the IASA standards support activity.
      In particular, a detailed budget for the entire related ISOC
      activity, quarterly financial reports, and audited annual
      financial reports shall all be available to the IETF community.
      In addition, key contract material and MOUs shall also be publicly
      available, subject to any reasonable confidentiality obligations
      approved by the IAOC."

According to the IAOC:

   "The month's financial statement will be posted within 30 days of the
    end of the month."

   "Minutes of IAOC meetings shall be published following their adoption
    by the IAOC, and in any event not later than 30 days after the meeting."

   "The IAD shall provide an Operations Report to the IAOC monthly, and to
    the ISOC Board as required; all such reports shall be published online.
    The report shall provide an update on the Budget, the performance of all
    contractors, and other relevant information as shall be decided."

   "Non-confidential agreements shall be posted upon execution. Public
    agreements include ICANN/IANA MoUs and SLAs."

   "When a contract contains confidential information, that information
    shall be summarized if possible to protect its confidentiality, or if not,
    extracted. The balance of the contract shall be published on the IASA
    website within 14 days of execution."

I do not have any specific questions.

Regards,
-sm 


From nabil.n.bitar@verizon.com  Tue Feb 12 07:25:10 2013
Return-Path: <nabil.n.bitar@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 144B021F8EEC; Tue, 12 Feb 2013 07:25:10 -0800 (PST)
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 ijZMG9l1EoQP; Tue, 12 Feb 2013 07:25:09 -0800 (PST)
Received: from fldsmtpe01.verizon.com (fldsmtpe01.verizon.com [140.108.26.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2021921F8EE3; Tue, 12 Feb 2013 07:25:09 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe01.verizon.com with ESMTP; 12 Feb 2013 14:53:14 +0000
From: "Bitar, Nabil N" <nabil.n.bitar@verizon.com>
X-IronPort-AV: E=Sophos;i="4.84,650,1355097600";  d="scan'208,217";a="413212070"
Received: from fldp1lumxc7hb03.verizon.com (HELO FLDP1LUMXC7HB03.us.one.verizon.com) ([166.68.75.86]) by fldsmtpi03.verizon.com with ESMTP; 12 Feb 2013 14:52:12 +0000
Received: from fldp1lumxc7v63.us.one.verizon.com ([169.254.3.33]) by FLDP1LUMXC7HB03.us.one.verizon.com ([166.68.75.86]) with mapi; Tue, 12 Feb 2013 09:52:12 -0500
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-ancp-pon.all@tools.ietf.org" <draft-ietf-ancp-pon.all@tools.ietf.org>
Date: Tue, 12 Feb 2013 09:52:07 -0500
Subject: Re: Gen-ART LC review of draft-ietf-ancp-pon-04
Thread-Topic: Gen-ART LC review of draft-ietf-ancp-pon-04
Thread-Index: Ac4JMIncWadkfIo5Qp609P3ZKd123A==
Message-ID: <CD3FC0F0.76E96%nabil.n.bitar@verizon.com>
In-Reply-To: <06da01ce08ec$a9fc9590$fdf5c0b0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.3.120616
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CD3FC0F076E96nabilnbitarverizoncom_"
MIME-Version: 1.0
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 15:25:10 -0000

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

Hi Roni,
Thanks. Will do the edit you pointed out.

Thanks,
Nbail

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Tuesday, February 12, 2013 1:46 AM
To: "draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-ancp-pon.all@=
tools.ietf.org>" <draft-ietf-ancp-pon.all@tools.ietf.org<mailto:draft-ietf-=
ancp-pon.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-ancp-pon-04
Resent-To: <droms@bucknell.edu<mailto:droms@bucknell.edu>>, <matthew.bocci@=
alcatel-lucent.com<mailto:matthew.bocci@alcatel-lucent.com>>, "<, nabil.n.b=
itar@verizon.com<mailto:nabil.n.bitar@verizon.com>>", <sanjay.wadhwa@alcate=
l-lucent.com<mailto:sanjay.wadhwa@alcatel-lucent.com>>, <wdec@cisco.com<mai=
lto:wdec@cisco.com>>

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-ancp-pon-04

Reviewer: Roni Even

Review Date:2013=962=9612

IETF LC End Date: 2013-2=9619

IESG Telechat date:



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





Major issues:



Minor issues:




Nits/editorial comments:

 1.  OMCI is expanded very late in the document and not on the first usage.


--_000_CD3FC0F076E96nabilnbitarverizoncom_
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(0, 0, 0); font-size: 14p=
x; font-family: Calibri, sans-serif; "><div>Hi Roni,</div><div>Thanks. Will=
 do the edit you pointed out.</div><div><br></div><div>Thanks,</div><div>Nb=
ail</div><div><br></div><span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"fon=
t-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTT=
OM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEF=
T: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: me=
dium none; PADDING-TOP: 3pt"><span style=3D"font-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:bold">Date: </span> Tuesday, Feb=
ruary 12, 2013 1:46 AM<br><span style=3D"font-weight:bold">To: </span> &quo=
t;<a href=3D"mailto:draft-ietf-ancp-pon.all@tools.ietf.org">draft-ietf-ancp=
-pon.all@tools.ietf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-ancp-pon=
.all@tools.ietf.org">draft-ietf-ancp-pon.all@tools.ietf.org</a>&gt;<br><spa=
n style=3D"font-weight:bold">Cc: </span> &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=
><span style=3D"font-weight:bold">Subject: </span> Gen-ART LC review of dra=
ft-ietf-ancp-pon-04<br><span style=3D"font-weight:bold">Resent-To: </span> =
&lt;<a href=3D"mailto:droms@bucknell.edu">droms@bucknell.edu</a>&gt;, &lt;<=
a href=3D"mailto:matthew.bocci@alcatel-lucent.com">matthew.bocci@alcatel-lu=
cent.com</a>&gt;, &quot;&lt;, <a href=3D"mailto:nabil.n.bitar@verizon.com">=
nabil.n.bitar@verizon.com</a>&gt;&quot;, &lt;<a href=3D"mailto:sanjay.wadhw=
a@alcatel-lucent.com">sanjay.wadhwa@alcatel-lucent.com</a>&gt;, &lt;<a href=
=3D"mailto:wdec@cisco.com">wdec@cisco.com</a>&gt;<br></div><div><br></div><=
div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micros=
oft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xm=
lns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://=
www.w3.org/TR/REC-html40"><meta name=3D"Generator" content=3D"Microsoft Wor=
d 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;}
@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:296448786;
	mso-list-type:hybrid;
	mso-list-template-ids:1423221754 67698703 67698713 67698715 67698703 67698=
713 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]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal"><a name=3D"O=
LE_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 hre=
f=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_bl=
ank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p><=
/o:p></p><p class=3D"MsoNormal">Please resolve these comments along with an=
y other Last Call comments you may receive.<o:p></o:p></p><p class=3D"MsoPl=
ainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Document:
</span><span style=3D"font-family: 'Courier New', serif; ">draft-ietf-ancp-=
pon-04<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-s=
ize: 11pt; font-family: Calibri, sans-serif; ">Reviewer: 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:2013=962=9612<o:p></o:p></span>=
</p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; ">IETF LC End Date: 2013-2=9619<o:p></o:p></span></p><=
p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calib=
ri, sans-serif; ">IESG Telechat date:
<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 1=
1pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p cla=
ss=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, s=
ans-serif; ">Summary: This draft is ready for publication as an Information=
al RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; ">.<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"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Cal=
ibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><=
span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Major is=
sues:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-si=
ze: 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: Calib=
ri, sans-serif; ">Minor issues:<o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><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=
: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p =
class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p><ol style=3D"mar=
gin-top:0in" start=3D"1" type=3D"1"><li class=3D"MsoNormal" style=3D"mso-li=
st:l0 level1 lfo1">OMCI is expanded very late in the document and not on th=
e first usage.<o:p></o:p></li></ol><p class=3D"MsoNormal"><o:p>&nbsp;</o:p>=
</p></div></div></div></span></body></html>

--_000_CD3FC0F076E96nabilnbitarverizoncom_--

From dhc@dcrocker.net  Tue Feb 12 09:05:42 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678E221F8FB7 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 09:05:42 -0800 (PST)
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 FxklwrHHDshl for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 09:05:41 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2E35421F8FB6 for <ietf@ietf.org>; Tue, 12 Feb 2013 09:05:41 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r1CH5ehv010174 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Tue, 12 Feb 2013 09:05:40 -0800
Message-ID: <511A7663.1000408@dcrocker.net>
Date: Tue, 12 Feb 2013 09:05:39 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Remote Participation Services
References: <CC6E5D3D-A7B6-4C73-8FE8-2B2CD8015304@ietf.org> <51199813.8060208@network-heretics.com> <18073.1360638304@sandelman.ca>
In-Reply-To: <18073.1360638304@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 12 Feb 2013 09:05:40 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 17:05:42 -0000

On 2/11/2013 7:05 PM, Michael Richardson wrote:
> It's not the slides that are the problem.
> It's the "presentation" itself.


+1.


If a meeting has good structure, management and content, the presence or 
absence of slides doesn't matter.

If a meeting has poor structure, management or content, the presence or 
absence of slides doesn't matter.

Focus on the substance, not the form.  Slides are form.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From chair@ietf.org  Tue Feb 12 10:45:14 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3789F21F908D for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 10:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 WjbTTFtoLecc for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 10:45:13 -0800 (PST)
Received: from mail.amsl.com (unknown [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id A869C21F9089 for <ietf@ietf.org>; Tue, 12 Feb 2013 10:45:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A3055124260 for <ietf@ietf.org>; Tue, 12 Feb 2013 10:45:13 -0800 (PST)
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 UVQHBn3S6Rb3 for <ietf@ietf.org>; Tue, 12 Feb 2013 10:45:13 -0800 (PST)
Received: from [64.170.98.199] (unknown [64.170.98.199]) by c8a.amsl.com (Postfix) with ESMTPSA id 89D0B12425F for <ietf@ietf.org>; Tue, 12 Feb 2013 10:45:13 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: One Week Left To Nominate YOUR Choice for the Internet Hall Of Fame!
Date: Tue, 12 Feb 2013 13:45:13 -0500
Message-Id: <90FCA8C1-365C-4DA1-9B8A-8ED1FD56F1E1@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: Tue, 12 Feb 2013 18:45:14 -0000

A reminder that the deadline for the Internet Hall of Fame nominations =
is 18 February 2013. Individuals who have played a significant role in =
the conceptualization, building, and development of the Internet in any =
region or country are considered for induction.  Please take this =
opportunity to participate; your involvement will result in a highly =
diverse and well-qualified group of nominees! =20

More details and the nomination form are available here: =
http://www.internethalloffame.org/nominations

Thanks for all you do for the Internet,
  Russ


From narten@us.ibm.com  Tue Feb 12 12:56:04 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2605B21F8B66 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 12:56:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08FP9fEWrRPw for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 12:56:03 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 68FAB21F8B64 for <ietf@ietf.org>; Tue, 12 Feb 2013 12:56:03 -0800 (PST)
Received: from /spool/local by e7.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Tue, 12 Feb 2013 15:55:57 -0500
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 12 Feb 2013 15:15:48 -0500
Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 58695D10840; Tue, 12 Feb 2013 12:38:48 -0500 (EST)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r1CHclAC313038; Tue, 12 Feb 2013 12:38:48 -0500
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 r1CHf5Bs027791; Tue, 12 Feb 2013 10:41:06 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-239-200.mts.ibm.com [9.65.239.200]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id r1CHexP0027001 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Feb 2013 10:41:01 -0700
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id r1CHcWbD019578; Tue, 12 Feb 2013 12:38:32 -0500
Message-Id: <201302121738.r1CHcWbD019578@cichlid.raleigh.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
In-reply-to: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com>
Comments: In-reply-to The IESG <iesg-secretary@ietf.org> message dated "Fri, 11 Jan 2013 11:36:16 -0800."
Date: Tue, 12 Feb 2013 12:38:32 -0500
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13021220-5806-0000-0000-00001F8B02BA
Cc: opsawg@ietf.org, draft-ietf-opsawg-oam-overview@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, 12 Feb 2013 20:56:04 -0000

I agree with many of the comments that others have raised on this
thread. Just a couple of things to add that I don't recall seeing
mentioned.

   An OAM protocol is run in the context of a Maintenance Domain,
   consisting of two or more nodes that run the OAM protocol, referred
   to as Maintenance Points (MP).

This defintion could be better. I assume an MD is really more like a
"region", that is a collection of nodes within which (or across which)
some OAM function is run. You might run, e.g., a ping. While that ping
may be between to MPs, it also involves other nodes (MIs). But MIs seem
to be excluded per the above.

   o Continuity Checking (CC):
      Used for verifying the liveness of a connection between two MPs.

What is "liveness" and what is "connection"?  Please define these
terms or point to the defintions in other documents. (I have looked
and have not found a precise definition.)

Note: later in document:

   Continuity checks are used to verify the liveness of a connection or
   a path between two MPs, and are typically sent proactively, though
   they can be invoked on-demand as well.

Here "path" and "connection" are used interchangably.   

   o Connectivity Verification (CV):
      Allows an MP to check whether it is connected to a peer MP, and to
      verify that messages from the peer MP are received through the
      expected path.

what is "connected to a peer"? Does that mean "there is a working
path?" Or something else?

   o Path Discovery / Fault Localization:
      An MP uses this mechanism to trace the route to a peer MP, i.e.,

s/the route/the path/ ???

      to identify the nodes along the path to the peer MP. When a
      connection fails, this mechanism also allows the MP to detect the
      location of the failure.

   o Performance Monitoring:
      Consists of 3 main functions

        o Loss Measurement (LM) - monitors the packet loss rate of a
          connection.

what is "connection" in the context of technologies like TRILL (or IP
for that matter)?, which do hop-by-hop forwarding and/or may do load
balancing via ECMP?

   o "Ping" mode: In this mode LSP ping is used for end-to-end
      connectivity verification between two LERs.

What's an LER?

Thomas


From ulrich@herberg.name  Tue Feb 12 13:59:03 2013
Return-Path: <ulrich@herberg.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E0121F8BA6 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 13:59:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.829
X-Spam-Level: 
X-Spam-Status: No, score=-2.829 tagged_above=-999 required=5 tests=[AWL=0.148,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vZ8RaBR7sH0 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 13:59:02 -0800 (PST)
Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEEE21F8B88 for <ietf@ietf.org>; Tue, 12 Feb 2013 13:59:02 -0800 (PST)
Received: by mail-ve0-f171.google.com with SMTP id b10so546973vea.2 for <ietf@ietf.org>; Tue, 12 Feb 2013 13:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herberg.name; s=dkim; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Z3kxZwMSKye5uXO0PfMruCDVXLqVnDOtt7LNyRqm4Ng=; b=umGaE1yW5LErewJYW3Q8nhVLjgBOwNqQt+IuU/lEF6ZT+7WHQOszkW88MdtbO+4aEl 9PuCguo/NdQGZMC7l4SJgLlVdQxBXDffS/WCJqaz7ITnWL13R5776kBGq8BhwChxybTu naJ31NNwVD77UPEFFgJvcBxBmPjeDM3LYTuQY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=Z3kxZwMSKye5uXO0PfMruCDVXLqVnDOtt7LNyRqm4Ng=; b=I9mqQVIR87Q68AjFlcPP6E/IZ+pHXGPYQDxmiURQZpjy6HIjRZJdh1WU+kyceHvQN8 iYSoNq4U1DlV9ZL6Bc+Y5ArMEovqRMcSdEa0EFejvuR1nSk4TXoL073pBuOM3jmE/oyq wodUBOUK6Ievpf4kyM643LYWBcdjkUY5zgljPnp/6mEIPfaGfGtMdabiiq0+eSl2aHJL /vP6TJJyWUkHJemiY+WufmfwqbCCGVK6HrGz0rHlSU5zb1OIHwASSbTPPP5EzMyaglLj 0AnsMehtaXMnccCqSRcFVU63DgzGe9jm5TmCn7DpYAEgFX75AenaBIYy6eSZfYWI8hjB uUXw==
MIME-Version: 1.0
X-Received: by 10.58.233.210 with SMTP id ty18mr25980088vec.46.1360706341815;  Tue, 12 Feb 2013 13:59:01 -0800 (PST)
Received: by 10.220.195.67 with HTTP; Tue, 12 Feb 2013 13:59:01 -0800 (PST)
In-Reply-To: <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com>
Date: Tue, 12 Feb 2013 13:59:01 -0800
Message-ID: <CAK=bVC-A9HgfTEv=f-7ATk2iCwNqNmAmCzom61WEy0LhLzD5Aw@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Ulrich Herberg <ulrich@herberg.name>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmBfPRS1rOPyGM7UQl0FWiX7VEkFJDW1FBtcz78Wp2cz5ojBk8DfEEPYqqKtPNVvaMnKmaZ
Cc: draft-cardenas-dff@tools.ietf.org, ietf@ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2013 21:59:03 -0000

AB,

thank you for the review. See my answer below:

On Sun, Feb 10, 2013 at 3:08 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
>
> Reply to your request dated 07/02/2013
> Also following AD advice.
> Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 10/02/2013
>
> Reviewer Comment #AB1: Related to Aim and Terminology.
> ++++++++++++++++++++++++++++++++++++
>
> Overall I support the work, but subject to amendments.
>
> The Abstract is interesting but seem general

Do you have any specific suggestions what you would like to add/change
in the abstract?



> >    This document specifies the "Depth-First Forwarding" (DFF) protocol
> >    for IPv6 networks,
>
> AB> do you mean all IPv6 networks, if some please mention *some*

I don't think this is relevant to add in the abstract. As stated in
section 3 of the draft, it can be used for all IPv6 networks, but for
some the protocol is not very beneficial (and examples are given for
such situations).


> >    a data forwarding mechanism that can increase
> >    reliability of data delivery in networks with dynamic topology and/or
> >    lossy links.
>
> AB> IPv6 considers dynamic topology, does the paragraph mean that some
> networks are static topology.

I am not quite sure what you mean by IPv6 "considers topology". In a
static topology (i.e. with no or very few changes of links) and with
low packet loss rate, the DFF protocol would have little (or no)
benefit, because most likely the packets would be sent from the source
to the destination according to the information provided by the
routing protocol, and no packets would be lost.



> Suggest to clarify the dynamic
> frequency.

I am not sure what you would like to see clarified. Can you be more specific?


> Also not clear what is missing with IPv6 protocol in such
> nets that needs DFF.

If you mean data forwarding, I think the draft is pretty clear about
which cases it is beneficial in. The motivation for DFF is explained
in section 1.1.


> >  The protocol operates entirely on the forwarding plane,
> >    but may interact with the routing plane.
>
> AB> amend> entirely on the forwarding plane,
>            to; entirely within the forwarding plane,

I am not a native English speaker, but "to operate on" seems a valid
usage of the word. But maybe a native speaker could suggest which is
the right usage.


>
> >    The routing plane may be informed of
> >    failures to deliver a packet or loops.
>
> AB> Amend> routing plane may be informed
>           to;   routing plane protocols may be informed

I think the current sentence is sufficient; I don't see the benefit of
adding the word "protocols".



> Terminology section>
>
> AB> you need to define that all routers have the DFF protocol, even
> though it is known by heart that any forwarder needs to run DFF but
> you MUST mention that at least to the reader,

I think this is actually a good point. I was wondering whether to
enforce all routers in a routing domain to run DFF. That does not seem
like a reasonable approach. I found only one case that could be a
problem when using both DFF and non-DFF routers in the network that
results in a loop, but I think I found an easy fix. Here is the
problem illustrated using an example:

...--- A ----- B ---- C --- ...

Assume routers A and C use DFF, but not B. When B receives a packet
from A, it would ignore the DFF header and skip over it, and then
forward the packet to C (assuming C is the next hop in its RIB). Now,
it is possible that C returns  the packet (RET==1) to B, e.g. because
it does not have any other neighbor. B receives the returned packet
and would resend the packet to C (because it does not care about the
DFF header), and thus RET would still be 1. C, having tried already
all neighbors would return the packet to B (and so on, loop between B
and C until hop-limit == 0).

I see the following options:
1) Change the options header type from something starting with 001
    (i.e. "skip over this option and continue processing the header.") to
    011 ("discard the packet.") in IPv6 to discard the packet if the
    header is unknown. This would avoid the problem, but I don't think
    that's possible for 6lowpan mesh-under.
2) Mandate that all routers in the routing domain "MUST use DFF" for
    forwarding packets.
3) Add a rule that if a packet is returned (RET==1) from P_prev_hop
    (i.e. the original previous hop when first received a packet), it is
    discarded, e.g. if router C receives a packet from B with RET==1 and B
    is the P_prev_hop.

Option 1) would be possible, but not for 6lowpans, only for IPv6
route-over. Option 2) is probably not very good. Option 3) would fix
the loop issue, and thus allows non-DFF and DFF routers in the same
network. I will provide some updated text in the next revision of the
draft.



>
> AB> you missed to define the Router, which is mentioned many times but
> I don't know which one. I think it is a must because you refer to two
> planes forwarding and routing planes. Please define the Forwarder as
> well. I don't find any Forwarder action in the draft, why not while
> you specify there is a forwarding plane!

I am undecided on defining the term "router". It is a well-known term
in IETF; but then, maybe one could define it like in RFC6130 ("Router
- A router running this protocol"). Not sure this conveys a lot of
information, though. So unless others also suggest adding it, I will
not change the terminology section.
Since I don't use the term "forwarder" (which is usually part of the
functions of a router), I don't think I should define that in the
terminology.


>
> AB> suggest that you explaine forwarding and routing in separate and
> show where they join relating to your protocol.

I think the concept of forwarding and routing plane is fairly well
understood in the IETF, so I don't think I should re-explain that in
the draft.

Best regards
Ulrich

From abdussalambaryun@gmail.com  Tue Feb 12 22:48:23 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3CB721F8A77 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 22:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.537
X-Spam-Level: 
X-Spam-Status: No, score=-3.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FTUPCkG7A7dX for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 22:48:23 -0800 (PST)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by ietfa.amsl.com (Postfix) with ESMTP id 85CF821F8A71 for <ietf@ietf.org>; Tue, 12 Feb 2013 22:48:22 -0800 (PST)
Received: by mail-wg0-f50.google.com with SMTP id es5so708719wgb.5 for <ietf@ietf.org>; Tue, 12 Feb 2013 22:48:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=cLYu+KpsdGxQe6yrGa8ZEaiGkp1iR8XGipsDQqGsD1E=; b=HgWDTksRR3e5wza3EtCbQUR++xar2N7y3JXmNTCVCK0sy2F++oZd5eYw8lWCMsCQ+c V0TzdJTntBL+S2nO3Q3rF2hYGD7kbT7ZuQ39hFciSX5Mk7JAnWnE7VvJJ//6tLYNb0pB TbANYg58BPRcgnVWRK6vQcEe0RCMzwgMWOGJVfaMf2JxaQD3QrbbaEfpmPvtd4NlXIXX fiOeGhME9bCw0eFxl/97YmlRBAXWvsiucbSrYs83Vs9xPvWVuTtJejZ8nqjVx+9Axw5f /j7dC0aQ3bvl/SQqu8wxZSDMh2Ks6psA47dhFAHCDEh7KoExegtmXKINJTONC4xolSKo qipw==
MIME-Version: 1.0
X-Received: by 10.180.83.10 with SMTP id m10mr7768396wiy.5.1360738101508; Tue, 12 Feb 2013 22:48:21 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Tue, 12 Feb 2013 22:48:21 -0800 (PST)
Date: Wed, 13 Feb 2013 07:48:21 +0100
Message-ID: <CADnDZ88=thD_3=78rKO-uvd6fnYwWsg0n9dcgAM=SJpYUDVueA@mail.gmail.com>
Subject: IETF Participat Position
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: Donald.Eastlake@motorola.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, 13 Feb 2013 06:48:24 -0000

Hi folks

The IESG has evaluation process positions as DISCUSS and others, which
is part of examining the I-D before making a decision. IMO also IETF
participants have positions which may name process positions (includes
the WG-chairs and IESG members' positions, because they are also
IETF-participants), I think this message can be a good recommendation
point of view to add-to/update RFC4144,

I agree that after submission of the I-D to IESG by the authors or WG,
the reviewer SHOULD NOT discuss with the authors after his review only
if the reviewer is a user of the I-D. We can define the reviewer is in
REVIEW position, and there is possibility of DISCUSS if he/she is a
user. On the other hand, I think the authors/WGs MUST reply to the
review, because they are in SUBMIT position, they reply to all
comments on the submitted I-D.

I beleive that at any time/place any participant may comment on any
document or input in IETF and may open discussion, but it helps if it
known where the participant poster stands. I remember that once
related to one I-D a participant was commenting in WG and the author
misunderstood him and thought he was in object position but he was in
agree position, he just commented for the best.

Therefore, I may not reply to the below, for all the best reasons :)

AB
++

Sub: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First
Forwarding in Unreliable Networks (DFF)) to Experimental RFC
On 2/12/13, Ulrich Herberg <ulrich@herberg.name> wrote:
> AB,
>
> thank you for the review. See my answer below:
>
> On Sun, Feb 10, 2013 at 3:08 AM, Abdussalam Baryun
> <abdussalambaryun@gmail.com> wrote:
>>
>> Reply to your request dated 07/02/2013
>> Also following AD advice.
>> Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 10/02/2013
>>
>> Reviewer Comment #AB1: Related to Aim and Terminology.
>> ++++++++++++++++++++++++++++++++++++
>>
>> Overall I support the work, but subject to amendments.
>>
>> The Abstract is interesting but seem general
>
> Do you have any specific suggestions what you would like to add/change
> in the abstract?
>
>
>
>> >    This document specifies the "Depth-First Forwarding" (DFF) protocol
>> >    for IPv6 networks,
>>
>> AB> do you mean all IPv6 networks, if some please mention *some*
>
> I don't think this is relevant to add in the abstract. As stated in
> section 3 of the draft, it can be used for all IPv6 networks, but for
> some the protocol is not very beneficial (and examples are given for
> such situations).
>
>
>> >    a data forwarding mechanism that can increase
>> >    reliability of data delivery in networks with dynamic topology
>> > and/or
>> >    lossy links.
>>
>> AB> IPv6 considers dynamic topology, does the paragraph mean that some
>> networks are static topology.
>
> I am not quite sure what you mean by IPv6 "considers topology". In a
> static topology (i.e. with no or very few changes of links) and with
> low packet loss rate, the DFF protocol would have little (or no)
> benefit, because most likely the packets would be sent from the source
> to the destination according to the information provided by the
> routing protocol, and no packets would be lost.
>
>
>
>> Suggest to clarify the dynamic
>> frequency.
>
> I am not sure what you would like to see clarified. Can you be more
> specific?
>
>
>> Also not clear what is missing with IPv6 protocol in such
>> nets that needs DFF.
>
> If you mean data forwarding, I think the draft is pretty clear about
> which cases it is beneficial in. The motivation for DFF is explained
> in section 1.1.
>
>
>> >  The protocol operates entirely on the forwarding plane,
>> >    but may interact with the routing plane.
>>
>> AB> amend> entirely on the forwarding plane,
>>            to; entirely within the forwarding plane,
>
> I am not a native English speaker, but "to operate on" seems a valid
> usage of the word. But maybe a native speaker could suggest which is
> the right usage.
>
>
>>
>> >    The routing plane may be informed of
>> >    failures to deliver a packet or loops.
>>
>> AB> Amend> routing plane may be informed
>>           to;   routing plane protocols may be informed
>
> I think the current sentence is sufficient; I don't see the benefit of
> adding the word "protocols".
>
>
>
>> Terminology section>
>>
>> AB> you need to define that all routers have the DFF protocol, even
>> though it is known by heart that any forwarder needs to run DFF but
>> you MUST mention that at least to the reader,
>
> I think this is actually a good point. I was wondering whether to
> enforce all routers in a routing domain to run DFF. That does not seem
> like a reasonable approach. I found only one case that could be a
> problem when using both DFF and non-DFF routers in the network that
> results in a loop, but I think I found an easy fix. Here is the
> problem illustrated using an example:
>
> ...--- A ----- B ---- C --- ...
>
> Assume routers A and C use DFF, but not B. When B receives a packet
> from A, it would ignore the DFF header and skip over it, and then
> forward the packet to C (assuming C is the next hop in its RIB). Now,
> it is possible that C returns  the packet (RET==1) to B, e.g. because
> it does not have any other neighbor. B receives the returned packet
> and would resend the packet to C (because it does not care about the
> DFF header), and thus RET would still be 1. C, having tried already
> all neighbors would return the packet to B (and so on, loop between B
> and C until hop-limit == 0).
>
> I see the following options:
> 1) Change the options header type from something starting with 001
>     (i.e. "skip over this option and continue processing the header.") to
>     011 ("discard the packet.") in IPv6 to discard the packet if the
>     header is unknown. This would avoid the problem, but I don't think
>     that's possible for 6lowpan mesh-under.
> 2) Mandate that all routers in the routing domain "MUST use DFF" for
>     forwarding packets.
> 3) Add a rule that if a packet is returned (RET==1) from P_prev_hop
>     (i.e. the original previous hop when first received a packet), it is
>     discarded, e.g. if router C receives a packet from B with RET==1 and B
>     is the P_prev_hop.
>
> Option 1) would be possible, but not for 6lowpans, only for IPv6
> route-over. Option 2) is probably not very good. Option 3) would fix
> the loop issue, and thus allows non-DFF and DFF routers in the same
> network. I will provide some updated text in the next revision of the
> draft.
>
>
>
>>
>> AB> you missed to define the Router, which is mentioned many times but
>> I don't know which one. I think it is a must because you refer to two
>> planes forwarding and routing planes. Please define the Forwarder as
>> well. I don't find any Forwarder action in the draft, why not while
>> you specify there is a forwarding plane!
>
> I am undecided on defining the term "router". It is a well-known term
> in IETF; but then, maybe one could define it like in RFC6130 ("Router
> - A router running this protocol"). Not sure this conveys a lot of
> information, though. So unless others also suggest adding it, I will
> not change the terminology section.
> Since I don't use the term "forwarder" (which is usually part of the
> functions of a router), I don't think I should define that in the
> terminology.
>
>
>>
>> AB> suggest that you explaine forwarding and routing in separate and
>> show where they join relating to your protocol.
>
> I think the concept of forwarding and routing plane is fairly well
> understood in the IETF, so I don't think I should re-explain that in
> the draft.
>
> Best regards
> Ulrich
>

From sm@resistor.net  Wed Feb 13 04:35:50 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC33021F87E1; Wed, 13 Feb 2013 04:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=-0.091, BAYES_00=-2.599, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W8AsCbnnBEJ9; Wed, 13 Feb 2013 04:35:49 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DBF721F87CE; Wed, 13 Feb 2013 04:35:48 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1DCZY7C013397; Wed, 13 Feb 2013 04:35:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360758942; bh=FBdWTZANlyeRY/OzfyEDpHyX8iXnUprs5jYYhlPK8m0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Kto3uXKWxqVVjmi8sjRS83BBMCgdwPbF7YhbrZ7cwKua4o8nGb9txzxLYQbgpMYsn dKnKEPTZe292xjre60KZWGDQ5l75O4b6LEUaBvNMsiU3l5UEshumt2NjP73gYQo/Ic knu2Wdxy6y9UdChB9XZ0rSHORKB9Dwmy+rdCIYYg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360758942; i=@resistor.net; bh=FBdWTZANlyeRY/OzfyEDpHyX8iXnUprs5jYYhlPK8m0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dXT2UuQZWlQHdUFam5NxGAK7huevda0S/SUodw+uYpD8NoKw1DbWWwGpIxxWi8tMC Ov/x2F4U7DRHhqRu8yY6IytXT/Y9BuGJZfRkr2kST7Eoa9QqqFRUJZOczajay9kG9R x/0ec3uLWzBLhXD5b3wvUk83bmsQy7IZP0nXTxl8=
Message-Id: <6.2.5.6.2.20130213040129.09254bc0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 13 Feb 2013 04:33:39 -0800
To: Anthony Mancuso <amancuso@google.com>
From: SM <sm@resistor.net>
Subject: Re: [paws] Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
In-Reply-To: <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.g mail.com>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130204064015.09261fa0@resistor.net> <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: paws@ietf.org, Gabor Bajko <Gabor.Bajko@nokia.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, 13 Feb 2013 12:35:50 -0000

Hi Anthony,
At 17:00 12-02-2013, Anthony Mancuso wrote:
>In Section 1.1:
>
>   "Academia and Industry have studied multiple cognitive radio [2]
>    mechanisms for use in such a scenario."
>
>The reference seemed odd.  It took me some time to understand that 
>it was put in to address a comment.  However, the first (external) 
>reference that defines that is a 404.
>
>TODO(amancuso): fix link

Ok.

>I think the MUST below is one of the two boilerplate words you had a 
>comment on. Is there another?

See the section after the Abstract and Section 2.1.

>In response to earlier comments, this section was reworded and 
>"MUST" changed to "must". I assume this is what you were questioning.

Ok.

>----
>
>In Section 4.2:
>
>   "A simplified operation scenario of offloading content, such as video
>    stream, from the a metered Internet connection to the a WS connection
>    consists of the following steps:"
>
>What is a metered Internet connection?
>----
>Usage is monitored (metered) and paid for. I rephrased to clarify: 
>"more congested or costly Internet connection, such as a metered 
>(fee-based-on-usage) wire, wireless, or satellite service."

In my opinion you don't really have to get into all that.  I'll defer 
to the author.

>cleaned up protocol and operational requirements in response to 
>earlier comments. This is a good example of a use case, but didn't 
>fit comfortably as a P or O requirement, and was deleted from 
>requirements sections.

Ok.

>White Space Database (used to be defined in terminology). Changed it 
>simply to "database".

Ok.

>This is a rather large container of worms. We kicked it around for 
>about a half-hour and concluded that since this doc is for the 
>Internet Engineering Task Force, most readers will understand (and 
>forgive). Nonetheless, this is a good point, so I generalized it as 
>follows (while retaining the commonly used (and loosely-understood) 
>term: "The database and the master device MUST be connected (e.g., 
>through the Internet)."

I agree about that container. :-)  The draft is trying to convince me 
that white space is better for the Internet connection (see my 
previous comment about metered).  The requirements is about a 
protocol to Access Spectrum Database.  IP connectivity is a 
lower-layer issue.  I am ok with the above text.


>This section only intends to state the general requirement. It is my 
>understanding that the current draft of the protocol specification 
>specifies JSON encoding of location parameters that is compatible with GEOPRIV.

Ok.

Regards,
-sm 


From amancuso@google.com  Tue Feb 12 17:00:15 2013
Return-Path: <amancuso@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E008321F8964 for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 17:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.249
X-Spam-Level: 
X-Spam-Status: No, score=-100.249 tagged_above=-999 required=5 tests=[AWL=-1.766, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56nTXGknrz4Q for <ietf@ietfa.amsl.com>; Tue, 12 Feb 2013 17:00:09 -0800 (PST)
Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by ietfa.amsl.com (Postfix) with ESMTP id CC6DC21F8960 for <ietf@ietf.org>; Tue, 12 Feb 2013 17:00:08 -0800 (PST)
Received: by mail-lb0-f174.google.com with SMTP id l12so565229lbo.33 for <ietf@ietf.org>; Tue, 12 Feb 2013 17:00:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ok2wjQIYhTjAlcbaA1Dc1iWo2pDs4yACcnXXpnDqmbY=; b=iM6U9zI14hBWm2TAYNzu21DyL76d8F6zUit0dQdja2rDruvEx6TlfJwsx+Sc1+NPhE 11B48/UPZj2gMcKgTYydWBF1beEEpgD2an+roRbaGgPh7x/0dZEhKiJP9NJtm2N9j5LU D93voPDPaCfKOkbwvgl4RdgOPTQFPdTH3VtzMJ5DSB/s6LB7DPggRvqTnGWGvdVYCYkL Na3q4NuNaGiGAcDiFC/fXnraLJS49NBGUtEVoUtDoGM2M1i6pZgqCjec/+ajGt+vut5Z Mdo3ocf4y8a3G4HcVqb4SloLrssUM+aJ8Rqli3sooO29UrBhGjuWmjxpDLBlW5vOaqQW +8Wg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=ok2wjQIYhTjAlcbaA1Dc1iWo2pDs4yACcnXXpnDqmbY=; b=NL+RLUbTShnsLQRirIei5+uqU9WT7zOA/iXXPLdbCxHOVlRrkQpLPVYO+4FBp9GvkR nQ1Ui2C1coboqfmfhUMwHv6agyFwwi+LVueH9ZkjXXsU+fZZ/ObEshh8TjTf4bPf8rR2 j9JNlUaH7ccVWFXbIXvjybMEVrLlFvmdU/GcWkXabIiHZ+YnBskp2racMtT9E+wQCWQT 7vm9DqZYBbQ93CzUV6EV1FFoNfoLQTQNB9+WBHnhE2QtsFlHxWn6woGi1RdKqZmlJa4Y +I7oLsLXqZCDeTmwDB1GVH/8nNRKtPSy5swiYiV7TxZtA2F4wEUcFp3Moarf/xivzOKW XZ1Q==
MIME-Version: 1.0
X-Received: by 10.152.122.100 with SMTP id lr4mr18440939lab.28.1360717207424;  Tue, 12 Feb 2013 17:00:07 -0800 (PST)
Received: by 10.152.102.178 with HTTP; Tue, 12 Feb 2013 17:00:07 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130204064015.09261fa0@resistor.net>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130204064015.09261fa0@resistor.net>
Date: Tue, 12 Feb 2013 17:00:07 -0800
Message-ID: <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.gmail.com>
Subject: Re: [paws] Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
From: Anthony Mancuso <amancuso@google.com>
To: SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>,  Gabor Bajko <Gabor.Bajko@nokia.com>
Content-Type: multipart/alternative; boundary=f46d042ef661c9d0a904d590a9c6
X-Gm-Message-State: ALoCoQl5N7I0/8FUKv8gpDSI0fFgpW8B6rt4bRNDmavBzgB3CMVTqs9T77AqytaaloEmG5lap7ZKSEZ+fi8zz966P4NnlzIgb7gpt7bQ35/Buuxr7xY6pDlksj3+zkalUys1mUaYpPMVtSI9c7YhYVOA6ii4a/rCkw4fi4jPrhdb8/ZFnEmADkPTQcPpZ2srq8dVf7jmwget
X-Mailman-Approved-At: Wed, 13 Feb 2013 10:13:26 -0800
Cc: "paws@ietf.org" <paws@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, 13 Feb 2013 01:00:16 -0000

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

IESG members (and PAWS list),

Below are the Last Call comments and my responses, which I am using to
generate v. 13 of the PAWS Use Cases & Requirements Draft. I expect to post
v. 13 soon, perhaps this Friday morning. Please follow up as soon as you
can with any further comments.

I list Pete Resnick's and Peter Stanforth's comments and my responses
first, followed by Barry Leila's, then SM's. Note: Some sections are
affected by multiple comments so you may need to read all the comments and
responses to a section to understand the final effect of all comments on a
section.

I apologize that some of the section references may be difficult to
coordinate with the last (and next) posted version of the doc since I did
some reorganizing (partially in response to these comments). I did my best
to show the new section numbers in my responses.

Thanks for all your comments. They greatly helped in clarifying this
material and tying it to an extensible protocol to access whitespace.

Tony Mancuso

*********************

Pete Resnick's comments:

Abstract

End of the first paragraph, perhaps add: "The IETF has undertaken to
develop a protocol for that management database."
___
Mancuso: For purposes of the abstract, I think this IETF doc speaks to the
our efforts to develop the protocol (but I added this sentence in the
Intro).
_____

Introduction

Added reference to the PAWS protocol to 1.1.

Please don't refer to the WG, either in the Abstract or in the Intro. First
of all, there ought to be no references in the Abstract anyway since the
Abstract is often displayed in announcements and other places without the
rest of the document. But more importantly, I don't think what you put in
flows very well. In the Abstract, just saying "protocol" is sufficient. In
the Intro, I'd suggest simply changing the last paragraph to:

   This document includes the problem statement for the development of a
   database query protocol to access a database of whitespace
   information followed by use cases and requirements for that protocol
   associated with the use of white space spectrum by secondary users.

-- Deleted reference in abstract. Changed last Intro paragraph as
suggested. Also moved the problem statement section up (as described in the
text, it should follow the Introduction and precede the Use Cases section.
Also moved the discussions of protocol services into the problem statement
(there were two db features mentioned and one (db discovery) was
duplicative of an existing section in the existing Problem Statement
section.
_____
Stanforth: Broadcast use case is a master with no slave, at least in the
context of a slave that communicates with or is controlled by a master.
_____
Resnick: So are you saying we do or do not need the term "master" in these
sections?
_____
Mancuso: I clarified the definition of master device: "A device that
queries a database, on its own behalf and/or on behalf of a slave device,
to obtain available spectrum information.". I think this definition plus
the definition of a slave device ("A device that queries the database
through a Master Device.") makes the use of the term in this and latter
sections and illustrations appropriate -- namely, a master device is one
that contacts a database to obtain spectrum (for itself or other devices).
Slave devices under these definitions, do not contact the db directly,
omitting them from the discussion and referring in the text or
illustrations solely to a master device makes sense, and is not dependent
on also referencing a slave device. Another way of saying it: we use the
term master only as a way of describing a device used to query the db
directly for spectrum availability. Denoting a device as master does not
necessarily imply the use of slaves (devices that are not used to query the
db directly) in a particular use case or illustration.

That's all fine, but then in the first sentence of 3.1, it says "A white
space radio network is created by a master device." That's not true, or at
least not necessarily true. The white space network is created by either
the master or the high-power slave. What defines something as a master is
not that it creates a white space radio network. A master is simply defined
as that which queries the database. So I suspect the word "master" in this
section is wrong and the first paragraph of 3.1 needs a bit more work to
remove all reference to creation of the whitespace network. Creating the
network is not part of the discovery phase at all.

-- This doc as originally written had a lot of extra wording (which we have
been working to prune and clarify). This section is an example of such
extra wording that needs trimming. I simplified this section to limit the
discussion to discovery. However, I still wonder why you say that a
high-power slave can establish a white-space network since, by our
definition, it can't query the database for available white space spectrum.
I think perhaps you are referring to a high-power portable device acting as
a master device, but I'm not sure.

3.2: Similar questions regarding regulatory domains. For example, "2.  To
register with the database, the master device sends the database the
registration information required under regulatory rules." How does the
device determine which regulatory rules it is under and therefore which
information to send to the database. If the answer is, "It queries the
database", then it is not the regulatory rules the device cares about; it
is the information the database is configured to ask for (which will
presumably be in accordance to some regulations, but are out of band of any
protocol work). If the answer is, "It is pre-configured in the device",
then the regulatory rules are again out of band. Either way, mention of
them would be unnecessary.
___
Mancuso: Agreed. I think this was simply a matter of misphrasing. Deleted
the extra language to read: "To register with the database, the master
device sends registration information to the database.

There are still several references in 3.2 to "regulatory domain" and
"regulatory requirement" that I think are unnecessary and confusing and
should be removed.

-- Removed references to regulatory domain and simplified the steps to
eliminate unnecessary discussion of regulatory requirements.


4.2: This scenario was confusing to me because the master seems completely
unnecessary to the example. Please explain.
_____
Mancuso: As noted, the master is optionally used by the slave to query the
db for spectrum. And again, master only connotes the device's ability to
query the db directly.

OK, this section still does not make sense to me. The slave is getting
whitespace in this scenario. But in the diagram, the slave doesn't have the
antenna; the master does. That doesn't jibe with the rest of the example.
If it's the slave that wants to move away from its metered service and use
whitespace, then it should have the antenna. If the slave wants to talk to
an AP that's going to use the whitespace, there should be a box for the AP
in the diagram. If you want to say that the master and the AP can be one
device, still show two boxes but say they can be in the same box. If the
master is doing the querying and setting up the whitespace and the "slave"
is doing nothing with regard to whitespace but simply using the master as
an Internet gateway, then the "slave" is not a slave.

-- Yes, the slave needs an antenna. I think the terms "master" and "slave"
(as we define them) were muddying the illustration. I changed the
illustration and text to clarify that the portable device here is using
white space to offload video streaming from a metered Internet service to
an unmetered AP Internet service (the portable device talks to the AP over
whitespace).


5.1, item 1: Is this referring to the Internet connectivity between the WS
device and the database? If so, as above, does it necessarily need to be an
air interface?
___
Mancuso: This wasn't meant to imply air the exclusive interface -- Made
this clearer by using "any" air interface used by devices; further limited
reference to messages between devices and db as messages from master device
to db (since, by definition, slave devices don't communicate directly to
db).

You missed one bit of what I was asking: Couldn't the interface between the
database and the master be wired, not air at all?

--- Rephrased to be more explicit: "Interface agnostic - An interface
between a master white space device and database can be wired or unwired
(e.g., a radio/air interface technology such as IEEE 802.11af, IEEE
802.15.4m, IEEE 802.16, IEEE 802.22, LTE etc.) However, the messaging
interface between a master white space device and the database should be
agnostic to the interface used for such messaging while being cognizant of
the characteristics of the interface technology and the need to include any
relevant attributes in the query to the database."


Requirements:
_____
P.1: "The master device may validate the database against a list of
approved databases maintained by a regulatory body." I don't understand
that as a protocol requirement. What is being required?
___
Mancuso: (Moved info up from Operation requirements per later comment).
Rephrased to clarify that the master device MUST identify a db, and MAY
discover or be pre-configured with db URIs, and MAY validate db URIs
against a list of approved databases maintained by a regulatory body."

I don't think I explained my question well enough. So let me try it this
way. Here's what you currently have:

   P.1  The master device MUST identify a database to which it can

      register, make spectrum availability requests, etc.

That's not the requirement. Here you're just describing what the master is
going to do. So MUST isn't needed here. "will" is probably sufficient. Next
comes the requirement:

      The master
      device MAY select a database by discovery at run time or by means

      of a pre-programmed URI address.

That's fine, but it doesn't make it clear that the discovery protocol is a
requirement. Shouldn't it say, "The protocol must support the discovery of
an appropriate database given a location provided by the master device. The
master device may select a database..."?

      The master device MAY validate
      discovered or configured database addresses against a list of

      approved databases maintained by a regulatory body.

Here's my original confusion. I think this would be better as, "The master
device may validate discovered or configured database addresses against a
list of known databases (e.g., a list of databases approved by a regulatory
body)." That is, the requirement (and it's not a protocol requirement) is
that the master will have the ability to (optionally) do the validation
against a list. Where that list comes from, e.g., a regulatory body, is not
part of the requirement.

-- Made the suggested wording changes.


O.2: The "required accuracy" is ambiguous. Do you mean, "accuracy required
by the database"?
_____
Stanforth: Acceptable Location Accuracy is defined by the regulator and
applied to the calculations of the database
_____
Resnick: So the database will tell the device what level of accuracy is
required?
_____
Mancuso: Clarified as follows: "Locations MUST be determined to the
accuracy required by the applicable regulatory domain." These are
operational requirements, and not part of the protocol. Accuracy is
verified by certification of devices by regulators.

Oh, I think that made it worse. If the regulators are determining the
accuracy and certifying the devices, this is not an operational
requirement; it's all going to be pre-configured. Is that what you mean?

-- Restated to: "A master device MUST be able to determine its location
including uncertainty and confidence level. A fixed master device MAY use a
location programmed at installation or be configured to determine its
location to the accuracy required by the applicable regulatory domain."
These seems like a valid operational requirement for devices that use the
protocol.


O.4: Again, "regulatory body" seems unnecessary here. Substituting
"database" seems sufficient, since you'll be getting the rule set from the
database.
_____
Stanforth: General observation about this and the next couple of comments.
The FCC Certifies a radio and a database as a "system" OFCOMis not
considering a system. Other regulators may have other thoughts. In the case
of the FCC some of the function is validated/certified, what ever you want
to call it for the combination not as a function of one or the other.
So while it seems logical to have an implementation within a database it is
not necessarily considered as such.
_____
Resnick: Again, I'm not understand your reply. Can you expand on what you
mean here?
_____
Mancuso: The statement here is regarding the rule set, which is from the
regulator, so the current phrasing seems OK.

I think we are talking past each other: How does the master device
determine the rule set? Is it getting it from the database? Is it
pre-configured? In any event, does the master device know that the rule set
came from the regulator? If not, then there's no need to mention the
regulator at all.

-- The best I could do here, given the range of responses a db may
communicate to a device regarding a rule set (the name of the rule set, a
more detailed list of all parameters in a rule set, etc.) is "The master
device MUST be configured to understand the requirements of the rule set of
the regulatory body that apply to its operation at its location."


Note there are a significant number of device-only rule-set requirements
(complexity is to be expected), so the operational requirement here is for
the master to obtain "information." The current expectation is that the db
may communicate the name of the applicable regulatory rule set to the
device, but not the specific parameters.

But the master device is only dealing with the name of the rule set. It
doesn't have semantics to the master device. The master device DOES NOT
CARE that the rule set came from a regulator, or the manufacturer, or from
invaders from Mars. The concept of the regulator is irrelevant to the
operational requirement.

-- Yes, but humans (perhaps invading Martians, someday?) will read this doc
--- the qualification to the rule set described here "rule set of the
regulatory body" is only meant to explain what rule set we are talking
about. Just mentioning "rule set" seems incomplete and ambiguous.
_____

O.5 (and O.9 through O.10 and O.12 through O.14): As above, you can change
"local regul8atory policy" to "the database rule set", "determined by
regulator policy" can be "enumerated in the database rule set", etc.
____
Mancuso: A db can serve multiple regulatory domains, and hence, rule sets.
And note that the currently applicable rule set may not come from a local
regulatory domain, but be imported from a foreign regulator (e.g., Brazil
decides to use FCC rules)
_____

Security Considerations

Section 8, generally: Same issue with "regulatory". See if there are any
that are more accurately "database rules".
____
Mancuso: Again, multiple rule sets may apply for a given regulatory domain.

See above.

I agree with the request to pare down the references to regulatory domain.
Further, a lot of the "requirements" in this section either are not
requirements, strictly speaking, or restated protocol requirements. Hence,
I pared down this section significantly to state as simply as possible what
a device and db must minimally do to operate in white space.

****************

Barry Leila's comments:

Some Last Call comments, in advance of IESG Evaluation:

-- General --

It's completely a non-starter that there's no email address for
Anthony Mancuso; this has to be added.  He won't get any of the IESG
Evaluation messages this way, and the RFC Editor won't be able to
contact him during the publication process.

___
Fixed this. Added email and other author (editor) information.
_________

The first and third references need to be in RFC reference form, and
not simply as URIs.  They should look something like this:

[1] V. Chen, S. Das, Z. Lei, J. Malyar, P. McCann, "Protocol to
Access Spectrum Database", draft-ietf-paws-protocol-01 (work in
progress), December 2012

[3] National Imagery and Mapping Agency, "Department of Defense
World Geodetic System 1984, Its Definition and Relationships with
Local Geodetic Systems", NIMA TR8350.2 Third Edition Amendment 1,
January 2000,
<http://earth-info.nga.mil/GandG/publications/tr8350.2/tr8350_2.html>

For the second reference: the RFC Editor will not generally accept
Wikipedia as a reference, because its contents are unstable.  Perhaps
you could use something like <http://fcc.gov/oet/cognitiveradio/>
instead?
____
TODO(amancuso): I'm working on these cites. I am still figuring out how to
do this in xxe.
I'll return to this after I respond to all the other last call comments.
-----

Just an alert: the RFC Editor will probably add hyphens when "white
space" is used as an adjective, as in "white-space spectrum".  This is
particularly notable when you have "non-white space spectrum", which
looks like space that is non-white (as opposed to "non-white-space
spectrum").  You may feel free to wait for them to do that.  Or you
can do it.
-----
added hyphens to "white-space" and "non-white-space" throughout.
-----

Abstract

Abstracts should not contain citations, so the "[1]" citation should
be removed.  But perhaps more to the point, the Abstract is too long;
the first paragraph can be trimmed after the second sentence (clipping
everything beginning with "An obvious requirement", which doesn't need
to be in the abstract (but should be and is in the Introduction)).
-----
Removed cite. Trimmed down the abstract.
____


-- Section 1.1 --

The first paragraph seems overlong, and could do with splitting.
Perhaps start a new paragraph with "An obvious requirement", and then
another with "Academia and industry".
-----
Done.
_____

-- Section 3.1 -- (old section 3 moved into new section 3 subsections)

It looks like a lot of stuff in these earlier sections used to have
2119 language, and got Peted.  You missed one: the "MUST" in the
second sentence should be "must".

---
Done.
_____

-- Section 3.2 --

Does Figure 1 actually show anything useful or interesting?  It says
it illustrates a registration requirement, but I don't see it.
-----
Agreed. Deleted figure and renumbered successive figures.
____

I'd say that "most current and up-to-date information" is redundant
(this also shows up in 6.3).  And anyway, step 1 isn't a step -- you
don't *do* anything there.
-----
N/A. Refers to deleted language.
-----


-- Section 4.1 --

   Figure 2 (Figure 2) depicts the general architecture such a simple
   master-slave network

You're missing an "of".  And is there a reason for "Figure 2 (Figure
2)" (and with other figures) that I don't understand?
----
fixed "of"; Deleted extra figure names throughout.
-----

Bullet 3: There is no Section 4.1.1 to see.

Bullet 4: It's not really optional (which implies that it's at the
option of the master).  It's required if the database requires it, but
not all databases require it.  Can you re-word?  (And there is no
Section 4.1.2, either.)

----
Subsection numbering was changed in last iterations of the doc.

Clarification: the db doesn't require registration -- the rules set of the
regulatory domain that applies to the device may. The db may notify the
device of the rule set name that applies to it. To avoid listing protocol
requirements here, though, I generalized the language differently, and
simply said that the device "may" register. This section is not meant to
define the required protocol steps, just common ones in a communication
exchange between the device and the db.

Bullet 5: The part beginning "Note that" is out of place here, but
that's OK, because it's repeated where it belongs, in bullet 6.  I
suggest you just remove it from here.
----
Removed the redundant part covered in item 6 but kept the part that
mentions that a item 5 (spectrum availability request) may be made by the
master on behalf of a slave device.

-- Section 5 (now Section 3)--

   The databases may be regulatory specific
   since the available spectrum and regulations may vary, but the
   fundamental operation of the protocol should be regulatory
   independent.

Is "should be" appropriate?  I should think "has to be".
-----
I rephrased to clarify the point trying be made here in relation to the
regulatory agnostic protocol steps: "While databases are expected to
support the rule set(s) of one or more regulatory domains, and the
regulations and available spectrum associated with each rule set may vary,
the fundamental operation of the protocol should be regulatory independent."

   In Figure 11, note that there could be multiple databases serving
   white space devices.

There is no Figure 11.  You mean 7?
-----
fixed figure numbering
-----

   The databases are locale specific since the
   regulations and available spectrum may vary.

I think you mean "location-specific"; in the App world "locale" has a
particular meaning that I don't think you mean (in other words, this
is not an issue of local language).  This applies to the use of
"locale" elsewhere in the document as well.
----
Deleted this sentence since it was peripheral to the main point about
multiple dbs. But I do agree that "locale" is an overloaded term, and
"location" is more appropriate. I changed "locale" to "location" throughout.

-- Section 5.1 --

Bullet 1 says "Radio/air interface agnostic", but seems to be talking
about the messaging between the master and the DB, which will not
necessarily be over an air interface.  Please re-word this bullet,
being careful to make the distinction between white-space usage (which
will of course be over the air) and DB access (which could be over any
network interface).
----
this language was updated in response to earlier comments, and now makes it
clear that master-db connection nor constrained to air interfaces.
-----

Bullet 3 confuses me.  First it says that it's possible for the device
to know what rules are applicable, because it knows its location.
Then it says to note that even though it knows its location, it may
not be able to know what rule set to use.  Is that not contradictory,
or am I misunderstanding?  Then it gives an important requirement
that's buried at the end.

I suggest putting the requirement earlier, and then following it with
the extended explanation of the need for it.
----
deleted extra wording that clouded the main (and general) point that the
protocol must support the communication of domain-specific rule set
information to devices: "To allow the global use of white space devices in
different countries (whatever the regulatory domain), the protocol should
support the database communicating applicable regulatory rule set
information to the white space device.."

-- Section 5.2 --

   The device needs to
   determine the location of the specific database to which it can send
   queries in addition to registering itself for operation and using the
   available spectrum.

I'm having a lot of trouble parsing this sentence, and I'm still not
sure I understand what it means.  Can you try rephrasing it?
--
reworded (and renumbered) section 3.2 limits the discussion to db discovery
and explains the steps that can be taken to do this.
-----

-- Section 6.1 -- (new section 5)

         The Data Model MUST support WGS84 (see NGA: DoD World Geodetic
         System 1984 [3]).

I think this statement makes that reference normative.
----
I think you mean the cite should be to an RFC.
TODO(amancuso): Update the cite.

      D.3  The Data Model MUST support device description data that
         identifies a device (serial number, certification IDs, etc.)
         and describes device characteristics, such as or device class
         (fixed, mobile, portable, indoor, outdoor, etc.), Radio Access
         Technology (RAT), etc.

Is the "or" in there a stray, or is there something else wrong?
-----
deleted stray "or"
-----

-- Section 6.2 --

   P.9  The protocol MUST support an available spectrum request from the
      master device to the database.  These parameters MAY include any
      of the parameters and attributes required to be supported in the
      Data Model Requirements.

"These parameters" implies that you've mentioned parameters before,
but you haven't.  What parameters?  (Same comment for P.10 and P.11.)
----
the parameters referred to here are those listed as required data items in
the preceding data model section. I reworded to clarify, as follows: "The
protocol MUST support an available spectrum request from the  master device
to the database, which may include one or more of the data items listed in
[xref to Data Model section]."

Added the same trailing clause to p. 10 & 11.
-----

-- Section 6.3 --

   O.5  The master device MAY register with the database according to
      local regulatory policy.

As above: this is not a correct use of MAY, because it's not at the
option of the master device.  In fact, as you say later in this
requirement, it MUST register when it's required to.  Please re-word
this.

  (O.6)
      Parameters provided to the database
      MAY include device location, accuracy of the location

Again... are these parameters provided purely at the option of the
requestor (in which case "MAY" is fine), or are they provided because
they're required by the database (in which case "MAY" is not right)?

   O.8  According to local regulator policy, a master device MAY inform
      the database of the actual frequency usage

   O.10  According to local regulatory policy, the master device MAY
      query the database with parameters received from the slave device.

More of the same about the "MAY".

---
entire section reorganized and simplified in response t earlier comments to
eliminate material duplicative of protocol requirements and to delete
unnecessary references to regulatory domains.
----

-- Section 8 -- (now Section 7)

         It is assumed that both the master device and the white space
         database have NOT been compromised from a security standpoint.

      Threat 1: User modifies a device to masquerade as another valid
      certified device

Here's how I read these two adjacent paragraphs: (1) It is assumed
that the device is not compromised; (2) Threat 1: A user compromises
the device.

Am I completely misunderstanding?  (I also find the explanation below
that to be convoluted.  Can you work on it, and try to un-convolute
it?)
---
I reorganized the sentences to make the basic point the attackers can
eavesdrop on communication channels between master device and db. I deleted
the confusing statement that seemed to claim that the network was
uncompromisable.

         A master device MAY
         need to identify itself to the database and be authorized to
         obtain information about available spectrum.

Totally wrong "MAY"; make it "might".  Remember that "MAY" means that
something is entirely optional.  "MAY need to" is pretty much always
wrong.
---
Simplified the wording to make the basic point that device id information
can be captured and reused by an attacker. Removed "permissive" wording.
_____

Threat 4:
         The available spectrum
         information or transmit power allowed type of parameters
         carried in the response could be modified by the attacker
         resulting in the master device using spectrum that is not
         available at a location or transmitting at a greater power
         level than allowed resulting in interference to the primary
         user of that spectrum.

That's quite a sentence.  Please unravel it and re-word.
-----
rephrased
-----

Threat 6: Expand "MiM".
---
rephrased
-----

   The security requirements arising from the above threats are captured
   in the requirements of Section 6.1 (Section 6.1).

There's that duplication again: "Section 6.1 (Section 6.1)"

---
fixed xref
---
-- Section 9 --

This section is entirely unnecessary, and you should remove it.
There's no need to repeat what you've already said.

-----
Agreed. Deleted section
-----

*****************

SM's comments:

I read the draft.  I am okay with whatever the working group decides.

In Section 1.1:

  "Academia and Industry have studied multiple cognitive radio [2]
   mechanisms for use in such a scenario."

The reference seemed odd.  It took me some time to understand that it was
put in to address a comment.  However, the first (external) reference that
defines that is a 404.

TODO(amancuso): fix link

There are two occurrences of the RFC 2119 boilerplate in the draft.

-----
I think the MUST below is one of the two boilerplate words you had a
comment on. Is there another?
-----

In Section 3.1: (new 3.2)

  "Before the master device can transmit in white space spectrum, it MUST
   obtain the address of a trusted white space database, which it will
   query for available white space spectrum."

Why is this a MUST?
---
In response to earlier comments, this section was reworded and "MUST"
changed to "must". I assume this is what you were questioning.
----

In Section 4.2:

  "A simplified operation scenario of offloading content, such as video
   stream, from the a metered Internet connection to the a WS connection
   consists of the following steps:"

What is a metered Internet connection?
----
Usage is monitored (metered) and paid for. I rephrased to clarify: "more
congested or costly Internet connection, such as a metered
(fee-based-on-usage) wire, wireless, or satellite service."


In Section 4.4:

  "To set up a replacement network, spectrum needs to be quickly
   cleared and reallocated to the crisis response organization."

Is that what P.15 is about?  BTW, O.17 uses a "should" for this.
---
cleaned up protocol and operational requirements in response to earlier
comments. This is a good example of a use case, but didn't fit comfortably
as a P or O requirement, and was deleted from requirements sections.

In Section 6.2: (Section 6 is now Section 5)

  "P.3  The protocol MUST provide the ability for the database to
     authenticate the master device."

  "P.5  The messages sent by the master device to the database and the
      messages sent by the database to the master device MUST support
      integrity protection."

  "P.6  The protocol MUST provide the capability for messages sent by
      the master device and database to be encrypted."

This sounds like the usual IETF security stuff.
-----
The protocol requirements were written to tie in with the primary PAWS
messages that are needed.
-----

  "P.8  The protocol MUST support a registration acknowledgement
      indicating the success of failure of the master device
      registration."

The "success of failure" might need fixing.
---
changed to "success or failure"
----

  "P.14  The protocol MUST support a validation response from the
      database to the master to indicate if the slave device is
      validated by the WSDB.  The validation response MUST indicate the
      success or failure of the validation request."

What is WSDB?
---
White Space Database (used to be defined in terminology). Changed it simply
to "database".

In Section 6.3: (entire section simplified in response to other comments)

  "O.1  The database and the master device MUST be connected to the
      Internet."

What is the Internet?
----
This is a rather large container of worms. We kicked it around for about a
half-hour and concluded that since this doc is for the Internet Engineering
Task Force, most readers will understand (and forgive). Nonetheless, this
is a good point, so I generalized it as follows (while retaining the
commonly used (and loosely-understood) term: "The database and the master
device MUST be connected (e.g., through the Internet)."

  "O.2  A master device MUST be able to determine its location including
      uncertainty and confidence level."

Does the working group plan to build its deliverables upon the GEOPRIV
work?
----
This section only intends to state the general requirement. It is my
understanding that the current draft of the protocol specification
specifies JSON encoding of location parameters that is compatible with
GEOPRIV.
---

I found the draft easy to read.  The draft goes into extraneous details in
some parts.  As an off-topic comment I see that the working group had the
usual JSON versus XML discussion [1]. :-)  I understood the concept of
white spaces as discussed in the draft.  If I understood correctly the
usage of database is related to the data model in Section 6.  On seeing
Figure 7 it seemed to me that what was missing is an architecture document
which provides a high-level view of how all this is supposed to work.  I am
not suggesting a reorganization of the draft as it may end up as too much
work.  The draft attempts to convince the reader about the importance of
white spaces and its use cases.  It's basically about database queries.

----
The use cases, the focus of this doc, attempt to show the high-level
architecture and provide a description of typical (and simplified) white
space master/slave networks and their relationship to the white space
database. Database queries are a critical and necessary step in
establishing a white space network (i.e., to obtain an available spectrum
list).
--------------

Regards,
-sm

***************************

end of Last Call comments.




On Mon, Feb 4, 2013 at 9:18 AM, SM <sm@resistor.net> wrote:

> At 05:24 01-02-2013, The IESG wrote:
>
>> The IESG has received a request from the Protocol to Access WS database
>> WG (paws) to consider the following document:
>> - 'Protocol to Access White Space (PAWS) Database: Use Cases and
>>    Requirements'
>>   <draft-ietf-paws-problem-stmt-**usecases-rqmts-12.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 2013-02-15. Exceptionally, comments may be
>>
>
> I read the draft.  I am okay with whatever the working group decides.
>
> In Section 1.1:
>
>   "Academia and Industry have studied multiple cognitive radio [2]
>    mechanisms for use in such a scenario."
>
> The reference seemed odd.  It took me some time to understand that it was
> put in to address a comment.  However, the first (external) reference that
> defines that is a 404.
>
> There are two occurrences of the RFC 2119 boilerplate in the draft.
>
> In Section 3.1:
>
>   "Before the master device can transmit in white space spectrum, it MUST
>    obtain the address of a trusted white space database, which it will
>    query for available white space spectrum."
>
> Why is this a MUST?
>
> In Section 4.2:
>
>   "A simplified operation scenario of offloading content, such as video
>    stream, from the a metered Internet connection to the a WS connection
>    consists of the following steps:"
>
> What is a metered Internet connection?
>
> In Section 4.4:
>
>   "To set up a replacement network, spectrum needs to be quickly
>    cleared and reallocated to the crisis response organization."
>
> Is that what P.15 is about?  BTW, O.17 uses a "should" for this.
>
> In Section 6.2:
>
>   "P.3  The protocol MUST provide the ability for the database to
>      authenticate the master device."
>
>   "P.5  The messages sent by the master device to the database and the
>       messages sent by the database to the master device MUST support
>       integrity protection."
>
>   "P.6  The protocol MUST provide the capability for messages sent by
>       the master device and database to be encrypted."
>
> This sounds like the usual IETF security stuff.
>
>   "P.8  The protocol MUST support a registration acknowledgement
>       indicating the success of failure of the master device
>       registration."
>
> The "success of failure" might need fixing.
>
>   "P.14  The protocol MUST support a validation response from the
>       database to the master to indicate if the slave device is
>       validated by the WSDB.  The validation response MUST indicate the
>       success or failure of the validation request."
>
> What is WSDB?
>
> In Section 6.3:
>
>   "O.1  The database and the master device MUST be connected to the
>       Internet."
>
> What is the Internet?
>
>   "O.2  A master device MUST be able to determine its location including
>       uncertainty and confidence level."
>
> Does the working group plan to build its deliverables upon the GEOPRIV
> work?
>
> I found the draft easy to read.  The draft goes into extraneous details in
> some parts.  As an off-topic comment I see that the working group had the
> usual JSON versus XML discussion [1]. :-)  I understood the concept of
> white spaces as discussed in the draft.  If I understood correctly the
> usage of database is related to the data model in Section 6.  On seeing
> Figure 7 it seemed to me that what was missing is an architecture document
> which provides a high-level view of how all this is supposed to work.  I am
> not suggesting a reorganization of the draft as it may end up as too much
> work.  The draft attempts to convince the reader about the importance of
> white spaces and its use cases.  It's basically about database queries.
>
> Regards,
> -sm
>
> 1. http://www.ietf.org/mail-**archive/web/apps-discuss/**
> current/msg07261.html<http://www.ietf.org/mail-archive/web/apps-discuss/current/msg07261.html>
>
> ______________________________**_________________
> paws mailing list
> paws@ietf.org
> https://www.ietf.org/mailman/**listinfo/paws<https://www.ietf.org/mailman/listinfo/paws>
>

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

<div dir=3D"ltr"><div>IESG members (and PAWS list),</div><div><br></div><di=
v>Below are the Last Call comments and my responses, which I am using to ge=
nerate v. 13 of the PAWS Use Cases &amp; Requirements Draft. I expect to po=
st v. 13 soon, perhaps this Friday morning. Please follow up as soon as you=
 can with any further comments.</div>

<div><br></div><div>I list Pete Resnick&#39;s and Peter Stanforth&#39;s com=
ments and my responses first, followed by Barry Leila&#39;s, then SM&#39;s.=
 Note: Some sections are affected by multiple comments so you may need to r=
ead all the comments and responses to a section to understand the final eff=
ect of all comments on a section.=A0</div>
<div><br></div><div>I apologize that some of the section references may be =
difficult to coordinate with the last (and next) posted version of the doc =
since I did some reorganizing (partially in response to these comments). I =
did my best to show the new section numbers in my responses.</div>

<div><br></div><div>Thanks for all your comments. They greatly helped in cl=
arifying this material and tying it to an extensible protocol to access whi=
tespace.</div><div><br></div><div>Tony Mancuso</div><div><br></div><div>
*********************</div>
<div><br></div><div>Pete Resnick&#39;s comments:</div><div><br></div><div>A=
bstract</div><div><br></div><div>End of the first paragraph, perhaps add: &=
quot;The IETF has undertaken to develop a protocol for that management data=
base.&quot;</div>

<div>___</div><div>Mancuso: For purposes of the abstract, I think this IETF=
 doc speaks to the our efforts to develop the protocol (but I added this se=
ntence in the Intro).</div><div>_____</div><div><br></div><div>Introduction=
</div>

<div><br></div><div>Added reference to the PAWS protocol to 1.1.</div><div>=
<br></div><div>Please don&#39;t refer to the WG, either in the Abstract or =
in the Intro. First of all, there ought to be no references in the Abstract=
 anyway since the Abstract is often displayed in announcements and other pl=
aces without the rest of the document. But more importantly, I don&#39;t th=
ink what you put in flows very well. In the Abstract, just saying &quot;pro=
tocol&quot; is sufficient. In the Intro, I&#39;d suggest simply changing th=
e last paragraph to:</div>

<div><br></div><div>=A0 =A0This document includes the problem statement for=
 the development of a</div><div>=A0 =A0database query protocol to access a =
database of whitespace</div><div>=A0 =A0information followed by use cases a=
nd requirements for that protocol</div>

<div>=A0 =A0associated with the use of white space spectrum by secondary us=
ers.</div><div><br></div><div>-- Deleted reference in abstract. Changed las=
t Intro paragraph as suggested. Also moved the problem statement section up=
 (as described in the text, it should follow the Introduction and precede t=
he Use Cases section. Also moved the discussions of protocol services into =
the problem statement (there were two db features mentioned and one (db dis=
covery) was duplicative of an existing section in the existing Problem Stat=
ement section.</div>

<div>_____</div><div>Stanforth: Broadcast use case is a master with no slav=
e, at least in the context of a slave that communicates with or is controll=
ed by a master.</div><div>_____</div><div>Resnick: So are you saying we do =
or do not need the term &quot;master&quot; in these sections?</div>

<div>_____</div><div>Mancuso: I clarified the definition of master device: =
&quot;A device that queries a database, on its own behalf and/or on behalf =
of a slave device, to obtain available spectrum information.&quot;. I think=
 this definition plus the definition of a slave device (&quot;A device that=
 queries the database through a Master Device.&quot;) makes the use of the =
term in this and latter sections and illustrations appropriate -- namely, a=
 master device is one that contacts a database to obtain spectrum (for itse=
lf or other devices). Slave devices under these definitions, do not contact=
 the db directly, omitting them from the discussion and referring in the te=
xt or illustrations solely to a master device makes sense, and is not depen=
dent on also referencing a slave device. Another way of saying it: we use t=
he term master only as a way of describing a device used to query the db di=
rectly for spectrum availability. Denoting a device as master does not nece=
ssarily imply the use of slaves (devices that are not used to query the db =
directly) in a particular use case or illustration.</div>

<div><br></div><div>That&#39;s all fine, but then in the first sentence of =
3.1, it says &quot;A white space radio network is created by a master devic=
e.&quot; That&#39;s not true, or at least not necessarily true. The white s=
pace network is created by either the master or the high-power slave. What =
defines something as a master is not that it creates a white space radio ne=
twork. A master is simply defined as that which queries the database. So I =
suspect the word &quot;master&quot; in this section is wrong and the first =
paragraph of 3.1 needs a bit more work to remove all reference to creation =
of the whitespace network. Creating the network is not part of the discover=
y phase at all.</div>

<div><br></div><div>-- This doc as originally written had a lot of extra wo=
rding (which we have been working to prune and clarify). This section is an=
 example of such extra wording that needs trimming. I simplified this secti=
on to limit the discussion to discovery. However, I still wonder why you sa=
y that a high-power slave can establish a white-space network since, by our=
 definition, it can&#39;t query the database for available white space spec=
trum. I think perhaps you are referring to a high-power portable device act=
ing as a master device, but I&#39;m not sure.</div>

<div><br></div><div>3.2: Similar questions regarding regulatory domains. Fo=
r example, &quot;2. =A0To register with the database, the master device sen=
ds the database the registration information required under regulatory rule=
s.&quot; How does the device determine which regulatory rules it is under a=
nd therefore which information to send to the database. If the answer is, &=
quot;It queries the database&quot;, then it is not the regulatory rules the=
 device cares about; it is the information the database is configured to as=
k for (which will presumably be in accordance to some regulations, but are =
out of band of any protocol work). If the answer is, &quot;It is pre-config=
ured in the device&quot;, then the regulatory rules are again out of band. =
Either way, mention of them would be unnecessary.</div>

<div>___</div><div>Mancuso: Agreed. I think this was simply a matter of mis=
phrasing. Deleted the extra language to read: &quot;To register with the da=
tabase, the master device sends registration information to the database.</=
div>

<div><br></div><div>There are still several references in 3.2 to &quot;regu=
latory domain&quot; and &quot;regulatory requirement&quot; that I think are=
 unnecessary and confusing and should be removed.</div><div><br></div>
<div>
-- Removed references to regulatory domain and simplified the steps to elim=
inate unnecessary discussion of regulatory requirements.</div><div><br></di=
v><div><br></div><div>4.2: This scenario was confusing to me because the ma=
ster seems completely unnecessary to the example. Please explain.</div>

<div>_____</div><div>Mancuso: As noted, the master is optionally used by th=
e slave to query the db for spectrum. And again, master only connotes the d=
evice&#39;s ability to query the db directly.</div><div><br></div><div>

OK, this section still does not make sense to me. The slave is getting whit=
espace in this scenario. But in the diagram, the slave doesn&#39;t have the=
 antenna; the master does. That doesn&#39;t jibe with the rest of the examp=
le. If it&#39;s the slave that wants to move away from its metered service =
and use whitespace, then it should have the antenna. If the slave wants to =
talk to an AP that&#39;s going to use the whitespace, there should be a box=
 for the AP in the diagram. If you want to say that the master and the AP c=
an be one device, still show two boxes but say they can be in the same box.=
 If the master is doing the querying and setting up the whitespace and the =
&quot;slave&quot; is doing nothing with regard to whitespace but simply usi=
ng the master as an Internet gateway, then the &quot;slave&quot; is not a s=
lave.</div>

<div><br></div><div>-- Yes, the slave needs an antenna. I think the terms &=
quot;master&quot; and &quot;slave&quot; (as we define them) were muddying t=
he illustration. I changed the illustration and text to clarify that the po=
rtable device here is using white space to offload video streaming from a m=
etered Internet service to an unmetered AP Internet service (the portable d=
evice talks to the AP over whitespace).</div>

<div><br></div><div><br></div><div>5.1, item 1: Is this referring to the In=
ternet connectivity between the WS device and the database? If so, as above=
, does it necessarily need to be an air interface?</div><div>___</div>
<div>
Mancuso: This wasn&#39;t meant to imply air the exclusive interface -- Made=
 this clearer by using &quot;any&quot; air interface used by devices; furth=
er limited reference to messages between devices and db as messages from ma=
ster device to db (since, by definition, slave devices don&#39;t communicat=
e directly to db).</div>

<div><br></div><div>You missed one bit of what I was asking: Couldn&#39;t t=
he interface between the database and the master be wired, not air at all?<=
/div><div><br></div><div>--- Rephrased to be more explicit: &quot;Interface=
 agnostic - An interface between a master white space device and database c=
an be wired or unwired (e.g., a radio/air interface technology such as IEEE=
 802.11af, IEEE 802.15.4m, IEEE 802.16, IEEE 802.22, LTE etc.) However, the=
 messaging interface between a master white space device and the database s=
hould be agnostic to the interface used for such messaging while being cogn=
izant of the characteristics of the interface technology and the need to in=
clude any relevant attributes in the query to the database.&quot;</div>

<div><br></div><div><br></div><div>Requirements:</div><div>_____</div><div>=
P.1: &quot;The master device may validate the database against a list of ap=
proved databases maintained by a regulatory body.&quot; I don&#39;t underst=
and that as a protocol requirement. What is being required?</div>

<div>___</div><div>Mancuso: (Moved info up from Operation requirements per =
later comment). Rephrased to clarify that the master device MUST identify a=
 db, and MAY discover or be pre-configured with db URIs, and MAY validate d=
b URIs against a list of approved databases maintained by a regulatory body=
.&quot;</div>

<div><br></div><div>I don&#39;t think I explained my question well enough. =
So let me try it this way. Here&#39;s what you currently have:</div><div><b=
r></div><div>=A0 =A0P.1 =A0The master device MUST identify a database to wh=
ich it can</div>

<div><br></div><div>=A0 =A0 =A0 register, make spectrum availability reques=
ts, etc.</div><div><br></div><div>That&#39;s not the requirement. Here you&=
#39;re just describing what the master is going to do. So MUST isn&#39;t ne=
eded here. &quot;will&quot; is probably sufficient. Next comes the requirem=
ent:</div>

<div><br></div><div>=A0 =A0 =A0 The master</div><div>=A0 =A0 =A0 device MAY=
 select a database by discovery at run time or by means</div><div><br></div=
><div>=A0 =A0 =A0 of a pre-programmed URI address.</div><div><br></div><div=
>That&#39;s fine, but it doesn&#39;t make it clear that the discovery proto=
col is a requirement. Shouldn&#39;t it say, &quot;The protocol must support=
 the discovery of an appropriate database given a location provided by the =
master device. The master device may select a database...&quot;?</div>

<div><br></div><div>=A0 =A0 =A0 The master device MAY validate</div><div>=
=A0 =A0 =A0 discovered or configured database addresses against a list of</=
div><div><br></div><div>=A0 =A0 =A0 approved databases maintained by a regu=
latory body.</div>

<div><br></div><div>Here&#39;s my original confusion. I think this would be=
 better as, &quot;The master device may validate discovered or configured d=
atabase addresses against a list of known databases (e.g., a list of databa=
ses approved by a regulatory body).&quot; That is, the requirement (and it&=
#39;s not a protocol requirement) is that the master will have the ability =
to (optionally) do the validation against a list. Where that list comes fro=
m, e.g., a regulatory body, is not part of the requirement.</div>

<div><br></div><div>-- Made the suggested wording changes.</div><div><br></=
div><div><br></div><div>O.2: The &quot;required accuracy&quot; is ambiguous=
. Do you mean, &quot;accuracy required by the database&quot;?</div><div>

_____</div><div>Stanforth: Acceptable Location Accuracy is defined by the r=
egulator and applied to the calculations of the database</div><div>_____</d=
iv><div>Resnick: So the database will tell the device what level of accurac=
y is required?</div>

<div>_____</div><div>Mancuso: Clarified as follows: &quot;Locations MUST be=
 determined to the accuracy required by the applicable regulatory domain.&q=
uot; These are operational requirements, and not part of the protocol. Accu=
racy is verified by certification of devices by regulators.</div>

<div><br></div><div>Oh, I think that made it worse. If the regulators are d=
etermining the accuracy and certifying the devices, this is not an operatio=
nal requirement; it&#39;s all going to be pre-configured. Is that what you =
mean?</div>

<div><br></div><div>-- Restated to: &quot;A master device MUST be able to d=
etermine its location including uncertainty and confidence level. A fixed m=
aster device MAY use a location programmed at installation or be configured=
 to determine its location to the accuracy required by the applicable regul=
atory domain.&quot; These seems like a valid operational requirement for de=
vices that use the protocol.</div>

<div><br></div><div><br></div><div>O.4: Again, &quot;regulatory body&quot; =
seems unnecessary here. Substituting &quot;database&quot; seems sufficient,=
 since you&#39;ll be getting the rule set from the database.</div><div>

_____</div><div>Stanforth: General observation about this and the next coup=
le of comments. The FCC Certifies a radio and a database as a &quot;system&=
quot; OFCOMis not considering a system. Other regulators may have other tho=
ughts. In the case of the FCC some of the function is validated/certified, =
what ever you want to call it for the combination not as a function of one =
or the other.</div>

<div>So while it seems logical to have an implementation within a database =
it is not necessarily considered as such.</div><div>_____</div><div>Resnick=
: Again, I&#39;m not understand your reply. Can you expand on what you mean=
 here?</div>

<div>_____</div><div>Mancuso: The statement here is regarding the rule set,=
 which is from the regulator, so the current phrasing seems OK.</div><div><=
br></div><div>I think we are talking past each other: How does the master d=
evice determine the rule set? Is it getting it from the database? Is it pre=
-configured? In any event, does the master device know that the rule set ca=
me from the regulator? If not, then there&#39;s no need to mention the regu=
lator at all.</div>

<div><br></div><div>-- The best I could do here, given the range of respons=
es a db may communicate to a device regarding a rule set (the name of the r=
ule set, a more detailed list of all parameters in a rule set, etc.) is &qu=
ot;The master device MUST be configured to understand the requirements of t=
he rule set of the regulatory body that apply to its operation at its locat=
ion.&quot;</div>

<div><br></div><div><br></div><div>Note there are a significant number of d=
evice-only rule-set requirements (complexity is to be expected), so the ope=
rational requirement here is for the master to obtain &quot;information.&qu=
ot; The current expectation is that the db may communicate the name of the =
applicable regulatory rule set to the device, but not the specific paramete=
rs.</div>

<div><br></div><div>But the master device is only dealing with the name of =
the rule set. It doesn&#39;t have semantics to the master device. The maste=
r device DOES NOT CARE that the rule set came from a regulator, or the manu=
facturer, or from invaders from Mars. The concept of the regulator is irrel=
evant to the operational requirement.</div>

<div><br></div><div>-- Yes, but humans (perhaps invading Martians, someday?=
) will read this doc --- the qualification to the rule set described here &=
quot;rule set of the regulatory body&quot; is only meant to explain what ru=
le set we are talking about. Just mentioning &quot;rule set&quot; seems inc=
omplete and ambiguous.=A0</div>

<div>_____</div><div><br></div><div>O.5 (and O.9 through O.10 and O.12 thro=
ugh O.14): As above, you can change &quot;local regul8atory policy&quot; to=
 &quot;the database rule set&quot;, &quot;determined by regulator policy&qu=
ot; can be &quot;enumerated in the database rule set&quot;, etc.</div>

<div>____</div><div>Mancuso: A db can serve multiple regulatory domains, an=
d hence, rule sets. And note that the currently applicable rule set may not=
 come from a local regulatory domain, but be imported from a foreign regula=
tor (e.g., Brazil decides to use FCC rules)</div>

<div>_____</div><div><br></div><div>Security Considerations</div><div><br><=
/div><div>Section 8, generally: Same issue with &quot;regulatory&quot;. See=
 if there are any that are more accurately &quot;database rules&quot;.</div=
>

<div>____</div><div>Mancuso: Again, multiple rule sets may apply for a give=
n regulatory domain.</div><div><br></div><div>See above.</div><div><br></di=
v><div>I agree with the request to pare down the references to regulatory d=
omain. Further, a lot of the &quot;requirements&quot; in this section eithe=
r are not requirements, strictly speaking, or restated protocol requirement=
s. Hence, I pared down this section significantly to state as simply as pos=
sible what a device and db must minimally do to operate in white space.=A0<=
/div>

<div><br></div><div>****************</div><div><br></div><div>Barry Leila&#=
39;s comments:</div><div><br></div><div>Some Last Call comments, in advance=
 of IESG Evaluation:</div><div><br></div><div>-- General --</div><div>
<br>
</div><div>It&#39;s completely a non-starter that there&#39;s no email addr=
ess for</div><div>Anthony Mancuso; this has to be added. =A0He won&#39;t ge=
t any of the IESG</div><div>Evaluation messages this way, and the RFC Edito=
r won&#39;t be able to</div>

<div>contact him during the publication process.</div><div><br></div><div>_=
__</div><div>Fixed this. Added email and other author (editor) information.=
</div><div>_________</div><div><br></div><div>The first and third reference=
s need to be in RFC reference form, and</div>

<div>not simply as URIs. =A0They should look something like this:</div><div=
><br></div><div>[1] V. Chen, S. Das, Z. Lei, J. Malyar, P. McCann, &quot;Pr=
otocol to</div><div>Access Spectrum Database&quot;, draft-ietf-paws-protoco=
l-01 (work in</div>

<div>progress), December 2012</div><div><br></div><div>[3] National Imagery=
 and Mapping Agency, &quot;Department of Defense</div><div>World Geodetic S=
ystem 1984, Its Definition and Relationships with</div><div>Local Geodetic =
Systems&quot;, NIMA TR8350.2 Third Edition Amendment 1,</div>

<div>January 2000,</div><div>&lt;<a href=3D"http://earth-info.nga.mil/GandG=
/publications/tr8350.2/tr8350_2.html" target=3D"_blank">http://earth-info.n=
ga.mil/GandG/publications/tr8350.2/tr8350_2.html</a>&gt;</div><div><br></di=
v>
<div>For the second reference: the RFC Editor will not generally accept</di=
v>
<div>Wikipedia as a reference, because its contents are unstable. =A0Perhap=
s</div><div>you could use something like &lt;<a href=3D"http://fcc.gov/oet/=
cognitiveradio/" target=3D"_blank">http://fcc.gov/oet/cognitiveradio/</a>&g=
t;</div>
<div>instead?</div>
<div>____</div><div>TODO(amancuso): I&#39;m working on these cites. I am st=
ill figuring out how to do this in xxe.=A0</div><div>I&#39;ll return to thi=
s after I respond to all the other last call comments.</div><div>-----</div=
>

<div><br></div><div>Just an alert: the RFC Editor will probably add hyphens=
 when &quot;white</div><div>space&quot; is used as an adjective, as in &quo=
t;white-space spectrum&quot;. =A0This is</div><div>particularly notable whe=
n you have &quot;non-white space spectrum&quot;, which</div>

<div>looks like space that is non-white (as opposed to &quot;non-white-spac=
e</div><div>spectrum&quot;). =A0You may feel free to wait for them to do th=
at. =A0Or you</div><div>can do it.</div><div>-----</div><div>added hyphens =
to &quot;white-space&quot; and &quot;non-white-space&quot; throughout.</div=
>

<div>-----</div><div><br></div><div>Abstract</div><div><br></div><div>Abstr=
acts should not contain citations, so the &quot;[1]&quot; citation should</=
div><div>be removed. =A0But perhaps more to the point, the Abstract is too =
long;</div>

<div>the first paragraph can be trimmed after the second sentence (clipping=
</div><div>everything beginning with &quot;An obvious requirement&quot;, wh=
ich doesn&#39;t need</div><div>to be in the abstract (but should be and is =
in the Introduction)).</div>

<div>-----</div><div>Removed cite. Trimmed down the abstract.</div><div>___=
_</div><div><br></div><div><br></div><div>-- Section 1.1 --</div><div><br><=
/div><div>The first paragraph seems overlong, and could do with splitting.<=
/div>

<div>Perhaps start a new paragraph with &quot;An obvious requirement&quot;,=
 and then</div><div>another with &quot;Academia and industry&quot;.</div><d=
iv>-----</div><div>Done.</div><div>_____</div><div><br></div><div>-- Sectio=
n 3.1 -- (old section 3 moved into new section 3 subsections)</div>

<div><br></div><div>It looks like a lot of stuff in these earlier sections =
used to have</div><div>2119 language, and got Peted. =A0You missed one: the=
 &quot;MUST&quot; in the</div><div>second sentence should be &quot;must&quo=
t;.</div>

<div><br></div><div>---</div><div>Done.</div><div>_____</div><div><br></div=
><div>-- Section 3.2 --</div><div><br></div><div>Does Figure 1 actually sho=
w anything useful or interesting? =A0It says</div><div>it illustrates a reg=
istration requirement, but I don&#39;t see it.</div>

<div>-----</div><div>Agreed. Deleted figure and renumbered successive figur=
es.</div><div>____</div><div><br></div><div>I&#39;d say that &quot;most cur=
rent and up-to-date information&quot; is redundant</div><div>(this also sho=
ws up in 6.3). =A0And anyway, step 1 isn&#39;t a step -- you</div>

<div>don&#39;t *do* anything there.</div><div>-----</div><div>N/A. Refers t=
o deleted language.</div><div>-----</div><div><br></div><div><br></div><div=
>-- Section 4.1 --</div><div><br></div><div>=A0 =A0Figure 2 (Figure 2) depi=
cts the general architecture such a simple</div>

<div>=A0 =A0master-slave network</div><div><br></div><div>You&#39;re missin=
g an &quot;of&quot;. =A0And is there a reason for &quot;Figure 2 (Figure</d=
iv><div>2)&quot; (and with other figures) that I don&#39;t understand?</div=
>
<div>
----</div><div>fixed &quot;of&quot;; Deleted extra figure names throughout.=
</div><div>-----</div><div><br></div><div>Bullet 3: There is no Section 4.1=
.1 to see.</div><div><br></div><div>Bullet 4: It&#39;s not really optional =
(which implies that it&#39;s at the</div>

<div>option of the master). =A0It&#39;s required if the database requires i=
t, but</div><div>not all databases require it. =A0Can you re-word? =A0(And =
there is no</div><div>Section 4.1.2, either.)</div><div><br></div><div>----=
</div>

<div>Subsection numbering was changed in last iterations of the doc.</div><=
div><br></div><div>Clarification: the db doesn&#39;t require registration -=
- the rules set of the regulatory domain that applies to the device may. Th=
e db may notify the device of the rule set name that applies to it. To avoi=
d listing protocol requirements here, though, I generalized the language di=
fferently, and simply said that the device &quot;may&quot; register. This s=
ection is not meant to define the required protocol steps, just common ones=
 in a communication exchange between the device and the db.=A0</div>

<div><br></div><div>Bullet 5: The part beginning &quot;Note that&quot; is o=
ut of place here, but</div><div>that&#39;s OK, because it&#39;s repeated wh=
ere it belongs, in bullet 6. =A0I</div><div>suggest you just remove it from=
 here.</div>

<div>----</div><div>Removed the redundant part covered in item 6 but kept t=
he part that mentions that a item 5 (spectrum availability request) may be =
made by the master on behalf of a slave device.</div><div><br></div><div>

-- Section 5 (now Section 3)--</div><div><br></div><div>=A0 =A0The database=
s may be regulatory specific</div><div>=A0 =A0since the available spectrum =
and regulations may vary, but the</div><div>=A0 =A0fundamental operation of=
 the protocol should be regulatory</div>

<div>=A0 =A0independent.</div><div><br></div><div>Is &quot;should be&quot; =
appropriate? =A0I should think &quot;has to be&quot;.</div><div>-----</div>=
<div>I rephrased to clarify the point trying be made here in relation to th=
e regulatory agnostic protocol steps: &quot;While databases are expected to=
 support the rule set(s) of one or more regulatory domains, and the regulat=
ions and available spectrum associated with each rule set may vary, the fun=
damental operation of the protocol should be regulatory independent.&quot;<=
/div>

<div><br></div><div>=A0 =A0In Figure 11, note that there could be multiple =
databases serving</div><div>=A0 =A0white space devices.</div><div><br></div=
><div>There is no Figure 11. =A0You mean 7?</div><div>-----</div><div>fixed=
 figure numbering</div>

<div>-----</div><div><br></div><div>=A0 =A0The databases are locale specifi=
c since the</div><div>=A0 =A0regulations and available spectrum may vary.</=
div><div><br></div><div>I think you mean &quot;location-specific&quot;; in =
the App world &quot;locale&quot; has a</div>

<div>particular meaning that I don&#39;t think you mean (in other words, th=
is</div><div>is not an issue of local language). =A0This applies to the use=
 of</div><div>&quot;locale&quot; elsewhere in the document as well.</div>

<div>----</div><div>Deleted this sentence since it was peripheral to the ma=
in point about multiple dbs. But I do agree that &quot;locale&quot; is an o=
verloaded term, and &quot;location&quot; is more appropriate. I changed &qu=
ot;locale&quot; to &quot;location&quot; throughout.</div>

<div><br></div><div>-- Section 5.1 --</div><div><br></div><div>Bullet 1 say=
s &quot;Radio/air interface agnostic&quot;, but seems to be talking</div><d=
iv>about the messaging between the master and the DB, which will not</div>

<div>necessarily be over an air interface. =A0Please re-word this bullet,</=
div><div>being careful to make the distinction between white-space usage (w=
hich</div><div>will of course be over the air) and DB access (which could b=
e over any</div>

<div>network interface).</div><div>----</div><div>this language was updated=
 in response to earlier comments, and now makes it clear that master-db con=
nection nor constrained to air interfaces.</div><div>-----</div><div><br>

</div><div>Bullet 3 confuses me. =A0First it says that it&#39;s possible fo=
r the device</div><div>to know what rules are applicable, because it knows =
its location.</div><div>Then it says to note that even though it knows its =
location, it may</div>

<div>not be able to know what rule set to use. =A0Is that not contradictory=
,</div><div>or am I misunderstanding? =A0Then it gives an important require=
ment</div><div>that&#39;s buried at the end.</div><div><br></div><div>I sug=
gest putting the requirement earlier, and then following it with</div>

<div>the extended explanation of the need for it.</div><div>----</div><div>=
deleted extra wording that clouded the main (and general) point that the pr=
otocol must support the communication of domain-specific rule set informati=
on to devices: &quot;To allow the global use of white space devices in diff=
erent countries (whatever the regulatory domain), the protocol should suppo=
rt the database communicating applicable regulatory rule set information to=
 the white space device..&quot;</div>

<div><br></div><div>-- Section 5.2 --</div><div><br></div><div>=A0 =A0The d=
evice needs to</div><div>=A0 =A0determine the location of the specific data=
base to which it can send</div><div>=A0 =A0queries in addition to registeri=
ng itself for operation and using the</div>

<div>=A0 =A0available spectrum.</div><div><br></div><div>I&#39;m having a l=
ot of trouble parsing this sentence, and I&#39;m still not</div><div>sure I=
 understand what it means. =A0Can you try rephrasing it?</div><div>--</div>=
<div>

reworded (and renumbered) section 3.2 limits the discussion to db discovery=
 and explains the steps that can be taken to do this.</div><div>-----</div>=
<div><br></div><div>-- Section 6.1 -- (new section 5)</div><div><br></div>

<div>=A0 =A0 =A0 =A0 =A0The Data Model MUST support WGS84 (see NGA: DoD Wor=
ld Geodetic</div><div>=A0 =A0 =A0 =A0 =A0System 1984 [3]).</div><div><br></=
div><div>I think this statement makes that reference normative.</div><div>-=
---</div><div>I think you mean the cite should be to an RFC.</div>

<div>TODO(amancuso): Update the cite.</div><div><br></div><div>=A0 =A0 =A0 =
D.3 =A0The Data Model MUST support device description data that</div><div>=
=A0 =A0 =A0 =A0 =A0identifies a device (serial number, certification IDs, e=
tc.)</div><div>

=A0 =A0 =A0 =A0 =A0and describes device characteristics, such as or device =
class</div><div>=A0 =A0 =A0 =A0 =A0(fixed, mobile, portable, indoor, outdoo=
r, etc.), Radio Access</div><div>=A0 =A0 =A0 =A0 =A0Technology (RAT), etc.<=
/div><div><br></div><div>
Is the &quot;or&quot; in there a stray, or is there something else wrong?</=
div>
<div>-----</div><div>deleted stray &quot;or&quot;</div><div>-----</div><div=
><br></div><div>-- Section 6.2 --</div><div><br></div><div>=A0 =A0P.9 =A0Th=
e protocol MUST support an available spectrum request from the</div><div>=
=A0 =A0 =A0 master device to the database. =A0These parameters MAY include =
any</div>

<div>=A0 =A0 =A0 of the parameters and attributes required to be supported =
in the</div><div>=A0 =A0 =A0 Data Model Requirements.</div><div><br></div><=
div>&quot;These parameters&quot; implies that you&#39;ve mentioned paramete=
rs before,</div>

<div>but you haven&#39;t. =A0What parameters? =A0(Same comment for P.10 and=
 P.11.)</div><div>----</div><div>the parameters referred to here are those =
listed as required data items in the preceding data model section. I reword=
ed to clarify, as follows: &quot;The protocol MUST support an available spe=
ctrum request from the =A0master device to the database, which may include =
one or more of the data items listed in [xref to Data Model section].&quot;=
</div>

<div><br></div><div>Added the same trailing clause to p. 10 &amp; 11.</div>=
<div>-----</div><div><br></div><div>-- Section 6.3 --</div><div><br></div><=
div>=A0 =A0O.5 =A0The master device MAY register with the database accordin=
g to</div>

<div>=A0 =A0 =A0 local regulatory policy.</div><div><br></div><div>As above=
: this is not a correct use of MAY, because it&#39;s not at the</div><div>o=
ption of the master device. =A0In fact, as you say later in this</div><div>=
requirement, it MUST register when it&#39;s required to. =A0Please re-word<=
/div>

<div>this.</div><div><br></div><div>=A0 (O.6)</div><div>=A0 =A0 =A0 Paramet=
ers provided to the database</div><div>=A0 =A0 =A0 MAY include device locat=
ion, accuracy of the location</div><div><br></div><div>Again... are these p=
arameters provided purely at the option of the</div>

<div>requestor (in which case &quot;MAY&quot; is fine), or are they provide=
d because</div><div>they&#39;re required by the database (in which case &qu=
ot;MAY&quot; is not right)?</div><div><br></div><div>=A0 =A0O.8 =A0Accordin=
g to local regulator policy, a master device MAY inform</div>

<div>=A0 =A0 =A0 the database of the actual frequency usage</div><div><br><=
/div><div>=A0 =A0O.10 =A0According to local regulatory policy, the master d=
evice MAY</div><div>=A0 =A0 =A0 query the database with parameters received=
 from the slave device.</div>

<div><br></div><div>More of the same about the &quot;MAY&quot;.</div><div><=
br></div><div>---</div><div>entire section reorganized and simplified in re=
sponse t earlier comments to eliminate material duplicative of protocol req=
uirements and to delete unnecessary references to regulatory domains.</div>

<div>----</div><div><br></div><div>-- Section 8 -- (now Section 7)</div><di=
v><br></div><div>=A0 =A0 =A0 =A0 =A0It is assumed that both the master devi=
ce and the white space</div><div>=A0 =A0 =A0 =A0 =A0database have NOT been =
compromised from a security standpoint.</div>

<div><br></div><div>=A0 =A0 =A0 Threat 1: User modifies a device to masquer=
ade as another valid</div><div>=A0 =A0 =A0 certified device</div><div><br><=
/div><div>Here&#39;s how I read these two adjacent paragraphs: (1) It is as=
sumed</div>

<div>that the device is not compromised; (2) Threat 1: A user compromises</=
div><div>the device.</div><div><br></div><div>Am I completely misunderstand=
ing? =A0(I also find the explanation below</div><div>that to be convoluted.=
 =A0Can you work on it, and try to un-convolute</div>

<div>it?)</div><div>---</div><div>I reorganized the sentences to make the b=
asic point the attackers can eavesdrop on communication channels between ma=
ster device and db. I deleted the confusing statement that seemed to claim =
that the network was uncompromisable.</div>

<div><br></div><div>=A0 =A0 =A0 =A0 =A0A master device MAY</div><div>=A0 =
=A0 =A0 =A0 =A0need to identify itself to the database and be authorized to=
</div><div>=A0 =A0 =A0 =A0 =A0obtain information about available spectrum.<=
/div><div><br></div><div>Totally wrong &quot;MAY&quot;; make it &quot;might=
&quot;. =A0Remember that &quot;MAY&quot; means that</div>

<div>something is entirely optional. =A0&quot;MAY need to&quot; is pretty m=
uch always</div><div>wrong.</div><div>---</div><div>Simplified the wording =
to make the basic point that device id information can be captured and reus=
ed by an attacker. Removed &quot;permissive&quot; wording.</div>

<div>_____</div><div><br></div><div>Threat 4:</div><div>=A0 =A0 =A0 =A0 =A0=
The available spectrum</div><div>=A0 =A0 =A0 =A0 =A0information or transmit=
 power allowed type of parameters</div><div>=A0 =A0 =A0 =A0 =A0carried in t=
he response could be modified by the attacker</div>

<div>=A0 =A0 =A0 =A0 =A0resulting in the master device using spectrum that =
is not</div><div>=A0 =A0 =A0 =A0 =A0available at a location or transmitting=
 at a greater power</div><div>=A0 =A0 =A0 =A0 =A0level than allowed resulti=
ng in interference to the primary</div>

<div>=A0 =A0 =A0 =A0 =A0user of that spectrum.</div><div><br></div><div>Tha=
t&#39;s quite a sentence. =A0Please unravel it and re-word.</div><div>-----=
</div><div>rephrased</div><div>-----</div><div><br></div><div>Threat 6: Exp=
and &quot;MiM&quot;.</div>

<div>---</div><div>rephrased</div><div>-----</div><div><br></div><div>=A0 =
=A0The security requirements arising from the above threats are captured</d=
iv><div>=A0 =A0in the requirements of Section 6.1 (Section 6.1).</div><div>=
<br>
</div>
<div>There&#39;s that duplication again: &quot;Section 6.1 (Section 6.1)&qu=
ot;</div><div><br></div><div>---</div><div>fixed xref</div><div>---</div><d=
iv>-- Section 9 --</div><div><br></div><div>This section is entirely unnece=
ssary, and you should remove it.</div>

<div>There&#39;s no need to repeat what you&#39;ve already said.</div><div>=
<br></div><div>-----</div><div>Agreed. Deleted section</div><div>-----</div=
><div><br></div><div>*****************</div><div><br></div><div>SM&#39;s co=
mments:</div>

<div><br></div><div>I read the draft. =A0I am okay with whatever the workin=
g group decides.</div><div><br></div><div>In Section 1.1:</div><div><br></d=
iv><div>=A0 &quot;Academia and Industry have studied multiple cognitive rad=
io [2]</div>

<div>=A0 =A0mechanisms for use in such a scenario.&quot;</div><div><br></di=
v><div>The reference seemed odd. =A0It took me some time to understand that=
 it was put in to address a comment. =A0However, the first (external) refer=
ence that defines that is a 404.</div>

<div><br></div><div>TODO(amancuso): fix link</div><div><br></div><div>There=
 are two occurrences of the RFC 2119 boilerplate in the draft.</div><div><b=
r></div><div>-----</div><div>I think the MUST below is one of the two boile=
rplate words you had a comment on. Is there another?</div>

<div>-----</div><div><br></div><div>In Section 3.1: (new 3.2)</div><div><br=
></div><div>=A0 &quot;Before the master device can transmit in white space =
spectrum, it MUST</div><div>=A0 =A0obtain the address of a trusted white sp=
ace database, which it will</div>

<div>=A0 =A0query for available white space spectrum.&quot;</div><div><br><=
/div><div>Why is this a MUST?</div><div>---</div><div>In response to earlie=
r comments, this section was reworded and &quot;MUST&quot; changed to &quot=
;must&quot;. I assume this is what you were questioning.</div>

<div>----</div><div><br></div><div>In Section 4.2:</div><div><br></div><div=
>=A0 &quot;A simplified operation scenario of offloading content, such as v=
ideo</div><div>=A0 =A0stream, from the a metered Internet connection to the=
 a WS connection</div>

<div>=A0 =A0consists of the following steps:&quot;</div><div><br></div><div=
>What is a metered Internet connection?</div><div>----</div><div>Usage is m=
onitored (metered) and paid for. I rephrased to clarify: &quot;more congest=
ed or costly Internet connection, such as a metered (fee-based-on-usage) wi=
re, wireless, or satellite service.&quot;</div>

<div><br></div><div><br></div><div>In Section 4.4:</div><div><br></div><div=
>=A0 &quot;To set up a replacement network, spectrum needs to be quickly</d=
iv><div>=A0 =A0cleared and reallocated to the crisis response organization.=
&quot;</div>

<div><br></div><div>Is that what P.15 is about? =A0BTW, O.17 uses a &quot;s=
hould&quot; for this.</div><div>---</div><div>cleaned up protocol and opera=
tional requirements in response to earlier comments. This is a good example=
 of a use case, but didn&#39;t fit comfortably as a P or O requirement, and=
 was deleted from requirements sections.=A0</div>

<div><br></div><div>In Section 6.2: (Section 6 is now Section 5)</div><div>=
<br></div><div>=A0 &quot;P.3 =A0The protocol MUST provide the ability for t=
he database to</div><div>=A0 =A0 =A0authenticate the master device.&quot;</=
div><div>

<br></div><div>=A0 &quot;P.5 =A0The messages sent by the master device to t=
he database and the</div><div>=A0 =A0 =A0 messages sent by the database to =
the master device MUST support</div><div>=A0 =A0 =A0 integrity protection.&=
quot;</div>
<div>
<br></div><div>=A0 &quot;P.6 =A0The protocol MUST provide the capability fo=
r messages sent by</div><div>=A0 =A0 =A0 the master device and database to =
be encrypted.&quot;</div><div><br></div><div>This sounds like the usual IET=
F security stuff.</div>

<div>-----</div><div>The protocol requirements were written to tie in with =
the primary PAWS messages that are needed.</div><div>-----</div><div><br></=
div><div>=A0 &quot;P.8 =A0The protocol MUST support a registration acknowle=
dgement</div>

<div>=A0 =A0 =A0 indicating the success of failure of the master device</di=
v><div>=A0 =A0 =A0 registration.&quot;</div><div><br></div><div>The &quot;s=
uccess of failure&quot; might need fixing.</div><div>---</div><div>changed =
to &quot;success or failure&quot;</div>

<div>----</div><div><br></div><div>=A0 &quot;P.14 =A0The protocol MUST supp=
ort a validation response from the</div><div>=A0 =A0 =A0 database to the ma=
ster to indicate if the slave device is</div><div>=A0 =A0 =A0 validated by =
the WSDB. =A0The validation response MUST indicate the</div>

<div>=A0 =A0 =A0 success or failure of the validation request.&quot;</div><=
div><br></div><div>What is WSDB?</div><div>---</div><div>White Space Databa=
se (used to be defined in terminology). Changed it simply to &quot;database=
&quot;.</div>

<div><br></div><div>In Section 6.3: (entire section simplified in response =
to other comments)</div><div><br></div><div>=A0 &quot;O.1 =A0The database a=
nd the master device MUST be connected to the</div><div>=A0 =A0 =A0 Interne=
t.&quot;</div>

<div><br></div><div>What is the Internet?</div><div>----</div><div>This is =
a rather large container of worms. We kicked it around for about a half-hou=
r and concluded that since this doc is for the Internet Engineering Task Fo=
rce, most readers will understand (and forgive). Nonetheless, this is a goo=
d point, so I generalized it as follows (while retaining the commonly used =
(and loosely-understood) term: &quot;The database and the master device MUS=
T be connected (e.g., through the Internet).&quot;</div>

<div><br></div><div>=A0 &quot;O.2 =A0A master device MUST be able to determ=
ine its location including</div><div>=A0 =A0 =A0 uncertainty and confidence=
 level.&quot;</div><div><br></div><div>Does the working group plan to build=
 its deliverables upon the GEOPRIV work?=A0</div>

<div>----</div><div>This section only intends to state the general requirem=
ent. It is my understanding that the current draft of the protocol specific=
ation specifies JSON encoding of location parameters that is compatible wit=
h GEOPRIV.</div>

<div>---</div><div><br></div><div>I found the draft easy to read. =A0The dr=
aft goes into extraneous details in some parts. =A0As an off-topic comment =
I see that the working group had the usual JSON versus XML discussion [1]. =
:-) =A0I understood the concept of white spaces as discussed in the draft. =
=A0If I understood correctly the usage of database is related to the data m=
odel in Section 6. =A0On seeing Figure 7 it seemed to me that what was miss=
ing is an architecture document which provides a high-level view of how all=
 this is supposed to work. =A0I am not suggesting a reorganization of the d=
raft as it may end up as too much work. =A0The draft attempts to convince t=
he reader about the importance of white spaces and its use cases. =A0It&#39=
;s basically about database queries.</div>

<div><br></div><div>----</div><div>The use cases, the focus of this doc, at=
tempt to show the high-level architecture and provide a description of typi=
cal (and simplified) white space master/slave networks and their relationsh=
ip to the white space database. Database queries are a critical and necessa=
ry step in establishing a white space network (i.e., to obtain an available=
 spectrum list).</div>

<div>--------------</div><div><br></div><div>Regards,</div><div>-sm</div><d=
iv><br></div><div>***************************</div><div><br></div><div>end =
of Last Call comments.</div><div><br></div><div><br></div><div class=3D"gma=
il_extra">

<br><br><div class=3D"gmail_quote">On Mon, Feb 4, 2013 at 9:18 AM, SM <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@re=
sistor.net</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>At 05:24 01-02-2013, The IESG wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IESG has received a request from the Protocol to Access WS database<br>
WG (paws) to consider the following document:<br>
- &#39;Protocol to Access White Space (PAWS) Database: Use Cases and<br>
=A0 =A0Requirements&#39;<br>
=A0 &lt;draft-ietf-paws-problem-stmt-<u></u>usecases-rqmts-12.txt&gt; as In=
formational<br>
RFC<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2013-02-15. Exceptionally, comments may be<br>
</blockquote>
<br></div>
I read the draft. =A0I am okay with whatever the working group decides.<br>
<br>
In Section 1.1:<br>
<br>
=A0 &quot;Academia and Industry have studied multiple cognitive radio [2]<b=
r>
=A0 =A0mechanisms for use in such a scenario.&quot;<br>
<br>
The reference seemed odd. =A0It took me some time to understand that it was=
 put in to address a comment. =A0However, the first (external) reference th=
at defines that is a 404.<br>
<br>
There are two occurrences of the RFC 2119 boilerplate in the draft.<br>
<br>
In Section 3.1:<br>
<br>
=A0 &quot;Before the master device can transmit in white space spectrum, it=
 MUST<br>
=A0 =A0obtain the address of a trusted white space database, which it will<=
br>
=A0 =A0query for available white space spectrum.&quot;<br>
<br>
Why is this a MUST?<br>
<br>
In Section 4.2:<br>
<br>
=A0 &quot;A simplified operation scenario of offloading content, such as vi=
deo<br>
=A0 =A0stream, from the a metered Internet connection to the a WS connectio=
n<br>
=A0 =A0consists of the following steps:&quot;<br>
<br>
What is a metered Internet connection?<br>
<br>
In Section 4.4:<br>
<br>
=A0 &quot;To set up a replacement network, spectrum needs to be quickly<br>
=A0 =A0cleared and reallocated to the crisis response organization.&quot;<b=
r>
<br>
Is that what P.15 is about? =A0BTW, O.17 uses a &quot;should&quot; for this=
.<br>
<br>
In Section 6.2:<br>
<br>
=A0 &quot;P.3 =A0The protocol MUST provide the ability for the database to<=
br>
=A0 =A0 =A0authenticate the master device.&quot;<br>
<br>
=A0 &quot;P.5 =A0The messages sent by the master device to the database and=
 the<br>
=A0 =A0 =A0 messages sent by the database to the master device MUST support=
<br>
=A0 =A0 =A0 integrity protection.&quot;<br>
<br>
=A0 &quot;P.6 =A0The protocol MUST provide the capability for messages sent=
 by<br>
=A0 =A0 =A0 the master device and database to be encrypted.&quot;<br>
<br>
This sounds like the usual IETF security stuff.<br>
<br>
=A0 &quot;P.8 =A0The protocol MUST support a registration acknowledgement<b=
r>
=A0 =A0 =A0 indicating the success of failure of the master device<br>
=A0 =A0 =A0 registration.&quot;<br>
<br>
The &quot;success of failure&quot; might need fixing.<br>
<br>
=A0 &quot;P.14 =A0The protocol MUST support a validation response from the<=
br>
=A0 =A0 =A0 database to the master to indicate if the slave device is<br>
=A0 =A0 =A0 validated by the WSDB. =A0The validation response MUST indicate=
 the<br>
=A0 =A0 =A0 success or failure of the validation request.&quot;<br>
<br>
What is WSDB?<br>
<br>
In Section 6.3:<br>
<br>
=A0 &quot;O.1 =A0The database and the master device MUST be connected to th=
e<br>
=A0 =A0 =A0 Internet.&quot;<br>
<br>
What is the Internet?<br>
<br>
=A0 &quot;O.2 =A0A master device MUST be able to determine its location inc=
luding<br>
=A0 =A0 =A0 uncertainty and confidence level.&quot;<br>
<br>
Does the working group plan to build its deliverables upon the GEOPRIV work=
?<br>
<br>
I found the draft easy to read. =A0The draft goes into extraneous details i=
n some parts. =A0As an off-topic comment I see that the working group had t=
he usual JSON versus XML discussion [1]. :-) =A0I understood the concept of=
 white spaces as discussed in the draft. =A0If I understood correctly the u=
sage of database is related to the data model in Section 6. =A0On seeing Fi=
gure 7 it seemed to me that what was missing is an architecture document wh=
ich provides a high-level view of how all this is supposed to work. =A0I am=
 not suggesting a reorganization of the draft as it may end up as too much =
work. =A0The draft attempts to convince the reader about the importance of =
white spaces and its use cases. =A0It&#39;s basically about database querie=
s.<br>


<br>
Regards,<br>
-sm<br>
<br>
1. <a href=3D"http://www.ietf.org/mail-archive/web/apps-discuss/current/msg=
07261.html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/a=
pps-discuss/<u></u>current/msg07261.html</a> =A0<div><div>
<br>
______________________________<u></u>_________________<br>
paws mailing list<br>
<a href=3D"mailto:paws@ietf.org" target=3D"_blank">paws@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/paws" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/paws</a><br>
</div></div></blockquote></div><br></div></div>

--f46d042ef661c9d0a904d590a9c6--

From amancuso@google.com  Wed Feb 13 08:50:39 2013
Return-Path: <amancuso@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E4421F8A89 for <ietf@ietfa.amsl.com>; Wed, 13 Feb 2013 08:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.864
X-Spam-Level: 
X-Spam-Status: No, score=-101.864 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Soan5PYUq-v for <ietf@ietfa.amsl.com>; Wed, 13 Feb 2013 08:50:39 -0800 (PST)
Received: from mail-la0-x232.google.com (la-in-x0232.1e100.net [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3286B21F8A7E for <ietf@ietf.org>; Wed, 13 Feb 2013 08:50:37 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id ec20so1384335lab.37 for <ietf@ietf.org>; Wed, 13 Feb 2013 08:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=91XQwHOWEcZn2nNZUMWkdQN2wf1xfNGRWCTmQMoVKq0=; b=fVqc5af0wgi5SpOA/uZmqncmn3gbaVxOALpzou03xeFKSxo+MovnXY9/ZwZuFS/i7+ F2evJ6K/XOHkmLeVwn7GdcnbHaWHULMmF2KM1PfjFtsDe+mYlfYs1+fi+JwL6DdcLeKX +s8spAeX7RMDW6HqSMrX9LX7Vn0cTwheye6jSq2RIbJHRs3Xlv1LBm2zDECkfKmSaxqe Ubv8RGClGCmyAWZlEhqYekL8uve33xsLhHLI0CIGE8ptnf5RNcYn43iBFbidFAbII1JU os8hE2HIFC6MGs5Ie9CUWwz9PST2fkr4PjYmMY/7y4kVFd+bhEqXdN0qWPxtDaZW+elV wIFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=91XQwHOWEcZn2nNZUMWkdQN2wf1xfNGRWCTmQMoVKq0=; b=USDtZGQi+NpJVpLkphp3wGClZVP/k0bFX5Xbcr/eAhoR72bGeUdJ7PV7SP5PIJw5v2 cybqxOo7oRzq2CnlsnqBEDYhA3REYXqyD3Y40OaaYIFeexkG/OA9xhvMGydPHeu+bZ+6 sWISVMgcq3N8oU1gKuX8ZMv/Hbga5IZ4sDyg8n3Eu5lOZ9DOI7uOdEQSVZFTrJCApyU6 EwZ+/e86TE37ZloHUp8Qce1s3XWbwyEgmktWbn8XT+gDi04KyV34dsEttpS02kCZU/gB G7z7bz3tLmKiTgH8j/vGROZ75FA6VQvGEDEPl0SHzlX5SIAWFswIq7TWckwizAidJ4JG f2LQ==
MIME-Version: 1.0
X-Received: by 10.112.39.1 with SMTP id l1mr9208357lbk.35.1360774236875; Wed, 13 Feb 2013 08:50:36 -0800 (PST)
Received: by 10.152.6.42 with HTTP; Wed, 13 Feb 2013 08:50:36 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130213040129.09254bc0@resistor.net>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130204064015.09261fa0@resistor.net> <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.gmail.com> <6.2.5.6.2.20130213040129.09254bc0@resistor.net>
Date: Wed, 13 Feb 2013 08:50:36 -0800
Message-ID: <CAN5AP-9dwOzKYOV_Xkw01pwGMX=x7+nYUjzv1WtJP-K_WYiR1w@mail.gmail.com>
Subject: Re: [paws] Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
From: Anthony Mancuso <amancuso@google.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=0023547c9bbd022ba404d59df139
X-Gm-Message-State: ALoCoQkOtNPV7ryt1u9JNjVJ1nau6opGXBvZh8HDh6qQ7k7aedpmEWQYuImxo6fbjTSOSglGy25We6w4aiASb2SIRBFq5bSv/LPCPlSC1xdX3T4Qd72FfJplDaubu/EKnKPPy8aemdBX/8UHxklvW22g4IGM0UNESIwI4zPP5bii4kO1f8WOVfoTg5XZB3j8elVX98RLsq+r
X-Mailman-Approved-At: Wed, 13 Feb 2013 10:13:26 -0800
Cc: "paws@ietf.org" <paws@ietf.org>, Gabor Bajko <Gabor.Bajko@nokia.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, 13 Feb 2013 16:50:39 -0000

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

Hi SM,

I responded inline to your latest comments, below, where I took additional
action.

Thanks,

Tony


On Wed, Feb 13, 2013 at 4:33 AM, SM <sm@resistor.net> wrote:

> Hi Anthony,
>
> At 17:00 12-02-2013, Anthony Mancuso wrote:
>
>> In Section 1.1:
>>
>>   "Academia and Industry have studied multiple cognitive radio [2]
>>    mechanisms for use in such a scenario."
>>
>> The reference seemed odd.  It took me some time to understand that it was
>> put in to address a comment.  However, the first (external) reference that
>> defines that is a 404.
>>
>> TODO(amancuso): fix link
>>
>
> Ok.


>  I think the MUST below is one of the two boilerplate words you had a
>> comment on. Is there another?
>>
>
> See the section after the Abstract and Section 2.1.


    TM: Now i see the two. I removed the second (redundant) RFC 2119
wording and reference.

>
>
>  In response to earlier comments, this section was reworded and "MUST"
>> changed to "must". I assume this is what you were questioning.
>>
>
> Ok.
>
>
>  ----
>>
>> In Section 4.2:
>>
>>   "A simplified operation scenario of offloading content, such as video
>>    stream, from the a metered Internet connection to the a WS connection
>>    consists of the following steps:"
>>
>> What is a metered Internet connection?
>> ----
>> Usage is monitored (metered) and paid for. I rephrased to clarify: "more
>> congested or costly Internet connection, such as a metered
>> (fee-based-on-usage) wire, wireless, or satellite service."
>>
>
> In my opinion you don't really have to get into all that.  I'll defer to
> the author.


     TM: Agreed. Simply referred to the "metered" Internet service as a
paid service.

>
>
>  cleaned up protocol and operational requirements in response to earlier
>> comments. This is a good example of a use case, but didn't fit comfortably
>> as a P or O requirement, and was deleted from requirements sections.
>>
>
> Ok.
>
>
>  White Space Database (used to be defined in terminology). Changed it
>> simply to "database".
>>
>
> Ok.
>
>
>  This is a rather large container of worms. We kicked it around for about
>> a half-hour and concluded that since this doc is for the Internet
>> Engineering Task Force, most readers will understand (and forgive).
>> Nonetheless, this is a good point, so I generalized it as follows (while
>> retaining the commonly used (and loosely-understood) term: "The database
>> and the master device MUST be connected (e.g., through the Internet)."
>>
>
> I agree about that container. :-)  The draft is trying to convince me that
> white space is better for the Internet connection (see my previous comment
> about metered).  The requirements is about a protocol to Access Spectrum
> Database.  IP connectivity is a lower-layer issue.  I am ok with the above
> text.


>
>
>  This section only intends to state the general requirement. It is my
>> understanding that the current draft of the protocol specification
>> specifies JSON encoding of location parameters that is compatible with
>> GEOPRIV.
>>
>
> Ok.
>
> Regards,
> -sm
>

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

<div dir=3D"ltr">Hi SM,<div><br></div><div>I responded inline to your lates=
t comments, below, where I took additional action.</div><div><br></div><div=
 style>Thanks,</div><div><br></div><div style>Tony</div><div class=3D"gmail=
_extra">
<br><br><div class=3D"gmail_quote">On Wed, Feb 13, 2013 at 4:33 AM, SM <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:sm@resistor.net" target=3D"_blank">sm@r=
esistor.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Anthony,<div class=3D"im"><br>
At 17:00 12-02-2013, Anthony Mancuso wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In Section 1.1:<br>
<br>
=A0 &quot;Academia and Industry have studied multiple cognitive radio [2]<b=
r>
=A0 =A0mechanisms for use in such a scenario.&quot;<br>
<br>
The reference seemed odd. =A0It took me some time to understand that it was=
 put in to address a comment. =A0However, the first (external) reference th=
at defines that is a 404.<br>
<br>
TODO(amancuso): fix link<br>
</blockquote>
<br></div>
Ok.=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I think the MUST below is one of the two boilerplate words you had a commen=
t on. Is there another?<br>
</blockquote>
<br></div>
See the section after the Abstract and Section 2.1.</blockquote><div>=A0 =
=A0</div><div style>=A0 =A0 TM: Now i see the two. I removed the second (re=
dundant) RFC 2119 wording and reference.</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In response to earlier comments, this section was reworded and &quot;MUST&q=
uot; changed to &quot;must&quot;. I assume this is what you were questionin=
g.<br>
</blockquote>
<br></div>
Ok.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
----<br>
<br>
In Section 4.2:<br>
<br>
=A0 &quot;A simplified operation scenario of offloading content, such as vi=
deo<br>
=A0 =A0stream, from the a metered Internet connection to the a WS connectio=
n<br>
=A0 =A0consists of the following steps:&quot;<br>
<br>
What is a metered Internet connection?<br>
----<br>
Usage is monitored (metered) and paid for. I rephrased to clarify: &quot;mo=
re congested or costly Internet connection, such as a metered (fee-based-on=
-usage) wire, wireless, or satellite service.&quot;<br>
</blockquote>
<br></div>
In my opinion you don&#39;t really have to get into all that. =A0I&#39;ll d=
efer to the author.</blockquote><div>=A0</div><div style>=A0 =A0 =A0TM: Agr=
eed. Simply referred to the &quot;metered&quot; Internet service as a paid =
service.</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
cleaned up protocol and operational requirements in response to earlier com=
ments. This is a good example of a use case, but didn&#39;t fit comfortably=
 as a P or O requirement, and was deleted from requirements sections.<br>

</blockquote>
<br></div>
Ok.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
White Space Database (used to be defined in terminology). Changed it simply=
 to &quot;database&quot;.<br>
</blockquote>
<br></div>
Ok.<div class=3D"im"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This is a rather large container of worms. We kicked it around for about a =
half-hour and concluded that since this doc is for the Internet Engineering=
 Task Force, most readers will understand (and forgive). Nonetheless, this =
is a good point, so I generalized it as follows (while retaining the common=
ly used (and loosely-understood) term: &quot;The database and the master de=
vice MUST be connected (e.g., through the Internet).&quot;<br>

</blockquote>
<br></div>
I agree about that container. :-) =A0The draft is trying to convince me tha=
t white space is better for the Internet connection (see my previous commen=
t about metered). =A0The requirements is about a protocol to Access Spectru=
m Database. =A0IP connectivity is a lower-layer issue. =A0I am ok with the =
above text.=A0</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im"><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This section only intends to state the general requirement. It is my unders=
tanding that the current draft of the protocol specification specifies JSON=
 encoding of location parameters that is compatible with GEOPRIV.<br>
</blockquote>
<br></div>
Ok.<br>
<br>
Regards,<br>
-sm <br>
</blockquote></div><br></div></div>

--0023547c9bbd022ba404d59df139--

From vincent.roca@inria.fr  Wed Feb 13 09:07:49 2013
Return-Path: <vincent.roca@inria.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 F0E2A21F89EF; Wed, 13 Feb 2013 09:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.806
X-Spam-Level: 
X-Spam-Status: No, score=-109.806 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, 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 Zu1Zl40bPZjW; Wed, 13 Feb 2013 09:07:48 -0800 (PST)
Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by ietfa.amsl.com (Postfix) with ESMTP id 217B621F8A6F; Wed, 13 Feb 2013 09:07:43 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,658,1355094000"; d="scan'208,217";a="2109953"
Received: from unknown (HELO [10.2.29.151]) ([78.250.189.3]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 13 Feb 2013 17:55:43 +0100
Subject: Re: GenART LC review of draft-ietf-rmt-fcast-07
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-215950537
From: Vincent Roca <vincent.roca@inria.fr>
In-Reply-To: <032b01cdf34f$7714f300$653ed900$@gmail.com>
Date: Wed, 13 Feb 2013 18:07:19 +0100
Message-Id: <DBDA5F3C-6911-4266-8F0E-637A404BE7A9@inria.fr>
References: <032b01cdf34f$7714f300$653ed900$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Wed, 13 Feb 2013 10:13:26 -0800
Cc: gen-art@ietf.org, Vincent Roca <vincent.roca@inria.fr>, ietf@ietf.org, draft-ietf-rmt-fcast.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2013 17:07:49 -0000

--Apple-Mail-1-215950537
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dear Roni,

Thanks a lot for your comments. Here are my answers.


> Document: draft-ietf-rmt-fcast-07
> Reviewer: Roni Even
> Review Date:2013=961=9615
> IETF LC End Date: 2013-1=9622
> IESG Telechat date:
> =20
> Summary: This draft is almost ready for publication as Standard track =
RFC.
> =20
> =20
> Major issues:
> =20
> Minor issues:
> =20
> 1.       I had some problem when reading the document about what is =
mandatory to support. The distinction between what is  required to be  =
supported and used is mentioned in section 5. Also section 3.3 discusses =
what compliant implementation is, but section 5 provides the full =
information. I think that it will be better to move section 5 before or =
at the beginning of section 3 or as part of  3.3.  no need to have the =
information twice.

I agree. The new 3.3 section now explains the concepts, and the =
"mandatory to implement" things are moved to
the "Requirements for Compliant Implementations" section.


This "compliant implementations" section is moved at the end of section =
3 as suggested by Joseph Yee.
The new ToC is therefore:

   2.  FCAST Data Formats
   3.  FCAST Principles
   4.  Requirements for Compliant Implementations


> 2.       In section 3.3 =93The support of GZIP encoding, or any other =
solution, remains optional.=94 I think that support is mandatory.

You're right and there is also some confusion here between the GZIP use =
in MDEnc, and the GZIP use in
Content-Encoding. It makes no sense to say GZIP is mandatory in MDEnc, =
and optional in Content-Encoding.
This is now clarified in the "compliant implementations" section.


NEW item in "compliant implementations" section:

   | Content-Encoding       | MUST be supported.  All FCAST            |
   |                        | implementations MUST support GZIP        |
   |                        | encoding [RFC1952]                       |


Additionally, I've moved text from Section 2.2 about Content-Length and
Content-Encoding (that includes lengthy discussion on GZIP usage)
to Section 3.3. There's now a single place to explain concepts with all
the details.


OLD item in 2.2:

   o  Content-Encoding: it specifies the optional encoding of the object
      list, performed by FCAST.  For instance:
           Content-Encoding: gzip
      indicates that the Object List field has been encoded with GZIP
      [RFC1952].  If there is no Content-Encoding entry, the receiver
      MUST assume that the Object List field is plain text (default).
      The support of GZIP encoding, in addition to the plain text form,
      is REQUIRED.  The Content-Encoding entry MAY be used to indicate
      other encoding types to support non-standard FCAST implementation
      or future extended specifications.


NEW item in 2.2:

   o  Content-Encoding: it specifies the optional encoding of the object
      list, performed by FCAST.


OLD item in 3.3:
   o  Content-Encoding: a string that contains the optional encoding of
      the object performed by FCAST.  If there is no Content-Encoding
      entry, the receiver MUST assume that the object is not encoded
      (default).  The support of GZIP encoding, or any other solution,
      remains optional.


NEW item in 3.3:

   o  Content-Encoding: a string that contains the optional encoding of
      the object performed by FCAST.  For instance:
           Content-Encoding: gzip
      indicates that the Object List field has been encoded with GZIP
      [RFC1952].  If there is no Content-Encoding entry, the receiver
      MUST assume that FCAST did not perform any encoding to the object
      (default).


While doing that I realized that the Fcast-CID-Complete and Fcast-CID-ID
were not mentioned at all in the "compliant implementations" section. =
This
is now corrected as follows:

NEW item in "compliant implementations" section:

   CID-specific Meta-data items (Section 2.2):

       +-----------------------+-------------------+
       | Feature               | Status            |
       +-----------------------+-------------------+
       | Fcast-CID-Complete    | MUST be supported |
       | Fcast-CID-ID          | MUST be supported |
       +-----------------------+-------------------+


>  Nits/editorial comments:


The following 4 comments have been resolved.

> In section 5.1 at the end of first table =93in-bound=94 should be =
=93in-band=94
> In section 6 in the paragraph after the bullet points =93possibly =
possibly=94
> In section 7 =93This specification requires IANA to create two new =
registries=94 I think there are three new registries.
> In section 7.1 second paragraph =93registry registry=94

Thanks a lot for your comments.
Cheers,

   Vincent


--Apple-Mail-1-215950537
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><base href=3D"x-msg://491/"></head><body style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div>Dear Roni,</div><div><br></div>Thanks a lot =
for your comments.&nbsp;Here are my =
answers.<div><div><br></div><div><br><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Document:<span =
class=3D"Apple-converted-space">&nbsp;</span></span><span =
style=3D"font-family: 'Courier New'; =
">draft-ietf-rmt-fcast-07</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p></o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Reviewer: Roni Even<o:p></o:p></span></div><div style=3D"margin-top: =
0in; margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; ">Review =
Date:2013=961=9615<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">IETF LC End Date: =
2013-1=9622<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">IESG Telechat =
date:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Summary: This draft is almost ready for publication as Standard track =
RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">.<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p>&nbsp;</o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">Major =
issues:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
">Minor issues:<o:p></o:p></span></div><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0in; margin-bottom: 0.0001pt; font-size: =
10.5pt; font-family: Consolas; "><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></div><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0.5in; =
margin-bottom: 0.0001pt; font-size: 10.5pt; font-family: Consolas; =
text-indent: -0.25in; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><span>1.<span style=3D"font: normal normal normal =
7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">I had some problem when reading the document about what is =
mandatory to support. The distinction between what is &nbsp;required to =
be &nbsp;supported and used is mentioned in section 5. Also section 3.3 =
discusses what compliant implementation is, but section 5 provides the =
full information. I think that it will be better to move section 5 =
before or at the beginning of section 3 or as part of &nbsp;3.3. =
&nbsp;no need to have the information =
twice.</span></div></div></div></span></blockquote><div><br></div><div>I =
agree. The new 3.3 section now explains the concepts, and the "mandatory =
to implement" things are moved to</div><div>the "Requirements for =
Compliant Implementations" =
section.</div><div><br></div><div><div><br></div></div><div>This&nbsp;"com=
pliant implementations" section&nbsp;is moved&nbsp;at the end of section =
3 as suggested by&nbsp;Joseph Yee.</div><div>The new ToC is =
therefore:</div><div><br></div><div>&nbsp; &nbsp;2. &nbsp;FCAST Data =
Formats</div><div>&nbsp; &nbsp;3. &nbsp;FCAST Principles<br>&nbsp; =
&nbsp;4. &nbsp;Requirements for Compliant =
Implementations<br><br></div><br><blockquote type=3D"cite"><div =
lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" =
style=3D"page: WordSection1; "><div style=3D"margin-top: 0in; =
margin-right: 0in; margin-left: 0.5in; margin-bottom: 0.0001pt; =
font-size: 10.5pt; font-family: Consolas; text-indent: -0.25in; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></span></div><div style=3D"margin-top: 0in; margin-right: =
0in; margin-left: 0.5in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; text-indent: -0.25in; "><span style=3D"font-size: =
11pt; font-family: Calibri, sans-serif; "><span>2.<span style=3D"font: =
normal normal normal 7pt/normal 'Times New Roman'; =
">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span></span><span =
dir=3D"LTR"></span><span style=3D"font-size: 11pt; font-family: Calibri, =
sans-serif; ">In section 3.3 =93</span><span style=3D"font-size: 11pt; =
font-family: Calibri, sans-serif; ">The support of GZIP encoding, or any =
other solution, remains optional.=94 I think that support is =
mandatory.</span></div></div></div></blockquote><div><br></div><div>You're=
 right and there is also some confusion here between the GZIP use =
in&nbsp;MDEnc, and the GZIP use in</div><div>Content-Encoding.&nbsp;It =
makes no sense to say GZIP is mandatory in MDEnc, and optional in =
Content-Encoding.</div><div>This is now clarified =
in&nbsp;the&nbsp;"compliant implementations" =
section.</div><div><div><br></div><div><br></div><div>NEW item =
in&nbsp;"compliant implementations" =
section:</div><div><div><div><br></div></div><div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp;| =
Content-Encoding &nbsp; &nbsp; &nbsp; | MUST be supported. &nbsp;All =
FCAST &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp;| &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;| implementations MUST support GZIP &nbsp; &nbsp; &nbsp; =
&nbsp;|</font></div><div><font class=3D"Apple-style-span" face=3D"'Courier=
 New'">&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| encoding [RFC1952] &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|</font></div><div><br></div></div></div></div><div><br></div><div>Additio=
nally, I've moved text from Section 2.2 about Content-Length =
and</div><div>Content-Encoding (that includes lengthy discussion on GZIP =
usage)</div><div>to Section 3.3. There's now a single place to explain =
concepts with all</div><div>the =
details.</div><div><br></div><div><br></div><div>OLD item in =
2.2:</div><div><br></div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: it specifies the optional encoding of the =
object</div><div>&nbsp; &nbsp; &nbsp; list, performed by FCAST. =
&nbsp;For instance:</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Content-Encoding: gzip</div><div>&nbsp; &nbsp; &nbsp; indicates =
that the Object List field has been encoded with GZIP</div><div>&nbsp; =
&nbsp; &nbsp; [RFC1952]. &nbsp;If there is no Content-Encoding entry, =
the receiver</div><div>&nbsp; &nbsp; &nbsp; MUST assume that the Object =
List field is plain text (default).</div><div>&nbsp; &nbsp; &nbsp; The =
support of GZIP encoding, in addition to the plain text =
form,</div><div>&nbsp; &nbsp; &nbsp; is REQUIRED. &nbsp;The =
Content-Encoding entry MAY be used to indicate</div><div>&nbsp; &nbsp; =
&nbsp; other encoding types to support non-standard FCAST =
implementation</div><div>&nbsp; &nbsp; &nbsp; or future extended =
specifications.</div><div><br></div><div><br></div></div><div>NEW item =
in 2.2:</div><div><br></div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: it specifies the optional encoding of the =
object</div><div>&nbsp; &nbsp; &nbsp; list, performed by =
FCAST.</div><div><br></div></div><div><br></div><div>OLD item in =
3.3:</div><div><div>&nbsp; &nbsp;o &nbsp;Content-Encoding: a string that =
contains the optional encoding of</div><div>&nbsp; &nbsp; &nbsp; the =
object performed by FCAST. &nbsp;If there is no =
Content-Encoding</div><div>&nbsp; &nbsp; &nbsp; entry, the receiver MUST =
assume that the object is not encoded</div><div>&nbsp; &nbsp; &nbsp; =
(default). &nbsp;The support of GZIP encoding, or any other =
solution,</div><div>&nbsp; &nbsp; &nbsp; remains =
optional.</div><div><br></div></div><div><br></div><div>NEW item in =
3.3:</div><div><div><br></div><div><div><div>&nbsp; &nbsp;o =
&nbsp;Content-Encoding: a string that contains the optional encoding =
of</div><div>&nbsp; &nbsp; &nbsp; the object performed by FCAST. =
&nbsp;For instance:</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Content-Encoding: gzip</div><div>&nbsp; &nbsp; &nbsp; indicates =
that the Object List field has been encoded with GZIP</div><div>&nbsp; =
&nbsp; &nbsp; [RFC1952]. &nbsp;If there is no Content-Encoding entry, =
the receiver</div><div>&nbsp; &nbsp; &nbsp; MUST assume that FCAST did =
not perform any encoding to the object</div><div>&nbsp; &nbsp; &nbsp; =
(default).</div></div></div></div><div><br></div><div><br></div><div>While=
 doing that I realized that the&nbsp;Fcast-CID-Complete =
and&nbsp;Fcast-CID-ID</div><div>were not mentioned at all in the =
"compliant implementations"&nbsp;section. This</div><div>is now =
corrected as follows:</div><div><br></div><div>NEW item =
in&nbsp;"compliant implementations" =
section:</div><div><br></div><div><div>&nbsp; &nbsp;CID-specific =
Meta-data items (Section 2.2):</div><div><br></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><font=
 class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;| Feature &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Status &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><font=
 class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;| Fcast-CID-Complete &nbsp; &nbsp;| MUST be supported =
|</font></div><div><font class=3D"Apple-style-span" face=3D"'Courier =
New'">&nbsp; &nbsp; &nbsp; &nbsp;| Fcast-CID-ID &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;| MUST be supported |</font></div><div><font =
class=3D"Apple-style-span" face=3D"'Courier New'">&nbsp; &nbsp; &nbsp; =
&nbsp;+-----------------------+-------------------+</font></div><div><br><=
/div></div><br><blockquote type=3D"cite"><div lang=3D"EN-US" link=3D"blue"=
 vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><div style=3D"margin-top: 0in; margin-right: 0in; =
margin-left: 0in; margin-bottom: 0.0001pt; font-size: 10.5pt; =
font-family: Consolas; "><span style=3D"font-size: 11pt; font-family: =
Calibri, sans-serif; "><o:p>&nbsp;</o:p></span><span =
class=3D"Apple-style-span" style=3D"font-family: Calibri, sans-serif; =
font-size: 15px; line-height: 17px; ">Nits/editorial =
comments:</span></div></div></div></blockquote><div><br></div><div><br></d=
iv><div>The following 4 comments have been =
resolved.</div><br><blockquote type=3D"cite"><div lang=3D"EN-US" =
link=3D"blue" vlink=3D"purple"><div class=3D"WordSection1" style=3D"page: =
WordSection1; "><p class=3D"MsoNormal" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; line-height: =
17px; font-size: 11pt; font-family: Calibri, sans-serif; =
"><o:p></o:p></p><ol start=3D"1" type=3D"1" style=3D"margin-bottom: 0in; =
margin-top: 0in; "><li class=3D"MsoNormal" style=3D"margin-top: 0in; =
margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; line-height: =
17px; font-size: 11pt; font-family: Calibri, sans-serif; ">In section =
5.1 at the end of first table =93in-bound=94 should be =
=93in-band=94<o:p></o:p></li><li class=3D"MsoNormal" style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; =
line-height: 17px; font-size: 11pt; font-family: Calibri, sans-serif; =
">In section 6 in the paragraph after the bullet points =93possibly =
possibly=94<o:p></o:p></li><li class=3D"MsoNormal" style=3D"margin-top: =
0in; margin-right: 0in; margin-bottom: 10pt; margin-left: 0in; =
line-height: 17px; font-size: 11pt; font-family: Calibri, sans-serif; =
">In section 7 =93This specification requires IANA to create two new =
registries=94 I think there are three new registries.<o:p></o:p></li><li =
class=3D"MsoNormal" style=3D"margin-top: 0in; margin-right: 0in; =
margin-bottom: 10pt; margin-left: 0in; line-height: 17px; font-size: =
11pt; font-family: Calibri, sans-serif; ">In section 7.1 second =
paragraph =93registry =
registry=94</li></ol></div></div></blockquote><div><br></div>Thanks a =
lot for your comments.</div><div>Cheers,</div><div><br></div><div>&nbsp; =
&nbsp;Vincent</div><div><br></div></div></body></html>=

--Apple-Mail-1-215950537--

From barryleiba.mailing.lists@gmail.com  Wed Feb 13 12:33:38 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F32821F8555; Wed, 13 Feb 2013 12:33:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.812
X-Spam-Level: 
X-Spam-Status: No, score=-102.812 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhXDuYun6p1O; Wed, 13 Feb 2013 12:33:37 -0800 (PST)
Received: from mail-ve0-f178.google.com (mail-ve0-f178.google.com [209.85.128.178]) by ietfa.amsl.com (Postfix) with ESMTP id 4755921F84EA; Wed, 13 Feb 2013 12:33:37 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id db10so1470875veb.9 for <multiple recipients>; Wed, 13 Feb 2013 12:33:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=zL/j3gNlO/Qgcu3R1vfxxKLCBfLvJDF6S7pxaEPKv8Y=; b=Fo92R5LYXN/NkzwuQd3DTu/VasaMe4eA+IyGTuJNINfTAh5yDT4ABh1KOIeAJqozw6 awFFWGLJHr8PMRP5VetPKhwJcLO2xHgCr6nVBf41pzJsuSHkfDz0fqCkOUbcoI/12qYa Kz03K+AMbWQsZ8jy6CtZ2ND2KYpO7X1u1Dnvmpjfidbfi6o8dCAsqd/mHorztXWOAqHE 7Q0gSQMnX5bfkQSc8o9+Sdu/2I9TcsDDGyhkk/hmVwgdkayYOpseCvqtrn2knt32zCJD n4ALIiG/mamUKSpSa3X+frAKv+FhrDK5vE1GWBl1sgDYru7k9UOrDyif4Qx/gSilPvMM uuoA==
MIME-Version: 1.0
X-Received: by 10.220.149.200 with SMTP id u8mr31610068vcv.7.1360787616708; Wed, 13 Feb 2013 12:33:36 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Wed, 13 Feb 2013 12:33:36 -0800 (PST)
In-Reply-To: <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.gmail.com>
References: <20130201132421.6136.92013.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130204064015.09261fa0@resistor.net> <CAN5AP--WNa85vJm+6ogiqzadMTgeON4zSG=BrQL35NLuaBAs5Q@mail.gmail.com>
Date: Wed, 13 Feb 2013 15:33:36 -0500
X-Google-Sender-Auth: G5vQnueBH1ZEWOhkAfYiZXxfBUg
Message-ID: <CAC4RtVA8ZM9H_KM5=sx+j_1_=m-ZEYSswwtH+X42UnnkOUGOsQ@mail.gmail.com>
Subject: Re: [paws] Last Call: <draft-ietf-paws-problem-stmt-usecases-rqmts-12.txt> (Protocol to Access White Space (PAWS) Database: Use Cases and Requirements) to Informational RFC
From: Barry Leiba <barryleiba@computer.org>
To: Anthony Mancuso <amancuso@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Gabor Bajko <Gabor.Bajko@nokia.com>, SM <sm@resistor.net>, Pete Resnick <presnick@qti.qualcomm.com>, "paws@ietf.org" <paws@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, 13 Feb 2013 20:33:38 -0000

Thanks for the thorough reply, Tony.  I'm happy with all the
resolutions you propose to my issues, and I'm looking forward to
reviewing the updated document.

> I list Pete Resnick's and Peter Stanforth's comments and my responses first,
> followed by Barry Leila's, then SM's.

I'm not, however, happy with how you spell my name.  But I'll get over it.....

Barry LeiBa

From bclaise@cisco.com  Thu Feb 14 08:04:38 2013
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113FC21F84F4 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 08:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.539
X-Spam-Level: 
X-Spam-Status: No, score=-10.539 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 L8mjOmDvh9VB for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 08:04:37 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id DADE121F883A for <ietf@ietf.org>; Thu, 14 Feb 2013 08:04:36 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1EG4Z2P022986; Thu, 14 Feb 2013 17:04:35 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1EG4EZQ018930; Thu, 14 Feb 2013 17:04:25 +0100 (CET)
Message-ID: <511D0AFE.3000407@cisco.com>
Date: Thu, 14 Feb 2013 17:04:14 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130209090616.0a22ba20@resistor.net>
In-Reply-To: <6.2.5.6.2.20130209090616.0a22ba20@resistor.net>
Content-Type: multipart/alternative; boundary="------------030700070008010902040401"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2013 16:04:38 -0000

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

Hi Jari,
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Experiences from Cross-Area Work at the IETF'
>>   <draft-arkko-iesg-crossarea-02.txt> as Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-03-06. Exceptionally, comments 
>> may be
>
Hi Jari,

Thanks for your draft.
A couple of points.

1.

    Cross-area work does present some challenges, however.  Apart from
    the advisor model there are no established practices and the
    processes and division of responsibility differs from case to case
    [RFC2026  <http://tools.ietf.org/html/rfc2026>].

Regarding "there are no established practices", I would stress the 
directorate process. Not really processes in the sense of RFC 2026, but 
pretty useful for cross area work.

For example, for MIB doctors, see 
http://www.ietf.org/iesg/directorate/mib-doctors.html

    All MIB documents will be passed by a MIB doctor reviewer before
    they will be approved by the IESG. The MIB doctor review must be
    done after the Working Group Last Call and before the IETF Last
    Call. ADs and WG chairs responsible on I-Ds that include MIB
    documents should ask the OPS ADs for a MIB review as soon as the
    document completed WGLC.

For example, for the YANG doctors, see 
http://www.ietf.org/iesg/directorate/yang-doctors.html

    All YANG documents will be passed by a YANG doctor reviewer before
    they will be approved by the IESG. The YANG doctor review must be
    done after the Working Group Last Call and before the IETF Last
    Call. ADs and WG chairs responsible on I-Ds that include YANG
    documents should ask the OPS ADs for a review as soon as the
    document completed WGLC.

For example, the performance metrics directorate, see 
http://www.ietf.org/iesg/directorate/performance-metrics.html
Note that this directorate is a relatively new directorate, so the 
"process" is still debated

Etc... I can tell you that that "IPFIX doctors" is about to be put in place.

As an OPS AD, I'm trying to make sure that the OPS-related directorates 
have a clear documentation containing: the directorate goal, the 
"process", the benefits, the guidelines, etc...
2.

       part of the problem here is
       that IESG does not normally develop a master plan, but rather
       individual documents and charter proposals are brought to the IESG
       in a piecemeal fashion, one by one.  This makes it hard to see
       bigger trends and possibilities for colliding work.

I'm not sure if the master plan is the primary problem. At the time of 
the charter creation, discussions regarding the work division between 
different WGs take place. However, along the time, different WGs take 
different directions. And there, the master plan might fall apart. So I 
would say the problem is the lack of revisiting the existing charters/WG 
new directions on regular basis.
Somehow, my comment relates to a sentence I see later in the draft:

       Periodic review and re-assessment is healthy and encouraged.


3.
Jari, you mentioned in one of the emails: "The document has been mostly 
aimed at ADs and WG chairs"
Out of the 10 recommendations, some don't give me a clear advice. I can 
only say: "sure, that is common sense!"

    7.   The best examples of successful cross-area work involve
         combining two pieces of expertise, with both parties having an
         incentive to complete the work.

4.
Potentially, out of the 10 recommendations, you could flag the ones that 
might require some sort of process improvements.
For example:

    10.  In general, the ability to associate work with all the areas
         that it relates to will be helpful not just for scheduling, but
         also for participants following an area of work, review teams,
         and so on.


Regards, Benoit

--------------030700070008010902040401
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hi Jari,<br>
    <blockquote
      cite="mid:6.2.5.6.2.20130209090616.0a22ba20@resistor.net"
      type="cite">
      <blockquote type="cite">The IESG has received a request from an
        individual submitter to consider
        <br>
        the following document:
        <br>
        - 'Experiences from Cross-Area Work at the IETF'
        <br>
        &nbsp; &lt;draft-arkko-iesg-crossarea-02.txt&gt; as Informational RFC
        <br>
        <br>
        The IESG plans to make a decision in the next few weeks, and
        solicits
        <br>
        final comments on this action. Please send substantive comments
        to the
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-03-06. Exceptionally,
        comments may be
        <br>
      </blockquote>
      <br>
    </blockquote>
    Hi Jari,<br>
    <br>
    Thanks for your draft.<br>
    A couple of points.<br>
    <br>
    1.<br>
    <pre class="newpage">   Cross-area work does present some challenges, however.  Apart from
   the advisor model there are no established practices and the
   processes and division of responsibility differs from case to case
   [<a href="http://tools.ietf.org/html/rfc2026" title="&quot;The Internet Standards Process -- Revision 3&quot;">RFC2026</a>].

</pre>
    Regarding "there are no established practices", I would stress the
    directorate process. Not really processes in the sense of RFC 2026,
    but pretty useful for cross area work.<br>
    <br>
    For example, for MIB doctors, see
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/directorate/mib-doctors.html">http://www.ietf.org/iesg/directorate/mib-doctors.html</a><br>
    <blockquote>All MIB documents will be passed by a MIB doctor
      reviewer before they will be approved by the IESG. The MIB doctor
      review must be done after the Working Group Last Call and before
      the IETF Last Call. ADs and WG chairs responsible on I-Ds that
      include MIB documents should ask the OPS ADs for a MIB review as
      soon as the document completed WGLC.<br>
      <br>
    </blockquote>
    For example, for the YANG doctors, see
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/directorate/yang-doctors.html">http://www.ietf.org/iesg/directorate/yang-doctors.html</a><br>
    <blockquote>All YANG documents will be passed by a YANG doctor
      reviewer before they will be approved by the IESG. The YANG doctor
      review must be done after the Working Group Last Call and before
      the IETF Last Call. ADs and WG chairs responsible on I-Ds that
      include YANG documents should ask the OPS ADs for a review as soon
      as the document completed WGLC.</blockquote>
    For example, the performance metrics directorate, see
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/directorate/performance-metrics.html">http://www.ietf.org/iesg/directorate/performance-metrics.html</a><br>
    Note that this directorate is a relatively new directorate, so the
    "process" is still debated<br>
    <br>
    Etc... I can tell you that that "IPFIX doctors" is about to be put
    in place.<br>
    <br>
    As an OPS AD, I'm trying to make sure that the OPS-related
    directorates have a clear documentation containing: the directorate
    goal, the "process", the benefits, the guidelines, etc... <br>
    2.<br>
    <pre class="newpage">      part of the problem here is
      that IESG does not normally develop a master plan, but rather
      individual documents and charter proposals are brought to the IESG
      in a piecemeal fashion, one by one.  This makes it hard to see
      bigger trends and possibilities for colliding work.</pre>
    I'm not sure if the master plan is the primary problem. At the time
    of the charter creation, discussions regarding the work division
    between different WGs take place. However, along the time, different
    WGs take different directions. And there, the master plan might fall
    apart. So I would say the problem is the lack of revisiting the
    existing charters/WG new directions on regular basis.<br>
    Somehow, my comment relates to a sentence I see later in the draft:<br>
    <pre class="newpage">      Periodic review and re-assessment is healthy and encouraged.</pre>
    <br>
    3.<br>
    Jari, you mentioned in one of the emails: "The document has been
    mostly aimed at ADs and WG chairs"<br>
    Out of the 10 recommendations, some don't give me a clear advice. I
    can only say: "sure, that is common sense!"<br>
    <pre class="newpage">   7.   The best examples of successful cross-area work involve
        combining two pieces of expertise, with both parties having an
        incentive to complete the work.</pre>
    4.<br>
    Potentially, out of the 10 recommendations, you could flag the ones
    that might require some sort of process improvements.<br>
    For example:<br>
    <pre class="newpage">   10.  In general, the ability to associate work with all the areas
        that it relates to will be helpful not just for scheduling, but
        also for participants following an area of work, review teams,
        and so on.</pre>
    <br>
    Regards, Benoit
  </body>
</html>

--------------030700070008010902040401--

From sm@resistor.net  Thu Feb 14 15:02:49 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BE8821F870C for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdegTTHmJgeh for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:02:45 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B50F721F86F6 for <ietf@ietf.org>; Thu, 14 Feb 2013 15:02:45 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1EN2bAh017625; Thu, 14 Feb 2013 15:02:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360882963; bh=RWouAWpCDT1eyLysrTt70j4WZCQ109s0UzbQtnBB1ao=; h=Date:To:From:Subject:Cc; b=MSoGAFJKDqF4bKfiiHUjwmM5rK//XWjFsIQL8DBsgk4tS+ELxnr3rMms/HrPYNPrF L9uZdz8MKxs39tc7/TTal+awUCMm0DhbrItQlqo3wplzsHVNKERkCNaPrtapBsHKEh BKujdH3BKpqOQiTrpxdi6HvZuwi1frTODLksgAfk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360882963; i=@resistor.net; bh=RWouAWpCDT1eyLysrTt70j4WZCQ109s0UzbQtnBB1ao=; h=Date:To:From:Subject:Cc; b=eEdDi85jYVLDIilwi26nsQ11BojQn5MBce+yhiPa5vPPdX/LmJlnPntls17QTrfJ2 0SaejcFaArMEdOIU9NGuUQV3y95LkSb7qRF4OL20hl43NSLI0rNBNKiauP5FEkZ5CD L1EyLqAomGFRr2Tl1vQfM5t8yhunw2mtyNSVYjjo=
Message-Id: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 14 Feb 2013 15:02:02 -0800
To: Pete Resnick <presnick@qti.qualcomm.com>
From: SM <sm@resistor.net>
Subject: Musing on draft-resnick-on-consensus-01
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2013 23:02:49 -0000

Hi Pete,

I was musing on draft-resnick-on-consensus-01.  In the Section 1:

  "We don't require full consensus; that would allow a single
   intransigent person who simply keeps saying "No!"  to stop
   the process cold.  We only require rough consensus: If the
   chair of a working group determines that a technical issue
   brought forward by an objector has been truly considered by
   the working group ..."

The above is about working group consensus.  I suggest adding some 
text in the Introduction Section which mentions that it is about 
that.  The "We only require rough consensus" can be misunderstood as 
being the bar in an IETF-wide call.

  "Participants ask, "Why are we bothering with this 'humming'
   thing?  Wouldn't a show of hands be easier?"

The IAB recently had a discussion about "bottom-up organizational 
modes".  If I am not mistaken (please correct me) the IETF is the 
only organization that uses "humming".  I would say that it works in 
the IETF as it is part of the culture; it cannot be grafted on an 
organization.  There are cases when a show of hands can be used.  The 
sentence that follows the quoted text explains when to use "humming".

In Section 2:

   "The key is to separate those choices that are simply unappealing
    from those that are truly problematic."

I leave it to you to see whether you want to use the following:

    "Any attempt to determine consensus is difficult if the issues 
are technical,
     economic and political. Impassioned discussion, with little 
technical content,
     leads to an impass. It is up to the chair to tease apart the 
points and find
     out how to reduce the amount people disagree on. Find the bounds of the
     conversation. Separate out the technical issues."

Credits to Ralph Droms for the above.

   'This also brings up an important point about reaching consensus:
    Consensus does not really involve compromising.  "Compromising"
    implies that there remains something wrong with the outcome, but
    that the objector has simply given up.'

I read "compromise" as something intermediate between two 
things.  Consensus is used for conflict resolution.  It's not 
possible to resolve an issue if the two sides are not ready to 
compromise.  If you have two sides you end up with a King Solomon 
scenario.  It is very difficult to resolve the issue then.  Maybe 
"conciliatory" may be a better term to express the idea (see text 
quoted above).

The draft uses "objection" and "objector" in discussing about 
consensus.  That works in a formal or legalistic context.  In an IETF 
context you end up being the person standing out as you raised an 
objection.  Arguments do not have to be for or against 
(objection).  It's difficult for me to find the words to explain 
this.  I see that you used the word "concerns" in Section 4.

In Section 3:

   "If the chair finds, in their technical judgement, that the issue
    has truly been considered, and that the vast majority of the working"

Is it "technical judgement" or "the technical issue has been 
considered"?  For the former, the chair ends up taking a technical 
decision.  For the latter, the chair only has to use judgement.

   "that the vast majority of the working group has come to the conclusion
    that the tradeoff is worth making"

If you consider the arguments instead you don't have to get into 
majority and minority.

  "Now, a conclusion of only rough consensus relies heavily on the good
   judgement of the consensus caller..."

I like that paragraph.

RFC 3929 broaches consensus from a different angle.  I'll highlight 
the following: "There must be a clear statement of the decision to be 
reached".  The decision process used to get there is based on 
consensus.  However, it is not easy to attain consensus.  Rough 
consensus is the lesser barrier when consensus is not possible.  In 
other words rough consensus is not the default choice (re: rough 
consensus and running code).  The draft explains that by using 
"single intransigent person" as an example.  Section 2 discusses 
about lack of disagreement.  Lack of disagreement can also be a sign 
that the working group has not carefully considered the question.

It is not possible to reach consensus on the musings in the 
draft.  I'll pick a sentence: "it is a good solution to a real 
problem, even if the non-experts don't have the ability to fully 
judge the details".  There is a theory that the good solution would 
be chosen by a group which includes a significant number of 
non-experts.  If the questions being asked are too complex, it can 
end up with the wrong decision being taken.  If the group is 
segmented (e.g. multishareholder :-)), it can lead to a biased decision.

There are different types of consensus; e.g. the consensus of the 
girls, which is unappealable.

Regards,
-sm


From touch@isi.edu  Thu Feb 14 15:03:05 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E08321F8881 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:03:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.761
X-Spam-Level: 
X-Spam-Status: No, score=-104.761 tagged_above=-999 required=5 tests=[AWL=1.838, 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 RqOHixw7+PfW for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:03:01 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id DCD4C21F871C for <ietf@ietf.org>; Thu, 14 Feb 2013 15:03:00 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r1EN2nVV014368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 14 Feb 2013 15:02:49 -0800 (PST)
Message-ID: <511D6D18.8000205@isi.edu>
Date: Thu, 14 Feb 2013 15:02:48 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: back by popular demand - a DNS calculator
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Feb 2013 23:03:05 -0000

Hi, all,

By popular request, I've restored the DNS calculator function as an
operational service. See:

http://www.isi.edu/touch/tools/dns-calc.html

(this was designed for a Sigcomm OO session, but it's been used several
places as an example why the DNS should NOT be anything more than a
mapping service)

Joe

PS - if you do happen to use it as an example, please do drop me a note;
I'd be very glad to track that info. and/or include a pointer to any
classes that use it.

From mdavids@forfun.net  Thu Feb 14 15:07:11 2013
Return-Path: <mdavids@forfun.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C8D21F885C for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HZJ1MXU5SGYZ for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 15:07:10 -0800 (PST)
Received: from xs.forfun.net (lo.forfun.net [IPv6:2001:980:5270:1:200:ff:fe00:0]) by ietfa.amsl.com (Postfix) with ESMTP id 858A721F8777 for <ietf@ietf.org>; Thu, 14 Feb 2013 15:07:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=forfun.net; s=forfun;  h=Subject:Content-Type:In-Reply-To:References:To:MIME-Version:From:Date:Message-ID; bh=2Frz1E9soCg8XsyC2HzgvtYMaI4WX3nxnZyGjMvg1h0=;  b=bXolEhIgowvOikmfkHUuCKPNIP4VksG5gPqSPe+ciWMt+jst+JYySTIwYm2Jt/ujbAa8+hQ1GiFEUwtdLA+OOzwXGgLEHLXDK3eu3uyfmbqSKQmuXNLiPOPJIiEsDbZD;
Received: from imac2.home.forfun.net ([192.168.68.177] helo=iMac2.local) by xs.forfun.net with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from <mdavids@forfun.net>) id 1U67tR-0005mD-UV for ietf@ietf.org; Fri, 15 Feb 2013 00:07:07 +0100
Message-ID: <511D6E18.2020205@forfun.net>
Date: Fri, 15 Feb 2013 00:07:04 +0100
From: "Marco Davids (Prive)" <mdavids@forfun.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
References: <511D6D18.8000205@isi.edu>
In-Reply-To: <511D6D18.8000205@isi.edu>
X-Enigmail-Version: 1.5
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040200090107050303090400"
X-SA-Exim-Connect-IP: 192.168.68.177
X-SA-Exim-Mail-From: mdavids@forfun.net
Subject: Re: back by popular demand - a DNS calculator
X-SA-Exim-Version: 4.2.1 (built Sun, 08 Jan 2012 03:05:19 +0000)
X-SA-Exim-Scanned: Yes (on xs.forfun.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, 14 Feb 2013 23:07:11 -0000

Dit is een cryptografisch ondertekend bericht in MIME-formaat.

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

Op 15-02-13 00:02, Joe Touch schreef:
>
> By popular request, I've restored the DNS calculator function as an
> operational service. See:
>
> http://www.isi.edu/touch/tools/dns-calc.html

Great! But.... I was hoping it would do DNSSEC by now.

Like Bert's  tool has been doing for ages:

dig 2.3.*.2.+.rp.secret-wg.org TXT +dnssec

http://bert.secret-wg.org/Tools/index.html

;-)

--=20
Marco Davids



--------------ms040200090107050303090400
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME-cryptografische ondertekening

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINNTCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIG+TCCBeGgAwIBAgIDBF+FMA0GCSqGSIb3DQEB
CwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTIwNjEzMDI1MzA4
WhcNMTMwNjE0MDcxNzEzWjBAMRswGQYDVQQDDBJtZGF2aWRzQGZvcmZ1bi5uZXQxITAfBgkq
hkiG9w0BCQEWEm1kYXZpZHNAZm9yZnVuLm5ldDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALB1nukEwsGSGxhXwKQIdr8zo16V1fopU0sAz7kywbMaoZbNml4Bj9HLdi3D9cBR
AabNhwMdiUiVrX0mOK0pO1JFHjeJZb0mWSlImMx1NNBHeSIfB2JicwQ9CJnMqGv44E0wzcW5
gj9ttcXf6z3ODXXKF4/QMWOI1Fson6D62GXx/ox9choiXZeJjlB5qjB9YCYWcEOl+l7KjnHP
r84uJgpUweIK6d6dDUGyjwHkisFWgt+YaqAzEwGrGQXKBYBilBsoOXwL/eTN8pn0Zx1KL6oS
gFUjXKDcLK1WT/DFqqPSp56w94dwjMDH5NK/3xYWH223yANYqU0ouduCzqxvDmkCAwEAAaOC
A60wggOpMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDAdBgNVHQ4EFgQUd6Ftd0An3x9H3Gt9SFx8k2LbZPAwHwYDVR0jBBgwFoAUU3Lt
kpzg2ssBXHx+ljVO8tS4UYIwHQYDVR0RBBYwFIESbWRhdmlkc0Bmb3JmdW4ubmV0MIICIQYD
VR0gBIICGDCCAhQwggIQBgsrBgEEAYG1NwECAjCCAf8wLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3Rh
cnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29t
IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRz
IG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRl
bmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdh
dGlvbnMuMIGcBggrBgEFBQcCAjCBjzAnFiBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhv
cml0eTADAgECGmRMaWFiaWxpdHkgYW5kIHdhcnJhbnRpZXMgYXJlIGxpbWl0ZWQhIFNlZSBz
ZWN0aW9uICJMZWdhbCBhbmQgTGltaXRhdGlvbnMiIG9mIHRoZSBTdGFydENvbSBDQSBwb2xp
Y3kuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNy
bC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0
c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5z
dGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqG
GGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQsFAAOCAQEACwajs94UDysw
TKsikKC+30u5PSUc2fr6ZJbfE+3HTjNksjvrrVfA570zrBWTEuNPXHYKHciAJTaZa51PBngY
LIe6+XZqqtxzXvkPNqjPde9nmDC89oZ291WWtdk1RiI74jwVRtpQ4HuiLL0hFqw+uTQ6KcSa
KEjUFmugbu9/bpf5YWcxXXrUsIi4PB9wsHX9Pt5krTbl97gnlHVobdXruAR9R41hm4Oq5DvC
jBhkwt0ZgHSWCEXgbLRuCKS88UhpJYswbt/rcgRCJJ7zy5+1XIH3E/RcxfzQ5rrQSIRuheGz
qBuVDyqHyl1MuMGFVbpIBBU9SZg8y2jmRsuYJLrfeTGCA90wggPZAgEBMIGUMIGMMQswCQYD
VQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0
YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmlt
YXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwRfhTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG
9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMzAyMTQyMzA3MDRaMCMGCSqG
SIb3DQEJBDEWBBRbqUrcSDIzo9FQDBcr3G9+nD6hQDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCG
SAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqG
SIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1
cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFz
cyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDBF+FMIGnBgsqhkiG9w0BCRAC
CzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMEX4UwDQYJKoZI
hvcNAQEBBQAEggEASQMDRET9U7ybatS0VBk+BQEcMZfZglCfnx01Xbe6SpvlGNVsOu1aWgCp
gV6SACzqWHwwnWBgin03tPoXW0/zBtE/BSIEnrrthDSPJtRCt9lfBxAYWiYkQncPTTLGd7OM
uS79e6/rGoZwuxga/8WrtrloONz6y8plGhfBBMlKCLzGdsv7KyNxHH9grRYTLth6SgbntJru
Hb9QCTMBaXnwLjF4g2t96LAFSl3NjC8+Dvt9ClSFEg11N5/uo6vqxLEbgZBy6hPKZ8Aw/vjE
I3xw+nFXeWK9iyCX3M2fBac1R78u+jS0o/1B8HE3K7ooHJDbU6RLxWUMlQvfFoMsO4/vHQAA
AAAAAA==
--------------ms040200090107050303090400--

From melinda.shore@gmail.com  Thu Feb 14 16:37:23 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7777521F8928 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 16:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.372
X-Spam-Level: 
X-Spam-Status: No, score=-3.372 tagged_above=-999 required=5 tests=[AWL=0.227,  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 Zpme1MbtgkdM for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 16:37:23 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id DE1E321F8920 for <ietf@ietf.org>; Thu, 14 Feb 2013 16:37:22 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so1275608dae.17 for <ietf@ietf.org>; Thu, 14 Feb 2013 16:37:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=tPkShDg6NFSwtpMfW/Aci14AWXuDc53QM9WR42wQA3E=; b=uMSrXXiiN4o2JNBGJXp/0Hl9H4mVwHF2Hkc8/qOtD2a9gd05xOeR/hpwuxPNXjtzIG 09kdEwH7bdZVYQ4AIObt4tVaHYbKA70jCNGnOpdsH+RYKay1EMOG9a04NvEjWKH8NvfD nirMeL0PC3RaiOXpqYNKy9/VK0dry9hCFxDVTMIrPRNrRqlgJhTUOApFhel/6XyXsA++ 6Y2Uch2DAOiD8OhLuYoxRMWIvdYT8kjf4eGePDqKE9hgZzrVS5P5rWvaRYsQCn0uFd2S Vs4uxk2S8nJ4RwgG7kJmvtE0JmNKjWZzIVp+p64/GZkmnnyZ7BWkbCHjolTQ8O+MhmEA 2EQA==
X-Received: by 10.68.254.69 with SMTP id ag5mr1641345pbd.31.1360888642371; Thu, 14 Feb 2013 16:37:22 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id d1sm55195589paz.17.2013.02.14.16.37.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 14 Feb 2013 16:37:21 -0800 (PST)
Message-ID: <511D833F.4080406@gmail.com>
Date: Thu, 14 Feb 2013 15:37:19 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Musing on draft-resnick-on-consensus-01
References: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 00:37:23 -0000

On 2/14/13 2:02 PM, SM wrote:
> The IAB recently had a discussion about "bottom-up organizational
> modes".  If I am not mistaken (please correct me) the IETF is the only
> organization that uses "humming".  I would say that it works in the IETF
> as it is part of the culture; it cannot be grafted on an organization. 
> There are cases when a show of hands can be used.  The sentence that
> follows the quoted text explains when to use "humming".

It seems to me that this kind of misses the point.  Consensus-
based decision making is not simply not voting, but it's processy
and a mechanism for reaching a decision collaboratively.  Unfortunately
it's been the case for a very long time that the IETF does not
actually do that, that participants don't understand what it
means to use "rough consensus" for reaching decisions, working
group chairs often don't understand, IESG members often don't
understand, etc.  So if people in the process tend to see it
as a particular variant on voting, and they're incorrect, it's
probably a mistake to use mechanisms that tend to support the
incorrect view.  Hand raising looks so much like voting that
it's confusing.

> It's not possible to resolve
> an issue if the two sides are not ready to compromise. 

This is probably *the* principal problem in consensus
decision-making.  The participants have to be invested
in making the process work, and in having a mutually
satisfactory outcome.  That's very, very often not the
case in the IETF, and I'm enthusiastic about Pete's draft
as a result - as much about culture transfer as about
process normativity and improvement.

In some sense what's under discussion actually exists in
the IESG, with DISCUSSes being blocking, etc.  The difference,
of course, is that at some level there's an expectation of
altruism from IESG members but not of IETF participants.

There's a huge issue here with education.  And again, kudos to
Pete for taking this on.  It's a very steep hill.

> There are different types of consensus; e.g. the consensus of the girls,
> which is unappealable.

Whut?

Melinda



From stpeter@stpeter.im  Thu Feb 14 19:22:21 2013
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 B58B321F8939 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 19:22:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.592
X-Spam-Level: 
X-Spam-Status: No, score=-102.592 tagged_above=-999 required=5 tests=[AWL=0.007, 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 Fk0WM9bZMFpW for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 19:22:20 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2B621F8938 for <ietf@ietf.org>; Thu, 14 Feb 2013 19:22:20 -0800 (PST)
Received: from [192.168.1.7] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 83DA7406D9; Thu, 14 Feb 2013 20:29:29 -0700 (MST)
Message-ID: <511DA9ED.9040105@stpeter.im>
Date: Thu, 14 Feb 2013 20:22:21 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: jari.arkko@piuha.net
Subject: Re: Last Call: <draft-arkko-iesg-crossarea-02.txt> (Experiences from Cross-Area Work at the IETF) to Informational RFC
References: <20130206234933.11375.20586.idtracker@ietfa.amsl.com>
In-Reply-To: <20130206234933.11375.20586.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.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, 15 Feb 2013 03:22:21 -0000

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

Hi Jari, although I was asked to complete an AppsDir review of this
document, on reading it several times I realized that my feedback is
more personal and less from the Apps Area perspective, so I am sending
a more general message.

On 2/6/13 4:49 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to
> consider the following document: - 'Experiences from Cross-Area
> Work at the IETF' <draft-arkko-iesg-crossarea-02.txt> as
> Informational RFC

Section 3 begins:

   From an IETF participant's point of view, it is important that there
   is a working group where the technical topic that he or she is
   interested in can be discussed.

I'm not convinced that IETF participants really care whether the
institutional machinery of WG formation has been put in place. In my
experience, a fair amount of interesting work has happened outside of
any WG (e.g., Jeff Hodges and I worked on RFC 6125 on a
special-purpose IETF mailing list, not in a WG). As long as there's
some kind of venue, discussion can occur.

A related note on the following sentence in Section 1:

   If the work is
   interesting, the necessary people come to the meetings and work on
   the specifications.

Well, meetings (in the sense of WG sessions, or even IETF meetings)
aren't truly necessary if there is some other appropriate venue available.

IMHO, Section 2 could benefit from examples of cross-area work
involving RAI and Apps. Current and recent WGs include PRECIS (with
involvement from Apps, RAI, Security, and Ops/Mgt), ALTO (straddling
Apps and Transport), OAUTH (straddling Apps and Security), CORE (in
Apps but with close connections to 6lowpan in Int), PAWS (it was an
open question whether it would end up in Apps or Ops/Mgt), and current
efforts to define multi-stream support in MMUSIC, CLUE, and RTCWEB.
The Apps and RAI AD can probably provide further insight here.

In Section 3:

   Cross-area work is needed,
   of course, in any situation where a particular technical problem does
   not cleanly map to one organization.

Is an IETF area truly an "organization"? Isn't the organization here
the IETF?

In Section 4:

      But it
      is also possible that concerns raised in one forum are not
      understood in another, and this can lead to an effort going
      forward after finding the "lowest bar" forum to take it up.

By "forum" you seem to mean "IETF area".

OLD
      Similarly, requests for cross-area review are relatively
      infrequent or sent only to a particular subset of people in an
      area (such as a directorate).
NEW
      Similarly, requests for cross-area review are relatively
      infrequent or sent only to a particular subset of people in an
      area (such as a directorate or related working group).

I tend to agree with Benoit that the scope of, and audience for, the
suggestions in Section 4 are not particularly clear. Unfortunately, I
do not yet have actionable suggestions for improvement.

Peter

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


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

iQIcBAEBAgAGBQJRHantAAoJEOoGpJErxa2pVaQQAJ9KVAlQi0gCB5Y7EI0+D2JR
O0LfIHyoFYQ532iuEvmsmngZfhg3kOYq8VmvsUQJmLs+ipIrOdH8jbJFmmZIHUXv
HwX3E6H+pRpE0b4RLMMBa0qIOZmL0QmaxhkoSTre6OP5x10WT3OrmoBIY/56yiJ5
7TvTjET+MNOj0B6shO6bGzI/q5xUuRkDlP5/d4beD5VMDjXFFkcI6eHoXteVLlel
DxAElJrmRWmpGs9Wqo9YABgdvVDGBUKwqR4ap1+9kIAi68nighu3BWLmBw2nRJXi
eLA5jR7ZMvbVe+KD2hlE/3oG75QvcUNSBo/gh5NS1npPPl+xKng+1xgFus7XrAc0
KHBLuI39HwzHiNuybuLmFsuRlR1/Sxe8vqfK8nNYnddkGEe90a4O+Lq6TXnedDpY
CJgsZnfk9MxAYFoGDKvLeVD5FN7dev0kUe+OdCrn6DlosHMUoOps3dYtMoyviEzv
vx/qijxSIi5dvztWWrEvB816rjSg4KCm67rgfNtIW2YiVyZT0QoLFZdNt2+J6H2w
OaxUYK0A4sE0Zk+eXcXaK2HVo3twG/CGnTYyDI7/u+dEfTNzePxxXHDavT5gQ8jl
/xBDTzyD/2mbh1zeJb2ea6Dv7OYhg1NVj7F8DCaST9lJHdF6eEICBQe9X29X2gHm
NYlQwrYXJ/TIvc2U1Oyd
=cXfj
-----END PGP SIGNATURE-----

From narten@us.ibm.com  Thu Feb 14 21:53:23 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B0021F8C74 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 21:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.216
X-Spam-Level: 
X-Spam-Status: No, score=-110.216 tagged_above=-999 required=5 tests=[AWL=0.383, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cz9WAHCoFjE0 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 21:53:21 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id AF79A21F8530 for <ietf@ietf.org>; Thu, 14 Feb 2013 21:53:08 -0800 (PST)
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, 14 Feb 2013 22:53:08 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 14 Feb 2013 22:53:05 -0700
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id C579819D803E for <ietf@ietf.org>; Thu, 14 Feb 2013 22:53:03 -0700 (MST)
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 r1F5r5RJ263858 for <ietf@ietf.org>; Thu, 14 Feb 2013 22:53:05 -0700
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 r1F5r4oL012357 for <ietf@ietf.org>; Thu, 14 Feb 2013 22:53:04 -0700
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 r1F5r4f0012335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 14 Feb 2013 22:53:04 -0700
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 r1F5r34q005513 for <ietf@ietf.org>; Fri, 15 Feb 2013 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r1F5r2LR005468 for ietf@ietf.org; Fri, 15 Feb 2013 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201302150553.r1F5r2LR005468@rotala.raleigh.ibm.com>
Date: Fri, 15 Feb 2013 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13021505-5406-0000-0000-00000552ADC4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 05:53:23 -0000

Total of 101 messages in the last 7 days.
 
script run at: Fri Feb 15 00:53:02 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 14.85% |   15 | 13.68% |   130635 | abdussalambaryun@gmail.com
  8.91% |    9 |  7.09% |    67750 | sm@resistor.net
  6.93% |    7 |  7.53% |    71897 | ulrich@herberg.name
  1.98% |    2 | 11.39% |   108741 | amancuso@google.com
  4.95% |    5 |  3.39% |    32338 | melinda.shore@gmail.com
  3.96% |    4 |  2.93% |    27951 | moore@network-heretics.com
  2.97% |    3 |  2.89% |    27580 | jari.arkko@piuha.net
  2.97% |    3 |  2.46% |    23500 | barryleiba@computer.org
  2.97% |    3 |  2.01% |    19205 | joelja@bogus.com
  2.97% |    3 |  1.75% |    16737 | dhc@dcrocker.net
  1.98% |    2 |  2.13% |    20377 | ietf@jiaziyi.com
  1.98% |    2 |  2.04% |    19449 | frederick.hirsch@nokia.com
  1.98% |    2 |  1.77% |    16892 | rdroms.ietf@gmail.com
  1.98% |    2 |  1.70% |    16245 | narten@us.ibm.com
  1.98% |    2 |  1.68% |    16058 | brian.e.carpenter@gmail.com
  0.99% |    1 |  2.61% |    24941 | vincent.roca@inria.fr
  1.98% |    2 |  1.54% |    14714 | fred@cisco.com
  1.98% |    2 |  1.50% |    14323 | eburger-l@standardstrack.com
  0.99% |    1 |  2.46% |    23465 | ietf@thomasclausen.org
  1.98% |    2 |  1.40% |    13356 | bob.hinden@gmail.com
  1.98% |    2 |  1.32% |    12620 | worley@ariadne.com
  0.99% |    1 |  1.94% |    18570 | magnus.westerlund@ericsson.com
  0.99% |    1 |  1.59% |    15178 | nabil.n.bitar@verizon.com
  0.99% |    1 |  1.53% |    14599 | bclaise@cisco.com
  0.99% |    1 |  1.41% |    13508 | adrian@olddog.co.uk
  0.99% |    1 |  1.29% |    12308 | ron.even.tlv@gmail.com
  0.99% |    1 |  1.25% |    11951 | hsantos@isdg.net
  0.99% |    1 |  1.25% |    11918 | mdavids@forfun.net
  0.99% |    1 |  1.02% |     9744 | rse@rfc-editor.org
  0.99% |    1 |  0.98% |     9351 | aretana@cisco.com
  0.99% |    1 |  0.90% |     8568 | stpeter@stpeter.im
  0.99% |    1 |  0.88% |     8425 | sob@harvard.edu
  0.99% |    1 |  0.86% |     8194 | jmh@joelhalpern.com
  0.99% |    1 |  0.85% |     8083 | dean.willis@softarmor.com
  0.99% |    1 |  0.82% |     7836 | gtw@gtwassociates.com
  0.99% |    1 |  0.73% |     6941 | d3e3e3@gmail.com
  0.99% |    1 |  0.73% |     6931 | dave@cridland.net
  0.99% |    1 |  0.71% |     6788 | mstjohns@comcast.net
  0.99% |    1 |  0.64% |     6114 | ynir@checkpoint.com
  0.99% |    1 |  0.64% |     6112 | dougb@dougbarton.us
  0.99% |    1 |  0.64% |     6099 | scott@kitterman.com
  0.99% |    1 |  0.64% |     6079 | mcr+ietf@sandelman.ca
  0.99% |    1 |  0.62% |     5941 | john-ietf@jck.com
  0.99% |    1 |  0.60% |     5732 | rbarnes@bbn.com
  0.99% |    1 |  0.60% |     5723 | ned+ietf@mauve.mrochek.com
  0.99% |    1 |  0.56% |     5346 | chair@ietf.org
  0.99% |    1 |  0.55% |     5248 | mrex@sap.com
  0.99% |    1 |  0.52% |     4959 | touch@isi.edu
--------+------+--------+----------+------------------------
100.00% |  101 |100.00% |   955020 | Total


From paf@frobbit.se  Thu Feb 14 23:08:29 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E72921F8552 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 23:08:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MdFgOORksET3 for <ietf@ietfa.amsl.com>; Thu, 14 Feb 2013 23:08:29 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id D6CED21F84FF for <ietf@ietf.org>; Thu, 14 Feb 2013 23:08:28 -0800 (PST)
Received: from [10.1.1.180] (unknown [94.175.239.226]) by mail.frobbit.se (Postfix) with ESMTPSA id CF0F421AA0; Fri, 15 Feb 2013 08:08:27 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: back by popular demand - a DNS calculator
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <511D6E18.2020205@forfun.net>
Date: Fri, 15 Feb 2013 07:08:26 +0000
Content-Transfer-Encoding: 7bit
Message-Id: <D20C9269-28D9-4E6D-BED4-BB06F86F38E1@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>
To: Marco Davids (Prive) <mdavids@forfun.net>
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, 15 Feb 2013 07:08:29 -0000

On 14 feb 2013, at 23:07, Marco Davids (Prive) <mdavids@forfun.net> wrote:

> Great! But.... I was hoping it would do DNSSEC by now.

...how can one otherwise know that 2+3 is 4^H5

   Patrik


From brian.e.carpenter@gmail.com  Fri Feb 15 00:03:04 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C16B121F861F for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 00:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.815
X-Spam-Level: 
X-Spam-Status: No, score=-100.815 tagged_above=-999 required=5 tests=[AWL=0.876, 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 VIwZ99yvcAKl for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 00:03:04 -0800 (PST)
Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) by ietfa.amsl.com (Postfix) with ESMTP id EC94C21F8610 for <ietf@ietf.org>; Fri, 15 Feb 2013 00:03:03 -0800 (PST)
Received: by mail-wi0-f179.google.com with SMTP id ez12so794542wid.6 for <ietf@ietf.org>; Fri, 15 Feb 2013 00:03:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=LMkXT+jn5AJhssosShddfK7WJ355BGAHV+c/qytjmLQ=; b=rLvs1xBecOxwDkaq8cIVGf/LiLf7MrDgSyaB3cgEfziu8ms6Wn1V4NkNNfeOtdk6OD qeZtaiVWAp5XRn7wTPDGX7E5S9sdTeQdY3UWRIwxHLzzeMW449cTYJgfZwtZUTq97Yh4 tbNdR1XZWD3xZi8dLAubgnTUSnQGTX5azcd9xKvIDjI0BfnHEmUWkd3FEenvPNjy1zIz uc9JpSTnal3ZkJ90YEm22T+LTSqMZk5c3yLAds4k12UOar2dq113sqhlnWKP1eIhEe6W j5Sxv2j/gtvQHZ9j+IuImHoNnAITrKYoP+8TXWq+S9UYfliB/1xldtGR8mRqSFvrr9v+ fI8g==
X-Received: by 10.180.85.103 with SMTP id g7mr2303033wiz.29.1360915383120; Fri, 15 Feb 2013 00:03:03 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-220.as13285.net. [2.101.188.220]) by mx.google.com with ESMTPS id t7sm3359274wiy.2.2013.02.15.00.03.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 00:03:02 -0800 (PST)
Message-ID: <511DEBC0.7070800@gmail.com>
Date: Fri, 15 Feb 2013 08:03:12 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu>
In-Reply-To: <511D6D18.8000205@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 08:03:04 -0000

On 14/02/2013 23:02, Joe Touch wrote:
> Hi, all,
> 
> By popular request, I've restored the DNS calculator function as an
> operational service. See:
> 
> http://www.isi.edu/touch/tools/dns-calc.html
> 
> (this was designed for a Sigcomm OO session, but it's been used several
> places as an example why the DNS should NOT be anything more than a
> mapping service)

I suppose people here have already tried traceroute 216.81.59.173

   Brian

> 
> Joe
> 
> PS - if you do happen to use it as an example, please do drop me a note;
> I'd be very glad to track that info. and/or include a pointer to any
> classes that use it.
> 

From bortzmeyer@nic.fr  Fri Feb 15 00:23:11 2013
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 B0BC721F8880 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 00:23:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.111
X-Spam-Level: 
X-Spam-Status: No, score=-101.111 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 tu6UH5YEw4Jl for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 00:23:11 -0800 (PST)
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 334A821F8801 for <ietf@ietf.org>; Fri, 15 Feb 2013 00:23:10 -0800 (PST)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id A90303B5BB; Fri, 15 Feb 2013 08:23:06 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 63E16190AE3; Fri, 15 Feb 2013 09:19:53 +0100 (CET)
Date: Fri, 15 Feb 2013 09:19:53 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Joe Touch <touch@isi.edu>
Subject: Re: back by popular demand - a DNS calculator
Message-ID: <20130215081953.GA27437@sources.org>
References: <511D6D18.8000205@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <511D6D18.8000205@isi.edu>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.6
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 08:23:11 -0000

On Thu, Feb 14, 2013 at 03:02:48PM -0800,
 Joe Touch <touch@isi.edu> wrote 
 a message of 16 lines which said:

> By popular request, I've restored the DNS calculator function as an
> operational service. 

Why no delegation from postel.org? It is not really DNS if you have to
use an explicit name server.


% dig @128.9.160.161 ANY 3.4.add.calc.postel.org


; <<>> DiG 9.7.3 <<>> @128.9.160.161 ANY 3.4.add.calc.postel.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30695
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;3.4.add.calc.postel.org.	IN	ANY

;; AUTHORITY SECTION:
postel.org.		15	IN	SOA	dns.postel.org. touch.postel.org. 2013021402 60 30 1209600 15

;; Query time: 195 msec
;; SERVER: 128.9.160.161#53(128.9.160.161)
;; WHEN: Fri Feb 15 09:19:33 2013
;; MSG SIZE  rcvd: 98


From sm@resistor.net  Fri Feb 15 01:45:10 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B08E21F862D for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 01:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQKcWNX+4Iol for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 01:45:08 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 88E9E21F861B for <ietf@ietf.org>; Fri, 15 Feb 2013 01:45:08 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1F9iwfC021836; Fri, 15 Feb 2013 01:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360921503; bh=iN0xtwpeLZNbBepZ6LiGMuJ3/1vL27LQMyc8fhyC9mc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dTXPi4RgX5a8bKxgU/OIN81f2IrEYVJi/sPkrHh+Lmyo0GYCgLny2fbSwCtXz1bh5 E8k/WAtPolQhWUpa/8AHKCbnICrnHwfKdgnexucPY6b/pQnBHSBMxsonJW+XLosxeD 9FZIbPjsMZjt5S+cNR0P1D0WjMDiCBLsONyc2poI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360921503; i=@resistor.net; bh=iN0xtwpeLZNbBepZ6LiGMuJ3/1vL27LQMyc8fhyC9mc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tz8gX7fpEEB+lOYF/SSxtx6rSVLQ/uR/NdeDdMV9SGLH3Q6HrG+9m2G3FrFXuKHtC 5LWUvKXY4o04zckOLhPniOPrBdmM19lSxNjMaA4WjTdSAdIR8i3rTBFq0krw/DB8lU wiTo8BF5N0WVvsPTGd2WeHc8tjbha0WONt4ViGKc=
Message-Id: <6.2.5.6.2.20130214222030.0b4fe7c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 15 Feb 2013 01:27:28 -0800
To: Melinda Shore <melinda.shore@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Musing on draft-resnick-on-consensus-01
In-Reply-To: <511D833F.4080406@gmail.com>
References: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com> <511D833F.4080406@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 09:45:10 -0000

Hi Melinda,
At 16:37 14-02-2013, Melinda Shore wrote:
>It seems to me that this kind of misses the point.  Consensus-
>based decision making is not simply not voting, but it's processy
>and a mechanism for reaching a decision collaboratively.  Unfortunately

Yes (not including the first sentence).

>it's been the case for a very long time that the IETF does not
>actually do that, that participants don't understand what it
>means to use "rough consensus" for reaching decisions, working
>group chairs often don't understand, IESG members often don't
>understand, etc.  So if people in the process tend to see it
>as a particular variant on voting, and they're incorrect, it's
>probably a mistake to use mechanisms that tend to support the
>incorrect view.  Hand raising looks so much like voting that
>it's confusing.

Consensus-based decision-making is expensive.  The IETF has settled 
for lesser as it is less work for the decision-maker and less work 
for the other side.  The IETF proudly presents:

   We reject: kings, presidents and voting.

   We believe in: rough consensus and running code.

And that created a belief system.

Working groups use polls and "hand raising" nowadays as a disguise 
for voting.  It is understandable (to me) that it confuses 
participants.  One might gain an external view of the IETF by taking 
a look at draft-bollow-ectf-06.

>This is probably *the* principal problem in consensus
>decision-making.  The participants have to be invested
>in making the process work, and in having a mutually
>satisfactory outcome.  That's very, very often not the
>case in the IETF, and I'm enthusiastic about Pete's draft
>as a result - as much about culture transfer as about
>process normativity and improvement.

Agreed.  I like your usage of "mutually satisfactory outcome".

>In some sense what's under discussion actually exists in
>the IESG, with DISCUSSes being blocking, etc.  The difference,
>of course, is that at some level there's an expectation of
>altruism from IESG members but not of IETF participants.

Agreed.

>Whut?

I should have written "not subject to appeal".  It means that the 
appeal will be rejected unless there is a miracle.  In the IETF there 
is, for example, consensus by exhaustion.  A girl explained to me the 
meaning of "consensus of the girls".  I don't know whether it is 
applicable to the IETF.

Here's an unrelated story.  A group of people go out to dinner at a 
fancy restaurant.  There is an implicit understanding that everyone 
shares the bill.  However, after the last course you find out that 
one of the persons in the group does not have any money.  What would 
you do an why (an answer is not expected)?

Consensus is not necessarily about compromise; it can be about 
finding the third way.

Regards,
-sm 


From abdussalambaryun@gmail.com  Fri Feb 15 04:04:11 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 203C021F8628 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 04:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5QyCXAx0Q8q7 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 04:04:10 -0800 (PST)
Received: from mail-we0-x230.google.com (we-in-x0230.1e100.net [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 56DA421F85E8 for <ietf@ietf.org>; Fri, 15 Feb 2013 04:04:10 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id s43so2874685wey.35 for <ietf@ietf.org>; Fri, 15 Feb 2013 04:04:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=LQYE4lQxYKgQSDnCaw5+KmZgtU8/kOX4YzKgZssP1Wc=; b=GcdnzltYQOX3QA2ocQasO241kQfbqwCU0KFKPbeKSEGqYjwhRbZwFs7cCFI5P+k0SK Wzz6aa54fIcZk3x2JbD62AF3kufY0W9dK5XXFVKJDPX1j4HcyaJK4z5tVW19dH4mBZIv qqo3p6oc4L8ayqTERlV9dCOZNms+b84XywQGIE4ShNzOPUZGWOwO7G26xdv+Ev4OvUAC RYcqYgZPoM8WFyB8M4R1qa8L6lp3JgAWh5G3gMh70hSdpOS04nOJUq7LwcCTqtl52Yoz 12rk216RLBicGpSVnDEiRMveZpVa081wfyRGoTwLzvF+dnu9op8wCpjYaTKOBu9dm+1C csQQ==
MIME-Version: 1.0
X-Received: by 10.180.94.69 with SMTP id da5mr5327725wib.30.1360929847821; Fri, 15 Feb 2013 04:04:07 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Fri, 15 Feb 2013 04:04:07 -0800 (PST)
Date: Fri, 15 Feb 2013 13:04:07 +0100
Message-ID: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com>
Subject: Re: Musing on draft-resnick-on-consensus-01
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: SM <sm@resistor.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 12:04:11 -0000

I agree that many don't understand how consensus is targeted. Suggest
that the draft to be more related to participant discussions and
reasonable disputes. However, IMHO, we need first enogh discussions to
get to rough consensus, so the IETF WG Chairs should not ignore any
input only after the *discussions* become repeated/non-productive. If
there are discussions, then we should postpone the call for consensus,

AB

On 2/14/13 2:02 PM, SM wrote:
> The IAB recently had a discussion about "bottom-up organizational
> modes".  If I am not mistaken (please correct me) the IETF is the only
> organization that uses "humming".  I would say that it works in the IETF
> as it is part of the culture; it cannot be grafted on an organization.
> There are cases when a show of hands can be used.  The sentence that
> follows the quoted text explains when to use "humming".

It seems to me that this kind of misses the point.  Consensus-
based decision making is not simply not voting, but it's processy
and a mechanism for reaching a decision collaboratively.  Unfortunately
it's been the case for a very long time that the IETF does not
actually do that, that participants don't understand what it
means to use "rough consensus" for reaching decisions, working
group chairs often don't understand, IESG members often don't
understand, etc.  So if people in the process tend to see it
as a particular variant on voting, and they're incorrect, it's
probably a mistake to use mechanisms that tend to support the
incorrect view.  Hand raising looks so much like voting that
it's confusing.

> It's not possible to resolve
> an issue if the two sides are not ready to compromise.

This is probably *the* principal problem in consensus
decision-making.  The participants have to be invested
in making the process work, and in having a mutually
satisfactory outcome.  That's very, very often not the
case in the IETF, and I'm enthusiastic about Pete's draft
as a result - as much about culture transfer as about
process normativity and improvement.

In some sense what's under discussion actually exists in
the IESG, with DISCUSSes being blocking, etc.  The difference,
of course, is that at some level there's an expectation of
altruism from IESG members but not of IETF participants.

There's a huge issue here with education.  And again, kudos to
Pete for taking this on.  It's a very steep hill.

> There are different types of consensus; e.g. the consensus of the girls,
> which is unappealable.

Whut?

Melinda

From melinda.shore@gmail.com  Fri Feb 15 07:51:32 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EB2D21F88BE for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 07:51:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.383
X-Spam-Level: 
X-Spam-Status: No, score=-3.383 tagged_above=-999 required=5 tests=[AWL=0.216,  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 OoyUiu62W7Bb for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 07:51:31 -0800 (PST)
Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8A32821F88BD for <ietf@ietf.org>; Fri, 15 Feb 2013 07:51:30 -0800 (PST)
Received: by mail-pb0-f48.google.com with SMTP id wy12so654612pbc.21 for <ietf@ietf.org>; Fri, 15 Feb 2013 07:51:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m7PFjE0UfCL3vqisJ9E7Tx1qbN6hRSoNrbRzjKSymhg=; b=S3QCH8D9VbZ02I0KI1rGk+Ny01OX/fQPoKFgnZkJIXPVeWMHzDLI/hJZqFi77xbKdx IMbKLXsE/uIpIqytEk91Ijg/F1WszSW1yMkJ6262SK5hBcxIUe5E2WF6jtYPze9EfCuK 8tINpPhYbnvUw+mLpYn3VaXqXHdB8jGXjgrI5qVXRr/7h2lYp8+186WwlihTEjr8bRqz tHbQ2/XFSPrug1SocfHUXCQfrbv8ms9YSGFCoo6IJowc+BzItVPPZRHz9FcHU2rdPo7I Bwyg3cXOrnDIkrRmY7UVt6hRrhAJFJ1mCp/4LJeaOSeJ8oaP2TQoVscFPYBGX6HRa/YR 8ehA==
X-Received: by 10.68.225.166 with SMTP id rl6mr7070125pbc.91.1360943489460; Fri, 15 Feb 2013 07:51:29 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id s9sm10701231pav.7.2013.02.15.07.51.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 07:51:28 -0800 (PST)
Message-ID: <511E597E.2090102@gmail.com>
Date: Fri, 15 Feb 2013 06:51:26 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: Musing on draft-resnick-on-consensus-01
References: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com>
In-Reply-To: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 15:51:33 -0000

On 2/15/13 3:04 AM, Abdussalam Baryun wrote:
> I agree that many don't understand how consensus is targeted. Suggest
> that the draft to be more related to participant discussions and
> reasonable disputes. 

Absolutely not.

Melinda



From randy@psg.com  Fri Feb 15 08:22:07 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A69D721F8824 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nzxbRMhEtnSg for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:22:06 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 1827E21F88C1 for <ietf@ietf.org>; Fri, 15 Feb 2013 08:22:06 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1U6O2z-0005as-PA; Fri, 15 Feb 2013 16:22:02 +0000
Date: Sat, 16 Feb 2013 01:22:00 +0900
Message-ID: <m2hald5yzb.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Musing on draft-resnick-on-consensus-01
In-Reply-To: <511E597E.2090102@gmail.com>
References: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com> <511E597E.2090102@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: SM <sm@resistor.net>, IETF Disgust <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 16:22:07 -0000

my take is that we have advanced to that stage of organizational life
where we have newcomers who, when faced with a new culture with subtle
process, are led by personal and/or cultural background to assert that
the process should be changed to a model which they already understand,
and for it to be documented in triplicate.  rightly or wrongly, for
historical and left coast cultural reasons, the ietf culture is more to
watch, listen, learn, and *contribute technically*.  thanks, melinda,
for having the patience to try and educate.

randy

From melinda.shore@gmail.com  Fri Feb 15 08:26:03 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6890021F88FC for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:26:03 -0800 (PST)
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 g+JNz2kWq6yZ for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:26:02 -0800 (PST)
Received: from mail-da0-f46.google.com (mail-da0-f46.google.com [209.85.210.46]) by ietfa.amsl.com (Postfix) with ESMTP id 6575A21F88E3 for <ietf@ietf.org>; Fri, 15 Feb 2013 08:26:02 -0800 (PST)
Received: by mail-da0-f46.google.com with SMTP id p5so1534445dak.33 for <ietf@ietf.org>; Fri, 15 Feb 2013 08:26:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=j+4ymR9RshcZmft/Y2DaqSMEdUMzPAfJtwMiRySbNhE=; b=c12qrmFm3E6acEcjYF+h1VJGbLgsxdj58fLTKzrXVuk3TXOvrmLpjwIAQXwKNOzbX7 yL8Um4nkJG0XjFZKoyZ26FyNh4XLUkMmuaqW0MiS6ImsUghJkgFbdYpUm/4HmlfCuaEd IJ7QwD60hlWVk224aY0dfjS0kBCmudOqbbo0H9S8YWmxNE+bCQE3UVPXlWtYOLWYoRmH 4ryk/S/ZPsp1S3UBFqxOaGSFf47CkZ7oO8SLMzbyfACKyGfaoY/BH9y6nCmmh2UfA15q a07VhS0j6koqGkviU3Bcg1hBI2l3mJ6kSk1zcyqHNtfHnUJ3ZAuA+RqoweYtGR1P1A1B cm6g==
X-Received: by 10.66.83.196 with SMTP id s4mr13941443pay.74.1360945562016; Fri, 15 Feb 2013 08:26:02 -0800 (PST)
Received: from spandex.local (216-67-48-121-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.48.121]) by mx.google.com with ESMTPS id eh5sm5160858pbc.44.2013.02.15.08.26.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 15 Feb 2013 08:26:01 -0800 (PST)
Message-ID: <511E6196.4090103@gmail.com>
Date: Fri, 15 Feb 2013 07:25:58 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Musing on draft-resnick-on-consensus-01
References: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com> <511E597E.2090102@gmail.com> <m2hald5yzb.wl%randy@psg.com>
In-Reply-To: <m2hald5yzb.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, IETF Disgust <ietf@ietf.org>, Abdussalam Baryun <abdussalambaryun@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 16:26:03 -0000

On 2/15/13 7:22 AM, Randy Bush wrote:
> thanks, melinda,
> for having the patience to try and educate.

I have to apologize for being sleep-deprived and short (well, not
*short* short).  I think that so far the discussion has been
productive and I would really hate to see it derailed.  As nearly
as I can tell the only serious flaw with this document is that it's
quite overdue, and I'm very, very pleased that we're finally having
this discussion.

Melinda



From presnick@qti.qualcomm.com  Fri Feb 15 08:52:00 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6D921F87CA for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:52:00 -0800 (PST)
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 KnQIo2wzlVxM for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 08:51:59 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1568D21F851C for <ietf@ietf.org>; Fri, 15 Feb 2013 08:51:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1360947119; x=1392483119; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=vZiWvdV64pCuZqODGXLFJzbQk97Pd2MJfB0KsKxNo60=; b=gcPbVo6J/COiAOkFMFg61QLQg9ftgcUQWaHcLd2DsnMb9q2SBNbX1Slo 8FjvAMaf7M3IEWtHQ8ZVRsx06ZQRJ5FbLoSJ+QMytkTcWyv1GBGRDlSbe 00xmWAzwsmqLNzQqYqvu5SkCftc5tDMfs1bX0AHGv4JDfQtwMGigMomQb o=;
X-IronPort-AV: E=Sophos;i="4.84,674,1355126400"; d="scan'208";a="23163802"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth01.qualcomm.com with ESMTP; 15 Feb 2013 08:51:58 -0800
X-IronPort-AV: E=Sophos;i="4.84,674,1355126400"; d="scan'208";a="431948432"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 Feb 2013 08:51:58 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.4; Fri, 15 Feb 2013 08:51:58 -0800
Message-ID: <511E67AB.10707@qti.qualcomm.com>
Date: Fri, 15 Feb 2013 10:51:55 -0600
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: SM <sm@resistor.net>
Subject: Re: Musing on draft-resnick-on-consensus-01
References: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com>
In-Reply-To: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 16:52:00 -0000

Just to level set: I had not really intended for this document to be 
discussed on the IETF general list quite yet. It still has quite a few 
gaping holes. So even though it is posted as an I-D, I'm inclined to 
have people send comments to me individually for the time being. If and 
when I think it is ready for wide-ranging discussion, I'll be sure to 
solicit comments here. If you do insist on discussing it here, 
understand that sometimes the answer will be, "Yep; gotta think about 
that. Not done yet."

Also note the disclaimer in the document:

       Note: This document contains the musings of an individual.  Right
       now, it is just some rough notes and has lots of holes that need
       to be filled in.  Even if those holes are filled, in its current
       form, it is not intended to be published as an RFC, let alone
       being a BCP for a change of IETF policy.  If it evolves into such
       a thing, great.  If it simply sparks discussion as an Internet
       Draft, that's a perfectly fine outcome.

That said, I'll answer some of SM's comments publicly since he posted 
publicly:

On 2/14/13 5:02 PM, SM wrote:

> The above is about working group consensus.  I suggest adding some 
> text in the Introduction Section which mentions that it is about 
> that.  The "We only require rough consensus" can be misunderstood as 
> being the bar in an IETF-wide call.

No, "We only require rough consensus" *is* the bar in an IETF-wide call. 
If I need to make that clearer in the document, I shall. We use exactly 
the same decision criteria for working groups and for the IETF writ-large.

> The IAB recently had a discussion about "bottom-up organizational 
> modes".  If I am not mistaken (please correct me) the IETF is the only 
> organization that uses "humming".  I would say that it works in the 
> IETF as it is part of the culture; it cannot be grafted on an 
> organization. There are cases when a show of hands can be used.  The 
> sentence that follows the quoted text explains when to use "humming". 

Melinda addressed this quite well. "Humming" is simply a practice meant 
to reinforce that we use consensus rather than voting as our basis for 
decision making. But as the document says, it is possible to "hum" when 
what you are really doing is voting, and it is possible to use a show of 
hands to help guide consensus. (See section 4, paragraph 4.) The 
practice of humming is not *really* what's important; it's getting 
consensus and not allowing majority rule. Another organization could 
adopt humming *if* it was interested in consensus-based decision making.

>   "The key is to separate those choices that are simply unappealing
>    from those that are truly problematic."
>
> I leave it to you to see whether you want to use the following:

Thanks. One of the big holes I haven't attempted to fill is more 
specific practical advice. That might serve usefully.

> I read "compromise" as something intermediate between two things.  
> Consensus is used for conflict resolution.  It's not possible to 
> resolve an issue if the two sides are not ready to compromise.  If you 
> have two sides you end up with a King Solomon scenario.  It is very 
> difficult to resolve the issue then.  Maybe "conciliatory" may be a 
> better term to express the idea (see text quoted above).

Yes, a couple of people have brought up this section, and I will need to 
expand. The main point is that neither "giving up" (i.e., believing that 
an issue is a real problem, but no longer being willing to discuss it) 
nor "horse trading" (i.e., "I'll let you put your broken thing in the 
document if you let me put my thing into the document that you think is 
broken") is coming to consensus. "Giving up" and "horse trading" are 
failures of consensus. (I distinguish "giving up" from "deciding that 
the document has made a good engineering tradeoff" and "horse trading" 
from "discovering common ground", the latter of which in each case are 
*good* things.) I have to figure out how to make that point more clearly.

> The draft uses "objection" and "objector" in discussing about 
> consensus.  That works in a formal or legalistic context.  In an IETF 
> context you end up being the person standing out as you raised an 
> objection.  Arguments do not have to be for or against (objection).  
> It's difficult for me to find the words to explain this.  I see that 
> you used the word "concerns" in Section 4.

Note the title of section 2. Figuring out the objections is the 
important part of coming to consensus. "Thoughts" or "concerns" are 
often distracting to figuring out consensus. I'll try to explicate in 
the document.

> In Section 3:
>
>   "If the chair finds, in their technical judgement, that the issue
>    has truly been considered, and that the vast majority of the working"
>
> Is it "technical judgement" or "the technical issue has been 
> considered"?  For the former, the chair ends up taking a technical 
> decision.  For the latter, the chair only has to use judgement.

I really meant "technical judgement". This is one of the trickiest bits 
of *rough* consensus. There are times where a chair is truly going to 
have to use their technical judgement to figure out whether the WG has 
truly addressed an outstanding issue that someone maintains is still a 
problem. This is hard. And it requires the good faith of the chair, and 
the trust of *all* of the participants (including the person(s) who end 
up in the rough). And it's where appeals can happen. And it's a 
cornerstone of how rough consensus works. More text necessary.

> RFC 3929 broaches consensus from a different angle.

Quite. 3929 is much more about practical advice. I am likely to get to 
some of that (and will cite/incorporate from 3929 as I can when I do 
so). But mine is more of a "getting our minds around the issue" 
document. And there are certain things in 3929 that I think are serious 
points of disagreement (on the theory) between Ted and I. Those I'll 
also likely need to address.

> Rough consensus is the lesser barrier when consensus is not possible.

That's not quite right. See the discussion re: chair's judgement above. 
When the consensus is rough, it is much more precarious and much harder 
to determine. It's not a lesser barrier; majority rule would be a lesser 
barrier. I'll have to find some words to express this.

> Lack of disagreement can also be a sign that the working group has not 
> carefully considered the question.

That goes back to the "everyone working in good faith" premise. If a 
working group has not carefully considered a question, that's a failure 
across a huge number of people, from participants up through the IESG.

Thank you for your comments.

pr

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


From touch@isi.edu  Fri Feb 15 09:05:36 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136F221F87DC for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.829
X-Spam-Level: 
X-Spam-Status: No, score=-102.829 tagged_above=-999 required=5 tests=[AWL=-0.230, 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 78LAkmcdfzFL for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:05:35 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB9721F856F for <ietf@ietf.org>; Fri, 15 Feb 2013 09:05:35 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r1FH5AUF021503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Feb 2013 09:05:13 -0800 (PST)
Message-ID: <511E6AC5.9050303@isi.edu>
Date: Fri, 15 Feb 2013 09:05:09 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <20130215081953.GA27437@sources.org>
In-Reply-To: <20130215081953.GA27437@sources.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 17:05:36 -0000

On 2/15/2013 12:19 AM, Stephane Bortzmeyer wrote:
> On Thu, Feb 14, 2013 at 03:02:48PM -0800,
>   Joe Touch <touch@isi.edu> wrote
>   a message of 16 lines which said:
>
>> By popular request, I've restored the DNS calculator function as an
>> operational service.
>
> Why no delegation from postel.org? It is not really DNS if you have to
> use an explicit name server.

I don't follow your logic.

FYI, postel.org entries are hosted on a "hidden master" DNS server 
inside the postel.org domain on a research host. The public masters for 
that domain are hosted elsewhere on production machines.

The response you got below is because the public masters hadn't caught 
up. I'm checking on why that hasn't happened, but in the meantime (as 
per the web page) you can go directly to the hidden master:

dig @dns.postel.org ANY 3.4.add.calc.postel.org

Joe

>
> % dig @128.9.160.161 ANY 3.4.add.calc.postel.org
>
>
> ; <<>> DiG 9.7.3 <<>> @128.9.160.161 ANY 3.4.add.calc.postel.org
> ; (1 server found)
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30695
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
> ;; WARNING: recursion requested but not available
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags: do; udp: 4096
> ;; QUESTION SECTION:
> ;3.4.add.calc.postel.org.	IN	ANY
>
> ;; AUTHORITY SECTION:
> postel.org.		15	IN	SOA	dns.postel.org. touch.postel.org. 2013021402 60 30 1209600 15
>
> ;; Query time: 195 msec
> ;; SERVER: 128.9.160.161#53(128.9.160.161)
> ;; WHEN: Fri Feb 15 09:19:33 2013
> ;; MSG SIZE  rcvd: 98
>

From touch@isi.edu  Fri Feb 15 09:19:27 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58D2D21F88D1 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.82
X-Spam-Level: 
X-Spam-Status: No, score=-102.82 tagged_above=-999 required=5 tests=[AWL=-0.221, 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 5JdBg8sTZflG for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:19:26 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5DE4421F856E for <ietf@ietf.org>; Fri, 15 Feb 2013 09:19:26 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r1FHJ25u025953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Feb 2013 09:19:03 -0800 (PST)
Message-ID: <511E6E05.9040302@isi.edu>
Date: Fri, 15 Feb 2013 09:19:01 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Marco Davids (Prive)" <mdavids@forfun.net>
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>
In-Reply-To: <511D6E18.2020205@forfun.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 17:19:27 -0000

On 2/14/2013 3:07 PM, Marco Davids (Prive) wrote:
> Op 15-02-13 00:02, Joe Touch schreef:
>>
>> By popular request, I've restored the DNS calculator function as an
>> operational service. See:
>>
>> http://www.isi.edu/touch/tools/dns-calc.html
>
> Great! But.... I was hoping it would do DNSSEC by now.
>
> Like Bert's  tool has been doing for ages:
>
> dig 2.3.*.2.+.rp.secret-wg.org TXT +dnssec
>
> http://bert.secret-wg.org/Tools/index.html

I'd be glad to know how long that's been up (mine was posted in 2001 for 
the Sigcomm OO session). AFAICT, that web page was put up in 2003, but 
I'd be glad to hear otherwise.

Some key differences, FWIW:

	- my variant returns the response as an IP address,
	rather than inside a TXT record (there's a point to
	that, as per the OO slides posted on the page above)

	- the Bert version uses DNS strings that aren't valid
	(*, +, ',', ++)

	- my variant has a static number of entries (40,003).
	That's intentional to avoid potential impact on
	DNS caches.

Joe

From hsantos@isdg.net  Fri Feb 15 09:38:53 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71B5621F86B1 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:38:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level: 
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5 tests=[AWL=0.359, 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 rAp1pRJnhtP7 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:38:52 -0800 (PST)
Received: from ntbbs.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C875B21F8691 for <ietf@ietf.org>; Fri, 15 Feb 2013 09:38:51 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=8354; t=1360949929; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=R6xrUSt UwfbNltDZ1HzcjlDPARg=; b=MKs/YXYzpRh+LJAn77JYRVE+asjoPr7BPUVrltk v2w2AX3vuvESGACHFpy1GPxSe2i0tx+utgOHYpevakgqpvfCFx1LOdELcEUCZN7o LK9YTXo6eAB/H/JHEzfJsE1jBDkWWKfy7fhFZGJ23tuzB8942DnJcAyOYpAeuj8y HMgU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 15 Feb 2013 12:38:49 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4086651283.32570.3336; Fri, 15 Feb 2013 12:38:48 -0500
Message-ID: <511E723A.9000300@isdg.net>
Date: Fri, 15 Feb 2013 12:36:58 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>,  SM <sm@resistor.net>
Subject: Re: Musing on draft-resnick-on-consensus-01
References: <6.2.5.6.2.20130214115531.0aaeb968@elandnews.com> <511E67AB.10707@qti.qualcomm.com>
In-Reply-To: <511E67AB.10707@qti.qualcomm.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: Fri, 15 Feb 2013 17:38:53 -0000

Not to oversimplify the problem or the pursuit for a solution, I think 
there are some possible simple, but perhaps not practical, solutions to 
the concerns you cite.

- Faster Reviews, Resolutions by external people, i.e. IESG or a new 
technical review group specifically for this purpose.  When the WG 
itself is at a impasse, the AD should be able to resolve it, but not 
always there too, due to the issue below.

- IETF needs to recruit more leaders, not overload existing ones. IMO, 
we have fewer leaders responsible for wider cross areas.  This is good 
for proper integration and management but without experience, there 
could be a lost of synergism, diverse engineering insights.  Singular 
mindsets and philosophies can and do emerge (perhaps just with aging).

Currently, I think the system is designed for appeals to occur. When 
apathy develops, lack of confidence in the work, the threats of appeals 
are the last efforts for corrections.   Its no wonder you see new 
process pressures to produce ideas to circumvent them, i.e. fast 
tracking, filtering or watering down concerns, even using tools to 
excommunicate (moderate, block) participants, etc.

Overall, I think more diversity needed, not less.   These actions can 
help with minimizing potential conflicts.  (Note, this is not suggesting 
your ideas is not about diversity).

--
HLS

On 2/15/2013 11:51 AM, Pete Resnick wrote:
> Just to level set: I had not really intended for this document to be 
> discussed on the IETF general list quite yet. It still has quite a few 
> gaping holes. So even though it is posted as an I-D, I'm inclined to 
> have people send comments to me individually for the time being. If 
> and when I think it is ready for wide-ranging discussion, I'll be sure 
> to solicit comments here. If you do insist on discussing it here, 
> understand that sometimes the answer will be, "Yep; gotta think about 
> that. Not done yet."
>
> Also note the disclaimer in the document:
>
>       Note: This document contains the musings of an individual. Right
>       now, it is just some rough notes and has lots of holes that need
>       to be filled in.  Even if those holes are filled, in its current
>       form, it is not intended to be published as an RFC, let alone
>       being a BCP for a change of IETF policy.  If it evolves into such
>       a thing, great.  If it simply sparks discussion as an Internet
>       Draft, that's a perfectly fine outcome.
>
> That said, I'll answer some of SM's comments publicly since he posted 
> publicly:
>
> On 2/14/13 5:02 PM, SM wrote:
>
>> The above is about working group consensus.  I suggest adding some 
>> text in the Introduction Section which mentions that it is about 
>> that.  The "We only require rough consensus" can be misunderstood as 
>> being the bar in an IETF-wide call.
>
> No, "We only require rough consensus" *is* the bar in an IETF-wide 
> call. If I need to make that clearer in the document, I shall. We use 
> exactly the same decision criteria for working groups and for the IETF 
> writ-large.
>
>> The IAB recently had a discussion about "bottom-up organizational 
>> modes".  If I am not mistaken (please correct me) the IETF is the 
>> only organization that uses "humming".  I would say that it works in 
>> the IETF as it is part of the culture; it cannot be grafted on an 
>> organization. There are cases when a show of hands can be used.  The 
>> sentence that follows the quoted text explains when to use "humming". 
>
> Melinda addressed this quite well. "Humming" is simply a practice 
> meant to reinforce that we use consensus rather than voting as our 
> basis for decision making. But as the document says, it is possible to 
> "hum" when what you are really doing is voting, and it is possible to 
> use a show of hands to help guide consensus. (See section 4, paragraph 
> 4.) The practice of humming is not *really* what's important; it's 
> getting consensus and not allowing majority rule. Another organization 
> could adopt humming *if* it was interested in consensus-based decision 
> making.
>
>>   "The key is to separate those choices that are simply unappealing
>>    from those that are truly problematic."
>>
>> I leave it to you to see whether you want to use the following:
>
> Thanks. One of the big holes I haven't attempted to fill is more 
> specific practical advice. That might serve usefully.
>
>> I read "compromise" as something intermediate between two things.  
>> Consensus is used for conflict resolution.  It's not possible to 
>> resolve an issue if the two sides are not ready to compromise.  If 
>> you have two sides you end up with a King Solomon scenario.  It is 
>> very difficult to resolve the issue then.  Maybe "conciliatory" may 
>> be a better term to express the idea (see text quoted above).
>
> Yes, a couple of people have brought up this section, and I will need 
> to expand. The main point is that neither "giving up" (i.e., believing 
> that an issue is a real problem, but no longer being willing to 
> discuss it) nor "horse trading" (i.e., "I'll let you put your broken 
> thing in the document if you let me put my thing into the document 
> that you think is broken") is coming to consensus. "Giving up" and 
> "horse trading" are failures of consensus. (I distinguish "giving up" 
> from "deciding that the document has made a good engineering tradeoff" 
> and "horse trading" from "discovering common ground", the latter of 
> which in each case are *good* things.) I have to figure out how to 
> make that point more clearly.
>
>> The draft uses "objection" and "objector" in discussing about 
>> consensus.  That works in a formal or legalistic context.  In an IETF 
>> context you end up being the person standing out as you raised an 
>> objection.  Arguments do not have to be for or against (objection).  
>> It's difficult for me to find the words to explain this.  I see that 
>> you used the word "concerns" in Section 4.
>
> Note the title of section 2. Figuring out the objections is the 
> important part of coming to consensus. "Thoughts" or "concerns" are 
> often distracting to figuring out consensus. I'll try to explicate in 
> the document.
>
>> In Section 3:
>>
>>   "If the chair finds, in their technical judgement, that the issue
>>    has truly been considered, and that the vast majority of the working"
>>
>> Is it "technical judgement" or "the technical issue has been 
>> considered"?  For the former, the chair ends up taking a technical 
>> decision.  For the latter, the chair only has to use judgement.
>
> I really meant "technical judgement". This is one of the trickiest 
> bits of *rough* consensus. There are times where a chair is truly 
> going to have to use their technical judgement to figure out whether 
> the WG has truly addressed an outstanding issue that someone maintains 
> is still a problem. This is hard. And it requires the good faith of 
> the chair, and the trust of *all* of the participants (including the 
> person(s) who end up in the rough). And it's where appeals can happen. 
> And it's a cornerstone of how rough consensus works. More text necessary.
>
>> RFC 3929 broaches consensus from a different angle.
>
> Quite. 3929 is much more about practical advice. I am likely to get to 
> some of that (and will cite/incorporate from 3929 as I can when I do 
> so). But mine is more of a "getting our minds around the issue" 
> document. And there are certain things in 3929 that I think are 
> serious points of disagreement (on the theory) between Ted and I. 
> Those I'll also likely need to address.
>
>> Rough consensus is the lesser barrier when consensus is not possible.
>
> That's not quite right. See the discussion re: chair's judgement 
> above. When the consensus is rough, it is much more precarious and 
> much harder to determine. It's not a lesser barrier; majority rule 
> would be a lesser barrier. I'll have to find some words to express this.
>
>> Lack of disagreement can also be a sign that the working group has 
>> not carefully considered the question.
>
> That goes back to the "everyone working in good faith" premise. If a 
> working group has not carefully considered a question, that's a 
> failure across a huge number of people, from participants up through 
> the IESG.
>
> Thank you for your comments.
>
> pr
>



From wesley.george@twcable.com  Fri Feb 15 09:46:42 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852D121F878F for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.028
X-Spam-Level: 
X-Spam-Status: No, score=-1.028 tagged_above=-999 required=5 tests=[AWL=0.435,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 eC6XUfm0i7pp for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 09:46:42 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 0683421F877B for <ietf@ietf.org>; Fri, 15 Feb 2013 09:46:41 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,674,1355115600"; d="scan'208";a="28220123"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 15 Feb 2013 12:46:40 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Fri, 15 Feb 2013 12:46:41 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 15 Feb 2013 12:46:41 -0500
Subject: RE: presenting vs discussion in WG meetings (was re:Remote Participation Services)
Thread-Topic: presenting vs discussion in WG meetings (was re:Remote Participation Services)
Thread-Index: Ac4LpGgRGu+8L4AKSuKDPT5vqyIpGw==
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 17:46:42 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Dave Crocker
> Sent: Tuesday, February 12, 2013 12:06 PM
> To: ietf@ietf.org
> Subject: Re: Remote Participation Services
>

[WEG] changed subject line to reflect actual topic
>
>
> If a meeting has good structure, management and content, the presence or
> absence of slides doesn't matter.
>

[WEG] Perhaps it would be helpful to make an informal recommendation to WG =
chairs (via the wiki, for example) that generally they should carve each re=
quest for agenda time roughly in half, with a hard limit of $speaker_time/2=
 devoted to "presenting" or otherwise framing the discussion and the remain=
ing time devoted to open mic discussion. Likely this will result in present=
ers asking for 2x their previous time, but at least it will be a more reali=
stic method to plan out time during a meeting and reduce the instances wher=
e the WG will be running short of time for meaningful discussion if the pre=
senter (or WG chair) isn't good at managing the available time and spends t=
he whole allocation reading slides to the people in attendance.

Wes George

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

From internet-drafts@ietf.org  Fri Feb 15 10:43:21 2013
Return-Path: <internet-drafts@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 D252421F8821; Fri, 15 Feb 2013 10:43:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 FGrwiGkBWLc9; Fri, 15 Feb 2013 10:43:21 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC9E21F878F; Fri, 15 Feb 2013 10:43:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Internet-Drafts Administrator <internet-drafts@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Internet Draft Initial Version (-00) Cut-Off Monday, February 18
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130215184321.8607.90539.idtracker@ietfa.amsl.com>
Date: Fri, 15 Feb 2013 10:43:21 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 18:43:22 -0000

This is a reminder that the Internet Draft Initial Version (-00) cut- =

off is this coming Monday, February 18th, 2013. Please note that, because  =

the AMS office is closed this Monday, manual submissions will not be  =

processed until Tuesday, February 19th.

All Initial Version (-00) submissions are due by UTC 24:00.

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/submit/

The Internet-Draft cutoff dates as well as other significant dates for =

IETF 86 can be found at: =

https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86

Thank you for your understanding and cooperation. If you have any =

questions or concerns please send a message to =

internet-drafts@ietf.org.

From moore@network-heretics.com  Fri Feb 15 12:57:04 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6A121F8692 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 12:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.366
X-Spam-Level: 
X-Spam-Status: No, score=-3.366 tagged_above=-999 required=5 tests=[AWL=0.233,  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 Crkt-UnXxqYu for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 12:57:03 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9595921F8686 for <ietf@ietf.org>; Fri, 15 Feb 2013 12:57:03 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 5275C20964 for <ietf@ietf.org>; Fri, 15 Feb 2013 15:57:03 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute2.internal (MEProxy); Fri, 15 Feb 2013 15:57:03 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=fDjf7hCjXtd3aDMVt7PEyX BZJ94=; b=jN/Qk0xoxgA0Ao7cEYKAGI/ZSIPaFK8BYQQe6NWNGAk/HjSqy5aag8 puHrufJojr4pgYebR5vGbU2bRwSvKsavji8l5it+v87JTmnh+s39UxRtiqhjeLOk tp2Fu37REgi+HE63HliHOzb7XW/Alp+ak48+2Lyr5fNw6dpNH38Hc=
X-Sasl-enc: MyfSPV9vaF/XFkLMOiy+rTe2Njw6LpaobPX1SEDPGzPu 1360961822
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 743418E01CD; Fri, 15 Feb 2013 15:57:02 -0500 (EST)
Message-ID: <511EA11D.7010700@network-heretics.com>
Date: Fri, 15 Feb 2013 15:57:01 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.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: Fri, 15 Feb 2013 20:57:04 -0000

On 02/15/2013 12:46 PM, George, Wes wrote:
> [WEG] Perhaps it would be helpful to make an informal recommendation to WG chairs (via the wiki, for example) that generally they should carve each request for agenda time roughly in half, with a hard limit of $speaker_time/2 devoted to "presenting" or otherwise framing the discussion and the remaining time devoted to open mic discussion. Likely this will result in presenters asking for 2x their previous time, but at least it will be a more realistic method to plan out time during a meeting and reduce the instances where the WG will be running short of time for meaningful discussion if the presenter (or WG chair) isn't good at managing the available time and spends the whole allocation reading slides to the people in attendance.
I actually don't think a hard limit is a good idea.  WGs need more 
presentation time in their early phases.

But this makes me realize that there's a related issue.   An expectation 
that WG meetings are for presentations, leads to an expectation that 
there's lots of opportunity to present suggestions for new work to do.   
WG time scheduled for considering new work can actually take away time 
for discussion of ongoing work.   And once the time is scheduled and 
people have made commitments to travel to meetings for the purpose of 
presenting new work, chairs are understandably reluctant to deny them 
their allotted presentation time.

(It seems like every time I attend an IETF there are numerous WG 
meetings with schedules full of presentations for new work that are 
hardly even listened to, and that those presentations crowd out 
discussion of ongoing work.   When the alloted time for such discussion 
has elapsed, the chair will sigh and say "ok, let's take that to the 
mailing list".)

I suggest that ongoing work should nearly always take precedence over 
consideration of new work, particularly for new work that's not fairly 
close to the current scope of the WG's charter.

It follows that chairs probably shouldn't schedule all of their allotted 
meeting time by filling otherwise unused time with presentations of 
proposals for new work.   The amount of time required for discussion is 
difficult to predict, and often runs over that anticipated.  A better 
strategy might be this:  List the major issues that need to be sorted 
out in face-to-face discussion, probably in order of importance (how 
much is this particular issue blocking WG progress on its chartered 
goals?) combined with some sense of how likely the group is to make 
progress.   Allot maybe 5 minutes for each topic for presentation time 
(introduction of the discussion), to be followed by the actual 
discussion.   Each discussion gets cut off after some pre-determined 
amount of time, or when the chair determines that it's unlikely to 
produce any useful progress.

If there's time left over after everything has been discussed, and the 
WG is close to finishing its chartered goals, the chair can invite 
speakers to briefly present proposals for new work.  But in general a WG 
shouldn't preallocate time for such presentations in WG meetings - they 
should rather be discussed in separate BOF sessions.

Keith


From dhc@dcrocker.net  Fri Feb 15 13:42:27 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119BC21E8034 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 13:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cw6CngAhoRwg for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 13:42:22 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D576021F85B1 for <ietf@ietf.org>; Fri, 15 Feb 2013 13:42:22 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r1FLgMmS018429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 15 Feb 2013 13:42:22 -0800
Message-ID: <511EABB7.1010607@dcrocker.net>
Date: Fri, 15 Feb 2013 13:42:15 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com>
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.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, 15 Feb 2013 13:42:22 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 21:42:27 -0000

On 2/15/2013 9:46 AM, George, Wes wrote:
> [WEG] Perhaps it would be helpful to make an informal recommendation
> to WG chairs (via the wiki, for example) that generally they should
> carve each request for agenda time roughly in half, with a hard limit
> of $speaker_time/2


You are looking for an objective mechanism to handle a subjective issue. 
  It's a natural desire, but it's doomed to fail.

The requirement is to use meeting time well.  Yes, part of 'well' is to 
severely limit the occurrence of tutorials.  But a "presentation" might 
be highly appropriate or highly inappropriate, depending on its actual 
content.

For example, one type of presentation is to perform a careful expose', 
delineating design choices.  In form, it can look quite a bit like a 
tutorial. One time I helped resolve a seriously deadlocked and essential 
wg debate by just such an exercise.  I did a point-by-point comparison 
of the features (functions, benefits, costs, limitations, etc.) between 
two choices.  The powerpoint slides showed a 3-column table with each 
row listing a salient aspect.  By the end, the group developed 
reasonably good rough consensus towards one choice. My effort was a 
'presentation' but every minute of it was useful and, I believe, 
appropriate.

We need chairs and everyone else to be clear about what is useful and 
what is not and to then allocate (and enforce) time accordingly.  This 
is a matter of specific wg context and presentation content.

That doesn't happen algorithmically.


d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From paf@frobbit.se  Fri Feb 15 14:06:16 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2E1E21F846B for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:06:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zz7XiW2fQhxg for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:06:16 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0D421F85E0 for <ietf@ietf.org>; Fri, 15 Feb 2013 14:06:16 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::9863:9b76:9df9:bb3] (unknown [IPv6:2a02:80:3ffc:0:9863:9b76:9df9:bb3]) by mail.frobbit.se (Postfix) with ESMTPSA id 8521F21A66; Fri, 15 Feb 2013 23:06:15 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: back by popular demand - a DNS calculator
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <511E6E05.9040302@isi.edu>
Date: Fri, 15 Feb 2013 23:06:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu>
To: Joe Touch <touch@ISI.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: Fri, 15 Feb 2013 22:06:16 -0000

On 15 feb 2013, at 18:19, Joe Touch <touch@ISI.EDU> wrote:

> 	- the Bert version uses DNS strings that aren't valid
> 	(*, +, ',', ++)

Are we going to open again the question whether the DNS protocol can =
handle any value in the octets, as compared to the hostname definition =
that says something more limited? ;-)

   Patrik


From touch@isi.edu  Fri Feb 15 14:11:15 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A99C621E803C for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.74
X-Spam-Level: 
X-Spam-Status: No, score=-104.74 tagged_above=-999 required=5 tests=[AWL=1.559, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 9HFWMO9aVpVs for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:11:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4092F21E8034 for <ietf@ietf.org>; Fri, 15 Feb 2013 14:11:15 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id r1FMAjhx004514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Feb 2013 14:10:46 -0800 (PST)
Message-ID: <511EB264.2060308@isi.edu>
Date: Fri, 15 Feb 2013 14:10:44 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
In-Reply-To: <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 22:11:15 -0000

On 2/15/2013 2:06 PM, Patrik Fältström wrote:
> On 15 feb 2013, at 18:19, Joe Touch <touch@ISI.EDU> wrote:
>
>> 	- the Bert version uses DNS strings that aren't valid
>> 	(*, +, ',', ++)
>
> Are we going to open again the question whether the DNS protocol can handle any value in the octets, as compared to the hostname definition that says something more limited? ;-)
>
>     Patrik

Let's just say that there doesn't appear to be disagreement that the DNS 
can handle a-z/0-9/'-'.

Other values _may or may not_ be permitted or handled opaquely in the 
lookup, AFAICT. It remains a question AFAICT.

Joe



From randy@psg.com  Fri Feb 15 14:14:10 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C3A21E8043 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:14:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FFwHss05gHl2 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:14:10 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0D15921E803C for <ietf@ietf.org>; Fri, 15 Feb 2013 14:14:10 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1U6TXi-0006SC-35; Fri, 15 Feb 2013 22:14:06 +0000
Date: Sat, 16 Feb 2013 07:14:05 +0900
Message-ID: <m2a9r55ioi.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Patrik =?ISO-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Re: back by popular demand - a DNS calculator
In-Reply-To: <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 22:14:10 -0000

>> - the Bert version uses DNS strings that aren't valid
>>   (*, +, ',', ++)

this is not an accident

> Are we going to open again the question whether the DNS protocol can
> handle any value in the octets, as compared to the hostname definition
> that says something more limited? ;-)

no need.  the spec is pretty clear.

randy

From warren@kumari.net  Fri Feb 15 14:45:04 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7770421F848B for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level: 
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=-0.201, 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 2k64Hz9UUMai for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 14:45:04 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id E934921F8431 for <ietf@ietf.org>; Fri, 15 Feb 2013 14:45:03 -0800 (PST)
Received: from [192.168.1.136] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id BC8451B4091D; Fri, 15 Feb 2013 17:45:02 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Re: back by popular demand - a DNS calculator
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
Date: Fri, 15 Feb 2013 17:45:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
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, 15 Feb 2013 22:45:04 -0000

On Feb 15, 2013, at 5:06 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

> On 15 feb 2013, at 18:19, Joe Touch <touch@ISI.EDU> wrote:
>=20
>> 	- the Bert version uses DNS strings that aren't valid
>> 	(*, +, ',', ++)
>=20
> Are we going to open again the question whether the DNS protocol can =
handle any value in the octets, as compared to the hostname definition =
that says something more limited? ;-)

Sure -- the DNS protocol *cannot* "handle any value in the octets" -- in =
fact, there are an *infinite* number of values it cannot handle *in the =
octets*. For example, it cannot handle 257. It also cannot handle 321, =
nor 19.3...

:-P
W

>=20
>   Patrik
>=20

--
Don't be impressed with unintelligible stuff said condescendingly.
    -- Radia Perlman.






From john-ietf@jck.com  Fri Feb 15 15:17:46 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC7021F857C for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 15:17:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.662
X-Spam-Level: 
X-Spam-Status: No, score=-102.662 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0PIEGHHMtXi for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 15:17:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 591B621F857B for <ietf@ietf.org>; Fri, 15 Feb 2013 15:17:46 -0800 (PST)
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 1U6UXI-0004mD-QJ; Fri, 15 Feb 2013 18:17:44 -0500
Date: Fri, 15 Feb 2013 18:17:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: back by popular demand - a DNS calculator
Message-ID: <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com>
In-Reply-To: <511EB264.2060308@isi.edu>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>	<511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2013 23:17:46 -0000

--On Friday, February 15, 2013 14:10 -0800 Joe Touch
<touch@isi.edu> wrote:

> Let's just say that there doesn't appear to be disagreement
> that the DNS can handle a-z/0-9/'-'.
> 
> Other values _may or may not_ be permitted or handled opaquely
> in the lookup, AFAICT. It remains a question AFAICT.

Joe,

Except for IDNs (or labels starting with "xn--" more
specifically), for which there are special rules, it appears to
me that the spec is _extremely_ clear that a lookup operation
that fails to deal with those "other values" in labels
--including even properly-escaped embedded "." characters -- is
unambiguously non-conforming.

There should be no "AFACIT" about it, much less a question.

Whether or not it is a good idea to use such labels and in what
contexts is a different matter.

   john



From touch@isi.edu  Fri Feb 15 16:48:55 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C626A21F85AE for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 16:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.969
X-Spam-Level: 
X-Spam-Status: No, score=-103.969 tagged_above=-999 required=5 tests=[AWL=0.630, 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 GUCaN29pzFUR for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 16:48:55 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA9921F85A1 for <ietf@ietf.org>; Fri, 15 Feb 2013 16:48:55 -0800 (PST)
Received: from [192.168.1.96] (pool-71-105-87-221.lsanca.dsl-w.verizon.net [71.105.87.221]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id r1G0mHWB009454 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 15 Feb 2013 16:48:23 -0800 (PST)
Message-ID: <511ED751.2090703@isi.edu>
Date: Fri, 15 Feb 2013 16:48:17 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>	<511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu> <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com>
In-Reply-To: <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2013 00:48:55 -0000

On 2/15/2013 3:17 PM, John C Klensin wrote:
>
>
> --On Friday, February 15, 2013 14:10 -0800 Joe Touch
> <touch@isi.edu> wrote:
>
>> Let's just say that there doesn't appear to be disagreement
>> that the DNS can handle a-z/0-9/'-'.
>>
>> Other values _may or may not_ be permitted or handled opaquely
>> in the lookup, AFAICT. It remains a question AFAICT.
>
> Joe,
>
> Except for IDNs (or labels starting with "xn--" more
> specifically), for which there are special rules, it appears to
> me that the spec is _extremely_ clear that a lookup operation
> that fails to deal with those "other values" in labels
> --including even properly-escaped embedded "." characters -- is
> unambiguously non-conforming.

Seems clear to me:

RFC1035:

The labels must follow the rules for ARPANET host names.  They must
start with a letter, end with a letter or digit, and have as interior
characters only letters, digits, and hyphen.  There are also some
restrictions on the length.  Labels must be 63 characters or less.

--

If any label were allowed, then why does IDN conversion go so far out of 
its way to exclude particular strings, e.g., those beginning/ending with 
'-' and encodes everything 0..7F into a-z/0-9?

(I was focused on looking up A records given FQDNs)

Joe

From d3e3e3@gmail.com  Fri Feb 15 16:57:01 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D341021F85B4 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 16:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.436
X-Spam-Level: 
X-Spam-Status: No, score=-104.436 tagged_above=-999 required=5 tests=[AWL=1.163, 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 3Nx9W4MpCcSO for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 16:57:01 -0800 (PST)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 1172521F858B for <ietf@ietf.org>; Fri, 15 Feb 2013 16:57:01 -0800 (PST)
Received: by mail-oa0-f45.google.com with SMTP id o6so4419402oag.32 for <ietf@ietf.org>; Fri, 15 Feb 2013 16:57:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=ewXBc0Ji9XVOlqrz/TNno6L5hNJOKidh6OJGWQ2Lsmw=; b=fJMMP3XBhqDQaTc9W5otuHYI7yX9MXgD7rSWb+N7nRm9UEMJg32w2XG7uTrBS4SQ6L dPTAnNxT1Fb7kxHxSYZ0f0w8aGGMyeI7pJ38byGa5EhVKr/5MiYZIG/t5YqsJLBQcjTO kpV6TKb5ElnS+d3froMbB5b20zRI4Wqx0kyzBEYSQmJ7qpsGLY7E1p53o73TurhIawp0 K33wkyTAeJbRqyf1haq3x+jGE8PJqO57wRtorzS5am5vWFM1fT2T+PXRCsUq9Ntx768a pKV3gJVYAG9nxLGni7caEYYZhPKCFbiAiCj5joZtWryE+yAMWmolcmgZMPtdgiD/ZroS Pg2A==
X-Received: by 10.60.170.242 with SMTP id ap18mr2982993oec.97.1360976220598; Fri, 15 Feb 2013 16:57:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Fri, 15 Feb 2013 16:56:40 -0800 (PST)
In-Reply-To: <511ED751.2090703@isi.edu>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu> <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com> <511ED751.2090703@isi.edu>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 15 Feb 2013 19:56:40 -0500
Message-ID: <CAF4+nEF07vibLRDeawu08kCJ3cDhDpC5op15=k7htTsr6c5Ygg@mail.gmail.com>
Subject: Re: back by popular demand - a DNS calculator
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
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: Sat, 16 Feb 2013 00:57:01 -0000

Let's see, here is the list of RFCs that the RFC Editor believes
update RFC 1035:
RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996,
RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2845,
RFC 3425, RFC 3658, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 5936,
RFC 5966, RFC 6604,

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Fri, Feb 15, 2013 at 7:48 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 2/15/2013 3:17 PM, John C Klensin wrote:
>>
>>
>>
>> --On Friday, February 15, 2013 14:10 -0800 Joe Touch
>> <touch@isi.edu> wrote:
>>
>>> Let's just say that there doesn't appear to be disagreement
>>> that the DNS can handle a-z/0-9/'-'.
>>>
>>> Other values _may or may not_ be permitted or handled opaquely
>>> in the lookup, AFAICT. It remains a question AFAICT.
>>
>>
>> Joe,
>>
>> Except for IDNs (or labels starting with "xn--" more
>> specifically), for which there are special rules, it appears to
>> me that the spec is _extremely_ clear that a lookup operation
>> that fails to deal with those "other values" in labels
>> --including even properly-escaped embedded "." characters -- is
>> unambiguously non-conforming.
>
>
> Seems clear to me:
>
> RFC1035:
>
> The labels must follow the rules for ARPANET host names.  They must
> start with a letter, end with a letter or digit, and have as interior
> characters only letters, digits, and hyphen.  There are also some
> restrictions on the length.  Labels must be 63 characters or less.
>
> --
>
> If any label were allowed, then why does IDN conversion go so far out of its
> way to exclude particular strings, e.g., those beginning/ending with '-' and
> encodes everything 0..7F into a-z/0-9?
>
> (I was focused on looking up A records given FQDNs)
>
> Joe

From abdussalambaryun@gmail.com  Fri Feb 15 17:12:32 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A24521F855D for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 17:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30GrVqQ6-+qt for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 17:12:32 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id A81BD21F855F for <ietf@ietf.org>; Fri, 15 Feb 2013 17:12:30 -0800 (PST)
Received: by mail-we0-f174.google.com with SMTP id r6so3308358wey.33 for <ietf@ietf.org>; Fri, 15 Feb 2013 17:12:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NaTrfXYBV+j1OKtDMWXKl5e2YTILN6u8IRDjRT1hWAE=; b=FWHcd5+xP+3FCRvM+IOP80Kew1Dv40oT9GC63jaAdGRI266FI+02j8lBWqcapi968X Qadjtua/y0RjIbJBUHTWr99Lf83dnwAwUaIfssL8m0TtgRqgK4QbU7xKKN0Wm+HB3J3s MFTVLHSHJCLlY20ZVdYYnpMKXMBNxiswDsp8lHiLganLKCy/EYTdpw3ejybFLBw/X0LB B5fJnsU37PCcBYNV9UEQUcJlARLX2R4lETdq8ESz0MYZxpLzD7wVJ/CHlk0z4ZmVkv1a dMdMgU9rwy3BdpKo7blcg7/g7QDblbOWz303JdAWiKGfzIlR1hcihQ31WyWpBep3pz70 eRfQ==
MIME-Version: 1.0
X-Received: by 10.180.93.168 with SMTP id cv8mr7453660wib.5.1360977149970; Fri, 15 Feb 2013 17:12:29 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Fri, 15 Feb 2013 17:12:29 -0800 (PST)
In-Reply-To: <m2hald5yzb.wl%randy@psg.com>
References: <CADnDZ89=gwB8nAJOAmQz0GLCwkD7ZYYvF=M0PQ5yhK3OCtg3yw@mail.gmail.com> <511E597E.2090102@gmail.com> <m2hald5yzb.wl%randy@psg.com>
Date: Sat, 16 Feb 2013 02:12:29 +0100
Message-ID: <CADnDZ89ocWmjW6UnknRwVP8ECL_imKPj5EMZcjUEd9ZEbYAakA@mail.gmail.com>
Subject: Re: Musing on draft-resnick-on-consensus-01
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2013 01:12:32 -0000

On 2/15/13, Randy Bush <randy@psg.com> wrote:
> my take is that we have advanced to that stage of organizational life
> where we have newcomers who, when faced with a new culture with subtle
> process, are led by personal and/or cultural background to assert that
> the process should be changed to a model which they already understand,
> and for it to be documented in triplicate.

I think nothing needs to change in community culture or world culture
because it develops by itself, but in IETF all people face new
culture, so all the newcomer-participants, oldcomer, and the
subscribed-listeners. The ietf processes may need to change to cope
with community needs.

> rightly or wrongly, for
> historical and left coast cultural reasons, the ietf culture is more to
> watch, listen, learn, and *contribute technically*.  thanks, melinda,
> for having the patience to try and educate.

I think IETF culture is more to volunteer, discuss, cooperate, and
contribute-technically.

AB

From mohta@necom830.hpcl.titech.ac.jp  Fri Feb 15 17:26:11 2013
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 BEF3721F8433 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 17:25:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.09
X-Spam-Level: 
X-Spam-Status: No, score=-2.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iefQc0jsrSVa for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 17:25:29 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 6244921F8430 for <ietf@ietf.org>; Fri, 15 Feb 2013 17:25:28 -0800 (PST)
Received: (qmail 65912 invoked from network); 16 Feb 2013 01:23:52 -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; 16 Feb 2013 01:23:52 -0000
Message-ID: <511EDFB4.1030000@necom830.hpcl.titech.ac.jp>
Date: Sat, 16 Feb 2013 10:24:04 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>	<511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu> <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com> <511ED751.2090703@isi.edu>
In-Reply-To: <511ED751.2090703@isi.edu>
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: Sat, 16 Feb 2013 01:26:11 -0000

Joe Touch wrote:

> Seems clear to me:
> 
> RFC1035:
> 
> The labels must follow the rules for ARPANET host names.  They must
> start with a letter, end with a letter or digit, and have as interior
> characters only letters, digits, and hyphen.  There are also some
> restrictions on the length.  Labels must be 63 characters or less.

That is syntax in section "2.3.1. Preferred name syntax" as syntax
preferred by applications that use host names.

   The following syntax will result in fewer problems with many
   applications that use domain names (e.g., mail, TELNET).

The basic rule of the RFC is:

   Although labels can contain any 8 bit values in octets that make up a
   label

A label may include '.' character as is, as there is no escape
mechanism, though applications expecting host names may fail to
recognize it.

						Masataka Ohta

From paf@frobbit.se  Fri Feb 15 23:02:57 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8354321F857A for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.3
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, 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 tq+s+YGJDeTl for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:02:50 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 7078421F85C0 for <ietf@ietf.org>; Fri, 15 Feb 2013 23:02:50 -0800 (PST)
Received: from [192.168.1.11] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 3194220096; Sat, 16 Feb 2013 08:02:49 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] back by popular demand - a DNS calculator
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net>
Date: Sat, 16 Feb 2013 08:02:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <10350DF8-6C01-4DC1-A51B-359604256978@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net>
To: Warren Kumari <warren@kumari.net>
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: Sat, 16 Feb 2013 07:02:57 -0000

On 15 feb 2013, at 23:45, Warren Kumari <warren@kumari.net> wrote:

> Sure -- the DNS protocol *cannot* "handle any value in the octets" -- =
in fact, there are an *infinite* number of values it cannot handle *in =
the octets*. For example, it cannot handle 257. It also cannot handle =
321, nor 19.3...

Ok, it is obvious Friday...somewhere...

Once when being on IESG way back when I was tasked to write the response =
to the letter we got with a suggestion on an alternative solution for =
the "running out of IPv4 addresses" problem.

The proposal was to not stop counting at 255 in each of the four numbers =
separated by periods, but continue to (at least) 999.

   Patrik


From paf@frobbit.se  Fri Feb 15 23:04:16 2013
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14D5121F85C0 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:04:16 -0800 (PST)
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=-0.500, 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 WwKCVCQahU7g for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:04:15 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3F521F857A for <ietf@ietf.org>; Fri, 15 Feb 2013 23:04:15 -0800 (PST)
Received: from [192.168.1.11] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id E377B21A97; Sat, 16 Feb 2013 08:04:14 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: back by popular demand - a DNS calculator
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <511ED751.2090703@isi.edu>
Date: Sat, 16 Feb 2013 08:04:14 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <74E1EE28-284E-47E6-9F55-5C62C35651CC@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>	<511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu> <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com> <511ED751.2090703@isi.edu>
To: Joe Touch <touch@ISI.EDU>
X-Mailer: Apple Mail (2.1499)
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: Sat, 16 Feb 2013 07:04:16 -0000

On 16 feb 2013, at 01:48, Joe Touch <touch@ISI.EDU> wrote:

> (I was focused on looking up A records given FQDNs)

Thats a different thing than talking about what the DNS protocol can handle.

   Patrik


From dave@cridland.net  Fri Feb 15 23:33:23 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCBD721F856F for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.826
X-Spam-Level: 
X-Spam-Status: No, score=-3.826 tagged_above=-999 required=5 tests=[AWL=0.850,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.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 eezHfQLLJb95 for <ietf@ietfa.amsl.com>; Fri, 15 Feb 2013 23:33:22 -0800 (PST)
Received: from mail-oa0-f46.google.com (mail-oa0-f46.google.com [209.85.219.46]) by ietfa.amsl.com (Postfix) with ESMTP id BDF2921F856D for <ietf@ietf.org>; Fri, 15 Feb 2013 23:33:22 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id k1so4524469oag.33 for <ietf@ietf.org>; Fri, 15 Feb 2013 23:33:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=VySoxPRpCzEfZRHwT+qJZaP1JYiXUp2ssyCw5rh6RV0=; b=EhIx1n505Kqo7ppCR0NKPwdNeQORFQFXP6cGmQI3IsAJddQhrfot6iRi6n62bcHjbu U3UbrdVQqvjCS9SP8VlX53/og+OkPwCo1q3Pq5UEDzhkpDaLsmCEtMAeOvU5SPe4qW5w DckMvBtTG2FRRYym9kk3kkxvGeyJTtoqNpSdk=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=VySoxPRpCzEfZRHwT+qJZaP1JYiXUp2ssyCw5rh6RV0=; b=cM9o3h5I979iaOiAPY09UvGJe7A2aMrlixgFsISXue//qc0ybB93GhpihsbfsUe2OM hy/83vBSRhGq8I8KrywyKWNKKnjDSXm4Qr9N/CqmY9UCi//xknRBpK6sTT3PMpzMyeun M2e8jPg6EdDyOQ+SL/aGUitzMTFDObgWQXwCaqoghFVYZd+pY7ALdQXuFUdfcOQ6G+dj CrJtEgjE6/ODxf0WOgUw+zSbDqQx8mSxyZE336G+f331Me1O71RABjnO/3rk4/pyRrmX 40KzIIKkoq699HaVTzL/LSYNn6z9TNupUwn5qZEL6/v7d/1wETiCwnAUQrpL6jD4XFYq 0ycQ==
MIME-Version: 1.0
X-Received: by 10.60.27.161 with SMTP id u1mr3360207oeg.1.1361000002232; Fri, 15 Feb 2013 23:33:22 -0800 (PST)
Received: by 10.60.59.74 with HTTP; Fri, 15 Feb 2013 23:33:21 -0800 (PST)
Received: by 10.60.59.74 with HTTP; Fri, 15 Feb 2013 23:33:21 -0800 (PST)
In-Reply-To: <10350DF8-6C01-4DC1-A51B-359604256978@frobbit.se>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net> <10350DF8-6C01-4DC1-A51B-359604256978@frobbit.se>
Date: Sat, 16 Feb 2013 07:33:21 +0000
Message-ID: <CAKHUCzx_cw2Fh_D+xJRd9tA-ModS6zVv8p9gqpLZo8sDyditoQ@mail.gmail.com>
Subject: Re: [IETF] back by popular demand - a DNS calculator
From: Dave Cridland <dave@cridland.net>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=e89a8fb20302ac20a204d5d281da
X-Gm-Message-State: ALoCoQkByySqElLNN2BjIdsDvt42Rt7xY7coIUqqwyA124NCkO6yfSEOJ9xV+4/cEpLUWH6FjjQI
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2013 07:33:23 -0000

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

On 16 Feb 2013 07:03, "Patrik F=E4ltstr=F6m" <paf@frobbit.se> wrote:
>
>
> On 15 feb 2013, at 23:45, Warren Kumari <warren@kumari.net> wrote:
>
> > Sure -- the DNS protocol *cannot* "handle any value in the octets" --
in fact, there are an *infinite* number of values it cannot handle *in the
octets*. For example, it cannot handle 257. It also cannot handle 321, nor
19.3...
>
> Ok, it is obvious Friday...somewhere...
>
> Once when being on IESG way back when I was tasked to write the response
to the letter we got with a suggestion on an alternative solution for the
"running out of IPv4 addresses" problem.
>
> The proposal was to not stop counting at 255 in each of the four numbers
separated by periods, but continue to (at least) 999.
>

Seems quite sensible to me. After all, we do this in TELNET option
negotiation.

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

<p dir=3D"ltr"><br>
On 16 Feb 2013 07:03, &quot;Patrik F=E4ltstr=F6m&quot; &lt;<a href=3D"mailt=
o:paf@frobbit.se">paf@frobbit.se</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; On 15 feb 2013, at 23:45, Warren Kumari &lt;<a href=3D"mailto:warren@k=
umari.net">warren@kumari.net</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Sure -- the DNS protocol *cannot* &quot;handle any value in the o=
ctets&quot; -- in fact, there are an *infinite* number of values it cannot =
handle *in the octets*. For example, it cannot handle 257. It also cannot h=
andle 321, nor 19.3...<br>

&gt;<br>
&gt; Ok, it is obvious Friday...somewhere...<br>
&gt;<br>
&gt; Once when being on IESG way back when I was tasked to write the respon=
se to the letter we got with a suggestion on an alternative solution for th=
e &quot;running out of IPv4 addresses&quot; problem.<br>
&gt;<br>
&gt; The proposal was to not stop counting at 255 in each of the four numbe=
rs separated by periods, but continue to (at least) 999.<br>
&gt;</p>
<p dir=3D"ltr">Seems quite sensible to me. After all, we do this in TELNET =
option negotiation.</p>

--e89a8fb20302ac20a204d5d281da--

From brian.e.carpenter@gmail.com  Sat Feb 16 00:04:23 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B695521F86D0 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 00:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.743
X-Spam-Level: 
X-Spam-Status: No, score=-99.743 tagged_above=-999 required=5 tests=[AWL=-0.822, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bUgs4eznWe5Y for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 00:04:22 -0800 (PST)
Received: from mail-we0-x236.google.com (we-in-x0236.1e100.net [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9C97821F8569 for <ietf@ietf.org>; Sat, 16 Feb 2013 00:04:22 -0800 (PST)
Received: by mail-we0-f182.google.com with SMTP id t57so3538825wey.13 for <ietf@ietf.org>; Sat, 16 Feb 2013 00:04:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=h7sJVFU3923m3CGbWnShjXHXNo849eIKOmihgKGQrqk=; b=uSvSBO2BWdHNBUwqMf36vIF5BWRthJ7lBeuDx29uLQVj8TP8sOzTd7wmjbUxxBXGrd 7n3w9V6di+oDEdkS78k/Dqk74DRqjUTiRqUxxbAY4VDPYED0g/UMYTgTeWnxEIJROVFY HY8KrodsP+/PRRTpSzMUzmQwcOUZf/bAu9HzEpsV4BmVxeYkwFJrV4yrvfpTFlmKGeAz 3VscjlcIKB++ytQzqjSamTJ3bwVenCtUOtNhbUPlF32g+IV0kR6/qUSnaMWWJAFNcOmS AVmGBA2X4BkiHS4HBh5fO4FZxnuyKWLmYuL4Rr/mubxUIMKYdRgsW2ZYChD36Q0tYS7A FUMA==
X-Received: by 10.194.58.175 with SMTP id s15mr8666625wjq.31.1361001861732; Sat, 16 Feb 2013 00:04:21 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-21.as13285.net. [2.102.217.21]) by mx.google.com with ESMTPS id fv2sm6185397wib.6.2013.02.16.00.04.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Feb 2013 00:04:21 -0800 (PST)
Message-ID: <511F3D95.3030302@gmail.com>
Date: Sat, 16 Feb 2013 08:04:37 +0000
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: Keith Moore <moore@network-heretics.com>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com> <511EA11D.7010700@network-heretics.com>
In-Reply-To: <511EA11D.7010700@network-heretics.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: Sat, 16 Feb 2013 08:04:23 -0000

On 15/02/2013 20:57, Keith Moore wrote:
...
> But this makes me realize that there's a related issue.   An expectation
> that WG meetings are for presentations, leads to an expectation that
> there's lots of opportunity to present suggestions for new work to do.  
> WG time scheduled for considering new work can actually take away time
> for discussion of ongoing work.   And once the time is scheduled and
> people have made commitments to travel to meetings for the purpose of
> presenting new work, chairs are understandably reluctant to deny them
> their allotted presentation time.

This is closely related to a well-known problem at academic conferences.
Many people can only get funded to travel if they are presenting a paper.
It's common practice, therefore, to have either a poster session (which
allows massively parallel presentations) or hot-topics sessions (with a
strict and very short time-limit). We tend to throw the hot-topics sessions
into WG meetings, which is not ideal.

Why not have a poster session as part of Bits-n-Bites? It would give
new ideas a chance to be seen without wasting WG time. Make it official
enough that people can use it in their travel requests.

    Brian

From abdussalambaryun@gmail.com  Sat Feb 16 05:00:21 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5894721F86D3 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:00:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.041,  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 mFG7TARQsg1V for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:00:20 -0800 (PST)
Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by ietfa.amsl.com (Postfix) with ESMTP id 3EFAD21F86D2 for <ietf@ietf.org>; Sat, 16 Feb 2013 05:00:20 -0800 (PST)
Received: by mail-wg0-f53.google.com with SMTP id fn15so3517402wgb.20 for <ietf@ietf.org>; Sat, 16 Feb 2013 05:00:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=1uL/cclzQHcbevyOKSdYMiriBWoHl8RKp56a/PPlTJQ=; b=n1/2XIp2qzPSbmVwU1kGvk1Iw8h8ViUpyp7zoEmmVBfeZeQ61655VOrkvCYsS7tDd7 DZZC1tKUEN7UDLJZ6bsdRujsXyBLEY9MuncFNCeUgF+U1PZ6NLBJKMAkjr25mCDo+Fjb 1hgb8dXPHR6FW5QAxGvQSnqTTu0SB6CH05LIHCAPw+7WyH/HRdMxe5L4qrVgJKUaZ/8l XNDALL10AVsz7dJpFDJCp+8h0wa/nXQR5xoObqUmLBYWtavDoC5mGOOJ8vdACk9CKcD5 5szMgIkRD+TtaV7nb712ekCUX82p9UmadAdLqlnCwEQ0oWt3nau8GmODlWyuxuUUJApE DX+g==
MIME-Version: 1.0
X-Received: by 10.180.83.10 with SMTP id m10mr11208835wiy.5.1361019619448; Sat, 16 Feb 2013 05:00:19 -0800 (PST)
Received: by 10.180.101.70 with HTTP; Sat, 16 Feb 2013 05:00:19 -0800 (PST)
In-Reply-To: <CADnDZ89723BDPJrQ+C80_APtQx9+BGGopjBQtTYxBHB1naCn=w@mail.gmail.com>
References: <CADnDZ89723BDPJrQ+C80_APtQx9+BGGopjBQtTYxBHB1naCn=w@mail.gmail.com>
Date: Sat, 16 Feb 2013 14:00:19 +0100
Message-ID: <CADnDZ89WCPNnSKf9-=QaTFMM61t+iECeCwquh5=az1cH1SitxQ@mail.gmail.com>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2013 13:00:21 -0000

+1

AB

On 16/02/13 08:04, Brian Carpenter wrote:
> On 15/02/2013 20:57, Keith Moore wrote:
> ...
>> But this makes me realize that there's a related issue.   An expectation
>> that WG meetings are for presentations, leads to an expectation that
>> there's lots of opportunity to present suggestions for new work to do.
>> WG time scheduled for considering new work can actually take away time
>> for discussion of ongoing work.   And once the time is scheduled and
>> people have made commitments to travel to meetings for the purpose of
>> presenting new work, chairs are understandably reluctant to deny them
>> their allotted presentation time.
>
> This is closely related to a well-known problem at academic conferences.
> Many people can only get funded to travel if they are presenting a paper.
> It's common practice, therefore, to have either a poster session (which
> allows massively parallel presentations) or hot-topics sessions (with a
> strict and very short time-limit). We tend to throw the hot-topics sessions
> into WG meetings, which is not ideal.
>
> Why not have a poster session as part of Bits-n-Bites? It would give
> new ideas a chance to be seen without wasting WG time. Make it official
> enough that people can use it in their travel requests.
>
>     Brian
>

From moore@network-heretics.com  Sat Feb 16 05:23:12 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2948621F879E for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.386
X-Spam-Level: 
X-Spam-Status: No, score=-3.386 tagged_above=-999 required=5 tests=[AWL=0.214,  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 BpFFCctB9QqU for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:23:11 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id 5C4E821F8633 for <ietf@ietf.org>; Sat, 16 Feb 2013 05:23:11 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 1FCB6209CD; Sat, 16 Feb 2013 08:23:10 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute5.internal (MEProxy); Sat, 16 Feb 2013 08:23:10 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=X3NvhPS72IM6PrQH9ihQvm bgVq8=; b=P48TUritkAGLYcuVM4rgrQtRXFAIahXUmk58M8CS1hLqhxth7hkZGH U8ZQx0QCNo1sOd1+GlIDbZRgy+pObLbnJo1BmFuYGTGGOIEmDn5mmp1gUfQvgm4B 54SFuSWvY9/kV5+LSZQEu297+Acpx5T6mgsVhO/MwEFsMomJEGY10=
X-Sasl-enc: GCmchrPsJ/z+3VsgHKnBWffEWi9E3B45/FYY51JRzB/J 1361020989
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 547998E069E; Sat, 16 Feb 2013 08:23:09 -0500 (EST)
Message-ID: <511F883A.90207@network-heretics.com>
Date: Sat, 16 Feb 2013 08:23:06 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com> <511EA11D.7010700@network-heretics.com> <511F3D95.3030302@gmail.com>
In-Reply-To: <511F3D95.3030302@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: Sat, 16 Feb 2013 13:23:12 -0000

On 02/16/2013 03:04 AM, Brian E Carpenter wrote:
> On 15/02/2013 20:57, Keith Moore wrote:
> ...
>> But this makes me realize that there's a related issue.   An expectation
>> that WG meetings are for presentations, leads to an expectation that
>> there's lots of opportunity to present suggestions for new work to do.
>> WG time scheduled for considering new work can actually take away time
>> for discussion of ongoing work.   And once the time is scheduled and
>> people have made commitments to travel to meetings for the purpose of
>> presenting new work, chairs are understandably reluctant to deny them
>> their allotted presentation time.
> This is closely related to a well-known problem at academic conferences.
> Many people can only get funded to travel if they are presenting a paper.
> It's common practice, therefore, to have either a poster session (which
> allows massively parallel presentations) or hot-topics sessions (with a
> strict and very short time-limit). We tend to throw the hot-topics sessions
> into WG meetings, which is not ideal.
>
> Why not have a poster session as part of Bits-n-Bites? It would give
> new ideas a chance to be seen without wasting WG time. Make it official
> enough that people can use it in their travel requests.
That sounds like a great idea to me.

Keith


From warren@kumari.net  Sat Feb 16 05:43:59 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 551E221F8836 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:43:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.781
X-Spam-Level: 
X-Spam-Status: No, score=-102.781 tagged_above=-999 required=5 tests=[AWL=0.121, BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001,  MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ckD13dNNHgNp for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 05:43:58 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9193C21F881A for <ietf@ietf.org>; Sat, 16 Feb 2013 05:43:58 -0800 (PST)
Received: from [192.168.1.141] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 64F711B40706; Sat, 16 Feb 2013 08:43:57 -0500 (EST)
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net> <10350DF8-6C01-4DC1-A51B-359604256978@frobbit.se>
In-Reply-To: <10350DF8-6C01-4DC1-A51B-359604256978@frobbit.se>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary=Apple-Mail-02969AAF-2BF9-4B44-A6D8-9FDD787FF3D6
Message-Id: <61F39145-5658-4EE0-813C-FD0FA29EF644@kumari.net>
X-Mailer: iPad Mail (10A523)
From: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] back by popular demand - a DNS calculator
Date: Sat, 16 Feb 2013 08:46:27 -0500
To: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2013 13:43:59 -0000

--Apple-Mail-02969AAF-2BF9-4B44-A6D8-9FDD787FF3D6
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



Sent from my iPad

On Feb 16, 2013, at 2:02 AM, Patrik F=C3=A4ltstr=C3=B6m <paf@frobbit.se> wro=
te:

>=20
> On 15 feb 2013, at 23:45, Warren Kumari <warren@kumari.net> wrote:
>=20
>> Sure -- the DNS protocol *cannot* "handle any value in the octets" -- in f=
act, there are an *infinite* number of values it cannot handle *in the octet=
s*. For example, it cannot handle 257. It also cannot handle 321, nor 19.3..=
.
>=20
> Ok, it is obvious Friday...somewhere...
>=20
> Once when being on IESG way back when I was tasked to write the response t=
o the letter we got with a suggestion on an alternative solution for the "ru=
nning out of IPv4 addresses" problem.
>=20
> The proposal was to not stop counting at 255 in each of the four numbers s=
eparated by periods, but continue to (at least) 999.
>=20

That's also a solved problem -- there is even a draft about it : http://tool=
s.ietf.org/html/draft-terrell-math-quant-ternary-logic-of-binary-sys-01

You just use ternary logic instead of binary and all your problems are solve=
d... or something...I get a little lost during the proof of Fermat's...

W


>   Patrik
>=20

--Apple-Mail-02969AAF-2BF9-4B44-A6D8-9FDD787FF3D6
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><br><br>Sent from my iPad</div><div><b=
r>On Feb 16, 2013, at 2:02 AM, Patrik F=C3=A4ltstr=C3=B6m &lt;<a href=3D"mai=
lto:paf@frobbit.se">paf@frobbit.se</a>&gt; wrote:<br><br></div><blockquote t=
ype=3D"cite"><div><span></span><br><span>On 15 feb 2013, at 23:45, Warren Ku=
mari &lt;<a href=3D"mailto:warren@kumari.net">warren@kumari.net</a>&gt; wrot=
e:</span><br><span></span><br><blockquote type=3D"cite"><span>Sure -- the DN=
S protocol *cannot* "handle any value in the octets" -- in fact, there are a=
n *infinite* number of values it cannot handle *in the octets*. For example,=
 it cannot handle 257. It also cannot handle 321, nor 19.3...</span><br></bl=
ockquote><span></span><br><span>Ok, it is obvious Friday...somewhere...</spa=
n><br><span></span><br><span>Once when being on IESG way back when I was tas=
ked to write the response to the letter we got with a suggestion on an alter=
native solution for the "running out of IPv4 addresses" problem.</span><br><=
span></span><br><span>The proposal was to not stop counting at 255 in each o=
f the four numbers separated by periods, but continue to (at least) 999.</sp=
an><br><span></span><br></div></blockquote><div><br></div><div>That's also a=
 solved problem -- there is even a draft about it :&nbsp;<a href=3D"http://t=
ools.ietf.org/html/draft-terrell-math-quant-ternary-logic-of-binary-sys-01">=
http://tools.ietf.org/html/draft-terrell-math-quant-ternary-logic-of-binary-=
sys-01</a></div><div><br></div><div>You just use ternary logic instead of bi=
nary and all your problems are solved... or something...I get a little lost d=
uring the proof of Fermat's...</div><div><br></div><div>W</div><div><br></di=
v><br><blockquote type=3D"cite"><div><span> &nbsp;&nbsp;Patrik</span><br><sp=
an></span><br></div></blockquote></body></html>=

--Apple-Mail-02969AAF-2BF9-4B44-A6D8-9FDD787FF3D6--

From hallam@gmail.com  Sat Feb 16 10:22:55 2013
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 5FA9221F8953; Sat, 16 Feb 2013 10:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.794
X-Spam-Level: 
X-Spam-Status: No, score=-5.794 tagged_above=-999 required=5 tests=[AWL=-2.196, 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 zn0sB2+6UtxB; Sat, 16 Feb 2013 10:22:54 -0800 (PST)
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by ietfa.amsl.com (Postfix) with ESMTP id A22B621F8930; Sat, 16 Feb 2013 10:22:53 -0800 (PST)
Received: by mail-wi0-f182.google.com with SMTP id hi18so2238263wib.9 for <multiple recipients>; Sat, 16 Feb 2013 10:22:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=mhWeL7kjJLap9HNa5NHMm97l86OvwXO7JPfPET7oqAU=; b=D4AYCQ98so6IBf4lVsXG9iEwnym+gFfCNKVdI6xu23PMI4k0F2LG1W+Ywq8VvMNodj sHCzLdKGXKabboEX1D579KQsocX71t15WgzlUvijGBoKwa8vK8RqIpl5zb3gVKEPPzfN XRQApS22dT1QujLzTxYTHPPex1fQJSWQ1EsLLzBplacKfpJesvXC8TvNG6dEjLLtUGfM wVkgOEX7pNIf1xSP2/PCgOLWsfA/fd3Nhdhh7sIj9GP1J5geeW3pen89+hblp6xm6eg0 QvM0j7RJ2YZwmARFnLB0RQem1TCmIl5/feVYuJ4i1cUmfbObJPcTd+3gl04KaBerSsde zsaQ==
MIME-Version: 1.0
X-Received: by 10.180.100.169 with SMTP id ez9mr12326625wib.3.1361038972848; Sat, 16 Feb 2013 10:22:52 -0800 (PST)
Received: by 10.194.176.169 with HTTP; Sat, 16 Feb 2013 10:22:52 -0800 (PST)
In-Reply-To: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com>
References: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com>
Date: Sat, 16 Feb 2013 13:22:52 -0500
Message-ID: <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com>
Subject: Re: [therightkey] LC comments on draft-laurie-pki-sunlight-05
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary=14dae9cc9c56808b2304d5db9408
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, Adam Langley <agl@google.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: Sat, 16 Feb 2013 18:22:55 -0000

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

Sorry for the delay but I have been thinking of CT and in particular the
issues of

* Latency for the CA waiting for a notary server to respond
* Business models for notary servers

As a rule open source software works really well as the marginal cost of
production is zero. Open source services tend to sux because even though
the marginal cost of a service is negligible, large numbers times
negligible adds up to big numbers. Running a DNS server for a university
department costs very little, running it for the whole university starts to
cost real money and running a registry like .com with 99.9999% reliability
ends up with $100 million hardware costs.

So the idea that I plug my business into a network of notary servers being
run by amateurs or as a community service is a non-starter for me. We have
to align the responsibility for running any server that the CA has a
critical dependency on with a business model.

Looking at the CT proposal, it seems to me that we could fix the business
model issue and remove a lot of the CA operational issues as follows:

1) Each browser provider that is interested in enforcing a CT requirement
stands up a meta-notary server.

2) Each CA runs their own notary server and this is the only resource that
needs to have a check in at certificate issue.

3) Each CA notary server checkpoints to one or more meta-notary servers
every 60 minutes. As part of the check in process it uploads the whole
information for all the certificates issued in that time interval.

4) Meta-Notaries deliver tokens that assert that the CA notaries are
current every 60 minutes. Note here that 'current' is according to the
criteria set by the meta notary. This is an intentional piece of 'slop' in
the system.

5) The OCSP tokens delivered by the CA contain the information necessary to
checkpoint the certificate to the Meta-Notaries.

6) A browser enforcing CT disclosure pulls a list of anchor points from its
chosen meta-notary every 60 minutes and uses them to validate the CT
assertions delivered in certs.


The 'slop' introduced at the meta-notary can of course be removed if we
want to ensure that the system is robust even if there is a collusion
between the CA and the meta-notary. But since the whole point of the scheme
is transparency, the meta-notary operation can be audited by third parties
in any event.

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

Sorry for the delay but I have been thinking of CT and in particular the is=
sues of
<div><br></div><div>* Latency for the CA waiting for a notary server to res=
pond</div><div>* Business models for notary servers</div><div><br></div><di=
v>As a rule open source software works really well as the marginal cost of =
production is zero. Open source services tend to sux because even though th=
e marginal cost of a service is negligible, large numbers times negligible =
adds up to big numbers. Running a DNS server for a university department co=
sts very little, running it for the whole university starts to cost real mo=
ney and running a registry like .com with 99.9999% reliability ends up with=
 $100 million hardware costs.</div>
<div><br></div><div>So the idea that I plug my business into a network of n=
otary servers being run by amateurs or as a community service is a non-star=
ter for me. We have to align the responsibility for running any server that=
 the CA has a critical dependency on with a business model.</div>
<div><br></div><div>Looking at the CT proposal, it seems to me that we coul=
d fix the business model issue and remove a lot of the CA operational issue=
s as follows:</div><div><br></div><div>1) Each browser provider that is int=
erested in enforcing a CT requirement stands up a meta-notary server.</div>
<div><br></div><div>2) Each CA runs their own notary server and this is the=
 only resource that needs to have a check in at certificate issue.</div><di=
v><br></div><div>3) Each CA notary server checkpoints to one or more meta-n=
otary servers every 60 minutes. As part of the check in process it uploads =
the whole information for all the certificates issued in that time interval=
.</div>
<div><br></div><div>4) Meta-Notaries deliver tokens that assert that the CA=
 notaries are current every 60 minutes. Note here that &#39;current&#39; is=
 according to the criteria set by the meta notary. This is an intentional p=
iece of &#39;slop&#39; in the system.=A0</div>
<div><br></div><div>5) The OCSP tokens delivered by the CA contain the info=
rmation necessary to checkpoint the certificate to the Meta-Notaries.</div>=
<div><br></div><div>6) A browser enforcing CT disclosure pulls a list of an=
chor points from its chosen meta-notary every 60 minutes and uses them to v=
alidate the CT assertions delivered in certs.</div>
<div><br></div><div><br></div><div>The &#39;slop&#39; introduced at the met=
a-notary can of course be removed if we want to ensure that the system is r=
obust even if there is a collusion between the CA and the meta-notary. But =
since the whole point of the scheme is transparency, the meta-notary operat=
ion can be audited by third parties in any event.=A0</div>
<div><br></div>

--14dae9cc9c56808b2304d5db9408--

From paul.hoffman@vpnc.org  Sat Feb 16 10:54:39 2013
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1355421F87CE; Sat, 16 Feb 2013 10:54:39 -0800 (PST)
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 cYWmPBo5wDGK; Sat, 16 Feb 2013 10:54:37 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1DE21F86AF; Sat, 16 Feb 2013 10:54:37 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-243.dsl.dynamic.sonic.net [50.1.98.243]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r1GIsW2B020451 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 16 Feb 2013 11:54:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [therightkey] LC comments on draft-laurie-pki-sunlight-05
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com>
Date: Sat, 16 Feb 2013 10:54:32 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <72D4ABBB-9B39-41F6-9AFF-37F0A7DBDAC1@vpnc.org>
References: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com> <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: therightkey@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: Sat, 16 Feb 2013 18:54:39 -0000

On Feb 16, 2013, at 10:22 AM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> Looking at the CT proposal, it seems to me that we could fix the =
business model issue and remove a lot of the CA operational issues as =
follows:
>=20
> 1) Each browser provider that is interested in enforcing a CT =
requirement stands up a meta-notary server.
>=20
> 2) Each CA runs their own notary server and this is the only resource =
that needs to have a check in at certificate issue.
>=20
> 3) Each CA notary server checkpoints to one or more meta-notary =
servers every 60 minutes. As part of the check in process it uploads the =
whole information for all the certificates issued in that time interval.
>=20
> 4) Meta-Notaries deliver tokens that assert that the CA notaries are =
current every 60 minutes. Note here that 'current' is according to the =
criteria set by the meta notary. This is an intentional piece of 'slop' =
in the system.=20
>=20
> 5) The OCSP tokens delivered by the CA contain the information =
necessary to checkpoint the certificate to the Meta-Notaries.
>=20
> 6) A browser enforcing CT disclosure pulls a list of anchor points =
from its chosen meta-notary every 60 minutes and uses them to validate =
the CT assertions delivered in certs.

Are you saying that those six items should be added to the experimental =
RFC as requirements, or are you just discussing what might happen =
operationally after the RFC is published?=20

--Paul Hoffman=

From benl@google.com  Sat Feb 16 10:55:59 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E0421F887D for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 10:55:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZpWKT+4A0mzP for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 10:55:59 -0800 (PST)
Received: from mail-ia0-x22c.google.com (ia-in-x022c.1e100.net [IPv6:2607:f8b0:4001:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D2BF721F8849 for <ietf@ietf.org>; Sat, 16 Feb 2013 10:55:58 -0800 (PST)
Received: by mail-ia0-f172.google.com with SMTP id l29so2198604iag.31 for <ietf@ietf.org>; Sat, 16 Feb 2013 10:55:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9GCLH3GRy1sXy/A0r1frGN4WexvkDPA0VvbVHlqlbvg=; b=j9Znx05zHMHbrYwWhXiidxeV53ZvLABu9pRzBBA1s8Ikmnb2v+yeYPk79ORZVN7OtU EDcbX0Gabn9rXIk7GdSI6hN3h3TAS8527c2widbWXCG1vfj/vDbjYZyxV9H0FlxTwOqX SPztoFoGU11/cElGdSXYzLX5LlPJgh4Pra+ndFwnKBg2C/MhFbIzDmnNZ9oNUyGjdqEC 6wNaKzZNls7pBK5TO5EDFfz67D+dIGt8xelGGSwJQOPKdnrb6o+pVDv2y1oNvkZ2almh IOSbXAQ+yMX8HwotLjb7jBKL1IAk1XySfjZI9f7ghTS2yd2Qii/ANAh3YYcrFtUQcOfZ ZmVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=9GCLH3GRy1sXy/A0r1frGN4WexvkDPA0VvbVHlqlbvg=; b=KrCPzxFXT6RiLMPDIKlwFIDnWJz712dwZDDCaQctu4yxsV0kbug6T9tW8d1KFIN3Tr 9OBLhBrZUBmBSTe8D4em6Xlq2+viVnDY9dMVv52SCtQutyhWAcjpThzxSlBak4vMJwN+ i3JhKOThzJHpbyavD4AXxiP8xDeML12yU2xjKaY8I7aKtd5leQOy5OrE18MjwQdc8sMx nZGBWyXtXwtTmaRQdPVbbXxMaQt8wjpYqUOAZkYXz6q23AQkglTdfCR0UlBlgipySy0m CYRBCF+w3mt5PGwFrqc/PyLyKZtHOXKHj4B+3mRPk/Ml+vyZMK/fNEBXya0wZthnINI9 DkZg==
MIME-Version: 1.0
X-Received: by 10.50.17.201 with SMTP id q9mr4680814igd.107.1361040958321; Sat, 16 Feb 2013 10:55:58 -0800 (PST)
Received: by 10.64.19.136 with HTTP; Sat, 16 Feb 2013 10:55:58 -0800 (PST)
In-Reply-To: <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com>
References: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com> <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com>
Date: Sat, 16 Feb 2013 10:55:58 -0800
Message-ID: <CABrd9SS7as7S3vz2AEOJQruCF7aJRSVGjaG6awV9YWyuQaadWQ@mail.gmail.com>
Subject: Re: [therightkey] LC comments on draft-laurie-pki-sunlight-05
From: Ben Laurie <benl@google.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlE88AO5Nux9f+plivXDzdNicYvfXLdFWkFsIhxT1ouFJbkXmm+TkHu1F6T4G3kFvOKao0fG+16nWDwLYdkYxCPKS4YE9yteD3FEQ0hUj7hsjbM3dtVrr+yfWZqtgJfqyLgTviO7C45fTYo/rAM0cd/71gQnGQ8Y3rfOpib8aDIqjkOKke4RyKSuWoYquP90+NsNfkM
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, Adam Langley <agl@google.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: Sat, 16 Feb 2013 18:55:59 -0000

On 16 February 2013 10:22, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> Sorry for the delay but I have been thinking of CT and in particular the
> issues of
>
> * Latency for the CA waiting for a notary server to respond
> * Business models for notary servers
>
> As a rule open source software works really well as the marginal cost of
> production is zero. Open source services tend to sux because even though the
> marginal cost of a service is negligible, large numbers times negligible
> adds up to big numbers. Running a DNS server for a university department
> costs very little, running it for the whole university starts to cost real
> money and running a registry like .com with 99.9999% reliability ends up
> with $100 million hardware costs.
>
> So the idea that I plug my business into a network of notary servers being
> run by amateurs or as a community service is a non-starter for me. We have
> to align the responsibility for running any server that the CA has a
> critical dependency on with a business model.

Note that we do not expect CAs to talk to _all_ log servers, only
those that are appropriately responsive - and also note that a CA can
fire off a dozen log requests in parallel and then just use the first
three that come back, which would deal with any temporary log issues.

We should probably add this ability to the open source stack at some point.

> Looking at the CT proposal, it seems to me that we could fix the business
> model issue and remove a lot of the CA operational issues as follows:
>
> 1) Each browser provider that is interested in enforcing a CT requirement
> stands up a meta-notary server.
>
> 2) Each CA runs their own notary server and this is the only resource that
> needs to have a check in at certificate issue.

Isn't this part the only part that's actually needed? The
meta-notaries seem like redundant extra complication (and also sound
like they fulfil essentially the same role as monitors).

I assume, btw, that by "notary server" you mean "log server"?

Also, if a CA only uses its own log, what happens when it screws up
and gets its log struck off the list of trusted logs? This is why we
recommend some redundancy in log signatures.

> 3) Each CA notary server checkpoints to one or more meta-notary servers
> every 60 minutes. As part of the check in process it uploads the whole
> information for all the certificates issued in that time interval.
>
> 4) Meta-Notaries deliver tokens that assert that the CA notaries are current
> every 60 minutes. Note here that 'current' is according to the criteria set
> by the meta notary. This is an intentional piece of 'slop' in the system.
>
> 5) The OCSP tokens delivered by the CA contain the information necessary to
> checkpoint the certificate to the Meta-Notaries.
>
> 6) A browser enforcing CT disclosure pulls a list of anchor points from its
> chosen meta-notary every 60 minutes and uses them to validate the CT
> assertions delivered in certs.
>
>
> The 'slop' introduced at the meta-notary can of course be removed if we want
> to ensure that the system is robust even if there is a collusion between the
> CA and the meta-notary. But since the whole point of the scheme is
> transparency, the meta-notary operation can be audited by third parties in
> any event.
>

From mcr@sandelman.ca  Sat Feb 16 11:21:23 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D5321F89CE for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 11:21:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFZLRloGDgxG for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 11:21:22 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 3083B21F89DA for <ietf@ietf.org>; Sat, 16 Feb 2013 11:21:22 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 849FA20168 for <ietf@ietf.org>; Sat, 16 Feb 2013 14:27:54 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E47DF6376A; Sat, 16 Feb 2013 14:20:14 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D1AAA636C5 for <ietf@ietf.org>; Sat, 16 Feb 2013 14:20:14 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: proceedings not in archival format
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 16 Feb 2013 14:20:14 -0500
Message-ID: <3547.1361042414@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Feb 2013 19:21:23 -0000

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


I could not recall the name of a vendor who was at the Bits'n'Bites in
Atlanta.   So I went to
https://www.ietf.org/meeting/85/bits-n-bites.html, but the list wasn't
there.  Since it said that they'd get an ackledgement in the plenary, I=20
went to:=20
  https://www.ietf.org/proceedings/85/technical-plenary.html

looking for the right slide.=20=20

Why are there .pptx files there?
a) It's not an archival quality format (HTML or PDF/A)
b) According to our openstand principles it's hardly a standard.

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


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

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

iQCVAwUAUR/b7oqHRg3pndX9AQIzAwQAirPIBI4ZJrXDlJ9d0nULXYFjJKP4qTT2
ZgS7Iaj1X/5Q0bOZ1dB5GPnT253qvZYNUqLfbSYcRV/8ZCkwgAdpyaGoaZ0MSSSu
jDaLdfNZ9TXf8x0RMFUL552LGwUNZw5tx+G4XoO4Rz+0asWkPNwyVeBI9E66DpWE
wo1csZZUUEE=
=Vjov
-----END PGP SIGNATURE-----
--=-=-=--

From amorris@amsl.com  Sat Feb 16 13:23:07 2013
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F3821F87DF for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 13:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.211
X-Spam-Level: 
X-Spam-Status: No, score=-1.211 tagged_above=-999 required=5 tests=[AWL=1.388,  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 hKMJYdpItC3F for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 13:23:07 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDF521F8596 for <ietf@ietf.org>; Sat, 16 Feb 2013 13:23:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 07C0A1245FB; Sat, 16 Feb 2013 13:23:07 -0800 (PST)
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 c-KuT8eGge88; Sat, 16 Feb 2013 13:23:06 -0800 (PST)
Received: from [192.168.1.182] (c-76-102-55-37.hsd1.ca.comcast.net [76.102.55.37]) by c8a.amsl.com (Postfix) with ESMTPSA id D20611245F9; Sat, 16 Feb 2013 13:23:06 -0800 (PST)
Subject: Re: proceedings not in archival format
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <3547.1361042414@sandelman.ca>
Date: Sat, 16 Feb 2013 13:22:48 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <39224CC4-B3C3-4CE3-9471-B97B1E1883E7@amsl.com>
References: <3547.1361042414@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2013 21:23:07 -0000

Michael,

You're quite correct -- our proceedings documents are supposed to be =
maintained in PDF. I'm not sure what the issue is here but I can assure =
you that I'm looking into it and that we will get this addressed as =
quickly as possible.

Regards,
Alexa

On Feb 16, 2013, at 11:20 AM, Michael Richardson wrote:

>=20
> I could not recall the name of a vendor who was at the Bits'n'Bites in
> Atlanta.   So I went to
> https://www.ietf.org/meeting/85/bits-n-bites.html, but the list wasn't
> there.  Since it said that they'd get an ackledgement in the plenary, =
I=20
> went to:=20
>  https://www.ietf.org/proceedings/85/technical-plenary.html
>=20
> looking for the right slide. =20
>=20
> Why are there .pptx files there?
> a) It's not an archival quality format (HTML or PDF/A)
> b) According to our openstand principles it's hardly a standard.
>=20
> --=20
> ]               Never tell me the odds!                 | ipv6 mesh =
networks [=20
> ]   Michael Richardson, Sandelman Software Works        | network =
architect  [=20
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on =
rails    [=20
> =09
>=20

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From hallam@gmail.com  Sat Feb 16 16:24:12 2013
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 D289221F8A5F; Sat, 16 Feb 2013 16:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 eOS4jC-u36Oh; Sat, 16 Feb 2013 16:24:11 -0800 (PST)
Received: from mail-wg0-x22a.google.com (wg-in-x022a.1e100.net [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5789621F8A47; Sat, 16 Feb 2013 16:24:11 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id 12so1829677wgh.1 for <multiple recipients>; Sat, 16 Feb 2013 16:24:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=dlrDbfKfWzX5knvTWSzHzoA6mXW4/R+O0DoN5rHbXlU=; b=o+GGFf2Nx6JqQ7CQ5222fIz6YujfKAIub8mdtW5YAx4OX7QH3ge8kKfgSe4G6VqLvV j/1EM2ikHXWQ7loCdFXs9sAQiIhz3BrepshNnD4LlxayX6Zqez6OLjeqFN2dzGmV6Koq tU3DrS8MBONYzy9sbgselqBRewB6A3KMA26zA5dYa1kpWHBmgAat27xJ16pscCF/7XqA JUYhB0lS3jQgaj0/JYXZ6Fk9/Madm8rRueHZwKe/RJNiL5lKVusOcsnyG1WgqnJRJTI+ ItA2Xv23Hw6ftXX0OwN4W+QfYwj7C4PKKyYrODN0kHvq3f1eEtlGOxXYj9VfWwOv9egI kdoA==
MIME-Version: 1.0
X-Received: by 10.194.156.170 with SMTP id wf10mr11499066wjb.25.1361060650309;  Sat, 16 Feb 2013 16:24:10 -0800 (PST)
Received: by 10.194.176.169 with HTTP; Sat, 16 Feb 2013 16:24:09 -0800 (PST)
In-Reply-To: <CABrd9SS7as7S3vz2AEOJQruCF7aJRSVGjaG6awV9YWyuQaadWQ@mail.gmail.com>
References: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com> <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com> <CABrd9SS7as7S3vz2AEOJQruCF7aJRSVGjaG6awV9YWyuQaadWQ@mail.gmail.com>
Date: Sat, 16 Feb 2013 19:24:09 -0500
Message-ID: <CAMm+LwjM6w1jdZj8Z9bmBjUJ0VQMaZdGHMG4EupRtMxuDb=12w@mail.gmail.com>
Subject: Re: [therightkey] LC comments on draft-laurie-pki-sunlight-05
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ben Laurie <benl@google.com>
Content-Type: multipart/alternative; boundary=089e012280fc94596804d5e0a0a0
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, Adam Langley <agl@google.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: Sun, 17 Feb 2013 00:24:12 -0000

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

On Sat, Feb 16, 2013 at 1:55 PM, Ben Laurie <benl@google.com> wrote:

> On 16 February 2013 10:22, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> > Sorry for the delay but I have been thinking of CT and in particular the
> > issues of
> >
> > * Latency for the CA waiting for a notary server to respond
> > * Business models for notary servers
> >
> > As a rule open source software works really well as the marginal cost of
> > production is zero. Open source services tend to sux because even though
> the
> > marginal cost of a service is negligible, large numbers times negligible
> > adds up to big numbers. Running a DNS server for a university department
> > costs very little, running it for the whole university starts to cost
> real
> > money and running a registry like .com with 99.9999% reliability ends up
> > with $100 million hardware costs.
> >
> > So the idea that I plug my business into a network of notary servers
> being
> > run by amateurs or as a community service is a non-starter for me. We
> have
> > to align the responsibility for running any server that the CA has a
> > critical dependency on with a business model.
>
> Note that we do not expect CAs to talk to _all_ log servers, only
> those that are appropriately responsive - and also note that a CA can
> fire off a dozen log requests in parallel and then just use the first
> three that come back, which would deal with any temporary log issues.
>
> We should probably add this ability to the open source stack at some point.
>
> > Looking at the CT proposal, it seems to me that we could fix the business
> > model issue and remove a lot of the CA operational issues as follows:
> >
> > 1) Each browser provider that is interested in enforcing a CT requirement
> > stands up a meta-notary server.
> >
> > 2) Each CA runs their own notary server and this is the only resource
> that
> > needs to have a check in at certificate issue.
>
> Isn't this part the only part that's actually needed? The
> meta-notaries seem like redundant extra complication (and also sound
> like they fulfil essentially the same role as monitors).
>
> I assume, btw, that by "notary server" you mean "log server"?
>
> Also, if a CA only uses its own log, what happens when it screws up
> and gets its log struck off the list of trusted logs? This is why we
> recommend some redundancy in log signatures.


That is the reason for checkpointing against meta notaries.

Otherwise a CA might not actually release the logs.

-- 
Website: http://hallambaker.com/

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

<br><br><div class=3D"gmail_quote">On Sat, Feb 16, 2013 at 1:55 PM, Ben Lau=
rie <span dir=3D"ltr">&lt;<a href=3D"mailto:benl@google.com" target=3D"_bla=
nk">benl@google.com</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">On 16 February 2013 10:22, Phillip Hallam-Baker &lt;<a hr=
ef=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; wrote:<br>
&gt; Sorry for the delay but I have been thinking of CT and in particular t=
he<br>
&gt; issues of<br>
&gt;<br>
&gt; * Latency for the CA waiting for a notary server to respond<br>
&gt; * Business models for notary servers<br>
&gt;<br>
&gt; As a rule open source software works really well as the marginal cost =
of<br>
&gt; production is zero. Open source services tend to sux because even thou=
gh the<br>
&gt; marginal cost of a service is negligible, large numbers times negligib=
le<br>
&gt; adds up to big numbers. Running a DNS server for a university departme=
nt<br>
&gt; costs very little, running it for the whole university starts to cost =
real<br>
&gt; money and running a registry like .com with 99.9999% reliability ends =
up<br>
&gt; with $100 million hardware costs.<br>
&gt;<br>
&gt; So the idea that I plug my business into a network of notary servers b=
eing<br>
&gt; run by amateurs or as a community service is a non-starter for me. We =
have<br>
&gt; to align the responsibility for running any server that the CA has a<b=
r>
&gt; critical dependency on with a business model.<br>
<br>
</div>Note that we do not expect CAs to talk to _all_ log servers, only<br>
those that are appropriately responsive - and also note that a CA can<br>
fire off a dozen log requests in parallel and then just use the first<br>
three that come back, which would deal with any temporary log issues.<br>
<br>
We should probably add this ability to the open source stack at some point.=
<br>
<div class=3D"im"><br>
&gt; Looking at the CT proposal, it seems to me that we could fix the busin=
ess<br>
&gt; model issue and remove a lot of the CA operational issues as follows:<=
br>
&gt;<br>
&gt; 1) Each browser provider that is interested in enforcing a CT requirem=
ent<br>
&gt; stands up a meta-notary server.<br>
&gt;<br>
&gt; 2) Each CA runs their own notary server and this is the only resource =
that<br>
&gt; needs to have a check in at certificate issue.<br>
<br>
</div>Isn&#39;t this part the only part that&#39;s actually needed? The<br>
meta-notaries seem like redundant extra complication (and also sound<br>
like they fulfil essentially the same role as monitors).<br>
<br>
I assume, btw, that by &quot;notary server&quot; you mean &quot;log server&=
quot;?<br>
<br>
Also, if a CA only uses its own log, what happens when it screws up<br>
and gets its log struck off the list of trusted logs? This is why we<br>
recommend some redundancy in log signatures.</blockquote><div><br></div><di=
v>That is the reason for checkpointing against meta notaries.</div><div>=A0=
</div><div>Otherwise a CA might not actually release the logs.</div></div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>

--089e012280fc94596804d5e0a0a0--

From ole@cisco.com  Sat Feb 16 17:17:59 2013
Return-Path: <ole@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A461421F85A0 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 17:17:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.444
X-Spam-Level: 
X-Spam-Status: No, score=-110.444 tagged_above=-999 required=5 tests=[AWL=0.155, 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 WYAxJPnKCdmv for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 17:17:58 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 113E221F862B for <ietf@ietf.org>; Sat, 16 Feb 2013 17:17:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=325; q=dns/txt; s=iport; t=1361063878; x=1362273478; h=date:from:reply-to:to:subject:message-id:mime-version; bh=LrZuqBK3U66MPmkNHXOuRfAV7E16ZpeS2Bxf1a3rtxI=; b=bLxD1SBfSthEFQFw1uQ8xb4MiZv1pKfSTvMa/UcsDT87RhjlQTaOpemW n2zpBfdYDXEQhfayDVD19p+jEpuk9cXRf5bbk4sXsIshFeZrKsf2InD74 hB/kU6+NJ0imDNPvwkOdpv61ixnknNwpJhwcSm/AVTs0Ag/SheLMGIb+q w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AskKAOMtIFGQ/khR/2dsb2JhbABCAzGFUbodgQEWc4JggX0TiBKcT4ZYmViNdoExKIMvA4hnkzaFVYUSgyiBUQ
X-IronPort-AV: E=Sophos;i="4.84,680,1355097600"; d="scan'208";a="11837115"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-3.cisco.com with ESMTP; 17 Feb 2013 01:17:56 +0000
Received: from [10.27.1.132] (sjc-ole-8913.cisco.com [10.27.1.132]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1H1Hs8H014746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 17 Feb 2013 01:17:56 GMT
Date: Sat, 16 Feb 2013 17:17:54 -0800 (PST)
From: Ole Jacobsen <ole@cisco.com>
To: The IETF <ietf@ietf.org>
Subject: The IETF is coming to New Delhi!
Message-ID: <alpine.OSX.2.01.1302161716200.98051@173-11-110-132-sfba.hfc.comcastbusiness.net>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Feb 2013 01:17:59 -0000

Sorry about the late announcement:

http://www.ietfindia.in/

... looks like it ends today, oh well.

:-)


Ole J. Jacobsen
Editor and Publisher,  The Internet Protocol Journal
Cisco Systems
Tel: +1 408-527-8972   Mobile: +1 415-370-4628
E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
Skype: organdemo


From eburger-l@standardstrack.com  Sat Feb 16 18:15:26 2013
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 EB88921F85AE for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 18:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level: 
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[AWL=0.889,  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 4lrvC91kHRY7 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 18:15:26 -0800 (PST)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [74.124.215.15]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA2721F858E for <ietf@ietf.org>; Sat, 16 Feb 2013 18:15:26 -0800 (PST)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:62320 helo=[192.168.15.177]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <eburger-l@standardstrack.com>) id 1U6tmW-0003o6-28; Sat, 16 Feb 2013 18:15:08 -0800
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: The IETF is coming to New Delhi!
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <alpine.OSX.2.01.1302161716200.98051@173-11-110-132-sfba.hfc.comcastbusiness.net>
Date: Sat, 16 Feb 2013 21:15:24 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <C30C4F04-E1CB-4ACD-B990-13661C147BF7@standardstrack.com>
References: <alpine.OSX.2.01.1302161716200.98051@173-11-110-132-sfba.hfc.comcastbusiness.net>
To: Ole Jacobsen <ole@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: The IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Feb 2013 02:15:27 -0000

They've got us beat by 10 years. Hope they didn't register the trademark.

On Feb 16, 2013, at 8:17 PM, Ole Jacobsen <ole@cisco.com> wrote:

> 
> Sorry about the late announcement:
> 
> http://www.ietfindia.in/
> 
> ... looks like it ends today, oh well.
> 
> :-)
> 
> 
> Ole J. Jacobsen
> Editor and Publisher,  The Internet Protocol Journal
> Cisco Systems
> Tel: +1 408-527-8972   Mobile: +1 415-370-4628
> E-mail: ole@cisco.com  URL: http://www.cisco.com/ipj
> Skype: organdemo
> 


From McQuilWP@pobox.com  Sat Feb 16 18:37:40 2013
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 E673B21F8BA7 for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 18:37:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0N+uO2gcR5Sf for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 18:37:39 -0800 (PST)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 64A6D21F84DA for <ietf@ietf.org>; Sat, 16 Feb 2013 18:37:39 -0800 (PST)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 6D0ACA3BB; Sat, 16 Feb 2013 21:37:38 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:subject:mime-version:content-type :content-transfer-encoding; s=sasl; bh=1nZQrgj9KK7D9iq54QScLx+5g eA=; b=FFlprjC+zs0ywg6jq/+w4WDWx2r2TzjvePZJPYq0tbUdUlXeSdigert9v BXrWEM/XGgGusCistFpo85Xnx641tGs7wh+3iZle5EXewiB0J1JVybw3W+KKDgm2 PEWBx0LbKzzCEvdqRs6BWzv19vqeMJght7CUqyNhm4rvx3RaKs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:subject:mime-version:content-type :content-transfer-encoding; q=dns; s=sasl; b=a8rLPsmeiQXIt/qI1AJ ztD8O0tvhCNWK8HyLjf1+XfHy1EgAAUKYKwZRDVe84nAKMttoyezK+1+zx4QS7NG GviWKrzwMx942033jVYGQwpt0qNt6Y99PGgHnS4usDDHWRVBCnfvH6gmScKW12Ud 5LwC0IxoWz3ss7MyLj5Zxgks=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 61C50A3BA; Sat, 16 Feb 2013 21:37:38 -0500 (EST)
Received: from BQ07NB (unknown [68.107.15.47]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id C0131A3B9; Sat, 16 Feb 2013 21:37:37 -0500 (EST)
Date: Sat, 16 Feb 2013 18:37:35 -0800
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1859828466.20130216183735@pobox.com>
To: IETF Discussion List <ietf@ietf.org>
Subject: draft-ruoska-encoding-00.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: FE468B64-78AA-11E2-8D2E-ACA62E706CDE-02871704!b-pb-sasl-quonix.pobox.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Feb 2013 02:37:41 -0000

Since there is no author email address in the draft, I'm sending
this to the IETF Discussion list.


Issues:

Section 2.1:
"integer idenfier" -> "integer identifier"

Section 2.1, para 2:
"Implemenations" ->"Implementations"

Section 3.1, 3rd from last para:
"These bits determines" -> "These bits determine"

Section 3.2.3, para 2:
"sub braches but braches" -> "sub branches but branches"

Section 3.2.3, para 3:
"orginal" -> "original"

Section 3.3.2:
This section should mention the format for negative numbers (2's
comp, 1's comp, signed magnitude,...)

Section 4:
No values are given for designating the 4 types of Identifier.

Section 3.4:
Definition of Extended Frame does not allow an Identifier for
*any* new data type frame. Is this reasonable?

Section 4.2, para 2:

>   Integer identifiers are used to make document less resource hungry.
                                         ^--the
>   They are very efficient from resource point of view when compared to
                                 ^--a
>   string idenfiers.  Downside is that they make debugging a bit more
               ^--ti   ^--The 
>   complicated.  People are not good in remembering semantics bind to
                                      at                       bound
>   plain numbers so debugging tools maid need access to a look at table
                                     may                   lookup
>   to convert integer idenfiers to more human friendly strings.
                           ^--ti

Section 4.3:
Ascii art diagram split across page break.

Section 5, para 2:
"Implemenations" -> "Implementations"

Section 5.1, last para:
"String indentifier" -> "String identifier"

Section 7, para 1:
"Implemenations" -> "Implementations"

Section "Author's Address":
No email address given for Jukka-Pekka Makela.

-- 
Bill McQuillan <McQuilWP@pobox.com>


From joelja@bogus.com  Sat Feb 16 20:03:50 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A766521F871E for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 20:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.889
X-Spam-Level: 
X-Spam-Status: No, score=-101.889 tagged_above=-999 required=5 tests=[AWL=0.110, 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 yfQI9FgmbXXF for <ietf@ietfa.amsl.com>; Sat, 16 Feb 2013 20:03:50 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3B18321F8700 for <ietf@ietf.org>; Sat, 16 Feb 2013 20:03:50 -0800 (PST)
Received: from joels-MacBook-Air.local (c-71-193-176-225.hsd1.wa.comcast.net [71.193.176.225]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1H43li8067320 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sun, 17 Feb 2013 04:03:47 GMT (envelope-from joelja@bogus.com)
Message-ID: <5120569E.2040808@bogus.com>
Date: Sat, 16 Feb 2013 20:03:42 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Keith Moore <moore@network-heretics.com>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com> <511EA11D.7010700@network-heretics.com> <511F3D95.3030302@gmail.com>
In-Reply-To: <511F3D95.3030302@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Sun, 17 Feb 2013 04:03:47 +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: Sun, 17 Feb 2013 04:03:50 -0000

On 2/16/13 12:04 AM, Brian E Carpenter wrote:
> On 15/02/2013 20:57, Keith Moore wrote:
> ...
>> But this makes me realize that there's a related issue.   An expectation
>> that WG meetings are for presentations, leads to an expectation that
>> there's lots of opportunity to present suggestions for new work to do.
>> WG time scheduled for considering new work can actually take away time
>> for discussion of ongoing work.   And once the time is scheduled and
>> people have made commitments to travel to meetings for the purpose of
>> presenting new work, chairs are understandably reluctant to deny them
>> their allotted presentation time.
In v6ops we require that scheduled material to be discussed in the 
meeting have been aired out on the mailing list first. That is a rather 
good filter for which discussions about new work should be accepted. The 
time between meetings is ultimately a lot more scalable and less 
precious than the time during meetings. while there is certainly the 
opportunity for WG discussion to go where it needs to, one does not plan 
a trip to the IETF on the basis of impromptu MIC time.
> This is closely related to a well-known problem at academic conferences.
> Many people can only get funded to travel if they are presenting a paper.
> It's common practice, therefore, to have either a poster session (which
> allows massively parallel presentations) or hot-topics sessions (with a
> strict and very short time-limit). We tend to throw the hot-topics sessions
> into WG meetings, which is not ideal.
There is literally no editorial barrier to the submission of an internet 
draft. Moreover the typical basis for the dicussion of an idea on a 
mailing list or in a WG meeting is that it exists as an internet draft.
>
> Why not have a poster session as part of Bits-n-Bites? It would give
> new ideas a chance to be seen without wasting WG time. Make it official
> enough that people can use it in their travel requests.
>
>      Brian
>


From lars@netapp.com  Sun Feb 17 08:39:39 2013
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F4421F8B1C for <ietf@ietfa.amsl.com>; Sun, 17 Feb 2013 08:39:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.291
X-Spam-Level: 
X-Spam-Status: No, score=-10.291 tagged_above=-999 required=5 tests=[AWL=0.308, 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 Wa87jXEzFKXZ for <ietf@ietfa.amsl.com>; Sun, 17 Feb 2013 08:39:38 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 770B621F8B19 for <ietf@ietf.org>; Sun, 17 Feb 2013 08:39:27 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.84,682,1355126400"; d="scan'208";a="22795445"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx12-out.netapp.com with ESMTP; 17 Feb 2013 08:38:52 -0800
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r1HGcqmC025484; Sun, 17 Feb 2013 08:38:52 -0800 (PST)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.54]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0328.009; Sun, 17 Feb 2013 08:38:52 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: presenting vs discussion in WG meetings (was re:Remote Participation Services)
Thread-Topic: presenting vs discussion in WG meetings (was re:Remote Participation Services)
Thread-Index: Ac4LpGgRGu+8L4AKSuKDPT5vqyIpGwAXaZCAABdQz4AARD4fgA==
Date: Sun, 17 Feb 2013 16:38:51 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E91F724448@SACEXCMBX01-PRD.hq.netapp.com>
References: <2671C6CDFBB59E47B64C10B3E0BD5923033E16C1DA@PRVPEXVS15.corp.twcable.com> <511EA11D.7010700@network-heretics.com> <511F3D95.3030302@gmail.com>
In-Reply-To: <511F3D95.3030302@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D71FE1C34B16D747B79533602E83290A@tahoe.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Keith Moore <moore@network-heretics.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: Sun, 17 Feb 2013 16:39:39 -0000

On Feb 16, 2013, at 9:04, Brian E Carpenter <brian.e.carpenter@gmail.com> w=
rote:
> Why not have a poster session as part of Bits-n-Bites? It would give
> new ideas a chance to be seen without wasting WG time. Make it official
> enough that people can use it in their travel requests.

Great idea!

(Or do it during the welcome reception - bigger room.)

Lars=

From john-ietf@jck.com  Mon Feb 18 07:29:40 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29CD121F899F for <ietf@ietfa.amsl.com>; Mon, 18 Feb 2013 07:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.658
X-Spam-Level: 
X-Spam-Status: No, score=-102.658 tagged_above=-999 required=5 tests=[AWL=-0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AQijCoc1BXYQ for <ietf@ietfa.amsl.com>; Mon, 18 Feb 2013 07:29:31 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEFD21F8A14 for <ietf@ietf.org>; Mon, 18 Feb 2013 07:29:30 -0800 (PST)
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 1U7Sem-0009JA-Up; Mon, 18 Feb 2013 10:29:28 -0500
Date: Mon, 18 Feb 2013 10:29:06 -0500
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>
Subject: Re: back by popular demand - a DNS calculator
Message-ID: <1A09DE5F552B2856CADC2F9A@JcK-HP8200.jck.com>
In-Reply-To: <511ED751.2090703@isi.edu>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net>	<511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <511EB264.2060308@isi.edu> <5DC7250E2074ECC45C666D27@JcK-HP8200.jck.com> <511ED751.2090703@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 15:29:40 -0000

--On Friday, February 15, 2013 16:48 -0800 Joe Touch
<touch@isi.edu> wrote:

> If any label were allowed, then why does IDN conversion go so
> far out of its way to exclude particular strings, e.g., those
> beginning/ending with '-' and encodes everything 0..7F into
> a-z/0-9?
> 
> (I was focused on looking up A records given FQDNs)

Now you are asking a different question, although the answer for
A RRs generally is still the same.  My apologies to those who
don't need the mini-tutorial that follows -- many of those of us
who work primarily in applications would need similar tutorials
to understand the reasons for some of the decisions in the work
of those who primarily operate at lower layers of the stack.

I recommend rereading the relevant sections of RFCs 1123 and
2181 but, briefly, the DNS doesn't impose any limitations other
than what will fit in an octet.  However, many, perhaps most,
applications do impose their own rules and those rules usually
match what 1034/1035 call the "preferred syntax" -- a syntax
derived from popular applications at the time as those
specifications make clear.  As one example with which I'm
painfully familiar, SMTP treats a domain name containing
characters outside the ASCII range as syntax violations and a
conforming implementation will never look up such a domain as
part of mail address resolution or routing.  Consequently,
something like
    Non-ASCII-String MX 0 some.domain.example.
is perfectly valid as far as the DNS is concerned but nonsense
as far as actual utility is concerned -- SMTP implementations
are the only users of MX RRs and no conforming SMTP
implementation will ever access such a record.

IDNA is a clever trick (or, from other perspectives, an ugly
hack) that accomplishes two main things:

	-- It permits IDNs to be used with applications
	including, e.g., SMTP, without changing _their_ syntax
	rules because the labels stored in the DNS and
	transmitted on the wire still conform to those
	"preferred syntax" rules.
	
	-- It warns applications and forces the additional
	restrictions and processing that enable sensible
	treatment of non-ASCII strings.  As the most obvious
	example, the case-insensitive matching that the DNS
	specifies for ASCII strings is not defined by the DNS
	for non-ASCII ones (and, indeed, becomes more
	complicated and language or locale-sensitive for some
	characters).

I don't believe the importance of the second was fully
appreciated when we got started on IDNA.  To this day, people
who believe that IDNA can be replaced by simply placing Unicode
strings encoded in UTF-8 into the DNS tend to make proposals
that ignore those issues.

The additional exclusions of IDNA such as prohibition of most
symbols in the Unicode collection and restrictions on the
appearance of "--" in the third and fourth octets of labels
apply only to IDNA implementations and are intended to provide
an extended, but still relatively safe, version of the
historical "preferred syntax" and/or to protect the syntax for
signaling special coding in the (unlikely but not impossible)
event that a different one is needed for some purpose in the
future.

The bottom line is that none of these restrictions, including
the SMTP one and the IDNA ones, are a property or requirement of
the DNS.

    best,
      john


From mrex@sap.com  Mon Feb 18 08:07:16 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94E6621F8BF8 for <ietf@ietfa.amsl.com>; Mon, 18 Feb 2013 08:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.233
X-Spam-Level: 
X-Spam-Status: No, score=-10.233 tagged_above=-999 required=5 tests=[AWL=0.016, 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 IBxE3TcP6MWo for <ietf@ietfa.amsl.com>; Mon, 18 Feb 2013 08:07:16 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9CC6E21F8A6B for <ietf@ietf.org>; Mon, 18 Feb 2013 08:07:15 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r1IG7Dio026808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 18 Feb 2013 17:07:13 +0100 (MET)
Subject: Re: back by popular demand - a DNS calculator
In-Reply-To: <CAF4+nEF07vibLRDeawu08kCJ3cDhDpC5op15=k7htTsr6c5Ygg@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 18 Feb 2013 17:07:12 +0100 (CET)
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: <20130218160712.12DBA1A594@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Feb 2013 16:07:16 -0000

Donald Eastlake wrote:
> Let's see, here is the list of RFCs that the RFC Editor believes
> update RFC 1035:
> RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 1995, RFC 1996,
> RFC 2065, RFC 2136, RFC 2181, RFC 2137, RFC 2308, RFC 2535, RFC 2845,
> RFC 3425, RFC 3658, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 5936,
> RFC 5966, RFC 6604,

Let's see, here is the list of RFCs that update STD13:
 *NONE*

http://tools.ietf.org/html/std13


;-)

-Martin

From tterribe@xiph.org  Tue Feb 19 05:46:28 2013
Return-Path: <tterribe@xiph.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 B270921F8CD2 for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 05:46:28 -0800 (PST)
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=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, 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 sKMqy5r+Yi55 for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 05:46:28 -0800 (PST)
Received: from smtp.mozilla.org (mx2.corp.phx1.mozilla.com [63.245.216.70]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDAB21F8BF6 for <ietf@ietf.org>; Tue, 19 Feb 2013 05:46:28 -0800 (PST)
Received: from [132.177.252.38] (unknown [132.177.252.38]) (Authenticated sender: tterriberry@mozilla.com) by mx2.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 5D5F2F2131 for <ietf@ietf.org>; Tue, 19 Feb 2013 05:46:27 -0800 (PST)
Message-ID: <51238232.8010705@xiph.org>
Date: Tue, 19 Feb 2013 05:46:26 -0800
From: "Timothy B. Terriberry" <tterribe@xiph.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120625 SeaMonkey/2.10.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Fwd: New Version Notification for draft-terriberry-ipr-license-00.txt
References: <20130218201949.7524.28428.idtracker@ietfa.amsl.com>
In-Reply-To: <20130218201949.7524.28428.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20130218201949.7524.28428.idtracker@ietfa.amsl.com>
Content-Type: multipart/mixed; boundary="------------040003000705030901090200"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 13:46:28 -0000

This is a multi-part message in MIME format.
--------------040003000705030901090200
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

As part of the preparations for the video-codec effort, we (Mozilla) are 
seeking feedback on a set of suitable IPR licensing terms. We hope these 
terms could be used (voluntarily) by all (or at least most) contributors 
to the effort, which would simplify the legal analysis required to 
deploy the codec. draft-terriberry-ipr-license-00 contains a first draft 
of such terms. We're very interested in getting feedback on them, both 
from those making contributions and those who might implement or deploy 
the codec.

--------------040003000705030901090200
Content-Type: message/rfc822;
 name="New Version Notification for draft-terriberry-ipr-license-00_txt.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename*0="New Version Notification for draft-terriberry-ipr-license-00";
 filename*1="_txt.eml"

Return-Path: <internet-drafts@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on kizuka
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=4.0 tests=AWL,BAYES_00 autolearn=ham
	version=3.3.2
X-Original-To: derf@kizuka.merseine.nu
Delivered-To: derf@kizuka.merseine.nu
Received: from mail.xiph.org (westfish.xiph.osuosl.org [140.211.166.32])
	by kizuka.merseine.nu (Postfix) with ESMTP id 1E96275C067
	for <derf@kizuka.merseine.nu>; Mon, 18 Feb 2013 15:19:51 -0500 (EST)
Received: by mail.xiph.org (Postfix)
	id 87A481CD9F; Mon, 18 Feb 2013 12:19:51 -0800 (PST)
Delivered-To: tterribe@xiph.org
Received: from fraxinus.osuosl.org (fraxinus.osuosl.org [140.211.166.137])
	by mail.xiph.org (Postfix) with ESMTP id 852071C38F
	for <tterribe@xiph.org>; Mon, 18 Feb 2013 12:19:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by fraxinus.osuosl.org (Postfix) with ESMTP id 7D4BF100DC9
	for <tterribe@xiph.org>; Mon, 18 Feb 2013 20:19:38 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
	by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id y5C0yBa+JY8c for <tterribe@xiph.org>;
	Mon, 18 Feb 2013 20:19:36 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from mail.ietf.org (mail.ietf.org [64.170.98.30])
	by fraxinus.osuosl.org (Postfix) with ESMTP id C582DFFE21
	for <tterribe@xiph.org>; Mon, 18 Feb 2013 20:19:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 7C2F721F8C7E
	for <tterribe@xiph.org>; Mon, 18 Feb 2013 12:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.30])
	by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6E6-Dnv3SXO4 for <tterribe@xiph.org>;
	Mon, 18 Feb 2013 12:19:49 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 0A07521F8C56
	for <tterribe@xiph.org>; Mon, 18 Feb 2013 12:19:49 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: tterribe@xiph.org
Subject: New Version Notification for draft-terriberry-ipr-license-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130218201949.7524.28428.idtracker@ietfa.amsl.com>
Date: Mon, 18 Feb 2013 12:19:49 -0800


A new version of I-D, draft-terriberry-ipr-license-00.txt
has been successfully submitted by Timothy B. Terriberry and posted to the
IETF repository.

Filename:	 draft-terriberry-ipr-license
Revision:	 00
Title:		 Example IPR License Terms
Creation date:	 2013-02-18
Group:		 Individual Submission
Number of pages: 5
URL:             http://www.ietf.org/internet-drafts/draft-terriberry-ipr-l=
icense-00.txt
Status:          http://datatracker.ietf.org/doc/draft-terriberry-ipr-licen=
se
Htmlized:        http://tools.ietf.org/html/draft-terriberry-ipr-license-00


Abstract:
   This draft gives provides an example set of licensing terms for use
   in IPR disclosures that are compatible with the goals of the proposed
   video-codec working group for further discussion and refinement by
   participants at the IETF.  Although usage of such a license is
   strictly voluntary, the hope is that getting agreement on a set of
   terms before the bulk of the work begins will allow contributors to
   use a common license and minimize the amount of legal analysis that
   must be performed in order to deploy the codec.

                                                                           =
       =



The IETF Secretariat


--------------040003000705030901090200--

From amorris@amsl.com  Tue Feb 19 10:59:15 2013
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86D2A21E80BE for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 10:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zBITqGXTqI1T for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 10:59:13 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 35AD621E80BB for <ietf@ietf.org>; Tue, 19 Feb 2013 10:59:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 32D17124159; Tue, 19 Feb 2013 10:59:12 -0800 (PST)
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 EBXF5D34gDeH; Tue, 19 Feb 2013 10:59:12 -0800 (PST)
Received: from [64.170.98.170] (unknown [64.170.98.170]) by c8a.amsl.com (Postfix) with ESMTPSA id 17D94120CF1; Tue, 19 Feb 2013 10:59:12 -0800 (PST)
Subject: Re: proceedings not in archival format
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <3547.1361042414@sandelman.ca>
Date: Tue, 19 Feb 2013 10:59:13 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <16D250D3-60B9-4737-A47C-B0B07E4AB3AE@amsl.com>
References: <3547.1361042414@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 18:59:15 -0000

Michael,

As it turns out, there was a small bug in our Proceedings tool which =
caused it to report that there were no files left to be converted from =
PPT to PDF. The bug has been repaired, and the remaining unconverted =
files have now been converted to PDF.

Thanks for bringing this to our attention.

Regards,
Alexa


On Feb 16, 2013, at 11:20 AM, Michael Richardson wrote:

>=20
> I could not recall the name of a vendor who was at the Bits'n'Bites in
> Atlanta.   So I went to
> https://www.ietf.org/meeting/85/bits-n-bites.html, but the list wasn't
> there.  Since it said that they'd get an ackledgement in the plenary, =
I=20
> went to:=20
>  https://www.ietf.org/proceedings/85/technical-plenary.html
>=20
> looking for the right slide. =20
>=20
> Why are there .pptx files there?
> a) It's not an archival quality format (HTML or PDF/A)
> b) According to our openstand principles it's hardly a standard.
>=20
> --=20
> ]               Never tell me the odds!                 | ipv6 mesh =
networks [=20
> ]   Michael Richardson, Sandelman Software Works        | network =
architect  [=20
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on =
rails    [=20
> =09
>=20

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From rpelletier@isoc.org  Tue Feb 19 18:16:40 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9BAD21F8802 for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 18:16:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQJBebx-PzoL for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 18:16:40 -0800 (PST)
Received: from smtp110.ord1c.emailsrvr.com (smtp110.ord1c.emailsrvr.com [108.166.43.110]) by ietfa.amsl.com (Postfix) with ESMTP id 0452221F880F for <ietf@ietf.org>; Tue, 19 Feb 2013 18:16:40 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 5850F980B8; Tue, 19 Feb 2013 21:16:39 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id D564E98079;  Tue, 19 Feb 2013 21:16:38 -0500 (EST)
Subject: Re: [IAOC] Sunday IAOC Overview Session
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <6.2.5.6.2.20130211222756.0b8a9540@resistor.net>
Date: Tue, 19 Feb 2013 21:16:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 02:16:41 -0000

On Feb 12, 2013, at 4:08 AM, SM wrote:

> At 14:54 11-02-2013, The IAOC wrote:
>> Please let us know ahead of time if you have specific questions you =
would like
>> to see discussed.
>=20
> The latest minutes posted by the IAB is dated January 9, 2013.  The =
latest minutes posted by the IESG is dated January 24, 2013.  The latest =
minutes posted by the IETF Trust is dated November 12, 2012.  The latest =
minutes posted by the IAOC is dated November 7, 2012.

The IAOC approved the 29 November and 13 December minutes on 31 January. =
 They are now posted.  The approval was delayed somewhat due to the =
holidays. Minutes are reviewed on the IAOC list and occasionally take a =
bit longer to achieve consensus.  The minutes for 17 and 31 January were =
approved on 14 February and are also now posted.

There haven't been any trust meetings, except one on 13 December 2012 =
for the sole purpose of approving  the minutes of 7 November, which have =
been posted.

>=20
> The IETF Trust stated previously that the "Trustees are fully in =
agreement with this requirement for openness, transparency, and =
accountability, and are making a conscious effort to increase their =
reporting and community interaction".  I leave it to the reader to =
assess the results of that effort.
>=20
> There were more than three financial statements posted yearly by the =
IAOC in 2009 and 2010.  There are only three yearly after 2010.

The 2012 Financial Statements are current through November.  December =
closes the year and will be reviewed by the Budget Committee on 26 =
February, the IAOC on the 28th and thereafter posted.  The December =
financial statement is always delayed while the Internet Society closes =
its books on the year.

>=20
> According to a RFP posted in May 2012 "Any Agreement negotiated with a =
Vendor, excluding cost, will be made public after execution".  I don't =
see the agreement at http://iaoc.ietf.org/contracts.html  The latest =
contract for the Secretariat is dated 2006.

These should have been on the web site, and will be corrected as soon as =
possible after Orlando.  Thanks for bringing this to our attention.

In an effort to make it easier to find information we are working on an =
update to the IAOC and Trust websites that will improve their =
organization.

Ray

> During a past IETF meeting someone mentioned that "BCP 101 does not =
specify this [transparency requirements] level of detail".  =46rom =
Section 7 of BCP 101:
>=20
>  "Transparency: The IETF community shall have complete visibility into
>     the financial and legal structure of the ISOC activities that are
>     related to, but not part of, the IASA standards support activity.
>     In particular, a detailed budget for the entire related ISOC
>     activity, quarterly financial reports, and audited annual
>     financial reports shall all be available to the IETF community.
>     In addition, key contract material and MOUs shall also be publicly
>     available, subject to any reasonable confidentiality obligations
>     approved by the IAOC."
>=20
> According to the IAOC:
>=20
>  "The month's financial statement will be posted within 30 days of the
>   end of the month."
>=20
>  "Minutes of IAOC meetings shall be published following their adoption
>   by the IAOC, and in any event not later than 30 days after the =
meeting."
>=20
>  "The IAD shall provide an Operations Report to the IAOC monthly, and =
to
>   the ISOC Board as required; all such reports shall be published =
online.
>   The report shall provide an update on the Budget, the performance of =
all
>   contractors, and other relevant information as shall be decided."
>=20
>  "Non-confidential agreements shall be posted upon execution. Public
>   agreements include ICANN/IANA MoUs and SLAs."
>=20
>  "When a contract contains confidential information, that information
>   shall be summarized if possible to protect its confidentiality, or =
if not,
>   extracted. The balance of the contract shall be published on the =
IASA
>   website within 14 days of execution."
>=20
> I do not have any specific questions.
>=20
> Regards,
> -sm=20


From rpelletier@isoc.org  Tue Feb 19 18:31:10 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 423F421F8881 for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 18:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 TCoOISX6446x for <ietf@ietfa.amsl.com>; Tue, 19 Feb 2013 18:31:09 -0800 (PST)
Received: from smtp110.ord1c.emailsrvr.com (smtp110.ord1c.emailsrvr.com [108.166.43.110]) by ietfa.amsl.com (Postfix) with ESMTP id 8C62021F887F for <ietf@ietf.org>; Tue, 19 Feb 2013 18:31:09 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4D59598079; Tue, 19 Feb 2013 21:31:09 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id BEE1098077;  Tue, 19 Feb 2013 21:31:08 -0500 (EST)
Subject: Re: [IAOC] Sunday IAOC Overview Session
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org>
Date: Tue, 19 Feb 2013 21:31:08 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF2444F3-451D-4B5A-8D54-70B05D5AD36E@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net> <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org>
To: Ray Pelletier <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1085)
Cc: John C Klensin <john-ietf@jck.com>, SM <sm@resistor.net>, ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 02:31:10 -0000

On Feb 19, 2013, at 9:16 PM, Ray Pelletier wrote:

>=20
> On Feb 12, 2013, at 4:08 AM, SM wrote:
>=20
>> At 14:54 11-02-2013, The IAOC wrote:
>>> Please let us know ahead of time if you have specific questions you =
would like
>>> to see discussed.
>>=20
>> The latest minutes posted by the IAB is dated January 9, 2013.  The =
latest minutes posted by the IESG is dated January 24, 2013.  The latest =
minutes posted by the IETF Trust is dated November 12, 2012.  The latest =
minutes posted by the IAOC is dated November 7, 2012.
>=20
> The IAOC approved the 29 November and 13 December minutes on 31 =
January.  They are now posted.  The approval was delayed somewhat due to =
the holidays. Minutes are reviewed on the IAOC list and occasionally =
take a bit longer to achieve consensus.  The minutes for 17 and 31 =
January were approved on 14 February and are also now posted.
>=20
> There haven't been any trust meetings, except one on 13 December 2012 =
for the sole purpose of approving  the minutes of 7 November, which have =
been posted.
>=20
>>=20
>> The IETF Trust stated previously that the "Trustees are fully in =
agreement with this requirement for openness, transparency, and =
accountability, and are making a conscious effort to increase their =
reporting and community interaction".  I leave it to the reader to =
assess the results of that effort.
>>=20
>> There were more than three financial statements posted yearly by the =
IAOC in 2009 and 2010.  There are only three yearly after 2010.
>=20
> The 2012 Financial Statements are current through November.  December =
closes the year and will be reviewed by the Budget Committee on 26 =
February, the IAOC on the 28th and thereafter posted.  The December =
financial statement is always delayed while the Internet Society closes =
its books on the year.
>=20
>>=20
>> According to a RFP posted in May 2012 "Any Agreement negotiated with =
a Vendor, excluding cost, will be made public after execution".  I don't =
see the agreement at http://iaoc.ietf.org/contracts.html  The latest =
contract for the Secretariat is dated 2006.
>=20
> These should have been on the web site, and will be corrected as soon =
as possible after Orlando.  Thanks for bringing this to our attention.
>=20
> In an effort to make it easier to find information we are working on =
an update to the IAOC and Trust websites that will improve their =
organization.
>=20
> Ray
>=20
>> During a past IETF meeting someone mentioned that "BCP 101 does not =
specify this [transparency requirements] level of detail".  =46rom =
Section 7 of BCP 101:
>>=20
>> "Transparency: The IETF community shall have complete visibility into
>>    the financial and legal structure of the ISOC activities that are
>>    related to, but not part of, the IASA standards support activity.
>>    In particular, a detailed budget for the entire related ISOC
>>    activity, quarterly financial reports, and audited annual
>>    financial reports shall all be available to the IETF community.
>>    In addition, key contract material and MOUs shall also be publicly
>>    available, subject to any reasonable confidentiality obligations
>>    approved by the IAOC."
>>=20
>> According to the IAOC:
>>=20
>> "The month's financial statement will be posted within 30 days of the
>>  end of the month."
>>=20
>> "Minutes of IAOC meetings shall be published following their adoption
>>  by the IAOC, and in any event not later than 30 days after the =
meeting."
>>=20
>> "The IAD shall provide an Operations Report to the IAOC monthly, and =
to
>>  the ISOC Board as required; all such reports shall be published =
online.
>>  The report shall provide an update on the Budget, the performance of =
all
>>  contractors, and other relevant information as shall be decided."

Operations reports are contained here:  =
http://iaoc.ietf.org/operations.html=20
and here http://iaoc.ietf.org/fstatement_detail.html

>>=20
>> "Non-confidential agreements shall be posted upon execution. Public
>>  agreements include ICANN/IANA MoUs and SLAs."

ICANN's are here:  http://iaoc.ietf.org/contracts.html

Ray

>>=20
>> "When a contract contains confidential information, that information
>>  shall be summarized if possible to protect its confidentiality, or =
if not,
>>  extracted. The balance of the contract shall be published on the =
IASA
>>  website within 14 days of execution."
>>=20
>> I do not have any specific questions.
>>=20
>> Regards,
>> -sm=20
>=20


From roland.bless@kit.edu  Tue Feb 19 18:32:28 2013
Return-Path: <roland.bless@kit.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 2612621F886B; Tue, 19 Feb 2013 18:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.268
X-Spam-Level: 
X-Spam-Status: No, score=-5.268 tagged_above=-999 required=5 tests=[AWL=-0.831, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, SARE_SPEC_REPLICA_OBFU=1.812]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xd7q9Axk8CZY; Tue, 19 Feb 2013 18:32:26 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 41DAD21F87BA; Tue, 19 Feb 2013 18:32:25 -0800 (PST)
Received: from irams1.ira.uni-karlsruhe.de ([141.3.10.5]) by iramx2.ira.uni-karlsruhe.de with esmtps port 25  id 1U7zTg-0003cs-Pm; Wed, 20 Feb 2013 03:32:22 +0100
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by irams1.ira.uni-karlsruhe.de with esmtp port 25  id 1U7zTg-00012p-1e; Wed, 20 Feb 2013 03:32:12 +0100
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 474AAA80682; Wed, 20 Feb 2013 03:32:11 +0100 (CET)
Message-ID: <512435A9.1090507@kit.edu>
Date: Wed, 20 Feb 2013 03:32:09 +0100
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: [P2PSIP] Last Call: <draft-ietf-p2psip-base-24.txt> (REsource LOcation And	Discovery (RELOAD) Base Protocol) to Proposed Standard
References: <20130206042108.14054.8941.idtracker@ietfa.amsl.com>
In-Reply-To: <20130206042108.14054.8941.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (irams1.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1361327543.009862000
Cc: p2psip@ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 02:32:28 -0000

Hi,

On 06.02.2013 05:21, The IESG wrote:
> The IESG has received a request from the Peer-to-Peer Session Initiation
> Protocol WG (p2psip) to consider the following document:
> - 'REsource LOcation And Discovery (RELOAD) Base Protocol'
>   <draft-ietf-p2psip-base-24.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-02-19. 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.

Sorry for the late comments, but I re-read the whole draft which took
some time. There are still some clarifications
necessary as well as some inconsistencies left.
Unfortunately, my comments from June, 19th were not addressed yet.
https://www.ietf.org/mail-archive/web/p2psip/current/msg06229.html

Polina Goltsman also found many issues listed below while working on an
implementation.  The list is long, but the good news is that it's
mainly clarifications that are missing.

Major issues:

1) sec. 6.3.2:
length field in Forwarding Header covers what exactly?  it is not
really clear whether the length field counts the whole message or in
case of fragmentation only the fragment size. When reading Sec 6.7 is
seems that the former is meant, but the definition could and should be
clearer. Similarly, sec. 6.7 should be clear about this, e.g.,
describing that all Forwarding Headers are identical for fragments of
the same message with exception of the fragment field.

2) sec. 7.4.1.1: replica number handling is unclear
   it is unclear how replica numbers are incremented (e.g., per
   peer) and what receiving peers should actually do with this number.
   Is it important to store the value or would a boolean be sufficient
   so that the peer knows that it's a replica?

3) sec. 6.5.2: transport protocol set for AppAttach
   Applications may require use of other transport protocols than
   those defined in OverlayLinkType (TLS/DTLS, what about plain UDP,
SCTP, DCCP, etc.),
   but currently, this seems to be not possible (do the considerations
of sec. 6.5.1.6
   apply here?).

4) sec. 6.3.4:
   How can a different signature algorithm be used if not all
implementations
   support it? There is no possibility to provide the feedback, that the
   signature algorithm is not acceptable at a particular node.

5) sec. 10.5: handling of parallel JOIN requests and use of peer_ready
   it is not clear what should happen if two JNs try to join at the same
   time at the same AP (can they be processed in parallel or should they
   be processed in sequence).
   Furthermore, when MUST/SHOULD a JN send peer_ready Update - in step 9?


Minor issues:
citations are put first, followed by comments starting with #

sec. 1.1
========
old:
   storage rather than for bulk storage of large objects.  Records are
   stored under numeric addresses which occupy the same space as node
new:
   storage rather than for bulk storage of large objects.  Records are
   stored under numeric addresses, called Resource-IDs, which occupy
   the same space as node

# Resource-IDs are used in 1.2.2 but not introduced

sec. 1.2
========
   Message Transport:  Handles end-to-end reliability, manages request
   ...

# What are the interactions with Forwarding and Link Management and
  the Topology Plugin

old:
   Forwarding and Link Management Layer:  Stores and implements the
      routing table by providing packet forwarding services between
      nodes.  It also handles establishing new links between nodes,
      including setting up connections across NATs using ICE.

# It may be confusing to say "routing table" here, since this
# is usually associated with the topology plugin. So IMHO
# it is the Connection Table, not the routing table.
# Furthermore, I propose the following change:
old:
      including setting up connections across NATs using ICE.
new:
      including setting up connections for overlay links across
      NATs using ICE.

old:
      directly between nodes.  TLS [RFC5246] and DTLS [RFC6347] are the
      currently defined "link layer" protocols used by RELOAD for hop-
new:
      currently defined "overlay link layer" protocols used by RELOAD
for hop-

# avoids confusion with the classic ISO/OSI link layer (layer 2)

old:
   In addition to the above components, nodes communicate with a central
new:
   In addition to the above components, nodes may communicate with a central

# while it may be the default case, it is not strictly required

sec. 1.3
========
old:
   RELOAD also provides an optional shared secret based admission
   control feature using shared secrets and TLS-PSK.  In order to form a
new:
   RELOAD also provides an optional shared secret based admission
   control feature using shared secrets and TLS-PSK/TLS-SRP.  In order to

# TLS-SRP should be mentioned here, too

sec. 2
======
old:
   Terms used in this document are defined inline when used and are also
new:
   Terms in this document are defined inline when used and are also

# avoid double "used"

old:
   Bootstrap Node:  A network node used by Joining Nodes to help locate
      the Admitting Peer.
new:
   Bootstrap Node:  A network node used by Joining Nodes to help accessing
      the overlay by forwarding messages to peers.

# The bootstrap node does not locate the Admitting Peer, but the JN locates
# the AP by routing a message to its own Resource-ID

old:
   Connection Table:  The set of nodes to which a node is directly
      connected, which include nodes that are not yet available for
      routing.
new:
   Connection Table:  Contains connection information for the set of
      nodes to which a node is directly connected, which include nodes
      that are not yet available for routing.

# it is a data structure ...

   Node-ID:  A value of fixed but configurable length that uniquely
      identifies a node.  Node-IDs of all 0s and all 1s are reserved and
      are invalid Node-IDs.  A value of zero is not used in the wire
      protocol but can be used to indicate an invalid node in
      implementations and APIs.  The Node-ID of all 1s is used on the
      wire protocol as a wildcard.

# what means "invalid" exactly? A wildcard can be used at least on
# the wire so it is not invalid being used as destination Node-IDs.
# So the above definition is slightly contradictory.

old:
   Responsible Peer:  The peer that is responsible for a specific
      resource, as defined by the plugin algorithm.
new:
   Responsible Peer:  The peer that is responsible for a specific
      resource, as defined by the topology plugin algorithm.

old:
   Usage:  An usage is the definition of a set of data structures (data
      Kinds) that an application wants to store in the overlay.  An
      usage may also define a set of network protocols (application IDs)
new:
   Usage:  A usage is the definition of a set of data structures (data
      Kinds) that an application wants to store in the overlay.  A
      usage may also define a set of network protocols (application IDs)

# Typo: 2x An usage -> A usage

sec. 3.1
========
old:
   o  To determine its position in the overlay topology (if the overlay
      is structured; topology plugins do not need to be structured).
new:
   o  To determine its position in the overlay topology (if the overlay
      is structured; overlays do not need to be structured).

# a structured topology plugin is not the same as a structured overlay

   o  To determine the set of resources for which the node is
      responsible.

# this isn't necessarily true for unstructured overlays?

old:
   The general principle here is that the security mechanisms (TLS at
new:
   The general principle here is that the security mechanisms ((D)TLS at

sec. 3.2
========
   entity.  From the perspective of a peer, a client is a node that has
   connected to the overlay, but has not yet taken steps to insert

# an additional reference to the Connection Table would be nice

sec. 3.2.1
==========
      clients that choose this option need to process Update messages

# Update messages are not introduced yet, so a forward reference to
# section 6.4.2.3 would be helpful

      performing an Attach.  A client wishing to connect using this
      mechanism with a certificate with multiple Node-IDs can use a Ping
      (Section 6.5.3) to probe the Node-ID of the node to which it is
      connected before doing the Attach (Section 6.5.1).

# At this point it is not really clear why this step is necessary.
# Certificates with multiple Node-IDs were not explained yet.
# Furthermore, the reference to Section 6.5.1 should be moved
# to the previous sentence.

sec. 3.3
========
old:
   This section will discuss the capabilities of RELOAD's routing layer,
new:
   This section discusses the capabilities of RELOAD's routing layer,

old:
   Resource-based routing:    RELOAD supports routing messages based
      solely on the name of the resource.  Such messages are delivered
new:
   Resource-based routing:    RELOAD supports routing messages based
      solely on the name of the resource or Resource-ID.  Such messages

old:
   Clients:    RELOAD supports requests from and to clients that do not
      participate in overlay routing, located via either of the
      mechanisms described above.
new:
   Clients:    RELOAD supports requests from and to clients that do not
      participate in overlay routing.

# the addition is not really necessary and may be confusing

old:
   Destination Lists:    While in principle it is possible to just
      inject a message into the overlay with a single Node-ID as the
new:
   Destination Lists:    While in principle it is possible to just
      inject a message into the overlay with a single Node-ID or
      a single Resource-ID as the

# Resource-ID is also a possible destination

old:
   The basic routing mechanism used by RELOAD is Symmetric Recursive.
new:
   The basic routing mode used by RELOAD is Symmetric Recursive Routing
(SRR,
   cf. Section 6.2)

# I would prefer to use the term "mode" (as on p. 28) and it should be
# consistent with the text in section 6.2

old:
   opaque ID X1 which maps internally to [A, B] (perhaps by being an
   encryption of [A, B] and forwards to Z with only X1 as the via list.
new:
   opaque ID X1 which maps internally to [A, B] (perhaps by being an
   encryption of [A, B]) and forwards to Z with only X1 as the via list.

# simple typo

old:
   RELOAD also supports a basic Iterative "routing" mode (where the
new:
   RELOAD also supports a basic Iterative routing mode (where the

old:
   Iterative "routing" is implemented using the RouteQuery method, which
new:
   Iterative routing is implemented using the RouteQuery method, which

old:
   requests this behavior.  Note that iterative "routing" is selected
new:
   requests this behavior.  Note that Iterative routing is selected

sec. 3.4
========

   pairs.  The result is a connection between A and B. At this point, A
   and B MAY send messages directly between themselves without going
   through other overlay peers.  In other words, A and B are on each
   other's connection tables.  They MAY then execute an Update process,

#  MAY is RFC 2119 terminology, which is defined in section 5
#  Besides Update process a Join process is also possible.

   order to support this case, some small number of "bootstrap nodes"
   typically need to be publicly accessible so that new peers can

# what "publicly accessible" means exactly is not defined
# typically need to be publicly accessible (i.e., not behind a NAT or
# firewall) ...

old:
   The second case is when a client connects to a peer at an arbitrary
   IP address, rather than to its responsible peer, as described in the
new:
   The second case is when a client connects to a peer at an arbitrary
   node-ID, rather than to its responsible peer, as described in the

# since responsible peer may depend on the overlay topology, node-ID
# seems to be a better fit here

sec. 3.5.2
==========
old:
   When a new peer wishes to join the Overlay Instance, it will need a
   Node-ID that it is allowed to use and a set of credentials which
new:
   When a new peer wishes to join the Overlay Instance, it needs a
   Node-ID that it is allowed to use and a set of credentials which

# not really sure about this change as non-native speaker

   match that Node-ID.  When an enrollment server is used, the Node-ID
   used is the Node-ID found in the certificate received from the

# the mode with self-signed certificates is missing and should be
# mentioned also here

   "bootstrap node".  Because this is the first connection the peer
   makes, these nodes will need public IP addresses so that they can be

# may also work if the bootstrap node is directly reachable, e.g.,
# in the same domain
# in this paragraph and the following paragraph "Once a peer"
# is used three times

   past adjacencies which have public IP address and attempt to use them

# inconsistent use of term "adjacencies"/adjacent within the document
# different meanings as follows:
#  1.) all directly connected nodes (i.e., all nodes in the Connection
Table), e.g., sec. 3.5.2  and 6.4.2.3
#  2.) all peers in the routing table
#  3.) adjacent according to the overlay topology, e.g. sec. 6.4.2.1

sec. 4
======
   limits on size, on the values which may be stored.  For many Kinds,
   the set may be restricted to a single value; some sets may be allowed

# what set?

sec. 4.1.2.
===========
old:
   responsibility if the responsible peer fail [Chord].
new:
   responsibility if the responsible peer fails [Chord].

sec. 6
======
old:
   messages.  We then describe the symmetric recursive routing model,
   which is RELOAD's default routing algorithm.  We then define the
new:
   messages.  We then describe the symmetric recursive routing mode,
   which is RELOAD's default routing mode.  We then define the

# IMHO the term mode fits best, the routing algorithm is defined
# within the topology plugin

sec. 6.1.
=========
old:
   peer SHOULD generate an appropriate error but local policy can
new:
   peer SHOULD generate an appropriate error message but local policy can

   Once the peer has determined that the message is correctly formatted

# what does "correctly formatted" mean exactly?

sec. 6.1.1.
===========
      this node so it MUST verify the signature as described in
      Section 7.1 and MUST pass it up to the upper layers.  "Upper
      layers" is used here to mean the components above the "Overlay
      Link Service Boundary" line in the figure in Section 1.2.

# this is somewhat confusing. The text describes what the
# Forwarding and link management component does, but what
# other components are meant here?

      state, e.g., by unpacking any opaque IDS.

# I think any is incorrect, since other IDs are
# not inserted by this node and so it cannot "unpack" those,
# but only its own opaque IDs

sec. 6.1.2.
===========
   the first entry on the destination list is in the peer's connection
   table, then it MUST forward the message to that peer directly.

# This is probably motivated by clients. A hint to this fact
# may help.

old:
   destination list, it would detect that I is a opaque ID, recover the
new:
   destination list, it would detect that I is an opaque ID, recover the

# Typo fix

old:
   called List Compression.  Possibilities for a opaque ID include a
new:
   called List Compression.  Possibilities for an opaque ID include a
# Typo fix

   An intermediate node receiving a request from another node MUST
   return a response to this request with a destination list equal to
   the concatenation of the Node-ID of the node that sent the request
   with the via list in the request.  The intermediate node normally

# 1.) unclear why an _intermediate_ peer should return a response
#     (if it is not the destination node),
# 2.) the via list must be reversed before concatenating the Node-ID
# so:
old:
   with the via list in the request.  The intermediate node normally
new:
   with the reversed via list in the request.  The intermediate node
normally

sec. 6.1.3.
===========
old:
   compressed via list), the peer MUST replace that entry with the
   original via list that it replaced and then re-examine the
new:
   compressed via list), the peer MUST replace that entry with the
   reversed original via list that it replaced and then re-examine the

# the via list must be reversed for responses...

sec. 6.2.
=========

old:
   This Section defines RELOAD's Symmetric Recursive Routing (SRR)
   algorithm, which is the default algorithm used by nodes to route
   messages through the overlay.  All implementations MUST implement
   this routing algorithm.  An overlay MAY be configured to use
   alternative routing algorithms, and alternative routing algorithms
   MAY be selected on a per-message basis.  I.e., a node in an overlay
   which supports SRR and some other routing algorithm called XXX might
   use SRR some of the time and XXX some of the time.
new:
   This Section defines RELOAD's Symmetric Recursive Routing (SRR)
   mode, which is the default mode used by nodes to route
   messages through the overlay.  All implementations MUST implement
   this routing mode.  An overlay MAY be configured to use
   alternative routing modes, and alternative routing modes
   MAY be selected on a per-message basis.  I.e., a node in an overlay
   which supports SRR and some other routing mode called XXX might
   use SRR some of the time and XXX some of the time.

# better use mode for consistency (algorithm is contained in the
# topology plugin

sec. 6.2.1.
===========
old:
   node MAY also construct a more complicated destination list for
   source routing.
new:
   node MAY also construct a more complicated destination list for
   (loose) source routing.

   Once the message is constructed, the node sends the message to some
   adjacent peer.  If the first entry on the destination list is
   directly connected, then the message MUST be routed down that
   connection.  Otherwise, the topology plugin MUST be consulted to
   determine the appropriate next hop.

#  adjacent peer should be adjacent node, since it may be a client
#  directly connected means: a valid entry in the Connection Table
#  exists? this should be mentioned here...

sec. 6.2.2.
===========
# a hint that the same Transaction-ID as in the request MUST be used
# could be added.

sec. 6.3.1.1.
=============
   Unless a given structure that uses a select explicitly allows for
   unknown types in the select, any unknown type SHOULD be treated as an

# How is that allowance specified in the specification? Is it by the comment
# /* This structure can be extended */

sec. 6.3.2.
===========
      receive message with a TTL greater than the current value of
      initial-ttl (or the 100 default) MUST discard the message and send
      an "Error_TTL_Exceeded" error.

# what if the initial-ttl is larger than 100 and the TTL is >100 but
# < initial-ttl? The condition "or the 100 default" holds

old:
      used to indicate the fragment offset; see Section 6.7.
new:
      used to indicate the fragment offset in bytes; see Section 6.7.

old:
   length:  The count in bytes of the size of the message, including the
      header.
new:
   length:  The count in bytes of the size of the whole unfragmented
message,
   including the header.

# as already mentioned in the beginning this should be more precise


      destinations which the message should pass through.  The
      destination list is constructed by the message originator.  The

# is it allowed that intermediate peers add destinations? if not, please
# state so

old:
      next.  The list shrinks as the message traverses each listed peer.
new:
      next.  The list may shrink as the message traverses each listed peer.

# it need not be always the case that the list shrinks with each
traversed peer

sec. 6.3.2.2.
=============
old:
   structure with a DestinationType of opaque_id_type and a opaque_id
new:
   structure with a DestinationType of opaque_id_type and an opaque_id

# typo fix

old:
   opaque
      A compressed list of Node-IDs and an eventual Resource-ID.
      Because this value was compressed by one of the peers, it is only
      meaningful to that peer and cannot be decoded by other peers.
      Thus, it is represented as an opaque string.

   resource
      The Resource-ID of the resource which is desired.  This type MUST
      only appear in the final location of a destination list and MUST
      NOT appear in a via list.  It is meaningless to try to route
      through a resource.
new:
   resource
      The Resource-ID of the resource which is desired.  This type MUST
      only appear in the final location of a destination list and MUST
      NOT appear in a via list.  It is meaningless to try to route
      through a resource.

   opaque_id_type
      A compressed list of Node-IDs and an eventual Resource-ID.
      Because this value was compressed by one of the peers, it is only
      meaningful to that peer and cannot be decoded by other peers.
      Thus, it is represented as an opaque string.

# 1.) match the order in the select
# 2.) it must be opaque_id_type, not opaque

sec. 6.3.2.3
============
   flags
      Three flags are defined FORWARD_CRITICAL(0x01),
      DESTINATION_CRITICAL(0x02), and RESPONSE_COPY(0x04).  These flags
      MUST NOT be set in a response.  If the FORWARD_CRITICAL flag is

# What is the correct reaction if these flags are set in a response?
# (returning an Error_Invalid_Message or ignore?)

sec. 6.3.3.1
============
old:
   A node processing a request MUST return its status in the
   message_code field.  If the request was a success, then the message
new:
   A node processing a request MUST return its status in the
   message_code field of a response.  If the request was a success, then
the message

# clarification?

   Error_Request_Timeout:  A response to the request has not been
      received in a suitable amount of time.  The requesting node MAY
      resend the request at a later time.

# not clear when this will ever be used. Which node should send
# this error message?

   All RELOAD messages MUST be signed.  Intermediate nodes do not verify
   signatures.  Upon receipt (and fragment reassembly if needed) the
   destination node MUST verify the signature and the authorizing
   certificate.  If the signature fails, the implementation SHOULD
   simply drop the message and MUST NOT process it.  This check provides

# What happens if none {0,0} is given? Then no Node-ID is present...

sec. 6.4.2.
===========
What happens if these messages (like Join, Leave) are accidentally sent
to a Client?
Do the send an Invalid Message back?

   A new peer (but one that already has credentials) uses the JoinReq
   message to join the overlay.  The JoinReq is sent to the responsible
   peer depending on the routing mechanism described in the topology

Is the destination address now the Resource-ID or the Node-ID
of the "responsible peer"?

   Because joins may only be executed between nodes which are directly
   adjacent, receiving peers MUST verify that any JoinReq they receive

# 1.) should be peers rather than nodes
# 2.) directly adjacent means here: directly adjacent in the overlay
# topology (could otherwise be misunderstood as being directly
# connected)
# 3.) what must happen if the verification fails?

   adjacent, receiving peers MUST verify that any LeaveReq they receive
   arrives from a transport channel that is bound to the Node-ID to be

# what happens if that verification fails?

old:
   assumed by the leaving peer.)  This also prevents replay attacks
new:
   assumed by the leaving peer.  This also prevents replay attacks

# Typo fix

sec. 6.4.2.3
============
   the state change.  In general, peers send Update messages to all
   their adjacencies whenever they detect a topology shift.

# A hint to the Connection Table and Clients would clarify

sec. 6.4.2.4.
=============
old:
   X. A RouteQuery can also request that the receiving peer initiate an
new:
   X. A RouteQuery can also request that the receiving peer initiates an

old:
   One important use of the RouteQuery request is to support iterative
   routing.  The sender selects one of the peers in its routing table

# add reference to Section 3.3.

sec. 6.4.2.4.1
==============
   destination
      The destination which the requester is interested in.  This may be
      any valid destination object, including a Node-ID, opaque ID, or
      Resource-ID.

# Does opaque ID make sense here?

sec. 6.5.1
==========
   A node sends an Attach request when it wishes to establish a direct
   TCP or UDP connection to another node for the purpose of sending

# TCP/TLS or DTLS?

old:
   node A has Attached to node B, but not received any Updates from B,
new:
   node A has attached to node B, but not received any Updates from B,

# Typo

   channel but MUST NOT route messages through B to other peers via that
   channel.  The process of Attaching is separate from the process of
# Is that also true for clients?

sec. 6.5.1.1
============
old:
        } AttachReqAns;

   The values contained in AttachReqAns are:

new:
        } AttachReq;

   The values contained in AttachReq are:

old:
      A single AttachReqAns MUST NOT include both candidates whose
new:
      A single AttachReq MUST NOT include both candidates whose

# consistency!

sec. 6.5.1.2.
=============
old:
6.5.1.2.  Response Definition

new:
6.5.1.2.  Response Definition

The AttachAns message hast the same format as the AttachReq message.


#s/AttachReqAns/AttachAns/ in the whole paragraph.

sec. 6.5.1.3.
=============

   An agent follows the ICE specification as described in [RFC5245] with

# agent was not defined in the RELOAD context so far.

sec. 6.5.4.2.
=============
old:
   o  The configuration document is correctly digitally signed (see
      Section 11 for details on signatures.
new:
   o  The configuration document is correctly digitally signed (see
      Section 11 for details on signatures).

old:
   one listed in the current configuration file).  Details on kind-
   signer field in the configuration file is described in Section 11.1.
new:
   one listed in the current configuration file).  Details on kind-
   signer field in the configuration file are described in Section 11.1.

# typos

sec. 6.6.2
==========
old:
   Each connection has it own sequence number space.  Initially the
new:
   Each connection and direction has it own sequence number space.
Initially the

sec. 6.6.3.1
============
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time.  Note that because retransmissions of the same
   message are given new sequence numbers, there may be multiple
   unacknowledged sequence numbers in use.

# Since retransmissions violate the first sentence, it may be better
# to use:
old:
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time.  Note that because retransmissions of the same
new:
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time, except for retransmissions. Note that because

   from the routing table.  The link MAY be restored to the routing
   table if ACKs resume before the connection is closed, as described

# this should read Connection Table twice?

sec. 6.7
=========
   and fragments it, each fragment has a full copy of the Forwarding

# 1.) clarification would be good that the length field is covering the
# total msg length and which field are different in the "copies"
# (at least the fragment field)
# 2.) what happens if overlapping fragments are received?


Feedback on sections 7 and greater will follow in a separate mail
later today.

Regards,
 Roland


From sm@resistor.net  Tue Feb 19 23:56:11 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D17321F888B; Tue, 19 Feb 2013 23:56:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nlxAcEDFlMdT; Tue, 19 Feb 2013 23:56:10 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6931621F86CD; Tue, 19 Feb 2013 23:56:10 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1K7u3uc013009; Tue, 19 Feb 2013 23:56:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361346969; bh=mGzozt1Dl5ufczLfm7sqTJEt5IPU2y5dn7RsRGvZ68M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=L9Z+KqqbBd4ydYVm+AEUKt3ctE9Y4tp75P4ultzYey0B02S89Md2ecNXnVbXRv2ag DiPkvGGOa1oIAeGsSq1yQEnKmvH1+kA/mZ99vO+B96nKcHCwC6yWAYw3fWxed91SVj ns9B0qpfySEcNU5JKhjTdPz/W6DDZPTw4RgM4se4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361346969; i=@resistor.net; bh=mGzozt1Dl5ufczLfm7sqTJEt5IPU2y5dn7RsRGvZ68M=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xW/+zcWoGrF4w/ZlSnwyUhoOnSdo/Fl3/3WKVR4YY2mfkEKi+PXufjMLwVoNls9ax FF3zHhU+0MRmMV7++m3FjdPzqPmaBgBM+XH25KZhaF70lAVJitc7JM2I+WEzqtaDbU 789BQgeNGznHCME+y07qvB4Bk2qzvAejLlEPf1KE=
Message-Id: <6.2.5.6.2.20130219223927.0a44f008@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 19 Feb 2013 23:25:30 -0800
To: Ray Pelletier <rpelletier@isoc.org>
From: SM <sm@resistor.net>
Subject: Re: [IAOC] Sunday IAOC Overview Session
In-Reply-To: <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net> <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 07:56:11 -0000

Hi Ray,
At 18:16 19-02-2013, Ray Pelletier wrote:
>The IAOC approved the 29 November and 13 December minutes on 31 
>January.  They are now posted.  The approval was delayed somewhat 
>due to the holidays. Minutes are reviewed on the IAOC list and 
>occasionally take a bit longer to achieve consensus.  The minutes 
>for 17 and 31 January were approved on 14 February and are also now posted.

Thanks.

>There haven't been any trust meetings, except one on 13 December 
>2012 for the sole purpose of approving  the minutes of 7 November, 
>which have been posted.

Ok.

>The 2012 Financial Statements are current through 
>November.  December closes the year and will be reviewed by the 
>Budget Committee on 26 February, the IAOC on the 28th and thereafter 
>posted.  The December financial statement is always delayed while 
>the Internet Society closes its books on the year.

Thanks for the explaining this.

At 18:31 19-02-2013, Ray Pelletier wrote:
>Operations reports are contained here:  http://iaoc.ietf.org/operations.html
>and here http://iaoc.ietf.org/fstatement_detail.html

Ok.

>ICANN's are here:  http://iaoc.ietf.org/contracts.html

The ICANN/IANA agreements are available from ICANN.

The last RFC Editor contracts are from 2008.  The last Secretariat 
contract is from 2006.  All contracts except for the ones with ICANN 
are never published even though that one of the agreements mention 
that the contract will be published.

Regards,
-sm  


From rpelletier@isoc.org  Wed Feb 20 04:45:00 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B80421F872C for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 04:45:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, 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 M7Znqh1aIhmR for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 04:44:59 -0800 (PST)
Received: from smtp78.ord1c.emailsrvr.com (smtp78.ord1c.emailsrvr.com [108.166.43.78]) by ietfa.amsl.com (Postfix) with ESMTP id 6FBD721F8798 for <ietf@ietf.org>; Wed, 20 Feb 2013 04:44:59 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id F3CC11E80B8; Wed, 20 Feb 2013 07:44:58 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 7E99D1E80BC;  Wed, 20 Feb 2013 07:44:58 -0500 (EST)
Subject: Re: [IAOC] Sunday IAOC Overview Session
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <6.2.5.6.2.20130219223927.0a44f008@resistor.net>
Date: Wed, 20 Feb 2013 07:44:57 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6CA3CD9-25D9-4D49-90D3-AC550C38DBB0@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net> <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org> <6.2.5.6.2.20130219223927.0a44f008@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
Cc: John C Klensin <john-ietf@jck.com>, iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 12:45:00 -0000

On Feb 20, 2013, at 2:25 AM, SM wrote:

> Hi Ray,
> At 18:16 19-02-2013, Ray Pelletier wrote:
>> The IAOC approved the 29 November and 13 December minutes on 31 =
January.  They are now posted.  The approval was delayed somewhat due to =
the holidays. Minutes are reviewed on the IAOC list and occasionally =
take a bit longer to achieve consensus.  The minutes for 17 and 31 =
January were approved on 14 February and are also now posted.
>=20
> Thanks.
>=20
>> There haven't been any trust meetings, except one on 13 December 2012 =
for the sole purpose of approving  the minutes of 7 November, which have =
been posted.
>=20
> Ok.
>=20
>> The 2012 Financial Statements are current through November.  December =
closes the year and will be reviewed by the Budget Committee on 26 =
February, the IAOC on the 28th and thereafter posted.  The December =
financial statement is always delayed while the Internet Society closes =
its books on the year.
>=20
> Thanks for the explaining this.
>=20
> At 18:31 19-02-2013, Ray Pelletier wrote:
>> Operations reports are contained here:  =
http://iaoc.ietf.org/operations.html
>> and here http://iaoc.ietf.org/fstatement_detail.html
>=20
> Ok.
>=20
>> ICANN's are here:  http://iaoc.ietf.org/contracts.html
>=20
> The ICANN/IANA agreements are available from ICANN.
>=20
> The last RFC Editor contracts are from 2008.  The last Secretariat =
contract is from 2006.  All contracts except for the ones with ICANN are =
never published even though that one of the agreements mention that the =
contract will be published.

We will attend to all of these after Orlando to get the contracts =
published.  Each contract will need to be reviewed for business =
confidential material before posting, typically material that may be =
business proprietary so as to not reveal matters that may assist =
competitors.  It's a necessary courtesy.

Ray

>=20
> Regards,
> -sm =20


From john-ietf@jck.com  Wed Feb 20 06:09:34 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E43D521F880B; Wed, 20 Feb 2013 06:09:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.652
X-Spam-Level: 
X-Spam-Status: No, score=-102.652 tagged_above=-999 required=5 tests=[AWL=-0.053, 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 JqkVFr+X5It9; Wed, 20 Feb 2013 06:09:34 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3D1EC21F8809; Wed, 20 Feb 2013 06:09:34 -0800 (PST)
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 1U8AMQ-000FJ8-Jg; Wed, 20 Feb 2013 09:09:26 -0500
Date: Wed, 20 Feb 2013 09:09:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ray Pelletier <rpelletier@isoc.org>
Subject: Re: [IAOC] Sunday IAOC Overview Session
Message-ID: <399FCDD9714E1F6A26A8B460@JcK-HP8200.jck.com>
In-Reply-To: <F6CA3CD9-25D9-4D49-90D3-AC550C38DBB0@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net> <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org> <6.2.5.6.2.20130219223927.0a44f008@resistor.net> <F6CA3CD9-25D9-4D49-90D3-AC550C38DBB0@isoc.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: SM <sm@resistor.net>, ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 14:09:35 -0000

--On Wednesday, February 20, 2013 07:44 -0500 Ray Pelletier
<rpelletier@isoc.org> wrote:

>> The last RFC Editor contracts are from 2008.  The last
>> Secretariat contract is from 2006.  All contracts except for
>> the ones with ICANN are never published even though that one
>> of the agreements mention that the contract will be published.
> 
> We will attend to all of these after Orlando to get the
> contracts published.  Each contract will need to be reviewed
> for business confidential material before posting, typically
> material that may be business proprietary so as to not reveal
> matters that may assist competitors.  It's a necessary
> courtesy.

Ray,

This doesn't help with the past, but I would have assumed (based
on experience in other organizations) that, if the rules require
posting contracts with confidential material elided, then the
issue of what is or is not treated as confidential would be part
of the contract negotiation process.  That would leave a version
with the appropriate material elided approved by both parties
along with the full contract and ready to publish as soon is the
contract is signed.  

It would have the small additional advantage of eliminating any
risk of a contractor claiming that everything they touch,
including broad SOW material, is confidential material that must
be protected from their competitors.  If a contractor were to
make such a claim during contract negotiation, you would
presumably just say "no, not acceptable in the IETF Community"
and move on.  If the claim were asserted only after the contract
was signed and work started, you could presumably be in for a
rather painful process.

Is there any reason why that approach cannot be taken in the
future?

regards,
   john


From rpelletier@isoc.org  Wed Feb 20 07:13:09 2013
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2949A21F8821 for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 07:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 FfsHCuMuz9U4 for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 07:13:08 -0800 (PST)
Received: from smtp110.ord1c.emailsrvr.com (smtp110.ord1c.emailsrvr.com [108.166.43.110]) by ietfa.amsl.com (Postfix) with ESMTP id 7F24B21F8803 for <ietf@ietf.org>; Wed, 20 Feb 2013 07:13:08 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 3DBF0980BA; Wed, 20 Feb 2013 10:13:08 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp6.relay.ord1c.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id B7C42980DC;  Wed, 20 Feb 2013 10:13:07 -0500 (EST)
Subject: Re: [IAOC] Sunday IAOC Overview Session
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <399FCDD9714E1F6A26A8B460@JcK-HP8200.jck.com>
Date: Wed, 20 Feb 2013 10:13:07 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <2A3E2F72-ADB3-4307-B82B-265C1A941252@isoc.org>
References: <20130211225402.13757.92479.idtracker@ietfa.amsl.com> <6.2.5.6.2.20130211222756.0b8a9540@resistor.net> <F73FF937-0D4C-4B47-B2E4-D11C24830256@isoc.org> <6.2.5.6.2.20130219223927.0a44f008@resistor.net> <F6CA3CD9-25D9-4D49-90D3-AC550C38DBB0@isoc.org> <399FCDD9714E1F6A26A8B460@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1085)
Cc: SM <sm@resistor.net>, ietf@ietf.org, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 15:13:09 -0000

On Feb 20, 2013, at 9:09 AM, John C Klensin wrote:

> 
> 
> --On Wednesday, February 20, 2013 07:44 -0500 Ray Pelletier
> <rpelletier@isoc.org> wrote:
> 
>>> The last RFC Editor contracts are from 2008.  The last
>>> Secretariat contract is from 2006.  All contracts except for
>>> the ones with ICANN are never published even though that one
>>> of the agreements mention that the contract will be published.
>> 
>> We will attend to all of these after Orlando to get the
>> contracts published.  Each contract will need to be reviewed
>> for business confidential material before posting, typically
>> material that may be business proprietary so as to not reveal
>> matters that may assist competitors.  It's a necessary
>> courtesy.
> 
> Ray,
> 
> This doesn't help with the past, but I would have assumed (based
> on experience in other organizations) that, if the rules require
> posting contracts with confidential material elided, then the
> issue of what is or is not treated as confidential would be part
> of the contract negotiation process.  That would leave a version
> with the appropriate material elided approved by both parties
> along with the full contract and ready to publish as soon is the
> contract is signed.  
> 
> It would have the small additional advantage of eliminating any
> risk of a contractor claiming that everything they touch,
> including broad SOW material, is confidential material that must
> be protected from their competitors.  If a contractor were to
> make such a claim during contract negotiation, you would
> presumably just say "no, not acceptable in the IETF Community"
> and move on.  If the claim were asserted only after the contract
> was signed and work started, you could presumably be in for a
> rather painful process.
> 
> Is there any reason why that approach cannot be taken in the
> future?

No.  A good suggestion.
Thanks
Ray



> 
> regards,
>   john
> 


From roland.bless@kit.edu  Wed Feb 20 08:36:09 2013
Return-Path: <roland.bless@kit.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 7DB3521F8816; Wed, 20 Feb 2013 08:36:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.918
X-Spam-Level: 
X-Spam-Status: No, score=-4.918 tagged_above=-999 required=5 tests=[AWL=-1.081, BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-4, SARE_SPEC_REPLICA_OBFU=1.812]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qI5N0129hnut; Wed, 20 Feb 2013 08:36:06 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id D038C21F87FB; Wed, 20 Feb 2013 08:36:04 -0800 (PST)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  id 1U8Ce8-0000J5-Ot; Wed, 20 Feb 2013 17:36:03 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 99068A80682; Wed, 20 Feb 2013 17:35:52 +0100 (CET)
Message-ID: <5124FB68.4030208@kit.edu>
Date: Wed, 20 Feb 2013 17:35:52 +0100
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: [P2PSIP] Last Call: <draft-ietf-p2psip-base-24.txt> (REsource LOcation And	Discovery (RELOAD) Base Protocol) to Proposed Standard
References: <20130206042108.14054.8941.idtracker@ietfa.amsl.com> <512435A9.1090507@kit.edu>
In-Reply-To: <512435A9.1090507@kit.edu>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1361378163.879749000
Cc: "Goltsman, Polina" <polina.goltsman@student.kit.edu>, p2psip@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2013 16:36:09 -0000

Hi again,

[this time with all comments, including chapters 7 and 10, no changes
 in the first part so you can jump to [**CONT**] if you are looking for
 the new stuff]

Sorry for the late comments, but I re-read the whole draft which took
some time. There are still some clarifications
necessary as well as some inconsistencies left.
Unfortunately, my comments from June, 19th were not addressed yet.
https://www.ietf.org/mail-archive/web/p2psip/current/msg06229.html

Polina Goltsman also found many issues listed below while working on an
implementation.  The list is long, but the good news is that it's
mainly clarifications that are missing.

Major issues:

1) sec. 6.3.2:
length field in Forwarding Header covers what exactly?  it is not
really clear whether the length field counts the whole message or in
case of fragmentation only the fragment size. When reading Sec 6.7 is
seems that the former is meant, but the definition could and should be
clearer. Similarly, sec. 6.7 should be clear about this, e.g.,
describing that all Forwarding Headers are identical for fragments of
the same message with exception of the fragment field.

2) sec. 7.4.1.1: replica number handling is unclear
   it is unclear how replica numbers are incremented (e.g., per
   peer) and what receiving peers should actually do with this number.
   Is it important to store the value or would a boolean be sufficient
   so that the peer knows that it's a replica?

3) sec. 6.5.2: transport protocol set for AppAttach
   Applications may require use of other transport protocols than
   those defined in OverlayLinkType (TLS/DTLS, what about plain UDP,
SCTP, DCCP, etc.),
   but currently, this seems to be not possible (do the considerations
of sec. 6.5.1.6
   apply here?).

4) sec. 6.3.4:
   How can a different signature algorithm be used if not all
implementations
   support it? There is no possibility to provide the feedback, that the
   signature algorithm is not acceptable at a particular node.

5) sec. 10.5: handling of parallel JOIN requests and use of peer_ready
   it is not clear what should happen if two JNs try to join at the same
   time at the same AP (can they be processed in parallel or should they
   be processed in sequence).
   Furthermore, when MUST/SHOULD a JN send peer_ready Update - in step 9?


Minor issues:
citations are put first, followed by comments starting with #

sec. 1.1
========
old:
   storage rather than for bulk storage of large objects.  Records are
   stored under numeric addresses which occupy the same space as node
new:
   storage rather than for bulk storage of large objects.  Records are
   stored under numeric addresses, called Resource-IDs, which occupy
   the same space as node

# Resource-IDs are used in 1.2.2 but not introduced

sec. 1.2
========
   Message Transport:  Handles end-to-end reliability, manages request
   ...

# What are the interactions with Forwarding and Link Management and
  the Topology Plugin

old:
   Forwarding and Link Management Layer:  Stores and implements the
      routing table by providing packet forwarding services between
      nodes.  It also handles establishing new links between nodes,
      including setting up connections across NATs using ICE.

# It may be confusing to say "routing table" here, since this
# is usually associated with the topology plugin. So IMHO
# it is the Connection Table, not the routing table.
# Furthermore, I propose the following change:
old:
      including setting up connections across NATs using ICE.
new:
      including setting up connections for overlay links across
      NATs using ICE.

old:
      directly between nodes.  TLS [RFC5246] and DTLS [RFC6347] are the
      currently defined "link layer" protocols used by RELOAD for hop-
new:
      currently defined "overlay link layer" protocols used by RELOAD
for hop-

# avoids confusion with the classic ISO/OSI link layer (layer 2)

old:
   In addition to the above components, nodes communicate with a central
new:
   In addition to the above components, nodes may communicate with a central

# while it may be the default case, it is not strictly required

sec. 1.3
========
old:
   RELOAD also provides an optional shared secret based admission
   control feature using shared secrets and TLS-PSK.  In order to form a
new:
   RELOAD also provides an optional shared secret based admission
   control feature using shared secrets and TLS-PSK/TLS-SRP.  In order to

# TLS-SRP should be mentioned here, too

sec. 2
======
old:
   Terms used in this document are defined inline when used and are also
new:
   Terms in this document are defined inline when used and are also

# avoid double "used"

old:
   Bootstrap Node:  A network node used by Joining Nodes to help locate
      the Admitting Peer.
new:
   Bootstrap Node:  A network node used by Joining Nodes to help accessing
      the overlay by forwarding messages to peers.

# The bootstrap node does not locate the Admitting Peer, but the JN locates
# the AP by routing a message to its own Resource-ID

old:
   Connection Table:  The set of nodes to which a node is directly
      connected, which include nodes that are not yet available for
      routing.
new:
   Connection Table:  Contains connection information for the set of
      nodes to which a node is directly connected, which include nodes
      that are not yet available for routing.

# it is a data structure ...

   Node-ID:  A value of fixed but configurable length that uniquely
      identifies a node.  Node-IDs of all 0s and all 1s are reserved and
      are invalid Node-IDs.  A value of zero is not used in the wire
      protocol but can be used to indicate an invalid node in
      implementations and APIs.  The Node-ID of all 1s is used on the
      wire protocol as a wildcard.

# what means "invalid" exactly? A wildcard can be used at least on
# the wire so it is not invalid being used as destination Node-IDs.
# So the above definition is slightly contradictory.

old:
   Responsible Peer:  The peer that is responsible for a specific
      resource, as defined by the plugin algorithm.
new:
   Responsible Peer:  The peer that is responsible for a specific
      resource, as defined by the topology plugin algorithm.

old:
   Usage:  An usage is the definition of a set of data structures (data
      Kinds) that an application wants to store in the overlay.  An
      usage may also define a set of network protocols (application IDs)
new:
   Usage:  A usage is the definition of a set of data structures (data
      Kinds) that an application wants to store in the overlay.  A
      usage may also define a set of network protocols (application IDs)

# Typo: 2x An usage -> A usage

sec. 3.1
========
old:
   o  To determine its position in the overlay topology (if the overlay
      is structured; topology plugins do not need to be structured).
new:
   o  To determine its position in the overlay topology (if the overlay
      is structured; overlays do not need to be structured).

# a structured topology plugin is not the same as a structured overlay

   o  To determine the set of resources for which the node is
      responsible.

# this isn't necessarily true for unstructured overlays?

old:
   The general principle here is that the security mechanisms (TLS at
new:
   The general principle here is that the security mechanisms ((D)TLS at

sec. 3.2
========
   entity.  From the perspective of a peer, a client is a node that has
   connected to the overlay, but has not yet taken steps to insert

# an additional reference to the Connection Table would be nice

sec. 3.2.1
==========
      clients that choose this option need to process Update messages

# Update messages are not introduced yet, so a forward reference to
# section 6.4.2.3 would be helpful

      performing an Attach.  A client wishing to connect using this
      mechanism with a certificate with multiple Node-IDs can use a Ping
      (Section 6.5.3) to probe the Node-ID of the node to which it is
      connected before doing the Attach (Section 6.5.1).

# At this point it is not really clear why this step is necessary.
# Certificates with multiple Node-IDs were not explained yet.
# Furthermore, the reference to Section 6.5.1 should be moved
# to the previous sentence.

sec. 3.3
========
old:
   This section will discuss the capabilities of RELOAD's routing layer,
new:
   This section discusses the capabilities of RELOAD's routing layer,

old:
   Resource-based routing:    RELOAD supports routing messages based
      solely on the name of the resource.  Such messages are delivered
new:
   Resource-based routing:    RELOAD supports routing messages based
      solely on the name of the resource or Resource-ID.  Such messages

old:
   Clients:    RELOAD supports requests from and to clients that do not
      participate in overlay routing, located via either of the
      mechanisms described above.
new:
   Clients:    RELOAD supports requests from and to clients that do not
      participate in overlay routing.

# the addition is not really necessary and may be confusing

old:
   Destination Lists:    While in principle it is possible to just
      inject a message into the overlay with a single Node-ID as the
new:
   Destination Lists:    While in principle it is possible to just
      inject a message into the overlay with a single Node-ID or
      a single Resource-ID as the

# Resource-ID is also a possible destination

old:
   The basic routing mechanism used by RELOAD is Symmetric Recursive.
new:
   The basic routing mode used by RELOAD is Symmetric Recursive Routing
(SRR,
   cf. Section 6.2)

# I would prefer to use the term "mode" (as on p. 28) and it should be
# consistent with the text in section 6.2

old:
   opaque ID X1 which maps internally to [A, B] (perhaps by being an
   encryption of [A, B] and forwards to Z with only X1 as the via list.
new:
   opaque ID X1 which maps internally to [A, B] (perhaps by being an
   encryption of [A, B]) and forwards to Z with only X1 as the via list.

# simple typo

old:
   RELOAD also supports a basic Iterative "routing" mode (where the
new:
   RELOAD also supports a basic Iterative routing mode (where the

old:
   Iterative "routing" is implemented using the RouteQuery method, which
new:
   Iterative routing is implemented using the RouteQuery method, which

old:
   requests this behavior.  Note that iterative "routing" is selected
new:
   requests this behavior.  Note that Iterative routing is selected

sec. 3.4
========

   pairs.  The result is a connection between A and B. At this point, A
   and B MAY send messages directly between themselves without going
   through other overlay peers.  In other words, A and B are on each
   other's connection tables.  They MAY then execute an Update process,

#  MAY is RFC 2119 terminology, which is defined in section 5
#  Besides Update process a Join process is also possible.

   order to support this case, some small number of "bootstrap nodes"
   typically need to be publicly accessible so that new peers can

# what "publicly accessible" means exactly is not defined
# typically need to be publicly accessible (i.e., not behind a NAT or
# firewall) ...

old:
   The second case is when a client connects to a peer at an arbitrary
   IP address, rather than to its responsible peer, as described in the
new:
   The second case is when a client connects to a peer at an arbitrary
   node-ID, rather than to its responsible peer, as described in the

# since responsible peer may depend on the overlay topology, node-ID
# seems to be a better fit here

sec. 3.5.2
==========
old:
   When a new peer wishes to join the Overlay Instance, it will need a
   Node-ID that it is allowed to use and a set of credentials which
new:
   When a new peer wishes to join the Overlay Instance, it needs a
   Node-ID that it is allowed to use and a set of credentials which

# not really sure about this change as non-native speaker

   match that Node-ID.  When an enrollment server is used, the Node-ID
   used is the Node-ID found in the certificate received from the

# the mode with self-signed certificates is missing and should be
# mentioned also here

   "bootstrap node".  Because this is the first connection the peer
   makes, these nodes will need public IP addresses so that they can be

# may also work if the bootstrap node is directly reachable, e.g.,
# in the same domain
# in this paragraph and the following paragraph "Once a peer"
# is used three times

   past adjacencies which have public IP address and attempt to use them

# inconsistent use of term "adjacencies"/adjacent within the document
# different meanings as follows:
#  1.) all directly connected nodes (i.e., all nodes in the Connection
Table), e.g., sec. 3.5.2  and 6.4.2.3
#  2.) all peers in the routing table
#  3.) adjacent according to the overlay topology, e.g. sec. 6.4.2.1

sec. 4
======
   limits on size, on the values which may be stored.  For many Kinds,
   the set may be restricted to a single value; some sets may be allowed

# what set?

sec. 4.1.2.
===========
old:
   responsibility if the responsible peer fail [Chord].
new:
   responsibility if the responsible peer fails [Chord].

sec. 6
======
old:
   messages.  We then describe the symmetric recursive routing model,
   which is RELOAD's default routing algorithm.  We then define the
new:
   messages.  We then describe the symmetric recursive routing mode,
   which is RELOAD's default routing mode.  We then define the

# IMHO the term mode fits best, the routing algorithm is defined
# within the topology plugin

sec. 6.1.
=========
old:
   peer SHOULD generate an appropriate error but local policy can
new:
   peer SHOULD generate an appropriate error message but local policy can

   Once the peer has determined that the message is correctly formatted

# what does "correctly formatted" mean exactly?

sec. 6.1.1.
===========
      this node so it MUST verify the signature as described in
      Section 7.1 and MUST pass it up to the upper layers.  "Upper
      layers" is used here to mean the components above the "Overlay
      Link Service Boundary" line in the figure in Section 1.2.

# this is somewhat confusing. The text describes what the
# Forwarding and link management component does, but what
# other components are meant here?

      state, e.g., by unpacking any opaque IDS.

# I think any is incorrect, since other IDs are
# not inserted by this node and so it cannot "unpack" those,
# but only its own opaque IDs

sec. 6.1.2.
===========
   the first entry on the destination list is in the peer's connection
   table, then it MUST forward the message to that peer directly.

# This is probably motivated by clients. A hint to this fact
# may help.

old:
   destination list, it would detect that I is a opaque ID, recover the
new:
   destination list, it would detect that I is an opaque ID, recover the

# Typo fix

old:
   called List Compression.  Possibilities for a opaque ID include a
new:
   called List Compression.  Possibilities for an opaque ID include a
# Typo fix

   An intermediate node receiving a request from another node MUST
   return a response to this request with a destination list equal to
   the concatenation of the Node-ID of the node that sent the request
   with the via list in the request.  The intermediate node normally

# 1.) unclear why an _intermediate_ peer should return a response
#     (if it is not the destination node),
# 2.) the via list must be reversed before concatenating the Node-ID
# so:
old:
   with the via list in the request.  The intermediate node normally
new:
   with the reversed via list in the request.  The intermediate node
normally

sec. 6.1.3.
===========
old:
   compressed via list), the peer MUST replace that entry with the
   original via list that it replaced and then re-examine the
new:
   compressed via list), the peer MUST replace that entry with the
   reversed original via list that it replaced and then re-examine the

# the via list must be reversed for responses...

sec. 6.2.
=========

old:
   This Section defines RELOAD's Symmetric Recursive Routing (SRR)
   algorithm, which is the default algorithm used by nodes to route
   messages through the overlay.  All implementations MUST implement
   this routing algorithm.  An overlay MAY be configured to use
   alternative routing algorithms, and alternative routing algorithms
   MAY be selected on a per-message basis.  I.e., a node in an overlay
   which supports SRR and some other routing algorithm called XXX might
   use SRR some of the time and XXX some of the time.
new:
   This Section defines RELOAD's Symmetric Recursive Routing (SRR)
   mode, which is the default mode used by nodes to route
   messages through the overlay.  All implementations MUST implement
   this routing mode.  An overlay MAY be configured to use
   alternative routing modes, and alternative routing modes
   MAY be selected on a per-message basis.  I.e., a node in an overlay
   which supports SRR and some other routing mode called XXX might
   use SRR some of the time and XXX some of the time.

# better use mode for consistency (algorithm is contained in the
# topology plugin

sec. 6.2.1.
===========
old:
   node MAY also construct a more complicated destination list for
   source routing.
new:
   node MAY also construct a more complicated destination list for
   (loose) source routing.

   Once the message is constructed, the node sends the message to some
   adjacent peer.  If the first entry on the destination list is
   directly connected, then the message MUST be routed down that
   connection.  Otherwise, the topology plugin MUST be consulted to
   determine the appropriate next hop.

#  adjacent peer should be adjacent node, since it may be a client
#  directly connected means: a valid entry in the Connection Table
#  exists? this should be mentioned here...

sec. 6.2.2.
===========
# a hint that the same Transaction-ID as in the request MUST be used
# could be added.

sec. 6.3.1.1.
=============
   Unless a given structure that uses a select explicitly allows for
   unknown types in the select, any unknown type SHOULD be treated as an

# How is that allowance specified in the specification? Is it by the comment
# /* This structure can be extended */

sec. 6.3.2.
===========
      receive message with a TTL greater than the current value of
      initial-ttl (or the 100 default) MUST discard the message and send
      an "Error_TTL_Exceeded" error.

# what if the initial-ttl is larger than 100 and the TTL is >100 but
# < initial-ttl? The condition "or the 100 default" holds

old:
      used to indicate the fragment offset; see Section 6.7.
new:
      used to indicate the fragment offset in bytes; see Section 6.7.

old:
   length:  The count in bytes of the size of the message, including the
      header.
new:
   length:  The count in bytes of the size of the whole unfragmented
message,
   including the header.

# as already mentioned in the beginning this should be more precise


      destinations which the message should pass through.  The
      destination list is constructed by the message originator.  The

# is it allowed that intermediate peers add destinations? if not, please
# state so

old:
      next.  The list shrinks as the message traverses each listed peer.
new:
      next.  The list may shrink as the message traverses each listed peer.

# it need not be always the case that the list shrinks with each
traversed peer

sec. 6.3.2.2.
=============
old:
   structure with a DestinationType of opaque_id_type and a opaque_id
new:
   structure with a DestinationType of opaque_id_type and an opaque_id

# typo fix

old:
   opaque
      A compressed list of Node-IDs and an eventual Resource-ID.
      Because this value was compressed by one of the peers, it is only
      meaningful to that peer and cannot be decoded by other peers.
      Thus, it is represented as an opaque string.

   resource
      The Resource-ID of the resource which is desired.  This type MUST
      only appear in the final location of a destination list and MUST
      NOT appear in a via list.  It is meaningless to try to route
      through a resource.
new:
   resource
      The Resource-ID of the resource which is desired.  This type MUST
      only appear in the final location of a destination list and MUST
      NOT appear in a via list.  It is meaningless to try to route
      through a resource.

   opaque_id_type
      A compressed list of Node-IDs and an eventual Resource-ID.
      Because this value was compressed by one of the peers, it is only
      meaningful to that peer and cannot be decoded by other peers.
      Thus, it is represented as an opaque string.

# 1.) match the order in the select
# 2.) it must be opaque_id_type, not opaque

sec. 6.3.2.3
============
   flags
      Three flags are defined FORWARD_CRITICAL(0x01),
      DESTINATION_CRITICAL(0x02), and RESPONSE_COPY(0x04).  These flags
      MUST NOT be set in a response.  If the FORWARD_CRITICAL flag is

# What is the correct reaction if these flags are set in a response?
# (returning an Error_Invalid_Message or ignore?)

sec. 6.3.3.1
============
old:
   A node processing a request MUST return its status in the
   message_code field.  If the request was a success, then the message
new:
   A node processing a request MUST return its status in the
   message_code field of a response.  If the request was a success, then
the message

# clarification?

   Error_Request_Timeout:  A response to the request has not been
      received in a suitable amount of time.  The requesting node MAY
      resend the request at a later time.

# not clear when this will ever be used. Which node should send
# this error message?

   All RELOAD messages MUST be signed.  Intermediate nodes do not verify
   signatures.  Upon receipt (and fragment reassembly if needed) the
   destination node MUST verify the signature and the authorizing
   certificate.  If the signature fails, the implementation SHOULD
   simply drop the message and MUST NOT process it.  This check provides

# What happens if none {0,0} is given? Then no Node-ID is present...

sec. 6.4.2.
===========
What happens if these messages (like Join, Leave) are accidentally sent
to a Client?
Do the send an Invalid Message back?

   A new peer (but one that already has credentials) uses the JoinReq
   message to join the overlay.  The JoinReq is sent to the responsible
   peer depending on the routing mechanism described in the topology

Is the destination address now the Resource-ID or the Node-ID
of the "responsible peer"?

   Because joins may only be executed between nodes which are directly
   adjacent, receiving peers MUST verify that any JoinReq they receive

# 1.) should be peers rather than nodes
# 2.) directly adjacent means here: directly adjacent in the overlay
# topology (could otherwise be misunderstood as being directly
# connected)
# 3.) what must happen if the verification fails?

   adjacent, receiving peers MUST verify that any LeaveReq they receive
   arrives from a transport channel that is bound to the Node-ID to be

# what happens if that verification fails?

old:
   assumed by the leaving peer.)  This also prevents replay attacks
new:
   assumed by the leaving peer.  This also prevents replay attacks

# Typo fix

sec. 6.4.2.3
============
   the state change.  In general, peers send Update messages to all
   their adjacencies whenever they detect a topology shift.

# A hint to the Connection Table and Clients would clarify

sec. 6.4.2.4.
=============
old:
   X. A RouteQuery can also request that the receiving peer initiate an
new:
   X. A RouteQuery can also request that the receiving peer initiates an

old:
   One important use of the RouteQuery request is to support iterative
   routing.  The sender selects one of the peers in its routing table

# add reference to Section 3.3.

sec. 6.4.2.4.1
==============
   destination
      The destination which the requester is interested in.  This may be
      any valid destination object, including a Node-ID, opaque ID, or
      Resource-ID.

# Does opaque ID make sense here?

sec. 6.5.1
==========
   A node sends an Attach request when it wishes to establish a direct
   TCP or UDP connection to another node for the purpose of sending

# TCP/TLS or DTLS?

old:
   node A has Attached to node B, but not received any Updates from B,
new:
   node A has attached to node B, but not received any Updates from B,

# Typo

   channel but MUST NOT route messages through B to other peers via that
   channel.  The process of Attaching is separate from the process of
# Is that also true for clients?

sec. 6.5.1.1
============
old:
        } AttachReqAns;

   The values contained in AttachReqAns are:

new:
        } AttachReq;

   The values contained in AttachReq are:

old:
      A single AttachReqAns MUST NOT include both candidates whose
new:
      A single AttachReq MUST NOT include both candidates whose

# consistency!

sec. 6.5.1.2.
=============
old:
6.5.1.2.  Response Definition

new:
6.5.1.2.  Response Definition

The AttachAns message hast the same format as the AttachReq message.


#s/AttachReqAns/AttachAns/ in the whole paragraph.

sec. 6.5.1.3.
=============

   An agent follows the ICE specification as described in [RFC5245] with

# agent was not defined in the RELOAD context so far.

sec. 6.5.4.2.
=============
old:
   o  The configuration document is correctly digitally signed (see
      Section 11 for details on signatures.
new:
   o  The configuration document is correctly digitally signed (see
      Section 11 for details on signatures).

old:
   one listed in the current configuration file).  Details on kind-
   signer field in the configuration file is described in Section 11.1.
new:
   one listed in the current configuration file).  Details on kind-
   signer field in the configuration file are described in Section 11.1.

# typos

sec. 6.6.2
==========
old:
   Each connection has it own sequence number space.  Initially the
new:
   Each connection and direction has it own sequence number space.
Initially the

sec. 6.6.3.1
============
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time.  Note that because retransmissions of the same
   message are given new sequence numbers, there may be multiple
   unacknowledged sequence numbers in use.

# Since retransmissions violate the first sentence, it may be better
# to use:
old:
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time.  Note that because retransmissions of the same
new:
   A node MUST NOT have more than one unacknowledged message on the DTLS
   connection at a time, except for retransmissions. Note that because

   from the routing table.  The link MAY be restored to the routing
   table if ACKs resume before the connection is closed, as described

# this should read Connection Table twice?

sec. 6.7
=========
   and fragments it, each fragment has a full copy of the Forwarding

# 1.) clarification would be good that the length field is covering the
# total msg length and which field are different in the "copies"
# (at least the fragment field)
# 2.) what happens if overlapping fragments are received?

[**CONT**]

sec. 7
======
      data may be stored in a single transaction, rather than querying
      for the value of a counter before the actual store.

# a reader may wonder which counter is meant here - slightly confusing.
# I assume that the text assumes a hypothetical different design that
# uses counters as an alternative to timestamps?

      If a node attempting to store new data in response to a user
      request (rather than as an overlay maintenance operation such as
      occurs when healing the overlay from a partition) is rejected with
      an Error_Data_Too_Old error, the node MAY elect to perform its
      store using a storage_time that increments the value used with the
      previous store.

# I don't understand what "using a storage_time that increments the
# value used with the previous store" actually means. In this case
# it is assumed that the requesting node has already the storage_time
# of the previous store available or must it send a StatReq first?
# In the former case it could simply check if localtime > storage_time
# before sending the request. By what amount should the value be
incremented?


sec. 7.4
========
old:
   o  Store values in the overlay
   o  Fetch values from the overlay
   o  Stat:  get metadata about values in the overlay
   o  Find the values stored at an individual peer
new:
   o  Store: store values in the overlay
   o  Fetch: get values from the overlay
   o  Stat: get metadata about values in the overlay
   o  Find: get values stored at an individual peer

# just consistency

sec. 7.4.1.1
============
   which represents a sequence of stored values for a given Kind.  The
   same Kind-ID MUST NOT be used twice in a given store request.  Each

# what is the proper reaction if this condition is violated by a sending
node?

   replica_number
      The number of this replica.  When a storing peer saves replicas to
      other peers each peer is assigned a replica number starting from 1
      and sent in the Store message.  This field is set to 0 when a node
      is storing its own data.  This allows peers to distinguish replica
      writes from original writes.

# must it be "When a storing (responsible) peer saves replicas to"?
# IMHO this description is too vague, since
# as stated in 2) at the beginning of this mail it is not clear
# how to assign the replica numbers when storing replicas.
# Let's assume responsible peer X stores replicas at neighbors
# A and C: gets A replica number 1 and C replica number 2?
# if node B replaces neighbor C, does B get replica number 3 or number 2?
# if the responsible peer X is replaced by a new node Y, Y will get
# get the data from peer X, but how should X change its replica number?
# Can Y simply start sending replicas beginning at 1?
# I couldn't find any place in the document where it would make a
# difference between replica number 2 and replica number 42

old:
   kind
      The Kind-ID.  Implementations MUST reject requests corresponding
      to unknown Kinds.
new:
   kind
      The Kind-ID.  Implementations MUST reject (Error_Unknown_Kind)
      requests corresponding to unknown Kinds.

# hint on the correct error message for this check

old:
   values
      The value or values to be stored.  This may contain one or more
      stored_data values depending on the data model associated with
new:
   values
      The value or values to be stored.  This may contain one or more
      StoredData values depending on the data model associated with

# consistency

old:
   o  The signatures over each individual data element (if any) are
new:
   o  The signatures over each individual StoredData element (if any) are
# consistency

   o  For original (non-replica) stores, the peer MUST check that if the
      generation counter is non-zero, it equals the current value of the
      generation counter for this Kind.  This feature allows the
      generation counter to be used in a way similar to the HTTP Etag
      feature.

# what is the proper reaction in case the check fails? A reference to the
# mentioned HTTP Etag feature would also be nice.

   o  The storage time values are greater than that of any value which
      would be replaced by this Store.
   o  The size and number of the stored values is consistent with the
      limits specified in the overlay configuration.

# what is the reaction in case the checks fail?

   If all these checks succeed, the peer MUST attempt to store the data

# this seems to suggest that the list is complete, though more checks are
# describe in the following section 7.4.1.2. Maybe it's more consistent
# to have them described in one place.

sec.7.4.1.2.
=============

   replicas
      The list of other peers at which the data was/will be replicated.
      In overlays and applications where the responsible peer is
      intended to store redundant copies, this allows the storing node
      to independently verify that the replicas have in fact been
      stored.  It does this verification by using the Stat method (see
      Section 7.4.3).  Note that the storing node is not required to
      perform this verification.

# what is meant by the term "storing node"? Is this the responsible node
# who actually stores the data or is it the node who originated the
# StoreReq? This may be inconsistent with the rest of the document.
# Moreover, it is not clear that this implies a certain order. Must
# the responsible node having successfully finished storing the replicas
# before returning the replicas?

   If any type of request tries to access a data Kind that the peer does
   not know about, an Error_Unknown_Kind MUST be generated.  The

# The reaction is defined differently for StoreReq, FetchReq, StatReq
# and FindReq:
# - StoreReq: send back Error_Unknown_Kind
# - FetchReq: "Implementations SHOULD reject requests corresponding to
#              unknown Kinds unless specifically configured otherwise."
#   -> what means "reject" exactly?
# - StatReq: no hint given how to behave
# - FindReq: "If a Kind-ID is not known, then the corresponding
Resource-ID MUST be
   0." -> Cannot distinguish from the case where a Resource-ID is not known:
#      "The closest Resource-ID to the specified Resource-ID.  This is 0
#       if no Resource-ID is known."
#
# Is the intention to trigger Configuration update requests?
# cf. StoreReq: A node which
#   receives this error MUST generate a ConfigUpdate message which
#   contains the appropriate Kind definition (assuming that in fact a
#   Kind was used which was defined in the configuration document).

sec. 7.4.1.3
=============

   remove a value, the owner stores a new DataValue with "exists" set to
   False:

      exists = False
      value = {} (0 length)

# what happens if a value is given?
# Ignore the value or reject with an error invalid message?

sec. 7.4.2.2.
=============
old:
           uint64                 generation;
new:
           uint64                 generation_counter;
and
old:
   generation
      the generation counter for this Kind.
new:
   generation_counter
      the generation counter for this Kind.

# consistency

sec. 7.4.4.1:
=============

   kinds
      The desired Kind-IDs.  Each value MUST only appear once, and if
      not the request MUST be rejected with an error.

# What is the error code?

sec. 7.4.4.2:
=============
   The response is simply a series of FindKindData elements, one per
   Kind, concatenated end-to-end.  The contents of each element are:

# unclear what end-to-end means here?

sec. 10
=======
   protocol.  A short list of differences:

# A further difference is the fact that CHORD uses hashes of IP addresses
# while in RELOAD nodes get assigned Node-IDs and the routing table
# does not contain "underlay addresses"

sec. 10.1
=========
old:
   and n+1, with all arithmetic being done modulo 2^{k}, where k is the
   length of the Node-ID in bits, so that node 2^{k} - 1 is directly
new:
   and n+1, with all arithmetic being done modulo 2^(k), where k is the
   length of the Node-ID in bits, so that node 2^(k) - 1 is directly

# consistency with other formulas...

sec. 10.3
=========
   If a peer is not responsible for a Resource-ID k, but is directly
   connected to a node with Node-ID k, then it MUST route the message to

# what means "directly connected" here? Is it an entry in the
ConnectionTable
# or RoutingTable? I guess the former in order to cover routing to Clients

sec. 10.5
=========
   1.  JN MUST connect to its chosen bootstrap node.

# it is unclear what "connect" exactly means. This is actually
# described in Sec. 11.4:
#  "When contacting a bootstrap node, the joining node MUST first form
#   the DTLS or TLS connection to the bootstrap node and then sends an
#   Attach request over this connection with the destination Node-ID set
#   to the joining node's Node-ID."
# So my suggestion is to explain it a little but more or to put a forward
# reference to section 11.4.

   2.  JN SHOULD send an Attach request to the admitting peer (AP) for
       Node-ID n.  The "send_update" flag can be used to acquire the
       routing table for AP.

# This is inconsistent with Section 12 stating
# "JN then sends an Attach through that peer to a resource ID of itself
(JN)."
# (Node ID n vs. Resource-ID n)
#
# Moreover, it is not clear how the JN finds the AP. This is explained in
#Section 12:
#   to one of the bootstrap nodes.  JN then sends an Attach through that
#   peer to a resource ID of itself (JN).  It gets routed to the
#   admitting peer (AP) because JN is not yet part of the overlay.  When
# I suggest to change it to:
   2.  JN SHOULD send an Attach request to Resource-ID of itself (JN) in
       order to contact the Admitting peer (AP) for Node-ID n.
       The "send_update" flag can be used to acquire the
       routing table from AP.
# Question: should it be "acquire the routing table of AP" or "acquire the
# routing table from AP"?

   3.  JN SHOULD send Attach requests to initiate connections to each of
       the peers in the neighbor table as well as to the desired finger
       table entries.  Note that this does not populate their routing
       tables, but only their connection tables, so JN will not get
       messages that it is expected to route to other nodes.

# here it is unclear that the Attach requests are sent via the AP
# and what "desired" finger table entries means, e.g., in contrast to all?

# why are we having two SHOULDs instead of two MUSTs, since 10.7 states:
#    A peer MUST maintain an association (via Attach) to every member of
#   its neighbor set.  A peer MUST attempt to maintain at least three


   In order to set up its i'th finger table entry, JN MUST send an
   Attach to peer n+2^(128-i).  This will be routed to a peer in

# instead of peer n+2^(128-i) better resource-ID n+2^(128-i)?

# How should an AP react if it detects that a JN sent
# the Join to the wrong AP (not responsible at all or not
# anymore)?

sec. 10.7.
==========
   A peer MUST maintain an association (via Attach) to every member of
   its neighbor set.  A peer MUST attempt to maintain at least three

# why only to the neighbor set and not the whole routing table?

Sec. 10.7.1:
============
   Every time a connection to a peer in the neighbor table is lost (as
   determined by connectivity pings or the failure of some request), the

# I think that "connectivity pings" means periodically sent Pings to all
# members of the Connection Table by the Link Management Layer as
# mentioned in sec. 6.5. A reference may help here.
# However, I couldn't find out how often such "connectivity pings" should
# be sent (the chord-ping-interval is only related to pinging finger table
# entries).

# It is unclear to me why (sec. 10.7.1) the spec states:
#  "peer MUST remove the entry from its neighbor table and replace it
#   with the best match it has from the other peers in its routing table.
#   If using reactive recovery, it then sends an immediate Update to all
#   nodes in its Neighbor Table."
#  so the peer replaces the failed entry with one of its fingers,
#  which is maybe a poor choice, and sends this information to
#  its neighbors. IMHO it makes much more sense to request routing
#  information from the neighbors in order to get a better replacement
#  for the lost peer, instead of "confusing" the neighbors with more
#  inaccurate routing information.

   If the neighbor failure affects the peer's range of responsible IDs,
   then the Update MUST be sent to all nodes in its Connection Table.

# a short hint that it's the Connection Table instead of the Neighbor Table
# due to Clients would be nice

   If connectivity is lost to all successor peers in the neighbor table,
   then this peer SHOULD behave as if it is joining the network and MUST
   use Pings to find a peer and send it a Join.  If connectivity is lost

# Only Join or Attach and Join?

Sec. 10.7.2.:
=============
   If a finger table entry is found to have failed, all references to

# how is it determined to have "failed"? 10.7.1 is only
# related to neighbor failures...does the same definition
# apply here?

Sec. 10.7.3.:
=============
   If the neighbor failure affects the peer's range of responsible IDs,
   then the Update MUST be sent to all nodes in its Connection Table.

# add hint that it's Connection Table due to Clients

   interval" element (denominated in seconds.)  A peer SHOULD randomly
   offset these Update requests so they do not occur all at once.

# This is a little bit too imprecise.
# How should this be done? A typical mechanism
# is using a randomly chosen offset from an interval [0.5*Tp,1.5*Tp]
# where Tp is the target period, cf.
# S. Floyd, V. Jacobson, „The Synchronization of Periodic Routing
# Messages“, IEEE/ACM Transactions on Networking, Vol. 2, No. 2, April,
# 1994, http://portal.acm.org/citation.cfm?id=187045

Sec: 10.7.4.2.:
==============
   A peer SHOULD NOT send Ping requests looking for new finger table
   entries more often than the configuration element "chord-ping-
   interval", which defaults to 3600 seconds (one per hour).

# This paragraph should probably moved some paragraphs down as it
# has been stated yet that a peer should actually send Ping requests
# at all (this is explained in the subsequent paragraphs).

Sec 12:
========
# throughout the figures: "Update" should be "UpdateReq"
# and Attach should be AttachReq?
# Otherwise it's not consistent with the use of Attach vs.
AttachReq/AttachAns

Neighbor Table and Connection Table are written sometimes
in lower case and sometimes in upper case style. I'm sure that
the RFC editor will ask for consistency in writing...

That's all for now...

Regards,
 Roland


From carlosm3011@gmail.com  Wed Feb 20 18:46:23 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7270E21F8C54 for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 18:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KN7bfdagQm1M for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 18:46:22 -0800 (PST)
Received: from mail-qc0-f179.google.com (mail-qc0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id A1D0321F8C49 for <ietf@ietf.org>; Wed, 20 Feb 2013 18:46:22 -0800 (PST)
Received: by mail-qc0-f179.google.com with SMTP id b40so3369483qcq.38 for <ietf@ietf.org>; Wed, 20 Feb 2013 18:46:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UbQL/vAimYzI3t8AyVQqDTZo8dMyRaufIHIq9pav+4U=; b=Tzf6OfLNKwB22YVOPPeytdHTh6G+6cupKYl+tzTw2BP7eQxLyBZvaE/Jwb/uH3/miz eaMuO68XdxFBy1OmF8jVcIABE96Y96ODSaT0idULoaoEBwwxyoJkQSN98QePpEX4akMu 17Bvh8+VHgrY1umibqEqRQtAF9aE6iCajxiDZtJIgMM6Fx2yJZlDuWEK3LHvZ+v5T7lx 0yUQs5HwypqH6u6OOokmuTi6ClmpSjKMMf2TytF0sckSF4YPrk0jvveqDQ5O+IHsZ2ZW qsA+il6rBx80942YsZW+4CmXGvEPmwZxfRM9zO41upEgYMXEF6LoCF+CuwV9+XyLLCfO j/mQ==
X-Received: by 10.49.59.48 with SMTP id w16mr11065554qeq.38.1361414782167; Wed, 20 Feb 2013 18:46:22 -0800 (PST)
Received: from bonaire.local ([190.167.194.178]) by mx.google.com with ESMTPS id dw10sm15448964qab.11.2013.02.20.18.46.19 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 20 Feb 2013 18:46:21 -0800 (PST)
Message-ID: <51258A78.5000501@gmail.com>
Date: Wed, 20 Feb 2013 22:46:16 -0400
From: "Carlos M. martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: back by popular demand - a DNS calculator
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net>
In-Reply-To: <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2013 02:46:23 -0000

Wasn't the 'evil bit' able to hold the value 2 ?

Use all evil bits for IP addresses and we'll soon have no need for IPv6.

:D

~C.

On 2/15/13 6:45 PM, Warren Kumari wrote:
> 
> On Feb 15, 2013, at 5:06 PM, Patrik Fältström <paf@frobbit.se> wrote:
> 
>> On 15 feb 2013, at 18:19, Joe Touch <touch@ISI.EDU> wrote:
>>
>>> 	- the Bert version uses DNS strings that aren't valid
>>> 	(*, +, ',', ++)
>>
>> Are we going to open again the question whether the DNS protocol can handle any value in the octets, as compared to the hostname definition that says something more limited? ;-)
> 
> Sure -- the DNS protocol *cannot* "handle any value in the octets" -- in fact, there are an *infinite* number of values it cannot handle *in the octets*. For example, it cannot handle 257. It also cannot handle 321, nor 19.3...
> 
> :-P
> W
> 
>>
>>   Patrik
>>
> 
> --
> Don't be impressed with unintelligible stuff said condescendingly.
>     -- Radia Perlman.
> 
> 
> 
> 
> 

From smb@cs.columbia.edu  Wed Feb 20 19:46:46 2013
Return-Path: <smb@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C2321F8CED for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 19:46:46 -0800 (PST)
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 d4xLE9V51CbV for <ietf@ietfa.amsl.com>; Wed, 20 Feb 2013 19:46:45 -0800 (PST)
Received: from rambutan.cc.columbia.edu (rambutan.cc.columbia.edu [128.59.29.5]) by ietfa.amsl.com (Postfix) with ESMTP id D3AAB21F8CE3 for <ietf@ietf.org>; Wed, 20 Feb 2013 19:46:44 -0800 (PST)
Received: from [10.9.0.182] (fireball.cs.columbia.edu [128.59.13.10]) (user=smb2132 mech=PLAIN bits=0) by rambutan.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id r1L3kelv004669 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2013 22:46:40 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] back by popular demand - a DNS calculator
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <51258A78.5000501@gmail.com>
Date: Wed, 20 Feb 2013 22:46:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <881E7F7A-947B-4E30-A5ED-F16180B292A1@cs.columbia.edu>
References: <511D6D18.8000205@isi.edu> <511D6E18.2020205@forfun.net> <511E6E05.9040302@isi.edu> <88B5FFF0-751F-42FE-BE37-32B0DF414DBA@frobbit.se> <4321F24F-FCB5-47E8-8775-F60ED5080211@kumari.net> <51258A78.5000501@gmail.com>
To: "Carlos M. martinez" <carlosm3011@gmail.com>
X-Mailer: Apple Mail (2.1499)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.5
Cc: ietf@ietf.org, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2013 03:46:46 -0000

On Feb 20, 2013, at 9:46 PM, Carlos M. martinez <carlosm3011@gmail.com> =
wrote:

> Wasn't the 'evil bit' able to hold the value 2 ?
>=20
Yes, but we need an RFC for that.  =46rom RFC 3514:

6. IANA Considerations

   This document defines the behavior of security elements for the 0x0
   and 0x1 values of this bit.  Behavior for other values of the bit may
   be defined only by IETF consensus [RFC2434].


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From listsebby@me.com  Thu Feb 21 12:55:42 2013
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 D36AB21F8F41 for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 12:55:41 -0800 (PST)
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 CUusMWUsLLxH for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 12:55:41 -0800 (PST)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtp001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id 024CD21F8F40 for <ietf@ietf.org>; Thu, 21 Feb 2013 12:55:40 -0800 (PST)
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MIL0048V8SP35B0@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Thu, 21 Feb 2013 20:55:39 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327,1.0.431,0.0.0000 definitions=2013-02-21_08:2013-02-21, 2013-02-21, 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-1302210211
Content-type: text/plain; charset=us-ascii
MIME-version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Bonjour-dev Digest, Vol 10, Issue 19
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <607A7C4F-2FBC-4DCD-853E-8E8735394991@latencyzero.com>
Date: Thu, 21 Feb 2013 20:55:36 +0000
Content-transfer-encoding: quoted-printable
Message-id: <3E07105E-58DC-4E08-AC9F-D259A0A4B16F@me.com>
References: <mailman.9.1361476805.17107.bonjour-dev@lists.apple.com> <5126829A.7090509@oracle.com> <607A7C4F-2FBC-4DCD-853E-8E8735394991@latencyzero.com>
To: Rick Mann <rmann@latencyzero.com>
X-Mailer: Apple Mail (2.1499)
Cc: bonjour-dev@lists.apple.com, David Brower <david.brower@oracle.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, 21 Feb 2013 20:55:42 -0000

(Because this was brought up very, very recently.)

On 21 Feb 2013, at 20:28, Rick Mann <rmann@latencyzero.com> wrote:
> On Feb 21, 2013, at 12:24 , David Brower <david.brower@oracle.com> =
wrote:
>> It depends on the records.  If you phrase it like you that, you will =
probably get the blank stare answer.  When you start talking about the =
PTR, SRV and TXT records specifically, then you'll have a case -- but it =
isn't really Bonjour that is the proximate force, because those were =
issues against interpretations of the previous RFCs.
>>=20
>> Now, the legalistic point I'm debating at the moment is whether it is =
proper and/or legal to have the SRV record use as the target name the =
string version of an ip4 address, eg:  "192.169.0.145".   That's a =
perfectly legal and representable set of characters for a hostname, so =
maybe OK.   How about for an ip6 address  with colons, which aren't =
allowed in hostnames?
>=20
> All I know is that a couple years ago, I tried and failed with both =
DynDNS and DNSMadeEasy to get them to allow me to put spaces in TXT =
records. I cited all relevant material I could find, but they kept going =
back to the original DNS specifications saying those didn't allow =
spaces.

RFC 1035, 2.3.1, wisely advises the use of compatible constraints on =
labels in host names.  I am aware that DNS is binary transparent, and =
mDNS/DNS-SD make use of that feature to be useful, but I can well =
understand the scepticism of your DNS hosts.  Perhaps this is a =
legitimate call to relax the restrictions, *if* the operator/user is =
aware of the potential consequences.

Cheers,
Sabahattin


From marka@isc.org  Thu Feb 21 16:36:41 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B6121E803C for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 16:36:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.139
X-Spam-Level: 
X-Spam-Status: No, score=-2.139 tagged_above=-999 required=5 tests=[AWL=0.460,  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 nVqNQ8d+mf-E for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 16:36:40 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id EC56321E8034 for <ietf@ietf.org>; Thu, 21 Feb 2013 16:36:39 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 5E67A5F9865; Fri, 22 Feb 2013 00:36:27 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1361493399; bh=GCQednnDbdiD+IstM0GARNVIyVt/5Nuty56Srdubxns=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=k6CTHVqkO5MCf0OUPnnJqx+rE4F+VjuR778GvF+6sxHU3iska/CMplHYN9WWxGdnI 6os8BtOwIw5zplGgLrXrXpJDQdan9c6YNfGL1MxZWWxzsjc7kaZ+/cCfdkHYXtMW6+ YQmEw08dAuNAkuy9808ITB8cQVc9LIoceKaszlAs=
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 B603D216C3B; Fri, 22 Feb 2013 00:36:25 +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 D67B42FF36F2; Fri, 22 Feb 2013 11:36:23 +1100 (EST)
To: Sabahattin Gucukoglu <listsebby@me.com>
From: Mark Andrews <marka@isc.org>
References: <mailman.9.1361476805.17107.bonjour-dev@lists.apple.com> <5126829A.7090509@oracle.com> <607A7C4F-2FBC-4DCD-853E-8E8735394991@latencyzero.com> <3E07105E-58DC-4E08-AC9F-D259A0A4B16F@me.com>
Subject: Re: Bonjour-dev Digest, Vol 10, Issue 19
In-reply-to: Your message of "Thu, 21 Feb 2013 20:55:36 -0000." <3E07105E-58DC-4E08-AC9F-D259A0A4B16F@me.com>
Date: Fri, 22 Feb 2013 11:36:23 +1100
Message-Id: <20130222003623.D67B42FF36F2@drugs.dv.isc.org>
Cc: Rick Mann <rmann@latencyzero.com>, bonjour-dev@lists.apple.com, "ietf@ietf.org" <ietf@ietf.org>, David Brower <david.brower@oracle.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, 22 Feb 2013 00:36:41 -0000

In message <3E07105E-58DC-4E08-AC9F-D259A0A4B16F@me.com>, Sabahattin Gucukoglu 
writes:
> (Because this was brought up very, very recently.)
> 
> On 21 Feb 2013, at 20:28, Rick Mann <rmann@latencyzero.com> wrote:
> > On Feb 21, 2013, at 12:24 , David Brower <david.brower@oracle.com> 
> wrote:
> >> It depends on the records.  If you phrase it like you that, you will 
> >> probably get the blank stare answer.  When you start talking about the 
> >> PTR, SRV and TXT records specifically, then you'll have a case -- but it 
> >> isn't really Bonjour that is the proximate force, because those were 
> >> issues against interpretations of the previous RFCs.
> >> 
> >> Now, the legalistic point I'm debating at the moment is whether it is 
> >> proper and/or legal to have the SRV record use as the target name the 
> >> string version of an ip4 address, eg:  "192.169.0.145".   That's a 
> >> perfectly legal and representable set of characters for a hostname, so 
> >> maybe OK.

Actually it isn't a legal hostname if it is supposed to be a fully
qualified host name as all digit tlds are prohibited in valid host
names.  RFC 1123

> >> How about for an ip6 address  with colons, which aren't allowed in 
> >> hostnames?
> > 
> > All I know is that a couple years ago, I tried and failed with both 
> > DynDNS and DNSMadeEasy to get them to allow me to put spaces in TXT 
> > records. I cited all relevant material I could find, but they kept going 
> > back to the original DNS specifications saying those didn't allow spaces.

RFC 1035 permits spaces in TXT records.
RFC 1035 permits spaces in domain names.

You either using a " delimited string or \032 to represent a space.

RFC 1035:
<character-string> is expressed in one or two ways: as a contiguous set
of characters without interior spaces, or as a string beginning with a "
and ending with a ".  Inside a " delimited string any character can
occur, except for a " itself, which must be quoted using \ (back slash).

\DDD            where each D is a digit is the octet corresponding to
                the decimal number described by DDD.  The resulting
                octet is assumed to be text and is not checked for
                special meaning.

DynDNS and DNSMadeEasy are wrong in this respect.
 
> RFC 1035, 2.3.1, wisely advises the use of compatible constraints on 
> labels in host names.  I am aware that DNS is binary transparent, and 
> mDNS/DNS-SD make use of that feature to be useful, but I can well 
> understand the scepticism of your DNS hosts.  Perhaps this is a 
> legitimate call to relax the restrictions, *if* the operator/user is 
> aware of the potential consequences.
> 
> Cheers,
> Sabahattin

-- 
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 Feb 21 21:53:10 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEB7D21F8C75 for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 21:53:10 -0800 (PST)
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 K+mMPHTqvR+s for <ietf@ietfa.amsl.com>; Thu, 21 Feb 2013 21:53:10 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 11F6F21F86A9 for <ietf@ietf.org>; Thu, 21 Feb 2013 21:53:09 -0800 (PST)
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, 21 Feb 2013 22:53:09 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 21 Feb 2013 22:53:08 -0700
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 323AA3E4003F for <ietf@ietf.org>; Thu, 21 Feb 2013 22:52:58 -0700 (MST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r1M5r6qB368282 for <ietf@ietf.org>; Thu, 21 Feb 2013 22:53:06 -0700
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 r1M5r4ar025025 for <ietf@ietf.org>; Thu, 21 Feb 2013 22:53:04 -0700
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 r1M5r3cg025000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 21 Feb 2013 22:53:04 -0700
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 r1M5r2vn006104 for <ietf@ietf.org>; Fri, 22 Feb 2013 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r1M5r22p006059 for ietf@ietf.org; Fri, 22 Feb 2013 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201302220553.r1M5r22p006059@rotala.raleigh.ibm.com>
Date: Fri, 22 Feb 2013 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13022205-5406-0000-0000-0000058E337C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 05:53:10 -0000

Total of 60 messages in the last 7 days.
 
script run at: Fri Feb 22 00:53:02 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  3.33% |    2 | 16.69% |    80360 | roland.bless@kit.edu
  6.67% |    4 |  6.60% |    31766 | rpelletier@isoc.org
  6.67% |    4 |  4.86% |    23392 | touch@isi.edu
  6.67% |    4 |  4.14% |    19919 | paf@frobbit.se
  5.00% |    3 |  4.17% |    20050 | abdussalambaryun@gmail.com
  5.00% |    3 |  4.09% |    19692 | john-ietf@jck.com
  3.33% |    2 |  4.57% |    22005 | hallam@gmail.com
  3.33% |    2 |  3.17% |    15244 | moore@network-heretics.com
  3.33% |    2 |  3.06% |    14749 | sm@resistor.net
  3.33% |    2 |  2.82% |    13596 | warren@kumari.net
  3.33% |    2 |  2.68% |    12916 | brian.e.carpenter@gmail.com
  3.33% |    2 |  2.61% |    12573 | amorris@amsl.com
  3.33% |    2 |  2.44% |    11749 | melinda.shore@gmail.com
  3.33% |    2 |  2.06% |     9928 | randy@psg.com
  1.67% |    1 |  2.79% |    13424 | hsantos@isdg.net
  1.67% |    1 |  2.55% |    12273 | presnick@qti.qualcomm.com
  1.67% |    1 |  1.99% |     9580 | benl@google.com
  1.67% |    1 |  1.93% |     9300 | tterribe@xiph.org
  1.67% |    1 |  1.85% |     8902 | narten@us.ibm.com
  1.67% |    1 |  1.74% |     8375 | marka@isc.org
  1.67% |    1 |  1.71% |     8226 | dave@cridland.net
  1.67% |    1 |  1.50% |     7229 | d3e3e3@gmail.com
  1.67% |    1 |  1.48% |     7125 | mcquilwp@pobox.com
  1.67% |    1 |  1.45% |     6976 | joelja@bogus.com
  1.67% |    1 |  1.44% |     6916 | listsebby@me.com
  1.67% |    1 |  1.42% |     6817 | wesley.george@twcable.com
  1.67% |    1 |  1.37% |     6579 | carlosm3011@gmail.com
  1.67% |    1 |  1.35% |     6504 | dhc@dcrocker.net
  1.67% |    1 |  1.29% |     6226 | paul.hoffman@vpnc.org
  1.67% |    1 |  1.22% |     5872 | mcr+ietf@sandelman.ca
  1.67% |    1 |  1.21% |     5822 | lars@netapp.com
  1.67% |    1 |  1.15% |     5552 | mohta@necom830.hpcl.titech.ac.jp
  1.67% |    1 |  1.14% |     5470 | ole@cisco.com
  1.67% |    1 |  1.14% |     5467 | eburger-l@standardstrack.com
  1.67% |    1 |  1.14% |     5465 | bortzmeyer@nic.fr
  1.67% |    1 |  1.13% |     5441 | smb@cs.columbia.edu
  1.67% |    1 |  1.03% |     4959 | mrex@sap.com
  1.67% |    1 |  1.02% |     4924 | internet-drafts@ietf.org
--------+------+--------+----------+------------------------
100.00% |   60 |100.00% |   481363 | Total


From benl@google.com  Fri Feb 22 03:18:48 2013
Return-Path: <benl@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB51A21F8740 for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 03:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.978
X-Spam-Level: 
X-Spam-Status: No, score=-101.978 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 EV6Czxnh4Tio for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 03:18:48 -0800 (PST)
Received: from mail-ia0-x229.google.com (ia-in-x0229.1e100.net [IPv6:2607:f8b0:4001:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id CC1D621F8721 for <ietf@ietf.org>; Fri, 22 Feb 2013 03:18:42 -0800 (PST)
Received: by mail-ia0-f169.google.com with SMTP id j5so445842iaf.28 for <ietf@ietf.org>; Fri, 22 Feb 2013 03:18:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZwGzg2BH62kO5rVkpbM2lcWy9kHgZGwHszJsALrYc4g=; b=L7E/4p5VPOx58/lpz1QOazigUp4WpYhpYLCBUQFs5d4ycZSv88kU+aSDK5N4kIc3Ty A1iKXlHP52HoSWiAIAJClCdrYHubniel0GUN2lPBX5E7RpHej5dc4TZMt40XyKbsgEaG QPDJypbm8H1whmJMC0/tT3zOAyc/FOOOM11qzCK/SKQgbpJGXSRLP7Qh4j0mQmMDwsZD VnmclVGVhzhIlXFbV7MVcNYF16Vtx8qcZ2qMqFTQyIy99/lT5Jh0Uqfov1jOwd9Rh63q QsjeQF3eJ/u5zwywhgb3CAWxRJJzYxRx/wkgqhnMH742O1FvbAhc0ZNkk/YCBkgrbdol LMvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=ZwGzg2BH62kO5rVkpbM2lcWy9kHgZGwHszJsALrYc4g=; b=T+FqW5lTIJijYURCSUFXefgyfppvAW19CMShx7q2wRzZ2dXgGfqXtMD+K0lOOQxiJd 98Jw7JDkWnsBo2c8fud9Bdc5SNqhNfuD5v0w2MxxiNAKSvuhiGVJYzM4JXTw3aEa9LUa nOjLwhknzir6e1aJUSY/QGLAphqIapqHvE554V6wb7C7HjZ++MWTyu2hQLcFl2/rYDmv wIkJbNVFx2pFvu3A0U3l3baRcRJmSMaBsOvv73LEqgAk0EUwEeYq1a7fXvacg59lihxg oOJWOx2VHIMthkPCREC7dfiN3YlOQoBED7+bC5lXXU5maXLWYYnGv5xHZGCPHt318gMw skrw==
MIME-Version: 1.0
X-Received: by 10.50.212.3 with SMTP id ng3mr713534igc.43.1361531922420; Fri, 22 Feb 2013 03:18:42 -0800 (PST)
Received: by 10.64.140.71 with HTTP; Fri, 22 Feb 2013 03:18:42 -0800 (PST)
In-Reply-To: <CAMm+LwjM6w1jdZj8Z9bmBjUJ0VQMaZdGHMG4EupRtMxuDb=12w@mail.gmail.com>
References: <CABrd9SQMAGtOTcWVaUfxRE9SZS2dZVhUa3WbJVk8or_LxH6i1w@mail.gmail.com> <CAMm+LwiCQXq9ZLMGtVQMsS8MN9HRDtjg2DqTk9B8S6A7Q38J8w@mail.gmail.com> <CABrd9SS7as7S3vz2AEOJQruCF7aJRSVGjaG6awV9YWyuQaadWQ@mail.gmail.com> <CAMm+LwjM6w1jdZj8Z9bmBjUJ0VQMaZdGHMG4EupRtMxuDb=12w@mail.gmail.com>
Date: Fri, 22 Feb 2013 11:18:42 +0000
Message-ID: <CABrd9SR0z+aWUvW0Ok+hsbi+5rYkuQYzSaZxUCi3VcT+_XPzcQ@mail.gmail.com>
Subject: Re: [therightkey] LC comments on draft-laurie-pki-sunlight-05
From: Ben Laurie <benl@google.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlW6+oh422cjqIJz7Im03RVaobaidh8femIQL8MFxeZYvyDxmOyJ+hI1USnUCMcTAUCrvjMRS9DmYbUOQe6qU9/JlOauKv90mNvAKl0bWKQKOwWI8BWQfVQq12V8Fg/LAvQUwL7L4HnhfJNeo52qq8Bato2bV8OAZ19X2AOYjgjIKI36Nfpj8BgYZDr7LN+yNYeMPAE
Cc: Emilia Kasper <ekasper@google.com>, "therightkey@ietf.org" <therightkey@ietf.org>, Adam Langley <agl@google.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, 22 Feb 2013 11:18:48 -0000

On 17 February 2013 00:24, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>
> On Sat, Feb 16, 2013 at 1:55 PM, Ben Laurie <benl@google.com> wrote:
>>
>> On 16 February 2013 10:22, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>> > Sorry for the delay but I have been thinking of CT and in particular the
>> > issues of
>> >
>> > * Latency for the CA waiting for a notary server to respond
>> > * Business models for notary servers
>> >
>> > As a rule open source software works really well as the marginal cost of
>> > production is zero. Open source services tend to sux because even though
>> > the
>> > marginal cost of a service is negligible, large numbers times negligible
>> > adds up to big numbers. Running a DNS server for a university department
>> > costs very little, running it for the whole university starts to cost
>> > real
>> > money and running a registry like .com with 99.9999% reliability ends up
>> > with $100 million hardware costs.
>> >
>> > So the idea that I plug my business into a network of notary servers
>> > being
>> > run by amateurs or as a community service is a non-starter for me. We
>> > have
>> > to align the responsibility for running any server that the CA has a
>> > critical dependency on with a business model.
>>
>> Note that we do not expect CAs to talk to _all_ log servers, only
>> those that are appropriately responsive - and also note that a CA can
>> fire off a dozen log requests in parallel and then just use the first
>> three that come back, which would deal with any temporary log issues.
>>
>> We should probably add this ability to the open source stack at some
>> point.
>>
>> > Looking at the CT proposal, it seems to me that we could fix the
>> > business
>> > model issue and remove a lot of the CA operational issues as follows:
>> >
>> > 1) Each browser provider that is interested in enforcing a CT
>> > requirement
>> > stands up a meta-notary server.
>> >
>> > 2) Each CA runs their own notary server and this is the only resource
>> > that
>> > needs to have a check in at certificate issue.
>>
>> Isn't this part the only part that's actually needed? The
>> meta-notaries seem like redundant extra complication (and also sound
>> like they fulfil essentially the same role as monitors).
>>
>> I assume, btw, that by "notary server" you mean "log server"?
>>
>> Also, if a CA only uses its own log, what happens when it screws up
>> and gets its log struck off the list of trusted logs? This is why we
>> recommend some redundancy in log signatures.
>
>
> That is the reason for checkpointing against meta notaries.
>
> Otherwise a CA might not actually release the logs.

An unreleased log is not compliant - and so would not be accepted by browsers.

From chair@ietf.org  Fri Feb 22 04:35:11 2013
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4215D21F8E53 for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 04:35:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 Gw2+uAe4YPje for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 04:35:10 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id DC49C21F8E4E for <ietf@ietf.org>; Fri, 22 Feb 2013 04:35:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D9FD21244F3 for <ietf@ietf.org>; Fri, 22 Feb 2013 04:35:10 -0800 (PST)
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 1o_a61xh2Hc9 for <ietf@ietf.org>; Fri, 22 Feb 2013 04:35:10 -0800 (PST)
Received: from [10.71.9.255] (unknown [111.223.96.126]) by c8a.amsl.com (Postfix) with ESMTPSA id 63BCC1244E6 for <ietf@ietf.org>; Fri, 22 Feb 2013 04:35:10 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
Subject: IETF chair's blog
Date: Fri, 22 Feb 2013 07:35:07 -0500
To: IETF <ietf@ietf.org>
Message-Id: <1BBAE003-DEA4-462A-998D-863F6FF90A69@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, 22 Feb 2013 12:35:11 -0000

Jari has created a blog as an experiment to see if would be possible to
provide periodic status reports and other thoughts from the chair. Here's
the link:

http://www.ietf.org/blog/2013/02/chairs-blog/


From hsantos@isdg.net  Fri Feb 22 08:01:28 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78D3D21F8EB9 for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 08:01:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.263
X-Spam-Level: 
X-Spam-Status: No, score=-102.263 tagged_above=-999 required=5 tests=[AWL=0.336, 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 IiiOQduSz97Q for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 08:01:27 -0800 (PST)
Received: from ntbbs.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4F59F21F8EA2 for <ietf@ietf.org>; Fri, 22 Feb 2013 08:01:27 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=457; t=1361548883; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=TZiCqQL N6xTSXJsjWMAGHrRE4Rg=; b=HF7NK9wNiSOJM7g+oQJk1Z+wtZ14c7KLJ0QbZgI cH9mTdguz37qZFJcODFIkaIyPkVQoB2ee2ypToGmGN35Spfltprbk1b2m2nMJZCL SYBmhAX3Os4GCWIcypKWBORXaEMTxf7avEq9god2dzV/eQ6qsDzfuAPrcjnavcMC 7L1k=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 22 Feb 2013 11:01:23 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 342633794.4226.3964; Fri, 22 Feb 2013 11:01:22 -0500
Message-ID: <512795E5.4070503@isdg.net>
Date: Fri, 22 Feb 2013 10:59:33 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>
In-Reply-To: <1BBAE003-DEA4-462A-998D-863F6FF90A69@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: Fri, 22 Feb 2013 16:01:28 -0000

+1

I saw a small mission statement in this post, good start.  Perhaps an 
"official" mission statement  for the new incoming chair.  Take it slow. 
Don't need to see a "blog of the day!"

On 2/22/2013 7:35 AM, IETF Chair wrote:
> Jari has created a blog as an experiment to see if would be possible to
> provide periodic status reports and other thoughts from the chair. Here's
> the link:
>
> http://www.ietf.org/blog/2013/02/chairs-blog/
>
>
>



From doug@ewellic.org  Fri Feb 22 08:09:40 2013
Return-Path: <doug@ewellic.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 6066221F8E92 for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 08:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.87
X-Spam-Level: 
X-Spam-Status: No, score=-1.87 tagged_above=-999 required=5 tests=[AWL=0.729,  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 0nQ9nNxNQQYl for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 08:09:39 -0800 (PST)
Received: from p3plwbeout03-02.prod.phx3.secureserver.net (p3plsmtp03-02-2.prod.phx3.secureserver.net [72.167.218.214]) by ietfa.amsl.com (Postfix) with ESMTP id 6E74A21F8B60 for <ietf@ietf.org>; Fri, 22 Feb 2013 08:09:39 -0800 (PST)
Received: from localhost ([72.167.218.245]) by p3plwbeout03-02.prod.phx3.secureserver.net with bizsmtp id 3U9e1l0035JG3DC01U9eeu; Fri, 22 Feb 2013 09:09:38 -0700
X-SID: 3U9e1l0035JG3DC01
Received: (qmail 3604 invoked by uid 99); 22 Feb 2013 16:09:38 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.190
User-Agent: Workspace Webmail 5.6.33
Message-Id: <20130222090937.665a7a7059d7ee80bb4d670165c8327d.ad3940b1cb.wbe@email03.secureserver.net>
From: "Doug Ewell" <doug@ewellic.org>
To: ietf@ietf.org, rg+ietf@qti.qualcomm.com
Subject: Re: draft-gellens-negotiating-human-language-01
Date: Fri, 22 Feb 2013 09:09:37 -0700
Mime-Version: 1.0
Cc: ietf-languages@iana.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 16:09:40 -0000

Draft-gellens-negotiating-human-language-01, "Negotiating Human Language=0A=
Using SDP", says this about the source of values for the SDP 'lang'=0Aattri=
bute:=0A=0A> The "lang" attribute value must be a single [RFC3066] language=
 tag=0A> in US-ASCII [RFC3066].=0A=0AAlthough this wording is quoted from R=
FC 4566, the subsequent section=0Aproposing a new 'humintlang' attribute us=
es the same wording.=0A=0AAny new format or protocol that employs language =
tags should apply BCP=0A47 (RFC 5646), not RFC 3066, which was obsoleted in=
 2006. BCP 47 allows=0Athe use of more than 7300 additional language subtag=
s derived from ISO=0A639-3, as well as script subtags based on ISO 15924 an=
d variant subtags,=0Anone of which are permitted in a generative manner by =
RFC 3066.=0A=0AThe draft says, "The attribute value should be a language ta=
g from the=0AIANA registry [IANA-lang-tags]", referencing=0Awww.iana.org/as=
signments/language-subtag-registry, but RFC 3066 does not=0Ause this regist=
ry; it references the core ISO standards directly, which=0Areduces stabilit=
y, and it uses its own IANA registry (also obsolete)=0Aonly for a few dozen=
 predefined variant tags, many of which are=0Adeprecated in BCP 47. =0A=0AR=
FC 4647, also part of BCP 47, provides guidelines for matching language=0At=
ags, and may benefit the SDP negotiation process described in the=0Adraft.=
=0A=0A--=0ADoug Ewell | Thornton, CO, USA=0Ahttp://ewellic.org | @DougEwell=
 =C2=AD=0A

From internet-drafts@ietf.org  Fri Feb 22 08:18:24 2013
Return-Path: <internet-drafts@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 CDA2621F8496; Fri, 22 Feb 2013 08:18:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.57
X-Spam-Level: 
X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4J+IGg9yitHn; Fri, 22 Feb 2013 08:18:24 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 672DD21F847C; Fri, 22 Feb 2013 08:18:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Internet-Drafts Administrator <internet-drafts@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Internet Draft Final Submission Cut-Off Monday, February 25
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130222161824.23195.40206.idtracker@ietfa.amsl.com>
Date: Fri, 22 Feb 2013 08:18:24 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 16:18:25 -0000

This is a reminder that the Internet Draft Final Submission (version -01
and up) cut-off is Monday, February 25, 2013. =


All Final Version (-01 and up) submissions are due by UTC 24:00 Monday, Feb=
ruary 25.

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/submit/

The Internet-Draft cutoff dates as well as other significant dates for IETF=
 86 can be found at: =

https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86

Thank you for your understanding and cooperation. If you have any  question=
s or concerns, then please send a message to internet-drafts@ietf.org.

From alejandroacostaalamo@gmail.com  Fri Feb 22 11:29:08 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2942421F8613; Fri, 22 Feb 2013 11:29:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HUUb7Q0zL-AV; Fri, 22 Feb 2013 11:29:07 -0800 (PST)
Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8E94621F85CE; Fri, 22 Feb 2013 11:29:07 -0800 (PST)
Received: by mail-ve0-f172.google.com with SMTP id cz11so867293veb.17 for <multiple recipients>; Fri, 22 Feb 2013 11:29:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=srE7w8Xo+fuLoFJ6FG6/Tpzpq/gpe1wSnsVcAmgtfow=; b=zH9k5oQtrgKnqeG6Qs3l1FiXp6aKliW1bht/NPHcFCM1NUxV19vuTRqg3I4voTtU/f sKiFwaKisfdKhKwsYJxP/ozHH4l7DI2aXdDhO6ZMf7u26sBTlCCcPumgZLqcGIU/rhGo DY1C3bnM3YByBLN46Y7iKT6UwE/yz9tP9h3n2FjjxLkq0XLya/8Sr5g9+GJgWn+s2usU ut4wGSNSZAdgCpz28TtKbs+fmXh96NZ5FRc/HiGj8+tWYv8axyqzeX696HS+1NrZUn3b FXpt5qB8lRdQYLOcp1yZbeK76VL+oaVgP3Z02JnNX7LsFHUpmTn3P8eKemPV+KbFYq4Q u09Q==
MIME-Version: 1.0
X-Received: by 10.220.119.200 with SMTP id a8mr4169707vcr.38.1361561346900; Fri, 22 Feb 2013 11:29:06 -0800 (PST)
Received: by 10.220.179.72 with HTTP; Fri, 22 Feb 2013 11:29:06 -0800 (PST)
In-Reply-To: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>
Date: Fri, 22 Feb 2013 14:59:06 -0430
Message-ID: <CAOmxzdwSM=sYvAiX3x53TUG5xPpdbC5erGqjkdPU6dHuJ+Ggog@mail.gmail.com>
Subject: Re: IETF chair's blog
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 19:29:08 -0000

I agree with this initiative.

Alejandro,

On 2/22/13, IETF Chair <chair@ietf.org> wrote:
> Jari has created a blog as an experiment to see if would be possible to
> provide periodic status reports and other thoughts from the chair. Here's
> the link:
>
> http://www.ietf.org/blog/2013/02/chairs-blog/
>
>

From doramaria@gmail.com  Fri Feb 22 11:53:07 2013
Return-Path: <doramaria@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6D221F8AC3; Fri, 22 Feb 2013 11:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, 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 Us3B76jFmDVF; Fri, 22 Feb 2013 11:53:05 -0800 (PST)
Received: from mail-qc0-f176.google.com (mail-qc0-f176.google.com [209.85.216.176]) by ietfa.amsl.com (Postfix) with ESMTP id 1A80821F8B0E; Fri, 22 Feb 2013 11:53:04 -0800 (PST)
Received: by mail-qc0-f176.google.com with SMTP id n41so443437qco.35 for <multiple recipients>; Fri, 22 Feb 2013 11:53:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:references:in-reply-to:mime-version :content-transfer-encoding:content-type:message-id:cc:x-mailer:from :subject:date:to; bh=v5ipAaiGfyXcyt0ijAGNBdm629c6v51aOl9c4HtjQpo=; b=JZwVnjKOXD2tIWmr3+syZCEpo3fSfsSiq6utAWteeQCWfIQ9j4T2319o5/BwI/UEoO pVW34Ligw0c5rZaL7XimttPp4WlXthjZA6N/mwtASGuEj9+oXssKYuBQzjPYZxCpx56B 5zgED7XvYvJ5E7XjrgryIYLRqrSCpcPjehBX5eGKxFiXfuKjNuZ4scn/4Ei1W1g6LWSI SdrtBYXdSJeAadq03DARLMc8sNbxt/6751p5+lhR6kkFoM54jhSftV4ASgyldA13c+xx SLq43a+s0Xh+0Sc5E0wKwNELptV6uIXbCE4is6TZMb9TxeiBmMQDe4gMXRoO+h9RGMQ7 Z9oA==
X-Received: by 10.224.27.136 with SMTP id i8mr1773541qac.63.1361562782779; Fri, 22 Feb 2013 11:53:02 -0800 (PST)
Received: from [10.14.240.50] (mobile-166-147-117-159.mycingular.net. [166.147.117.159]) by mx.google.com with ESMTPS id ec9sm3321468qab.9.2013.02.22.11.53.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 22 Feb 2013 11:53:01 -0800 (PST)
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <CAOmxzdwSM=sYvAiX3x53TUG5xPpdbC5erGqjkdPU6dHuJ+Ggog@mail.gmail.com>
In-Reply-To: <CAOmxzdwSM=sYvAiX3x53TUG5xPpdbC5erGqjkdPU6dHuJ+Ggog@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <C39423A9-07BC-43BD-914B-855DC8F54C37@gmail.com>
X-Mailer: iPhone Mail (10A523)
From: DM Abreu <doramaria@gmail.com>
Subject: Re: IETF chair's blog
Date: Fri, 22 Feb 2013 14:52:58 -0500
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2013 19:53:07 -0000

I love the transparency as well !

Thank you !!

Dora Maria


Sent from my mobile

On Feb 22, 2013, at 2:29 PM, Alejandro Acosta <alejandroacostaalamo@gmail.co=
m> wrote:

> I agree with this initiative.
>=20
> Alejandro,
>=20
> On 2/22/13, IETF Chair <chair@ietf.org> wrote:
>> Jari has created a blog as an experiment to see if would be possible to
>> provide periodic status reports and other thoughts from the chair. Here's=

>> the link:
>>=20
>> http://www.ietf.org/blog/2013/02/chairs-blog/
>>=20
>>=20

From warren@kumari.net  Fri Feb 22 16:46:21 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3D521E808D for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 16:46:21 -0800 (PST)
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 3z8AMTPQrV-T for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 16:46:21 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05E521E8043 for <ietf@ietf.org>; Fri, 22 Feb 2013 16:46:20 -0800 (PST)
Received: from [192.168.1.145] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 63BE41B41870; Fri, 22 Feb 2013 19:46:20 -0500 (EST)
From: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Showing support during IETF LC...
Date: Fri, 22 Feb 2013 19:46:19 -0500
Message-Id: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>
To: "ietf@ietf.org Disgust" <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: Sat, 23 Feb 2013 00:46:21 -0000

Hi there,

So, I have an etiquette question[0].

When a draft comes up for IETF LC, you get the standard:
"The IESG has received a request from the Funny Orange Orangutang WG =
(foo) to
consider the following document: 'Orangutans Considered Harmful" =
<draft-ietf-foo-dangerous-orangutangs-04.txt>

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 1970-01-01."

So, if I have issues with the draft, I know to send them to the list -- =
but what if I simply want to show support?

Normally I figure that if the draft is the product of a WG there is =
already demonstrated support, and so I don't bother cluttering up the =
list with "+1, me too, FTW!, etc." but is this actually the right thing =
to do? What if I really think the draft is important / useful; is it =
appropriate then? Or, if I think that the draft may not pass otherwise? =
Is there any difference if it is not a WG product?=20

What would Miss Manners say?


W
[0]: Asking etiquette questions on -discuss seems only marginally saner =
than asking dining or travel questions on -attendees , but=85 :-P
--
"Let's just say that if complete and utter chaos was lightning, he'd be =
the sort to stand on a hilltop in a thunderstorm wearing wet copper =
armour and shouting 'All gods are bastards'."

    -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of =
Magic)



From john@jlc.net  Fri Feb 22 17:29:37 2013
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F000321F893D for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 17:29:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.124
X-Spam-Level: 
X-Spam-Status: No, score=-106.124 tagged_above=-999 required=5 tests=[AWL=0.475, 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 oqcS6X7uO1gj for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 17:29:37 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8CD21F8934 for <ietf@ietf.org>; Fri, 22 Feb 2013 17:29:37 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 58DC433D3B; Fri, 22 Feb 2013 20:29:37 -0500 (EST)
Date: Fri, 22 Feb 2013 20:29:37 -0500
From: John Leslie <john@jlc.net>
To: Warren Kumari <warren@kumari.net>
Subject: Re: Showing support during IETF LC...
Message-ID: <20130223012937.GI63436@verdi>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>
User-Agent: Mutt/1.4.1i
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 01:29:38 -0000

Warren Kumari <warren@kumari.net> wrote:
> 
> Normally I figure that if the draft is the product of a WG there is
> already demonstrated support, and so I don't bother cluttering up the
> list with "+1, me too, FTW!, etc." but is this actually the right thing
> to do? What if I really think the draft is important / useful; is it
> appropriate then? Or, if I think that the draft may not pass otherwise?
> Is there any difference if it is not a WG product? 
> 
> What would Miss Manners say?

   Miss Manners would almost certainly say that clogging the <ietf> list
with +1 is bad manners. Let me explain a bit.

   The message from the IESG starts a formal process to "judge" "IETF
consensus". The rules of this may seem counter-intuitive, but they are
well-established.

   IETF Consensus is presumed if folks are "sufficiently" notified and
post nothing pointing out unresolved issues. Thus "I support" and
"I oppose" are both meaningless (and Miss Manners would say, "Don't
do it.")

   The process continues "long enough" for folks to react under
"normal" circumstances. Usually during this LastCall, a sponsoring
Area Director (IESG member) issues a "ballot" to the IESG members.
Traditionally, that AD ballots "Yes" at that time.

   Formally, it makes no difference what issues are raised in response
to a LastCall announcement: unless some other AD ballots Discuss, the
IESG will generally approve a WG submission by getting enough "No
Objection" ballots. The process is defined at:
www.ietf.org/iesg/voting-procedures.html

   More often than not, there are no comments either way to the <ietf>
list, and the ADs must read through the document themselves or rely on
a "directorate" review to find issues which might deserve a Discuss.
In theory, an individual raising an issue on the <ietf> list has the
same weight as a directorate review, but in practice each AD takes a
directorate review more seriously unless he/she knows the commentor
well.

   After the IETF-wide LastCall, the issue is placed on an IESG agenda,
whereupon it will generally pass in the absence of a Discuss, whether
or not anybody commented during the LastCall.

   There is a theory, observed mostly in the breach, that discussion
on the <ietf> list will follow and resolve any issues raised by an
individual responding to the LastCall. When this happens, it is a
Good Thing (TM).

   (I think this covers your particular questions; but if you disagree,
feel free to ask for clarification. Just please read the IESG statement
I linked to first.)

--
John Leslie <john@jlc.net>

From sm@resistor.net  Fri Feb 22 23:33:02 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1242321F88DB for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 23:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.578
X-Spam-Level: 
X-Spam-Status: No, score=-102.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D19y2ExjS9Nb for <ietf@ietfa.amsl.com>; Fri, 22 Feb 2013 23:33:00 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BADBB21F8891 for <ietf@ietf.org>; Fri, 22 Feb 2013 23:33:00 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1N7Wrip008800; Fri, 22 Feb 2013 23:32:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361604779; bh=9zEoUkJhfA4oOJ6jVDaBUYXKIBsjiSfFvAybv+ctW9g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=LtyNL8LWUIIEr2S06ccnqJVbZPUsEBlMlfaO+vDN8Igt0TIgq//0+/OaKB9U5+xL2 2c4cpExTCLTVuq/6yIQAR5YkQm5PwY1YDpuo3npuGtu9+bhGjqr6vuFrkWWsiyYb/P 1TAWTM1c4NHUlnZ5oemKy2aMCT1UxRadSWLfQZEc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361604779; i=@resistor.net; bh=9zEoUkJhfA4oOJ6jVDaBUYXKIBsjiSfFvAybv+ctW9g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Z2haHqGYLCuVa1+K58agjEfwrifGNTx+Rcs/1pnwpDzCM44y9UBQvF+TyBFA129mf b15p/3bYcIkMfph35TLpqsdAQMSIJZ6OVtJS/kF9PMtS6Dbu+zHtgVJ+NTcGuVz3uy 5/cNpEB5FrzV0tI4RTRPAHdTjv3OXarPVtkVLE8k=
Message-Id: <6.2.5.6.2.20130222215507.09ef6078@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 22 Feb 2013 23:32:29 -0800
To: John Leslie <john@jlc.net>
From: SM <sm@resistor.net>
Subject: Re: Showing support during IETF LC...
In-Reply-To: <20130223012937.GI63436@verdi>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <20130223012937.GI63436@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 07:33:02 -0000

Hi John,
At 17:29 22-02-2013, John Leslie wrote:
>    IETF Consensus is presumed if folks are "sufficiently" notified and
>post nothing pointing out unresolved issues. Thus "I support" and
>"I oppose" are both meaningless (and Miss Manners would say, "Don't
>do it.")

Yes.

The Last Call boilerplate says "substantive comments".  One unproven 
theory is that it is for a person to clearly express what he or she 
thinks.  It helps if the person can explain why he or she reached 
that conclusion.

>    There is a theory, observed mostly in the breach, that discussion
>on the <ietf> list will follow and resolve any issues raised by an
>individual responding to the LastCall. When this happens, it is a
>Good Thing (TM).

Yes.

"Whatever is true in one form of words is true in every other form of 
words which conveys the same meaning".  The unproven theory is that 
the law of identity is applicable when there is a show of support 
during a Last Call.

Regards,
-sm 


From brian.e.carpenter@gmail.com  Sat Feb 23 00:04:16 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD48621F8F64 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 00:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.781
X-Spam-Level: 
X-Spam-Status: No, score=-99.781 tagged_above=-999 required=5 tests=[AWL=-0.860, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O65DjhRZcU6B for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 00:04:14 -0800 (PST)
Received: from mail-wi0-x229.google.com (wi-in-x0229.1e100.net [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5E49021F8DCB for <ietf@ietf.org>; Sat, 23 Feb 2013 00:04:14 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id l13so2950447wie.4 for <ietf@ietf.org>; Sat, 23 Feb 2013 00:04:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ivutk+S6HrG8CdoaXwaIV33Gw8W5bSNdxm2/WWI0NW8=; b=nd1moVn/Ms/XE6EsfXRHcOQSopEjgI1DwKpgyRpfe6DhyA7sZHHQmgDBzZdn6if2nb oqIkqq8e6VaERonUlxPKx7939zKQimoFbNI6qhdE1uHnMaSnQcXpNKCbInn/eMYO4ONB +Ax0ItahTApW3j0HI5oyceRjnWRu+MiHTFjbu/mEyqqg0kRFoocN1hMb7wgBqFei97WI 2GkTslbikwsxPxwYIJ1QjwgmLqyScIStmCGIpWDWGZbDwX7CySjaMMgnnOOodET59KF3 sAtWtH9IOp00atLWg1tq1VoYBropbSyotfkFqu+ZUsk+FwKXQ6ooLkLP83e719XzvMk0 HawA==
X-Received: by 10.180.108.3 with SMTP id hg3mr1638861wib.33.1361606653577; Sat, 23 Feb 2013 00:04:13 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-216-117.as13285.net. [2.102.216.117]) by mx.google.com with ESMTPS id n2sm2238132wiy.6.2013.02.23.00.04.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 23 Feb 2013 00:04:12 -0800 (PST)
Message-ID: <51287807.8060505@gmail.com>
Date: Sat, 23 Feb 2013 08:04:23 +0000
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: Warren Kumari <warren@kumari.net>
Subject: Re: Showing support during IETF LC...
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>
In-Reply-To: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 08:04:16 -0000

I think it's worth looking at what draft-resnick-on-consensus
says about the nature of rough consensus. It tells us why
reasoned objections are more important than "+1" messages
(or "-1" messages for that matter).

By the same token, it seems that a reasoned message saying
why something is important and valuable would help the IESG,
if the document is on a somewhat obscure topic. However, as
John Leslie pointed out, that isn't strictly necessary, since
silence is equivalent to saying "no objection".

All IMHO, YMMV, of course.

   Brian

On 23/02/2013 00:46, Warren Kumari wrote:
> Hi there,
>=20
> So, I have an etiquette question[0].
>=20
> When a draft comes up for IETF LC, you get the standard:
> "The IESG has received a request from the Funny Orange Orangutang WG (f=
oo) to
> consider the following document: 'Orangutans Considered Harmful" <draft=
-ietf-foo-dangerous-orangutangs-04.txt>
>=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 1970-01-01."
>=20
> So, if I have issues with the draft, I know to send them to the list --=
 but what if I simply want to show support?
>=20
> Normally I figure that if the draft is the product of a WG there is alr=
eady demonstrated support, and so I don't bother cluttering up the list w=
ith "+1, me too, FTW!, etc." but is this actually the right thing to do? =
What if I really think the draft is important / useful; is it appropriate=
 then? Or, if I think that the draft may not pass otherwise? Is there any=
 difference if it is not a WG product?=20
>=20
> What would Miss Manners say?
>=20
>=20
> W
> [0]: Asking etiquette questions on -discuss seems only marginally saner=
 than asking dining or travel questions on -attendees , but=E2=80=A6 :-P
> --
> "Let's just say that if complete and utter chaos was lightning, he'd be=
 the sort to stand on a hilltop in a thunderstorm wearing wet copper armo=
ur and shouting 'All gods are bastards'."
>=20
>     -- Rincewind discussing Twoflower (Terry Pratchett, The Colour of M=
agic)
>=20
>=20
>=20


From rg+ietf@qualcomm.com  Sat Feb 23 00:20:40 2013
Return-Path: <rg+ietf@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 D1E8E21F8F4B for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 00:20:40 -0800 (PST)
X-Quarantine-ID: <LQOaNCnm8zSW>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -99.745
X-Spam-Level: 
X-Spam-Status: No, score=-99.745 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQOaNCnm8zSW for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 00:20:39 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 73B8321F8F25 for <ietf@ietf.org>; Sat, 23 Feb 2013 00:20:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1361607639; x=1393143639; h=from:message-id:in-reply-to:references:date:to:subject: cc:content-transfer-encoding; bh=QGhYzG0j+lWfsNBfr+0+bpqIBGSEjJ/FT+aARR9x8Jg=; b=l45dL5SBd9fANCUHoq58iYdBmS+ISMQvuRxrRJrdseP0hKcO7nm4OjMn hiNSfZQrVsPq3ZKw09ykjTGizzRM/yk4Kp20BZtfHpWMSNlz2rQtzs/Y4 2+9UpiT0bmLK2CvowrfpVqk5AxULjnhBgZDqQ529bxZEd36D4nXpMkv5X A=;
X-IronPort-AV: E=Sophos;i="4.84,721,1355126400"; d="scan'208,217";a="25256631"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 23 Feb 2013 00:20:38 -0800
From: Randall Gellens <randy@qti.qualcomm.com>
X-IronPort-AV: E=Sophos;i="4.84,721,1355126400";  d="scan'208,217";a="437956435"
Received: from warlock.qualcomm.com ([129.46.50.49]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Feb 2013 00:20:38 -0800
Received: from Ironmsg03-R.qualcomm.com (ironmsg03-R.qualcomm.com [172.30.46.17]) by warlock.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id r1N8KcH5008755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 23 Feb 2013 00:20:38 -0800
X-IronPort-AV: E=Sophos;i="4.84,721,1355126400";  d="scan'208,217";a="437956434"
Received: from myvpn-l-dyp000796dys.ras.qualcomm.com (HELO [10.177.189.109]) ([10.64.136.16]) by Ironmsg03-R.qualcomm.com with ESMTP; 23 Feb 2013 00:20:35 -0800
Mime-Version: 1.0
Message-Id: <p0624060bcd4e2914868a@[10.177.189.109]>
In-Reply-To: <20130222090937.665a7a7059d7ee80bb4d670165c8327d.ad3940b1cb.wbe@email0 3.secureserver.net>
References: <20130222090937.665a7a7059d7ee80bb4d670165c8327d.ad3940b1cb.wbe@email0 3.secureserver.net>
X-Mailer: Eudora for Mac OS X
Date: Sat, 23 Feb 2013 00:18:22 -0800
To: Doug Ewell <doug@ewellic.org>, <ietf@ietf.org>, <rg+ietf@qualcomm.com>
Subject: Re: draft-gellens-negotiating-human-language-01
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Cc: ietf-languages@iana.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Feb 2013 08:20:41 -0000

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type=3D"text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>Re:
draft-gellens-negotiating-human-language-01</title></head><body>
<div>Hi Doug,</div>
<div><br></div>
<div>Thanks very much.&nbsp; So, if I understand, your suggestions
would be:</div>
<div><br></div>
<div>(1) Change the text for the possible new 'humintlang' attribute
from:</div>
<div><br></div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;humintlang&quot;
attribute value must be a single RFC 3066<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC3066] language tag in US-ASCII
[RFC3066].&nbsp; It is not dependent<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on the charset attribute.</div>
<div><br></div>
<div>To:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;humintlang&quot; attribute
value must be a single RFC 5646<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC5646] language tag from the IANA
registry [IANA-lang-<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tags].&nbsp; It is not dependent on the
charset attribute.</div>
<div><br></div>
<div>(2) Add RFC 5646 to the Normative References</div>
<div><br></div>
<div>Since the IANA registry referenced now was actually created by
RFC 5646 not RFC 3066, this is both better technically (for the
reasons you mention) and more correct.</div>
<div><br></div>
<div>Let me know if I've understood, and if so, I may be able to get
an update in before the cut-off.</div>
<div><br></div>
<div><br></div>
<div>At 9:09 AM -0700 2/22/13, Doug Ewell wrote:</div>
<div><br></div>
<blockquote type=3D"cite"
cite>Draft-gellens-negotiating-human-language-01, &quot;Negotiating
Human Language Using SDP&quot;, says this about the source of values
for the SDP 'lang' attribute: &gt; The &quot;lang&quot; attribute
value must be a single [RFC3066] language tag &gt; in US-ASCII
[RFC3066]. Although this wording is quoted from RFC 4566, the
subsequent section proposing a new 'humintlang' attribute uses the
same wording. Any new format or protocol that employs language tags
should apply BCP 47 (RFC 5646), not RFC 3066, which was obsoleted in
2006. BCP 47 allows the use of more than 7300 additional language
subtags derived from ISO 639-3, as well as script subtags based on ISO
15924 and variant subtags, none of which are permitted in a generative
manner by RFC 3066. The draft says, &quot;The attribute value should
be a language tag from the IANA registry [IANA-lang-tags]&quot;,
referencing www.iana.org/assignments/language-subtag-registry, but RFC
3066 does not use this registry; it references the core ISO standards
directly, which reduces stability, and it uses its own IANA registry
(also obsolete) only for a few dozen predefined variant tags, many of
which are deprecated in BCP 47. RFC 4647, also part of BCP 47,
provides guidelines for matching language tags, and may benefit the
SDP negotiation process described in the draft. -- Doug Ewell |
Thornton, CO, USA http://ewellic.org | @DougEwell =B0=A9</blockquote>
<div><br></div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div>Randall Gellens<br>
Opinions are personal;&nbsp;&nbsp;&nbsp; facts are
suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<br>
-------------- Randomly selected tag: ---------------<br>
Two things are infinite: the universe and human stupidity;<br>
and I'm not even sure about the universe.<br>
 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--Albert Einstein<br>
</div></body>
</html>

From abdussalambaryun@gmail.com  Sat Feb 23 03:58:37 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B68621F8F71 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 03:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[AWL=0.048,  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 7lCysBWU6TsL for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 03:58:37 -0800 (PST)
Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by ietfa.amsl.com (Postfix) with ESMTP id E132C21F8EB2 for <ietf@ietf.org>; Sat, 23 Feb 2013 03:58:36 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id fa10so943531pad.27 for <ietf@ietf.org>; Sat, 23 Feb 2013 03:58:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to:cc :content-type; bh=gDsfGEiI4cvKLYYRhW78Rx9rfyK9ubWKnsnkIBsBSEw=; b=tiZA5c7HfmIAOJAt7KZTN7RDPzkrVakF4/sR1XqgqUtvEnyVrXCcqzavHQ6KtPu9/l v9Qmbk78HdU+ZBl46Rbz05CYijxpXyVCpSMNBm3aLUggDPaSktxZ48V2mnbreGuEoAyb Fc5SVIxZ3CADX3u6kGKjbKMSuZ9WRlgKKewfhp/CK4m9jhx8Oi4XAGG36/wzzqcZTE6u aroQEl3GmxD8KHjOwyS4JDQVvdoc+vVyWjFcbHE3IBNNW6pXU8g+NrA4/jJ2hhgGgiI4 vLlSC4FCkwQlF3KNTsHXHgSGxxW7hE4mSZl4W3o/qk18nrS/3oH6dhJLT9gzoCPWwDbC Gj3A==
MIME-Version: 1.0
X-Received: by 10.66.234.132 with SMTP id ue4mr8989736pac.163.1361620716655; Sat, 23 Feb 2013 03:58:36 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Sat, 23 Feb 2013 03:58:36 -0800 (PST)
Date: Sat, 23 Feb 2013 12:58:36 +0100
Message-ID: <CADnDZ8_cXYSjcY=-rQRikVjXHQrrUwaVQuC8UHaWuCL1VPXntQ@mail.gmail.com>
Subject: Re: Showing support during IETF LC...
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: warren@kumari.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 11:58:37 -0000

Hi Warren,

I think IESG do ask for comments, and think that even +1 is a comment,
I prefer if the draft was a WG darft only participants out of the WG
can support. However, you SHOULD mention why you support that, is it
related to a technology, RFC or a WG works, SHOWing interest is
important to see how can the submitted darft be depended on in future.
Usually we don't want just to publish a draft that has few
interest/reason.

Overall, it is the IESG or any sender to your account that SHOULD
specify what was the request about, so as your example, there is no
harm in support,

Thanks for your input,

AB

From abdussalambaryun@gmail.com  Sat Feb 23 04:07:40 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC61121F8E7B for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 04:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.552
X-Spam-Level: 
X-Spam-Status: No, score=-3.552 tagged_above=-999 required=5 tests=[AWL=0.047,  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 Cc-TSg530kql for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 04:07:38 -0800 (PST)
Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) by ietfa.amsl.com (Postfix) with ESMTP id BD8C321F8E7A for <ietf@ietf.org>; Sat, 23 Feb 2013 04:07:35 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id kp14so944687pab.5 for <ietf@ietf.org>; Sat, 23 Feb 2013 04:07:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ZUbHm83k4BD0lio5PIumx3wv4sHByb2R/ZszkTKASxE=; b=LtkCxlFqbWDVr5qIuxNuO+i2svruPD9KuMBZ0Hz9Q8fK8EBTSrdEwuL/KMjxxcWL3Q fN6YR8BwppRhR1K9Q5kkZecIEgqhPZU1JRhp3PWA8YJxkIkDlak/aLN2GKtatiVjEvor sqbtzyFnTsAHCMMF1p2HsGR3KgSZ+3wMQr5Yb0+QJfPnORK6rfTwckgwUjdXB3Lcj77d Fyo0fUb1wvU3+0oEutgabXMu8i34WhQUXuoBup2oK/wmvvibncqJ9CfRMfZWlo2nbQ1P Z2an3pGuQCfThY7x7mbUNNsSOSXaqBtwHL0ICEjFF94w5DlE6LkOjB7ZZHTS2rhf+C4q PXhg==
MIME-Version: 1.0
X-Received: by 10.68.204.68 with SMTP id kw4mr8103850pbc.113.1361621255586; Sat, 23 Feb 2013 04:07:35 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Sat, 23 Feb 2013 04:07:35 -0800 (PST)
In-Reply-To: <CADnDZ8_cXYSjcY=-rQRikVjXHQrrUwaVQuC8UHaWuCL1VPXntQ@mail.gmail.com>
References: <CADnDZ8_cXYSjcY=-rQRikVjXHQrrUwaVQuC8UHaWuCL1VPXntQ@mail.gmail.com>
Date: Sat, 23 Feb 2013 13:07:35 +0100
Message-ID: <CADnDZ8_2G9W-=hw9ZwgysXzXoPqP7PGPY=ZqGKPCrDznuGtSNQ@mail.gmail.com>
Subject: Re: Showing support during IETF LC...
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: warren@kumari.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 12:07:40 -0000

In addition to what said, I think that the most important think is
that the submitted draft be examined by the community, or read by the
community, this is what IESG needs to know the feeling in the
community after being read. I hope all drafts be read at least by 3 of
the community (not sure of statistics, known only by the IESG),
because we don't want most of our RFCs only commented/read by the IETS
:-)

AB

On 2/23/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> Hi Warren,
>
> I think IESG do ask for comments, and think that even +1 is a comment,
> I prefer if the draft was a WG darft only participants out of the WG
> can support. However, you SHOULD mention why you support that, is it
> related to a technology, RFC or a WG works, SHOWing interest is
> important to see how can the submitted darft be depended on in future.
> Usually we don't want just to publish a draft that has few
> interest/reason.
>
> Overall, it is the IESG or any sender to your account that SHOULD
> specify what was the request about, so as your example, there is no
> harm in support,
>
> Thanks for your input,
>
> AB
>

From john-ietf@jck.com  Sat Feb 23 06:42:05 2013
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5831621F867D for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 06:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.647
X-Spam-Level: 
X-Spam-Status: No, score=-102.647 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AaooBS+7InzH for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 06:42:04 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 49FA521F8F52 for <ietf@ietf.org>; Sat, 23 Feb 2013 06:41:55 -0800 (PST)
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 1U9GIU-000LqF-90; Sat, 23 Feb 2013 09:41:54 -0500
Date: Sat, 23 Feb 2013 09:41:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Warren Kumari <warren@kumari.net>
Subject: Re: Showing support during IETF LC...
Message-ID: <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com>
In-Reply-To: <51287807.8060505@gmail.com>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@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 discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Feb 2013 14:42:05 -0000

--On Saturday, February 23, 2013 08:04 +0000 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>...
> By the same token, it seems that a reasoned message saying
> why something is important and valuable would help the IESG,
> if the document is on a somewhat obscure topic. However, as
> John Leslie pointed out, that isn't strictly necessary, since
> silence is equivalent to saying "no objection".

Two small additions.  

First, "no objection" and silence by IESG members are roughly
equivalent, but approval of a document with complete community
silence (either outside the relevant WG or on an individual
submission) makes some ADs nervous (and, IMO, should) and, in
theory at least, would be subject to appeal on the grounds that
there is no actual evidence of _community_ consensus.  IMO at
least, if a question is asked about a document and there are
nothing but blank stares, that is not evidence of consensus.  As
draft-resnick-on-consensus effectively points out, that depends
a bit on what question is asked and where.  However, I note that
RFC 2026 contains language like (Section 1.2) "establishing
widespread community consensus", (Section 6.5) "genuine
consensus achieved" and that doesn't imply to me that approval
by speechless zombies is sufficient.

Second, I strongly agree about warnings again clutter on the
IETF list and that "+1" is pretty useless to all concerned.
What seems to be missing from the thread is that there are other
alternatives.  In particular, I think it may be reasonable to
send a note to the IESG (not the IETF list) or even to just the
AD who is responsible for a document (who can always forward to
the IESG if he or she thinks that necessary), the says "I've
studied this and don't see any problems", "I've read this and,
while I'm not an expert in the field, I don't see a problem",
"after reviewing this, I don't see any problems and it appears
to be useful" or something along those lines.  None of those
help much with "why should this be approved", but they do
provide evidence that people have actually reviewed the document
rather than letting it go on the grounds that someone else will
do so.

> All IMHO, YMMV, of course.

For me as well.
    john





From doug@ewellic.org  Sat Feb 23 07:21:05 2013
Return-Path: <doug@ewellic.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 92E2021F8ECB for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 07:21:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jyr6RVtNio4z for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 07:21:04 -0800 (PST)
Received: from p3plsmtpa11-07.prod.phx3.secureserver.net (p3plsmtpa11-07.prod.phx3.secureserver.net [68.178.252.108]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8CF21F8EC8 for <ietf@ietf.org>; Sat, 23 Feb 2013 07:21:03 -0800 (PST)
Received: from [172.20.17.183] ([65.114.197.45]) by p3plsmtpa11-07.prod.phx3.secureserver.net with  id 3rM11l00F0zF9c101rM2zm; Sat, 23 Feb 2013 08:21:03 -0700
MIME-Version: 1.0
To: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>,  "rg+ietf@qualcomm.com" <rg+ietf@qualcomm.com>
From: Doug Ewell <doug@ewellic.org>
Subject: RE: draft-gellens-negotiating-human-language-01
Date: Sat, 23 Feb 2013 08:20:37 -0700
Content-Type: multipart/alternative; boundary="_638819FF-FDD3-47D9-88E1-096B50433DED_"
Message-Id: <20130223152104.3C8CF21F8EC8@ietfa.amsl.com>
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Feb 2013 15:21:05 -0000

--_638819FF-FDD3-47D9-88E1-096B50433DED_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi Randall,

You might want to reference BCP 47 instead of RFC 5646, but this is up to y=
ou.

Technically the Registry was created by RFC 4646, the predecessor to 5646, =
and it does not actually include tags, but rather subtags which are used to=
 assemble tags. You can have a tag of just "en", which is just a language s=
ubtag, but you can also have "zh-Hans-SG" for Chinese, simplified character=
s, as used in Singapore. Those are three subtags that you piece together to=
 make a tag. The tag itself is not in the Registry, but the parts are.

I would actually suggest leaving off the reference to the Registry and just=
 say the tag must conform to 5646 (or BCP 47). That will imply the use of t=
he Registry.

Thanks,

--
Doug Ewell | Thornton, CO, USA
http://ewellic.org | @DougEwell

-----Original Message-----
From: "Randall Gellens" <randy@qti.qualcomm.com>
Sent: =E2=80=8E2/=E2=80=8E23/=E2=80=8E2013 1:18
To: "Doug Ewell" <doug@ewellic.org>; "ietf@ietf.org" <ietf@ietf.org>; "rg+i=
etf@qualcomm.com" <rg+ietf@qualcomm.com>
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
Subject: Re: draft-gellens-negotiating-human-language-01

Hi Doug,


Thanks very much.  So, if I understand, your suggestions would be:


(1) Change the text for the possible new 'humintlang' attribute from:


      The "humintlang" attribute value must be a single RFC 3066
      [RFC3066] language tag in US-ASCII [RFC3066].  It is not dependent
      on the charset attribute.


To:

      The "humintlang" attribute value must be a single RFC 5646
      [RFC5646] language tag from the IANA registry [IANA-lang-
      tags].  It is not dependent on the charset attribute.


(2) Add RFC 5646 to the Normative References


Since the IANA registry referenced now was actually created by RFC 5646 not=
 RFC 3066, this is both better technically (for the reasons you mention) an=
d more correct.


Let me know if I've understood, and if so, I may be able to get an update i=
n before the cut-off.




At 9:09 AM -0700 2/22/13, Doug Ewell wrote:


Draft-gellens-negotiating-human-language-01, "Negotiating Human Language Us=
ing SDP", says this about the source of values for the SDP 'lang' attribute=
: > The "lang" attribute value must be a single [RFC3066] language tag > in=
 US-ASCII [RFC3066]. Although this wording is quoted from RFC 4566, the sub=
sequent section proposing a new 'humintlang' attribute uses the same wordin=
g. Any new format or protocol that employs language tags should apply BCP 4=
7 (RFC 5646), not RFC 3066, which was obsoleted in 2006. BCP 47 allows the =
use of more than 7300 additional language subtags derived from ISO 639-3, a=
s well as script subtags based on ISO 15924 and variant subtags, none of wh=
ich are permitted in a generative manner by RFC 3066. The draft says, "The =
attribute value should be a language tag from the IANA registry [IANA-lang-=
tags]", referencing www.iana.org/assignments/language-subtag-registry, but =
RFC 3066 does not use this registry; it references the core ISO standards d=
irectly, which reduces stability, and it uses its own IANA registry (also o=
bsolete) only for a few dozen predefined variant tags, many of which are de=
precated in BCP 47. RFC 4647, also part of BCP 47, provides guidelines for =
matching language tags, and may benefit the SDP negotiation process describ=
ed in the draft. -- Doug Ewell | Thornton, CO, USA http://ewellic.org | @Do=
ugEwell =C2=B0=C2=A9




--=20
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Two things are infinite: the universe and human stupidity;
and I'm not even sure about the universe.
                                       --Albert Einstein=

--_638819FF-FDD3-47D9-88E1-096B50433DED_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<HTML><HEAD><TITLE>Re: draft-gellens-negotiating-human-language-01</TITLE>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE type=3Dtext/css><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></STYLE>
</HEAD>
<BODY>
<DIV>
<DIV style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">Hi Randall,=
<BR><BR>You might want to reference BCP 47 instead of RFC 5646, but this is=
 up to you.<BR><BR>Technically the Registry was created by RFC 4646, the pr=
edecessor to 5646, and it does not actually include tags, but rather subtag=
s which are used to assemble tags. You can have a tag of just "en", which i=
s just a language subtag, but you can also have "zh-Hans-SG" for Chinese, s=
implified characters, as used in Singapore. Those are three subtags that yo=
u piece together to make a tag. The tag itself is not in the Registry, but =
the parts are.<BR><BR>I would actually suggest leaving off the reference to=
 the Registry and just say the tag must conform to 5646 (or BCP 47). That w=
ill imply the use of the Registry.<BR><BR>Thanks,<BR><BR>--<BR>Doug Ewell |=
 Thornton, CO, USA<BR>http://ewellic.org | @DougEwell</DIV></DIV>
<DIV dir=3Dltr>
<HR>
<SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGH=
T: bold">From: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,=
sans-serif"><A href=3D"mailto:randy@qti.qualcomm.com">Randall Gellens</A></=
SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; F=
ONT-WEIGHT: bold">Sent: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY:=
 Calibri,sans-serif">=E2=80=8E2/=E2=80=8E23/=E2=80=8E2013 1:18</SPAN><BR><S=
PAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT:=
 bold">To: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans=
-serif"><A href=3D"mailto:doug@ewellic.org">Doug Ewell</A>; <A href=3D"mail=
to:ietf@ietf.org">ietf@ietf.org</A>; <A href=3D"mailto:rg+ietf@qualcomm.com=
">rg+ietf@qualcomm.com</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-F=
AMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Cc: </SPAN><SPAN style=3D"FON=
T-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif"><A href=3D"mailto:ietf-langu=
ages@iana.org">ietf-languages@iana.org</A></SPAN><BR><SPAN style=3D"FONT-SI=
ZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Subject: </SP=
AN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">Re: dra=
ft-gellens-negotiating-human-language-01</SPAN><BR><BR></DIV>
<DIV>Hi Doug,</DIV>
<DIV><BR></DIV>
<DIV>Thanks very much.&nbsp; So, if I understand, your suggestions would be=
:</DIV>
<DIV><BR></DIV>
<DIV>(1) Change the text for the possible new 'humintlang' attribute from:<=
/DIV>
<DIV><BR></DIV>
<DIV>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The "humintlang" attribute value must b=
e a single RFC 3066<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC3066] language ta=
g in US-ASCII [RFC3066].&nbsp; It is not dependent<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; on the charset attribute.</DIV>
<DIV><BR></DIV>
<DIV>To:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The "humintlang" attribute v=
alue must be a single RFC 5646<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC5646] =
language tag from the IANA registry [IANA-lang-<BR>&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; tags].&nbsp; It is not dependent on the charset attribute.</DIV>
<DIV><BR></DIV>
<DIV>(2) Add RFC 5646 to the Normative References</DIV>
<DIV><BR></DIV>
<DIV>Since the IANA registry referenced now was actually created by RFC 564=
6 not RFC 3066, this is both better technically (for the reasons you mentio=
n) and more correct.</DIV>
<DIV><BR></DIV>
<DIV>Let me know if I've understood, and if so, I may be able to get an upd=
ate in before the cut-off.</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<DIV>At 9:09 AM -0700 2/22/13, Doug Ewell wrote:</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type=3D"cite">Draft-gellens-negotiating-human-language-01, "Neg=
otiating Human Language Using SDP", says this about the source of values fo=
r the SDP 'lang' attribute: &gt; The "lang" attribute value must be a singl=
e [RFC3066] language tag &gt; in US-ASCII [RFC3066]. Although this wording =
is quoted from RFC 4566, the subsequent section proposing a new 'humintlang=
' attribute uses the same wording. Any new format or protocol that employs =
language tags should apply BCP 47 (RFC 5646), not RFC 3066, which was obsol=
eted in 2006. BCP 47 allows the use of more than 7300 additional language s=
ubtags derived from ISO 639-3, as well as script subtags based on ISO 15924=
 and variant subtags, none of which are permitted in a generative manner by=
 RFC 3066. The draft says, "The attribute value should be a language tag fr=
om the IANA registry [IANA-lang-tags]", referencing www.iana.org/assignment=
s/language-subtag-registry, but RFC 3066 does not use this registry; it ref=
erences the core ISO standards directly, which reduces stability, and it us=
es its own IANA registry (also obsolete) only for a few dozen predefined va=
riant tags, many of which are deprecated in BCP 47. RFC 4647, also part of =
BCP 47, provides guidelines for matching language tags, and may benefit the=
 SDP negotiation process described in the draft. -- Doug Ewell | Thornton, =
CO, USA http://ewellic.org | @DougEwell =C2=B0=C2=A9</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><BR></DIV><X-SIGSEP><PRE>--=20
</PRE></X-SIGSEP>
<DIV>Randall Gellens<BR>Opinions are personal;&nbsp;&nbsp;&nbsp; facts are =
suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<BR>-------------- Random=
ly selected tag: ---------------<BR>Two things are infinite: the universe a=
nd human stupidity;<BR>and I'm not even sure about the universe.<BR>&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;--Albert Einstein<BR></DIV></BODY></HTML>=

--_638819FF-FDD3-47D9-88E1-096B50433DED_--


From acooper@cdt.org  Sat Feb 23 09:10:44 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C3F21F8FB6 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 09:10:44 -0800 (PST)
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 sX7FdJpuKDgw for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 09:10:43 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 890D321F8EB2 for <ietf@ietf.org>; Sat, 23 Feb 2013 09:10:43 -0800 (PST)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Sat, 23 Feb 2013 12:10:41 -0500
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <6.2.5.6.2.20130130143748.09bc0140@resistor.net>
Date: Sat, 23 Feb 2013 12:10:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
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: Sat, 23 Feb 2013 17:10:44 -0000

Hi SM,

Thanks for your comments. Some responses are inline.

On Jan 30, 2013, at 7:29 PM, SM wrote:

> At 14:30 16-01-2013, IAB Chair wrote:
>> This is an announcement of an IETF-wide Call for Comment on 'Privacy =
Considerations for Internet Protocols'.
>>=20
>> The document is being considered for publication as an Informational =
RFC within the IAB stream, and is available for inspection here:
>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>=20
> In Section 1:
>=20
>  'With regard to data, often it is a concept applied to
>   "personal data," information relating to an identified or
>   identifiable individual.'
>=20
> I suggest rewriting the above sentence.

The authors have re-written that sentence several times and in different =
ways already. Do you have a specific suggestion about how to improve it?

>=20
>  "Many sets of privacy principles and privacy design frameworks have =
been
>   developed in different forums over the years."
>=20
> There is also some work in the APEC region (see =
http://publications.apec.org/publication-detail.php?pub_id=3D390 =
(payware)).

As far as I know the APEC framework is one of many frameworks (none of =
which we cite since there are so many) based on the OECD-style FIPs. Is =
that incorrect?

>=20
> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC =
6772.

Fixed.

>=20
> I read some of the previous versions of this draft.  The Abstract =
Section describes the document as providing guidance for developing =
privacy considerations for inclusion in protocol specifications.  I =
found the draft difficult to digest.  I suggest simplifying the draft to =
make the guidance accessible to the target audience.

I'm not quite sure what you are recommending here, but we have had =
conversations in the IAB privacy program about moving the guidance part =
up, or otherwise trying to make the focus on the guidance piece more =
prominent. The difficulty is that there is a broad range in the extent =
to which potential readers are familiar with privacy concepts, so =
jumping straight into the guidance would not be appropriate for some =
portion of the audience. If you have concrete suggestions for how to =
simplify, those would be helpful.

>=20
> One of the issues nowadays is what to do about intermediaries.  If I =
am not mistaken RFC 3238 was one of the first documents to tackle that =
question from a privacy perspective.  There have been a few proposals to =
introduce intermediaries as part of the architecture (I am using the =
word is used loosely).  It is easy to argue for intermediaries based on =
use cases.  There was a case recently where the users only became aware =
that they have signed up for using an intermediary through the EULA.
>=20
> The draft introduces the concept of secondary use (Section 4.2.3).  =
Strictly speaking, it is a disclosure (Section 4.2.4).

Not all secondary uses involve disclosure (such as the example given in =
4.2.3). I have added a sentence to clarify this, however:

"Secondary use encompasses any use of data, including disclosure."

>=20
> The draft mentions consent in several places.  The authors are likely =
aware that consent was a hot topic for DNT.  It's easier to start with =
something that is easy for the average person to understand and build =
from there.  Section 7.2 could more about consent instead of user =
participation or control.

We tried to think of a case where a consent mechanism was actually =
developed in the IETF, but as a general matter consent mechanisms tend =
to be out of scope, which is why we focus more on user controls (which =
still show up rarely but do show up).

Thanks,
Alissa

>=20
> Regards,
> -sm=20
>=20



From hsantos@isdg.net  Sat Feb 23 11:53:40 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFA5E21F8E8C for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 11:53:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.868
X-Spam-Level: 
X-Spam-Status: No, score=-101.868 tagged_above=-999 required=5 tests=[AWL=-0.133, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJZwXBK43242 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 11:53:36 -0800 (PST)
Received: from ntbbs.santronics.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id A9B0F21F891C for <ietf@ietf.org>; Sat, 23 Feb 2013 11:53:35 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4756; t=1361649210; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=4q3hUWZ 5x3pBAZ/FSqjBK1KS4WQ=; b=JB1L2ErwRXwZszXauMxJHdAcLeAtAN9lf1QtIEQ PuIA6rYZ/cPNm20fXkmFwGizqXVoFpaYXM/o5nHuyO22W6DkyXumZNJUgfPQfPdP 0Uaii1IX7khUY6RLWLB//D4/anCrXujsK28cXFe/wamLAc1D85j8xCtkZz5GQ8bT d9go=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 23 Feb 2013 14:53:30 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 442958770.3.1736; Sat, 23 Feb 2013 14:53:28 -0500
Message-ID: <51291DC9.7050404@isdg.net>
Date: Sat, 23 Feb 2013 14:51:37 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org>
In-Reply-To: <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, 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: Sat, 23 Feb 2013 19:53:41 -0000

Hi, with a quick review, and many comments and points, I think the one 
single part that I would have some questions about is in the intro:

    The guidance provided in
    this document is generic and can be used to inform the design of any
    protocol to be used anywhere in the world, without reference to
    specific legal frameworks.


Is that a goal?  Do you feel you have reached providing such "Global 
Common" guidelines in the area of privacy?  How does it compare to US 
ECPA provisions for "User Expectations" which has served as a global 
model for other jurisdictions?

The reason I ask is because I have been very sensitive to ethical design 
and product liability issues in our product lines since 1986 following 
the guidelines set forth by the US ECPA for:

- Thou shall not block/reject things without user knowledge,
- Thou shall not tamper/edit things especially when passing things (relays),
- Thou shall kept private things private.

This was considered "Global" once upon a time.  Now its arguable.

--
HLS

On 2/23/2013 12:10 PM, Alissa Cooper wrote:
> Hi SM,
>
> Thanks for your comments. Some responses are inline.
>
> On Jan 30, 2013, at 7:29 PM, SM wrote:
>
>> At 14:30 16-01-2013, IAB Chair wrote:
>>> This is an announcement of an IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'.
>>>
>>> The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:
>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>> In Section 1:
>>
>>   'With regard to data, often it is a concept applied to
>>    "personal data," information relating to an identified or
>>    identifiable individual.'
>>
>> I suggest rewriting the above sentence.
> The authors have re-written that sentence several times and in different ways already. Do you have a specific suggestion about how to improve it?
>
>>   "Many sets of privacy principles and privacy design frameworks have been
>>    developed in different forums over the years."
>>
>> There is also some work in the APEC region (see http://publications.apec.org/publication-detail.php?pub_id=390 (payware)).
> As far as I know the APEC framework is one of many frameworks (none of which we cite since there are so many) based on the OECD-style FIPs. Is that incorrect?
>
>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC 6772.
> Fixed.
>
>> I read some of the previous versions of this draft.  The Abstract Section describes the document as providing guidance for developing privacy considerations for inclusion in protocol specifications.  I found the draft difficult to digest.  I suggest simplifying the draft to make the guidance accessible to the target audience.
> I'm not quite sure what you are recommending here, but we have had conversations in the IAB privacy program about moving the guidance part up, or otherwise trying to make the focus on the guidance piece more prominent. The difficulty is that there is a broad range in the extent to which potential readers are familiar with privacy concepts, so jumping straight into the guidance would not be appropriate for some portion of the audience. If you have concrete suggestions for how to simplify, those would be helpful.
>
>> One of the issues nowadays is what to do about intermediaries.  If I am not mistaken RFC 3238 was one of the first documents to tackle that question from a privacy perspective.  There have been a few proposals to introduce intermediaries as part of the architecture (I am using the word is used loosely).  It is easy to argue for intermediaries based on use cases.  There was a case recently where the users only became aware that they have signed up for using an intermediary through the EULA.
>>
>> The draft introduces the concept of secondary use (Section 4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).
> Not all secondary uses involve disclosure (such as the example given in 4.2.3). I have added a sentence to clarify this, however:
>
> "Secondary use encompasses any use of data, including disclosure."
>
>> The draft mentions consent in several places.  The authors are likely aware that consent was a hot topic for DNT.  It's easier to start with something that is easy for the average person to understand and build from there.  Section 7.2 could more about consent instead of user participation or control.
> We tried to think of a case where a consent mechanism was actually developed in the IETF, but as a general matter consent mechanisms tend to be out of scope, which is why we focus more on user controls (which still show up rarely but do show up).
>
> Thanks,
> Alissa
>
>> Regards,
>> -sm
>>
>
>
>



From sm@resistor.net  Sat Feb 23 14:05:17 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3C721F89B9; Sat, 23 Feb 2013 14:05:17 -0800 (PST)
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 GM4AOIeNzprz; Sat, 23 Feb 2013 14:05:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9A1C21F870A; Sat, 23 Feb 2013 14:05:15 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1NM4mLv001602; Sat, 23 Feb 2013 14:04:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361657093; bh=DwnqdemOyQyuz0B9Szc86rdqy8dsWSF4MZBYpcb/4bY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lkHAnHd3iQ4s1vprN464Eqgth2PKE8m2WOBnvMU+7OfsQwQhpkLzhHhiUjwjSsbX8 c7JlhGA1REA4pCjRp7jEpJ97Al/ktAT2UqaBRJMcnNRkzOnmKVHHoNrtTvSpH1Wxgv I5gAX8nNCjwkgjxFlgekxx2xNFZj+XlEiSzG0Apo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361657093; i=@resistor.net; bh=DwnqdemOyQyuz0B9Szc86rdqy8dsWSF4MZBYpcb/4bY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qlzBHXayMvWUceXYErXdb68JE6c954JXYm40MjJ4KeZnr67BZ65jQIRirdbqNd/tr IBCsxdfK1+2PkqAQO+Gg+uw20nQeyr+PW85nVR8l2KBN7k1dWJMp5HgUG3qRk89ZdZ oXqtnyrIh0KYpxZ2FMbefDTzC6lh8ZQva60QHylE=
Message-Id: <6.2.5.6.2.20130223124833.0ac15800@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 23 Feb 2013 14:04:30 -0800
To: Alissa Cooper <acooper@cdt.org>
From: SM <sm@resistor.net>
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
In-Reply-To: <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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: Sat, 23 Feb 2013 22:05:17 -0000

Hi Alissa,
At 09:10 23-02-2013, Alissa Cooper wrote:
>The authors have re-written that sentence several times and in 
>different ways already. Do you have a specific suggestion about how 
>to improve it?

Short answer, if nobody else said anything about the sentence I 
suggest leaving it as it is.  I'll send suggested text if I can think 
of something.

>As far as I know the APEC framework is one of many frameworks (none 
>of which we cite since there are so many) based on the OECD-style 
>FIPs. Is that incorrect?

No, it isn't.

>I'm not quite sure what you are recommending here, but we have had 
>conversations in the IAB privacy program about moving the guidance 
>part up, or otherwise trying to make the focus on the guidance piece 
>more prominent. The difficulty is that there is a broad range in the 
>extent to which potential readers are familiar with privacy 
>concepts, so jumping straight into the guidance would not be 
>appropriate for some portion of the audience. If you have concrete 
>suggestions for how to simplify, those would be helpful.

I agree with what you said above about difficulty.

How about taking a RFC 3552 approach?  If I understood that document 
correctly, it takes a tutorial approach to define common terms 
instead of using a terminology section.  Thinking aloud, maybe the 
problem is trying to keep privacy concepts and guidance together.  I 
would say, remove Section 2, see how that "breaks" the document and 
then take it from there.

Or maybe the problem is trying to reconcile data and communication 
model.  I'll comment (I am not sure when) on the privacy mailing list.

>Not all secondary uses involve disclosure (such as the example given 
>in 4.2.3). I have added a sentence to clarify this, however:

That would be the NEA stuff.

>"Secondary use encompasses any use of data, including disclosure."

Ok.

I gather that you know that there will be debates about whether it is 
disclosure or secondary use. :-)

>We tried to think of a case where a consent mechanism was actually 
>developed in the IETF, but as a general matter consent mechanisms 
>tend to be out of scope, which is why we focus more on user controls 
>(which still show up rarely but do show up).

I would avoid trying to develop a consent mechanism.  I was think of 
this more in terms of consent (of the user).

RFC 3552 starts by discussing the goals.  The question I would ask is 
what are the goals of privacy.

Regards,
-sm


From rg+ietf@qualcomm.com  Sat Feb 23 19:35:05 2013
Return-Path: <rg+ietf@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 98A2B21F8EE7 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:35:05 -0800 (PST)
X-Quarantine-ID: <5AC6qjM288PP>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
X-Spam-Flag: NO
X-Spam-Score: -100.443
X-Spam-Level: 
X-Spam-Status: No, score=-100.443 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_HTML_ONLY=1.457, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5AC6qjM288PP for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:35:04 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id A3BA221F898A for <ietf@ietf.org>; Sat, 23 Feb 2013 19:35:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1361676904; x=1393212904; h=from:to:message-id:in-reply-to:references:date:subject: cc:content-transfer-encoding; bh=ItgcT8mM39U8bKjxvBIxIM28BcpeJItCTtTWdnIUYI0=; b=LNoFiunY0z8ibUWdUzNZnkcoFqj0XGImJAIAJcNA7iWSJZ+Wjr6tJBIo 2B16gJyfRKpmseLFDd5C12KG4c/oda/xth5qfk2GQp5lAI9WXKwSEAzN8 dq03/VW5CFkdb4GLPYf0VsuRxizdPt4hA8fjRqReVxnWXnh5n12isLlzz c=;
X-IronPort-AV: E=Sophos;i="4.84,726,1355126400"; d="scan'208,217";a="25372984"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 23 Feb 2013 19:35:03 -0800
From: Randall Gellens <randy@qti.qualcomm.com>
To: Doug Ewell <doug@ewellic.org>, Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>, "rg+ietf@qualcomm.com" <rg+ietf@qualcomm.com>
X-IronPort-AV: E=Sophos;i="4.84,726,1355126400";  d="scan'208,217";a="429714237"
Received: from warlock.qualcomm.com ([129.46.50.49]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Feb 2013 19:35:03 -0800
Received: from Ironmsg03-L.qualcomm.com (ironmsg03-L.qualcomm.com [172.30.48.18]) by warlock.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id r1O3Z2Zn002548 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 23 Feb 2013 19:35:02 -0800
X-IronPort-AV: E=Sophos;i="4.84,726,1355126400";  d="scan'208,217";a="429714179"
Received: from myvpn-r-107.ras.qualcomm.com (HELO [10.177.188.71]) ([10.64.0.107]) by Ironmsg03-L.qualcomm.com with ESMTP; 23 Feb 2013 19:34:58 -0800
Mime-Version: 1.0
Message-Id: <p06240600cd4f39966807@[10.177.188.71]>
In-Reply-To: <7e04165c-4807-4fa3-a587-a8230b37b476@NASANEXHC07.na.qualcomm.com>
References: <7e04165c-4807-4fa3-a587-a8230b37b476@NASANEXHC07.na.qualcomm.com>
X-Mailer: Eudora for Mac OS X
Date: Sat, 23 Feb 2013 19:34:47 -0800
Subject: RE: draft-gellens-negotiating-human-language-01
Mime-Version: 1.0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2013 03:35:05 -0000

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type=3D"text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>RE:
draft-gellens-negotiating-human-language-01</title></head><body>
<div>Hi Doug,</div>
<div><br></div>
<div>At 8:20 AM -0700 2/23/13, Doug Ewell wrote:</div>
<div><br></div>
<blockquote type=3D"cite" cite>You might want to reference BCP 47
instead of RFC 5646, but this is up to you.</blockquote>
<div><br></div>
<div>When I reference RFC 5646, the actual reference includes it as
both RFC and BCP.</div>
<div><br></div>
<blockquote type=3D"cite" cite>I would actually suggest leaving off the
reference to the Registry and just say the tag must conform to 5646
(or BCP 47). That will imply the use of the Registry.</blockquote>
<div><br></div>
<div>How about: &quot;The 'humintlang' attribute value MUST be a
language tag per RFC 5646&quot;?</div>
<div><br></div>
<div><br></div>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>
<hr></blockquote>
<blockquote type=3D"cite" cite>From: <a
href=3D"mailto:randy@qti.qualcomm.com">Randall Gellens</a><br>
Sent: 2/23/2013 1:18<br>
To: <a href=3D"mailto:doug@ewellic.org">Doug Ewell</a>; <a
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a
href=3D"mailto:rg+ietf@qualcomm.com">rg+ietf@qualcomm.com</a><br>
Cc: <a
href=3D"mailto:ietf-languages@iana.org">ietf-languages@iana.org</a><br>
Subject: Re: draft-gellens-negotiating-human-language-01<br>
</blockquote>
<blockquote type=3D"cite" cite>Hi Doug,</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>Thanks very much.&nbsp; So, if I
understand, your suggestions would be:</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>(1) Change the text for the possible new
'humintlang' attribute from:</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The
&quot;humintlang&quot; attribute value must be a single RFC 3066<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC3066] language tag in US-ASCII
[RFC3066].&nbsp; It is not dependent<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on the charset attribute.</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>To:<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The &quot;humintlang&quot; attribute
value must be a single RFC 5646<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [RFC5646] language tag from the IANA
registry [IANA-lang-<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tags].&nbsp; It is not dependent on the
charset attribute.</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>(2) Add RFC 5646 to the Normative
References</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>Since the IANA registry referenced now
was actually created by RFC 5646 not RFC 3066, this is both better
technically (for the reasons you mention) and more
correct.</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>Let me know if I've understood, and if
so, I may be able to get an update in before the cut-off.</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite>At 9:09 AM -0700 2/22/13, Doug Ewell
wrote:</blockquote>
<blockquote type=3D"cite" cite><br>
<blockquote type=3D"cite"
cite>Draft-gellens-negotiating-human-language-01, &quot;Negotiating
Human Language Using SDP&quot;, says this about the source of values
for the SDP 'lang' attribute: &gt; The &quot;lang&quot; attribute
value must be a single [RFC3066] language tag &gt; in US-ASCII
[RFC3066]. Although this wording is quoted from RFC 4566, the
subsequent section proposing a new 'humintlang' attribute uses the
same wording. Any new format or protocol that employs language tags
should apply BCP 47 (RFC 5646), not RFC 3066, which was obsoleted in
2006. BCP 47 allows the use of more than 7300 additional language
subtags derived from ISO 639-3, as well as script subtags based on ISO
15924 and variant subtags, none of which are permitted in a generative
manner by RFC 3066. The draft says, &quot;The attribute value should
be a language tag from the IANA registry [IANA-lang-tags]&quot;,
referencing www.iana.org/assignments/language-subtag-registry, but RFC
3066 does not use this registry; it references the core ISO standards
directly, which reduces stability, and it uses its own IANA registry
(also obsolete) only for a few dozen predefined variant tags, many of
which are deprecated in BCP 47. RFC 4647, also part of BCP 47,
provides guidelines for matching language tags, and may benefit the
SDP negotiation process described in the draft. -- Doug Ewell |
Thornton, CO, USA http://ewellic.org | @DougEwell =B0=A9</blockquote>
</blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite><br></blockquote>
<blockquote type=3D"cite" cite><tt>--</tt></blockquote>
<blockquote type=3D"cite" cite>Randall Gellens<br>
Opinions are personal;&nbsp;&nbsp;&nbsp; facts are
suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<br>
-------------- Randomly selected tag: ---------------<br>
Two things are infinite: the universe and human stupidity;<br>
and I'm not even sure about the universe.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--Albert
Einstein</blockquote>
<div><br></div>
<div><br></div>
<x-sigsep><pre>-- 
</pre></x-sigsep>
<div>Randall Gellens<br>
Opinions are personal;&nbsp;&nbsp;&nbsp; facts are
suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<br>
-------------- Randomly selected tag: ---------------<br>
Things are more like they used to be than they are new.<br>
</div></body>
</html>

From aservin@lacnic.net  Sat Feb 23 19:38:23 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D705F21F8934 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.69
X-Spam-Level: 
X-Spam-Status: No, score=-0.69 tagged_above=-999 required=5 tests=[AWL=-0.636,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, 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 ABNt7EVvAWQF for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:38:23 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id E97DA21F8C16 for <ietf@ietf.org>; Sat, 23 Feb 2013 19:38:22 -0800 (PST)
Received: from MiniR2D2.local (unknown [203.126.139.254]) by mail.lacnic.net.uy (Postfix) with ESMTP id F2A7C308445 for <ietf@ietf.org>; Sun, 24 Feb 2013 01:38:04 -0200 (UYST)
Message-ID: <51298B1E.60007@lacnic.net>
Date: Sun, 24 Feb 2013 11:38:06 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>
In-Reply-To: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Feb 2013 03:38:24 -0000

	Very good initiative.

	Twitter, Google+, Facebook, etc. could be the next steps. Let's embrace
new tools to collaborate.

Regards,
as

On 22/02/2013 20:35, IETF Chair wrote:
> Jari has created a blog as an experiment to see if would be possible to
> provide periodic status reports and other thoughts from the chair. Here's
> the link:
> 
> http://www.ietf.org/blog/2013/02/chairs-blog/
> 

From doug@ewellic.org  Sat Feb 23 19:45:15 2013
Return-Path: <doug@ewellic.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 5EE3621F8FB1 for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XLbaDHNCAZ4h for <ietf@ietfa.amsl.com>; Sat, 23 Feb 2013 19:45:14 -0800 (PST)
Received: from m1plsmtpa01-01.prod.mesa1.secureserver.net (m1plsmtpa01-01.prod.mesa1.secureserver.net [64.202.165.173]) by ietfa.amsl.com (Postfix) with ESMTP id 3245D21F8FAF for <ietf@ietf.org>; Sat, 23 Feb 2013 19:45:14 -0800 (PST)
Received: from [192.168.1.101] ([24.8.50.184]) by m1plsmtpa01-01.prod.mesa1.secureserver.net with  id 43lC1l0063ySsww013lCdC; Sat, 23 Feb 2013 20:45:13 -0700
MIME-Version: 1.0
To: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>,  "rg+ietf@qualcomm.com" <rg+ietf@qualcomm.com>
From: Doug Ewell <doug@ewellic.org>
Subject: RE: draft-gellens-negotiating-human-language-01
Date: Sat, 23 Feb 2013 20:44:43 -0700
Content-Type: multipart/alternative; boundary="_0E817988-1DCE-4F45-893C-FFEFD99DB45D_"
Message-Id: <20130224034514.3245D21F8FAF@ietfa.amsl.com>
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2013 03:45:15 -0000

--_0E817988-1DCE-4F45-893C-FFEFD99DB45D_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

That means essentially the same thing. Check to make sure your other review=
ers feel that wording is OK.

--
Doug Ewell | Thornton, CO, USA
http://ewellic.org | @DougEwell

-----Original Message-----
From: "Randall Gellens" <randy@qti.qualcomm.com>
Sent: =E2=80=8E2/=E2=80=8E23/=E2=80=8E2013 20:34
To: "Doug Ewell" <doug@ewellic.org>; "Randall Gellens" <randy@qti.qualcomm.=
com>; "ietf@ietf.org" <ietf@ietf.org>; "rg+ietf@qualcomm.com" <rg+ietf@qual=
comm.com>
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
Subject: RE: draft-gellens-negotiating-human-language-01

Hi Doug,


At 8:20 AM -0700 2/23/13, Doug Ewell wrote:


You might want to reference BCP 47 instead of RFC 5646, but this is up to y=
ou.


When I reference RFC 5646, the actual reference includes it as both RFC and=
 BCP.


I would actually suggest leaving off the reference to the Registry and just=
 say the tag must conform to 5646 (or BCP 47). That will imply the use of t=
he Registry.


How about: "The 'humintlang' attribute value MUST be a language tag per RFC=
 5646"?









From: Randall Gellens
Sent: 2/23/2013 1:18
To: Doug Ewell; ietf@ietf.org; rg+ietf@qualcomm.com
Cc: ietf-languages@iana.org
Subject: Re: draft-gellens-negotiating-human-language-01

Hi Doug,


Thanks very much.  So, if I understand, your suggestions would be:


(1) Change the text for the possible new 'humintlang' attribute from:


      The "humintlang" attribute value must be a single RFC 3066
      [RFC3066] language tag in US-ASCII [RFC3066].  It is not dependent
      on the charset attribute.


To:

      The "humintlang" attribute value must be a single RFC 5646
      [RFC5646] language tag from the IANA registry [IANA-lang-
      tags].  It is not dependent on the charset attribute.


(2) Add RFC 5646 to the Normative References


Since the IANA registry referenced now was actually created by RFC 5646 not=
 RFC 3066, this is both better technically (for the reasons you mention) an=
d more correct.


Let me know if I've understood, and if so, I may be able to get an update i=
n before the cut-off.




At 9:09 AM -0700 2/22/13, Doug Ewell wrote:


Draft-gellens-negotiating-human-language-01, "Negotiating Human Language Us=
ing SDP", says this about the source of values for the SDP 'lang' attribute=
: > The "lang" attribute value must be a single [RFC3066] language tag > in=
 US-ASCII [RFC3066]. Although this wording is quoted from RFC 4566, the sub=
sequent section proposing a new 'humintlang' attribute uses the same wordin=
g. Any new format or protocol that employs language tags should apply BCP 4=
7 (RFC 5646), not RFC 3066, which was obsoleted in 2006. BCP 47 allows the =
use of more than 7300 additional language subtags derived from ISO 639-3, a=
s well as script subtags based on ISO 15924 and variant subtags, none of wh=
ich are permitted in a generative manner by RFC 3066. The draft says, "The =
attribute value should be a language tag from the IANA registry [IANA-lang-=
tags]", referencing www.iana.org/assignments/language-subtag-registry, but =
RFC 3066 does not use this registry; it references the core ISO standards d=
irectly, which reduces stability, and it uses its own IANA registry (also o=
bsolete) only for a few dozen predefined variant tags, many of which are de=
precated in BCP 47. RFC 4647, also part of BCP 47, provides guidelines for =
matching language tags, and may benefit the SDP negotiation process describ=
ed in the draft. -- Doug Ewell | Thornton, CO, USA http://ewellic.org | @Do=
ugEwell =C2=B0=C2=A9




--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Two things are infinite: the universe and human stupidity;
and I'm not even sure about the universe.
                                       --Albert Einstein




--=20
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Things are more like they used to be than they are new.=

--_0E817988-1DCE-4F45-893C-FFEFD99DB45D_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<HTML><HEAD><TITLE>RE: draft-gellens-negotiating-human-language-01</TITLE>
<META content=3D"text/html; charset=3Dutf-8" http-equiv=3DContent-Type>
<STYLE type=3Dtext/css><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></STYLE>
</HEAD>
<BODY>
<DIV>
<DIV style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">That means =
essentially the same thing. Check to make sure your other reviewers feel th=
at wording is OK.<BR><BR>--<BR>Doug Ewell | Thornton, CO, USA<BR>http://ewe=
llic.org | @DougEwell</DIV></DIV>
<DIV dir=3Dltr>
<HR>
<SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGH=
T: bold">From: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,=
sans-serif"><A href=3D"mailto:randy@qti.qualcomm.com">Randall Gellens</A></=
SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; F=
ONT-WEIGHT: bold">Sent: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY:=
 Calibri,sans-serif">=E2=80=8E2/=E2=80=8E23/=E2=80=8E2013 20:34</SPAN><BR><=
SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT=
: bold">To: </SPAN><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,san=
s-serif"><A href=3D"mailto:doug@ewellic.org">Doug Ewell</A>; <A href=3D"mai=
lto:randy@qti.qualcomm.com">Randall Gellens</A>; <A href=3D"mailto:ietf@iet=
f.org">ietf@ietf.org</A>; <A href=3D"mailto:rg+ietf@qualcomm.com">rg+ietf@q=
ualcomm.com</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; FONT-FAMILY: Cali=
bri,sans-serif; FONT-WEIGHT: bold">Cc: </SPAN><SPAN style=3D"FONT-SIZE: 11p=
t; FONT-FAMILY: Calibri,sans-serif"><A href=3D"mailto:ietf-languages@iana.o=
rg">ietf-languages@iana.org</A></SPAN><BR><SPAN style=3D"FONT-SIZE: 11pt; F=
ONT-FAMILY: Calibri,sans-serif; FONT-WEIGHT: bold">Subject: </SPAN><SPAN st=
yle=3D"FONT-SIZE: 11pt; FONT-FAMILY: Calibri,sans-serif">RE: draft-gellens-=
negotiating-human-language-01</SPAN><BR><BR></DIV>
<DIV>Hi Doug,</DIV>
<DIV><BR></DIV>
<DIV>At 8:20 AM -0700 2/23/13, Doug Ewell wrote:</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type=3D"cite">You might want to reference BCP 47 instead of RFC=
 5646, but this is up to you.</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>When I reference RFC 5646, the actual reference includes it as both RF=
C and BCP.</DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type=3D"cite">I would actually suggest leaving off the referenc=
e to the Registry and just say the tag must conform to 5646 (or BCP 47). Th=
at will imply the use of the Registry.</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV>How about: "The 'humintlang' attribute value MUST be a language tag pe=
r RFC 5646"?</DIV>
<DIV><BR></DIV>
<DIV><BR></DIV>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">
<HR>
</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">From: <A href=3D"mailto:randy@qti.qualcomm.com">R=
andall Gellens</A><BR>Sent: 2/23/2013 1:18<BR>To: <A href=3D"mailto:doug@ew=
ellic.org">Doug Ewell</A>; <A href=3D"mailto:ietf@ietf.org">ietf@ietf.org</=
A>; <A href=3D"mailto:rg+ietf@qualcomm.com">rg+ietf@qualcomm.com</A><BR>Cc:=
 <A href=3D"mailto:ietf-languages@iana.org">ietf-languages@iana.org</A><BR>=
Subject: Re: draft-gellens-negotiating-human-language-01<BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">Hi Doug,</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">Thanks very much.&nbsp; So, if I understand, your=
 suggestions would be:</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">(1) Change the text for the possible new 'humintl=
ang' attribute from:</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The "humintlang" a=
ttribute value must be a single RFC 3066<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
[RFC3066] language tag in US-ASCII [RFC3066].&nbsp; It is not dependent<BR>=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; on the charset attribute.</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">To:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The "hu=
mintlang" attribute value must be a single RFC 5646<BR>&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; [RFC5646] language tag from the IANA registry [IANA-lang-<BR>&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; tags].&nbsp; It is not dependent on the charset=
 attribute.</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">(2) Add RFC 5646 to the Normative References</BLO=
CKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">Since the IANA registry referenced now was actual=
ly created by RFC 5646 not RFC 3066, this is both better technically (for t=
he reasons you mention) and more correct.</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">Let me know if I've understood, and if so, I may =
be able to get an update in before the cut-off.</BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">At 9:09 AM -0700 2/22/13, Doug Ewell wrote:</BLOC=
KQUOTE>
<BLOCKQUOTE type=3D"cite"><BR>
<BLOCKQUOTE type=3D"cite">Draft-gellens-negotiating-human-language-01, "Neg=
otiating Human Language Using SDP", says this about the source of values fo=
r the SDP 'lang' attribute: &gt; The "lang" attribute value must be a singl=
e [RFC3066] language tag &gt; in US-ASCII [RFC3066]. Although this wording =
is quoted from RFC 4566, the subsequent section proposing a new 'humintlang=
' attribute uses the same wording. Any new format or protocol that employs =
language tags should apply BCP 47 (RFC 5646), not RFC 3066, which was obsol=
eted in 2006. BCP 47 allows the use of more than 7300 additional language s=
ubtags derived from ISO 639-3, as well as script subtags based on ISO 15924=
 and variant subtags, none of which are permitted in a generative manner by=
 RFC 3066. The draft says, "The attribute value should be a language tag fr=
om the IANA registry [IANA-lang-tags]", referencing www.iana.org/assignment=
s/language-subtag-registry, but RFC 3066 does not use this registry; it ref=
erences the core ISO standards directly, which reduces stability, and it us=
es its own IANA registry (also obsolete) only for a few dozen predefined va=
riant tags, many of which are deprecated in BCP 47. RFC 4647, also part of =
BCP 47, provides guidelines for matching language tags, and may benefit the=
 SDP negotiation process described in the draft. -- Doug Ewell | Thornton, =
CO, USA http://ewellic.org | @DougEwell =C2=B0=C2=A9</BLOCKQUOTE></BLOCKQUO=
TE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><BR></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite"><TT>--</TT></BLOCKQUOTE>
<BLOCKQUOTE type=3D"cite">Randall Gellens<BR>Opinions are personal;&nbsp;&n=
bsp;&nbsp; facts are suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<BR>=
-------------- Randomly selected tag: ---------------<BR>Two things are inf=
inite: the universe and human stupidity;<BR>and I'm not even sure about the=
 universe.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;<SPAN></SPAN>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--Albert Eins=
tein</BLOCKQUOTE>
<DIV><BR></DIV>
<DIV><BR></DIV><X-SIGSEP><PRE>--=20
</PRE></X-SIGSEP>
<DIV>Randall Gellens<BR>Opinions are personal;&nbsp;&nbsp;&nbsp; facts are =
suspect;&nbsp;&nbsp;&nbsp; I speak for myself only<BR>-------------- Random=
ly selected tag: ---------------<BR>Things are more like they used to be th=
an they are new.<BR></DIV></BODY></HTML>=

--_0E817988-1DCE-4F45-893C-FFEFD99DB45D_--


From petithug@acm.org  Sun Feb 24 10:21:09 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F01BE21F908E for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 10:21:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.55
X-Spam-Level: 
X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.050, 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 sECnVWSAYHoN for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 10:21:08 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id C076921F908D for <ietf@ietf.org>; Sun, 24 Feb 2013 10:21:03 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902] (unknown [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 2D42A204B2; Sun, 24 Feb 2013 18:21:02 +0000 (UTC)
Message-ID: <512A5A10.4090406@acm.org>
Date: Sun, 24 Feb 2013 10:21:04 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net>
In-Reply-To: <51298B1E.60007@lacnic.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Feb 2013 18:21:09 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/23/2013 07:38 PM, Arturo Servin wrote:
> 
> Very good initiative.
> 
> Twitter, Google+, Facebook, etc. could be the next steps. Let's embrace new
> tools to collaborate.

Let's not.  Collaboration based on software running on servers run by the IETF
or a contractor payed by the IETF is fine.  Using collaboration tools owned by
the entities you listed, or similar entities, is not.

> 
> Regards, as
> 
> On 22/02/2013 20:35, IETF Chair wrote:
>> Jari has created a blog as an experiment to see if would be possible to 
>> provide periodic status reports and other thoughts from the chair.
>> Here's the link:
>> 
>> http://www.ietf.org/blog/2013/02/chairs-blog/
>> 
> 


- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRKloIAAoJECnERZXWan7EOMQP/05jtr5JVAQVZJJlP/At7cOx
wEYxU5Z/v5wn21m0BfCqnfFxXhAOP+/vGje785gS+GPZZktnWffQu7JN0TNny8Rn
U4nhgA19x7wdtz0jtTAV92JF4pEI2ZZ8uv74EoLzCobFW+biAy5jJM9mGFy+MqKB
tuXIQpYc5dDRxmQe8szGWoVw6+ycGLfsHgZdeOZGhjPO7cSwnYboQ5w5/4WIhpe/
Pd9hTvsig0D6dBB3Dwl+rC8T0lzP4+yqHgfF6Y7+kS0rjToWdbA1R87GVxtVip1q
08HL8DGRicfrxVrpezvQOO3D5aNjbe3tdu3zyff5jZHMg19OLPvM9hE66sFBSuHp
5pLt2jdTceG5BIwSc0u6+cIbGxFTVTO1+aU86K7SPzxlWNryWbDpPStUKszl7X9h
8fu7a4A5Jd1o5BgqIqtDNrLbdtrMP4p0emuLOaTA2GayQqfMi3tDlhgzHAF1jgpS
osWxUOhK6kaM441lFr9eJ/fTX130WnreDHoBhh3Fu090jukNZGBwqnSLkFrkqANO
L/4u0Q3YchSvh/NQO4d/mEha+y7vQ202shsT4cgm6OsiPYe5iCoPuPbFlexpPF8m
DQvoOyFjMmyJzpaEkzO0PBXYhgLEIynx/O7vq89/4R3SDU96t+aHnl5nxGmS/NDb
L8j1K0cpZ12CfCaGQevT
=4P1+
-----END PGP SIGNATURE-----

From hannes.tschofenig@gmx.net  Sun Feb 24 11:29:31 2013
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B944D21F90BC for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 11:29:31 -0800 (PST)
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 XTHWfu9ehLy0 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 11:29:29 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id CEBA521F90B7 for <ietf@ietf.org>; Sun, 24 Feb 2013 11:29:28 -0800 (PST)
Received: from mailout-de.gmx.net ([10.1.76.34]) by mrigmx.server.lan (mrigmx002) with ESMTP (Nemesis) id 0MOEEk-1UFDZD0yTU-005XuP for <ietf@ietf.org>; Sun, 24 Feb 2013 20:29:27 +0100
Received: (qmail invoked by alias); 24 Feb 2013 19:23:38 -0000
Received: from a88-115-219-140.elisa-laajakaista.fi (EHLO [192.168.100.100]) [88.115.219.140] by mail.gmx.net (mp034) with SMTP; 24 Feb 2013 20:23:38 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+60TtNYcu6UTz7gBYpJ4l8CIHSK13jWD8payywLF t9Rm3bDhEIFkf7
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <51291DC9.7050404@isdg.net>
Date: Sun, 24 Feb 2013 21:23:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1085)
X-Y-GMX-Trusted: 0
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, draft-iab-privacy-considerations@tools.ietf.org, SM <sm@resistor.net>, IAB IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Feb 2013 19:29:31 -0000

Hi Hector,=20


On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:

> Hi, with a quick review, and many comments and points, I think the one =
single part that I would have some questions about is in the intro:
>=20
>   The guidance provided in
>   this document is generic and can be used to inform the design of any
>   protocol to be used anywhere in the world, without reference to
>   specific legal frameworks.
>=20
>=20
> Is that a goal?
Yes, that's the goal.=20

As you know, the IETF develops specifications that are used on the =
Internet and not just in a specific region. Trying to interpret national =
laws and to provide region-by-region specific guidance did not seem =
desirable to us.=20

>  Do you feel you have reached providing such "Global Common" =
guidelines in the area of privacy?

Yes, I think so and this document follows the spirit of RFC 3552 =
"Guidelines for Writing RFC Text on Security Considerations". This =
document is essentially the privacy version of what RFC 3552 is for =
security. If you look at RFC 3552 you will also fail to find references =
to regulation on security matters (even though they exist).=20

We did look at many documents that seemed relevant input, such as the =
mentioned OECD document, and we spoke with data protection authorities =
and solicited their input. Our job would have been easier if we could =
have just re-used one of these documents listing the privacy principles. =
Unfortunately, it turns out that these documents were written for a =
different audience and that audience is supposed to have different =
capabilities regarding the design and the deployment of their services. =
In the IETF we do not have the same degree of freedom and impact and so =
we developed these guidelines to the best of our capabilities.=20

>  How does it compare to US ECPA provisions for "User Expectations" =
which has served as a global model for other jurisdictions?

>=20
> The reason I ask is because I have been very sensitive to ethical =
design and product liability issues in our product lines since 1986 =
following the guidelines set forth by the US ECPA for:
>=20
> - Thou shall not block/reject things without user knowledge,
> - Thou shall not tamper/edit things especially when passing things =
(relays),
> - Thou shall kept private things private.
>=20
> This was considered "Global" once upon a time.  Now its arguable.
What is interesting for us to find out whether you believe that the =
Electronic Communications Privacy Act has for additional privacy aspects =
we need to address in the document.=20
It is not our goal to interpret specific regulatory documents (even =
though it is interesting). This is the (well-paid) job of many lawyers.=20=


Ciao
Hannes

>=20
> --
> HLS
>=20
> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>> Hi SM,
>>=20
>> Thanks for your comments. Some responses are inline.
>>=20
>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>=20
>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>> This is an announcement of an IETF-wide Call for Comment on =
'Privacy Considerations for Internet Protocols'.
>>>>=20
>>>> The document is being considered for publication as an =
Informational RFC within the IAB stream, and is available for inspection =
here:
>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>> In Section 1:
>>>=20
>>>  'With regard to data, often it is a concept applied to
>>>   "personal data," information relating to an identified or
>>>   identifiable individual.'
>>>=20
>>> I suggest rewriting the above sentence.
>> The authors have re-written that sentence several times and in =
different ways already. Do you have a specific suggestion about how to =
improve it?
>>=20
>>>  "Many sets of privacy principles and privacy design frameworks have =
been
>>>   developed in different forums over the years."
>>>=20
>>> There is also some work in the APEC region (see =
http://publications.apec.org/publication-detail.php?pub_id=3D390 =
(payware)).
>> As far as I know the APEC framework is one of many frameworks (none =
of which we cite since there are so many) based on the OECD-style FIPs. =
Is that incorrect?
>>=20
>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC =
6772.
>> Fixed.
>>=20
>>> I read some of the previous versions of this draft.  The Abstract =
Section describes the document as providing guidance for developing =
privacy considerations for inclusion in protocol specifications.  I =
found the draft difficult to digest.  I suggest simplifying the draft to =
make the guidance accessible to the target audience.
>> I'm not quite sure what you are recommending here, but we have had =
conversations in the IAB privacy program about moving the guidance part =
up, or otherwise trying to make the focus on the guidance piece more =
prominent. The difficulty is that there is a broad range in the extent =
to which potential readers are familiar with privacy concepts, so =
jumping straight into the guidance would not be appropriate for some =
portion of the audience. If you have concrete suggestions for how to =
simplify, those would be helpful.
>>=20
>>> One of the issues nowadays is what to do about intermediaries.  If I =
am not mistaken RFC 3238 was one of the first documents to tackle that =
question from a privacy perspective.  There have been a few proposals to =
introduce intermediaries as part of the architecture (I am using the =
word is used loosely).  It is easy to argue for intermediaries based on =
use cases.  There was a case recently where the users only became aware =
that they have signed up for using an intermediary through the EULA.
>>>=20
>>> The draft introduces the concept of secondary use (Section 4.2.3).  =
Strictly speaking, it is a disclosure (Section 4.2.4).
>> Not all secondary uses involve disclosure (such as the example given =
in 4.2.3). I have added a sentence to clarify this, however:
>>=20
>> "Secondary use encompasses any use of data, including disclosure."
>>=20
>>> The draft mentions consent in several places.  The authors are =
likely aware that consent was a hot topic for DNT.  It's easier to start =
with something that is easy for the average person to understand and =
build from there.  Section 7.2 could more about consent instead of user =
participation or control.
>> We tried to think of a case where a consent mechanism was actually =
developed in the IETF, but as a general matter consent mechanisms tend =
to be out of scope, which is why we focus more on user controls (which =
still show up rarely but do show up).
>>=20
>> Thanks,
>> Alissa
>>=20
>>> Regards,
>>> -sm
>>>=20
>>=20
>>=20
>>=20
>=20
>=20


From jmpolk@cisco.com  Sun Feb 24 12:08:59 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F31921F90E1 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 12:08:59 -0800 (PST)
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 nR-HR3KsQosG for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 12:08:58 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id EC78421F90BF for <ietf@ietf.org>; Sun, 24 Feb 2013 12:08:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6668; q=dns/txt; s=iport; t=1361736538; x=1362946138; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=/uyb5uAcPA19YQpABriO/sNyYjTx6Xm6cC5aK2WBLLI=; b=Ws/hnysI/rcxIDjMJ2HDRZdvDfB0/Ywm57pitjrNsikvAv34MtDqrJha wpUacFsy3Z4G//jd7iT6aZLEzmftGMtH2DSqdBXE7rnKZ+uhYtv2XAhRR NOPbJnoKKR302L1dk55m017xuk5WlYov8RbZe5N5jTga7LjelFujeGfcB c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFABhyKlGtJXG//2dsb2JhbABFwVCBEBZzgh8BAQEEOC8SEAcCAg4DBAEBAQkeBw8KLQkIBgESCYgKDJAarD2JbYUWCwcGgzoDiDM2jnGEKYsfgyY
X-IronPort-AV: E=Sophos;i="4.84,730,1355097600"; d="scan'208";a="180589127"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-5.cisco.com with ESMTP; 24 Feb 2013 20:08:57 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1OK8uY7027011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 24 Feb 2013 20:08:57 GMT
Message-Id: <201302242008.r1OK8uY7027011@rcdn-core2-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 24 Feb 2013 14:08:57 -0600
To: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>,  "rg+ietf@qualcomm.com" <rg+ietf@qualcomm.com>
From: James Polk <jmpolk@cisco.com>
Subject: RE: draft-gellens-negotiating-human-language-01
In-Reply-To: <20130224034514.3245D21F8FAF@ietfa.amsl.com>
References: <20130224034514.3245D21F8FAF@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Authenticated-User: jmpolk
Cc: "ietf-languages@iana.org" <ietf-languages@iana.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2013 20:08:59 -0000

Hey Randy

SDP, defined in the MMUSIC WG (why isn't this=20
being discussed on that list? because it'll have=20
to go to that list before this draft progresses=20
anyway), isn't a negotiation protocol, it's an=20
offer/answer exchange (per RFC3264) - and even if=20
you didn't want SIP, there's not a back-and-forth=20
that typical "negotiations" have. You're already familiar with RFC 4566=
 (SDP).

SIP has a session layer language tag, from RFC 3261

20.3 Accept-Language

    The Accept-Language header field is used in requests to indicate the
    preferred languages for reason phrases, session descriptions, or
    status responses carried as message bodies in the response.  If no
    Accept-Language header field is present, the server SHOULD assume all
    languages are acceptable to the client.

    The Accept-Language header field follows the syntax defined in
    [H14.4].  The rules for ordering the languages based on the "q"
    parameter apply to SIP as well.

    Example:

       Accept-Language: da, en-gb;q=3D0.8, en;q=3D0.7

RFC 4566 has an attribute (a=3Dlang) that you=20
quote, but I'm confused why you first propose using it, then dismiss its=
 use.

Now, your draft does say

    For various reasons, including
    the ability to establish multiple streams each using a different
    media (e.g., voice, text, video), it makes sense to use a per-stream
    negotiation mechanism, using SDP.

but there I have not found justification (or even=20
examples) for these "various reasons"... maybe I=20
missed them, but media level attributes are there=20
for those offers that have more than one m=3D line,=20
where the same attribute has a different value=20
per m=3D line. In your one example, you list 'en' &=20
'it' for the languages you want to receive in the=20
offer, and just 'it' in the answer. Why does this=20
have to be a media level attribute when you're=20
really after _the_one_language_for_all_m-lines_?

James
At 09:44 PM 2/23/2013, Doug Ewell wrote:
>That means essentially the same thing. Check to=20
>make sure your other reviewers feel that wording is OK.
>
>--
>Doug Ewell | Thornton, CO, USA
>http://ewellic.org | @DougEwell
>
>----------
>From: <mailto:randy@qti.qualcomm.com>Randall Gellens
>Sent: =E2=80=8E2/=E2=80=8E23/=E2=80=8E2013 20:34
>To: <mailto:doug@ewellic.org>Doug Ewell;=20
><mailto:randy@qti.qualcomm.com>Randall Gellens;=20
><mailto:ietf@ietf.org>ietf@ietf.org;=20
><mailto:rg+ietf@qualcomm.com>rg+ietf@qualcomm.com
>Cc: <mailto:ietf-languages@iana.org>ietf-languages@iana.org
>Subject: RE: draft-gellens-negotiating-human-language-01
>
>Hi Doug,
>
>At 8:20 AM -0700 2/23/13, Doug Ewell wrote:
>
>>You might want to reference BCP 47 instead of=20
>>RFC 5646, but this is up to you.
>
>When I reference RFC 5646, the actual reference=20
>includes it as both RFC and BCP.
>
>>I would actually suggest leaving off the=20
>>reference to the Registry and just say the tag=20
>>must conform to 5646 (or BCP 47). That will imply the use of the Registry.
>
>How about: "The 'humintlang' attribute value=20
>MUST be a language tag per RFC 5646"?
>
>
>>
>>
>>----------
>>From: <mailto:randy@qti.qualcomm.com>Randall Gellens
>>Sent: 2/23/2013 1:18
>>To: <mailto:doug@ewellic.org>Doug Ewell;=20
>><mailto:ietf@ietf.org>ietf@ietf.org;=20
>><mailto:rg+ietf@qualcomm.com>rg+ietf@qualcomm.com
>>Cc: <mailto:ietf-languages@iana.org>ietf-languages@iana.org
>>Subject: Re: draft-gellens-negotiating-human-language-01
>>Hi Doug,
>>
>>Thanks very much.  So, if I understand, your suggestions would be:
>>
>>(1) Change the text for the possible new 'humintlang' attribute from:
>>
>>       The "humintlang" attribute value must be a single RFC 3066
>>       [RFC3066] language tag in US-ASCII [RFC3066].  It is not dependent
>>       on the charset attribute.
>>
>>To:
>>
>>       The "humintlang" attribute value must be a single RFC 5646
>>       [RFC5646] language tag from the IANA registry [IANA-lang-
>>       tags].  It is not dependent on the charset attribute.
>>
>>(2) Add RFC 5646 to the Normative References
>>
>>Since the IANA registry referenced now was=20
>>actually created by RFC 5646 not RFC 3066, this=20
>>is both better technically (for the reasons you mention) and more correct.
>>
>>Let me know if I've understood, and if so, I=20
>>may be able to get an update in before the cut-off.
>>
>>
>>At 9:09 AM -0700 2/22/13, Doug Ewell wrote:
>>
>>>Draft-gellens-negotiating-human-language-01,=20
>>>"Negotiating Human Language Using SDP", says=20
>>>this about the source of values for the SDP=20
>>>'lang' attribute: > The "lang" attribute value=20
>>>must be a single [RFC3066] language tag > in=20
>>>US-ASCII [RFC3066]. Although this wording is=20
>>>quoted from RFC 4566, the subsequent section=20
>>>proposing a new 'humintlang' attribute uses=20
>>>the same wording. Any new format or protocol=20
>>>that employs language tags should apply BCP 47=20
>>>(RFC 5646), not RFC 3066, which was obsoleted=20
>>>in 2006. BCP 47 allows the use of more than=20
>>>7300 additional language subtags derived from=20
>>>ISO 639-3, as well as script subtags based on=20
>>>ISO 15924 and variant subtags, none of which=20
>>>are permitted in a generative manner by RFC=20
>>>3066. The draft says, "The attribute value=20
>>>should be a language tag from the IANA=20
>>>registry [IANA-lang-tags]", referencing=20
>>>www.iana.org/assignments/language-subtag-registry,=20
>>>but RFC 3066 does not use this registry; it=20
>>>references the core ISO standards directly,=20
>>>which reduces stability, and it uses its own=20
>>>IANA registry (also obsolete) only for a few=20
>>>dozen predefined variant tags, many of which=20
>>>are deprecated in BCP 47. RFC 4647, also part=20
>>>of BCP 47, provides guidelines for matching=20
>>>language tags, and may benefit the SDP=20
>>>negotiation process described in the draft. --=20
>>>Doug Ewell | Thornton, CO, USA http://ewellic.org | @DougEwell =C2=B0=C2=
=A9
>>
>>
>>--
>>Randall Gellens
>>Opinions are personal;    facts are suspect;    I speak for myself only
>>-------------- Randomly selected tag: ---------------
>>Two things are infinite: the universe and human stupidity;
>>and I'm not even sure about the universe.
>>                                        --Albert Einstein
>
>
>
>--
>
>Randall Gellens
>Opinions are personal;    facts are suspect;    I speak for myself only
>-------------- Randomly selected tag: ---------------
>Things are more like they used to be than they are new.


From aservin@lacnic.net  Sun Feb 24 17:24:01 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC9121F918C for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 17:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.467
X-Spam-Level: *
X-Spam-Status: No, score=1.467 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119, MIME_QP_LONG_LINE=1.396, 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 y4z3AaYdXBgn for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 17:24:00 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3700E21F918B for <ietf@ietf.org>; Sun, 24 Feb 2013 17:24:00 -0800 (PST)
Received: from [203.126.139.29] (unknown [111.223.96.126]) by mail.lacnic.net.uy (Postfix) with ESMTP id 5BE3B308445; Sun, 24 Feb 2013 23:23:48 -0200 (UYST)
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <512A5A10.4090406@acm.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>
X-Mailer: iPad Mail (10B141)
From: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF chair's blog
Date: Mon, 25 Feb 2013 09:21:52 +0800
To: Marc Petit-Huguenin <petithug@acm.org>
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 25 Feb 2013 01:24:01 -0000

Why not?

I, my organization and many more (included ISOC) have found them very useful=
 for outreach activities. I do not see why the IETF shouldn't. Please, tell m=
e.


as

Sent from my iPad

On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>=20
>> Very good initiative.
>>=20
>> Twitter, Google+, Facebook, etc. could be the next steps. Let's embrace n=
ew
>> tools to collaborate.
>=20
> Let's not.  Collaboration based on software running on servers run by the I=
ETF
> or a contractor payed by the IETF is fine.  Using collaboration tools owne=
d by
> the entities you listed, or similar entities, is not.
>=20
>>=20
>> Regards, as
>>=20
>> On 22/02/2013 20:35, IETF Chair wrote:
>>> Jari has created a blog as an experiment to see if would be possible to=20=

>>> provide periodic status reports and other thoughts from the chair.
>>> Here's the link:
>>>=20
>>> http://www.ietf.org/blog/2013/02/chairs-blog/
>=20
>=20
> - --=20
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: http://blog.marc.petit-huguenin.org
> Profile: http://www.linkedin.com/in/petithug
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>=20
> iQIcBAEBCAAGBQJRKloIAAoJECnERZXWan7EOMQP/05jtr5JVAQVZJJlP/At7cOx
> wEYxU5Z/v5wn21m0BfCqnfFxXhAOP+/vGje785gS+GPZZktnWffQu7JN0TNny8Rn
> U4nhgA19x7wdtz0jtTAV92JF4pEI2ZZ8uv74EoLzCobFW+biAy5jJM9mGFy+MqKB
> tuXIQpYc5dDRxmQe8szGWoVw6+ycGLfsHgZdeOZGhjPO7cSwnYboQ5w5/4WIhpe/
> Pd9hTvsig0D6dBB3Dwl+rC8T0lzP4+yqHgfF6Y7+kS0rjToWdbA1R87GVxtVip1q
> 08HL8DGRicfrxVrpezvQOO3D5aNjbe3tdu3zyff5jZHMg19OLPvM9hE66sFBSuHp
> 5pLt2jdTceG5BIwSc0u6+cIbGxFTVTO1+aU86K7SPzxlWNryWbDpPStUKszl7X9h
> 8fu7a4A5Jd1o5BgqIqtDNrLbdtrMP4p0emuLOaTA2GayQqfMi3tDlhgzHAF1jgpS
> osWxUOhK6kaM441lFr9eJ/fTX130WnreDHoBhh3Fu090jukNZGBwqnSLkFrkqANO
> L/4u0Q3YchSvh/NQO4d/mEha+y7vQ202shsT4cgm6OsiPYe5iCoPuPbFlexpPF8m
> DQvoOyFjMmyJzpaEkzO0PBXYhgLEIynx/O7vq89/4R3SDU96t+aHnl5nxGmS/NDb
> L8j1K0cpZ12CfCaGQevT
> =3D4P1+
> -----END PGP SIGNATURE-----

From abdussalambaryun@gmail.com  Sun Feb 24 21:32:53 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE5521F9119; Sun, 24 Feb 2013 21:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.558
X-Spam-Level: 
X-Spam-Status: No, score=-3.558 tagged_above=-999 required=5 tests=[AWL=0.041,  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 OytI8e8fvLj4; Sun, 24 Feb 2013 21:32:52 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 500F621F90A6; Sun, 24 Feb 2013 21:32:52 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id kp1so1543182pab.3 for <multiple recipients>; Sun, 24 Feb 2013 21:32:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=clA/s3CK7v0T/BYeQKHg05PHj/0UwihFc0psQA/fe98=; b=DoQdlGVQLNkzBYtoNebE/cVCpfFN/tb4G8I48aMyeUWE6Ufyv9cVc84Xno/V3j6rPU QD4pO7JClzduAL6MWvhAd3Cl1raVcVL/zlR8M0sPbIknEh1u7GCak/YYCSkd9xGcaikd BWPt9Hrj7nWHD0flDK6ua76np4HEQQ+g73/0SKv/odmIl5M+cOnQ1mRrBmYmEEKBW/uP 2MTY42osD+m8EMlzG0JJ2VOWzyHg4t/qrsZrHfd/KwFQpA0dqUjfAWhrZwzkpmP23jIt sSM/vj3khOzbHhowusJub6AWZxTdUUe0ew600wneFxXT5jS12Bl7Ev604hkqXX/twxmu wWyg==
MIME-Version: 1.0
X-Received: by 10.67.5.193 with SMTP id co1mr17254569pad.6.1361770372119; Sun, 24 Feb 2013 21:32:52 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Sun, 24 Feb 2013 21:32:51 -0800 (PST)
In-Reply-To: <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com>
Date: Mon, 25 Feb 2013 06:32:51 +0100
Message-ID: <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-cardenas-dff@tools.ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 05:32:53 -0000

Reply to your request dated 07/02/2013
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 24/02/2013

Reviewer Comment #AB2: Related to Applicability and Processing.
++++++++++++++++++++++++++++++++++++

The DFF mechanism specified in the document can either be used as
"route-over" IPv6 forwarding mechanism (Mode of Operation:
"route-over"), or as "mesh-under"
LoWPAN adaptation layer (Mode of Operation: "mesh-under").

AB> the document should specify that these two modes must not occur in
the same time.

Section 3. Applicability
AB> is general, not sure what is the use-case for the protocol,

AB> does this protocol only for neighbor forwarding and exclude IP
tunnling, then specify.

Section 5.
AB> mentioned RFC6130 this is for MANET so does this protocol apply
for MANETs, not mentioned in section 3. Do you mean that LowPAN is
similar to MANET, not sure how this protocol works in all environment?

AB> how does this protocol forward without considering the IP
forwarding? Should IP forward stop its function (not clear)?

AB> DFF has access on <list of bidirectional neighbors> what kind of
access you mean?

Section 9.1
AB> how can DFF become a routing domain? it is not a routing protocol?
Does this DFF work with ALL routing protocols in the IETF, please
specify either ALL or which?

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------



> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>   <draft-cardenas-dff-09.txt> as Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    This document specifies the "Depth-First Forwarding" (DFF) protocol
>>    for IPv6 networks, a data forwarding mechanism that can increase
>>    reliability of data delivery in networks with dynamic topology and/or
>>    lossy links.  The protocol operates entirely on the forwarding plane,
>>    but may interact with the routing plane.  DFF forwards data packets
>>    using a mechanism similar to a "depth-first search" for the
>>    destination of a packet.  The routing plane may be informed of
>>    failures to deliver a packet or loops.  This document specifies the
>>    DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>>    addition also for LoWPAN "mesh-under" networks (as specified in
>>    RFC4944).
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>    http://datatracker.ietf.org/ipr/1645/
>>    http://datatracker.ietf.org/ipr/1646/
>>
>>
>>
>>
>

From abdussalambaryun@gmail.com  Sun Feb 24 21:59:36 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61C921F9126; Sun, 24 Feb 2013 21:59:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.258
X-Spam-Level: 
X-Spam-Status: No, score=-3.258 tagged_above=-999 required=5 tests=[AWL=-0.259, 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 D5jbc5R6EUFl; Sun, 24 Feb 2013 21:59:34 -0800 (PST)
Received: from mail-da0-f49.google.com (mail-da0-f49.google.com [209.85.210.49]) by ietfa.amsl.com (Postfix) with ESMTP id EDDBA21F910A; Sun, 24 Feb 2013 21:59:33 -0800 (PST)
Received: by mail-da0-f49.google.com with SMTP id t11so369276daj.22 for <multiple recipients>; Sun, 24 Feb 2013 21:59:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=jL9HLtUH0RzP+iP5IsdtgddYl9dcqx8RZOn+bWqCI/Q=; b=FL/cxpJjoEOWSITZqTqf/DZKbPmgxacKy8A/pcnQhgY9rXaPwUos/dPbGgYEh8ncWJ rvWo27+TdqbRzG15HHu6I0QzxeaFPvCof9tryU+Tmyzu5X0MwRdH/AE+FGkofaGutgLV gtaD2d0buhvJs6RHGooiWYlhlDtkY5cVnhOdUajl1V3FM+J+smUG66+asv0H6uOLKp2K 5lnDCwnX5dbqGUIRtWs0Ohb1oEHfOxjVTS86QxTH2tO4KGyKSvmCo/e/xrudE/UqDWl+ dKaBeh+NAx4jDKjkpSobEjjEl02FCPJBFbYqFxT6F31gZOU/fsyVCVwBouUFJh3Ww6i3 Ljig==
MIME-Version: 1.0
X-Received: by 10.68.28.194 with SMTP id d2mr15874713pbh.215.1361771973678; Sun, 24 Feb 2013 21:59:33 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Sun, 24 Feb 2013 21:59:33 -0800 (PST)
In-Reply-To: <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com> <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com>
Date: Mon, 25 Feb 2013 06:59:33 +0100
Message-ID: <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: draft-cardenas-dff@tools.ietf.org, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 05:59:36 -0000

Reply to your request dated 07/02/2013
Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 24/02/2013

Reviewer Comment #AB3: Related to Processing and interaction with others.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

In section 11
AB>The DFF MUST contain the next hop of RIB, but in section 5 it mentions MAY.
AB>suggest> please amend both should be same requirement for protocol.

AB> the way it determines the next hop does not show that this
protocol is sensitive to other parameters in the RIB, it just takes
the addresses without considering the routing protocol strategy in its
RIB. IMHO, this may make the DFF make mistakes in taking the right
next hop,

Section 12
AB> is not understood, it seems a general not specific, I suggest more
explaining how this interaction with routing protocol is occured?

Section 13
AB> who creates the sequence number is it the DFF or the routing
protocol. It seems the DFF, so please specify how it will
maintain/save such sequence number in this section.
AB> suggest this section to be : DFF Sequence Number.

Section 14
AB> again do you mean that both modes can work together. I don't think
that you mean that, so you should specify that each routing domain
MUST have one mode, and specify how to maintain that mode in such
protocol.

Overall> about processing>
AB> this protocol needs to be discussed more how it will interact with
the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore
alot of work done in the IETF which is not fiting the general
applicability it is offering.

+++++++++++++The END+++++++++++

Regards
AB
---------------------------------------------------------------------------------------
This message and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
This message is in compliance with the IETF regulations.
---------------------------------------------------------------------------------------


>> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>>   <draft-cardenas-dff-09.txt> as Experimental RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may
>>> be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>    This document specifies the "Depth-First Forwarding" (DFF) protocol
>>>    for IPv6 networks, a data forwarding mechanism that can increase
>>>    reliability of data delivery in networks with dynamic topology and/or
>>>    lossy links.  The protocol operates entirely on the forwarding plane,
>>>    but may interact with the routing plane.  DFF forwards data packets
>>>    using a mechanism similar to a "depth-first search" for the
>>>    destination of a packet.  The routing plane may be informed of
>>>    failures to deliver a packet or loops.  This document specifies the
>>>    DFF mechanism both for IPv6 networks (as specified in RFC2460) and in
>>>    addition also for LoWPAN "mesh-under" networks (as specified in
>>>    RFC4944).
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>>
>>>
>>> The following IPR Declarations may be related to this I-D:
>>>
>>>    http://datatracker.ietf.org/ipr/1645/
>>>    http://datatracker.ietf.org/ipr/1646/
>>>
>>>
>>>
>>>
>>
>

From trammell@tik.ee.ethz.ch  Sun Feb 24 22:52:24 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B265F21F91D5 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:52:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.186
X-Spam-Level: 
X-Spam-Status: No, score=-6.186 tagged_above=-999 required=5 tests=[AWL=0.413,  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 d8m4oH5ma9h8 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:52:23 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED2321F91C5 for <ietf@ietf.org>; Sun, 24 Feb 2013 22:52:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id BB38DD9307; Mon, 25 Feb 2013 07:52:22 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5R1gLgCoef6e; Mon, 25 Feb 2013 07:52:22 +0100 (MET)
Received: from [10.0.27.102] (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 74D14D9304; Mon, 25 Feb 2013 07:52:22 +0100 (MET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IETF chair's blog
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>
Date: Mon, 25 Feb 2013 07:52:21 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1499)
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, 25 Feb 2013 06:52:24 -0000

Hi, Arturo, all,

It does not seem appropriate for a technical standards organization =
dedicated to making the Internet work better through the development of =
open standards to implicitly endorse "communication protocols" which are =
based on closed access to distributed databases through interfaces that =
can and do change at the whim of the organizations that control them, =
further where those organizations have demonstrated a willingness to =
assert editorial control over the content they disseminate.

If a social network were to emerge that allows open participation at =
_every_ level, based on an open application protocol therefor, that =
would be something different. I fear that network effects have already =
made  such a thing unlikely in this iteration of "Internet x.0".

(Aside: I myself have used all three listed networks to get attention =
for ISOC functions at the chapter level, though I'm uneasy about that. I =
won't dispute that they're great for outreach, and when you're doing =
outreach, you have to go where the people are. In my defense, though, I =
was advertising a talk wherein I discussed why it's a bad idea to rely =
on such closed platforms. :) )

Cheers,

Brian

On Feb 25, 2013, at 2:21 AM, Arturo Servin <aservin@lacnic.net> wrote:

>=20
> Why not?
>=20
> I, my organization and many more (included ISOC) have found them very =
useful for outreach activities. I do not see why the IETF shouldn't. =
Please, tell me.
>=20
>=20
> as
>=20
> Sent from my iPad
>=20
> On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org> =
wrote:
>=20
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>=20
>> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>>=20
>>> Very good initiative.
>>>=20
>>> Twitter, Google+, Facebook, etc. could be the next steps. Let's =
embrace new
>>> tools to collaborate.
>>=20
>> Let's not.  Collaboration based on software running on servers run by =
the IETF
>> or a contractor payed by the IETF is fine.  Using collaboration tools =
owned by
>> the entities you listed, or similar entities, is not.
>>=20
>>>=20
>>> Regards, as
>>>=20
>>> On 22/02/2013 20:35, IETF Chair wrote:
>>>> Jari has created a blog as an experiment to see if would be =
possible to=20
>>>> provide periodic status reports and other thoughts from the chair.
>>>> Here's the link:
>>>>=20
>>>> http://www.ietf.org/blog/2013/02/chairs-blog/
>>=20
>>=20
>> - --=20
>> Marc Petit-Huguenin
>> Email: marc@petit-huguenin.org
>> Blog: http://blog.marc.petit-huguenin.org
>> Profile: http://www.linkedin.com/in/petithug
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.12 (GNU/Linux)
>>=20
>> iQIcBAEBCAAGBQJRKloIAAoJECnERZXWan7EOMQP/05jtr5JVAQVZJJlP/At7cOx
>> wEYxU5Z/v5wn21m0BfCqnfFxXhAOP+/vGje785gS+GPZZktnWffQu7JN0TNny8Rn
>> U4nhgA19x7wdtz0jtTAV92JF4pEI2ZZ8uv74EoLzCobFW+biAy5jJM9mGFy+MqKB
>> tuXIQpYc5dDRxmQe8szGWoVw6+ycGLfsHgZdeOZGhjPO7cSwnYboQ5w5/4WIhpe/
>> Pd9hTvsig0D6dBB3Dwl+rC8T0lzP4+yqHgfF6Y7+kS0rjToWdbA1R87GVxtVip1q
>> 08HL8DGRicfrxVrpezvQOO3D5aNjbe3tdu3zyff5jZHMg19OLPvM9hE66sFBSuHp
>> 5pLt2jdTceG5BIwSc0u6+cIbGxFTVTO1+aU86K7SPzxlWNryWbDpPStUKszl7X9h
>> 8fu7a4A5Jd1o5BgqIqtDNrLbdtrMP4p0emuLOaTA2GayQqfMi3tDlhgzHAF1jgpS
>> osWxUOhK6kaM441lFr9eJ/fTX130WnreDHoBhh3Fu090jukNZGBwqnSLkFrkqANO
>> L/4u0Q3YchSvh/NQO4d/mEha+y7vQ202shsT4cgm6OsiPYe5iCoPuPbFlexpPF8m
>> DQvoOyFjMmyJzpaEkzO0PBXYhgLEIynx/O7vq89/4R3SDU96t+aHnl5nxGmS/NDb
>> L8j1K0cpZ12CfCaGQevT
>> =3D4P1+
>> -----END PGP SIGNATURE-----


From petithug@acm.org  Sun Feb 24 22:52:30 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 910E321F91EE for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:52:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.046, 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 Zt09eciKY3-H for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:52:29 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 83B9B21F91E5 for <ietf@ietf.org>; Sun, 24 Feb 2013 22:52:28 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902] (unknown [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 1B5B920515; Mon, 25 Feb 2013 06:52:27 +0000 (UTC)
Message-ID: <512B0A2D.3050102@acm.org>
Date: Sun, 24 Feb 2013 22:52:29 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>
In-Reply-To: <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 06:52:30 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/24/2013 05:21 PM, Arturo Servin wrote:
> 
> Why not?
> 
> I, my organization and many more (included ISOC) have found them very
> useful for outreach activities. I do not see why the IETF shouldn't.
> Please, tell me.

You said collaborate below, now you are saying outreach.  What I said was
specifically about collaboration.

> 
> 
> as
> 
> Sent from my iPad
> 
> On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org> wrote:
> 
> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>>> 
>>>> Very good initiative.
>>>> 
>>>> Twitter, Google+, Facebook, etc. could be the next steps. Let's
>>>> embrace new tools to collaborate.
> 
> Let's not.  Collaboration based on software running on servers run by the 
> IETF or a contractor payed by the IETF is fine.  Using collaboration tools 
> owned by the entities you listed, or similar entities, is not.
> 
>>>> 
>>>> Regards, as
>>>> 
>>>> On 22/02/2013 20:35, IETF Chair wrote:
>>>>> Jari has created a blog as an experiment to see if would be
>>>>> possible to provide periodic status reports and other thoughts from
>>>>> the chair. Here's the link:
>>>>> 
>>>>> http://www.ietf.org/blog/2013/02/chairs-blog/
> 
> 
> 

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRKworAAoJECnERZXWan7EZXoP/0ehb3X/JWVcNRzB4Wq6EI1Y
KuSgWcbFcluE9Lb5Oy65D3Cxg05g6hy3q/SZ3/e8sGR4h3OoRorkGPOrXJ0Aquuc
DkAHQ5pf3yq5524RsV3k3kuuVW2ujTFxKb4u0FynoPhR6SRwNvvdvneP8Wyp9+mA
wRRtmd6peLQjIs4JZ5hROc2X2UlkIlaixonsjs7tkwo2PO5etuIGpMTDegM421Ke
K3L378iKzQa9UkYqhpuXix8HDGoUFTuJrhQTQVDz+lgnew5Hxy4h2lhKwIgYyQn0
30EyPv79RWw1tLBMXvRoLM19NjThuQZyRHwqQbFbe65B02JWVsbgDN3GY03BWOvA
GuqMnHal+ddkcYfPX+Dgzn9fadJvPwz+zuai7Hqey26PQiJzonKyUKB5KzpkDbyu
KOvsIHbx1mP7XP5YmI6QnNYAzH6a9uvAxZHVeWFXJg5QnqWj89EWiASlnelVXaBL
3geMF+WIsdQY78NqJHKnXnS0gMa9oL1n8QE7Ped0uDKop+7p+8n772Eth0pLaekV
gnHa7D1Is1k0sKb+yuXUAHu9ml9MASZytgryPoZ7ZAdZKTcldE3f/YS2fyUtjkNp
42frEnmsriw9n5BQAqYFK1BJcyqwVOx1qXzhY5TfsrGavp65xi4ru4z4pIdoZkdB
iLrVuEGNU/USYznpgheR
=Fh1E
-----END PGP SIGNATURE-----

From aservin@lacnic.net  Sun Feb 24 22:57:05 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE22921F91E5 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:57:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r7nz6K00Us-K for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:57:03 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id EEDC721F91E1 for <ietf@ietf.org>; Sun, 24 Feb 2013 22:56:44 -0800 (PST)
Received: from minir2d2.local (unknown [IPv6:2001:df9:0:4017:e42c:c034:61ed:fff8]) by mail.lacnic.net.uy (Postfix) with ESMTP id E3465308424; Mon, 25 Feb 2013 04:56:31 -0200 (UYST)
Message-ID: <512B0B20.2000403@lacnic.net>
Date: Mon, 25 Feb 2013 14:56:32 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <512B0A2D.3050102@acm.org>
In-Reply-To: <512B0A2D.3050102@acm.org>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 25 Feb 2013 06:57:05 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


	Yes, I correct, I meant to outreach and not collaborate.

	If it were to collaborate, an ietf application with open standards
should be the way forward.

	For outreach my opinion is that does not matter.

Regards,
as

On 25/02/2013 14:52, Marc Petit-Huguenin wrote:
> On 02/24/2013 05:21 PM, Arturo Servin wrote:
> 
>> Why not?
> 
>> I, my organization and many more (included ISOC) have found them
>> very useful for outreach activities. I do not see why the IETF
>> shouldn't. Please, tell me.
> 
> You said collaborate below, now you are saying outreach.  What I
> said was specifically about collaboration.
> 
> 
> 
>> as
> 
>> Sent from my iPad
> 
>> On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org>
>> wrote:
> 
>> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>>>> 
>>>>> Very good initiative.
>>>>> 
>>>>> Twitter, Google+, Facebook, etc. could be the next steps.
>>>>> Let's embrace new tools to collaborate.
> 
>> Let's not.  Collaboration based on software running on servers
>> run by the IETF or a contractor payed by the IETF is fine.  Using
>> collaboration tools owned by the entities you listed, or similar
>> entities, is not.
> 
>>>>> 
>>>>> Regards, as
>>>>> 
>>>>> On 22/02/2013 20:35, IETF Chair wrote:
>>>>>> Jari has created a blog as an experiment to see if would
>>>>>> be possible to provide periodic status reports and other
>>>>>> thoughts from the chair. Here's the link:
>>>>>> 
>>>>>> http://www.ietf.org/blog/2013/02/chairs-blog/
> 
> 
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlErCx8ACgkQr8mvgVZWPgmfCQD/dupspw+Jh/PB7E+wHEALBSyJ
EOJA8t63U+NkFZgv7GcA/jwXf6NQuPajpCGiERB/zsqJJiy3jurIIC17Ofv1/yZM
=N8V+
-----END PGP SIGNATURE-----

From aservin@lacnic.net  Sun Feb 24 23:00:00 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5257E21F91F5 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:00:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNi6TEPLpnZT for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 22:59:59 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 3B8C121F91ED for <ietf@ietf.org>; Sun, 24 Feb 2013 22:59:59 -0800 (PST)
Received: from minir2d2.local (unknown [IPv6:2001:df9:0:4017:e42c:c034:61ed:fff8]) by mail.lacnic.net.uy (Postfix) with ESMTP id DD451308424; Mon, 25 Feb 2013 04:59:40 -0200 (UYST)
Message-ID: <512B0BDE.8060700@lacnic.net>
Date: Mon, 25 Feb 2013 14:59:42 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Brian Trammell <trammell@tik.ee.ethz.ch>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch>
In-Reply-To: <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 25 Feb 2013 07:00:00 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


	I meant outreach, not collaborate.

	In the case of collaboration I agree with you. Although today we use
webex that does not seem to open to me (at least not more than FB,
Google+ and twitter).

	In the case of outreach it does not matter to me if we are using
closed or open applications.

/as

On 25/02/2013 14:52, Brian Trammell wrote:
> Hi, Arturo, all,
> 
> It does not seem appropriate for a technical standards organization
> dedicated to making the Internet work better through the
> development of open standards to implicitly endorse "communication
> protocols" which are based on closed access to distributed
> databases through interfaces that can and do change at the whim of
> the organizations that control them, further where those
> organizations have demonstrated a willingness to assert editorial
> control over the content they disseminate.
> 
> If a social network were to emerge that allows open participation
> at _every_ level, based on an open application protocol therefor,
> that would be something different. I fear that network effects have
> already made  such a thing unlikely in this iteration of "Internet
> x.0".
> 
> (Aside: I myself have used all three listed networks to get
> attention for ISOC functions at the chapter level, though I'm
> uneasy about that. I won't dispute that they're great for outreach,
> and when you're doing outreach, you have to go where the people
> are. In my defense, though, I was advertising a talk wherein I
> discussed why it's a bad idea to rely on such closed platforms. :)
> )
> 
> Cheers,
> 
> Brian
> 
> On Feb 25, 2013, at 2:21 AM, Arturo Servin <aservin@lacnic.net>
> wrote:
> 
>> 
>> Why not?
>> 
>> I, my organization and many more (included ISOC) have found them
>> very useful for outreach activities. I do not see why the IETF
>> shouldn't. Please, tell me.
>> 
>> 
>> as
>> 
>> Sent from my iPad
>> 
>> On 25 Feb 2013, at 02:21, Marc Petit-Huguenin <petithug@acm.org>
>> wrote:
>> 
> On 02/23/2013 07:38 PM, Arturo Servin wrote:
>>>>> 
>>>>> Very good initiative.
>>>>> 
>>>>> Twitter, Google+, Facebook, etc. could be the next steps.
>>>>> Let's embrace new tools to collaborate.
> 
> Let's not.  Collaboration based on software running on servers run
> by the IETF or a contractor payed by the IETF is fine.  Using
> collaboration tools owned by the entities you listed, or similar
> entities, is not.
> 
>>>>> 
>>>>> Regards, as
>>>>> 
>>>>> On 22/02/2013 20:35, IETF Chair wrote:
>>>>>> Jari has created a blog as an experiment to see if would
>>>>>> be possible to provide periodic status reports and other
>>>>>> thoughts from the chair. Here's the link:
>>>>>> 
>>>>>> http://www.ietf.org/blog/2013/02/chairs-blog/
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlErC94ACgkQr8mvgVZWPglc7wD/ZpaDDjPL8QYgcZrQH0xX+KD/
WOypj8I57wHOnJcfGNcA/jErGblgtaJuhgde5og6u5SE80bqmJBqcyxXfxUv/WOK
=37Ql
-----END PGP SIGNATURE-----

From sustrik@250bpm.com  Sun Feb 24 23:02:29 2013
Return-Path: <sustrik@250bpm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4CA721F91F4 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.694
X-Spam-Level: 
X-Spam-Status: No, score=-0.694 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SK=1.35, HOST_EQ_SK=0.555]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2zg130v3G7N for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:02:24 -0800 (PST)
Received: from mail.moloch.sk (chrocht.moloch.sk [62.176.169.44]) by ietfa.amsl.com (Postfix) with ESMTP id 492EB21F91F9 for <ietf@ietf.org>; Sun, 24 Feb 2013 23:02:24 -0800 (PST)
Received: from [192.168.1.134] (188-167-109-79.dynamic.chello.sk [188.167.109.79]) by mail.moloch.sk (Postfix) with ESMTPSA id AEF7A1802020; Mon, 25 Feb 2013 08:02:22 +0100 (CET)
Message-ID: <512B0C7E.5010900@250bpm.com>
Date: Mon, 25 Feb 2013 08:02:22 +0100
From: Martin Sustrik <sustrik@250bpm.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Thunderbird/3.1.16
MIME-Version: 1.0
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>	<8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>	<512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net>
In-Reply-To: <512B0B20.2000403@lacnic.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 07:02:30 -0000

On 25/02/13 07:56, Arturo Servin wrote:

> 	If it were to collaborate, an ietf application with open standards
> should be the way forward.

Moreover, entities controlling these social platforms are, presumably, 
also participating in IETF. So, using these tools would give one party 
unfair advantage -- ability to promote or obscure individual 
discussions/threads/posts, ban users etc.

Martin

From fred@cisco.com  Sun Feb 24 23:05:42 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2164C21F91FF for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.495
X-Spam-Level: 
X-Spam-Status: No, score=-110.495 tagged_above=-999 required=5 tests=[AWL=0.104, 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 cZnbyp0sF8AA for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:05:41 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4D05D21F91F4 for <ietf@ietf.org>; Sun, 24 Feb 2013 23:05:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1568; q=dns/txt; s=iport; t=1361775941; x=1362985541; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=FV4+T41SCIVHmhKTXmJW6ChiJFF1ujhbJnp+ZMyLp0k=; b=UcBcxkyVvFxOk626pia92iE51EaK1Ccfr/I5Y3n2O+gY+zUDjqeuZFhz fDbJFyic/2jZVF6Qo8Huibcbk+0eJli1ntDhpuyw+SPeC94JsNs3YYl/j G2gKUnQMO9NJjfk+uiJjQIcFin77vXg07NofDvJ+v5NBvpmr5JAUymWwT c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAHwMK1GtJV2b/2dsb2JhbABFwVKBDRZzgh8BAQEDATo/EAIBCA4UFBAyJQIEDg0Mh3kGvT+OWwIxB4JfYQOQS5ZXgweCJw
X-IronPort-AV: E=Sophos;i="4.84,732,1355097600"; d="scan'208";a="180729634"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-4.cisco.com with ESMTP; 25 Feb 2013 07:05:41 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1P75eYD005346 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Feb 2013 07:05:40 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 01:05:40 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Arturo Servin <aservin@lacnic.net>
Subject: Re: IETF chair's blog
Thread-Topic: IETF chair's blog
Thread-Index: AQHOEPkYCmF/o8dPakGrSc5fI35y8piIw1kAgAD2swCAANWfgA==
Date: Mon, 25 Feb 2013 07:05:40 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>
In-Reply-To: <512A5A10.4090406@acm.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.119]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6301A5256CF55A4CA580A6357AEB4CDF@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 07:05:42 -0000

>> Twitter, Google+, Facebook, etc. could be the next steps. Let's embrace =
new
>> tools to collaborate.
>=20
> Let's not.  Collaboration based on software running on servers run by the=
 IETF
> or a contractor payed by the IETF is fine.  Using collaboration tools own=
ed by
> the entities you listed, or similar entities, is not.

I'm of two opinions here. One, I agree with Marc that the case has not been=
 made for the use of proprietary technologies such as you mention; we actua=
lly do pretty well, and the ultimate issue is about effective communication=
 with all of the relevant participants, not with those few that use a given=
 social networking service (I, for example, use Facebook, but not twitter a=
nd not google+, and have specific reasons for my choices there). On the oth=
er hand, experiments involving other technologies (we have, for example, ex=
perimented with .ps, .pdf, .xml, jabber, and RFID badges) should not be out=
 of bounds. Experiments should follow IETF experimental procedure.

Arturo, my suggestion: in some context, after discussion with the working-g=
roup-or-whatever-in-question, use one of the tools you mention to accomplis=
h IETF work. Take careful notes of what proportion of the indicated communi=
ty (if the IPv6 Operations WG, for example, the participants in v6ops) join=
 the discussions, and what contribution those discussions make. Think about=
 archives, focused issue discussion (what SMTP readers call "threads"), and=
 so on. Then write a draft documenting the outcome of that.=

From petithug@acm.org  Sun Feb 24 23:10:27 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880CC21F9200 for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:10:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.557
X-Spam-Level: 
X-Spam-Status: No, score=-102.557 tagged_above=-999 required=5 tests=[AWL=0.043, 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 MSBI0ZZymU5c for <ietf@ietfa.amsl.com>; Sun, 24 Feb 2013 23:10:26 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id BED4F21F91F4 for <ietf@ietf.org>; Sun, 24 Feb 2013 23:10:26 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902] (unknown [IPv6:2601:9:4b80:32:44a7:dd23:2fef:6902]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id B653420515; Mon, 25 Feb 2013 07:10:25 +0000 (UTC)
Message-ID: <512B0E64.2030101@acm.org>
Date: Sun, 24 Feb 2013 23:10:28 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Martin Sustrik <sustrik@250bpm.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>	<8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>	<512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com>
In-Reply-To: <512B0C7E.5010900@250bpm.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 07:10:27 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/24/2013 11:02 PM, Martin Sustrik wrote:
> On 25/02/13 07:56, Arturo Servin wrote:
> 
>> If it were to collaborate, an ietf application with open standards should
>> be the way forward.
> 
> Moreover, entities controlling these social platforms are, presumably,
> also participating in IETF. So, using these tools would give one party
> unfair advantage -- ability to promote or obscure individual
> discussions/threads/posts, ban users etc.

Exactly.  And it bothers me that we are not making much progress in having our
own remote participant service and have to rely on Webex.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRKw5bAAoJECnERZXWan7ESloQAIbg7xr93BwSjH8cNheN5zBg
CVmoXV7ZqQdzQgZfHDjjwTBk3KSm6y99lzjyMQX3t/tqKWnqJH4jG7dVbtyGHAU8
+Q5j04tVaJ8S+fShS1SIJ5ySu+vjpTMF932++GkMWVsqklJw/hGDekH63dRdD7cK
k2cQ4rcakHhx8n8rfA/JKRh+bwCN65GJH0+4E/SSf1RQmuYOhIp69lMeAJmb4t/d
kT25XVkvuJlkqVfh3klZf+UwcV6sOnWaxYHsk+JA1K/dr3sAIFLAcju50AaRNgHa
dchB1FvNMt373CBec5qk6qJ06qrKugq9KZsgnHxYR0YnyM6tVrcD1Mq/eHuVPlW9
SXAlqtEnVBAXoVvNdAMyccrv7i9L/HcHwrsYfUsUmOy3X/PWj1IfNRY6cqyvt6C8
p72KZTXeitg1pVKFd8PKVgmSPg1C2vO2uji7cpCqPY5JcwoVGOuEVNN4aoXkgvAT
TsD5gm/uQCVI90/g/XGVeth6zGmShbXxsLHfZ4LCDdCEuc0NTOvB119tVw2kpSXT
akmyi5Kl777BUz5x3WUoL4RlbeK6kpFaM7kAW7Uy3lzGnu2+IvwwJQqamhcqLQcv
fngKTC2COHJo+6Wb19/Kpg6wlQG82NTBczlHlPyjeeyG3ZIVdrWs7UA/zX/E+vNc
mziqVf91EVS9WzLE/nK+
=2NJB
-----END PGP SIGNATURE-----

From brian.e.carpenter@gmail.com  Mon Feb 25 00:20:13 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECED721F91D1 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.744
X-Spam-Level: 
X-Spam-Status: No, score=-99.744 tagged_above=-999 required=5 tests=[AWL=-0.823, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qb0WWzc6bV2a for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:20:12 -0800 (PST)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id C3B5221F91B3 for <ietf@ietf.org>; Mon, 25 Feb 2013 00:20:11 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id l13so4250657wie.4 for <ietf@ietf.org>; Mon, 25 Feb 2013 00:20:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lgV0krjRtcfIfjbyr0zq+j3b9L3rkJ0XXCa1dFLszLc=; b=uFfDsuW7Oq72HkAq8iblyj86BugFiteQM/h+7j55QDYw4Q32fa96lSDCpU8rtOPMyf pj93Uf2E4puUEs4r0e8JDzlYc5sTOq3FkhVX1Aj1ZGa0soIkhQTSS9UrGJpwsN51G1sc YE7Nx7uUbvj+xAf1SeKoLabiZf7rV0Auow5OHTSabWDIbTj76UK02yq2X+qZ3WlEOri9 6LFXJAJbrBt+76G437osyfdwA1RcB1VgNBSPdStK41OBxmIXqJ7HlBlQZsRxFau+Cai6 p9Ah5VAwSC9PRp7v0FOY8B+ytqQ2FvdaOYVsd+PY5JOGEEf+7mfJGTtr3Y29DApi+jA2 MzSg==
X-Received: by 10.180.94.135 with SMTP id dc7mr10300250wib.11.1361780410302; Mon, 25 Feb 2013 00:20:10 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-89.as13285.net. [2.102.217.89]) by mx.google.com with ESMTPS id du2sm13371889wib.0.2013.02.25.00.20.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Feb 2013 00:20:09 -0800 (PST)
Message-ID: <512B1EBA.30507@gmail.com>
Date: Mon, 25 Feb 2013 08:20:10 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 08:20:13 -0000

Fred,

On 25/02/2013 07:05, Fred Baker (fred) wrote:
>>> Twitter, Google+, Facebook, etc. could be the next steps.
>>> Let's embrace new tools to collaborate.
>> Let's not.  Collaboration based on software running on
>> servers run by the IETF or a contractor payed by the IETF
>> is fine.  Using collaboration tools owned by the entities
>> you listed, or similar entities, is not.
> 
> I'm of two opinions here. One, I agree with Marc that the
> case has not been made for the use of proprietary
> technologies such as you mention; we actually do pretty well,
> and the ultimate issue is about effective communication with
> all of the relevant participants, not with those few that use
> a given social networking service 

Exactly. The inter-personal communication toolset we use in the
IETF is quite limited because of some unwritten constraints,
which certainly include:

- very widely available, including free or open source solutions
- operating-system independent
- standardised, non-proprietary
- not unduly plagued by advertising
- preferably, standardised by the IETF itself
- most tools allow time-shifting for worldwide collaboration
- reasonably secure
- do not damage privacy but do not encourage anonymity

I think we have to be very careful going outside that set
of constraints (which is why I'm not a big fan of Webex or for
that matter Meetecho).

...
> Arturo, my suggestion: in some context, after discussion with
> the working-group-or-whatever-in-question, use one of the
> tools you mention to accomplish IETF work. Take careful notes
> of what proportion of the indicated community (if the IPv6
> Operations WG, for example, the participants in v6ops) join
> the discussions, and what contribution those discussions
> make. Think about archives, 

s/archives/public archives/

focused issue discussion (what
> SMTP readers call "threads"), and so on. Then write a draft
> documenting the outcome of that.

Yes

    Brian

From aservin@lacnic.net  Mon Feb 25 00:49:08 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69BD021F91D5 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:49:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bx94VnE41TuX for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 00:49:08 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id D099221F91B0 for <ietf@ietf.org>; Mon, 25 Feb 2013 00:49:07 -0800 (PST)
Received: from MiniR2D2.local (unknown [IPv6:2001:df9:0:4022:801e:caa:204d:5dbb]) by mail.lacnic.net.uy (Postfix) with ESMTP id DE237308469; Mon, 25 Feb 2013 06:48:57 -0200 (UYST)
Message-ID: <512B257A.3030902@lacnic.net>
Date: Mon, 25 Feb 2013 16:48:58 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
In-Reply-To: <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 25 Feb 2013 08:49:08 -0000

Fred,

	I am not convinced that social nets (proprietary or not) are yet a good
tool to do IETF work. They are good to communicate one-way and some
informal two-ways, but that's all (at least for now)

	What I had in mind was something very simple such that the IETF chair
could do is to automatically post to twitter, facebook, etc whenever
there is a new post from his blog and receive from communication using
those tools (besides the comments in the blog). But that is all.
	
	About using an open social net approach	I think there could be some
value but not sure if we are there yet, I will give it some thoughts
anyhow and how it could be done.

Regard,
as

On 25/02/2013 15:05, Fred Baker (fred) wrote:
> Arturo, my suggestion: in some context, after discussion with the working-group-or-whatever-in-question, use one of the tools you mention to accomplish IETF work. Take careful notes of what proportion of the indicated community (if the IPv6 Operations WG, for example, the participants in v6ops) join the discussions, and what contribution those discussions make. Think about archives, focused issue discussion (what SMTP readers call "threads"), and so on. Then write a draft documenting the outcome of that.

From Michael.Tuexen@lurchi.franken.de  Mon Feb 25 03:11:27 2013
Return-Path: <Michael.Tuexen@lurchi.franken.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 5EBCD21F9273 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 03:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jwgfwbkshy1A for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 03:11:26 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id 514FB21F89F9 for <ietf@ietf.org>; Mon, 25 Feb 2013 03:11:26 -0800 (PST)
Received: from [192.168.1.101] (p5481BC8E.dip.t-dialin.net [84.129.188.142]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 92D281C0C069D; Mon, 25 Feb 2013 12:11:23 +0100 (CET)
Subject: Re: IETF chair's blog
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <512B0E64.2030101@acm.org>
Date: Mon, 25 Feb 2013 12:11:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>	<8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>	<512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org>
To: Marc Petit-Huguenin <petithug@acm.org>
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, 25 Feb 2013 11:11:27 -0000

On Feb 25, 2013, at 8:10 AM, Marc Petit-Huguenin wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>=20
> On 02/24/2013 11:02 PM, Martin Sustrik wrote:
>> On 25/02/13 07:56, Arturo Servin wrote:
>>=20
>>> If it were to collaborate, an ietf application with open standards =
should
>>> be the way forward.
>>=20
>> Moreover, entities controlling these social platforms are, =
presumably,
>> also participating in IETF. So, using these tools would give one =
party
>> unfair advantage -- ability to promote or obscure individual
>> discussions/threads/posts, ban users etc.
>=20
> Exactly.  And it bothers me that we are not making much progress in =
having our
> own remote participant service and have to rely on Webex.
Couldn't we use one based on RTCWeb (in the near future)?

Best regards
Michael
>=20
> - --=20
> Marc Petit-Huguenin
> Email: marc@petit-huguenin.org
> Blog: http://blog.marc.petit-huguenin.org
> Profile: http://www.linkedin.com/in/petithug
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>=20
> iQIcBAEBCAAGBQJRKw5bAAoJECnERZXWan7ESloQAIbg7xr93BwSjH8cNheN5zBg
> CVmoXV7ZqQdzQgZfHDjjwTBk3KSm6y99lzjyMQX3t/tqKWnqJH4jG7dVbtyGHAU8
> +Q5j04tVaJ8S+fShS1SIJ5ySu+vjpTMF932++GkMWVsqklJw/hGDekH63dRdD7cK
> k2cQ4rcakHhx8n8rfA/JKRh+bwCN65GJH0+4E/SSf1RQmuYOhIp69lMeAJmb4t/d
> kT25XVkvuJlkqVfh3klZf+UwcV6sOnWaxYHsk+JA1K/dr3sAIFLAcju50AaRNgHa
> dchB1FvNMt373CBec5qk6qJ06qrKugq9KZsgnHxYR0YnyM6tVrcD1Mq/eHuVPlW9
> SXAlqtEnVBAXoVvNdAMyccrv7i9L/HcHwrsYfUsUmOy3X/PWj1IfNRY6cqyvt6C8
> p72KZTXeitg1pVKFd8PKVgmSPg1C2vO2uji7cpCqPY5JcwoVGOuEVNN4aoXkgvAT
> TsD5gm/uQCVI90/g/XGVeth6zGmShbXxsLHfZ4LCDdCEuc0NTOvB119tVw2kpSXT
> akmyi5Kl777BUz5x3WUoL4RlbeK6kpFaM7kAW7Uy3lzGnu2+IvwwJQqamhcqLQcv
> fngKTC2COHJo+6Wb19/Kpg6wlQG82NTBczlHlPyjeeyG3ZIVdrWs7UA/zX/E+vNc
> mziqVf91EVS9WzLE/nK+
> =3D2NJB
> -----END PGP SIGNATURE-----
>=20


From spromano@unina.it  Mon Feb 25 03:15:37 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5B621F9275 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 03:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4N7lraMAZ2u for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 03:15:37 -0800 (PST)
Received: from relay1.tre.it (mail.tre.it [62.13.171.46]) by ietfa.amsl.com (Postfix) with ESMTP id 6DF1F21F9274 for <ietf@ietf.org>; Mon, 25 Feb 2013 03:15:36 -0800 (PST)
Received: from [192.168.1.101] ([10.86.2.134]) by relay1.tre.it  with ESMTP id r1PBFUis004059-r1PBFUit004059; Mon, 25 Feb 2013 12:15:30 +0100
Subject: Re: IETF chair's blog
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F9A9E6A5-A115-415B-930F-30F95D0DF293"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <512B1EBA.30507@gmail.com>
Date: Mon, 25 Feb 2013 12:15:39 +0100
Message-Id: <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.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, 25 Feb 2013 11:15:37 -0000

--Apple-Mail=_F9A9E6A5-A115-415B-930F-30F95D0DF293
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi  Brian,

> Exactly. The inter-personal communication toolset we use in the
> IETF is quite limited because of some unwritten constraints,
> which certainly include:
>=20
> - very widely available, including free or open source solutions
> - operating-system independent
> - standardised, non-proprietary
> - not unduly plagued by advertising
> - preferably, standardised by the IETF itself
> - most tools allow time-shifting for worldwide collaboration
> - reasonably secure
> - do not damage privacy but do not encourage anonymity
>=20
> I think we have to be very careful going outside that set
> of constraints (which is why I'm not a big fan of Webex or for
> that matter Meetecho).

Just out of curiosity, can you list which of the above requirements is =
not met by Meetecho?

Thanks,

Simon


                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_F9A9E6A5-A115-415B-930F-30F95D0DF293
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
&nbsp;Brian,<div><br></div><div><div><blockquote =
type=3D"cite"><div>Exactly. The inter-personal communication toolset we =
use in the<br>IETF is quite limited because of some unwritten =
constraints,<br>which certainly include:<br><br>- very widely available, =
including free or open source solutions<br>- operating-system =
independent<br>- standardised, non-proprietary<br>- not unduly plagued =
by advertising<br>- preferably, standardised by the IETF itself<br>- =
most tools allow time-shifting for worldwide collaboration<br>- =
reasonably secure<br>- do not damage privacy but do not encourage =
anonymity<br><br>I think we have to be very careful going outside that =
set<br>of constraints (which is why I'm not a big fan of Webex or =
for<br>that matter Meetecho).<br></div></blockquote><div><br></div>Just =
out of curiosity, can you list which of the above requirements is not =
met by =
Meetecho?</div><div><br></div><div>Thanks,</div><div><br></div><div>Simon<=
br><div><br></div></div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_F9A9E6A5-A115-415B-930F-30F95D0DF293--

From brian.e.carpenter@gmail.com  Mon Feb 25 06:28:07 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE90721F91DF for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 06:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.731
X-Spam-Level: 
X-Spam-Status: No, score=-99.731 tagged_above=-999 required=5 tests=[AWL=-0.810, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X956i6BX2RU7 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 06:28:07 -0800 (PST)
Received: from mail-we0-x22c.google.com (we-in-x022c.1e100.net [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id F23B221F91D9 for <ietf@ietf.org>; Mon, 25 Feb 2013 06:28:06 -0800 (PST)
Received: by mail-we0-f172.google.com with SMTP id x10so2559025wey.17 for <ietf@ietf.org>; Mon, 25 Feb 2013 06:28:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/8xdn4/Lz6Hi0GpEFxM+O37socvUOB+GGEKO6OMXoTg=; b=iSBts+2YvQ5Ot6szE6+OuYzBqRX5oyhKsaMV2/LQnfCCSYYF3sBfqis3PEmgE532Qq L0wKpOuy09+jl6p9220OUUVnvfPMjzAADOFiOLKtOdJO8Ir0v0YPzlJLkpw5pyiGTyQt NGt8meoSZXpTclQNOlOPry7HKOKUOxHyHhAJt563CVmi+fkZ8X1uP8f9aIeovylvQarl ALh3zN80XAfPikqOHcFzt9EW3L5J3wWNicTAtIVh8EpQQihF60DQ4eTj9tZuqm3pNFAQ ux0IxT7EBlYRMgzuM1sKaZ2DkVzRBwxZDIaIU8uQnxfQRpaa1O7TIbuPNKIT4XeoJn2m G70A==
X-Received: by 10.181.12.103 with SMTP id ep7mr12548395wid.12.1361802486118; Mon, 25 Feb 2013 06:28:06 -0800 (PST)
Received: from [192.168.1.65] (host-2-102-217-89.as13285.net. [2.102.217.89]) by mx.google.com with ESMTPS id o8sm15233377wix.7.2013.02.25.06.28.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Feb 2013 06:28:05 -0800 (PST)
Message-ID: <512B74F7.5060506@gmail.com>
Date: Mon, 25 Feb 2013 14:28:07 +0000
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: Simon Pietro Romano <spromano@unina.it>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
In-Reply-To: <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 14:28:07 -0000

Hi Simon,

On 25/02/2013 11:15, Simon Pietro Romano wrote:
> Hi  Brian,
> 
>> Exactly. The inter-personal communication toolset we use in the
>> IETF is quite limited because of some unwritten constraints,
>> which certainly include:
>>
>> - very widely available, including free or open source solutions
>> - operating-system independent
>> - standardised, non-proprietary
>> - not unduly plagued by advertising
>> - preferably, standardised by the IETF itself
>> - most tools allow time-shifting for worldwide collaboration
>> - reasonably secure
>> - do not damage privacy but do not encourage anonymity
>>
>> I think we have to be very careful going outside that set
>> of constraints (which is why I'm not a big fan of Webex or for
>> that matter Meetecho).
> 
> Just out of curiosity, can you list which of the above requirements is not met by Meetecho?

It's proprietary, isn't it? The pop-ups on the the web site don't seem to
work for me, but I can see a Buy button. (I realise that usage for the IETF
is free, and I have no complaints.) Not sure about the standards status.

Anyway - if we want to move forward in an agreed way, I do think we
need a list of criteria. I forgot "reliable" BTW.

Maybe this conversation belongs on tools-discuss@ietf.org.

    Brian

From petithug@acm.org  Mon Feb 25 07:25:53 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A177321F9475 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 07:25:53 -0800 (PST)
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.040, 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 ptHTKt52cYqS for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 07:25:52 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 93E1A21F947D for <ietf@ietf.org>; Mon, 25 Feb 2013 07:25:51 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476] (unknown [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 8A7A220515; Mon, 25 Feb 2013 15:25:49 +0000 (UTC)
Message-ID: <512B827F.4060406@acm.org>
Date: Mon, 25 Feb 2013 07:25:51 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org>	<8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net>	<512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org> <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de>
In-Reply-To: <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 15:25:53 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/25/2013 03:11 AM, Michael Tuexen wrote:
> On Feb 25, 2013, at 8:10 AM, Marc Petit-Huguenin wrote:
> 
> On 02/24/2013 11:02 PM, Martin Sustrik wrote:
>>>> On 25/02/13 07:56, Arturo Servin wrote:
>>>> 
>>>>> If it were to collaborate, an ietf application with open standards
>>>>> should be the way forward.
>>>> 
>>>> Moreover, entities controlling these social platforms are,
>>>> presumably, also participating in IETF. So, using these tools would
>>>> give one party unfair advantage -- ability to promote or obscure
>>>> individual discussions/threads/posts, ban users etc.
> 
> Exactly.  And it bothers me that we are not making much progress in having
> our own remote participant service and have to rely on Webex.
>> Couldn't we use one based on RTCWeb (in the near future)?

Why not, but it's just technology.  For me the most important point is that it
is managed on IETF (or IETF's contractor) servers.  By that criteria a private
license of Webex running on IETF's servers is better than the far more open
Meetecho running somewhere else (but if both where running on IETF servers,
open software is better than close software).

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRK4J8AAoJECnERZXWan7ELnMQALBhuasu/c1TmdHeIg8QNhuS
kW1rgn/mMzYWp8myFacRggl3fPsslNmOXoCvdNE0e8FLETR0CmtqTsekhOB7Tg95
zmzffM5BG/b8iJjhemacPnA9nLSpXlAJal47b9elY2f+hytERAuLNmJBdUx2dy4y
T8x+EVeR4n+NAGAoesISzRsx9c7m/BOiJZJMDjIbyVcjnPpZ3i38WzUqUHK+XX1C
fwoCkjPrQ5owcSeJxR9tMdzVngqxoDgZMfdTT4b/ECa3wu1fHlPN7Ggx8y3/+m6V
EGnSBZIeYqkBaQ3WL1ehVoMWDyNlCOUYVCTd3ircjjNY9C/Aqu7NrhxwsjeMatEI
fMQ2HniB19fE/BVsuIgWL6mZksQ7whK/KMKwfvGEHV2X0coHDLokr8pee0nZXFYu
7K/+qYxOUc/jSqyoXScDOVmS7uoAZDvZgKgtfNGyHiPPVc9Gc4BI8nwrtiRdkTkE
AGtx8EmgJC5D5fM/i1ddjwoMuJ8Iy1oeMIIilWQOeLV0sNSrh7sBzBrTirV4TWzc
L4NAh6b36nkx6ckumtLHV7xrfsHv+VngL/lE+hvIHQ8hhnEh5JkIJLqisbMZRunY
tFOWJ9O5f0xv8bXwTppU30QiRGXJV2OeglrMUgPcQN173ymQToh4SsiiZ2vWaiF3
OF3fBZI4ADLgdFODNbQY
=MOA/
-----END PGP SIGNATURE-----

From alejandroacostaalamo@gmail.com  Mon Feb 25 07:31:53 2013
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0299B21F9483 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 07:31:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rw0hu+hM4fo3 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 07:31:52 -0800 (PST)
Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) by ietfa.amsl.com (Postfix) with ESMTP id 7599221F9472 for <ietf@ietf.org>; Mon, 25 Feb 2013 07:31:52 -0800 (PST)
Received: by mail-ve0-f175.google.com with SMTP id cy12so2246312veb.20 for <ietf@ietf.org>; Mon, 25 Feb 2013 07:31:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=gYfhdtraCE0bfpM3/22fn2ujIiJDGIKFTg+yA+6UuNg=; b=n/TQhWgCltTEBnG+iYVk1A6VPqVO1HS+zmPoxUg7VpeuYiJQdxuFPYmtutZ7khx1jl DIErLtmSSjnlUJN+e39f+gtxJcFRBNGKQKYL8OX330SjphzI81vbpvQHSRzvcIk1pRay MLfdUdM819HGfsBWLT2uHoBCftjfAWMCz+dZ8XzFCYH/BK512Jan7Fi38WxpkGiZrAv5 D2YRdwCYYwKFN4ViTmizZNbFaIpBkCkhd+loVt7liqQJNxiClpSndx2/j7t1q1QtzeG6 clvStoraLg8/SqCPMEXkATXeCsPn254ewTCldhG/QNZhajED2XualzBsp2TZN2fxKjIF o2Jg==
MIME-Version: 1.0
X-Received: by 10.52.175.130 with SMTP id ca2mr8884660vdc.109.1361806311909; Mon, 25 Feb 2013 07:31:51 -0800 (PST)
Received: by 10.220.179.72 with HTTP; Mon, 25 Feb 2013 07:31:51 -0800 (PST)
In-Reply-To: <512B257A.3030902@lacnic.net>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B257A.3030902@lacnic.net>
Date: Mon, 25 Feb 2013 11:01:51 -0430
Message-ID: <CAOmxzdzxNejS_D3wHm_rPHBmAYZDXVK5odhP2ge057NQRu2mWw@mail.gmail.com>
Subject: Re: IETF chair's blog
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Arturo Servin <aservin@lacnic.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 15:31:53 -0000

On 2/25/13, Arturo Servin <aservin@lacnic.net> wrote:
> Fred,
>
> 	I am not convinced that social nets (proprietary or not) are yet a good
> tool to do IETF work. They are good to communicate one-way and some
> informal two-ways, but that's all (at least for now)
>
> 	What I had in mind was something very simple such that the IETF chair
> could do is to automatically post to twitter, facebook, etc whenever
> there is a new post from his blog and receive from communication using
> those tools (besides the comments in the blog). But that is all.

This scenario sounds good for me.  Of course this is not a
substitution of the mailing list, this is complementary. It's nice to
receive a tweet with the subject of the blog post and the URL to click
on it.

Some time ago in this mailing list we were discussing that the average
age of IETF is getting old (of course, there are many exceptions). Did
you know that young people do not use email as much as us?. Saying
that, this can be a good way to bring young people to IETF.

Alejandro Acosta,


{...}

From worley@shell01.TheWorld.com  Mon Feb 25 08:00:10 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1510C21F92A0 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:00:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[AWL=0.259,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3F34GWAbEYC for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:00:08 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id 115F421F94E1 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:00:02 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1PFxPsJ008965 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:59:27 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1PFxO6o2601616 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:59:25 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1PFxOpb2603069; Mon, 25 Feb 2013 10:59:24 -0500 (EST)
Date: Mon, 25 Feb 2013 10:59:24 -0500 (EST)
Message-Id: <201302251559.r1PFxOpb2603069@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.ch> (trammell@tik.ee.ethz.ch)
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <959ECB50-4DFE-4A66-81DB-36EF64BF5971@tik.ee.ethz.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, 25 Feb 2013 16:00:10 -0000

> From: Brian Trammell <trammell@tik.ee.ethz.ch>
> 
> It does not seem appropriate for a technical standards organization
> dedicated to making the Internet work better through the development
> of open standards to implicitly endorse "communication protocols"
> which are based on closed access to distributed databases through
> interfaces that can and do change at the whim of the organizations
> that control them, further where those organizations have
> demonstrated a willingness to assert editorial control over the
> content they disseminate.

First, let me add my cynical definitions:

    "Collaborate" is when I listen to you.

    "Public relations" is when *you* listen to *me*.

Let us use these terms correctly (as opposed to most usage in the
business world).

In regard to "platforms", I'm torn, because the current crop of
commercial social media is a good technique of doing PR and no doubt
would help the IETF generate public awareness.  On the other hand,
having a major sector of social interaction be operated on a
completely closed platform operated by an organization with completely
commercial purposes is *exactly the opposite* of what the IETF is
attempting to accomplish.

Dale

From worley@shell01.TheWorld.com  Mon Feb 25 08:01:14 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26D8321F9508 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:01:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level: 
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FMGXp+ixvQbF for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:01:12 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFB021F9503 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:01:12 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1PG0gPi028882; Mon, 25 Feb 2013 11:00:45 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1PG0dVF2600802; Mon, 25 Feb 2013 11:00:39 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1PG0YLR2598111; Mon, 25 Feb 2013 11:00:34 -0500 (EST)
Date: Mon, 25 Feb 2013 11:00:34 -0500 (EST)
Message-Id: <201302251600.r1PG0YLR2598111@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Randall Gellens <randy@qti.qualcomm.com>
In-reply-to: <p0624060bcd4e2914868a@[10.177.189.109]> (randy@qti.qualcomm.com)
Subject: Re: draft-gellens-negotiating-human-language-01
References: <20130222090937.665a7a7059d7ee80bb4d670165c8327d.ad3940b1cb.wbe@email0 3.secureserver.net> <p0624060bcd4e2914868a@[10.177.189.109]>
Cc: ietf-languages@iana.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 16:01:14 -0000

(It's not clear to me what the proper mailing list is to discuss this
draft.  From the headers of the messages, it appears that the primary
list is ietf@ietf.org, but the first message in this thread about that
draft already has a "Re:" in the subject line, so the discussion
started somewhere else.)

(Also, it's not clear why Randall's messages are coming through in
HTML.)

But onward to questions of substance:

- Why SDP and not SIP?

I'd like to see a more thorough exploration of why language
negotiation is to be handled in SDP rather than SIP.  (SIP, like HTTP,
uses the Content-Language header to specify languages.)  In principle,
specifying data that may be used in call-routing should be done in the
SIP layer, but it's well-accepted in the SIP world that call routing
may be affected by the SDP content as well (e.g., media types).

And some discussion and comparison should be done with the SIP/HTTP
Content-Language header (used to specify the language of the
communications) and the SIP Accept-Language header (used to specify
the language of text components of SIP messages), particularly given
that Accept-Language has different set of language specifiers and a
richer syntax for specifying preferences.  In any case, preference
should be given to reusing one of the existing syntaxes for specifying
language preferences.

- Dependency between media descriptions?

   Another example would be a user who is able to speak but is deaf or
   hard-of-hearing and requires a voice stream plus a text stream
   (known as voice carry over).  Making language a media attribute
   allows the standard session negotiation mechanism to handle this by
   providing the information and mechanism for the endpoints to make
   appropriate decisions.

This scenario suggests that there might be dependency or interaction
between language specifications for different media descriptions.
Whether this is needed should be determined and documented.

- Specifying preference levels?

   For example, some users may be able to speak several languages, but
   have a preference.

This might argue for describing degrees of preference using "q"
parameters (as in the SIP Accept-Language header).

- Expressing multiple languages in answers

   (While it is true that a conversation among multilingual people
   often involves multiple languages, it does not seem useful enough
   as a general facility to warrant complicating the desired semantics
   of the SDP attribute to allow negotiation of multiple simultaneous
   languages within an interactive media stream.)

Why shouldn't an answer be able to indicate multiple languages?  At
the least, this might provide the offerer with useful information.

- Reusing a=lang

Searching, I can only find these descriptions of the use of
"a=lang:...":

    RFC 4566
    draft-saintandre-sip-xmpp-chat
    draft-gellens-negotiating-human-language

So it looks like "a=lang:..." is entirely unused at the present and is
safe to be redefined.

Dale

From jari.arkko@piuha.net  Mon Feb 25 08:33:51 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9EB421F9370 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:33:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, 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 HPpPud2x+SDq for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:33:51 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 746CD21F94A2 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:33:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6584A2CC4A for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:47 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mr6PVzF5-Ttg for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:46 +0200 (EET)
Received: from www.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 3B48C2CC3B for <ietf@ietf.org>; Mon, 25 Feb 2013 18:33:46 +0200 (EET)
Received: from 114.123.150.111 (SquirrelMail authenticated user jarkko) by www.piuha.net with HTTP; Mon, 25 Feb 2013 18:33:46 +0200
Message-ID: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
In-Reply-To: <512B74F7.5060506@gmail.com>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com>
Date: Mon, 25 Feb 2013 18:33:46 +0200
Subject: Re: IETF chair's blog
From: jari.arkko@piuha.net
To: "ietf@ietf.org" <ietf@ietf.org>
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 16:33:52 -0000

Thanks everyone for the feedback, on and off list.

We did the blog primarily as a means to convey more thoughts and encourage
discussion. That's the content part. We'll see later how that works out.

The medium part is orthogonal, but interesting. For this stage we thought
that an IETF-server based web system would work nicely, even if we could
have done all on pure e-mail mode as well. I do have a question mark on
how to handle comments, however. It seems that open blog commentary on web
system will invite plenty of spam, so where does that leave us? Ask for
comments to be sent on this list, i.e., e-mail commentary? We seem to be
in that mode already... Or should we implement some specific spam
protection scheme that will save me and the secretariat from manual work
in checking postings? A tools-login required for posting comments? Or
something else, what?

Going further, you asked about social media and material on external
systems. This is not on the agenda for the current blog experiment (except
in a small way, see below). But it is something that we should find an
answer to eventually.

I am of the opinion that long-term, the IETF can not stay away from the
collaboration and discussion tools that majority of the Internet users are
using, including social media. But we need to control how this happens,
and I do worry about being able to own our own content and providing
everyone an equal access to it. I'd like to make a separation between
spreading information from the IETF across multiple media, hosting that
information in the external medium, and making an external medium the only
way to participate. I think we should stay away from the latter two
approaches. But the first one is benign, I think. As an example, we were
planning to send out a tweet from the IETF tweeter account about the
creation of the blog, with an URL back to the IETF site. (If I had even
the beginnings of an Internet connection I could check if that went out. I
also don't know if this e-mail will go out.)

Jari



From sm@resistor.net  Mon Feb 25 08:39:12 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0B421F95D9 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:39:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FBgwoZE1e3sz for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 08:39:10 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F48121F95D8 for <ietf@ietf.org>; Mon, 25 Feb 2013 08:39:10 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1PGd0da026917; Mon, 25 Feb 2013 08:39:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361810345; bh=v7SKqoSUJJpLQVAkdw8y/HX+5e1Hd1PQCHwDFv8PGfo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NudzuQ0zxQjUzuPN2bl9CsZfvn/ulpsSARvALSuAUaYHOZKPiftTmCB5rhX+/a2E+ gyAZeTavRIMJAdIVhYQRm3rWztHJOletIbqWk5F0q89usaI5otMsctCx4j1uzNJOr9 wpv8xpMGDAvH/fZ/HgeL6cPhRar1CzHKNsmook6E=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361810345; i=@resistor.net; bh=v7SKqoSUJJpLQVAkdw8y/HX+5e1Hd1PQCHwDFv8PGfo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MxNI+zqbO0iXMHqStsRZRZ+poyR8hcrJyPOpBNaZcN6345fQNjbAB09XpJqVEKQr/ mJ7vkerMunMBY1M5hcW+87oBa5nQZE18h31TEPhKafj2uQ2pjEvqRSpgZWvbcO9DRK NtlfIAbbRKcDwShZXzIw1eg6+kqcrrNUuoa4hk8A=
Message-Id: <6.2.5.6.2.20130225072932.09f0be18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Feb 2013 08:37:28 -0800
To: Simon Pietro Romano <spromano@unina.it>
From: SM <sm@resistor.net>
Subject: Vendor standardization (was: IETF chair's blog)
In-Reply-To: <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 16:39:13 -0000

Hi Simon,
At 03:15 25-02-2013, Simon Pietro Romano wrote:
>Just out of curiosity, can you list which of the above requirements 
>is not met by Meetecho?

Meetecho is a vendor.  In my humble opinion the IETF "standardizes" 
on protocols; it does not "standardize" on vendors.  I can still 
access the audio for IETF 56 which are hosted on IETF 
infrastructure.  I may not be able to access the links [1] provided 
by Meetecho [2] in future.

 From the Universi Dominici Gregis:

   "While keeping in mind present-day requirements, I have been careful, in
    formulating the new discipline, not to depart in substance from the wise
    and venerable tradition already established."

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/video-codec/current/msg00068.html
2. It applies to WebEx too. 


From ietf-secretariat@ietf.org  Mon Feb 25 09:05:33 2013
Return-Path: <ietf-secretariat@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 2281721F95C7; Mon, 25 Feb 2013 09:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7k9X4cvHZYq; Mon, 25 Feb 2013 09:05:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A085721F94CC; Mon, 25 Feb 2013 09:05:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Secretariat <ietf-secretariat@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Internet Draft Final Submission Cut-Off Today
X-Test-IDTracker: no
X-IETF-IDTracker: 4.40
Message-ID: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>
Date: Mon, 25 Feb 2013 09:05:32 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 17:05:33 -0000

This is a reminder that the Internet Draft Final Submission (version -01
and up) cut-off is today, Monday, February 25, 2013. =


All Final Version (-01 and up) submissions are due by UTC 24:00.

All drafts can be uploaded using the ID submission tool located here:
https://datatracker.ietf.org/submit/

The Internet-Draft cutoff dates as well as other significant dates for IETF=
 86 can be found at: =

https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86

Thank you for your understanding and cooperation. If you have any  question=
s or concerns, then please send a message to internet-drafts@ietf.org.

From spromano@unina.it  Mon Feb 25 09:30:14 2013
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D672621F95D4 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:30:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.718
X-Spam-Level: 
X-Spam-Status: No, score=-100.718 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQ8Q6jan6dpw for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:30:09 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5896F21F95BE for <ietf@ietf.org>; Mon, 25 Feb 2013 09:30:08 -0800 (PST)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id r1PHTxO8000912 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Feb 2013 18:29:59 +0100
Subject: Re: IETF chair's blog
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2335B444-22B7-4D9A-9023-B344DA76A871"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <512B74F7.5060506@gmail.com>
Date: Mon, 25 Feb 2013 18:30:10 +0100
Message-Id: <C15E83A6-52BC-413A-AE98-2486222E0266@unina.it>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org>	<51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.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: Mon, 25 Feb 2013 17:30:14 -0000

--Apple-Mail=_2335B444-22B7-4D9A-9023-B344DA76A871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Brian,

> It's proprietary, isn't it? The pop-ups on the the web site don't seem =
to
> work for me, but I can see a Buy button. (I realise that usage for the =
IETF
> is free, and I have no complaints.)

As you say, usage for the IETF is free, like our software ('free as in =
freedom'...).
The Buy button you mention (which is not operational as of yet) will be =
used to buy a 'one-shot' conference on a SaaS basis and does not relate =
to our IETF activities.

> Not sure about the standards status.

We tend to rely solely on open (IETF) standards: SIP, XMPP, BFCP, RTP, =
etc. We have some hooks towards proprietary technologies (flash and the =
like), but just for interoperability purposes.


> Anyway - if we want to move forward in an agreed way, I do think we
> need a list of criteria. I forgot "reliable" BTW.

Agreed. This is a highly desirable (and difficult to achieve) feature.

Cheers,

Simon


>=20
> Maybe this conversation belongs on tools-discuss@ietf.org.
>=20
>    Brian
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =CB l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/






--Apple-Mail=_2335B444-22B7-4D9A-9023-B344DA76A871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi =
Brian,<div><div><br><blockquote type=3D"cite"><div>It's proprietary, =
isn't it? The pop-ups on the the web site don't seem to<br>work for me, =
but I can see a Buy button. (I realise that usage for the IETF<br>is =
free, and I have no complaints.) </div></blockquote><div><br></div>As =
you say, usage for the IETF is free, like our software ('free as in =
freedom'...).</div><div>The Buy button you mention (which is not =
operational as of yet) will be used to buy a 'one-shot' conference on a =
SaaS basis and does not relate to our IETF =
activities.</div><div><br><blockquote type=3D"cite"><div>Not sure about =
the standards status.<br></div></blockquote><div><br></div>We tend to =
rely solely on open (IETF) standards: SIP, XMPP, BFCP, RTP, etc. We have =
some hooks towards proprietary technologies (flash and the like), but =
just for interoperability =
purposes.</div><div><br></div><div><br></div><div><blockquote =
type=3D"cite"><div>Anyway - if we want to move forward in an agreed way, =
I do think we<br>need a list of criteria. I forgot "reliable" =
BTW.<br></div></blockquote><div><br></div><div>Agreed. This is a highly =
desirable (and difficult to achieve) =
feature.</div><div><br></div><div><div>Cheers,</div><div><br></div><div>Si=
mon</div><div><br></div></div><br><blockquote type=3D"cite"><div><br>Maybe=
 this conversation belongs on <a =
href=3D"mailto:tools-discuss@ietf.org">tools-discuss@ietf.org</a>.<br><br>=
 &nbsp;&nbsp;&nbsp;Brian<br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =CB =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_2335B444-22B7-4D9A-9023-B344DA76A871--

From cabo@tzi.org  Mon Feb 25 09:58:25 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF0621E804B for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.138
X-Spam-Level: 
X-Spam-Status: No, score=-106.138 tagged_above=-999 required=5 tests=[AWL=0.111, 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 id7B3sLpOlGE for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 09:58:14 -0800 (PST)
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 73C9621F92DF for <ietf@ietf.org>; Mon, 25 Feb 2013 09:58:09 -0800 (PST)
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 r1PHw0pN015280; Mon, 25 Feb 2013 18:58:00 +0100 (CET)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id CCE233955; Mon, 25 Feb 2013 18:58:00 +0100 (CET)
Subject: Re: IETF chair's blog
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>
X-Priority: 3 (Normal)
In-Reply-To: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
Date: Mon, 25 Feb 2013 18:58:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <039FF5C1-3BCE-40F6-BAC5-FD856AC98084@tzi.org>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com> <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
To: jari.arkko@piuha.net
X-Mailer: Apple Mail (2.1499)
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, 25 Feb 2013 17:58:28 -0000

On Feb 25, 2013, at 17:33, jari.arkko@piuha.net wrote:

> A tools-login required for posting comments?

In a ~ 20-year IETFer, it evokes a bit of a smirk to see the IETF now =
starting to define its social media strategy...

The answer to the question depends on whether you want to engage IETFers =
only or a larger public.

If it is IETFers only, this mailing list is fine.
(The tools login is an even narrower group.)

A blog can be useful for addressing a larger public. =20
It's going to be far cry from Obama's tweets, but it's better than =
posting to an internal mailing list.

If this is supposed to be two-way communication and you want to get =
input from the larger public, be prepared for some loss of control.

Spammers aren't really the problem these days; there is pretty good =
software to minimize their impact.

People who genuinely want to engage you but are adding more noise than =
signal are the real problem.

We have enough experience with people who live in a completely different =
reality than most of us do.  Imagine running an appeals process through =
this blog.
(There are also people within the IETF that are well-respected for their =
technical input but still live in a slightly different reality from the =
rest of the world; their statements can become off-message for you =
quickly.)
So there needs to be a policy when comments are hidden or even deleted =
(no, that's not censorship), and this policy may need to be made known.  =
It will be debated.
There also need to be people who maintain response times within some =
reasonable latency while you are out skiing -- a response, maybe not the =
final solution.

Reaching out from an organization into social media tends to become a =
pretty big operation quickly, if it is done in a professional way.
But it may be worth it.
At least you don't have the SEC coming after you if you happen to make =
the wrong kind of statement.
Doing this with an appropriately personal touch may be the natural =
approach for us, but most of the work items do remain.

Gr=FC=DFe, Carsten


From mary.ietf.barnes@gmail.com  Mon Feb 25 10:36:17 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD55221E803C for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:36:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.575
X-Spam-Level: 
X-Spam-Status: No, score=-103.575 tagged_above=-999 required=5 tests=[AWL=0.024, 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 Gs97t-+LRlAI for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:36:17 -0800 (PST)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id CBB3421F9325 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:36:16 -0800 (PST)
Received: by mail-qe0-f48.google.com with SMTP id 3so1782954qea.35 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:36:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=1CDqfiZj1i28zujCbckUtTpf5KXPW64y+ZRc4wzjE0g=; b=qruBytJeEPI4kXXN7lqukT8uWIE/4Iyv/vJCjHyzMwMsOYMJPpfHHqlethK6Tta0OD CSQCy6cSuhOuNvMNjNtRkqXUu2vNhj88QcG6b7oCM+zNH8Y+1IvcqcU7Y0DWdve8jO2b PGuKZP+Osl/Ru1a4Y8kIifU/zSvyxygeVS6Ah31NCoeEFEPnt8sGEpy/H9S2/mtDEgTm wKwhKiVXSHbV4VJUN7S9cTsqDrKxuzFu8N20heTjBGcJpRFcz28l/KFpu7iloopHRfij f9WPeACWbrqJnsZEaDAZ06IAFmB9EJFdweAFFIHF0BPD3vi8w1mkwVPZoTvzhRrb74Df 0H7w==
MIME-Version: 1.0
X-Received: by 10.49.96.33 with SMTP id dp1mr15030306qeb.60.1361817375905; Mon, 25 Feb 2013 10:36:15 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Mon, 25 Feb 2013 10:36:15 -0800 (PST)
In-Reply-To: <20130225181820.10165.59200.idtracker@ietfa.amsl.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com>
Date: Mon, 25 Feb 2013 12:36:15 -0600
Message-ID: <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com>
Subject: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: IETF-Discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 18:36:18 -0000

In light of the upcoming meeting in Orlando, I have updated the
document.  For folks that are not on the IETF-86 attendees list, we've
had a fairly lengthy discussion about the remoteness of the venue and
the lack of access to food other than the hotel restaurants that are
often mediocre and over-priced.   For folks that aren't familiar, this
document has recommendations for meeting planners and IAOC folks in
terms of selecting venues that can ensure that IETF participants have
access to the types of food they require during the meetings.   Lunch
is often the biggest challenge due to frequent lunchtime meetings and
the volume of people requiring lunch at the exact same time.

I wrote this document right after the IETF meeting in Dublin (almost 5
years ago) and given the Orlando venue selection (which occurred after
the Dublin meeting) it does not seem to me that the requirements and
recommendations in this document are being considered as serious input
to that process.   While I am the most vocal with regards to this
issue, it isn't just me - others just don't want to be the target for
the types of discussions we inevitably have on this topic.  I will
note that if we were discussing wheel chair accessibility to IETF
meetings, most folks would understand the concern.  In the US, medical
conditions that require special diets are considered hidden
disabilities and the same legal requirements apply in terms of those
diets being accommodated.   While IETF is a non-profit, my
understanding is they have no legal requirements to provide the
accommodations, one would expect such as part of the nature of IETF in
terms of being an open and inclusive organization.

I will note that there have definitely been improvements since Dublin,
including the fruit bars when we have Ice Cream Thursdays and the
secretariat always communicates requirements when they are made aware
(e.g., WG chairs luncheon, as well as IAB stuff).  ISOC has also been
accommodating for their Tuesday lunch sessions.   As an aside while
I'm on the food topic, I didn't learn until last IETF that we don't
have Ice Cream Thursdays unless someone sponsors it.  Since I was
highly disappointed at the Atlanta meeting, I was able to get Polycom
to sponsor the event at IETF-86 ;)

At this stage, the feedback I would like related to this document is
with regards it's readiness for publication as an RFC.  One of the
updates to the document was with regards to the references to other
IETF logistic documents (the Tao and the travel FAQ) which have since
been published.  I believe this document is equally substantive and
applicable to the IETF as those documents.

Regards,
Mary


---------- Forwarded message ----------
From:  <internet-drafts@ietf.org>
Date: Mon, Feb 25, 2013 at 12:18 PM
Subject: I-D Action: draft-barnes-healthy-food-06.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : Healthy Food and Special Dietary
Requirements for IETF meetings
        Author(s)       : Mary Barnes
        Filename        : draft-barnes-healthy-food-06.txt
        Pages           : 18
        Date            : 2013-02-25

Abstract:
   This document describes the basic requirements for food for folks
   that attend IETF meetings require special diets, as well as those
   that prefer to eat healthy.  While, the variety of special diets is
   quite broad, the most general categories are described.  There can be
   controversy as to what constitutes healthy eating, but there are some
   common, generally available foods that comprise the basis for healthy
   eating and special diets.  This document provides some
   recommendations to meeting planners, as well as participants, in
   handling these requirements.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-barnes-healthy-food

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-barnes-healthy-food-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-barnes-healthy-food-06


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 hsantos@isdg.net  Mon Feb 25 10:59:13 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF0921F9300 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.897
X-Spam-Level: 
X-Spam-Status: No, score=-101.897 tagged_above=-999 required=5 tests=[AWL=-0.220, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amwSM9m7zG3E for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 10:59:13 -0800 (PST)
Received: from ftp.catinthebox.net (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3853621F91B0 for <ietf@ietf.org>; Mon, 25 Feb 2013 10:59:08 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3130; t=1361818742; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=rjqZpgz oFpWEkTy1pQ4cPK27aVc=; b=bYtW/MM9zxsVwvt/ozbBVDkaI48dSI9ZRpEA3XR g9GFb7BjxZ3rkh/vPYnevkRG0toPhnCogBhOUEKs7vQEW+zHPiH64c3Zfe3SJdfU gZ7Z28ZqwfDONU/ghakYtVX9mFZ3tUEupIindhjEaNvko5/V8spIycBFHvvx6eW0 VeEk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 25 Feb 2013 13:59:02 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 612489518.1761.3208; Mon, 25 Feb 2013 13:59:01 -0500
Message-ID: <512BB403.60900@isdg.net>
Date: Mon, 25 Feb 2013 13:57:07 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B1EBA.30507@gmail.com> <BBB5AA20-D2EF-4F90-BF98-993A1AFE25DB@unina.it> <512B74F7.5060506@gmail.com> <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
In-Reply-To: <775f4e94eac2f111e3dc1bdc5f95bee7.squirrel@www.piuha.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 18:59:13 -0000

Its not really orthogonal if you are seeking a feature list.  Will it be out-sourced, open source or in-house developed?

That's the dilemma with most older establishments that do not wish to provide less support for its long time "customers" but need to also migrate and provide other methods as well.    Overall, its a game of how much do you single source the publishing and the basic service communications with multiple portals I/O methods.   You will get redundancy if you don't single source.

Personally, you should start with single sourcing the web blog entries either with the IETF mail list or another "IETFBLOG" mailing list.  Adding a tweet notification can be optionally provided, just don't focus on it as a principle method, at least not yet.   I would consider RSS feeds as well.  The follow-ups should perhaps begin within the list.  There is also the archive view that can be done starting with blog mailing list entry.

--
HLS


On 2/25/2013 11:33 AM, jari.arkko@piuha.net wrote:
> Thanks everyone for the feedback, on and off list.
>
> We did the blog primarily as a means to convey more thoughts and encourage
> discussion. That's the content part. We'll see later how that works out.
>
> The medium part is orthogonal, but interesting. For this stage we thought
> that an IETF-server based web system would work nicely, even if we could
> have done all on pure e-mail mode as well. I do have a question mark on
> how to handle comments, however. It seems that open blog commentary on web
> system will invite plenty of spam, so where does that leave us? Ask for
> comments to be sent on this list, i.e., e-mail commentary? We seem to be
> in that mode already... Or should we implement some specific spam
> protection scheme that will save me and the secretariat from manual work
> in checking postings? A tools-login required for posting comments? Or
> something else, what?
>
> Going further, you asked about social media and material on external
> systems. This is not on the agenda for the current blog experiment (except
> in a small way, see below). But it is something that we should find an
> answer to eventually.
>
> I am of the opinion that long-term, the IETF can not stay away from the
> collaboration and discussion tools that majority of the Internet users are
> using, including social media. But we need to control how this happens,
> and I do worry about being able to own our own content and providing
> everyone an equal access to it. I'd like to make a separation between
> spreading information from the IETF across multiple media, hosting that
> information in the external medium, and making an external medium the only
> way to participate. I think we should stay away from the latter two
> approaches. But the first one is benign, I think. As an example, we were
> planning to send out a tweet from the IETF tweeter account about the
> creation of the blog, with an URL back to the IETF site. (If I had even
> the beginnings of an Internet connection I could check if that went out. I
> also don't know if this e-mail will go out.)
>
> Jari
>




From jari.arkko@piuha.net  Mon Feb 25 11:04:23 2013
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59B421F92E4 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nc6ZS8pxGHMd for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:04:23 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id ED43021F9330 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:04:22 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BAB822CC5B; Mon, 25 Feb 2013 21:04:21 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4sg_VV_Oht0; Mon, 25 Feb 2013 21:04:21 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2E5C42CC3B; Mon, 25 Feb 2013 21:04:13 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Showing support during IETF LC...
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com>
Date: Tue, 26 Feb 2013 02:03:57 +0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 19:04:23 -0000

Agree with what John, Brian, and others have said. FWIW, at times - =
particularly with documents having some controversy - the ADs are left =
wondering what the silent majority is thinking. So in some cases the =
private messages to the AD in question or to the IESG are helpful. And =
while "+1" is usually bad form, indicating that you've done a thorough =
review and found no issues is appreciated. (Or better yet, that you =
intend to put this technology into your own use.)

Finally, John Leslie wrote:

> In theory, an individual raising an issue on the <ietf> list has the
> same weight as a directorate review, but in practice each AD takes a
> directorate review more seriously unless he/she knows the commentor
> well.


I hope that is not the case. It should not be. The concerns raised in a =
comment to the list, from an individual or directorate, should be =
weighed on how "reasoned messages" they are. How they are justified. And =
your own understanding of the issue and its seriousness, now that it has =
been explained. Of course, we are all humans, so there can be natural =
bias to trusting people you know more than others. But we are _trying_ =
to do it differently.

Naturally, an opinion from, say, a working group chair in the same area =
tends to be well-reasoned, because he or she has a lot of experience in =
the matter. But just because he or she might be a directorate member =
should not result in the opinion being weighed any more than someone =
else's.

Jari


From mary.ietf.barnes@gmail.com  Mon Feb 25 11:16:36 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 071F621E80AA for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id exnRgcuaC6pp for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:16:35 -0800 (PST)
Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5F03421E80A8 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:16:35 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id g10so1814604qah.11 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:16:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=Hp5K8rChuUqDPryhQo1Ndt2/3r+s5hrNJeNk4+JKs/I=; b=diY3B825tIdXmiTCHaQU7mEE6yA9eO7+iSgGs7ABaNlnQZohlIbWNhWHKlQhSGqEfZ Z8IXysFwoBveDkrHOz5994zSBUm9UHXo0gCG9+WXE9QghmykKjV57D04Oo94lUWIjqVi 0zbQYXfdCTmYG7ziwBIm77UT+MeNtNm7W2kRcnHXa0olAIH2me0tkEonXZ+q5W1XZjw0 ManMU5mqDKI2RXn2UVwvFRIpJoL0K3NfmOh8NmrQHE+pjhcjsNX9rVlJjEzdqGx76BDg Xt/HAneUvXHSlBmaozD1ghYYSeDqZiMlbNl6UAEW2nWNKpvR43mMNmqjRfb7iPvioADt 20DA==
MIME-Version: 1.0
X-Received: by 10.49.96.33 with SMTP id dp1mr15266130qeb.60.1361819794857; Mon, 25 Feb 2013 11:16:34 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Mon, 25 Feb 2013 11:16:34 -0800 (PST)
In-Reply-To: <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
Date: Mon, 25 Feb 2013 13:16:34 -0600
Message-ID: <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com>
Subject: Re: Showing support during IETF LC...
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John C Klensin <john-ietf@jck.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: Mon, 25 Feb 2013 19:16:36 -0000

On Mon, Feb 25, 2013 at 1:03 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
> Agree with what John, Brian, and others have said. FWIW, at times - parti=
cularly with documents having some controversy - the ADs are left wondering=
 what the silent majority is thinking. So in some cases the private message=
s to the AD in question or to the IESG are helpful. And while "+1" is usual=
ly bad form, indicating that you've done a thorough review and found no iss=
ues is appreciated. (Or better yet, that you intend to put this technology =
into your own use.)
[MB] It's not clear to me why you think +1 is bad form.  I interpret
+1 to mean that an individual agrees with the
assessment/input/comments of the email to which they +1.  Rather than
regurgitate the information, it seems expedient to me to use +1 in
those cases.    Certainly, if no substantive comments are made or no
statement such as you indicate appears in the thread, then certainly
+1 isn't useful.  [/MB]
>
> Finally, John Leslie wrote:
>
>> In theory, an individual raising an issue on the <ietf> list has the
>> same weight as a directorate review, but in practice each AD takes a
>> directorate review more seriously unless he/she knows the commentor
>> well.
>
>
> I hope that is not the case. It should not be. The concerns raised in a c=
omment to the list, from an individual or directorate, should be weighed on=
 how "reasoned messages" they are. How they are justified. And your own und=
erstanding of the issue and its seriousness, now that it has been explained=
. Of course, we are all humans, so there can be natural bias to trusting pe=
ople you know more than others. But we are _trying_ to do it differently.
>
> Naturally, an opinion from, say, a working group chair in the same area t=
ends to be well-reasoned, because he or she has a lot of experience in the =
matter. But just because he or she might be a directorate member should not=
 result in the opinion being weighed any more than someone else's.
>
> Jari
>

From mrex@sap.com  Mon Feb 25 11:31:01 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5D321F9286 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.235
X-Spam-Level: 
X-Spam-Status: No, score=-10.235 tagged_above=-999 required=5 tests=[AWL=0.014, 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 WlBxi9p5C-10 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:31:00 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 7A8AF21F91F3 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:31:00 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r1PJUwqJ016064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 25 Feb 2013 20:30:58 +0100 (MET)
Subject: Re: Showing support during IETF LC...
In-Reply-To: <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Mon, 25 Feb 2013 20:30:58 +0100 (CET)
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: <20130225193058.1C2D71A5C5@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: John C Klensin <john-ietf@jck.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 19:31:01 -0000

Jari Arkko wrote:
> Agree with what John, Brian, and others have said. FWIW, at times
> - particularly with documents having some controversy - the ADs are
> left wondering what the silent majority is thinking.

I've previously mentioned that I believe the current IESG ballot rules
are insufficient.  They should be changed to require a positive confirmation
from *TWO* IESG members, not just one (the latter being the AD who brings
the document to the IESG).

I believe that at least two IESG members should confirm that they believe
publication of a specific document is a good idea.  IMO, the current
rules go too far in substituting "rough consensus" by "no objection".

-Martin

From sm@resistor.net  Mon Feb 25 11:54:41 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 350B721F91D8 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.576
X-Spam-Level: 
X-Spam-Status: No, score=-102.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tfQUfHC5PJPX for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:54:40 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 290B921F91B4 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:54:40 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1PJsZqW023598 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:54:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361822079; bh=4GTjJBLrJ0/cyxItdIcv/0tG5tsUzN+L3FAgC+aTOtg=; h=Date:To:From:Subject:In-Reply-To:References; b=xM8eGOMTqFXDsigN88lXbJBgFWyziGNGH5m47xjj/oqMMlaMADZP6glp3CsJe/zTJ dGGePN6KHKuxcbHe3j6adeGRKKY5seOrqvzE2fxZyZsGpjJ9R+Ge2J9fXosO6vVoZR Ao73L3U1ms6tI5xs0ZKmHGXxVF86Ug1DvIaQC2mA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361822079; i=@resistor.net; bh=4GTjJBLrJ0/cyxItdIcv/0tG5tsUzN+L3FAgC+aTOtg=; h=Date:To:From:Subject:In-Reply-To:References; b=zDvwnEQMsjdgHAR18LHsgty3iBT9391PUUQeqdgPi0fU7w30ymVc795Ioa+OT6vYC zvKPCq3Q8sLQadkt3bwm96lIY9c41biZLURne3QZGVKuSbrz+jmJ6A63vJb33tl+H3 o9Cy+mhwt3//yjsCMEyo5xLDmTlCMFw5c2wZNZH8=
Message-Id: <6.2.5.6.2.20130225104036.0af8b318@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Feb 2013 11:33:07 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-intarea-nat-reveal-analysis-05.txt> (Analysis of Solution Candidates to Reveal a Host Identifier (HOST_ID) in Shared Address Deployments) to Informational RFC
In-Reply-To: <20130222190642.19027.84724.idtracker@ietfa.amsl.com>
References: <20130222190642.19027.84724.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: Mon, 25 Feb 2013 19:54:41 -0000

At 11:06 22-02-2013, The IESG wrote:
>The IESG has received a request from the Internet Area Working Group WG
>(intarea) to consider the following document:
>- 'Analysis of Solution Candidates to Reveal a Host Identifier (HOST_ID)
>    in Shared Address Deployments'
>   <draft-ietf-intarea-nat-reveal-analysis-05.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2013-03-08. Exceptionally, comments may be

My comments should not be read as a statement of support. :-)

In Section 1:

   "Section 3 discusses privacy issues common to all HOST_ID solutions.
    It is out of scope of this document to elaborate on privacy issues
    specific to each solution."

I suggest explaining what "HOST_ID" is.

In Section 2:

   "HOST_ID does not reveal the identity of a user, a subscriber or an
    application."

I suggest adding an explanation for that statement.

In Section 4.4.1:

   "For HTTP, Forwarded header ([I-D.ietf-appsawg-http-forwarded]) can be
    used to display the original IP address when an address sharing
    device is involved."

A HTTP proxy is not an address sharing device in my opinion.

   "The address sharing device has to strip all included Forwarded
    headers before injecting their own."

In Section 4.4.2:

  "Injecting Forwarded header also introduces some implementation
   complexity if the HTTP packet is at or close to the MTU size."

What is a HTTP packet?

Regards,
-sm






From hsantos@isdg.net  Mon Feb 25 11:57:47 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4C721F91CC for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.359
X-Spam-Level: 
X-Spam-Status: No, score=-102.359 tagged_above=-999 required=5 tests=[AWL=0.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 FNGNFt9TpUUv for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 11:57:42 -0800 (PST)
Received: from listserv.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0995B21F8FD4 for <ietf@ietf.org>; Mon, 25 Feb 2013 11:57:39 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=7697; t=1361822254; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=YS98X6X 13Z5jUdP1n37gJBkxrkw=; b=UZbUsxeBZGzlwd3bh9zrWO7vmTWSxI0LuJlMij8 aOebb0wVRrn2Jj6QMDjAi+5A9sl4X3Hg6xKLegT3Q23tjUPCyxHd7g+8ZMjcsVvP TyfR0s2jbomIjnjtLhMWX21fVRHedGJbiyQe1vUdxnbgV8EBiUisbkKa4m1D6Mup FwRY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 25 Feb 2013 14:57:34 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 616002193.1761.1388; Mon, 25 Feb 2013 14:57:34 -0500
Message-ID: <512BC1BC.3000009@isdg.net>
Date: Mon, 25 Feb 2013 14:55:40 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net> <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net>
In-Reply-To: <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, IAB IAB <iab@iab.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, draft-iab-privacy-considerations@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, 25 Feb 2013 19:57:47 -0000

Hi,

Related to your question, if it wasn't done already, I think there is 
one item to consider  or define - $Owner(s) and/or $Ownership. (I don't 
see any terms like owner, ownership in this document). The US ECPA has 
evolved with additional new laws, some as the "Good Samaritan" 
provisions, relaxations and also there has been new challenges and in my 
assessment it was primarily based on long adhered ownership principles. 
Just like employers enjoyed many US ECPA privacy exemptions, the 
Googles, Facebooks and other 3rd party service bureaus have also used 
"ownership" justify their leveraging of user data - "its our network and 
equipment...."

I think the $intermediary term touches base, but i don't see it describe 
nor the $initiator being related to the owner of things.

Ownership is very fundamental when we look at  the natural ethical 
design considerations, this should be one of the tenets of the document, 
in my view.  Recognized ownership has a very vital effect on what a 
protocol may|can|should offer or not offer as to not open Pandora's box.

--
HLS

On 2/24/2013 2:23 PM, Hannes Tschofenig wrote:
> Hi Hector,
>
>
> On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:
>
>> Hi, with a quick review, and many comments and points, I think the one single part that I would have some questions about is in the intro:
>>
>>    The guidance provided in
>>    this document is generic and can be used to inform the design of any
>>    protocol to be used anywhere in the world, without reference to
>>    specific legal frameworks.
>>
>>
>> Is that a goal?
> Yes, that's the goal.
>
> As you know, the IETF develops specifications that are used on the Internet and not just in a specific region. Trying to interpret national laws and to provide region-by-region specific guidance did not seem desirable to us.
>
>>   Do you feel you have reached providing such "Global Common" guidelines in the area of privacy?
> Yes, I think so and this document follows the spirit of RFC 3552 "Guidelines for Writing RFC Text on Security Considerations". This document is essentially the privacy version of what RFC 3552 is for security. If you look at RFC 3552 you will also fail to find references to regulation on security matters (even though they exist).
>
> We did look at many documents that seemed relevant input, such as the mentioned OECD document, and we spoke with data protection authorities and solicited their input. Our job would have been easier if we could have just re-used one of these documents listing the privacy principles. Unfortunately, it turns out that these documents were written for a different audience and that audience is supposed to have different capabilities regarding the design and the deployment of their services. In the IETF we do not have the same degree of freedom and impact and so we developed these guidelines to the best of our capabilities.
>
>>   How does it compare to US ECPA provisions for "User Expectations" which has served as a global model for other jurisdictions?
>> The reason I ask is because I have been very sensitive to ethical design and product liability issues in our product lines since 1986 following the guidelines set forth by the US ECPA for:
>>
>> - Thou shall not block/reject things without user knowledge,
>> - Thou shall not tamper/edit things especially when passing things (relays),
>> - Thou shall kept private things private.
>>
>> This was considered "Global" once upon a time.  Now its arguable.
> What is interesting for us to find out whether you believe that the Electronic Communications Privacy Act has for additional privacy aspects we need to address in the document.
> It is not our goal to interpret specific regulatory documents (even though it is interesting). This is the (well-paid) job of many lawyers.
>
> Ciao
> Hannes
>
>> --
>> HLS
>>
>> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>>> Hi SM,
>>>
>>> Thanks for your comments. Some responses are inline.
>>>
>>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>>
>>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>>> This is an announcement of an IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'.
>>>>>
>>>>> The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:
>>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>>> In Section 1:
>>>>
>>>>   'With regard to data, often it is a concept applied to
>>>>    "personal data," information relating to an identified or
>>>>    identifiable individual.'
>>>>
>>>> I suggest rewriting the above sentence.
>>> The authors have re-written that sentence several times and in different ways already. Do you have a specific suggestion about how to improve it?
>>>
>>>>   "Many sets of privacy principles and privacy design frameworks have been
>>>>    developed in different forums over the years."
>>>>
>>>> There is also some work in the APEC region (see http://publications.apec.org/publication-detail.php?pub_id=390 (payware)).
>>> As far as I know the APEC framework is one of many frameworks (none of which we cite since there are so many) based on the OECD-style FIPs. Is that incorrect?
>>>
>>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC 6772.
>>> Fixed.
>>>
>>>> I read some of the previous versions of this draft.  The Abstract Section describes the document as providing guidance for developing privacy considerations for inclusion in protocol specifications.  I found the draft difficult to digest.  I suggest simplifying the draft to make the guidance accessible to the target audience.
>>> I'm not quite sure what you are recommending here, but we have had conversations in the IAB privacy program about moving the guidance part up, or otherwise trying to make the focus on the guidance piece more prominent. The difficulty is that there is a broad range in the extent to which potential readers are familiar with privacy concepts, so jumping straight into the guidance would not be appropriate for some portion of the audience. If you have concrete suggestions for how to simplify, those would be helpful.
>>>
>>>> One of the issues nowadays is what to do about intermediaries.  If I am not mistaken RFC 3238 was one of the first documents to tackle that question from a privacy perspective.  There have been a few proposals to introduce intermediaries as part of the architecture (I am using the word is used loosely).  It is easy to argue for intermediaries based on use cases.  There was a case recently where the users only became aware that they have signed up for using an intermediary through the EULA.
>>>>
>>>> The draft introduces the concept of secondary use (Section 4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).
>>> Not all secondary uses involve disclosure (such as the example given in 4.2.3). I have added a sentence to clarify this, however:
>>>
>>> "Secondary use encompasses any use of data, including disclosure."
>>>
>>>> The draft mentions consent in several places.  The authors are likely aware that consent was a hot topic for DNT.  It's easier to start with something that is easy for the average person to understand and build from there.  Section 7.2 could more about consent instead of user participation or control.
>>> We tried to think of a case where a consent mechanism was actually developed in the IETF, but as a general matter consent mechanisms tend to be out of scope, which is why we focus more on user controls (which still show up rarely but do show up).
>>>
>>> Thanks,
>>> Alissa
>>>
>>>> Regards,
>>>> -sm
>>>>
>>>
>>>
>>



From acooper@cdt.org  Mon Feb 25 12:02:13 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB33921E811F for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.616
X-Spam-Level: 
X-Spam-Status: No, score=-102.616 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wBcjCxaLgUBK for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:02:05 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id C8C3021E812C for <ietf@ietf.org>; Mon, 25 Feb 2013 12:01:33 -0800 (PST)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 25 Feb 2013 15:01:26 -0500
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <512BC1BC.3000009@isdg.net>
Date: Mon, 25 Feb 2013 15:01:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EED5C632-6A8D-4AE9-9B5F-F15CF2F9196B@cdt.org>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net> <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net> <512BC1BC.3000009@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1084)
Cc: SM <sm@resistor.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IAB IAB <iab@iab.org>, draft-iab-privacy-considerations@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, 25 Feb 2013 20:02:14 -0000

Hi Hector,

Just to clarify, do you mean ownership of personal data? Or something =
else?

Thanks,
Alissa

On Feb 25, 2013, at 2:55 PM, Hector Santos wrote:

> Hi,
>=20
> Related to your question, if it wasn't done already, I think there is =
one item to consider  or define - $Owner(s) and/or $Ownership. (I don't =
see any terms like owner, ownership in this document). The US ECPA has =
evolved with additional new laws, some as the "Good Samaritan" =
provisions, relaxations and also there has been new challenges and in my =
assessment it was primarily based on long adhered ownership principles. =
Just like employers enjoyed many US ECPA privacy exemptions, the =
Googles, Facebooks and other 3rd party service bureaus have also used =
"ownership" justify their leveraging of user data - "its our network and =
equipment...."
>=20
> I think the $intermediary term touches base, but i don't see it =
describe nor the $initiator being related to the owner of things.
>=20
> Ownership is very fundamental when we look at  the natural ethical =
design considerations, this should be one of the tenets of the document, =
in my view.  Recognized ownership has a very vital effect on what a =
protocol may|can|should offer or not offer as to not open Pandora's box.
>=20
> --
> HLS
>=20
> On 2/24/2013 2:23 PM, Hannes Tschofenig wrote:
>> Hi Hector,
>>=20
>>=20
>> On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:
>>=20
>>> Hi, with a quick review, and many comments and points, I think the =
one single part that I would have some questions about is in the intro:
>>>=20
>>>   The guidance provided in
>>>   this document is generic and can be used to inform the design of =
any
>>>   protocol to be used anywhere in the world, without reference to
>>>   specific legal frameworks.
>>>=20
>>>=20
>>> Is that a goal?
>> Yes, that's the goal.
>>=20
>> As you know, the IETF develops specifications that are used on the =
Internet and not just in a specific region. Trying to interpret national =
laws and to provide region-by-region specific guidance did not seem =
desirable to us.
>>=20
>>>  Do you feel you have reached providing such "Global Common" =
guidelines in the area of privacy?
>> Yes, I think so and this document follows the spirit of RFC 3552 =
"Guidelines for Writing RFC Text on Security Considerations". This =
document is essentially the privacy version of what RFC 3552 is for =
security. If you look at RFC 3552 you will also fail to find references =
to regulation on security matters (even though they exist).
>>=20
>> We did look at many documents that seemed relevant input, such as the =
mentioned OECD document, and we spoke with data protection authorities =
and solicited their input. Our job would have been easier if we could =
have just re-used one of these documents listing the privacy principles. =
Unfortunately, it turns out that these documents were written for a =
different audience and that audience is supposed to have different =
capabilities regarding the design and the deployment of their services. =
In the IETF we do not have the same degree of freedom and impact and so =
we developed these guidelines to the best of our capabilities.
>>=20
>>>  How does it compare to US ECPA provisions for "User Expectations" =
which has served as a global model for other jurisdictions?
>>> The reason I ask is because I have been very sensitive to ethical =
design and product liability issues in our product lines since 1986 =
following the guidelines set forth by the US ECPA for:
>>>=20
>>> - Thou shall not block/reject things without user knowledge,
>>> - Thou shall not tamper/edit things especially when passing things =
(relays),
>>> - Thou shall kept private things private.
>>>=20
>>> This was considered "Global" once upon a time.  Now its arguable.
>> What is interesting for us to find out whether you believe that the =
Electronic Communications Privacy Act has for additional privacy aspects =
we need to address in the document.
>> It is not our goal to interpret specific regulatory documents (even =
though it is interesting). This is the (well-paid) job of many lawyers.
>>=20
>> Ciao
>> Hannes
>>=20
>>> --
>>> HLS
>>>=20
>>> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>>>> Hi SM,
>>>>=20
>>>> Thanks for your comments. Some responses are inline.
>>>>=20
>>>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>>>=20
>>>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>>>> This is an announcement of an IETF-wide Call for Comment on =
'Privacy Considerations for Internet Protocols'.
>>>>>>=20
>>>>>> The document is being considered for publication as an =
Informational RFC within the IAB stream, and is available for inspection =
here:
>>>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>>>> In Section 1:
>>>>>=20
>>>>>  'With regard to data, often it is a concept applied to
>>>>>   "personal data," information relating to an identified or
>>>>>   identifiable individual.'
>>>>>=20
>>>>> I suggest rewriting the above sentence.
>>>> The authors have re-written that sentence several times and in =
different ways already. Do you have a specific suggestion about how to =
improve it?
>>>>=20
>>>>>  "Many sets of privacy principles and privacy design frameworks =
have been
>>>>>   developed in different forums over the years."
>>>>>=20
>>>>> There is also some work in the APEC region (see =
http://publications.apec.org/publication-detail.php?pub_id=3D390 =
(payware)).
>>>> As far as I know the APEC framework is one of many frameworks (none =
of which we cite since there are so many) based on the OECD-style FIPs. =
Is that incorrect?
>>>>=20
>>>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC =
6772.
>>>> Fixed.
>>>>=20
>>>>> I read some of the previous versions of this draft.  The Abstract =
Section describes the document as providing guidance for developing =
privacy considerations for inclusion in protocol specifications.  I =
found the draft difficult to digest.  I suggest simplifying the draft to =
make the guidance accessible to the target audience.
>>>> I'm not quite sure what you are recommending here, but we have had =
conversations in the IAB privacy program about moving the guidance part =
up, or otherwise trying to make the focus on the guidance piece more =
prominent. The difficulty is that there is a broad range in the extent =
to which potential readers are familiar with privacy concepts, so =
jumping straight into the guidance would not be appropriate for some =
portion of the audience. If you have concrete suggestions for how to =
simplify, those would be helpful.
>>>>=20
>>>>> One of the issues nowadays is what to do about intermediaries.  If =
I am not mistaken RFC 3238 was one of the first documents to tackle that =
question from a privacy perspective.  There have been a few proposals to =
introduce intermediaries as part of the architecture (I am using the =
word is used loosely).  It is easy to argue for intermediaries based on =
use cases.  There was a case recently where the users only became aware =
that they have signed up for using an intermediary through the EULA.
>>>>>=20
>>>>> The draft introduces the concept of secondary use (Section 4.2.3). =
 Strictly speaking, it is a disclosure (Section 4.2.4).
>>>> Not all secondary uses involve disclosure (such as the example =
given in 4.2.3). I have added a sentence to clarify this, however:
>>>>=20
>>>> "Secondary use encompasses any use of data, including disclosure."
>>>>=20
>>>>> The draft mentions consent in several places.  The authors are =
likely aware that consent was a hot topic for DNT.  It's easier to start =
with something that is easy for the average person to understand and =
build from there.  Section 7.2 could more about consent instead of user =
participation or control.
>>>> We tried to think of a case where a consent mechanism was actually =
developed in the IETF, but as a general matter consent mechanisms tend =
to be out of scope, which is why we focus more on user controls (which =
still show up rarely but do show up).
>>>>=20
>>>> Thanks,
>>>> Alissa
>>>>=20
>>>>> Regards,
>>>>> -sm
>>>>>=20
>>>>=20
>>>>=20
>>>=20
>=20
>=20
>=20



From warren@kumari.net  Mon Feb 25 12:06:42 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDC221E8160 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:06:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.534
X-Spam-Level: 
X-Spam-Status: No, score=-102.534 tagged_above=-999 required=5 tests=[AWL=0.065, 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 HdY9bxhyEKTC for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:06:42 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A0C21E8147 for <ietf@ietf.org>; Mon, 25 Feb 2013 12:06:39 -0800 (PST)
Received: from [192.168.1.145] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 8ED3E1B40B78; Mon, 25 Feb 2013 15:06:38 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Showing support during IETF LC...
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com>
Date: Mon, 25 Feb 2013 15:06:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6BD79347-3A9B-42DD-B75A-3FF55021CD76@kumari.net>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net> <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: John C Klensin <john-ietf@jck.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: Mon, 25 Feb 2013 20:06:42 -0000

On Feb 25, 2013, at 2:16 PM, Mary Barnes <mary.ietf.barnes@gmail.com> =
wrote:

> On Mon, Feb 25, 2013 at 1:03 PM, Jari Arkko <jari.arkko@piuha.net> =
wrote:
>> Agree with what John, Brian, and others have said. FWIW, at times - =
particularly with documents having some controversy - the ADs are left =
wondering what the silent majority is thinking. So in some cases the =
private messages to the AD in question or to the IESG are helpful. And =
while "+1" is usually bad form, indicating that you've done a thorough =
review and found no issues is appreciated. (Or better yet, that you =
intend to put this technology into your own use.)
> [MB] It's not clear to me why you think +1 is bad form.  I interpret
> +1 to mean that an individual agrees with the
> assessment/input/comments of the email to which they +1.  Rather than
> regurgitate the information, it seems expedient to me to use +1 in
> those cases.    Certainly, if no substantive comments are made or no
> statement such as you indicate appears in the thread, then certainly
> +1 isn't useful.  [/MB]

I suspect it is because it is very hard to know if someone replying with =
'+1' has actually read / has a useful opinion on whatever they are =
replying to, or is just going alone with the herd=85

Then again, which is more useful / less annoying?:
Version 1:=20
"I also do not understand why +1 is bad form.
Instead of simply restating in other words that which was said =
previously, I could simply reply with +1 to show that I agree with a =
particular stance.

Obviously, if there are no comments of substance in the discussion then =
simply replying with +1 is not contributing anything"

or, Version 2:
"+1"

:-P

W
>>=20
>> Finally, John Leslie wrote:
>>=20
>>> In theory, an individual raising an issue on the <ietf> list has the
>>> same weight as a directorate review, but in practice each AD takes a
>>> directorate review more seriously unless he/she knows the commentor
>>> well.
>>=20
>>=20
>> I hope that is not the case. It should not be. The concerns raised in =
a comment to the list, from an individual or directorate, should be =
weighed on how "reasoned messages" they are. How they are justified. And =
your own understanding of the issue and its seriousness, now that it has =
been explained. Of course, we are all humans, so there can be natural =
bias to trusting people you know more than others. But we are _trying_ =
to do it differently.
>>=20
>> Naturally, an opinion from, say, a working group chair in the same =
area tends to be well-reasoned, because he or she has a lot of =
experience in the matter. But just because he or she might be a =
directorate member should not result in the opinion being weighed any =
more than someone else's.
>>=20
>> Jari
>>=20
>=20

--
The duke had a mind that ticked like a clock and, like a clock, it =
regularly went cuckoo.

    -- (Terry Pratchett, Wyrd Sisters)



From hsantos@isdg.net  Mon Feb 25 12:28:11 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D3E21F925B for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.938
X-Spam-Level: 
X-Spam-Status: No, score=-101.938 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N6kqpvf1CqAN for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:28:10 -0800 (PST)
Received: from ntbbs.santronics.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id DE49821F923A for <ietf@ietf.org>; Mon, 25 Feb 2013 12:28:09 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=8986; t=1361824081; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=wYMDiZz cxt+tQyxGv9wQDpWr/1w=; b=A+4PTZgOu7Vs6e9zR+fLBv/hBi5jUyuajwrIS7s BCdG/n156HVnKjHZycZktsV3OiimbbJVeQWPNXrYwvOnIPen+6IMRAedxoaihWjR bq6FPA2tC/yzSxQlvMM4XQi/Yenqr48mu/tSDV0ReAE1bAfGWfVAjp893otaILmY qPuQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 25 Feb 2013 15:28:01 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 617828091.1761.2240; Mon, 25 Feb 2013 15:28:00 -0500
Message-ID: <512BC8DE.6060606@isdg.net>
Date: Mon, 25 Feb 2013 15:26:06 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net> <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net> <512BC1BC.3000009@isdg.net> <EED5C632-6A8D-4AE9-9B5F-F15CF2F9196B@cdt.org>
In-Reply-To: <EED5C632-6A8D-4AE9-9B5F-F15CF2F9196B@cdt.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IAB IAB <iab@iab.org>, draft-iab-privacy-considerations@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, 25 Feb 2013 20:28:11 -0000

Hi,  I would think both - ownership of the "things" and ownership of the 
medium moving, transporting, storing the "things."    Case in point:  I 
can write a protocol to move private data from point A to point B.  My 
first requirement is to make sure the design stipulates it stayed 
private, especially at the receiving end.  However, there is precedence 
where claims were made for ownership of the storage regardless of how 
temporary it may have been at the intermediary, a routed email for 
example.  Someone leverage a private email communications for their 
benefit by viewing the monitoring intermediate passthru transport data.  
I'm not sure how such a document as this prevent this. It would be more 
about ethics I suppose, but if a protocol was to consider this, a 
designer may come up with ideas to prevent or minimize it or leverage it 
even more.

On 2/25/2013 3:01 PM, Alissa Cooper wrote:
> Hi Hector,
>
> Just to clarify, do you mean ownership of personal data? Or something else?
>
> Thanks,
> Alissa
>
> On Feb 25, 2013, at 2:55 PM, Hector Santos wrote:
>
>> Hi,
>>
>> Related to your question, if it wasn't done already, I think there is one item to consider  or define - $Owner(s) and/or $Ownership. (I don't see any terms like owner, ownership in this document). The US ECPA has evolved with additional new laws, some as the "Good Samaritan" provisions, relaxations and also there has been new challenges and in my assessment it was primarily based on long adhered ownership principles. Just like employers enjoyed many US ECPA privacy exemptions, the Googles, Facebooks and other 3rd party service bureaus have also used "ownership" justify their leveraging of user data - "its our network and equipment...."
>>
>> I think the $intermediary term touches base, but i don't see it describe nor the $initiator being related to the owner of things.
>>
>> Ownership is very fundamental when we look at  the natural ethical design considerations, this should be one of the tenets of the document, in my view.  Recognized ownership has a very vital effect on what a protocol may|can|should offer or not offer as to not open Pandora's box.
>>
>> --
>> HLS
>>
>> On 2/24/2013 2:23 PM, Hannes Tschofenig wrote:
>>> Hi Hector,
>>>
>>>
>>> On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:
>>>
>>>> Hi, with a quick review, and many comments and points, I think the one single part that I would have some questions about is in the intro:
>>>>
>>>>    The guidance provided in
>>>>    this document is generic and can be used to inform the design of any
>>>>    protocol to be used anywhere in the world, without reference to
>>>>    specific legal frameworks.
>>>>
>>>>
>>>> Is that a goal?
>>> Yes, that's the goal.
>>>
>>> As you know, the IETF develops specifications that are used on the Internet and not just in a specific region. Trying to interpret national laws and to provide region-by-region specific guidance did not seem desirable to us.
>>>
>>>>   Do you feel you have reached providing such "Global Common" guidelines in the area of privacy?
>>> Yes, I think so and this document follows the spirit of RFC 3552 "Guidelines for Writing RFC Text on Security Considerations". This document is essentially the privacy version of what RFC 3552 is for security. If you look at RFC 3552 you will also fail to find references to regulation on security matters (even though they exist).
>>>
>>> We did look at many documents that seemed relevant input, such as the mentioned OECD document, and we spoke with data protection authorities and solicited their input. Our job would have been easier if we could have just re-used one of these documents listing the privacy principles. Unfortunately, it turns out that these documents were written for a different audience and that audience is supposed to have different capabilities regarding the design and the deployment of their services. In the IETF we do not have the same degree of freedom and impact and so we developed these guidelines to the best of our capabilities.
>>>
>>>>   How does it compare to US ECPA provisions for "User Expectations" which has served as a global model for other jurisdictions?
>>>> The reason I ask is because I have been very sensitive to ethical design and product liability issues in our product lines since 1986 following the guidelines set forth by the US ECPA for:
>>>>
>>>> - Thou shall not block/reject things without user knowledge,
>>>> - Thou shall not tamper/edit things especially when passing things (relays),
>>>> - Thou shall kept private things private.
>>>>
>>>> This was considered "Global" once upon a time.  Now its arguable.
>>> What is interesting for us to find out whether you believe that the Electronic Communications Privacy Act has for additional privacy aspects we need to address in the document.
>>> It is not our goal to interpret specific regulatory documents (even though it is interesting). This is the (well-paid) job of many lawyers.
>>>
>>> Ciao
>>> Hannes
>>>
>>>> --
>>>> HLS
>>>>
>>>> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>>>>> Hi SM,
>>>>>
>>>>> Thanks for your comments. Some responses are inline.
>>>>>
>>>>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>>>>
>>>>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>>>>> This is an announcement of an IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'.
>>>>>>>
>>>>>>> The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:
>>>>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>>>>> In Section 1:
>>>>>>
>>>>>>   'With regard to data, often it is a concept applied to
>>>>>>    "personal data," information relating to an identified or
>>>>>>    identifiable individual.'
>>>>>>
>>>>>> I suggest rewriting the above sentence.
>>>>> The authors have re-written that sentence several times and in different ways already. Do you have a specific suggestion about how to improve it?
>>>>>
>>>>>>   "Many sets of privacy principles and privacy design frameworks have been
>>>>>>    developed in different forums over the years."
>>>>>>
>>>>>> There is also some work in the APEC region (see http://publications.apec.org/publication-detail.php?pub_id=390 (payware)).
>>>>> As far as I know the APEC framework is one of many frameworks (none of which we cite since there are so many) based on the OECD-style FIPs. Is that incorrect?
>>>>>
>>>>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC 6772.
>>>>> Fixed.
>>>>>
>>>>>> I read some of the previous versions of this draft.  The Abstract Section describes the document as providing guidance for developing privacy considerations for inclusion in protocol specifications.  I found the draft difficult to digest.  I suggest simplifying the draft to make the guidance accessible to the target audience.
>>>>> I'm not quite sure what you are recommending here, but we have had conversations in the IAB privacy program about moving the guidance part up, or otherwise trying to make the focus on the guidance piece more prominent. The difficulty is that there is a broad range in the extent to which potential readers are familiar with privacy concepts, so jumping straight into the guidance would not be appropriate for some portion of the audience. If you have concrete suggestions for how to simplify, those would be helpful.
>>>>>
>>>>>> One of the issues nowadays is what to do about intermediaries.  If I am not mistaken RFC 3238 was one of the first documents to tackle that question from a privacy perspective.  There have been a few proposals to introduce intermediaries as part of the architecture (I am using the word is used loosely).  It is easy to argue for intermediaries based on use cases.  There was a case recently where the users only became aware that they have signed up for using an intermediary through the EULA.
>>>>>>
>>>>>> The draft introduces the concept of secondary use (Section 4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).
>>>>> Not all secondary uses involve disclosure (such as the example given in 4.2.3). I have added a sentence to clarify this, however:
>>>>>
>>>>> "Secondary use encompasses any use of data, including disclosure."
>>>>>
>>>>>> The draft mentions consent in several places.  The authors are likely aware that consent was a hot topic for DNT.  It's easier to start with something that is easy for the average person to understand and build from there.  Section 7.2 could more about consent instead of user participation or control.
>>>>> We tried to think of a case where a consent mechanism was actually developed in the IETF, but as a general matter consent mechanisms tend to be out of scope, which is why we focus more on user controls (which still show up rarely but do show up).
>>>>>
>>>>> Thanks,
>>>>> Alissa
>>>>>
>>>>>> Regards,
>>>>>> -sm
>>>>>>
>>>>>
>>
>>
>
>
>



From fred@cisco.com  Mon Feb 25 12:33:09 2013
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D98021F9205 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.401
X-Spam-Level: 
X-Spam-Status: No, score=-110.401 tagged_above=-999 required=5 tests=[AWL=0.198, 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 6HtMQxSfiOXS for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:33:08 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6099F21F8FD4 for <ietf@ietf.org>; Mon, 25 Feb 2013 12:33:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1565; q=dns/txt; s=iport; t=1361824388; x=1363033988; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LduxptX5nLOhrjhO5zH4NQxFnO+W/HMoNIYEWsZFrLQ=; b=cgf9gkGqtSkALEKxbG7PIHnePeBukpF6i2DsuzYd+WNJnEAH0mG0/FMf SPh0AEbYdnar51K2WzY+8xZQL/ZW4L1xQHZSBe6BtHXscEbFbPDfiESt9 Aj/OVfY3eV5JfTfE/FOjvVaIaWrB6adzd3fEmR1tn+yPWxqPZYX/AFjPR A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAP/JK1GtJV2c/2dsb2JhbABFwVmBBRZzgh8BAQEDATo/BQsCAQgiFBAyJQIEDgUIDId5Br97jlsCMQeCX2EDpyKDB4In
X-IronPort-AV: E=Sophos;i="4.84,736,1355097600"; d="scan'208";a="180774740"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP; 25 Feb 2013 20:33:04 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r1PKX4h2010527 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Feb 2013 20:33:04 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.206]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 14:33:04 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Showing support during IETF LC...
Thread-Topic: Showing support during IETF LC...
Thread-Index: AQHOEV8+19Hec0eFEE2s7rzNhYCn4ZiHep6AgABvBQCAA4bSgA==
Date: Mon, 25 Feb 2013 20:33:04 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B7A7571@xmb-rcd-x09.cisco.com>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com>
In-Reply-To: <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.119]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B1917D04F6C433469004FCC9EF13A124@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 20:33:09 -0000

On Feb 23, 2013, at 6:41 AM, John C Klensin <john-ietf@jck.com> wrote:

> First, "no objection" and silence by IESG members are roughly
> equivalent, but approval of a document with complete community
> silence (either outside the relevant WG or on an individual
> submission) makes some ADs nervous (and, IMO, should) and, in
> theory at least, would be subject to appeal on the grounds that
> there is no actual evidence of _community_ consensus.=20

For this reason, in a working group near me, when we put out a WGLC we expl=
icitly state that we are looking not only for objections, but for support. =
As a document shepherd, I will represent to the IESG that whatever document=
 I send them is in one of a few states:

1) we got tired of the document and kicked it in their general direction
2) there is a smallish group within the working group that actually cares a=
bout this, and they agree
3) a large fraction of the working group is in support of this

and of course, in any of those scenarios, there remains no pending issue th=
at has not been pummeled to death, either resulting in consensus language o=
r having a hold-out or two that is "in the rough".

I, as a chair, am thinking deeply about that right now. We just finished a =
working group last call on a document that has had tepid support in the wor=
king group for a while, and in WGLC had exactly two comments, both of which=
 expressed non-support. I don't think I can send it to the IESG in that sta=
te, because I can't make the indicated representation.=

From acooper@cdt.org  Mon Feb 25 12:35:39 2013
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 942DA21F9028 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.615
X-Spam-Level: 
X-Spam-Status: No, score=-102.615 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BGktdko30EvN for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:35:39 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 0210521F9036 for <ietf@ietf.org>; Mon, 25 Feb 2013 12:35:38 -0800 (PST)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)); Mon, 25 Feb 2013 15:35:35 -0500
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alissa Cooper <acooper@cdt.org>
In-Reply-To: <512BC8DE.6060606@isdg.net>
Date: Mon, 25 Feb 2013 15:35:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E4B68C3-B22C-47AD-A025-09842CBD7991@cdt.org>
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net> <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net> <512BC1BC.3000009@isdg.net> <EED5C632-6A8D-4AE9-9B5F-F15CF2F9196B@cdt.org> <512BC8DE.6060606@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1084)
Cc: SM <sm@resistor.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IAB IAB <iab@iab.org>, draft-iab-privacy-considerations@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, 25 Feb 2013 20:35:39 -0000

It is true that claims of ownership rights, whether over data or =
transmission mediums, can have an affect on privacy. But as you say, I'm =
not sure what concrete guidance we can give protocol developers and =
implementers about considering ownership, since decisions about who owns =
what or who will be claiming ownership over what are made essentially =
independently from any decision about protocol design. Furthermore, I =
imagine that there is some contention about presuming that recipients of =
personal data are the owners. I would certainly be wary of including =
that presumption here, as it leads down the slippery "rights vs. harms" =
slope pretty quickly, and we've managed to avoid that altogether in this =
document so far.

Alissa

On Feb 25, 2013, at 3:26 PM, Hector Santos wrote:

> Hi,  I would think both - ownership of the "things" and ownership of =
the medium moving, transporting, storing the "things."    Case in point: =
 I can write a protocol to move private data from point A to point B.  =
My first requirement is to make sure the design stipulates it stayed =
private, especially at the receiving end.  However, there is precedence =
where claims were made for ownership of the storage regardless of how =
temporary it may have been at the intermediary, a routed email for =
example.  Someone leverage a private email communications for their =
benefit by viewing the monitoring intermediate passthru transport data.  =
I'm not sure how such a document as this prevent this. It would be more =
about ethics I suppose, but if a protocol was to consider this, a =
designer may come up with ideas to prevent or minimize it or leverage it =
even more.
>=20
> On 2/25/2013 3:01 PM, Alissa Cooper wrote:
>> Hi Hector,
>>=20
>> Just to clarify, do you mean ownership of personal data? Or something =
else?
>>=20
>> Thanks,
>> Alissa
>>=20
>> On Feb 25, 2013, at 2:55 PM, Hector Santos wrote:
>>=20
>>> Hi,
>>>=20
>>> Related to your question, if it wasn't done already, I think there =
is one item to consider  or define - $Owner(s) and/or $Ownership. (I =
don't see any terms like owner, ownership in this document). The US ECPA =
has evolved with additional new laws, some as the "Good Samaritan" =
provisions, relaxations and also there has been new challenges and in my =
assessment it was primarily based on long adhered ownership principles. =
Just like employers enjoyed many US ECPA privacy exemptions, the =
Googles, Facebooks and other 3rd party service bureaus have also used =
"ownership" justify their leveraging of user data - "its our network and =
equipment...."
>>>=20
>>> I think the $intermediary term touches base, but i don't see it =
describe nor the $initiator being related to the owner of things.
>>>=20
>>> Ownership is very fundamental when we look at  the natural ethical =
design considerations, this should be one of the tenets of the document, =
in my view.  Recognized ownership has a very vital effect on what a =
protocol may|can|should offer or not offer as to not open Pandora's box.
>>>=20
>>> --
>>> HLS
>>>=20
>>> On 2/24/2013 2:23 PM, Hannes Tschofenig wrote:
>>>> Hi Hector,
>>>>=20
>>>>=20
>>>> On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:
>>>>=20
>>>>> Hi, with a quick review, and many comments and points, I think the =
one single part that I would have some questions about is in the intro:
>>>>>=20
>>>>>   The guidance provided in
>>>>>   this document is generic and can be used to inform the design of =
any
>>>>>   protocol to be used anywhere in the world, without reference to
>>>>>   specific legal frameworks.
>>>>>=20
>>>>>=20
>>>>> Is that a goal?
>>>> Yes, that's the goal.
>>>>=20
>>>> As you know, the IETF develops specifications that are used on the =
Internet and not just in a specific region. Trying to interpret national =
laws and to provide region-by-region specific guidance did not seem =
desirable to us.
>>>>=20
>>>>>  Do you feel you have reached providing such "Global Common" =
guidelines in the area of privacy?
>>>> Yes, I think so and this document follows the spirit of RFC 3552 =
"Guidelines for Writing RFC Text on Security Considerations". This =
document is essentially the privacy version of what RFC 3552 is for =
security. If you look at RFC 3552 you will also fail to find references =
to regulation on security matters (even though they exist).
>>>>=20
>>>> We did look at many documents that seemed relevant input, such as =
the mentioned OECD document, and we spoke with data protection =
authorities and solicited their input. Our job would have been easier if =
we could have just re-used one of these documents listing the privacy =
principles. Unfortunately, it turns out that these documents were =
written for a different audience and that audience is supposed to have =
different capabilities regarding the design and the deployment of their =
services. In the IETF we do not have the same degree of freedom and =
impact and so we developed these guidelines to the best of our =
capabilities.
>>>>=20
>>>>>  How does it compare to US ECPA provisions for "User Expectations" =
which has served as a global model for other jurisdictions?
>>>>> The reason I ask is because I have been very sensitive to ethical =
design and product liability issues in our product lines since 1986 =
following the guidelines set forth by the US ECPA for:
>>>>>=20
>>>>> - Thou shall not block/reject things without user knowledge,
>>>>> - Thou shall not tamper/edit things especially when passing things =
(relays),
>>>>> - Thou shall kept private things private.
>>>>>=20
>>>>> This was considered "Global" once upon a time.  Now its arguable.
>>>> What is interesting for us to find out whether you believe that the =
Electronic Communications Privacy Act has for additional privacy aspects =
we need to address in the document.
>>>> It is not our goal to interpret specific regulatory documents (even =
though it is interesting). This is the (well-paid) job of many lawyers.
>>>>=20
>>>> Ciao
>>>> Hannes
>>>>=20
>>>>> --
>>>>> HLS
>>>>>=20
>>>>> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>>>>>> Hi SM,
>>>>>>=20
>>>>>> Thanks for your comments. Some responses are inline.
>>>>>>=20
>>>>>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>>>>>=20
>>>>>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>>>>>> This is an announcement of an IETF-wide Call for Comment on =
'Privacy Considerations for Internet Protocols'.
>>>>>>>>=20
>>>>>>>> The document is being considered for publication as an =
Informational RFC within the IAB stream, and is available for inspection =
here:
>>>>>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>>>>>> In Section 1:
>>>>>>>=20
>>>>>>>  'With regard to data, often it is a concept applied to
>>>>>>>   "personal data," information relating to an identified or
>>>>>>>   identifiable individual.'
>>>>>>>=20
>>>>>>> I suggest rewriting the above sentence.
>>>>>> The authors have re-written that sentence several times and in =
different ways already. Do you have a specific suggestion about how to =
improve it?
>>>>>>=20
>>>>>>>  "Many sets of privacy principles and privacy design frameworks =
have been
>>>>>>>   developed in different forums over the years."
>>>>>>>=20
>>>>>>> There is also some work in the APEC region (see =
http://publications.apec.org/publication-detail.php?pub_id=3D390 =
(payware)).
>>>>>> As far as I know the APEC framework is one of many frameworks =
(none of which we cite since there are so many) based on the OECD-style =
FIPs. Is that incorrect?
>>>>>>=20
>>>>>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be =
RFC 6772.
>>>>>> Fixed.
>>>>>>=20
>>>>>>> I read some of the previous versions of this draft.  The =
Abstract Section describes the document as providing guidance for =
developing privacy considerations for inclusion in protocol =
specifications.  I found the draft difficult to digest.  I suggest =
simplifying the draft to make the guidance accessible to the target =
audience.
>>>>>> I'm not quite sure what you are recommending here, but we have =
had conversations in the IAB privacy program about moving the guidance =
part up, or otherwise trying to make the focus on the guidance piece =
more prominent. The difficulty is that there is a broad range in the =
extent to which potential readers are familiar with privacy concepts, so =
jumping straight into the guidance would not be appropriate for some =
portion of the audience. If you have concrete suggestions for how to =
simplify, those would be helpful.
>>>>>>=20
>>>>>>> One of the issues nowadays is what to do about intermediaries.  =
If I am not mistaken RFC 3238 was one of the first documents to tackle =
that question from a privacy perspective.  There have been a few =
proposals to introduce intermediaries as part of the architecture (I am =
using the word is used loosely).  It is easy to argue for intermediaries =
based on use cases.  There was a case recently where the users only =
became aware that they have signed up for using an intermediary through =
the EULA.
>>>>>>>=20
>>>>>>> The draft introduces the concept of secondary use (Section =
4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).
>>>>>> Not all secondary uses involve disclosure (such as the example =
given in 4.2.3). I have added a sentence to clarify this, however:
>>>>>>=20
>>>>>> "Secondary use encompasses any use of data, including =
disclosure."
>>>>>>=20
>>>>>>> The draft mentions consent in several places.  The authors are =
likely aware that consent was a hot topic for DNT.  It's easier to start =
with something that is easy for the average person to understand and =
build from there.  Section 7.2 could more about consent instead of user =
participation or control.
>>>>>> We tried to think of a case where a consent mechanism was =
actually developed in the IETF, but as a general matter consent =
mechanisms tend to be out of scope, which is why we focus more on user =
controls (which still show up rarely but do show up).
>>>>>>=20
>>>>>> Thanks,
>>>>>> Alissa
>>>>>>=20
>>>>>>> Regards,
>>>>>>> -sm
>>>>>>>=20
>>>>>>=20
>>>=20
>>>=20
>>=20
>>=20
>>=20
>=20
>=20
>=20



From dhc@dcrocker.net  Mon Feb 25 12:48:29 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 443EE21F88BD for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:48:29 -0800 (PST)
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 ApnbVs-0Y0NQ for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:48:28 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AF67121F885E for <ietf@ietf.org>; Mon, 25 Feb 2013 12:48:28 -0800 (PST)
Received: from [172.19.126.234] (64.125.189.90.t00817-23.above.net [64.125.189.90] (may be forged)) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r1PKmQxl027905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Feb 2013 12:48:27 -0800
Message-ID: <512BCE18.7000206@dcrocker.net>
Date: Mon, 25 Feb 2013 12:48:24 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>
Subject: Re: Showing support during IETF LC...
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net> <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com>
In-Reply-To: <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 25 Feb 2013 12:48:27 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 20:48:29 -0000

On 2/25/2013 11:16 AM, Mary Barnes wrote:
> On Mon, Feb 25, 2013 at 1:03 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
>> Agree with what John, Brian, and others have said. FWIW, at times - particularly with documents having some controversy - the ADs are left wondering what the silent majority is thinking. So in some cases the private messages to the AD in question or to the IESG are helpful. And while "+1" is usually bad form, indicating that you've done a thorough review and found no issues is appreciated. (Or better yet, that you intend to put this technology into your own use.)
> [MB] It's not clear to me why you think +1 is bad form.  I interpret
> +1 to mean that an individual agrees with the
> assessment/input/comments of the email to which they +1.

During an actual discussion, a +1 often conveys plenty of information.

During a Last Call, the core requirement is to establish the substance 
of benefits and concerns.  As such, pro forma statements are just too 
easy to assure informed support (or non-support.)  In this context, a +1 
is often more like voting and possibly can be like ballot-box stuffing...

IMO, during a Last Call, people need to say /why/ they are in favor or 
against and the why needs to be about the substance of functionality, 
performance, operations, and/or the like.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ynir@checkpoint.com  Mon Feb 25 12:51:07 2013
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB7221E80B3 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.571
X-Spam-Level: 
X-Spam-Status: No, score=-10.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 JSrRNxJTe90k for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 12:51:06 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7919321E809D for <ietf@ietf.org>; Mon, 25 Feb 2013 12:51:06 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r1PKp430020624; Mon, 25 Feb 2013 22:51:05 +0200
X-CheckPoint: {512BCED1-0-1B221DC2-2FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.54]) by DAG-EX10.ad.checkpoint.com ([169.254.3.95]) with mapi id 14.02.0342.003; Mon, 25 Feb 2013 22:51:04 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Showing support during IETF LC...
Thread-Topic: Showing support during IETF LC...
Thread-Index: AQHOEV88SRRe8gg6+0eBIipq0w77BJiG9IKAgABvBQCAA23sgIAAHeqA
Date: Mon, 25 Feb 2013 20:51:03 +0000
Message-ID: <4E275030-AACF-4265-9131-9C60AF631EED@checkpoint.com>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
In-Reply-To: <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.24.87]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A1F9FF2BE3531244A472AFCC39974FE5@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 20:51:08 -0000

Hi, Jari.

On Feb 25, 2013, at 9:03 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Agree with what John, Brian, and others have said. FWIW, at times - parti=
cularly with documents having some controversy - the ADs are left wondering=
 what the silent majority is thinking. So in some cases the private message=
s to the AD in question or to the IESG are helpful. And while "+1" is usual=
ly bad form, indicating that you've done a thorough review and found no iss=
ues is appreciated. (Or better yet, that you intend to put this technology =
into your own use.)

Finding issues is one goal of LC. So to go back to Warren's example of draf=
t-ietf-foo-dangerous-orangutangs, there of course is room for comments abou=
t why they spelled it Orangutan in the title, but Orangutang (with a g) in =
the abstract. And of course there's room for comments about why section 2 d=
oes not explain why DNSSEC would not protect web users from Orangutan(g)s.

But LC comments can also be about whether or not this is something that sho=
uld be done at all. Maybe some believe that the IETF should not be dealing =
with Orangutans at all because we have already standardized on chimps. Or m=
aybe ACME corporation has IPR on Orangutans and we should not deal with the=
m. There can even be a comment saying that nobody needs this and nobody's g=
oing to implement this (OK, the ape example kind of fails here).

It's because of this last kind of comment that we need to show support. "I =
think this is a good document" is not a helpful comment. "I think this docu=
ment will be useful for people implementing routing protocols" is. And if w=
e get some +1's on that comment especially from people who know about routi=
ng, this is useful. In this case we shouldn't be looking for consensus, or =
rather not just for consensus. We also need a community of people who need =
this document. And some explanations as to why this is a good idea, along w=
ith some +1s is an OK way to determine that there is a community.

Yoav


From barryleiba.mailing.lists@gmail.com  Mon Feb 25 13:53:38 2013
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9BCC21E80F0 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 13:53:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.952
X-Spam-Level: 
X-Spam-Status: No, score=-102.952 tagged_above=-999 required=5 tests=[AWL=0.025, 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 QpTS0tWLcGCT for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 13:53:38 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E102221E80C7 for <ietf@ietf.org>; Mon, 25 Feb 2013 13:53:37 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id l6so2035173vcl.31 for <ietf@ietf.org>; Mon, 25 Feb 2013 13:53:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=IQqvE8NACPL3VF9jMR9L6qrXFP3BDU0t2lQa+S3G34U=; b=LpvpewWBUf2cA5l097sxrBfYqIvIv7gOUL6vfebDZp0aE3kuqwDOGRx6jto8Xza162 GmFBbQe0Ru+oEUiWXoKeaWnSC8bF3MMqfm1O891zoK+NbgFkd8FKBNIhxTZ7gMaECRrT 7hPlGcP6o7gTQgyBDxNnl50ges9MGzweVWv+ZsS762NxIIRrsFrRwZunx6ZEb2b7lL81 cj70hF8nndYWT568RhLHAZrrRpqw4SKKT9dTuR8fdKsN1iMqPO6Ojy4GE9WHt89NyCgO hcPlwJ5wl2TtwgN8D85+APA7dyCNoSQyJhcnHw47qgHLK+fEyhBRgF3IJ/79Zu+fvZhD whGg==
MIME-Version: 1.0
X-Received: by 10.220.151.5 with SMTP id a5mr10594488vcw.22.1361829217311; Mon, 25 Feb 2013 13:53:37 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.59.3.41 with HTTP; Mon, 25 Feb 2013 13:53:37 -0800 (PST)
In-Reply-To: <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net>
Date: Mon, 25 Feb 2013 16:53:37 -0500
X-Google-Sender-Auth: -jYIFLndjOt19eeFBrwZ7qZ4UHM
Message-ID: <CAC4RtVDD6oXMAd=rdgjgJ8jvMTT-wLc2YfUFZyKB7F6Pb+RRxg@mail.gmail.com>
Subject: Re: Showing support during IETF LC...
From: Barry Leiba <barryleiba@computer.org>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 21:53:38 -0000

> Agree with what John, Brian, and others have said. FWIW, at times - particularly
> with documents having some controversy - the ADs are left wondering what the
> silent majority is thinking. So in some cases the private messages to the AD in
> question or to the IESG are helpful. And while "+1" is usually bad form, indicating
> that you've done a thorough review and found no issues is appreciated.

To go into a little detail on this point, let me talk about a
relatively recent document that came to the IESG as an AD-sponsored
item.  The document had, in its life of a few years, been offered to
at least two (i'm told three) working groups.  None of them objected
to it, but none of them wanted it, and, in the end, the author and the
sponsoring AD decided to go the AD-sponsored individual submission
route.

When I reviewed the document and its history, I found that, while it
had a bunch of comments about this or that working group not wanting
it, there was evidence of exactly two people, apart from the author
and AD, who had given it any *substantive* review and comment.  The
author discussed those comments and revised the document to address
them, so that was all fine.

I raised this as a question:
This is a document being approved in the IETF Stream, with boilerplate
that says it has IETF consensus:

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).

Does that document represent the consensus of the IETF community,
given that there was only evidence of substantive review from two
people outside the publication path?[1]

Now, perhaps... just perhaps... there were dozens of others who
reviewed it, thought it was perfectly fine and had no issues, and felt
they didn't need to say anything to that effect.  Perhaps all those
folks who said that they didn't think it should be adopted by the
working groups it was being offered to had given it very thorough
review, indeed, and found it to be an excellent document... just not
something they needed in their working groups.

That would have made a huge difference in my opinion of the level of
IETF consensus (and would have saved some cuts and bruises on the IESG
telechat).

Now, never mind any details of this particular document: the point is
that it's often useful to go on record somewhere, with someone, saying
that you've done a review, you have no issues (or agree with Ferd's
issue list, or whatever), and you're part of the consensus on the
document.  Whether those messages should be posted to the IETF list,
to the sponsoring AD, or elsewhere is a question I won't comment on.

Barry

[1] Arguably one, because one of the two was the document shepherd.
But in this case, the shepherd had reviewed it earlier, and could have
been asked to shepherd it because of that fact.  So I counted it as
two.

From joelja@bogus.com  Mon Feb 25 14:10:44 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 543F621F9134 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 14:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.522
X-Spam-Level: 
X-Spam-Status: No, score=-102.522 tagged_above=-999 required=5 tests=[AWL=0.077, 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 h+aeRM9HVWfh for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 14:10:43 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 93B9021F912F for <ietf@ietf.org>; Mon, 25 Feb 2013 14:10:43 -0800 (PST)
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 r1PMAfIC007541 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 25 Feb 2013 22:10:41 GMT (envelope-from joelja@bogus.com)
Message-ID: <512BE164.7070607@bogus.com>
Date: Mon, 25 Feb 2013 14:10:44 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Mary Barnes <mary.ietf.barnes@gmail.com>, IETF-Discussion list <ietf@ietf.org>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com>
In-Reply-To: <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 25 Feb 2013 22:10:41 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 22:10:44 -0000

On 2/25/13 10:36 AM, Mary Barnes wrote:
> In light of the upcoming meeting in Orlando, I have updated the
> document.  For folks that are not on the IETF-86 attendees list, we've
> had a fairly lengthy discussion about the remoteness of the venue and
> the lack of access to food other than the hotel restaurants that are
> often mediocre and over-priced.   For folks that aren't familiar, this
> document has recommendations for meeting planners and IAOC folks in
> terms of selecting venues that can ensure that IETF participants have
> access to the types of food they require during the meetings.   Lunch
> is often the biggest challenge due to frequent lunchtime meetings and
> the volume of people requiring lunch at the exact same time.
>
> I wrote this document right after the IETF meeting in Dublin (almost 5
> years ago) and given the Orlando venue selection (which occurred after
> the Dublin meeting) it does not seem to me that the requirements and
> recommendations in this document are being considered as serious input
> to that process.   While I am the most vocal with regards to this
> issue, it isn't just me - others just don't want to be the target for
> the types of discussions we inevitably have on this topic.
fwiw I generally support documents that encourage a consistent and 
repeatable approach to meeting requirements and which assigns 
responsibility to the participants as well, and I would probably support 
this document.

One observation though. The introduction:

   While much of the success of IETF protocols can be attributed to the
    availability of large cookies and readily available beer, there are
    some IETF participants for whom such items aren't compatible with
    dietary restrictions or the choice to eat a healthy diet.


A significant contributor to the complaints about breaks without snacks 
and indeed "cookies" is hypoglycemia and there the snack/cookie issue 
should be seen in that light. Big cookies is clearly a trope, in the 
context of plenary dicussion, but low blood sugar is not.

>    I will
> note that if we were discussing wheel chair accessibility to IETF
> meetings, most folks would understand the concern.  In the US, medical
> conditions that require special diets are considered hidden
> disabilities and the same legal requirements apply in terms of those
> diets being accommodated.   While IETF is a non-profit, my
> understanding is they have no legal requirements to provide the
> accommodations, one would expect such as part of the nature of IETF in
> terms of being an open and inclusive organization.
>
> I will note that there have definitely been improvements since Dublin,
> including the fruit bars when we have Ice Cream Thursdays and the
> secretariat always communicates requirements when they are made aware
> (e.g., WG chairs luncheon, as well as IAB stuff).  ISOC has also been
> accommodating for their Tuesday lunch sessions.   As an aside while
> I'm on the food topic, I didn't learn until last IETF that we don't
> have Ice Cream Thursdays unless someone sponsors it.  Since I was
> highly disappointed at the Atlanta meeting, I was able to get Polycom
> to sponsor the event at IETF-86 ;)
>
> At this stage, the feedback I would like related to this document is
> with regards it's readiness for publication as an RFC.  One of the
> updates to the document was with regards to the references to other
> IETF logistic documents (the Tao and the travel FAQ) which have since
> been published.  I believe this document is equally substantive and
> applicable to the IETF as those documents.
>
> Regards,
> Mary
>
>
> ---------- Forwarded message ----------
> From:  <internet-drafts@ietf.org>
> Date: Mon, Feb 25, 2013 at 12:18 PM
> Subject: I-D Action: draft-barnes-healthy-food-06.txt
> To: i-d-announce@ietf.org
>
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>
>
>          Title           : Healthy Food and Special Dietary
> Requirements for IETF meetings
>          Author(s)       : Mary Barnes
>          Filename        : draft-barnes-healthy-food-06.txt
>          Pages           : 18
>          Date            : 2013-02-25
>
> Abstract:
>     This document describes the basic requirements for food for folks
>     that attend IETF meetings require special diets, as well as those
>     that prefer to eat healthy.  While, the variety of special diets is
>     quite broad, the most general categories are described.  There can be
>     controversy as to what constitutes healthy eating, but there are some
>     common, generally available foods that comprise the basis for healthy
>     eating and special diets.  This document provides some
>     recommendations to meeting planners, as well as participants, in
>     handling these requirements.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-barnes-healthy-food
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-barnes-healthy-food-06
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-barnes-healthy-food-06
>
>
> 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 ed.lewis@neustar.biz  Mon Feb 25 14:27:35 2013
Return-Path: <ed.lewis@neustar.biz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E43821E8040 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 14:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.902
X-Spam-Level: 
X-Spam-Status: No, score=-100.902 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T6oCZOOPBtpp for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 14:27:34 -0800 (PST)
Received: from eastrmfepo203.cox.net (eastrmfepo203.cox.net [68.230.241.218]) by ietfa.amsl.com (Postfix) with ESMTP id 8559C21F8FB2 for <ietf@ietf.org>; Mon, 25 Feb 2013 14:27:34 -0800 (PST)
Received: from eastrmimpo209 ([68.230.241.224]) by eastrmfepo203.cox.net (InterMail vM.8.01.04.00 201-2260-137-20101110) with ESMTP id <20130225222734.HGAR21186.eastrmfepo203.cox.net@eastrmimpo209> for <ietf@ietf.org>; Mon, 25 Feb 2013 17:27:34 -0500
Received: from [127.0.0.1] ([68.98.141.167]) by eastrmimpo209 with cox id 4mTX1l00C3cuADQ01mTYka; Mon, 25 Feb 2013 17:27:34 -0500
X-CT-Class: Clean
X-CT-Score: 0.00
X-CT-RefID: str=0001.0A020204.512BE556.0012,ss=1,re=0.000,fgs=0
X-CT-Spam: 0
X-Authority-Analysis: v=2.0 cv=aIYuX8Bm c=1 sm=1 a=d1qrA6Qzssd1VjKW2xnq3A==:17 a=Nz4po29ivTsA:10 a=hGBaWAWWAAAA:8 a=fQxxqKK1ac4A:10 a=XMz4fRBIYauFWZZlbzgA:9 a=CjuIK1q_8ugA:10 a=9k6G2--EmesA:10 a=_W_S_7VecoQA:10 a=IVvN-queBXaZjq7k:21 a=d1qrA6Qzssd1VjKW2xnq3A==:117
X-CM-Score: 0.00
Authentication-Results: cox.net; none
Subject: Re: Showing support during IETF LC...
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C591687A-4F22-4631-A9A7-20296921F347"
From: Edward Lewis <ed.lewis@neustar.biz>
In-Reply-To: <20130223012937.GI63436@verdi>
Date: Tue, 26 Feb 2013 06:27:35 +0800
Message-Id: <6606B858-C9AD-48BC-8D15-14DBC88E5948@neustar.biz>
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <20130223012937.GI63436@verdi>
To: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
Cc: Edward Lewis <ed.lewis@neustar.biz>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 22:27:35 -0000

--Apple-Mail=_C591687A-4F22-4631-A9A7-20296921F347
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

=46rom an earlier message:

> >Miss Manners would almost certainly say that clogging the <ietf> list
> >with +1 is bad manners.


I have this scenario in mind:

A -12 comes out and I read it thoroughly and have about 10 points that =
need to be addressed.

So I respond to the document (not in last call) and all of the points =
are adequately (in my opinion) addressed.

A -13 is issued and sent to last call.

So - I shouldn't voice support?  Do I go down in the record as someone =
that had voiced concerns?  Or do I go down in the record as someone who =
supports the document?

At a recent address, Fadi Chehade (the new "head" of ICANN) spoke about =
the need for multi-stake holder input, that it was more important than =
expediency in going forward.  He was talking about ICANN, but his words =
apply to the IETF too.  What I took from his comments was (and this =
should be news to no one) that the goal is to produce documents that =
reflect as broad a consensus as possible, the goal is not to produce =
documents that lack complaints.

If only the whiners speak out, then all we get is the product of =
nitpicking.  So I believe that shows of support ("+1's) are important, =
as well as confirmation that comments raised (against a -12) are =
addressed (in a -13).

BTW, the -13, -12 and +1's are on different scales, different units, ... =
uh, never mind, it seemed funny at the time.

=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
Edward Lewis            =20
NeuStar                    You can leave a voice message at =
+1-571-434-5468

There are no answers - just tradeoffs, decisions, and responses.


--Apple-Mail=_C591687A-4F22-4631-A9A7-20296921F347
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>=46rom an earlier message:</div><div><br><blockquote =
type=3D"cite"><div>&gt;Miss Manners would almost certainly say that =
clogging the &lt;ietf&gt; list</div><div>&gt;with +1 is bad =
manners.</div></blockquote></div><div><br></div><div>I have this =
scenario in mind:</div><div><br></div><div>A -12 comes out and I read it =
thoroughly and have about 10 points that need to be =
addressed.</div><div><br></div><div>So I respond to the document (not in =
last call) and all of the points are adequately (in my opinion) =
addressed.</div><div><br></div><div>A -13 is issued and sent to last =
call.</div><div><br></div><div>So - I shouldn't voice support? &nbsp;Do =
I go down in the record as someone that had voiced concerns? &nbsp;Or do =
I go down in the record as someone who supports the =
document?</div><div><br></div><div>At a recent address, Fadi Chehade =
(the new "head" of ICANN) spoke about the need for multi-stake holder =
input, that it was more important than expediency in going forward. =
&nbsp;He was talking about ICANN, but his words apply to the IETF too. =
&nbsp;What I took from his comments was (and this should be news to no =
one) that the goal is to produce&nbsp;documents that reflect as broad a =
consensus as possible, the goal is&nbsp;not to produce documents that =
lack complaints.</div><div><br></div><div>If only the whiners speak out, =
then all we get is the product of nitpicking. &nbsp;So I believe that =
shows of support ("+1's) are important, as well as confirmation that =
comments raised (against a -12) are addressed (in a =
-13).</div><div><br></div><div>BTW, the -13, -12 and +1's are on =
different scales, different units, ... uh, never mind, it seemed funny =
at the time.</div><br><div>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; =
">-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D=
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D<span></sp=
an>-=3D-=3D-=3D-<span class=3D"Apple-style-span" style=3D"border-collapse:=
 separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>Edward =
Lewis&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span></s=
pan>&nbsp;&nbsp;&nbsp;<br>NeuStar&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;<span></span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp; You can leave a voice message at =
+1-571-434-5468<br><br>There are no answers - just tradeoffs, decisions, =
and responses.</div></div></div></span></span>
</div>
<br></body></html>=

--Apple-Mail=_C591687A-4F22-4631-A9A7-20296921F347--

From randy@psg.com  Mon Feb 25 15:01:15 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95C021E8131 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEfQeFSW3run for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:01:14 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id ECDC821E8143 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:00:56 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UA72S-000P2e-If; Mon, 25 Feb 2013 23:00:53 +0000
Date: Tue, 26 Feb 2013 07:00:50 +0800
Message-ID: <m2r4k4c82l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: IETF chair's blog
In-Reply-To: <512B827F.4060406@acm.org>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org> <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de> <512B827F.4060406@acm.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:01:15 -0000

> For me the most important point is that it is managed on IETF (or
> IETF's contractor) servers.

as no private data are involved, i am curious why?

randy

From ietf@thomasclausen.org  Mon Feb 25 15:02:07 2013
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53FF21E80FE; Mon, 25 Feb 2013 15:02:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.369
X-Spam-Level: 
X-Spam-Status: No, score=-0.369 tagged_above=-999 required=5 tests=[AWL=-0.099, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_23=0.6, 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 C4U1FOehEAlJ; Mon, 25 Feb 2013 15:02:07 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id D6EF321E8129; Mon, 25 Feb 2013 15:01:13 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 8AB10A363C; Mon, 25 Feb 2013 15:01:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 2338C1C9F40; Mon, 25 Feb 2013 15:01:12 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.137] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id A3A2E1C6E8E; Mon, 25 Feb 2013 15:01:09 -0800 (PST)
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com> <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com> <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BFFD20F-58D8-4118-9F81-EF760A6DDB3A@thomasclausen.org>
X-Mailer: iPad Mail (10B141)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
Date: Tue, 26 Feb 2013 00:01:07 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: "draft-cardenas-dff@tools.ietf.org" <draft-cardenas-dff@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:02:07 -0000

Note, I am not an author of this particular document, but I've got some expe=
rimental and operational experience with it - having implemented DFF and bui=
lt deployments including it.

On 25 f=C3=A9vr. 2013, at 06:59, Abdussalam Baryun <abdussalambaryun@gmail.c=
om> wrote:

> Reply to your request dated 07/02/2013
> Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 24/02/2013
>=20
> Reviewer Comment #AB3: Related to Processing and interaction with others.
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>=20
> In section 11
> AB>The DFF MUST contain the next hop of RIB, but in section 5 it mentions M=
AY.
> AB>suggest> please amend both should be same requirement for protocol.
>=20
> AB> the way it determines the next hop does not show that this
> protocol is sensitive to other parameters in the RIB, it just takes
> the addresses without considering the routing protocol strategy in its
> RIB. IMHO, this may make the DFF make mistakes in taking the right
> next hop

What you say above doesn't make any sense. DFF considers the content of the R=
IB, among other information, and recommends following the "next hop" indicat=
ed in the RIB first - i.e., DFF explicitly takes the "right next hop" accord=
ing to "the routing protocol strategy" as expressed in the RIB.

Of course, if you happen to know more about what the routing protocol does (=
e.g., have access to internal state of the routing protocol), you could do s=
omething more clever - DFF doesn't prohibit that either, so I think that the=
 authors struck a nice middle ground here.

> Section 12
> AB> is not understood, it seems a general not specific, I suggest more
> explaining how this interaction with routing protocol is occured?

It seems pretty clear to me what's expected here: signal to the routing prot=
ocol (and then, whatever the routing protocol does with that signal depends o=
n what routing protocol it is).

It's, IMO, hard to be any clearer here.


> Section 13
> AB> who creates the sequence number is it the DFF or the routing
> protocol. It seems the DFF, so please specify how it will
> maintain/save such sequence number in this section.
> AB> suggest this section to be : DFF Sequence Number.
>=20

[befuddled]=20

Section 13 is already very clear on this.

> Section 14
> AB> again do you mean that both modes can work together. I don't think
> that you mean that, so you should specify that each routing domain
> MUST have one mode, and specify how to maintain that mode in such
> protocol.

Eh, here too I am befuddled. I do not see anywhere that the authors indicate=
 that the two "modes can work together" - actually, the document doesn't tal=
k about "modes" at all, and  the protocol doesn't have "modes".

Rather, this section describes how one would use DFF, depending on what othe=
r choices are made in the network deployment. In other words: DFF doesn't sp=
ecify a "mode", but rather says "if your network is of this kind, then do li=
ke that".

So, I think that there's strictly nothing to change here, no need to maintai=
n a "mode" etc.

> Overall> about processing>
> AB> this protocol needs to be discussed more how it will interact with
> the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore
> alot of work done in the IETF which is not fiting the general
> applicability it is offering.

No, it doesn't.

DFF is completely orthogonal to routing protocols

DFF can (logically) layer below any routing protocol, without modifications t=
o that routing protocol.=20

DFF can use a RIB and can provide signals to a routing protocol (or not - if=
 the routing protocol doesn't want them)

Thomas

> +++++++++++++The END+++++++++++
>=20
> Regards
> AB
> --------------------------------------------------------------------------=
-------------
> This message and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> This message is in compliance with the IETF regulations.
> --------------------------------------------------------------------------=
-------------
>=20
>=20
>>> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>>>>=20
>>>> The IESG has received a request from an individual submitter to conside=
r
>>>> the following document:
>>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>>>>  <draft-cardenas-dff-09.txt> as Experimental RFC
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and solicits
>>>> final comments on this action. Please send substantive comments to the
>>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments may
>>>> be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>=20
>>>>   This document specifies the "Depth-First Forwarding" (DFF) protocol
>>>>   for IPv6 networks, a data forwarding mechanism that can increase
>>>>   reliability of data delivery in networks with dynamic topology and/or=

>>>>   lossy links.  The protocol operates entirely on the forwarding plane,=

>>>>   but may interact with the routing plane.  DFF forwards data packets
>>>>   using a mechanism similar to a "depth-first search" for the
>>>>   destination of a packet.  The routing plane may be informed of
>>>>   failures to deliver a packet or loops.  This document specifies the
>>>>   DFF mechanism both for IPv6 networks (as specified in RFC2460) and in=

>>>>   addition also for LoWPAN "mesh-under" networks (as specified in
>>>>   RFC4944).
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>>>>=20
>>>>=20
>>>> The following IPR Declarations may be related to this I-D:
>>>>=20
>>>>   http://datatracker.ietf.org/ipr/1645/
>>>>   http://datatracker.ietf.org/ipr/1646/
>>=20

From sm@resistor.net  Mon Feb 25 15:17:07 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD12621F9527 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id psjlD3QN-4XB for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:17:06 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DC74521F9362 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:17:05 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1PNGwnV001844; Mon, 25 Feb 2013 15:17:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361834222; bh=UPDuwWU/oj4yvlNVDtiNSxtuvhczrpUnGPdDLvRhI2I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=FRjsNfeFwGETODXD5V7LZViXyFUeCQAgxO+dyhPryriRBl4tysj7N9ubstboWqH85 16X9lEUemudmzkTzXQYqDps7+vY+8P2J4xarsnaHvKHeVuldQ5GQZSDCM+ACMzfLNU mMjknQx8Hs3E1BQVnv2P25kLMFeR0TUKJsNIPDdc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361834222; i=@resistor.net; bh=UPDuwWU/oj4yvlNVDtiNSxtuvhczrpUnGPdDLvRhI2I=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=z920n8xqQ0kIpUOg2zn2zbnK3plIdENE09mUnPIO0bM6HseTvf7QY9jHVZKXb4UQ9 pSuC4vT+FYoGk8QfEduHBX4YRCF6SsIWP2AiAGSW8lxd8jixS5saWVBCEXk+eYv+A6 tjQjDCh92TdstUpfMopGjI/jE4TRBuyBuLzLZyG0=
Message-Id: <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Feb 2013 15:03:02 -0800
To: Mary Barnes <mary.ietf.barnes@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
In-Reply-To: <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.g mail.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:17:07 -0000

Hi Mary,
At 10:36 25-02-2013, Mary Barnes wrote:
>have Ice Cream Thursdays unless someone sponsors it.  Since I was
>highly disappointed at the Atlanta meeting, I was able to get Polycom
>to sponsor the event at IETF-86 ;)

This is ample motivation for me to support the draft. :-)

>At this stage, the feedback I would like related to this document is
>with regards it's readiness for publication as an RFC.  One of the

It better to decide whether to publish now (Last Call) then to wait 
another five years.

In Section 4:

  "A wide range of research has shown that about 10% of the population
   prefer to eat a healthy diet."

Can I have some references for that?

  "Thus, it is estimated that at least 10 percent of the IETF
   participants would take advantage of healthy food offerings."

Based on the previous sentence, the above could be read as at least 
10 percent of IETF participants are educated. :-)

   "There are laws in many countries and jurisdictions (e.g.,U.S., E.U.)
    that make it illegal to mislabel foods that are Halal or Kosher.  At
    this time, food manufacturers in many jusisdictions (e.g.,U.S., U.K,
    E.U.) must include all ingredients on the labels of any packaged food
    product."

The "must" was violated ( 
http://ec.europa.eu/ireland/press_office/news_of_the_day/horse-meat-food-labelling-plan_en.htm 
).

In Section 5:

   "For cases of first time attendees for a specific location, relevant
    information can be gathered from attendees that have previously
    visited the city."

There are recurrent discussions as nobody volunteered to gather that 
information in one place.

In Section 8:

   "One can never assume that everything has been taken care of by
    someone else."

I suggest moving that to the security considerations section.

I suggest having the draft make recommendations instead of setting 
requirements.  Some of the items in Section 7 "might" be things the 
IETF can do; some of the items are for other parties.  It would be 
easier if the two sets are kept separate.  I suggest moving the 
History stuff to an appendix (e.g. "The Cornucopia restaurant in 
Dublin [cornucopia] is a perfect example of how this can be done in 
an extremely cost-effective efficient and gastronomically appealing 
manner".  I suggest avoiding stuff like "American Disabilities 
Act".  It would be better to formulate the draft in terms of an 
international audience.

Regards,
-sm


From ben@nostrum.com  Mon Feb 25 15:28:14 2013
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EAF21E8148; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.262
X-Spam-Level: 
X-Spam-Status: No, score=-102.262 tagged_above=-999 required=5 tests=[AWL=-0.262, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, 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 R8IUlHnP2EKc; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
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 27DDC21E8128; Mon, 25 Feb 2013 15:28:14 -0800 (PST)
Received: from vpn-cust-10-119-74-38.witopia.net (69.147.243.203.rdns.ubiquityservers.com [69.147.243.203] (may be forged)) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id r1PNSDGb082966 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 25 Feb 2013 17:28:13 -0600 (CST) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC/Telechat review of draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04
Date: Mon, 25 Feb 2013 17:28:06 -0600
Message-Id: <03EE5FB0-F0D0-481D-99F9-1D45568C0AC5@nostrum.com>
To: draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (shaman.nostrum.com: 69.147.243.203 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: Mon, 25 Feb 2013 23:28:14 -0000

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

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

Document:  draft-ietf-dhc-dhcpv6-client-link-layer-addr-opt-04
Reviewer: Ben Campbell
Review Date: 2013-02-25
IETF LC End Date: 2013-02-28
IESG Telechat date: 2013-02-28

Summary: Ready for publication as a proposed standard

Major issues:

None

Minor issues:

None

Nits/editorial comments:

-- Header:

I ca't help but enjoy the fact that the file name is longer than the =
draft title :-)  (No change needed)

-- section 2, last paragraph:

s/"For e.g."/"For example,"  =20



From petithug@acm.org  Mon Feb 25 15:28:45 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B7D21F948D for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level: 
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.039, 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 xwbUgNEet7PS for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:28:44 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 79ACD21E8128 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:28:38 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476] (unknown [IPv6:2601:9:4b80:32:69cb:6b3f:dfaa:1476]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 6397A20515; Mon, 25 Feb 2013 23:28:37 +0000 (UTC)
Message-ID: <512BF3A7.3020903@acm.org>
Date: Mon, 25 Feb 2013 15:28:39 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org> <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de> <512B827F.4060406@acm.org> <m2r4k4c82l.wl%randy@psg.com>
In-Reply-To: <m2r4k4c82l.wl%randy@psg.com>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:28:45 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/25/2013 03:00 PM, Randy Bush wrote:
>> For me the most important point is that it is managed on IETF (or IETF's
>> contractor) servers.
> 
> as no private data are involved, i am curious why?
> 

Because public does not mean unlimited availability.  Let's say that the IETF
decides to use a collaboration tool hosted by a service run by an external
company.  The data is public (although it can be stored in a proprietary
format) so anybody can consult it.  But suddenly the service is
bankrupted/become collateral damage when servers are seized/has its
certificates expiring/etc...  Unless someone did some preventive data
liberation, the data is no longer available, at least until whatever caused
the problem is solved.

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRK/OkAAoJECnERZXWan7EP/gQAK+bhwya94XYiAXwvwlR5bTX
ejSRx7Z8OhE25ggkNOBmY/zaRNyfmFSxmPGlEMWrMjDd/3n761NjyOHnHksNyqT4
WVUbPwIy0fFKPwVsWp6YzrmrmuFkwL3NOGjgBRXQuO1N0dLj42yk1NbSrqxfSzXx
wiUCu+U3ucCD7F5aNg3tZh+6BNMCbFjjk9KKrylxfRtg0x1lJjNuPkXUhIsyQLer
fwqeRAzZhFBT5xo1Nr0lijb6Eu1rYZjaMESQTPs8IquDI0FLrxLvwyiO7wCK7s5Y
b21qN+/yZaxxqgbv3om0gRwWx7r2MZshZD5TXGE7XiUfiTHkp7tgP/ymnh9U2t39
JcnXocng470JfewJk1+zBzrfriTGSpaSK0RpDRd+Ft/KLT4J5iBoD2/5AR3PCWwM
nHiab1UqdKEsyMuNEEPSA7xaM0N401IRVePaVv7Woo7YtbrEKmXCwwqQERy2hgqJ
W4RSIg8BrI1FTztkRFWrvYZYhU7nIiQY9lxBW7Un84aWeS78TS6ePPfDmVPjPk2e
GAV9DQw6yf21hdiHwP0slHeKrcSYA/sNu1vq7f8j1+ympJrqvA6b7/kZzCRx8YNI
NYYgEvp4Z8ISCzyIOr16L6M7zs0yAwDHRxCU22tjMIq3GH33nKWpDjIw/RU9sekX
/1LePxXi9Xs+mZLAa0KO
=7oou
-----END PGP SIGNATURE-----

From mary.ietf.barnes@gmail.com  Mon Feb 25 15:51:14 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E40921E81AC for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:51:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UiZVfIBnPLox for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:51:12 -0800 (PST)
Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) by ietfa.amsl.com (Postfix) with ESMTP id 2150C21E81A5 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:51:11 -0800 (PST)
Received: by mail-qe0-f54.google.com with SMTP id k5so1854119qej.41 for <ietf@ietf.org>; Mon, 25 Feb 2013 15:51:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=2WYd5icjKcZtBTL7R9ZMJ7vsMXXY6RSUycl635JqeXE=; b=wclhWxCI2WxV65dm6Rdu7EqjMZouvz88XMb9RMdv6w5PNs3UaxFDO+2piGwUQ7Otlc aRcv66EXrhjJg2W/K+pgKmwJ0usWT8IwBXpHF8ZBDwAwZJ5k04vN2MoJiCNj1KCDdv6B YcNJfa/pBqZpHlbUTSUiF7u3WJY6k/eNYgwHlJBsiI/vZiA9m6ZAX2Rk2HNkTKp9I3EK BJpnMBk0MHKaqxtRtb8FfcJtWM9Qu3UMYmiuHndf3OGvnxyWauBsyfgelo+U1jb0CyEw 0tujJNWA0Jb8Kv+kU3TQYf5LpMqTSn2T7PXksEb1LJpAMShgxBz6VXWhA4R9mDrK4GE+ gNQg==
MIME-Version: 1.0
X-Received: by 10.229.201.200 with SMTP id fb8mr3403041qcb.122.1361836263587;  Mon, 25 Feb 2013 15:51:03 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Mon, 25 Feb 2013 15:51:03 -0800 (PST)
In-Reply-To: <512BE164.7070607@bogus.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <512BE164.7070607@bogus.com>
Date: Mon, 25 Feb 2013 17:51:03 -0600
Message-ID: <CAHBDyN7S63fhGDd+yhqyejKm+fCZR-TR0j0brpMafSQSg3k3Jw@mail.gmail.com>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Feb 2013 23:51:14 -0000

On Mon, Feb 25, 2013 at 4:10 PM, joel jaeggli <joelja@bogus.com> wrote:
> On 2/25/13 10:36 AM, Mary Barnes wrote:
>>
>> In light of the upcoming meeting in Orlando, I have updated the
>> document.  For folks that are not on the IETF-86 attendees list, we've
>> had a fairly lengthy discussion about the remoteness of the venue and
>> the lack of access to food other than the hotel restaurants that are
>> often mediocre and over-priced.   For folks that aren't familiar, this
>> document has recommendations for meeting planners and IAOC folks in
>> terms of selecting venues that can ensure that IETF participants have
>> access to the types of food they require during the meetings.   Lunch
>> is often the biggest challenge due to frequent lunchtime meetings and
>> the volume of people requiring lunch at the exact same time.
>>
>> I wrote this document right after the IETF meeting in Dublin (almost 5
>> years ago) and given the Orlando venue selection (which occurred after
>> the Dublin meeting) it does not seem to me that the requirements and
>> recommendations in this document are being considered as serious input
>> to that process.   While I am the most vocal with regards to this
>> issue, it isn't just me - others just don't want to be the target for
>> the types of discussions we inevitably have on this topic.
>
> fwiw I generally support documents that encourage a consistent and
> repeatable approach to meeting requirements and which assigns responsibility
> to the participants as well, and I would probably support this document.
>
> One observation though. The introduction:
>
>   While much of the success of IETF protocols can be attributed to the
>    availability of large cookies and readily available beer, there are
>    some IETF participants for whom such items aren't compatible with
>    dietary restrictions or the choice to eat a healthy diet.
>
>
> A significant contributor to the complaints about breaks without snacks and
> indeed "cookies" is hypoglycemia and there the snack/cookie issue should be
> seen in that light. Big cookies is clearly a trope, in the context of
> plenary dicussion, but low blood sugar is not.
[MB]  Cookies, like any processed carbohydrates, are a poor food
choice for folks that have blood sugar issues (you can find the
research on this in pubmed).  A low carb diet is a significantly
better choice if one has difficulty stabilizing blood sugar.
Certainly, once you reach the hypoglycemic point you do need carbs
immediately but something like fruit juice or even better chocolate
milk (since it has some protein) is a much better choice for that
situation than a cookie.  Eating a cookie will just cause the cycle to
repeat until you do get real food into your system.   So, avoiding
processed carbs in lieu of fresh vegetables and fruit along with
protein such as peanut butter, nuts or cheese can reduce the incidence
of hypoglycemia.   Fortunately, some of the venues have had the veggie
trays during breaks and that's great as it does give us some options.
Since I do have issues with hypoglycemia, I must eat frequently and I
always have safe and appropriate snacks with me to tide me over -
again, nuts or high protein snack bars work really well in this
situation.  And, I regularly smuggle them in (packaged) to countries
that don't want you bringing in any food.  I will have a *big* issue
if we travel to a country and they get confiscated.  From a practical
perspective, given that the hotels likely charge $3.00/cookie, IETF
could buy cases of quality vegan, kosher, gluten-free snack bars for
the same price.  Of course that gets into some of the issues I
highlight with regards to these hotels not allowing outside food.
[/MB]
>
>
>>    I will
>> note that if we were discussing wheel chair accessibility to IETF
>> meetings, most folks would understand the concern.  In the US, medical
>> conditions that require special diets are considered hidden
>> disabilities and the same legal requirements apply in terms of those
>> diets being accommodated.   While IETF is a non-profit, my
>> understanding is they have no legal requirements to provide the
>> accommodations, one would expect such as part of the nature of IETF in
>> terms of being an open and inclusive organization.
>>
>> I will note that there have definitely been improvements since Dublin,
>> including the fruit bars when we have Ice Cream Thursdays and the
>> secretariat always communicates requirements when they are made aware
>> (e.g., WG chairs luncheon, as well as IAB stuff).  ISOC has also been
>> accommodating for their Tuesday lunch sessions.   As an aside while
>> I'm on the food topic, I didn't learn until last IETF that we don't
>> have Ice Cream Thursdays unless someone sponsors it.  Since I was
>> highly disappointed at the Atlanta meeting, I was able to get Polycom
>> to sponsor the event at IETF-86 ;)
>>
>> At this stage, the feedback I would like related to this document is
>> with regards it's readiness for publication as an RFC.  One of the
>> updates to the document was with regards to the references to other
>> IETF logistic documents (the Tao and the travel FAQ) which have since
>> been published.  I believe this document is equally substantive and
>> applicable to the IETF as those documents.
>>
>> Regards,
>> Mary
>>
>>
>> ---------- Forwarded message ----------
>> From:  <internet-drafts@ietf.org>
>> Date: Mon, Feb 25, 2013 at 12:18 PM
>> Subject: I-D Action: draft-barnes-healthy-food-06.txt
>> To: i-d-announce@ietf.org
>>
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>>
>>
>>          Title           : Healthy Food and Special Dietary
>> Requirements for IETF meetings
>>          Author(s)       : Mary Barnes
>>          Filename        : draft-barnes-healthy-food-06.txt
>>          Pages           : 18
>>          Date            : 2013-02-25
>>
>> Abstract:
>>     This document describes the basic requirements for food for folks
>>     that attend IETF meetings require special diets, as well as those
>>     that prefer to eat healthy.  While, the variety of special diets is
>>     quite broad, the most general categories are described.  There can be
>>     controversy as to what constitutes healthy eating, but there are some
>>     common, generally available foods that comprise the basis for healthy
>>     eating and special diets.  This document provides some
>>     recommendations to meeting planners, as well as participants, in
>>     handling these requirements.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-barnes-healthy-food
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-barnes-healthy-food-06
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-barnes-healthy-food-06
>>
>>
>> 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 hsantos@isdg.net  Mon Feb 25 15:53:17 2013
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501B321E81B1 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.371
X-Spam-Level: 
X-Spam-Status: No, score=-102.371 tagged_above=-999 required=5 tests=[AWL=0.228, 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 MxJzbFVy5jEM for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 15:53:14 -0800 (PST)
Received: from ntbbs.winserver.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id B8B6721E818A for <ietf@ietf.org>; Mon, 25 Feb 2013 15:53:11 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=10915; t=1361836388; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=l57sBW0 VFcFBaALiM3mN/WUG+5g=; b=JR5wW9pne2mSwrt7P9S6BvjHWKU5jYSwR4gF3qm tB8b0WXcjc2um+jz2WYIfeMeUkVrX8zHjl+fuSS6Av7JwJ70/GcU9RhdqvirpqU2 S7IwX75gIRCbBkDtNZdtYkZmJSCzTIDZQ2I5bmSGvaBJLPracX/K8JtLlNEAFOCY oPo4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 25 Feb 2013 18:53:08 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 630135181.1761.3124; Mon, 25 Feb 2013 18:53:07 -0500
Message-ID: <512BF8F1.9080803@isdg.net>
Date: Mon, 25 Feb 2013 18:51:13 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: Alissa Cooper <acooper@cdt.org>
Subject: Re: [IAB] Call for Comment: 'Privacy Considerations for Internet Protocols'
References: <669123F2-8F12-4C46-956D-C4A12B5363D4@iab.org> <6.2.5.6.2.20130130143748.09bc0140@resistor.net> <56F8F5B5-89A9-4E49-8449-CC03AF38E0AD@cdt.org> <51291DC9.7050404@isdg.net> <F1119762-D5A4-4B01-983E-790F23E78228@gmx.net> <512BC1BC.3000009@isdg.net> <EED5C632-6A8D-4AE9-9B5F-F15CF2F9196B@cdt.org> <512BC8DE.6060606@isdg.net> <0E4B68C3-B22C-47AD-A025-09842CBD7991@cdt.org>
In-Reply-To: <0E4B68C3-B22C-47AD-A025-09842CBD7991@cdt.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IAB IAB <iab@iab.org>, draft-iab-privacy-considerations@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, 25 Feb 2013 23:53:17 -0000

Hi. I agree it is complex. Maybe your comments should be incorporated 
into the doc rather than ignore the topic.  I suggest the ideas of 
ownership can be conveyed into the other terms already defined, i.e. the 
$Attacker or $Eavesdropper can only be considered with these litigious 
profile only because they aren't "owners." These two terms were properly 
provided with negative connotations where the $observer was provided 
with positive connotations.  It describes some form of authorization is 
possible abeit from someone - an "owner?" The $initiator is the only 
entity that can be provided with ownership connotations.  Since this is 
not necessarily the case, all these terms can be different entities from 
a possible proposed $Owner entity.  I think it can be described while 
still keeping away from any "slippery slope."

Thanks

--
HLS




On 2/25/2013 3:35 PM, Alissa Cooper wrote:
> It is true that claims of ownership rights, whether over data or transmission mediums, can have an affect on privacy. But as you say, I'm not sure what concrete guidance we can give protocol developers and implementers about considering ownership, since decisions about who owns what or who will be claiming ownership over what are made essentially independently from any decision about protocol design. Furthermore, I imagine that there is some contention about presuming that recipients of personal data are the owners. I would certainly be wary of including that presumption here, as it leads down the slippery "rights vs. harms" slope pretty quickly, and we've managed to avoid that altogether in this document so far.
>
> Alissa
>
> On Feb 25, 2013, at 3:26 PM, Hector Santos wrote:
>
>> Hi,  I would think both - ownership of the "things" and ownership of the medium moving, transporting, storing the "things."    Case in point:  I can write a protocol to move private data from point A to point B.  My first requirement is to make sure the design stipulates it stayed private, especially at the receiving end.  However, there is precedence where claims were made for ownership of the storage regardless of how temporary it may have been at the intermediary, a routed email for example.  Someone leverage a private email communications for their benefit by viewing the monitoring intermediate passthru transport data.  I'm not sure how such a document as this prevent this. It would be more about ethics I suppose, but if a protocol was to consider this, a designer may come up with ideas to prevent or minimize it or leverage it even more.
>>
>> On 2/25/2013 3:01 PM, Alissa Cooper wrote:
>>> Hi Hector,
>>>
>>> Just to clarify, do you mean ownership of personal data? Or something else?
>>>
>>> Thanks,
>>> Alissa
>>>
>>> On Feb 25, 2013, at 2:55 PM, Hector Santos wrote:
>>>
>>>> Hi,
>>>>
>>>> Related to your question, if it wasn't done already, I think there is one item to consider  or define - $Owner(s) and/or $Ownership. (I don't see any terms like owner, ownership in this document). The US ECPA has evolved with additional new laws, some as the "Good Samaritan" provisions, relaxations and also there has been new challenges and in my assessment it was primarily based on long adhered ownership principles. Just like employers enjoyed many US ECPA privacy exemptions, the Googles, Facebooks and other 3rd party service bureaus have also used "ownership" justify their leveraging of user data - "its our network and equipment...."
>>>>
>>>> I think the $intermediary term touches base, but i don't see it describe nor the $initiator being related to the owner of things.
>>>>
>>>> Ownership is very fundamental when we look at  the natural ethical design considerations, this should be one of the tenets of the document, in my view.  Recognized ownership has a very vital effect on what a protocol may|can|should offer or not offer as to not open Pandora's box.
>>>>
>>>> --
>>>> HLS
>>>>
>>>> On 2/24/2013 2:23 PM, Hannes Tschofenig wrote:
>>>>> Hi Hector,
>>>>>
>>>>>
>>>>> On Feb 23, 2013, at 9:51 PM, Hector Santos wrote:
>>>>>
>>>>>> Hi, with a quick review, and many comments and points, I think the one single part that I would have some questions about is in the intro:
>>>>>>
>>>>>>    The guidance provided in
>>>>>>    this document is generic and can be used to inform the design of any
>>>>>>    protocol to be used anywhere in the world, without reference to
>>>>>>    specific legal frameworks.
>>>>>>
>>>>>>
>>>>>> Is that a goal?
>>>>> Yes, that's the goal.
>>>>>
>>>>> As you know, the IETF develops specifications that are used on the Internet and not just in a specific region. Trying to interpret national laws and to provide region-by-region specific guidance did not seem desirable to us.
>>>>>
>>>>>>   Do you feel you have reached providing such "Global Common" guidelines in the area of privacy?
>>>>> Yes, I think so and this document follows the spirit of RFC 3552 "Guidelines for Writing RFC Text on Security Considerations". This document is essentially the privacy version of what RFC 3552 is for security. If you look at RFC 3552 you will also fail to find references to regulation on security matters (even though they exist).
>>>>>
>>>>> We did look at many documents that seemed relevant input, such as the mentioned OECD document, and we spoke with data protection authorities and solicited their input. Our job would have been easier if we could have just re-used one of these documents listing the privacy principles. Unfortunately, it turns out that these documents were written for a different audience and that audience is supposed to have different capabilities regarding the design and the deployment of their services. In the IETF we do not have the same degree of freedom and impact and so we developed these guidelines to the best of our capabilities.
>>>>>
>>>>>>   How does it compare to US ECPA provisions for "User Expectations" which has served as a global model for other jurisdictions?
>>>>>> The reason I ask is because I have been very sensitive to ethical design and product liability issues in our product lines since 1986 following the guidelines set forth by the US ECPA for:
>>>>>>
>>>>>> - Thou shall not block/reject things without user knowledge,
>>>>>> - Thou shall not tamper/edit things especially when passing things (relays),
>>>>>> - Thou shall kept private things private.
>>>>>>
>>>>>> This was considered "Global" once upon a time.  Now its arguable.
>>>>> What is interesting for us to find out whether you believe that the Electronic Communications Privacy Act has for additional privacy aspects we need to address in the document.
>>>>> It is not our goal to interpret specific regulatory documents (even though it is interesting). This is the (well-paid) job of many lawyers.
>>>>>
>>>>> Ciao
>>>>> Hannes
>>>>>
>>>>>> --
>>>>>> HLS
>>>>>>
>>>>>> On 2/23/2013 12:10 PM, Alissa Cooper wrote:
>>>>>>> Hi SM,
>>>>>>>
>>>>>>> Thanks for your comments. Some responses are inline.
>>>>>>>
>>>>>>> On Jan 30, 2013, at 7:29 PM, SM wrote:
>>>>>>>
>>>>>>>> At 14:30 16-01-2013, IAB Chair wrote:
>>>>>>>>> This is an announcement of an IETF-wide Call for Comment on 'Privacy Considerations for Internet Protocols'.
>>>>>>>>>
>>>>>>>>> The document is being considered for publication as an Informational RFC within the IAB stream, and is available for inspection here:
>>>>>>>>> http://tools.ietf.org/html/draft-iab-privacy-considerations
>>>>>>>> In Section 1:
>>>>>>>>
>>>>>>>>   'With regard to data, often it is a concept applied to
>>>>>>>>    "personal data," information relating to an identified or
>>>>>>>>    identifiable individual.'
>>>>>>>>
>>>>>>>> I suggest rewriting the above sentence.
>>>>>>> The authors have re-written that sentence several times and in different ways already. Do you have a specific suggestion about how to improve it?
>>>>>>>
>>>>>>>>   "Many sets of privacy principles and privacy design frameworks have been
>>>>>>>>    developed in different forums over the years."
>>>>>>>>
>>>>>>>> There is also some work in the APEC region (see http://publications.apec.org/publication-detail.php?pub_id=390 (payware)).
>>>>>>> As far as I know the APEC framework is one of many frameworks (none of which we cite since there are so many) based on the OECD-style FIPs. Is that incorrect?
>>>>>>>
>>>>>>>> As a nit, the draft-ietf-geopriv-policy-27 reference should be RFC 6772.
>>>>>>> Fixed.
>>>>>>>
>>>>>>>> I read some of the previous versions of this draft.  The Abstract Section describes the document as providing guidance for developing privacy considerations for inclusion in protocol specifications.  I found the draft difficult to digest.  I suggest simplifying the draft to make the guidance accessible to the target audience.
>>>>>>> I'm not quite sure what you are recommending here, but we have had conversations in the IAB privacy program about moving the guidance part up, or otherwise trying to make the focus on the guidance piece more prominent. The difficulty is that there is a broad range in the extent to which potential readers are familiar with privacy concepts, so jumping straight into the guidance would not be appropriate for some portion of the audience. If you have concrete suggestions for how to simplify, those would be helpful.
>>>>>>>
>>>>>>>> One of the issues nowadays is what to do about intermediaries.  If I am not mistaken RFC 3238 was one of the first documents to tackle that question from a privacy perspective.  There have been a few proposals to introduce intermediaries as part of the architecture (I am using the word is used loosely).  It is easy to argue for intermediaries based on use cases.  There was a case recently where the users only became aware that they have signed up for using an intermediary through the EULA.
>>>>>>>>
>>>>>>>> The draft introduces the concept of secondary use (Section 4.2.3).  Strictly speaking, it is a disclosure (Section 4.2.4).
>>>>>>> Not all secondary uses involve disclosure (such as the example given in 4.2.3). I have added a sentence to clarify this, however:
>>>>>>>
>>>>>>> "Secondary use encompasses any use of data, including disclosure."
>>>>>>>
>>>>>>>> The draft mentions consent in several places.  The authors are likely aware that consent was a hot topic for DNT.  It's easier to start with something that is easy for the average person to understand and build from there.  Section 7.2 could more about consent instead of user participation or control.
>>>>>>> We tried to think of a case where a consent mechanism was actually developed in the IETF, but as a general matter consent mechanisms tend to be out of scope, which is why we focus more on user controls (which still show up rarely but do show up).
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Alissa
>>>>>>>
>>>>>>>> Regards,
>>>>>>>> -sm
>>>>>>>>
>>>>
>>>
>>>
>>
>>
>
>
>



From randy@psg.com  Mon Feb 25 16:10:32 2013
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B061621E819C for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 16:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.585
X-Spam-Level: 
X-Spam-Status: No, score=-2.585 tagged_above=-999 required=5 tests=[AWL=0.014,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ij30V7xRW5sU for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 16:10:32 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0286721E8191 for <ietf@ietf.org>; Mon, 25 Feb 2013 16:10:32 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <randy@psg.com>) id 1UA87h-000PMT-Q3; Tue, 26 Feb 2013 00:10:22 +0000
Date: Tue, 26 Feb 2013 08:10:21 +0800
Message-ID: <m2obf8c4uq.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: IETF chair's blog
In-Reply-To: <512BF3A7.3020903@acm.org>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8A832DDC-1D5E-4C1B-87BB-36A384937480@lacnic.net> <512B0A2D.3050102@acm.org> <512B0B20.2000403@lacnic.net> <512B0C7E.5010900@250bpm.com> <512B0E64.2030101@acm.org> <96CB57D2-68EA-4AC5-92AD-90CEA37E2A93@lurchi.franken.de> <512B827F.4060406@acm.org> <m2r4k4c82l.wl%randy@psg.com> <512BF3A7.3020903@acm.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 00:10:32 -0000

>>> For me the most important point is that it is managed on IETF (or IETF's
>>> contractor) servers.
>> as no private data are involved, i am curious why?
> Because public does not mean unlimited availability.  Let's say that
> the IETF decides to use a collaboration tool hosted by a service run
> by an external company.  The data is public (although it can be stored
> in a proprietary format) so anybody can consult it.  But suddenly the
> service is bankrupted/become collateral damage when servers are
> seized/has its certificates expiring/etc...  Unless someone did some
> preventive data liberation, the data is no longer available, at least
> until whatever caused the problem is solved.

so your criteria acctually open and continual availability, and
availability of export.  i think these would apply well to ietf or
whatever services as well.

randy

From jmpolk@cisco.com  Mon Feb 25 16:47:04 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB20A21E81AB; Mon, 25 Feb 2013 16:47:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.416
X-Spam-Level: 
X-Spam-Status: No, score=-110.416 tagged_above=-999 required=5 tests=[AWL=0.183, 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 TPtJ-1GF5GbQ; Mon, 25 Feb 2013 16:47:03 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 18B0621E8196; Mon, 25 Feb 2013 16:47:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=850; q=dns/txt; s=iport; t=1361839623; x=1363049223; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=1sGu5wILb6fI0wz8VwdrOofeHaZFzB11yyjKWPhMPCk=; b=Gr56rcsOsX8Sl2NQi4YBPzRGF0M9W8HufUoi46dJTei1AF1viAdA75+2 weR0S1WnhxtXwBpFhbCZ7Tmy2V1hPzG/J1Qh5fWx3Dtdg8qomZU/6OjV5 lSAJ9oZ22R0B6nC75J8flEuIgsbP88eyurcWMsrExtkdsCTIGOCgSmssc M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnwFAIoFLFGtJXHB/2dsb2JhbABFhgi7VIEGFnOCIAEBBDgCPxAHBCEVEA8KLREGARKIEwzADQSPDgeDQAOIaZ45gyY
X-IronPort-AV: E=Sophos;i="4.84,736,1355097600"; d="scan'208";a="181045929"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 26 Feb 2013 00:47:02 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r1Q0l2Im030997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2013 00:47:02 GMT
Message-Id: <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 25 Feb 2013 18:47:02 -0600
To: IETF Secretariat <ietf-secretariat@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 00:47:04 -0000

The ID upload tool says the deadline has passed, yet a decade or more 
the deadline has been 8pm ET/5pm PT. That's 15 minutes from now.

What gives?

James

At 11:05 AM 2/25/2013, IETF Secretariat wrote:

>This is a reminder that the Internet Draft Final Submission (version -01
>and up) cut-off is today, Monday, February 25, 2013.
>
>All Final Version (-01 and up) submissions are due by UTC 24:00.
>
>All drafts can be uploaded using the ID submission tool located here:
>https://datatracker.ietf.org/submit/
>
>The Internet-Draft cutoff dates as well as other significant dates 
>for IETF 86 can be found at:
>https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86
>
>Thank you for your understanding and cooperation. If you have 
>any  questions or concerns, then please send a message to 
>internet-drafts@ietf.org.


From stpeter@stpeter.im  Mon Feb 25 16:50:46 2013
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 0891B21E80D6; Mon, 25 Feb 2013 16:50:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Level: 
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKWvKd1gC5pe; Mon, 25 Feb 2013 16:50:45 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE0F21E80B6; Mon, 25 Feb 2013 16:50:45 -0800 (PST)
Received: from [192.168.1.6] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 32C784004E; Mon, 25 Feb 2013 17:58:30 -0700 (MST)
Message-ID: <512C06EC.8050408@stpeter.im>
Date: Mon, 25 Feb 2013 17:50:52 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: James Polk <jmpolk@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>
In-Reply-To: <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Secretariat <ietf-secretariat@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, 26 Feb 2013 00:50:46 -0000

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

On 2/25/13 5:47 PM, James Polk wrote:
> The ID upload tool says the deadline has passed, yet a decade or
> more the deadline has been 8pm ET/5pm PT. That's 15 minutes from
> now.

I had the same problem last week for the -00 cutoff.

It used to be 5 PM Pacific, now it's 24:00 UTC.

Peter

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


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

iQIcBAEBAgAGBQJRLAbrAAoJEOoGpJErxa2pJCQQAK05V61dUleo5z+nsodQPNCn
Lt98t7543ic48vaYHpwCYv4zT7sbCJ9KJ7bm0gqBHwnsRnUvb2qeLfQTrBGpKHLG
ZFLiIVDoTqJjEKzcGoEv6ZupZADjiZZZxAN0c+0o2NWJJFs5Jt1x/88k4fmAPGpo
qUGOAUdaQ+ayD4qPYysSiexAJ4kj4x2oSjqWK9SQXJ2LX816mI6YIY75BxF/HniE
Hz95w05hVS6h1LNpr5O0DlY44pUHrBEi4jxXF7GVPhA/XvBS1ONRlbWVBz/tsURG
SJ1HXkKOWpKegld6HjllqjvkSXIEKcs/xc5L68+pkOmdySQ7SQxl0WBqIXDv0Yul
t82W5gUxgkX0XpDE5+SQ3npuseCY77q9HzN3XkzZA1HWTcSMPIUEY7PhgWmuSms6
/aH46hBLVJhOAWDSNieG+lfnJahlvrmTUcZ5l/JJo/AeTbK+cxY8a0NDVit+pi2P
wS8XKBuyM5Z1BxqxtozmDAU1HP3qhTt+m/tBNPNkN185MSylDlnWZQVbZ+ZjH5Jq
LrO9ELqyPC6Evq0j4V4pltOs0T7yVMw7XFWKZv/cVjkC7fu6ZZ3inMovnjmHfQe/
H+ItSqZuHLMOBuFjioPskdujLWadIt1vpULjsw5tdaton82sruaqIC0NdSh7Sr7C
hKLwIVutjXHVvW7b5kzC
=60kr
-----END PGP SIGNATURE-----

From d3e3e3@gmail.com  Mon Feb 25 16:51:20 2013
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B1D21E81AC; Mon, 25 Feb 2013 16:51:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.417
X-Spam-Level: 
X-Spam-Status: No, score=-103.417 tagged_above=-999 required=5 tests=[AWL=0.182, 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 YrAsZJyJ1t3G; Mon, 25 Feb 2013 16:51:19 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id A58B021E8191; Mon, 25 Feb 2013 16:51:19 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so4258640oag.14 for <multiple recipients>; Mon, 25 Feb 2013 16:51:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=m098SVMgcuXOEdeyp9thDnx3rlPqmMhm7anznFZLZJE=; b=B6FJD6jm2EK7XKETfzpLkniDRRbnxkqxDU709iHYBgiVCLllwFqV1+VCyW08wY0IAg cvWI+QYlgUt82VIfpFHItm5GKtvYZupKhe6Lm18IaIU2Kq5rRAeNwJz1Y+ZjFWbna8AY FFma3/dq2oAkb6D6J/7CoNICqYDlmqoZ1dgTI/qPlV2MIlQUwGPkT9W0wGwiF0SarpLd Iwwjg1SeJ0sAzKaN/OczqRj6aKaSajeuJ7lzG9JyjSUAR40sTby51tnIAyZYZvvJc7Zv kir5juy4Z22Xyw5mI3Tzg47k4ezadm2fUDqZLIDgwUQGjAPZQjlpT7RPuBFhFjnMn/+0 RO7w==
X-Received: by 10.182.123.49 with SMTP id lx17mr9630087obb.63.1361839879277; Mon, 25 Feb 2013 16:51:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.98.168 with HTTP; Mon, 25 Feb 2013 16:50:59 -0800 (PST)
In-Reply-To: <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 25 Feb 2013 19:50:59 -0500
Message-ID: <CAF4+nEHF4JPrk2F+cs1ZjxB1nSH4_aLU8eYbVVq_xOHzWCxqPg@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
To: James Polk <jmpolk@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Secretariat <ietf-secretariat@ietf.org>, ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 00:51:20 -0000

As has been true for a few years, the deadline is midnight UTC Monday
and not dependent on any particular United States time zone. The
Important Dates information and reminder messages all state this.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Mon, Feb 25, 2013 at 7:47 PM, James Polk <jmpolk@cisco.com> wrote:
> The ID upload tool says the deadline has passed, yet a decade or more the
> deadline has been 8pm ET/5pm PT. That's 15 minutes from now.
>
> What gives?
>
> James
>
> At 11:05 AM 2/25/2013, IETF Secretariat wrote:
>
>> This is a reminder that the Internet Draft Final Submission (version -01
>> and up) cut-off is today, Monday, February 25, 2013.
>>
>> All Final Version (-01 and up) submissions are due by UTC 24:00.
>>
>> All drafts can be uploaded using the ID submission tool located here:
>> https://datatracker.ietf.org/submit/
>>
>> The Internet-Draft cutoff dates as well as other significant dates for
>> IETF 86 can be found at:
>> https://www.ietf.org/meeting/cutoff-dates-2013.html#IETF86
>>
>> Thank you for your understanding and cooperation. If you have any
>> questions or concerns, then please send a message to
>> internet-drafts@ietf.org.
>
>

From jmpolk@cisco.com  Mon Feb 25 16:58:12 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 972AD21F94AB; Mon, 25 Feb 2013 16:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.422
X-Spam-Level: 
X-Spam-Status: No, score=-110.422 tagged_above=-999 required=5 tests=[AWL=0.177, 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 vu26PL5K1G0G; Mon, 25 Feb 2013 16:58:11 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id C7E2B21F94AD; Mon, 25 Feb 2013 16:58:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1685; q=dns/txt; s=iport; t=1361840292; x=1363049892; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version; bh=MJHXKsgaUf8FFQGu4ZGu6NmrEIOlT0soP3hP/MPJG/Y=; b=kZNbEorNyYa9JaLcXeN4j3b6FKe0H7h9XL5gU/RdjM2EO0d1XoSH1W5F N9PcA5sBnX78mqqWG3rQ/EhB9ljLPTw6IEtQU8onlbtWI7K5Bfb5NTVW/ kstJ7KuKjwxiCTKhmt8YjbM4CVpr4Thb52ntunvWolbADfpJfPW3IlyJz k=;
X-IronPort-AV: E=Sophos;i="4.84,736,1355097600"; d="scan'208";a="181048725"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 26 Feb 2013 00:58:11 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1Q0wBlI032453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2013 00:58:11 GMT
Message-Id: <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 25 Feb 2013 18:58:11 -0600
To: Peter Saint-Andre <stpeter@stpeter.im>, James Polk <jmpolk@cisco.com>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <512C06EC.8050408@stpeter.im>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Cc: IETF Secretariat <ietf-secretariat@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, 26 Feb 2013 00:58:12 -0000

At 06:50 PM 2/25/2013, Peter Saint-Andre wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 2/25/13 5:47 PM, James Polk wrote:
> > The ID upload tool says the deadline has passed, yet a decade or
> > more the deadline has been 8pm ET/5pm PT. That's 15 minutes from
> > now.
>
>I had the same problem last week for the -00 cutoff.
>
>It used to be 5 PM Pacific, now it's 24:00 UTC.

It's always been 2400 UTC, but with all the daylight savings time 
adjustments from country to country changing from year to year, I 
have talked to the Secretariat before (and recently), and verified 
this is indeed 8pm ET, at least for those in the US.

James


>Peter
>
>- --
>Peter Saint-Andre
>https://stpeter.im/
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
>iQIcBAEBAgAGBQJRLAbrAAoJEOoGpJErxa2pJCQQAK05V61dUleo5z+nsodQPNCn
>Lt98t7543ic48vaYHpwCYv4zT7sbCJ9KJ7bm0gqBHwnsRnUvb2qeLfQTrBGpKHLG
>ZFLiIVDoTqJjEKzcGoEv6ZupZADjiZZZxAN0c+0o2NWJJFs5Jt1x/88k4fmAPGpo
>qUGOAUdaQ+ayD4qPYysSiexAJ4kj4x2oSjqWK9SQXJ2LX816mI6YIY75BxF/HniE
>Hz95w05hVS6h1LNpr5O0DlY44pUHrBEi4jxXF7GVPhA/XvBS1ONRlbWVBz/tsURG
>SJ1HXkKOWpKegld6HjllqjvkSXIEKcs/xc5L68+pkOmdySQ7SQxl0WBqIXDv0Yul
>t82W5gUxgkX0XpDE5+SQ3npuseCY77q9HzN3XkzZA1HWTcSMPIUEY7PhgWmuSms6
>/aH46hBLVJhOAWDSNieG+lfnJahlvrmTUcZ5l/JJo/AeTbK+cxY8a0NDVit+pi2P
>wS8XKBuyM5Z1BxqxtozmDAU1HP3qhTt+m/tBNPNkN185MSylDlnWZQVbZ+ZjH5Jq
>LrO9ELqyPC6Evq0j4V4pltOs0T7yVMw7XFWKZv/cVjkC7fu6ZZ3inMovnjmHfQe/
>H+ItSqZuHLMOBuFjioPskdujLWadIt1vpULjsw5tdaton82sruaqIC0NdSh7Sr7C
>hKLwIVutjXHVvW7b5kzC
>=60kr
>-----END PGP SIGNATURE-----


From mnot@mnot.net  Mon Feb 25 17:02:14 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFF3121E8139; Mon, 25 Feb 2013 17:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.579
X-Spam-Level: 
X-Spam-Status: No, score=-105.579 tagged_above=-999 required=5 tests=[AWL=-2.980, 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 GKQNNLmUCYf4; Mon, 25 Feb 2013 17:02:13 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 24D5821E80B6; Mon, 25 Feb 2013 17:02:13 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.5.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1654322E253; Mon, 25 Feb 2013 20:02:10 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>
Date: Tue, 26 Feb 2013 12:02:07 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <37971208-DA42-4846-8F4E-A03788C8014F@mnot.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>
To: James Polk <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Secretariat <ietf-secretariat@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, 26 Feb 2013 01:02:14 -0000

Don't think so:

mnot-mini:~> date -u
Tue 26 Feb 2013 01:01:29 UTC


On 26/02/2013, at 11:58 AM, James Polk <jmpolk@cisco.com> wrote:

> At 06:50 PM 2/25/2013, Peter Saint-Andre wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>=20
>> On 2/25/13 5:47 PM, James Polk wrote:
>> > The ID upload tool says the deadline has passed, yet a decade or
>> > more the deadline has been 8pm ET/5pm PT. That's 15 minutes from
>> > now.
>>=20
>> I had the same problem last week for the -00 cutoff.
>>=20
>> It used to be 5 PM Pacific, now it's 24:00 UTC.
>=20
> It's always been 2400 UTC, but with all the daylight savings time =
adjustments from country to country changing from year to year, I have =
talked to the Secretariat before (and recently), and verified this is =
indeed 8pm ET, at least for those in the US.
>=20
> James
>=20
>=20
>> Peter
>>=20
>> - --
>> Peter Saint-Andre
>> https://stpeter.im/
>>=20
>>=20
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>=20
>> iQIcBAEBAgAGBQJRLAbrAAoJEOoGpJErxa2pJCQQAK05V61dUleo5z+nsodQPNCn
>> Lt98t7543ic48vaYHpwCYv4zT7sbCJ9KJ7bm0gqBHwnsRnUvb2qeLfQTrBGpKHLG
>> ZFLiIVDoTqJjEKzcGoEv6ZupZADjiZZZxAN0c+0o2NWJJFs5Jt1x/88k4fmAPGpo
>> qUGOAUdaQ+ayD4qPYysSiexAJ4kj4x2oSjqWK9SQXJ2LX816mI6YIY75BxF/HniE
>> Hz95w05hVS6h1LNpr5O0DlY44pUHrBEi4jxXF7GVPhA/XvBS1ONRlbWVBz/tsURG
>> SJ1HXkKOWpKegld6HjllqjvkSXIEKcs/xc5L68+pkOmdySQ7SQxl0WBqIXDv0Yul
>> t82W5gUxgkX0XpDE5+SQ3npuseCY77q9HzN3XkzZA1HWTcSMPIUEY7PhgWmuSms6
>> /aH46hBLVJhOAWDSNieG+lfnJahlvrmTUcZ5l/JJo/AeTbK+cxY8a0NDVit+pi2P
>> wS8XKBuyM5Z1BxqxtozmDAU1HP3qhTt+m/tBNPNkN185MSylDlnWZQVbZ+ZjH5Jq
>> LrO9ELqyPC6Evq0j4V4pltOs0T7yVMw7XFWKZv/cVjkC7fu6ZZ3inMovnjmHfQe/
>> H+ItSqZuHLMOBuFjioPskdujLWadIt1vpULjsw5tdaton82sruaqIC0NdSh7Sr7C
>> hKLwIVutjXHVvW7b5kzC
>> =3D60kr
>> -----END PGP SIGNATURE-----
>=20

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




From joelja@bogus.com  Mon Feb 25 17:46:09 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E33CF21F9211; Mon, 25 Feb 2013 17:46:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 uhNGktDsDNzQ; Mon, 25 Feb 2013 17:46:08 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D91EE21F91B8; Mon, 25 Feb 2013 17:46:08 -0800 (PST)
Received: from joels-MacBook-Air.local (50-0-150-57.dsl.static.sonic.net [50.0.150.57]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1Q1k6em011048 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 26 Feb 2013 01:46:07 GMT (envelope-from joelja@bogus.com)
Message-ID: <512C13DF.8070607@bogus.com>
Date: Mon, 25 Feb 2013 17:46:07 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>, James Polk <jmpolk@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <37971208-DA42-4846-8F4E-A03788C8014F@mnot.net>
In-Reply-To: <37971208-DA42-4846-8F4E-A03788C8014F@mnot.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 26 Feb 2013 01:46:07 +0000 (UTC)
Cc: IETF Secretariat <ietf-secretariat@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, 26 Feb 2013 01:46:10 -0000

On 2/25/13 5:02 PM, Mark Nottingham wrote:
> Don't think so:
>
> mnot-mini:~> date -u
> Tue 26 Feb 2013 01:01:29 UTC
>
>
> On 26/02/2013, at 11:58 AM, James Polk <jmpolk@cisco.com> wrote:
>
>> At 06:50 PM 2/25/2013, Peter Saint-Andre wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 2/25/13 5:47 PM, James Polk wrote:
>>>> The ID upload tool says the deadline has passed, yet a decade or
>>>> more the deadline has been 8pm ET/5pm PT. That's 15 minutes from
>>>> now.
>>> I had the same problem last week for the -00 cutoff.
>>>
>>> It used to be 5 PM Pacific, now it's 24:00 UTC.
>> It's always been 2400 UTC, but with all the daylight savings time adjustments from country to country changing from year to year, I have talked to the Secretariat before (and recently), and verified this is indeed 8pm ET, at least for those in the US.
Between march 10 and November 3rd DST applies in the USA. Outside that 
midnight UTC is 1600 Pacific.
>> James
>>
>>
>>> Peter
>>>
>>> - --
>>> Peter Saint-Andre
>>> https://stpeter.im/
>>>
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>>
>>> iQIcBAEBAgAGBQJRLAbrAAoJEOoGpJErxa2pJCQQAK05V61dUleo5z+nsodQPNCn
>>> Lt98t7543ic48vaYHpwCYv4zT7sbCJ9KJ7bm0gqBHwnsRnUvb2qeLfQTrBGpKHLG
>>> ZFLiIVDoTqJjEKzcGoEv6ZupZADjiZZZxAN0c+0o2NWJJFs5Jt1x/88k4fmAPGpo
>>> qUGOAUdaQ+ayD4qPYysSiexAJ4kj4x2oSjqWK9SQXJ2LX816mI6YIY75BxF/HniE
>>> Hz95w05hVS6h1LNpr5O0DlY44pUHrBEi4jxXF7GVPhA/XvBS1ONRlbWVBz/tsURG
>>> SJ1HXkKOWpKegld6HjllqjvkSXIEKcs/xc5L68+pkOmdySQ7SQxl0WBqIXDv0Yul
>>> t82W5gUxgkX0XpDE5+SQ3npuseCY77q9HzN3XkzZA1HWTcSMPIUEY7PhgWmuSms6
>>> /aH46hBLVJhOAWDSNieG+lfnJahlvrmTUcZ5l/JJo/AeTbK+cxY8a0NDVit+pi2P
>>> wS8XKBuyM5Z1BxqxtozmDAU1HP3qhTt+m/tBNPNkN185MSylDlnWZQVbZ+ZjH5Jq
>>> LrO9ELqyPC6Evq0j4V4pltOs0T7yVMw7XFWKZv/cVjkC7fu6ZZ3inMovnjmHfQe/
>>> H+ItSqZuHLMOBuFjioPskdujLWadIt1vpULjsw5tdaton82sruaqIC0NdSh7Sr7C
>>> hKLwIVutjXHVvW7b5kzC
>>> =60kr
>>> -----END PGP SIGNATURE-----
> --
> Mark Nottingham   http://www.mnot.net/
>
>
>
>


From mary.ietf.barnes@gmail.com  Mon Feb 25 20:02:04 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B0D21E8170 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:02:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.576
X-Spam-Level: 
X-Spam-Status: No, score=-103.576 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z9nmEp6SgDaw for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:02:03 -0800 (PST)
Received: from mail-qe0-f48.google.com (mail-qe0-f48.google.com [209.85.128.48]) by ietfa.amsl.com (Postfix) with ESMTP id D8CF721E816D for <ietf@ietf.org>; Mon, 25 Feb 2013 20:02:02 -0800 (PST)
Received: by mail-qe0-f48.google.com with SMTP id 3so2186835qea.35 for <ietf@ietf.org>; Mon, 25 Feb 2013 20:02:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Kz8tAfGbLcIt/gNfiJtTeuVHVlcTjAJB+OO3tPF4nyM=; b=KEA8ELBcgtUQQharse4zv+F6LwXEtKh+RTHIfTMhnqxOXJbmPLCgAegMTFROQeOTKr WC5Mj5JcX/9XUJCS7B6K0BDAPIehaGdmbQauFkcSngvroB1PbXaek/IiwODTm2/PewIX NSLjhRnIXMog5jXhc4HutJnU7srrjRn4GSyWxDqRJZNXU0k2B8j9HfPA7VQBbbjUxQHn GIqwmxK8vOtb8r2phshNlYGoVJOTIBXMhxfem67pzM5ysrgUkILkgVcyw8U65NGvtogb O0rH3vZpDC8a2vcFlH8iMU7bGXLkhHQBeiHyH3nMGDpXPkz+u7J6fH7rw++gXHF45GND 4sUw==
MIME-Version: 1.0
X-Received: by 10.49.96.33 with SMTP id dp1mr17621544qeb.60.1361851322248; Mon, 25 Feb 2013 20:02:02 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Mon, 25 Feb 2013 20:02:02 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net>
Date: Mon, 25 Feb 2013 22:02:02 -0600
Message-ID: <CAHBDyN6vhbTyGvXA2inKjpLr7rZx9_qms4zmpuz6VC-oAszS4Q@mail.gmail.com>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
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, 26 Feb 2013 04:02:04 -0000

On Mon, Feb 25, 2013 at 5:03 PM, SM <sm@resistor.net> wrote:
> Hi Mary,
>
> At 10:36 25-02-2013, Mary Barnes wrote:
>>
>> have Ice Cream Thursdays unless someone sponsors it.  Since I was
>> highly disappointed at the Atlanta meeting, I was able to get Polycom
>> to sponsor the event at IETF-86 ;)
>
>
> This is ample motivation for me to support the draft. :-)
>
>
>> At this stage, the feedback I would like related to this document is
>> with regards it's readiness for publication as an RFC.  One of the
>
>
> It better to decide whether to publish now (Last Call) then to wait another
> five years.
>
> In Section 4:
>
>  "A wide range of research has shown that about 10% of the population
>   prefer to eat a healthy diet."
>
> Can I have some references for that?
[MB]  You can find quite a few articles that discuss how many people
follow a healthy lifestyle - exercise, eat their veggies, don't smoke,
etc. and that's about 10% if the population (there are US and European
studies).   In is extremely common for those who do one to do the
other.  The  highest number I have found for the recommended amount of
veggies is about 12%, for example.  If you want I can add some of
these references:
- http://www.cnpp.usda.gov/publications/hei/HEi89-90report.pdf (12%
scored in the range classified as a healthy diet)
- http://www.biomedcentral.com/1472-6963/8/213 (Study of Basque women)
- http://www.ehfg.org/fileadmin/ehfg/Website/Archiv/2011/Presentations/W3/w3_1_chestnov_2.pdf
(a Russian study)
Or, I can change the "about" to "roughly".  I think the number is
likely a tad higher.  My point was that it's not just too or three
people but a fair percentage of the participants.
[/MB]
>
>  "Thus, it is estimated that at least 10 percent of the IETF
>   participants would take advantage of healthy food offerings."
>
> Based on the previous sentence, the above could be read as at least 10
> percent of IETF participants are educated. :-)
[MB]  I was giving everyone the benefit of the doubt ;) [/MB]
>
>   "There are laws in many countries and jurisdictions (e.g.,U.S., E.U.)
>    that make it illegal to mislabel foods that are Halal or Kosher.  At
>    this time, food manufacturers in many jusisdictions (e.g.,U.S., U.K,
>    E.U.) must include all ingredients on the labels of any packaged food
>    product."
>
> The "must" was violated (
> http://ec.europa.eu/ireland/press_office/news_of_the_day/horse-meat-food-labelling-plan_en.htm
> ).
>
> In Section 5:
>
>   "For cases of first time attendees for a specific location, relevant
>    information can be gathered from attendees that have previously
>    visited the city."
>
> There are recurrent discussions as nobody volunteered to gather that
> information in one place.
>
> In Section 8:
>
>   "One can never assume that everything has been taken care of by
>    someone else."
>
> I suggest moving that to the security considerations section.
[MB] Ok. [/MB]
>
> I suggest having the draft make recommendations instead of setting
> requirements.
[MB] I don't know that the distinction particularly matters in this
type of document.  These are
requirements to ensure that some of us have food that we can eat.  If
the some of requirements aren't
satisfied, some of us do not have readily accessible food to eat. [/MB]
> Some of the items in Section 7 "might" be things the IETF can
> do; some of the items are for other parties.
[MB] My opinion is that the folks that sign contracts and work with
the venue staff are responsible for
communicating those requirements and ensuring the venue can meet those
requirements. [/MB]
>  It would be easier if the two
> sets are kept separate.  I suggest moving the History stuff to an appendix
> (e.g. "The Cornucopia restaurant in Dublin [cornucopia] is a perfect example
> of how this can be done in an extremely cost-effective efficient and
> gastronomically appealing manner".
[MB] I personally think it's really helpful to have a very specific,
real-life example. But,  I could
change it to be more general and not reference the specific restaurant
since we also had a
great place like that in Quebec City.  [/MB]

>I suggest avoiding stuff like "American
> Disabilities Act".  It would be better to formulate the draft in terms of an
> international audience.
[MB] It is an example and it's the only one I'm familiar with although
I assume other countries have similar laws.  The last sentence
referencing the ADA is a very important distinction in terms of who is
required to obey the law, but perhaps it's not particular useful or
relevant to this document, so I can remove that sentence. [/MB]
>
> Regards,
> -sm
>

From aservin@lacnic.net  Mon Feb 25 20:04:52 2013
Return-Path: <aservin@lacnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6C121E8173 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.688
X-Spam-Level: *
X-Spam-Status: No, score=1.688 tagged_above=-999 required=5 tests=[AWL=-4.288,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_DYNAMIC_HCC=4.295,  HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, RELAY_IS_220=2.118]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqoUwbOWQ+I6 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:04:29 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 9866121E816D for <ietf@ietf.org>; Mon, 25 Feb 2013 20:04:29 -0800 (PST)
Received: from 221.149.dhcp.conference.apricot.net (unknown [220.247.149.221]) by mail.lacnic.net.uy (Postfix) with ESMTP id D227C308424; Tue, 26 Feb 2013 02:04:18 -0200 (UYST)
Message-ID: <512C3445.60709@lacnic.net>
Date: Tue, 26 Feb 2013 12:04:21 +0800
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B257A.3030902@lacnic.net> <CAOmxzdzxNejS_D3wHm_rPHBmAYZDXVK5odhP2ge057NQRu2mWw@mail.gmail.com>
In-Reply-To: <CAOmxzdzxNejS_D3wHm_rPHBmAYZDXVK5odhP2ge057NQRu2mWw@mail.gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck: 
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
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, 26 Feb 2013 04:04:55 -0000

	It appears that the path that this discussion has followed has proven
your point.

/as

On 25/02/2013 23:31, Alejandro Acosta wrote:
> On 2/25/13, Arturo Servin <aservin@lacnic.net> wrote:
>> Fred,
>>
>> 	I am not convinced that social nets (proprietary or not) are yet a good
>> tool to do IETF work. They are good to communicate one-way and some
>> informal two-ways, but that's all (at least for now)
>>
>> 	What I had in mind was something very simple such that the IETF chair
>> could do is to automatically post to twitter, facebook, etc whenever
>> there is a new post from his blog and receive from communication using
>> those tools (besides the comments in the blog). But that is all.
> 
> This scenario sounds good for me.  Of course this is not a
> substitution of the mailing list, this is complementary. It's nice to
> receive a tweet with the subject of the blog post and the URL to click
> on it.
> 
> Some time ago in this mailing list we were discussing that the average
> age of IETF is getting old (of course, there are many exceptions). Did
> you know that young people do not use email as much as us?. Saying
> that, this can be a good way to bring young people to IETF.
> 
> Alejandro Acosta,
> 
> 
> {...}
> 

From melinda.shore@gmail.com  Mon Feb 25 20:16:15 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9102421E817F for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:16:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.409
X-Spam-Level: 
X-Spam-Status: No, score=-3.409 tagged_above=-999 required=5 tests=[AWL=0.190,  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 qmkPuuq1YaJs for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 20:16:14 -0800 (PST)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) by ietfa.amsl.com (Postfix) with ESMTP id 9743121F9032 for <ietf@ietf.org>; Mon, 25 Feb 2013 20:16:14 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id bj3so2184433pad.20 for <ietf@ietf.org>; Mon, 25 Feb 2013 20:16:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=e7/s3/B05I/DVXJBDXe2DFMNBwAMkWWYJ75jZTE4nqA=; b=JaWDPHW/PSmdYkejsqbFJ8lmxqzD/EhCEkMQXbKM67RO4dvCnwNWEsOnVY8jzYcFF9 UJC1bdCm2HIDmahOvTyQeIUysXDAt34ue6sWAF7/0oQFUc8ENa164Znf+ak7bhq+sSqn F8E8gyxht6OPlCm7V4G9NVDQJDVMs5kmcfHg9AhADsDu45P64LNCYXbmC7Db+8hF0r0e Pu0YHc68rBDNSMd4wiMGDBjEP9gLIDrHZgmfGhff7IoeZd5zCaQU0tGlmzRrgXwWqVkd 7sFOTBAILyozOoLMZ8qb2ZpV/qJfbtCJjHxIt9opoleTv+erE0Ey92MRzSmSfZ/2w4/G KDcQ==
X-Received: by 10.66.9.2 with SMTP id v2mr22742316paa.18.1361852174382; Mon, 25 Feb 2013 20:16:14 -0800 (PST)
Received: from spandex.local (216-67-46-104-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.104]) by mx.google.com with ESMTPS id e6sm16042828paw.16.2013.02.25.20.16.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Feb 2013 20:16:13 -0800 (PST)
Message-ID: <512C370B.1050001@gmail.com>
Date: Mon, 25 Feb 2013 19:16:11 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net> <CAHBDyN6vhbTyGvXA2inKjpLr7rZx9_qms4zmpuz6VC-oAszS4Q@mail.gmail.com>
In-Reply-To: <CAHBDyN6vhbTyGvXA2inKjpLr7rZx9_qms4zmpuz6VC-oAszS4Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 04:16:15 -0000

On 2/25/13 7:02 PM, Mary Barnes wrote:
> Or, I can change the "about" to "roughly".  I think the number is
> likely a tad higher.  

I'd actually guess that it's considerably higher, although I don't
know that "I'd actually guess" is a useful metric.

> [MB] It is an example and it's the only one I'm familiar with although
> I assume other countries have similar laws.  The last sentence
> referencing the ADA is a very important distinction in terms of who is
> required to obey the law, but perhaps it's not particular useful or
> relevant to this document, so I can remove that sentence. [/MB]

This probably goes to the broader question about this particular
meeting (IETF 86( but I think it's important to note -somewhere-
that just because a particular facility/building meets ADA
requirements does not mean that the meeting is particularly
accessible.

I like this document, and I think it will also be very useful for
people who would like to come to a meeting but unsure about
being able to eat.  I'd like to see it progress.

Melinda



From presnick@qti.qualcomm.com  Mon Feb 25 23:09:44 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBC9221F95D0 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 23:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level: 
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g56jpsubOxWb for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 23:09:44 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id EF87021F955B for <ietf@ietf.org>; Mon, 25 Feb 2013 23:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1361862583; x=1393398583; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Mqqw3F81x99ylt5cOx37H2z46oRY6NVqxb8fZCbDPGQ=; b=bYKloWP7LqMSh7D4AUwGXcYu0OB3VuRGgp0Q5fVrdRlMv1Op8+z5OWJ3 YKtS7Cm5dr+VSNQO+XUzR9jT+oK0uaFUP5UkCDDoB/cRtuUxQC1cwrIZg hIraOqgNKPQEkWZAawDkeTACJrOMtO4yF96ekEGVIaT67jOmVXMgVLLjK E=;
X-IronPort-AV: E=Sophos;i="4.84,739,1355126400"; d="scan'208";a="26043390"
Received: from unknown (HELO ironmsg02-lv.qualcomm.com) ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 25 Feb 2013 23:09:43 -0800
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 25 Feb 2013 23:09:43 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 25 Feb 2013 23:09:42 -0800
Message-ID: <512C5FB6.2020403@qti.qualcomm.com>
Date: Tue, 26 Feb 2013 01:09:42 -0600
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: Edward Lewis <ed.lewis@neustar.biz>
Subject: Re: Showing support during IETF LC...
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net>	<20130223012937.GI63436@verdi> <6606B858-C9AD-48BC-8D15-14DBC88E5948@neustar.biz>
In-Reply-To: <6606B858-C9AD-48BC-8D15-14DBC88E5948@neustar.biz>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 07:09:45 -0000

On 2/25/13 4:27 PM, Edward Lewis wrote:
> I have this scenario in mind:
>
> A -12 comes out and I read it thoroughly and have about 10 points that 
> need to be addressed.
>
> So I respond to the document (not in last call) and all of the points 
> are adequately (in my opinion) addressed.
>
> A -13 is issued and sent to last call.
>
> So - I shouldn't voice support?  Do I go down in the record as someone 
> that had voiced concerns?  Or do I go down in the record as someone 
> who supports the document?

When -13 comes out, a message saying "-13 addresses all of my issues" is 
good data. If you already sent such a message to the WG when -13 came 
out, then you're already "down in the record" and I'd expect the chair 
to mention in the writeup to the IESG, "A bunch of comments were 
received during WG last call and addressed to the commenters' 
satisfaction, so I think this document has gotten good positive support 
in its current form", and that's also perfectly good data.

(Similarly, saying during Last Call, "I intend to implement this thing; 
it looks really useful for my purposes" is good data, and if you've said 
it to the WG already, I expect -- in summary -- to hear about it in the 
writeup, and that's good data. And saying during Last Call, "I've never 
seen this document before in my life, but I've given it a review 'cause 
I'm a nice guy and it looks pretty good to me" is also pretty reasonable 
data.)

But saying "+1" or "I support this document" during Last Call *with no 
context* isn't all that useful from the point of view of someone calling 
consensus. The problem is there's no way to tell what precisely that 
means. It could mean, "I've been reviewing this and all of my previous 
concerns were answered", it could mean, "I'm planning on implementing", 
it could mean, "I did a random review and it looks good", or it could 
mean, "Someone told me I should say 'I support this document'." And that 
means you can only tell what it means by reputation of the speaker, 
which isn't a great metric for these sorts of things.

So yes, voice support, but do it in context. And if you've already 
voiced support (like to the WG), expect that it's been noticed and you 
don't need to voice it again.

pr

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


From lear@cisco.com  Mon Feb 25 23:36:44 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDA621F968B for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 23:36:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.71
X-Spam-Level: 
X-Spam-Status: No, score=-110.71 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oY7cxRb97F37 for <ietf@ietfa.amsl.com>; Mon, 25 Feb 2013 23:36:44 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 7269F21F9685 for <ietf@ietf.org>; Mon, 25 Feb 2013 23:36:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=247; q=dns/txt; s=iport; t=1361864204; x=1363073804; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=7m4mKla/7a29Oa1gRGWQcQnbh7B+RSjalreNQdui5KY=; b=DjtSuxHXFO6x3NAQeqBup6MR9O+AYCFmHl9RZe7IfjOBvdjQw1zLlKGC 9qMiDMeuliTe1TPLWWdP+lgfKzhB35228k1vrCkJgR5/BmkMaZPRHUNKZ 2zLYvGCotpYhE+IHLeBAc3PXLyV8rNd+YmATo1BNw55QmcCXnsikTvsf+ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAB9lLFGrRDoG/2dsb2JhbABFhk+7DgIHgQEWc4IfAQEBBCMPAUUBEAsYAgIFFgsCAgkDAgECAUUGDQEHAQGIDq0RgkCQAYEjjWcHgi2BEwOWPZBngwg
X-IronPort-AV: E=Sophos;i="4.84,739,1355097600"; d="scan'208";a="70269175"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 26 Feb 2013 07:36:44 +0000
Received: from sjc-vpn3-1532.cisco.com (sjc-vpn3-1532.cisco.com [10.21.69.252]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1Q7af2n022582 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2013 07:36:43 GMT
Message-ID: <512C6609.1020206@cisco.com>
Date: Tue, 26 Feb 2013 08:36:41 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Showing support during IETF LC...
References: <70CCC52B-7CF1-40B3-AFA1-D333CEDFF821@kumari.net> <51287807.8060505@gmail.com> <63BD5E21DD50CA6FBD9EAEC4@JcK-HP8200.jck.com> <9D3087A6-4281-4C07-971A-87DCC27D3329@piuha.net> <CAHBDyN5Jn7dUokX9qbkKif-oJXfJNExw4ZPdkBkUpw9T6NR=1Q@mail.gmail.com> <6BD79347-3A9B-42DD-B75A-3FF55021CD76@kumari.net>
In-Reply-To: <6BD79347-3A9B-42DD-B75A-3FF55021CD76@kumari.net>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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, 26 Feb 2013 07:36:45 -0000

On 2/25/13 9:06 PM, Warren Kumari wrote:
> I suspect it is because it is very hard to know if someone replying with '+1' has actually read / has a useful opinion on whatever they are replying to, or is just going alone with the herdâ€¦

+1.



From sm@resistor.net  Tue Feb 26 00:02:27 2013
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025D621F889C for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 00:02:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level: 
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jASrFY0UVhuV for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 00:02:24 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3678621F8891 for <ietf@ietf.org>; Tue, 26 Feb 2013 00:02:24 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r1Q82BXK006067; Tue, 26 Feb 2013 00:02:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1361865736; bh=BQLudrpgV69jVxmimWKrEaxpY8o7hTYk1wshWZ8v0Lg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zQ71jZDlUYSrPozgIW6YSl2FprfDzHKZnRRnFfniF7e6lw02ZSIRSx67a3QlqECyI SLnfNw3NLIzkUdZS+2ZrsEA4gtV6QsBrsBtrUK0R3hHVhBTFoywTsJrT1TPeNee3DG G6z6ylfKi+2ZiJw9O/3qlq9IpKV+9hEG7oEQizKM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1361865736; i=@resistor.net; bh=BQLudrpgV69jVxmimWKrEaxpY8o7hTYk1wshWZ8v0Lg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=EpYQPlJ2jRaLIH56fFQikAOAMySU9+UN5lo035vZ7kYMVJfnxCFagfoovTtO4SEOB mogyAND7hWOTIRzRBIN0ofTbcLpOdkVLmRV56QfMMqAhWr7CEmJ6p/wWmlTMBFGZeY k4q2WM25wL4yEuCTKucjTdMF8qMRMA46+awJ5k1I=
Message-Id: <6.2.5.6.2.20130225222432.09e8a028@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 25 Feb 2013 23:55:05 -0800
To: Mary Barnes <mary.ietf.barnes@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
In-Reply-To: <CAHBDyN6vhbTyGvXA2inKjpLr7rZx9_qms4zmpuz6VC-oAszS4Q@mail.g mail.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net> <CAHBDyN6vhbTyGvXA2inKjpLr7rZx9_qms4zmpuz6VC-oAszS4Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 08:02:27 -0000

Hi Mary,
At 20:02 25-02-2013, Mary Barnes wrote:
>[MB]  You can find quite a few articles that discuss how many people
>follow a healthy lifestyle - exercise, eat their veggies, don't smoke,
>etc. and that's about 10% if the population (there are US and European
>studies).   In is extremely common for those who do one to do the
>other.  The  highest number I have found for the recommended amount of
>veggies is about 12%, for example.  If you want I can add some of
>these references:

Thanks.  I asked as the question might be asked.  I don't think that 
the references are needed in the draft.

>Or, I can change the "about" to "roughly".  I think the number is
>likely a tad higher.  My point was that it's not just too or three
>people but a fair percentage of the participants.

Ok.

>[MB]  I was giving everyone the benefit of the doubt ;) [/MB]

:-)

>[MB] I don't know that the distinction particularly matters in this
>type of document.  These are
>requirements to ensure that some of us have food that we can eat.  If
>the some of requirements aren't
>satisfied, some of us do not have readily accessible food to eat. [/MB]

In my humble opinion it might be less difficult to get the draft 
through the process.  The sponsoring AD might have a better idea.

There are a few points in Section 4 which the IETF cannot say no to 
as it will be viewed as insensitive.

>[MB] My opinion is that the folks that sign contracts and work with
>the venue staff are responsible for
>communicating those requirements and ensuring the venue can meet those
>requirements. [/MB]

After Downtown Disney anyone will be able to see whether any of the 
requirements were mentioned in any contract.

>[MB] I personally think it's really helpful to have a very specific,
>real-life example. But,  I could
>change it to be more general and not reference the specific restaurant
>since we also had a
>great place like that in Quebec City.  [/MB]

I don't know how the IETF meeting locations will evolve.   My guess 
is that the IETF will never go to that Dublin location again. The 
food outlets referenced in the draft are not available in every 
country.  That is why I suggested being more general.

>[MB] It is an example and it's the only one I'm familiar with although
>I assume other countries have similar laws.  The last sentence
>referencing the ADA is a very important distinction in terms of who is
>required to obey the law, but perhaps it's not particular useful or
>relevant to this document, so I can remove that sentence. [/MB]

I'll make a side comment first.

  "IETF is an open and inclusive organization"

"inclusive" is a code word for something else.

Legal matters are generally problematic.  It does not bother me if 
the American Disabilities Act is applicable for Canada and 
Quebec.  The people from those countries might have a different opinion. :-)

If the document is published with the following text: "It represents 
the consensus of the IETF community, it creates a very important distinction.

It has been said that the following does not exist: http://freebeer.org

Regards,
-sm 


From abdussalambaryun@gmail.com  Tue Feb 26 03:29:49 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C5E21F88E3; Tue, 26 Feb 2013 03:29:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 ShS4MyXfi98y; Tue, 26 Feb 2013 03:29:48 -0800 (PST)
Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) by ietfa.amsl.com (Postfix) with ESMTP id A633921F88E2; Tue, 26 Feb 2013 03:29:48 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id um15so2332790pbc.14 for <multiple recipients>; Tue, 26 Feb 2013 03:29:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=K5/vb1i34aNMRR/+I3ey/yQAa71hHNFirCwB1pQo/V0=; b=LxHsiwC8JRP7tnS4jSCFEiNZJi0NX+HvygLBUEFLDs3E0SoiffyBa7x9CgG2AhwF49 ImBdC7NaiK7z0hblq46Q1/T1NEV95NQ4x6573sPrexCi348o5Ny6kBDhxSBntsmND+T/ qNdVujGAEBthrKoQKhThDJeUQnRm6Mc0aGEfStoQyR7ep118pBGBOYcWl3LYhbLcHTJA CXpdufmSe1E26e02BU5PQ1NRI2N3qps9E+sAMZFXHh0n7+shPENybLSpliUFn+NsQXRb fCMQxxWpfJ+V3pt0H4DnrtH9ygZFdyiP6zeGeAiMcJukGZt7CkpcEWrymuu3Z8e7QXu9 aycA==
MIME-Version: 1.0
X-Received: by 10.68.143.40 with SMTP id sb8mr23243016pbb.202.1361878188401; Tue, 26 Feb 2013 03:29:48 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Tue, 26 Feb 2013 03:29:48 -0800 (PST)
In-Reply-To: <8BFFD20F-58D8-4118-9F81-EF760A6DDB3A@thomasclausen.org>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com> <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com> <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com> <8BFFD20F-58D8-4118-9F81-EF760A6DDB3A@thomasclausen.org>
Date: Tue, 26 Feb 2013 11:29:48 +0000
Message-ID: <CADnDZ8_5oX7-=zw7RGnKo3NgzfEXG+gzJKgBm3Y1Dw5SDfckMQ@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=047d7b2e42a2a5acef04d69ef9f6
Cc: "draft-cardenas-dff@tools.ietf.org" <draft-cardenas-dff@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 11:29:50 -0000

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

Could you give your summary experience of implementing DFF and which
network was it deployed/tested in and the summary result? I think this
information will help other users and also the IESG to make future
decisions :-)

AB

On Mon, Feb 25, 2013 at 11:01 PM, Thomas Heide Clausen <
ietf@thomasclausen.org> wrote:

> Note, I am not an author of this particular document, but I've got some
> experimental and operational experience with it - having implemented DFF
> and built deployments including it.
>
> On 25 f=E9vr. 2013, at 06:59, Abdussalam Baryun <abdussalambaryun@gmail.c=
om>
> wrote:
>
> > Reply to your request dated 07/02/2013
> > Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 24/02/2013
> >
> > Reviewer Comment #AB3: Related to Processing and interaction with other=
s.
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> > In section 11
> > AB>The DFF MUST contain the next hop of RIB, but in section 5 it
> mentions MAY.
> > AB>suggest> please amend both should be same requirement for protocol.
> >
> > AB> the way it determines the next hop does not show that this
> > protocol is sensitive to other parameters in the RIB, it just takes
> > the addresses without considering the routing protocol strategy in its
> > RIB. IMHO, this may make the DFF make mistakes in taking the right
> > next hop
>
> What you say above doesn't make any sense. DFF considers the content of
> the RIB, among other information, and recommends following the "next hop"
> indicated in the RIB first - i.e., DFF explicitly takes the "right next
> hop" according to "the routing protocol strategy" as expressed in the RIB=
.
>
> Of course, if you happen to know more about what the routing protocol doe=
s
> (e.g., have access to internal state of the routing protocol), you could =
do
> something more clever - DFF doesn't prohibit that either, so I think that
> the authors struck a nice middle ground here.
>
> > Section 12
> > AB> is not understood, it seems a general not specific, I suggest more
> > explaining how this interaction with routing protocol is occured?
>
> It seems pretty clear to me what's expected here: signal to the routing
> protocol (and then, whatever the routing protocol does with that signal
> depends on what routing protocol it is).
>
> It's, IMO, hard to be any clearer here.
>
>
> > Section 13
> > AB> who creates the sequence number is it the DFF or the routing
> > protocol. It seems the DFF, so please specify how it will
> > maintain/save such sequence number in this section.
> > AB> suggest this section to be : DFF Sequence Number.
> >
>
> [befuddled]
>
> Section 13 is already very clear on this.
>
> > Section 14
> > AB> again do you mean that both modes can work together. I don't think
> > that you mean that, so you should specify that each routing domain
> > MUST have one mode, and specify how to maintain that mode in such
> > protocol.
>
> Eh, here too I am befuddled. I do not see anywhere that the authors
> indicate that the two "modes can work together" - actually, the document
> doesn't talk about "modes" at all, and  the protocol doesn't have "modes"=
.
>
> Rather, this section describes how one would use DFF, depending on what
> other choices are made in the network deployment. In other words: DFF
> doesn't specify a "mode", but rather says "if your network is of this kin=
d,
> then do like that".
>
> So, I think that there's strictly nothing to change here, no need to
> maintain a "mode" etc.
>
> > Overall> about processing>
> > AB> this protocol needs to be discussed more how it will interact with
> > the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore
> > alot of work done in the IETF which is not fiting the general
> > applicability it is offering.
>
> No, it doesn't.
>
> DFF is completely orthogonal to routing protocols
>
> DFF can (logically) layer below any routing protocol, without
> modifications to that routing protocol.
>
> DFF can use a RIB and can provide signals to a routing protocol (or not -
> if the routing protocol doesn't want them)
>
> Thomas
>
> > +++++++++++++The END+++++++++++
> >
> > Regards
> > AB
> >
> -------------------------------------------------------------------------=
--------------
> > This message and any attachments are confidential to the intended
> > recipient and may also be privileged. If you are not the intended
> > recipient please delete it from your system and notify the sender.
> > This message is in compliance with the IETF regulations.
> >
> -------------------------------------------------------------------------=
--------------
> >
> >
> >>> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
> >>>>
> >>>> The IESG has received a request from an individual submitter to
> consider
> >>>> the following document:
> >>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
> >>>>  <draft-cardenas-dff-09.txt> as Experimental RFC
> >>>>
> >>>> The IESG plans to make a decision in the next few weeks, and solicit=
s
> >>>> final comments on this action. Please send substantive comments to t=
he
> >>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments
> may
> >>>> be
> >>>> sent to iesg@ietf.org instead. In either case, please retain the
> >>>> beginning of the Subject line to allow automated sorting.
> >>>>
> >>>> Abstract
> >>>>
> >>>>
> >>>>   This document specifies the "Depth-First Forwarding" (DFF) protoco=
l
> >>>>   for IPv6 networks, a data forwarding mechanism that can increase
> >>>>   reliability of data delivery in networks with dynamic topology
> and/or
> >>>>   lossy links.  The protocol operates entirely on the forwarding
> plane,
> >>>>   but may interact with the routing plane.  DFF forwards data packet=
s
> >>>>   using a mechanism similar to a "depth-first search" for the
> >>>>   destination of a packet.  The routing plane may be informed of
> >>>>   failures to deliver a packet or loops.  This document specifies th=
e
> >>>>   DFF mechanism both for IPv6 networks (as specified in RFC2460) and
> in
> >>>>   addition also for LoWPAN "mesh-under" networks (as specified in
> >>>>   RFC4944).
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> The file can be obtained via
> >>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
> >>>>
> >>>> IESG discussion can be tracked via
> >>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
> >>>>
> >>>>
> >>>> The following IPR Declarations may be related to this I-D:
> >>>>
> >>>>   http://datatracker.ietf.org/ipr/1645/
> >>>>   http://datatracker.ietf.org/ipr/1646/
> >>
>

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

<div>Could you give your summary experience of implementing DFF and which n=
etwork was it deployed/tested in and the summary result? I think this infor=
mation will help other users and also the IESG to make future decisions=A0:=
-)</div>
<div>=A0</div><div>AB<br><br></div><div class=3D"gmail_quote">On Mon, Feb 2=
5, 2013 at 11:01 PM, Thomas Heide Clausen <span dir=3D"ltr">&lt;<a href=3D"=
mailto:ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org</a>=
&gt;</span> wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-=
color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=
=3D"gmail_quote">Note, I am not an author of this particular document, but =
I&#39;ve got some experimental and operational experience with it - having =
implemented DFF and built deployments including it.<br>

<div class=3D"im"><br>
On 25 f=E9vr. 2013, at 06:59, Abdussalam Baryun &lt;<a href=3D"mailto:abdus=
salambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Reply to your request dated 07/02/2013<br>
&gt; Draft Reviewed By: Abdussalam Baryun (AB) =A0 Dated: 24/02/2013<br>
&gt;<br>
&gt; Reviewer Comment #AB3: Related to Processing and interaction with othe=
rs.<br>
&gt; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
&gt;<br>
&gt; In section 11<br>
&gt; AB&gt;The DFF MUST contain the next hop of RIB, but in section 5 it me=
ntions MAY.<br>
&gt; AB&gt;suggest&gt; please amend both should be same requirement for pro=
tocol.<br>
&gt;<br>
&gt; AB&gt; the way it determines the next hop does not show that this<br>
&gt; protocol is sensitive to other parameters in the RIB, it just takes<br=
>
&gt; the addresses without considering the routing protocol strategy in its=
<br>
&gt; RIB. IMHO, this may make the DFF make mistakes in taking the right<br>
&gt; next hop<br>
<br>
</div>What you say above doesn&#39;t make any sense. DFF considers the cont=
ent of the RIB, among other information, and recommends following the &quot=
;next hop&quot; indicated in the RIB first - i.e., DFF explicitly takes the=
 &quot;right next hop&quot; according to &quot;the routing protocol strateg=
y&quot; as expressed in the RIB.<br>

<br>
Of course, if you happen to know more about what the routing protocol does =
(e.g., have access to internal state of the routing protocol), you could do=
 something more clever - DFF doesn&#39;t prohibit that either, so I think t=
hat the authors struck a nice middle ground here.<br>

<div class=3D"im"><br>
&gt; Section 12<br>
&gt; AB&gt; is not understood, it seems a general not specific, I suggest m=
ore<br>
&gt; explaining how this interaction with routing protocol is occured?<br>
<br>
</div>It seems pretty clear to me what&#39;s expected here: signal to the r=
outing protocol (and then, whatever the routing protocol does with that sig=
nal depends on what routing protocol it is).<br>
<br>
It&#39;s, IMO, hard to be any clearer here.<br>
<div class=3D"im"><br>
<br>
&gt; Section 13<br>
&gt; AB&gt; who creates the sequence number is it the DFF or the routing<br=
>
&gt; protocol. It seems the DFF, so please specify how it will<br>
&gt; maintain/save such sequence number in this section.<br>
&gt; AB&gt; suggest this section to be : DFF Sequence Number.<br>
&gt;<br>
<br>
</div>[befuddled]<br>
<br>
Section 13 is already very clear on this.<br>
<div class=3D"im"><br>
&gt; Section 14<br>
&gt; AB&gt; again do you mean that both modes can work together. I don&#39;=
t think<br>
&gt; that you mean that, so you should specify that each routing domain<br>
&gt; MUST have one mode, and specify how to maintain that mode in such<br>
&gt; protocol.<br>
<br>
</div>Eh, here too I am befuddled. I do not see anywhere that the authors i=
ndicate that the two &quot;modes can work together&quot; - actually, the do=
cument doesn&#39;t talk about &quot;modes&quot; at all, and =A0the protocol=
 doesn&#39;t have &quot;modes&quot;.<br>

<br>
Rather, this section describes how one would use DFF, depending on what oth=
er choices are made in the network deployment. In other words: DFF doesn&#3=
9;t specify a &quot;mode&quot;, but rather says &quot;if your network is of=
 this kind, then do like that&quot;.<br>

<br>
So, I think that there&#39;s strictly nothing to change here, no need to ma=
intain a &quot;mode&quot; etc.<br>
<div class=3D"im"><br>
&gt; Overall&gt; about processing&gt;<br>
&gt; AB&gt; this protocol needs to be discussed more how it will interact w=
ith<br>
&gt; the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore<br=
>
&gt; alot of work done in the IETF which is not fiting the general<br>
&gt; applicability it is offering.<br>
<br>
</div>No, it doesn&#39;t.<br>
<br>
DFF is completely orthogonal to routing protocols<br>
<br>
DFF can (logically) layer below any routing protocol, without modifications=
 to that routing protocol.<br>
<br>
DFF can use a RIB and can provide signals to a routing protocol (or not - i=
f the routing protocol doesn&#39;t want them)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Thomas<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; +++++++++++++The END+++++++++++<br>
&gt;<br>
&gt; Regards<br>
&gt; AB<br>
&gt; ----------------------------------------------------------------------=
-----------------<br>
&gt; This message and any attachments are confidential to the intended<br>
&gt; recipient and may also be privileged. If you are not the intended<br>
&gt; recipient please delete it from your system and notify the sender.<br>
&gt; This message is in compliance with the IETF regulations.<br>
&gt; ----------------------------------------------------------------------=
-----------------<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt; On 2/7/13, The IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.=
org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The IESG has received a request from an individual submitt=
er to consider<br>
&gt;&gt;&gt;&gt; the following document:<br>
&gt;&gt;&gt;&gt; - &#39;Depth-First Forwarding in Unreliable Networks (DFF)=
&#39;<br>
&gt;&gt;&gt;&gt; =A0&lt;draft-cardenas-dff-09.txt&gt; as Experimental RFC<b=
r>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The IESG plans to make a decision in the next few weeks, a=
nd solicits<br>
&gt;&gt;&gt;&gt; final comments on this action. Please send substantive com=
ments to the<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing=
 lists by 2013-02-24. Exceptionally, comments may<br>
&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>=
 instead. In either case, please retain the<br>
&gt;&gt;&gt;&gt; beginning of the Subject line to allow automated sorting.<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Abstract<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =A0 This document specifies the &quot;Depth-First Forwardi=
ng&quot; (DFF) protocol<br>
&gt;&gt;&gt;&gt; =A0 for IPv6 networks, a data forwarding mechanism that ca=
n increase<br>
&gt;&gt;&gt;&gt; =A0 reliability of data delivery in networks with dynamic =
topology and/or<br>
&gt;&gt;&gt;&gt; =A0 lossy links. =A0The protocol operates entirely on the =
forwarding plane,<br>
&gt;&gt;&gt;&gt; =A0 but may interact with the routing plane. =A0DFF forwar=
ds data packets<br>
&gt;&gt;&gt;&gt; =A0 using a mechanism similar to a &quot;depth-first searc=
h&quot; for the<br>
&gt;&gt;&gt;&gt; =A0 destination of a packet. =A0The routing plane may be i=
nformed of<br>
&gt;&gt;&gt;&gt; =A0 failures to deliver a packet or loops. =A0This documen=
t specifies the<br>
&gt;&gt;&gt;&gt; =A0 DFF mechanism both for IPv6 networks (as specified in =
RFC2460) and in<br>
&gt;&gt;&gt;&gt; =A0 addition also for LoWPAN &quot;mesh-under&quot; networ=
ks (as specified in<br>
&gt;&gt;&gt;&gt; =A0 RFC4944).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The file can be obtained via<br>
&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-cardenas-=
dff/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-cardenas-dff/=
</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-cardenas-=
dff/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-carden=
as-dff/ballot/</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The following IPR Declarations may be related to this I-D:=
<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; =A0 <a href=3D"http://datatracker.ietf.org/ipr/1645/" targ=
et=3D"_blank">http://datatracker.ietf.org/ipr/1645/</a><br>
&gt;&gt;&gt;&gt; =A0 <a href=3D"http://datatracker.ietf.org/ipr/1646/" targ=
et=3D"_blank">http://datatracker.ietf.org/ipr/1646/</a><br>
&gt;&gt;<br>
</div></div></blockquote></div><br>

--047d7b2e42a2a5acef04d69ef9f6--

From ietf@thomasclausen.org  Tue Feb 26 03:51:39 2013
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0CFD21F8962; Tue, 26 Feb 2013 03:51:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.51
X-Spam-Level: 
X-Spam-Status: No, score=-0.51 tagged_above=-999 required=5 tests=[AWL=0.092,  BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_23=0.6, 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 h8RWVX06kwjL; Tue, 26 Feb 2013 03:51:38 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id BC10621F8949; Tue, 26 Feb 2013 03:51:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A41B51C0345; Tue, 26 Feb 2013 03:51:38 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.137] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 113D81C00CB; Tue, 26 Feb 2013 03:51:37 -0800 (PST)
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com> <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com> <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com> <8BFFD20F-58D8-4118-9F81-EF760A6DDB3A@thomasclausen.org> <CADnDZ8_5oX7-=zw7RGnKo3NgzfEXG+gzJKgBm3Y1Dw5SDfckMQ@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CADnDZ8_5oX7-=zw7RGnKo3NgzfEXG+gzJKgBm3Y1Dw5SDfckMQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-CFDC1B3F-C9C4-4E0D-96F1-8A10B635508B
Content-Transfer-Encoding: 7bit
Message-Id: <A3EB9430-2B0D-495A-A171-B98E767512A2@thomasclausen.org>
X-Mailer: iPad Mail (10B141)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
Date: Tue, 26 Feb 2013 12:51:35 +0100
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Cc: "draft-cardenas-dff@tools.ietf.org" <draft-cardenas-dff@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 11:51:40 -0000

--Apple-Mail-CFDC1B3F-C9C4-4E0D-96F1-8A10B635508B
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 26 f=C3=A9vr. 2013, at 12:29, Abdussalam Baryun <abdussalambaryun@gmail.c=
om> wrote:

> Could you give your summary experience of implementing DFF and which netwo=
rk was it deployed/tested in and the summary result? I think this informatio=
n will help other users and also the IESG to make future decisions :-)

Well, it was about a day worth of implementation effort. Testing in the lab w=
ith various ROLL and MANET routing protocols, and OSPF, was trivial: grab of=
f-the-shelf implementation of the routing protocol, run as usual, marvel at t=
he results ;)

It has been deployed outside of the lab. I cannot go too much into the detai=
ls of those deployments, other than say that the experience matched that whi=
ch we saw in the lab quite nicely.

We've tested over different L2's, including proprietary low-power wireless, W=
iFi, PLC, Ethernet...saw no ill effect and for all but Ethernet observed goo=
d performance improvements (we included Ethernet in our testing, where there=
 were no effects at all, simply to have a baseline).

What's your experience with this protocol, AB? You seem to be very intereste=
d in it, do you have any experimental or operational data to share?

Thomas

>  AB
>=20
> On Mon, Feb 25, 2013 at 11:01 PM, Thomas Heide Clausen <ietf@thomasclausen=
.org> wrote:
>> Note, I am not an author of this particular document, but I've got some e=
xperimental and operational experience with it - having implemented DFF and b=
uilt deployments including it.
>>=20
>> On 25 f=C3=A9vr. 2013, at 06:59, Abdussalam Baryun <abdussalambaryun@gmai=
l.com> wrote:
>>=20
>> > Reply to your request dated 07/02/2013
>> > Draft Reviewed By: Abdussalam Baryun (AB)   Dated: 24/02/2013
>> >
>> > Reviewer Comment #AB3: Related to Processing and interaction with other=
s.
>> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> >
>> > In section 11
>> > AB>The DFF MUST contain the next hop of RIB, but in section 5 it mentio=
ns MAY.
>> > AB>suggest> please amend both should be same requirement for protocol.
>> >
>> > AB> the way it determines the next hop does not show that this
>> > protocol is sensitive to other parameters in the RIB, it just takes
>> > the addresses without considering the routing protocol strategy in its
>> > RIB. IMHO, this may make the DFF make mistakes in taking the right
>> > next hop
>>=20
>> What you say above doesn't make any sense. DFF considers the content of t=
he RIB, among other information, and recommends following the "next hop" ind=
icated in the RIB first - i.e., DFF explicitly takes the "right next hop" ac=
cording to "the routing protocol strategy" as expressed in the RIB.
>>=20
>> Of course, if you happen to know more about what the routing protocol doe=
s (e.g., have access to internal state of the routing protocol), you could d=
o something more clever - DFF doesn't prohibit that either, so I think that t=
he authors struck a nice middle ground here.
>>=20
>> > Section 12
>> > AB> is not understood, it seems a general not specific, I suggest more
>> > explaining how this interaction with routing protocol is occured?
>>=20
>> It seems pretty clear to me what's expected here: signal to the routing p=
rotocol (and then, whatever the routing protocol does with that signal depen=
ds on what routing protocol it is).
>>=20
>> It's, IMO, hard to be any clearer here.
>>=20
>>=20
>> > Section 13
>> > AB> who creates the sequence number is it the DFF or the routing
>> > protocol. It seems the DFF, so please specify how it will
>> > maintain/save such sequence number in this section.
>> > AB> suggest this section to be : DFF Sequence Number.
>> >
>>=20
>> [befuddled]
>>=20
>> Section 13 is already very clear on this.
>>=20
>> > Section 14
>> > AB> again do you mean that both modes can work together. I don't think
>> > that you mean that, so you should specify that each routing domain
>> > MUST have one mode, and specify how to maintain that mode in such
>> > protocol.
>>=20
>> Eh, here too I am befuddled. I do not see anywhere that the authors indic=
ate that the two "modes can work together" - actually, the document doesn't t=
alk about "modes" at all, and  the protocol doesn't have "modes".
>>=20
>> Rather, this section describes how one would use DFF, depending on what o=
ther choices are made in the network deployment. In other words: DFF doesn't=
 specify a "mode", but rather says "if your network is of this kind, then do=
 like that".
>>=20
>> So, I think that there's strictly nothing to change here, no need to main=
tain a "mode" etc.
>>=20
>> > Overall> about processing>
>> > AB> this protocol needs to be discussed more how it will interact with
>> > the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore
>> > alot of work done in the IETF which is not fiting the general
>> > applicability it is offering.
>>=20
>> No, it doesn't.
>>=20
>> DFF is completely orthogonal to routing protocols
>>=20
>> DFF can (logically) layer below any routing protocol, without modificatio=
ns to that routing protocol.
>>=20
>> DFF can use a RIB and can provide signals to a routing protocol (or not -=
 if the routing protocol doesn't want them)
>>=20
>> Thomas
>>=20
>> > +++++++++++++The END+++++++++++
>> >
>> > Regards
>> > AB
>> > -----------------------------------------------------------------------=
----------------
>> > This message and any attachments are confidential to the intended
>> > recipient and may also be privileged. If you are not the intended
>> > recipient please delete it from your system and notify the sender.
>> > This message is in compliance with the IETF regulations.
>> > -----------------------------------------------------------------------=
----------------
>> >
>> >
>> >>> On 2/7/13, The IESG <iesg-secretary@ietf.org> wrote:
>> >>>>
>> >>>> The IESG has received a request from an individual submitter to cons=
ider
>> >>>> the following document:
>> >>>> - 'Depth-First Forwarding in Unreliable Networks (DFF)'
>> >>>>  <draft-cardenas-dff-09.txt> as Experimental RFC
>> >>>>
>> >>>> The IESG plans to make a decision in the next few weeks, and solicit=
s
>> >>>> final comments on this action. Please send substantive comments to t=
he
>> >>>> ietf@ietf.org mailing lists by 2013-02-24. Exceptionally, comments m=
ay
>> >>>> be
>> >>>> sent to iesg@ietf.org instead. In either case, please retain the
>> >>>> beginning of the Subject line to allow automated sorting.
>> >>>>
>> >>>> Abstract
>> >>>>
>> >>>>
>> >>>>   This document specifies the "Depth-First Forwarding" (DFF) protoco=
l
>> >>>>   for IPv6 networks, a data forwarding mechanism that can increase
>> >>>>   reliability of data delivery in networks with dynamic topology and=
/or
>> >>>>   lossy links.  The protocol operates entirely on the forwarding pla=
ne,
>> >>>>   but may interact with the routing plane.  DFF forwards data packet=
s
>> >>>>   using a mechanism similar to a "depth-first search" for the
>> >>>>   destination of a packet.  The routing plane may be informed of
>> >>>>   failures to deliver a packet or loops.  This document specifies th=
e
>> >>>>   DFF mechanism both for IPv6 networks (as specified in RFC2460) and=
 in
>> >>>>   addition also for LoWPAN "mesh-under" networks (as specified in
>> >>>>   RFC4944).
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> The file can be obtained via
>> >>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/
>> >>>>
>> >>>> IESG discussion can be tracked via
>> >>>> http://datatracker.ietf.org/doc/draft-cardenas-dff/ballot/
>> >>>>
>> >>>>
>> >>>> The following IPR Declarations may be related to this I-D:
>> >>>>
>> >>>>   http://datatracker.ietf.org/ipr/1645/
>> >>>>   http://datatracker.ietf.org/ipr/1646/
>> >>
>=20

--Apple-Mail-CFDC1B3F-C9C4-4E0D-96F1-8A10B635508B
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>On 26 f=C3=A9vr. 2013, at 12:29, Abdus=
salam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com">abdussalambar=
yun@gmail.com</a>&gt; wrote:</div><div><br></div><blockquote type=3D"cite"><=
div><div>Could you give your summary experience of implementing DFF and whic=
h network was it deployed/tested in and the summary result? I think this inf=
ormation will help other users and also the IESG to make future decisions&nb=
sp;:-)</div>
</div></blockquote><div><br></div><div>Well, it was about a day worth of imp=
lementation effort. Testing in the lab with various ROLL and MANET routing p=
rotocols, and OSPF, was trivial: grab off-the-shelf implementation of the ro=
uting protocol, run as usual, marvel at the results ;)</div><div><br></div><=
div>It has been deployed outside of the lab. I cannot go too much into the d=
etails of those deployments, other than say that the experience matched that=
 which we saw in the lab quite nicely.</div><div><br></div><div>We've tested=
 over different L2's, including proprietary low-power wireless, WiFi, PLC, E=
thernet...saw no ill effect and for all but Ethernet observed good performan=
ce improvements (we included Ethernet in our testing, where there were no ef=
fects at all, simply to have a baseline).</div><div><br></div><div>What's yo=
ur experience with this protocol, AB? You seem to be very interested in it, d=
o you have any experimental or operational data to share?</div><div><br></di=
v><div>Thomas</div><div><br></div><div><blockquote type=3D"cite"><div><div>&=
nbsp;AB</div><div><br></div><div class=3D"gmail_quote">On Mon, Feb 25, 2013 a=
t 11:01 PM, Thomas Heide Clausen <span dir=3D"ltr">&lt;<a href=3D"mailto:iet=
f@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt;</span>=
 wrote:<br>
<blockquote style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-c=
olor:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class=3D=
"gmail_quote">Note, I am not an author of this particular document, but I've=
 got some experimental and operational experience with it - having implement=
ed DFF and built deployments including it.<br>

<div class=3D"im"><br>
On 25 f=C3=A9vr. 2013, at 06:59, Abdussalam Baryun &lt;<a href=3D"mailto:abd=
ussalambaryun@gmail.com">abdussalambaryun@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Reply to your request dated 07/02/2013<br>
&gt; Draft Reviewed By: Abdussalam Baryun (AB) &nbsp; Dated: 24/02/2013<br>
&gt;<br>
&gt; Reviewer Comment #AB3: Related to Processing and interaction with other=
s.<br>
&gt; ++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
&gt;<br>
&gt; In section 11<br>
&gt; AB&gt;The DFF MUST contain the next hop of RIB, but in section 5 it men=
tions MAY.<br>
&gt; AB&gt;suggest&gt; please amend both should be same requirement for prot=
ocol.<br>
&gt;<br>
&gt; AB&gt; the way it determines the next hop does not show that this<br>
&gt; protocol is sensitive to other parameters in the RIB, it just takes<br>=

&gt; the addresses without considering the routing protocol strategy in its<=
br>
&gt; RIB. IMHO, this may make the DFF make mistakes in taking the right<br>
&gt; next hop<br>
<br>
</div>What you say above doesn't make any sense. DFF considers the content o=
f the RIB, among other information, and recommends following the "next hop" i=
ndicated in the RIB first - i.e., DFF explicitly takes the "right next hop" a=
ccording to "the routing protocol strategy" as expressed in the RIB.<br>

<br>
Of course, if you happen to know more about what the routing protocol does (=
e.g., have access to internal state of the routing protocol), you could do s=
omething more clever - DFF doesn't prohibit that either, so I think that the=
 authors struck a nice middle ground here.<br>

<div class=3D"im"><br>
&gt; Section 12<br>
&gt; AB&gt; is not understood, it seems a general not specific, I suggest mo=
re<br>
&gt; explaining how this interaction with routing protocol is occured?<br>
<br>
</div>It seems pretty clear to me what's expected here: signal to the routin=
g protocol (and then, whatever the routing protocol does with that signal de=
pends on what routing protocol it is).<br>
<br>
It's, IMO, hard to be any clearer here.<br>
<div class=3D"im"><br>
<br>
&gt; Section 13<br>
&gt; AB&gt; who creates the sequence number is it the DFF or the routing<br>=

&gt; protocol. It seems the DFF, so please specify how it will<br>
&gt; maintain/save such sequence number in this section.<br>
&gt; AB&gt; suggest this section to be : DFF Sequence Number.<br>
&gt;<br>
<br>
</div>[befuddled]<br>
<br>
Section 13 is already very clear on this.<br>
<div class=3D"im"><br>
&gt; Section 14<br>
&gt; AB&gt; again do you mean that both modes can work together. I don't thi=
nk<br>
&gt; that you mean that, so you should specify that each routing domain<br>
&gt; MUST have one mode, and specify how to maintain that mode in such<br>
&gt; protocol.<br>
<br>
</div>Eh, here too I am befuddled. I do not see anywhere that the authors in=
dicate that the two "modes can work together" - actually, the document doesn=
't talk about "modes" at all, and &nbsp;the protocol doesn't have "modes".<b=
r>

<br>
Rather, this section describes how one would use DFF, depending on what othe=
r choices are made in the network deployment. In other words: DFF doesn't sp=
ecify a "mode", but rather says "if your network is of this kind, then do li=
ke that".<br>

<br>
So, I think that there's strictly nothing to change here, no need to maintai=
n a "mode" etc.<br>
<div class=3D"im"><br>
&gt; Overall&gt; about processing&gt;<br>
&gt; AB&gt; this protocol needs to be discussed more how it will interact wi=
th<br>
&gt; the routing protocols in MANET, 6LowPAN, ROLL. The documents ignore<br>=

&gt; alot of work done in the IETF which is not fiting the general<br>
&gt; applicability it is offering.<br>
<br>
</div>No, it doesn't.<br>
<br>
DFF is completely orthogonal to routing protocols<br>
<br>
DFF can (logically) layer below any routing protocol, without modifications t=
o that routing protocol.<br>
<br>
DFF can use a RIB and can provide signals to a routing protocol (or not - if=
 the routing protocol doesn't want them)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Thomas<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; +++++++++++++The END+++++++++++<br>
&gt;<br>
&gt; Regards<br>
&gt; AB<br>
&gt; -----------------------------------------------------------------------=
----------------<br>
&gt; This message and any attachments are confidential to the intended<br>
&gt; recipient and may also be privileged. If you are not the intended<br>
&gt; recipient please delete it from your system and notify the sender.<br>
&gt; This message is in compliance with the IETF regulations.<br>
&gt; -----------------------------------------------------------------------=
----------------<br>
&gt;<br>
&gt;<br>
&gt;&gt;&gt; On 2/7/13, The IESG &lt;<a href=3D"mailto:iesg-secretary@ietf.o=
rg">iesg-secretary@ietf.org</a>&gt; wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The IESG has received a request from an individual submitte=
r to consider<br>
&gt;&gt;&gt;&gt; the following document:<br>
&gt;&gt;&gt;&gt; - 'Depth-First Forwarding in Unreliable Networks (DFF)'<br>=

&gt;&gt;&gt;&gt; &nbsp;&lt;draft-cardenas-dff-09.txt&gt; as Experimental RFC=
<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The IESG plans to make a decision in the next few weeks, an=
d solicits<br>
&gt;&gt;&gt;&gt; final comments on this action. Please send substantive comm=
ents to the<br>
&gt;&gt;&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing l=
ists by 2013-02-24. Exceptionally, comments may<br>
&gt;&gt;&gt;&gt; be<br>
&gt;&gt;&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> i=
nstead. In either case, please retain the<br>
&gt;&gt;&gt;&gt; beginning of the Subject line to allow automated sorting.<b=
r>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Abstract<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &nbsp; This document specifies the "Depth-First Forwarding"=
 (DFF) protocol<br>
&gt;&gt;&gt;&gt; &nbsp; for IPv6 networks, a data forwarding mechanism that c=
an increase<br>
&gt;&gt;&gt;&gt; &nbsp; reliability of data delivery in networks with dynami=
c topology and/or<br>
&gt;&gt;&gt;&gt; &nbsp; lossy links. &nbsp;The protocol operates entirely on=
 the forwarding plane,<br>
&gt;&gt;&gt;&gt; &nbsp; but may interact with the routing plane. &nbsp;DFF f=
orwards data packets<br>
&gt;&gt;&gt;&gt; &nbsp; using a mechanism similar to a "depth-first search" f=
or the<br>
&gt;&gt;&gt;&gt; &nbsp; destination of a packet. &nbsp;The routing plane may=
 be informed of<br>
&gt;&gt;&gt;&gt; &nbsp; failures to deliver a packet or loops. &nbsp;This do=
cument specifies the<br>
&gt;&gt;&gt;&gt; &nbsp; DFF mechanism both for IPv6 networks (as specified i=
n RFC2460) and in<br>
&gt;&gt;&gt;&gt; &nbsp; addition also for LoWPAN "mesh-under" networks (as s=
pecified in<br>
&gt;&gt;&gt;&gt; &nbsp; RFC4944).<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The file can be obtained via<br>
&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-cardenas-d=
ff/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-cardenas-dff/</=
a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt;&gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-cardenas-d=
ff/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-cardenas=
-dff/ballot/</a><br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The following IPR Declarations may be related to this I-D:<=
br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &nbsp; <a href=3D"http://datatracker.ietf.org/ipr/1645/" ta=
rget=3D"_blank">http://datatracker.ietf.org/ipr/1645/</a><br>
&gt;&gt;&gt;&gt; &nbsp; <a href=3D"http://datatracker.ietf.org/ipr/1646/" ta=
rget=3D"_blank">http://datatracker.ietf.org/ipr/1646/</a><br>
&gt;&gt;<br>
</div></div></blockquote></div><br>
</div></blockquote></div></body></html>=

--Apple-Mail-CFDC1B3F-C9C4-4E0D-96F1-8A10B635508B--

From abdussalambaryun@gmail.com  Tue Feb 26 04:12:42 2013
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1247821F8A45 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 04:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.55
X-Spam-Level: 
X-Spam-Status: No, score=-3.55 tagged_above=-999 required=5 tests=[AWL=0.048,  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 JuSBLnUPZOYZ for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 04:12:41 -0800 (PST)
Received: from mail-da0-f48.google.com (mail-da0-f48.google.com [209.85.210.48]) by ietfa.amsl.com (Postfix) with ESMTP id 35F8B21F8901 for <ietf@ietf.org>; Tue, 26 Feb 2013 04:12:41 -0800 (PST)
Received: by mail-da0-f48.google.com with SMTP id w4so1981982dam.21 for <ietf@ietf.org>; Tue, 26 Feb 2013 04:12:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=5RZC2V3zSPPc4uS3biCbN3zEmKu0bPkt8P4HhLmzdCM=; b=SVB3P0YCvqXNabhjv/KRtJeyCmwVXaqoXCo53SpZPHe23gZ9fnR6f/oZ1wgcLRr7M5 LEYixVuzoG7jV9ysUWUVmyVMWCnxZvm0cIlMlcgT+G/wz+tu0IMfTgPrk44dF+Ge0crQ iRtVR7x8UxcaDDAdQFdiGiTGLKlmbA4QhXy12cTIIqyr6g9nLYLzgXBHZpE0reBDvgbB 8ntDvDMvLAll9JL4Va99W9QxZRYb/0RyyvbayYvmSujSTuvG6QFmMINUoBDS4QRWZjer c6dutKOY6WlOXhMbd1INm7TmOGPxrGFe6rACBb97EWJ0lAhYESTb6xSNki8dVpO/vr9J nA9Q==
MIME-Version: 1.0
X-Received: by 10.68.153.97 with SMTP id vf1mr23064642pbb.93.1361880760958; Tue, 26 Feb 2013 04:12:40 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Tue, 26 Feb 2013 04:12:40 -0800 (PST)
In-Reply-To: <A3EB9430-2B0D-495A-A171-B98E767512A2@thomasclausen.org>
References: <20130207132146.18387.62853.idtracker@ietfa.amsl.com> <CADnDZ8_twkd7pi=8z7P=k4uWn6S8UqY1-eJKDBe_Emw_TZBoUA@mail.gmail.com> <CADnDZ888ma4+tM2LLuAdr9CYiLT44KA1OjJkADaYhNWpgGrKmA@mail.gmail.com> <CADnDZ8_AasAnnZuWhd8Oy16Q5q1U16i0zBuYaN=LeTmRnN9USQ@mail.gmail.com> <8BFFD20F-58D8-4118-9F81-EF760A6DDB3A@thomasclausen.org> <CADnDZ8_5oX7-=zw7RGnKo3NgzfEXG+gzJKgBm3Y1Dw5SDfckMQ@mail.gmail.com> <A3EB9430-2B0D-495A-A171-B98E767512A2@thomasclausen.org>
Date: Tue, 26 Feb 2013 12:12:40 +0000
Message-ID: <CADnDZ88EpT4R5UiC3mPW95Z+Qzuwvxy0aa=+VejgeqjHG6=Hew@mail.gmail.com>
Subject: Re: Last Call: <draft-cardenas-dff-09.txt> (Depth-First Forwarding in Unreliable Networks (DFF)) to Experimental RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Heide Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=f46d041701bdfbd8ea04d69f92e8
Cc: "draft-cardenas-dff@tools.ietf.org" <draft-cardenas-dff@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 12:12:42 -0000

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

On Tue, Feb 26, 2013 at 11:51 AM, Thomas Heide Clausen <
ietf@thomasclausen.org> wrote:

> On 26 f=E9vr. 2013, at 12:29, Abdussalam Baryun <abdussalambaryun@gmail.c=
om>
> wrote:
>
> Could you give your summary experience of implementing DFF and which
> network was it deployed/tested in and the summary result? I think this
> information will help other users and also the IESG to make future
> decisions :-)
>
>
> Well, it was about a day worth of implementation effort. Testing in the
> lab with various ROLL and MANET routing protocols, and OSPF, was trivial:
> grab off-the-shelf implementation of the routing protocol, run as usual,
> marvel at the results ;)
>
> It has been deployed outside of the lab. I cannot go too much into the
> details of those deployments, other than say that the experience matched
> that which we saw in the lab quite nicely.
>
> We've tested over different L2's, including proprietary low-power
> wireless, WiFi, PLC, Ethernet...saw no ill effect and for all but Etherne=
t
> observed good performance improvements (we included Ethernet in our
> testing, where there were no effects at all, simply to have a baseline).
>
> What's your experience with this protocol, AB? You seem to be very
> interested in it, do you have any experimental or operational data to sha=
re?
>
>
My experience with the protocol is reading experience only as it is an
individual work, and may go into implementation if I know future works
related. However, I thank you for your input because it is important,

AB

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

<div class=3D"gmail_quote">On Tue, Feb 26, 2013 at 11:51 AM, Thomas Heide C=
lausen <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf@thomasclausen.org" targ=
et=3D"_blank">ietf@thomasclausen.org</a>&gt;</span> wrote:<br><blockquote s=
tyle=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204=
,204,204);border-left-width:1px;border-left-style:solid" class=3D"gmail_quo=
te">
<div dir=3D"auto"><div class=3D"im"><div>On 26 f=E9vr. 2013, at 12:29, Abdu=
ssalam Baryun &lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_=
blank">abdussalambaryun@gmail.com</a>&gt; wrote:</div><div><br></div><block=
quote type=3D"cite">
<div><div>Could you give your summary experience of implementing DFF and wh=
ich network was it deployed/tested in and the summary result? I think this =
information will help other users and also the IESG to make future decision=
s=A0:-)</div>

</div></blockquote><div><br></div></div><div>Well, it was about a day worth=
 of implementation effort. Testing in the lab with various ROLL and MANET r=
outing protocols, and OSPF, was trivial: grab off-the-shelf implementation =
of the routing protocol, run as usual, marvel at the results ;)</div>
<div><br></div><div>It has been deployed outside of the lab. I cannot go to=
o much into the details of those deployments, other than say that the exper=
ience matched that which we saw in the lab quite nicely.</div><div><br>
</div><div>We&#39;ve tested over different L2&#39;s, including proprietary =
low-power wireless, WiFi, PLC, Ethernet...saw no ill effect and for all but=
 Ethernet observed good performance improvements (we included Ethernet in o=
ur testing, where there were no effects at all, simply to have a baseline).=
</div>
<div><br></div><div>What&#39;s your experience with this protocol, AB? You =
seem to be very interested in it, do you have any experimental or operation=
al data to share?</div><span class=3D"HOEnZb"><font color=3D"#888888"><div>
<br></div></font></span></div></blockquote><div>=A0</div><div>My experience=
 with the protocol is reading experience only as it is an individual work, =
and may go into implementation if I know future works related. However, I t=
hank you for your input because it is important,</div>
<div>=A0</div><div>AB</div><div>=A0</div></div>

--f46d041701bdfbd8ea04d69f92e8--

From wesley.george@twcable.com  Tue Feb 26 06:42:19 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0269521F8A79 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 06:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.534
X-Spam-Level: 
X-Spam-Status: No, score=-0.534 tagged_above=-999 required=5 tests=[AWL=-0.071, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpMo5SQuhE-3 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 06:42:18 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 6641021F8A6B for <ietf@ietf.org>; Tue, 26 Feb 2013 06:42:18 -0800 (PST)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,740,1355115600"; d="scan'208";a="32673162"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 26 Feb 2013 09:41:25 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Tue, 26 Feb 2013 09:42:18 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: SM <sm@resistor.net>, Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Tue, 26 Feb 2013 09:42:16 -0500
Subject: RE: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
Thread-Topic: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
Thread-Index: Ac4TrlLiys1+NJeKSLaootl1V3HOdQAfrbyg
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923041E9A7D16@PRVPEXVS15.corp.twcable.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net>
In-Reply-To: <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 26 Feb 2013 14:42:19 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M

> In Section 5:
>
>    "For cases of first time attendees for a specific location, relevant
>     information can be gathered from attendees that have previously
>     visited the city."
>
> There are recurrent discussions as nobody volunteered to gather that
> information in one place.

[WEG] Perhaps a model similar to RFC 6640 would be appropriate - having thi=
s draft explicitly recommend use of a wiki or other semi-permanent method t=
o store and share information collaboratively about specific locations' hea=
lthy/restricted diet options based on past experience. It could probably be=
 a persistent subsection of the IETF meeting wiki, or it could just as easi=
ly be a pointer to a non-IETF-specific external website that is set up with=
 precisely this goal (helping travelers with special dietary needs meet the=
ir requirements in strange cities) in mind.

Wes George


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

From mary.ietf.barnes@gmail.com  Tue Feb 26 07:09:26 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E575021F8706 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 07:09:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.577
X-Spam-Level: 
X-Spam-Status: No, score=-103.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 MUK+zHW3wwx9 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 07:09:26 -0800 (PST)
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3CF21F8756 for <ietf@ietf.org>; Tue, 26 Feb 2013 07:09:26 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id z4so2493001qan.5 for <ietf@ietf.org>; Tue, 26 Feb 2013 07:09:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=P31Um75C8tMwVpouzMzZD9dMY3POEEaKrJagAUTzDgE=; b=Tz/CJyEse5MEXfrD/+xmyYDMshnvXFgCT2EV6/s7tdKVLzQ3Gk0KcVceYp/4eowfEr P4/mOmxtPDrjfY37mgz98BP871B+nf1SNnHlvnfxJ6DwjFWkdZSfXXEcFrnx/D1QHa59 Jkv3bvGITwj24lbdngoJKXCf950fmlPvwzuQInrEJ32WgDtfiL7IofMrp9go9C8c/26W KunG+K2LZCMB5qs/jdEsc5PG/1/uFW8iLhhw4x1Ha0sYqtlgciqr81vVmQpzsek9dEZ8 i3L4Rf2nmdc/QF6B9NfuvCHekGRtN/CMGj0aeLAVh5LGN3V9apLgrceJqCcdh4q3aCIg Fzng==
MIME-Version: 1.0
X-Received: by 10.49.96.33 with SMTP id dp1mr20734845qeb.60.1361891365674; Tue, 26 Feb 2013 07:09:25 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Tue, 26 Feb 2013 07:09:25 -0800 (PST)
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923041E9A7D16@PRVPEXVS15.corp.twcable.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923041E9A7D16@PRVPEXVS15.corp.twcable.com>
Date: Tue, 26 Feb 2013 09:09:25 -0600
Message-ID: <CAHBDyN5g4eYWRrmkOPj_N9PusWZhPH6b+MgsjuwF9nNNBxzjrw@mail.gmail.com>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 15:09:27 -0000

On Tue, Feb 26, 2013 at 8:42 AM, George, Wes <wesley.george@twcable.com> wr=
ote:
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
SM
>
>> In Section 5:
>>
>>    "For cases of first time attendees for a specific location, relevant
>>     information can be gathered from attendees that have previously
>>     visited the city."
>>
>> There are recurrent discussions as nobody volunteered to gather that
>> information in one place.
>
> [WEG] Perhaps a model similar to RFC 6640 would be appropriate - having t=
his draft explicitly recommend use of a wiki or other semi-permanent method=
 to store and share information collaboratively about specific locations' h=
ealthy/restricted diet options based on past experience. It could probably =
be a persistent subsection of the IETF meeting wiki, or it could just as ea=
sily be a pointer to a non-IETF-specific external website that is set up wi=
th precisely this goal (helping travelers with special dietary needs meet t=
heir requirements in strange cities) in mind.
[MB] That's an excellent suggestion in terms of information sharing.
We have been doing that on the IETF food list, but for the cities that
we re-visit on a regular basis, having this more widely available on a
wiki would be helpful.  Perhaps, we could add something to the tools
page and do it by meeting location to include all the logistics
(including the food) and have it more permanent. [/MB]
>
> Wes George
>
>
> This E-mail and any of its attachments may contain Time Warner Cable prop=
rietary information, which is privileged, confidential, or subject to copyr=
ight belonging to Time Warner Cable. This E-mail is intended solely for the=
 use of the individual or entity to which it is addressed. If you are not t=
he intended recipient of this E-mail, you are hereby notified that any diss=
emination, distribution, copying, or action taken in relation to the conten=
ts of and attachments to this E-mail is strictly prohibited and may be unla=
wful. If you have received this E-mail in error, please notify the sender i=
mmediately and permanently delete the original and any copy of this E-mail =
and any printout.

From worley@shell01.TheWorld.com  Tue Feb 26 11:01:18 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72C2521F8745 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:01:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Level: 
X-Spam-Status: No, score=-2.748 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mb4EA76c-QxR for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:01:18 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id B80C021F8727 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:01:17 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1QJ18ZI002662; Tue, 26 Feb 2013 14:01:11 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1QJ18Ap2690214; Tue, 26 Feb 2013 14:01:08 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1QJ17ZL2693351; Tue, 26 Feb 2013 14:01:07 -0500 (EST)
Date: Tue, 26 Feb 2013 14:01:07 -0500 (EST)
Message-Id: <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: James Polk <jmpolk@cisco.com>, ietf@ietf.org
In-reply-to: <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> (jmpolk@cisco.com)
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.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, 26 Feb 2013 19:01:18 -0000

> From: James Polk <jmpolk@cisco.com>
> 
> >It used to be 5 PM Pacific, now it's 24:00 UTC.
> 
> It's always been 2400 UTC, but with all the daylight savings time 
> adjustments from country to country changing from year to year, I 
> have talked to the Secretariat before (and recently), and verified 
> this is indeed 8pm ET, at least for those in the US.

Well, 2400 UTC is 8pm Eastern Daylight (i.e., summer) Time (GMT-4),
but 7pm Eastern Standard Time (GMT-5).  So I'd ask *when* did the
Secretariat tell you that?

Personally, I'd trust "date -u" much sooner than any random person.
Even better:

    $ date --date='00:00 Feb 26, 2013 UTC'
    Mon Feb 25 19:00:00 EST 2013
    $ 

Dale

From john+ietf@jck.com  Tue Feb 26 09:36:36 2013
Return-Path: <john+ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7463421F883B for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 09:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GOpVdzuokzF1 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 09:36:36 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EDE5C21F883A for <ietf@ietf.org>; Tue, 26 Feb 2013 09:36:35 -0800 (PST)
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 1UAOS8-0001aY-Kt; Tue, 26 Feb 2013 12:36:32 -0500
Date: Tue, 26 Feb 2013 12:36:26 -0500
From: John C Klensin <john+ietf@jck.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, "George, Wes" <wesley.george@twcable.com>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
Message-ID: <897437F0B6CE3B5211E74305@JcK-HP8200.jck.com>
In-Reply-To: <CAHBDyN5g4eYWRrmkOPj_N9PusWZhPH6b+MgsjuwF9nNNBxzjrw@mail.gmail.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923041E9A7D16@PRVPEXVS15.corp.twcable.com> <CAHBDyN5g4eYWRrmkOPj_N9PusWZhPH6b+MgsjuwF9nNNBxzjrw@mail.gmail.c om>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Tue, 26 Feb 2013 11:09:24 -0800
Cc: SM <sm@resistor.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 17:36:36 -0000

--On Tuesday, February 26, 2013 09:09 -0600 Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:

>> [WEG] Perhaps a model similar to RFC 6640 would be
>> appropriate - having this draft explicitly recommend use of a
>> wiki or other semi-permanent method to store and share
>> information collaboratively about specific locations'
>> healthy/restricted diet options based on past experience. It
>> could probably be a persistent subsection of the IETF meeting
>> wiki, or it could just as easily be a pointer to a
>> non-IETF-specific external website that is set up with
>> precisely this goal (helping travelers with special dietary
>> needs meet their requirements in strange cities) in mind.

> [MB] That's an excellent suggestion in terms of information
> sharing. We have been doing that on the IETF food list, but
> for the cities that we re-visit on a regular basis, having
> this more widely available on a wiki would be helpful.
> Perhaps, we could add something to the tools page and do it by
> meeting location to include all the logistics (including the
> food) and have it more permanent. [/MB]

Let me suggest a small refinement.  See if you can separate the
"help in particular locations" issues from the "if there aren't
answers to these questions, we can't go there" ones.  Then we
need to make that list clear to the IASA in "a site visit isn't
complete without answers" form.  The specific answers and
optimizations are going to differ from site to site --and that
is where community input and wikis are useful-- but we need,
IMO, to eliminate "didn't think about that" and "don't have a
clue" from the information related to these subjects that comes
back from site visits.

    john


From Michael.Tuexen@lurchi.franken.de  Tue Feb 26 11:12:14 2013
Return-Path: <Michael.Tuexen@lurchi.franken.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 BFF6521F8A6B for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.539
X-Spam-Level: 
X-Spam-Status: No, score=-2.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JOXozOC9mTty for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:12:14 -0800 (PST)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id CB5F121F8A66 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:12:13 -0800 (PST)
Received: from [192.168.1.101] (p5481BD18.dip.t-dialin.net [84.129.189.24]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id 9022A1C0C069A; Tue, 26 Feb 2013 20:12:11 +0100 (CET)
Subject: Re: Internet Draft Final Submission Cut-Off Today
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
Date: Tue, 26 Feb 2013 20:12:10 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
To: Dale R. Worley <worley@ariadne.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: Tue, 26 Feb 2013 19:12:14 -0000

On Feb 26, 2013, at 8:01 PM, Dale R. Worley wrote:

>> From: James Polk <jmpolk@cisco.com>
>> 
>>> It used to be 5 PM Pacific, now it's 24:00 UTC.
>> 
>> It's always been 2400 UTC, but with all the daylight savings time 
>> adjustments from country to country changing from year to year, I 
>> have talked to the Secretariat before (and recently), and verified 
>> this is indeed 8pm ET, at least for those in the US.
> 
> Well, 2400 UTC is 8pm Eastern Daylight (i.e., summer) Time (GMT-4),
> but 7pm Eastern Standard Time (GMT-5).  So I'd ask *when* did the
> Secretariat tell you that?
> 
> Personally, I'd trust "date -u" much sooner than any random person.
> Even better:
> 
>    $ date --date='00:00 Feb 26, 2013 UTC'
>    Mon Feb 25 19:00:00 EST 2013
>    $ 
Requires a Unix like system...
> 
> Dale
> 


From melinda.shore@gmail.com  Tue Feb 26 11:18:31 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C38C21F872E for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.414
X-Spam-Level: 
X-Spam-Status: No, score=-3.414 tagged_above=-999 required=5 tests=[AWL=0.185,  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 9eGGsNUAaGi7 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:18:31 -0800 (PST)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 18FF021F8727 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:18:31 -0800 (PST)
Received: by mail-da0-f44.google.com with SMTP id z20so2176392dae.3 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:18:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=i7dl6Qng2A55WMdjsgeZIx703fUhomOwPklaxazp9p8=; b=BRP1F550EG+EkthNYglgPc4yHxTrpnEyezD9d95Geqqj7Mrd5zaYTwXL7WKSGD4J7k eytpc+9zqvEjHu/X5jdQKYho0qKrT6o4iOxxqe2z2fU0uiDCJJx4LLRi2afaxIjv+8UA kSa2eK98huPaFH1xc1MMHGGlbZObo2K1SfP+WBwZEDwqKw3ftUtgfkFgRdr/osdq9OCO 5v8xf82P+uQSqCGwlSh2Nk86SWpSn3XlvBuYvbzTO3l8n/nUoGCTn9CW2FJjCsUGh4Ad C3vo3ngEz8yFNEGib/e2OY4VbRETc+5CeSdDP0kK7Df3Df1CKYBEZBngEYZcltnBe66H kOSA==
X-Received: by 10.68.0.170 with SMTP id 10mr25239020pbf.59.1361906310881; Tue, 26 Feb 2013 11:18:30 -0800 (PST)
Received: from spandex.local (216-67-46-104-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.104]) by mx.google.com with ESMTPS id rl3sm1798049pbb.28.2013.02.26.11.18.28 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 11:18:29 -0800 (PST)
Message-ID: <512D0A83.2020208@gmail.com>
Date: Tue, 26 Feb 2013 10:18:27 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>
In-Reply-To: <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>
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: Tue, 26 Feb 2013 19:18:31 -0000

On 2/26/13 10:12 AM, Michael Tuexen wrote:
> Requires a Unix like system...

I find these Linux-isms to be an abomination (remember when Unix
users used to know how to use Unix?  Seems like ages and ages ago).

I use timeanddate.com quite a bit, myself.  It's got some handy
calculators.

Melinda


From joelja@bogus.com  Tue Feb 26 11:23:58 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26AFD21F87FB for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.953
X-Spam-Level: 
X-Spam-Status: No, score=-101.953 tagged_above=-999 required=5 tests=[AWL=0.646, 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 jd65Yipja67C for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:23:57 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id AC7C621F86C5 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:23:57 -0800 (PST)
Received: from joels-MacBook-Air.local ([72.5.115.169]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1QJNqKd023220 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 26 Feb 2013 19:23:52 GMT (envelope-from joelja@bogus.com)
Message-ID: <512D0BC7.6080200@bogus.com>
Date: Tue, 26 Feb 2013 11:23:51 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>, "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>
In-Reply-To: <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>
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, 26 Feb 2013 19:23:52 +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, 26 Feb 2013 19:23:58 -0000

On 2/26/13 11:12 AM, Michael Tuexen wrote:
> On Feb 26, 2013, at 8:01 PM, Dale R. Worley wrote:
>
>>> From: James Polk <jmpolk@cisco.com>
>>>
>>> Personally, I'd trust "date -u" much sooner than any random person.
>>> Even better:
>>>
>>>     $ date --date='00:00 Feb 26, 2013 UTC'
>>>     Mon Feb 25 19:00:00 EST 2013
>>>     $
> Requires a Unix like system...
Finding the current time in UTC could reasonably  be left as an exercise 
for the reader...
>> Dale
>>


From mcr@sandelman.ca  Tue Feb 26 11:27:49 2013
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0D2321F8825 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJPI6EFbMq6X for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:27:49 -0800 (PST)
Received: from tuna.sandelman.ca (unknown [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) by ietfa.amsl.com (Postfix) with ESMTP id 33F6A21F87FB for <ietf@ietf.org>; Tue, 26 Feb 2013 11:27:49 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id AA80720168 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:34:56 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 5114C63A5C; Tue, 26 Feb 2013 14:26:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 42E5B63769 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:26:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Fwd: I-D Action: draft-barnes-healthy-food-06.txt
In-Reply-To: <CAHBDyN5g4eYWRrmkOPj_N9PusWZhPH6b+MgsjuwF9nNNBxzjrw@mail.gmail.com>
References: <20130225181820.10165.59200.idtracker@ietfa.amsl.com> <CAHBDyN5DZTABYKm+XsKPPP95skJP8D3GzkSFxuxUEaM5Gxf27A@mail.gmail.com> <6.2.5.6.2.20130225142157.0ae6baf8@resistor.net> <2671C6CDFBB59E47B64C10B3E0BD5923041E9A7D16@PRVPEXVS15.corp.twcable.com> <CAHBDyN5g4eYWRrmkOPj_N9PusWZhPH6b+MgsjuwF9nNNBxzjrw@mail.gmail.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 26 Feb 2013 14:26:38 -0500
Message-ID: <26017.1361906798@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 19:27:49 -0000

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


>>>>> "Mary" =3D=3D Mary Barnes <mary.ietf.barnes@gmail.com> writes:
    >>> In Section 5:
    >>>=20
    >>> "For cases of first time attendees for a specific location,
    >>> relevant information can be gathered from attendees that have
    >>> previously visited the city."

    >>> There are recurrent discussions as nobody volunteered to gather
    >>> that information in one place.

    >> [WEG] Perhaps a model similar to RFC 6640 would be appropriate -
    >> having this draft explicitly recommend use of a wiki or other
    >> semi-permanent method to store and share information
    >> collaboratively about specific locations' healthy/restricted diet
    >> options based on past experience. It could probably be a
    >> persistent subsection of the IETF meeting wiki, or it could just
    >> as easily be a pointer to a non-IETF-specific external website
    >> that is set up with precisely this goal (helping travelers with
    >> special dietary needs meet their requirements in strange cities)
    >> in mind.

    Mary> [MB] That's an excellent suggestion in terms of information
    Mary> sharing.  We have been doing that on the IETF food list, but
    Mary> for the cities that we re-visit on a regular basis, having
    Mary> this more widely available on a wiki would be helpful.
    Mary> Perhaps, we could add something to the tools page and do it by
    Mary> meeting location to include all the logistics (including the
    Mary> food) and have it more permanent. [/MB]

That's one of the best arguments as to why we should revisit cities
we have bene to before ...=20

(a recent Type-II diabetic. I booked a place in Orlando with a
kitchen...)

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20



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

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

iQCVAwUAUS0MboqHRg3pndX9AQKcagP9GE+ebcxxdvpL1i5OSdQmpOLvrXN2f1fZ
40SFT+JeUkuSd9IEaPRGlIhDz9ZsP2gZkVGk8CKQ+C1AkRrvfwH+WosZAZIS7xR5
UMkM7js7kgK2ZLWe6/J3SJ9JeibBdANkmv48/9TBbpR+XjYFjRsXbTyXWd1MYre9
gzNw3lGerno=
=mhtI
-----END PGP SIGNATURE-----
--=-=-=--

From touch@isi.edu  Tue Feb 26 11:40:51 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B21F821F87C5 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level: 
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[AWL=-0.571, 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 PRkAQvy2sGXv for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:40:50 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7A621F87BB for <ietf@ietf.org>; Tue, 26 Feb 2013 11:40:50 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r1QJdsYE028322 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Feb 2013 11:39:55 -0800 (PST)
Message-ID: <512D0F7E.8030402@isi.edu>
Date: Tue, 26 Feb 2013 11:39:42 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com>
In-Reply-To: <512D0BC7.6080200@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 19:40:51 -0000

On 2/26/2013 11:23 AM, joel jaeggli wrote:
> On 2/26/13 11:12 AM, Michael Tuexen wrote:
>> On Feb 26, 2013, at 8:01 PM, Dale R. Worley wrote:
>>
>>>> From: James Polk <jmpolk@cisco.com>
>>>>
>>>> Personally, I'd trust "date -u" much sooner than any random person.
>>>> Even better:
>>>>
>>>>     $ date --date='00:00 Feb 26, 2013 UTC'
>>>>     Mon Feb 25 19:00:00 EST 2013
>>>>     $
>> Requires a Unix like system...
> Finding the current time in UTC could reasonably  be left as an exercise
> for the reader...

It could be posted on the Internet Draft submission tool page, including 
a "countdown clock" too, if you really want useful  ;-)

Then again, having these deadlines at all is a bit silly.

It just forces authors to "informally distribute" updates directly on 
the list, and cuts off access to work that doesn't need to happen in 
sync with an IETF meeting.

Joe

From dave@cridland.net  Tue Feb 26 11:45:55 2013
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 262DC21F8830 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.037
X-Spam-Level: 
X-Spam-Status: No, score=-3.037 tagged_above=-999 required=5 tests=[AWL=-0.061, 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 6Xlk72WALWkj for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:45:54 -0800 (PST)
Received: from mail-oa0-f50.google.com (mail-oa0-f50.google.com [209.85.219.50]) by ietfa.amsl.com (Postfix) with ESMTP id 7A0AF21F8825 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:45:53 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id l20so5962056oag.23 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:45:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=iLt+252HSfeTGhpwHFblH8cyYGOvm/TNTwYlF3jigcM=; b=SoxpVId0o43UqbSKaPVgww0Y9fX/qqY98P+mFYFojRXaF1JjqulqUFRJpKj7CkiT3W gDbgkqDz+Ni/CDbgwfaNcZ+16yXRYrteoVN/dBB9ECgRSDx9mMoqk9QWESHVn6Ofq0hh IrA2hN0/6sLU8p4nHaIRLMrTM3qgx5aV5GUiM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=iLt+252HSfeTGhpwHFblH8cyYGOvm/TNTwYlF3jigcM=; b=PMbEMDwDF4fStRdTIVyfAYjSuibK9o/N+f+b7qQmbmFlTSn1Hgk8D/XCA1NtCyVP4h 3hBovsa8G1RIQVYo2bkJM160n3ws2UHYcGkNPjZ0eVPtLx45bEBNYOhmAjkaw6V08IKf MECGEZbD+yaa45hSbP1zglFRt49zEXZXUS8EEZ0jKeBLF8cQBkoxugX3ylXD4Sh1ETBv zZ58p3XFgbawWB4iEA6N3LS2XshMpfXWRpRbjM40d0KynE6MWmJa8X7y1Zb4RnAUNaT0 OXk9FwHsB3JlSXUO3MzciahxRNyIAOvIrK+aXjBP3mEoo3E1Hz/t2HJs1Pu2hNXhNmYW qlQQ==
MIME-Version: 1.0
X-Received: by 10.182.113.40 with SMTP id iv8mr12381402obb.12.1361907952927; Tue, 26 Feb 2013 11:45:52 -0800 (PST)
Received: by 10.60.10.72 with HTTP; Tue, 26 Feb 2013 11:45:52 -0800 (PST)
Received: by 10.60.10.72 with HTTP; Tue, 26 Feb 2013 11:45:52 -0800 (PST)
In-Reply-To: <512D0BC7.6080200@bogus.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com>
Date: Tue, 26 Feb 2013 19:45:52 +0000
Message-ID: <CAKHUCzxHd6QphevKZVNH9xjZr0CSFxbMjcev67MSk+FJLoORNQ@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Dave Cridland <dave@cridland.net>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=f46d04479f95c0600d04d6a5e76b
X-Gm-Message-State: ALoCoQmduwLMT8PQCDiTwFr0uQ4sDwmf8GamlwBGXbejGIOkSEqGPusqaxkiBlwW6wns8I7IL9LT
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 19:45:55 -0000

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

On Feb 26, 2013 2:24 PM, "joel jaeggli" <joelja@bogus.com> wrote:
> Finding the current time in UTC could reasonably  be left as an exercise
for the reader...

Simple. Go to the UK, ensure it's winter, and ask a policeman.

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

<p><br>
On Feb 26, 2013 2:24 PM, &quot;joel jaeggli&quot; &lt;<a href=3D"mailto:joe=
lja@bogus.com">joelja@bogus.com</a>&gt; wrote:<br>
&gt; Finding the current time in UTC could reasonably =A0be left as an exer=
cise for the reader...</p>
<p>Simple. Go to the UK, ensure it&#39;s winter, and ask a policeman.<br>
</p>

--f46d04479f95c0600d04d6a5e76b--

From petithug@acm.org  Tue Feb 26 11:47:17 2013
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1745221F89DA for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.567
X-Spam-Level: 
X-Spam-Status: No, score=-102.567 tagged_above=-999 required=5 tests=[AWL=0.033, 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 E1tJNKzBWom6 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:47:16 -0800 (PST)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 1D32B21F89E1 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:47:16 -0800 (PST)
Received: from [IPv6:2601:9:4b80:32:21c7:2154:4ebf:7150] (unknown [IPv6:2601:9:4b80:32:21c7:2154:4ebf:7150]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "Marc Petit-Huguenin", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id F2B13204B0; Tue, 26 Feb 2013 19:47:14 +0000 (UTC)
Message-ID: <512D1145.4060600@acm.org>
Date: Tue, 26 Feb 2013 11:47:17 -0800
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20130116 Icedove/10.0.12
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>
In-Reply-To: <512D0F7E.8030402@isi.edu>
X-Enigmail-Version: 1.4.1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 19:47:17 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 02/26/2013 11:39 AM, Joe Touch wrote:
> On 2/26/2013 11:23 AM, joel jaeggli wrote:
>> On 2/26/13 11:12 AM, Michael Tuexen wrote:
>>> On Feb 26, 2013, at 8:01 PM, Dale R. Worley wrote:
>>> 
>>>>> From: James Polk <jmpolk@cisco.com>
>>>>> 
>>>>> Personally, I'd trust "date -u" much sooner than any random
>>>>> person. Even better:
>>>>> 
>>>>> $ date --date='00:00 Feb 26, 2013 UTC' Mon Feb 25 19:00:00 EST
>>>>> 2013 $
>>> Requires a Unix like system...
>> Finding the current time in UTC could reasonably  be left as an exercise 
>> for the reader...
> 
> It could be posted on the Internet Draft submission tool page, including a 
> "countdown clock" too, if you really want useful  ;-)
> 
> Then again, having these deadlines at all is a bit silly.
> 
> It just forces authors to "informally distribute" updates directly on the
> list, and cuts off access to work that doesn't need to happen in sync with
> an IETF meeting.

Something like "documents published less than two weeks before a WG session
cannot be discussed in this session" would be better.  Also, "slides published
less than one week before a WG session cannot be used in this session".

- -- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRLRFDAAoJECnERZXWan7EKBMQALd82QtUSxacpAczLjgCU/tO
HpJgxvMtTyhAZaa25DO+yB/AQn/wYWTqYWJQNxUmvlZ8u5elux78dLrhJPr5IzGB
dG9B7xM9w0OP9CKLDVJOGQxLBOXAblANS809lHF8HmzdXdj1UvgrqOST/g1LNVRr
FaEe8yf97F2fOSGN7erX7vmZ+Adf647Au0MhxfwRkEF+me8WEeXIMsYe9+faP/Io
6f+rc0SSBSGZl7/mHE2mfdSwHEwNN/GYR8AHOjq2+GtKmHSogXg0m7UxHjkVZ4Sr
bBqtfjYEtMJZx/BZJ9IdoD8n8XRJpnxRz2bPDVw3n5IZxXgF09zATpyp4Q9B1Ie8
T7rjr2k8aYqaiWqnFAwbCMxa+mYWojKJgVUi5tRWsYDtmqxkCWy1iJ6HFHFI8D6v
i0Y3HCZL8IHTft3Xkz3D00qxya1/WC/COC/TKoEsZCMk6XAlfua5DcFzPgjcZZIW
cAKaWDWz+t4PPxTBPTFgfBIqeMiV+Blor7N3Z9AGzhM+f2zrpih1Tp+gQpcfmXdE
b4SjdfAQbNgu0ktDTRWIU1UOUM1UVT1goHnjiw14Shi/9bbuU9yWHOd8CzP1d2LN
6cCi91i1bK2kK17FpL9G7fbeQ/qqJSu/s+6a2gRCVIS8ZnNMXcJAN0hiRpCrLbT2
wToOJQf8npzwUjkJUfeL
=QFzZ
-----END PGP SIGNATURE-----

From touch@isi.edu  Tue Feb 26 11:58:34 2013
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6078021F8746 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:58:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.136
X-Spam-Level: 
X-Spam-Status: No, score=-103.136 tagged_above=-999 required=5 tests=[AWL=-0.537, 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 IpvtfgPzQn4M for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 11:58:33 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id CD54921F86D8 for <ietf@ietf.org>; Tue, 26 Feb 2013 11:58:33 -0800 (PST)
Received: from [128.9.160.166] (abc.isi.edu [128.9.160.166]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id r1QJvUPO001997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 26 Feb 2013 11:57:30 -0800 (PST)
Message-ID: <512D139D.8090305@isi.edu>
Date: Tue, 26 Feb 2013 11:57:17 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Marc Petit-Huguenin <petithug@acm.org>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org>
In-Reply-To: <512D1145.4060600@acm.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 19:58:34 -0000

On 2/26/2013 11:47 AM, Marc Petit-Huguenin wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 02/26/2013 11:39 AM, Joe Touch wrote:
>> On 2/26/2013 11:23 AM, joel jaeggli wrote:
>>> On 2/26/13 11:12 AM, Michael Tuexen wrote:
>>>> On Feb 26, 2013, at 8:01 PM, Dale R. Worley wrote:
>>>>
>>>>>> From: James Polk <jmpolk@cisco.com>
>>>>>>
>>>>>> Personally, I'd trust "date -u" much sooner than any random
>>>>>> person. Even better:
>>>>>>
>>>>>> $ date --date='00:00 Feb 26, 2013 UTC' Mon Feb 25 19:00:00 EST
>>>>>> 2013 $
>>>> Requires a Unix like system...
>>> Finding the current time in UTC could reasonably  be left as an exercise
>>> for the reader...
>>
>> It could be posted on the Internet Draft submission tool page, including a
>> "countdown clock" too, if you really want useful  ;-)
>>
>> Then again, having these deadlines at all is a bit silly.
>>
>> It just forces authors to "informally distribute" updates directly on the
>> list, and cuts off access to work that doesn't need to happen in sync with
>> an IETF meeting.
>
> Something like "documents published less than two weeks before a WG session
> cannot be discussed in this session" would be better.  Also, "slides published
> less than one week before a WG session cannot be used in this session".

That's fine, though it still puts minor mods in the same class as 
complete revisions.

Maybe we need a two-tiered numbering system, e.g., major revs cannot 
occur less than two weeks before a meeting where they will be discussed, 
but minor mods are OK up to 48 hours in advance.

:-)

Joe

From mrex@sap.com  Tue Feb 26 12:28:44 2013
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73D2921F874A for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:28:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.235
X-Spam-Level: 
X-Spam-Status: No, score=-10.235 tagged_above=-999 required=5 tests=[AWL=0.014, 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 xtDzrGyDx-Wq for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:28:43 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 95BB321F8735 for <ietf@ietf.org>; Tue, 26 Feb 2013 12:28:43 -0800 (PST)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id r1QKSNw4019516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 26 Feb 2013 21:28:24 +0100 (MET)
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <512D0BC7.6080200@bogus.com>
To: joel jaeggli <joelja@bogus.com>
Date: Tue, 26 Feb 2013 21:28:23 +0100 (CET)
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: <20130226202823.DD1441A5D0@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: Tue, 26 Feb 2013 20:28:44 -0000

joel jaeggli wrote:
> Michael Tuexen wrote:
> > Dale R. Worley wrote:
> >
> >>> From: James Polk <jmpolk@cisco.com>
> >>>
> >>> Personally, I'd trust "date -u" much sooner than any random person.
> >>> Even better:
> >>>
> >>>     $ date --date='00:00 Feb 26, 2013 UTC'
> >>>     Mon Feb 25 19:00:00 EST 2013
> >>>     $
> > Requires a Unix like system...
> Finding the current time in UTC could reasonably  be left as an exercise 
> for the reader...

I have a recurring remote participation problem with the
IETF Meeting Agendas, because it specifies the time of WG meeting slots
in local time (local to the IETF Meeting), but does not give the
local time zone *anywhere*.

I would appreciate if the local time zone indication would be added
like somewhere at the top of the page, to each IETF meeting agenda.

-Martin

From jmpolk@cisco.com  Tue Feb 26 12:32:24 2013
Return-Path: <jmpolk@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B124821F874A for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:32:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.428
X-Spam-Level: 
X-Spam-Status: No, score=-110.428 tagged_above=-999 required=5 tests=[AWL=0.171, 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 2wuJPjjgtlFb for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:32:18 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 81AD821F8745 for <ietf@ietf.org>; Tue, 26 Feb 2013 12:32:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=865; q=dns/txt; s=iport; t=1361910734; x=1363120334; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=M7V4YXyt0nNsZp/4cM+b1sleOpWXZLtHn91hqXpoL8c=; b=cV0D9wSaYnrbsjgYtQVvh1gQvnbqVSn17GQnl6tx9l+DUVp/pp4YAx1x Jqea6dQXOp4IXlg9m2Ixz1099Tj6sIai64FCFEoOm/bhiG50fZbd/liVV 9O8fhVtNytX/P8I1ZzWDbd8D4IxOWuFTeFTMJGf1y6tIxkoWvK+E0BzPe U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApYFAK0aLVGtJV2b/2dsb2JhbABFhgi7bX8Wc4IfAQEBBDgCTwcEFQMJFRAPCj4GARKIE69QPZAQjxuDQAOIap4+gyc
X-IronPort-AV: E=Sophos;i="4.84,742,1355097600"; d="scan'208";a="181462808"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-8.cisco.com with ESMTP; 26 Feb 2013 20:32:14 +0000
Received: from jmpolk-WS.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) (authenticated bits=0) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id r1QKWDGb018703 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 26 Feb 2013 20:32:14 GMT
Message-Id: <201302262032.r1QKWDGb018703@rcdn-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Feb 2013 14:32:13 -0600
To: "Dale R. Worley" <worley@ariadne.com>, <ietf@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 20:32:24 -0000

At 01:01 PM 2/26/2013, Dale R. Worley wrote:
> > From: James Polk <jmpolk@cisco.com>
> >
> > >It used to be 5 PM Pacific, now it's 24:00 UTC.
> >
> > It's always been 2400 UTC, but with all the daylight savings time
> > adjustments from country to country changing from year to year, I
> > have talked to the Secretariat before (and recently), and verified
> > this is indeed 8pm ET, at least for those in the US.
>
>Well, 2400 UTC is 8pm Eastern Daylight (i.e., summer) Time (GMT-4),
>but 7pm Eastern Standard Time (GMT-5).  So I'd ask *when* did the
>Secretariat tell you that?

well, I can't remember if it was for Paris or Vancouver now that you ask...


>Personally, I'd trust "date -u" much sooner than any random person.
>Even better:
>
>     $ date --date='00:00 Feb 26, 2013 UTC'
>     Mon Feb 25 19:00:00 EST 2013
>     $
>
>Dale


From warren@kumari.net  Tue Feb 26 12:32:53 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A1B621F8871 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.563
X-Spam-Level: 
X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 h9NDULHVOlNV for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 12:32:52 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42F7621F889C for <ietf@ietf.org>; Tue, 26 Feb 2013 12:32:52 -0800 (PST)
Received: from [192.168.1.145] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id AA7381B41871; Tue, 26 Feb 2013 15:32:44 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Re: Internet Draft Final Submission Cut-Off Today
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAKHUCzxHd6QphevKZVNH9xjZr0CSFxbMjcev67MSk+FJLoORNQ@mail.gmail.com>
Date: Tue, 26 Feb 2013 15:32:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A3F0B23-53F4-4B85-94EC-4E4A526D4D52@kumari.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <CAKHUCzxHd6QphevKZVNH9xjZr0CSFxbMjcev67MSk+FJLoORNQ@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
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: Tue, 26 Feb 2013 20:32:53 -0000

On Feb 26, 2013, at 2:45 PM, Dave Cridland <dave@cridland.net> wrote:

>=20
> On Feb 26, 2013 2:24 PM, "joel jaeggli" <joelja@bogus.com> wrote:
> > Finding the current time in UTC could reasonably  be left as an =
exercise for the reader...
>=20
> Simple. Go to the UK, ensure it's winter, and ask a policeman.

Er, I see a  bootstrapping problem here -- don't I need to *roughly* =
know the time to know if it is winter?

Am I allowed to ask the policeman if it is winter? If a have  a foreign =
accent is he less likely to think I'm drunk / playing the fool?


W


--=20
Militant Agnostic -- I don't know and you don't either...




From cyrus@daboo.name  Tue Feb 26 13:18:48 2013
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 120AC21F85E0 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 13:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.521
X-Spam-Level: 
X-Spam-Status: No, score=-102.521 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 lubVRZYcJy8L for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 13:18:47 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 0509321F85D8 for <ietf@ietf.org>; Tue, 26 Feb 2013 13:18:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7A1543E1D819; Tue, 26 Feb 2013 16:18:46 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBNIqxp-iZ_3; Tue, 26 Feb 2013 16:18:45 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 4457E3E1D80E; Tue, 26 Feb 2013 16:18:44 -0500 (EST)
Date: Tue, 26 Feb 2013 16:18:41 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: mrex@sap.com, joel jaeggli <joelja@bogus.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
Message-ID: <34B824FD6401DAA3320288E7@caldav.corp.apple.com>
In-Reply-To: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1186
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 21:18:48 -0000

Hi Martin,

--On February 26, 2013 at 9:28:23 PM +0100 Martin Rex <mrex@sap.com> wrote:

>> Finding the current time in UTC could reasonably  be left as an exercise
>> for the reader...
>
> I have a recurring remote participation problem with the
> IETF Meeting Agendas, because it specifies the time of WG meeting slots
> in local time (local to the IETF Meeting), but does not give the
> local time zone *anywhere*.
>
> I would appreciate if the local time zone indication would be added
> like somewhere at the top of the page, to each IETF meeting agenda.

The good news is the iCalendar data available for the agenda does have the 
correct timezone specified, so if you import the iCalendar data into your 
calendar client (of course assuming you use one) then you will be able to 
view the sessions correctly adjusted to whatever local time you have your 
client set for.

That said, it would still be nice to include the timezone information on 
the agenda page.

It is worth noting that daylight saving time starts on the Sunday morning 
of the IETF meeting, so all the agenda times are in fact UTC -4 hours for 
Sunday and later days, but UTC -5 for Saturday.

-- 
Cyrus Daboo


From paulej@packetizer.com  Tue Feb 26 14:25:42 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7486221F8838 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[AWL=0.198,  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 OpymO9f3OuPV for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:25:41 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id D7D9521F87D3 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:25:37 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r1QMPM8f020564 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 26 Feb 2013 17:25:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1361917523; bh=QX/m6/yeqhD3dQa39wbwbzNptYEDxNF7neNE0RgYgfQ=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=cHxp5tncRf6HfHqA6PWM2k4wXNbt4KdiiY+C47m7Wzx/QX8MP15xYdAX/sxEGPg8P MesIGS7+ogICYbW9fxp7dHUAT8zU6Ib6y2kJiKAau3yIh/HvoIwXzXqdukC5S+BYhY F+TPsDbOHgqMnNEDTIbJwqu2KoN1XIzri2d5rbT0=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Dale R. Worley'" <worley@ariadne.com>, "'James Polk'" <jmpolk@cisco.com>, <ietf@ietf.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
In-Reply-To: <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>
Subject: RE: Internet Draft Final Submission Cut-Off Today
Date: Tue, 26 Feb 2013 17:25:28 -0500
Message-ID: <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEbUqlLCH+67NxJwQLMVL08Sr0SFQHi0Wh2Ao3a48sB5hZCjwHccQ08mbCg/wA=
Content-Language: en-us
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 22:25:42 -0000

Dale,

> Personally, I'd trust "date -u" much sooner than any random person.
> Even better:
> 
>     $ date --date='00:00 Feb 26, 2013 UTC'
>     Mon Feb 25 19:00:00 EST 2013
>     $

Funny thing is when I try the date from the announcement:

> All Final Version (-01 and up) submissions are due by UTC 24:00 Monday,
February 25.

I get this:

$ date --date='24:00 Feb 25, 2013 UTC'
date: invalid date `24:00 Feb 25, 2013 UTC'

Seriously, what the heck is 24:00?  Is that like the meeting we'll have in
the afternoon at about 13:90?

Paul



From melinda.shore@gmail.com  Tue Feb 26 14:31:15 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F11BF21F85B8 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.42
X-Spam-Level: 
X-Spam-Status: No, score=-3.42 tagged_above=-999 required=5 tests=[AWL=0.179,  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 NW6M-i2nAfB1 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:31:15 -0800 (PST)
Received: from mail-pb0-f51.google.com (mail-pb0-f51.google.com [209.85.160.51]) by ietfa.amsl.com (Postfix) with ESMTP id 43D6821F85C4 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:31:15 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so2632736pbc.24 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:31:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ROm9T+lqAxnWQrom4hREMPaCRpXEJ5cbqhnLyGoi0tQ=; b=ImIwYdE6/lN5MKy6FVo3XCCkl3ZF345tOYc0S6MfganeKpJj/woLStMj/8EFpeGQI+ jIzbERAcCItNwGvuP1mjb4fU86cL54/qnELzSxbZwxI504d4V7JPMHxYyUvZ0HS5KUg7 CxqAukFnRF20XUP4sMWThX7vxPG8n2GOuRRTfpJWBxyz5PRdHypXxHtPibwgfRdg9mJ3 f6WIqMwlmuhvqCZgu25hWlgbLYJq78yIisv6aMcrU4/DLTpXsB9CNtp04v0gB1Fn55oo swAO7sfHWSLQbO7yWgCQY7FM5MI0Q8/hm2/jE9BwbJOYlBb18nqHyo3e0ZDa3FzQ3chn YDhg==
X-Received: by 10.66.160.34 with SMTP id xh2mr4033142pab.98.1361917875098; Tue, 26 Feb 2013 14:31:15 -0800 (PST)
Received: from spandex.local (216-67-46-104-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.104]) by mx.google.com with ESMTPS id kl4sm2216362pbc.31.2013.02.26.14.31.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 14:31:14 -0800 (PST)
Message-ID: <512D37B0.7010108@gmail.com>
Date: Tue, 26 Feb 2013 13:31:12 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>
In-Reply-To: <037501ce1470$2ed50c50$8c7f24f0$@packetizer.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: Tue, 26 Feb 2013 22:31:16 -0000

On 2/26/13 1:25 PM, Paul E. Jones wrote:
> Seriously, what the heck is 24:00?  

That one is weird, no doubt about it, but ultimately
it's 23:59 + 1 minute, which is clear.  But I really
think "24:00" is confusing. 0:00 is clearer.  I'm
wondering if they're trying to work around some ferkakte
piece of software.

Melinda


From joelja@bogus.com  Tue Feb 26 14:34:00 2013
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B2C21F8746 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.276
X-Spam-Level: 
X-Spam-Status: No, score=-102.276 tagged_above=-999 required=5 tests=[AWL=0.323, 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 OqJzSHTtT4Bx for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:34:00 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 20FFE21F86D5 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:33:59 -0800 (PST)
Received: from joels-MacBook-Air.local ([72.5.115.169]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id r1QMXn7R025508 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 26 Feb 2013 22:33:49 GMT (envelope-from joelja@bogus.com)
Message-ID: <512D384C.2020109@bogus.com>
Date: Tue, 26 Feb 2013 14:33:48 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:19.0) Gecko/20130117 Thunderbird/19.0
MIME-Version: 1.0
To: "Paul E. Jones" <paulej@packetizer.com>, "'Dale R. Worley'" <worley@ariadne.com>, "'James Polk'" <jmpolk@cisco.com>, ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>
In-Reply-To: <037501ce1470$2ed50c50$8c7f24f0$@packetizer.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, 26 Feb 2013 22:33:49 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 22:34:01 -0000

On 2/26/13 2:25 PM, Paul E. Jones wrote:
> Dale,
>
>> Personally, I'd trust "date -u" much sooner than any random person.
>> Even better:
>>
>>      $ date --date='00:00 Feb 26, 2013 UTC'
>>      Mon Feb 25 19:00:00 EST 2013
>>      $
> Funny thing is when I try the date from the announcement:
>
>> All Final Version (-01 and up) submissions are due by UTC 24:00 Monday,
> February 25.
>
> I get this:
>
> $ date --date='24:00 Feb 25, 2013 UTC'
> date: invalid date `24:00 Feb 25, 2013 UTC'
>
> Seriously, what the heck is 24:00?  Is that like the meeting we'll have in
> the afternoon at about 13:90?
The minute which occurs after 23:59 is 00:00 of the following day if you 
have a leap second, you get 23:59:60 which is fun...
> Paul
>
>


From mrw@lilacglade.org  Tue Feb 26 14:34:52 2013
Return-Path: <mrw@lilacglade.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCC9221F86D5 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.901
X-Spam-Level: 
X-Spam-Status: No, score=-101.901 tagged_above=-999 required=5 tests=[AWL=0.698, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w8EFQArdxZSS for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:34:52 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBBD21F8578 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:34:52 -0800 (PST)
Received: from [10.1.10.107] (unknown [10.1.10.107]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.painless-security.com (Postfix) with ESMTPSA id B8C30201D1; Tue, 26 Feb 2013 17:29:58 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <512D37B0.7010108@gmail.com>
Date: Tue, 26 Feb 2013 17:34:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD815EE4-18AC-4706-B237-BF91FB411B2B@lilacglade.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com>
To: Melinda Shore <melinda.shore@gmail.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: Tue, 26 Feb 2013 22:34:53 -0000

I think the problem is that if they said 0:00, it would be on Tuesday, =
February 26th, not Monday, February 25th, and people would submit a day =
late...

Margaret

On Feb 26, 2013, at 5:31 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:

> On 2/26/13 1:25 PM, Paul E. Jones wrote:
>> Seriously, what the heck is 24:00? =20
>=20
> That one is weird, no doubt about it, but ultimately
> it's 23:59 + 1 minute, which is clear.  But I really
> think "24:00" is confusing. 0:00 is clearer.  I'm
> wondering if they're trying to work around some ferkakte
> piece of software.
>=20
> Melinda
>=20


From presnick@qti.qualcomm.com  Tue Feb 26 14:38:46 2013
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85C8221F878F for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:38:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.566
X-Spam-Level: 
X-Spam-Status: No, score=-102.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hRFAnKtWbMMd for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:38:45 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id B973D21F8739 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:38:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1361918325; x=1393454325; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=+NKkp90BTNeEvtKQzNRg/INnxpvZvV0GtD4JeK90zAE=; b=hP7ZZqR3luPV8QOBZOhbczsgTicyVP87RJaENZQ/t2BtRNzHlB35m6o2 ACMuMphgwl04tiZPM3GjrzoJyCi3fvtMGsVIbgQwR8YKAAq2Z20gYAiZA p4ktWco1tLKq/v9ae/tvkyC5sy6i0v9uQ3SpMRLXfuvAEES6SAqLeS6pN Y=;
X-IronPort-AV: E=Sophos;i="4.84,743,1355126400"; d="scan'208";a="26291698"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 26 Feb 2013 14:38:33 -0800
X-IronPort-AV: E=Sophos;i="4.84,743,1355126400"; d="scan'208";a="406621877"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 26 Feb 2013 14:38:33 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.2.318.4; Tue, 26 Feb 2013 14:38:33 -0800
Message-ID: <512D3968.50104@qti.qualcomm.com>
Date: Tue, 26 Feb 2013 16:38:32 -0600
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: Joe Touch <touch@isi.edu>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>	<512D1145.4060600@acm.org> <512D139D.8090305@isi.edu>
In-Reply-To: <512D139D.8090305@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 22:38:46 -0000

On 2/26/13 1:57 PM, Joe Touch wrote:
> On 2/26/2013 11:47 AM, Marc Petit-Huguenin wrote:
>> On 02/26/2013 11:39 AM, Joe Touch wrote:
>>> Then again, having these deadlines at all is a bit silly.
>>>
>>> It just forces authors to "informally distribute" updates directly 
>>> on the
>>> list, and cuts off access to work that doesn't need to happen in 
>>> sync with
>>> an IETF meeting.
>>
>> Something like "documents published less than two weeks before a WG 
>> session
>> cannot be discussed in this session" would be better.  Also, "slides 
>> published
>> less than one week before a WG session cannot be used in this session".
>
> That's fine, though it still puts minor mods in the same class as 
> complete revisions.
>
> Maybe we need a two-tiered numbering system, e.g., major revs cannot 
> occur less than two weeks before a meeting where they will be 
> discussed, but minor mods are OK up to 48 hours in advance.
>
> :-)

You can't bury a recurring-rathole thread like this in the middle of 
another thread and expect good fireworks! ;-)

But more seriously: I agree with you both. The deadline is silly. Chairs 
should be able to manage what gets discussed at a face-to-face without 
an artificial posting moratorium, and it can be done with reasonable 
discretion for exceptions. But we have had this conversation many times, 
including at the face-to-face plenary, and we've repeatedly heard that 
chairs prefer to have this default "no" in place to reduce the number of 
arguments they have to have with recalcitrant WG members. And there is 
an AD-override of the moratorium, so if you do have good reason to post 
an update, it is allowed.

I suggested at one point that a middle ground might be to keep allow 
submission to a "holding pen" that would require chair or AD to release 
it. It didn't garner a lot of excitement.

pr

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


From paulej@packetizer.com  Tue Feb 26 14:45:38 2013
Return-Path: <paulej@packetizer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93A4121F869F for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.405
X-Spam-Level: 
X-Spam-Status: No, score=-2.405 tagged_above=-999 required=5 tests=[AWL=0.194,  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 qID3c9TSHSwe for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:45:37 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 86E6521F8632 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:45:37 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r1QMjX6h021740 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 26 Feb 2013 17:45:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1361918733; bh=lDThSKzPEgx/p4cL7j6+LLmBK+zQ69FsntXLb0B7o/w=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=HsW7OSVzPjToDRV9Wxc4hpCfx06fuVV5exIXuajbBZBtHJiDdPHOaJACtBGTyqPnF hT+CYR81Zz5UNQZWUoGRqNYaH7aXqz8DeT31N1RJX/NEZSbqEwHlYjln2v76KwVZjG HkEOxJXCcSmKmwYZMBJC6TjZ52qjdo3WO7P+SJ5E=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Joe Touch'" <touch@isi.edu>, "'joel jaeggli'" <joelja@bogus.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>
In-Reply-To: <512D0F7E.8030402@isi.edu>
Subject: RE: Internet Draft Final Submission Cut-Off Today
Date: Tue, 26 Feb 2013 17:45:38 -0500
Message-ID: <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQEbUqlLCH+67NxJwQLMVL08Sr0SFQHi0Wh2Ao3a48sB5hZCjwHccQ08AXAR31kClKOm0QGDE/xPmYRkJzA=
Content-Language: en-us
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Feb 2013 22:45:38 -0000

Joes,

> Then again, having these deadlines at all is a bit silly.
> 
> It just forces authors to "informally distribute" updates directly on
> the list, and cuts off access to work that doesn't need to happen in
> sync with an IETF meeting.

I agree with your point to a large extent, but I'm sure there are reasons.

On the one hand, having a cut-off time could help WG chairs make a decision
as to whether to entertain a discussion on a draft.  On the other hand,
having no cut-off date might mean that drafts are submitted extremely late
and it makes it more challenging or impossible to prepare an agenda.

Perhaps having a "soft" cut-off is more reasonable.  If the document is
"late", then it would be up to the WG chair to decide whether to entertain
it.  If there are no documents by the deadline, the chair could decide to
cancel the meeting.

What one would not want, though, are hundreds of drafts submitted the night
before the IETF meeting starts with some expectation of discussion time.

Paul



From mrw@lilacglade.org  Tue Feb 26 14:49:13 2013
Return-Path: <mrw@lilacglade.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3271321F870E for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:49:13 -0800 (PST)
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 McQaWWdyhngM for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:49:12 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id B2B8821F86CD for <ietf@ietf.org>; Tue, 26 Feb 2013 14:49:12 -0800 (PST)
Received: from [10.1.10.107] (unknown [10.1.10.107]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.painless-security.com (Postfix) with ESMTPSA id 0B513201D1; Tue, 26 Feb 2013 17:44:19 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <512D3968.50104@qti.qualcomm.com>
Date: Tue, 26 Feb 2013 17:49:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>	<512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.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: Tue, 26 Feb 2013 22:49:13 -0000

On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> But more seriously: I agree with you both. The deadline is silly.=20

+1

The deadline originated because the secretariat needed time to post all =
of those drafts (by hand) before the meeting.  The notion of an =
automated tool that blocks submissions for two weeks before the meeting =
is just silly.

Margaret



From melinda.shore@gmail.com  Tue Feb 26 14:50:55 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 306D821F887D for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.425
X-Spam-Level: 
X-Spam-Status: No, score=-3.425 tagged_above=-999 required=5 tests=[AWL=0.174,  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 OpFmS57ipzRm for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:50:54 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7049121F8858 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:50:54 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id wz12so2657577pbc.17 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:50:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=4PWiuCVkiOa70PbWW5DWUTX5tCKh8dOVmZteTuqngIc=; b=M+xpt+JE+Swhi8myzY7sscwblNmpJ6kc/8HnfsH7uHvZj/QXsxW01ILqk40H9CHUpR aX0os6DECxtDk2aakNIFo1KNtksyKoEY3tSk8pOAfa1X1tQG31v5TekqXjB6dmPv51kN OL8gFLHYLjDsnugNG8RuB1rfUwAvDzh918EyNwVtRstQ6bSlW39x4hwYsu2llf6S2JXb BGUUETCaBc8XCXbv/KHBo9WA0SjLdfI78+xmuFVi/eRfqQqFINxKadr7zoe6kyabslvw R/oeXvlA14goz109Qe8bRlvHgJqmeoUzxD8qyB87zpGjtfVp9xBxfARGQOjrtNWp4nFP B/UA==
X-Received: by 10.68.191.9 with SMTP id gu9mr91496pbc.23.1361919054219; Tue, 26 Feb 2013 14:50:54 -0800 (PST)
Received: from spandex.local (216-67-46-104-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.104]) by mx.google.com with ESMTPS id x2sm2879427paw.8.2013.02.26.14.50.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Feb 2013 14:50:53 -0800 (PST)
Message-ID: <512D3C4B.3040007@gmail.com>
Date: Tue, 26 Feb 2013 13:50:51 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com>
In-Reply-To: <037c01ce1472$ffe26f20$ffa74d60$@packetizer.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: Tue, 26 Feb 2013 22:50:55 -0000

On 2/26/13 1:45 PM, Paul E. Jones wrote:
> On the one hand, having a cut-off time could help WG chairs make a decision
> as to whether to entertain a discussion on a draft.  On the other hand,
> having no cut-off date might mean that drafts are submitted extremely late
> and it makes it more challenging or impossible to prepare an agenda.

Well, for one thing the IETF does its work on mailing lists, and
meetings support that rather than the other way 'round.  For another,
I'm not sure this deadline makes any difference in practice (other
than introducing an inconvenience).  We're going to be giving meeting
time to a draft for which there's no revision, because it needs
meeting time.  It's on the agenda whether there's a revision or
not.  I understand the deadline was introduced to provide incentives
for people to get their stuff in in advance of a meeting.  But.

Melinda


From grmocg@gmail.com  Tue Feb 26 14:54:31 2013
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 D4F1D21F877B for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:54:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.045
X-Spam-Level: 
X-Spam-Status: No, score=-7.045 tagged_above=-999 required=5 tests=[AWL=-3.447, 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 AaXdxWaOAIln for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:54:29 -0800 (PST)
Received: from mail-oa0-f41.google.com (mail-oa0-f41.google.com [209.85.219.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0380021F8726 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:54:24 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id i10so6536827oag.14 for <ietf@ietf.org>; Tue, 26 Feb 2013 14:54:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=lxnvQAwjyETMOVVdnouXQG1HvZH0k29joyYCCrJFS/s=; b=v9BKyYBAvd9L30yMWg1bq5zqe3N9OBy7sjPtjfXVHCtNKSiPngANzxSLDr/98hcjtz XubVBXgb06Wen7Kg1vliJEjmkHqadwAX6PmbIGkE7Fgngpmqv71GokJ5t7jlsRlcWqNu LU3VblJ7QnFPjkh1gHIqM7YNPeeIsLaPlRaKk8sVbIDa4G+844XI0KBNtgb5phzA17f1 fHuPlx/uPS0+RXsfKZ64UFzaNj+AlgshfTTfNAV1f5ySDTZi2uc3pria2woj8gX07pCB Ka4Dg/1r7XyOipBaNSqvWdnsIkZUOh1/hRq+hCm30TqPKoJX0B4wI9sI86LEkUng3BfV bG7w==
MIME-Version: 1.0
X-Received: by 10.182.115.34 with SMTP id jl2mr91691obb.9.1361919264607; Tue, 26 Feb 2013 14:54:24 -0800 (PST)
Received: by 10.76.109.72 with HTTP; Tue, 26 Feb 2013 14:54:24 -0800 (PST)
In-Reply-To: <512D3C4B.3040007@gmail.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com>
Date: Tue, 26 Feb 2013 14:54:24 -0800
Message-ID: <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Roberto Peon <grmocg@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04448141fad70804d6a8890c
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, 26 Feb 2013 22:54:31 -0000

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

I'm not sure that the deadline serves any positive purpose so long as we
keep all of the versions anyway.
It certainly is annoying the way it is now and is disruptive to the
development process rather than helpful for it.

-=R


On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 2/26/13 1:45 PM, Paul E. Jones wrote:
> > On the one hand, having a cut-off time could help WG chairs make a
> decision
> > as to whether to entertain a discussion on a draft.  On the other hand,
> > having no cut-off date might mean that drafts are submitted extremely
> late
> > and it makes it more challenging or impossible to prepare an agenda.
>
> Well, for one thing the IETF does its work on mailing lists, and
> meetings support that rather than the other way 'round.  For another,
> I'm not sure this deadline makes any difference in practice (other
> than introducing an inconvenience).  We're going to be giving meeting
> time to a draft for which there's no revision, because it needs
> meeting time.  It's on the agenda whether there's a revision or
> not.  I understand the deadline was introduced to provide incentives
> for people to get their stuff in in advance of a meeting.  But.
>
> Melinda
>
>

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

<div dir=3D"ltr">I&#39;m not sure that the deadline serves any positive pur=
pose so long as we keep all of the versions anyway.=A0<div style>It certain=
ly is annoying the way it is now and is disruptive to the development proce=
ss rather than helpful for it.</div>
<div style><br></div><div style>-=3DR</div></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Tue, Feb 26, 2013 at 2:50 PM, Melind=
a Shore <span dir=3D"ltr">&lt;<a href=3D"mailto:melinda.shore@gmail.com" ta=
rget=3D"_blank">melinda.shore@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 2/26/13 1:45 PM, Paul E=
. Jones wrote:<br>
&gt; On the one hand, having a cut-off time could help WG chairs make a dec=
ision<br>
&gt; as to whether to entertain a discussion on a draft. =A0On the other ha=
nd,<br>
&gt; having no cut-off date might mean that drafts are submitted extremely =
late<br>
&gt; and it makes it more challenging or impossible to prepare an agenda.<b=
r>
<br>
</div>Well, for one thing the IETF does its work on mailing lists, and<br>
meetings support that rather than the other way &#39;round. =A0For another,=
<br>
I&#39;m not sure this deadline makes any difference in practice (other<br>
than introducing an inconvenience). =A0We&#39;re going to be giving meeting=
<br>
time to a draft for which there&#39;s no revision, because it needs<br>
meeting time. =A0It&#39;s on the agenda whether there&#39;s a revision or<b=
r>
not. =A0I understand the deadline was introduced to provide incentives<br>
for people to get their stuff in in advance of a meeting. =A0But.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
</font></span></blockquote></div><br></div>

--f46d04448141fad70804d6a8890c--

From warren@kumari.net  Tue Feb 26 14:59:21 2013
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B4921F8830 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.564
X-Spam-Level: 
X-Spam-Status: No, score=-102.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M7WhIq5seSX8 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 14:59:16 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0651E21F882A for <ietf@ietf.org>; Tue, 26 Feb 2013 14:59:15 -0800 (PST)
Received: from [192.168.1.145] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 002331B4030C; Tue, 26 Feb 2013 17:59:13 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Re: Internet Draft Final Submission Cut-Off Today
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com>
Date: Tue, 26 Feb 2013 17:59:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com> <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
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: Tue, 26 Feb 2013 22:59:21 -0000

On Feb 26, 2013, at 5:54 PM, Roberto Peon <grmocg@gmail.com> wrote:

> I'm not sure that the deadline serves any positive purpose so long as =
we keep all of the versions anyway.=20
> It certainly is annoying the way it is now and is disruptive to the =
development process rather than helpful for it.

Um, maybe.

Another way to look at it is that a deadline, any deadline, helps stop =
folk procrastinating and actually *submit*.

Have a look at the number of submissions just before the cutoffs=85

W

>=20
> -=3DR
>=20
>=20
> On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore =
<melinda.shore@gmail.com> wrote:
> On 2/26/13 1:45 PM, Paul E. Jones wrote:
> > On the one hand, having a cut-off time could help WG chairs make a =
decision
> > as to whether to entertain a discussion on a draft.  On the other =
hand,
> > having no cut-off date might mean that drafts are submitted =
extremely late
> > and it makes it more challenging or impossible to prepare an agenda.
>=20
> Well, for one thing the IETF does its work on mailing lists, and
> meetings support that rather than the other way 'round.  For another,
> I'm not sure this deadline makes any difference in practice (other
> than introducing an inconvenience).  We're going to be giving meeting
> time to a draft for which there's no revision, because it needs
> meeting time.  It's on the agenda whether there's a revision or
> not.  I understand the deadline was introduced to provide incentives
> for people to get their stuff in in advance of a meeting.  But.
>=20
> Melinda
>=20
>=20

--=20
I had no shoes and wept.  Then I met a man who had no feet.  So I said, =
"Hey man, got any shoes you're not using?"=20



From grmocg@gmail.com  Tue Feb 26 15:02:35 2013
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 6868621F8814 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.009
X-Spam-Level: 
X-Spam-Status: No, score=-7.009 tagged_above=-999 required=5 tests=[AWL=-3.411, 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 Svw0aAKEsT9s for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:02:34 -0800 (PST)
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by ietfa.amsl.com (Postfix) with ESMTP id A1B7A21F8809 for <ietf@ietf.org>; Tue, 26 Feb 2013 15:02:34 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id l10so6468749oag.2 for <ietf@ietf.org>; Tue, 26 Feb 2013 15:02:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=uI4iVk+RPh/aS8ELvDyXay6HbfVApNqCv7QUCQRNNPQ=; b=X+iZjYYqd9cBm4DhpiAM8Kcg8C5bE6SBD3Z/+xC/9OoxBPeggkKllfRxRluBCqtsrT sa8bCWI1EomBkEh23UpFyHemIVWTsttW+QNJzTW/XghMDwLZJwKekQJ9mVIoxiXdB6Gl BJogvytOIErIwY4ibQb9Zn8/JiISiCGdOIKv5l6EmdwtjDzw7x+7imajUIne+h6COYs1 LRPOL/COs6ulP0s1Ea2YxEmLEisz+6ljG3w7wTCelssLH0kFvSEevmIOFR3zEq3ZUfTf jG3EVCKYsS20nEFlJdQeXiSWoPqDeAUXHLjFzYzwfubj/PxXleJ7bZ56/6AXVGKOgj+s ZVeg==
MIME-Version: 1.0
X-Received: by 10.60.13.162 with SMTP id i2mr3325153oec.121.1361919754259; Tue, 26 Feb 2013 15:02:34 -0800 (PST)
Received: by 10.76.109.72 with HTTP; Tue, 26 Feb 2013 15:02:34 -0800 (PST)
In-Reply-To: <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com> <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com> <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
Date: Tue, 26 Feb 2013 15:02:34 -0800
Message-ID: <CAP+FsNfbx0at0xmNKDUrTpqMLREbuRVtQvSCEKx68LNUPnJ4aQ@mail.gmail.com>
Subject: Re: [IETF] Re: Internet Draft Final Submission Cut-Off Today
From: Roberto Peon <grmocg@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=e89a8fb201182a580204d6a8a726
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, 26 Feb 2013 23:02:35 -0000

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

For that to help, one must also assert that the people who would read the
changes two weeks before the meeting wouldn't read the changes the night
before the meeting, and that they'll remember whatever it is they need to
remember to be a useful active participant.
-=3DR


On Tue, Feb 26, 2013 at 2:59 PM, Warren Kumari <warren@kumari.net> wrote:

>
> On Feb 26, 2013, at 5:54 PM, Roberto Peon <grmocg@gmail.com> wrote:
>
> > I'm not sure that the deadline serves any positive purpose so long as w=
e
> keep all of the versions anyway.
> > It certainly is annoying the way it is now and is disruptive to the
> development process rather than helpful for it.
>
> Um, maybe.
>
> Another way to look at it is that a deadline, any deadline, helps stop
> folk procrastinating and actually *submit*.
>
> Have a look at the number of submissions just before the cutoffs=85
>
> W
>
> >
> > -=3DR
> >
> >
> > On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore <melinda.shore@gmail.com=
>
> wrote:
> > On 2/26/13 1:45 PM, Paul E. Jones wrote:
> > > On the one hand, having a cut-off time could help WG chairs make a
> decision
> > > as to whether to entertain a discussion on a draft.  On the other han=
d,
> > > having no cut-off date might mean that drafts are submitted extremely
> late
> > > and it makes it more challenging or impossible to prepare an agenda.
> >
> > Well, for one thing the IETF does its work on mailing lists, and
> > meetings support that rather than the other way 'round.  For another,
> > I'm not sure this deadline makes any difference in practice (other
> > than introducing an inconvenience).  We're going to be giving meeting
> > time to a draft for which there's no revision, because it needs
> > meeting time.  It's on the agenda whether there's a revision or
> > not.  I understand the deadline was introduced to provide incentives
> > for people to get their stuff in in advance of a meeting.  But.
> >
> > Melinda
> >
> >
>
> --
> I had no shoes and wept.  Then I met a man who had no feet.  So I said,
> "Hey man, got any shoes you're not using?"
>
>
>

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

<div dir=3D"ltr">For that to help, one must also assert that the people who=
 would read the changes two weeks before the meeting wouldn&#39;t read the =
changes the night before the meeting, and that they&#39;ll remember whateve=
r it is they need to remember to be a useful active participant.<div style>
-=3DR</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quo=
te">On Tue, Feb 26, 2013 at 2:59 PM, Warren Kumari <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:warren@kumari.net" target=3D"_blank">warren@kumari.net</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"><br>
On Feb 26, 2013, at 5:54 PM, Roberto Peon &lt;<a href=3D"mailto:grmocg@gmai=
l.com">grmocg@gmail.com</a>&gt; wrote:<br>
<br>
&gt; I&#39;m not sure that the deadline serves any positive purpose so long=
 as we keep all of the versions anyway.<br>
&gt; It certainly is annoying the way it is now and is disruptive to the de=
velopment process rather than helpful for it.<br>
<br>
</div>Um, maybe.<br>
<br>
Another way to look at it is that a deadline, any deadline, helps stop folk=
 procrastinating and actually *submit*.<br>
<br>
Have a look at the number of submissions just before the cutoffs=85<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
W<br>
<br>
&gt;<br>
&gt; -=3DR<br>
&gt;<br>
&gt;<br>
&gt; On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore &lt;<a href=3D"mailto:m=
elinda.shore@gmail.com">melinda.shore@gmail.com</a>&gt; wrote:<br>
&gt; On 2/26/13 1:45 PM, Paul E. Jones wrote:<br>
&gt; &gt; On the one hand, having a cut-off time could help WG chairs make =
a decision<br>
&gt; &gt; as to whether to entertain a discussion on a draft. =A0On the oth=
er hand,<br>
&gt; &gt; having no cut-off date might mean that drafts are submitted extre=
mely late<br>
&gt; &gt; and it makes it more challenging or impossible to prepare an agen=
da.<br>
&gt;<br>
&gt; Well, for one thing the IETF does its work on mailing lists, and<br>
&gt; meetings support that rather than the other way &#39;round. =A0For ano=
ther,<br>
&gt; I&#39;m not sure this deadline makes any difference in practice (other=
<br>
&gt; than introducing an inconvenience). =A0We&#39;re going to be giving me=
eting<br>
&gt; time to a draft for which there&#39;s no revision, because it needs<br=
>
&gt; meeting time. =A0It&#39;s on the agenda whether there&#39;s a revision=
 or<br>
&gt; not. =A0I understand the deadline was introduced to provide incentives=
<br>
&gt; for people to get their stuff in in advance of a meeting. =A0But.<br>
&gt;<br>
&gt; Melinda<br>
&gt;<br>
&gt;<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
I had no shoes and wept. =A0Then I met a man who had no feet. =A0So I said,=
 &quot;Hey man, got any shoes you&#39;re not using?&quot;<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--e89a8fb201182a580204d6a8a726--

From nick@inex.ie  Tue Feb 26 15:06:54 2013
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F77D21F86F0 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:06:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0l5eJ3BDwNeD for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:06:53 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id 7010221F86E3 for <ietf@ietf.org>; Tue, 26 Feb 2013 15:06:53 -0800 (PST)
X-Envelope-To: <ietf@ietf.org>
Received: from cupcake.foobar.org (twinkie.foobar.org [87.192.56.84]) (authenticated bits=0) by mail.netability.ie (8.14.4/8.14.5) with ESMTP id r1QN3wTc095094 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 26 Feb 2013 23:04:03 GMT (envelope-from nick@inex.ie)
Message-ID: <512D4006.9080203@inex.ie>
Date: Tue, 26 Feb 2013 23:06:46 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [IETF] Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com> <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com> <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
In-Reply-To: <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
X-Enigmail-Version: 1.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=windows-1252
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, 26 Feb 2013 23:06:54 -0000

On 26/02/2013 22:59, Warren Kumari wrote:
> Another way to look at it is that a deadline, any deadline, helps stop folk procrastinating and actually *submit*.

+1

lots of people - including me - are almost entirely event driven (no pun
intended).

Nick


From mnot@mnot.net  Tue Feb 26 15:16:48 2013
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2CF21F86FF for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.571
X-Spam-Level: 
X-Spam-Status: No, score=-105.571 tagged_above=-999 required=5 tests=[AWL=-2.972, 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 9pzqepNGoWYj for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 15:16:47 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id BA86421F86FB for <ietf@ietf.org>; Tue, 26 Feb 2013 15:16:40 -0800 (PST)
Received: from [192.168.1.80] (unknown [118.209.5.152]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id AAD8622E1F3; Tue, 26 Feb 2013 18:16:33 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Internet Draft Final Submission Cut-Off Today
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
Date: Wed, 27 Feb 2013 10:16:30 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <830DCA9D-265B-42A4-8057-4CCD1A42BE8F@mnot.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com> <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com> <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
To: Warren Kumari <warren@kumari.net>
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: Tue, 26 Feb 2013 23:16:48 -0000

On 27/02/2013, at 9:59 AM, Warren Kumari <warren@kumari.net> wrote:

>=20
> On Feb 26, 2013, at 5:54 PM, Roberto Peon <grmocg@gmail.com> wrote:
>=20
>> I'm not sure that the deadline serves any positive purpose so long as =
we keep all of the versions anyway.=20
>> It certainly is annoying the way it is now and is disruptive to the =
development process rather than helpful for it.
>=20
> Um, maybe.
>=20
> Another way to look at it is that a deadline, any deadline, helps stop =
folk procrastinating and actually *submit*.
>=20
> Have a look at the number of submissions just before the cutoffs=85

I think that's a poor trade-off. As discussed before, the publishing =
embargo disrupts work that isn't in sync with meetings. This is a =
tangible and somewhat high price to pay just to serve as a =
procrastination-buster for those that need it.

I'd be willing to deal with an embargo for draft-ietf-*, but don't see =
at all why it extends to other drafts.

Regards,


>> On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore =
<melinda.shore@gmail.com> wrote:
>> On 2/26/13 1:45 PM, Paul E. Jones wrote:
>>> On the one hand, having a cut-off time could help WG chairs make a =
decision
>>> as to whether to entertain a discussion on a draft.  On the other =
hand,
>>> having no cut-off date might mean that drafts are submitted =
extremely late
>>> and it makes it more challenging or impossible to prepare an agenda.
>>=20
>> Well, for one thing the IETF does its work on mailing lists, and
>> meetings support that rather than the other way 'round.  For another,
>> I'm not sure this deadline makes any difference in practice (other
>> than introducing an inconvenience).  We're going to be giving meeting
>> time to a draft for which there's no revision, because it needs
>> meeting time.  It's on the agenda whether there's a revision or
>> not.  I understand the deadline was introduced to provide incentives
>> for people to get their stuff in in advance of a meeting.  But.
>>=20
>> Melinda
>>=20
>>=20
>=20
> --=20
> I had no shoes and wept.  Then I met a man who had no feet.  So I =
said, "Hey man, got any shoes you're not using?"=20
>=20
>=20

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




From scott@kitterman.com  Tue Feb 26 17:41:44 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DEB21F8615 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 17:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAgAx-1Ir+yy for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 17:41:44 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id D487721F8613 for <ietf@ietf.org>; Tue, 26 Feb 2013 17:41:43 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id C213620E411E; Tue, 26 Feb 2013 20:41:42 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1361929302; bh=+2bh/aKFqTDuiD4OJmA8FS9fMTjrs8OCqTsKg2rq/Ak=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JoZRkbSOIoINNeNXGS+TRxcwpQqGuyj18lLQbv1de6uMMzyqS4ON8yRGDF4J8WJEZ p7obWPRQeH3smSF+NSlzMKZaaP2nCI3vZIfWQ+GKMlOWo3MynEn4fBQs8CsmHn8kU6 x1z66P53iIAAWonhjcoAPqGym8qaCJrEooGr7bv4=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id A749E20E40FD;  Tue, 26 Feb 2013 20:41:42 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: [IETF] Internet Draft Final Submission Cut-Off Today
Date: Tue, 26 Feb 2013 20:41:41 -0500
Message-ID: <90798068.bN2CWuo9af@scott-latitude-e6320>
User-Agent: KMail/4.9.4 (Linux/3.5.0-25-generic; KDE/4.9.4; i686; ; )
In-Reply-To: <830DCA9D-265B-42A4-8057-4CCD1A42BE8F@mnot.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net> <830DCA9D-265B-42A4-8057-4CCD1A42BE8F@mnot.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 01:41:44 -0000

On Wednesday, February 27, 2013 10:16:30 AM Mark Nottingham wrote:
> I think that's a poor trade-off. As discussed before, the publishing embargo
> disrupts work that isn't in sync with meetings. This is a tangible and
> somewhat high price to pay just to serve as a procrastination-buster for
> those that need it.
> 
> I'd be willing to deal with an embargo for draft-ietf-*, but don't see at
> all why it extends to other drafts.

Why embargo working group drafts for groups that aren't meeting?  It's a 
pointless roadblock.

Scott K

From johnl@iecc.com  Tue Feb 26 18:10:38 2013
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5360521F85C4 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 18:10:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.035
X-Spam-Level: 
X-Spam-Status: No, score=-111.035 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ILoudMTtGMKZ for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 18:10:37 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id C4DA421F85C2 for <ietf@ietf.org>; Tue, 26 Feb 2013 18:10:30 -0800 (PST)
Received: (qmail 75943 invoked from network); 27 Feb 2013 02:10:26 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 27 Feb 2013 02:10:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=512d6b11.xn--btvx9d.k1302; i=johnl@user.iecc.com; bh=C1XvZnerP/uHbUnaSAMz76utj2W2xNtujLBymPCGp6E=; b=pYwANhG/VUb0MZ4TljW4vHu3tQmLJ5gHWGDe6DOm1FPkpGNDNBIhYqX2dOlZSFGHiAAjqGhD0PROnr1456eY1vMtZgPYpbPoipzbyJ1cPjvsuiOYjZJSESTQcoL2MgLY0n9CVu3Irn0bXsTnJU3TAAasF/08/iOSEIx2fdGVEeY=
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=512d6b11.xn--btvx9d.k1302; olt=johnl@user.iecc.com; bh=C1XvZnerP/uHbUnaSAMz76utj2W2xNtujLBymPCGp6E=; b=W0KVbZlfPgPV74c5eTN58GYHDlCtt1fmr0Yw2GOFbHh+A1aTzKqBF8s3HXNlHtPqHy/itaOe+Bf7TSeky9gAXMoMY0ccs/ly9K9g2Nm2rPiICCX44mDjFYGDHJaR/5RnZP8PCT9Anchu9ykJaFYP3IvUvRGwieqy1vtk+vw6CUg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 27 Feb 2013 02:10:03 -0000
Message-ID: <20130227021003.41313.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [IETF] Internet Draft Final Submission Cut-Off Today
In-Reply-To: <830DCA9D-265B-42A4-8057-4CCD1A42BE8F@mnot.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: 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: Wed, 27 Feb 2013 02:10:38 -0000

>I'd be willing to deal with an embargo for draft-ietf-*, but don't see at all why it extends
>to other drafts.

We have software.  Embargo drafts for WGs that are actually meeting
during the preceding week, leave the others alone.





From worley@shell01.TheWorld.com  Tue Feb 26 19:20:45 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BBE21F85A0 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.757
X-Spam-Level: 
X-Spam-Status: No, score=-2.757 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2BlsxFsbxZNZ for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:20:45 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 62FFA21F858A for <ietf@ietf.org>; Tue, 26 Feb 2013 19:20:44 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1R3Kag5023031; Tue, 26 Feb 2013 22:20:38 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1R3KZ1u2707140; Tue, 26 Feb 2013 22:20:35 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1R3KXUs2701280; Tue, 26 Feb 2013 22:20:33 -0500 (EST)
Date: Tue, 26 Feb 2013 22:20:33 -0500 (EST)
Message-Id: <201302270320.r1R3KXUs2701280@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: mrex@sap.com
In-reply-to: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp> (mrex@sap.com)
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 03:20:46 -0000

> From: mrex@sap.com (Martin Rex)

> I have a recurring remote participation problem with the
> IETF Meeting Agendas, because it specifies the time of WG meeting slots
> in local time (local to the IETF Meeting), but does not give the
> local time zone *anywhere*.
> 
> I would appreciate if the local time zone indication would be added
> like somewhere at the top of the page, to each IETF meeting agenda.

I would be nice to have local time zone information.  But in a pinch,
you can google "Time in Orlando" to get the answer.

As for "date --date='...'", well, ye shall know the workman by his
tools.

Dale

From dougb@dougbarton.us  Tue Feb 26 19:35:45 2013
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E05921F85D6 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Hs2PmLIR2TA for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:35:44 -0800 (PST)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 05EB721F85CB for <ietf@ietf.org>; Tue, 26 Feb 2013 19:35:37 -0800 (PST)
Received: from [IPv6:2001:470:d:5e7:85e7:9937:9229:9ffc] (unknown [IPv6:2001:470:d:5e7:85e7:9937:9229:9ffc]) by dougbarton.us (Postfix) with ESMTPSA id 8B0E222B6E for <ietf@ietf.org>; Wed, 27 Feb 2013 03:35:36 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1361936136; bh=aD21OW9DRUxLk6ydq82tkSTf4eIJJNNYborNMge3A0M=; h=Date:From:To:Subject:References:In-Reply-To; b=q/SrGjn4hlp3OvBGWnY6qOM1OUunA5unLByVaHNxSfd9pR0fWaoXBqDhb399l1E3T coLKD/t/G9yUzaHs7y5H4Dc+5saoWxmiobFjb1rqe9SDTR0jD8/hKjGy/GzpeZokzA sYLJ23fv978J/fx45pbtsivckzCZUngn42AUyMyo=
Message-ID: <512D7F07.8040308@dougbarton.us>
Date: Tue, 26 Feb 2013 19:35:35 -0800
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>	<512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
In-Reply-To: <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
X-Enigmail-Version: 1.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 03:35:45 -0000

On 02/26/2013 02:49 PM, Margaret Wasserman wrote:
>
> On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
>
>> But more seriously: I agree with you both. The deadline is silly.
>
> +1
>
> The deadline originated because the secretariat needed time to post all of those drafts (by hand) before the meeting.  The notion of an automated tool that blocks submissions for two weeks before the meeting is just silly.

-1

There are a non-trivial number of people who are intensely busy in the 
weeks leading up to a meeting, with a high degree of overlap with the 
set of people we want to be able to actually read the drafts prior to 
the face to face meeting of the WG. The same argument applies, although 
to a somewhat lesser extent, to being able to post for groups that are 
not meeting.

Is a few weeks where people cannot post what they want, when they want 
to; in order for the larger populace of the IETF to be able to focus on 
the activity in and around the meeting REALLY that much of a burden?

Doug


From scott@kitterman.com  Tue Feb 26 19:42:05 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2250021F8653 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:42:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uG4o-+ANrW-t for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 19:42:04 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2985321F8650 for <ietf@ietf.org>; Tue, 26 Feb 2013 19:42:04 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id DE68D20E411E; Tue, 26 Feb 2013 22:41:54 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1361936523; bh=EwYkP8aNfedCGf7hI2IHIWU8i13gIPp6tfdNt8h/s50=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GXNF0NQVSwnpYqQkGb7jfx+Y7N9aXwqyhCTn58P3yIijBSrFpczfNJ0djdIcMDnZ6 zWrqvRs7azKl8idIS6wGNrGE9mBTqokI2LU8VHOR5LqnzdjDOXcu8Kp1VEXTq8GePb /bkAYMnoY9rEgeL60oxTcgqmTIqDIj9oFzuseurc=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id C12CB20E40FD;  Tue, 26 Feb 2013 22:41:54 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
Date: Tue, 26 Feb 2013 22:41:50 -0500
Message-ID: <2367396.pqKL5uhMr8@scott-latitude-e6320>
User-Agent: KMail/4.9.5 (Linux/3.5.0-25-generic; KDE/4.9.5; i686; ; )
In-Reply-To: <512D7F07.8040308@dougbarton.us>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <512D7F07.8040308@dougbarton.us>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 03:42:05 -0000

On Tuesday, February 26, 2013 07:35:35 PM Doug Barton wrote:
> On 02/26/2013 02:49 PM, Margaret Wasserman wrote:
> > On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com> 
wrote:
> >> But more seriously: I agree with you both. The deadline is silly.
> > 
> > +1
> > 
> > The deadline originated because the secretariat needed time to post all of
> > those drafts (by hand) before the meeting.  The notion of an automated
> > tool that blocks submissions for two weeks before the meeting is just
> > silly.
> -1
> 
> There are a non-trivial number of people who are intensely busy in the
> weeks leading up to a meeting, with a high degree of overlap with the
> set of people we want to be able to actually read the drafts prior to
> the face to face meeting of the WG. The same argument applies, although
> to a somewhat lesser extent, to being able to post for groups that are
> not meeting.
> 
> Is a few weeks where people cannot post what they want, when they want
> to; in order for the larger populace of the IETF to be able to focus on
> the activity in and around the meeting REALLY that much of a burden?

How does that relate to working groups that aren't meeting?  It was silly I 
had to rush to post a draft on Monday for a WG that's not meeting.

Scott K

From ajs@anvilwalrusden.com  Tue Feb 26 21:49:01 2013
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B57521F86C4 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 21:49:01 -0800 (PST)
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 p8qRtwrxmvaE for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 21:49:00 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 890B321F85D7 for <ietf@ietf.org>; Tue, 26 Feb 2013 21:49:00 -0800 (PST)
Received: from mx1.yitter.info (c-24-60-131-7.hsd1.nh.comcast.net [24.60.131.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7E16E8A031 for <ietf@ietf.org>; Wed, 27 Feb 2013 05:48:59 +0000 (UTC)
Date: Wed, 27 Feb 2013 00:48:57 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
Message-ID: <20130227054857.GD7506@mx1.yitter.info>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <512D37B0.7010108@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 05:49:01 -0000

On Tue, Feb 26, 2013 at 01:31:12PM -0900, Melinda Shore wrote:
> it's 23:59 + 1 minute, which is clear.  But I really
> think "24:00" is confusing. 0:00 is clearer.  I'm
> wondering if they're trying to work around some ferkakte
> piece of software.

I don't think so.  ISO (ISO 8601) seems to think that "24:00" refers
to the very end of the day, and "00:00" refers to the very beginning
of the next day.  So there's a conceptual distinction involved.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From marka@isc.org  Tue Feb 26 21:54:49 2013
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23AB021F86C4 for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 21:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level: 
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[AWL=0.309,  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 uSppwvoSmwqC for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 21:54:47 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC3421F8526 for <ietf@ietf.org>; Tue, 26 Feb 2013 21:54:47 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 4E0DE5F98BF; Wed, 27 Feb 2013 05:54:37 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1361944486; bh=yy8K29tjv3n2ajzn3tERF3sgT/sjMzuORzcN3jiBavM=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=oKJSlahE2bQ6/2rVOL3ZCA/p2O67CL/HOjGOcBPgLQgwd4HZ+lw3X5I9pLnIW34Z/ tNodryHS+JAuB+hvb+Wmv5fQaVaLTH33lp5+i3i3uKEu+qQncee4ToqI4dmtiGIKzC ib1Rsgjtko948wWZhKBxHvfYfaSm1a2B0u4nfWeU=
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 7FFBB216C40; Wed, 27 Feb 2013 05:54:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 43E7930270AD; Wed, 27 Feb 2013 16:54:31 +1100 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <20130227054857.GD7506@mx1.yitter.info>
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-reply-to: Your message of "Wed, 27 Feb 2013 00:48:57 CDT." <20130227054857.GD7506@mx1.yitter.info>
Date: Wed, 27 Feb 2013 16:54:31 +1100
Message-Id: <20130227055431.43E7930270AD@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, 27 Feb 2013 05:54:49 -0000

In message <20130227054857.GD7506@mx1.yitter.info>, Andrew Sullivan writes:
> On Tue, Feb 26, 2013 at 01:31:12PM -0900, Melinda Shore wrote:
> > it's 23:59 + 1 minute, which is clear.  But I really
> > think "24:00" is confusing. 0:00 is clearer.  I'm
> > wondering if they're trying to work around some ferkakte
> > piece of software.
> 
> I don't think so.  ISO (ISO 8601) seems to think that "24:00" refers
> to the very end of the day, and "00:00" refers to the very beginning
> of the next day.  So there's a conceptual distinction involved.
> 
> A

And to avoid confusion many places use 23:59:59 as end of trading day.

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

From grmocg@gmail.com  Tue Feb 26 22:51:22 2013
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 15A2721F87BA for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 22:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.973
X-Spam-Level: 
X-Spam-Status: No, score=-6.973 tagged_above=-999 required=5 tests=[AWL=-3.375, 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 9KXbiUfmBeMK for <ietf@ietfa.amsl.com>; Tue, 26 Feb 2013 22:51:21 -0800 (PST)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4170321F87AF for <ietf@ietf.org>; Tue, 26 Feb 2013 22:51:20 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id j1so484070oag.21 for <ietf@ietf.org>; Tue, 26 Feb 2013 22:51:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=aNJ0Cxv1wF779jl/3A5FlzE8p23AaxHXcOv/n0H0q8M=; b=oA8HtHZYpVTWZRAYRG+YCTjWb7khlBNmAiu75wnJK6XeOLybpvy8xSap/PBAg5EKJ5 lauBcBNJjYZnkxuYgPimqMS0EcRhO3VzQ2t0ke1h7vFitzmQHT4E0j/Snvn/5zaAm+z2 7jWus/9mB+4t7EY4CpX9xQAT3Xe/2z2asTGLcqsli0VO2jk8J1A4lt0DF51BR+K079lF Sl2KXCYtwQ8tCiwOf97KZOuhf83P1xAZFGsGBoYgR3k00Kyap2RlH5O1nzt0h/JkcmrW 4yHpgdWMduotwNxm465XMazXH0YHBLHZbRWN/3AUGx0U3Ab8uwlZEgC9UDF9awDwbNkT 11Bw==
MIME-Version: 1.0
X-Received: by 10.60.170.80 with SMTP id ak16mr1120369oec.23.1361947880562; Tue, 26 Feb 2013 22:51:20 -0800 (PST)
Received: by 10.76.109.72 with HTTP; Tue, 26 Feb 2013 22:51:20 -0800 (PST)
In-Reply-To: <512D7F07.8040308@dougbarton.us>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <512D7F07.8040308@dougbarton.us>
Date: Tue, 26 Feb 2013 22:51:20 -0800
Message-ID: <CAP+FsNdCSuTN-LSL_q5GoPi8JivMcQfEAN59xRDjsG2L6+uyTA@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Roberto Peon <grmocg@gmail.com>
To: Doug Barton <dougb@dougbarton.us>
Content-Type: multipart/alternative; boundary=bcaec54c501e9fa57004d6af3351
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 06:51:22 -0000

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

I'm doing a lot of work in regards to, creating working code, benchmarking,
testing, writing specs and prose, writing emails, wash, rinse, repeat, and
yes, the deadline is interfering with the publishing of the work-product of
all of that and likely the progress of the group.

... and what is the benefit of the arbitrary 2-weeks-before deadline?
Arguably so people can read the drafts, yes I understand that, yet if the
active participants don't have time to read it, then it won't get time for
discussion at the meeting. If they did, then it will be discussed, and if
people feel that it wasn't presented early enough, then they say so on the
various venues available, not limited simply to stating so at the
microphone.
-=R


On Tue, Feb 26, 2013 at 7:35 PM, Doug Barton <dougb@dougbarton.us> wrote:

> On 02/26/2013 02:49 PM, Margaret Wasserman wrote:
>
>>
>> On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com>
>> wrote:
>>
>>  But more seriously: I agree with you both. The deadline is silly.
>>>
>>
>> +1
>>
>> The deadline originated because the secretariat needed time to post all
>> of those drafts (by hand) before the meeting.  The notion of an automated
>> tool that blocks submissions for two weeks before the meeting is just silly.
>>
>
> -1
>
> There are a non-trivial number of people who are intensely busy in the
> weeks leading up to a meeting, with a high degree of overlap with the set
> of people we want to be able to actually read the drafts prior to the face
> to face meeting of the WG. The same argument applies, although to a
> somewhat lesser extent, to being able to post for groups that are not
> meeting.
>
> Is a few weeks where people cannot post what they want, when they want to;
> in order for the larger populace of the IETF to be able to focus on the
> activity in and around the meeting REALLY that much of a burden?
>
> Doug
>
>

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

<div dir=3D"ltr">I&#39;m doing a lot of work in regards to, creating workin=
g code, benchmarking, testing, writing specs and prose, writing emails, was=
h, rinse, repeat, and yes, the deadline is interfering with the publishing =
of the work-product of all of that and likely the progress of the group.<di=
v>
<br></div><div>... and what is the benefit of the arbitrary 2-weeks-before =
deadline? Arguably so people can read the drafts, yes I understand that, ye=
t if the active participants don&#39;t have time to read it, then it won&#3=
9;t get time for discussion at the meeting. If they did, then it will be di=
scussed, and if people feel that it wasn&#39;t presented early enough, then=
 they say so on the various venues available, not limited simply to stating=
 so at the microphone.</div>
<div style>-=3DR</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Tue, Feb 26, 2013 at 7:35 PM, Doug Barton <span dir=3D"=
ltr">&lt;<a href=3D"mailto:dougb@dougbarton.us" target=3D"_blank">dougb@dou=
gbarton.us</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On 0=
2/26/2013 02:49 PM, Margaret Wasserman wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
On Feb 26, 2013, at 5:38 PM, Pete Resnick &lt;<a href=3D"mailto:presnick@qt=
i.qualcomm.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt; wrote:<=
br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
But more seriously: I agree with you both. The deadline is silly.<br>
</blockquote>
<br>
+1<br>
<br>
The deadline originated because the secretariat needed time to post all of =
those drafts (by hand) before the meeting. =A0The notion of an automated to=
ol that blocks submissions for two weeks before the meeting is just silly.<=
br>

</blockquote>
<br></div></div>
-1<br>
<br>
There are a non-trivial number of people who are intensely busy in the week=
s leading up to a meeting, with a high degree of overlap with the set of pe=
ople we want to be able to actually read the drafts prior to the face to fa=
ce meeting of the WG. The same argument applies, although to a somewhat les=
ser extent, to being able to post for groups that are not meeting.<br>

<br>
Is a few weeks where people cannot post what they want, when they want to; =
in order for the larger populace of the IETF to be able to focus on the act=
ivity in and around the meeting REALLY that much of a burden?<span class=3D=
"HOEnZb"><font color=3D"#888888"><br>

<br>
Doug<br>
<br>
</font></span></blockquote></div><br></div>

--bcaec54c501e9fa57004d6af3351--

From stefan.winter@restena.lu  Wed Feb 27 00:46:36 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22A2321F850C for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_14=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 ktvc29kCYuos for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:46:35 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3DE21F8506 for <ietf@ietf.org>; Wed, 27 Feb 2013 00:46:33 -0800 (PST)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id AD99F10589 for <ietf@ietf.org>; Wed, 27 Feb 2013 09:46:31 +0100 (CET)
Received: from [IPv6:2001:a18:1:8:c1a3:676a:f579:5714] (unknown [IPv6:2001:a18:1:8:c1a3:676a:f579:5714]) by smtprelay.restena.lu (Postfix) with ESMTPS id A346410583 for <ietf@ietf.org>; Wed, 27 Feb 2013 09:46:31 +0100 (CET)
Message-ID: <512DC7E3.8080501@restena.lu>
Date: Wed, 27 Feb 2013 09:46:27 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com>
In-Reply-To: <512D37B0.7010108@gmail.com>
X-Enigmail-Version: 1.5
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2KDHPSABDQRTDAIKGSBVW"
X-Virus-Scanned: ClamAV
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 08:46:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2KDHPSABDQRTDAIKGSBVW
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

> [...] ferkakte [...]

As a German, I'm now torn apart between being flattered that we've
successfully exported a German word to the U.S. and being speechlessly
shocked by the way spelling was b0rked in the process.

Stefan

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


------enig2KDHPSABDQRTDAIKGSBVW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEtx+cACgkQ+jm90f8eFWYDoACbBhZTYzp1JWKKSWPj+C1jLBja
2IsAni4zC4KXPZ+TEcbRWe9ec4GQiQUl
=3Bqr
-----END PGP SIGNATURE-----

------enig2KDHPSABDQRTDAIKGSBVW--

From glenzorn@gmail.com  Wed Feb 27 00:53:02 2013
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB95A21F85A1 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:53:01 -0800 (PST)
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 yHkN60kau5Cp for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:53:01 -0800 (PST)
Received: from mail-da0-f42.google.com (mail-da0-f42.google.com [209.85.210.42]) by ietfa.amsl.com (Postfix) with ESMTP id C3B6521F85E7 for <ietf@ietf.org>; Wed, 27 Feb 2013 00:53:00 -0800 (PST)
Received: by mail-da0-f42.google.com with SMTP id n15so195941dad.29 for <ietf@ietf.org>; Wed, 27 Feb 2013 00:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=JrQzObQ81k9Mb0UrFH9q4Ui5qXS/nE2faqZrk+ZIB3E=; b=PtZUT5AZtiaNRf1BH2mNF6HWAobPNzobKD2EUpLzMKv2iBrfwxCsDih/299j8FaqbO FePxUCCAGMhY+InQDkfs7C9rnHKX9OGD2aesp6LSLdbsE1LjjdyLSIbWv3u/bAKTeevZ duU/v5j/fLcWg7ObfW6DvjI0zQiCM8Q7wvC7Oo7e4XZE8qKZ3SwYAZ3HeQ1iJm89X51u /nqU4dbVxq08LScWrG/q8mffA4Pl0JJa2+sly9wArxCCszERrzqhfiFP8YK0aYEYvqTc IT9kNJsk1DcHIxM5pgnY7lxsLprRfX7dbArLKSsRSZ9GlZ9rdpv+w0rGWRPyL6widIWe SAEA==
X-Received: by 10.68.213.66 with SMTP id nq2mr2259437pbc.29.1361955178051; Wed, 27 Feb 2013 00:52:58 -0800 (PST)
Received: from [192.168.0.104] (ppp-124-122-121-4.revip2.asianet.co.th. [124.122.121.4]) by mx.google.com with ESMTPS id k7sm4640143paz.13.2013.02.27.00.52.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Feb 2013 00:52:57 -0800 (PST)
Message-ID: <512DC965.1040606@gmail.com>
Date: Wed, 27 Feb 2013 15:52:53 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130126 Thunderbird/17.0.2
MIME-Version: 1.0
To: Stefan Winter <stefan.winter@restena.lu>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu>
In-Reply-To: <512DC7E3.8080501@restena.lu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 08:53:02 -0000

On 02/27/2013 03:46 PM, Stefan Winter wrote:
> Hi,
 >
 >> [...] ferkakte [...]
 >
 > As a German, I'm now torn apart between being flattered that we've
 > successfully exported a German word to the U.S. and being
 > speechlessly shocked by the way spelling was b0rked in the process.

I believe that it's actually Yiddish.

>
 >
 > Stefan
 >



From klaas@cisco.com  Wed Feb 27 00:58:55 2013
Return-Path: <klaas@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 B916E21F85AF for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.299
X-Spam-Level: 
X-Spam-Status: No, score=-10.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d+cJ7lec0AMt for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 00:58:55 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id D501621F8495 for <ietf@ietf.org>; Wed, 27 Feb 2013 00:58:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=626; q=dns/txt; s=iport; t=1361955535; x=1363165135; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Yh2BYacTEhjk3ihNehQYDLD9TQ2Bg9w0OydsdGTR93s=; b=LmI1KwP0kXNPO43NZHsg+grCJ3f8pxwF1pIkt95oAwuW9onEyKqDR9he RWvuG07R7VVi0L8XTbkwkYdkGvjbbNI3gMTkXiqM2uEqN4c0+ydWK/hJn 8GI98a1r/UZsDhgVf/uzdop467cOGbg3yAMkdGN8bj+UoGRj53j+5dvWh E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FADbJLVGQ/khL/2dsb2JhbAArGoYIvAR8FnOCHwEBAQMBeQULCxguITYGE4gBAwkGDC60Qw2JWow8giUzB4JfYQOUZIFdi1OFF4MJ
X-IronPort-AV: E=Sophos;i="4.84,746,1355097600"; d="scan'208";a="80750906"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 27 Feb 2013 08:58:53 +0000
Received: from dhcp-10-61-101-248.cisco.com (dhcp-10-61-101-248.cisco.com [10.61.101.248]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1R8wrm0002464 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 27 Feb 2013 08:58:53 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Klaas Wierenga <klaas@cisco.com>
In-Reply-To: <512DC965.1040606@gmail.com>
Date: Wed, 27 Feb 2013 09:58:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F09E051-FC1E-42C3-A706-12E639AF60F3@cisco.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu> <512DC965.1040606@gmail.com>
To: Glen Zorn <glenzorn@gmail.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: Wed, 27 Feb 2013 08:58:55 -0000

On Feb 27, 2013, at 9:52 AM, Glen Zorn <glenzorn@gmail.com>
 wrote:

> On 02/27/2013 03:46 PM, Stefan Winter wrote:
>> Hi,
> >
> >> [...] ferkakte [...]
> >
> > As a German, I'm now torn apart between being flattered that we've
> > successfully exported a German word to the U.S. and being
> > speechlessly shocked by the way spelling was b0rked in the process.
>=20
> I believe that it's actually Yiddish.

yup: =
http://www.yiddishdictionaryonline.com/dictionary/display.php?action=3Dsea=
rch&type=3Drom&word=3Dfarkakt

still my bet would be that this Yiddish word has Germanic origins=85.=20

Klaas=

From tjc@ecs.soton.ac.uk  Wed Feb 27 01:20:19 2013
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0EB521F8491 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:20:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.458
X-Spam-Level: 
X-Spam-Status: No, score=-2.458 tagged_above=-999 required=5 tests=[AWL=0.141,  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 Ic5uZVTI3d0Q for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:20:17 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5AE21F84C9 for <ietf@ietf.org>; Wed, 27 Feb 2013 01:20:16 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r1R9KCWf025262 for <ietf@ietf.org>; Wed, 27 Feb 2013 09:20:12 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk r1R9KCWf025262
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1361956812; bh=QIy1qkd+jvCFSBUalIVvdhO3C1M=; h=Mime-Version:Subject:From:In-Reply-To:Date:References:To; b=a5yAfjlMFFMS2z8591Iwcu2DdIC5GY/XNqJaEj4Gs/QFx6frPxmPISb9Wl9k1Jbew uwtAkkw4GrT+qwbWTcLnyZ8iHCZXOEd3+FETX3o7i6PpTD+ejunw7oteiSZazQCaq0 muT20pnM1ZGOkIvW2x62oLuPMbm5Qw0GCp595mDU=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id p1Q9KC0430608058Wd ret-id none; Wed, 27 Feb 2013 09:20:12 +0000
Received: from [192.168.1.103] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id r1R9K8Ow020980 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Wed, 27 Feb 2013 09:20:09 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Time zones in IETF agenda
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
Date: Wed, 27 Feb 2013 09:20:09 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp> <363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=p1Q9KC043060805800; tid=p1Q9KC0430608058Wd; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: r1R9KCWf025262
X-ECS-MailScanner-From: tjc@ecs.soton.ac.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, 27 Feb 2013 09:20:20 -0000

On 26 Feb 2013, at 20:28, Martin Rex <mrex@sap.com> wrote:

> I have a recurring remote participation problem with the
> IETF Meeting Agendas, because it specifies the time of WG meeting =
slots
> in local time (local to the IETF Meeting), but does not give the
> local time zone *anywhere*.
>=20
> I would appreciate if the local time zone indication would be added
> like somewhere at the top of the page, to each IETF meeting agenda.

So in this interesting discussion of UTC, Martin has actually made an =
excellent point.  Having UTC listings for the agenda would be very =
helpful, or an alternative agenda showing UTC.

Tim


From stefan.winter@restena.lu  Wed Feb 27 01:24:50 2013
Return-Path: <stefan.winter@restena.lu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 685A921F84E9 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=-0.225, BAYES_00=-2.599, J_CHICKENPOX_14=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 m+fmiqWWdz2N for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:24:46 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 3538621F8526 for <ietf@ietf.org>; Wed, 27 Feb 2013 01:24:41 -0800 (PST)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 9C80D10589; Wed, 27 Feb 2013 10:24:34 +0100 (CET)
Received: from [IPv6:2001:a18:1:8:c1a3:676a:f579:5714] (unknown [IPv6:2001:a18:1:8:c1a3:676a:f579:5714]) by smtprelay.restena.lu (Postfix) with ESMTPS id 91C3610583; Wed, 27 Feb 2013 10:24:34 +0100 (CET)
Message-ID: <512DD0CC.4040905@restena.lu>
Date: Wed, 27 Feb 2013 10:24:28 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Klaas Wierenga <klaas@cisco.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu> <512DC965.1040606@gmail.com> <3F09E051-FC1E-42C3-A706-12E639AF60F3@cisco.com>
In-Reply-To: <3F09E051-FC1E-42C3-A706-12E639AF60F3@cisco.com>
X-Enigmail-Version: 1.5
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2EQSSQXBINKWOBLSDFLCV"
X-Virus-Scanned: ClamAV
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 09:24:50 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
------enig2EQSSQXBINKWOBLSDFLCV
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,

>>>> [...] ferkakte [...]
>>>
>>> As a German, I'm now torn apart between being flattered that we've
>>> successfully exported a German word to the U.S. and being
>>> speechlessly shocked by the way spelling was b0rked in the process.
>>
>> I believe that it's actually Yiddish.
>=20
> yup: http://www.yiddishdictionaryonline.com/dictionary/display.php?acti=
on=3Dsearch&type=3Drom&word=3Dfarkakt
>=20
> still my bet would be that this Yiddish word has Germanic origins=85.=20

Here we see one of the *good* things about having an I-D cutoff
deadline. One finally finds time to do /other/ things ;-)

Stefan

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


------enig2EQSSQXBINKWOBLSDFLCV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlEt0NIACgkQ+jm90f8eFWarXwCfUYSs2oGu/Qxps5hwQxOfCc5e
9h4An1Sarf3O6JbCbhVUJWKRK7sLMWnh
=4DdE
-----END PGP SIGNATURE-----

------enig2EQSSQXBINKWOBLSDFLCV--

From trammell@tik.ee.ethz.ch  Wed Feb 27 01:28:58 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA7321F857A for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.212
X-Spam-Level: 
X-Spam-Status: No, score=-6.212 tagged_above=-999 required=5 tests=[AWL=0.387,  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 9P7pnHFrA7X6 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:28:58 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 1999721F8576 for <ietf@ietf.org>; Wed, 27 Feb 2013 01:28:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id 46246D9308; Wed, 27 Feb 2013 10:28:57 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 97nBjk-NRBEC; Wed, 27 Feb 2013 10:28:56 +0100 (MET)
Received: from [10.0.27.102] (cust-integra-122-165.antanet.ch [80.75.122.165]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id D0826D930A; Wed, 27 Feb 2013 10:28:56 +0100 (MET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Time zones in IETF agenda
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
Date: Wed, 27 Feb 2013 10:28:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0191B2F0-A469-4952-8BF7-203715833B0A@tik.ee.ethz.ch>
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp> <363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk> <EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
To: Tim Chown <tjc@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 09:28:59 -0000

On Feb 27, 2013, at 10:20 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> On 26 Feb 2013, at 20:28, Martin Rex <mrex@sap.com> wrote:
>=20
>> I have a recurring remote participation problem with the
>> IETF Meeting Agendas, because it specifies the time of WG meeting =
slots
>> in local time (local to the IETF Meeting), but does not give the
>> local time zone *anywhere*.
>>=20
>> I would appreciate if the local time zone indication would be added
>> like somewhere at the top of the page, to each IETF meeting agenda.
>=20
> So in this interesting discussion of UTC, Martin has actually made an =
excellent point.  Having UTC listings for the agenda would be very =
helpful, or an alternative agenda showing UTC.

+1. Given our high remote participation, I put UTC in the agenda for the =
MILE WG anyway (usually correctly, even). And given that the IETF often =
meets on one side or another of the DST change in local time, having an =
unchanging time reference would be helpful even for attendees.

Cheers,

Brian=

From brian.e.carpenter@gmail.com  Wed Feb 27 01:53:28 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7580E21F84B8 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.579
X-Spam-Level: 
X-Spam-Status: No, score=-99.579 tagged_above=-999 required=5 tests=[AWL=-0.658, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6e8r2ZrhjiKw for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 01:53:28 -0800 (PST)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id C0EB421F84A9 for <ietf@ietf.org>; Wed, 27 Feb 2013 01:53:27 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id l13so7243246wie.0 for <ietf@ietf.org>; Wed, 27 Feb 2013 01:53:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HIKV5GBjbRbPrlTrjlkQOL7sJA00PMW3uFMOhtJk1eQ=; b=0cAd+TDj/C9E7CL35I69VhC8Lbk2vP76vGHi/6C1tdxff8KW5YerM1y2Iwgn+qEZ9F M/g0DVOR0mx1QgOWtGgnZE54CGmJxjWOkkAoHXVWctwkxvx3yd6ivaYkPM6P0mbV9pxH BT1CpDOwmvoU3/TkHxOcNrxX4+1IFkrVFOt/1/MjFbIrci0KgSZWWqtTQRLJZM2k5DAu LdZZb/W7bTjIWSvAHyICY+A22xMR6fBuWPOcoN1Boz4+gNhcpETheVLGBLbER44zLs8U +GLLb2LhkcnV+/QW7gmNy5WAvDbBIhmyOrcdNim7nNIEXTV0/OXyVsOB0VS13syKtddz dmag==
X-Received: by 10.194.119.68 with SMTP id ks4mr2691592wjb.3.1361958806726; Wed, 27 Feb 2013 01:53:26 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-189-70.as13285.net. [2.101.189.70]) by mx.google.com with ESMTPS id m6sm7542073wic.2.2013.02.27.01.53.24 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Feb 2013 01:53:25 -0800 (PST)
Message-ID: <512DD798.7060303@gmail.com>
Date: Wed, 27 Feb 2013 09:53:28 +0000
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: Brian Trammell <trammell@tik.ee.ethz.ch>
Subject: Re: Time zones in IETF agenda
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>	<363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>	<EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk> <0191B2F0-A469-4952-8BF7-203715833B0A@tik.ee.ethz.ch>
In-Reply-To: <0191B2F0-A469-4952-8BF7-203715833B0A@tik.ee.ethz.ch>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 09:53:28 -0000

On 27/02/2013 09:28, Brian Trammell wrote:
> On Feb 27, 2013, at 10:20 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
> 
>> On 26 Feb 2013, at 20:28, Martin Rex <mrex@sap.com> wrote:
>>
>>> I have a recurring remote participation problem with the
>>> IETF Meeting Agendas, because it specifies the time of WG meeting slots
>>> in local time (local to the IETF Meeting), but does not give the
>>> local time zone *anywhere*.
>>>
>>> I would appreciate if the local time zone indication would be added
>>> like somewhere at the top of the page, to each IETF meeting agenda.
>> So in this interesting discussion of UTC, Martin has actually made an excellent point.  Having UTC listings for the agenda would be very helpful, or an alternative agenda showing UTC.
> 
> +1. Given our high remote participation, I put UTC in the agenda for the MILE WG anyway (usually correctly, even). And given that the IETF often meets on one side or another of the DST change in local time, having an unchanging time reference would be helpful even for attendees.

UTC time *and* date please, for people in whichever hemisphere happens to be
opposite the IETF.

   Brian

From fanf2@hermes.cam.ac.uk  Wed Feb 27 04:19:27 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AD7321F852B for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 04:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.634
X-Spam-Level: 
X-Spam-Status: No, score=-3.634 tagged_above=-999 required=5 tests=[AWL=-1.035, 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 Adc28Tuth48m for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 04:19:24 -0800 (PST)
Received: from ppsw-42.csi.cam.ac.uk (ppsw-42.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f42]) by ietfa.amsl.com (Postfix) with ESMTP id 25E4A21F8549 for <ietf@ietf.org>; Wed, 27 Feb 2013 04:19:24 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:37388) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:25) with esmtpa (EXTERNAL:fanf2) id 1UAfyf-00084h-9E (Exim 4.80_167-5a66dd3) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 27 Feb 2013 12:19:17 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1UAfyf-0001m7-71 (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 27 Feb 2013 12:19:17 +0000
Date: Wed, 27 Feb 2013 12:19:17 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: "Paul E. Jones" <paulej@packetizer.com>
Subject: RE: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>
Message-ID: <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 12:19:27 -0000

Paul E. Jones <paulej@packetizer.com> wrote:
>
> Seriously, what the heck is 24:00?

See http://dotat.at/tmp/ISO_8601-2004_E.pdf section 4.2.3 "midnight"

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From mehmet.ersue@nsn.com  Wed Feb 27 04:31:56 2013
Return-Path: <mehmet.ersue@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F4221F856D; Wed, 27 Feb 2013 04:31:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.563
X-Spam-Level: 
X-Spam-Status: No, score=-106.563 tagged_above=-999 required=5 tests=[AWL=0.036, 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 M+tlN0XCPNmo; Wed, 27 Feb 2013 04:31:55 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8560921F854C; Wed, 27 Feb 2013 04:31:55 -0800 (PST)
Received: from demuprx017.emea.nsn-intra.net ([10.150.129.56]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r1RCVjGG007506 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 27 Feb 2013 13:31:45 +0100
Received: from DEMUHTC003.nsn-intra.net ([10.159.42.34]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r1RCVhO5024310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 27 Feb 2013 13:31:45 +0100
Received: from DEMUHTC013.nsn-intra.net (10.159.42.44) by DEMUHTC003.nsn-intra.net (10.159.42.34) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 27 Feb 2013 13:31:42 +0100
Received: from DEMUMBX005.nsn-intra.net ([169.254.5.216]) by DEMUHTC013.nsn-intra.net ([10.159.42.44]) with mapi id 14.02.0328.009; Wed, 27 Feb 2013 13:31:42 +0100
From: "Ersue, Mehmet (NSN - DE/Munich)" <mehmet.ersue@nsn.com>
To: ext Tony Finch <dot@dotat.at>, "Paul E. Jones" <paulej@packetizer.com>
Subject: RE: Internet Draft Final Submission Cut-Off Today
Thread-Topic: Internet Draft Final Submission Cut-Off Today
Thread-Index: AQHOFOS6eX1/rBeGokWQ1B/nUNzRqJiNorMA
Date: Wed, 27 Feb 2013 12:31:41 +0000
Message-ID: <E4DE949E6CE3E34993A2FF8AE79131F804E611@DEMUMBX005.nsn-intra.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.159.42.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 933
X-purgate-ID: 151667::1361968305-0000547A-E5CA6295/0-0/0-0
Cc: "86attendees@ietf.org" <86attendees@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, 27 Feb 2013 12:31:56 -0000

Do not worry that much and use:=20
http://www.timeanddate.com/worldclock/meetingtime.html?month=3D3&day=3D11&y=
ear=3D2013&p1=3D224&p2=3D64&p3=3D43&p4=3D37&p5=3D33&iv=3D0=20

Cheers,=20
Mehmet=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of e=
xt Tony
> Finch
> Sent: Wednesday, February 27, 2013 1:19 PM
> To: Paul E. Jones
> Cc: ietf@ietf.org
> Subject: RE: Internet Draft Final Submission Cut-Off Today
>=20
> Paul E. Jones <paulej@packetizer.com> wrote:
> >
> > Seriously, what the heck is 24:00?
>=20
> See http://dotat.at/tmp/ISO_8601-2004_E.pdf section 4.2.3 "midnight"
>=20
> Tony.
> --
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at fir=
st.
> Rough, becoming slight or moderate. Showers, rain at first. Moderate or g=
ood,
> occasionally poor at first.

From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 27 04:57:45 2013
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 73F2C21F859D for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 04:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.09
X-Spam-Level: 
X-Spam-Status: No, score=-1.09 tagged_above=-999 required=5 tests=[AWL=-1.000,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58LNxwZArbhI for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 04:57:43 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 54A1821F85AF for <ietf@ietf.org>; Wed, 27 Feb 2013 04:57:43 -0800 (PST)
Received: (qmail 51656 invoked from network); 27 Feb 2013 12:56:01 -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; 27 Feb 2013 12:56:01 -0000
Message-ID: <512E0297.6070708@necom830.hpcl.titech.ac.jp>
Date: Wed, 27 Feb 2013 21:56:55 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk>
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: Wed, 27 Feb 2013 12:57:45 -0000

(2013/02/27 21:19), Tony Finch wrote:
> Paul E. Jones <paulej@packetizer.com> wrote:
>>
>> Seriously, what the heck is 24:00?
> 
> See http://dotat.at/tmp/ISO_8601-2004_E.pdf section 4.2.3 "midnight"

The IS should clarify that a day is [0:0, 24:0), not [0:0, 24:0]
and everything should be fine.

						Masataka Ohta


From fanf2@hermes.cam.ac.uk  Wed Feb 27 05:32:59 2013
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7883E21F8622 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 05:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.56
X-Spam-Level: 
X-Spam-Status: No, score=-5.56 tagged_above=-999 required=5 tests=[AWL=1.039,  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 YSfZM0YCmTGZ for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 05:32:58 -0800 (PST)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 6B97D21F8611 for <ietf@ietf.org>; Wed, 27 Feb 2013 05:32:58 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:48607) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1UAh7v-0002ny-pv (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 27 Feb 2013 13:32:55 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1UAh7v-0003aP-2T (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Wed, 27 Feb 2013 13:32:55 +0000
Date: Wed, 27 Feb 2013 13:32:55 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-Reply-To: <512E0297.6070708@necom830.hpcl.titech.ac.jp>
Message-ID: <alpine.LSU.2.00.1302271326330.27013@hermes-1.csi.cam.ac.uk>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk> <512E0297.6070708@necom830.hpcl.titech.ac.jp>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 13:32:59 -0000

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> wrote:
> (2013/02/27 21:19), Tony Finch wrote:
> > Paul E. Jones <paulej@packetizer.com> wrote:
> >>
> >> Seriously, what the heck is 24:00?
> >
> > See http://dotat.at/tmp/ISO_8601-2004_E.pdf section 4.2.3 "midnight"
>
> The IS should clarify that a day is [0:0, 24:0), not [0:0, 24:0]
> and everything should be fine.

Its definition of a calendar day is consistent with its definition of a
time interval. It doesn't make any distinction between including and
excluding the end instants. And I don't think it would be sensible to do
so: it would clutter the time interval notation with no clear benefit.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Forties, Cromarty: East, veering southeast, 4 or 5, occasionally 6 at first.
Rough, becoming slight or moderate. Showers, rain at first. Moderate or good,
occasionally poor at first.

From victor.kuarsingh@gmail.com  Wed Feb 27 05:37:50 2013
Return-Path: <victor.kuarsingh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53A8621F85E7 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 05:37:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.454
X-Spam-Level: 
X-Spam-Status: No, score=-0.454 tagged_above=-999 required=5 tests=[AWL=0.260,  BAYES_00=-2.599, FH_RELAY_NODNS=1.451, IP_NOT_FRIENDLY=0.334, 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 olFA+yohCj2q for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 05:37:49 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BD51621F85BB for <ietf@ietf.org>; Wed, 27 Feb 2013 05:37:49 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id c11so601006ieb.29 for <ietf@ietf.org>; Wed, 27 Feb 2013 05:37:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:user-agent:date:subject:from:to:cc:message-id :thread-topic:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=yVJSp3M6MBeR7u9XpStvHZAbJfcAw46R1YSPE/UywVg=; b=TE/XlBOnzgwpHp+ABc5w1PDX6gcja1ekoWnbQPd0nqbIpPW1WdIKN93z2yb3i02zZG BSjdvxWBeSPAl4J2ZkqLv4PFMX0++iv2oGadXFore8+cj5zw9pqvJBjdYt9XIXH1RjKF T8aVqGcoD96RBdsssrnilbssPw1ZvuVa+uoMy8zLn4uJbyqsE3s+4vlUCh4EvwawrKU7 GaWErbkxRgqVJwUNI4EeRSCVEN1SRqC4wWOVCzDPwSk75mDpCzZ3eD1TNzr081GrlEv1 uzHJQVGHSys2/lX1Djfw3bAi5ThhxPzFvX8Jl/NcG7Y7u7ntUQzsaNwshzBxxcvqLM70 2wNg==
X-Received: by 10.50.17.131 with SMTP id o3mr1094652igd.112.1361972269275; Wed, 27 Feb 2013 05:37:49 -0800 (PST)
Received: from [192.168.100.33] ([67.224.83.162]) by mx.google.com with ESMTPS id gy3sm2192543igc.10.2013.02.27.05.37.45 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 27 Feb 2013 05:37:48 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.10.0.110310
Date: Wed, 27 Feb 2013 08:37:44 -0500
Subject: Re: Time zones in IETF agenda
From: Victor Kuarsingh <victor.kuarsingh@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Brian Trammell <trammell@tik.ee.ethz.ch>
Message-ID: <CD537587.40BC4%victor.kuarsingh@gmail.com>
Thread-Topic: Time zones in IETF agenda
In-Reply-To: <512DD798.7060303@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 13:37:50 -0000

On 2013-02-27 4:53 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

>On 27/02/2013 09:28, Brian Trammell wrote:
>> On Feb 27, 2013, at 10:20 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
>> 
>>> On 26 Feb 2013, at 20:28, Martin Rex <mrex@sap.com> wrote:
>>>
>>>> I have a recurring remote participation problem with the
>>>> IETF Meeting Agendas, because it specifies the time of WG meeting
>>>>slots
>>>> in local time (local to the IETF Meeting), but does not give the
>>>> local time zone *anywhere*.
>>>>
>>>> I would appreciate if the local time zone indication would be added
>>>> like somewhere at the top of the page, to each IETF meeting agenda.
>>> So in this interesting discussion of UTC, Martin has actually made an
>>>excellent point.  Having UTC listings for the agenda would be very
>>>helpful, or an alternative agenda showing UTC.
>> 
>> +1. Given our high remote participation, I put UTC in the agenda for
>>the MILE WG anyway (usually correctly, even). And given that the IETF
>>often meets on one side or another of the DST change in local time,
>>having an unchanging time reference would be helpful even for attendees.
>
>UTC time *and* date please, for people in whichever hemisphere happens to
>be
>opposite the IETF.
>
>   Brian

+1.  UTC (in addition to whatever local time based on venue) is the
clearest way of specifying a time.  It's easily converted into other time
zones by those who need to do so.

Regards,

Victor K


>



From lear@cisco.com  Wed Feb 27 06:00:23 2013
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D91621F8611 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.593
X-Spam-Level: 
X-Spam-Status: No, score=-110.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 c-hAxojMnkNn for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:00:22 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 47D0C21F85E7 for <ietf@ietf.org>; Wed, 27 Feb 2013 06:00:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=661; q=dns/txt; s=iport; t=1361973622; x=1363183222; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=QZSlgbtYdYdg/N4ek726RBMkVS5HwrdF9nIrqcN7fAc=; b=l5A5w8eoANzzcJ+elZBiV5v4AtkpDbdpZCGKObISTpjlmvFEM7jrSadk xojSc4cIDiOKAzm57D+1VNhUw0Ai6sd/IG405HGTXYR/rT41xDx/A637b Ki+/me8LC06gCtQT8VqCp4Nf1rojM9JJ8MVwXg4La4MZ095C5feu8Z0A/ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkEFAGUQLlGQ/khR/2dsb2JhbABFhghHu0Z3FnOCHwEBAQQjDwFFARALGAICBRYLAgIJAwIBAgFFEwEHAQGIDwysE5I0BIEjjXEHFoIXgRMDlkGQaoMJ
X-IronPort-AV: E=Sophos;i="4.84,747,1355097600"; d="scan'208";a="80757962"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 27 Feb 2013 14:00:21 +0000
Received: from dhcp-10-55-80-140.cisco.com (dhcp-10-55-80-140.cisco.com [10.55.80.140]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1RE0KxF018068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 27 Feb 2013 14:00:21 GMT
Message-ID: <512E1174.8000408@cisco.com>
Date: Wed, 27 Feb 2013 15:00:20 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
In-Reply-To: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 14:00:23 -0000

On 2/26/13 9:28 PM, Martin Rex wrote:
> I have a recurring remote participation problem with the
> IETF Meeting Agendas, because it specifies the time of WG meeting slots
> in local time (local to the IETF Meeting), but does not give the
> local time zone *anywhere*.
>

Except for the ICS files that are generated by the agenda tool
(https://datatracker.ietf.org/meeting/86/agenda.html).  If you take the
URL that is generated after you select the sessions you are interested
in, you can import a series of EVENTs complete with VTIMEZONEs into any
modern calendar program (e.g., Outlook, iCalendar) and the Right ThingÂ®
will happen.

Eliot


From rlb@ipv.sx  Wed Feb 27 06:03:07 2013
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C868E21F8611 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.739
X-Spam-Level: 
X-Spam-Status: No, score=-2.739 tagged_above=-999 required=5 tests=[AWL=0.237,  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 cJAiK41-YwHY for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:03:03 -0800 (PST)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id D47AC21F861B for <ietf@ietf.org>; Wed, 27 Feb 2013 06:03:02 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id h1so1179316oag.3 for <ietf@ietf.org>; Wed, 27 Feb 2013 06:03:02 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=+S6WAXZxoI3REmE2mAfL46nAHirqxQobycsE9Ibnw6c=; b=LR0UP4pkQ92KneDsGb3+bAQbwBlPAVj19oBp17cJMMA+qD3fnU7CI/eR/b7FsHjbhR THnt6GrkiQNWHQIgeaIwy8dzv+njv8RL2Lr6MssxhyDQ/XtF2WVhb99zexGFdg6fp7ea KxRq0hlUXSb6JKOpoj5ol9rCFi7rM20kMyMugSCQ6cMCoPBorIdBbLr6Ypxx39Q5HNjh QJd5sc06pDNYhuDoFnPzxdpkV+SAQbwlmBN8+wsaXvzwpjpZmCoso8XG0JBzrbXNsQkY l+LcsOoZcdthWT1PEToFql4b7uY46TY5wptFaAW/5OsvZ5TjZD1tIvK92W0XQ2p1ELwf 7NkA==
MIME-Version: 1.0
X-Received: by 10.182.202.73 with SMTP id kg9mr2100983obc.95.1361973782421; Wed, 27 Feb 2013 06:03:02 -0800 (PST)
Received: by 10.60.60.98 with HTTP; Wed, 27 Feb 2013 06:03:02 -0800 (PST)
X-Originating-IP: [192.1.51.63]
In-Reply-To: <CD537587.40BC4%victor.kuarsingh@gmail.com>
References: <512DD798.7060303@gmail.com> <CD537587.40BC4%victor.kuarsingh@gmail.com>
Date: Wed, 27 Feb 2013 09:03:02 -0500
Message-ID: <CAL02cgTrfJMbNTRYDURkyy45_OMVPG0Up0hyW1mibuKpk4HSGA@mail.gmail.com>
Subject: Re: Time zones in IETF agenda
From: Richard Barnes <rlb@ipv.sx>
To: Victor Kuarsingh <victor.kuarsingh@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f6436fc7ebcce04d6b53b22
X-Gm-Message-State: ALoCoQm5OcAqNnI+AFgcpUJRs2ZHXxMFekV+L6CMcm86oZXw5z8hsPXJQOu20sjq/JGhQ8Z0NSP+
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 14:03:07 -0000

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

<http://www.worldtimebuddy.com/>



On Wed, Feb 27, 2013 at 8:37 AM, Victor Kuarsingh <
victor.kuarsingh@gmail.com> wrote:

>
>
> On 2013-02-27 4:53 AM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>
> >On 27/02/2013 09:28, Brian Trammell wrote:
> >> On Feb 27, 2013, at 10:20 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:
> >>
> >>> On 26 Feb 2013, at 20:28, Martin Rex <mrex@sap.com> wrote:
> >>>
> >>>> I have a recurring remote participation problem with the
> >>>> IETF Meeting Agendas, because it specifies the time of WG meeting
> >>>>slots
> >>>> in local time (local to the IETF Meeting), but does not give the
> >>>> local time zone *anywhere*.
> >>>>
> >>>> I would appreciate if the local time zone indication would be added
> >>>> like somewhere at the top of the page, to each IETF meeting agenda.
> >>> So in this interesting discussion of UTC, Martin has actually made an
> >>>excellent point.  Having UTC listings for the agenda would be very
> >>>helpful, or an alternative agenda showing UTC.
> >>
> >> +1. Given our high remote participation, I put UTC in the agenda for
> >>the MILE WG anyway (usually correctly, even). And given that the IETF
> >>often meets on one side or another of the DST change in local time,
> >>having an unchanging time reference would be helpful even for attendees.
> >
> >UTC time *and* date please, for people in whichever hemisphere happens to
> >be
> >opposite the IETF.
> >
> >   Brian
>
> +1.  UTC (in addition to whatever local time based on venue) is the
> clearest way of specifying a time.  It's easily converted into other time
> zones by those who need to do so.
>
> Regards,
>
> Victor K
>
>
> >
>
>
>

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

<div>&lt;<a href=3D"http://www.worldtimebuddy.com/">http://www.worldtimebud=
dy.com/</a>&gt;</div><div><br></div><div><br><br><div class=3D"gmail_quote"=
>On Wed, Feb 27, 2013 at 8:37 AM, Victor Kuarsingh <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:victor.kuarsingh@gmail.com" target=3D"_blank">victor.kuarsi=
ngh@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"><br>
<br>
On 2013-02-27 4:53 AM, &quot;Brian E Carpenter&quot; &lt;<a href=3D"mailto:=
brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
wrote:<br>
<div><div class=3D"h5"><br>
&gt;On 27/02/2013 09:28, Brian Trammell wrote:<br>
&gt;&gt; On Feb 27, 2013, at 10:20 AM, Tim Chown &lt;<a href=3D"mailto:tjc@=
ecs.soton.ac.uk">tjc@ecs.soton.ac.uk</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 26 Feb 2013, at 20:28, Martin Rex &lt;<a href=3D"mailto:mre=
x@sap.com">mrex@sap.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I have a recurring remote participation problem with the<b=
r>
&gt;&gt;&gt;&gt; IETF Meeting Agendas, because it specifies the time of WG =
meeting<br>
&gt;&gt;&gt;&gt;slots<br>
&gt;&gt;&gt;&gt; in local time (local to the IETF Meeting), but does not gi=
ve the<br>
&gt;&gt;&gt;&gt; local time zone *anywhere*.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I would appreciate if the local time zone indication would=
 be added<br>
&gt;&gt;&gt;&gt; like somewhere at the top of the page, to each IETF meetin=
g agenda.<br>
&gt;&gt;&gt; So in this interesting discussion of UTC, Martin has actually =
made an<br>
&gt;&gt;&gt;excellent point. =A0Having UTC listings for the agenda would be=
 very<br>
&gt;&gt;&gt;helpful, or an alternative agenda showing UTC.<br>
&gt;&gt;<br>
&gt;&gt; +1. Given our high remote participation, I put UTC in the agenda f=
or<br>
&gt;&gt;the MILE WG anyway (usually correctly, even). And given that the IE=
TF<br>
&gt;&gt;often meets on one side or another of the DST change in local time,=
<br>
&gt;&gt;having an unchanging time reference would be helpful even for atten=
dees.<br>
&gt;<br>
&gt;UTC time *and* date please, for people in whichever hemisphere happens =
to<br>
&gt;be<br>
&gt;opposite the IETF.<br>
&gt;<br>
&gt; =A0 Brian<br>
<br>
</div></div>+1. =A0UTC (in addition to whatever local time based on venue) =
is the<br>
clearest way of specifying a time. =A0It&#39;s easily converted into other =
time<br>
zones by those who need to do so.<br>
<br>
Regards,<br>
<br>
Victor K<br>
<br>
<br>
&gt;<br>
<br>
<br>
</blockquote></div><br></div>

--e89a8f6436fc7ebcce04d6b53b22--

From wesley.george@twcable.com  Wed Feb 27 06:44:18 2013
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 547FF21F861C for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:44:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.002
X-Spam-Level: 
X-Spam-Status: No, score=-1.002 tagged_above=-999 required=5 tests=[AWL=0.461,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 HGLq1I2sE+8R for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 06:44:17 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEC721F85FD for <ietf@ietf.org>; Wed, 27 Feb 2013 06:44:17 -0800 (PST)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.84,747,1355115600"; d="scan'208";a="34215560"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 27 Feb 2013 09:43:24 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Wed, 27 Feb 2013 09:44:16 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Scott Kitterman <scott@kitterman.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 27 Feb 2013 09:44:15 -0500
Subject: RE: Internet Draft Final Submission Cut-Off Today
Thread-Topic: Internet Draft Final Submission Cut-Off Today
Thread-Index: Ac4UnHN6lGw4n76kQ7mNSC/plZmyowAWq2jQ
Message-ID: <2671C6CDFBB59E47B64C10B3E0BD5923041EF8D00E@PRVPEXVS15.corp.twcable.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <512D7F07.8040308@dougbarton.us> <2367396.pqKL5uhMr8@scott-latitude-e6320>
In-Reply-To: <2367396.pqKL5uhMr8@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 14:44:18 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Scott Kitterman
> Sent: Tuesday, February 26, 2013 10:42 PM
> To: ietf@ietf.org
> Subject: Re: Internet Draft Final Submission Cut-Off Today
>
> How does that relate to working groups that aren't meeting?

[WEG] Signal to noise ratio. I (and I assume others) use the IETF's RSS fee=
d to see all new drafts when they are posted. This is in order to have a fi=
ghting chance to see drafts I might care about that happen in WGs that I am=
 not an active participant in, both to help me see if there are other WG li=
sts I need to subscribe to or if there are meetings I should attend as a "t=
ourist", or direct feedback to the authors prior to IETF LC.
New drafts posted for WGs that aren't meeting (and while I'm at it, throwaw=
ay placeholder -00 drafts with no content) help contribute to the crush of =
drafts to sift through, because it's not readily apparent based on the RSS =
summary or the draft itself whether the WG is meeting. Add me as one more +=
1 in support of a quiet period to give me a chance to catch up on draft rev=
iew before the meeting.

> It was silly I had to rush to post a draft on Monday for a WG that's not
> meeting.
>

[WEG] Yes it was silly you had to rush, because if the WG isn't meeting, th=
ere's no reason why you couldn't have simply waited until after the morator=
ium elapsed, or posted it well prior to the inevitable rush of work that pr=
ecedes every meeting.
Though alternatively it should be possible to have the system continue acce=
pting submissions and only make them public at the expiration of the postin=
g moratorium.

Wes George

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

From cyrus@daboo.name  Wed Feb 27 07:05:19 2013
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7822221F867B for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:05:19 -0800 (PST)
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 NVJJusqp2R9c for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:05:18 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id 74CBE21F85BB for <ietf@ietf.org>; Wed, 27 Feb 2013 07:05:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 10DB93E294F5; Wed, 27 Feb 2013 10:05:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oGcJNBq_HldM; Wed, 27 Feb 2013 10:05:16 -0500 (EST)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 96B313E294E8; Wed, 27 Feb 2013 10:05:15 -0500 (EST)
Date: Wed, 27 Feb 2013 10:05:12 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Tim Chown <tjc@ecs.soton.ac.uk>, "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: Time zones in IETF agenda
Message-ID: <AD1F39A78073C80213D63C32@caldav.corp.apple.com>
In-Reply-To: <EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
References: <20130226202823.DD1441A5D0@ld9781.wdf.sap.corp> <363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk> <EMEW3|299023b6ce260ff4cdb522832c522124p1Q9KC03tjc|ecs.soton.ac.uk|363913E0-FFFB-4E55-9158-AFDB2F34A98D@ecs.soton.ac.uk>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=978
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 15:05:19 -0000

Hi Tim,

--On February 27, 2013 at 9:20:09 AM +0000 Tim Chown <tjc@ecs.soton.ac.uk> 
wrote:

>> I would appreciate if the local time zone indication would be added
>> like somewhere at the top of the page, to each IETF meeting agenda.
>
> So in this interesting discussion of UTC, Martin has actually made an
> excellent point.  Having UTC listings for the agenda would be very
> helpful, or an alternative agenda showing UTC.

Do use a calendar (iCalendar) client to manage your own time? If so, the 
iCalendar "feed" of the agenda will provide everything you need in terms of 
viewing the events in whatever timezone you want.

Having an alternative text agenda in UTC still requires mental arithmetic 
to convert to one's own local time - a lot harder for those living in zones 
with a large offset, or an offset with a 1/2 hour component to it. Better 
would be an option on the webpage to allow the text-based agenda to be 
displayed in a chosen timezone.

-- 
Cyrus Daboo


From mary.ietf.barnes@gmail.com  Wed Feb 27 07:13:10 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7A8221F870E for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.578
X-Spam-Level: 
X-Spam-Status: No, score=-103.578 tagged_above=-999 required=5 tests=[AWL=0.021, 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 yKmU+A0GuEoL for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:13:10 -0800 (PST)
Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by ietfa.amsl.com (Postfix) with ESMTP id 021E821F86C2 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:13:09 -0800 (PST)
Received: by mail-qa0-f47.google.com with SMTP id j8so3403205qah.20 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:13:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=LCpQwfPqwaOLo7BIMzWsXj9V48lcIlNeARcNbQnshZ4=; b=S4e+p0i60O8NNgLFNYEprRr3EQOFMszAL4ESG0YN5wAOkDzfnCFmnea6XtjcQinhR+ 1tBhTwn7nLUAdn1UscIJR19tzD7/xmW+CWNPbeBf4Jg9VkHOy/VeStVvUpgzj8xI/XIY C9mz6Dp7kNkQIkhV4JtuqsMWa87pFFbZaNmi8vQUIX0BBWFjooL5ur14Jt5b7d/VSl6G RufeLbXMqkz2NhLIxfj1CfihUCFhpMh4fY5nlqg7IBs72bXzgsA3VL+KFu8pUlqvp00K siN1opZ6GkJ3+5eXdB8uTnmzqsDL58uc8OOh/JjdgZ5ISmks388DSA6S0EOp+7rBrtsD x2cA==
MIME-Version: 1.0
X-Received: by 10.224.27.136 with SMTP id i8mr8454847qac.63.1361977989378; Wed, 27 Feb 2013 07:13:09 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Wed, 27 Feb 2013 07:13:09 -0800 (PST)
In-Reply-To: <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <037c01ce1472$ffe26f20$ffa74d60$@packetizer.com> <512D3C4B.3040007@gmail.com> <CAP+FsNdQoo3k8a-VdLOAaYJO7F23UYKQdQ4PRL=4z64oeSby8w@mail.gmail.com> <EDFCCD44-F7D3-4277-9748-E212E1490646@kumari.net>
Date: Wed, 27 Feb 2013 09:13:09 -0600
Message-ID: <CAHBDyN6uVCwJSKANKq8ar47azoWKPQxi3Zb2VthROcD+ceAsrQ@mail.gmail.com>
Subject: Re: [IETF] Re: Internet Draft Final Submission Cut-Off Today
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 15:13:10 -0000

On Tue, Feb 26, 2013 at 4:59 PM, Warren Kumari <warren@kumari.net> wrote:
>
> On Feb 26, 2013, at 5:54 PM, Roberto Peon <grmocg@gmail.com> wrote:
>
>> I'm not sure that the deadline serves any positive purpose so long as we=
 keep all of the versions anyway.
>> It certainly is annoying the way it is now and is disruptive to the deve=
lopment process rather than helpful for it.
>
> Um, maybe.
>
> Another way to look at it is that a deadline, any deadline, helps stop fo=
lk procrastinating and actually *submit*.
>
> Have a look at the number of submissions just before the cutoffs=85
[MB] I agree.  The deadline is what pushes the vast majority to get
work done.  WG chairs to have discretion and they can ask the
secretariat to post something after the deadline.  I believe that's
more than sufficient.  As Melinda noted in another email work should
happen on the mailing list.  If the documents aren't out earlier, then
there is no time to discuss on the mailing list.  Without mailing list
discussion or folks even having read drafts, the WG time is not nearly
as effective  in my experience and I honestly think that's one reason
it takes IETF so *many* cycles to get work done.

In the RAI area, we've had a process in place that has earlier
deadlines that REQUIRE wg discussion or the documents do NOT get
agenda time.  That has proven fairly effective  We have made the
deadlines less restrictive over the past year and we seem to have
reached a good steady state in the process. If anyone wants to debate
the merits of that process, please do so on the RAI area list as we
are always looking to improve. The nature of this WG is different, of
course.  For the other WG I chair,  the group has been pretty good
about getting documents updated outside the deadlines.  But, that's
because we have regularly design team meetings that introduce
deadlines for work to get out for mailing list discussion, which gets
back to the basic fact that many procrastinate or get distracted with
other things and unless there's a deadline, the work will not get done
in a timely manner. [/MB]
>
> W
>
>>
>> -=3DR
>>
>>
>> On Tue, Feb 26, 2013 at 2:50 PM, Melinda Shore <melinda.shore@gmail.com>=
 wrote:
>> On 2/26/13 1:45 PM, Paul E. Jones wrote:
>> > On the one hand, having a cut-off time could help WG chairs make a dec=
ision
>> > as to whether to entertain a discussion on a draft.  On the other hand=
,
>> > having no cut-off date might mean that drafts are submitted extremely =
late
>> > and it makes it more challenging or impossible to prepare an agenda.
>>
>> Well, for one thing the IETF does its work on mailing lists, and
>> meetings support that rather than the other way 'round.  For another,
>> I'm not sure this deadline makes any difference in practice (other
>> than introducing an inconvenience).  We're going to be giving meeting
>> time to a draft for which there's no revision, because it needs
>> meeting time.  It's on the agenda whether there's a revision or
>> not.  I understand the deadline was introduced to provide incentives
>> for people to get their stuff in in advance of a meeting.  But.
>>
>> Melinda
>>
>>
>
> --
> I had no shoes and wept.  Then I met a man who had no feet.  So I said, "=
Hey man, got any shoes you're not using?"
>
>

From mary.ietf.barnes@gmail.com  Wed Feb 27 07:18:01 2013
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927BB21F870E for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.579
X-Spam-Level: 
X-Spam-Status: No, score=-103.579 tagged_above=-999 required=5 tests=[AWL=0.020, 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 XzNJqzegRhAg for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:18:00 -0800 (PST)
Received: from mail-qe0-f50.google.com (mail-qe0-f50.google.com [209.85.128.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8B22E21F86C2 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:18:00 -0800 (PST)
Received: by mail-qe0-f50.google.com with SMTP id w7so522543qeb.9 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:18:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=9CuMe+hlmtF4SGxnHRygy36UgIFrWXJpX/jg/O1NnuI=; b=OAhbJ6PpJViCQhhTSHUbUCLfUMJj6t0HHaWnuVozSj++IfVsijibA+yWdvcNIHyLvM wvecVS0tQ7EkTREUeXrEWBBLwc4cQx1UWXW4p3FgkdSKecO8eD9Z3GLsRZafMqMRVsZO ZAzjdH71iiLVNVatXdB8BTHLL/mQ7MzChVwn6dfzh3TNInR7tZSUs8VLOsuQvedOe1u4 ADs1zunLfMILlf6qoOM2c7ZEXLuF3IVeb2KiEoD24GhBnQi2tt2j7hFeRkMTZJqTx1Gl H0zlTrH+NoxiyPQfyOcAlebsepYhkwt0qtjbR5vtBkIAiMmi4yRfVsc+uyBkHGBA8Cjm ljQA==
MIME-Version: 1.0
X-Received: by 10.224.216.65 with SMTP id hh1mr8165780qab.43.1361978280054; Wed, 27 Feb 2013 07:18:00 -0800 (PST)
Received: by 10.49.24.130 with HTTP; Wed, 27 Feb 2013 07:17:59 -0800 (PST)
In-Reply-To: <2367396.pqKL5uhMr8@scott-latitude-e6320>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <512D7F07.8040308@dougbarton.us> <2367396.pqKL5uhMr8@scott-latitude-e6320>
Date: Wed, 27 Feb 2013 09:17:59 -0600
Message-ID: <CAHBDyN61YoQ0k09_DpaYiEQ50EAjNvzEXQ9pY+GcGOx-J0bjMw@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Scott Kitterman <scott@kitterman.com>
Content-Type: text/plain; charset=ISO-8859-1
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, 27 Feb 2013 15:18:01 -0000

You have two choices with the current model:
1) If the document is critical for WG progress, then talk to your WG
chairs and see if they are willing to contact the secretariat to let
the document through.  You do need a very compelling reason to do
this, so it shouldn't be done as a rule.
2) Submit the document the Monday of the meeting week when the
submission process is re-opened.

If one looks at the volume of documents that many need to read before
meetings, if everyone waited until the few days before the meetings to
submit, then our meetings would be even less effective.  How many
could read all the pages of the WG documents that they are interested
in a few days?  I don't recall the number right off, but in the past
someone created a file with all the RAI area drafts - it was a crazy
number and even for a two week period, it was humanly impossible to
read all the drafts unless you speed read (and miss information) and
are reading 24 hrs/day.

Regards,
Mary.

On Tue, Feb 26, 2013 at 9:41 PM, Scott Kitterman <scott@kitterman.com> wrote:
> On Tuesday, February 26, 2013 07:35:35 PM Doug Barton wrote:
>> On 02/26/2013 02:49 PM, Margaret Wasserman wrote:
>> > On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com>
> wrote:
>> >> But more seriously: I agree with you both. The deadline is silly.
>> >
>> > +1
>> >
>> > The deadline originated because the secretariat needed time to post all of
>> > those drafts (by hand) before the meeting.  The notion of an automated
>> > tool that blocks submissions for two weeks before the meeting is just
>> > silly.
>> -1
>>
>> There are a non-trivial number of people who are intensely busy in the
>> weeks leading up to a meeting, with a high degree of overlap with the
>> set of people we want to be able to actually read the drafts prior to
>> the face to face meeting of the WG. The same argument applies, although
>> to a somewhat lesser extent, to being able to post for groups that are
>> not meeting.
>>
>> Is a few weeks where people cannot post what they want, when they want
>> to; in order for the larger populace of the IETF to be able to focus on
>> the activity in and around the meeting REALLY that much of a burden?
>
> How does that relate to working groups that aren't meeting?  It was silly I
> had to rush to post a draft on Monday for a WG that's not meeting.
>
> Scott K

From melinda.shore@gmail.com  Wed Feb 27 07:55:59 2013
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BD921F8519 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:55:59 -0800 (PST)
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 ZWxtxfMfM2mo for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 07:55:59 -0800 (PST)
Received: from mail-pb0-f52.google.com (mail-pb0-f52.google.com [209.85.160.52]) by ietfa.amsl.com (Postfix) with ESMTP id 42B6C21F8498 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:55:59 -0800 (PST)
Received: by mail-pb0-f52.google.com with SMTP id ma3so440691pbc.39 for <ietf@ietf.org>; Wed, 27 Feb 2013 07:55:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=t1mfLOprm9hjw5dOK4llJAz7daNL/SazW6XhBr/i+zU=; b=HLtbZYMDxpqk3DoWu77rtKF0z+HlAfZtXg4rdY2iHxufABYojKtQhKFFBfu+77kdrp iCceUmmE890FsxzS5iJ8WjRsAcGXIo5R6o11DPBssGd7aYa0qeFwPjNumQbJywkRpeaX o6VJOODpfksD16LE/pJk3Rp3CqF8tyLlh+ARyl376Jpnrv71jUXwLMzumpGdE144zGLu GlJyfo8p+eC9qUZaXOam0P2iQjMmBQnmUV+jwQWHV/vFujo+cyvtNm3zYfbY6RQpel4k kObYYfQBKrVqroLFhrY7OZVVFLCbxeovLyQuCxOutLfz2KOFXVvvWQG2GGO0HG+3/YfY QR7Q==
X-Received: by 10.67.3.65 with SMTP id bu1mr8276621pad.150.1361980559022; Wed, 27 Feb 2013 07:55:59 -0800 (PST)
Received: from spandex.local (216-67-46-104-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.46.104]) by mx.google.com with ESMTPS id qb10sm5038714pbb.43.2013.02.27.07.55.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 27 Feb 2013 07:55:58 -0800 (PST)
Message-ID: <512E2C8B.8070306@gmail.com>
Date: Wed, 27 Feb 2013 06:55:55 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu> <512DC965.1040606@gmail.com>
In-Reply-To: <512DC965.1040606@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 15:55:59 -0000

On 2/26/13 11:52 PM, Glen Zorn wrote:
> I believe that it's actually Yiddish.

It is.  It may or may not be German, as well.  Don't know.

Melinda



From scott@kitterman.com  Wed Feb 27 09:25:41 2013
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9388021F85F3 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 09:25:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h+cq9AQHEq4B for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 09:25:40 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 8203A21F8523 for <ietf@ietf.org>; Wed, 27 Feb 2013 09:25:40 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id ABA2420E4113; Wed, 27 Feb 2013 12:25:39 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1361985939; bh=d7Ysu99pBsh+q6cKVHkHCvEVZF/7mULOdy2AGQoU2ug=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FnSq1ZzEU1rW2QuyHD5HYTKg1IyKyflCcvw5GNholVRtV+CyjlqCYBQWRedw0iKl2 1dKifTjBtszJTPJP8UY7M5vONyPGngOI8gVW+Nk+kJDsoSwZyPRMOEbgqI+T7uAdiW rlVzv7tkgEhvbZolEhHG1618OOXFVQ09VluBiQtA=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 92F1520E4081;  Wed, 27 Feb 2013 12:25:39 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Internet Draft Final Submission Cut-Off Today
Date: Wed, 27 Feb 2013 12:25:38 -0500
Message-ID: <3563049.M2nv1ex2jF@scott-latitude-e6320>
User-Agent: KMail/4.9.5 (Linux/3.5.0-25-generic; KDE/4.9.5; i686; ; )
In-Reply-To: <2671C6CDFBB59E47B64C10B3E0BD5923041EF8D00E@PRVPEXVS15.corp.twcable.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <2367396.pqKL5uhMr8@scott-latitude-e6320> <2671C6CDFBB59E47B64C10B3E0BD5923041EF8D00E@PRVPEXVS15.corp.twcable.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 17:25:41 -0000

On Wednesday, February 27, 2013 09:44:15 AM George, Wes wrote:
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Scott Kitterman
> > Sent: Tuesday, February 26, 2013 10:42 PM
> > To: ietf@ietf.org
> > Subject: Re: Internet Draft Final Submission Cut-Off Today
> > 
> > How does that relate to working groups that aren't meeting?
> 
> [WEG] Signal to noise ratio. I (and I assume others) use the IETF's RSS feed
> to see all new drafts when they are posted. This is in order to have a
> fighting chance to see drafts I might care about that happen in WGs that I
> am not an active participant in, both to help me see if there are other WG
> lists I need to subscribe to or if there are meetings I should attend as a
> "tourist", or direct feedback to the authors prior to IETF LC. New drafts
> posted for WGs that aren't meeting (and while I'm at it, throwaway
> placeholder -00 drafts with no content) help contribute to the crush of
> drafts to sift through, because it's not readily apparent based on the RSS
> summary or the draft itself whether the WG is meeting. Add me as one more
> +1 in support of a quiet period to give me a chance to catch up on draft
> review before the meeting.

If you want a quiet period, stop looking at the feed.  If, as I' and others 
have suggested, submissions are still blocked for WG that are meeting, then 
anything in the feed after the cutoff is unrelated to your meeting 
preparations. 

> > It was silly I had to rush to post a draft on Monday for a WG that's not
> > meeting.
> 
> [WEG] Yes it was silly you had to rush, because if the WG isn't meeting,
> there's no reason why you couldn't have simply waited until after the
> moratorium elapsed, or posted it well prior to the inevitable rush of work
> that precedes every meeting. Though alternatively it should be possible to
> have the system continue accepting submissions and only make them public at
> the expiration of the posting moratorium.

It was rush in the sense that I'd have preferred to wait another day or two 
for feedback on a few points.  It wasn't a rush job in the sense of rushing to 
prepare a draft.  As it is, we have a good (IME anyway) draft that resolves a 
number of issues and is a solid foundation for moving on to address our 
remaining issues.  Waiting to post it would have only slowed the progress of 
the WG.  There are natural places in the work of a WG to post an updated 
draft.  For WG that aren't meeting, IETF meeting draft cut offs should not 
affect that.  It's not like the list of WG that are meeting aren't known well 
in advance of the cut off.

Scott K

From henrik@levkowetz.com  Wed Feb 27 10:04:10 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBFE21F8890 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Wghu0SHpHe3 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:04:09 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 6155721F8667 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:04:09 -0800 (PST)
Received: from [2a01:3f0:1:0:4c4e:bad7:4c4f:8fe8] (port=62532 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UAlMJ-0004Ii-BI; Wed, 27 Feb 2013 19:04:03 +0100
Message-ID: <512E4A93.5010904@levkowetz.com>
Date: Wed, 27 Feb 2013 19:04:03 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com>
In-Reply-To: <512D37B0.7010108@gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4c4e:bad7:4c4f:8fe8
X-SA-Exim-Rcpt-To: melinda.shore@gmail.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Internet Draft Final Submission Cut-Off Today
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.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, 27 Feb 2013 18:04:10 -0000

Hi Melinda,

On 2013-02-26 23:31 Melinda Shore said:
> On 2/26/13 1:25 PM, Paul E. Jones wrote:
>> Seriously, what the heck is 24:00?  
> 
> That one is weird, no doubt about it, but ultimately
> it's 23:59 + 1 minute, which is clear.  But I really
> think "24:00" is confusing. 0:00 is clearer.  I'm
> wondering if they're trying to work around some ferkakte
> piece of software.

No, it's just trying to provide a time indication that people
will easily interpret correctly.  Trying out the correct
notation (using 00:00 and the following date) on people
during informal testing, I found that people were much more
prone to interpret that as the deadline being 24 hours later
than was intended.

I can of course make it 23:59 to be both correct and easily
read, if the powers-that-be will permit a one-second shift in
actual deadline time.


Best regards,

	Henrik


From mohta@necom830.hpcl.titech.ac.jp  Wed Feb 27 10:21:19 2013
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 B87C321F8947 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:21:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.59
X-Spam-Level: 
X-Spam-Status: No, score=-0.59 tagged_above=-999 required=5 tests=[AWL=-0.500,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEIdzlyNEVzP for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:21:17 -0800 (PST)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id C09AF21F8942 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:21:16 -0800 (PST)
Received: (qmail 55479 invoked from network); 27 Feb 2013 18:19:33 -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; 27 Feb 2013 18:19:33 -0000
Message-ID: <512E4E5B.1050508@necom830.hpcl.titech.ac.jp>
Date: Thu, 28 Feb 2013 03:20:11 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <alpine.LSU.2.00.1302271215580.27013@hermes-1.csi.cam.ac.uk> <512E0297.6070708@necom830.hpcl.titech.ac.jp> <alpine.LSU.2.00.1302271326330.27013@hermes-1.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1302271326330.27013@hermes-1.csi.cam.ac.uk>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 18:21:19 -0000

Tony Finch wrote:

>> The IS should clarify that a day is [0:0, 24:0), not [0:0, 24:0]
>> and everything should be fine.
> 
> Its definition of a calendar day is consistent with its definition of a
> time interval. It doesn't make any distinction between including and
> excluding the end instants. And I don't think it would be sensible to do
> so: it would clutter the time interval notation with no clear benefit.

In Japan, at the beginning of 2004, copyright protection period
of movies, copyright of which were unexpired at that time, was
extended by 20 years.

But, copyright of some movies expired at the end of 2003.

There were disputes in courts and the supreme court judged
that copyright of the movies expired.

						Masataka Ohta


From ned+ietf@mauve.mrochek.com  Wed Feb 27 10:29:18 2013
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 7A8A921F8862 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PKAkkCbnatR8 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:29:18 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 39C7121F8860 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:29:11 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OQON8RNH4W000J81@mauve.mrochek.com> for ietf@ietf.org; Wed, 27 Feb 2013 10:24:09 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OQH0ICCQ1C000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 27 Feb 2013 10:24:07 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OQON8Q439C000054@mauve.mrochek.com>
Date: Wed, 27 Feb 2013 10:18:07 -0800 (PST)
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-reply-to: "Your message dated Tue, 26 Feb 2013 17:49:11 -0500" <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
To: Margaret Wasserman <mrw@lilacglade.org>
Cc: Pete Resnick <presnick@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: Wed, 27 Feb 2013 18:29:18 -0000

> On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:

> > But more seriously: I agree with you both. The deadline is silly.

> +1

+1

> The deadline originated because the secretariat needed time to post all of those drafts (by hand) before the meeting.  The notion of an automated tool that blocks submissions for two weeks before the meeting is just silly.

All the more so since it just leads people to use informal distribution
methods. I don't recall a case where a chair forbid the discussion of a draft
distributed this way.

I recall hearing something once about routing around obstacles... Pity we don't
internalize such principles fully.

				Ned

From grmocg@gmail.com  Wed Feb 27 10:49:09 2013
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 9204021F88B0 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.942
X-Spam-Level: 
X-Spam-Status: No, score=-6.942 tagged_above=-999 required=5 tests=[AWL=-3.344, 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 ppNYerfZBy7X for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:49:08 -0800 (PST)
Received: from mail-oa0-f53.google.com (mail-oa0-f53.google.com [209.85.219.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7F721F8887 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:49:08 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id m1so1888770oag.26 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:49:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=2TW189cpgH3pxVP51XHsZMqRRISiIke79XYFKJWIoOs=; b=bAWz/vziy7jAuzpUDY6bj7sfXrY5Y9gRczLPou9dKUi21DyA+/xbVpH33Ybg3A9Con Vb4HryoEhs8EtqzgNu7yxGDZcFo77JvNoAQumtqmbf/6xXStufq2rLfiuLYqrlscTZV/ 2m+/fv2Rwx/zmtB02n17eokv0aMY/4ayySe+IQKBaTreUZKzan24wyPRAhvg8PQL22Rb 2zftgoh2eMeC8pBC3l2JPqhbCWeHB9mZgNhe+iZl993sRvFM5HCH/e5Qg4vq/D/rHgWc 1bTZv++r89Kqe168RbMoIIjuG969yEBPiSAgdJZm57ChvdqlMW5eSFYQBBF2SBywplGY 7Qtw==
MIME-Version: 1.0
X-Received: by 10.60.9.1 with SMTP id v1mr3129295oea.130.1361990948155; Wed, 27 Feb 2013 10:49:08 -0800 (PST)
Received: by 10.76.109.72 with HTTP; Wed, 27 Feb 2013 10:49:08 -0800 (PST)
In-Reply-To: <01OQON8Q439C000054@mauve.mrochek.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <01OQON8Q439C000054@mauve.mrochek.com>
Date: Wed, 27 Feb 2013 10:49:08 -0800
Message-ID: <CAP+FsNcFqYA_YNriG95YEuko0-dV9U3LSgZWW=CPT+TsQGi1bw@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
From: Roberto Peon <grmocg@gmail.com>
To: ned+ietf@mauve.mrochek.com
Content-Type: multipart/alternative; boundary=e89a8fb20318a6faf304d6b93ad9
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 18:49:09 -0000

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

+1

In any case, the proposal as I understood it was that the deadline *would*
apply to drafts which the secretariat had to examine, just not the rest.
 I certainly don't agree with giving an unsupportable load to our
secretariat before the meetings (and it isn't being proposed by me :) )

-=R


On Wed, Feb 27, 2013 at 10:18 AM, <ned+ietf@mauve.mrochek.com> wrote:

>
> > On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com>
> wrote:
>
> > > But more seriously: I agree with you both. The deadline is silly.
>
> > +1
>
> +1
>
> > The deadline originated because the secretariat needed time to post all
> of those drafts (by hand) before the meeting.  The notion of an automated
> tool that blocks submissions for two weeks before the meeting is just silly.
>
> All the more so since it just leads people to use informal distribution
> methods. I don't recall a case where a chair forbid the discussion of a
> draft
> distributed this way.
>
> I recall hearing something once about routing around obstacles... Pity we
> don't
> internalize such principles fully.
>
>                                 Ned
>

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

<div dir=3D"ltr">+1<div><br></div><div style>In any case, the proposal as I=
 understood it was that the deadline *would* apply to drafts which the secr=
etariat had to examine, just not the rest.</div><div style>=A0I certainly d=
on&#39;t agree with giving an unsupportable load to our secretariat before =
the meetings (and it isn&#39;t being proposed by me :) )</div>
<div style><br></div><div style>-=3DR</div></div><div class=3D"gmail_extra"=
><br><br><div class=3D"gmail_quote">On Wed, Feb 27, 2013 at 10:18 AM,  <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_=
blank">ned+ietf@mauve.mrochek.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"HOEnZb"><div class=3D"h5"><br>
&gt; On Feb 26, 2013, at 5:38 PM, Pete Resnick &lt;<a href=3D"mailto:presni=
ck@qti.qualcomm.com">presnick@qti.qualcomm.com</a>&gt; wrote:<br>
<br>
&gt; &gt; But more seriously: I agree with you both. The deadline is silly.=
<br>
<br>
&gt; +1<br>
<br>
+1<br>
<br>
&gt; The deadline originated because the secretariat needed time to post al=
l of those drafts (by hand) before the meeting. =A0The notion of an automat=
ed tool that blocks submissions for two weeks before the meeting is just si=
lly.<br>

<br>
</div></div>All the more so since it just leads people to use informal dist=
ribution<br>
methods. I don&#39;t recall a case where a chair forbid the discussion of a=
 draft<br>
distributed this way.<br>
<br>
I recall hearing something once about routing around obstacles... Pity we d=
on&#39;t<br>
internalize such principles fully.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned<br>
</blockquote></div><br></div>

--e89a8fb20318a6faf304d6b93ad9--

From cabo@tzi.org  Wed Feb 27 10:49:55 2013
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D006C21F8A27 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.164
X-Spam-Level: 
X-Spam-Status: No, score=-106.164 tagged_above=-999 required=5 tests=[AWL=0.085, 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 s8wkFkvoGixR for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:49:55 -0800 (PST)
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 A78EC21F88B0 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:49:54 -0800 (PST)
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 r1RInlKS024215; Wed, 27 Feb 2013 19:49:47 +0100 (CET)
Received: from [10.0.1.4] (reingewinn.informatik.uni-bremen.de [134.102.218.123]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 537C0378D; Wed, 27 Feb 2013 19:49:47 +0100 (CET)
Subject: Re: Internet Draft Final Submission Cut-Off Today
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: <01OQON8Q439C000054@mauve.mrochek.com>
Date: Wed, 27 Feb 2013 19:49:46 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0246891A-DD8F-4A7D-8880-BE95FA7B2365@tzi.org>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <01OQON8Q439C000054@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 18:49:55 -0000

On Feb 27, 2013, at 19:18, ned+ietf@mauve.mrochek.com wrote:

> routing around obstacles

It turns out for most people the easiest route around is submitting in =
time.

That is actually what counts here: how does the rule influence the =
behavior of people.

Chair hat: WORKSFORME.  (And, if I could decide it, WONTFIX.)

Gr=FC=DFe, Carsten


From moore@network-heretics.com  Wed Feb 27 10:57:51 2013
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C9CD21F89CC for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.457
X-Spam-Level: 
X-Spam-Status: No, score=-3.457 tagged_above=-999 required=5 tests=[AWL=0.142,  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 nyrKsvX4ekkA for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 10:57:50 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by ietfa.amsl.com (Postfix) with ESMTP id A27E421F8996 for <ietf@ietf.org>; Wed, 27 Feb 2013 10:57:50 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 0F0EB21056 for <ietf@ietf.org>; Wed, 27 Feb 2013 13:57:50 -0500 (EST)
Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 27 Feb 2013 13:57:50 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=BwiNNMw+xfGOd9YtSwOIgG 5nbdo=; b=BI5kZCPKk13gxpjHTOn61uAOdHkPUDLVRAEAnmxoR3YDR9jnsIba4P JOKLCn+ftGupo0rSnQ7YFEYmWWfMI52lD0xKeoKdtYKZsdIWrHKnCJmPBnH68dkK Zk1UIESJvV/uJ5be6/64qT9FKKUv0Gq8se4ECi1HbxNWZPNR/rxSI=
X-Sasl-enc: yq4yT3iERpG8VnYxskDNGGKC37PPpsN4FfX3wqQU75Dx 1361991469
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 6B145C80E93; Wed, 27 Feb 2013 13:57:49 -0500 (EST)
Message-ID: <512E5729.7090005@network-heretics.com>
Date: Wed, 27 Feb 2013 13:57:45 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <01OQON8Q439C000054@mauve.mrochek.com> <0246891A-DD8F-4A7D-8880-BE95FA7B2365@tzi.org>
In-Reply-To: <0246891A-DD8F-4A7D-8880-BE95FA7B2365@tzi.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: Wed, 27 Feb 2013 18:57:51 -0000

On 02/27/2013 01:49 PM, Carsten Bormann wrote:
> On Feb 27, 2013, at 19:18, ned+ietf@mauve.mrochek.com wrote:
>
>> routing around obstacles
> It turns out for most people the easiest route around is submitting in time.
>
> That is actually what counts here: how does the rule influence the behavior of people.
>
> Chair hat: WORKSFORME.  (And, if I could decide it, WONTFIX.)
+1.

As far as I can tell, the deadline actually serves the purpose of 
getting people to focus on IETF and update their documents sufficiently 
prior to the meeting, that it's reasonable to expect meeting 
participants to read the drafts that they intend to discuss.   And I say 
this as someone who, as an author, has often found the deadline to be 
very inconvenient.

Keith


From rwfranks@gmail.com  Wed Feb 27 11:16:27 2013
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 C19EF21F8AAC for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:16:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.378
X-Spam-Level: 
X-Spam-Status: No, score=-101.378 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_14=0.6, 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 s6a9ABN6BqgB for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:16:27 -0800 (PST)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF5E21F8ABA for <ietf@ietf.org>; Wed, 27 Feb 2013 11:16:27 -0800 (PST)
Received: by mail-ie0-f170.google.com with SMTP id c11so1066526ieb.15 for <ietf@ietf.org>; Wed, 27 Feb 2013 11:16:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=CywVtxGo+1g/TNfvYKvYlzG9gTHpjDythvSzMbpp77o=; b=WpN5rbglLut/g7pVRPPRT2N3BDoly9l8MteWtHEo74qBB2SXlLykeRRwg/uxkNfCND exPb9DNoVGwqzWjtNQzuCOKq3H9XyojZMBEN0JF3yM/KGDqPrEtzH5NGl4vgVKsY9O/a n4xxIh8qYtzU0sA7l+hH6zhydgcKjX9USYntjA+io6p+u3Q7Wo+THmdLMrOmNOIS3/f+ oybYxUhZAR60fX/o1gIcPOwm3CIWUw8DR37vf3OzckL1kmWPjA4NzaqwG6df3sVnWER6 7K2Z/HFdIAVQyJV/LyTMSnuhM8HMyWNGaSJyGMcnAUz5+i2zBb4HUCayajOFdbHaqNjP phaw==
X-Received: by 10.50.100.201 with SMTP id fa9mr7675656igb.28.1361992586880; Wed, 27 Feb 2013 11:16:26 -0800 (PST)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.64.70.170 with HTTP; Wed, 27 Feb 2013 11:16:05 -0800 (PST)
In-Reply-To: <512DC7E3.8080501@restena.lu>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu>
From: Dick Franks <rwfranks@acm.org>
Date: Wed, 27 Feb 2013 19:16:05 +0000
X-Google-Sender-Auth: E5t5zeLx5Jz3Zfvr8WR7h7D3X2E
Message-ID: <CAKW6Ri5k+Hf_rQHWdMv=05XqXiJK0x4aaT9KQd_1UE38ZGFkUA@mail.gmail.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
To: Stefan Winter <stefan.winter@restena.lu>
Content-Type: text/plain; charset=UTF-8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 19:16:27 -0000

On 27 February 2013 08:46, Stefan Winter <stefan.winter@restena.lu> wrote:
> Hi,
>
>> [...] ferkakte [...]
>
> As a German, I'm now torn apart between being flattered that we've
> successfully exported a German word to the U.S. and being speechlessly
> shocked by the way spelling was b0rked in the process.
>

You got off lightly.
The English exported an entire language which got b0rked in the process!

From dhc@dcrocker.net  Wed Feb 27 11:18:55 2013
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55B9621F8A11 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHYjvFMSYIif for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:18:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BA20E21F887F for <ietf@ietf.org>; Wed, 27 Feb 2013 11:18:54 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r1RJIsUf015719 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 27 Feb 2013 11:18:54 -0800
Message-ID: <512E5C18.7040800@dcrocker.net>
Date: Wed, 27 Feb 2013 11:18:48 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <01OQON8Q439C000054@mauve.mrochek.com>
In-Reply-To: <01OQON8Q439C000054@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, 27 Feb 2013 11:18:54 -0800 (PST)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Feb 2013 19:18:55 -0000

On 2/27/2013 10:18 AM, ned+ietf@mauve.mrochek.com wrote:
> All the more so since it just leads people to use informal distribution
> methods. I don't recall a case where a chair forbid the discussion of a draft
> distributed this way.
>
> I recall hearing something once about routing around obstacles... Pity we don't
> internalize such principles fully.


Well, in an odd way we really do internalize most of the core Internet 
design and architecture rules quite well.

When the topic is IETF process, we seem to have an astonishingly 
consistent preference for choices that go in the opposite direction from 
what we've learned in creating the technology...

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ned+ietf@mauve.mrochek.com  Wed Feb 27 11:40:55 2013
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 6105F21F8B83 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lZeah+dyvsoN for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 11:40:55 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DD9C121F8B81 for <ietf@ietf.org>; Wed, 27 Feb 2013 11:40:54 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OQOPQPJYNK000J1D@mauve.mrochek.com> for ietf@ietf.org; Wed, 27 Feb 2013 11:35:53 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OQH0ICCQ1C000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 27 Feb 2013 11:35:51 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OQOPQO9W32000054@mauve.mrochek.com>
Date: Wed, 27 Feb 2013 11:21:28 -0800 (PST)
Subject: Re: Internet Draft Final Submission Cut-Off Today
In-reply-to: "Your message dated Wed, 27 Feb 2013 13:57:45 -0500" <512E5729.7090005@network-heretics.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com> <201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com> <512C06EC.8050408@stpeter.im> <201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de> <512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu> <512D1145.4060600@acm.org> <512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org> <01OQON8Q439C000054@mauve.mrochek.com> <0246891A-DD8F-4A7D-8880-BE95FA7B2365@tzi.org> <512E5729.7090005@network-heretics.com>
To: Keith Moore <moore@network-heretics.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: Wed, 27 Feb 2013 19:40:55 -0000

> On 02/27/2013 01:49 PM, Carsten Bormann wrote:
> > On Feb 27, 2013, at 19:18, ned+ietf@mauve.mrochek.com wrote:
> >
> >> routing around obstacles
> > It turns out for most people the easiest route around is submitting in time.
> >
> > That is actually what counts here: how does the rule influence the behavior of people.
> >
> > Chair hat: WORKSFORME.  (And, if I could decide it, WONTFIX.)
> +1.

> As far as I can tell, the deadline actually serves the purpose of
> getting people to focus on IETF and update their documents sufficiently
> prior to the meeting, that it's reasonable to expect meeting
> participants to read the drafts that they intend to discuss.   And I say
> this as someone who, as an author, has often found the deadline to be
> very inconvenient.

And your evidence for this is .. what exactly? Yes, the deadline makes the
drafts show up a bit sooner, but I rather suspect that the overwhelming
majority of people don't bother to do much reading in the inverval. I certainly
don't.

And given the ready available tools to tell the reader what's changed I don't
need to. In almost all cases for -nn where nn > 00 I can check what's changed
in a few minutes, and I can do it in the context of the actual work being done.

I don't really have any objection to a -00 cutoff, but the second cutoff
is nothing short of asinine.

In any case, I personally have basically stopped caring about the deadline and
I encourage others to do the same. If I make the deadline fine, if not I post
the update somewhere else, done.

				Ned

From falsehood911@gmail.com  Wed Feb 27 22:54:59 2013
Return-Path: <falsehood911@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC04821F8569 for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 22:54:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x3Ra8A9UeUXB for <ietf@ietfa.amsl.com>; Wed, 27 Feb 2013 22:54:59 -0800 (PST)
Received: from mail-ye0-f182.google.com (mail-ye0-f182.google.com [209.85.213.182]) by ietfa.amsl.com (Postfix) with ESMTP id 0288F21F84D8 for <ietf@ietf.org>; Wed, 27 Feb 2013 22:54:56 -0800 (PST)
Received: by mail-ye0-f182.google.com with SMTP id r9so216422yen.13 for <ietf@ietf.org>; Wed, 27 Feb 2013 22:54:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:content-type :message-id:content-transfer-encoding:from:subject:date:to:x-mailer; bh=5WsYzE2jbCkTX9M/rkNaXtxoFis5HFy8Q7VdS/rRbv8=; b=uCv08N3pX9foB6ZMZbyFzCvPoffoTAG8xM5jIzsdctCDIrRIUsaqJ25mZ/DlqcqaSB xzQmCw8DR4NWkYl+Y8nn1IzZ+N4Gq7eKT/ogyor0iUo0l8T6G4aM5GFa8CGQgaSqeTJ+ cOL+DDvSEfAQn7QxWMgliIPD2UMJWfH9mDmormmNG7hQanTb7L2XHc6NnfDi79eXPvTS V1HTEnjmyTPID5qycFnfgrcG7QBLYwKpzgqVEI7f8oBdq0j9pZMru/IJL7CFqvMv+HHL REuThZTN8K9mEawv9dswz7CcqSSywkfTizXARmqes9O3hj172YMzZeo7tbhWreKgS/eP PxAw==
X-Received: by 10.236.60.101 with SMTP id t65mr3900320yhc.190.1362034496570; Wed, 27 Feb 2013 22:54:56 -0800 (PST)
Received: from [192.168.1.6] (24-196-90-204.dhcp.mdsn.wi.charter.com. [24.196.90.204]) by mx.google.com with ESMTPS id r43sm7845590yhl.19.2013.02.27.22.54.54 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 27 Feb 2013 22:54:55 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v753.1)
In-Reply-To: <512C3445.60709@lacnic.net>
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B257A.3030902@lacnic.net> <CAOmxzdzxNejS_D3wHm_rPHBmAYZDXVK5odhP2ge057NQRu2mWw@mail.gmail.com> <512C3445.60709@lacnic.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4E14AC56-45B1-4A5E-9501-2B6FB1E12159@gmail.com>
Content-Transfer-Encoding: 7bit
From: falsehood911@gmail.com
Subject: Re: IETF chair's blog
Date: Thu, 28 Feb 2013 00:54:52 -0600
To: ietf@ietf.org
X-Mailer: Apple Mail (2.753.1)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 06:55:00 -0000

Young people like myself may use other networks to communicate, but  
we also mistrust them. There is something virtuous about the IETF  
stance that is appealing and helpful to its brand (and made signing  
up for this listserve more attractive). I am wary of diluting that  
brand by putting the brand into walled gardens, especially any sort  
of Facebook page. Whatever use there is, it should be easy for people  
to find the open-source resources, keeping outside hosted content as  
a gateway into the ISTF.

-WLS

On Feb 25, 2013, at 10:04 PM, Arturo Servin wrote:

> t
> 	It appears that the path that this discussion has followed has proven
> your point.
>
> /as
>
> On 25/02/2013 23:31, Alejandro Acosta wrote:
>> On 2/25/13, Arturo Servin <aservin@lacnic.net> wrote:
>>> Fred,
>>>
>>> 	I am not convinced that social nets (proprietary or not) are yet  
>>> a good
>>> tool to do IETF work. They are good to communicate one-way and some
>>> informal two-ways, but that's all (at least for now)
>>>
>>> 	What I had in mind was something very simple such that the IETF  
>>> chair
>>> could do is to automatically post to twitter, facebook, etc whenever
>>> there is a new post from his blog and receive from communication  
>>> using
>>> those tools (besides the comments in the blog). But that is all.
>>
>> This scenario sounds good for me.  Of course this is not a
>> substitution of the mailing list, this is complementary. It's nice to
>> receive a tweet with the subject of the blog post and the URL to  
>> click
>> on it.
>>
>> Some time ago in this mailing list we were discussing that the  
>> average
>> age of IETF is getting old (of course, there are many exceptions).  
>> Did
>> you know that young people do not use email as much as us?. Saying
>> that, this can be a good way to bring young people to IETF.
>>
>> Alejandro Acosta,
>>
>>
>> {...}
>>


From brian.e.carpenter@gmail.com  Thu Feb 28 00:05:05 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6199F21F84C1 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 00:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.555
X-Spam-Level: 
X-Spam-Status: No, score=-99.555 tagged_above=-999 required=5 tests=[AWL=-0.634, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzDAjINg-pRM for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 00:05:05 -0800 (PST)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id A96E121F84BC for <ietf@ietf.org>; Thu, 28 Feb 2013 00:05:04 -0800 (PST)
Received: by mail-we0-f181.google.com with SMTP id t44so1246030wey.26 for <ietf@ietf.org>; Thu, 28 Feb 2013 00:05:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0XrdgGLlRkRzbAzNjm/HNPIH22jiLePD9L2menz9T08=; b=t5nP5rYg6DKIJTtLp0Sl3V2+B9fADW8gbCayztO5e8MMI/QR/5k0EYvuLhiUWEJntZ 0rfAPZDYc5h5A7G+WQt6sEVytKzNr/90CfPDdyA//G3b6AcabZEHpKlMJ3MuX8cQ44WH N4HtmzJEJd7FPVl3xO8tgOeIa7KUFqCxzNrtLVZbAvjF4UOIJ52QZmaDXRsyeBAZl0wK 9RVrLuwG4B/aHIwxAdPklSHDFPeVjvMGUqtBXzrelgHcHndu1urKkmcOBEodQCg6Dym1 AeevkiRsV8M/cPLYmunwp5X4X8Zq01RUogWH6Z9cOR1hhYIVpTe6B7Zad7OvTh03/php MN6g==
X-Received: by 10.194.20.72 with SMTP id l8mr8954376wje.36.1362038703806; Thu, 28 Feb 2013 00:05:03 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-166.as13285.net. [2.101.188.166]) by mx.google.com with ESMTPS id ay10sm31710368wib.3.2013.02.28.00.05.01 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 00:05:02 -0800 (PST)
Message-ID: <512F0FB7.10707@gmail.com>
Date: Thu, 28 Feb 2013 08:05:11 +0000
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: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>	<512D37B0.7010108@gmail.com> <512E4A93.5010904@levkowetz.com>
In-Reply-To: <512E4A93.5010904@levkowetz.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 08:05:05 -0000

On 27/02/2013 18:04, Henrik Levkowetz wrote:
> Hi Melinda,
> 
> On 2013-02-26 23:31 Melinda Shore said:
>> On 2/26/13 1:25 PM, Paul E. Jones wrote:
>>> Seriously, what the heck is 24:00?  
>> That one is weird, no doubt about it, but ultimately
>> it's 23:59 + 1 minute, which is clear.  But I really
>> think "24:00" is confusing. 0:00 is clearer.  I'm
>> wondering if they're trying to work around some ferkakte
>> piece of software.
> 
> No, it's just trying to provide a time indication that people
> will easily interpret correctly.  Trying out the correct
> notation (using 00:00 and the following date) on people
> during informal testing, I found that people were much more
> prone to interpret that as the deadline being 24 hours later
> than was intended.

Strange. Do they think that a train that departs at 00:01
is 23 hours and 59 minutes earlier than one that departs at 00:00?

However, the phrase "midnight on Monday" is certainly unclear.
I suppose it means 00:00 on Tuesday, but maybe not.

But in any case, while teaching, I chose to set assignment deadlines
at 23:59 for exactly this reason - nothing is completely idiot proof,
but this seems to work out OK.

   Brian

From brian.e.carpenter@gmail.com  Thu Feb 28 00:12:59 2013
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDF021F8BB0 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 00:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.533
X-Spam-Level: 
X-Spam-Status: No, score=-99.533 tagged_above=-999 required=5 tests=[AWL=-0.612, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_ILLEGAL_IP=1.908, RCVD_IN_PBL=0.905, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OqH7iKojhOE for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 00:12:58 -0800 (PST)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 518FF21F8B33 for <ietf@ietf.org>; Thu, 28 Feb 2013 00:12:58 -0800 (PST)
Received: by mail-we0-f171.google.com with SMTP id u54so1290920wey.16 for <ietf@ietf.org>; Thu, 28 Feb 2013 00:12:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XA5kz+NOsR1VMPxxJX3NylQKyweNrj9Je2O02PLt9kk=; b=iccAokuPPRyPhgXDqzmA0hUOi4NY68Vd3EFHacX0u8i/ILjlxOb1aq7Ta6uxhBlhm7 r+WcW0AIpmEU4swBEkFHwZlEDzq8XC0JUC7W3TcqrIRjaLZ3uf9qygC0yHSOGyOlggKx xaStOg1YFyFqBdXTTJ6rFHdBvpsHowF6lS/VIE477M7sGyYCt5RghJkNi+6bssWfGF2Q 40OJD+hR0X0uRUGNszMND6n31px4TwJBOgnqrnqBJEO04IcO3UmdMjMWGCORNBNN+vyH GLu7WvVRcPnxoEzEeWLdfxtQ+iks8Mk6f3hBs4eYpPHjF4aucW8Od+463uyKco5GE+BC jnCQ==
X-Received: by 10.180.94.135 with SMTP id dc7mr31130943wib.11.1362039177450; Thu, 28 Feb 2013 00:12:57 -0800 (PST)
Received: from [192.168.1.65] (host-2-101-188-166.as13285.net. [2.101.188.166]) by mx.google.com with ESMTPS id bs6sm13648778wib.4.2013.02.28.00.12.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 00:12:56 -0800 (PST)
Message-ID: <512F1192.5000906@gmail.com>
Date: Thu, 28 Feb 2013 08:13:06 +0000
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com> <512D0F7E.8030402@isi.edu>	<512D1145.4060600@acm.org> <512D139D.8090305@isi.edu>	<512D3968.50104@qti.qualcomm.com>	<47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>	<01OQON8Q439C000054@mauve.mrochek.com>	<0246891A-DD8F-4A7D-8880-BE95FA7B2365@tzi.org>	<512E5729.7090005@network-heretics.com> <01OQOPQO9W32000054@mauve.mrochek.com>
In-Reply-To: <01OQOPQO9W32000054@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 08:12:59 -0000

Ned,

On 27/02/2013 19:21, ned+ietf@mauve.mrochek.com wrote:
>> On 02/27/2013 01:49 PM, Carsten Bormann wrote:
>> > On Feb 27, 2013, at 19:18, ned+ietf@mauve.mrochek.com wrote:
>> >
>> >> routing around obstacles
>> > It turns out for most people the easiest route around is submitting
>> in time.
>> >
>> > That is actually what counts here: how does the rule influence the
>> behavior of people.
>> >
>> > Chair hat: WORKSFORME.  (And, if I could decide it, WONTFIX.)
>> +1.
> 
>> As far as I can tell, the deadline actually serves the purpose of
>> getting people to focus on IETF and update their documents sufficiently
>> prior to the meeting, that it's reasonable to expect meeting
>> participants to read the drafts that they intend to discuss.   And I say
>> this as someone who, as an author, has often found the deadline to be
>> very inconvenient.
> 
> And your evidence for this is .. what exactly? Yes, the deadline makes the
> drafts show up a bit sooner, but I rather suspect that the overwhelming
> majority of people don't bother to do much reading in the inverval. I
> certainly
> don't.

Just to present another view, I certainly do.

I agree that this is more important for -00 drafts, and that looking at
the diffs *may* be sufficient for updated drafts. However, with hundreds
of documents coming down the pipe shortly before the meeting, I firmly
believe that the two deadlines are essential in order to achieve any
kind of systematic triage and decide what needs careful reading.

I think many of us have a wide range of interests that make this
triage important.

  Brian

From daedulus@btconnect.com  Thu Feb 28 02:13:40 2013
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1F6321F8AC3 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 02:13:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.735
X-Spam-Level: 
X-Spam-Status: No, score=-5.735 tagged_above=-999 required=5 tests=[AWL=0.864,  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 YHhauZ9OOVoS for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 02:13:39 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe002.messaging.microsoft.com [207.46.163.25]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9A921F89AA for <ietf@ietf.org>; Thu, 28 Feb 2013 02:13:38 -0800 (PST)
Received: from mail184-co9-R.bigfish.com (10.236.132.253) by CO9EHSOBE004.bigfish.com (10.236.130.67) with Microsoft SMTP Server id 14.1.225.23; Thu, 28 Feb 2013 10:13:38 +0000
Received: from mail184-co9 (localhost [127.0.0.1])	by mail184-co9-R.bigfish.com (Postfix) with ESMTP id 50E551002B3; Thu, 28 Feb 2013 10:13:38 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.85; KIP:(null); UIP:(null); IPV:NLI; H:AMSPRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: PS-19(zz98dI9371I542Izz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz1033IL8275dh8275bhz2dh2a8h5a9h668h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h304l1155h)
Received: from mail184-co9 (localhost.localdomain [127.0.0.1]) by mail184-co9 (MessageSwitch) id 1362046416379209_21925; Thu, 28 Feb 2013 10:13:36 +0000 (UTC)
Received: from CO9EHSMHS027.bigfish.com (unknown [10.236.132.238])	by mail184-co9.bigfish.com (Postfix) with ESMTP id 59670600048; Thu, 28 Feb 2013 10:13:36 +0000 (UTC)
Received: from AMSPRD0710HT003.eurprd07.prod.outlook.com (157.56.249.85) by CO9EHSMHS027.bigfish.com (10.236.130.37) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 28 Feb 2013 10:13:36 +0000
Received: from DB3PRD0511HT002.eurprd05.prod.outlook.com (157.56.254.213) by pod51017.outlook.com (10.255.160.166) with Microsoft SMTP Server (TLS) id 14.16.263.1; Thu, 28 Feb 2013 10:13:32 +0000
Message-ID: <028701ce159b$c4b78a00$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Margaret Wasserman <mrw@lilacglade.org>, Pete Resnick <presnick@qti.qualcomm.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<9354DE06-D414-47E2-9D23-6964B3CB7BAA@lurchi.franken.de>	<512D0BC7.6080200@bogus.com><512D0F7E.8030402@isi.edu>	<512D1145.4060600@acm.org><512D139D.8090305@isi.edu> <512D3968.50104@qti.qualcomm.com> <47BA0849-28A5-43A3-9F82-C27905CAF6D7@lilacglade.org>
Subject: Re: Internet Draft Final Submission Cut-Off Today
Date: Thu, 28 Feb 2013 10:05:08 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.254.213]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 10:13:40 -0000

----- Original Message -----
From: "Margaret Wasserman" <mrw@lilacglade.org>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Cc: <ietf@ietf.org>
Sent: Tuesday, February 26, 2013 10:49 PM

On Feb 26, 2013, at 5:38 PM, Pete Resnick <presnick@qti.qualcomm.com>
wrote:

> But more seriously: I agree with you both. The deadline is silly.

+1

The deadline originated because the secretariat needed time to post all
of those drafts (by hand) before the meeting.  The notion of an
automated tool that blocks submissions for two weeks before the meeting
is just silly.

<tp>

Sometimes, history is bunk:-)

Whatever reason is buried in the mists of time, the sheer volume of I-Ds
that flood the IETF each and every day requires a pause in the process
for someone who wishes to make an informed contribution to an IETF
meeting to step back and consider what preparation they need to do
before attending.

The publication deadline provides that, especially against the authors
who want to do everything at or after the last minute, regardless of the
cost to those who want to use their time more productively by planning
ahead.

Of course, if your only interest is in your own I-D, or that of your
fellow-workers, then you may not grasp the importance of this issue in
the work of the IETF at large:-(

Tom Petch

Margaret





From henrik@levkowetz.com  Thu Feb 28 03:02:19 2013
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B577B21F8522 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 03:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vs0huyDq7Qxi for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 03:02:19 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 1D3DE21F84E6 for <ietf@ietf.org>; Thu, 28 Feb 2013 03:02:19 -0800 (PST)
Received: from [2a01:3f0:1:0:4c4e:bad7:4c4f:8fe8] (port=52409 helo=tannat.netnod.se) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1UB1Fd-00053y-Ap; Thu, 28 Feb 2013 12:02:13 +0100
Message-ID: <512F3935.8050100@levkowetz.com>
Date: Thu, 28 Feb 2013 12:02:13 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com>	<201302261901.r1QJ17ZL2693351@shell01.TheWorld.com>	<037501ce1470$2ed50c50$8c7f24f0$@packetizer.com>	<512D37B0.7010108@gmail.com> <512E4A93.5010904@levkowetz.com> <512F0FB7.10707@gmail.com>
In-Reply-To: <512F0FB7.10707@gmail.com>
X-Enigmail-Version: 1.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 2a01:3f0:1:0:4c4e:bad7:4c4f:8fe8
X-SA-Exim-Rcpt-To: brian.e.carpenter@gmail.com, ietf@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Re: Internet Draft Final Submission Cut-Off Today
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 11:02:19 -0000

Hi Brian,

On 2013-02-28 09:05 Brian E Carpenter said:
> On 27/02/2013 18:04, Henrik Levkowetz wrote:
>> Hi Melinda,
>>
>> On 2013-02-26 23:31 Melinda Shore said:
>>> On 2/26/13 1:25 PM, Paul E. Jones wrote:
>>>> Seriously, what the heck is 24:00?  
>>> That one is weird, no doubt about it, but ultimately
>>> it's 23:59 + 1 minute, which is clear.  But I really
>>> think "24:00" is confusing. 0:00 is clearer.  I'm
>>> wondering if they're trying to work around some ferkakte
>>> piece of software.
>>
>> No, it's just trying to provide a time indication that people
>> will easily interpret correctly.  Trying out the correct
>> notation (using 00:00 and the following date) on people
>> during informal testing, I found that people were much more
>> prone to interpret that as the deadline being 24 hours later
>> than was intended.
> 
> Strange. Do they think that a train that departs at 00:01
> is 23 hours and 59 minutes earlier than one that departs at 00:00?

Probably not:  I think it's the 00:00 which some people tend to
(unconsciously) translate to 'Midnight', and midnight at a certain
date is, exactly as you point out below, somewhat less clear.

> However, the phrase "midnight on Monday" is certainly unclear.
> I suppose it means 00:00 on Tuesday, but maybe not.
> 
> But in any case, while teaching, I chose to set assignment deadlines
> at 23:59 for exactly this reason - nothing is completely idiot proof,
> but this seems to work out OK.

Ack.  I'll try to get acceptance for that.

Best regards,

	Henrik


From carlosm3011@gmail.com  Thu Feb 28 06:02:15 2013
Return-Path: <carlosm3011@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C25921F8697 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 06:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AP1CslAq6zcM for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 06:02:14 -0800 (PST)
Received: from mail-ve0-f181.google.com (mail-ve0-f181.google.com [209.85.128.181]) by ietfa.amsl.com (Postfix) with ESMTP id 5C58621F86A5 for <ietf@ietf.org>; Thu, 28 Feb 2013 06:02:03 -0800 (PST)
Received: by mail-ve0-f181.google.com with SMTP id d10so1794537vea.40 for <ietf@ietf.org>; Thu, 28 Feb 2013 06:02:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:reply-to:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rfPUrQ/R6b6hz66MogConVtX+DEiye1WoJjOLWpnptk=; b=o9CxU6u+PcSAUuRxViATGrdmjagCYoYrHWSsJQO7jRDARYG5LpIzlaHDjNqvB7+zj+ gNOYaymM/U85BltuTI8izR7szpd3R0Nysp6u3wtzMOv0wdLk5mmAjLtjJctOyD9QlGK+ kZ9T3b+OREBYm2v1ROme8hJQWLt84vOci0vMMzqqoq7jAhL6fRVH6xygvYBxZwgUMiMV TApsejEIWs5QO5ac1ZS9jZ7oi3KUKvUKELXSKPdqbTLKpRur154wY8tuxGnR+HYU20kt 4PktckbUvonWx3131nW1e5tryctcFskFaq5PPCU2dHfz6UUDwVPgpdFkPs+OD+9PfOin ++UQ==
X-Received: by 10.52.29.209 with SMTP id m17mr2220574vdh.111.1362060122638; Thu, 28 Feb 2013 06:02:02 -0800 (PST)
Received: from [200.7.85.156] ([200.7.85.156]) by mx.google.com with ESMTPS id yu12sm1915358vec.6.2013.02.28.06.02.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 28 Feb 2013 06:02:01 -0800 (PST)
Message-ID: <512F6354.1010006@gmail.com>
Date: Thu, 28 Feb 2013 12:01:56 -0200
From: "Carlos M. Martinez" <carlosm3011@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3
MIME-Version: 1.0
To: falsehood911@gmail.com
Subject: Re: IETF chair's blog
References: <1BBAE003-DEA4-462A-998D-863F6FF90A69@ietf.org> <51298B1E.60007@lacnic.net> <512A5A10.4090406@acm.org> <8C48B86A895913448548E6D15DA7553B7A52DA@xmb-rcd-x09.cisco.com> <512B257A.3030902@lacnic.net> <CAOmxzdzxNejS_D3wHm_rPHBmAYZDXVK5odhP2ge057NQRu2mWw@mail.gmail.com> <512C3445.60709@lacnic.net> <4E14AC56-45B1-4A5E-9501-2B6FB1E12159@gmail.com>
In-Reply-To: <4E14AC56-45B1-4A5E-9501-2B6FB1E12159@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: carlos@lacnic.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, 28 Feb 2013 14:02:15 -0000

What about possibly 'open' social networks? I remember Quora intended to
become something like that. What about something the whateverOverflow
sites (StackOverflow, etc). IMO they are some of the best managed
technical 'social' sites out there, they do a great job.

I can easily imagine a IETFOverflow :D

Back to the discussion, I'm also torn here, but I definitely believe
that some FB/Twitter outreach from the IETF itself wouldn't hurt at all.

I do believe that a radical change in the way discussions are conducted
(like moving from the MLs to a say, a Google Hangout or whatever) cannot
be undertaken without some major thinking and pro/con evaluation.

>From the discussion here, it appears that my approach to the cloud and
social is kinda 'middle aged', not so young nor old. I use Google Docs
quite a lot, but keep a local copy of everything in my drive. I use
Dropbox, but also copy everything to an external drive. I use FB, but
wouldn't send a work message through it (and believe me I know people
who do use FB messaging for work)

As our friend 'falsehood911' comments, I do also believe that there is
something to be said for traditions and stances. They got there for a
reason, even if that reason got lost in the mists of time. One should do
well being careful before abandoning / changing them.

Warm philosophical regards,

~Carlos


On 2/28/13 4:54 AM, falsehood911@gmail.com wrote:
> Young people like myself may use other networks to communicate, but we
> also mistrust them. There is something virtuous about the IETF stance
> that is appealing and helpful to its brand (and made signing up for this
> listserve more attractive). I am wary of diluting that brand by putting
> the brand into walled gardens, especially any sort of Facebook page.
> Whatever use there is, it should be easy for people to find the
> open-source resources, keeping outside hosted content as a gateway into
> the ISTF.
> 
> -WLS
> 
> On Feb 25, 2013, at 10:04 PM, Arturo Servin wrote:
> 
>> t
>>     It appears that the path that this discussion has followed has proven
>> your point.
>>
>> /as
>>
>> On 25/02/2013 23:31, Alejandro Acosta wrote:
>>> On 2/25/13, Arturo Servin <aservin@lacnic.net> wrote:
>>>> Fred,
>>>>
>>>>     I am not convinced that social nets (proprietary or not) are yet
>>>> a good
>>>> tool to do IETF work. They are good to communicate one-way and some
>>>> informal two-ways, but that's all (at least for now)
>>>>
>>>>     What I had in mind was something very simple such that the IETF
>>>> chair
>>>> could do is to automatically post to twitter, facebook, etc whenever
>>>> there is a new post from his blog and receive from communication using
>>>> those tools (besides the comments in the blog). But that is all.
>>>
>>> This scenario sounds good for me.  Of course this is not a
>>> substitution of the mailing list, this is complementary. It's nice to
>>> receive a tweet with the subject of the blog post and the URL to click
>>> on it.
>>>
>>> Some time ago in this mailing list we were discussing that the average
>>> age of IETF is getting old (of course, there are many exceptions). Did
>>> you know that young people do not use email as much as us?. Saying
>>> that, this can be a good way to bring young people to IETF.
>>>
>>> Alejandro Acosta,
>>>
>>>
>>> {...}
>>>
> 

From worley@shell01.TheWorld.com  Thu Feb 28 11:48:02 2013
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40EB21F87D2 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 11:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.457
X-Spam-Level: 
X-Spam-Status: No, score=-2.457 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OWh0y3Z7O+Kf for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 11:48:02 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3D021F87D5 for <ietf@ietf.org>; Thu, 28 Feb 2013 11:48:02 -0800 (PST)
Received: from shell.TheWorld.com (root@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id r1SJlb3f028812 for <ietf@ietf.org>; Thu, 28 Feb 2013 14:47:39 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id r1SJlbD72803225 for <ietf@ietf.org>; Thu, 28 Feb 2013 14:47:37 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id r1SJlblY2790436; Thu, 28 Feb 2013 14:47:37 -0500 (EST)
Date: Thu, 28 Feb 2013 14:47:37 -0500 (EST)
Message-Id: <201302281947.r1SJlblY2790436@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <512DC7E3.8080501@restena.lu> (stefan.winter@restena.lu)
Subject: Re: Internet Draft Final Submission Cut-Off Today
References: <20130225170532.25599.13118.idtracker@ietfa.amsl.com>	<201302260047.r1Q0l2Im030997@rcdn-core2-6.cisco.com>	<512C06EC.8050408@stpeter.im>	<201302260058.r1Q0wBlI032453@rcdn-core-2.cisco.com> <201302261901.r1QJ17ZL2693351@shell01.TheWorld.com> <037501ce1470$2ed50c50$8c7f24f0$@packetizer.com> <512D37B0.7010108@gmail.com> <512DC7E3.8080501@restena.lu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Feb 2013 19:48:03 -0000

> From: Stefan Winter <stefan.winter@restena.lu>
> 
> > [...] ferkakte [...]
> 
> As a German, I'm now torn apart between being flattered that we've
> successfully exported a German word to the U.S. and being speechlessly
> shocked by the way spelling was b0rked in the process.

Given that the word is Yiddish, and therefore has been transliterated
from the Hebrew alphabet (in which Yiddish is written) into the Latin
alphabet, you can blame the problem on incorrect
internationalization...

Dale

From narten@us.ibm.com  Thu Feb 28 21:53:11 2013
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3774121F8802 for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 21:53:11 -0800 (PST)
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 pYg-K7U3I1wS for <ietf@ietfa.amsl.com>; Thu, 28 Feb 2013 21:53:10 -0800 (PST)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 5903E21F89E1 for <ietf@ietf.org>; Thu, 28 Feb 2013 21:53:10 -0800 (PST)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 28 Feb 2013 22:53:09 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 28 Feb 2013 22:53:07 -0700
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 2C0FE1FF0038 for <ietf@ietf.org>; Thu, 28 Feb 2013 22:48:15 -0700 (MST)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id r215r6NB060136 for <ietf@ietf.org>; Thu, 28 Feb 2013 22:53:07 -0700
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 r215r6e8011048 for <ietf@ietf.org>; Thu, 28 Feb 2013 22:53:06 -0700
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 r215r5wC010971 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 28 Feb 2013 22:53:05 -0700
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 r215r46x004784 for <ietf@ietf.org>; Fri, 1 Mar 2013 00:53:04 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id r215r38a004739 for ietf@ietf.org; Fri, 1 Mar 2013 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201303010553.r215r38a004739@rotala.raleigh.ibm.com>
Date: Fri, 01 Mar 2013 00:53:03 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 13030105-2398-0000-0000-0000119F299A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Mar 2013 05:53:11 -0000

Total of 164 messages in the last 7 days.
 
script run at: Fri Mar  1 00:53:03 EST 2013
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.88% |    8 |  5.91% |    73893 | mary.ietf.barnes@gmail.com
  3.66% |    6 |  5.37% |    67104 | hsantos@isdg.net
  3.66% |    6 |  4.88% |    60980 | abdussalambaryun@gmail.com
  3.66% |    6 |  3.53% |    44167 | brian.e.carpenter@gmail.com
  3.66% |    6 |  3.46% |    43216 | sm@resistor.net
  3.66% |    6 |  3.27% |    40959 | petithug@acm.org
  3.66% |    6 |  3.12% |    38970 | aservin@lacnic.net
  2.44% |    4 |  3.12% |    39059 | grmocg@gmail.com
  3.05% |    5 |  2.49% |    31099 | melinda.shore@gmail.com
  3.05% |    5 |  2.37% |    29661 | worley@ariadne.com
  2.44% |    4 |  2.52% |    31523 | jmpolk@cisco.com
  1.83% |    3 |  2.93% |    36630 | doug@ewellic.org
  2.44% |    4 |  2.31% |    28836 | joelja@bogus.com
  1.83% |    3 |  2.87% |    35852 | acooper@cdt.org
  2.44% |    4 |  2.05% |    25592 | warren@kumari.net
  1.22% |    2 |  2.80% |    34990 | ietf@thomasclausen.org
  1.83% |    3 |  1.61% |    20190 | scott@kitterman.com
  1.22% |    2 |  2.14% |    26777 | spromano@unina.it
  1.22% |    2 |  1.76% |    21986 | randy@qti.qualcomm.com
  1.22% |    2 |  1.24% |    15565 | presnick@qti.qualcomm.com
  1.22% |    2 |  1.19% |    14893 | fred@cisco.com
  1.22% |    2 |  1.18% |    14804 | trammell@tik.ee.ethz.ch
  1.22% |    2 |  1.15% |    14423 | wesley.george@twcable.com
  1.22% |    2 |  1.11% |    13924 | mnot@mnot.net
  1.22% |    2 |  1.09% |    13631 | jari.arkko@piuha.net
  1.22% |    2 |  1.05% |    13167 | cabo@tzi.org
  1.22% |    2 |  1.02% |    12793 | henrik@levkowetz.com
  1.22% |    2 |  1.02% |    12784 | stefan.winter@restena.lu
  1.22% |    2 |  1.00% |    12503 | ned+ietf@mauve.mrochek.com
  1.22% |    2 |  0.99% |    12424 | dhc@dcrocker.net
  1.22% |    2 |  0.98% |    12273 | paulej@packetizer.com
  1.22% |    2 |  0.98% |    12230 | touch@isi.edu
  1.22% |    2 |  0.97% |    12177 | michael.tuexen@lurchi.franken.de
  1.22% |    2 |  0.96% |    12029 | cyrus@daboo.name
  1.22% |    2 |  0.96% |    12002 | lear@cisco.com
  1.22% |    2 |  0.92% |    11521 | alejandroacostaalamo@gmail.com
  1.22% |    2 |  0.92% |    11464 | dot@dotat.at
  1.22% |    2 |  0.88% |    10962 | mrw@lilacglade.org
  1.22% |    2 |  0.87% |    10872 | mohta@necom830.hpcl.titech.ac.jp
  1.22% |    2 |  0.84% |    10462 | randy@psg.com
  1.22% |    2 |  0.83% |    10404 | mrex@sap.com
  0.61% |    1 |  0.93% |    11579 | hannes.tschofenig@gmx.net
  0.61% |    1 |  0.88% |    11004 | ed.lewis@neustar.biz
  0.61% |    1 |  0.79% |     9863 | rlb@ipv.sx
  0.61% |    1 |  0.73% |     9159 | benl@google.com
  0.61% |    1 |  0.72% |     8993 | carlosm3011@gmail.com
  0.61% |    1 |  0.67% |     8331 | barryleiba@computer.org
  0.61% |    1 |  0.66% |     8260 | narten@us.ibm.com
  0.61% |    1 |  0.61% |     7667 | daedulus@btconnect.com
  0.61% |    1 |  0.59% |     7429 | falsehood911@gmail.com
  0.61% |    1 |  0.58% |     7315 | mcr+ietf@sandelman.ca
  0.61% |    1 |  0.57% |     7184 | ynir@checkpoint.com
  0.61% |    1 |  0.56% |     6989 | mehmet.ersue@nsn.com
  0.61% |    1 |  0.55% |     6927 | victor.kuarsingh@gmail.com
  0.61% |    1 |  0.55% |     6835 | john@jlc.net
  0.61% |    1 |  0.54% |     6803 | dave@cridland.net
  0.61% |    1 |  0.54% |     6796 | john-ietf@jck.com
  0.61% |    1 |  0.53% |     6668 | tjc@ecs.soton.ac.uk
  0.61% |    1 |  0.53% |     6573 | john+ietf@jck.com
  0.61% |    1 |  0.53% |     6568 | moore@network-heretics.com
  0.61% |    1 |  0.52% |     6506 | d3e3e3@gmail.com
  0.61% |    1 |  0.51% |     6396 | klaas@cisco.com
  0.61% |    1 |  0.51% |     6364 | dougb@dougbarton.us
  0.61% |    1 |  0.51% |     6361 | marka@isc.org
  0.61% |    1 |  0.49% |     6089 | glenzorn@gmail.com
  0.61% |    1 |  0.48% |     6066 | doramaria@gmail.com
  0.61% |    1 |  0.48% |     5958 | rwfranks@acm.org
  0.61% |    1 |  0.47% |     5818 | stpeter@stpeter.im
  0.61% |    1 |  0.46% |     5721 | nick@inex.ie
  0.61% |    1 |  0.45% |     5581 | ben@nostrum.com
  0.61% |    1 |  0.45% |     5579 | johnl@taugh.com
  0.61% |    1 |  0.42% |     5243 | ajs@anvilwalrusden.com
  0.61% |    1 |  0.40% |     5055 | sustrik@250bpm.com
  0.61% |    1 |  0.38% |     4790 | chair@ietf.org
  0.61% |    1 |  0.38% |     4763 | internet-drafts@ietf.org
  0.61% |    1 |  0.38% |     4729 | ietf-secretariat@ietf.org
--------+------+--------+----------+------------------------
100.00% |  164 |100.00% |  1250753 | Total

