
From russw@riw.us  Wed Jan  1 02:32:50 2014
Return-Path: <russw@riw.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AC0F1AE4D9 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 02:32:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.262
X-Spam-Level: 
X-Spam-Status: No, score=0.262 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12ARzEiHq6EW for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 02:32:48 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id 3E31A1AE4D7 for <ietf@ietf.org>; Wed,  1 Jan 2014 02:32:48 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:59752 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:AES128-SHA256:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VyJ6N-0008LT-Ml for ietf@ietf.org; Wed, 01 Jan 2014 10:32:39 +0000
From: "Russ White" <russw@riw.us>
To: <ietf@ietf.org>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net>
In-Reply-To: <52C35FFD.607@dcrocker.net>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 05:32:30 -0500
Message-ID: <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQDwmmlRCqrzcengRYjHYrwgOSmqfwFXWRe7Aq8twaQAhkIKxgH3NkOqAlUijiMBdm4GVgG9AnsVm8waAdA=
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 10:32:50 -0000

>       We should not approve an IETF policy statement
>      until we have a good idea of the way we will use it.

I'm struggling a bit with this statement -- it seems just as broad as the
draft under discussion, and just as much of a "policy" as the draft under
discussion. 

What does a "good idea," actually mean? That we have a fairly well defined
way to accomplish any particular goal before going about stating those
goals? That we should not go about trying to accomplish something until we
already have a good idea of how to accomplish it? If so, I don't think this
is a good result. The point of engineering seems, to me, to be that you
choose a goal, then you find a way to get to that goal. You might, on
stating the goal, find there's no obvious way to fulfill the goal, but
that's when you turn to research and lots of thinking, rather than simply
declaring the goal unreachable, and hence not worth articulating.

As for the politics piece -- I don't read this draft as political. The
problem is, rather, a more practical one -- if the Internet is made up of
systems and protocols that are essentially completely open to anyone reading
anything you send, post, or otherwise place into an IETF designed protocol
at any time by anyone, then the Internet isn't a place where anyone is going
to want to actually do much of anything at all. The general objections to
this are twofold:

- If you've not done anything wrong, you have nothing to hide. Refuted on
multiple occasions. You can begin by observing that "wrong," is, in the
modern world (and unfortunately), a completely relative term. It might mean
something completely different tomorrow than what it means today, but the
electronic record, as things stand today, is generally permanent.

- If you don't want to hide it, then don't put it on the Internet. Ten years
ago, no-one thought information about who your friends are (or what you eat
for dinner on a regular basis) had any economic worth. Today, this
information is considered valuable, and hence information you might actually
want to be careful to control in some way. What will suddenly be discovered
to be valuable in ten years' time? We can't even guess, so the better
statement is -- you should hide everything unless you've made a conscious
decision to unhide it. The default shouldn't be, "let everyone see," the
default should be, "let no-one see." 

There is an elephant in the room that I think needs to be brought out and
recognized: people don't make millions/billions on this information just by
knowing it. No-one pays a search engine provider to find out what's in your
email just because they want to know. They pay to know what's in your email
so they can (hopefully) change your behavior in some way (buy this rather
than that, you need that even though you hadn't thought of it before), or
your beliefs (vote for Joe rather than John). We are playing with something
that's more than just "I don't want people to know stuff about me," here.
This comes down to a fundamental level of trust -- who am I revealing
information to that might be used to shape my thoughts and actions in the
future, and how can I control the revelation of that information?

The fact is that the IETF has designed a suite of protocols that are mostly
unsecure, and widely used in a world where we're just starting to see the
importance of security around not only your credit card number, but also
your address book. That the IETF should make a statement saying, "we seem to
have something backwards here, and it's about time we reverse our
assumptions," isn't a political statement at all -- it's a facing of
reality. That the facing of reality has come about through any particular
political situation shouldn't imply that the statement is generally
political -- reacting to a political situation with a statement of a change
in policy isn't a political reaction, nor even (necessarily) a reaction
against the politics. Rather, it's just saying, "hey, we didn't think about
this problem before now, but now that we've thought about it, we need to set
some new goals."

Don't confuse the on list argument about politics with the actual point of
the draft; they're two different things entirely.

Anyway, that's my 2c. I've read the opposing arguments, and I'm still in
support of this draft.

Russ 


From ynir@checkpoint.com  Wed Jan  1 03:42:07 2014
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F6DE1AE246 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 03:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CcufslXzm7SW for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 03:42:06 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DCD071AE1D1 for <ietf@ietf.org>; Wed,  1 Jan 2014 03:42:05 -0800 (PST)
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id s01BfvER032484; Wed, 1 Jan 2014 13:41:58 +0200
X-CheckPoint: {52C3FA3B-0-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.77]) by IL-EX10.ad.checkpoint.com ([169.254.2.82]) with mapi id 14.03.0123.003; Wed, 1 Jan 2014 13:41:57 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Russ White <russw@riw.us>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPBmnBkZBWqxoR2EeGzFgLW3uyk5pu4QSAgACqLQCAABNlgA==
Date: Wed, 1 Jan 2014 11:41:57 +0000
Message-ID: <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>
In-Reply-To: <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.20.34]
x-kse-antivirus-interceptor-info: protection disabled
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F2F7E516A4B34A49B1A750D6B6D352C6@ad.checkpoint.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 11:42:07 -0000

On Jan 1, 2014, at 12:32 PM, Russ White <russw@riw.us> wrote:

>=20
>>      We should not approve an IETF policy statement
>>     until we have a good idea of the way we will use it.
>=20
> I'm struggling a bit with this statement -- it seems just as broad as the
> draft under discussion, and just as much of a "policy" as the draft under
> discussion.
>=20
> What does a "good idea," actually mean?=20

I guess a "good idea" would be a checklist for document authors, document s=
hepherds, and IESG members on what they need to consider in a document to a=
scertain whether it complies with this BCP nn.=20

We know what to look for in a security review. We know somewhat less well, =
but in a vague way what to look for in terms of privacy. I have no idea wha=
t to look for to counteract pervasive surveillance. Just as an example, let=
's look at a particular draft, and assume that it is ready for last call, a=
nd I need to write the shepherd's write-up.

I'll choose draft-ietf-httpauth-hoba-02.

The draft is about an authentication method for HTTP, where an asymmetric p=
er-origin key pair is used to authenticate the user (or rather, the user ag=
ent) to an HTTP server.=20

So now we have to make assumptions about our pervasive surveyor (is that th=
e word?):
 1. Can they decrypt TLS?=20
 2. Can they see the plaintext of the authentication process?
 3. Can they see the plaintext of the registration process?
 4. Can they retrieve the public key database at the server?
 5. Can they plant entries in the public key database, using perhaps the pr=
ocedure in section 6.2, allowing them to impersonate the user?

If they can do #1, they may be able to do #2 and #3, and then #4 is superfl=
uous. If they have access to the public key (through #3 or #4) and access t=
o the authentication plaintext (#2) then they can track where the user is l=
ogging in from.=20

There are so many capabilities we can imagine that the nation state adversa=
ry may have, and we only have a vague notion of what information must be pr=
evented from leaking to such an adversary. I don't think that I can check a=
 document to make sure it won't be smacked down in IETF LC or at the IESG f=
or not complying with BCP nn.

Also, what if we can hide more information out of a protocol, but at the ex=
pense of another roundtrip or more processing power. Who gets to balance th=
e two goals?

Yoav



From lear@lear.ch  Wed Jan  1 04:09:21 2014
Return-Path: <lear@lear.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA41B1AE4F8 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 04:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xcEHbXuSDaMK for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 04:09:20 -0800 (PST)
Received: from upstairs.ofcourseimright.com (upstairs.ofcourseimright.com [IPv6:2001:8a8:1006:4:223:54ff:fec2:5702]) by ietfa.amsl.com (Postfix) with ESMTP id 7AF651AE4F5 for <ietf@ietf.org>; Wed,  1 Jan 2014 04:09:19 -0800 (PST)
Received: from [192.168.0.3] (86-40-178-137-dynamic.b-ras2.srl.dublin.eircom.net [86.40.178.137]) (authenticated bits=0) by upstairs.ofcourseimright.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id s01C8uXL020499 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 1 Jan 2014 13:08:58 +0100
Mime-Version: 1.0 (1.0)
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <52C3A9D2.2090509@gmail.com> <290E20B455C66743BE178C5C84F1240847E51037C7@EXMB01CMS.surrey.ac.uk> <94CB7C32-46E2-47D8-BD38-9BAC4D545A85@cisco.com>
In-Reply-To: <94CB7C32-46E2-47D8-BD38-9BAC4D545A85@cisco.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-DF0843AC-3051-4E09-8D78-E6986DFFAD88
Content-Transfer-Encoding: 7bit
Message-Id: <43521858-7A9E-4FE1-A0A9-BB608599BFC6@lear.ch>
X-Mailer: iPhone Mail (11B554a)
From: Eliot Lear <lear@lear.ch>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 12:08:56 +0000
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 12:58:32 -0000

--Apple-Mail-DF0843AC-3051-4E09-8D78-E6986DFFAD88
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

(Apologies for dups)

Lloyd,

I share many of your concerns, especially in light of the fact that some - b=
ut no means all - security ADs have had a dodgy record in the past.=20

As Yoav infers, there is considerably more work to be done on the threat ana=
lysis that has been ably begun by Brian & co.  Discussion and development of=
 our understanding of the problem is what is called for.  If this draft has t=
hat effect, it has served a useful purpose.  If some are able to eliminate t=
hreats, all the better.=20

If, on the other hand, developers of a specification discussed the matter in=
 earnest and there was consensus on the way forward, even if some pervasive t=
hreats were not eliminated, and if that work is held up by claims relating t=
o this draft, then this draft will have caused harm.

That is nothing more or less than common sense.

As to whether this draft is political, it cannot be stressed enough that if o=
ne group of people can subvert our architecture, others can as well. Our pol=
itical statement, such as it is, is that in order to maintain confidence in t=
he Internet, our protocol suite should be resistant to this sort of thing, b=
ut within the bounds of pragmatism.=20

Eliot

> On Jan 1, 2014, at 6:08 AM, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk> wr=
ote:
>=20
> what it means for work moving through the IETF process
> is that any work becomes subject to security veto.
>=20
> if security types don't like your work - tough. it's
> going nowhere. draft-farrell really widens that scope.
> and this is going to mean arguments about
> much more than the tradeoffs of using MD5.
>=20
> for a self-described technical organisation that
> does not make policy pronouncements (which is
> itself a very political position, but never mind)
> this draft is awfully political.
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Melinda Shore [melinda.sho=
re@gmail.com]
> Sent: 01 January 2014 05:38
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive M=
onitoring is an Attack) to Best Current Practice
>=20
>> On 12/31/13 3:23 PM, Dave Crocker wrote:
>>  We should not approve an IETF policy statement
>> until we have a good idea of the way we will use it.
>=20
> I think this is a critical point and I agree quite strongly
> with it.  I've mostly been baffled by the IETF response to
> revelations about internet eavesdropping, to be honest,
> and it's struck me that work on some of the problems that
> need to be solved to provide better privacy guarantees (for
> example, fixing PKI and providing better keying) have been
> pushed to a back burner in a scramble to make grandiose
> pronouncements.  It's not that draft-farrell is a bad
> document on its own merits, it's just that I cannot for
> the life of me understand what it specifically means for
> work moving through the IETF process.
>=20
> Melinda



--Apple-Mail-DF0843AC-3051-4E09-8D78-E6986DFFAD88
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><span></span></div><div><meta http-equ=
iv=3D"content-type" content=3D"text/html; charset=3Dutf-8"><div><div><font c=
olor=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; background-c=
olor: rgba(255, 255, 255, 0);">(Apologies for dups)</span></font></div><div>=
<font color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; backg=
round-color: rgba(255, 255, 255, 0);"><br></span></font></div><div><font col=
or=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; background-col=
or: rgba(255, 255, 255, 0);">Lloyd,<br><br>I share many of your concerns, es=
pecially in light of the fact that some - but no means all - security ADs ha=
ve had a dodgy record in the past.&nbsp;<br><br>As Yoav infers, there is con=
siderably more work to be done on the threat analysis&nbsp;</span></font><sp=
an style=3D"background-color: rgba(255, 255, 255, 0);">that has been ably be=
gun by Brian &amp; co. &nbsp;</span><span style=3D"background-color: rgba(25=
5, 255, 255, 0);">Discussion and development of our understanding of the pro=
blem is what is called for. &nbsp;If this draft has that effect, it has serv=
ed a useful purpose. &nbsp;If some are able to eliminate threats, all the be=
tter.&nbsp;</span></div><div><font color=3D"#000000"><span style=3D"-webkit-=
text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br>If, o=
n the other hand, developers of a specification discussed the matter in earn=
est and there was consensus on the way forward, even if some pervasive threa=
ts were not eliminated, and if that work is held up by claims relating to th=
is draft, then this draft will have caused harm.<br><br>That is nothing more=
 or less than common sense.<br><br>As to whether this draft is political, it=
 cannot be stressed enough that if one group of people can subvert our archi=
tecture, others can as well. Our political statement, such as it is, is that=
 in order to maintain confidence in the Internet, our protocol suite should b=
e resistant to this sort of thing, but within the bounds of pragmatism.&nbsp=
;<br><br></span></font><div>Eliot</div><div><br></div><blockquote type=3D"ci=
te"><font color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; b=
ackground-color: rgba(255, 255, 255, 0);">On Jan 1, 2014, at 6:08 AM, "<a hr=
ef=3D"mailto:l.wood@surrey.ac.uk" x-apple-data-detectors=3D"true" x-apple-da=
ta-detectors-type=3D"link" x-apple-data-detectors-result=3D"1">l.wood@surrey=
.ac.uk</a>" &lt;<a href=3D"mailto:l.wood@surrey.ac.uk" x-apple-data-detector=
s=3D"true" x-apple-data-detectors-type=3D"link" x-apple-data-detectors-resul=
t=3D"2">l.wood@surrey.ac.uk</a>&gt; wrote:<br></span></font></blockquote><bl=
ockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-s=
ize-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></fo=
nt></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span styl=
e=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">what it means for work moving through the IETF process<br></span></font>=
</blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">=
is that any work becomes subject to security veto.<br></span></font></blockq=
uote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-webki=
t-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></s=
pan></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><s=
pan style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255=
, 255, 0);">if security types don't like your work - tough. it's<br></span><=
/font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span s=
tyle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255=
, 0);">going nowhere. draft-farrell really widens that scope.<br></span></fo=
nt></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span styl=
e=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">and this is going to mean arguments about<br></span></font></blockquote>=
<blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-tex=
t-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">much more th=
an the tradeoffs of using MD5.<br></span></font></blockquote><blockquote typ=
e=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size-adjust: a=
uto; background-color: rgba(255, 255, 255, 0);"><br></span></font></blockquo=
te><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-=
text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">for a sel=
f-described technical organisation that<br></span></font></blockquote><block=
quote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size=
-adjust: auto; background-color: rgba(255, 255, 255, 0);">does not make poli=
cy pronouncements (which is<br></span></font></blockquote><blockquote type=3D=
"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto=
; background-color: rgba(255, 255, 255, 0);">itself a very political positio=
n, but never mind)<br></span></font></blockquote><blockquote type=3D"cite"><=
font color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; backgr=
ound-color: rgba(255, 255, 255, 0);">this draft is awfully political.<br></s=
pan></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><s=
pan style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255=
, 255, 0);"><br></span></font></blockquote><blockquote type=3D"cite"><font c=
olor=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; background-c=
olor: rgba(255, 255, 255, 0);">Lloyd Wood<br></span></font></blockquote><blo=
ckquote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-si=
ze-adjust: auto; background-color: rgba(255, 255, 255, 0);"><a href=3D"http:=
//about.me/lloydwood" x-apple-data-detectors=3D"true" x-apple-data-detectors=
-type=3D"link" x-apple-data-detectors-result=3D"3">http://about.me/lloydwood=
</a><br></span></font></blockquote><blockquote type=3D"cite"><font color=3D"=
#000000"><span style=3D"-webkit-text-size-adjust: auto; background-color: rg=
ba(255, 255, 255, 0);">________________________________________<br></span></=
font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span st=
yle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255,=
 0);">From: ietf [<a href=3D"mailto:ietf-bounces@ietf.org" x-apple-data-dete=
ctors=3D"true" x-apple-data-detectors-type=3D"link" x-apple-data-detectors-r=
esult=3D"4">ietf-bounces@ietf.org</a>] On Behalf Of Melinda Shore [<a href=3D=
"mailto:melinda.shore@gmail.com" x-apple-data-detectors=3D"true" x-apple-dat=
a-detectors-type=3D"link" x-apple-data-detectors-result=3D"5">melinda.shore@=
gmail.com</a>]<br></span></font></blockquote><blockquote type=3D"cite"><font=
 color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; background=
-color: rgba(255, 255, 255, 0);">Sent: 01 January 2014 05:38<br></span></fon=
t></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=
=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0)=
;">To:&nbsp;<a href=3D"mailto:ietf@ietf.org" x-apple-data-detectors=3D"true"=
 x-apple-data-detectors-type=3D"link" x-apple-data-detectors-result=3D"7">ie=
tf@ietf.org</a><br></span></font></blockquote><blockquote type=3D"cite"><fon=
t color=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; backgroun=
d-color: rgba(255, 255, 255, 0);">Subject: Re: Last Call: &lt;draft-farrell-=
perpass-attack-02.txt&gt; (Pervasive Monitoring is an Attack) to Best Curren=
t Practice<br></span></font></blockquote><blockquote type=3D"cite"><font col=
or=3D"#000000"><span style=3D"-webkit-text-size-adjust: auto; background-col=
or: rgba(255, 255, 255, 0);"><br></span></font></blockquote><blockquote type=
=3D"cite"><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-=
webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">On=
 12/31/13 3:23 PM, Dave Crocker wrote:<br></span></font></blockquote></block=
quote><blockquote type=3D"cite"><blockquote type=3D"cite"><font color=3D"#00=
0000"><span style=3D"-webkit-text-size-adjust: auto; background-color: rgba(=
255, 255, 255, 0);">&nbsp;We should not approve an IETF policy statement<br>=
</span></font></blockquote></blockquote><blockquote type=3D"cite"><blockquot=
e type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size-adj=
ust: auto; background-color: rgba(255, 255, 255, 0);">until we have a good i=
dea of the way we will use it.</span></font></blockquote></blockquote><block=
quote type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size=
-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></font>=
</blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">=
I think this is a critical point and I agree quite strongly<br></span></font=
></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">=
with it. &nbsp;I've mostly been baffled by the IETF response to<br></span></=
font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span st=
yle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255,=
 0);">revelations about internet eavesdropping, to be honest,<br></span></fo=
nt></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span styl=
e=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">and it's struck me that work on some of the problems that<br></span></fo=
nt></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span styl=
e=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">need to be solved to provide better privacy guarantees (for<br></span></=
font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span st=
yle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255,=
 0);">example, fixing PKI and providing better keying) have been<br></span><=
/font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span s=
tyle=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255=
, 0);">pushed to a back burner in a scramble to make grandiose<br></span></f=
ont></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span sty=
le=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">pronouncements. &nbsp;It's not that draft-farrell is a bad<br></span></f=
ont></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span sty=
le=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0=
);">document on its own merits, it's just that I cannot for<br></span></font=
></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">=
the life of me understand what it specifically means for<br></span></font></=
blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"=
-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">w=
ork moving through the IETF process.<br></span></font></blockquote><blockquo=
te type=3D"cite"><font color=3D"#000000"><span style=3D"-webkit-text-size-ad=
just: auto; background-color: rgba(255, 255, 255, 0);"><br></span></font></b=
lockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"-=
webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);">Me=
linda<br></span></font></blockquote></div></div><div><div><div><br></div></d=
iv></div></div></body></html>=

--Apple-Mail-DF0843AC-3051-4E09-8D78-E6986DFFAD88--

From russw@riw.us  Wed Jan  1 05:56:37 2014
Return-Path: <russw@riw.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95A081AE6C3 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 05:56:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.262
X-Spam-Level: 
X-Spam-Status: No, score=0.262 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Q4NANoYyFAA for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 05:56:36 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id AC6AD1AE591 for <ietf@ietf.org>; Wed,  1 Jan 2014 05:56:35 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:49511 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:AES128-SHA256:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VyMHc-0002HB-IZ; Wed, 01 Jan 2014 13:56:28 +0000
From: "Russ White" <russw@riw.us>
To: "'Yoav Nir'" <ynir@checkpoint.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com>
In-Reply-To: <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 08:56:27 -0500
Message-ID: <02a801cf06f9$44cb20e0$ce6162a0$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQDwmmlRCqrzcengRYjHYrwgOSmqfwFXWRe7Aq8twaQAhkIKxgH3NkOqAlUijiMBdm4GVgG9AnsVAgaNTXoBNujQTpuyZFAg
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 13:56:37 -0000

> We know what to look for in a security review. We know somewhat less well,
> but in a vague way what to look for in terms of privacy. I have no idea
what to
> look for to counteract pervasive surveillance. Just as an example, let's
look at
> a particular draft, and assume that it is ready for last call, and I need
to write
> the shepherd's write-up.

A checklist of things to look for would be a useful addition to the draft,
of course. But being realistic, we need to start with something much more
generic, like:

==
- Does this protocol proposal provide for ways to hide the information being
transmitted between two parties, if applicable? 

There are some instances where this is not applicable, such as routing
protocols, or information about useable resources in CDNI. OTOH, there are
many instances where this is applicable, such as specific orders for
specific content within the CDNI realm. This question, by the way, is also a
relevant security question.

- What information must be protected in order to protect the confidentiality
of the information being transmitted on the wire (if confidentiality is
provided for in the first question)?

This is something we should be thinking about anyway, but uncovering the
assumptions is a useful exercise. Once we uncover a number of these
assumptions, we could well find a common set of things that would then
become BCPs, or impact the actual design and operation of systems.

- What risks does this protocol pose in terms of metadata for an attacker
who can access the packet flow (without specifically seeing the contents of
those packets)?

This might, at first, be speculative, but as our body of knowledge in this
area grows, we will understand how to answer this question better.

- Are there known ways for user to protect themselves against these risks?

The point of this exercise would be to expose and think about the risks at
hand first. Once we start thinking about what the risks are, maybe we can
start fashioning protections against them. Right now, since we don't have a
lot of information, it's best to start with thinking through the problem
space. Once we understand the problem space better, we can start thinking
about protection. 
==

It's useful to note that privacy and security are often (but not always)
intertwined, and to consider whether pervasive monitoring isn't just a
subset of security issues. It took years for the community to develop a
strong understanding of security. Things acceptable ten years ago are no
longer acceptable, and things acceptable today might not be acceptable in
ten years. Does that mean we give up? No. It means we start with broad
general goals, and refine those goals over time as we explore the space. But
to have that discussion, we need to decide that defense against pervasive
monitoring is a worthwhile goal -- what I'm seeing on list right now is,
"it's not a worthy goal because we don't know how to do it," and, "it's not
a worthy goal because it's a political goal." I don't agree with either line
of reasoning.

> Also, what if we can hide more information out of a protocol, but at the
> expense of another roundtrip or more processing power. Who gets to
> balance the two goals?

This same objection can be raised against data integrity, security, and even
the correctness of a routing protocol's view of the physical topology. I
could ask, "if it takes one more round trip, or a bit more processing, to
make certain there are routing loops, then who gets to balance between the
goals of no routing loops and the use of more processing power?" It's not a
silly question -- I can imagine systems with such low packet rates that
temporary routing loops with timed out packets are an acceptable solution
against sending more control plane state, or using more processor. As
another example, UDP verses TCP already makes a clear distinction between
the willingness of the protocol to lose data on the wire or not verses
additional state.

The bottom line is this: to move forward, we must start someplace. 

Russ




From abdussalambaryun@gmail.com  Wed Jan  1 06:37:09 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77A3C1AE81F for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 06:37:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BBoFmO7JJ75l for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 06:37:06 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id E0FBF1AEA77 for <ietf@ietf.org>; Wed,  1 Jan 2014 06:37:06 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id r10so13322276pdi.38 for <ietf@ietf.org>; Wed, 01 Jan 2014 06:37:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=0+sAQX8bpfD0jaXM2sO8/Cs9b1x1Et0Y+59XaaBs3/g=; b=RqxixDm8iO52ZSyDpOKVpPtOmSmUR+xFAJl4LfO0P7mRHd5uQP/8ZgmdAop928R9lf 16SK3KB/4/pxEUSpmcfUpcLpxSnVRJ/5voUe1KxpLK9HBJtlHxYwIJ8iDT+H6FaQO0QE 6SOKeAtWYzXzHe4SoX8djJSpE4Y2GyI47FRnnBpXDHH5/b/rVpdAH5okxpku+H5FwGKs jV39BpwbHeztLyjV6R3cQ6Je97RBIVvRLKr+OV+4bvIJH6SzndicePQdFLxSLoj0odVA Odav6ljWNO7E5obIRJoy7lNNuya2WjB+18o0pjAHLEYBKzcl2oZix5Afy3zn8dkPpvSo lW/g==
MIME-Version: 1.0
X-Received: by 10.68.230.137 with SMTP id sy9mr82214490pbc.126.1388587020486;  Wed, 01 Jan 2014 06:37:00 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 1 Jan 2014 06:37:00 -0800 (PST)
Date: Wed, 1 Jan 2014 15:37:00 +0100
Message-ID: <CADnDZ8--0YMvbZGnQmCCfV-U-=BhJZBYVUOezbYgnDOXP-0eMw@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Russ White <russw@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 14:37:09 -0000

On 1/1/14, Russ White <russw@riw.us> wrote:
>
.....
> The fact is that the IETF has designed a suite of protocols that are mostly
> unsecure, and widely used in a world where we're just starting to see the
> importance of security around not only your credit card number, but also
> your address book. That the IETF should make a statement saying, "we seem
> to
> have something backwards here, and it's about time we reverse our
> assumptions," isn't a political statement at all -- it's a facing of
> reality.

I agree, but we should not rush the document to IESG until we get
strong agreements from community. I commented before that the document
should be informational not BCP, becasue it should be saying as you
say, Hay we now thought about it and we think this is what we will do.
Refering why I feel some politics, is if some people still want it as
BCP with quick process even with some disagreements, then I think the
draft became political now.

> That the facing of reality has come about through any particular
> political situation shouldn't imply that the statement is generally
> political -- reacting to a political situation with a statement of a change
> in policy isn't a political reaction, nor even (necessarily) a reaction
> against the politics. Rather, it's just saying, "hey, we didn't think about
> this problem before now, but now that we've thought about it, we need to
> set
> some new goals."

I agree with you only if the draft is a statement but IMHO it is not
only statement (its unclear practical statement), therefore, this
document should be informational and not BCP, do you agree?

>
> Don't confuse the on list argument about politics with the actual point of
> the draft; they're two different things entirely.

I know they are different but the authors of the document still have
it as BCP and they are not clear of how this document will be *used*.

>
> Anyway, that's my 2c. I've read the opposing arguments, and I'm still in
> support of this draft.

So if you support, could you just state directly how this document
will be used? I understand from your message and support that you mean
I support that it is giving statement-information that we the IETF
will plan for future goals and practices, and the information will be
used to start works to find solutions, but not used into the current
IESG document review process because we still have no clear
directions.

AB

From abdussalambaryun@gmail.com  Wed Jan  1 06:37:36 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08CAD1AEA6E for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 06:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JU85b5cgFj3E for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 06:37:25 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B3D221AE81F for <ietf@ietf.org>; Wed,  1 Jan 2014 06:37:24 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so13335680pdj.29 for <ietf@ietf.org>; Wed, 01 Jan 2014 06:37:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mL+Kera3Ky9QMTC2gWvd8FqzmyDzPIjiGnorRGN8OAg=; b=vxEdeHwlLWn513Ik0NqF92t278CiPRQPjiyjteKMH9o1Z95uXRHXEf5pOFIqF1RXoR WEdA5VxiS0laeJBZPjjmKG3HwcTLxDzH7dVjkAP3nKgNRBWvi+rzkedYj9X3YlNA80VN iXzn0R0U1O1SVTi+PF9MUchfKPBtbvjGQWlkae1NktoedHqFpy9FYhszG54WfCw2ogEv o43/99n0uAXeEChti9VjzxwRHGTKRTWBBPWDe3s6ANB5UvTrUtVXtXRbEctWy3Rxrt3Y YYc0eZbSupgyAewOWiMOg73bn4Mfh1epJlN2MH0GBXvVfXk+FTvQt7ijVhhgz3TCPfn7 uUig==
MIME-Version: 1.0
X-Received: by 10.67.4.169 with SMTP id cf9mr24680494pad.45.1388587038303; Wed, 01 Jan 2014 06:37:18 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 1 Jan 2014 06:37:18 -0800 (PST)
In-Reply-To: <900C14E4-CA19-44C9-865D-5B5E44A5FE28@ietf.org>
References: <900C14E4-CA19-44C9-865D-5B5E44A5FE28@ietf.org>
Date: Wed, 1 Jan 2014 15:37:18 +0100
Message-ID: <CADnDZ88qgcQm5-2DGzGvDQNRjYg3s8m2pAVZxciT8tku3PkOvA@mail.gmail.com>
Subject: Re: 2013 review
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 14:37:36 -0000

My view (with comments) on this 2013 year related to IETF
(agreements&statements, community interest, documents&reviews),
General Area, and WGs:

For the IETF: Firstly, this year had excellent new methods introduced
for reveiwing documents which were established and more organised in
participation and review format. More new webpages for IETF areas are
organised and updated for volunteers and new/remote participants.
There are some documents with long process to become RFC which was
discussed but not evaluated.

Secondly, this year the community is interested in diversity but still
not much clear work was done in 2013, however, an assigned DT is
working on the requirements to report back may be in 2014 to the
community. This year the community discussed IESG performance and its
processing of WG documents, but still no interest clear in evaluation
from community to IESG work or no evaluation of WGs performance from
ADs.

Thirdly, this year 2013 included some statements/agreements the IETF
made with other organisation for the future progress, however, thoes
statements had many arguments which needs more work in the IETF
General Area.

For the IETF General Area: The Area is getting more involved with
community in providing more information and summarising things as this
below message with more and blogs within 2013 (from Feb 2013 Archived
until Dec, hoping to continue). Some figures of participation
statistics were published which is good for community progress. There
was also in this year more attention to help remote participation in
meetings, and also to discuss arranging meetings in other regions. The
community discussed shortage of ADs and increase in WGs, but still no
solutions. IMHO, this area is very important and needs more
organisation and improvement.

For IETF WGs: there was some individual documents sent to some related
WGs for review but still not much responses (this needs more
encouraging), and ADs or Chairs do try to mention to their WGs about
related issues in other works, but still no method for cross-WGs
involved other than AD announcements. No much interaction between IESG
and WGs, usually done through Chairs or authors, but still some times
in some issues the WG is excluded.

Wish you all the best for the new year 2014 with more volunteering
participations, new documents, new solutions, new ideas and
encouragements for IETF progress and future.

AB

On 12/31/13, IETF Chair <chair@ietf.org> wrote:
> The last day of the year seems like a good opportunity to reflect on some of
> the things that happened during 2013:
>
> http://www.ietf.org/blog/2013/12/2013-review/
>
> If you have additional thoughts or reflections on the past year - please
> share them!
>
> Jari
>
>

From russw@riw.us  Wed Jan  1 07:20:35 2014
Return-Path: <russw@riw.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E46B1AE31D for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 07:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y7zo51EGIzLr for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 07:20:33 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1805E1AE2A6 for <ietf@ietf.org>; Wed,  1 Jan 2014 07:20:25 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:52173 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:AES128-SHA256:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VyNak-0002nr-4C; Wed, 01 Jan 2014 15:20:18 +0000
From: "Russ White" <russw@riw.us>
To: "'Abdussalam Baryun'" <abdussalambaryun@gmail.com>
References: <CADnDZ8--0YMvbZGnQmCCfV-U-=BhJZBYVUOezbYgnDOXP-0eMw@mail.gmail.com>
In-Reply-To: <CADnDZ8--0YMvbZGnQmCCfV-U-=BhJZBYVUOezbYgnDOXP-0eMw@mail.gmail.com>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 10:20:16 -0500
Message-ID: <007901cf0704$fa526080$eef72180$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJA8MJAvQ/iu0sPybWI/NAe7pdam5mMJUGA
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 15:20:35 -0000

> I agree with you only if the draft is a statement but IMHO it is not only
> statement (its unclear practical statement), therefore, this document
should
> be informational and not BCP, do you agree?

The difference, to me, is between saying:

- We'd really like to tell people about this.
- We're laying a foundation to do something in this space.

So, how do I think this document will be *used?*

As a starting point. I've recommended some specific thoughts on questions to
draft authors to include in another email. I don't think these are the
"final" questions, nor do I think they need to be included for this initial
version to go to BCP -- so long as we understand this is a goal statement
which will have more information added in the bis and update processes.
Since our knowledge of this space will naturally grow over time, I suspect
this document will change over time, just as id-nits, security requirements,
and other such documents have.

There might be a lot of other "better ways," to go about this -- start a WG,
etc. -- but this is the immediately apparent vehicle for the moment. So
given the choice of doing nothing, "because we don't have a detailed
accounting of everything we'd like to do," or, "because this is political,
rather than technical," and passing this document into BCP status so a
conversation is started, and we think about the right direction from here --
I'd rather pass this document into BCP status so we can think about the
right direction to go from here.

Russ


From dhc@dcrocker.net  Wed Jan  1 07:46:50 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37B5A1AE33E for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 07:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znAyH-_Pdvcf for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 07:46:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0034F1AE336 for <ietf@ietf.org>; Wed,  1 Jan 2014 07:46:48 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s01FkbLY028718 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 Jan 2014 07:46:41 -0800
Message-ID: <52C43804.9080708@dcrocker.net>
Date: Wed, 01 Jan 2014 07:45:08 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@lear.ch>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <52C3A9D2.2090509@gmail.com> <290E20B455C66743BE178C5C84F1240847E51037C7@EXMB01CMS.surrey.ac.uk> <94CB7C32-46E2-47D8-BD38-9BAC4D545A85@cisco.com> <43521858-7A9E-4FE1-A0A9-BB608599BFC6@lear.ch>
In-Reply-To: <43521858-7A9E-4FE1-A0A9-BB608599BFC6@lear.ch>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 01 Jan 2014 07:46:42 -0800 (PST)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Jan 2014 15:46:50 -0000

On 1/1/2014 4:08 AM, Eliot Lear wrote:
> As to whether this draft is political, it cannot be stressed enough that
> if one group of people can subvert our architecture, others can as well.
> Our political statement, such as it is, is that in order to maintain
> confidence in the Internet, our protocol suite should be resistant to
> this sort of thing, but within the bounds of pragmatism.


Let me suggest that this is exactly the wrong way to talk about the 
issue, in the IETF.  Again, it's not that the statement is wrong, but 
that it is not the way engineers need to approach work.

Here's engineering phrasing that gets us doing the same work, but 
without worrying about the human factor of "confidence".  That is, it 
uses phrasing that matches all the other work we do, rather than placing 
us into some sort of social protection task:

      There is a substantial community in the Internet wishing to have 
its data and activities protected against pervasive monitoring.  The 
IETF needs to design specifications and practices (existing and new) 
with the means to ensure such protection.

Another reason of why we should stay out of the more exciting language 
about pervasive monitoring is that it leads us into making technical 
statements that are wrong.  Pervasive monitoring has not 'subverted' any 
architecture.  It has simply taken advantage of holes in the architecture.

There is a strong market request that we close those holes.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From agmalis@gmail.com  Wed Jan  1 08:49:09 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279C91AE63B for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 08:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qrtJSphBhRTf for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 08:49:07 -0800 (PST)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 977911AE63A for <ietf@ietf.org>; Wed,  1 Jan 2014 08:49:07 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id r5so13109824qcx.0 for <ietf@ietf.org>; Wed, 01 Jan 2014 08:49:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=QxcmL4wAYAjoxX8dhHBaksX0TAWU4JUodp7jmucms10=; b=AtkYFe9zZN8pfCO8wgyv102/veLtvz0CbWwtnmq/spAgqHzW92U+7FCgFErrAKuwf/ fh9nlylNmtrtQObT4j5XnmIVyoJhG0DwvY3ga7CH8ddeNv09wXH2xRDibJ/WSEbNkohU bqrEcVgK4GfwnjHhDsZo0RjgyJqgXJiVcZRyi/xg8fqHhO7Uo6CY0F0e3owlVIeZvPIP VTybdnFCjrFiPpkLy6qgOljAC1ZIsNtX1bNmmNDYrQwzRgMbcpXPMj2mfCZ1rdbHgDkk ki7kiYbxnnTuFz5ghjM4n/H+VLA5ZJWYWUyOxEdYU/6+uev6glCOyjT2rTsGs65wYjw6 QNDA==
X-Received: by 10.49.86.169 with SMTP id q9mr132524064qez.19.1388594940791; Wed, 01 Jan 2014 08:49:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Wed, 1 Jan 2014 08:48:40 -0800 (PST)
In-Reply-To: <CADnDZ88qgcQm5-2DGzGvDQNRjYg3s8m2pAVZxciT8tku3PkOvA@mail.gmail.com>
References: <900C14E4-CA19-44C9-865D-5B5E44A5FE28@ietf.org> <CADnDZ88qgcQm5-2DGzGvDQNRjYg3s8m2pAVZxciT8tku3PkOvA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 1 Jan 2014 11:48:40 -0500
Message-ID: <CAA=duU0-1phdk+Piv0S=EHPZ9s9-Lx5m_o1OE6KjPJSvg5MgbA@mail.gmail.com>
Subject: Re: 2013 review
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 16:49:09 -0000

On Wed, Jan 1, 2014 at 9:37 AM, Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:
> For IETF WGs: there was some individual documents sent to some related
> WGs for review but still not much responses (this needs more
> encouraging), and ADs or Chairs do try to mention to their WGs about
> related issues in other works, but still no method for cross-WGs
> involved other than AD announcements. No much interaction between IESG
> and WGs, usually done through Chairs or authors, but still some times
> in some issues the WG is excluded.


I personally think this is a WG-by-WG issue, and a lot rests on the
efforts of the ADs and relevant WG chairs to make sure that issues of
joint interest get cross-pollinated between WGs. There's been a lot of
work done in the routing area by the ADs and WG chairs to make sure
that WG participants are aware of related drafts or issues in other
WGs in the area. I agree that in general, cross-area interaction could
use a lot of work.

Cheers,
Andy

From john-ietf@jck.com  Wed Jan  1 08:52:52 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A521AE63A for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 08:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cR2aJ9hY8oBw for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 08:52:51 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B02D21AE328 for <ietf@ietf.org>; Wed,  1 Jan 2014 08:52:51 -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 1VyP22-000Ipl-Qf; Wed, 01 Jan 2014 11:52:34 -0500
Date: Wed, 01 Jan 2014 11:52:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: Russ White <russw@riw.us>, 'Yoav Nir' <ynir@checkpoint.com>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Message-ID: <378D6420CA2FBFD6FB34E2DC@JcK-HP8200.jck.com>
In-Reply-To: <02a801cf06f9$44cb20e0$ce6162a0$@riw.us>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <02a801cf06f9$44cb20e0$ce6162a0$@riw.us>
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 16:52:53 -0000

Russ and others,

Just as an example of where we get ourselves sideways in talking
about what the draft says and means...

--On Wednesday, January 01, 2014 08:56 -0500 Russ White
<russw@riw.us> wrote:

> ==
> - Does this protocol proposal provide for ways to hide the
> information being transmitted between two parties, if
> applicable? 

That isn't what it says.  By saying "hide", you are accidentally
making the same encryption or encryption-like assumption I made.
For the reasons you give below, I think that assumption is
usually reasonable, but I think we really mean "ways to make the
information hard to intercept and interpret" or which "hidden"
is only one family of techniques.  For those who know the story
and with apologies to those who don't, "how is your Navajo"?

> There are some instances where this is not applicable, such as
> routing protocols, or information about useable resources in
> CDNI. OTOH, there are many instances where this is applicable,
> such as specific orders for specific content within the CDNI
> realm. This question, by the way, is also a relevant security
> question.

Indeed.
    john





From john-ietf@jck.com  Wed Jan  1 09:13:10 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169761AE673 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 09:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2ZRhE-l1AEL for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 09:13:08 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 819591AE105 for <ietf@ietf.org>; Wed,  1 Jan 2014 09:13:08 -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 1VyPLh-000IrE-Gu; Wed, 01 Jan 2014 12:12:53 -0500
Date: Wed, 01 Jan 2014 12:12:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Message-ID: <CF99BC4DD9545AB43BBAB194@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 17:13:10 -0000

Another message from the 11-12 December thread, then I'm going
to try to crawl back out of this and get some work done...

--On Thursday, December 12, 2013 15:20 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> If it is, then it would seem to call for "ubiquitous
>> confidentiality" unless you are making a very fine point.
> 
> Indeed it is making a fine point - what it calls for is the
> IETF to provide technological mechanisms that allow operators
> and users to protect privacy. To what extent those mechanisms
> are deployed is not under the IETF's control and will
> presumably vary between countries.

Brian,

I'm sorry, but, beyond a certain point, that sets you (and us)
up for a position that has an extremely poor ethical (and
engineering) history.  The worst examples take us straight to
various principles that have names but "we just invented this
technology, you can't blame us for how it was used or its
consequences" is perhaps the least negative of them of those
examples.  It is also, at least IMO, bad engineering because
good engineering has to consider the entire constraint space and
system, even if the constraints are economic or social and not
just physics.

Worse, we are already more than halfway into the sociopolitical
side of the problem by even getting started in this discussion.
Even there may be some associated technical problems and
opportunities, privacy isn't a technical problem either.  More
important, the expectation of privacy isn't a technical problem;
we create a technical problem only when we assume that
expectation and its reasonableness.   I happen to disagree with
those who say "ok, it can be ignored" or "any expectation of
privacy has become unreasonable" and assume you do too, but,
when I complain about pain when I try to perform particular
actions, my physician is fond of saying "so don't do that".  If
one really has no expectation of privacy, then there is no
technical or other problem with surveillance, pervasive or
otherwise.  To go as far as we are going and then appeal to "not
a technical problem" or, worse, ethical imperatives about the
consequences of how our work is applied is, to be polite,
disingenuous.


best,
    john






From randy@psg.com  Wed Jan  1 10:03:56 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A46E1AE3C1 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 10:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6S2JZkFmc5AK for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 10:03:55 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 49B321AE376 for <ietf@ietf.org>; Wed,  1 Jan 2014 10:03:55 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VyQ8w-0007br-FB for ietf@ietf.org; Wed, 01 Jan 2014 18:03:47 +0000
Date: Wed, 01 Jan 2014 08:03:45 -1000
Message-ID: <m2ob3vpoji.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-Reply-To: <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>
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: multipart/signed; boundary="pgp-sign-Multipart_Wed_Jan__1_08:03:40_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 18:03:56 -0000

--pgp-sign-Multipart_Wed_Jan__1_08:03:40_2014-1
Content-Type: text/plain; charset=US-ASCII

the violations of trust in the internet are on the front page every day
for months.  but we don't need no stinkin' policy or architectural
response.  we just need a mailing list on which to blather endlessly
while rome burns.

what are you gonna do to make the internet a better and safer place
today?

randy


--pgp-sign-Multipart_Wed_Jan__1_08:03:40_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJSxFiAAAoJEMzMBey4OgLtELQH/jcuoQEQwz1DPHK/4h7XmJEh
PGnu9wX9ygl8ZLZwGfu3hVXosBajokl7cTQvwOiXi2e9i1VsdPKeTxoGx6mNMVLv
kElZlepMVoRMs2sb96I5xYQHDCORFwmVnuqEhlU+b2Sth2xmo2klAKyYppZrv/5q
AQ5IJNRV4HXsznx7RloJAz3xkfNRevtEZ6jLYoeZjhf2eLIZZ5rzbaWyrBBHrp7t
o2Z8Vdfyl7FNPSGLY4nWqFtvI7g2Mga2x7VUubZEPgQRQFXYnZUa7svVpwa10aAp
l+xgAEhgnuMFZ+fQ03dYHI2XYIzdwqPPQ/JjYHZ6ePBWuqwOrTZhNIVQVsm91Ec=
=k31y
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Wed_Jan__1_08:03:40_2014-1--

From tbray@textuality.com  Wed Jan  1 11:01:43 2014
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241761AE971 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65d7CHRw21tj for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:01:40 -0800 (PST)
Received: from mail-la0-f53.google.com (mail-la0-f53.google.com [209.85.215.53]) by ietfa.amsl.com (Postfix) with ESMTP id 3ACB21AE96C for <ietf@ietf.org>; Wed,  1 Jan 2014 11:01:40 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id mc6so6795774lab.40 for <ietf@ietf.org>; Wed, 01 Jan 2014 11:01:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=35lsI/QoTFheXY4UY8n3C1nKIbqX4uSN1xxW5+Z7vzA=; b=CyZnrlFiH9ObBaytMOpbFft4A1DKDWo9uuUbkBJPNWajL0yQXsbmqSv/y0VOFpgo99 eBakOde81abgGEeIP4ZZo37hj7i86gI92JHeOcxS/iQsqMt3Dua6jriYGkZhzyMKcuxy gF/b0ZYY25ZlgD+5bdMkRI6JIv7WofBZmIhsuCQ4yCdu11mDLCw9D0OcffAEKty2p4+o bYB4Tl2yNLFoQG/FiWLl8grzKn7Zor8yJB1m/AonYxFyOx1yEKh/RDwjYUmx/owCxrSP OpcHN7xKTPAl009TP6g9HTrp/eYlj4egcuPFUaQvl9kr4fDuvjL/U4z0+ht4r7LEsFVa EONA==
X-Gm-Message-State: ALoCoQk/xsVfZSw4Sy6qnLISVgQfRY079dn5CBNz4Is5Dp+KZUCFmH72WvLOye2xoOrfy8by2tPE
MIME-Version: 1.0
X-Received: by 10.152.36.101 with SMTP id p5mr1261432laj.67.1388602892866; Wed, 01 Jan 2014 11:01:32 -0800 (PST)
Received: by 10.114.24.6 with HTTP; Wed, 1 Jan 2014 11:01:32 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <m2ob3vpoji.wl%randy@psg.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <m2ob3vpoji.wl%randy@psg.com>
Date: Wed, 1 Jan 2014 11:01:32 -0800
Message-ID: <CAHBU6iuyMiLcRNS1Oc0xkZ=Rd2WoquE9b8fxexvO3QyJub26nQ@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Tim Bray <tbray@textuality.com>
To: Eliot Lear <lear@lear.ch>
Content-Type: multipart/alternative; boundary=089e0158b5bc29e64f04eeed4e0e
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 19:01:43 -0000

--089e0158b5bc29e64f04eeed4e0e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 1, 2014 at 4:08 AM, Eliot Lear <lear@lear.ch> wrote:

If, on the other hand, developers of a specification discussed the matter
> in earnest and there was consensus on the way forward, even if some
> pervasive threats were not eliminated, and if that work is held up by
> claims relating to this draft, then this draft will have caused harm.
>

This paragraph seems ridiculous to me.  The perpass-attack draft says that
pervasive monitoring has the characteristics of an attack, and that the
protocols we design SHOULD include appropriate mitigation measures. I quote
from the draft:

  "Mitigation" is a technical term that does not imply an ability to
completely prevent or thwart an attack.

There are very few (any?) absolutes in any of the protocols we build, just
a wealth of often-conflicting design criteria, which force us to trade off
and make judgment calls.  draft-perpass-attack says that mitigation of
pervasive surveillance should be seen as one of the design criteria, and
it=E2=80=99s not OK to ignore it. A reasonable take is that a specification=
 could
be held up if there are plausible arguments that this criterion has not
been given appropriate consideration, and I see nothing wrong with that.
Similar hold-ups regularly occur when there are concerns that there hasn=E2=
=80=99t
been appropriate consideration for efficiency or error-handling or, well,
lots of other criteria.





>
>
> That is nothing more or less than common sense.
>
> As to whether this draft is political, it cannot be stressed enough that
> if one group of people can subvert our architecture, others can as well.
> Our political statement, such as it is, is that in order to maintain
> confidence in the Internet, our protocol suite should be resistant to thi=
s
> sort of thing, but within the bounds of pragmatism.
>
> Eliot
>
> On Jan 1, 2014, at 6:08 AM, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
> wrote:
>
>
> what it means for work moving through the IETF process
>
> is that any work becomes subject to security veto.
>
>
> if security types don't like your work - tough. it's
>
> going nowhere. draft-farrell really widens that scope.
>
> and this is going to mean arguments about
>
> much more than the tradeoffs of using MD5.
>
>
> for a self-described technical organisation that
>
> does not make policy pronouncements (which is
>
> itself a very political position, but never mind)
>
> this draft is awfully political.
>
>
> Lloyd Wood
>
> http://about.me/lloydwood
>
> ________________________________________
>
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Melinda Shore [
> melinda.shore@gmail.com]
>
> Sent: 01 January 2014 05:38
>
> To: ietf@ietf.org
>
> Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive
> Monitoring is an Attack) to Best Current Practice
>
>
> On 12/31/13 3:23 PM, Dave Crocker wrote:
>
>  We should not approve an IETF policy statement
>
> until we have a good idea of the way we will use it.
>
>
> I think this is a critical point and I agree quite strongly
>
> with it.  I've mostly been baffled by the IETF response to
>
> revelations about internet eavesdropping, to be honest,
>
> and it's struck me that work on some of the problems that
>
> need to be solved to provide better privacy guarantees (for
>
> example, fixing PKI and providing better keying) have been
>
> pushed to a back burner in a scramble to make grandiose
>
> pronouncements.  It's not that draft-farrell is a bad
>
> document on its own merits, it's just that I cannot for
>
> the life of me understand what it specifically means for
>
> work moving through the IETF process.
>
>
> Melinda
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jan 1, 2014 at 4:08 AM, Eliot Lear <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:lear@lear.ch" target=3D"_blank">lear@lear.ch</a>&gt;</span> wrote:</div=
><div class=3D"gmail_quote">

<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:sol=
id;padding-left:1ex"><div dir=3D"auto"><div><span></span></div><div><div><d=
iv>
<span style=3D"background-color:rgba(255,255,255,0)">If, on the other hand,=
 developers of a specification discussed the matter in earnest and there wa=
s consensus on the way forward, even if some pervasive threats were not eli=
minated, and if that work is held up by claims relating to this draft, then=
 this draft will have caused harm.</span></div>

</div></div></div></blockquote><div><br></div><div>This paragraph seems rid=
iculous to me. =C2=A0The perpass-attack draft says that pervasive monitorin=
g has the characteristics of an attack, and that the protocols we design SH=
OULD include appropriate mitigation measures. I quote from the draft:=C2=A0=
</div>
<div><br></div><div>=C2=A0 &quot;Mitigation&quot; is a technical term that =
does not imply an ability to completely prevent or thwart an attack.</div><=
div><br></div><div>There are very few (any?) absolutes in any of the protoc=
ols we build, just a wealth of often-conflicting design criteria, which for=
ce us to trade off and make judgment calls. =C2=A0draft-perpass-attack says=
 that mitigation of pervasive surveillance should be seen as one of the des=
ign criteria, and it=E2=80=99s not OK to ignore it. A reasonable take is th=
at a specification could be held up if there are plausible arguments that t=
his criterion has not been given appropriate consideration, and I see nothi=
ng wrong with that. Similar hold-ups regularly occur when there are concern=
s that there hasn=E2=80=99t been appropriate consideration for efficiency o=
r error-handling or, well, lots of other criteria.=C2=A0</div>
<div><br></div><div><br></div><div><br></div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1=
ex">
<div dir=3D"auto"><div><div><div><br></div><div><font color=3D"#000000"><sp=
an style=3D"background-color:rgba(255,255,255,0)"><br>That is nothing more =
or less than common sense.<br><br>As to whether this draft is political, it=
 cannot be stressed enough that if one group of people can subvert our arch=
itecture, others can as well. Our political statement, such as it is, is th=
at in order to maintain confidence in the Internet, our protocol suite shou=
ld be resistant to this sort of thing, but within the bounds of pragmatism.=
=C2=A0<span><font color=3D"#888888"><br>

<br></font></span></span></font><span><font color=3D"#888888"><div>Eliot</d=
iv></font></span><div><div><div><br></div><blockquote type=3D"cite"><font c=
olor=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)">On Ja=
n 1, 2014, at 6:08 AM, &quot;<a href=3D"mailto:l.wood@surrey.ac.uk" target=
=3D"_blank">l.wood@surrey.ac.uk</a>&quot; &lt;<a href=3D"mailto:l.wood@surr=
ey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk</a>&gt; wrote:<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)"><br></span></font></=
blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"background-color:rgba(255,255,255,0)">what it means for work moving throug=
h the IETF process<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">is that any work bec=
omes subject to security veto.<br></span></font></blockquote><blockquote ty=
pe=3D"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
"><br></span></font></blockquote><blockquote type=3D"cite"><font color=3D"#=
000000"><span style=3D"background-color:rgba(255,255,255,0)">if security ty=
pes don&#39;t like your work - tough. it&#39;s<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">going nowhere. draft=
-farrell really widens that scope.<br></span></font></blockquote><blockquot=
e type=3D"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
">and this is going to mean arguments about<br></span></font></blockquote><=
blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"background-=
color:rgba(255,255,255,0)">much more than the tradeoffs of using MD5.<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)"><br></span></font></=
blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"background-color:rgba(255,255,255,0)">for a self-described technical organ=
isation that<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">does not make policy=
 pronouncements (which is<br></span></font></blockquote><blockquote type=3D=
"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
">itself a very political position, but never mind)<br></span></font></bloc=
kquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"bac=
kground-color:rgba(255,255,255,0)">this draft is awfully political.<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)"><br></span></font></=
blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=3D=
"background-color:rgba(255,255,255,0)">Lloyd Wood<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)"><a href=3D"http://ab=
out.me/lloydwood" target=3D"_blank">http://about.me/lloydwood</a><br></span=
></font></blockquote>

<blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"background=
-color:rgba(255,255,255,0)">________________________________________<br></s=
pan></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><=
span style=3D"background-color:rgba(255,255,255,0)">From: ietf [<a href=3D"=
mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.org</a>] =
On Behalf Of Melinda Shore [<a href=3D"mailto:melinda.shore@gmail.com" targ=
et=3D"_blank">melinda.shore@gmail.com</a>]<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">Sent: 01 January 201=
4 05:38<br></span></font></blockquote><blockquote type=3D"cite"><font color=
=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)">To:=C2=A0=
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">Subject: Re: Last Ca=
ll: &lt;draft-farrell-perpass-attack-02.txt&gt; (Pervasive Monitoring is an=
 Attack) to Best Current Practice<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)"><br></span></font></=
blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><font color=
=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)">On 12/31/=
13 3:23 PM, Dave Crocker wrote:<br>

</span></font></blockquote></blockquote><blockquote type=3D"cite"><blockquo=
te type=3D"cite"><font color=3D"#000000"><span style=3D"background-color:rg=
ba(255,255,255,0)">=C2=A0We should not approve an IETF policy statement<br>=
</span></font></blockquote>

</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><font colo=
r=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)">until we=
 have a good idea of the way we will use it.</span></font></blockquote></bl=
ockquote>

<blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"background=
-color:rgba(255,255,255,0)"><br></span></font></blockquote><blockquote type=
=3D"cite"><font color=3D"#000000"><span style=3D"background-color:rgba(255,=
255,255,0)">I think this is a critical point and I agree quite strongly<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">with it. =C2=A0I&#39=
;ve mostly been baffled by the IETF response to<br></span></font></blockquo=
te><blockquote type=3D"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
">revelations about internet eavesdropping, to be honest,<br></span></font>=
</blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span style=
=3D"background-color:rgba(255,255,255,0)">and it&#39;s struck me that work =
on some of the problems that<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">need to be solved to=
 provide better privacy guarantees (for<br></span></font></blockquote><bloc=
kquote type=3D"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
">example, fixing PKI and providing better keying) have been<br></span></fo=
nt></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span sty=
le=3D"background-color:rgba(255,255,255,0)">pushed to a back burner in a sc=
ramble to make grandiose<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">pronouncements. =C2=
=A0It&#39;s not that draft-farrell is a bad<br></span></font></blockquote><=
blockquote type=3D"cite">

<font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)=
">document on its own merits, it&#39;s just that I cannot for<br></span></f=
ont></blockquote><blockquote type=3D"cite"><font color=3D"#000000"><span st=
yle=3D"background-color:rgba(255,255,255,0)">the life of me understand what=
 it specifically means for<br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">work moving through =
the IETF process.<br></span></font></blockquote><blockquote type=3D"cite"><=
font color=3D"#000000"><span style=3D"background-color:rgba(255,255,255,0)"=
><br>

</span></font></blockquote><blockquote type=3D"cite"><font color=3D"#000000=
"><span style=3D"background-color:rgba(255,255,255,0)">Melinda<br></span></=
font></blockquote></div></div></div></div><div><div><div><br></div></div></=
div>

</div></div></blockquote></div><br></div></div>

--089e0158b5bc29e64f04eeed4e0e--

From brian.e.carpenter@gmail.com  Wed Jan  1 11:15:43 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7E11AE8E1 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:15:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yY6FsY9lsXPF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:15:41 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id F15AC1AE674 for <ietf@ietf.org>; Wed,  1 Jan 2014 11:15:40 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so13481635pdj.29 for <ietf@ietf.org>; Wed, 01 Jan 2014 11:15:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=QeO4KvHbMEtJVMoj46RqC4uBKXekS4NJsqME4szCT08=; b=Uir7osiwyJC2fcoxF8l+Hga2NGmM6MBciL8gwzqM013GlOp36cafvTzqJUd6A0IBtF Ki6cLZbA2TNITcZxVGH3dIgtdcLiXEOlcqRzweCVkxUhlkHP/gMe+Y4lc5cstuOH9vmS hCwy1vDSDTywEG8pGGVoWYuLz3JmqdBJ6zvnEoPQtwL6R2964VlV76LFX5cA0FGuQ5SJ an1ftSWMwE6hYa+wygbTkItL3bH0oDWcFFGKCW3vTOOGY0OfTBE76ZT+iDcklCjj+kJ6 Wq0Q03p99Gx3BsafbEMa0bX+AY/Joi0umw2641wv7+4g1CMei4Dc9EJ4/2rVg/8a20Au aIog==
X-Received: by 10.68.164.4 with SMTP id ym4mr37823372pbb.53.1388603734518; Wed, 01 Jan 2014 11:15:34 -0800 (PST)
Received: from [192.168.178.21] (137.199.69.111.dynamic.snap.net.nz. [111.69.199.137]) by mx.google.com with ESMTPSA id un5sm34766843pab.3.2014.01.01.11.15.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 11:15:33 -0800 (PST)
Message-ID: <52C46959.3080905@gmail.com>
Date: Thu, 02 Jan 2014 08:15:37 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com>
In-Reply-To: <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 19:15:43 -0000

On 02/01/2014 00:41, Yoav Nir wrote:
> On Jan 1, 2014, at 12:32 PM, Russ White <russw@riw.us> wrote:
> 
>>>      We should not approve an IETF policy statement
>>>     until we have a good idea of the way we will use it.
>> I'm struggling a bit with this statement -- it seems just as broad as the
>> draft under discussion, and just as much of a "policy" as the draft under
>> discussion.
>>
>> What does a "good idea," actually mean? 
> 
> I guess a "good idea" would be a checklist for document authors, document shepherds, and IESG members on what they need to consider in a document to ascertain whether it complies with this BCP nn. 

IMHO that is exactly the wrong goal for this draft, which is a statement of
aspiration. I would expect the checklist to come from much more technical
documents to be developed over time.

I'm close to concluding that the present draft should not be a BCP at all,
just as RFC 1984 and RFC 2804 were not BCPs. Since it is derived from an
IAB-organised plenary, why not just make it an IAB stream Informational
document co-signed by the IESG? (With a few cosmetic text changes.)
Just get it published so that we can do the real work, as Randy says.

   Brian

> We know what to look for in a security review. We know somewhat less well, but in a vague way what to look for in terms of privacy. I have no idea what to look for to counteract pervasive surveillance. Just as an example, let's look at a particular draft, and assume that it is ready for last call, and I need to write the shepherd's write-up.
> 
> I'll choose draft-ietf-httpauth-hoba-02.
> 
> The draft is about an authentication method for HTTP, where an asymmetric per-origin key pair is used to authenticate the user (or rather, the user agent) to an HTTP server. 
> 
> So now we have to make assumptions about our pervasive surveyor (is that the word?):
>  1. Can they decrypt TLS? 
>  2. Can they see the plaintext of the authentication process?
>  3. Can they see the plaintext of the registration process?
>  4. Can they retrieve the public key database at the server?
>  5. Can they plant entries in the public key database, using perhaps the procedure in section 6.2, allowing them to impersonate the user?
> 
> If they can do #1, they may be able to do #2 and #3, and then #4 is superfluous. If they have access to the public key (through #3 or #4) and access to the authentication plaintext (#2) then they can track where the user is logging in from. 
> 
> There are so many capabilities we can imagine that the nation state adversary may have, and we only have a vague notion of what information must be prevented from leaking to such an adversary. I don't think that I can check a document to make sure it won't be smacked down in IETF LC or at the IESG for not complying with BCP nn.
> 
> Also, what if we can hide more information out of a protocol, but at the expense of another roundtrip or more processing power. Who gets to balance the two goals?
> 
> Yoav
> 
> 
> 

From brian.e.carpenter@gmail.com  Wed Jan  1 11:28:37 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817E51AEA3B for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:28:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izVntJh0_4v2 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 11:28:35 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 23E571AEA3C for <ietf@ietf.org>; Wed,  1 Jan 2014 11:28:35 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id kq14so13832588pab.20 for <ietf@ietf.org>; Wed, 01 Jan 2014 11:28:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XRKWhPLFijr9fLD3B+rsTItWGuBW0M80BRLCoKVkbgk=; b=OAhA3KCy3fL1J11QHkLMyEF+mhHNes54s782c52HddGYljx8QC22PjPOxjgW+7tF8U KwpUjlny1j84QSDKFplvczJn3B+3ByQL9mn1kIrK6be8WM2Q45SSlU8XeTudinkPvuPH MnYW56bA0796eiwP/RSlPtclj1kXWrZH0SSHt0sTHdZeMO4rM+awpuRrBkHItgO1bMwv Z8Xj3ic0VOPR6B8DHRCql9wjzyvp5pUPH+aNEwzThgrOM0lXn19jggFS8A4dSey0fr8r g6BA+zcqPZ3BQtepmmtlwPqBMwiHVzajKIDs3QqjIK8rWXE872GXoJ1jZawCo4bPQiDT I4Ug==
X-Received: by 10.68.244.2 with SMTP id xc2mr84156834pbc.58.1388604508614; Wed, 01 Jan 2014 11:28:28 -0800 (PST)
Received: from [192.168.178.21] (137.199.69.111.dynamic.snap.net.nz. [111.69.199.137]) by mx.google.com with ESMTPSA id g6sm126782036pat.2.2014.01.01.11.28.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 11:28:27 -0800 (PST)
Message-ID: <52C46C5F.9090400@gmail.com>
Date: Thu, 02 Jan 2014 08:28:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <CF99BC4DD9545AB43BBAB194@JcK-HP8200.jck.com>
In-Reply-To: <CF99BC4DD9545AB43BBAB194@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 19:28:37 -0000

On 02/01/2014 06:12, John C Klensin wrote:
> Another message from the 11-12 December thread, then I'm going
> to try to crawl back out of this and get some work done...
> 
> --On Thursday, December 12, 2013 15:20 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>>> If it is, then it would seem to call for "ubiquitous
>>> confidentiality" unless you are making a very fine point.

>> Indeed it is making a fine point - what it calls for is the
>> IETF to provide technological mechanisms that allow operators
>> and users to protect privacy. To what extent those mechanisms
>> are deployed is not under the IETF's control and will
>> presumably vary between countries.
> 
> Brian,
> 
> I'm sorry, but, beyond a certain point, that sets you (and us)
> up for a position that has an extremely poor ethical (and
> engineering) history.  The worst examples take us straight to
> various principles that have names but "we just invented this
> technology, you can't blame us for how it was used or its
> consequences" is perhaps the least negative of them of those
> examples.  

That might depend on how one feels about Mikhail Kalashnikov's defence:
("It is not my fault that the Kalashnikov was used in many troubled places.
I think the policies of these countries are to blame, not the designers.")
But I think you're over-interpreting my words. All IETF standards
are voluntary, so anything we specify that protects privacy is
also voluntary and we can't force people to use it.

> It is also, at least IMO, bad engineering because
> good engineering has to consider the entire constraint space and
> system, even if the constraints are economic or social and not
> just physics.

I can't disagree. Unfortunately the constraint space includes
jurisdictions with things like FISA courts or worse.

> Worse, we are already more than halfway into the sociopolitical
> side of the problem by even getting started in this discussion.
> Even there may be some associated technical problems and
> opportunities, privacy isn't a technical problem either.  More
> important, the expectation of privacy isn't a technical problem;
> we create a technical problem only when we assume that
> expectation and its reasonableness.   I happen to disagree with
> those who say "ok, it can be ignored" or "any expectation of
> privacy has become unreasonable" and assume you do too, but,
> when I complain about pain when I try to perform particular
> actions, my physician is fond of saying "so don't do that".  If
> one really has no expectation of privacy, then there is no
> technical or other problem with surveillance, pervasive or
> otherwise.  To go as far as we are going and then appeal to "not
> a technical problem" or, worse, ethical imperatives about the
> consequences of how our work is applied is, to be polite,
> disingenuous.

Yes. All I intended was to be realistic: whatever we specify,
we can't prevent people ignoring it. I think we have a lot of
running code proof of that.

    Brian

From stephen.farrell@cs.tcd.ie  Wed Jan  1 12:10:05 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F01F1A1F55 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:10:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAgeYRptFM3s for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:10:02 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C3F081A1F54 for <ietf@ietf.org>; Wed,  1 Jan 2014 12:10:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 7EA9BBE5F; Wed,  1 Jan 2014 20:09:53 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3e8TS0jHOEBV; Wed,  1 Jan 2014 20:09:52 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 30F03BE58; Wed,  1 Jan 2014 20:09:52 +0000 (GMT)
Message-ID: <52C47605.9070607@cs.tcd.ie>
Date: Wed, 01 Jan 2014 20:09:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Yoav Nir <ynir@checkpoint.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com>
In-Reply-To: <52C46959.3080905@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 20:10:05 -0000

(While still on holiday...)

On 01/01/2014 07:15 PM, Brian E Carpenter wrote:
> On 02/01/2014 00:41, Yoav Nir wrote:
>> On Jan 1, 2014, at 12:32 PM, Russ White <russw@riw.us> wrote:
>>
>>>>      We should not approve an IETF policy statement
>>>>     until we have a good idea of the way we will use it.
>>> I'm struggling a bit with this statement -- it seems just as broad as the
>>> draft under discussion, and just as much of a "policy" as the draft under
>>> discussion.
>>>
>>> What does a "good idea," actually mean? 
>>
>> I guess a "good idea" would be a checklist for document authors, document shepherds, and IESG members on what they need to consider in a document to ascertain whether it complies with this BCP nn. 
> 
> IMHO that is exactly the wrong goal for this draft, which is a statement of
> aspiration. I would expect the checklist to come from much more technical
> documents to be developed over time.
> 
> I'm close to concluding that the present draft should not be a BCP at all,
> just as RFC 1984 and RFC 2804 were not BCPs. Since it is derived from an
> IAB-organised plenary, why not just make it an IAB stream Informational
> document co-signed by the IESG? (With a few cosmetic text changes.)
> Just get it published so that we can do the real work, as Randy says.

I disagree. I think if we constantly desist in taking any action
because there are inevitably a number of nay-sayers, then we've
lost. And in this particular case, a BCP is exactly the right thing.
(I'll respond in more detail tomorrow, but do have to say that
there looks to be a lot of repetition in the last day's mails.)

S.

> 
>    Brian
> 
>> We know what to look for in a security review. We know somewhat less well, but in a vague way what to look for in terms of privacy. I have no idea what to look for to counteract pervasive surveillance. Just as an example, let's look at a particular draft, and assume that it is ready for last call, and I need to write the shepherd's write-up.
>>
>> I'll choose draft-ietf-httpauth-hoba-02.
>>
>> The draft is about an authentication method for HTTP, where an asymmetric per-origin key pair is used to authenticate the user (or rather, the user agent) to an HTTP server. 
>>
>> So now we have to make assumptions about our pervasive surveyor (is that the word?):
>>  1. Can they decrypt TLS? 
>>  2. Can they see the plaintext of the authentication process?
>>  3. Can they see the plaintext of the registration process?
>>  4. Can they retrieve the public key database at the server?
>>  5. Can they plant entries in the public key database, using perhaps the procedure in section 6.2, allowing them to impersonate the user?
>>
>> If they can do #1, they may be able to do #2 and #3, and then #4 is superfluous. If they have access to the public key (through #3 or #4) and access to the authentication plaintext (#2) then they can track where the user is logging in from. 
>>
>> There are so many capabilities we can imagine that the nation state adversary may have, and we only have a vague notion of what information must be prevented from leaking to such an adversary. I don't think that I can check a document to make sure it won't be smacked down in IETF LC or at the IESG for not complying with BCP nn.
>>
>> Also, what if we can hide more information out of a protocol, but at the expense of another roundtrip or more processing power. Who gets to balance the two goals?
>>
>> Yoav
>>
>>
>>
> 

From dhc@dcrocker.net  Wed Jan  1 12:15:28 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4C71A1F5F for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:15:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Avat3wPJDpQw for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:15:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 12DFA1A1F54 for <ietf@ietf.org>; Wed,  1 Jan 2014 12:15:25 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s01KF1ov000321 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 Jan 2014 12:15:05 -0800
Message-ID: <52C476EB.6010604@dcrocker.net>
Date: Wed, 01 Jan 2014 12:13:31 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Yoav Nir <ynir@checkpoint.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie>
In-Reply-To: <52C47605.9070607@cs.tcd.ie>
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.66]); Wed, 01 Jan 2014 12:15:05 -0800 (PST)
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Jan 2014 20:15:28 -0000

On 1/1/2014 12:09 PM, Stephen Farrell wrote:
> I disagree. I think if we constantly desist in taking any action
> because there are inevitably a number of nay-sayers, then we've
> lost. And in this particular case, a BCP is exactly the right thing.


He did not say take no action.  He suggested publishing it, but without 
standards status.  (bcp is standards status.)

It is clear from the list discussion that there is no broad, shared 
understanding of how this policy statement will be applied.  In other 
words, we do not have rough consensus about what the document /means/.

Having rough consensus about a basic emotion about the social aspects of 
the topic is not enough.

As a rule, the IETF tends to avoid standardizing specifications that it 
knows it does not understand.


d/

ps.  My own suggestion is Experimental.  It demonstrates IETF 
encouragement for developing exactly the understanding we currently lack.


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From russw@riw.us  Wed Jan  1 12:25:07 2014
Return-Path: <russw@riw.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C801A802C for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VKyOeHiWypSA for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:25:06 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id 2A57E1A1F54 for <ietf@ietf.org>; Wed,  1 Jan 2014 12:25:06 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:55616 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:AES128-SHA256:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VySLQ-0004oC-Pb; Wed, 01 Jan 2014 20:24:48 +0000
From: "Russ White" <russw@riw.us>
To: <dcrocker@bbiw.net>, "'Stephen Farrell'" <stephen.farrell@cs.tcd.ie>, "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Yoav Nir'" <ynir@checkpoint.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net>
In-Reply-To: <52C476EB.6010604@dcrocker.net>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 15:24:47 -0500
Message-ID: <017601cf072f$846877d0$8d396770$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQDwmmlRCqrzcengRYjHYrwgOSmqfwFXWRe7Aq8twaQAhkIKxgH3NkOqAlUijiMBdm4GVgG9AnsVAgaNTXoBNujQTgLD145yAg0f8yICLFkF2Zt67cEQ
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 20:25:07 -0000

> It is clear from the list discussion that there is no broad, shared
> understanding of how this policy statement will be applied.  In other
words,
> we do not have rough consensus about what the document /means/.

The problem with publishing as an informational is, as an information, it
has no standing within the community. 

I think we might be mixing what something means with what action to take
based on that meaning. I would agree there are no clear cut actions in the
draft as it stands, but we're not really certain what those actions might be
right now, at any rate. So the question becomes:

Should it be a standard of some sort -- a draft with some standing other
than "information" -- to find a way forward in building the questions,
rules, and ideas around protecting the internet protocols designed here
against pervasive monitoring? Should the IETF treat it as a standard that we
should work towards this goal?

If not, then don't bother writing it down at all, no matter the status. If
so, then it's worth saying in a way that drives us forward into other work
in this area.

> As a rule, the IETF tends to avoid standardizing specifications that it
knows it
> does not understand.

There is a difference between standardizing a specification in the technical
sense, and saying, "this is a community goal we've agreed to work on." 

My concern, in the end, is that we publish an informational, and then say:
"See, we've done something. Now we can get back to our regularly scheduled
arguments over whether this should be a bit field or an integer."

I don't think that's the right response. Pick the stronger vehicle, even if
it's not "perfect." As with many other things in the IETF, the perfect is
often the enemy of the good.

Russ


From melinda.shore@gmail.com  Wed Jan  1 12:29:59 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 501791A8032 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:29:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ygrSXyKOlli7 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:29:57 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id C65F51A1F54 for <ietf@ietf.org>; Wed,  1 Jan 2014 12:29:57 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id z10so13483789pdj.2 for <ietf@ietf.org>; Wed, 01 Jan 2014 12:29:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=n/KPFSerrPoFv1BRw1I2e2pWcmqcTn7h9nEBMgkTUco=; b=JyvVdcHuaOUcbmh2UG+4/Fk/RY7fM0UGNYXdsXA51M0UnhDwhGKK/MaR+XGdnVTRTJ NYfBld6bFOWZKoGB9IWkGfDq/b8/vSyo+e0dd+7K9YG5h03kNSx7R2OvhWRdZx4SWhuU x1BC6cyHbSzL+J10ZTpMmWiDmN2KMSl5WraquFHtahFWhJAfDWo8SI9Qcp5iLPuqO24q WGHfRFavq8Pvof/agWrRSMb/0mUukd8J6duQ7tr1EdaMCFDruSbPbt2EEv0RWTCAVeUf FoLyFap4nl9gJTbN8cDp723RT5V8QXsiHDbh8c/g1JlCpTvFWrsd+OSIJ00FxcKWdTOF JQGA==
X-Received: by 10.67.5.233 with SMTP id cp9mr18789159pad.147.1388608191199; Wed, 01 Jan 2014 12:29:51 -0800 (PST)
Received: from spandex.local (63-140-85-118.nwc.dsl.dynamic.acsalaska.net. [63.140.85.118]) by mx.google.com with ESMTPSA id i10sm127029565pat.11.2014.01.01.12.29.49 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 12:29:49 -0800 (PST)
Message-ID: <52C47ABB.5010009@gmail.com>
Date: Wed, 01 Jan 2014 11:29:47 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie>
In-Reply-To: <52C47605.9070607@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 20:29:59 -0000

On 1/1/14 11:09 AM, Stephen Farrell wrote:
> I disagree. I think if we constantly desist in taking any action
> because there are inevitably a number of nay-sayers, then we've
> lost. And in this particular case, a BCP is exactly the right thing.

I really don't think so, at least not in its current form.  I
think it's fine to publish it as-is as an opinion piece but it seems
to me that if it's going to be published as a "BCP" it really needs
to be clearer about specifically what is going to change in the
current document development and publication process.  I'd be a little
alarmed if somebody today decided that there's IETF consensus on
publishing as a BCP and that the inevitable nay-sayers can be
ignored; there seems to me to be significant dissent.

Melinda


From ajs@anvilwalrusden.com  Wed Jan  1 12:35:07 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E7B1A8035 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:35:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dkkOInjwSba1 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 12:35:05 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 793901A1F54 for <ietf@ietf.org>; Wed,  1 Jan 2014 12:35:05 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 2971A8A035 for <ietf@ietf.org>; Wed,  1 Jan 2014 20:34:58 +0000 (UTC)
Date: Wed, 1 Jan 2014 15:34:53 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Status (was: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice)
Message-ID: <20140101203451.GA6722@mx1.yitter.info>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52C476EB.6010604@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 20:35:07 -0000

On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:
> ps.  My own suggestion is Experimental.  

Please, no.  That status has been abused enough.  What would you be
trying to learn by this experiement?  What would the conditions be
that you would conclude you knew the answer?  If you can't answer
those questions, "Experimental" is just wrong.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From sm@elandsys.com  Wed Jan  1 13:00:02 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 820FF1AD791; Wed,  1 Jan 2014 13:00:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.429
X-Spam-Level: 
X-Spam-Status: No, score=-0.429 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JaJjDZGhKNrs; Wed,  1 Jan 2014 13:00: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 3F5461AD73E; Wed,  1 Jan 2014 13:00:01 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.144.184]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s01KxcCx022223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Jan 2014 12:59:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388609993; bh=YxbJCYr713KAtAOSKWR8citRAAzMvRzs8DZNnEVx3NY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MFF1IWzvdCB1/BDQVVIqjWxziHvVouFBUlEvo/kylrPHH/cC69KJPuqABMcGr/ETs dviMhs2jkfp6min8YGvbpHCFqXgeZvv0Q5rpJ9llXOz8mt/Trw4uw/q/w7ah1FUYd5 IrgKvMJsXeTNOqPfUc62OPbQgK4HfkwP9LQGBztQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1388609993; i=@elandsys.com; bh=YxbJCYr713KAtAOSKWR8citRAAzMvRzs8DZNnEVx3NY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Vel7YVcsxFz1v/g1L/t8JwmDdRmQryy0oOB9mUGGtkFEuZKAeLhrcgVVdyDXKGNLj iVLcmmpmRJQ2h184HYitV4djIh1kS68OX2IzR0FVP1vL39t99lrR+2c+eYVcDTCOmn 9Q12OsHGiWmibuQ0T+HaMmNnXZyOklP30P4bTPRE=
Message-Id: <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Jan 2014 10:47:07 -0800
To: Russ Housley <housley@vigilsec.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
In-Reply-To: <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Adrian Farrel <adrian@olddog.co.uk>, IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 21:00:02 -0000

Hi Russ,
At 07:48 31-12-2013, Russ Housley wrote:
>The IETF develops open standards for one global Internet, providing 
>maximum interoperability and scalability, and avoiding specialized 
>protocols in different places.

The concern is about whether to have text in the document for the 
above.  This is the third statement in Section 2:

   "3. IETF participants devise solutions for the Internet that meet the
       needs of diverse technical and operational environments."

The sentence which is not in the draft is:

   "The goal of the IETF is to maintain and enhance a working, viable,
    scalable, global Internet, and the problems we encounter are
    genuinely very difficult."

The comment from Adrian Farrel is as follows:

   "I pointed out that 3184 predated the mission statement in 3935 
and that it would
    be "better" (IMHO) to align this revision with the consensus 
mission statement
    than to define the purpose of the IETF as an aside in this document."

The goal of the IETF is currently described as follows:

   "The goal of the IETF is to make the Internet work better."

I read it as a simple statement.  The reader may ask: "what do you 
mean by that?"  This is where the discussion gets into the mission statement:

   "The mission of the IETF is to produce high quality, relevant
    technical and engineering documents that influence the way people
    design, use, and manage the Internet in such a way as to make the
    Internet work better."

An alternative might be:

    3. IETF participants devise solutions for the Internet that meet the
       needs of diverse technical and operational environments.

       The mission of the IETF is to produce high quality, relevant
       technical and engineering documents that influence the way people
       design, use, and manage the Internet in such a way as to make the
       Internet work better.  The IETF puts its emphasis on technical
       competence, rough consensus and individual participation, and needs
       to be open to competent input from any source.

       IETF participants use their best engineering judgment to find the
       best solution for the whole Internet, not just the best solution
       for any particular network, technology, vendor, or user.  While we
       all have ideas that may stand improvement from time to time, no
       one shall ever knowingly contribute advice or text that would make
       a standard technically inferior.

>BCP 79 is the proper reference.
>
>Following the IPR rules is an obligation for all IETF 
>participants.  It was in RFC 3184, and I think we need to keep in 
>this document.

The text in RFC 3184 is as follows:

   "We follow the intellectual property guidelines outlined in BCP 9."

In my opinion that text does not fit under the third statement.  An 
alternative, which was suggested, is to have it under another 
guideline.  The comment mentions that it is an obligation and I agree 
with that.  The point being discussed is that the obligation has to 
be kept in this document because it was in RFC 3184.  The document 
has been described as being about personal conduct and personal 
interaction.  The document does not discuss about rules.

The Note Well is used to direct people to BCP 79.  A person attending 
a working group session will be told about the Note Well.  A person 
subscribing to an IETF mailing list will be sent a pointer to the 
Note Well.  I suggest leaving it to the Note Well to list the rules 
as it has not been argued that the Note Well is inadequate.

Regards,
S. Moonesamy 


From melinda.shore@gmail.com  Wed Jan  1 13:18:56 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3FF51AD7BF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 13:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnRGx-We9lyx for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 13:18:55 -0800 (PST)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 409E91AD75F for <ietf@ietf.org>; Wed,  1 Jan 2014 13:18:55 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id x10so13387961pdj.19 for <ietf@ietf.org>; Wed, 01 Jan 2014 13:18:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=51/ihqwtdTrtRldugnUEEbsBf5sA9fTeY4tu2UOD9mY=; b=X1eq3WMvTbWmritBt1lzNo/KnWeaVanXocK2VHRkPH5QfpbnlHYS+RmIhZmMu3BFCz 0mxu0lXY4elnmwn9WUws4cJOZ30T1xxrO9B1TmoiddlGwmHyMcNxsgNxYlWmp+enHg85 hf/FJrlkLGWyN7JDngLzm3G8IyJoopH+MoV7FLSxE73BkJCsVosan1Bzs+gFj/vRpJ5y yxX1aJWKYa4jIpaRn3MAi+hE737gY6d5CBLHKbaKTdLd6IDOBthN6LqMtgRFlEJPgg/7 fpzsp76n/WxBVZgPwi5/GX8JY90HjsBCIomDXkqgmTqLZ+HFUbHYAFANYL4BW0cRL3/H JGRg==
X-Received: by 10.68.200.129 with SMTP id js1mr84402924pbc.14.1388611128700; Wed, 01 Jan 2014 13:18:48 -0800 (PST)
Received: from spandex.local (63-140-85-118.nwc.dsl.dynamic.acsalaska.net. [63.140.85.118]) by mx.google.com with ESMTPSA id un5sm35284839pab.3.2014.01.01.13.18.46 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 13:18:47 -0800 (PST)
Message-ID: <52C48635.7040508@gmail.com>
Date: Wed, 01 Jan 2014 12:18:45 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Status
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info>
In-Reply-To: <20140101203451.GA6722@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 21:18:56 -0000

On 1/1/14 11:34 AM, Andrew Sullivan wrote:
> On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:
>> ps.  My own suggestion is Experimental.   
> Please, no.  That status has been abused enough.  What would you be
> trying to learn by this experiement?  What would the conditions be
> that you would conclude you knew the answer?  If you can't answer
> those questions, "Experimental" is just wrong.

I'd actually be fine with experimental, to the extent that it
provided background for some experiments with trying to find
a workable framework for evaluating snoop-resistance in IETF
specifications.  I'm less good with publishing a BCP that's
neither "best" nor "current" nor "practice."

Melinda


From Ted.Lemon@nominum.com  Wed Jan  1 14:09:12 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D141ACCF5 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cr7W2f2L11FP for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:09:10 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 2E73A1ACCE8 for <ietf@ietf.org>; Wed,  1 Jan 2014 14:09:10 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUsSR/xM07f/cZptvJmxKdIy0zaKoeBUv@postini.com; Wed, 01 Jan 2014 14:09:03 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 7F5D51B82E0 for <ietf@ietf.org>; Wed,  1 Jan 2014 14:09:03 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 5891319005C; Wed,  1 Jan 2014 14:09:03 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 1 Jan 2014 14:09:02 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
Date: Wed, 1 Jan 2014 17:08:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 22:09:12 -0000

On Dec 31, 2013, at 3:48 PM, John C Klensin <john-ietf@jck.com> wrote:
> No matter what
> assurances are made to the contrary, we've seen example after
> example, general guideline after general guideline, turned into
> rigid rules during or after Last Call on particular documents
> because some AD decides that a document that doesn't match his
> (usually -- I think we've yet to have a really abusive,
> testosterone-poisoned, woman AD) ideas of how things should work
> and should therefore be blocked until the authors or WG either
> conform to whatever "requirement" supports his conclusion or
> produce an overwhelming proof that should not be necessary.

This argument boils down to "ADs can abuse process, so we ought not to =
ever publish a document that might provide process for them to abuse."   =
Forgive me, but this is just bad logic: if ADs are abusing process, the =
problem is the ADs, and the solution has to be addressed through the AD =
nomination and/or recall process.   There are already plenty of =
processes to abuse=97if I really want to scuttle a document, I don't =
need another BCP with which to do it.

On Jan 1, 2014, at 12:38 AM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
> I've mostly been baffled by the IETF response to
> revelations about internet eavesdropping, to be honest,
> and it's struck me that work on some of the problems that
> need to be solved to provide better privacy guarantees (for
> example, fixing PKI and providing better keying) have been
> pushed to a back burner in a scramble to make grandiose
> pronouncements.

Fixing PKI doesn't address the pervasive surveillance problem at all.

> It's not that draft-farrell is a bad
> document on its own merits, it's just that I cannot for
> the life of me understand what it specifically means for
> work moving through the IETF process.

It means that, if the IETF winds up having consensus to say so, we agree =
that document authors and working groups ought to consider the problem =
of pervasive surveillance: that considering these issues is documented =
best practice in the IETF.

On Jan 1, 2014, at 9:37 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
> So if you support, could you just state directly how this document
> will be used?

It will be used by working group chairs and document authors to =
understand the IETF's expectations with respect to whether their work =
needs to address the problem of pervasive surveillance on the internet.  =
 I expect that ADs will also have this in mind when reviewing documents, =
and may ask questions about documents if the documents appear not to =
have addressed the problem, and don't say why.   In some cases, further =
consideration in the working group will be called for.   In other cases, =
adding some explanatory text may suffice.   In still other cases, =
explaining the situation to the AD will be enough.

But the real goal of a document like this is to get working groups to =
think about this, not to create more tail-end process.   ADs can =
_already_ ask these questions, and can _already_ send documents back to =
the working group if the answers aren't satisfactory.   What this =
document does is to clearly state an IETF consensus (assuming one is =
reached), which might result in more consistency both across the process =
of developing a specific document, and also across time as the makeup of =
working groups and the IESG changes.

On Jan 1, 2014, at 10:45 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>     There is a substantial community in the Internet wishing to have =
its data and activities protected against pervasive monitoring.  The =
IETF needs to design specifications and practices (existing and new) =
with the means to ensure such protection.

It sounds like you are saying that the IETF does not lead, but rather =
follows the market.

On Jan 1, 2014, at 3:29 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
> I really don't think so, at least not in its current form.  I
> think it's fine to publish it as-is as an opinion piece but it seems
> to me that if it's going to be published as a "BCP" it really needs
> to be clearer about specifically what is going to change in the
> current document development and publication process.

This document is advice, not code.   It is indeed "best practice" in the =
sense that, if the IETF gains consensus on it, it is saying that we =
should make a habit of thinking about pervasive monitoring when writing =
our documents.   I think it would be harmful to be more specific than =
that.   One the one hand, formal process may be applied when good =
judgment would have argued otherwise, because "that's the process."   On =
the other hand, formal process may well accidentally exempt documents =
where a more general "you ought to think about this" would have clearly =
applied.


From john-ietf@jck.com  Wed Jan  1 14:34:11 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B18671AD628 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.138
X-Spam-Level: 
X-Spam-Status: No, score=-5.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYyC8vBSoKHF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:34:09 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CE4531AD67B for <ietf@ietf.org>; Wed,  1 Jan 2014 14:34:08 -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 1VyUMT-000J88-QX; Wed, 01 Jan 2014 17:34:01 -0500
Date: Wed, 01 Jan 2014 17:33:56 -0500
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Status
Message-ID: <33D17D89435054B582971148@JcK-HP8200.jck.com>
In-Reply-To: <52C48635.7040508@gmail.com>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info> <52C48635.7040508@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 22:34:11 -0000

--On Wednesday, January 01, 2014 12:18 -0900 Melinda Shore
<melinda.shore@gmail.com> wrote:

> On 1/1/14 11:34 AM, Andrew Sullivan wrote:
>> On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:
>>> ps.  My own suggestion is Experimental.   
>> Please, no.  That status has been abused enough.  What would
>> you be trying to learn by this experiement?  What would the
>> conditions be that you would conclude you knew the answer?
>> If you can't answer those questions, "Experimental" is just
>> wrong.
> 
> I'd actually be fine with experimental, to the extent that it
> provided background for some experiments with trying to find
> a workable framework for evaluating snoop-resistance in IETF
> specifications.  I'm less good with publishing a BCP that's
> neither "best" nor "current" nor "practice."

I have to agree with Andrew.  The most important parts of the
document are, to me, the statement that there is an issue, that
the IETF community recognizes that issue, and that there is a
general sentiment that considering it and doing something about
it is generally a good idea.

Where I start having problems is where it seems to specify
constraints on protocols or criteria that could be used to block
standardization of protocol specs that don't meet someone's
theory of what is possible or good enough.   As others have
said, we shouldn't be approving things (and claiming the
existence of consensus about them) that call for action but that
aren't actionable without new rounds of debate about what those
actions are or that seem to specify, a priori and for most or
all protocols, that some tradeoffs and constraints are more
important than others without careful examination of the others.

Identifying a document as experimental doesn't help with that in
any way unless, as Andrew suggested, we are prepared to specify
the experiments and the corresponding evaluation criteria.

I've deliberately avoided making concrete suggestions, but let
me give that up and suggest two alternatives:

(1) Many years ago, in a discussion of formal models of various
types of systems, Joe Weizenbaum [1] suggested the most of the
value in such models lay in the thinking, hypothesis testing,
and topic examination that went into their creation; "running"
the models was less often significantly useful.  Perhaps this
topic is much like that: the community, and especially those of
its members who have been following the discussions and thinking
about the various comments, have learned a great deal.  Maybe
publishing it, especially with claims of consensus, would be
anticlimax at best and an invitation, not just to abuse but to
additional versions of the endless process debates that, as I
think Randy Bush was suggesting, because a blocking factor and
substitute for getting actual work on the Internet done in the
IETF.  That isn't a good tradeoff, so maybe it is time to just
stop.

(2) Perhaps it is useful to the community that we make a strong
statement that pervasive surveillance is an attack on the
Internet, its openness, and the ability to use the network with
confidence.  I don't have a problem with such a statement
although, if we make it, I think we should also be considering
statements about patent abuses, competitiveness among ISPs and
other "open access" and "net neutrality" issues, and a
collection of other issues and areas.  But, if we do that, let's
do that and issue it as an informational statement or RFC, not
pretend that it is a standard, much less a best current
practice.   If that document wants to call for actions or
experiments, that would be great, as long as it isn't written in
a way that can easily be confused with such actions or
experiments.

best,
   john



[1] For those of you who don't recognize the name, look it up --
probably would be good for you.
> 
> Melinda
> 





From stephen.farrell@cs.tcd.ie  Wed Jan  1 14:42:12 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8611ADF4B for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jQGqthxlkPF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:42:11 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id DAD251ADC03 for <ietf@ietf.org>; Wed,  1 Jan 2014 14:42:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 757FFBE5F; Wed,  1 Jan 2014 22:42:03 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KE+0ynTCHylc; Wed,  1 Jan 2014 22:42:02 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5AF37BE62; Wed,  1 Jan 2014 22:42:01 +0000 (GMT)
Message-ID: <52C499AE.5060002@cs.tcd.ie>
Date: Wed, 01 Jan 2014 22:41:50 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Status
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info> <52C48635.7040508@gmail.com> <33D17D89435054B582971148@JcK-HP8200.jck.com>
In-Reply-To: <33D17D89435054B582971148@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 22:42:12 -0000

On 01/01/2014 10:33 PM, John C Klensin wrote:
> Where I start having problems is where it seems to specify
> constraints on protocols or criteria that could be used to block
> standardization of protocol specs that don't meet someone's
> theory of what is possible or good enough.

Can you quote text please?

S.

From russw@riw.us  Wed Jan  1 14:58:35 2014
Return-Path: <russw@riw.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A91B1A1F1B for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:58:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e50c3GgVTS2z for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 14:58:34 -0800 (PST)
Received: from server.riw.us (server.riw.us [162.144.32.236]) by ietfa.amsl.com (Postfix) with ESMTP id 1B67E1A1F02 for <ietf@ietf.org>; Wed,  1 Jan 2014 14:58:34 -0800 (PST)
Received: from cpe-098-122-144-218.nc.res.rr.com ([98.122.144.218]:63737 helo=RussPC) by server.riw.us with esmtpsa (UNKNOWN:AES128-SHA256:128) (Exim 4.82) (envelope-from <russw@riw.us>) id 1VyUk6-0005rY-QA; Wed, 01 Jan 2014 22:58:26 +0000
From: "Russ White" <russw@riw.us>
To: "'Ted Lemon'" <ted.lemon@nominum.com>, "'John C Klensin'" <john-ietf@jck.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
In-Reply-To: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Wed, 1 Jan 2014 17:58:20 -0500
Message-ID: <004001cf0744$fab41470$f01c3d50$@riw.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQDwmmlRCqrzcengRYjHYrwgOSmqfwFXWRe7Aq8twaQAhkIKxgH3NkOqAlUijiMBdm4GVgEaMmOFm9IDu0A=
Content-Language: en-us
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.riw.us
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
X-Get-Message-Sender-Via: server.riw.us: authenticated_id: russw@riw.us
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: 'IETF Discussion' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 22:58:35 -0000

> It means that, if the IETF winds up having consensus to say so, we agree
that
> document authors and working groups ought to consider the problem of
> pervasive surveillance: that considering these issues is documented best
> practice in the IETF.

Precisely.

Consider the alternative. In a year, we have a draft on the table that
seriously compromises privacy, or opens a huge door to surveillance. We can
point to an informational about why such a draft needs work, an experimental
about why such a draft needs work, or a BCP. Which one is the draft authors
going to take seriously, or pay attention to? "You really want me to change
my draft completely to meet the demands of an experimental draft? Since when
do we care about experimentals and informationals?"

IMHO, this draft, as it sits, explains the problem, leaves process questions
open to discussion, and yet says -- we should be seriously thinking about
this. 

Russ 


From melinda.shore@gmail.com  Wed Jan  1 15:07:41 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B320D1ADF4C for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:07:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HR-yjNanP6aX for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:07:40 -0800 (PST)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id DF5DE1ADF39 for <ietf@ietf.org>; Wed,  1 Jan 2014 15:07:39 -0800 (PST)
Received: by mail-pb0-f42.google.com with SMTP id uo5so13942058pbc.1 for <ietf@ietf.org>; Wed, 01 Jan 2014 15:07:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=N578EFOO3n0ewhO21WuhXH6iSRMhl/RpLDG3ux11SqQ=; b=n2XuCFSD6YA08CMvpUdJ9zcImTlLb/9UdYdhWcffuZtDiE4Kv/prWsdLCYPyoE/QGF gv0PXsSHMyuGllMs6ZqllGwWEuWodeVOEshLILaPI7ir5t6SAyzy1p8Pk0p+FFfPYqs5 naP7aZKutvcCWKgRhuNdQ1ovM/X1dHG1qs5rW2xLU/0H0eSd497qfPg+im2lovkLLFKf IaPCzz7CN1e9RowC9PO/JNEC3vkrKLBpkHL+4to5sTqi7sK2OtdhFyS6XrwRFlnUz5nF 3pG1ibrcx+ONDGl8BFltOHiZ0AhuE81KIViZdyWASVTWXaZ8oey7KOeUnBco3RxEYkxf NmQA==
X-Received: by 10.68.17.7 with SMTP id k7mr83704301pbd.119.1388617653311; Wed, 01 Jan 2014 15:07:33 -0800 (PST)
Received: from spandex.local (63-140-85-118.nwc.dsl.dynamic.acsalaska.net. [63.140.85.118]) by mx.google.com with ESMTPSA id fk4sm127635680pab.23.2014.01.01.15.07.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 15:07:32 -0800 (PST)
Message-ID: <52C49FB2.9090208@gmail.com>
Date: Wed, 01 Jan 2014 14:07:30 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us>
In-Reply-To: <004001cf0744$fab41470$f01c3d50$@riw.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 23:07:41 -0000

On 1/1/14 1:58 PM, Russ White wrote:
> Consider the alternative. In a year, we have a draft on the table that
> seriously compromises privacy, or opens a huge door to surveillance. We can
> point to an informational about why such a draft needs work, an experimental
> about why such a draft needs work, or a BCP. Which one is the draft authors
> going to take seriously, or pay attention to? "You really want me to change
> my draft completely to meet the demands of an experimental draft? Since when
> do we care about experimentals and informationals?"

I'm sorry, but when we get to the point where we need to point to an
RFC to stop progress on a document that has obvious vulnerabilities,
our brains have fallen out.

Melinda



From l.wood@surrey.ac.uk  Wed Jan  1 15:07:58 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A968B1ADF6E for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:07:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ay9l-p2aGp-V for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:07:56 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.164]) by ietfa.amsl.com (Postfix) with ESMTP id 88BE21ADF70 for <ietf@ietf.org>; Wed,  1 Jan 2014 15:07:55 -0800 (PST)
Received: from [195.245.230.131:28372] by server-4.bemta-3.messagelabs.com id 82/1B-10414-3CF94C25; Wed, 01 Jan 2014 23:07:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-78.messagelabs.com!1388617667!32506948!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27743 invoked from network); 1 Jan 2014 23:07:47 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-6.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 1 Jan 2014 23:07:47 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.22]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 1 Jan 2014 23:07:46 +0000
From: <l.wood@surrey.ac.uk>
To: <tbray@textuality.com>, <lear@lear.ch>
Date: Wed, 1 Jan 2014 23:07:45 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8HI+lxCEO6bffLSsCUvOXjAB35OwAHaVks
Message-ID: <290E20B455C66743BE178C5C84F1240847E51037C8@EXMB01CMS.surrey.ac.uk>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com>	<CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie>	<55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net>	<00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <m2ob3vpoji.wl%randy@psg.com>, <CAHBU6iuyMiLcRNS1Oc0xkZ=Rd2WoquE9b8fxexvO3QyJub26nQ@mail.gmail.com>
In-Reply-To: <CAHBU6iuyMiLcRNS1Oc0xkZ=Rd2WoquE9b8fxexvO3QyJub26nQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 23:07:59 -0000

Actually, no, similar holdups do not occur for concerns of error-handling. =
Examples:

in DTNRG (which, though IRTF, is highly relevant, being chaired as it is by=
 the now security AD):
- LTP was developed with no error detection: RFC5326. Managed to get some s=
hoehorned in at
the last moment in the NULL bits of RFC5237, but that was not a holdup.
- the bundle protocol was developed with no error detection, and no followi=
ng of the
end-to-end principle. That took ten years or so, a lot of researchers, a na=
tional space agency...

but in DTNRG, security was paramount in the design (and focused on by the c=
hairs). Those are the results.
The judgement calls come down in favour of security concerns above all else=
.

In the IETF:
RFCs 6935 and 6936, which relax the endpoint payload and pseudoheader check=
 by
allowing zero checksums in IPv6, because tunnelled payloads with their own =
checks=20
just don't need it. (That other applications do because IPv6 itself is lax =
on
reliability checks, has no header-only check and the closest it would get t=
o an endpoint
header check would be UDP-lite, and the applications can be polluted by mis=
-arriving
errored  zero-checksum UDP packets, is neither here nor there. This is argu=
ably the
predictable outcome of some poor design decisions in IPv6 twenty years ago.=
)

I'd welcome counterexamples where errors forced a holdup and rethink. I kno=
w of none.

We're heading into a world where security is paramount, and the only reason=
 we have
any reliability in protocols at all is as a sideeffect of the security reje=
cting perceived attacks,
and not because we actually know how to design error-rejecting protocols. (=
How many
people here could design a CRC? How many design secure systems?)

There will be no further internet engineering (which, given that 6935/6936 =
are
proposed standards, never mind the horse-designed-by-committee IPv6 camel,
may actually not be a bad thing); any internet engineering done, or any
reliability obtained in implementations, will just be an unintended sideeff=
ect
of security as a discipline.

Lloyd Wood
http://about.me/lloydwood

http://web.mit.edu/Saltzer/www/publications/endtoend/endtoend.pdf
________________________________________
From: Tim Bray [tbray@textuality.com]

> There are very few (any?) absolutes in any of the protocols we build, jus=
t a wealth
> of often-conflicting design criteria, which force us to trade off and mak=
e judgment calls.
>  draft-perpass-attack says that mitigation of pervasive surveillance shou=
ld be seen as
> one of the design criteria, and it=92s not OK to ignore it. A reasonable =
take is that a specification
> could be held up if there are plausible arguments that this criterion has=
 not been given appropriate
> consideration, and I see nothing wrong with that. Similar hold-ups regula=
rly occur when there are
> concerns that there hasn=92t been appropriate consideration for efficienc=
y or error-handling or, well, lots of other criteria.






From l.wood@surrey.ac.uk  Wed Jan  1 15:09:21 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D91921ADF39 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cK9hIjsiJwRF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:09:20 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.144]) by ietfa.amsl.com (Postfix) with ESMTP id C5A151ADF6E for <ietf@ietf.org>; Wed,  1 Jan 2014 15:09:19 -0800 (PST)
Received: from [195.245.231.67:57023] by server-8.bemta-5.messagelabs.com id 4B/80-29838-810A4C25; Wed, 01 Jan 2014 23:09:12 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-82.messagelabs.com!1388617752!32159833!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23418 invoked from network); 1 Jan 2014 23:09:12 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-14.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 1 Jan 2014 23:09:12 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.22]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 1 Jan 2014 23:09:11 +0000
From: <l.wood@surrey.ac.uk>
To: <melinda.shore@gmail.com>, <ietf@ietf.org>
Date: Wed, 1 Jan 2014 23:08:28 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8HRlIyApLSf0mHRpGrUvf2P3IrIAAAA/fM
Message-ID: <290E20B455C66743BE178C5C84F1240847E51037C9@EXMB01CMS.surrey.ac.uk>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us>,<52C49FB2.9090208@gmail.com>
In-Reply-To: <52C49FB2.9090208@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 23:09:22 -0000

DTNRG work suggests that they already have...

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Melinda Shore [melinda.shor=
e@gmail.com]
Sent: 01 January 2014 23:07
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

On 1/1/14 1:58 PM, Russ White wrote:
> Consider the alternative. In a year, we have a draft on the table that
> seriously compromises privacy, or opens a huge door to surveillance. We c=
an
> point to an informational about why such a draft needs work, an experimen=
tal
> about why such a draft needs work, or a BCP. Which one is the draft autho=
rs
> going to take seriously, or pay attention to? "You really want me to chan=
ge
> my draft completely to meet the demands of an experimental draft? Since w=
hen
> do we care about experimentals and informationals?"

I'm sorry, but when we get to the point where we need to point to an
RFC to stop progress on a document that has obvious vulnerabilities,
our brains have fallen out.

Melinda



From l.wood@surrey.ac.uk  Wed Jan  1 15:16:13 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E47AB1ACCF8 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:16:13 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wdTkXRtRjgMa for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 15:16:12 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id 89C8B1ACCEE for <ietf@ietf.org>; Wed,  1 Jan 2014 15:16:11 -0800 (PST)
Received: from [85.158.137.99:23756] by server-12.bemta-3.messagelabs.com id DC/DF-20055-4B1A4C25; Wed, 01 Jan 2014 23:16:04 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-217.messagelabs.com!1388618163!20316659!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1760 invoked from network); 1 Jan 2014 23:16:04 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-10.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 1 Jan 2014 23:16:04 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.22]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Wed, 1 Jan 2014 23:16:03 +0000
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>, <ietf@ietf.org>
Date: Wed, 1 Jan 2014 23:15:20 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8HG+UbHqkxeItzTXuecmcqWddrFwAK3JQ4
Message-ID: <290E20B455C66743BE178C5C84F1240847E51037CA@EXMB01CMS.surrey.ac.uk>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us>,<m2ob3vpoji.wl%randy@psg.com>
In-Reply-To: <m2ob3vpoji.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 23:16:14 -0000

Ask not what you can do for the IETF mailing list.=20
Ask what the IETF mailing list can do for you.

good one, Randy.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Randy Bush [randy@psg.com]
Sent: 01 January 2014 18:03
To: IETF Disgust
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

the violations of trust in the internet are on the front page every day
for months.  but we don't need no stinkin' policy or architectural
response.  we just need a mailing list on which to blather endlessly
while rome burns.

what are you gonna do to make the internet a better and safer place
today?

randy


From scott.brim@gmail.com  Wed Jan  1 16:43:03 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E03731ADE72 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 16:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkEHrf2MDlU7 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 16:43:02 -0800 (PST)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id E1EE91A802F for <ietf@ietf.org>; Wed,  1 Jan 2014 16:43:01 -0800 (PST)
Received: by mail-ob0-f181.google.com with SMTP id uy5so14010091obc.12 for <ietf@ietf.org>; Wed, 01 Jan 2014 16:42:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=68Fix1TRC12rEdZo1A35OI0nbjJ5hZ+ppBjzsxTz7Ko=; b=bpwTPR7s4JndL/supe3zLd4bvMSP79Ct365WDpnxh1BXq8oH/htApQVAsSlt68vTRg UnpyCkkN89zQjhOUOZm+W9vwwZ0L41AR2dk9sqTSChppjvaj5ryGhzYeJD1HDjctHsDM vvafBtol3farGS85hRc8+YHx5c9tyAVcZFwh0X9nn2eG1YoSclsZO0qvWhRwUjFUCnlA 6P2m+zoL36X+sJApqHXxkOE04naCr4FiJT7LMR6drVeBodKF5eilC2tSesHv0yjmOVde xnFwBIfCRoXksrUK4jSIkbHzS1O8XSHmS2zi+Ebsy7qsEwrzsIL0WO1xZ4fvaHOHqG6J hn6g==
X-Received: by 10.182.232.4 with SMTP id tk4mr54211819obc.9.1388623375049; Wed, 01 Jan 2014 16:42:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 1 Jan 2014 16:42:34 -0800 (PST)
In-Reply-To: <20140101203451.GA6722@mx1.yitter.info>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 1 Jan 2014 19:42:34 -0500
Message-ID: <CAPv4CP-d-tH68g=w4pfn8YB2wmrj+wK7RojnZtgUwemU032X8A@mail.gmail.com>
Subject: Re: Status (was: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice)
To: Andrew Sullivan <ajs@anvilwalrusden.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 00:43:04 -0000

On Wed, Jan 1, 2014 at 3:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:
>> ps.  My own suggestion is Experimental.
>
> Please, no.  That status has been abused enough.  What would you be
> trying to learn by this experiement?  What would the conditions be
> that you would conclude you knew the answer?  If you can't answer
> those questions, "Experimental" is just wrong.

Right. This is not a protocol that needs field testing, it's a
statement of policy.

The thing that needs to be clarified is apparently what the policy is.

Scott

From scott.brim@gmail.com  Wed Jan  1 17:17:41 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D21891A1F62 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 17:17:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yJba9FG71r4F for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 17:17:40 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id B1FE41A1F06 for <ietf@ietf.org>; Wed,  1 Jan 2014 17:17:40 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id uz6so13798938obc.23 for <ietf@ietf.org>; Wed, 01 Jan 2014 17:17:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=eWDBAb477Y4XgDyAeDaPdARv2F83oq6syKJh7B3GJy4=; b=feZK37RFgR3pSfnUz9U8qBQUzPz+5VN47nAtVnEMzlQrimARHAEvc3MIwgv58ZMIc9 zwV5Jroj2uQAKbvYq1tDnBCJRYRbe8k1FQLi3rzBwq81Ty8NKZvCCQzf4+IFHC7clE7l 6nOWg5TxRmyrDNGJP7A+BvtNWnNP+HPFDgzbWLGuIdkjh4MZpWAaurYd/ea4LmlNi9mY ruD/P0GQ2V2GsmMJ8e424vvTC8SzOHTQ9cw6xmefTb/SUIDJqOt+vUPJS9Fq1vuGbc92 ZPfM6H0RTCmASf4j9xEkgTfkiqogyqKsrTpklfuRE8S1nG4ODcrga+2jSLX3kZplfhdW VHGw==
X-Received: by 10.182.153.226 with SMTP id vj2mr54064023obb.26.1388625453800;  Wed, 01 Jan 2014 17:17:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 1 Jan 2014 17:17:13 -0800 (PST)
In-Reply-To: <52C48635.7040508@gmail.com>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info> <52C48635.7040508@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 1 Jan 2014 20:17:13 -0500
Message-ID: <CAPv4CP9UHvQ-QF=v=C=pPX7eHgUZWo4-xXfPPUZm6ixU2UOJiQ@mail.gmail.com>
Subject: Re: Status
To: Melinda Shore <melinda.shore@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 01:17:42 -0000

On Wed, Jan 1, 2014 at 4:18 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> I'd actually be fine with experimental, to the extent that it
> provided background for some experiments with trying to find
> a workable framework for evaluating snoop-resistance in IETF
> specifications.  I'm less good with publishing a BCP that's
> neither "best" nor "current" nor "practice."

I don't believe finding a "framework for evaluating snoop-resistance
in IETF specifications" describes the goal. That would be very very
difficult. Providing background for such an effort? Sure, but again I
don't think that's a primary goal. We want to establish guidelines for
WGs in doing security considerations ... but IMHO specific statements
of guidelines are beyond the scope of this draft. I believe this draft
is just establishing a fundamental principle on which to take the next
steps. Maybe it should just be informational because there's very
little actual practice in it?

Scott

From Ted.Lemon@nominum.com  Wed Jan  1 19:11:31 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D151AE123 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:11:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BpOpexg3io0G for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:11:29 -0800 (PST)
Received: from exprod7og121.obsmtp.com (exprod7og121.obsmtp.com [64.18.2.20]) by ietfa.amsl.com (Postfix) with ESMTP id CC4171ADF93 for <ietf@ietf.org>; Wed,  1 Jan 2014 19:11:29 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob121.postini.com ([64.18.6.12]) with SMTP ID DSNKUsTY20bx+nuTFnzTsBcJBlNTjM//Fqv0@postini.com; Wed, 01 Jan 2014 19:11:23 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 2404F1B82DD for <ietf@ietf.org>; Wed,  1 Jan 2014 19:11:23 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id F1FBD19005C; Wed,  1 Jan 2014 19:11:22 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 1 Jan 2014 19:11:22 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52C49FB2.9090208@gmail.com>
Date: Wed, 1 Jan 2014 22:11:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 03:11:31 -0000

On Jan 1, 2014, at 6:07 PM, Melinda Shore <melinda.shore@gmail.com> =
wrote:
> I'm sorry, but when we get to the point where we need to point to an
> RFC to stop progress on a document that has obvious vulnerabilities,
> our brains have fallen out.

This is counterfactual.   We used to routinely handwave about security.  =
 We've gotten better about that.   RFC3552 is why.   RFC3552 does not =
discuss the threat of pervasive monitoring.   So we need a document that =
does.  This is that document.   RFC3552 is a BCP.   It makes sense that =
this document would also be a BCP.   The fact that we needed RFC3552, =
and that we need this document, is not evidence that our brains have =
fallen out.   It is simply evidence that it is good to state =
expectations formally rather than hoping that everybody is on the same =
page but not making any attempt to actually get them there.


From dhc@dcrocker.net  Wed Jan  1 19:29:38 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29371AE141 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:29:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKAreKxXQfrr for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:29:37 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8661AE00D for <ietf@ietf.org>; Wed,  1 Jan 2014 19:29:37 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s023TPc1005847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 Jan 2014 19:29:29 -0800
Message-ID: <52C4DCBB.2020509@dcrocker.net>
Date: Wed, 01 Jan 2014 19:27:55 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>
In-Reply-To: <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.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.66]); Wed, 01 Jan 2014 19:29:29 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 03:29:38 -0000

On 1/1/2014 7:11 PM, Ted Lemon wrote:
> We used to routinely handwave about security.   We've gotten better about that.   RFC3552 is why.


No it's not.

It's useful, but had nothing at all to do with the strategic change. 
That came much earlier and was the result of policy changes in IESG 
requirements on specs.

The real lesson from that was the remarkably vague and obstructionist 
process that took place for years, until we started getting concrete.

The RFC is the result of that realization.  In other words, it's not 
that it enabled less handwaving but that the realization we needed to 
stop handwaving that enabled it.

Note that the current draft lacks any specificity and, therefore, leaves 
us with a similar vagueness as we used to have about security 
considerations.

To repeat from earlier:  the draft's goal and the draft are worthy for 
pursuit, but we are currently clueless about how to apply it.

Clueless.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From melinda.shore@gmail.com  Wed Jan  1 19:39:53 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3AAE1ADF24 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:39:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wKmyDw-n8adT for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:39:52 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5533B1ACC8A for <ietf@ietf.org>; Wed,  1 Jan 2014 19:39:52 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id rd3so14088441pab.13 for <ietf@ietf.org>; Wed, 01 Jan 2014 19:39:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=sF25VXxHwJqLuUUVoZiyEE55caWArloxv/ds5mBgeDY=; b=AuKyiq437C6F6yPoJFwfJmTAiqTjCjYMg90MfQfgHGDXbiGTe8NhF/vOgoZsGbZH8Q FsqC8iV3lJjyqUlrXdJAInlPEAeK6f9lgjBYNbwH9t1ANDp3dTgkWiDTojFNX5aDqT0q McyJ7aamX19HmVxHrecQJUj3bGGRZxAF41sDeducODRe05mP2NnwZHDoenM0ZF6F9D17 2srENGgaQa4wJ6oT+OZPOY5rVDQsQa56qj/ymVcfAtFT7ewSFsDEwWCR/jabHHZk2Xlv ONdthHvXyRYp2+gEGDnMw6C0TipxdOU4nJNYlXahXZLLCmOUV6zyDh0SLtccOehnVai6 BeDw==
X-Received: by 10.67.8.102 with SMTP id dj6mr85198640pad.10.1388633985650; Wed, 01 Jan 2014 19:39:45 -0800 (PST)
Received: from spandex.local (63-140-85-118.nwc.dsl.dynamic.acsalaska.net. [63.140.85.118]) by mx.google.com with ESMTPSA id os1sm43715443pac.20.2014.01.01.19.39.42 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 19:39:44 -0800 (PST)
Message-ID: <52C4DF7D.3010509@gmail.com>
Date: Wed, 01 Jan 2014 18:39:41 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>
In-Reply-To: <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 03:39:54 -0000

On 1/1/14 6:11 PM, Ted Lemon wrote:
> On Jan 1, 2014, at 6:07 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>> I'm sorry, but when we get to the point where we need to point to
>> an RFC to stop progress on a document that has obvious
>> vulnerabilities, our brains have fallen out.
> 
> This is counterfactual.   We used to routinely handwave about
> security.  

We still routinely handwave about security.  It's an afterthought
in entirely too many cases.  Drafts are adopted by working groups
while still having security considerations sections that consist
in their entirety of "TBD."  3552's impacts have been, I think,
on how documents are reviewed more than on how documents are
developed.

One of the reasons I'm somewhat annoyed about the wave of
gasbaggery and pontification that has followed truly disturbing
revelations about the extent to which the US government has
undermined privacy and compromised security technologies is
that work which might have helped provide tools to mitigate
some of the soft spots in IETF work has been backburnered in
favor of no small amount of unfocused grandiosity that doesn't
actually change much.

At any rate this draft is not RFC3552.  3552 provides very specific
guidelines for what needs to be considered in
writing^H^H^H^H^H^H^H^Hreviewing security considerations.

It is tempting to just let this through last call in hopes that
once it's done we can come back around to prioritizing work like
fixing PKI but I'd be very sorry indeed to see this published as a
BCP.

Melinda

From hallam@gmail.com  Wed Jan  1 19:42:13 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B068C1AE143 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:42:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pLnfZzCoL26H for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:42:11 -0800 (PST)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id DDF131ADFAD for <ietf@ietf.org>; Wed,  1 Jan 2014 19:42:10 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id b8so7132283lan.27 for <ietf@ietf.org>; Wed, 01 Jan 2014 19:42:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f0fMpIS1qPsSechpBjFBdIibQRA7ZqVSmNQag2jS2xM=; b=Th2GEi0ulNmaNx7TL2tYvDNO2mbgxAvEBafVHQ9WiLumdR+eCxibEFQMqutxuyziNc eC77b+3MiyKrHXqgmqD0AHE17JMjfMVoEb6FyxfUdMm665i0RohTPvlfXi5i6H9oqWFs S95hwYstgVfPrV/pslgSOxI1ko9eezPxaUZ38Xn+H2b8z1qsHI+4QDvOLdeJVuqiuBBs RBZ0d7xanuz4JfAV87CoEiFOxdurmh1I+tKFXDrcR9phcmEjn+zhrVWY8MnVb9jUUhi6 /Af+vB2DrXRJa+n8C4MkcbokwSHU52LLZy7XZxBEy/9XBLOJKaaQUSMBNrvhDOjwBDye uyow==
MIME-Version: 1.0
X-Received: by 10.112.168.199 with SMTP id zy7mr1717994lbb.68.1388634122286; Wed, 01 Jan 2014 19:42:02 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Wed, 1 Jan 2014 19:42:02 -0800 (PST)
In-Reply-To: <CAPv4CP-d-tH68g=w4pfn8YB2wmrj+wK7RojnZtgUwemU032X8A@mail.gmail.com>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <A6C36ED1-F014-4294-8F2F-FAA569341E89@checkpoint.com> <52C46959.3080905@gmail.com> <52C47605.9070607@cs.tcd.ie> <52C476EB.6010604@dcrocker.net> <20140101203451.GA6722@mx1.yitter.info> <CAPv4CP-d-tH68g=w4pfn8YB2wmrj+wK7RojnZtgUwemU032X8A@mail.gmail.com>
Date: Wed, 1 Jan 2014 22:42:02 -0500
Message-ID: <CAMm+LwiYjavcFUoA8KjTzgAGOveOQnQgGVoXu-L-GHnWDeuQkw@mail.gmail.com>
Subject: Re: Status (was: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2691494fb9e04eef493a0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 03:42:13 -0000

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

On Wed, Jan 1, 2014 at 7:42 PM, Scott Brim <scott.brim@gmail.com> wrote:

> On Wed, Jan 1, 2014 at 3:34 PM, Andrew Sullivan <ajs@anvilwalrusden.com>
> wrote:
> > On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:
> >> ps.  My own suggestion is Experimental.
> >
> > Please, no.  That status has been abused enough.  What would you be
> > trying to learn by this experiement?  What would the conditions be
> > that you would conclude you knew the answer?  If you can't answer
> > those questions, "Experimental" is just wrong.
>
> Right. This is not a protocol that needs field testing, it's a
> statement of policy.
>
> The thing that needs to be clarified is apparently what the policy is.
>

+1

The problem here in my view is that the appropriate privacy protections
depend on what level of the stack a protocol sits. And so it is not
appropriate to say that 'every protocol must do <splunge> because it is
only appropriate to address certain concerns at certain layers.

For example, attempting to address traffic or meta data leakage at the
application layer is generally a bad plan because that information is
needed to route the data packets.


It is not clear to me that the IETF can actually address traffic privacy
because that probably requires changes at the link layer. Yes, I know about
TOR but the privacy protections come at a huge cost in efficiency and use
of TOR is sufficiently limited that when Harvard had the bomb scare the
other week, the authorities simply brought the five people using TOR on
campus in for questioning to find the culprit.

If I am giving packets to a carrier and expect them to route them to their
destination then I kind of expect them to know where they are being sent.

We could certainly propose link layer schemes that would allow the carrier
to avoid leaking the information to a third party but those seem to be
'IEEE' territory rather than IETF territory.


Where I see the document being useful is not necessarily as a pass/fail
criteria for standards proposals but as a basis for chartering new WGs. I
have some proposals and so do others. Should we be looking for one working
group, two, many? How should the effort relate to past work, etc?

For the past 20 years the bulk of IETF work has been driven by enterprise
and government security concerns rather than end user concerns. So one
consequence is that the protocols we have are only 'good enough for
government work'. IPSEC and S/MIME work about as well as my Palm Treo did.
The Treo was certainly adequate for my business needs at the time but it
was not an iPhone and not even close.

IPSEC could have worked so much better, so could S/MIME and PGP. There
isn't an enterprise business case to do that but the work is essential if
we are going to get a billion people using a security protocol.


I now have running code (incomplete but it does run) that demonstrates that
'frictionless cryptography' for email is achievable using existing clients
(no plug ins) and a few slight changes in approach. By frictionless I mean
that sending and receiving encrypted mail requires absolutely no more
effort than normal mail. That is ZERO additional mouse clicks.

We could have done this ten years ago but the enterprise market that buys
S/MIME and OpenPGP products does not demand frictionless cryptography. Only
the general public is that demanding.



-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Jan 1, 2014 at 7:42 PM, Scott Brim <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:scott.brim@gmail.com" target=3D"_blank">scott.brim@gmail.co=
m</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 Wed, Jan 1, 2014 at 3:3=
4 PM, Andrew Sullivan &lt;<a href=3D"mailto:ajs@anvilwalrusden.com">ajs@anv=
ilwalrusden.com</a>&gt; wrote:<br>

&gt; On Wed, Jan 01, 2014 at 12:13:31PM -0800, Dave Crocker wrote:<br>
&gt;&gt; ps. =A0My own suggestion is Experimental.<br>
&gt;<br>
&gt; Please, no. =A0That status has been abused enough. =A0What would you b=
e<br>
&gt; trying to learn by this experiement? =A0What would the conditions be<b=
r>
&gt; that you would conclude you knew the answer? =A0If you can&#39;t answe=
r<br>
&gt; those questions, &quot;Experimental&quot; is just wrong.<br>
<br>
</div>Right. This is not a protocol that needs field testing, it&#39;s a<br=
>
statement of policy.<br>
<br>
The thing that needs to be clarified is apparently what the policy is.<br><=
/blockquote><div><br></div><div>+1=A0</div><div><br></div><div>The problem =
here in my view is that the appropriate privacy protections depend on what =
level of the stack a protocol sits. And so it is not appropriate to say tha=
t &#39;every protocol must do &lt;splunge&gt; because it is only appropriat=
e to address certain concerns at certain layers.</div>
<div><br></div><div>For example, attempting to address traffic or meta data=
 leakage at the application layer is generally a bad plan because that info=
rmation is needed to route the data packets.=A0</div><div><br></div><div>
<br></div><div>It is not clear to me that the IETF can actually address tra=
ffic privacy because that probably requires changes at the link layer. Yes,=
 I know about TOR but the privacy protections come at a huge cost in effici=
ency and use of TOR is sufficiently limited that when Harvard had the bomb =
scare the other week, the authorities simply brought the five people using =
TOR on campus in for questioning to find the culprit.</div>
<div><br></div><div>If I am giving packets to a carrier and expect them to =
route them to their destination then I kind of expect them to know where th=
ey are being sent.=A0</div><div><br></div><div>We could certainly propose l=
ink layer schemes that would allow the carrier to avoid leaking the informa=
tion to a third party but those seem to be &#39;IEEE&#39; territory rather =
than IETF territory.</div>
<div><br></div><div><br></div><div>Where I see the document being useful is=
 not necessarily as a pass/fail criteria for standards proposals but as a b=
asis for chartering new WGs. I have some proposals and so do others. Should=
 we be looking for one working group, two, many? How should the effort rela=
te to past work, etc?</div>
</div><div><br></div><div>For the past 20 years the bulk of IETF work has b=
een driven by enterprise and government security concerns rather than end u=
ser concerns. So one consequence is that the protocols we have are only &#3=
9;good enough for government work&#39;. IPSEC and S/MIME work about as well=
 as my Palm Treo did. The Treo was certainly adequate for my business needs=
 at the time but it was not an iPhone and not even close.</div>
<div><br></div><div>IPSEC could have worked so much better, so could S/MIME=
 and PGP. There isn&#39;t an enterprise business case to do that but the wo=
rk is essential if we are going to get a billion people using a security pr=
otocol.</div>
<div><br></div><div><br></div><div>I now have running code (incomplete but =
it does run) that demonstrates that &#39;frictionless cryptography&#39; for=
 email is achievable using existing clients (no plug ins) and a few slight =
changes in approach. By frictionless I mean that sending and receiving encr=
ypted mail requires absolutely no more effort than normal mail. That is ZER=
O additional mouse clicks.=A0</div>
<div><br></div><div>We could have done this ten years ago but the enterpris=
e market that buys S/MIME and OpenPGP products does not demand frictionless=
 cryptography. Only the general public is that demanding.</div><div><br>
</div><div><br></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2691494fb9e04eef493a0--

From hallam@gmail.com  Wed Jan  1 19:58:51 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE6E1AE17B for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gqpw7UgVHt6s for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 19:58:48 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3311AE17A for <ietf@ietf.org>; Wed,  1 Jan 2014 19:58:47 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id u14so7025648lbd.14 for <ietf@ietf.org>; Wed, 01 Jan 2014 19:58:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ypyCvngl8nZTXsZlUOtG2VJFpXZamUy/gz3ThOi88Ns=; b=d6Tdyb8yhckjyNywabY7C3vmj8DBnWJjfDOWB3R7VwexwUXnw/baGFioqnUDdYg487 YPSLHUO99Zs/xk2OnP5lKucGOtftTSNCmpOpzlPHqTytOMXsDd+fmWuioJpn2+m/30tR nuIh0NJGgKfJOELlWDeiLiDFvmu5ghWk//UTKCzcIhMQ8uYmrBQLUpU1MRzQs8ts3fCi PgxCkGeJ5UKQfGagtEzKkcH7Gz8FBAC0t2SMyuwO+CORmgWzWeT/u5cyWsGvb/E8IGR7 ETb96uhG8gXwr2RMn7ozyE+NeEnevcY+oRPe4TmOID1aBLTVy0EBLseoQ8DkKtcuvzC7 Otvw==
MIME-Version: 1.0
X-Received: by 10.112.138.70 with SMTP id qo6mr17302101lbb.34.1388635120634; Wed, 01 Jan 2014 19:58:40 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Wed, 1 Jan 2014 19:58:40 -0800 (PST)
In-Reply-To: <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
Date: Wed, 1 Jan 2014 22:58:40 -0500
Message-ID: <CAMm+LwhCk4KcbyLR6FpeOj+Bg-EvEq_zHNHOs2dsMOpNfix_kw@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e0112c02c16911f04eef4cf6d
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 03:58:51 -0000

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

On Tue, Dec 31, 2013 at 3:48 PM, John C Klensin <john-ietf@jck.com> wrote:

To take an example I hope is not taken as a proposal, the
> security of SMTP against in-transit interception and monitoring
> of messages could a considerably improved by eliminating
> relaying  (i.e., the application-level store and forward design
> of the protocol).


I like that idea a lot actually.

A lot of the limitations on mail come from the assumption that I will
accept a 4Mb mail message (current Gmail max) from anyone who wants to send
it to me.

If we were designing a new mail protocol for sending huge blobs of data we
would probably start with the rule that the sender is responsible for
storing the bulk of the message until the recipient has decided that they
want to accept it.

Essentially this would be merging dropbox type capabilities into mail.



>  That would have a number of profoundly bad
> effects, at least IMO, but it would enable some rather simple
> methods of mitigating the threat that are of arguable or complex
> utility if relaying is permitted.


I can't see that it would have bad effects. It would only be possible in a
completely different mail infrastructure that was not SMTP.

OK, it is technically possible to do just that with current SMTP
extensions, all that would be required is for an SMTP server to start
accepting some options that are currently reserved for SUBMIT.

But I would not want to do that in SMTP because the only infrastructure
that could benefit from the change in the model would have to be written
from scratch anyway (But it is still significant prior art.)


 If the Apps ADs ever get
> around to getting back to me about a months-old request to
> discuss practical methods of moving RFCs 5321 and 5322 forward
> to Internet Standard, I don't think it is reasonable to
> legitimize an attempt to impose a requirement that starts with
> "RFCnnnn says that monitoring threats should be mitigated where
> possible, so we have to return to first principles and debate
> whether SMTP should have relaying" when, without such a
> statement, we'd be able to say "widely deployed, useful, and
> working that way for a few decades, we just don't need to have
> that discussion about the base protocols".
>

I think trying to retrofit such features to SMTP would be a very bad plan.
There are times to start from a clean slate and this would be one of them.
Every part of a privacy protected email transport would have to be audited
for privacy protection. There would be no way to leverage the legacy base.
So it would be an entirely new protocol. Probably building on JSON/REST
style of design rather than RFC821.

Now we could argue over whether such a scheme is practical at all. But I
don't think building on top of SMTP would help in this particular case.

So no, I don't see that the pervasive surveillance document should impact
RFC5381 going to STANDARD. Just do it already.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Dec 31, 2013 at 3:48 PM, John C Klensin <span dir=3D"ltr">&lt;<a href=
=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</=
span> wrote:</div>
<div class=3D"gmail_quote"><br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204=
,204);border-left-style:solid;padding-left:1ex">
To take an example I hope is not taken as a proposal, the<br>
security of SMTP against in-transit interception and monitoring<br>
of messages could a considerably improved by eliminating<br>
relaying =A0(i.e., the application-level store and forward design<br>
of the protocol). </blockquote><div><br></div><div>I like that idea a lot a=
ctually.</div><div><br></div><div>A lot of the limitations on mail come fro=
m the assumption that I will accept a 4Mb mail message (current Gmail max) =
from anyone who wants to send it to me.=A0</div>
<div><br></div><div>If we were designing a new mail protocol for sending hu=
ge blobs of data we would probably start with the rule that the sender is r=
esponsible for storing the bulk of the message until the recipient has deci=
ded that they want to accept it.</div>
<div><br></div><div>Essentially this would be merging dropbox type capabili=
ties into mail.</div><div><br></div><div>=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-lef=
t-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
=A0That would have a number of profoundly bad<br>
effects, at least IMO, but it would enable some rather simple<br>
methods of mitigating the threat that are of arguable or complex<br>
utility if relaying is permitted. </blockquote><div><br></div><div>I can&#3=
9;t see that it would have bad effects. It would only be possible in a comp=
letely different mail infrastructure that was not SMTP.</div><div><br>
</div><div>OK, it is technically possible to do just that with current SMTP=
 extensions, all that would be required is for an SMTP server to start acce=
pting some options that are currently reserved for SUBMIT.=A0</div><div><br=
>
</div><div>But I would not want to do that in SMTP because the only infrast=
ructure that could benefit from the change in the model would have to be wr=
itten from scratch anyway (But it is still significant prior art.)</div>
<div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">=A0If the Apps ADs ever get<=
br>

around to getting back to me about a months-old request to<br>
discuss practical methods of moving RFCs 5321 and 5322 forward<br>
to Internet Standard, I don&#39;t think it is reasonable to<br>
legitimize an attempt to impose a requirement that starts with<br>
&quot;RFCnnnn says that monitoring threats should be mitigated where<br>
possible, so we have to return to first principles and debate<br>
whether SMTP should have relaying&quot; when, without such a<br>
statement, we&#39;d be able to say &quot;widely deployed, useful, and<br>
working that way for a few decades, we just don&#39;t need to have<br>
that discussion about the base protocols&quot;.<br></blockquote><div><br></=
div><div>I think trying to retrofit such features to SMTP would be a very b=
ad plan. There are times to start from a clean slate and this would be one =
of them. Every part of a privacy protected email transport would have to be=
 audited for privacy protection. There would be no way to leverage the lega=
cy base. So it would be an entirely new protocol. Probably building on JSON=
/REST style of design rather than RFC821.</div>
<div><br></div><div>Now we could argue over whether such a scheme is practi=
cal at all. But I don&#39;t think building on top of SMTP would help in thi=
s particular case.</div><div><br></div><div>So no, I don&#39;t see that the=
 pervasive surveillance document should impact RFC5381 going to STANDARD. J=
ust do it already.</div>
</div><div><br></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0112c02c16911f04eef4cf6d--

From dhc@dcrocker.net  Wed Jan  1 20:08:33 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A29351AE00A for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HSev_dRKG1P7 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:08:32 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 803671ADF5F for <ietf@ietf.org>; Wed,  1 Jan 2014 20:08:32 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0248LU8006250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 1 Jan 2014 20:08:24 -0800
Message-ID: <52C4E5DA.4020305@dcrocker.net>
Date: Wed, 01 Jan 2014 20:06:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>
In-Reply-To: <52C4DF7D.3010509@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.66]); Wed, 01 Jan 2014 20:08:24 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 04:08:33 -0000

On 1/1/2014 7:39 PM, Melinda Shore wrote:
> work which might have helped provide tools to mitigate
> some of the soft spots in IETF work has been backburnered in
> favor of no small amount of unfocused grandiosity that doesn't
> actually change much.


For all of our combined verbosity about privacy  abstractions and 
policy, I haven't noticed folk trying to propose specifics and getting 
ignored or backburnered.

I fear that we are indulging in a cause/effect error.  The probably 
reason we aren't pursuing needed specifics is that we don't know how to.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Wed Jan  1 20:31:29 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30CC31ADDBF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGe3xG4iQUu4 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:31:27 -0800 (PST)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 97E231AC85E for <ietf@ietf.org>; Wed,  1 Jan 2014 20:31:27 -0800 (PST)
Received: by mail-pa0-f43.google.com with SMTP id bj1so14131079pad.2 for <ietf@ietf.org>; Wed, 01 Jan 2014 20:31:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vA0uzEaBhi9eqP+1FSeDDaAj+Stb66Y7W0Td7WM88xQ=; b=JyFv03QNZ1ptc4/D3QQJd4KZVlx1IGn4W3Aiy6OGM0Ibh46d66/Evzg31iSz+I3pg1 CfUA0E1JzY11NImW6wECg3pqSxET6nKI/RrviqNUeBjLeuL7D4EUOBuwLBj/PDZdf+kc ab5SRChjT7vwHUW0bhSh4q820+bkp8OE6CI4xSzXiZpDxNQfa2Y/QU1F6SrgWn/vVuLA DUaW0f0ddH3LOGhkXe2XxM+wJO93B2xOrFN5ii3b4tlfesW5vzJmgnAGXQGkRr3XEKIN D5u7QsZx/IujXVjVFLg9XW3rIHib3kGIaV0RVR7R5fXG48CnBN4reRH241lFpauaD1bH 6ihA==
X-Received: by 10.66.197.164 with SMTP id iv4mr86070855pac.18.1388637080936; Wed, 01 Jan 2014 20:31:20 -0800 (PST)
Received: from [192.168.178.21] (137.199.69.111.dynamic.snap.net.nz. [111.69.199.137]) by mx.google.com with ESMTPSA id ha10sm98422544pbd.17.2014.01.01.20.31.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 20:31:20 -0800 (PST)
Message-ID: <52C4EB9C.108@gmail.com>
Date: Thu, 02 Jan 2014 17:31:24 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DCBB.2020509@dcrocker.net>
In-Reply-To: <52C4DCBB.2020509@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 04:31:29 -0000

On 02/01/2014 16:27, Dave Crocker wrote:
> On 1/1/2014 7:11 PM, Ted Lemon wrote:
>> We used to routinely handwave about security.   We've gotten better
>> about that.   RFC3552 is why.
> 
> 
> No it's not.
> 
> It's useful, but had nothing at all to do with the strategic change.
> That came much earlier and was the result of policy changes in IESG
> requirements on specs.

Yes. As I mentioned in Vancouver, it was RFC 2316 that stated an aspiration
and RFC 3365 that set technical requirements (whereas 3352 set writing
requirements; I should have mentioned that too). Surely the present draft
is only trying to state the aspiration - there's a lot more work to do before
the rest is ready to publish.

    Brian

> 
> The real lesson from that was the remarkably vague and obstructionist
> process that took place for years, until we started getting concrete.
> 
> The RFC is the result of that realization.  In other words, it's not
> that it enabled less handwaving but that the realization we needed to
> stop handwaving that enabled it.
> 
> Note that the current draft lacks any specificity and, therefore, leaves
> us with a similar vagueness as we used to have about security
> considerations.
> 
> To repeat from earlier:  the draft's goal and the draft are worthy for
> pursuit, but we are currently clueless about how to apply it.
> 
> Clueless.
> 
> d/
> 

From melinda.shore@gmail.com  Wed Jan  1 20:34:31 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 409131ADFF7 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gsBLN-lWVuX1 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 20:34:29 -0800 (PST)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 942D41AC85E for <ietf@ietf.org>; Wed,  1 Jan 2014 20:34:29 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so13650666pde.41 for <ietf@ietf.org>; Wed, 01 Jan 2014 20:34:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=3l8dAjRfpmZ5Tt8EJ70k+smReCGkAXzUGesdF/w0JPs=; b=FcSLHD5siMeVIFRppZ8ugR4zXFllk4xcXeyN3nM41ZCe5RDv89zq1hIOFonogNsRxr ncDXl7LhYTofdImBu39SCTr/eV8YUjD/+P22NyuqrsR+JDqVLQAiyChb3bANYYRFEm3A CM3e+eweGII4Kbtx1I8AElikeB3ppoGIdmPn4Xx+SpqlR6aT8hHAIuKUkpvYaJJ6H03D n8XWr+QD2sKkiw3wninRUHJW6Adwf4FY4b+nGunPsqH4OM66mrQESbLSkaxth2OxURAk YloeSKh88yxR6vBAgskxy7jj86c33tzV547kZWGR4amekpcSw4DbuL+D8sPruZzbssaw O+zg==
X-Received: by 10.68.6.66 with SMTP id y2mr85463491pby.60.1388637262911; Wed, 01 Jan 2014 20:34:22 -0800 (PST)
Received: from spandex.local (63-140-85-118.nwc.dsl.dynamic.acsalaska.net. [63.140.85.118]) by mx.google.com with ESMTPSA id nl7sm98462887pbc.6.2014.01.01.20.34.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jan 2014 20:34:21 -0800 (PST)
Message-ID: <52C4EC4A.5050500@gmail.com>
Date: Wed, 01 Jan 2014 19:34:18 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net>
In-Reply-To: <52C4E5DA.4020305@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 04:34:31 -0000

On 1/1/14 7:06 PM, Dave Crocker wrote:
> I fear that we are indulging in a cause/effect error.  The probably
> reason we aren't pursuing needed specifics is that we don't know how to.

That may be the case, and that this draft is a Something Must
Be Done document.  That is fine, and we all more-or-less seem
to be in agreement that something must be done.  I think,
however, that a Something Must Be Done document probably does
not belong on the standards track.  A This is What We'll Do
document does.  Concern about unforeseen consequences from
publishing a vague document seems appropriate to me.

Melinda



From mcr@sandelman.ca  Wed Jan  1 21:02:13 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFFDF1AE216 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 21:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.009
X-Spam-Level: *
X-Spam-Status: No, score=1.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6NDfn_ZYZjVL for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 21:02:11 -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 636AD1ADDBF for <ietf@ietf.org>; Wed,  1 Jan 2014 21:02:11 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F021D20044 for <ietf@ietf.org>; Thu,  2 Jan 2014 01:17:02 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 3BA6D64647; Thu,  2 Jan 2014 00:02:03 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D9CF063AD7 for <ietf@ietf.org>; Thu,  2 Jan 2014 00:02:03 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-Reply-To: <52C4DF7D.3010509@gmail.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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
Date: Thu, 02 Jan 2014 00:02:03 -0500
Message-ID: <21962.1388638923@sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 05:02:13 -0000

Melinda Shore <melinda.shore@gmail.com> wrote:
    >>> I'm sorry, but when we get to the point where we need to point to an
    >>> RFC to stop progress on a document that has obvious vulnerabilities,
    >>> our brains have fallen out.
    >>
    >> This is counterfactual.  We used to routinely handwave about security.

    > We still routinely handwave about security.  It's an afterthought in
    > entirely too many cases.  Drafts are adopted by working groups while
    > still having security considerations sections that consist in their
    > entirety of "TBD."  3552's impacts have been, I think, on how documents
    > are reviewed more than on how documents are developed.

I don't disagree that we still handwave.
I want to address the second part of the above statement.

I don't think it's a problem that a draft gets adopted as a WG item that is
incomplete in a variety of ways, including security considerations.

Let's not continue the trend to having a WG design team prior to having a WG.

One of the *KEY* things that a too well baked draft coming in to a WG messes
up is fixing the security issues; from ambiguous and arbitrarily different
encodings, to assumptions about what "Use IPsec" might mean.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [





From l.wood@surrey.ac.uk  Wed Jan  1 21:07:27 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B92021ADDBF for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 21:07:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBlZIdv8OQPQ for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 21:07:25 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.150]) by ietfa.amsl.com (Postfix) with ESMTP id 1BA191ADBD5 for <ietf@ietf.org>; Wed,  1 Jan 2014 21:07:24 -0800 (PST)
Received: from [85.158.136.51:27693] by server-14.bemta-5.messagelabs.com id E4/F8-24200-504F4C25; Thu, 02 Jan 2014 05:07:17 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-49.messagelabs.com!1388639237!21100621!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18212 invoked from network); 2 Jan 2014 05:07:17 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 2 Jan 2014 05:07:17 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.22]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 2 Jan 2014 05:07:16 +0000
From: <l.wood@surrey.ac.uk>
To: <mcr@sandelman.ca>, <ietf@ietf.org>
Date: Thu, 2 Jan 2014 05:05:09 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8Hd90DtAzKmSXwQG2KMHc6xtQdWgAAFibP
Message-ID: <290E20B455C66743BE178C5C84F1240847E51037CB@EXMB01CMS.surrey.ac.uk>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>,<21962.1388638923@sandelman.ca>
In-Reply-To: <21962.1388638923@sandelman.ca>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 05:07:28 -0000

> I don't think it's a problem that a draft gets adopted as a WG item that =
is
> incomplete in a variety of ways, including security considerations.
>=20
> Let's not continue the trend to having a WG design team prior to having a=
 WG.

perpass is not a WG, and draft-farrell-perpass-attack is not an adopted WG =
item.

I mean, it's incomplete, and it's circumventing what process we have.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Michael Richardson [mcr@san=
delman.ca]
Sent: 02 January 2014 05:02
To: IETF Discussion
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

Melinda Shore <melinda.shore@gmail.com> wrote:
    >>> I'm sorry, but when we get to the point where we need to point to a=
n
    >>> RFC to stop progress on a document that has obvious vulnerabilities=
,
    >>> our brains have fallen out.
    >>
    >> This is counterfactual.  We used to routinely handwave about securit=
y.

    > We still routinely handwave about security.  It's an afterthought in
    > entirely too many cases.  Drafts are adopted by working groups while
    > still having security considerations sections that consist in their
    > entirety of "TBD."  3552's impacts have been, I think, on how documen=
ts
    > are reviewed more than on how documents are developed.

I don't disagree that we still handwave.
I want to address the second part of the above statement.

I don't think it's a problem that a draft gets adopted as a WG item that is
incomplete in a variety of ways, including security considerations.

Let's not continue the trend to having a WG design team prior to having a W=
G.

One of the *KEY* things that a too well baked draft coming in to a WG messe=
s
up is fixing the security issues; from ambiguous and arbitrarily different
encodings, to assumptions about what "Use IPsec" might mean.

--
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        | network architect=
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [





From daedulus@btconnect.com  Thu Jan  2 01:43:38 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 334281AE463 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 01:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T56lSCzIED6K for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 01:43:36 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe001.messaging.microsoft.com [213.199.154.204]) by ietfa.amsl.com (Postfix) with ESMTP id DB4C11AE235 for <ietf@ietf.org>; Thu,  2 Jan 2014 01:43:35 -0800 (PST)
Received: from mail35-am1-R.bigfish.com (10.3.201.227) by AM1EHSOBE008.bigfish.com (10.3.204.28) with Microsoft SMTP Server id 14.1.225.22; Thu, 2 Jan 2014 09:43:28 +0000
Received: from mail35-am1 (localhost [127.0.0.1])	by mail35-am1-R.bigfish.com (Postfix) with ESMTP id 1A4974800D8; Thu,  2 Jan 2014 09:43:28 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h2327h2336h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(13464003)(24454002)(199002)(189002)(479174003)(377454003)(51704005)(50466002)(33646001)(44716002)(62236002)(79102001)(85306002)(47776003)(63696002)(74706001)(14496001)(77982001)(59766001)(74876001)(53806001)(19580405001)(19580395003)(42186004)(83322001)(51856001)(54316002)(77156001)(77096001)(23676002)(76482001)(31966008)(74502001)(74662001)(47446002)(56816005)(89996001)(90146001)(46102001)(88136002)(4396001)(56776001)(44736004)(49866001)(47736001)(50226001)(47976001)(50986001)(76796001)(76786001)(87976001)(85852003)(87286001)(87266001)(83072002)(62966002)(66066001)(74366001)(80022001)(65816001)(80976001)(84392001)(69226001)(61296002)(81542001)(81342001)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB244; H:AMXPRD0111HT001.eurprd01.prod.exchangelabs.com; CLIP:157.56.250.117; FPR:; RD:InfoNoRecords; A:0; MX:1; LANG:en; 
Received: from mail35-am1 (localhost.localdomain [127.0.0.1]) by mail35-am1 (MessageSwitch) id 138865580635777_17427; Thu,  2 Jan 2014 09:43:26 +0000 (UTC)
Received: from AM1EHSMHS007.bigfish.com (unknown [10.3.201.239])	by mail35-am1.bigfish.com (Postfix) with ESMTP id 04F7DE0056;	Thu,  2 Jan 2014 09:43:26 +0000 (UTC)
Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by AM1EHSMHS007.bigfish.com (10.3.207.107) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 2 Jan 2014 09:43:25 +0000
Received: from AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154) by AM2PRD0710HT004.eurprd07.prod.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.395.1; Thu, 2 Jan 2014 09:43:16 +0000
Received: from AMXPRD0111HT001.eurprd01.prod.exchangelabs.com (157.56.250.117) by AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154) with Microsoft SMTP Server (TLS) id 15.0.842.7; Thu, 2 Jan 2014 09:43:15 +0000
Message-ID: <00ac01cf079e$899982c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, <dcrocker@bbiw.net>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DCBB.2020509@dcrocker.net> <52C4EB9C.108@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Thu, 2 Jan 2014 09:39:21 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-ClientProxiedBy: AMXPR07CA009.eurprd07.prod.outlook.com (10.242.64.49) To AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154)
X-Forefront-PRVS: 0079056367
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 09:43:38 -0000

----- Original Message -----
From: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
To: <dcrocker@bbiw.net>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, January 02, 2014 4:31 AM
> On 02/01/2014 16:27, Dave Crocker wrote:
> > On 1/1/2014 7:11 PM, Ted Lemon wrote:
> >> We used to routinely handwave about security.   We've gotten better
> >> about that.   RFC3552 is why.
> >
> > No it's not.
> >
> > It's useful, but had nothing at all to do with the strategic change.
> > That came much earlier and was the result of policy changes in IESG
> > requirements on specs.
>
> Yes. As I mentioned in Vancouver, it was RFC 2316 that stated an
aspiration
> and RFC 3365 that set technical requirements (whereas 3352 set writing
> requirements; I should have mentioned that too). Surely the present
draft
> is only trying to state the aspiration - there's a lot more work to do
before
> the rest is ready to publish.

And which stream, to use modern jargon, published RFC2316 and at what
status?

Gosh, shock horror:-)

Tom Petch

p.s.
2316 Report of the IAB Security Architecture Workshop. S. Bellovin.
     April 1998. (Format: TXT=19733 bytes) (Status: INFORMATIONAL)





>
>     Brian
>
> >
> > The real lesson from that was the remarkably vague and
obstructionist
> > process that took place for years, until we started getting
concrete.
> >
> > The RFC is the result of that realization.  In other words, it's not
> > that it enabled less handwaving but that the realization we needed
to
> > stop handwaving that enabled it.
> >
> > Note that the current draft lacks any specificity and, therefore,
leaves
> > us with a similar vagueness as we used to have about security
> > considerations.
> >
> > To repeat from earlier:  the draft's goal and the draft are worthy
for
> > pursuit, but we are currently clueless about how to apply it.
> >
> > Clueless.
> >
> > d/
> >
>



From stephen.farrell@cs.tcd.ie  Thu Jan  2 04:24:10 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEE551ADF5A for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PxFOVFpj838Q for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:24:06 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D62221ACC8A for <ietf@ietf.org>; Thu,  2 Jan 2014 04:24:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 46382BE5D; Thu,  2 Jan 2014 12:23:56 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53u4-wgl29RQ; Thu,  2 Jan 2014 12:23:53 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 89C8EBE58; Thu,  2 Jan 2014 12:23:53 +0000 (GMT)
Message-ID: <52C55A4F.8050200@cs.tcd.ie>
Date: Thu, 02 Jan 2014 12:23:43 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
In-Reply-To: <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 12:24:10 -0000

John,

In a number of places below, you appear to make hugely
misleading and inaccurate characterisations of the text
of the draft, to the point where I think you seem to be
spreading FUD. Can you please explain how I'm wrong in
that conclusion? Ideally via reference to the actual
text, and justification for how you make the gigantic
leaps from that text to your vastly overstated
mischaracterisations below.

Or, since I'll separately address what I guess might be
the potential concerns behind the FUD that is here, you
can if you like ignore this message and just respond to
a mail I'll send later today.

On 12/31/2013 08:48 PM, John C Klensin wrote:

> That principle is that I do not believe the IETF should be
> making statements supporting any particular religion or set of
> religious principles or, as we might say on this side of the
> pond, expressing strong support for motherhood and apple pie.

I'm sorry but I think the term religion above is purely
being used as a pejorative, and wrongly in this case. Or
maybe you can justify the use of the term via at least
some reference to the actual text of the draft?

> Statements of general concern are ok, but apparent commitments
> to action without specifics seem to me to be ill-advised.  

Disagree. Ted Lemon put it well. This draft represents the
high-order bit but there's more work on going and to be
started.

> To
> me, your document, and much of the discussion, reflects the
> reason why that principle is important: No matter what
> assurances are made to the contrary, we've seen example after
> example, general guideline after general guideline, turned into
> rigid rules during or after Last Call on particular documents
> because some AD decides that a document that doesn't match his
> (usually -- I think we've yet to have a really abusive,
> testosterone-poisoned, woman AD) ideas of how things should work
> and should therefore be blocked until the authors or WG either
> conform to whatever "requirement" supports his conclusion or
> produce an overwhelming proof that should not be necessary.  

I think that's spreading FUD to be honest. I can't see how its
anything else.

And again, as Ted said, if some AD wanted to be a pain in that
way, there's plenty of ammunition available today for that (see
the 2119 references in 3552 for an example of such ammunition
that is not used). Indeed 3552 is a fine example of why we do
not want BCPs that contain too much detail - that detail will
go out of date or not apply to new situations and overall
adds to the potential ammunition that a misguided AD could use
to badly affect ongoing work. Any such detailed guidance should
be based on reality and not be theoretical IMO and so should
emerge from what we find can actually be deployed.

This BCP will not change the potential for any AD to abuse the
IETF. Not a whit. And it really doesn't matter what happened
10 years ago or whenever you care to pick.

> I think much of that case had been made by others and was
> writing my note in that context (see below).  But maybe not.
> 
> So, at the risk of repeating something others have said, I don't
> want to see a Last Call (or, worse, post-Last Call) debate about
> whether the authors of a document that isn't seen to be secure
> enough against persuasive surveillance has done everything that
> might be possible to mitigate that risk.  

"Everything that might be possible" is a serious mis-reading of
the draft and *nothing like* what's stated in the draft. I can't
see how you get that from the text. If there is text there that
could really be mis-read that badly then please point at it so
we can fix it.

> I'm in favor of
> mitigation being considered an important consideration, just as
> I'm in favor of privacy considerations more generally being
> considered important considerations.  But I'm also in favor of
> congestion control, operational reasonableness, security
> considerations that don't directly relate to privacy including
> strong authentication when it is warranted,
> internationalization, and a slew of other things that I think we
> should be considering when protocols are adopted... and
> considered without the impediment of someone saying "well, the
> IETF adopted a formal statement that says 'Particular issue XYZ
> should be mitigated where possible' so that consideration should
> dominate the others."

"Dominate the others" is another serious mis-reading. Again, please
point at the text that has so confused you. (To be honest, I don't
think its there so am mystified that you can get this meaning
from the current text.)

> 
> My problem with going in that direction interacts with your
> draft in many ways even though I'm in agreement about the
> high-level issue.  As a description of an issue, I think it is
> fine.  When you describe and rely on the consensus reached at
> IETF 88, I start having objections because I think the questions
> were stated in a way (and context) that made disagreement with
> them, or examination of the implications and details, nearly
> impossible.

You expected to examine all the implications and details in a
room with ~1000 people?

In any case, this draft does not, and should not, try to
examine all the implications since we don't know them all yet.
Nonetheless if we don't have this BCP then we will have to
re-litgate the overall discussion many times, which will
(I predict) effectively prevent us from making progress on
the more substantive issues with protocols. That is one harm
in your position and those of others who want to wait and
do nothing until everything is "clear."

> 
> To take an example I hope is not taken as a proposal, the
> security of SMTP against in-transit interception and monitoring
> of messages could a considerably improved by eliminating
> relaying  (i.e., the application-level store and forward design
> of the protocol).  That would have a number of profoundly bad
> effects, at least IMO, but it would enable some rather simple
> methods of mitigating the threat that are of arguable or complex
> utility if relaying is permitted.  If the Apps ADs ever get
> around to getting back to me about a months-old request to
> discuss practical methods of moving RFCs 5321 and 5322 forward
> to Internet Standard, I don't think it is reasonable to
> legitimize an attempt to impose a requirement that starts with
> "RFCnnnn says that monitoring threats should be mitigated where
> possible, so we have to return to first principles and debate
> whether SMTP should have relaying" when, without such a
> statement, we'd be able to say "widely deployed, useful, and
> working that way for a few decades, we just don't need to have
> that discussion about the base protocols".

I have no idea how that is relevant. Are you suggesting that
this BCP will suddenly mean that bad ideas get airtime when
they previously would have been discarded? That seems silly.

> 
>>From that point of view, when you say "Those developing IETF
> specifications need to be able to describe..." [Section 2,
> paragraph 4], I get the chills because, despite the mitigating
> (sic) second sentence, the third, and the subjectiveness of "a
> good answer", allows someone with the inclination to block
> almost any application-layer protocol until it is encumbered
> sufficiently with privacy decorations to make it unattractive
> and unlikely to be adopted in practice.  I would like the 5th
> paragraph of Section 2, except that I don't look forward to the
> pain I believe this document is likely to cause as that
> "appropriate balance" emerges and is visited and re-visited.

See above. I think that's a frankly weird mis-reading of the text
which is pretty clear that pervasive monitoring is to be addressed
in the same way as any other vulnerability.

> 
> Now to put my earlier note and your questions about it and its
> relevance in context...
> 
> 
> --On Wednesday, December 11, 2013 21:19 +0000 Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
> 
>> I've a question about the relevance of your comment
>> John:
>>
>> On 12/11/2013 08:53 PM, John C Klensin wrote:
>>>  if encryption
>>> were pervasive
>>
>> The draft in question does not call for that. It calls
>> for proper consideration of the pervasive monitoring
>> attack and work to mitigate that.
> 
>> Use of encryption for confidentiality will be a relevant
>> mitigation for various protocols, but to comment as if
>> this draft called for ubiquitous confidentiality seems
>> very odd if one has read the draft.
> 
> Oh, I had read the draft, and read the newer version this week.
> What I tried to do was to think about making the broad and
> general statements in the draft actionable and what that would
> mean.  Remembering that I work at the application layer where
> almost all data that users might consider sensitive occurs
> directly rather than by side-effect, our toolkit is rather
> limited.    At least at the application level, if there are ways
> with most protocols to significantly mitigate pervasive
> surveillance that do not replace it with ubiquitous
> confidentiality (or with pervasive encryption, which is what I
> actually said) and that fall within the scope of IETF protocols,
> I don't know what they might be.    

Eh... not sending PII when its not needed in a protocol? I
believe I answered that last month. [1] What's not clear
about that answer?

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

> 
> Actually, I do, but I think the IETF would find them
> unpalatable, and that brings me back to my concern about this
> document and its apparent attempt (whether you intended it or
> not) to move mitigation of pervasive surveillance to the front
> of the tradeoff line.  

That is not an accurate description of the text. You are
radically mis-interpreting what it says. There is nothing
in the draft that moves anything to front of any line.

> For example, effective surveillance of
> traffic content by monitoring of Internet links would become
> considerably more difficult if we (pervasively) went back to
> routing at the packet (or datagram) level and optimized our
> routing algorithms to prefer diverse paths within a stream or
> flow.  At least as I understand it, that would largely eliminate
> the use of MPLS 

Saying that this BCP would eliminate MPLS approaches being
purely FUD.

> and would slow things down overall unless ISPs
> started engineering their networks for more path diversity
> between any two endpoints (presumably increasing costs for the
> amount of traffic handled).   But it would make interception of
> a single flow for surveillance purposes a lot more unpleasant
> and costly for the monitoring body without requiring encryption.
> There are other examples but, as far as I know, they are equally
> unattractive... unless frustrating pervasive surveillance
> becomes out primary objective (and, as you point out in the last
> paragraph of Section 2, that of others).  

"Primary objective" bears no resemblance to the draft at all.

>> John - can you say what part of the draft caused you to
>> incorrectly conclude that "pervasive encryption" (whatever
>> that means) is even being discussed never mind recommended?
> 
> I hope that the above responds to that question, whether we
> agree about the conclusions or not.

The above does not quote any text and IMO hugely mis-states
what is in the draft. I have no clue how you could interpret
the text as you claim to have above.

S

> 
> best regards and best wishes for the new year,
>    john
> 
> 
> 
> 

From dhc@dcrocker.net  Thu Jan  2 04:35:12 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595601AE342 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UhX9hdd5yLV for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:35:11 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 192D71AD72A for <ietf@ietf.org>; Thu,  2 Jan 2014 04:35:11 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s02CYtsm011186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jan 2014 04:34:58 -0800
Message-ID: <52C55C95.4000806@dcrocker.net>
Date: Thu, 02 Jan 2014 04:33:25 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C55A4F.8050200@cs.tcd.ie>
In-Reply-To: <52C55A4F.8050200@cs.tcd.ie>
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.66]); Thu, 02 Jan 2014 04:34:58 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 12:35:12 -0000

On 1/2/2014 4:23 AM, Stephen Farrell wrote:
> This BCP will not change the potential for any AD to abuse the
> IETF. Not a whit. And it really doesn't matter what happened
> 10 years ago or whenever you care to pick.


Stephen,

I think this assessment is incorrect, based on the earlier history with 
Security Considerations.

For years, we were faced with a requirement to do these Considerations, 
but had no guidance about what would satisfy it and what wouldn't.  As a 
consequence, working groups had to play a guessing game -- sometimes for 
months -- as to what would satisfy the blocking AD.

Of course, that potential is always present, and not just for Security 
Considerations.  But it is exacerbated by a document with formal status 
that makes broad requirements but affords working groups no guidance 
about how to satisfy those requirements.

Again, this is why I think your document should be issued with 
non-normative status.

It's good to have the statements it makes.  It's bad to give them 
normative force until we have experience trying to apply it.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stephen.farrell@cs.tcd.ie  Thu Jan  2 04:48:15 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0C81AE19E for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:48:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3vsIVBvhgpDp for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:48:14 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id DD7B91AE16A for <ietf@ietf.org>; Thu,  2 Jan 2014 04:48:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id AE661BE5D; Thu,  2 Jan 2014 12:48:06 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Eb7c1dajgzX; Thu,  2 Jan 2014 12:48:05 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 678D5BE35; Thu,  2 Jan 2014 12:48:05 +0000 (GMT)
Message-ID: <52C55FFB.3080006@cs.tcd.ie>
Date: Thu, 02 Jan 2014 12:47:55 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C55A4F.8050200@cs.tcd.ie> <52C55C95.4000806@dcrocker.net>
In-Reply-To: <52C55C95.4000806@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 12:48:15 -0000

Hi Dave,

On 01/02/2014 12:33 PM, Dave Crocker wrote:
> On 1/2/2014 4:23 AM, Stephen Farrell wrote:
>> This BCP will not change the potential for any AD to abuse the
>> IETF. Not a whit. And it really doesn't matter what happened
>> 10 years ago or whenever you care to pick.
> 
> 
> Stephen,
> 
> I think this assessment is incorrect, based on the earlier history with
> Security Considerations.

We disagree about the assessment, though not the history.

> For years, we were faced with a requirement to do these Considerations,
> but had no guidance about what would satisfy it and what wouldn't.  As a
> consequence, working groups had to play a guessing game -- sometimes for
> months -- as to what would satisfy the blocking AD.
> 
> Of course, that potential is always present, and not just for Security
> Considerations.  But it is exacerbated by a document with formal status
> that makes broad requirements but affords working groups no guidance
> about how to satisfy those requirements.
> 
> Again, this is why I think your document should be issued with
> non-normative status.

I do get the concern.

> It's good to have the statements it makes.  It's bad to give them
> normative force until we have experience trying to apply it.

I think someone else pointed out yesterday that the normative
force here is only to the effect that pervasive monitoring needs
to be considered, but nothing normative is stated here about how
that is to be done. That latter is being worked on but will take
quite a while before we can really claim its based on reality.
I also think waiting until we have that experience will be
damaging.

- It would take years.
- The result would likely be this statement plus some details
  that will be relatively quickly be out of date.
- In this space, it will be hard to know which mitigations have
  really been effective.

So waiting would not be a good approach.

As to status: 2026 section 5 says:

   The BCP subseries of the RFC series is designed to be a way to
   standardize practices and the results of community deliberations.  A
   BCP document is subject to the same basic set of procedures as
   standards track documents and thus is a vehicle by which the IETF
   community can define and ratify the community's best current thinking
   on a statement of principle or on what is believed to be the best way
   to perform some operations or IETF process function.

This draft is precisely a statement of principle and hence ideally
suited to be a BCP.

I just don't think it'd be sane to require every statement of
principle to be accompanied by all the assembly instructions. And
it'd be wrong to never state principles.

Cheers,
S.



> 
> d/

From stephen.farrell@cs.tcd.ie  Thu Jan  2 04:57:07 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2074F1AE0C8 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4bYkWrmlfzP for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 04:57:06 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id F3E251ADF50 for <ietf@ietf.org>; Thu,  2 Jan 2014 04:57:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B7B82BE5F; Thu,  2 Jan 2014 12:56:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CT5jbW9pgi4I; Thu,  2 Jan 2014 12:56:57 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 291FBBE5D; Thu,  2 Jan 2014 12:56:57 +0000 (GMT)
Message-ID: <52C5620E.6030105@cs.tcd.ie>
Date: Thu, 02 Jan 2014 12:56:46 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, dcrocker@bbiw.net
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com>
In-Reply-To: <52C4EC4A.5050500@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 12:57:07 -0000

Melinda,

On 01/02/2014 04:34 AM, Melinda Shore wrote:
> On 1/1/14 7:06 PM, Dave Crocker wrote:
>> I fear that we are indulging in a cause/effect error.  The probably
>> reason we aren't pursuing needed specifics is that we don't know how to.
> 
> That may be the case, and that this draft is a Something Must
> Be Done document. That is fine, and we all more-or-less seem
> to be in agreement that something must be done.  I think,
> however, that a Something Must Be Done document probably does
> not belong on the standards track.  A This is What We'll Do
> document does.  Concern about unforeseen consequences from
> publishing a vague document seems appropriate to me.

The draft is not vague. Its high-level, which is quite
different. If there are parts that are vague please point
those out and we can try to fix them.

Waiting until we have a set of (not one!) this-is-what-we'll-do
documents would be a bad outcome for at least the reasons I
outlined in response to Dave just now.

Calling this a "Something Must Be Done" document seems
needlessly dismissive. Can you say how that's intended to
help?

I think we have a proof by demonstration that we have not
sufficiently considered this attack. The proposed BCP is
a first, high-level step in remedying that situation. And
if we can get WGs to properly consider the attack to be a
real current practice, then the draft will become a fine
BCP in all senses of the term.

S.


> 
> Melinda
> 
> 
> 

From stephen.farrell@cs.tcd.ie  Thu Jan  2 05:18:02 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 375461AE59A for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ddMoHral-prj for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:18:00 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 1129A1AE85B for <ietf@ietf.org>; Thu,  2 Jan 2014 05:18:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B0C5EBE5D; Thu,  2 Jan 2014 13:17:52 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VVcHDsCxtqVu; Thu,  2 Jan 2014 13:17:51 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2689DBE58; Thu,  2 Jan 2014 13:17:51 +0000 (GMT)
Message-ID: <52C566F4.2040201@cs.tcd.ie>
Date: Thu, 02 Jan 2014 13:17:40 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>
In-Reply-To: <52C4DF7D.3010509@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 13:18:02 -0000

Melinda,

On 01/02/2014 03:39 AM, Melinda Shore wrote:
> On 1/1/14 6:11 PM, Ted Lemon wrote:
>> On Jan 1, 2014, at 6:07 PM, Melinda Shore <melinda.shore@gmail.com>
>> wrote:
>>> I'm sorry, but when we get to the point where we need to point to
>>> an RFC to stop progress on a document that has obvious
>>> vulnerabilities, our brains have fallen out.
>>
>> This is counterfactual.   We used to routinely handwave about
>> security.  
> 
> We still routinely handwave about security.  It's an afterthought
> in entirely too many cases.  Drafts are adopted by working groups
> while still having security considerations sections that consist
> in their entirety of "TBD."  3552's impacts have been, I think,
> on how documents are reviewed more than on how documents are
> developed.

Agreed.

> 
> One of the reasons I'm somewhat annoyed about the wave of
> gasbaggery and pontification that has followed truly disturbing
> revelations about the extent to which the US government has
> undermined privacy and compromised security technologies is
> that work which might have helped provide tools to mitigate
> some of the soft spots in IETF work has been backburnered in
> favor of no small amount of unfocused grandiosity that doesn't
> actually change much.

I think the above is gasbaggery and, to me at least, quite
annoying.

I should update [1] but its a list of what's being done that
was up to date in mid Nov.

   [1] https://down.dsg.cs.tcd.ie/misc/perpass.txt

Feel free to join in those discussions some more.

> At any rate this draft is not RFC3552.  3552 provides very specific
> guidelines for what needs to be considered in
> writing^H^H^H^H^H^H^H^Hreviewing security considerations.

When'd you last re-read 3552? Is has all sorts of MUSTs that
we routinely do not and should not force draft authors to
conform to, for example:

   Authors of internet standards MUST describe which denial of service
   attacks their protocol is susceptible to.  This description MUST
   include the reasons it was either unreasonable or out of scope to
   attempt to avoid these denial of service attacks.

Is that still reasonable? I think not, there are too many DoS
vectors in the world now. The non-normative parts of 3552 are
very good though, but I think many of the normative instructions
are outdated. That BCP would have been better with far fewer or
no references to 2119 IMO.

And so with this one - stating only the high level requirement
is the right thing to do for now.

Leaving the high-level requirement unstated would mean that a
lot of IETF work in the coming years would not address this
attack.

> It is tempting to just let this through last call in hopes that
> once it's done we can come back around to prioritizing work like
> fixing PKI but I'd be very sorry indeed to see this published as a
> BCP.

"Fixing" PKI is neither terribly relevant here nor being ignored.

For TEMPORA PKI seems mostly irrelevant. For QUANTUMINSERT et al
some of the active attacks do depend on problems with the Web PKI
but I'd guess mixed-content is much more important in terms of
successful attacks than are PKI abuses, for now at least.

On the latter point, there is a wpkops WG that could do with more
help. We have also started discussion about chartering a CT WG. And
the uta WG might make some recommendations about TLS that help
there too. And the httpbis WG have seriously debated TLS for
HTTP/2.0 (that debate's not over but is real). If you have other
ideas for "fixing" PKI then I'd be glad to hear about them and
to try help make 'em happen, as appropriate.

On the whole I think your criticism is, to use your words,
gasbaggery and annoying. And wrong.

S.

> 
> Melinda
> 
> 

From scott.brim@gmail.com  Thu Jan  2 05:26:55 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC011AE16A for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:26:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p19WGFjKF-w5 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:26:53 -0800 (PST)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3072E1AE120 for <ietf@ietf.org>; Thu,  2 Jan 2014 05:26:53 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id k1so14689278oag.6 for <ietf@ietf.org>; Thu, 02 Jan 2014 05:26:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dwRQGDKBekjSYUWYqrhFZA6zVbVkFhHO8DnbT5BKsLo=; b=XytVz2y7vPMUcxQtSks+ooUPg+/ht8+xp6nXaLxTIrBnk/56SsLIqTURnK9QtwYNbH kpYUHvCcYxvwSiGUux2VX1HTqzG6ArFUXjv1kQRoUlEz08d67bNRWxhH472E6lcWEp3v o6RWdqTgz8fnGsK+V8kR3DANfDraEmkmLpByD9zeOLbo01V/3BBv9V7b5dDoNxxrj7Sk RRIWV4FqKWEKNbaOhyuA0V1ifp+CebnkQtUrFVVgp7NazNWFdWLiXlcG62R5zd/NW5BY uQBfKhed+CaQ+cFamgqcKsiq8D3P6pBBSLMLDqEW0f+cmJmp/QS9ZT0gsNXaARklaymq JktA==
MIME-Version: 1.0
X-Received: by 10.60.233.9 with SMTP id ts9mr1015743oec.65.1388669206143; Thu, 02 Jan 2014 05:26:46 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 2 Jan 2014 05:26:46 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 2 Jan 2014 05:26:46 -0800 (PST)
In-Reply-To: <52C566F4.2040201@cs.tcd.ie>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C566F4.2040201@cs.tcd.ie>
Date: Thu, 2 Jan 2014 08:26:46 -0500
Message-ID: <CAPv4CP85sTyroRohy+4Tr6qeEKyVTffqUgRvWRuuWu5jTzws2g@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Scott Brim <scott.brim@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=001a11369dc2be290e04eefcbe46
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 13:26:55 -0000

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

On Jan 2, 2014 8:18 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
> And so with this one - stating only the high level requirement
> is the right thing to do for now

Would it be better to leave this one informational and not make it a BCP?
There's extremely little in it that is Practice.  The next level down is
where we would add more specific guidelines and BCPs.

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

<p dir=3D"ltr"><br>
On Jan 2, 2014 8:18 AM, &quot;Stephen Farrell&quot; &lt;<a href=3D"mailto:s=
tephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br>
&gt; And so with this one - stating only the high level requirement<br>
&gt; is the right thing to do for now</p>
<p dir=3D"ltr">Would it be better to leave this one informational and not m=
ake it a BCP? There&#39;s extremely little in it that is Practice.=A0 The n=
ext level down is where we would add more specific guidelines and BCPs. </p=
>


--001a11369dc2be290e04eefcbe46--

From stephen.farrell@cs.tcd.ie  Thu Jan  2 05:36:03 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A53E1AE5CB for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:36:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUwNmUiPFoQe for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:36:00 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 300701AE568 for <ietf@ietf.org>; Thu,  2 Jan 2014 05:36:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 65DBFBE5D; Thu,  2 Jan 2014 13:35:52 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id csr5Oqakmy92; Thu,  2 Jan 2014 13:35:51 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.41.52.13]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 0F472BE58; Thu,  2 Jan 2014 13:35:50 +0000 (GMT)
Message-ID: <52C56B2C.5040707@cs.tcd.ie>
Date: Thu, 02 Jan 2014 13:35:40 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com>	<A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net>	<002501cef266$b0b8a540$4001a8c0@gateway.2wire.net>	<52A23B16.4060306@gmail.com>	<CC5864F92767060505B97E0A@JcK-HP8200.jck.com>	<52A8D6C4.2050006@cs.tcd.ie>	<55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>	<BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>	<004001cf0744$fab41470$f01c3d50$@riw.us>	<52C49FB2.9090208@gmail.com>	<78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>	<52C4DF7D.3010509@gmail.com>	<52C566F4.2040201@cs.tcd.ie> <CAPv4CP85sTyroRohy+4Tr6qeEKyVTffqUgRvWRuuWu5jTzws2g@mail.gmail.com>
In-Reply-To: <CAPv4CP85sTyroRohy+4Tr6qeEKyVTffqUgRvWRuuWu5jTzws2g@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 13:36:03 -0000

On 01/02/2014 01:26 PM, Scott Brim wrote:
> On Jan 2, 2014 8:18 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>> And so with this one - stating only the high level requirement
>> is the right thing to do for now
> 
> Would it be better to leave this one informational and not make it a BCP?
> There's extremely little in it that is Practice.  The next level down is
> where we would add more specific guidelines and BCPs.

See the quote from 2026 in my response to Dave - what is wrong
with following that and making a statement of principle as a
BCP?

There should be no need for all BCPs to have lots and lots of
detail surely.

And FWIW, I do think it'll be easier to get WGs to properly
consider the attack/threats if this is a BCP.

I also think it'll be cleaner to update as a BCP, if and
when we wanted to add more detail, but that's a minor detail.

S.

From derhoermi@gmx.net  Thu Jan  2 05:36:05 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727391AE5DB for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:36:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMcuo2moi3pH for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 05:36:03 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id AB6CA1AE5BB for <ietf@ietf.org>; Thu,  2 Jan 2014 05:36:02 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.12.134]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0Mcyxq-1Vhb1n3wEE-00IHb1 for <ietf@ietf.org>; Thu, 02 Jan 2014 14:35:54 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Thu, 02 Jan 2014 14:35:57 +0100
Message-ID: <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie>
In-Reply-To: <52C5620E.6030105@cs.tcd.ie>
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-Provags-ID: V03:K0:XeosQIeI2fTxZWog5w05GCGxZz/w8dAOvKAeRhH/GMbpRhSTKWa LbZrxo5xT8obykeqd4cyzmmU63/hCKCvFqXB4eEpJ4Qe9X6tgAb73++j2It7vmnCo8JL2Gy 5ZUYApDpo9WUn04xJXEHiJ6BkSIc2O52P3xM6WNIcKVpPB/LgTqouXfr5TvPC3EQ7XUlpsT M3klrPgLYLY7EAnnF/pvQ==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 13:36:05 -0000

* Stephen Farrell wrote:
>The draft is not vague. Its high-level, which is quite
>different. If there are parts that are vague please point
>those out and we can try to fix them.

The part where it says the IETF will work to mitigate Google's pervasive
monitoring. Also the part where it says Google's pervasive monitoring is
an attack on Internet communications. And the part where it says there's
a consensus on both points. There is no mention of Google in the draft,
so read that as any perpetrator of mass surveillance attacks.
-- 
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 Ted.Lemon@nominum.com  Thu Jan  2 06:25:47 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6211ADF82 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 06:25:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sMuuGfvMO8u2 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 06:25:46 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 244FC1ADF70 for <ietf@ietf.org>; Thu,  2 Jan 2014 06:25:46 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUsV243NvHfhsnlCvZgkZ0UGZ3yFEV3pD@postini.com; Thu, 02 Jan 2014 06:25:39 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 33D121B805A for <ietf@ietf.org>; Thu,  2 Jan 2014 06:25:39 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0AE1819005C; Thu,  2 Jan 2014 06:25:39 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Jan 2014 06:25:39 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de>
Date: Thu, 2 Jan 2014 09:25:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie> <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 14:25:47 -0000

On Jan 2, 2014, at 8:35 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> The part where it says the IETF will work to mitigate Google's =
pervasive
> monitoring.

Are we talking about the same document?   I just googled it for the word =
"google" and got zero hits.


From Ted.Lemon@nominum.com  Thu Jan  2 06:29:54 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 487851AE5AA for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 06:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FoOIPZgf_y1N for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 06:29:52 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id C48AF1AE36B for <ietf@ietf.org>; Thu,  2 Jan 2014 06:29:52 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKUsV32io9kkV1yF5PZ0HQPOBLoqpUVhwd@postini.com; Thu, 02 Jan 2014 06:29:46 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id E56771B805A for <ietf@ietf.org>; Thu,  2 Jan 2014 06:29:45 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id D773B19005C; Thu,  2 Jan 2014 06:29:45 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Jan 2014 06:29:45 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com>
Date: Thu, 2 Jan 2014 09:29:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <30467A7F-93EB-4E87-8EA8-A20381DD699A@nominum.com>
References: <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie> <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de> <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 14:29:54 -0000

On Jan 2, 2014, at 9:25 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
> On Jan 2, 2014, at 8:35 AM, Bjoern Hoehrmann <derhoermi@gmx.net> =
wrote:
>> The part where it says the IETF will work to mitigate Google's =
pervasive
>> monitoring.
> Are we talking about the same document?   I just googled it for the =
word "google" and got zero hits.

Dialing in a little closer, consider this snippet from the actual text =
of the document:

   In the Internet,
   the term ["attack"] is used to refer to a behavior that subverts the
   intent of a communicator without the agreement of the parties to the
   communication.

So in the case of Google, the parties seem to have agreed to the =
communication, which suggests to me that this document is specifically =
not talking about Google.   Unless Google is in the habit of =
eavesdropping on communications to which it is not a party.=

From daedulus@btconnect.com  Thu Jan  2 07:39:58 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DF91AE6AC for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:39:58 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xrCG2xe0a5eX for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:39:55 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe004.messaging.microsoft.com [213.199.154.207]) by ietfa.amsl.com (Postfix) with ESMTP id 30E3F1AE616 for <ietf@ietf.org>; Thu,  2 Jan 2014 07:39:54 -0800 (PST)
Received: from mail37-am1-R.bigfish.com (10.3.201.237) by AM1EHSOBE023.bigfish.com (10.3.207.145) with Microsoft SMTP Server id 14.1.225.22; Thu, 2 Jan 2014 15:39:47 +0000
Received: from mail37-am1 (localhost [127.0.0.1])	by mail37-am1-R.bigfish.com (Postfix) with ESMTP id 5AB724015F; Thu,  2 Jan 2014 15:39:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I542I1432I1418Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah1fc6hzz1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h2327h2336h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(24454002)(13464003)(51704005)(479174003)(377454003)(51444003)(189002)(199002)(62236002)(59766001)(77982001)(53806001)(23756003)(62966002)(54316002)(44716002)(79102001)(56776001)(47446002)(74502001)(50226001)(76482001)(4396001)(31966008)(50986001)(74876001)(74706001)(47736001)(66066001)(47976001)(44736004)(74366001)(65816001)(80022001)(47776003)(61296002)(76796001)(89996001)(42186004)(49866001)(81542001)(63696002)(46102001)(50466002)(74662001)(80976001)(84392001)(87286001)(87266001)(76786001)(87976001)(85306002)(14496001)(19580405001)(77096001)(88136002)(81342001)(77156001)(51856001)(69226001)(83072002)(83322001)(19580395003)(85852003)(33646001)(90146001)(56816005)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB252; H:DB3PRD0411HT002.eurprd04.prod.outlook.com; CLIP:157.56.253.53; FPR:; RD:InfoNoRecords; MX:1; A:0; LANG:en; 
Received: from mail37-am1 (localhost.localdomain [127.0.0.1]) by mail37-am1 (MessageSwitch) id 1388677185249870_16300; Thu,  2 Jan 2014 15:39:45 +0000 (UTC)
Received: from AM1EHSMHS011.bigfish.com (unknown [10.3.201.227])	by mail37-am1.bigfish.com (Postfix) with ESMTP id 388DA100052;	Thu,  2 Jan 2014 15:39:45 +0000 (UTC)
Received: from AM2PRD0710HT005.eurprd07.prod.outlook.com (157.56.249.213) by AM1EHSMHS011.bigfish.com (10.3.207.111) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 2 Jan 2014 15:39:45 +0000
Received: from DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) by AM2PRD0710HT005.eurprd07.prod.outlook.com (10.255.165.40) with Microsoft SMTP Server (TLS) id 14.16.395.1; Thu, 2 Jan 2014 15:39:44 +0000
Received: from DB3PRD0411HT002.eurprd04.prod.outlook.com (157.56.253.53) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.842.7; Thu, 2 Jan 2014 15:39:43 +0000
Message-ID: <004001cf07d0$55cca260$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Melinda Shore <melinda.shore@gmail.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Thu, 2 Jan 2014 15:32:57 +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.53]
X-ClientProxiedBy: AM3PR07CA001.eurprd07.prod.outlook.com (10.242.16.41) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 0079056367
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 15:39:59 -0000

---- Original Message -----
From: "Melinda Shore" <melinda.shore@gmail.com>
To: "Ted Lemon" <ted.lemon@nominum.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Thursday, January 02, 2014 3:39 AM
> On 1/1/14 6:11 PM, Ted Lemon wrote:
> > On Jan 1, 2014, at 6:07 PM, Melinda Shore <melinda.shore@gmail.com>
> > wrote:
<snip>
>
> One of the reasons I'm somewhat annoyed about the wave of
> gasbaggery and pontification that has followed truly disturbing
> revelations about the extent to which the US government has
> undermined privacy and compromised security technologies is
> that work which might have helped provide tools to mitigate
> some of the soft spots in IETF work has been backburnered in
> favor of no small amount of unfocused grandiosity that doesn't
> actually change much.

Melinda

I note your explicit reference to the US government.  I note, too,
recent postings (e.g. on the TLS and UTA lists) which cast doubt on the
integrity of the (American) NSA which, in turn, reminds me that I see
the
USA as a country of small government (starting with the Founding
Fathers), something to be distrusted, subverted even, and I think that
that is colo(u)ring this discussion (whether or not the proponents of
this I-D are American citizens).

Elsewhere, I believe that governments are more trusted, so when the head
of a (non-American) national security agency says that the world is now
a more dangerous place, that successful terrorist attacks are more
likely because of recent revelations, then that consideration, of
personal security, outweighs my concern that someone is reading my
messages to, say, a secret lover.  I have been close to terrorist
attacks - doubtless some on this list have been directly affected by
them - and while I see them as probability low/impact high, I am more
concerned about that risk than that of the state seeing something I
would rather it did not.  And, as I said before, if there is any breach
of privacy that concerns me, and again it is one that I see echoed in
the national media, it is that of the assembling of personal profiles by
large, quasi-monopolistic websites, something which the aspirations
of this I-D would seem to make more likely.

Tom Petch

> At any rate this draft is not RFC3552.  3552 provides very specific
> guidelines for what needs to be considered in
> writing^H^H^H^H^H^H^H^Hreviewing security considerations.
>
> It is tempting to just let this through last call in hopes that
> once it's done we can come back around to prioritizing work like
> fixing PKI but I'd be very sorry indeed to see this published as a
> BCP.
>
> Melinda
>



From mcr@sandelman.ca  Thu Jan  2 07:46:58 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62231ADFDA for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:46:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdcOI5Aq8MWW for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:46:57 -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 602181ADF83 for <ietf@ietf.org>; Thu,  2 Jan 2014 07:46:57 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CBD4920051; Thu,  2 Jan 2014 12:01:49 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 9E8F464647; Thu,  2 Jan 2014 10:46:49 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8E56863B88; Thu,  2 Jan 2014 10:46:49 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: l.wood@surrey.ac.uk
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E51037CB@EXMB01CMS.surrey.ac.uk>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com>, <21962.1388638923@sandelman.ca> <290E20B455C66743BE178C5C84F1240847E51037CB@EXMB01CMS.surrey.ac.uk>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 02 Jan 2014 10:46:49 -0500
Message-ID: <22724.1388677609@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 15:46:59 -0000

--=-=-=


<l.wood@surrey.ac.uk> wrote:
    >> I don't think it's a problem that a draft gets adopted as a WG item
    >> that is incomplete in a variety of ways, including security
    >> considerations.
    >>
    >> Let's not continue the trend to having a WG design team prior to
    >> having a WG.

    > perpass is not a WG, and draft-farrell-perpass-attack is not an adopted
    > WG item.

I think that Melinda is making a general statement about WG processes, not
one related to perpass.  Perhaps I'm wrong here.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting for hire =-



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

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

iQCVAwUBUsWJ6YqHRg3pndX9AQKmaAP9EI+ggbcYhi7uhNKoKw8bW1PCLHwa5vJc
H5MLm0OpIF1nLVMSznv2+tzqoKbJca3SUV2pfCs+2HLmidWaoUrpxhOSW0WUujq9
LLnnN9n6toCkRgNJ0Blatn6zDKTPBWr3VMKV1MDrrHxNYCL/hPr1XgGekg/hJCXf
hsyEY28saFU=
=cLLi
-----END PGP SIGNATURE-----
--=-=-=--

From derhoermi@gmx.net  Thu Jan  2 07:48:10 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401641AE4C0 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fzIxvC-JYqVX for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:48:08 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id CB2C61ADF83 for <ietf@ietf.org>; Thu,  2 Jan 2014 07:48:07 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.12.134]) by mail.gmx.com (mrgmx103) with ESMTPA (Nemesis) id 0LzKQf-1VKrRp0NRB-014VSj for <ietf@ietf.org>; Thu, 02 Jan 2014 16:48:00 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Thu, 02 Jan 2014 16:48:02 +0100
Message-ID: <ctuac9deupgsldod98jipl671ofrqmhmr0@hive.bjoern.hoehrmann.de>
References: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie> <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de> <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com> <30467A7F-93EB-4E87-8EA8-A20381DD699A@nominum.com>
In-Reply-To: <30467A7F-93EB-4E87-8EA8-A20381DD699A@nominum.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-Provags-ID: V03:K0:zwMAO5zLm/+A70x5PnSmSYU5MhRhHv5WgWyewFcM5+gLuo8vvx1 p+ETDSGzGhq/35GinfTVM5+CrvwxsmRM+tpwEB2AjQkmobtEwUAUSoG2oTBzyJUzuqpHN20 Ioxjz/wm1tJn/L50jZOW6KwVR1Y+yKoBj1GbjQ/VidZ7ilOKgMAo+XWDu+H3FkKF6hKmWmT MZcfHCQ6cApntvbXOvrYA==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 15:48:10 -0000

* Ted Lemon wrote:
>Dialing in a little closer, consider this snippet from the actual text of the document:
>
>   In the Internet,
>   the term ["attack"] is used to refer to a behavior that subverts the
>   intent of a communicator without the agreement of the parties to the
>   communication.
>
>So in the case of Google, the parties seem to have agreed to the 
>communication, which suggests to me that this document is specifically 
>not talking about Google.   Unless Google is in the habit of 
>eavesdropping on communications to which it is not a party.

The draft specifically calls out "legal but privacy-unfriendly purposes
by commercial enterprises" "no matter how benevolent some might consider
them to be" causing "through correlation with other communication
events, [revelation of] information the communicator did not intend to
be revealed"; that is a description of "behavioral advertising".

If you put Google "+1 button" scripts on your web site, that does not at
all mean first time visitors have somehow consented to Google being a
party to their communication, before they had a chance to become aware
of that. Indeed, many German web sites disable such "buttons" by default
('Two clicks for more privacy') for this reason.

If Google Analytics is somehow not pervasive monitoring then I do not
see how I could personally be affected by pervasive monitoring? "NSA
'spied on porn habits to target" does not seem different from "Google
'spied on porn habits to target" if I ignore that Google is no formal
part of the U.S. military. Is pervasively spying on porn habits an
attack? Yes if it's done by tapping undersea cables, no if it is done
through CDN server logs? How do you tell which CDNs are party to your
communications?
-- 
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 Ted.Lemon@nominum.com  Thu Jan  2 07:55:52 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F401AE3ED for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:55:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qa0HBpSDGyVr for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 07:55:50 -0800 (PST)
Received: from exprod7og116.obsmtp.com (exprod7og116.obsmtp.com [64.18.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id AFA851ADF83 for <ietf@ietf.org>; Thu,  2 Jan 2014 07:55:50 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob116.postini.com ([64.18.6.12]) with SMTP ID DSNKUsWL/yf5Ll4yVa+DdyU1vrGHJnFfL13y@postini.com; Thu, 02 Jan 2014 07:55:44 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 954991B82D7 for <ietf@ietf.org>; Thu,  2 Jan 2014 07:55:43 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 700D219005C; Thu,  2 Jan 2014 07:55:43 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 2 Jan 2014 07:55:43 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <ctuac9deupgsldod98jipl671ofrqmhmr0@hive.bjoern.hoehrmann.de>
Date: Thu, 2 Jan 2014 10:55:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <D86246D6-B0DC-4070-9B71-C906A80C01B4@nominum.com>
References: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <004001cf0744$fab41470$f01c3d50$@riw.us> <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie> <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de> <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com> <30467A7F-93EB-4E87-8EA8-A20381DD699A@nominum.com> <ctuac9deupgsldod98jipl671ofrqmhmr0@hive.bjoern.hoehrmann.de>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 15:55:52 -0000

On Jan 2, 2014, at 10:48 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
> The draft specifically calls out "legal but privacy-unfriendly =
purposes
> by commercial enterprises" "no matter how benevolent some might =
consider
> them to be" causing "through correlation with other communication
> events, [revelation of] information the communicator did not intend to
> be revealed"; that is a description of "behavioral advertising".

It might be helpful to quote the text without strategic elisions!   It's =
true that something like the G+1 button can be used for pervasive =
monitoring, but that's a bit different than saying that this document is =
specifically targeting Google and Google's general business model.   The =
point is that if by happenstance certain applications like the G+1 or FB =
Like button become less valuable as a result of IETF being more =
proactive in preventing pervasive monitoring, that would be an =
acceptable outcome.

Do you disagree with that?


From kent@bbn.com  Thu Jan  2 08:03:24 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B6D01ADF83 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:03:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yMblFyPp15nL for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:03:20 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 070821ADF60 for <ietf@ietf.org>; Thu,  2 Jan 2014 08:03:19 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:55763 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Vykjo-00018E-8Q for ietf@ietf.org; Thu, 02 Jan 2014 11:03:12 -0500
Message-ID: <52C58DC0.4000501@bbn.com>
Date: Thu, 02 Jan 2014 11:03:12 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <CADnDZ8-WoyxXDTQ0QoQOOYxc5xzLgpHmhA7VkuN6OmRV-DhX8Q@mail.gmail.com>
In-Reply-To: <CADnDZ8-WoyxXDTQ0QoQOOYxc5xzLgpHmhA7VkuN6OmRV-DhX8Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------040207050206050103070209"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 16:03:24 -0000

This is a multi-part message in MIME format.
--------------040207050206050103070209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I commented earlier to Stephen (off list) that BCP status seemed a bit 
out of place for
a position statement, so I'm heartened to see others have a similar 
concern. I concur
with the suggestion that this be (IAB stream) Informational.

If published as Informational, I don't worry that this doc does not lay 
out details
for what WGs are expected to do. At the behest of two IAB members, I am 
working on a
doc that examines keying options for major IETF security protocols, and 
discusses what
changes could be made to facilitate anonymous encryption as a fallback 
from authenticated encryption. This is just one aspect of an overall 
response to PM, but it will yield concrete proposals. Other folks are 
working on an updated threat model doc.

I have also noted that the document refers to PM as "indistinguishable" 
from an attack,
which IMHO seems too polite. PM is effected via passive and active 
wiretapping attacks, and
thus it IS an attack. Tim Bray's message characterized the current draft 
as saying "The perpass-attack draft says that pervasive monitoring has 
the characteristics of an attack, ..." This suggests that a reader 
doesn't interpret the text as saying that PM _is_ an attack.
We should avoid words that may lead a reader to believe that PM is 
/equivalent/ to an
attack. Its easy to make a case that PM is an attack. I provided (off 
list) feedback a
few weeks ago suggesting a different way to present the issues here, and 
have updated that text:

For many years the IETF security community has used an attack/threat 
model [RFC3552] that envisions an adversary who can engage in passive 
and active wiretapping at any point along a communication path. We 
commonly attribute the ability to engage in MITM attacks to such an 
adversary. Thus we have long believed that plaintext communications are 
vulnerable to passive wiretapping along a communication path if the 
content is not protected via encryption. We also have noted that, for 
staged delivery applications, e.g., mail, content is vulnerable to 
disclosure and modification in storage, especially en route.In response 
to this model we have developed a set of security protocols, (e.g., 
IPsec, TLS, DTLS, S/MIME, SSH, etc.) that can be used to protect 
transmitted content against passive wiretapping, based on use of 
encryption. These protocols also usually incorporate data integrity and 
authentication mechanisms, and, where appropriate, anti-replay 
mechanisms, to address MITM attacks. Thus we have offered users and 
system designers a set of tools that address the adversarial 
capabilities based on our model.

When pervasive monitoring is effected via passive wiretapping, or a mix 
of active and passive wiretapping (e.g., using packet injection attacks) 
it is not a new class of attack. It is precisely what we have long 
considered when designing security protocols. Thus I believe this 
document should include comments of the sort noted above, to help 
establish a context for this declaration about "pervasive monitoring".

Having established this context, the next task is to explain why 
pervasive monitoring is significantly different from our long-standing 
model. The extent of such monitoring seems much bigger in scope than 
folks may have imagined, given that intelligence services of numerous 
countries have been identified as carrying on such monitoring. However,
RFC 3552 states:

    By contrast, we assume that the attacker has nearly complete control
    of the communications channel over which the end-systems communicate.
    This means that the attacker can read any PDU (Protocol Data Unit) on
    the network and undetectably remove, change, or inject forged packets
    onto the wire.  This includes being able to generate packets that
    appear to be from a trusted machine.  Thus, even if the end-system
    with which you wish to communicate is itself secure, the Internet
    environment provides no assurance that packets which claim to be from
    that system in fact are.

This statement is pretty clear. I think the PM document needs to 
explain, in a technical context, why pervasive monitoring is 
qualitatively different, and thus merits this declaration by the IETF. 
We ought not lead readers to believe that we have not considered passive 
and active wiretapping as likely attacks in the past.

Some of the reported forms of pervasive monitoring may have involved the 
cooperation of or subversion of an ISP or a telecom provider. This is 
not a qualitatively different form of attack from the generic passive 
wiretapping that our security model has always assumed.

Some of the reported forms of pervasive monitoring have involved the 
cooperation of or subversion of application service providers. This does 
represent a major deviation from
the 3552 model:

    The Internet environment has a fairly well understood threat model.
*In general, we assume that the end-systems engaging in a protocol**
**   exchange have not themselves been compromised.*

So we should acknowledge this as one asp[ect of PM that is different 
from our threat model. However, if attacks take place at a point after 
which IETF protocols terminate, then it seems to be largely outside of 
our purview as a protocol-focused standards organization. For example, 
if I access e-mail via a _web_ _interface_ at an MSP, IETF security 
standards largely do not seem to apply to vulnerabilities associated 
with storage of the mail at the MSP; my mail can't be protected e-t-e 
because I'm not using S/MIME to read the mail. I can use TLS to protect 
the HTTPS session via which I access messages, and we can recommend that 
TLS be used with SMTP to deliver the mail to the MSP, but that seems to 
be the limit of our security protocols.






--------------040207050206050103070209
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">
    I commented earlier to Stephen (off list) that BCP status seemed a
    bit out of place for<br>
    a position statement, so I'm heartened to see others have a similar
    concern. I concur<br>
    with the suggestion that this be (IAB stream) Informational.<br>
    <br>
    If published as Informational, I don't worry that this doc does not
    lay out details<br>
    for what WGs are expected to do. At the behest of two IAB members, I
    am working on a <br>
    doc that examines keying options for major IETF security protocols,
    and discusses what <br>
    changes could be made to facilitate anonymous encryption as a
    fallback from authenticated encryption. This is just one aspect of
    an overall response to PM, but it will yield concrete proposals.
    Other folks are working on an updated threat model doc.<br>
    <br>
    I have also noted that the document refers to PM as
    "indistinguishable" from an attack,<br>
    which IMHO seems too polite. PM is effected via passive and active
    wiretapping attacks, and<br>
    thus it IS an attack. Tim Bray's message characterized the current
    draft as saying "The perpass-attack draft says that pervasive
    monitoring has the characteristics of an attack, ..." This suggests
    that a reader doesn't interpret the text as saying that PM <u>is</u>
    an attack.<br>
    We should avoid words that may lead a reader to believe that PM is <i>equivalent</i>
    to an<br>
    attack. Its easy to make a case that PM is an attack. I provided
    (off list) feedback a<br>
    few weeks ago suggesting a different way to present the issues here,
    and have updated that text:<br>
    <p class="MsoNormal"
      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">For many years the
        IETF security community has used an attack/threat model
        [RFC3552] that envisions an adversary who can engage in passive
        and active wiretapping at any point along a communication path.
        We commonly attribute the ability to engage in MITM attacks to
        such an adversary. Thus we have long believed that plaintext
        communications are vulnerable to passive wiretapping along a
        communication path if the content is not protected via
        encryption. We also have noted that, for staged delivery
        applications, e.g., mail, content is vulnerable to disclosure
        and modification in storage, especially en route.</span><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US"> In response to
        this model we have developed a set of security protocols, (e.g.,
        IPsec, TLS, DTLS, S/MIME, SSH, etc.) that can be used to protect
        transmitted content against passive wiretapping, based on use of
        encryption. These protocols also usually incorporate data
        integrity and authentication mechanisms, and, where appropriate,
        anti-replay mechanisms, to address MITM attacks. Thus we have
        offered users and system designers a set of tools that address
        the adversarial capabilities based on our model. <br>
      </span></p>
    <p class="MsoNormal"
      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">When pervasive
        monitoring is effected via passive wiretapping, or a mix of
        active and passive wiretapping (e.g., using packet injection
        attacks) it is not a new class of attack. It is precisely what
        we have long considered when designing security protocols. Thus
        I believe this document should include comments of the sort
        noted above, to help establish a context for this declaration
        about &#8220;pervasive monitoring&#8221;. <br>
      </span></p>
    <p class="MsoNormal"
      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">Having established
        this context, the next task is to explain why pervasive
        monitoring is significantly different from our long-standing
        model. The extent of such monitoring seems much bigger in scope
        than folks may have imagined, given that intelligence services
        of numerous countries have been identified as carrying on such
        monitoring. However,<br>
        RFC 3552 states:<br>
      </span></p>
    <p class="MsoNormal"
      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">&nbsp;&nbsp; By contrast, we
        assume that the attacker has nearly complete control<br>
        &nbsp;&nbsp; of the communications channel over which the end-systems
        communicate.<br>
        &nbsp;&nbsp; This means that the attacker can read any PDU (Protocol Data
        Unit) on<br>
        &nbsp;&nbsp; the network and undetectably remove, change, or inject forged
        packets<br>
        &nbsp;&nbsp; onto the wire.&nbsp; This includes being able to generate packets
        that<br>
        &nbsp;&nbsp; appear to be from a trusted machine.&nbsp; Thus, even if the
        end-system<br>
        &nbsp;&nbsp; with which you wish to communicate is itself secure, the
        Internet<br>
        &nbsp;&nbsp; environment provides no assurance that packets which claim to
        be from<br>
        &nbsp;&nbsp; that system in fact are.<br>
      </span></p>
    <p class="MsoNormal"
      style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">This statement is
        pretty clear. I think the PM document needs to explain, in a
        technical context, why pervasive monitoring is qualitatively
        different, and thus merits this declaration by the IETF. We
        ought not lead readers to believe that we have not considered
        passive and active wiretapping as likely attacks in the past.<br>
      </span><span
        style="font-size:10.0pt;font-family:Times;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US"><o:p></o:p></span></p>
    <span
      style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




      New Roman&quot;; mso-fareast-language:EN-US">Some of the reported
      forms of pervasive monitoring may have involved the cooperation of
      or subversion of an ISP or a telecom provider. This is not a
      qualitatively different form of attack from the generic passive
      wiretapping that our security model has always assumed. <br>
      <br>
    </span><span
      style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




      New Roman&quot;; mso-fareast-language:EN-US"><span
        style="font-size:10.0pt;font-family:Courier;mso-bidi-font-family:&quot;Times




        New Roman&quot;; mso-fareast-language:EN-US">Some of the
        reported forms of pervasive monitoring have involved the
        cooperation of or subversion of application service providers.
        This does represent a major deviation from<br>
        the 3552 model:<br>
        <br>
        &nbsp;&nbsp; The Internet environment has a fairly well understood threat
        model.<br>
        &nbsp;&nbsp; <b>In general, we assume that the end-systems engaging in a
          protocol</b><b><br>
        </b><b>&nbsp;&nbsp; exchange have not themselves been compromised.</b><br>
        <br>
        So we should acknowledge this as one asp[ect of PM that is
        different from our threat model. However, if attacks take place
        at a point after which IETF protocols terminate, then it seems
        to be largely outside of our purview as a protocol-focused
        standards organization. For example, if I access e-mail via a <u>web</u>
        <u>interface</u> at an MSP, IETF security standards largely do
        not seem to apply to vulnerabilities associated with storage of
        the mail at the MSP; my mail can&#8217;t be protected e-t-e because
        I&#8217;m not using S/MIME to read the mail. I can use TLS to protect
        the HTTPS session via which I access messages, and we can
        recommend that TLS be used with SMTP to deliver the mail to the
        MSP, but that seems to be the limit of our security protocols.<br>
        <br>
        <br>
      </span><br>
      <br>
    </span><br>
  </body>
</html>

--------------040207050206050103070209--

From stbryant@cisco.com  Thu Jan  2 08:10:41 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 887DF1AE5ED for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:10:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jhFlfKURCkfi for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:10:40 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id C78BE1AE097 for <ietf@ietf.org>; Thu,  2 Jan 2014 08:10:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1468; q=dns/txt; s=iport; t=1388679033; x=1389888633; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=v32kMwlpN867U+p1MFxEJw6Eqcqg0mHuyydm/fFZbKc=; b=m0y3MFMV8yS3s1lZuiyewhjrUSYyYPf61yZz3HlSr63Q5R1opiunw5zA O56RDz/NhrErvNFo4YnSA9IVJqmSD4zxi+kTxcpLNlZQcSt8Wl8OWYDV7 Edrj3WWnIhMFUXh0tY1ldUYxSNksgOcfM/lwBAa8wAJiDJY0z0sv8WA8B w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFABKPxVKQ/khM/2dsb2JhbABYgwu2dYMHgQsWdIIlAQEBBDhRCxgJGgsPAkYGAQwIAQGIAMMTF48khDYElDODZJIUgW+BPg
X-IronPort-AV: E=Sophos;i="4.95,591,1384300800";  d="scan'208";a="3106107"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 02 Jan 2014 16:10:32 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s02GAVNI009873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jan 2014 16:10:32 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s02GATgQ025618; Thu, 2 Jan 2014 16:10:30 GMT
Message-ID: <52C58F75.10106@cisco.com>
Date: Thu, 02 Jan 2014 16:10:29 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
In-Reply-To: <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 16:10:41 -0000

On 31/12/2013 20:48, John C Klensin wrote:
> For example, effective surveillance of traffic content by monitoring 
> of Internet links would become considerably more difficult if we 
> (pervasively) went back to routing at the packet (or datagram) level 
> and optimized our routing algorithms to prefer diverse paths within a 
> stream or flow. At least as I understand it, that would largely 
> eliminate the use of MPLS and would slow things down overall unless 
> ISPs started engineering their networks for more path diversity 
> between any two endpoints (presumably increasing costs for the amount 
> of traffic handled). But it would make interception of a single flow 
> for surveillance purposes a lot more unpleasant and costly for the 
> monitoring body without requiring encryption.

Actually John, I think some MPLS implementations did this across equal 
cost paths, but TCP performance went through the floor and so a lot of 
effort now goes into the maintenance of flow order. Some protocols are 
much more sensitive than TCP in this regard and can never be subjected 
to misordering. However if the transport protocols could cope with out 
of order delivery, we could get MPLS to spread flows across pretty much 
every available path. As well as having anti-surveillance properties, 
such an approach would have the anti-congestion properties of spread 
spectrum and so could be quite an interesting area of research.

Stewart

From dhc@dcrocker.net  Thu Jan  2 08:15:02 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 861E71AE6E9 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:15:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.2
X-Spam-Level: 
X-Spam-Status: No, score=-6.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okSy6rYG__BW for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:14:59 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA911AE6BE for <ietf@ietf.org>; Thu,  2 Jan 2014 08:14:59 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s02GEnfc014310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 2 Jan 2014 08:14:52 -0800
Message-ID: <52C5901E.2000904@dcrocker.net>
Date: Thu, 02 Jan 2014 08:13:18 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
In-Reply-To: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 02 Jan 2014 08:14:52 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 16:15:02 -0000

On 1/1/2014 2:08 PM, Ted Lemon wrote:
> This argument boils down to "ADs can abuse process, so we ought not
> to ever publish a document that might provide process for them to
> abuse."

A normative document that requires action, but does not characterize the 
action, inherently encourages idiosyncratic interpretation.  That's an 
invitation -- possibly even a demand -- for ADs to develop their 
personal preferences rather than to reflect a shared community sense of 
what is needed.


> It will be used by working group chairs and document authors to
> understand the IETF's expectations with respect to whether their work
> needs to address the problem of pervasive surveillance on the
> internet.

The problem here is your certitude about how it will be used.

The one thing that is certain about the document is that it does not 
specify that activity for those people.

And at this stage I don't think it should, because we don't know enough.


> I expect that ADs will also have this in mind when
> reviewing documents, and may ask questions about documents if the
> documents appear not to have addressed the problem, and don't say
> why.

A reasonable expectation.  But since we have no community understanding 
of what the specific questions should be and even less community 
understanding of what the answers will be, making the current draft 
normative essentially requires a deadly embrace in the standards 
process, as each occurrence produces an ad hoc negotiation over an 
extended period of time.  (This is exactly what happened for years with 
Security Considerations.)

All of this gets exacerbated by the likelihood of personal whim amongst 
ADs.  (It's not a question of intent; everyone intends well.  It's the 
lack of community guidance, at this stage.)



> But the real goal of a document like this is to get working groups to
> think about this, not to create more tail-end process.

Then don't make it normative, yet.


>  ADs can
> _already_ ask these questions, and can _already_ send documents back
> to the working group if the answers aren't satisfactory.   What this
> document does is to clearly state an IETF consensus (assuming one is
> reached), which might result in more consistency both across the
> process of developing a specific document, and also across time as
> the makeup of working groups and the IESG changes.
>
> On Jan 1, 2014, at 10:45 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> There is a substantial community in the Internet wishing to have
>> its data and activities protected against pervasive monitoring.
>> The IETF needs to design specifications and practices (existing and
>> new) with the means to ensure such protection.
>
> It sounds like you are saying that the IETF does not lead, but rather
> follows the market.

Since I don't see anything in that statement of mine about the market, I 
can't guess what took you to that interpretation.


> On Jan 1, 2014, at 3:29 PM, Melinda Shore <melinda.shore@gmail.com>
> wrote:
>> I really don't think so, at least not in its current form.  I think
>> it's fine to publish it as-is as an opinion piece but it seems to
>> me that if it's going to be published as a "BCP" it really needs to
>> be clearer about specifically what is going to change in the
>> current document development and publication process.
>
> This document is advice, not code.

"Advice" is not normative.


>   It is indeed "best practice" in
> the sense that, if the IETF gains consensus on it, it is saying that
> we should make a habit of thinking about pervasive monitoring when
> writing our documents.

Ted, a recurring problem in many folks' posting on this topic is that 
they seem to be applying invoking themselves as the model of what will 
happen with the document, rather than considering the community's 
history, including how different ADs have operated over the years.

And then there is the well-demonstrated variability already showing up 
in the current discussion.  It makes clear that we don't yet have shared 
community understanding of what we should be doing in terms of technical 
specifics.

The document really has nothing to do with best current practices 
because it is not about practices at all.  It is about concerns.  We 
don't make statements about concerns normative.  Especially when we do 
not have any history of working on a topic.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stbryant@cisco.com  Thu Jan  2 08:23:36 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10BB71AE6FC for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:23:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VLljhdGBpogc for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:23:34 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 095B01AE421 for <ietf@ietf.org>; Thu,  2 Jan 2014 08:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=633; q=dns/txt; s=iport; t=1388679807; x=1389889407; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=IN4Mrw5ZFesIM+bPEKKVXp8ursnHC9Ghs5u89aZP3io=; b=hfVYUJ6RHg424G7mDmoWOFz30hs5D/h28cHtIiSad+kjzvwgt0TuTiJH jIkIlQHKG85QE8x8sfkACWhBFWorqEABbkpiFDjuZQfSW5+6XGIAXIVOG 9FfmNkV3bpJKOoRiJUHy8yw4wY0UK+ky38NWkoQgBTf8ZNUE8TjQm4x23 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAFKSxVKQ/khL/2dsb2JhbABYgwu2dYMHgQsWdIIlAQEBBDhAARALGAkWBAsJAwIBAgFFBgEMAQcBAYgAww8Xjx0HhDYBA5gXkhSBb4E+
X-IronPort-AV: E=Sophos;i="4.95,591,1384300800";  d="scan'208";a="2437064"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 02 Jan 2014 16:23:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s02GNA1Q000710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jan 2014 16:23:11 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s02GN8mL026177; Thu, 2 Jan 2014 16:23:08 GMT
Message-ID: <52C5926C.1060403@cisco.com>
Date: Thu, 02 Jan 2014 16:23:08 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
In-Reply-To: <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 16:23:36 -0000

On 01/01/2014 22:08, Ted Lemon wrote:
> This argument boils down to "ADs can abuse process, so we ought not to 
> ever publish a document that might provide process for them to abuse.
Ted, I believe the point is that the AD concerned would not be abusing 
the process, they would simply be making a different judgement call, or 
a stricter interpretation (for what ever reason) of the in place PM 
requirements than the authors and preceding reviewers of the text.

The  -03 text is a significant improvement, but I still fear the impact 
of single issue technical politics on the output of our document stream.

Stewart

From derhoermi@gmx.net  Thu Jan  2 08:24:42 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 794C51AE712 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hg4UHqJbdCcj for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 08:24:40 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB3C1AE421 for <ietf@ietf.org>; Thu,  2 Jan 2014 08:24:40 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.12.134]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0LinyL-1VQGGI3XsD-00cuW9 for <ietf@ietf.org>; Thu, 02 Jan 2014 17:24:32 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Thu, 02 Jan 2014 17:24:34 +0100
Message-ID: <f63bc9dp85kjkee10p0gd3r6gmc52sv6i5@hive.bjoern.hoehrmann.de>
References: <52C49FB2.9090208@gmail.com> <78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com> <52C4DF7D.3010509@gmail.com> <52C4E5DA.4020305@dcrocker.net> <52C4EC4A.5050500@gmail.com> <52C5620E.6030105@cs.tcd.ie> <rlpac9l6tlsi4hhfi1tqabhjd6is18mpc5@hive.bjoern.hoehrmann.de> <0174D726-7FDD-464C-8A8D-C059FC841F92@nominum.com> <30467A7F-93EB-4E87-8EA8-A20381DD699A@nominum.com> <ctuac9deupgsldod98jipl671ofrqmhmr0@hive.bjoern.hoehrmann.de> <D86246D6-B0DC-4070-9B71-C906A80C01B4@nominum.com>
In-Reply-To: <D86246D6-B0DC-4070-9B71-C906A80C01B4@nominum.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-Provags-ID: V03:K0:ryGHByglGFDv4ITC7cFntyWqeDjehhedcMMrVqjy17FUewtFUfl /3lyDLe+jpBQ0XZYpOOza65ENwRlBNqy2ML6GKUo7TFAPPaFgv5iWeLzufzarYCfMCxX5Y2 zoUCacpobcuNC8RGDuXQ6l279xAYQ50UmEzragzXo0d4ziC78q9L3jBcOrnCl5UqgKa4Zk3 BaQj1MVE+B0C74IFP+ykA==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 16:24:42 -0000

* Ted Lemon wrote:
>On Jan 2, 2014, at 10:48 AM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:
>> The draft specifically calls out "legal but privacy-unfriendly purposes
>> by commercial enterprises" "no matter how benevolent some might consider
>> them to be" causing "through correlation with other communication
>> events, [revelation of] information the communicator did not intend to
>> be revealed"; that is a description of "behavioral advertising".
>
>It might be helpful to quote the text without strategic elisions!

You mean http://www.ietf.org/mail-archive/web/ietf/current/msg85172.html
should have quoted "There is no mention of Google in the draft, so read
that as any perpetrator of mass surveillance attacks"?

>It's true that something like the G+1 button can be used for pervasive 
>monitoring, but that's a bit different than saying that this document is 
>specifically targeting Google and Google's general business model.   The 
>point is that if by happenstance certain applications like the G+1 or FB 
>Like button become less valuable as a result of IETF being more 
>proactive in preventing pervasive monitoring, that would be an 
>acceptable outcome.
>
>Do you disagree with that?

Stephen Farrell asked which parts of the document are "vague". The point
is that the document is vague in explaining what "The IETF will work to
Mitigate" exactly. I think your question is entirely besides the point.
-- 
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 rstruik.ext@gmail.com  Tue Dec 31 11:02:22 2013
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3EB1AE2D5 for <ietf@ietfa.amsl.com>; Tue, 31 Dec 2013 11:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3
X-Spam-Level: ***
X-Spam-Status: No, score=3 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MANGLED_LIST=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAoOTT0eaLBt for <ietf@ietfa.amsl.com>; Tue, 31 Dec 2013 11:02:20 -0800 (PST)
Received: from mail-ea0-x236.google.com (mail-ea0-x236.google.com [IPv6:2a00:1450:4013:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id C190E1AE2EA for <ietf@ietf.org>; Tue, 31 Dec 2013 11:02:19 -0800 (PST)
Received: by mail-ea0-f182.google.com with SMTP id a15so5711645eae.27 for <ietf@ietf.org>; Tue, 31 Dec 2013 11:02:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=CrpdDW6uXPFAQB5q+2iVmpCDsHTVxWZVCMAGw7AQmsM=; b=BYQB1jTwojMTu2qwdDfWG22wOwaNrTayN66wjoOdNrfC7YDniXwEd0lhgoMj9mJEwt IpPmrI349U/ni2L318nCUYUOO0Da8ZxNa+TM+evx+dD2dvsn8iMyt6fxEXHBtXe+iv9e rTmZREJdTv9Jl4aZSxpIqLk04VRoStG2y9o04XVnJY7ZwPLaalmb13+Jhizu0lHlzCLs XaLNOTGgxYOytdZhj2DWFay2mqMA2LtNaw79e3E6UXSzNq9iqXHm2NICx3OsKWcMrm0c RlQYpLGxx2nNBS4fUl/duOrrS7GHwi2+TH1a9sO1pCrCZhf/et56J8AuV/m9OyDi2JWu ZRhw==
X-Received: by 10.14.224.197 with SMTP id x45mr6116614eep.103.1388516533080; Tue, 31 Dec 2013 11:02:13 -0800 (PST)
Received: from [192.168.1.6] (61-133-ftth.onsbrabantnet.nl. [88.159.133.61]) by mx.google.com with ESMTPSA id 1sm120601371eeg.4.2013.12.31.11.02.12 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Dec 2013 11:02:12 -0800 (PST)
Message-ID: <52C314B3.6090402@gmail.com>
Date: Tue, 31 Dec 2013 14:02:11 -0500
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com>
In-Reply-To: <20131203174852.21387.26099.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 02 Jan 2014 09:25:57 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Dec 2013 19:02:22 -0000

Dear colleagues:

While I do agree with some of the underlying sentiments of the draft, I 
am not that happy with the somewhat sloppy exposition of the draft, in 
particular to what problem one really wishes to address (see #1, #2 
below). Moreover, I feel that the implicit suggestion of the draft that 
one should take an almost binary approach to addressing passive attacks 
may be detrimental at achieving a solid security architectural design 
(it should be a proper balancing, rather than 0-1 thinking w.r.t. one of 
many security architectural considerations).

In my mind, the draft needs to be more carefully written, so as to make 
intent and grey scales of proposed design metrics clearer. More details 
below.

Some technical comments:

1) In Section 1, 3rd para, the term "attack" (in the context of 
pervasive monitoring) is too broadly defined: pervasive monitoring is 
(an extreme form of) monitoring and, thereby, an attack form that has 
been dubbed (decades ago) in the cryptographic literature as an attack 
by a *passive* adversary. (The fact that this may happen on a massive 
scale does not change its nature.) In the draft, though, one seems to 
lump this together with other attack forms, where a passive adversary 
may exploit insights gathered from passive attacks to subsequently 
facilitate an active attack (witness the use of "to enforce the 
opponent's will on the attacked party" in 3rd para, 3rd line or "that 
subverts the intent of a communicator without the agreement of the 
parties to the communication" in 3rd para, 6th line). The latter is an 
*active* attack, which is not part of pervasive monitoring itself (but 
only may take advantage of this). With passive attacks, in most cases 
(e.g., when using wireless communications) the presence or absence of an 
passive adversary cannot be distinguished. I would strongly suggest 
using proper notions and avoiding confusing and ill-defined terms (for 
definitions, see, e.g., Definition 12.15 of the Handbook of Applied 
Cryptography (CRC Press, 1995)). Shouldn't one simply change the title 
of Section 1 to the (somewhat obvious) statement "Pervasive monitoring 
is Indistinguishable from a Passive Attack" or "Pervasive Monitoring 
Cannot Be Distinguished From Non-Monitoring, So One Should Prepare For 
the Worst"?

2) In Section 1, 4th para, if the intent of the draft is to also raise 
awareness of active (pervasive) attacks, it should say so clearly and 
not suggest, as it seems to do right now, that this is due to "pervasive 
monitoring" (since, as already said, this is a misnomer). Here, again, 
though, this is nothing new by itself: security services need to be in 
place where the interests of communicating parties, including the 
communicating networks used by these parties (and lurking adversaries 
therein) are not aligned. I would suggest emphasizing, far more than 
currently done, the role pervasive monitoring could play in paving the 
way towards providing useful insight to make a subsequent (or 
interactive) active attack more successful, since that seems to be one 
of the underlying currents of the draft.

3) In Section 1, 1st para, it is stated that " [...] that this was an 
attack that should be mitigated where possible via the design of 
protocols that make pervasive monitoring significantly more expensive or 
infeasible". While I wholeheartedly agree that protocol design should 
include privacy-relevant objectives (such as hiding header info and 
meta-data), to me it seems this should always have been in the security 
services objective list with security and communication protocol design 
and it is somewhat surprising to see that this apparently is something 
new (or, do I read this in the wrong way?). Isn't the main change 
between the pre-Snowden and post-Snowden era that one is now aware that 
would should attach more weight to security objectives one may very well 
have unrightfully ignored in the past??? I am really concerned that this 
becomes now a single quest at the detriment of other security objectives 
one may wish to cater to. After all, with security and communication 
protocol design, one should balance different objectives according to 
deployment scenario at hand and there are many, many considerations that 
could play a role. To this point, I already expressed concern in an 
email of September 6th (see
http://www.ietf.org/mail-archive/web/perpass/current/msg00099.html) 
that, e.g., trying to avoid traffic analysis by making all frames the 
same size would be disastrous for applications in a highly constrained 
setting ("internet of things", "smart objects", and the-like); I also 
epressed some other concerns with respect to binary thinking here (see 
the link). I would therefore suggest to express the desire of IETF-88 
somewhat more intelligently and stipulate, e.g., that protocol should 
properly consider security objectives and weigh these and allow security 
policy settings to be picked so as to, indeed, enable more privacy-aware 
deployments. This is mostly a security policy issue, though, and should 
less so be a fixed setting of a security protocol itself. One could dub 
this "security policy agility" vs. "crypto agility" if one wishes.... 
(Note: TLS is an example of a somewhat unfortunate design here, where 
one has no security policy agility to hide lots of parms in the protocol 
flows at all). The main point of post-Snowded would then be that the 
"security policy agility" should include the policy to enable privacy 
protection to one's heart content.

4) Section 2, 2nd and 3rd para, seems to be a somewhat hidden admission 
that, perhaps, IETF itself may in the past not have done as good a job 
as it could have in considering and weighing all security objectives. 
After all, notions of passive and active attacks have been around for 
decades, but apparently some of this has been not taken too seriously 
for a while, or would have been considered "too expensive" to 
implementers or vested interests? It can hardly be considered news that, 
e.g., if one does not use adequately secured packets, then visible parts 
may be eavesdropped upon, etc. Right now, it reads as if one is 
indignified even in case one sends entirely unsecured packets and that 
this, surprise, surprise, may be vulnerable to attack. To some network 
people, it may be considered news if protocol messages do not behave as 
specified. To security people, this should be second nature: after all, 
all networks and network components should be considered as gigantic 
security engines, without constraint on actors on the communication channel.

5) Section 2, 5th para, seems to be an admission that protocol design 
should intelligently weigh design objectives (e.g., so as not to rule 
out monitoring for network monitoring purposes). So, if this means one 
wishes to cater for "security policy agility" as I alluded to above, so 
much the better.

Best regards, Rene

On 12/3/2013 12:48 PM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Pervasive Monitoring is an Attack'
>    <draft-farrell-perpass-attack-02.txt> as Best Current Practice
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2013-12-31. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     The IETF has consensus that pervasive monitoring is a technical
>     attack that should be mitigated in the design of IETF protocols,
>     where possible.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>


-- 
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363


From elear@cisco.com  Wed Jan  1 03:41:07 2014
Return-Path: <elear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D797F1AE246 for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 03:41:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BRTgvp0v_Zax for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 03:41:06 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 2496E1AE1D1 for <ietf@ietf.org>; Wed,  1 Jan 2014 03:41:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2979; q=dns/txt; s=iport; t=1388576459; x=1389786059; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=y6HvVksM3h/mub8MQQ9Ny9p7vpJxFXKE0/11IXW/Avk=; b=jZImw3H2wmYtsCV5C9LvyN2FE6Oz02hXcXwoXJzPUM93gCfROpESoFyw qBkum6nKF28zQSdQGRuesBJA3DUQl9H5nM95LL2WfT5bjqM24htSW6iPH uwYWAw+r3Rm9mssS2nrdRYq/eTtyBxZkiD7uiIv1Tk+GaSwbHcspTt0cu A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiwFAIb+w1KtJXG9/2dsb2JhbABYDoJ9OE+5I4EVFnSCJQEBAQMBOj8FCwIBCBEBAwEBAR4FCyERFwYIAgQOBRmHVwMJCAi/CQ2FKheNCoFgMweDI4ETAQOUM4F4gWyBMIsqA4U3gW9/Pw
X-IronPort-AV: E=Sophos;i="4.95,585,1384300800";  d="scan'208";a="9948287"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-3.cisco.com with ESMTP; 01 Jan 2014 11:40:59 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s01Bexvp003887 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 1 Jan 2014 11:40:59 GMT
Received: from xmb-rcd-x11.cisco.com ([169.254.1.68]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0123.003; Wed, 1 Jan 2014 05:40:58 -0600
From: "Eliot Lear (elear)" <elear@cisco.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPBmm9pbICcHPufUqxa+8Y/HlcnppvZyCAgABYBACAAAhiAP//+FNj
Date: Wed, 1 Jan 2014 11:40:57 +0000
Message-ID: <94CB7C32-46E2-47D8-BD38-9BAC4D545A85@cisco.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net>, <52C3A9D2.2090509@gmail.com>, <290E20B455C66743BE178C5C84F1240847E51037C7@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E51037C7@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 02 Jan 2014 09:26:42 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Jan 2014 11:41:08 -0000

Lloyd,

I share many of your concerns, especially in light of the fact that securit=
y ADs have had a dodgy record in the past.=20

In my opinion, there is considerably more work to be done on the threat ana=
lysis that has been ably begun by Brian & co.

Discussion and development of our understanding of the problem space is wha=
t I believe is called for.  If this draft has that effect, it has served a =
useful purpose.

If, on the other hand, developers of a specification discussed the matter i=
n earnest and there was consensus on the way forward, even if some pervasiv=
e threats were not eliminated, and if that work is held up by claims relati=
ng to this draft, then this draft will have caused harm.

That is nothing more or less than common sense.

As to whether this draft is political, I don't think it can be stressed eno=
ugh that if one group of people can subvert our architecture, others can as=
 well. Our political statement, such as it is, is that in order to maintain=
 confidence in the Internet, our protocol suite should be resistant to this=
 sort of thing, but within the bounds of pragmatism.=20

Eliot

> On Jan 1, 2014, at 6:08 AM, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk> w=
rote:
>=20
> what it means for work moving through the IETF process
> is that any work becomes subject to security veto.
>=20
> if security types don't like your work - tough. it's
> going nowhere. draft-farrell really widens that scope.
> and this is going to mean arguments about
> much more than the tradeoffs of using MD5.
>=20
> for a self-described technical organisation that
> does not make policy pronouncements (which is
> itself a very political position, but never mind)
> this draft is awfully political.
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Melinda Shore [melinda.sh=
ore@gmail.com]
> Sent: 01 January 2014 05:38
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive =
Monitoring is an Attack) to Best Current Practice
>=20
>> On 12/31/13 3:23 PM, Dave Crocker wrote:
>>   We should not approve an IETF policy statement
>>  until we have a good idea of the way we will use it.
>=20
> I think this is a critical point and I agree quite strongly
> with it.  I've mostly been baffled by the IETF response to
> revelations about internet eavesdropping, to be honest,
> and it's struck me that work on some of the problems that
> need to be solved to provide better privacy guarantees (for
> example, fixing PKI and providing better keying) have been
> pushed to a back burner in a scramble to make grandiose
> pronouncements.  It's not that draft-farrell is a bad
> document on its own merits, it's just that I cannot for
> the life of me understand what it specifically means for
> work moving through the IETF process.
>=20
> Melinda
>=20

From elear@cisco.com  Wed Jan  1 16:24:53 2014
Return-Path: <elear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621E51ADFCC for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 16:24:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F_TP18k_EAyA for <ietf@ietfa.amsl.com>; Wed,  1 Jan 2014 16:24:51 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 879FE1A1F5B for <ietf@ietf.org>; Wed,  1 Jan 2014 16:24:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5762; q=dns/txt; s=iport; t=1388622285; x=1389831885; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=QeHAKnG3+e2o3WcXzuYJCSOuzRK7Iyin4UIBW3zT25U=; b=U71Iel30OjGOYlmFFnJKmkztAfvyBsPwCizQ/hmwZKZHR70ltS1X76oh XdL0q27eJ3cQL6+vFtwK6a3zq22IT/Lz/GNgjOKVkTZF3j7IYurTXkoox fJGsrVAmNSUhgn93kuDY9hnrwtAMN7HT6dYeEkFnmWLf447DEHdq6X+qe Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQFAMGwxFKtJV2a/2dsb2JhbABYgwu6K4EWFnSCJgEBBHkQAgEIDi0LMiUCBA6ICcQ1F48dB4MjgRMEmBeSFIFvgT4
X-IronPort-AV: E=Sophos;i="4.95,587,1384300800"; d="scan'208,217";a="9994930"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-3.cisco.com with ESMTP; 02 Jan 2014 00:24:43 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s020Ohxt031274 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 2 Jan 2014 00:24:43 GMT
Received: from xmb-rcd-x11.cisco.com ([169.254.1.68]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Wed, 1 Jan 2014 18:24:43 -0600
From: "Eliot Lear (elear)" <elear@cisco.com>
To: Tim Bray <tbray@textuality.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPBmm9pbICcHPufUqxa+8Y/HlcnppvZyCAgACqLQCAAH4UgIAAECUA///1tmc=
Date: Thu, 2 Jan 2014 00:24:42 +0000
Message-ID: <22AEF4B7-9F17-4B72-8B16-8F6A7759771A@cisco.com>
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <00cb01cf06dc$c6d7d8c0$54878a40$@riw.us> <m2ob3vpoji.wl%randy@psg.com>, <CAHBU6iuyMiLcRNS1Oc0xkZ=Rd2WoquE9b8fxexvO3QyJub26nQ@mail.gmail.com>
In-Reply-To: <CAHBU6iuyMiLcRNS1Oc0xkZ=Rd2WoquE9b8fxexvO3QyJub26nQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_22AEF4B79F174B728B168F6A7759771Aciscocom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 02 Jan 2014 09:26:43 -0800
Cc: "ietf@ietf.org" <ietf@ietf.org>, Eliot Lear <lear@lear.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 00:24:53 -0000

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


Tim,


This paragraph seems ridiculous to me.

Then you've not the history to have seen reasonable protocols be held up- o=
r worse mangled- to satisfy unreasonable decisions by ADs based on their in=
terpretation of their authority.   We have been down this road before. And =
again, I'm not concerned about the current ADs, mind you. We've a good lot.

 The perpass-attack draft says that pervasive monitoring has the characteri=
stics of an attack, and that the protocols we design SHOULD include appropr=
iate mitigation measures.

Well it doesn't say that (at least in -03) and let's not suppose it did.

There are very few (any?) absolutes in any of the protocols we build, just =
a wealth of often-conflicting design criteria, which force us to trade off =
and make judgment calls.  draft-perpass-attack says that mitigation of perv=
asive surveillance should be seen as one of the design criteria, and it=92s=
 not OK to ignore it.

In fact I've argued all if this myself.  It presumes we understand the thre=
at well enough.  One concern at the moment is that a group will take an act=
ion in response that actually ENABLES more pervasive surveillance.  That ma=
y be unavoidable as there will be trade offs.


A reasonable take is that a specification could be held up if there are pla=
usible arguments that this criterion has not been given appropriate conside=
ration, and I see nothing wrong with that.

Sure. But now you've actually rung in another problem with the draft. Most =
participants in the IETF don't know how to address the threat and those who=
 think they do probably won't agree on either it's nature or the remediatio=
n.

We're simply not there yet.

The IETF should take this threat seriously and do what we can when we know =
what to do.

Eliot



--_000_22AEF4B79F174B728B168F6A7759771Aciscocom_
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 dir=3D"auto">
<div><br>
Tim,&nbsp;</div>
<div><br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div><br>
</div>
<div>This paragraph seems ridiculous to me. </div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Then you've not the history to have seen reasonable protocols be held up- o=
r worse mangled- to satisfy unreasonable decisions by ADs based on their in=
terpretation of their authority. &nbsp; We have been down this road before.=
 And again, I'm not concerned about the
 current ADs, mind you. We've a good lot.&nbsp;
<div><br>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>&nbsp;The perpass-attack draft says that pervasive monitoring has the =
characteristics of an attack, and that the protocols we design SHOULD inclu=
de appropriate mitigation measures.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Well it doesn't say that (at least in -03) and let's not suppose it did.&nb=
sp;<br>
<div><br>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>There are very few (any?) absolutes in any of the protocols we build, =
just a wealth of often-conflicting design criteria, which force us to trade=
 off and make judgment calls. &nbsp;draft-perpass-attack says that mitigati=
on of pervasive surveillance should be
 seen as one of the design criteria, and it=92s not OK to ignore it.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
In fact I've argued all if this myself. &nbsp;It presumes we understand the=
 threat well enough. &nbsp;One concern at the moment is that a group will t=
ake an action in response that actually ENABLES more pervasive surveillance=
. &nbsp;That may be unavoidable as there will be
 trade offs.&nbsp;</div>
<div><br>
</div>
<div>
<div><br>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<div>A reasonable take is that a specification could be held up if there ar=
e plausible arguments that this criterion has not been given appropriate co=
nsideration, and I see nothing wrong with that.</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
Sure. But now you've actually rung in another problem with the draft. Most =
participants in the IETF don't know how to address the threat and those who=
 think they do probably won't agree on either it's nature or the remediatio=
n. &nbsp;</div>
<div><br>
</div>
<div>We're simply not there yet.</div>
<div><br>
</div>
<div>The IETF should take this threat seriously and do what we can when we =
know what to do.</div>
<div><br>
</div>
<div>Eliot</div>
<div>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
<div dir=3D"auto">
<div>
<blockquote type=3D"cite"><font color=3D"#000000"><span style=3D"background=
-color:rgba(255,255,255,0)"><br>
</span></font></blockquote>
</div>
<div>
<div>
<div><br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</body>
</html>

--_000_22AEF4B79F174B728B168F6A7759771Aciscocom_--

From hsantos@isdg.net  Thu Jan  2 10:49:22 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B13AC1A1F79 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 10:49:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tdo8MM-_8Lyf for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 10:49:20 -0800 (PST)
Received: from groups.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 423011A1F65 for <ietf@ietf.org>; Thu,  2 Jan 2014 10:49:20 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3605; t=1388688543; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=d0WBnWV7qqdDPKdDVVoKy4RE7WA=; b=jIawIS1L8+4w0KJQTj9y KQZyTslKxWp2VuXXPvAK7kemQYoznMG/ERUm5lwM1W2Y7tBjGthffnnCIXA1K3C5 T5lnqGQlufRdyJileetTMn8tpGvN3OrIV2fvCyEm23Vy8dfe5hujcqmP7K9AUuJO H32tqDCV7+WpvpuWpqWGFLY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 02 Jan 2014 13:49:03 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2266024244.20793.5388; Thu, 02 Jan 2014 13:49:02 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3605; t=1388688000; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=YACzZgp Ev4XqBo15jWiagtSTGkNfi4nYci4/MQhwR/Y=; b=UO07azWMpsbS8y2Q93zo5uD eMEyHZIQJ7GCL0nqbtRJUrsPhFNd7DVBrSFmWHg6Dzl+H5jXb00GxqzF/LTWGvOd ZXuBLChQOFon/iMakT48MnCcdex/HQlEAOVUnyIuqVcw2/mTs5gGQJiabKvnM2gR VkOBtSztwUX9P/28c1ww=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 02 Jan 2014 13:40:00 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1712346489.9.348; Thu, 02 Jan 2014 13:39:59 -0500
Message-ID: <52C5B4A1.7060509@isdg.net>
Date: Thu, 02 Jan 2014 13:49:05 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com>	<A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net>	<002501cef266$b0b8a540$4001a8c0@gateway.2wire.net>	<52A23B16.4060306@gmail.com>	<CC5864F92767060505B97E0A@JcK-HP8200.jck.com>	<52A8D6C4.2050006@cs.tcd.ie>	<55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com>	<BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com>	<004001cf0744$fab41470$f01c3d50$@riw.us>	<52C49FB2.9090208@gmail.com>	<78121BF5-D5B4-4592-BFE5-FD5CFA338640@nominum.com>	<52C4DF7D.3010509@gmail.com>	<52C566F4.2040201@cs.tcd.ie> <CAPv4CP85sTyroRohy+4Tr6qeEKyVTffqUgRvWRuuWu5jTzws2g@mail.gmail.com> <52C56B2C.5040707@cs.tcd.ie>
In-Reply-To: <52C56B2C.5040707@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 18:49:22 -0000

On 1/2/2014 8:35 AM, Stephen Farrell wrote:

> On 01/02/2014 01:26 PM, Scott Brim wrote:
>> On Jan 2, 2014 8:18 AM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>>> And so with this one - stating only the high level requirement
>>> is the right thing to do for now
>>
>> Would it be better to leave this one informational and not make it a BCP?
>> There's extremely little in it that is Practice.  The next level down is
>> where we would add more specific guidelines and BCPs.
>
> See the quote from 2026 in my response to Dave - what is wrong
> with following that and making a statement of principle as a
> BCP?
>
> There should be no need for all BCPs to have lots and lots of
> detail surely.
>
> And FWIW, I do think it'll be easier to get WGs to properly
> consider the attack/threats if this is a BCP.
>
> I also think it'll be cleaner to update as a BCP, if and
> when we wanted to add more detail, but that's a minor detail.

The key problem is to get the WG to consider anyway despite any BCP or 
document of any status.  We should not have to be told what is "right 
or wrong" to consider when it comes ethical engineering.   We all know 
what is "bad" when we see it.  Right?

Well, perhaps not.  I will use an example with this whole effort to do 
the "right thing" when it comes to privacy and security.

Consider the super fast track APPS-DISCUSS WG draft proposed standard 
that is currently in LC:

 
http://tools.ietf.org/html/draft-ietf-appsawg-rrvs-header-field-05

This RRVS idea deals with an extremely risky potential concept to 
REUSE EMAIL ADDRESSES/IDS. The RRVS proposes an unclear method with 
claims it can offer a secured and safe way to allow email hosting 
sites the ability to offer reusable email addresses.   There are 
claims that this is in production mode, yet, there is no means to do 
general broad mail network interop testing.  There are no interop 
reports as far as I can see.  However, that are published (google 
reseached) reports and concerns for:

    - Privacy, Security Leaks and
    - (Email) Identity Lost

I will add:

    - Increased SPAM that are currently blocked but accepted for
      transferred ids.


All that, and I'm accused of bringing "Layer Nine" (whatever that 
means) to the table. If so, so be it.  I feel I am doing my job 
product manager and as a potential implementator of this RRVS proposal.

I believe this is what Stephen Farrell's draft is all about -- to get 
people to better consider what are the potential issues.   In the case 
of RRVS, as it is written as a proposed standard but an experimental 
status proposal to be further explored before the IETF accepts and 
advocates any idea that has a high potential to leak private, secured 
information, a risk for identity lost and reopens SPAM to transferred 
targets.

Isn't the purpose of this draft to get people to better engineer IETF 
sanctioned protocols in secured, safe ways without hampering progress? 
  Sure, we all know there is a balance, but some are so obvious such 
as this RRVS that it is already filled with "Layer Nine" and as 
"conflict of interest" rush to completely track that is mind numbing. 
Its become too overwhelming and you risk getting the negative label to 
speaking up.  The fact is, the concept is good, but it still needs 
more work.

So be it.

I guess we can use a strong document to throw at people when they 
begin to ignore you.  Hopefully, its shouldn't have to come to that 
each and every time. Its exhausting.

I vote to make any new document related to better IETF engineering a BCP.

-- 
HLS



From stephen.farrell@cs.tcd.ie  Thu Jan  2 11:23:42 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6786B1AC403 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 11:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.761
X-Spam-Level: *
X-Spam-Status: No, score=1.761 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MANGLED_LIST=2.3, RP_MATCHES_RCVD=-0.538] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vv7idiLKyFq7 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 11:23:37 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 58A451A82E2 for <ietf@ietf.org>; Thu,  2 Jan 2014 11:23:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 543C9BE5F; Thu,  2 Jan 2014 19:23:29 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k+ul1jyCZcty; Thu,  2 Jan 2014 19:23:27 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.46.18.246]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1AAFABE58; Thu,  2 Jan 2014 19:23:27 +0000 (GMT)
Message-ID: <52C5BCA4.60403@cs.tcd.ie>
Date: Thu, 02 Jan 2014 19:23:16 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Rene Struik <rstruik.ext@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <52C314B3.6090402@gmail.com>
In-Reply-To: <52C314B3.6090402@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 19:23:42 -0000

Hiya,

On 12/31/2013 07:02 PM, Rene Struik wrote:
> Dear colleagues:
> 
> While I do agree with some of the underlying sentiments of the draft, I
> am not that happy with the somewhat sloppy exposition of the draft, in
> particular to what problem one really wishes to address (see #1, #2
> below). Moreover, I feel that the implicit suggestion of the draft that
> one should take an almost binary approach to addressing passive attacks
> may be detrimental at achieving a solid security architectural design
> (it should be a proper balancing, rather than 0-1 thinking w.r.t. one of
> many security architectural considerations).

Sorry - what text suggests a binary approach? Please do give
quotes, as that is not the intent, and nor is it expressed.
In fact the draft says:

  "The IETF will work to mitigate the
   technical parts of the pervasive monitoring threat, just as we do for
   other protocol vulnerabilities."

I really don't see how that can be mis-interpreted as a
"binary" approach. Can you explain?

> 
> In my mind, the draft needs to be more carefully written, so as to make
> intent and grey scales of proposed design metrics clearer. More details
> below.
> 
> Some technical comments:
> 
> 1) In Section 1, 3rd para, the term "attack" (in the context of
> pervasive monitoring) is too broadly defined: pervasive monitoring is
> (an extreme form of) monitoring and, thereby, an attack form that has
> been dubbed (decades ago) in the cryptographic literature as an attack
> by a *passive* adversary. 

No. We are not defining pervasive monitoring as being purely passive,
since it is not. And nor is it an active attack entirely. So its
correct that the definition is that broad and differs from either
passive or active attacks.

I think a perhaps lot of your other comments hang on this
misunderstanding. But I'll comments on bits of those below. But
what you call a misnomer is deliberate, and is needed IMO.

I'd welcome a better definition if we can find one.

> (The fact that this may happen on a massive
> scale does not change its nature.) In the draft, though, one seems to
> lump this together with other attack forms, where a passive adversary
> may exploit insights gathered from passive attacks to subsequently
> facilitate an active attack (witness the use of "to enforce the
> opponent's will on the attacked party" in 3rd para, 3rd line or "that
> subverts the intent of a communicator without the agreement of the
> parties to the communication" in 3rd para, 6th line). The latter is an
> *active* attack, which is not part of pervasive monitoring itself (but
> only may take advantage of this). 

The active aspect is also a part of pervasive monitoring as
defined here, and needs to be considered as such. For example,
if an RSA private key is exfiltrated via an active attack in
order to later decrypt non-PFS ciphertext. (As in the Belgacom
case perhaps.) That is part of the pervasive monitoring
attack, but is not well described as either passive nor active.

> With passive attacks, in most cases
> (e.g., when using wireless communications) the presence or absence of an
> passive adversary cannot be distinguished. I would strongly suggest
> using proper notions and avoiding confusing and ill-defined terms (for
> definitions, see, e.g., Definition 12.15 of the Handbook of Applied
> Cryptography (CRC Press, 1995)). Shouldn't one simply change the title
> of Section 1 to the (somewhat obvious) statement "Pervasive monitoring
> is Indistinguishable from a Passive Attack" or "Pervasive Monitoring
> Cannot Be Distinguished From Non-Monitoring, So One Should Prepare For
> the Worst"?

No. It would be wrong to only consider pervasive monitoring as
a passive attack as that is not the case.

I think our conceptions of passive and active have in fact held
us back to an extent in that they may have made us less likely
to recognise the potential for the pervasive monitoring attack
which mixes both approaches and at scale.

> 2) In Section 1, 4th para, if the intent of the draft is to also raise
> awareness of active (pervasive) attacks, it should say so clearly and
> not suggest, as it seems to do right now, that this is due to "pervasive
> monitoring" (since, as already said, this is a misnomer). Here, again,
> though, this is nothing new by itself: security services need to be in
> place where the interests of communicating parties, including the
> communicating networks used by these parties (and lurking adversaries
> therein) are not aligned. I would suggest emphasizing, far more than
> currently done, the role pervasive monitoring could play in paving the
> way towards providing useful insight to make a subsequent (or
> interactive) active attack more successful, since that seems to be one
> of the underlying currents of the draft.

No, the main purpose of that paragraph is to empahasise that
the IETF don't need to take a position on the morality or
otherwise of e.g. specific NSA or GCHQ motivations. We can and
do say that their actions are an attack, but we do not say that
their motivations are good, bad or indifferent.

That is necessary so that when someone misinterprets the draft
as saying that "the IETF says that NSA are bad" they can be
corrected by pointing at this text.

The text in this draft *will* be deliberately misinterpreted
by some for their own ends so this really is needed.

> 3) In Section 1, 1st para, it is stated that " [...] that this was an
> attack that should be mitigated where possible via the design of
> protocols that make pervasive monitoring significantly more expensive or
> infeasible". While I wholeheartedly agree that protocol design should
> include privacy-relevant objectives (such as hiding header info and
> meta-data), to me it seems this should always have been in the security

"should always have been" is correct from a security and privacy
perspective. But it is clearly the case that such consideration has
not been a typical part of current or past practice.

Hence the need for this BCP.

> services objective list with security and communication protocol design
> and it is somewhat surprising to see that this apparently is something
> new (or, do I read this in the wrong way?). Isn't the main change
> between the pre-Snowden and post-Snowden era that one is now aware that
> would should attach more weight to security objectives one may very well
> have unrightfully ignored in the past??? I am really concerned that this
> becomes now a single quest at the detriment of other security objectives
> one may wish to cater to.

Sigh. "Single quest" is a very weird mis-reading of the draft.
See the text quoted above. I honestly don't get how you end up
thinking that.

> After all, with security and communication
> protocol design, one should balance different objectives according to
> deployment scenario at hand and there are many, many considerations that
> could play a role. To this point, I already expressed concern in an
> email of September 6th (see
> http://www.ietf.org/mail-archive/web/perpass/current/msg00099.html)

That message was not in relation to this draft. I don't know what
you mean in quoting it sorry. Can you clarify how it relates to
this draft?

> that, e.g., trying to avoid traffic analysis by making all frames the
> same size would be disastrous for applications in a highly constrained
> setting ("internet of things", "smart objects", and the-like); I also
> epressed some other concerns with respect to binary thinking here (see
> the link). I would therefore suggest to express the desire of IETF-88
> somewhat more intelligently and stipulate, e.g., that protocol should
> properly consider security objectives and weigh these and allow security
> policy settings to be picked so as to, indeed, enable more privacy-aware
> deployments. This is mostly a security policy issue, though, and should
> less so be a fixed setting of a security protocol itself. One could dub
> this "security policy agility" vs. "crypto agility" if one wishes....
> (Note: TLS is an example of a somewhat unfortunate design here, where
> one has no security policy agility to hide lots of parms in the protocol
> flows at all). The main point of post-Snowded would then be that the
> "security policy agility" should include the policy to enable privacy
> protection to one's heart content.

I have to say that the above seems to me pretty unclear in comparison
to the current text. (But I would think that of course:-)

> 
> 4) Section 2, 2nd and 3rd para, seems to be a somewhat hidden admission

"Hidden" is not what I think. I think we have failed in some
respects, and generally not done so well in respect of privacy.

> that, perhaps, IETF itself may in the past not have done as good a job
> as it could have in considering and weighing all security objectives.
> After all, notions of passive and active attacks have been around for
> decades, but apparently some of this has been not taken too seriously
> for a while, or would have been considered "too expensive" to
> implementers or vested interests? It can hardly be considered news that,
> e.g., if one does not use adequately secured packets, then visible parts
> may be eavesdropped upon, etc. Right now, it reads as if one is
> indignified even in case one sends entirely unsecured packets and that
> this, surprise, surprise, may be vulnerable to attack. To some network
> people, it may be considered news if protocol messages do not behave as
> specified. To security people, this should be second nature: after all,
> all networks and network components should be considered as gigantic
> security engines, without constraint on actors on the communication
> channel.

Sorry, I don't get what your comment is getting at.

> 
> 5) Section 2, 5th para, seems to be an admission that protocol design
> should intelligently weigh design objectives (e.g., so as not to rule
> out monitoring for network monitoring purposes). So, if this means one
> wishes to cater for "security policy agility" as I alluded to above, so
> much the better.

I wouldn't call it an "admission". Again though, I'm not clear
if you're asking for some change or not.

Cheers,
S.


> 
> Best regards, Rene
> 
> On 12/3/2013 12:48 PM, The IESG wrote:
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Pervasive Monitoring is an Attack'
>>    <draft-farrell-perpass-attack-02.txt> as Best Current Practice
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2013-12-31. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     The IETF has consensus that pervasive monitoring is a technical
>>     attack that should be mitigated in the design of IETF protocols,
>>     where possible.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
> 
> 

From stephen.farrell@cs.tcd.ie  Thu Jan  2 11:46:33 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB90F1ADDAC for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 11:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwDpljcoYFgK for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 11:46:32 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9E6FA1ADBCE for <ietf@ietf.org>; Thu,  2 Jan 2014 11:46:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id BDF30BE5F; Thu,  2 Jan 2014 19:46:23 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id goN3CU0L+nDv; Thu,  2 Jan 2014 19:46:22 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.46.18.246]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8D0A3BE5D; Thu,  2 Jan 2014 19:46:22 +0000 (GMT)
Message-ID: <52C5C204.60708@cs.tcd.ie>
Date: Thu, 02 Jan 2014 19:46:12 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: stbryant@cisco.com, Ted Lemon <ted.lemon@nominum.com>,  John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <BE20435A-F6BB-491B-BC56-951830B0F436@nominum.com> <52C5926C.1060403@cisco.com>
In-Reply-To: <52C5926C.1060403@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 19:46:34 -0000

On 01/02/2014 04:23 PM, Stewart Bryant wrote:
> On 01/01/2014 22:08, Ted Lemon wrote:
>> This argument boils down to "ADs can abuse process, so we ought not to
>> ever publish a document that might provide process for them to abuse.
> Ted, I believe the point is that the AD concerned would not be abusing
> the process, they would simply be making a different judgement call, or
> a stricter interpretation (for what ever reason) of the in place PM
> requirements than the authors and preceding reviewers of the text.
> 
> The  -03 text is a significant improvement, but I still fear the impact
> of single issue technical politics on the output of our document stream.

But Ted also pointed out that there is already plenty of ammunition
for an overly zealous AD to use to have that bad effect. And you and
others are I think also saying that that did happen in the past. If so,
then this BCP will have no impact in that respect - what is already
possible will continue to be possible regardless of what happens with
this draft.

S.


> 
> Stewart
> 

From stephen.farrell@cs.tcd.ie  Thu Jan  2 13:39:41 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04C3E1A8028 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 13:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtHbTNbd6Vfl for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 13:39:38 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 11F891A1F5F for <ietf@ietf.org>; Thu,  2 Jan 2014 13:39:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0FFF4BE5D; Thu,  2 Jan 2014 21:39:30 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 002glCvfmd27; Thu,  2 Jan 2014 21:39:28 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.46.18.246]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 434DCBE4C; Thu,  2 Jan 2014 21:39:28 +0000 (GMT)
Message-ID: <52C5DC86.3010908@cs.tcd.ie>
Date: Thu, 02 Jan 2014 21:39:18 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <20131203174852.21387.26099.idtracker@ietfa.amsl.com> <A3B306E3-846C-45BA-8ED9-13B96AA645A3@piuha.net> <002501cef266$b0b8a540$4001a8c0@gateway.2wire.net> <52A23B16.4060306@gmail.com> <CC5864F92767060505B97E0A@JcK-HP8200.jck.com> <52A8D6C4.2050006@cs.tcd.ie> <55026AF53DB6CBD3D29B2040@JcK-HP8200.jck.com> <52C35FFD.607@dcrocker.net> <CADnDZ8-WoyxXDTQ0QoQOOYxc5xzLgpHmhA7VkuN6OmRV-DhX8Q@mail.gmail.com> <52C58DC0.4000501@bbn.com>
In-Reply-To: <52C58DC0.4000501@bbn.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 21:39:41 -0000

Hi Steve,

A couple of points...

On 01/02/2014 04:03 PM, Stephen Kent wrote:
> I commented earlier to Stephen (off list) that BCP status seemed a bit
> out of place for
> a position statement, so I'm heartened to see others have a similar
> concern. I concur
> with the suggestion that this be (IAB stream) Informational.
> 
> If published as Informational, I don't worry that this doc does not lay
> out details
> for what WGs are expected to do. At the behest of two IAB members, I am
> working on a
> doc that examines keying options for major IETF security protocols, and
> discusses what
> changes could be made to facilitate anonymous encryption as a fallback
> from authenticated encryption. This is just one aspect of an overall
> response to PM, but it will yield concrete proposals. Other folks are
> working on an updated threat model doc.
> 
> I have also noted that the document refers to PM as "indistinguishable"
> from an attack,
> which IMHO seems too polite. PM is effected via passive and active
> wiretapping attacks, and
> thus it IS an attack. 

I fully agree its an attack, but the point of indistinguishable
is not to be polite, but rather to counter those who'd declare
that it is not an attack because their government only ever do
good things. That is also important. (And is the main reason for
this response as its a new point, I think most of the stuff
below is repetitive.

> Tim Bray's message characterized the current draft
> as saying "The perpass-attack draft says that pervasive monitoring has
> the characteristics of an attack, ..." This suggests that a reader
> doesn't interpret the text as saying that PM _is_ an attack.
> We should avoid words that may lead a reader to believe that PM is
> /equivalent/ to an
> attack. Its easy to make a case that PM is an attack. I provided (off
> list) feedback a
> few weeks ago suggesting a different way to present the issues here, and
> have updated that text:

I think I responded to that (wasn't it on list too? but anyway...).

> For many years the IETF security community has used an attack/threat
> model [RFC3552] that envisions an adversary who can engage in passive
> and active wiretapping at any point along a communication path. 

"a path" != many paths which is what we've now seen to be the case

> We
> commonly attribute the ability to engage in MITM attacks to such an
> adversary. Thus we have long believed that plaintext communications are
> vulnerable to passive wiretapping along a communication path if the
> content is not protected via encryption. We also have noted that, for
> staged delivery applications, e.g., mail, content is vulnerable to
> disclosure and modification in storage, especially en route.In response
> to this model we have developed a set of security protocols, (e.g.,
> IPsec, TLS, DTLS, S/MIME, SSH, etc.) that can be used to protect
> transmitted content against passive wiretapping, based on use of
> encryption. 

Sorry, no - those are fine tools but they do not fully protect.
For example S/MIME doesn't cover mail headers etc.

> These protocols also usually incorporate data integrity and
> authentication mechanisms, and, where appropriate, anti-replay
> mechanisms, to address MITM attacks. Thus we have offered users and
> system designers a set of tools that address the adversarial
> capabilities based on our model.

If that last is meant to mean that we've already done enough
then I don't share that view.

> When pervasive monitoring is effected via passive wiretapping, or a mix
> of active and passive wiretapping (e.g., using packet injection attacks)
> it is not a new class of attack. It is precisely what we have long
> considered when designing security protocols. 

I don't think that's defensible to be honest if you mean that
we've long considered this scale and kind of attack and designed
countermeasures accordingly.

> Thus I believe this
> document should include comments of the sort noted above, to help
> establish a context for this declaration about "pervasive monitoring".
> 
> Having established this context, the next task is to explain why
> pervasive monitoring is significantly different from our long-standing
> model. The extent of such monitoring seems much bigger in scope than
> folks may have imagined, given that intelligence services of numerous
> countries have been identified as carrying on such monitoring. However,
> RFC 3552 states:
> 
>    By contrast, we assume that the attacker has nearly complete control
>    ofthe communications channel over which the end-systems communicate.

Again, that talks about "the" channel though.

>    This means that the attacker can read any PDU (Protocol Data Unit) on
>    the network and undetectably remove, change, or inject forged packets
>    onto the wire.  This includes being able to generate packets that
>    appear to be from a trusted machine.  Thus, even if the end-system
>    with which you wish to communicate is itself secure, the Internet
>    environment provides no assurance that packets which claim to be from
>    that system in fact are.
> 
> This statement is pretty clear. I think the PM document needs to
> explain, in a technical context, why pervasive monitoring is
> qualitatively different, and thus merits this declaration by the IETF.

I don't agree to be honest that that is needed. The fact of the attack
is sufficient justification, compared to previous consideration of
potential, not actually exploited, threats.

> We ought not lead readers to believe that we have not considered passive
> and active wiretapping as likely attacks in the past.

I agree we did consider those. But in too limited a way as it turns
out.

> Some of the reported forms of pervasive monitoring may have involved the
> cooperation of or subversion of an ISP or a telecom provider. This is
> not a qualitatively different form of attack from the generic passive
> wiretapping that our security model has always assumed.
> 
> Some of the reported forms of pervasive monitoring have involved the
> cooperation of or subversion of application service providers. This does
> represent a major deviation from
> the 3552 model:
> 
>    The Internet environment has a fairly well understood threat model.
> *In general, we assume that the end-systems engaging in a protocol**
> **   exchange have not themselves been compromised.*
> 
> So we should acknowledge this as one asp[ect of PM that is different
> from our threat model. However, if attacks take place at a point after
> which IETF protocols terminate, then it seems to be largely outside of
> our purview as a protocol-focused standards organization. For example,
> if I access e-mail via a _web_ _interface_ at an MSP, IETF security
> standards largely do not seem to apply to vulnerabilities associated
> with storage of the mail at the MSP; my mail can't be protected e-t-e
> because I'm not using S/MIME to read the mail. I can use TLS to protect
> the HTTPS session via which I access messages, and we can recommend that
> TLS be used with SMTP to deliver the mail to the MSP, but that seems to
> be the limit of our security protocols.

I strongly disagree with that last point. If we are ever to succeed
with end-to-end email security for example (which I doubt), then that
would have to encompass web-UAs as an inherent part of the overall
system. Thus the security of the message store and submission server
would be intimately related to any e2e confidentiality mechanism.
And of course, we'd also need to counter spam somehow. Those are real
requirements that show that our threat models do need to extend to
some (but not all) aspects of host security.

Regards,
S.


> 
> 
> 
> 
> 
> 

From housley@vigilsec.com  Thu Jan  2 13:44:33 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DF81ADF9C; Thu,  2 Jan 2014 13:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NyCsLLAzek94; Thu,  2 Jan 2014 13:44:31 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1D63D1ADF8E; Thu,  2 Jan 2014 13:44:31 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 25B699A423A; Thu,  2 Jan 2014 16:44:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id n2B-dJtkz9zh; Thu,  2 Jan 2014 16:43:53 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1D3C89A4220; Thu,  2 Jan 2014 16:43:53 -0500 (EST)
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com>
Date: Thu, 2 Jan 2014 16:43:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1085)
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jan 2014 21:44:33 -0000

SM:

> An alternative might be:
>=20
>   3. IETF participants devise solutions for the Internet that meet the
>      needs of diverse technical and operational environments.
>=20
>      The mission of the IETF is to produce high quality, relevant
>      technical and engineering documents that influence the way people
>      design, use, and manage the Internet in such a way as to make the
>      Internet work better.  The IETF puts its emphasis on technical
>      competence, rough consensus and individual participation, and =
needs
>      to be open to competent input from any source.
>=20
>      IETF participants use their best engineering judgment to find the
>      best solution for the whole Internet, not just the best solution
>      for any particular network, technology, vendor, or user.  While =
we
>      all have ideas that may stand improvement from time to time, no
>      one shall ever knowingly contribute advice or text that would =
make
>      a standard technically inferior.

This proposed text is an improvement, but I would be much happier with =
the addition of one word to the first sentence:  ... devise solutions =
for the global Internet ...

>> BCP 79 is the proper reference.
>>=20
>> Following the IPR rules is an obligation for all IETF participants.  =
It was in RFC 3184, and I think we need to keep in this document.
>=20
> The text in RFC 3184 is as follows:
>=20
>  "We follow the intellectual property guidelines outlined in BCP 9."
>=20
> In my opinion that text does not fit under the third statement.  An =
alternative, which was suggested, is to have it under another guideline. =
 The comment mentions that it is an obligation and I agree with that.  =
The point being discussed is that the obligation has to be kept in this =
document because it was in RFC 3184.  The document has been described as =
being about personal conduct and personal interaction.  The document =
does not discuss about rules.

Disclosure of IPR that you know about is personal conduct.

> The Note Well is used to direct people to BCP 79.  A person attending =
a working group session will be told about the Note Well.  A person =
subscribing to an IETF mailing list will be sent a pointer to the Note =
Well.  I suggest leaving it to the Note Well to list the rules as it has =
not been argued that the Note Well is inadequate.

RFC 3184 included a sentence telling people about the expected conduct =
regarding IPR disclosure.  I strongly believe that 3184 should do the =
same.

Russ


From narten@us.ibm.com  Thu Jan  2 21:53:19 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FE1B1AD8F3 for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 21:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.739
X-Spam-Level: 
X-Spam-Status: No, score=-3.739 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MANGLED_SAVELE=2.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F9nif5WB9EMa for <ietf@ietfa.amsl.com>; Thu,  2 Jan 2014 21:53:17 -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 5182E1AC49D for <ietf@ietf.org>; Thu,  2 Jan 2014 21:53:17 -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, 2 Jan 2014 22:53:10 -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, 2 Jan 2014 22:53:08 -0700
Received: from b03cxnp07028.gho.boulder.ibm.com (b03cxnp07028.gho.boulder.ibm.com [9.17.130.15]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 410931FF001B for <ietf@ietf.org>; Thu,  2 Jan 2014 22:52:36 -0700 (MST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by b03cxnp07028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s035qtkK9240992 for <ietf@ietf.org>; Fri, 3 Jan 2014 06:52:55 +0100
Received: from d03av05.boulder.ibm.com (localhost [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s035r3Kt008556 for <ietf@ietf.org>; Thu, 2 Jan 2014 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.14.4/NCO v10.0 AVin) with ESMTP id s035r30p008528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 2 Jan 2014 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s035r264010591 for <ietf@ietf.org>; Fri, 3 Jan 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s035r2PK010558 for ietf@ietf.org; Fri, 3 Jan 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201401030553.s035r2PK010558@rotala.raleigh.ibm.com>
Date: Fri, 03 Jan 2014 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-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14010305-0928-0000-0000-0000050D8DDA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 05:53:19 -0000

Total of 111 messages in the last 7 days.
 
script run at: Fri Jan  3 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.01% |   10 | 10.17% |    97717 | stephen.farrell@cs.tcd.ie
  7.21% |    8 |  8.46% |    81254 | abdussalambaryun@gmail.com
  7.21% |    8 |  6.79% |    65233 | l.wood@surrey.ac.uk
  6.31% |    7 |  5.32% |    51156 | ted.lemon@nominum.com
  6.31% |    7 |  5.03% |    48310 | dhc@dcrocker.net
  5.41% |    6 |  4.27% |    41016 | melinda.shore@gmail.com
  4.50% |    5 |  4.25% |    40827 | john-ietf@jck.com
  4.50% |    5 |  4.13% |    39690 | russw@riw.us
  3.60% |    4 |  4.19% |    40272 | daedulus@btconnect.com
  3.60% |    4 |  3.22% |    30898 | scott.brim@gmail.com
  3.60% |    4 |  2.70% |    25972 | derhoermi@gmx.net
  3.60% |    4 |  2.60% |    24985 | ajs@anvilwalrusden.com
  2.70% |    3 |  3.24% |    31100 | sm+ietf@elandsys.com
  2.70% |    3 |  2.62% |    25194 | brian.e.carpenter@gmail.com
  2.70% |    3 |  2.24% |    21571 | housley@vigilsec.com
  1.80% |    2 |  2.80% |    26943 | hallam@gmail.com
  1.80% |    2 |  2.24% |    21520 | elear@cisco.com
  1.80% |    2 |  1.85% |    17754 | david.black@emc.com
  1.80% |    2 |  1.81% |    17386 | farmer@umn.edu
  1.80% |    2 |  1.65% |    15808 | ynir@checkpoint.com
  1.80% |    2 |  1.50% |    14372 | stbryant@cisco.com
  1.80% |    2 |  1.41% |    13558 | adrian@olddog.co.uk
  0.90% |    1 |  2.15% |    20646 | lear@lear.ch
  0.90% |    1 |  2.14% |    20576 | tbray@textuality.com
  0.90% |    1 |  2.10% |    20179 | kent@bbn.com
  0.90% |    1 |  1.43% |    13789 | rstruik.ext@gmail.com
  0.90% |    1 |  1.42% |    13632 | yaojk@cnnic.cn
  0.90% |    1 |  1.40% |    13445 | michel@arneill-py.sacramento.ca.us
  0.90% |    1 |  1.07% |    10304 | hsantos@isdg.net
  0.90% |    1 |  0.77% |     7423 | narten@us.ibm.com
  0.90% |    1 |  0.70% |     6770 | mcr@sandelman.ca
  0.90% |    1 |  0.70% |     6757 | joelja@bogus.com
  0.90% |    1 |  0.69% |     6620 | mcr+ietf@sandelman.ca
  0.90% |    1 |  0.65% |     6280 | agmalis@gmail.com
  0.90% |    1 |  0.65% |     6247 | johnl@taugh.com
  0.90% |    1 |  0.64% |     6142 | randy@psg.com
  0.90% |    1 |  0.52% |     5001 | chair@ietf.org
  0.90% |    1 |  0.48% |     4605 | ahmedbakhat@pta.gov.pk
--------+------+--------+----------+------------------------
100.00% |  111 |100.00% |   960952 | Total


From sm@elandsys.com  Fri Jan  3 01:45:13 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9F3B1ADF66; Fri,  3 Jan 2014 01:45:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3DYo_ASa-lY; Fri,  3 Jan 2014 01:45:12 -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 7511C1ADF67; Fri,  3 Jan 2014 01:45:12 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.153.168]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s039ipXH024636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jan 2014 01:45:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388742303; bh=GZpC200iZs4lOK2bfwW6H5ZaAQ1dA2wyKKKjSDqV8Os=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iuoTF6ndrKIkk1FuGF6nCPI7WCU5R+yzMLGTYupI35dAKIkgEP31wcwgPM7xyO9bf qQQZMiFjiYRLvnyX1qh46CWcZKdoP9Lu2Vl8RVOsZTy61aU4iX4MF9pIOkPXsQ17qn hgQX5xrLbLWbefMHJYwYw6XnvZdp90pBjyzCZM1o=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1388742303; i=@elandsys.com; bh=GZpC200iZs4lOK2bfwW6H5ZaAQ1dA2wyKKKjSDqV8Os=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=i58lRSbO7qgUPXRS0fHwV+epFjaBgb8mWvz1RDL9S4h4GuN2uBQBfHdq7TpHPsBCu cWKZ7RrMnBvhrU1/WufEFoHkl6Vpt+2gW3odVns8EaVaymZZsRoz5umI096Wq/WU6V hi10FANueGMv1JNYW38TlbTrpAJZyikiAVQPwrns=
Message-Id: <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 02 Jan 2014 23:36:11 -0800
To: Russ Housley <housley@vigilsec.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
In-Reply-To: <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 09:45:13 -0000

Hi Russ,
At 13:43 02-01-2014, Russ Housley wrote:
>This proposed text is an improvement, but I would be much happier 
>with the addition of one word to the first sentence:  ... devise 
>solutions for the global Internet ...

With the above suggestion, the third statement could be as follows:

    3. IETF participants devise solutions for the global Internet that
       meet the needs of diverse technical and operational environments.

>Disclosure of IPR that you know about is personal conduct.
>
> > The Note Well is used to direct people to BCP 79.  A person 
> attending a working group session will be told about the Note 
> Well.  A person subscribing to an IETF mailing list will be sent a 
> pointer to the Note Well.  I suggest leaving it to the Note Well to 
> list the rules as it has not been argued that the Note Well is inadequate.
>
>RFC 3184 included a sentence telling people about the expected 
>conduct regarding IPR disclosure.  I strongly believe that 3184 
>should do the same.

I'll consider this concern as unresolved.  The Area Directors can 
review the comments and recommend how to resolve the concern.

Regards,
S. Moonesamy  


From Ted.Lemon@nominum.com  Fri Jan  3 04:54:59 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B51F1ADFA3; Fri,  3 Jan 2014 04:54:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5F91O3-jTisb; Fri,  3 Jan 2014 04:54:58 -0800 (PST)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6D01ADF87; Fri,  3 Jan 2014 04:54:58 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUsazG7wQeQMbga0uecZ5RpWfuF32dyX5@postini.com; Fri, 03 Jan 2014 04:54:51 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D92AF1B82DC; Fri,  3 Jan 2014 04:54:50 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 83B3919005C; Fri,  3 Jan 2014 04:54:50 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 3 Jan 2014 04:54:44 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
Date: Fri, 3 Jan 2014 07:54:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E97AD58F-4F4B-4342-A4E5-9E8B4A6C246C@nominum.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com> <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 12:54:59 -0000

On Jan 3, 2014, at 2:36 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> I'll consider this concern as unresolved.  The Area Directors can =
review the comments and recommend how to resolve the concern.

We are not the Encyclopedia Britannica.   I think Russ' suggestion makes =
sense.


From agmalis@gmail.com  Fri Jan  3 07:36:04 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87191ADFD4 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 07:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZ9Hl2zjcWyZ for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 07:36:02 -0800 (PST)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id C0E481ADEBF for <ietf@ietf.org>; Fri,  3 Jan 2014 07:36:02 -0800 (PST)
Received: by mail-qc0-f176.google.com with SMTP id i8so14990752qcq.35 for <ietf@ietf.org>; Fri, 03 Jan 2014 07:35:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/hFS2WXglYusJoPd+1odUAfN33mjbv71ZabzhwEwFD4=; b=r0YDNgUT8N1fiWwk4w2iM/6ENFn9sy/QfGe2ZEaQFyVucdSPs15+1uMuFIg6vcBUR7 7fReUtVZILEnhWC50wrg4/cbaidB/cnFPSBLCPOwrg9Jb9FzH7D4vPTY87G0BtJo7ujX GPPh1i59DUT34AT48XfcQDRahl2KuU3zRFxFnP7q3DJEmxdVsiAMTysgigmAGZ1j9Oyq RtG1LMkzGfmFq9CzaBE1wFTS7sFGYIY/btwhYx32+SZafUaYNr8Pn3sWBL3hta2EqJfX QiVbIeib0BJ+L7lhxb0ZJHYktsILvxOvd+iAP9lSuRUjDDQseNKREzvKHtkpgIpKFISk bK6A==
X-Received: by 10.224.12.5 with SMTP id v5mr149192027qav.4.1388763355372; Fri, 03 Jan 2014 07:35:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Fri, 3 Jan 2014 07:35:35 -0800 (PST)
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Fri, 3 Jan 2014 10:35:35 -0500
Message-ID: <CAA=duU1YaVHqcwJa0i72o4J4ZTZ5_9JwTSfyTc8bZmkR5rAhSQ@mail.gmail.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 15:36:05 -0000

The document is in pretty good shape and looks pretty ready for
publication. Note that in the "NOTE" at the top of section 3, at the
beginning of the fourth line, the word "authors" is missing.

Also, the draft uses the older convention of "Network Working Group"
at the top of the boilerplate. If there was ever a draft that should
use the newer convention of "Internet Engineering Task Force (IETF)"
instead, this one probably qualifies.

Cheers,
Andy

On Fri, Jan 3, 2014 at 10:14 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Creating an IETF Working Group Draft'
>   <draft-crocker-id-adoption-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 2014-01-31. 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 productive output of an IETF working group is documents, as
>    mandated by the working group's charter.  When a working group is
>    ready to develop a particular document, the most common mechanism is
>    for it to "adopt" an existing document as a starting point.  The
>    document that a working group adopts and then develops further is
>    based on initial input at varying levels of maturity.  An initial
>    working group draft might be a document already in wide use, or it
>    might be a blank sheet, wholly created by the working group, or it
>    might represent any level of maturity in between.  This document
>    discusses how a working group typically handles the formal documents
>    that it targets for publication.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-crocker-id-adoption/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-crocker-id-adoption/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>

From erosen@cisco.com  Fri Jan  3 08:34:31 2014
Return-Path: <erosen@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 104731ADFDC for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.339
X-Spam-Level: 
X-Spam-Status: No, score=-7.339 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NLwPukVAKUdT for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:34:29 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 527FE1ADF8A for <ietf@ietf.org>; Fri,  3 Jan 2014 08:34:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2340; q=dns/txt; s=iport; t=1388766862; x=1389976462; h=from:to:cc:subject:in-reply-to:reply-to:date:message-id; bh=xwW0tzklFvq4u6QKxkGIAWmSlmIoP4oPN/dCsaKWzVk=; b=TN/flINrIRzKECk2lLwfHXREjzaA3ebcT6mnz2p5rUoN2I6+lDrLWkbb dMYQz7/A1qayN3lV1Rqod7nori1yiA+6K0fdJvy/XQaZGESConFCobhCE wAaccqNrY7Q+1HvklpSqXAnwolFC6Pu/aH8jfM48oiCGiP2bDUyGsWTUI 0=;
X-IronPort-AV: E=Sophos;i="4.95,598,1384300800"; d="scan'208";a="10362972"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-4.cisco.com with ESMTP; 03 Jan 2014 16:34:22 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s03GYLX6000575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jan 2014 16:34:21 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id s03GYJf7024106; Fri, 3 Jan 2014 11:34:19 -0500
From: Eric Rosen <erosen@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-reply-to: Your message of Thu, 02 Jan 2014 19:46:12 +0000. <52C5C204.60708@cs.tcd.ie>
Date: Fri, 03 Jan 2014 11:34:19 -0500
Message-ID: <24105.1388766859@erosen-linux>
Cc: John C Klensin <john-ietf@jck.com>, erosen@cisco.com, IETF Discussion <ietf@ietf.org>, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: erosen@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 16:34:31 -0000

Stewart> The -03 text is a significant improvement, but I still fear the
Stewart> impact of single issue technical politics on the output of our
Stewart> document stream.

Let's face it, the draft is nothing but a political manifesto, and the IETF
has no business even considering it.  It is also clear from this discussion
that there is no consensus, even rough consensus, in favor. 

Note the tone taken by proponents of the draft.  It has been suggested that
critics are at best wasting everyone's time, and at worst unethical.  When
it is pointed out that one cannot determine from the draft what the actual
impact on IETF process is, the proponents yell "there's no time to consider
the details, Rome is burning, we can't afford the time to listen to people
who disagree with us".  The claim that we have to act immediately, even
though we don't know what we need to do, is particularly ridiculous.  This
is all typical political discourse: ratchet up the volume of the sound
bites, claim the support of a "silent majority", and yell that the
dissenters are bad people who shouldn't be listened to.  This should not be
considered to be an acceptable mode of discourse in the IETF.

StephenF> But Ted also pointed out that there is already plenty of
StephenF> ammunition for an overly zealous AD to use to have that bad
StephenF> effect. And you and others are I think also saying that that did
StephenF> happen in the past.

Routinely.  Some past ADs are absolutely notorious in this regard, some from
an excess of zeal, and some from a strong conviction that they just know
what is best for everyone else.

StephenF> If so, then this BCP will have no impact in that respect - what is
StephenF> already possible will continue to be possible regardless of what
StephenF> happens with this draft.

Well, here's a particularly egregious example of poor reasoning:  "since it
is already possible for the Security ADs to abuse their power, giving them
more tools and more excuses for doing so will have no effect."  An obvious
non-sequitur, but a good sound bite.

It is true that the ADs already have plenty of opportunities to replace WG
consensus with their personal prejudices.  Let's not give them any more.
This draft isn't what makes abuses possible, it just makes them a lot more
likely.












From ajs@anvilwalrusden.com  Fri Jan  3 08:49:04 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87D81ADFDF for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.559
X-Spam-Level: **
X-Spam-Status: No, score=2.559 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szyx0hUiy9RX for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:49:03 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 9D14B1ADEB7 for <ietf@ietf.org>; Fri,  3 Jan 2014 08:49:03 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id C12828A031 for <ietf@ietf.org>; Fri,  3 Jan 2014 16:48:55 +0000 (UTC)
Date: Fri, 3 Jan 2014 11:48:53 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: review of draft-crocker-id-adoption-05
Message-ID: <20140103164853.GE8668@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 16:49:05 -0000

Dear colleagues,

I have read draft-crocker-id-adoption-05.

I'm not opposed to publication, though I confess I'm a little uneasy
with it.  This is yet another process document that, no matter how
much the text protests otherwise, will probably be used as a club in
some future contentious WG discussion to try to beat opponents into
submission.  If we want to publish this sort of thing, however, this
document is probably fine.  I have one small issue.

In section 5.2, there is this:

   a single, strong specification.  The detailed discussions to merge
   are better held in a design team than amidst the dynamics of an open
   working group mailing list.

I think it would be better to alter that to "â€¦to merge are often
better heldâ€¦".  I agree that for practical purposes things don't
always need to be thrashed out on the general list, but sometimes the
wider debate (or the very small active population of a WG) means that
a design team is a bad choice, and I don't want this text to give
people an excuse to try to take things "into the back room" when they
shouldn't.

I'll send some nits to the author directly.

Best regards,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From Ted.Lemon@nominum.com  Fri Jan  3 08:49:19 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF99E1AE009 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRpWIhl1BgBl for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:49:17 -0800 (PST)
Received: from exprod7og126.obsmtp.com (exprod7og126.obsmtp.com [64.18.2.206]) by ietfa.amsl.com (Postfix) with ESMTP id A06851AE008 for <ietf@ietf.org>; Fri,  3 Jan 2014 08:49:11 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob126.postini.com ([64.18.6.12]) with SMTP ID DSNKUsbqAKFZUP0lD2JcQZc1lIFZD2VXnA7i@postini.com; Fri, 03 Jan 2014 08:49:04 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1CC231B82E0 for <ietf@ietf.org>; Fri,  3 Jan 2014 08:49:04 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DE4A719005C; Fri,  3 Jan 2014 08:49:03 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 3 Jan 2014 08:49:03 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <24105.1388766859@erosen-linux>
Date: Fri, 3 Jan 2014 11:48:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <24E8B73F-C421-4B9D-881D-766C2415C61B@nominum.com>
References: <24105.1388766859@erosen-linux>
To: <erosen@cisco.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, Stewart Bryant <stbryant@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 16:49:19 -0000

On Jan 3, 2014, at 11:34 AM, Eric Rosen <erosen@cisco.com> wrote:
> Well, here's a particularly egregious example of poor reasoning:  =
"since it
> is already possible for the Security ADs to abuse their power, giving =
them
> more tools and more excuses for doing so will have no effect."  An =
obvious
> non-sequitur, but a good sound bite.

The point of the IETF stating a position on this is not to give ADs =
another thing they can hassle document authors about.   It is to =
formally encourage document authors and working groups to think about =
the issue.

> Note the tone taken by proponents of the draft.  It has been suggested =
that
> critics are at best wasting everyone's time, and at worst unethical.

I don't recall seeing anyone suggesting that.   Maybe I missed =
something=97there have been a lot of messages.  I do see a flaming =
diatribe from you, though.   If you are finding others' rhetoric =
uncomfortable, it might be worth listening to your own with a more =
critical ear!   :}


From scott.brim@gmail.com  Fri Jan  3 08:53:23 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8615D1ADFD7 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIpeWtE0QHfw for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 08:53:21 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7761ADF8A for <ietf@ietf.org>; Fri,  3 Jan 2014 08:53:20 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id vb8so15718303obc.21 for <ietf@ietf.org>; Fri, 03 Jan 2014 08:53:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=aQXNh4OibVIlJ6j29q/pq0P5jtOvOp+vfyhlKzcSXvs=; b=hvJ3r60J4ZEwk6bkin28Xw6vh05pGjTIYjNbs5G06S8IEY37yYoowEVuxwzAEZA7OP +CaHS7kip5lNmBRZ4m1eT93rY1lZe3rXHBKWd6kD95tmxTGfureEg/TMrmd9JsdzpjoY MILjaWXpzIumr6vEq3JCfj/zKeIBGYBMTwu3ffvT9oxi/3XRJmXpPwsA+U2P0wKg+J6g yKbQVJtSY4zaR9RJ+RDYQQQpdot15I3asU2uDP28qWUxJ4qFcwLYHSIzMgnaXpoccgzv fhiQ368pHb9gQYuLaV8dq0oKdU46VPL4Cwkky2eT2DZaVlihf74uoEb4KWiO4PFu/RDc 6rWA==
X-Received: by 10.60.233.9 with SMTP id ts9mr1018048oec.65.1388767993638; Fri, 03 Jan 2014 08:53:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 3 Jan 2014 08:52:53 -0800 (PST)
In-Reply-To: <24105.1388766859@erosen-linux>
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 3 Jan 2014 11:52:53 -0500
Message-ID: <CAPv4CP92NFooWCt0XyJPPOyLGxvx7REBh4hU6zNrSYcYjWHEiA@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: erosen@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, Stewart Bryant <stbryant@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 16:53:23 -0000

On Fri, Jan 3, 2014 at 11:34 AM, Eric Rosen <erosen@cisco.com> wrote:
> Let's face it, the draft is nothing but a political manifesto, and the IETF
> has no business even considering it.

If so, what politics? If you look closely at the draft and not so much
at what people are assuming about it, it is straightforward: pervasive
monitoring, for whatever cause, is indistinguishable from an attack;
the ease of such attacks is increasing; the IETF is behind the curve;
so we're going to do more to make it possible to resist such attacks.

Is there something in that that you disagree with?

> It is also clear from this discussion
> that there is no consensus, even rough consensus, in favor.

The problem with consensus is that people thought this draft either
should recommend specific actions, or was recommending specific
actions. Either would be wrong - the specific actions need to be
considered in specific contexts. I hope that has been made clear by
discussion.

> Note the tone taken by proponents of the draft.  It has been suggested that
> critics are at best wasting everyone's time, and at worst unethical.

There's a great deal of noise and confusion. Ignore statements that
you know are just wrong unless they come from those behind the draft,
as opposed to those claiming to represent their views (like me) or
those just commenting on it.

> When
> it is pointed out that one cannot determine from the draft what the actual
> impact on IETF process is, the proponents yell "there's no time to consider
> the details, Rome is burning, we can't afford the time to listen to people
> who disagree with us".  The claim that we have to act immediately, even
> though we don't know what we need to do, is particularly ridiculous.  This
> is all typical political discourse: ratchet up the volume of the sound
> bites, claim the support of a "silent majority", and yell that the
> dissenters are bad people who shouldn't be listened to.  This should not be
> considered to be an acceptable mode of discourse in the IETF.

I didn't see any of that from people who are actually responsible for the draft.

> Well, here's a particularly egregious example of poor reasoning:  "since it
> is already possible for the Security ADs to abuse their power, giving them
> more tools and more excuses for doing so will have no effect."  An obvious
> non-sequitur, but a good sound bite.

Yes, that was too casual.

Personally, I don't think making a general statement about pervasive
monitoring is going to give ADs any more power than they have now.
Think about when Jeff Schiller was AD and how he used the power of the
security audit (aside: I thought it was a good thing), and think about
how the flow is now. No powers have been taken away and yet somehow we
have a balance, and our protocols are better for the security
considerations. In terms of drafts you might produce, this is another
(major) facet to be considered, it's not granting a new power.

Scott

From housley@vigilsec.com  Fri Jan  3 09:00:32 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172661ADFF7; Fri,  3 Jan 2014 09:00:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9xcLLSWywrId; Fri,  3 Jan 2014 09:00:30 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAC41ADFDF; Fri,  3 Jan 2014 09:00:30 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id EF0929A4241; Fri,  3 Jan 2014 12:00:12 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id 3Q38S8zLi0mS; Fri,  3 Jan 2014 11:59:51 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DE1249A4243; Fri,  3 Jan 2014 11:59:51 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART review of draft-ietf-siprec-architecture-11
Date: Fri, 3 Jan 2014 11:59:40 -0500
Message-Id: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
To: draft-ietf-siprec-architecture.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:00:32 -0000

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

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

Document: draft-ietf-siprec-architecture-11
Reviewer: Russ Housley
Review Date: 2014-01-03
IETF LC End Date: 2013-10-01
IESG Telechat date: 2014-01-09

Summary:  

Thank you for addressing the issues raised in my previous review.
This document is ready for publication as an Informational RFC.

Major Concerns:  None.

Minor Concerns:  None.

Editorial Comments:

The changes to Section 3.2.4 to resolve my earlier comment have
introduced a clarity problem.  I suggest a minor rewording to fix it.

3.2.4.  Media Stream Mixing

   In a basic session involving only audio there are typically two
   audio/RTP streams between the two UAs involved transporting media in
   each direction.  When recording this media, the two streams may be
   mixed or not mixed at the SRC before being transmitted to the SRS.
   In the case when they are not mixed, two separate streams are sent
   to the SRS.  In the mixed case, a single mixed media stream is sent
   to the SRS.  However, in the case when the media streams are not
   mixed, the SDP offer sent to the SRS must describe two separate
   media streams.


From adrian@olddog.co.uk  Fri Jan  3 09:24:06 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 957751AE00D for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:24:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZaoqexbWMEVr for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:24:04 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 24E071AE009 for <ietf@ietf.org>; Fri,  3 Jan 2014 09:24:03 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s03HNrt1032567; Fri, 3 Jan 2014 17:23:53 GMT
Received: from 950129200 (16.17.90.92.rev.sfr.net [92.90.17.16]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s03HNn4N032534 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Jan 2014 17:23:51 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Andrew Sullivan'" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
References: <20140103164853.GE8668@mx1.yitter.info>
In-Reply-To: <20140103164853.GE8668@mx1.yitter.info>
Subject: RE: review of draft-crocker-id-adoption-05
Date: Fri, 3 Jan 2014 17:23:51 -0000
Message-ID: <020a01cf08a8$9354a640$b9fdf2c0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCUAZDSD44Na772LpGHbv0v6lXkJZzpSzHA
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:24:06 -0000

Hello Andrew,

[The aside]=20

>  This is yet another process document that, no matter how
> much the text protests otherwise, will probably be used as a club in
> some future contentious WG discussion to try to beat opponents into
> submission. =20

At the moment we don't seem to be able to move for fear of clubbing WGs =
at some future unspecified time.
And at the same time we have WG chairs saying "please give us a bit of =
general guidance on some topics".=20
So we might handle this by putting it on a wiki instead, but I think the =
community like to be able to read about "stuff". And our mode of =
publication (to date) has been the RFC not the wiki.

I'm in general in favor of encouraging people to have some backbone if =
they feel they are being clubbed, and not to cry out that they might be =
clubbed in the future.

I think I would have a different view if the I-D was proposing rules and =
regulations without fully examining the consequences.

[And the technical bit]

> In section 5.2, there is this:
>=20
>    a single, strong specification.  The detailed discussions to merge
>    are better held in a design team than amidst the dynamics of an =
open
>    working group mailing list.
>=20
> I think it would be better to alter that to "=E2=80=A6to merge are =
often
> better held=E2=80=A6".=20

That is a good suggestion, IMHO.

Thanks,
Adrian


From housley@vigilsec.com  Fri Jan  3 09:31:38 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401771ADFD7; Fri,  3 Jan 2014 09:31:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99ydKST2lQl5; Fri,  3 Jan 2014 09:31:36 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 7B5FB1ADBD2; Fri,  3 Jan 2014 09:31:36 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 51F2A9A423D; Fri,  3 Jan 2014 12:31:19 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id ORVn7GDBu3Km; Fri,  3 Jan 2014 12:30:58 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 192259A4246; Fri,  3 Jan 2014 12:30:57 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
Date: Fri, 3 Jan 2014 12:30:45 -0500
Message-Id: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
To: draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:31:38 -0000

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

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

Document: draft-ietf-mpls-tp-p2mp-framework-05
Reviewer: Russ Housley
Review Date: 2014-01-02
IETF LC End Date: 2014-01-16
IESG Telechat date: Unknown

Summary:  Ready for publication.


Question:

Should this document be an update to the MPLS-TP Framework (RFC 5921)?
I am not sure.  RFC 5921 does make it clear that it covers only point-
to-point transport paths.  The answer may be further complicated by
the fact that RFC 5921 is joint work with the ITU-T.


Major Concerns:  None.


Minor Concerns:  None.


Other Comments:

In the first sentence of Section 1, please define MPLS-TP as follows:
OLD:
   The Multiprotocol Label Switching Transport Profile is the ...
NEW:
   The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...

Please add TE-LSP to the terms defined in Section 1.2.

In Section 5.1, I cannot understand this sentence:
>
>  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>  interactions.
>
I think that the references are getting in the way.  I think the
message is: "the definitions of P2MP and GMPLS recovery do not
explicitly cover their interactions."  If I am correct, then some
commas need to be removed.

The phrase "MPLS Transport Profile" appears many places, and it would
be easier if they were replaces with "MPLS-TP" for consistency.


From michael.scharf@alcatel-lucent.com  Fri Jan  3 09:33:01 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7AF91AE013 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LoeweKy7pAZJ for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:32:59 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 88BC71ADFD4 for <ietf@ietf.org>; Fri,  3 Jan 2014 09:32:59 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s03HWo6T014313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Fri, 3 Jan 2014 11:32:51 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s03HWo7r011640 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Fri, 3 Jan 2014 18:32:50 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.70]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Fri, 3 Jan 2014 18:32:50 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Topic: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Index: AQHPCJaajVeEAzcLjk6SIrRU7XqAIJpzKCC6
Date: Fri, 3 Jan 2014 17:32:49 +0000
Message-ID: <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [155.132.188.47]
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:33:02 -0000

Hi,=0A=
=0A=
Two small comments, based on observations in TCPM. Obviously, this draft ca=
nnot handle all WG specifics, but maybe my two remarks also apply to other =
WGs...=0A=
=0A=
First, the document could perhaps mention that during the adoption of a dra=
ft there can be a discussion about the planned status (e.g., STD vs. EXP), =
even if the status can change later in the process. In TCPM, this is almost=
 always the case, and therefore the chairs have to consider the planned sta=
tus as one question when creating/adopting a WG draft.=0A=
=0A=
Second, I am not sure if the following statement in Section 2.2 could be de=
tailed a bit:=0A=
=0A=
      *  Is there strong working group support for working on the draft?=0A=
=0A=
Actually, in TCPM, the "working group support for working on the draft" is =
often not the most important criteria for adoption. The key one is the more=
 specific question whether there indeed "working group energy for contribut=
ing and reviewing". For instance, sometimes, we have the following situatio=
n: The community really likes a new, interesting idea, and the WG therefore=
 really wants that "somebody" works out all the nasty protocol details that=
 a full spec would require. This is typically left to the authors of the in=
dividual document proposing this idea. Yet, since TCPM deals with a core In=
ternet protocol, having a WG document also implies that the WG should indee=
d verify this spec, e.g., in all the corner cases that can occur in a compl=
ex protocol. And, surprise, surprise, finding volunteers for that is often =
more difficult than finding people that really like an idea and want the WG=
 to work on it... As a result, the chairs have to think about the completio=
n of any new WG document quite a bit in advance...=0A=
=0A=
If this effect should exist in other WGs as well, maybe one could add some =
additional explanation regarding the "willingness to contribute and review"=
 to a new WG document. It could also relate to Section 4 as one aspect of d=
ocument "maturity".=0A=
=0A=
Thanks=0A=
=0A=
Michael=0A=
=0A=
________________________________________=0A=
Von: IETF-Announce [ietf-announce-bounces@ietf.org]&quot; im Auftrag von &q=
uot;The IESG [iesg-secretary@ietf.org]=0A=
Gesendet: Freitag, 3. Januar 2014 16:14=0A=
An: IETF-Announce=0A=
Betreff: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Wo=
rking Group Draft) to Informational RFC=0A=
=0A=
The IESG has received a request from an individual submitter to consider=0A=
the following document:=0A=
- 'Creating an IETF Working Group Draft'=0A=
  <draft-crocker-id-adoption-05.txt> as Informational RFC=0A=
=0A=
The IESG plans to make a decision in the next few weeks, and solicits=0A=
final comments on this action. Please send substantive comments to the=0A=
ietf@ietf.org mailing lists by 2014-01-31. Exceptionally, comments may be=
=0A=
sent to iesg@ietf.org instead. In either case, please retain the=0A=
beginning of the Subject line to allow automated sorting.=0A=
=0A=
Abstract=0A=
=0A=
=0A=
   The productive output of an IETF working group is documents, as=0A=
   mandated by the working group's charter.  When a working group is=0A=
   ready to develop a particular document, the most common mechanism is=0A=
   for it to "adopt" an existing document as a starting point.  The=0A=
   document that a working group adopts and then develops further is=0A=
   based on initial input at varying levels of maturity.  An initial=0A=
   working group draft might be a document already in wide use, or it=0A=
   might be a blank sheet, wholly created by the working group, or it=0A=
   might represent any level of maturity in between.  This document=0A=
   discusses how a working group typically handles the formal documents=0A=
   that it targets for publication.=0A=
=0A=
=0A=
=0A=
=0A=
The file can be obtained via=0A=
http://datatracker.ietf.org/doc/draft-crocker-id-adoption/=0A=
=0A=
IESG discussion can be tracked via=0A=
http://datatracker.ietf.org/doc/draft-crocker-id-adoption/ballot/=0A=
=0A=
=0A=
No IPR declarations have been submitted directly on this I-D.=0A=
=0A=
=0A=

From erosen@cisco.com  Fri Jan  3 09:34:08 2014
Return-Path: <erosen@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715871AE016 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:34:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AjvRGRN4FKWi for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:34:07 -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 15C2B1AE013 for <ietf@ietf.org>; Fri,  3 Jan 2014 09:34:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=702; q=dns/txt; s=iport; t=1388770440; x=1389980040; h=from:to:cc:subject:in-reply-to:reply-to:date:message-id; bh=eOIUioXL/uKRoyEz/ZPhan78GFgvp//4mxtz8mgdxNw=; b=aHkRtTZWTOSEtSbJNDw9QIfwy2vOiKroQ8O8GSyQ6dOn/fVyk/V1zoKO S7wT86BdlB5wFOqVd3StXgk+MouclmaS0Fi6ah2lHLC1kiPokX8g54Our YPqyP+egIAMUDvUeb0+oGat6+zvWcrzrktbKt3nnSd/Qb2M8P9EjckBYh 4=;
X-IronPort-AV: E=Sophos;i="4.95,598,1384300800"; d="scan'208";a="295080222"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-2.cisco.com with ESMTP; 03 Jan 2014 17:34:00 +0000
Received: from erosen-linux.cisco.com (erosen-linux.cisco.com [161.44.70.34]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s03HXxGn031905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jan 2014 17:33:59 GMT
Received: from erosen-linux (localhost.localdomain [127.0.0.1]) by erosen-linux.cisco.com (8.13.8/8.13.8) with ESMTP id s03HXwWa026735; Fri, 3 Jan 2014 12:33:58 -0500
From: Eric Rosen <erosen@cisco.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-reply-to: Your message of Fri, 03 Jan 2014 11:52:53 -0500. <CAPv4CP92NFooWCt0XyJPPOyLGxvx7REBh4hU6zNrSYcYjWHEiA@mail.gmail.com>
Date: Fri, 03 Jan 2014 12:33:58 -0500
Message-ID: <26734.1388770438@erosen-linux>
Cc: John C Klensin <john-ietf@jck.com>, erosen@cisco.com, Stewart Bryant <stbryant@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: erosen@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:34:08 -0000

Scott> Is there something in that that you disagree with?

The issue isn't whether I agree or disagree with it, it's whether the IETF
should be making this foray into politics.  

Scott> Ignore statements that you know are just wrong unless they come from
Scott> those behind the draft,

That would only make sense if the draft were presented as an
individual-stream draft that represents only the authors' opinions, but does
not impact IETF process.

Ted> The point of the IETF stating a position on this is not to give ADs
Ted> another thing they can hassle document authors about.

One has to look at the likely impact of the draft, not merely at the
intentions of the authors.  













From chair@ietf.org  Fri Jan  3 09:36:58 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C141ADFEF; Fri,  3 Jan 2014 09:36:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JJLByT5_FwXs; Fri,  3 Jan 2014 09:36:57 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id EBC5D1AE013; Fri,  3 Jan 2014 09:36:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 092D4A6186; Fri,  3 Jan 2014 09:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rxTsYRfw9nQ5; Fri,  3 Jan 2014 09:35:27 -0800 (PST)
Received: from [172.20.10.5] (unknown [90.84.144.35]) by c9a.amsl.com (Postfix) with ESMTPSA id 03C9FA6180; Fri,  3 Jan 2014 09:35:26 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: IANA blog article
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Fri, 3 Jan 2014 18:36:48 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Discussion" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:36:59 -0000

In this article I wanted to highlight an important but often hidden part =
in the IETF ecosystem: Internet Assigned Numbers Authority (IANA).  What =
is IANA, how does it work, how is it related to the IETF, and how has it =
evolved over time? How will it evolve in the future, and how can you =
participate in the discussion?

http://www.ietf.org/blog/2014/01/iana/

Jari


From scott.brim@gmail.com  Fri Jan  3 09:42:54 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03EE41ADFE6 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cg4xstTFXOuD for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 09:42:52 -0800 (PST)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id A4E581ADFEF for <ietf@ietf.org>; Fri,  3 Jan 2014 09:42:52 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id m1so16378394oag.40 for <ietf@ietf.org>; Fri, 03 Jan 2014 09:42:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HLpa6teNQz0oOXcQ2gRctLWYOBiZvUNcv4LDx28c9Jo=; b=vj7RUF2n4IlieHm17T+C8fFTnzOf4eltK5UUccm59oHyYcFDAvjAuJ1oW7x0yZdye9 vCYCE3MVJ9n/i8WpRoh3bimRhwAdDIFSfBTulQfMb2ZWgAfeAVRVedVdd2uzCpr0Hjiy kY4pvEzlobRUcw8ih7CboXPbK8vwq8PeNZQIw24jpTYEZxjuY1YPbfFWcqMDNVy1A5q4 zzEIXVhmwFcKEOOh6mOntKGPrMYQOV1pRN1Az1aRN0m5oz95OhGsPtDD2t+hqBL476u5 UjvPkai/8AjMUBiUo0rd6aE5SP2DopLHG+GvLRkXqdxWYwSP6i4kiseo0co5QMKFnDFP DFBg==
X-Received: by 10.60.50.202 with SMTP id e10mr60403777oeo.39.1388770965173; Fri, 03 Jan 2014 09:42:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 3 Jan 2014 09:42:25 -0800 (PST)
In-Reply-To: <26734.1388770438@erosen-linux>
References: <CAPv4CP92NFooWCt0XyJPPOyLGxvx7REBh4hU6zNrSYcYjWHEiA@mail.gmail.com> <26734.1388770438@erosen-linux>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 3 Jan 2014 12:42:25 -0500
Message-ID: <CAPv4CP_ypmAN7iqaLkbpvCvxPbt7nn-RM=yu_Qe2cH9Ef4jhdQ@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: erosen@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, Stewart Bryant <stbryant@cisco.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 17:42:54 -0000

On Fri, Jan 3, 2014 at 12:33 PM, Eric Rosen <erosen@cisco.com> wrote:
>
> Scott> Is there something in that that you disagree with?
>
> The issue isn't whether I agree or disagree with it, it's whether the IETF
> should be making this foray into politics.

What politics? Do you agree that pervasive monitoring can be an
attack, and thus even "good" pervasive monitoring is indistinguishable
from an attack? Do you agree that we should make it possible to resist
attacks? Those seem to be straightforward statements.

> Scott> Ignore statements that you know are just wrong unless they come from
> Scott> those behind the draft,
>
> That would only make sense if the draft were presented as an
> individual-stream draft that represents only the authors' opinions, but does
> not impact IETF process.
>
> Ted> The point of the IETF stating a position on this is not to give ADs
> Ted> another thing they can hassle document authors about.
>
> One has to look at the likely impact of the draft, not merely at the
> intentions of the authors.

I meant: look for clarity from those who might actually provide it. I
believe you're saying that people's responses to the draft as it
stands show how they are going to respond to it if it's published --
ie the problem isn't the draft so much as its interpretation ... ?
Yes, that's pretty clearly a problem so far. Perhaps if it were
simplified way down, people couldn't read into it so much.

Scott

From derhoermi@gmx.net  Fri Jan  3 10:36:34 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2E331ACC82 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 10:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RB6j0CMoix1C for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 10:36:32 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 2728A1ADFB1 for <ietf@ietf.org>; Fri,  3 Jan 2014 10:36:32 -0800 (PST)
Received: from netb.Speedport_W_700V ([84.180.229.73]) by mail.gmx.com (mrgmx102) with ESMTPA (Nemesis) id 0Lz0aC-1VLoal404O-014GXP for <ietf@ietf.org>; Fri, 03 Jan 2014 19:36:24 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Fri, 03 Jan 2014 19:36:27 +0100
Message-ID: <97vdc91lkpeo7u3vg644oi0dpk8pc744vd@hive.bjoern.hoehrmann.de>
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux> <CAPv4CP92NFooWCt0XyJPPOyLGxvx7REBh4hU6zNrSYcYjWHEiA@mail.gmail.com>
In-Reply-To: <CAPv4CP92NFooWCt0XyJPPOyLGxvx7REBh4hU6zNrSYcYjWHEiA@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-Provags-ID: V03:K0:1HxxB7nXCJCsiEorkn31/kRguJU0LBE0gX0KMyHn9H3W93jSnhu NBNhfQW3EGLDRjcJxNl89XCqnW/KZV6ZqemUx1PGlBzJ10NS2cN6ZBuFoKN+oCUPyDxUQJ6 TfUkLbeT/Bv6BQyMSh8+wp0rINvXYoJ3XjKUvy2GhBSrNJlQclyRtkQb94OaQKeNFzo/LDo NryPe+kOcFhTDw7PtEr3Q==
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 18:36:34 -0000

* Scott Brim wrote:
>If so, what politics? If you look closely at the draft and not so much
>at what people are assuming about it, it is straightforward: pervasive
>monitoring, for whatever cause, is indistinguishable from an attack;
>the ease of such attacks is increasing; the IETF is behind the curve;
>so we're going to do more to make it possible to resist such attacks.
>
>Is there something in that that you disagree with?

I think pervasive monitoring is possible without taking any action that
is indistinguishable from an attack.

If the draft defines "pervasive monitoring" or "attack" so there cannot
be "pervasive monitoring" without taking any action that is indisting-
uishable from an "attack", ...
-- 
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 TurnerS@ieca.com  Fri Jan  3 10:52:22 2014
Return-Path: <TurnerS@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B8A1ADFC4 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 10:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9wkMHhHuo8lO for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 10:52:20 -0800 (PST)
Received: from gateway15.websitewelcome.com (gateway15.websitewelcome.com [67.18.70.8]) by ietfa.amsl.com (Postfix) with ESMTP id 9204F1ADFC3 for <ietf@ietf.org>; Fri,  3 Jan 2014 10:52:20 -0800 (PST)
Received: by gateway15.websitewelcome.com (Postfix, from userid 5007) id 326C05D63A12D; Fri,  3 Jan 2014 12:52:13 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway15.websitewelcome.com (Postfix) with ESMTP id 124825D63A09B for <ietf@ietf.org>; Fri,  3 Jan 2014 12:52:13 -0600 (CST)
Received: from [173.73.130.192] (port=61200 helo=[192.168.1.4]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <TurnerS@ieca.com>) id 1Vz9qu-0007gW-4M; Fri, 03 Jan 2014 12:52:12 -0600
Content-Type: multipart/signed; boundary="Apple-Mail=_723E184C-482D-4C50-BE18-53D9EFB01A3B"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: RETRACTION: Last Call: Progressing RFCs 5343, 5590, 5991, and 6353 to Internet Standard
From: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <8761q1aqa2.fsf@deeperthought.bsdly.net>
Date: Fri, 3 Jan 2014 13:52:08 -0500
Message-Id: <78545669-D27D-487C-B3AE-4011C6955555@ieca.com>
References: <20140103180641.30180.68094.idtracker@ietfa.amsl.com> <8761q1aqa2.fsf@deeperthought.bsdly.net>
To: "Peter N. M. Hansteen" <peter@bsdly.net>
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 173.73.130.192
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([192.168.1.4]) [173.73.130.192]:61200
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 18
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Cc: The IESG <iesg@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, isms@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 18:52:22 -0000

--Apple-Mail=_723E184C-482D-4C50-BE18-53D9EFB01A3B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I requested this retraction because I made a fat finger mistake and =
included 5991 instead of 5591 in the last call (David Harrington=92s =
keen eye caught this).  I tired to correct the mistake and get a revised =
LC issued, but I could change everything in the request/write-up except =
the name of the document that gets points to from the LC: =
status-change-5343-5590-5991-6353-to-internet-standard-01.  I thought =
that might add confusion so after consultation with the secretariat I =
asked for them to retract it, I put notes in the datatracker =
(http://datatracker.ietf.org/doc/status-change-5343-5590-5991-6353-to-inte=
rnet-standard/history/) for all to see, and am working on a new and =
corrected LC.

Apologies for any confusion.

spt


On Jan 03, 2014, at 13:12, Peter N. M. Hansteen <peter@bsdly.net> wrote:

> This begs the question:=20
>=20
> Do the withdrawal requests contain any publishable specifics as to why
> these status changes should not go forward?
>=20
> Yours,
> Peter N. M. Hansteen
>=20
> IETF Secretariat <ietf-secretariat@ietf.org> writes:
>=20
>> The following Last Call has been withdrawn by request of the area =
director:
>>=20
>> The IESG has received a request from multiple participants to make
>> the following status changes:
>>=20
>> - RFC5343 from Draft Standard to Internet Standard
>>    (Simple Network Management Protocol (SNMP) Context EngineID
>> Discovery)
>>=20
>> - RFC5991 from Proposed Standard to Internet Standard
>>    (Teredo Security Updates)
>>=20
>> - RFC5590 from Draft Standard to Internet Standard
>>    (Transport Subsystem for the Simple Network Management Protocol
>> (SNMP))
>>=20
>> - RFC6353 from Draft Standard to Internet Standard
>>    (Transport Layer Security (TLS) Transport Model for the Simple
>> Network Management Protocol (SNMP))
>>=20
>=20
> --=20
> Peter N. M. Hansteen, member of the first RFC 1149 implementation team
> http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
> "Remember to set the evil bit on all malicious network traffic"
> delilah spamd[29949]: 85.152.224.147: disconnected after 42673 =
seconds.


--Apple-Mail=_723E184C-482D-4C50-BE18-53D9EFB01A3B
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEgDCCBHww
ggJkoAMCAQICCQCdWMxKNutUeTANBgkqhkiG9w0BAQsFADAiMQswCQYDVQQGEwJVUzETMBEGA1UE
ChMKSUVDQSwgSW5jLjAeFw0xMzA0MDMxNDUxMThaFw0xNDA0MDMxNDUxMThaMDgxCzAJBgNVBAYT
AlVTMRMwEQYDVQQKEwpJRUNBLCBJbmMuMRQwEgYDVQQDEwtTZWFuIFR1cm5lcjCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAOpCGCRptT1m+bIpLTmbahZLZ0Qe4X99f8SgTQ7QISvUfpmn
tfOD1oA1AttXlOULEERYubzvDnUTXvstFomQx0XTA67IaV+mw9ODRtG1hPN/erdKX6sU6rH4tsEb
ba3Drr/I0HT3YVvD3SjWtGXjF12XLvTP6+LfMIIDTCAPiEd9KPG23D7skVu/4BvvmdLFI96OARhg
wQ86M+lTIn83KRJlbbfAeIevbRx/rUB7D+uvMdWxOzR0KZJhd6dEeTXVwBXZG4rnQ4uFM+mRSiD4
rxDCyOuIuOzR07tnOyCRio6sRipOZvwQUWttdsgMEs6IxLdWsaTXcs1HjCsxrdedovMCAwEAAaOB
njCBmzAOBgNVHQ8BAf8EBAMCBeAwHwYDVR0jBBgwFoAUAHRsSeXJUmFxTVY4q2HJ8uHl+w0wGwYD
VR0RBBQwEoEQVHVybmVyU0BpZWNhLmNvbTAyBgNVHR8EKzApMCegJaAjhiFodHRwOi8vd3d3Lmll
Y2EuY29tL2NybHMvaWVjYS5jcmwwFwYDVR0gBBAwDjAMBgorBgEEAYHXAAAAMA0GCSqGSIb3DQEB
CwUAA4ICAQAimDYm77ppTi4vK6qJSUhyvCDMGb8mngiEXEYKxsfdHPWoDO7+06j7dAZ8sDD9/FtE
kiUMyoNGSUmKHR+tGperVnNiM/Zk6WwCJv8dYZwhGXNQeEGzeys/UkFv7CFX7uDSn8GQeB8sOAZ1
N1hxV/TvT8qXvcRxP5+aWTAGAq3TKtCQxZjuU74L3st2hZiOhJlhjhqz0K5FIwWzXUK9uwhZe1th
GUpDbRustVgmKN2Xa0pzwqI1VUO0jnWt24A4u59xo6DJQXzQVMhCx0xhpemuT9BrsBDTX8eJdI1i
Wv9wp3ivSrfHjKXp8y8OGD+usiG40HCjj0W9C+dH0VfbgrB6QOI4vA9+kTg4mANth1cxyxwPYOSJ
v0zi1qR0eDIGI//2v2/s6TmGuNqbnRa26Ldv5gGqS7xj32Fiaby6UOXs4+aAIWGZEOH+BXjozcvE
eGBwjU/VRQYu6itR28PaNhNVji4D5ITaGxWWiycqK1EUaFraWHtk7W100ROX69xTeFVZP86D2ymi
/aohl5Vb1vlYHdqlbgqjDRl9dPbTxVCXEHf+jkexcuwlLTvr7F+5DIN6c/EbCpRqQx3edy193L48
OGyRDh1/Wmzpew0VWWAWOSXGl/P9VzXf3Z6GPt7flN/V9iEJAa3Mo+w+eIdzJkHBWR+yJcqQcCRM
MSyishMwLDGCAjgwggI0AgEBMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTAJBgUrDgMCGgUAoIHfMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTE0MDEwMzE4NTIwOVowIwYJKoZIhvcNAQkEMRYEFGFg0dUSW63UJC0BoeP4wT4T
wsRQMD4GCSsGAQQBgjcQBDExMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTBABgsqhkiG9w0BCRACCzExoC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklF
Q0EsIEluYy4CCQCdWMxKNutUeTANBgkqhkiG9w0BAQEFAASCAQDEWTcPJxWVbeOX1tgPWQkBivSo
rokWTh/eabGbuE59YibzYjvnWl1EOHDjfOeRLR3Ud9CfM21+p2mZ3R38mNeZdiF13OLSKZYcGgFq
0EXuF1NcM05qKr4PgYIglINEqhDYu9N5x96u4F8yJ2rAiZOLjBx1TrfLmzjeBh8KMbn/D9yvTsrY
8OQd1b0MVzcVEhWNYaZZjpsLNkYSbFAKZt6yHiHG2siVp+7zBfxi5v4zPj6zBpN2td/6rc5fGfFT
+Mv9rxn8FETPn6BIyvsv6ZmzynzV8jaUcOTMUs04Ye5JidRzs1KEoMpjMcYvv4pTEkhMf3TNYZfc
Q5o0faBMPgcKAAAAAAAA

--Apple-Mail=_723E184C-482D-4C50-BE18-53D9EFB01A3B--

From melinda.shore@gmail.com  Fri Jan  3 11:00:34 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A3AB1ADFC2 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 11:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ri0dwzNltzMV for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 11:00:32 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 8369E1ADFC4 for <ietf@ietf.org>; Fri,  3 Jan 2014 11:00:32 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so15777337pdj.1 for <ietf@ietf.org>; Fri, 03 Jan 2014 11:00:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/kgm4C1msXHqCDoKid8bKg+Ux/S3EEaPcTa1G3zv3qo=; b=NT1OWe/PJJ4oeJ9WDydDol77PAnjVf86ynRtOVhEkQxD17MMj4mVUG5nbONdw4wZ9u xBqylN+rIhmrgRCiP882ylRi4RMpZEkVoPy7I28Cm6/uyMD9Tlhh8JBZyAsppRRvNUUB stx0lpi+dDSWer/FisgqCF+41neJeFaGHy4WXjvwYNt2oWJVZGbINP9CrxygDBYIghC7 yac9pQtk4L9fcMae1oQrTL66vl0o6WqEHmeiBlk0/ARbgtxSI6yb9AV9YOJdWuQ80+2M eGh28PCwdxbVk9Gdi/LWo1wrsTyu37Ko5ZLv4flU1G9sFpyMl6yzE2AeeHZMrsGk1oRE sMWQ==
X-Received: by 10.68.242.163 with SMTP id wr3mr98488994pbc.84.1388775623903; Fri, 03 Jan 2014 11:00:23 -0800 (PST)
Received: from spandex.local (216-67-22-99-rb3.fai.dsl.dynamic.acsalaska.net. [216.67.22.99]) by mx.google.com with ESMTPSA id ae5sm144742307pac.18.2014.01.03.11.00.21 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Jan 2014 11:00:22 -0800 (PST)
Message-ID: <52C708C3.3050301@gmail.com>
Date: Fri, 03 Jan 2014 10:00: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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>
In-Reply-To: <26734.1388770438@erosen-linux>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 19:00:34 -0000

On 1/3/14 8:33 AM, Eric Rosen wrote:
> One has to look at the likely impact of the draft, not merely at the
> intentions of the authors.  

I don't know if I'd use "likely" here but I definitely think
the IETF should be somewhat more thoughtful about "possible."

I've been trying to figure out if there's a way forward that
doesn't involve bulldozing the dissenters.  Personally, I'd be
fine with publishing it as informational or experimental, or
if the document provided a lot more clarity about the basis for
review (along the lines of 3552).

Melinda


From Ted.Lemon@nominum.com  Fri Jan  3 11:22:53 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7AFC1ADFC6 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 11:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DW2YsHYVQrgQ for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 11:22:52 -0800 (PST)
Received: from exprod7og101.obsmtp.com (exprod7og101.obsmtp.com [64.18.2.155]) by ietfa.amsl.com (Postfix) with ESMTP id 111F41A1F65 for <ietf@ietf.org>; Fri,  3 Jan 2014 11:22:52 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUscOBJuePe0cH79jMvqupmHgR/ph2pR9@postini.com; Fri, 03 Jan 2014 11:22:45 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B14531B82AE for <ietf@ietf.org>; Fri,  3 Jan 2014 11:22:44 -0800 (PST)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 8C5A219005C; Fri,  3 Jan 2014 11:22:44 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 3 Jan 2014 11:22:44 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <26734.1388770438@erosen-linux>
Date: Fri, 3 Jan 2014 14:22:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3CB1E66E-D95A-4F44-A24D-D29FD8A4175A@nominum.com>
References: <26734.1388770438@erosen-linux>
To: <erosen@cisco.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 19:22:53 -0000

On Jan 3, 2014, at 12:33 PM, Eric Rosen <erosen@cisco.com> wrote:
> Ted> The point of the IETF stating a position on this is not to give =
ADs
> Ted> another thing they can hassle document authors about.
> One has to look at the likely impact of the draft, not merely at the
> intentions of the authors.=20

I'm sorry, I know that there have been some really painful incidents in =
the past, and that people are sensitized to the potential for a repeat, =
but I'd like to think that the IETF has learned from those experiences.

You say that we are edging into politics here, but I don't think that's =
true.   I think that it's entirely appropriate for us to document =
pervasive monitoring as an attack, because it is one.   If you disagree =
with that, that's fine, I'd like to hear your explanation.   If you =
agree that it's an attack, but think the IETF doesn't need to address =
it, I'd like to hear about that.   But it seems to me that you are doing =
neither of those things.

I think one likely impact of this draft is that authors and working =
groups will take pervasive monitoring more seriously as a threat when =
they are designing their protocols.   It's also possible that ADs will =
use this document as a bludgeon.   I don't think anyone on the current =
IESG wants to see that happen.   If you completely disagree that authors =
and working groups ought to be thinking about this, then I can see why =
you would argue for simply scrapping the document.   But if you are =
solely trying to address the concern that the IESG will go mad with =
power, then let's talk about how to tweak the document to address that =
concern.


From stbryant@cisco.com  Fri Jan  3 12:36:49 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D01A1AD69E for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 12:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TfUFSvpjA8bt for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 12:36:48 -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 D7C0A1AC441 for <ietf@ietf.org>; Fri,  3 Jan 2014 12:36:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=893; q=dns/txt; s=iport; t=1388781401; x=1389991001; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=/QvcrbSFMhdT/Y/d/RthvlFhYHWxP/eKTElQgINn9hw=; b=C/C2XdGgpdiWZykbSGgJ35QWVCx9G/S062OS6gPCTZhuriNWETDXx6cW nsODaNm5eK88X2Tf+KvYCVg9l0g23ERz73nzv3TQCbxCNteukBzU+P0oo JXxMcdygX2ip3Prb2YtKz89PcZIJ2vXWYEqncVVmfdpBb7afsYkHWrH3x 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFADAex1KtJXG+/2dsb2JhbABYgwu6F4EMFnSCJQEBAQMBOj8FCwIBCBgeBQshESUCBA4Fh3ADCQi+XA2EQBeMe4FgMweDJIETAQOWK4FsjFqFOoFvgT4
X-IronPort-AV: E=Sophos;i="4.95,599,1384300800"; d="scan'208";a="295141312"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-5.cisco.com with ESMTP; 03 Jan 2014 20:36:40 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s03Kaee8010337 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 3 Jan 2014 20:36:40 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.230]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Fri, 3 Jan 2014 14:36:40 -0600
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPCLYLAS2sNYxC+kmtoTtmduA/Y5pzdZWv
Date: Fri, 3 Jan 2014 20:36:38 +0000
Message-ID: <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
References: <26734.1388770438@erosen-linux>,<52C708C3.3050301@gmail.com>
In-Reply-To: <52C708C3.3050301@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 20:36:49 -0000

I have been wondering whether a simple update to "A Guide to Writing A Secu=
rity Considerations Section" is all that is needed to address the problem i=
n hand?

Stewart

Sent from my iPad

> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com> wrote:
>=20
>> On 1/3/14 8:33 AM, Eric Rosen wrote:
>> One has to look at the likely impact of the draft, not merely at the
>> intentions of the authors. =20
>=20
> I don't know if I'd use "likely" here but I definitely think
> the IETF should be somewhat more thoughtful about "possible."
>=20
> I've been trying to figure out if there's a way forward that
> doesn't involve bulldozing the dissenters.  Personally, I'd be
> fine with publishing it as informational or experimental, or
> if the document provided a lot more clarity about the basis for
> review (along the lines of 3552).
>=20
> Melinda
>=20

From randy@psg.com  Fri Jan  3 12:55:54 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF31D1ADFAA; Fri,  3 Jan 2014 12:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4-9VB5UwwPI; Fri,  3 Jan 2014 12:55:53 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id CD83F1AD69E; Fri,  3 Jan 2014 12:55:53 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VzBmF-0003xN-TT; Fri, 03 Jan 2014 20:55:32 +0000
Date: Fri, 03 Jan 2014 10:55:30 -1000
Message-ID: <m2k3egbxa5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
In-Reply-To: <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com> <6.2.5.6.2.20140102224801.0b454e28@elandnews.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: multipart/signed; boundary="pgp-sign-Multipart_Fri_Jan__3_10:55:27_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 20:55:55 -0000

--pgp-sign-Multipart_Fri_Jan__3_10:55:27_2014-1
Content-Type: text/plain; charset=US-ASCII

>> RFC 3184 included a sentence telling people about the expected
>> conduct regarding IPR disclosure.  I strongly believe that 3184
>> should do the same.
>
> I'll consider this concern as unresolved.  The Area Directors can
> review the comments and recommend how to resolve the concern.

consider this message a formal objection and support of russ's change
request.

randy
--pgp-sign-Multipart_Fri_Jan__3_10:55:27_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJSxyPCAAoJEMzMBey4OgLtxq0H/AtDCYa5oakKyfW9+GLUTeKw
pJKXf5IW/WKnN8Kt4NnKQcmxCmp1P6vGS03xvDQ9ddpTSLAUT9mFXpHHi51tqZkN
WTBP8/xJIJTgHl2a8b7Rpu+xPBu3TlHYPflHiIyn1/uygMpiZKJsLIoXDIBLmRfl
ZWnbyfRAEb+uDCjVjSH6qKy7KKq+tiRR4XWgIwxkoDlEpS3YdDbR/UNbQsA1byne
Bw9O7/zQ4LXPw37XBdMo5fuk6Q72y8dSb9dvBT5mnGNCEFs33n6yFU+z/ss1Z5zS
bet75GoSEPVzp2Ir45wblfZOrXTxK7LxCwDh76NeRxn01HCuPOaWJrKiFL0q4vw=
=yNM3
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Fri_Jan__3_10:55:27_2014-1--

From TurnerS@ieca.com  Fri Jan  3 15:09:08 2014
Return-Path: <TurnerS@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830491ADFC0 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 15:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuBdV5fqr9TO for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 15:09:07 -0800 (PST)
Received: from gateway06.websitewelcome.com (gateway06.websitewelcome.com [67.18.59.2]) by ietfa.amsl.com (Postfix) with ESMTP id 3149A1ADFDA for <ietf@ietf.org>; Fri,  3 Jan 2014 15:09:06 -0800 (PST)
Received: by gateway06.websitewelcome.com (Postfix, from userid 5007) id 8FCF64EF0BF3E; Fri,  3 Jan 2014 17:08:58 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway06.websitewelcome.com (Postfix) with ESMTP id 6DAEC4EF0BEB9 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:08:58 -0600 (CST)
Received: from [173.73.130.192] (port=61935 helo=[192.168.1.4]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <TurnerS@ieca.com>) id 1VzDrN-0006Yy-LG; Fri, 03 Jan 2014 17:08:57 -0600
Content-Type: multipart/signed; boundary="Apple-Mail=_9F96C8F3-C669-4155-BD5A-37E36035578D"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
From: Sean Turner <TurnerS@ieca.com>
In-Reply-To: <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
Date: Fri, 3 Jan 2014 18:08:53 -0500
Message-Id: <A8AE5CC5-E5F4-47E3-852F-DE21783FEAF0@ieca.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com> <6.2.5.6.2.20140102224801.0b454e28@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 173.73.130.192
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([192.168.1.4]) [173.73.130.192]:61935
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 23:09:08 -0000

--Apple-Mail=_9F96C8F3-C669-4155-BD5A-37E36035578D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Jan 03, 2014, at 02:36, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Russ,
> At 13:43 02-01-2014, Russ Housley wrote:
>> This proposed text is an improvement, but I would be much happier =
with the addition of one word to the first sentence:  ... devise =
solutions for the global Internet ...
>=20
> With the above suggestion, the third statement could be as follows:
>=20
>   3. IETF participants devise solutions for the global Internet that
>      meet the needs of diverse technical and operational environments.

Adding an informative reference RFC 3935 would also probably do it.

>> Disclosure of IPR that you know about is personal conduct.
>>=20
>> > The Note Well is used to direct people to BCP 79.  A person =
attending a working group session will be told about the Note Well.  A =
person subscribing to an IETF mailing list will be sent a pointer to the =
Note Well.  I suggest leaving it to the Note Well to list the rules as =
it has not been argued that the Note Well is inadequate.
>>=20
>> RFC 3184 included a sentence telling people about the expected =
conduct regarding IPR disclosure.  I strongly believe that 3184 should =
do the same.

We spend so much time on this and it=92s really unfun to have to scold =
folks on this issue so for me this is a +1 to adding something in about =
expected conduct regarding IPR disclosures.

spt


--Apple-Mail=_9F96C8F3-C669-4155-BD5A-37E36035578D
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIEgDCCBHww
ggJkoAMCAQICCQCdWMxKNutUeTANBgkqhkiG9w0BAQsFADAiMQswCQYDVQQGEwJVUzETMBEGA1UE
ChMKSUVDQSwgSW5jLjAeFw0xMzA0MDMxNDUxMThaFw0xNDA0MDMxNDUxMThaMDgxCzAJBgNVBAYT
AlVTMRMwEQYDVQQKEwpJRUNBLCBJbmMuMRQwEgYDVQQDEwtTZWFuIFR1cm5lcjCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAOpCGCRptT1m+bIpLTmbahZLZ0Qe4X99f8SgTQ7QISvUfpmn
tfOD1oA1AttXlOULEERYubzvDnUTXvstFomQx0XTA67IaV+mw9ODRtG1hPN/erdKX6sU6rH4tsEb
ba3Drr/I0HT3YVvD3SjWtGXjF12XLvTP6+LfMIIDTCAPiEd9KPG23D7skVu/4BvvmdLFI96OARhg
wQ86M+lTIn83KRJlbbfAeIevbRx/rUB7D+uvMdWxOzR0KZJhd6dEeTXVwBXZG4rnQ4uFM+mRSiD4
rxDCyOuIuOzR07tnOyCRio6sRipOZvwQUWttdsgMEs6IxLdWsaTXcs1HjCsxrdedovMCAwEAAaOB
njCBmzAOBgNVHQ8BAf8EBAMCBeAwHwYDVR0jBBgwFoAUAHRsSeXJUmFxTVY4q2HJ8uHl+w0wGwYD
VR0RBBQwEoEQVHVybmVyU0BpZWNhLmNvbTAyBgNVHR8EKzApMCegJaAjhiFodHRwOi8vd3d3Lmll
Y2EuY29tL2NybHMvaWVjYS5jcmwwFwYDVR0gBBAwDjAMBgorBgEEAYHXAAAAMA0GCSqGSIb3DQEB
CwUAA4ICAQAimDYm77ppTi4vK6qJSUhyvCDMGb8mngiEXEYKxsfdHPWoDO7+06j7dAZ8sDD9/FtE
kiUMyoNGSUmKHR+tGperVnNiM/Zk6WwCJv8dYZwhGXNQeEGzeys/UkFv7CFX7uDSn8GQeB8sOAZ1
N1hxV/TvT8qXvcRxP5+aWTAGAq3TKtCQxZjuU74L3st2hZiOhJlhjhqz0K5FIwWzXUK9uwhZe1th
GUpDbRustVgmKN2Xa0pzwqI1VUO0jnWt24A4u59xo6DJQXzQVMhCx0xhpemuT9BrsBDTX8eJdI1i
Wv9wp3ivSrfHjKXp8y8OGD+usiG40HCjj0W9C+dH0VfbgrB6QOI4vA9+kTg4mANth1cxyxwPYOSJ
v0zi1qR0eDIGI//2v2/s6TmGuNqbnRa26Ldv5gGqS7xj32Fiaby6UOXs4+aAIWGZEOH+BXjozcvE
eGBwjU/VRQYu6itR28PaNhNVji4D5ITaGxWWiycqK1EUaFraWHtk7W100ROX69xTeFVZP86D2ymi
/aohl5Vb1vlYHdqlbgqjDRl9dPbTxVCXEHf+jkexcuwlLTvr7F+5DIN6c/EbCpRqQx3edy193L48
OGyRDh1/Wmzpew0VWWAWOSXGl/P9VzXf3Z6GPt7flN/V9iEJAa3Mo+w+eIdzJkHBWR+yJcqQcCRM
MSyishMwLDGCAjgwggI0AgEBMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTAJBgUrDgMCGgUAoIHfMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI
hvcNAQkFMQ8XDTE0MDEwMzIzMDg1NFowIwYJKoZIhvcNAQkEMRYEFO7C7Nvy2BJyTYarxyAx8fyS
z+l0MD4GCSsGAQQBgjcQBDExMC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklFQ0EsIEluYy4C
CQCdWMxKNutUeTBABgsqhkiG9w0BCRACCzExoC8wIjELMAkGA1UEBhMCVVMxEzARBgNVBAoTCklF
Q0EsIEluYy4CCQCdWMxKNutUeTANBgkqhkiG9w0BAQEFAASCAQCiukcpszfVPCMaKok8sXoQzg1+
dharfOrEivOR+PvA26GOFwhAGfzJEFGu9v06lIAdcZXueCPEu3nHMToNQhkKl2nv81iGR9Zx+/Xk
/fTl89OV21ohISa5vPYZ7WhYqIXWwQI1FND49SKf/5PJ14zqTAhe52ylxO9kamtlIZmAnmBEAB/N
gCxs18xhFK82Y/VePotOXij9wCirvKybdmQfpAxErqUgIeoSe4T4EOh2H4tz2Wy1hkEooDfcfEhq
IFmQLq/Cekys0lL775K+utOY/f2crV73aR5c1QNQzQJqElasifG6kIVnkuoiDHsUS92B2U2aqhf9
n59TEg7orc3YAAAAAAAA

--Apple-Mail=_9F96C8F3-C669-4155-BD5A-37E36035578D--

From drc@virtualized.org  Fri Jan  3 15:27:22 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C4931ADFDA; Fri,  3 Jan 2014 15:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.541
X-Spam-Level: 
X-Spam-Status: No, score=-0.541 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7IVxHGwhLZ9K; Fri,  3 Jan 2014 15:27:19 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 53F001ADFEF; Fri,  3 Jan 2014 15:27:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 56B4184CEE; Fri,  3 Jan 2014 18:27:11 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 42468-10; Fri,  3 Jan 2014 18:27:11 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 3441B84B43; Fri,  3 Jan 2014 18:27:09 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_03A522CC-9566-4A79-862D-DFD47FF2A7F4"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IANA blog article
From: David Conrad <drc@virtualized.org>
In-Reply-To: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org>
Date: Fri, 3 Jan 2014 15:27:08 -0800
Message-Id: <55DCB0F3-2ACD-44CB-B6FC-68ACC2A342DD@virtualized.org>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 23:27:22 -0000

--Apple-Mail=_03A522CC-9566-4A79-862D-DFD47FF2A7F4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Jari,

On Jan 3, 2014, at 9:36 AM, IETF Chair <chair@ietf.org> wrote:
> In this article I wanted to highlight an important but often hidden =
part in the IETF ecosystem: Internet Assigned Numbers Authority (IANA).  =
What is IANA, how does it work, how is it related to the IETF, and how =
has it evolved over time? How will it evolve in the future, and how can =
you participate in the discussion?

Thanks for this.  I've often been surprised how few people know or =
understand the IANA functions, how they're performed and under what =
authority, and I suspect clarity on these issues is going to be =
increasingly important in the future. =20

A few points:

- Perhaps it is merely your shorthand, but I've found that saying "IANA" =
as if it is a discrete entity rather than a set of functions performed =
by a contractor (or contractors) tends to confuse things.  For example, =
you say "... IANA then makes the actual allocations ...".  In actuality =
(as you note later on), ICANN, acting as the current IANA "protocol =
parameters function" operator makes the allocation.=20

- As I suspect you're aware, ICANN, as the IANA function operator, =
performs a couple of other administrative duties that are considered (at =
least in the context of the IANA functions contract between the US Dept. =
of Commerce NTIA and ICANN, see =
http://www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_a=
nd_sacs.pdf) outside of the protocol parameter, root zone management, =
and top-level Internet numbers allocation functions, i.e., =
administration of the .ARPA top-level domain and administration of the =
.INT top-level domain. Given past experiences, I hope these other =
functions are kept in mind as people think/talk about future frameworks =
associated with IANA functions evolution.

- Some nits in the sentence "For instance, 2000, the IETF and ICANN =
signed a contract about the protocol parameters aspect of the IANA =
function (RFC 2560)": I presume you meant "in 2000" and "RFC 2860".  =
Also, as opposed to the IANA functions contract between the USG and =
ICANN referenced above, 2860 is not a contract but a "memorandum of =
understanding" -- I've been told by lawyers that the distinction is =
important.

- I probably wouldn't say the system of IANA functions have "grown up" =
as that suggests no further growth is necessary/needed.  I'd agree that =
the system is maturing, however I believe still has a ways to go, albeit =
primarily in non-technical areas. In particular, it will be nice to =
clarify the current ... ambiguity, at least in the eyes of some, =
regarding the authority over IANA functions.

I look forward to seeing how things evolve in the future.

Regards,
-drc
(IANA General Manager, 2005 - 2010)



--Apple-Mail=_03A522CC-9566-4A79-862D-DFD47FF2A7F4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSx0dMAAoJENV6ebf0/4rXBskIAO4Hjsy5JHkVndMks4GQ58Ee
2SCxBb6DNbmlrIryYJo/rf0ZL2A/ymXDxwki/OR/4eH/jTQoMAt4ZM6pMfJLU/kp
wPuAXO1oabL9f5Mfo7h66cFncmfVGcYx1p3iynFiIlLNG4uZ203TO5dwBC+mJvt4
kXzXf4asOPi5bSD/t/XSPuoUnDFnAw7pYD7fzkjj76fE1g6F80bbrIuHyzbWIxKo
Wych7HnEEvEu4W4Ol6sKaQoYKwjnarLJ6/XCtc0XH7J0bwd9ciNp8H9yegEQqs+X
s+cDWbM5HnXMK63tbFmiZ/Qn2OqLqsI8Edvb654JKUY8/8cqcUpPWvgUVCGX/sA=
=pIxo
-----END PGP SIGNATURE-----

--Apple-Mail=_03A522CC-9566-4A79-862D-DFD47FF2A7F4--

From sm@elandsys.com  Fri Jan  3 15:41:59 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ED7F1AD83F; Fri,  3 Jan 2014 15:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e6qgJdXXFW3B; Fri,  3 Jan 2014 15:41:58 -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 E37341ACC91; Fri,  3 Jan 2014 15:41:57 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.235.135]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s03NfS6d009181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jan 2014 15:41:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388792501; bh=H/hJeYRhlF/6jNm5UxgYCShFvF3VGeX3ysV01m+jh3Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WoBdAlFgmN9fwDEhsIivWLMGQDdVKjenw6y2dDsc2QoCtfuIGDAcSwZM/i/DZOX1v PqBvFZU3g1DQqCQviYSzvPNXFzsQWzKfapHJvm//0cIvKmcdQ/azd0kB4ockWo8C1E 1Fbg5vyoYArPs+Opp1bSkvsVt4tubJonlSDM0Fns=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1388792501; i=@elandsys.com; bh=H/hJeYRhlF/6jNm5UxgYCShFvF3VGeX3ysV01m+jh3Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0C6usXVDxuej7Ax4ZTLqb8cZD6PLEBBmUWVS7x05ZCj5p91tqI9jQwSvPfoLuaPhQ 3dnlIypKcVJgpr59QmZuqlhS4UAuPiaUePqF407p3jL9EuMKw2Ed0IsQmZFb03Z5oL CCZSPoalgR1Gx4d6VEC45TX96XAEWEcg78IOzH8Y=
Message-Id: <6.2.5.6.2.20140103153834.0c6591a8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 03 Jan 2014 15:39:37 -0800
To: Sean Turner <TurnerS@ieca.com>, Russ Housley <housley@vigilsec.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
In-Reply-To: <A8AE5CC5-E5F4-47E3-852F-DE21783FEAF0@ieca.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com> <6.2.5.6.2.20140102224801.0b454e28@elandnews.com> <A8AE5CC5-E5F4-47E3-852F-DE21783FEAF0@ieca.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ines Robles <mariainesrobles@googlemail.com>, IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 23:41:59 -0000

Hi Sean, Russ,
At 15:08 03-01-2014, Sean Turner wrote:
>We spend so much time on this and it's really unfun to have to scold 
>folks on this issue so for me this is a +1 to adding something in 
>about expected conduct regarding IPR disclosures.

Here is text which can be inserted in the last paragraph of Section 2:

   We follow the intellectual property guidelines outlined in BCP 79.
   IETF participants read the relevant Internet-Drafts ...

Regards,
S. Moonesamy  


From brian.e.carpenter@gmail.com  Fri Jan  3 16:38:33 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 223091AD845 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:38:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVWb2urNaRDu for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:38:31 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D36B01AC7F1 for <ietf@ietf.org>; Fri,  3 Jan 2014 16:38:31 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so15927657pdj.15 for <ietf@ietf.org>; Fri, 03 Jan 2014 16:38:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=oKQSz1EjP/86JbfxHvV65LhKOLHEp1JucgVBkJcKRi0=; b=PLRW6oFrixQ3QXlK8Y38vnQdnwnWS7m7wkF73z5Cuy4ek4ybEPwymzd7L/leHPA7vl x7kFobpHSUhj2dqJ9waTgOWkxG1JmNSoYvw3qffG13WEQ+wvxVEA8dpbzchwA4W8oLyS +Dj0m/yG+Y3CQpun73c3UBPlWtwSNTcO3+ILP9edUS66jrOMnjcsoffPbIw7ImKfstS8 6LxiQlK5bLagNSO0oJ1cHTLrzVqNUfD38zan6LH0h4mPhuLVcleeBMfoDxpL0dBvFWM/ NYUl3Pz/iiqJ44QFfj3xtvqaUQGuf30oiDd2jigyI6+12edc+5s/NtRiGJULI7C8dG9P fayA==
X-Received: by 10.68.242.163 with SMTP id wr3mr100033757pbc.84.1388795904598;  Fri, 03 Jan 2014 16:38:24 -0800 (PST)
Received: from [192.168.178.21] (1.197.69.111.dynamic.snap.net.nz. [111.69.197.1]) by mx.google.com with ESMTPSA id gv10sm111570330pbd.0.2014.01.03.16.38.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Jan 2014 16:38:23 -0800 (PST)
Message-ID: <52C75808.70701@gmail.com>
Date: Sat, 04 Jan 2014 13:38:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: erosen@cisco.com
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>
In-Reply-To: <26734.1388770438@erosen-linux>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 00:38:33 -0000

On 04/01/2014 06:33, Eric Rosen wrote:
> Scott> Is there something in that that you disagree with?
> 
> The issue isn't whether I agree or disagree with it, it's whether the IETF
> should be making this foray into politics.  

It would be politics if the draft said that (for example) it's
OK for the Fives Eyes consortium to perform pervasive
monitoring, but it's not OK for some other organisation to do
so. Or it would be politics if it said the opposite. It very
carefully doesn't say either of those things or anything like
it. It says that pervasive monitoring is in practical terms a
security attack and that we intend to take this into account in
future IETF work. How is that politics?

There is a political debate going on, but not here.

    Brian

From l.wood@surrey.ac.uk  Fri Jan  3 16:45:11 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 733901AE005 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:45: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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_DBL_REDIR=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXm4OJUVSlk6 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:45:09 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id E25BE1AE001 for <ietf@ietf.org>; Fri,  3 Jan 2014 16:45:08 -0800 (PST)
Received: from [85.158.137.99:65394] by server-12.bemta-3.messagelabs.com id F9/14-20055-C8957C25; Sat, 04 Jan 2014 00:45:00 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-217.messagelabs.com!1388796300!19606043!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20620 invoked from network); 4 Jan 2014 00:45:00 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-11.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jan 2014 00:45:00 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sat, 4 Jan 2014 00:44:59 +0000
From: <l.wood@surrey.ac.uk>
To: <brian.e.carpenter@gmail.com>, <erosen@cisco.com>
Date: Sat, 4 Jan 2014 00:42:44 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8I5Vln9JBk7GjbQ9GEnvC7deMKNQAAIilq
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346A1@EXMB01CMS.surrey.ac.uk>
References: <26734.1388770438@erosen-linux>,<52C75808.70701@gmail.com>
In-Reply-To: <52C75808.70701@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: john-ietf@jck.com, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 00:45:11 -0000

Sigh. That is in itself a political stance.

Jeff Schmidt's Disciplined Minds has a good overview of the political minds=
et of the professional workforce.

http://disciplinedminds.tripod.com


Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Brian E Carpenter [brian.e.=
carpenter@gmail.com]
Sent: 04 January 2014 00:38
To: erosen@cisco.com
Cc: John C Klensin; IETF Discussion; Stewart Bryant
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

On 04/01/2014 06:33, Eric Rosen wrote:
> Scott> Is there something in that that you disagree with?
>
> The issue isn't whether I agree or disagree with it, it's whether the IET=
F
> should be making this foray into politics.

It would be politics if the draft said that (for example) it's
OK for the Fives Eyes consortium to perform pervasive
monitoring, but it's not OK for some other organisation to do
so. Or it would be politics if it said the opposite. It very
carefully doesn't say either of those things or anything like
it. It says that pervasive monitoring is in practical terms a
security attack and that we intend to take this into account in
future IETF work. How is that politics?

There is a political debate going on, but not here.

    Brian=

From l.wood@surrey.ac.uk  Fri Jan  3 16:49:05 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C86481AE01D for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:49: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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOxALMw6zQz0 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:49:04 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.171]) by ietfa.amsl.com (Postfix) with ESMTP id B732F1AE01B for <ietf@ietf.org>; Fri,  3 Jan 2014 16:49:03 -0800 (PST)
Received: from [195.245.230.131:32519] by server-11.bemta-3.messagelabs.com id 84/64-19379-77A57C25; Sat, 04 Jan 2014 00:48:55 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-78.messagelabs.com!1388796535!31666780!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 22765 invoked from network); 4 Jan 2014 00:48:55 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-12.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jan 2014 00:48:55 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sat, 4 Jan 2014 00:48:55 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <melinda.shore@gmail.com>
Date: Sat, 4 Jan 2014 00:45:31 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPCLYLAS2sNYxC+kmtoTtmduA/Y5pzdZWvgABFieo=
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk>
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
In-Reply-To: <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 00:49:06 -0000

"Please include a full explanation of how pervasive monitoring is mitigated=
 in this protocol. If this protocol is not fully cryptographically secure t=
o defeat  pervasive monitoring, explain why not."

Yeah, that gives complete design control to the security AD.

Which problem is being addressed, exactly?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant (stbryant) [=
stbryant@cisco.com]
Sent: 03 January 2014 20:36
To: Melinda Shore
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

I have been wondering whether a simple update to "A Guide to Writing A Secu=
rity Considerations Section" is all that is needed to address the problem i=
n hand?

Stewart

Sent from my iPad

> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com> wrote:
>
>> On 1/3/14 8:33 AM, Eric Rosen wrote:
>> One has to look at the likely impact of the draft, not merely at the
>> intentions of the authors.
>
> I don't know if I'd use "likely" here but I definitely think
> the IETF should be somewhat more thoughtful about "possible."
>
> I've been trying to figure out if there's a way forward that
> doesn't involve bulldozing the dissenters.  Personally, I'd be
> fine with publishing it as informational or experimental, or
> if the document provided a lot more clarity about the basis for
> review (along the lines of 3552).
>
> Melinda
>

From stephen.farrell@cs.tcd.ie  Fri Jan  3 16:53:47 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 814E21AE000 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:53:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lk84JHJ--ZYb for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 16:53:45 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id BD7981ADFFE for <ietf@ietf.org>; Fri,  3 Jan 2014 16:53:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id D510DBE6E; Sat,  4 Jan 2014 00:53:37 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sZ+55D5ZJOxq; Sat,  4 Jan 2014 00:53:35 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.63.191]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id ED8A4BE3F; Sat,  4 Jan 2014 00:53:34 +0000 (GMT)
Message-ID: <52C75B83.6000302@cs.tcd.ie>
Date: Sat, 04 Jan 2014 00:53:23 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, stbryant@cisco.com, melinda.shore@gmail.com
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.6
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 00:53:47 -0000

Lloyd,

On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
> "Please include a full explanation of how pervasive monitoring is
> mitigated in this protocol. If this protocol is not fully
> cryptographically secure to defeat  pervasive monitoring, explain why
> not."

What are you quoting? That text is *not* part of the
draft, nor do I recall it being sent to the list by
anyone.

Surely inventing quotes is not fair game here?

S.

> 
> Yeah, that gives complete design control to the security AD.
> 
> Which problem is being addressed, exactly?
> 
> Lloyd Wood http://about.me/lloydwood 
> ________________________________________ From: ietf
> [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant (stbryant)
> [stbryant@cisco.com] Sent: 03 January 2014 20:36 To: Melinda Shore 
> Cc: ietf@ietf.org Subject: Re: Last Call:
> <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an
> Attack) to Best Current Practice
> 
> I have been wondering whether a simple update to "A Guide to Writing
> A Security Considerations Section" is all that is needed to address
> the problem in hand?
> 
> Stewart
> 
> Sent from my iPad
> 
>> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com>
>> wrote:
>> 
>>> On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at the
>>> likely impact of the draft, not merely at the intentions of the
>>> authors.
>> 
>> I don't know if I'd use "likely" here but I definitely think the
>> IETF should be somewhat more thoughtful about "possible."
>> 
>> I've been trying to figure out if there's a way forward that 
>> doesn't involve bulldozing the dissenters.  Personally, I'd be fine
>> with publishing it as informational or experimental, or if the
>> document provided a lot more clarity about the basis for review
>> (along the lines of 3552).
>> 
>> Melinda
>> 
> 
> 

From turners@ieca.com  Fri Jan  3 17:10:03 2014
Return-Path: <turners@ieca.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D9881AE00F for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:10:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.133
X-Spam-Level: *
X-Spam-Status: No, score=1.133 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IULx_jqyCBds for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:10:02 -0800 (PST)
Received: from gateway04.websitewelcome.com (gateway04.websitewelcome.com [67.18.14.8]) by ietfa.amsl.com (Postfix) with ESMTP id D81651AE009 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:10:01 -0800 (PST)
Received: by gateway04.websitewelcome.com (Postfix, from userid 5007) id 4E33F3F151E16; Fri,  3 Jan 2014 19:09:54 -0600 (CST)
Received: from gator3286.hostgator.com (gator3286.hostgator.com [198.57.247.250]) by gateway04.websitewelcome.com (Postfix) with ESMTP id 2EA283F151DC5 for <ietf@ietf.org>; Fri,  3 Jan 2014 19:09:54 -0600 (CST)
Received: from [173.73.130.192] (port=62146 helo=[192.168.1.4]) by gator3286.hostgator.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from <turners@ieca.com>) id 1VzFkP-0007VS-LG for ietf@ietf.org; Fri, 03 Jan 2014 19:09:53 -0600
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Sean Turner <turners@ieca.com>
In-Reply-To: <3CB1E66E-D95A-4F44-A24D-D29FD8A4175A@nominum.com>
Date: Fri, 3 Jan 2014 20:09:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AC29856-EA0A-45A3-A322-8888BDC2A26D@ieca.com>
References: <26734.1388770438@erosen-linux> <3CB1E66E-D95A-4F44-A24D-D29FD8A4175A@nominum.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1827)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gator3286.hostgator.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - ieca.com
X-BWhitelist: no
X-Source-IP: 173.73.130.192
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([192.168.1.4]) [173.73.130.192]:62146
X-Source-Auth: sean.turner@ieca.com
X-Email-Count: 1
X-Source-Cap: ZG9tbWdyNDg7ZG9tbWdyNDg7Z2F0b3IzMjg2Lmhvc3RnYXRvci5jb20=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:10:03 -0000

On Jan 03, 2014, at 14:22, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Jan 3, 2014, at 12:33 PM, Eric Rosen <erosen@cisco.com> wrote:
>> Ted> The point of the IETF stating a position on this is not to give =
ADs
>> Ted> another thing they can hassle document authors about.
>> One has to look at the likely impact of the draft, not merely at the
>> intentions of the authors.=20
>=20
> I'm sorry, I know that there have been some really painful incidents =
in the past, and that people are sensitized to the potential for a =
repeat, but I'd like to think that the IETF has learned from those =
experiences.
>=20
> You say that we are edging into politics here, but I don't think =
that's true.   I think that it's entirely appropriate for us to document =
pervasive monitoring as an attack, because it is one.   If you disagree =
with that, that's fine, I'd like to hear your explanation.   If you =
agree that it's an attack, but think the IETF doesn't need to address =
it, I'd like to hear about that.   But it seems to me that you are doing =
neither of those things.
>=20
> I think one likely impact of this draft is that authors and working =
groups will take pervasive monitoring more seriously as a threat when =
they are designing their protocols.   It's also possible that ADs will =
use this document as a bludgeon.   I don't think anyone on the current =
IESG wants to see that happen.   If you completely disagree that authors =
and working groups ought to be thinking about this, then I can see why =
you would argue for simply scrapping the document.   But if you are =
solely trying to address the concern that the IESG will go mad with =
power, then let's talk about how to tweak the document to address that =
concern.

Ted=92s one likely impact is pretty much exactly why I agreed to sponsor =
this draft; I also hoped that the end result coupled with RFC 6973 would =
be akin to the two punch combo of BCP 61 & 72.

I guess I=92m not shocked and a little amused that we ended up =
discussing process impacts especially wrt to this draft knowing Stephen =
and how much he absolutely loves process.  But, I guess that=92s because =
everybody wants to know how publication of this draft will affect their =
standard=92s experience (or that we =93engineer" everything).  But, the =
word reasonable in Tim=92s message jogged my memory about another =
conversation I had:

> From: Tim Bray <tbray@textuality.com>
>=20
> There are very few (any?) absolutes in any of the protocols we build, =
just a wealth of often-conflicting design criteria, which force us to =
trade off and make judgment calls.  draft-perpass-attack says that =
mitigation of pervasive surveillance should be seen as one of the design =
criteria, and it=92s not OK to ignore it. A reasonable take is that a =
specification could be held up if there are plausible arguments that =
this criterion has not been given appropriate consideration, and I see =
nothing wrong with that. Similar hold-ups regularly occur when there are =
concerns that there hasn=92t been appropriate consideration for =
efficiency or error-handling or, well, lots of other criteria.=20

When I read this draft for the first time, I wondered among other =
things:

Could publishing this draft make the Internet work better?  Some =
consider better to be more secure/private so sure I can see that it =
could and in fact support that thinking.

Could publishing this draft harm the Internet?  (I guess I=92m probably =
not supposed to be sarcastic here but I can=92t help myself) I couldn=92t =
think of a reason, but I guess I=92m not paranoid enough to have thought =
about the DoS attack that the IESG can levy against authors ;)  More =
seriously, there=92s plenty of checks on abuse of power in the IETF =
(appeals, recalls, negative re-up comments).  What you might not know =
(or believe) is that the IESG does also self-regulate itself somewhat - =
if an AD is going off the deep end they=92re going to hear about it from =
another AD.

Is the draft requesting anything unreasonable or overly burdensome? In =
my mind, no on both accounts.  In fact, there are already =
protocols/directorates that require this; thank you MIB Doctors for =
requiring of MIBs that sensitive information or information that raise =
significant privacy concerns be explicitly listed by name and the =
reasons for the sensitivity/privacy concerns MUST be explained (see RFC =
4181).

Is there an out?  Yes.  If you=92ve got a reason to =93monitor=94, then =
you just need to explain why, which is not unlike other =93outs=94: =
confidentiality not always required if you explain why (BCP61), AKM =
unless =85 (BCP 107), we also give outs to experimental protocols (lisp =
and mptcp comes to mind), etc. =20

Is there unnecessary process being introduced?  I thought not.

Is BCP appropriate?  Sure! We=92ve published BCPs that document what we =
want done as a best practice and what is a best current practice.  I=92ve =
tilted at this windmill both ways and no longer tilt.

Is it all figured out?  No, but that is just fine in my book.  There=92s =
some wicked smart people that participate in the IETF and we=92ll figure =
the process/impacts either now or as we go along.  So we can:

1) Publish now, learn as we go, and then publish the normative bits =
later.

2) Study for [insert timeframe] and then publish the normative bits =
later way we know how later.

Possibly naively, I think that publishing now and dealing with the =
growing pains of learning as we go option is a bit more in spirit of =
what the IETF is supposed to be about.  The latter option to me sounds a =
lot like what people complain about wrt the IETF process taking too long =
and having the bar be too high for the proposed standard level.

spt=

From derhoermi@gmx.net  Fri Jan  3 17:10:52 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656C41AE026 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxLn6aj2R3yQ for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:10:49 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 856721AE009 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:10:49 -0800 (PST)
Received: from netb.Speedport_W_700V ([84.180.229.73]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0MfAog-1Vnbj90XO6-00OmEw for <ietf@ietf.org>; Sat, 04 Jan 2014 02:10:41 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Sat, 04 Jan 2014 02:10:43 +0100
Message-ID: <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de>
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie>
In-Reply-To: <52C75B83.6000302@cs.tcd.ie>
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-Provags-ID: V03:K0:elnQ8t3OYoIHNsa/2PQP9Ww88tUugtsDS77Ao8NVCBIWCW+LDQ8 IXcIiHXWMO3uVLNnMee8PZ75CmVGUzfPZjFP2r1GkUR0X+BbQi105o9j1FaRugyqF/cr6fz UKLAa3XsyIrHS5pS/578hjjPR54IZZ23Q1gI2QzXdqlEStBMjRwoAQj1RJUyGCfKq4g8D7w KlDaioniXQqLIlyL32Njg==
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:10:52 -0000

* Stephen Farrell wrote:
>On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
>> "Please include a full explanation of how pervasive monitoring is
>> mitigated in this protocol. If this protocol is not fully
>> cryptographically secure to defeat  pervasive monitoring, explain why
>> not."
>
>What are you quoting? That text is *not* part of the
>draft, nor do I recall it being sent to the list by
>anyone.
>
>Surely inventing quotes is not fair game here?

The quote marks indicate that the text is a paraphrase; Lloyd Wood re-
states the meaning, or a possible interpretation, of the text, likely
to illustrate a problem with the text. This is a common discourse tech-
nique and should be entirely obvious; nothing unfair about it.

If it does not reflect the intended meaning of the text, then there are
various ways to make that very explicit in the text, for instance, it
could literally say that "full explanation of how pervasive monitoring
is mitigated" is not expected or required. Then it should be obvious
that the above is not a permissable paraphrase.
-- 
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 randy@psg.com  Fri Jan  3 17:11:15 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 378CA1AE03C; Fri,  3 Jan 2014 17:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KeDDz2O5XjFx; Fri,  3 Jan 2014 17:11:14 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id E40071AE039; Fri,  3 Jan 2014 17:11:13 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1VzFlZ-0004PS-UW; Sat, 04 Jan 2014 01:11:06 +0000
Date: Fri, 03 Jan 2014 15:11:05 -1000
Message-ID: <m2d2k8lffa.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: The IESG <iesg-secretary@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Fri_Jan__3_15:11:00_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:11:15 -0000

--pgp-sign-Multipart_Fri_Jan__3_15:11:00_2014-1
Content-Type: text/plain; charset=US-ASCII

this draft could be used by those nasty ADs to abuse working groups and
draft authors.  perhaps if it is experimental.

randy


--pgp-sign-Multipart_Fri_Jan__3_15:11:00_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJSx1+oAAoJEMzMBey4OgLt1icIAKQdN5eTH0sBkfgwguf9Bb4h
CHlpOyh/XTG7a6cNj1WxdP5hi4Jt8TUF531ni4i9QV5ED3HissjhUrKG3JcTT5uJ
hCwN3iLyLT1p4JLmLq9zu6sZwQXMrruZCktEt+bUrKSPLr+G1Z2/JTZ6R8Ta2f4t
NJqxqzot9O17A0/vw3M2bnBA8f/im/E1/nD1PziLP4e3rT+/dBN7cxZpCVhwLMKB
ejRBs60h3eZF+sfqoAMSCK5mxL/vQQ6EZR4dXSZcZmedcU0yjcFa/R1Mds6AexQC
hg5VmPjAzTuPQLKKnojDG3vn4R6618woIP9xpavboMd+VbgGy+nOn0+0a5MWCQ0=
=az4A
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Fri_Jan__3_15:11:00_2014-1--

From stephen.farrell@cs.tcd.ie  Fri Jan  3 17:19:56 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 740DB1AE009 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:19:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRyIuUKWsZ_A for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:19:53 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 923A81AD72A for <ietf@ietf.org>; Fri,  3 Jan 2014 17:19:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8359CBE6F; Sat,  4 Jan 2014 01:19:45 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BEQz3-n4tflA; Sat,  4 Jan 2014 01:19:44 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.63.191]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4CF59BE6E; Sat,  4 Jan 2014 01:19:44 +0000 (GMT)
Message-ID: <52C761A6.8060800@cs.tcd.ie>
Date: Sat, 04 Jan 2014 01:19:34 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de>
In-Reply-To: <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.6
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:19:56 -0000

On 01/04/2014 01:10 AM, Bjoern Hoehrmann wrote:
> * Stephen Farrell wrote:
>> On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
>>> "Please include a full explanation of how pervasive monitoring is
>>> mitigated in this protocol. If this protocol is not fully
>>> cryptographically secure to defeat  pervasive monitoring, explain why
>>> not."
>>
>> What are you quoting? That text is *not* part of the
>> draft, nor do I recall it being sent to the list by
>> anyone.
>>
>> Surely inventing quotes is not fair game here?
> 
> The quote marks indicate that the text is a paraphrase; Lloyd Wood re-
> states the meaning, or a possible interpretation, of the text, likely
> to illustrate a problem with the text. This is a common discourse tech-
> nique and should be entirely obvious; nothing unfair about it.
> 
> If it does not reflect the intended meaning of the text, then there are
> various ways to make that very explicit in the text, for instance, it
> could literally say that "full explanation of how pervasive monitoring
> is mitigated" is not expected or required. Then it should be obvious
> that the above is not a permissable paraphrase.

The text (I hate to bring it up, seems almost unfashionable;-),
says:

   Those developing IETF specifications need to be able to describe how
   they have considered pervasive monitoring, and, if the attack is
   relevant to the work to be published, be able to justify related
   design decisions.  This does not mean a new "pervasive monitoring
   considerations" section is needed in IETF documentation.  It means
   that, if asked, there needs to be a good answer to the question "is
   pervasive monitoring relevant to this work and if so how has it been
   addressed?"

Lloyd's "paraphrase" is entirely unlike the actual text. His
quote marks, are, like his argument, entirely bogus. (And not
even funny, which is often a redeeming quality of Lloyd's
posts:-) Given that there seems to be a trend to ignore the
actual text, and that that I've already commented on that, I
think yes, his supposed quote is out of order. Perhaps you
don't, and that's fine, but I do.

S.


> 

From derhoermi@gmx.net  Fri Jan  3 17:34:00 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEAB1ADFF8 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3l_0AG5bWPc for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:33:58 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5EF1AE010 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:33:58 -0800 (PST)
Received: from netb.Speedport_W_700V ([84.180.229.73]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0MSIf1-1Vrk6z3uJ9-00TVsx for <ietf@ietf.org>; Sat, 04 Jan 2014 02:33:49 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Date: Sat, 04 Jan 2014 02:33:47 +0100
Message-ID: <vkoec955qnuocbugji9kgvrenrr8j53dsa@hive.bjoern.hoehrmann.de>
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie>
In-Reply-To: <52C761A6.8060800@cs.tcd.ie>
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-Provags-ID: V03:K0:37D6QLNyEhy/2F+oQqwsaaCcQJk0w2uLsAyIw8supL2+gd7dkSE ouGLprHd6pGnhWxKqlfHBiGi0HzYoTtFgQxkmOeAmSruu5ASHqQS8+9WfmUw4KshNCaKpv8 n9J79nhTwB8Gbpfm0SU+CHaqh0L8ARp6DRIqbvy/N1ffU27xSmeLSc2sLYS5WGChFygc3Ms cZ4ifW5wBg85wVch2KrLQ==
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:34:00 -0000

* Stephen Farrell wrote:
>On 01/04/2014 01:10 AM, Bjoern Hoehrmann wrote:
>> * Stephen Farrell wrote:
>>> On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
>>>> "Please include a full explanation of how pervasive monitoring is
>>>> mitigated in this protocol. If this protocol is not fully
>>>> cryptographically secure to defeat  pervasive monitoring, explain why
>>>> not."

>The text (I hate to bring it up, seems almost unfashionable;-),
>says:
>
>   Those developing IETF specifications need to be able to describe how
>   they have considered pervasive monitoring, and, if the attack is
>   relevant to the work to be published, be able to justify related
>   design decisions.  This does not mean a new "pervasive monitoring
>   considerations" section is needed in IETF documentation.  It means
>   that, if asked, there needs to be a good answer to the question "is
>   pervasive monitoring relevant to this work and if so how has it been
>   addressed?"

>Lloyd's "paraphrase" is entirely unlike the actual text. His
>quote marks, are, like his argument, entirely bogus. (And not
>even funny, which is often a redeeming quality of Lloyd's
>posts:-) Given that there seems to be a trend to ignore the
>actual text, and that that I've already commented on that, I
>think yes, his supposed quote is out of order. Perhaps you
>don't, and that's fine, but I do.

If you think it would be a serious problem if the text is interpreted as
in the paraphrase above, then I think revisions to the actual text are
in order, because if there is any difference between the actual text and
the paraphrase, I find it hard to impossible to make out. It is not fine
to keep the text as-is if it is easy to misinterpret.
-- 
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 abdussalambaryun@gmail.com  Fri Jan  3 17:34:51 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 425E21AE010 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:34:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oIOW-ZoLUo54 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:34:49 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 097D51AE032 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:34:49 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id rd3so16319845pab.41 for <ietf@ietf.org>; Fri, 03 Jan 2014 17:34:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u1xDPuO0nJoKKd+ocZRejUoeVsdPmaO+x5+E9SgSXS8=; b=Wa7N49TAoWpRhy8YBAekpw4foaVBkgYK4n66yl0ONZBnBxPJjlDUG2EwPBxqe8mw4c X2Nq5Y+JEhH3Dit8ZQ09dBCFM03bFBrQKRjcyVb3Ilu4ZnKdHrlNJaHCkjkuJA5VOCfX IZQwRYngnHT/03yUAWja+7rROtJ9Vw6OkZGrQIGdcnB12dnXCpvHonQW/UhyWZKrIKDw wLXx8NH9xOhEab0sPkaTnQzYQDolUwSdboK6TZExBRQD6R1QP27loByYJoxC8b5ehnOA OGRIYHfq3Ku1g/QuhhDDLwCzLjNntaGiVDj0AWSK6QRYJpdC2vyNCN1xAtmmtPXKz9iR AiLg==
MIME-Version: 1.0
X-Received: by 10.68.244.168 with SMTP id xh8mr99408118pbc.3.1388799281691; Fri, 03 Jan 2014 17:34:41 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Fri, 3 Jan 2014 17:34:41 -0800 (PST)
In-Reply-To: <52C75B83.6000302@cs.tcd.ie>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie>
Date: Sat, 4 Jan 2014 02:34:41 +0100
Message-ID: <CADnDZ8-PgppMkym=XF_e+ercFMa4X+aua97Dui1RG3HKxHELzg@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=047d7b16348dd9836004ef1b0725
Cc: "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:34:51 -0000

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

I think if we want to do a practice solution roadmap together we need the
draft to add more editors for diversity or include at least two more
(recommending Dave and Melinda). Secondly the draft to state relating to
the current plan practice what IAB and IESG should do? And what WGs should
do? Is there a team work between the bodies or there is continuous
separation as old days? Why the draft only states for IETF
community confirmation and responsibilities and ignores the IAB and IESG
responsibilities in future actions? Couldn't this draft be a joint work of
all bodies?

IMHO the previous IESG and IAB are responsible for the defined attacks as
well and they should take different strategies in working with IETF
community. The draft should be written in a way to guide bottom designs but
also upper designs.

AB

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

I think if we want to do a practice=A0solution roadmap together we need the=
 draft to add more editors=A0for diversity=A0or include at least two more (=
recommending=A0Dave and Melinda).=A0Secondly the draft to state relating to=
 the current plan practice=A0what IAB and IESG should do? And what WGs shou=
ld do? Is there a team work between the bodies or there is continuous separ=
ation as old days? Why the draft only states for IETF community=A0confirmat=
ion and responsibilities=A0and ignores the IAB and IESG responsibilities in=
 future actions? Couldn&#39;t this draft be a joint work of all bodies?<div=
>
<br></div><div>IMHO the previous IESG and IAB are responsible for the defin=
ed=A0attacks as well and they should take different strategies in working w=
ith IETF community. The draft should be written in a way to guide=A0bottom =
designs but also upper=A0designs.=A0</div>
<div><br></div><div>AB<br><div><br></div></div>

--047d7b16348dd9836004ef1b0725--

From stephen.farrell@cs.tcd.ie  Fri Jan  3 17:35:58 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F63F1AE010 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:35:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxeETr294Fjv for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:35:57 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 273C11ADFF8 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:35:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 71F7BBE76; Sat,  4 Jan 2014 01:35:49 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id poXWqlirqvOq; Sat,  4 Jan 2014 01:35:48 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.63.191]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 454EFBE7D; Sat,  4 Jan 2014 01:35:47 +0000 (GMT)
Message-ID: <52C76569.70303@cs.tcd.ie>
Date: Sat, 04 Jan 2014 01:35:37 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie> <vkoec955qnuocbugji9kgvrenrr8j53dsa@hive.bjoern.hoehrmann.de>
In-Reply-To: <vkoec955qnuocbugji9kgvrenrr8j53dsa@hive.bjoern.hoehrmann.de>
X-Enigmail-Version: 1.6
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:35:58 -0000

On 01/04/2014 01:33 AM, Bjoern Hoehrmann wrote:

> If you think it would be a serious problem if the text is interpreted as
> in the paraphrase above, then I think revisions to the actual text are
> in order, because if there is any difference between the actual text and
> the paraphrase, I find it hard to impossible to make out. It is not fine
> to keep the text as-is if it is easy to misinterpret.

I welcome honest attempts to improve the text. Lloyd's was
not that.

Feel free to propose better text, I'll be happy to see that.

S.

> 

From l.wood@surrey.ac.uk  Fri Jan  3 17:46:27 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2AE1ADFFC for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:46:27 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qm5jBvNYKJwh for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 17:46:25 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.171]) by ietfa.amsl.com (Postfix) with ESMTP id AB4491ADFF7 for <ietf@ietf.org>; Fri,  3 Jan 2014 17:46:24 -0800 (PST)
Received: from [195.245.230.131:20544] by server-11.bemta-3.messagelabs.com id 78/83-19379-8E767C25; Sat, 04 Jan 2014 01:46:16 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1388799976!29408647!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20363 invoked from network); 4 Jan 2014 01:46:16 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 4 Jan 2014 01:46:16 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sat, 4 Jan 2014 01:46:16 +0000
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <stbryant@cisco.com>, <melinda.shore@gmail.com>
Date: Sat, 4 Jan 2014 01:46:15 +0000
Subject: RE: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: Ac8I52gwySKyIeymRzeG17+iNUUi9QABgjOW
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346A3@EXMB01CMS.surrey.ac.uk>
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk>, <52C75B83.6000302@cs.tcd.ie>
In-Reply-To: <52C75B83.6000302@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 01:46:27 -0000

Stephen,
Stephen

I am responding to Stewart's suggestion with a suggestion of the likely add=
ed text to the Guide he suggests a "simple update" to. Which would go beyon=
d the 'think about monitoring' to 'explicitly write up how monitoring is ha=
ndled' on the way to full security protocol emphasis. Which is what doomed =
work in DTNRG and made it irrelevant to its problem space, by the way.

I quoted stewart's email is full below before responding to it. That is the=
 usual thing to do.  I hope this helps with reading comprehension.

Before you check, "simple update" is not in your draft either.

I don't think pushing policy through rapidly here is fair game either.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stephen Farrell [stephen.farrell@cs.tcd.ie]
Sent: 04 January 2014 00:53
To: Wood L  Dr (Electronic Eng); stbryant@cisco.com; melinda.shore@gmail.co=
m
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Mo=
nitoring is an Attack) to Best Current Practice

Lloyd,

On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
> "Please include a full explanation of how pervasive monitoring is
> mitigated in this protocol. If this protocol is not fully
> cryptographically secure to defeat  pervasive monitoring, explain why
> not."

What are you quoting? That text is *not* part of the
draft, nor do I recall it being sent to the list by
anyone.

Surely inventing quotes is not fair game here?

S.

>
> Yeah, that gives complete design control to the security AD.
>
> Which problem is being addressed, exactly?
>
> Lloyd Wood http://about.me/lloydwood
> ________________________________________ From: ietf
> [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant (stbryant)
> [stbryant@cisco.com] Sent: 03 January 2014 20:36 To: Melinda Shore
> Cc: ietf@ietf.org Subject: Re: Last Call:
> <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an
> Attack) to Best Current Practice
>
> I have been wondering whether a simple update to "A Guide to Writing
> A Security Considerations Section" is all that is needed to address
> the problem in hand?
>
> Stewart
>
> Sent from my iPad
>
>> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com>
>> wrote:
>>
>>> On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at the
>>> likely impact of the draft, not merely at the intentions of the
>>> authors.
>>
>> I don't know if I'd use "likely" here but I definitely think the
>> IETF should be somewhat more thoughtful about "possible."
>>
>> I've been trying to figure out if there's a way forward that
>> doesn't involve bulldozing the dissenters.  Personally, I'd be fine
>> with publishing it as informational or experimental, or if the
>> document provided a lot more clarity about the basis for review
>> (along the lines of 3552).
>>
>> Melinda
>>
>
>

From mcr@sandelman.ca  Fri Jan  3 19:43:50 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E950E1AE079 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 19:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.019
X-Spam-Level: *
X-Spam-Status: No, score=1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_SOFTFAIL=0.665, T_TVD_MIME_NO_HEADERS=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSPIVsdqG637 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 19:43:48 -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 5ABF81AE077 for <ietf@ietf.org>; Fri,  3 Jan 2014 19:43:48 -0800 (PST)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id C66932002C; Fri,  3 Jan 2014 23:58:43 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 1D29564647; Fri,  3 Jan 2014 22:43:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 059C563AD7; Fri,  3 Jan 2014 22:43:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: adrian@olddog.co.uk
Subject: Re: review of draft-crocker-id-adoption-05
In-Reply-To: <020a01cf08a8$9354a640$b9fdf2c0$@olddog.co.uk>
References: <20140103164853.GE8668@mx1.yitter.info> <020a01cf08a8$9354a640$b9fdf2c0$@olddog.co.uk>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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: Fri, 03 Jan 2014 22:43:38 -0500
Message-ID: <32500.1388807018@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 03:43:51 -0000

--=-=-=


Adrian Farrel <adrian@olddog.co.uk> wrote:
    >> This is yet another process document that, no matter how
    >> much the text protests otherwise, will probably be used as a club in
    >> some future contentious WG discussion to try to beat opponents into
    >> submission.

    > At the moment we don't seem to be able to move for fear of clubbing WGs at some future unspecified time.
    > And at the same time we have WG chairs saying "please give us a bit of general guidance on some topics".

I read the document, and I find it useful.
So, as a guide to chairs, I think that all of the work/text has value.

This document is going forward as Informational rather than BCP.
While it represents some kind of consensus (and if it's the consensus of the
IESG as to how the IESG wants things done, that's important to know), I think
it's important that it's a guideline.

As such it doesn't have any force to club WG chairs.
But at the same time, having no force, I wonder at the value of putting this
into any place other than the wg-chairs wiki.

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




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

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

iQCVAwUBUseDaYqHRg3pndX9AQJRFwQAhoic+MM7yd/gg0MYMUSOyTDWaFvmCnyn
hvDBE+09ujtC7oGtMXF8OD7/c1bU6VBX92QXFvzNYR8aA4tyW5eFWgTwEmBuPAOC
jNlJlI05Og76nVurgg51B7knFRxhIeIR5m/IdROqgI4xo5dfkdUt4gYTB7B5kvTM
KT186Rsx9pM=
=+gF+
-----END PGP SIGNATURE-----
--=-=-=--

From brian.e.carpenter@gmail.com  Fri Jan  3 20:15:48 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7EE1A1DFA for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 20:15:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qaWnbnzjETW for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 20:15:46 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D569B1A16F0 for <ietf@ietf.org>; Fri,  3 Jan 2014 20:15:46 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id g10so16156280pdj.1 for <ietf@ietf.org>; Fri, 03 Jan 2014 20:15:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+mCOxMhKch7hZ6IAl8AXDKXNVDW6rJJkpXsCdtHa4LY=; b=sYjskaKtyyjvN96eVGMYrwWDkBKrllsDx6O5RHbuBBFVXq2GUc9tb2Zbq4HAczDzEs TryB9rnHAC+EyRC151gxCTkrvtpB8lQ5OEg1afHhqaj1oc0825/XHrlar+lmlQk6vrZk 8me6b0FLQmOeC6aZFr077XmDtyDNr+AJWLEgZHHnPuRwFe1iWZXC7xORrFhoEeNDhqPI slnOB0AxrnjD3IAz2B39NdjSrEOqpabACY5C4EUqlP7Hnq+yKIw3QKJMyHBZYFwaHKk+ weqq2e8HDbhsqr8DdX4GCIO1pcutItLM6Wg48CrAanv+wpXsfKrp+FZIiBXbVtDqCW3U jzXA==
X-Received: by 10.68.200.129 with SMTP id js1mr100170369pbc.14.1388808936898;  Fri, 03 Jan 2014 20:15:36 -0800 (PST)
Received: from [192.168.178.21] (1.197.69.111.dynamic.snap.net.nz. [111.69.197.1]) by mx.google.com with ESMTPSA id i10sm147309625pat.11.2014.01.03.20.15.33 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Jan 2014 20:15:35 -0800 (PST)
Message-ID: <52C78AEF.2010908@gmail.com>
Date: Sat, 04 Jan 2014 17:15:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie>
In-Reply-To: <52C761A6.8060800@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 04:15:48 -0000

On 04/01/2014 14:19, Stephen Farrell wrote:

>    It means
>    that, if asked, there needs to be a good answer to the question "is
>    pervasive monitoring relevant to this work and if so how has it been
>    addressed?"

I think this is an excellent question for a reviewer to ask,
regardless of whether the present draft is published as a BCP,
an Informational document, or never.

Responsible engineering means considering a great number of
eventualities when finalising a design, and this is just one
more of those eventualities.

     Brian

From drc@virtualized.org  Fri Jan  3 20:21:26 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 721EE1A1F4A for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 20:21:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27kPFrSnrBI3 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 20:21:23 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7F01A1F1B for <ietf@ietf.org>; Fri,  3 Jan 2014 20:21:23 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 2CF7184CEE; Fri,  3 Jan 2014 23:21:15 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 43861-06; Fri,  3 Jan 2014 23:21:14 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 0F7DA84B43; Fri,  3 Jan 2014 23:21:12 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_7C082628-01FF-4F28-B934-E6C26619220A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com>
Date: Fri, 3 Jan 2014 20:21:07 -0800
Message-Id: <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 04:21:26 -0000

--Apple-Mail=_7C082628-01FF-4F28-B934-E6C26619220A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Russ,

A few comments/suggestions on your draft:

Overall: =20

I'm a bit uncomfortable with specifying the contents of registries =
within RFCs these days as they can become out of date even before =
they're published.  For example, it's likely there's going to be a =
reservation of IPv6 space for LISP EID prefixes in the near future but =
(I suspect) after your draft is published as an RFC.  Perhaps it would =
make more sense to reference IANA registries instead of listing the =
contents of what would be in those registries in the draft text, e.g., =
pointing to =
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-speci=
al-registry.xml for IPv4 and =
http://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-speci=
al-registry.xhtml for IPv6 (and creating a special purpose registry for =
AS numbers)?

I find it curious that when talking about top-level domains, the =
criteria (according to RFC 6761) for reservation is "Standards Action" =
or "IESG Approval" but when talking about reserving Internet Number =
resources, the criteria is "IETF Review".  Any idea why there is a =
discrepancy?

Specific comments:

Section 2.1, second paragraph:

   The allocation and registration functions for all non-reserved AS
   numbers are handled by the Internet Numbers Registry System in
   accordance with policies developed by the Regional Internet
   Registries (RIRs).

I might suggest:

"The allocation and registration functions for all non-reserved AS =
numbers are currently handled by the Internet Numbers Registry System in =
accordance with policies developed via the Regional Internet Registries' =
(RIRs) public policy development processes."

Section 2.2, first paragraph:

   The allocation and registration functions for all non-reserved
   globally unique unicast IPv4 unicast addresses are handled by the
   Internet Numbers Registry System in accordance with policies
   developed by the Regional Internet Registries (RIRs).

Similar to the previous suggestion (dropping a redundant 'unicast'):

"The allocation and registration functions for all non-reserved globally =
unique unicast IPv4 addresses are currently handled by the Internet =
Numbers Registry System in accordance with policies developed via the =
RIRs' public policy development processes."

Section 2.3, second paragraph:

   The allocation and registration functions for all non-reserved
   globally unique unicast IPv6 unicast addresses are handled by the
   Internet Numbers Registry System in accordance with policies
   developed by the Regional Internet Registries (RIRs).

Similar to the previous suggestion (also dropping a redundant =
'unicast'):

"The allocation and registration functions for all non-reserved globally =
unique unicast IPv6 addresses are currently handled by the Internet =
Numbers Registry System in accordance with policies developed via the =
RIRs' public policy development processes."

Section 3:

The parenthetical "(e.g., anycast)" may be a bit confusing/ambiguous.  =
What most people today think of anycast (i.e., "shared unicast") don't =
generally need to be treated specially by the Internet Numbers Registry =
System or the IETF.  I'd recommend just dropping the parenthetical.

Section 4:

While the statement there is truthful, perhaps should there be some =
mention of the potential implications of reserved space in the context =
of trying to identify sources of badness that are using reserved =
addresses or ASes?  E.g., perhaps recommending that care should be taken =
by operators to ensure that traffic sourced and/or destined to reserved =
addresses/ASNs is appropriate?

Hope this helps.

Regards,
-drc


--Apple-Mail=_7C082628-01FF-4F28-B934-E6C26619220A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSx4w0AAoJENV6ebf0/4rXzYIIAKEt71N7xRxEuVhvKxlwvyUy
wYgZkFIY2aSLj58ACmjgRlACiCL/EhIqVAQj/GxtP4eUciQCe+IZZVIem0dXVHVO
L3eZeieV5k4+6d84TPaXgYPgJGGAPn2/1dtvShEdXDgpNl8TgCKUFCDWkzzd5anI
DpR3KCuRTdSfxRgVtZPV66TP0HPlzZ3he2Mci8DvmMgES3A5LUshCDphKJeE9/Ur
0+yGiZ5HtCcw8pnTnTLVTln13g+LU9xmHLlA84jcV24uZRdwCjjRpmqUraPaHNy5
RxFklMPbAi45iahB6jfgQgZKKVi9Oa8hIBhBVwkhAjSXZAmDVZa9x6C6vFeer1A=
=hoNX
-----END PGP SIGNATURE-----

--Apple-Mail=_7C082628-01FF-4F28-B934-E6C26619220A--

From tbray@textuality.com  Fri Jan  3 21:30:18 2014
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15571A1F56 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 21:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2B77hRK3TGr for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 21:30:17 -0800 (PST)
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) by ietfa.amsl.com (Postfix) with ESMTP id F2C541A1F4E for <ietf@ietf.org>; Fri,  3 Jan 2014 21:30:16 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id c11so8706580lbj.1 for <ietf@ietf.org>; Fri, 03 Jan 2014 21:30:08 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=HQgd9IubwTHML+HuoBLoNFtxIloHcMzx5s43HhUP16A=; b=bYf72Odw68rfk0Q4HDIZF5FN3RnFm+MRs6z1NgSjORchWrLqYO4j+9j1t8r07B3fBH RGVGY1F0FuAgB0+6sMGDYR8wZtMFFTXymMAxHKQwdGLaGWiO3Wi6eJ50vwTSGj5Ey0YK tJvmwDE3BkV+2Xl2RwXLCmAVW20tLf7loPJluTQVx1ZQ1ZDihmcVArLWGcgDsoG1Jnih rXTk4j7SVHRp3m6nNTgmMpZH/LnAl3aI+9yOUrgWRGXtsrzWuo2tSul6yy44ysU6RGpm rpbqNkLf/5d0wExJMv2ssAcox08GUHR8rpxTwpT9BgzE3OVXCYt4LzYh4MfH1byLepUC Doxw==
X-Gm-Message-State: ALoCoQmMFmCuM9QT4fopJY28VFRAcuXKmTrD2qSjnPU0yoS0K/Z45NTDKbOzRFStI7Kv26fBJ3Uk
MIME-Version: 1.0
X-Received: by 10.152.45.8 with SMTP id i8mr38690116lam.12.1388813408724; Fri, 03 Jan 2014 21:30:08 -0800 (PST)
Received: by 10.114.24.6 with HTTP; Fri, 3 Jan 2014 21:30:08 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de>
Date: Fri, 3 Jan 2014 21:30:08 -0800
Message-ID: <CAHBU6iuEfPyS-2jth4HmPQQu-d6gTJT2gsHkao70Ax_DS+JTdQ@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Tim Bray <tbray@textuality.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary=001a11c1ba20e2f93004ef1e512f
Cc: IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 05:30:19 -0000

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

On Fri, Jan 3, 2014 at 5:10 PM, Bjoern Hoehrmann <derhoermi@gmx.net> wrote:

> >Surely inventing quotes is not fair game here?
>
> The quote marks indicate that the text is a paraphrase; Lloyd Wood re-
> states the meaning, or a possible interpretation, of the text, likely
> to illustrate a problem with the text. This is a common discourse tech-
> nique and should be entirely obvious; nothing unfair about it.
>

No ***ing way.  Drafts say what they say, and recasting them in other words
and putting quotes around the transmogrified version is completely out of
bounds.

The quality of this discussion would be greatly improved if it were to
refocus on what the draft actually asserts and proposes.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jan 3, 2014 at 5:10 PM, Bjoern Hoehrmann <span dir=3D"ltr">&lt;<a href=
=3D"mailto:derhoermi@gmx.net" target=3D"_blank">derhoermi@gmx.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">&gt;Surely inventing quote=
s is not fair game here?<br>
<br>
</div>The quote marks indicate that the text is a paraphrase; Lloyd Wood re=
-<br>
states the meaning, or a possible interpretation, of the text, likely<br>
to illustrate a problem with the text. This is a common discourse tech-<br>
nique and should be entirely obvious; nothing unfair about it.<br></blockqu=
ote><div><br></div><div>No ***ing way. =C2=A0Drafts say what they say, and =
recasting them in other words and putting quotes around the transmogrified =
version is completely out of bounds. =C2=A0</div>
<div><br></div><div>The quality of this discussion would be greatly improve=
d if it were to refocus on what the draft actually asserts and proposes.</d=
iv><div><br></div></div></div></div>

--001a11c1ba20e2f93004ef1e512f--

From hallam@gmail.com  Fri Jan  3 22:16:05 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32C3F1AC7F3 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 22:16:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vFQgVmZPKQby for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 22:16:02 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id B27F61AC4AC for <ietf@ietf.org>; Fri,  3 Jan 2014 22:16:01 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id l4so8726468lbv.13 for <ietf@ietf.org>; Fri, 03 Jan 2014 22:15:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lXOaSz/nbIUKNBO2iGwyY0sm63igZrNUJCatcqazmaY=; b=PQWrhNJn5ieBVxiNE/DN4a+rVd4ncmongjo/eG/z4HDV/MIx5sVkV+fjea83L5Kvre djEDXgRcJjJVIysDNcWkVUNuAS2bN1ztBl8kIi26LVwmsezWutj9cfYDwZeintjOxNhz 2XclsLNw+XLPiF6G7bcZ5tGjFSz/CmagSnUb/m8Y/cR+juR8ygR387k24iVM8iqHR4QW zOD0yaVjL2oOyVwKFZfEnwtpib7Kng2t8bMRhsWl9Js3BH9zcIyFBjrNUnbhARcL2viF KU0krg3edK/9pz5juqaYOaH8GDMepx0hgiL9+fdzmkI8h27Nhggz/sUv/7TCvfgR65n0 s9Mw==
MIME-Version: 1.0
X-Received: by 10.112.138.98 with SMTP id qp2mr6238lbb.82.1388816153451; Fri, 03 Jan 2014 22:15:53 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Fri, 3 Jan 2014 22:15:53 -0800 (PST)
In-Reply-To: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org>
Date: Sat, 4 Jan 2014 01:15:53 -0500
Message-ID: <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0116049e7c232604ef1ef5aa
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 06:16:05 -0000

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

On Fri, Jan 3, 2014 at 12:36 PM, IETF Chair <chair@ietf.org> wrote:

> In this article I wanted to highlight an important but often hidden part
> in the IETF ecosystem: Internet Assigned Numbers Authority (IANA).  What is
> IANA, how does it work, how is it related to the IETF, and how has it
> evolved over time? How will it evolve in the future, and how can you
> participate in the discussion?
>

I think that the article needs to go back to some basic principles.

The whole point of the end-to-end architecture was that it enabled
innovation and diversity. In particular it was possible to add applications
to the Internet without going to some central authority to ask permission.
The IETF is not in the business of deciding how people use the Internet
except to the extent that doing so may harm others, it is only in the
business of setting standards that enable interoperability.


So when we look at the role of IANA, there are different concerns for
different protocol layers. The concerns at the IP layer are different to
the concerns of DNS which are in turn different to those of applications.

At the IP layer compact representation is vital and code points are a very
scarce resource by necessity. Allocation has to be carefully considered
because they potentially affect the routers at the core of the Internet
which are very difficult to change.

The DNS is an interesting case because the number of code points is
generous but finite. Less than 1% of code points are assigned.


At the application layer we have the curious situation that port
allocations are essentially exhausted so we use ports 80 and 443 for
everything. But in most cases the general rule should be that application
protocols should be designed so that code points are not a constrained
resource and the primary purpose of assignment should be to prevent
ambiguity arising and to provide as much documentation as is possible.

We have learned to our cost that X-Headers don't work. Telling people to go
experiment in a sandbox and then come to the IETF when the protocol is
ready and get issued a real code point has not worked. It guarantees we end
up with multiple code points.

The status quo for most registries is that they are permissive but there is
a large amount of difference in the criteria and there are experts involved
doing reviews for some systems but not others. There is a general lack of
consistency. A standards organization should look for consistency.


One important change is that every future application protocol proposal
should be required to have an effectively unlimited code space for
assignment. Another is that application protocols should be required to
reuse code points from common registries rather than define their own.

At the moment we have separate crypto registries for TLS, IPSEC, PEM, PKIX
and XML Digital Signature. The JOSE folk want to create another. There
should be a policy that tells people from the start that there will be no
new crypto registries.

Fixed length numeric assignment codes as TLS and IPSEC use should be
verboten and the text based registries merged into one common registry of
labels for all new assignments. So the SHA-3-256 text label would be the
basis for the URI form used by XML signature. The per-protocol registries
should then be closed to new registrations so that all crypto labels are
assigned from one registry on a first-come first-served basis.

One change that should be made is to separate out the assignment of code
points from the endorsement of code points. Assigning a code point should
mean no more than it won't be assigned for a different purpose. It should
not imply any form of endorsement.

Endorsement may be limited to an expert reviewer noting that a particular
document or institution should be considered the authoritative source of
the specification explaining a code point or it could be an IETF standards
action.


The IAB should be tasked with ways to reduce the number of separate
registries required. Reuse of an existing registry is almost always better
than defining a new one.

Coinsider the SMTP protocol. Even though the URI form for SMTP is actually
mailto:, it is obvious that the SMTP URI scheme could not possibly be
assigned to a different protocol without major confusion at the very least.
The same argument goes for .well-known.

Rather than have three separate registries and attempt to avoid conclusions
it would be better to have one registry for text labels so that
registration of a label automatically reserves the corresponding
.well-known, URI and SRV code points in one go.


If we took this to an extreme there would be only one registry of text
labels and the entries would describe the use(s) for which the label has
been assigned. If a label is assigned as an application protocol identifier
then it can't be a content type or an encryption algorithm. But it is
probably just sufficient to prune down the registries somewhat.

Finally, we need to change the assignment process for OIDs because it is
really hard to get a bunch of companies to agree on a draft if the OID
assignment is off one corporate arc. Rather than assigning arcs in the open
registration arc only to companies, they should be assigned to projects.

So in my Privacy Hardened scheme, I am going to need to define a new ASN.1
structure (puke) and some extension OIDs. In the current scheme I would
have to cut them off the Comodo arc (which makes getting buy in from
Symantec, etc. etc. harder) or my personal arc (Default Deny Security).
Both of which are likely to end up having all the entries renamed if the
proposal becomes an IETF working group. If instead I get a new arc for the
project, I can then hand over change control over the arc along with the
rest of the protocol if it is accepted by the IETF (or the same for W3C or
OASIS). If the project is not taken up then I keep control.


The objective of all these reforms is to emphasize that the role of the
IANA is to facilitate innovation, avoid unintentional collisions and not to
enforce control. It is not possible to prevent a use of the Internet by
withholding an assignment.



-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jan 3, 2014 at 12:36 PM, IETF Chair <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:chair@ietf.org" target=3D"_blank">chair@ietf.org</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
In this article I wanted to highlight an important but often hidden part in=
 the IETF ecosystem: Internet Assigned Numbers Authority (IANA). =A0What is=
 IANA, how does it work, how is it related to the IETF, and how has it evol=
ved over time? How will it evolve in the future, and how can you participat=
e in the discussion?<br>
</blockquote><div><br></div><div>I think that the article needs to go back =
to some basic principles.</div><div><br></div><div>The whole point of the e=
nd-to-end architecture was that it enabled innovation and diversity. In par=
ticular it was possible to add applications to the Internet without going t=
o some central authority to ask permission. The IETF is not in the business=
 of deciding how people use the Internet except to the extent that doing so=
 may harm others, it is only in the business of setting standards that enab=
le interoperability.</div>
<div><br></div><div><br></div><div>So when we look at the role of IANA, the=
re are different concerns for different protocol layers. The concerns at th=
e IP layer are different to the concerns of DNS which are in turn different=
 to those of applications.</div>
<div><br></div><div>At the IP layer compact representation is vital and cod=
e points are a very scarce resource by necessity. Allocation has to be care=
fully considered because they potentially affect the routers at the core of=
 the Internet which are very difficult to change.</div>
<div><br></div><div>The DNS is an interesting case because the number of co=
de points is generous but finite. Less than 1% of code points are assigned.=
</div><div><br></div><div><br></div><div>At the application layer we have t=
he curious situation that port allocations are essentially exhausted so we =
use ports 80 and 443 for everything. But in most cases the general rule sho=
uld be that application protocols should be designed so that code points ar=
e not a constrained resource and the primary purpose of assignment should b=
e to prevent ambiguity arising and to provide as much documentation as is p=
ossible.</div>
<div><br></div><div>We have learned to our cost that X-Headers don&#39;t wo=
rk. Telling people to go experiment in a sandbox and then come to the IETF =
when the protocol is ready and get issued a real code point has not worked.=
 It guarantees we end up with multiple code points.</div>
<div><br></div><div>The status quo for most registries is that they are per=
missive but there is a large amount of difference in the criteria and there=
 are experts involved doing reviews for some systems but not others. There =
is a general lack of consistency. A standards organization should look for =
consistency.</div>
<div><br></div><div><br></div><div>One important change is that every futur=
e application protocol proposal should be required to have an effectively u=
nlimited code space for assignment. Another is that application protocols s=
hould be required to reuse code points from common registries rather than d=
efine their own.</div>
<div><br></div><div>At the moment we have separate crypto registries for TL=
S, IPSEC, PEM, PKIX and XML Digital Signature. The JOSE folk want to create=
 another. There should be a policy that tells people from the start that th=
ere will be no new crypto registries.</div>
<div><br></div><div>Fixed length numeric assignment codes as TLS and IPSEC =
use should be verboten and the text based registries merged into one common=
 registry of labels for all new assignments. So the SHA-3-256 text label wo=
uld be the basis for the URI form used by XML signature. The per-protocol r=
egistries should then be closed to new registrations so that all crypto lab=
els are assigned from one registry on a first-come first-served basis.</div=
>
<div><br></div><div>One change that should be made is to separate out the a=
ssignment of code points from the endorsement of code points. Assigning a c=
ode point should mean no more than it won&#39;t be assigned for a different=
 purpose. It should not imply any form of endorsement.</div>
<div><br></div><div>Endorsement may be limited to an expert reviewer noting=
 that a particular document or institution should be considered the authori=
tative source of the specification explaining a code point or it could be a=
n IETF standards action.</div>
<div><br></div><div><br></div><div>The IAB should be tasked with ways to re=
duce the number of separate registries required. Reuse of an existing regis=
try is almost always better than defining a new one.</div><div><br></div>
<div>Coinsider the SMTP protocol. Even though the URI form for SMTP is actu=
ally mailto:, it is obvious that the SMTP URI scheme could not possibly be =
assigned to a different protocol without major confusion at the very least.=
 The same argument goes for .well-known.</div>
<div><br></div><div>Rather than have three separate registries and attempt =
to avoid conclusions it would be better to have one registry for text label=
s so that registration of a label automatically reserves the corresponding =
.well-known, URI and SRV code points in one go.</div>
<div><br></div><div><br></div><div>If we took this to an extreme there woul=
d be only one registry of text labels and the entries would describe the us=
e(s) for which the label has been assigned. If a label is assigned as an ap=
plication protocol identifier then it can&#39;t be a content type or an enc=
ryption algorithm. But it is probably just sufficient to prune down the reg=
istries somewhat.</div>
<div><br></div><div>Finally, we need to change the assignment process for O=
IDs because it is really hard to get a bunch of companies to agree on a dra=
ft if the OID assignment is off one corporate arc. Rather than assigning ar=
cs in the open registration arc only to companies, they should be assigned =
to projects.</div>
<div><br></div><div>So in my Privacy Hardened scheme, I am going to need to=
 define a new ASN.1 structure (puke) and some extension OIDs. In the curren=
t scheme I would have to cut them off the Comodo arc (which makes getting b=
uy in from Symantec, etc. etc. harder) or my personal arc (Default Deny Sec=
urity). Both of which are likely to end up having all the entries renamed i=
f the proposal becomes an IETF working group. If instead I get a new arc fo=
r the project, I can then hand over change control over the arc along with =
the rest of the protocol if it is accepted by the IETF (or the same for W3C=
 or OASIS). If the project is not taken up then I keep control.</div>
<div><br></div><div><br></div><div>The objective of all these reforms is to=
 emphasize that the role of the IANA is to facilitate innovation, avoid uni=
ntentional collisions and not to enforce control. It is not possible to pre=
vent a use of the Internet by withholding an assignment.=A0</div>
<div><br></div><div><br></div></div><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0116049e7c232604ef1ef5aa--

From hallam@gmail.com  Fri Jan  3 22:42:27 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3659D1ACC88 for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 22:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gmVz4lQQubrH for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 22:42:25 -0800 (PST)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 97E131ACC87 for <ietf@ietf.org>; Fri,  3 Jan 2014 22:42:25 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id b13so13941959wgh.6 for <ietf@ietf.org>; Fri, 03 Jan 2014 22:42:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0GlnM7XYvkaTjPIE6KSoy5DCtX0PZdZVgUUeE+ZaUcI=; b=Us5yUquy0NSFwi0TIqItZ3D4K7A4CRhyLGE3P/OBoy9YGCVqELBanFZS1t6aOLpDnm 27V2c2rQjzxRi1d8gLle02E5DNvqn74g2ZgY2YIdao03pNexlzbONxAMK5umtl0sNwSj ZeIigpyUp0fCbGOieWHqqN1RlwCmNImmDrV1qgo51/003AflHMbIpJCKhWSDubhqulqr gsWinGuOornn34E/0k++FPvcs67xrFVcwWtNvyv21tF1h/yjfj3fLzJphxdMvAfMFt8D xCyuCLi4C84fETCZKdnj1wLTP5YMTjGIDCFhcdoQrRRQ77SQr9V6p4JIs67BIRg/tDis xkHw==
MIME-Version: 1.0
X-Received: by 10.180.211.141 with SMTP id nc13mr3852944wic.1.1388817737714; Fri, 03 Jan 2014 22:42:17 -0800 (PST)
Received: by 10.194.243.136 with HTTP; Fri, 3 Jan 2014 22:42:17 -0800 (PST)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346A1@EXMB01CMS.surrey.ac.uk>
References: <26734.1388770438@erosen-linux> <52C75808.70701@gmail.com> <290E20B455C66743BE178C5C84F1240847E63346A1@EXMB01CMS.surrey.ac.uk>
Date: Sat, 4 Jan 2014 01:42:17 -0500
Message-ID: <CAMm+LwgsyMbDG6vWp6WNrY3_Og8fwDF-hWb57kVMMieoQs2n+w@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Phillip Hallam-Baker <hallam@gmail.com>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=001a11c3709cea142f04ef1f5371
Cc: John C Klensin <john-ietf@jck.com>, erosen@cisco.com, "Stewart Bryant \(stbryant\)" <stbryant@cisco.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 06:42:27 -0000

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

On Fri, Jan 3, 2014 at 7:42 PM, <l.wood@surrey.ac.uk> wrote:

> Sigh. That is in itself a political stance.
>
>
So is the Internet.

As well as murdering his uncle a couple of weeks ago, the tyrant running
North Korea murdered 80 people for having ipods and would doubtless have
done the same for Internet.



-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jan 3, 2014 at 7:42 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:l.wood=
@surrey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
Sigh. That is in itself a political stance.<br><br></blockquote><div><br></=
div><div>So is the Internet.</div><div><br></div><div>As well as murdering =
his uncle a couple of weeks ago, the tyrant running North Korea murdered 80=
 people for having ipods and would doubtless have done the same for Interne=
t.</div>
<div>=A0</div></div><div><br></div><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c3709cea142f04ef1f5371--

From hsantos@isdg.net  Fri Jan  3 23:08:51 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E7531ACC7E for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 23:08:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.08
X-Spam-Level: 
X-Spam-Status: No, score=-101.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUKKtvap7RDA for <ietf@ietfa.amsl.com>; Fri,  3 Jan 2014 23:08:48 -0800 (PST)
Received: from mail.catinthebox.net (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7F63D1ACC7D for <ietf@ietf.org>; Fri,  3 Jan 2014 23:08:48 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3324; t=1388819311; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=PeRqX2M9Q/+mM2+pgSCDTb3oN+4=; b=Ztzpnu/ttgi01wt5Gjgt zk/2kmAVO/fPSzKNd6ByscNN0l2Nxwstzxdrv2uOW1dcEv/9a3mttTR4ZKcgkW8/ pFMFmsW4LY3/yok6doPuJPXFBkomQ6sXBDffIBQqrB7+Fa8+cqfWqOp3sTo4x9fE oi4djZrLnDmHI0a6TRATirw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 04 Jan 2014 02:08:31 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2396791192.24875.5200; Sat, 04 Jan 2014 02:08:30 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3324; t=1388818763; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=mraFMbM dYlcPGSdnnphgaoie8LZEgdqu6+x8wqzoqNk=; b=f9XQc5GGBOhM0g7EpIbttb0 ujx4Wbh+izIM3ylFsdeJmqdcy34rDxs5W/bPO459lsYbhHvKUKf5rUY2Cuzt1Twr 0M7F/63XfoZ3VayxgMXzUE94jRkbRBN5/RTQHngpD33hvSmCo3t2rSlXZuD+VIlZ wIiWCBnbL+sDSxJjpHJM=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 04 Jan 2014 01:59:23 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1843109489.9.6480; Sat, 04 Jan 2014 01:59:22 -0500
Message-ID: <52C7B371.7050500@isdg.net>
Date: Sat, 04 Jan 2014 02:08:33 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com>, <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie>
In-Reply-To: <52C761A6.8060800@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 07:08:51 -0000

Here is my "paraphrase" or "interpretation:"

     Please remember to do your homework when it comes to ethical and
     societal design considerations, if any. Authors SHOULD ALWAYS
     be prepared to answer any questions related to such design
     considerations.

I think the problem is the lack of a section or "checklist" that one 
should be considering - ALWAYS.  The RFC templates should be a section 
with a baseline description:

     The author(s) of this document does not believe there are "pervasive
     monitoring" related attacks [RFCXXXX] in this specification.

Having this in the templates is a form of a "checklist" not only the 
authors can not avoid, but also reviewers.   At the end of the day, we 
don't want any possible considerations to "fall through" the 
proverbial "cracks."  Reviewers, participants, implementers need to be 
able to put the authors to the task to do their homework.

Ideally, "ethical IETF engineers" don't need these type of reminders, 
but it helps to have a "checklist."

My "Opinion"


On 1/3/2014 8:19 PM, Stephen Farrell wrote:
>
>
>
> On 01/04/2014 01:10 AM, Bjoern Hoehrmann wrote:
>> * Stephen Farrell wrote:
>>> On 01/04/2014 12:45 AM, l.wood@surrey.ac.uk wrote:
>>>> "Please include a full explanation of how pervasive monitoring is
>>>> mitigated in this protocol. If this protocol is not fully
>>>> cryptographically secure to defeat  pervasive monitoring, explain why
>>>> not."
>>>
>>> What are you quoting? That text is *not* part of the
>>> draft, nor do I recall it being sent to the list by
>>> anyone.
>>>
>>> Surely inventing quotes is not fair game here?
>>
>> The quote marks indicate that the text is a paraphrase; Lloyd Wood re-
>> states the meaning, or a possible interpretation, of the text, likely
>> to illustrate a problem with the text. This is a common discourse tech-
>> nique and should be entirely obvious; nothing unfair about it.
>>
>> If it does not reflect the intended meaning of the text, then there are
>> various ways to make that very explicit in the text, for instance, it
>> could literally say that "full explanation of how pervasive monitoring
>> is mitigated" is not expected or required. Then it should be obvious
>> that the above is not a permissable paraphrase.
>
> The text (I hate to bring it up, seems almost unfashionable;-),
> says:
>
>     Those developing IETF specifications need to be able to describe how
>     they have considered pervasive monitoring, and, if the attack is
>     relevant to the work to be published, be able to justify related
>     design decisions.  This does not mean a new "pervasive monitoring
>     considerations" section is needed in IETF documentation.  It means
>     that, if asked, there needs to be a good answer to the question "is
>     pervasive monitoring relevant to this work and if so how has it been
>     addressed?"
>
> Lloyd's "paraphrase" is entirely unlike the actual text. His
> quote marks, are, like his argument, entirely bogus. (And not
> even funny, which is often a redeeming quality of Lloyd's
> posts:-) Given that there seems to be a trend to ignore the
> actual text, and that that I've already commented on that, I
> think yes, his supposed quote is out of order. Perhaps you
> don't, and that's fine, but I do.
>
> S.
>
>
>>
>
>

-- 
HLS



From jari.arkko@piuha.net  Sat Jan  4 00:04:01 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F621ACCF8; Sat,  4 Jan 2014 00:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p0YuVoO-nQIV; Sat,  4 Jan 2014 00:04:01 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 93C2D1ACCE6; Sat,  4 Jan 2014 00:04:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 6C8892CC61; Sat,  4 Jan 2014 10:03:51 +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 cgdNW7Z8ujvw; Sat,  4 Jan 2014 10:03:50 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4291E2CC5D; Sat,  4 Jan 2014 10:03:50 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20140103153834.0c6591a8@elandnews.com>
Date: Sat, 4 Jan 2014 09:03:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7540B48A-7E50-400F-BF41-E4645BF58427@piuha.net>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com> <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com> <6.2.5.6.2.20140102224801.0b454e28@elandnews.com> <A8AE5CC5-E5F4-47E3-852F-DE21783FEAF0@ieca.com> <6.2.5.6.2.20140103153834.0c6591a8@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1510)
Cc: Ines Robles <mariainesrobles@googlemail.com>, IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 08:04:01 -0000

I think the text you SM and Russ discussed for the "global" issue is =
fine, and supported by the discussion. (Although I have to say, the word =
"whole" later in that section already did it for me; I did not consider =
the fix critical. But I think the document is better with the fix.)

>   3. IETF participants devise solutions for the global Internet that
>      meet the needs of diverse technical and operational environments.

I'm also happy to have the IPR rules referenced, again as discussed by =
you SM and Russ and supported by discussion.

> Here is text which can be inserted in the last paragraph of Section 2:
>=20
>  We follow the intellectual property guidelines outlined in BCP 79.
>  IETF participants read the relevant Internet-Drafts =85


And I think the suggestion from Dave was also worthwhile and supported =
by discussion:

>      ... All participants, particularly those with English as a first
>      language, attempt to accommodate the needs of other participants
>      by communicating clearly, including speaking slowly and limiting
>      the use of slang. =85

Finally, you should use data tracker URLs as Russ suggested.

I do think though that for the rest, we are beyond the stage where =
additional editing provides useful results. I think SM's text is good, =
easily understandable, and ready to go.=20

Jari


From jari.arkko@piuha.net  Sat Jan  4 00:19:10 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7C631AD7C5 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 00:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sBMAYI99JazT for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 00:19:09 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E03CA1ACC8A for <ietf@ietf.org>; Sat,  4 Jan 2014 00:19:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 113232CC61; Sat,  4 Jan 2014 10:19:01 +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 k-OiYOemogfd; Sat,  4 Jan 2014 10:18:59 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5A94B2CC5D; Sat,  4 Jan 2014 10:18:59 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IANA blog article
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <55DCB0F3-2ACD-44CB-B6FC-68ACC2A342DD@virtualized.org>
Date: Sat, 4 Jan 2014 09:19:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <37BE68C3-3302-4B53-A9EC-04DDEF507A11@piuha.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <55DCB0F3-2ACD-44CB-B6FC-68ACC2A342DD@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 08:19:11 -0000

Hi David,

and thanks for your comments. Some responses inline:

> - Perhaps it is merely your shorthand, but I've found that saying =
"IANA" as if it is a discrete entity rather than a set of functions =
performed by a contractor (or contractors) tends to confuse things.  For =
example, you say "... IANA then makes the actual allocations ...".  In =
actuality (as you note later on), ICANN, acting as the current IANA =
"protocol parameters function" operator makes the allocation.=20

Agreed=85 (I changed this in the article, btw.)

> - As I suspect you're aware, ICANN, as the IANA function operator, =
performs a couple of other administrative duties that are considered (at =
least in the context of the IANA functions contract between the US Dept. =
of Commerce NTIA and ICANN, see =
http://www.ntia.doc.gov/files/ntia/publications/sf_26_pg_1-2-final_award_a=
nd_sacs.pdf) outside of the protocol parameter, root zone management, =
and top-level Internet numbers allocation functions, i.e., =
administration of the .ARPA top-level domain and administration of the =
.INT top-level domain. Given past experiences, I hope these other =
functions are kept in mind as people think/talk about future frameworks =
associated with IANA functions evolution.

Ack.

> - Some nits in the sentence "For instance, 2000, the IETF and ICANN =
signed a contract about the protocol parameters aspect of the IANA =
function (RFC 2560)": I presume you meant "in 2000" and "RFC 2860".

Oops. Corrected.

> Also, as opposed to the IANA functions contract between the USG and =
ICANN referenced above, 2860 is not a contract but a "memorandum of =
understanding" -- I've been told by lawyers that the distinction is =
important.
>=20
> - I probably wouldn't say the system of IANA functions have "grown up" =
as that suggests no further growth is necessary/needed.  I'd agree that =
the system is maturing, however I believe still has a ways to go, albeit =
primarily in non-technical areas. In particular, it will be nice to =
clarify the current ... ambiguity, at least in the eyes of some, =
regarding the authority over IANA functions.

I do agree that "grown up" should not be taken as "evolution is done". =
Further growth and evolution is indeed needed.=20

Jari


From jari.arkko@piuha.net  Sat Jan  4 00:29:41 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A831D1AD7C5 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 00:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZZx6oY70V1M for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 00:29:39 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5B38C1ACCE6 for <ietf@ietf.org>; Sat,  4 Jan 2014 00:29:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8401A2CC61; Sat,  4 Jan 2014 10:29:31 +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 7cImcMPfvfAk; Sat,  4 Jan 2014 10:29:30 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3C82F2CC5D; Sat,  4 Jan 2014 10:29:28 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IANA blog article
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com>
Date: Sat, 4 Jan 2014 09:29:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 08:29:41 -0000

> I think that the article needs to go back to some basic principles.
>=20
> The whole point of the end-to-end architecture was that it enabled =
innovation and diversity. In particular it was possible to add =
applications to the Internet without going to some central authority to =
ask permission.

I very much agree with this principle. Although maybe that's a topic for =
another blog article or discussion=85 my article was mostly in the =
context of managing registries when we have already decided that it is =
one of those rare cases where a registry is needed, and have already =
decided what the rules and form of the registry is.

The wonderful thing about the Internet is indeed that most things do not =
need central control or registry.

A couple of responses below for the registry design question:

> We have learned to our cost that X-Headers don't work. Telling people =
to go experiment in a sandbox and then come to the IETF when the =
protocol is ready and get issued a real code point has not worked. It =
guarantees we end up with multiple code points.

I think I agree with this problem statement.

> The status quo for most registries is that they are permissive but =
there is a large amount of difference in the criteria and there are =
experts involved doing reviews for some systems but not others. There is =
a general lack of consistency. A standards organization should look for =
consistency.

I think we are trying. Can you be more specific about areas where there =
is lack of consistency? We can try to improve rules about specific IANA =
registries, provide more guidance to experts, etc. if we are not =
performing well enough in some area.

> One important change is that every future application protocol =
proposal should be required to have an effectively unlimited code space =
for assignment.

Agree.

> Another is that application protocols should be required to reuse code =
points from common registries rather than define their own.
>=20
> At the moment we have separate crypto registries for TLS, IPSEC, PEM, =
PKIX and XML Digital Signature. The JOSE folk want to create another. =
There should be a policy that tells people from the start that there =
will be no new crypto registries.

Here I am not so sure. Registries for adding specific crypto algorithms =
are not merely number allocations; they go with specifications and code =
that actually runs, say, AES on IPsec or AES on TLS. It is not entirely =
clear to me that crypto across different protocols and use cases should =
proceed in lock step. And even if it were useful, it is a difficult =
change to make retroactively, when the code points in different =
protocols started out differently.

But maybe I'm misunderstanding your suggestion.

> Finally, we need to change the assignment process for OIDs because it =
is really hard to get a bunch of companies to agree on a draft if the =
OID assignment is off one corporate arc. Rather than assigning arcs in =
the open registration arc only to companies, they should be assigned to =
projects.
>=20
> So in my Privacy Hardened scheme, I am going to need to define a new =
ASN.1 structure (puke) and some extension OIDs. In the current scheme I =
would have to cut them off the Comodo arc (which makes getting buy in =
from Symantec, etc. etc. harder) or my personal arc (Default Deny =
Security). Both of which are likely to end up having all the entries =
renamed if the proposal becomes an IETF working group. If instead I get =
a new arc for the project, I can then hand over change control over the =
arc along with the rest of the protocol if it is accepted by the IETF =
(or the same for W3C or OASIS). If the project is not taken up then I =
keep control.

This is interesting, and I could see a use case for it.

> The objective of all these reforms is to emphasize that the role of =
the IANA is to facilitate innovation, avoid unintentional collisions and =
not to enforce control. It is not possible to prevent a use of the =
Internet by withholding an assignment.=20

This I agree with.

Jari


From paf@frobbit.se  Sat Jan  4 01:31:49 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A891ACCF2 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 01:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmJ5Cxk7C6ud for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 01:31:48 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 589431A8034 for <ietf@ietf.org>; Sat,  4 Jan 2014 01:31:48 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::5984:3598:5ce5:82f8] (unknown [IPv6:2a02:80:3ffc:0:5984:3598:5ce5:82f8]) by mail.frobbit.se (Postfix) with ESMTPSA id 9D5AB211F2; Sat,  4 Jan 2014 10:31:36 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_A82333EE-E608-4422-A7ED-99CF375A8ED0"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IANA blog article
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
Date: Sat, 4 Jan 2014 10:31:08 +0100
Message-Id: <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 09:31:49 -0000

--Apple-Mail=_A82333EE-E608-4422-A7ED-99CF375A8ED0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 4 jan 2014, at 09:29, Jari Arkko <jari.arkko@piuha.net> wrote:

>> One important change is that every future application protocol =
proposal should be required to have an effectively unlimited code space =
for assignment.
>=20
> Agree.

I do not agree regarding the term "unlimited".

What is needed is that the specification do have a consequence analysis =
regarding expansion of use.

   Patrik


--Apple-Mail=_A82333EE-E608-4422-A7ED-99CF375A8ED0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD4DBQFSx9TcrMabGguI180RAvQWAJ9sj7iCc55g39QjLkCdOasMSEiwHACWMRbv
lzelOmgA98cxKxxNzXENCg==
=Pqt0
-----END PGP SIGNATURE-----

--Apple-Mail=_A82333EE-E608-4422-A7ED-99CF375A8ED0--

From john-ietf@jck.com  Sat Jan  4 04:11:00 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 219EB1ADF39 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 04:11:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.838
X-Spam-Level: 
X-Spam-Status: No, score=-2.838 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nelttQQNj6af for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 04:10:57 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9961ACCD8 for <ietf@ietf.org>; Sat,  4 Jan 2014 04:10:57 -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 1VzQ3x-000Ozk-Ck; Sat, 04 Jan 2014 07:10:45 -0500
Date: Sat, 04 Jan 2014 07:10:40 -0500
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IANA blog article
Message-ID: <0BF989509DD2BA5AD9CD9490@JcK-HP8200.jck.com>
In-Reply-To: <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 12:11:00 -0000

--On Saturday, January 04, 2014 10:31 +0100 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@frobbit.se> wrote:

>=20
> On 4 jan 2014, at 09:29, Jari Arkko <jari.arkko@piuha.net>
> wrote:
>=20
>>> One important change is that every future application
>>> protocol proposal should be required to have an effectively
>>> unlimited code space for assignment.
>>=20
>> Agree.
>=20
> I do not agree regarding the term "unlimited".
>=20
> What is needed is that the specification do have a consequence
> analysis regarding expansion of use.

At least if it isn't unlimited, but I agree with Patrik.

Remember that the most important single protocol value space we
have is one that we've gotten wrong (at least) three times,
twice requiring complete replacement of the relevant protocols
themselves to expand the space (even though, especially the
first time, there were other reasons to do so).

Remember:
	-- We will never need more than 254 hosts.
	-- We can expand that a bit by using an IMP number/ host
		number pair.
	-- A 32-bit range will always be enough, even if we
		break it into octet-boundary Classes and thereby limit
		how much of it can actually be used.
	-- A prefix model and bit boundaries will save us for a
		while.

and, more recently,

	-- A 128-bit range will be enough forever, even if we
		allocate it in ways that make the actual number of
		usable addresses much smaller.

Maybe we are right about the last one, maybe not.  But any
requirement of "unlimited" would essentially require
variable-length addresses (or variable-length parameter fields
more generally, and that has always been considered a major
architectural decision.

So, yes, analysis of how big the space really is and needs to be
and what the consequences are if it turns out to be not
"unlimited" enough.

   john


From adrian@olddog.co.uk  Sat Jan  4 04:16:47 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D593F1ADF4F; Sat,  4 Jan 2014 04:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AortstPeZRsf; Sat,  4 Jan 2014 04:16:46 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 420861ADF39; Sat,  4 Jan 2014 04:16:46 -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 s04CGb9F021218; Sat, 4 Jan 2014 12:16:38 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04CGZit021190 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 4 Jan 2014 12:16:36 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-tp-p2mp-framework-05.txt> (A Framework for Point-to-Multipoint MPLS in Transport Networks) to Informational RFC
Date: Sat, 4 Jan 2014 12:16:29 -0000
Message-ID: <007201cf0946$d2517c30$76f47490$@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: Ac8JRrPrn/n8O7gdQU+Zn0x2e4iDrA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 12:16:48 -0000

So this doesn't get lost, here comments I sent to the authors before starting
IETF last call...

> Dan will probably want to update his coordinates.
>
> ---
>
> You don't need to be so enthusiastic with your acronyms in Section 1.2
> The following are "well known" according to
> http://www.rfc-editor.org/rfc-style-guide/abbrev.expansion.txt
>
>   GMPLS   Generalized MPLS
>   LDP     Label Distribution Protocol
>   MPLS    Multiprotocol Label Switching
>
> There is a serial comma missing from
>    OAM     Operations, Administration and Maintenance
> The comma is also missing in your text.
>
> ---
>
> In Section 1.3 you say
>
>   There is no definition for MPLS TE-LSP support of multipoint-to-
>   multipoint connectivity and none is anticipated.
>
> Without opening up a discussion of whether what you cay is true, can you
> say why it is relevant? Perhaps "This document is limited to a 
> discussion of point-to-multipoint function and does not discuss 
> multipoint-to-multipoint support." You might also move this to Section
> 1.1.

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
> Sent: 02 January 2014 15:17
> To: IETF-Announce
> Cc: mpls@ietf.org
> Subject: [mpls] Last Call: <draft-ietf-mpls-tp-p2mp-framework-05.txt> (A
> Framework for Point-to-Multipoint MPLS in Transport Networks) to Informational
> RFC
> 
> 
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'A Framework for Point-to-Multipoint MPLS in Transport Networks'
>   <draft-ietf-mpls-tp-p2mp-framework-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 2014-01-16. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
>    The Multiprotocol Label Switching Transport Profile is the common set
>    of MPLS protocol functions defined to enable the construction and
>    operation of packet transport networks.  The MPLS-TP supports both
>    point-to-point and point-to-multipoint transport paths.  This
>    document defines the elements and functions of the MPLS-TP
>    architecture applicable specifically to supporting point-to-
>    multipoint transport paths.
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-p2mp-framework/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-p2mp-framework/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From paf@frobbit.se  Sat Jan  4 04:25:10 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A17B11ADF5F for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 04:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEL11JpNxQDh for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 04:25:09 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 97B2D1ADF5C for <ietf@ietf.org>; Sat,  4 Jan 2014 04:25:09 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::5984:3598:5ce5:82f8] (unknown [IPv6:2a02:80:3ffc:0:5984:3598:5ce5:82f8]) by mail.frobbit.se (Postfix) with ESMTPSA id 0CBFA20531; Sat,  4 Jan 2014 13:25:00 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_06E1D843-73FF-4A10-A4C8-1B67F914BC74"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IANA blog article
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <0BF989509DD2BA5AD9CD9490@JcK-HP8200.jck.com>
Date: Sat, 4 Jan 2014 13:24:57 +0100
Message-Id: <B7A8062F-71D7-4F96-8161-14BAF36DEFE4@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <0BF989509DD2BA5AD9CD9490@JcK-HP8200.jck.com>
To: John Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 12:25:10 -0000

--Apple-Mail=_06E1D843-73FF-4A10-A4C8-1B67F914BC74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 4 jan 2014, at 13:10, John C Klensin <john-ietf@jck.com> wrote:

> But any
> requirement of "unlimited" would essentially require
> variable-length addresses (or variable-length parameter fields
> more generally, and that has always been considered a major
> architectural decision.

Exactly why I object to the term.

You John explain why very well and also point out the bad decisions we =
made that we should learn from -- including the IPv6 decisions that I am =
extremely nervous over. Where early players once again get much larger =
address space than those arriving late.

  Patrik


--Apple-Mail=_06E1D843-73FF-4A10-A4C8-1B67F914BC74
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSx/2ZrMabGguI180RAp/aAJ4lqY5WBLU0fIZ7QHBCzSu6FRyocgCfQsVw
FNNSg9OiyJVJpNi1Gg/Mapc=
=JL8Z
-----END PGP SIGNATURE-----

--Apple-Mail=_06E1D843-73FF-4A10-A4C8-1B67F914BC74--

From loa@pi.nu  Sat Jan  4 04:32:27 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A549D1ADF38; Sat,  4 Jan 2014 04:32:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7o221jWLVd0; Sat,  4 Jan 2014 04:32:26 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 084F51ADE8A; Sat,  4 Jan 2014 04:32:26 -0800 (PST)
Received: from [192.168.1.5] (unknown [112.208.5.107]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id F2FF7180150F; Sat,  4 Jan 2014 13:32:13 +0100 (CET)
Message-ID: <52C7FF47.6080705@pi.nu>
Date: Sat, 04 Jan 2014 20:32:07 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>,  draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
In-Reply-To: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 12:32:27 -0000

Russ,

I never thought about this as an update to RFC 5921. If we publish
this document as is, every syllable of RFC 5921 remains unchanged.

This is hardly an update.

/Loa


On 2014-01-04 01:30, Russ Housley wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-mpls-tp-p2mp-framework-05
> Reviewer: Russ Housley
> Review Date: 2014-01-02
> IETF LC End Date: 2014-01-16
> IESG Telechat date: Unknown
>
> Summary:  Ready for publication.
>
>
> Question:
>
> Should this document be an update to the MPLS-TP Framework (RFC 5921)?
> I am not sure.  RFC 5921 does make it clear that it covers only point-
> to-point transport paths.  The answer may be further complicated by
> the fact that RFC 5921 is joint work with the ITU-T.
>
>
> Major Concerns:  None.
>
>
> Minor Concerns:  None.
>
>
> Other Comments:
>
> In the first sentence of Section 1, please define MPLS-TP as follows:
> OLD:
>     The Multiprotocol Label Switching Transport Profile is the ...
> NEW:
>     The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...
>
> Please add TE-LSP to the terms defined in Section 1.2.
>
> In Section 5.1, I cannot understand this sentence:
>>
>>   Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>>   recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>>   interactions.
>>
> I think that the references are getting in the way.  I think the
> message is: "the definitions of P2MP and GMPLS recovery do not
> explicitly cover their interactions."  If I am correct, then some
> commas need to be removed.
>
> The phrase "MPLS Transport Profile" appears many places, and it would
> be easier if they were replaces with "MPLS-TP" for consistency.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From adrian@olddog.co.uk  Sat Jan  4 05:28:34 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3051ADF7B; Sat,  4 Jan 2014 05:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5mVbOktUCKP; Sat,  4 Jan 2014 05:28:32 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id 80A8A1ADF85; Sat,  4 Jan 2014 05:28:32 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04DSN0O024623; Sat, 4 Jan 2014 13:28:23 GMT
Received: from 950129200 (AGrenoble-651-1-487-66.w90-42.abo.wanadoo.fr [90.42.183.66]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s04DSI4X024598 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 4 Jan 2014 13:28:22 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Russ Housley'" <housley@vigilsec.com>, <draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org>
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
In-Reply-To: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com>
Subject: RE: Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
Date: Sat, 4 Jan 2014 13:28:20 -0000
Message-ID: <008d01cf0950$d86d2920$89477b60$@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: AQFtY8DzS5vZJbZaAyHEQlLbsO5TQ5s3zxZQ
Content-Language: en-gb
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 13:28:34 -0000

Hi Russ,

Thanks for the review.

> Question:
> 
> Should this document be an update to the MPLS-TP Framework (RFC 5921)?
> I am not sure.  RFC 5921 does make it clear that it covers only point-
> to-point transport paths.  The answer may be further complicated by
> the fact that RFC 5921 is joint work with the ITU-T.

I don't think so.
That is, it is perfectly acceptable to build a P2P MPLS-TP system and that
system could be built on protocol solutions that do not include P2MP support.

As you say, 5921 explicitly says:

   This document defines the subset of the MPLS-TP applicable in general
   and to point-to-point transport paths.  The remaining subset,
   applicable specifically to point-to-multipoint transport paths, is
   outside the scope of this document.

...so an "updates" relationship would render this statement doubtful.

I'm pretty comfortable with the documents being separate.

> Other Comments:
> 
> In the first sentence of Section 1, please define MPLS-TP as follows:
> OLD:
>    The Multiprotocol Label Switching Transport Profile is the ...
> NEW:
>    The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...

Sure.

> Please add TE-LSP to the terms defined in Section 1.2.

Sure.

> In Section 5.1, I cannot understand this sentence:
> >
> >  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
> >  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
> >  interactions.
> >
> I think that the references are getting in the way.  I think the
> message is: "the definitions of P2MP and GMPLS recovery do not
> explicitly cover their interactions."  If I am correct, then some
> commas need to be removed.

Yes, you're right. And a minor rewrite could make this even clearer.

> The phrase "MPLS Transport Profile" appears many places, and it would
> be easier if they were replaces with "MPLS-TP" for consistency.

OK



From jnc@mercury.lcs.mit.edu  Sat Jan  4 05:43:56 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9461ADF86 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 05:43:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8XO8I7nfqgb2 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 05:43:54 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 403141ADF7A for <ietf@ietf.org>; Sat,  4 Jan 2014 05:43:53 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 2E3FD18C12B; Sat,  4 Jan 2014 08:43:46 -0500 (EST)
To: ietf@ietf.org
Subject: Re: IANA blog article
Message-Id: <20140104134346.2E3FD18C12B@mercury.lcs.mit.edu>
Date: Sat,  4 Jan 2014 08:43:46 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 13:43:56 -0000

    > From: John C Klensin <john-ietf@jck.com>

Minor historical aside:

    > Remember that the most important single protocol value space we have is
    > one that we've gotten wrong (at least) three times
    > ...
    >   -- We will never need more than 254 hosts.
    >   -- We can expand that a bit by using an IMP number/ host
    >           number pair.
    >   -- A 32-bit range will always be enough,

Actually (ironically), technically the so-called 'long IMP leader' had the
exact same number of address bits as IPv4 (i.e. 32 bits). (There was an 8-bit
'network number' field, althought it was never used.) See:

  http://www.chiappa.net/~jnc/tech/arpapkt.html

	Noel

From scott.brim@gmail.com  Sat Jan  4 06:56:59 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3CD81ADFDF for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 06:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2fIJTb95bWd for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 06:56:58 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 6928C1ADFB6 for <ietf@ietf.org>; Sat,  4 Jan 2014 06:56:58 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id gq1so16680570obb.17 for <ietf@ietf.org>; Sat, 04 Jan 2014 06:56:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RgYjCuZukRHVMaW7A3flMW7ANIq8rkabhLuZth9DkYQ=; b=Z+mGuEHnh3zwbQ8CnXMgtrJ55nxNve48sn5R0JS6GDsig896aT1BFw257EaLYR+4Ie E3f1bxsUl5E/c2JJer13L6BwNQ4+jUW8i/tJxByvufjugSfvAtb2ngSVLpjCr958O+DS 9R7RGsTJKJSp5CwYHhQMVyfEG81Jer6qg3Cu8ucZI/E9IP1dRygPO3quAOXyu+DCqEtc 6XNs+gUx61qZ94COGr+aVq4ovQnKf2QpZiBgRXKWsEa/JmBk8OEMgkOHtyRJcFAkT7qo 6p+7oHvx1pKZMIyPN51YXONY23M1CaiPYIiXhb590ZxXvViNC1ZitNqumVZwauIZzLsD 5FLw==
X-Received: by 10.60.70.35 with SMTP id j3mr11861oeu.80.1388847410598; Sat, 04 Jan 2014 06:56:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sat, 4 Jan 2014 06:56:30 -0800 (PST)
In-Reply-To: <52C78AEF.2010908@gmail.com>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie> <52C78AEF.2010908@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 4 Jan 2014 09:56:30 -0500
Message-ID: <CAPv4CP_1+vcH4-EYfypHnHwaK7YDnMnV_J8Vqe4+uuaN-+WJkA@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: Brian E Carpenter <brian.e.carpenter@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 14:56:59 -0000

On Fri, Jan 3, 2014 at 11:15 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 04/01/2014 14:19, Stephen Farrell wrote:
>
>>    It means
>>    that, if asked, there needs to be a good answer to the question "is
>>    pervasive monitoring relevant to this work and if so how has it been
>>    addressed?"
>
> I think this is an excellent question for a reviewer to ask,
> regardless of whether the present draft is published as a BCP,
> an Informational document, or never.
>
> Responsible engineering means considering a great number of
> eventualities when finalising a design, and this is just one
> more of those eventualities.

Some of us who do reviews already consider it, and are willing to
argue to get drafts fixed if they have privacy problems. This is just
making it a general IETF practice.

From agmalis@gmail.com  Sat Jan  4 06:58:47 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D9921ADFE2; Sat,  4 Jan 2014 06:58:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjO313u1zx4Z; Sat,  4 Jan 2014 06:58:45 -0800 (PST)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id D52D91ADFEE; Sat,  4 Jan 2014 06:58:44 -0800 (PST)
Received: by mail-qe0-f51.google.com with SMTP id 1so16463601qee.38 for <multiple recipients>; Sat, 04 Jan 2014 06:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=rmD9bpBmpauu3u4cR43+8DQrvljAcITN707Z9WGp4zo=; b=TWC93oKHAXNwCWkLg8IKEEdLva0rZh09tL5U3M7bl/kgb+Wkk/W3DgMgoNiJL6NY8L xOETvNGLVTfR1UD8ZNIHzJ73HhMw8a+m6fYfvbdbuzwHmchC/iQpLjuu3ENf7O68jeUC xerhdD25E5vheVbi8HOo/tgJ9mN1zRncJG6qhYA/5JDwNBJI6fHim/yBOGSJitKxLo/e iNgF20i7430pdUAfZlkGTAcmB/cyJjhTg3+0AGwj3C+7RaEU3GoPoX0X+N0IYDP3YMMo V4BfWtayRXNG/8rJnBR6xGHxoEBp1rI/Rw7DTRHjHvCHvF1IuaITj4L+dKDq691dQ5iM cu1g==
X-Received: by 10.49.15.227 with SMTP id a3mr165262415qed.66.1388847517030; Sat, 04 Jan 2014 06:58:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.166.9 with HTTP; Sat, 4 Jan 2014 06:58:16 -0800 (PST)
In-Reply-To: <m2d2k8lffa.wl%randy@psg.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <m2d2k8lffa.wl%randy@psg.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sat, 4 Jan 2014 09:58:16 -0500
Message-ID: <CAA=duU2A-cO3GGBvQg47EqquK0jhEKbmKk6A46_EOVWrUB7HwQ@mail.gmail.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: The IESG <iesg-secretary@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 14:58:47 -0000

On Fri, Jan 3, 2014 at 8:11 PM, Randy Bush <randy@psg.com> wrote:
> this draft could be used by those nasty ADs to abuse working groups and
> draft authors.  perhaps if it is experimental.

I disagree with Randy. It's the lack of such a draft that can
potentially cause more abuse by ADs "making it up as they go". With
this draft, there's an open, written process to follow, and that
written process can be amended in the future if necessary.

Cheers,
Andy

From scott.brim@gmail.com  Sat Jan  4 07:00:57 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 483761ADFE8 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 07:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MVfbtElWLzLy for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 07:00:56 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id EDACC1ADFFC for <ietf@ietf.org>; Sat,  4 Jan 2014 07:00:55 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wm4so16909055obc.0 for <ietf@ietf.org>; Sat, 04 Jan 2014 07:00:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=cJOpQZB8PwPp/gktl4H9niEJUbfpGcDXtdljdfuWEkY=; b=Z0LZ57YPsaoJJXAo1F+41L7TqD1T/QOacdd6XoBg9GMRJ/V7nvInwA/HTzsF/5mpxg zZ57kIIouL1+cwAwQjdykrAH8Pzxx4fPsmWOok0VQQlo/u3szlIxrTDYi6+BhC3xX9zP WGzP4ZFUNOcAPvbgwUKoCSXrHZSvDkjIgm64y6OWfkYs11EQPzNcALIuHM5yVGbiHHU5 Pc06aJ2gylIr4xegZVsBt1EU54NImfPKDNanQC9VqlujFWD1rpEqKHKpFIvHHFxuoMY/ untczd7XDLdYDL4vqC+ZItlhd8oqBTKEhn3TwHPvCPonqsZUXaoDDLYW/A78L1RS/oRQ N42Q==
X-Received: by 10.182.246.39 with SMTP id xt7mr64385783obc.16.1388847648190; Sat, 04 Jan 2014 07:00:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sat, 4 Jan 2014 07:00:28 -0800 (PST)
In-Reply-To: <52C7B371.7050500@isdg.net>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346A2@EXMB01CMS.surrey.ac.uk> <52C75B83.6000302@cs.tcd.ie> <c8nec9dqggob5ob6uj4q9u5pulhfjlg0js@hive.bjoern.hoehrmann.de> <52C761A6.8060800@cs.tcd.ie> <52C7B371.7050500@isdg.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 4 Jan 2014 10:00:28 -0500
Message-ID: <CAPv4CP_CM0MRR7LOiASNZwowFvmShNJKR_Tvi+MSAmnwarKjEQ@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: Hector Santos <hsantos@isdg.net>
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 15:00:57 -0000

On Sat, Jan 4, 2014 at 2:08 AM, Hector Santos <hsantos@isdg.net> wrote:
> I think the problem is the lack of a section or "checklist" that one should
> be considering

Yes but in this case we have the security considerations guidelines,
and could add a pointer to RFC 6973 and whatever new one comes out of
perpass. No need for a new section.

From dhc@dcrocker.net  Sat Jan  4 07:57:06 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78A61ADF8E; Sat,  4 Jan 2014 07:57:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5fdT5XRD2sL; Sat,  4 Jan 2014 07:57:05 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B90441ADFE2; Sat,  4 Jan 2014 07:57:05 -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 s04Fuss1018519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Jan 2014 07:56:58 -0800
Message-ID: <52C82EEA.1040705@dcrocker.net>
Date: Sat, 04 Jan 2014 07:55:22 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: IANA as a discrete function (Re: IANA blog article)
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <55DCB0F3-2ACD-44CB-B6FC-68ACC2A342DD@virtualized.org>
In-Reply-To: <55DCB0F3-2ACD-44CB-B6FC-68ACC2A342DD@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 04 Jan 2014 07:56:58 -0800 (PST)
Cc: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 15:57:06 -0000

On 1/3/2014 3:27 PM, David Conrad wrote:
> - Perhaps it is merely your shorthand, but I've found that saying "IANA" as if it is a discrete entity rather than a set of functions performed by a contractor (or contractors) tends to confuse things.  For example, you say "... IANA then makes the actual allocations ...".  In actuality (as you note later on), ICANN, acting as the current IANA "protocol parameters function" operator makes the allocation.


Glad you raised this.

Given the range of things that ICANN does and given the controversy some 
of that engenders and given that the IANA activities really are 
something that the IETF, itself, contracts to have done, I think it 
/better/ to refer to IANA as a discrete activity.

Labeling that set of functions as its own, IETF-assigned administrative 
identity can help to separate it from other other Internet 
administrative functions.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stephen.farrell@cs.tcd.ie  Sat Jan  4 08:01:43 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 818821AE020 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 08:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GYFf4sJLzTEU for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 08:01:39 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 97EAD1AE012 for <ietf@ietf.org>; Sat,  4 Jan 2014 08:01:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C9E55BE74; Sat,  4 Jan 2014 16:01:30 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id daSI3mzyAmdv; Sat,  4 Jan 2014 16:01:28 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.63.191]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C9FFCBE5D; Sat,  4 Jan 2014 16:01:28 +0000 (GMT)
Message-ID: <52C8304E.3080802@cs.tcd.ie>
Date: Sat, 04 Jan 2014 16:01:18 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>,  Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
In-Reply-To: <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 16:01:43 -0000

On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
> I have been wondering whether a simple update to "A Guide to Writing
> A Security Considerations Section" is all that is needed to address
> the problem in hand?

After a bit of offlist mail with Stewart, it turns out I had
misinterpreted the above.

I now believe (haven't quite confirmed, but its a fine idea
anyway so worth raising here) that what Stewart meant was
not to open up 3552 and add this text, (which'd take years) but
rather to make the RFC resulting from this draft be just another
part of BCP72 (aka RFC 3552).

(In case folks don't know, BCPs can be made up of multiple RFCs,
e.g. BCP 10 [1] is like that.)

I think that's quite an interesting idea, and would probably only
require adding a sentence or two to relate this text to that in 3552
(which is currently all of BCP72). I'd certainly have no problem
were that the outcome.

I guess that just might help folks with concerns that as a new BCP
this might be over zealously applied.

But I'm not sure - would that in fact help anyone with such concerns?

Cheers,
S.

PS: This might make suggest a fine longer term plan to work on a
broader revision of BCP72 as we better appreciate privacy concerns
in general and pervasive monitoring.

[1] http://tools.ietf.org/html/bcp10

> 
> Stewart
> 
> Sent from my iPad
> 
>> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com>
>> wrote:
>> 
>>> On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at the
>>> likely impact of the draft, not merely at the intentions of the
>>> authors.
>> 
>> I don't know if I'd use "likely" here but I definitely think the
>> IETF should be somewhat more thoughtful about "possible."
>> 
>> I've been trying to figure out if there's a way forward that 
>> doesn't involve bulldozing the dissenters.  Personally, I'd be fine
>> with publishing it as informational or experimental, or if the
>> document provided a lot more clarity about the basis for review
>> (along the lines of 3552).
>> 
>> Melinda
>> 
> 

From hallam@gmail.com  Sat Jan  4 09:15:25 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AABC41AE02F for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 09:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qgcqfK0PEO7f for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 09:15:23 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6A6491AE010 for <ietf@ietf.org>; Sat,  4 Jan 2014 09:15:22 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id l4so9023139lbv.27 for <ietf@ietf.org>; Sat, 04 Jan 2014 09:15:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=brXKssaVawDPcVexqiv+4MDidPXRwNdUTFwdNsV0qIo=; b=Im0M7ajnoK0pKu1FOFow6S4RlDod7Kkp/sOEnG4ODBi/6UoXshrEb3nQYg3WVHIZyY 7TjEjtu6okmWV0SmQpvJHuQj5em07ACg+WYNeZZDA+X74uXVd6NkVp85yhxXHAdHx809 srdgFxw9lT9WQFriPpLZgeukbsj5MYYpp0twTBKUkpqhhP4sm8sUKDzsNpOCTQ83G1F3 0Eh3dzLr7bl3hdJyFzb+dp75pWXi9ti5UrO3Vp2WG7xKRdbqX+ay6TLLvaPwEYe9gNPL +OnmnIAzrvdIbSH0M/xQ/yMZFEoBsEAEr4oUaxdMRxth7bUjmZI2NLYcgG/WEUAyFRRq bmIQ==
MIME-Version: 1.0
X-Received: by 10.112.201.197 with SMTP id kc5mr1100339lbc.64.1388855713996; Sat, 04 Jan 2014 09:15:13 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sat, 4 Jan 2014 09:15:13 -0800 (PST)
In-Reply-To: <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
Date: Sat, 4 Jan 2014 12:15:13 -0500
Message-ID: <CAMm+Lwjhkpeh_Oz3o0=fK3KewtOQ7bWBq0LCrjzp_PYnn0P3jA@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=001a11c2662e7a267b04ef282b9d
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 17:15:25 -0000

--001a11c2662e7a267b04ef282b9d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 4, 2014 at 4:31 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote=
:

>
> On 4 jan 2014, at 09:29, Jari Arkko <jari.arkko@piuha.net> wrote:
>
> >> One important change is that every future application protocol proposa=
l
> should be required to have an effectively unlimited code space for
> assignment.
> >
> > Agree.
>
> I do not agree regarding the term "unlimited".
>
> What is needed is that the specification do have a consequence analysis
> regarding expansion of use.
>

Please read my words as carefully as a wrote them.

There are excellent reasons why variable length IPv6 addresses would have
been a bad idea. That is why I separated considerations for IP layer, DNS
and Applications.

At the application layer, the concerns are very different. Variable length
identifiers are not a problem. We use them in RFC822, ASN.1, XML and JSON.

The only protocols above the bare IP layer where we don't use variable
length identifiers are IPSEC and TLS. But these are merely design mistakes
not to be repeated. Using fixed length identifiers in those protocols has
negligible performance advantages but even a 32 bit identifier space is not
big enough to make it a free for all. And so a technical choice creates an
ongoing administrative requirement.

The problem in TLS is worse because the algorithms are joined together in
suites and so there is a combinatorial issue. Since we have a key exchange
cipher, an encryption cipher and a MAC for each we actually have an average
of ten bits 32/3 per cipher. I can easily see us exhausting that.


What I would like is some architectural guidance from the IAB to the effect
that all future protocols MUST use an identification mechanism that puts
exhaustion of code points beyond the realm of practical possibility.

Since we are unlikely to be doing IPv7 any time soon and if we did it would
be a whole new ball game, this requirement would only apply to major
revisions of DNS, IPSEC, TLS like things and Application protocols.


I don't see an argument right now for a major revision of DNS. But if we
were to revisit it in a backwards incompatible way we would surely change
the protocol so that the number of possible resource records was more than
64K. The practical impact of the requirement is that the increase would
have to be from 64K to 'effectively unlimited' rather than to 4G (32 bits).

For other protocols the consequence would be to use one of the following:

1) Pseudo identifiers of 128 bits (or more), i.e. UUIDs
2) ASN.1 Object identifiers
3) Simple text labels (e.g. AES-128)
4) URIs


IP addresses will always be a special case because they have to operate
under some special constraints. We all use the same code point for
text/plain but we all have to use a different IP Address.


To respond to some points made by John and others later in the thread, mere
issue of a code point should not imply endorsement. I don't think that the
IETF should be in the business of endorsing cryptographic algorithms or
content types. There are certain cases where the IETF needs to be involved
in identifying the authoritative definition though. Is the definitive
definition of AES a document by NIST or someone else? Does Adobe define
application/pdf or ISO? (these are not questions I am asking, they are
illustration of the questions that IETF/IANA needs to answer).

I can certainly see potential for a situation where we start using some
open source content type and there is a fork where two different groups
claim to be the successor in interest and one true guardian of the spec.


For crypto, the situation is a little simpler and a lot more complicated
than assumed. The standards are in practice defined by running code. And
that code behaves in very particular ways.

If I add a crypto module to Windows (or most other well designed crypto
platforms), it will become available to all the applications running on
that platform. Which is all well and good of course. One consequence of
this is that the way S/MIME uses AES and the way TLS uses AES have to be
compatible. Otherwise large amounts of application code would need to be
rewritten to special case each algorithm. And not having to do that is the
objective of having a standard.

Fortunately the amount of variation possible is very small. There is the
byte ordering for keys and a few other endian issues that might be
underspecified or confused in the specs. But that is all. If an algorithm
needs more than that then it is not ready for use and should be discarded
(and new code points issued for the replacement).


What we do today is that we micromanage the process in ways that are
counterproductive. People write documents describing how to use the
<splunge> algorithm with IPSEC and S/MIME but any given platform is going
to have code based on one or the other. What appear to be two independent
specifications are in fact two variants of one specification since any
deviation between the two documents is unambiguously an ERROR.


--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Jan 4, 2014 at 4:31 AM, Patrik F=E4ltstr=F6m <span dir=3D"l=
tr">&lt;<a href=3D"mailto:paf@frobbit.se" target=3D"_blank">paf@frobbit.se<=
/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 4 jan 2014, at 09:29, Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.=
net">jari.arkko@piuha.net</a>&gt; wrote:<br>
<br>
&gt;&gt; One important change is that every future application protocol pro=
posal should be required to have an effectively unlimited code space for as=
signment.<br>
&gt;<br>
&gt; Agree.<br>
<br>
</div>I do not agree regarding the term &quot;unlimited&quot;.<br>
<br>
What is needed is that the specification do have a consequence analysis reg=
arding expansion of use.<br></blockquote><div><br></div><div>Please read my=
 words as carefully as a wrote them.</div><div><br></div><div>There are exc=
ellent reasons why variable length IPv6 addresses would have been a bad ide=
a. That is why I separated considerations for IP layer, DNS and Application=
s.=A0</div>
<div><br></div><div>At the application layer, the concerns are very differe=
nt. Variable length identifiers are not a problem. We use them in RFC822, A=
SN.1, XML and JSON.</div><div><br></div><div>The only protocols above the b=
are IP layer where we don&#39;t use variable length identifiers are IPSEC a=
nd TLS. But these are merely design mistakes not to be repeated. Using fixe=
d length identifiers in those protocols has negligible performance advantag=
es but even a 32 bit identifier space is not big enough to make it a free f=
or all. And so a technical choice creates an ongoing administrative require=
ment.</div>
<div><br></div><div>The problem in TLS is worse because the algorithms are =
joined together in suites and so there is a combinatorial issue. Since we h=
ave a key exchange cipher, an encryption cipher and a MAC for each we actua=
lly have an average of ten bits 32/3 per cipher. I can easily see us exhaus=
ting that.</div>
<div><br></div><div><br></div><div>What I would like is some architectural =
guidance from the IAB to the effect that all future protocols MUST use an i=
dentification mechanism that puts exhaustion of code points beyond the real=
m of practical possibility.</div>
<div><br></div><div>Since we are unlikely to be doing IPv7 any time soon an=
d if we did it would be a whole new ball game, this requirement would only =
apply to major revisions of DNS, IPSEC, TLS like things and Application pro=
tocols.=A0</div>
<div><br></div><div><br></div><div>I don&#39;t see an argument right now fo=
r a major revision of DNS. But if we were to revisit it in a backwards inco=
mpatible way we would surely change the protocol so that the number of poss=
ible resource records was more than 64K. The practical impact of the requir=
ement is that the increase would have to be from 64K to &#39;effectively un=
limited&#39; rather than to 4G (32 bits).</div>
<div><br></div><div>For other protocols the consequence would be to use one=
 of the following:</div><div><br></div><div>1) Pseudo identifiers of 128 bi=
ts (or more), i.e. UUIDs</div><div>2) ASN.1 Object identifiers=A0</div><div=
>
3) Simple text labels (e.g. AES-128)</div><div>4) URIs</div></div><div><br>=
</div><div><br></div><div>IP addresses will always be a special case becaus=
e they have to operate under some special constraints. We all use the same =
code point for text/plain but we all have to use a different IP Address.</d=
iv>
<div><br></div><div><br></div><div>To respond to some points made by John a=
nd others later in the thread, mere issue of a code point should not imply =
endorsement. I don&#39;t think that the IETF should be in the business of e=
ndorsing cryptographic algorithms or content types. There are certain cases=
 where the IETF needs to be involved in identifying the authoritative defin=
ition though. Is the definitive definition of AES a document by NIST or som=
eone else? Does Adobe define application/pdf or ISO? (these are not questio=
ns I am asking, they are illustration of the questions that IETF/IANA needs=
 to answer).</div>
<div><br></div><div>I can certainly see potential for a situation where we =
start using some open source content type and there is a fork where two dif=
ferent groups claim to be the successor in interest and one true guardian o=
f the spec.</div>
<div><br></div><div><br></div><div>For crypto, the situation is a little si=
mpler and a lot more complicated than assumed. The standards are in practic=
e defined by running code. And that code behaves in very particular ways.</=
div>
<div><br></div><div>If I add a crypto module to Windows (or most other well=
 designed crypto platforms), it will become available to all the applicatio=
ns running on that platform. Which is all well and good of course. One cons=
equence of this is that the way S/MIME uses AES and the way TLS uses AES ha=
ve to be compatible. Otherwise large amounts of application code would need=
 to be rewritten to special case each algorithm. And not having to do that =
is the objective of having a standard.</div>
<div><br></div><div>Fortunately the amount of variation possible is very sm=
all. There is the byte ordering for keys and a few other endian issues that=
 might be underspecified or confused in the specs. But that is all. If an a=
lgorithm needs more than that then it is not ready for use and should be di=
scarded (and new code points issued for the replacement).</div>
<div><br></div><div><br></div><div>What we do today is that we micromanage =
the process in ways that are counterproductive. People write documents desc=
ribing how to use the &lt;splunge&gt; algorithm with IPSEC and S/MIME but a=
ny given platform is going to have code based on one or the other. What app=
ear to be two independent specifications are in fact two variants of one sp=
ecification since any deviation between the two documents is unambiguously =
an ERROR.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c2662e7a267b04ef282b9d--

From hallam@gmail.com  Sat Jan  4 10:43:45 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3F831AE030 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 10:43:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdAJj19or9z4 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 10:43:41 -0800 (PST)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 548481AE027 for <ietf@ietf.org>; Sat,  4 Jan 2014 10:43:41 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id n7so8856948lam.16 for <ietf@ietf.org>; Sat, 04 Jan 2014 10:43:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q94fzcgv+c7fjdxRTBiCGv+1aD6Ft1oeqMPLnBtLlYQ=; b=TvjbbNvvOHQ3Q98v5TcZ+QX7LaKcVOAkWD0wuRvR9yrnm37xZ1PuqFyfWOqG+eXYx4 GAUwK0otuwcVRnD/zKsrvd8gwavhfNshlLTLsVls8GvJB5CvuUBCFpvsWHVd1XlMcIvz mUkev4WtcflG8JTjI/yJENbE+jzRQMcLdnxP11r3x6H8QuISkKWNQdulONQLg/ZeTSGE C6VHwXgpZvxLEHMoIsMnXUFEXNJgECzor/emhkGikjvlk0Fu4pPCxcSX4HyVTRSa+zAz 4uwFdcmSBXFcElm8CqLKxAkxU0OLFfFuihQxkLsHO1KmgEnUDOXCGis0x6HG/1Zjw0Mi rDqA==
MIME-Version: 1.0
X-Received: by 10.112.169.66 with SMTP id ac2mr3892078lbc.28.1388861012731; Sat, 04 Jan 2014 10:43:32 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sat, 4 Jan 2014 10:43:32 -0800 (PST)
In-Reply-To: <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
Date: Sat, 4 Jan 2014 13:43:32 -0500
Message-ID: <CAMm+LwgpCRUrA5qDpASP2FWGjfhmpWRGW_wvg=5ccMTW0SGX+Q@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11c38da04e6bd104ef296735
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 18:43:46 -0000

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

[trimmed to just the parts I am responding to]


On Sat, Jan 4, 2014 at 3:29 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

>
> > I think that the article needs to go back to some basic principles.
> >
> > The whole point of the end-to-end architecture was that it enabled
> innovation and diversity. In particular it was possible to add applicatio=
ns
> to the Internet without going to some central authority to ask permission=
.
>
> I very much agree with this principle. Although maybe that's a topic for
> another blog article or discussion=85


I know that it is what everyone agrees on. But some people also see the
mission of the IETF as to protect the Internet from harmful
experimentation. This is silly for two reasons, first is is a LOT harder to
bring down the Internet than most people imagine, second the people who are
likely to cause such an issue accidentally don't taken any notice of the
IETF or IANA in any case.

> The status quo for most registries is that they are permissive but there
> is a large amount of difference in the criteria and there are experts
> involved doing reviews for some systems but not others. There is a genera=
l
> lack of consistency. A standards organization should look for consistency=
.
>
> I think we are trying. Can you be more specific about areas where there i=
s
> lack of consistency? We can try to improve rules about specific IANA
> registries, provide more guidance to experts, etc. if we are not performi=
ng
> well enough in some area.


I see the problem mostly in the crypto area where the tradition has been
that each protocol defines its own registry of schemes. This is a bad
approach. I would like to see a single registry that keeps track of the
OID, text label and URI identifications of each algorithm and all crypto
applications should use the code points in that registry.

Choice of crypto algorithms is an ongoing maintenance task. It is not
therefore a task that can or should be performed by Working Groups unless
we want the Working Groups to become permanent.

IETF should only endorse a single core set of algorithms with a maximum of
one preferred and one alternative algorithm and this should be an IETF
consensus, not a WG consensus. A WG might add in additional recommendations
to support legacy interop, for example 3DES is still a defacto requirement
for S/MIME.

All other crypto maintenance should be achieved through a first-come common
registry.


The mere existence of a code point would not mean that it can or should be
used with IPSEC or S/MIME. None of us want to use MD2 or DES for example,
even though the code points are well known. All a code point means is that
the behavior of the protocol is defined. Caveat ingenio.


One case that will come up soon is this one
http://datatracker.ietf.org/doc/draft-ietf-jose-json-web-algorithms/

For the sake of saving a few bytes in a protocol using a text based
encoding, the OpenID people decided to use their own text based identifiers
for crypto algorithms. So the JOSE working group is wanting to create a new
set of algorithm identifiers for all the existing algorithms.

This is not a good practice for a standards organization. We have a
perfectly good set of text based labels already from the PEM days. Even
though PEM is deader than a dodo, the code points are widely used and we
have an existing registry.


The response to the JOSE demand for a new registry should be the following:

1) Reserve the code points already assigned in OpenID in the common
registry for the use of OpenID alone.

2) Require all applications that are not OpenID to use the common registry.


There are some things that are legitimately Working Group decisions.
Forking the IANA crypto registries is not.

* Each code point should identify an algorithm (plus possible parameters)
unambiguously

* A single algorithm can be identified by multiple code points.

* Each algorithm should have a single canonical code point which MUST be
accepted by all conforming applications.


So OpenID implementations would still be free to (and indeed required to)
use the legacy code points for backwards compatibility. But they would be
required to accept the common labels as well.

I would further suggest that when we next do a major revison of TLS or
IPSEC that is going to affect the algorithm negotiation scheme, we insert
one new code point for 'suite indicated in an extension' and this be an
indirect to a scheme based on the common registry. It would still be
possible to support suite restrictions but these would be implemented in
code and could support expressions of the form

(RSA2048 or RSA4096) and (AES128 or AES192 or AES256) and (..)
or
(ECDSA-splunge) and (AES256)

etc.

> Another is that application protocols should be required to reuse code
> points from common registries rather than define their own.
> >
> > At the moment we have separate crypto registries for TLS, IPSEC, PEM,
> PKIX and XML Digital Signature. The JOSE folk want to create another. The=
re
> should be a policy that tells people from the start that there will be no
> new crypto registries.
>
> Here I am not so sure. Registries for adding specific crypto algorithms
> are not merely number allocations; they go with specifications and code
> that actually runs, say, AES on IPsec or AES on TLS. It is not entirely
> clear to me that crypto across different protocols and use cases should
> proceed in lock step. And even if it were useful, it is a difficult chang=
e
> to make retroactively, when the code points in different protocols starte=
d
> out differently.
>

The definition of a code point is an administrative issue. The only case
where this is standards issue is when some doubt arises because a spec is
insufficient or misinterpreted.

The decision to require support of a specific algorithm set to enable
interoperability is not really WG material either because it is a decision
that has to be revisited over time.

I don't see much value in having an argument over the choice of crypto in
WG foo and then a year later start the whole debate from scratch on
protocol bar. Especially when it is the same set of people and the
arguments have not changed.

Crypto algorithms are by design a commodity. If they are not plug and play
then something is broken in the specification of the algorithm or the
protocol.

While crypto protocols are broken down into separate WGs, security is a
unified concern across all protocols and works as a system. It is
implemented in the same way.


The reason we change algorithm recommendations is that the security
evaluations of the protocols change. So when we deprecated DES, it was in
all IETF protocols, not just one.

We are currently phasing out use of SHA-1 across all deployed crypto
applications that rely on PKIX. This is not an IETF action or even a
CABForum action, it is the consequence of Microsoft deciding to bite the
bullet and declare that they are going to drop support for SHA-1 in certain
applications which will in turn force the entire WebPKI to follow suit.
Which is an outcome that the whole security community believes should
happen, the only dispute has been over timing.


>From an implementer point of view, having the IETF periodically issue an
RFC saying that the recommended crypto algorithms are X, Y and Z would be a
big help to us because then someone can take the OpenSSL (or Cryptolib etc)
library and subset it to only those ciphers knowing that they can support
all the IETF apps.

It would not be a particularly controversial project either. The consensus
in the crypto world today is clearly for the following set of required
algorithms:

Public Key Encryption:  RSA  (RSA-2048, RSA-4096)
Public Key Signature:  RSA  (RSA-2048, RSA-4096)
Public Key Exchange: DH (DH-2048, DH-4096)
Encryption: AES (AES-128, AES-192, AES-256)
Digest: SHA-2 (SHA-2-128, SHA-2-192, SHA-2-256)
MAC: HMAC-SHA2*

OK, the last we could argue on. We can also argue about the block cipher
modes and whether encrypt and authenticate modes are consensus. But those
are decisions where the application requirements do actually have an
impact. AES-CBC is not interchangable for AES-CFB.

And for alternatives we would essentially be looking at Suite-B plus SHA-3
with the massive caveat that IPR FUD is going to continue to make them
unusable for many applications for quite a while. However happy I am with
the litigation risk, the IPR holder can go after my customers. Since RIM is
up for sale and the patents likely to be bought by a troll, it is not a
risk the industry can currently take.

[Though if the NSA wants to say sorry for spying on the crypto community
and sabotaging standards, they could buy the patents themselves and make
them public domain]


That at any rate is what I mean by consistency. I think the IAB should look
at consolidation of IANA registries as one mechanism for achieving greater
consistency across protocols and avoiding unnecessary variations. The IAB
should not be responsible for deciding which algorithms we use (for
example) but they should take responsibility for deciding that the set of
algorithms will be decided in one place and not many.



--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr">[trimmed to just the parts I am responding to]<div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, Jan 4, 2014 at =
3:29 AM, Jari Arkko <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuh=
a.net" target=3D"_blank">jari.arkko@piuha.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im"><br>
&gt; I think that the article needs to go back to some basic principles.<br=
>
&gt;<br>
&gt; The whole point of the end-to-end architecture was that it enabled inn=
ovation and diversity. In particular it was possible to add applications to=
 the Internet without going to some central authority to ask permission.<br=
>

<br>
</div>I very much agree with this principle. Although maybe that&#39;s a to=
pic for another blog article or discussion=85 </blockquote><div><br></div><=
div>I know that it is what everyone agrees on. But some people also see the=
 mission of the IETF as to protect the Internet from harmful experimentatio=
n. This is silly for two reasons, first is is a LOT harder to bring down th=
e Internet than most people imagine, second the people who are likely to ca=
use such an issue accidentally don&#39;t taken any notice of the IETF or IA=
NA in any case.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><div class=3D"im">&gt; The status quo for m=
ost registries is that they are permissive but there is a large amount of d=
ifference in the criteria and there are experts involved doing reviews for =
some systems but not others. There is a general lack of consistency. A stan=
dards organization should look for consistency.<br>

<br>
</div>I think we are trying. Can you be more specific about areas where the=
re is lack of consistency? We can try to improve rules about specific IANA =
registries, provide more guidance to experts, etc. if we are not performing=
 well enough in some area.</blockquote>
<div><br></div><div>I see the problem mostly in the crypto area where the t=
radition has been that each protocol defines its own registry of schemes. T=
his is a bad approach. I would like to see a single registry that keeps tra=
ck of the OID, text label and URI identifications of each algorithm and all=
 crypto applications should use the code points in that registry.</div>
<div><br></div><div>Choice of crypto algorithms is an ongoing maintenance t=
ask. It is not therefore a task that can or should be performed by Working =
Groups unless we want the Working Groups to become permanent.</div><div>
<br></div><div>IETF should only endorse a single core set of algorithms wit=
h a maximum of one preferred and one alternative algorithm and this should =
be an IETF consensus, not a WG consensus. A WG might add in additional reco=
mmendations to support legacy interop, for example 3DES is still a defacto =
requirement for S/MIME.</div>
<div><br></div><div>All other crypto maintenance should be achieved through=
 a first-come common registry.</div><div><br></div><div><br></div><div>The =
mere existence of a code point would not mean that it can or should be used=
 with IPSEC or S/MIME. None of us want to use MD2 or DES for example, even =
though the code points are well known. All a code point means is that the b=
ehavior of the protocol is defined. Caveat ingenio.</div>
<div><br></div><div><br></div><div>One case that will come up soon is this =
one</div><div><a href=3D"http://datatracker.ietf.org/doc/draft-ietf-jose-js=
on-web-algorithms/">http://datatracker.ietf.org/doc/draft-ietf-jose-json-we=
b-algorithms/</a><br>
</div><div><br></div><div>For the sake of saving a few bytes in a protocol =
using a text based encoding, the OpenID people decided to use their own tex=
t based identifiers for crypto algorithms. So the JOSE working group is wan=
ting to create a new set of algorithm identifiers for all the existing algo=
rithms.</div>
<div><br></div><div>This is not a good practice for a standards organizatio=
n. We have a perfectly good set of text based labels already from the PEM d=
ays. Even though PEM is deader than a dodo, the code points are widely used=
 and we have an existing registry.</div>
<div><br></div><div><br></div><div>The response to the JOSE demand for a ne=
w registry should be the following:</div><div><br></div><div>1) Reserve the=
 code points already assigned in OpenID in the common registry for the use =
of OpenID alone.</div>
<div><br></div><div>2) Require all applications that are not OpenID to use =
the common registry.</div><div>=A0</div><div><br></div><div>There are some =
things that are legitimately Working Group decisions. Forking the IANA cryp=
to registries is not.=A0</div>
<div><br></div><div>* Each code point should identify an algorithm (plus po=
ssible parameters) unambiguously<br></div><div><br></div><div>* A single al=
gorithm can be identified by multiple code points.</div><div><br></div>
<div>* Each algorithm should have a single canonical code point which MUST =
be accepted by all conforming applications.</div><div><br></div><div><br></=
div><div>So OpenID implementations would still be free to (and indeed requi=
red to) use the legacy code points for backwards compatibility. But they wo=
uld be required to accept the common labels as well.</div>
<div><br></div><div>I would further suggest that when we next do a major re=
vison of TLS or IPSEC that is going to affect the algorithm negotiation sch=
eme, we insert one new code point for &#39;suite indicated in an extension&=
#39; and this be an indirect to a scheme based on the common registry. It w=
ould still be possible to support suite restrictions but these would be imp=
lemented in code and could support expressions of the form=A0</div>
<div><br></div><div>(RSA2048 or RSA4096) and (AES128 or AES192 or AES256) a=
nd (..)</div><div>or</div><div>(ECDSA-splunge) and (AES256)</div><div><br><=
/div><div>etc.</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D"im">&gt; Another is that application protocols should be requ=
ired to reuse code points from common registries rather than define their o=
wn.<br>
&gt;<br>
&gt; At the moment we have separate crypto registries for TLS, IPSEC, PEM, =
PKIX and XML Digital Signature. The JOSE folk want to create another. There=
 should be a policy that tells people from the start that there will be no =
new crypto registries.<br>

<br>
</div>Here I am not so sure. Registries for adding specific crypto algorith=
ms are not merely number allocations; they go with specifications and code =
that actually runs, say, AES on IPsec or AES on TLS. It is not entirely cle=
ar to me that crypto across different protocols and use cases should procee=
d in lock step. And even if it were useful, it is a difficult change to mak=
e retroactively, when the code points in different protocols started out di=
fferently.<br>
</blockquote><div><br></div><div>The definition of a code point is an admin=
istrative issue. The only case where this is standards issue is when some d=
oubt arises because a spec is insufficient or misinterpreted.=A0</div><div>
<br></div><div>The decision to require support of a specific algorithm set =
to enable interoperability is not really WG material either because it is a=
 decision that has to be revisited over time.=A0</div><div><br></div><div>
I don&#39;t see much value in having an argument over the choice of crypto =
in WG foo and then a year later start the whole debate from scratch on prot=
ocol bar. Especially when it is the same set of people and the arguments ha=
ve not changed.</div>
<div><br></div><div>Crypto algorithms are by design a commodity. If they ar=
e not plug and play then something is broken in the specification of the al=
gorithm or the protocol.</div><div><br></div><div>While crypto protocols ar=
e broken down into separate WGs, security is a unified concern across all p=
rotocols and works as a system. It is implemented in the same way.</div>
<div><br></div><div><br></div><div>The reason we change algorithm recommend=
ations is that the security evaluations of the protocols change. So when we=
 deprecated DES, it was in all IETF protocols, not just one.</div><div>
<br></div><div>We are currently phasing out use of SHA-1 across all deploye=
d crypto applications that rely on PKIX. This is not an IETF action or even=
 a CABForum action, it is the consequence of Microsoft deciding to bite the=
 bullet and declare that they are going to drop support for SHA-1 in certai=
n applications which will in turn force the entire WebPKI to follow suit. W=
hich is an outcome that the whole security community believes should happen=
, the only dispute has been over timing.</div>
<div><br></div><div><br></div><div>From an implementer point of view, havin=
g the IETF periodically issue an RFC saying that the recommended crypto alg=
orithms are X, Y and Z would be a big help to us because then someone can t=
ake the OpenSSL (or Cryptolib etc) library and subset it to only those ciph=
ers knowing that they can support all the IETF apps.</div>
<div><br></div><div>It would not be a particularly controversial project ei=
ther. The consensus in the crypto world today is clearly for the following =
set of required algorithms:</div><div><br></div><div>Public Key Encryption:=
 =A0RSA =A0(RSA-2048, RSA-4096)</div>
<div>Public Key Signature: =A0RSA =A0(RSA-2048, RSA-4096)<br></div><div>Pub=
lic Key Exchange: DH (DH-2048, DH-4096)</div><div>Encryption: AES (AES-128,=
 AES-192, AES-256)</div><div>Digest: SHA-2 (SHA-2-128, SHA-2-192, SHA-2-256=
)</div>
<div>MAC: HMAC-SHA2*</div><div><br></div><div>OK, the last we could argue o=
n. We can also argue about the block cipher modes and whether encrypt and a=
uthenticate modes are consensus. But those are decisions where the applicat=
ion requirements do actually have an impact. AES-CBC is not interchangable =
for AES-CFB.</div>
<div><br></div><div>And for alternatives we would essentially be looking at=
 Suite-B plus SHA-3 with the massive caveat that IPR FUD is going to contin=
ue to make them unusable for many applications for quite a while. However h=
appy I am with the litigation risk, the IPR holder can go after my customer=
s. Since RIM is up for sale and the patents likely to be bought by a troll,=
 it is not a risk the industry can currently take.=A0</div>
<div><br></div><div>[Though if the NSA wants to say sorry for spying on the=
 crypto community and sabotaging standards, they could buy the patents them=
selves and make them public domain]</div><div><br></div><div><br></div>
</div><div>That at any rate is what I mean by consistency. I think the IAB =
should look at consolidation of IANA registries as one mechanism for achiev=
ing greater consistency across protocols and avoiding unnecessary variation=
s. The IAB should not be responsible for deciding which algorithms we use (=
for example) but they should take responsibility for deciding that the set =
of algorithms will be decided in one place and not many.</div>
<div><br></div><div><br></div><div><br></div>-- <br>Website: <a href=3D"htt=
p://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c38da04e6bd104ef296735--

From stbryant@cisco.com  Sat Jan  4 11:15:12 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 544F31AE08B for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:15:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CaYqeRMuCEq for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:15:10 -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 0A2201AE088 for <ietf@ietf.org>; Sat,  4 Jan 2014 11:15:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2589; q=dns/txt; s=iport; t=1388862903; x=1390072503; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6KTo5hlRpy8lB1e0jGWBKam985Nsze3aPurmruVJjso=; b=hoWNrxHShrBJnA2Dz8WU/JLz2ggE3JhUWJ1m9PD3xqhNeI1vw0L+N3RU 71tx/6PhLWFAf5OA3atKua04LkC7t+fbrbi5/Aka806VFAFjz6IXERVvY GZt1WrIOF0Fmx/RlP63PqOvJdfCzD9cN5rZjZHWm1vhG7HseILP4SwAna M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAH5cyFKtJV2d/2dsb2JhbABYgws4uX2BCxZ0giUBAQEDATo/BQsCAQgYHgULIRElAgQOBYdwAwkIvncNhEAXjHyBQgEBHDMHgySBEwSWK4FsgTCLKoU7gW+BPoFx
X-IronPort-AV: E=Sophos;i="4.95,604,1384300800"; d="scan'208";a="292265996"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 04 Jan 2014 19:14:59 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s04JExJJ030547 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 4 Jan 2014 19:14:59 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.230]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.03.0123.003; Sat, 4 Jan 2014 13:14:59 -0600
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
Thread-Index: AQHPCLYLAS2sNYxC+kmtoTtmduA/Y5pzdZWvgAGp/AD//9GH3g==
Date: Sat, 4 Jan 2014 19:14:58 +0000
Message-ID: <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com>
References: <26734.1388770438@erosen-linux>,<52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>, <52C8304E.3080802@cs.tcd.ie>
In-Reply-To: <52C8304E.3080802@cs.tcd.ie>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 19:15:12 -0000

Sent from my iPad

> On 4 Jan 2014, at 16:01, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wr=
ote:
>=20
>=20
>=20
>> On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
>> I have been wondering whether a simple update to "A Guide to Writing
>> A Security Considerations Section" is all that is needed to address
>> the problem in hand?
>=20
> After a bit of offlist mail with Stewart, it turns out I had
> misinterpreted the above.
>=20
> I now believe (haven't quite confirmed, but its a fine idea
> anyway so worth raising here) that what Stewart meant was
> not to open up 3552 and add this text, (which'd take years) but
> rather to make the RFC resulting from this draft be just another
> part of BCP72 (aka RFC 3552).

Yes, that is what I meant. An RFC that says updates RFC3552 in
the top left corner, and provides advise on this security issue in
the same manner and style that RFC3552 deals with all the other
important security issues.

- Stewart


>=20
> (In case folks don't know, BCPs can be made up of multiple RFCs,
> e.g. BCP 10 [1] is like that.)
>=20
> I think that's quite an interesting idea, and would probably only
> require adding a sentence or two to relate this text to that in 3552
> (which is currently all of BCP72). I'd certainly have no problem
> were that the outcome.
>=20
> I guess that just might help folks with concerns that as a new BCP
> this might be over zealously applied.
>=20
> But I'm not sure - would that in fact help anyone with such concerns?
>=20
> Cheers,
> S.
>=20
> PS: This might make suggest a fine longer term plan to work on a
> broader revision of BCP72 as we better appreciate privacy concerns
> in general and pervasive monitoring.
>=20
> [1] http://tools.ietf.org/html/bcp10
>=20
>>=20
>> Stewart
>>=20
>> Sent from my iPad
>>=20
>>> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com>
>>> wrote:
>>>=20
>>>> On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at the
>>>> likely impact of the draft, not merely at the intentions of the
>>>> authors.
>>>=20
>>> I don't know if I'd use "likely" here but I definitely think the
>>> IETF should be somewhat more thoughtful about "possible."
>>>=20
>>> I've been trying to figure out if there's a way forward that=20
>>> doesn't involve bulldozing the dissenters.  Personally, I'd be fine
>>> with publishing it as informational or experimental, or if the
>>> document provided a lot more clarity about the basis for review
>>> (along the lines of 3552).
>>>=20
>>> Melinda
>>=20

From brian.e.carpenter@gmail.com  Sat Jan  4 11:46:24 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 193991AE087 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:46:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AthhPqmGoj41 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:46:22 -0800 (PST)
Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6231AE051 for <ietf@ietf.org>; Sat,  4 Jan 2014 11:46:22 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so17015083pbb.0 for <ietf@ietf.org>; Sat, 04 Jan 2014 11:46:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m/hSkf9Fn38tiLF8jPTmvNpSm4sWaGvZwq+tA5g5Q6g=; b=pwH84KyPxPvoZKihoh3IDYn5zhH9+qtmHWflM3I192aW1L+mGre2/S8H5yrN4DgtjF s8tKxVvXeWJjQJZEbPXdq3AGJl5jZrKg9F5w4bmAgqrfLd71yxgC0Ku6L8WbjEGGFq1Q IershnPU5YLu2G7dC6G2k+IQntww9WgbYaY03Q9+eIu+GuGHGm5pv13GuNpLp960bILN phffR/6W/tLUp8Iamx6XWh1XL8GRpAmKdvwpeGM7sE4S5LgBndlTBo/MjIWB93xJWJl/ ocd7XkHtUctLP3wWP/2kYlpqsgOH2MaJCN+0rBFKFCt4RqxHjYOKNwEAd8001kPr80X/ hHuQ==
X-Received: by 10.68.176.65 with SMTP id cg1mr108790468pbc.145.1388864774799;  Sat, 04 Jan 2014 11:46:14 -0800 (PST)
Received: from [192.168.178.21] (184.196.69.111.dynamic.snap.net.nz. [111.69.196.184]) by mx.google.com with ESMTPSA id zc6sm104703396pab.0.2014.01.04.11.46.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Jan 2014 11:46:14 -0800 (PST)
Message-ID: <52C86502.7020604@gmail.com>
Date: Sun, 05 Jan 2014 08:46:10 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: IANA blog article
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <0BF989509DD2BA5AD9CD9490@JcK-HP8200.jck.com>
In-Reply-To: <0BF989509DD2BA5AD9CD9490@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 19:46:24 -0000

On 05/01/2014 01:10, John C Klensin wrote:
>=20
> --On Saturday, January 04, 2014 10:31 +0100 Patrik F=C3=A4ltstr=C3=B6m
> <paf@frobbit.se> wrote:
>=20
>> On 4 jan 2014, at 09:29, Jari Arkko <jari.arkko@piuha.net>
>> wrote:
>>
>>>> One important change is that every future application
>>>> protocol proposal should be required to have an effectively
>>>> unlimited code space for assignment.
>>> Agree.
>> I do not agree regarding the term "unlimited".
>>
>> What is needed is that the specification do have a consequence
>> analysis regarding expansion of use.
>=20
> At least if it isn't unlimited, but I agree with Patrik.

There's some discussion of what can go wrong in RFC 6709, Section 4.4
on "Parameter Space Design".

    Brian


From scott.brim@gmail.com  Sat Jan  4 11:54:21 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91C0F1AE08B for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:54:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggMaJB9VKdSL for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:54:19 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 402A61AE051 for <ietf@ietf.org>; Sat,  4 Jan 2014 11:54:19 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id uz6so16775677obc.20 for <ietf@ietf.org>; Sat, 04 Jan 2014 11:54:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QPUB5y9wijSbdEno30X3gHqKIE/R6LQHRTe/1H8rXbQ=; b=zbm0Ug6uLFLj2hmpgCq2d/Yh7TQXgTyTtXERakGPRQPRqKyBdeZzP4tOc2oFaEx1zO QQgtfw78J2K1uN6PoReUQcnIh1XWx16EJPbmfsUgs6gPmdO5By0s2K012N5eiE0MKYt2 Q1sTxaHB4nxFf3+3tIgwR13kkNGrqlfGhf0asdTI2FQsXcAfbnj+NaM6Ob42RKAeTuxD 0xNrS5jRIfc/k1/nC+eb9wNgTHxrN2p6cTZHI/IpIvdGl2pOCH5YWlWP9MF/RCfWAyjo 3/QuuiGoSQAxZSNBot/19y4m5qGvZfBRkRHeC6j6rBqRfPUiZZNwGWQxOzoATxIOZls7 qyew==
MIME-Version: 1.0
X-Received: by 10.60.99.8 with SMTP id em8mr39744933oeb.8.1388865251313; Sat, 04 Jan 2014 11:54:11 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 4 Jan 2014 11:54:11 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 4 Jan 2014 11:54:11 -0800 (PST)
In-Reply-To: <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <52C8304E.3080802@cs.tcd.ie> <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com>
Date: Sat, 4 Jan 2014 14:54:11 -0500
Message-ID: <CAPv4CP8yWNyTxVYDFnseSz1OMqLexFXO_45FnO-EGa3ADM0S2g@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
From: Scott Brim <scott.brim@gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b33cad2f20f9d04ef2a63d8
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 19:54:21 -0000

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

Yes. I thought that would be the NEXT step after this draft. But let's not
skip this one. The next will take a bit of time, so let's publish this one
so the world can see our position.  Once the next one is done it can
incorporate this one and obsolete it.

Scott
On Jan 4, 2014 2:15 PM, "Stewart Bryant (stbryant)" <stbryant@cisco.com>
wrote:

>
>
> Sent from my iPad
>
> > On 4 Jan 2014, at 16:01, "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
> wrote:
> >
> >
> >
> >> On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
> >> I have been wondering whether a simple update to "A Guide to Writing
> >> A Security Considerations Section" is all that is needed to address
> >> the problem in hand?
> >
> > After a bit of offlist mail with Stewart, it turns out I had
> > misinterpreted the above.
> >
> > I now believe (haven't quite confirmed, but its a fine idea
> > anyway so worth raising here) that what Stewart meant was
> > not to open up 3552 and add this text, (which'd take years) but
> > rather to make the RFC resulting from this draft be just another
> > part of BCP72 (aka RFC 3552).
>
> Yes, that is what I meant. An RFC that says updates RFC3552 in
> the top left corner, and provides advise on this security issue in
> the same manner and style that RFC3552 deals with all the other
> important security issues.
>
> - Stewart
>
>
> >
> > (In case folks don't know, BCPs can be made up of multiple RFCs,
> > e.g. BCP 10 [1] is like that.)
> >
> > I think that's quite an interesting idea, and would probably only
> > require adding a sentence or two to relate this text to that in 3552
> > (which is currently all of BCP72). I'd certainly have no problem
> > were that the outcome.
> >
> > I guess that just might help folks with concerns that as a new BCP
> > this might be over zealously applied.
> >
> > But I'm not sure - would that in fact help anyone with such concerns?
> >
> > Cheers,
> > S.
> >
> > PS: This might make suggest a fine longer term plan to work on a
> > broader revision of BCP72 as we better appreciate privacy concerns
> > in general and pervasive monitoring.
> >
> > [1] http://tools.ietf.org/html/bcp10
> >
> >>
> >> Stewart
> >>
> >> Sent from my iPad
> >>
> >>> On 3 Jan 2014, at 19:00, "Melinda Shore" <melinda.shore@gmail.com>
> >>> wrote:
> >>>
> >>>> On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at the
> >>>> likely impact of the draft, not merely at the intentions of the
> >>>> authors.
> >>>
> >>> I don't know if I'd use "likely" here but I definitely think the
> >>> IETF should be somewhat more thoughtful about "possible."
> >>>
> >>> I've been trying to figure out if there's a way forward that
> >>> doesn't involve bulldozing the dissenters.  Personally, I'd be fine
> >>> with publishing it as informational or experimental, or if the
> >>> document provided a lot more clarity about the basis for review
> >>> (along the lines of 3552).
> >>>
> >>> Melinda
> >>
>

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

<p dir=3D"ltr">Yes. I thought that would be the NEXT step after this draft.=
 But let&#39;s not skip this one. The next will take a bit of time, so let&=
#39;s publish this one so the world can see our position.=A0 Once the next =
one is done it can incorporate this one and obsolete it. </p>

<p dir=3D"ltr">Scott </p>
<div class=3D"gmail_quote">On Jan 4, 2014 2:15 PM, &quot;Stewart Bryant (st=
bryant)&quot; &lt;<a href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com<=
/a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Sent from my iPad<br>
<br>
&gt; On 4 Jan 2014, at 16:01, &quot;Stephen Farrell&quot; &lt;<a href=3D"ma=
ilto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br=
>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt; On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:<br>
&gt;&gt; I have been wondering whether a simple update to &quot;A Guide to =
Writing<br>
&gt;&gt; A Security Considerations Section&quot; is all that is needed to a=
ddress<br>
&gt;&gt; the problem in hand?<br>
&gt;<br>
&gt; After a bit of offlist mail with Stewart, it turns out I had<br>
&gt; misinterpreted the above.<br>
&gt;<br>
&gt; I now believe (haven&#39;t quite confirmed, but its a fine idea<br>
&gt; anyway so worth raising here) that what Stewart meant was<br>
&gt; not to open up 3552 and add this text, (which&#39;d take years) but<br=
>
&gt; rather to make the RFC resulting from this draft be just another<br>
&gt; part of BCP72 (aka RFC 3552).<br>
<br>
Yes, that is what I meant. An RFC that says updates RFC3552 in<br>
the top left corner, and provides advise on this security issue in<br>
the same manner and style that RFC3552 deals with all the other<br>
important security issues.<br>
<br>
- Stewart<br>
<br>
<br>
&gt;<br>
&gt; (In case folks don&#39;t know, BCPs can be made up of multiple RFCs,<b=
r>
&gt; e.g. BCP 10 [1] is like that.)<br>
&gt;<br>
&gt; I think that&#39;s quite an interesting idea, and would probably only<=
br>
&gt; require adding a sentence or two to relate this text to that in 3552<b=
r>
&gt; (which is currently all of BCP72). I&#39;d certainly have no problem<b=
r>
&gt; were that the outcome.<br>
&gt;<br>
&gt; I guess that just might help folks with concerns that as a new BCP<br>
&gt; this might be over zealously applied.<br>
&gt;<br>
&gt; But I&#39;m not sure - would that in fact help anyone with such concer=
ns?<br>
&gt;<br>
&gt; Cheers,<br>
&gt; S.<br>
&gt;<br>
&gt; PS: This might make suggest a fine longer term plan to work on a<br>
&gt; broader revision of BCP72 as we better appreciate privacy concerns<br>
&gt; in general and pervasive monitoring.<br>
&gt;<br>
&gt; [1] <a href=3D"http://tools.ietf.org/html/bcp10" target=3D"_blank">htt=
p://tools.ietf.org/html/bcp10</a><br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Stewart<br>
&gt;&gt;<br>
&gt;&gt; Sent from my iPad<br>
&gt;&gt;<br>
&gt;&gt;&gt; On 3 Jan 2014, at 19:00, &quot;Melinda Shore&quot; &lt;<a href=
=3D"mailto:melinda.shore@gmail.com">melinda.shore@gmail.com</a>&gt;<br>
&gt;&gt;&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; On 1/3/14 8:33 AM, Eric Rosen wrote: One has to look at th=
e<br>
&gt;&gt;&gt;&gt; likely impact of the draft, not merely at the intentions o=
f the<br>
&gt;&gt;&gt;&gt; authors.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I don&#39;t know if I&#39;d use &quot;likely&quot; here but I =
definitely think the<br>
&gt;&gt;&gt; IETF should be somewhat more thoughtful about &quot;possible.&=
quot;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I&#39;ve been trying to figure out if there&#39;s a way forwar=
d that<br>
&gt;&gt;&gt; doesn&#39;t involve bulldozing the dissenters. =A0Personally, =
I&#39;d be fine<br>
&gt;&gt;&gt; with publishing it as informational or experimental, or if the=
<br>
&gt;&gt;&gt; document provided a lot more clarity about the basis for revie=
w<br>
&gt;&gt;&gt; (along the lines of 3552).<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Melinda<br>
&gt;&gt;<br>
</blockquote></div>

--047d7b33cad2f20f9d04ef2a63d8--

From melinda.shore@gmail.com  Sat Jan  4 11:57:53 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E56E1AE051 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GvgBn_KyEHJF for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 11:57:52 -0800 (PST)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA121AE093 for <ietf@ietf.org>; Sat,  4 Jan 2014 11:57:52 -0800 (PST)
Received: by mail-pb0-f50.google.com with SMTP id rr13so16964608pbb.37 for <ietf@ietf.org>; Sat, 04 Jan 2014 11:57:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=pYp6oFhdTKTA2KrYOUJXf91s5BiI54d02DvDe1OLS54=; b=BBKZAn2ISQKXlCZQzcAikxxnGAHU5KfyuOpHZq51zlxMUmwJoJVVRu0gjalth0vEGM Zmty7MXID0ZIfp6NCKf66GP6TykKq3wXu5ybAG1jvNS32W1wh33Pg+BHFKGFyXO/QlXF zpOW54nxsR9E8b9mTjk3VPcPPaJs38EPR0k0vsq2I4E7hrAK3h8unz08et7gNWxf+2mG 2jMsJqLlehbifoDSzyYqyfM7+1QENcuDkrys0iCbo/TKIYfKGq5JYPEhITgSDctL4qun OpND7yvvFen5L5U3qpqTXgHI8SZgUq3O/7mdtiujuAF9namfIM7n1dg93rdF1SdlB2fy IWUw==
X-Received: by 10.68.138.165 with SMTP id qr5mr90018703pbb.123.1388865465051;  Sat, 04 Jan 2014 11:57:45 -0800 (PST)
Received: from spandex.local (216-67-22-99-rb3.fai.dsl.dynamic.acsalaska.net. [216.67.22.99]) by mx.google.com with ESMTPSA id om6sm117634657pbc.43.2014.01.04.11.57.42 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Jan 2014 11:57:44 -0800 (PST)
Message-ID: <52C867B4.9030500@gmail.com>
Date: Sat, 04 Jan 2014 10:57:40 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <52C8304E.3080802@cs.tcd.ie> <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com> <CAPv4CP8yWNyTxVYDFnseSz1OMqLexFXO_45FnO-EGa3ADM0S2g@mail.gmail.com>
In-Reply-To: <CAPv4CP8yWNyTxVYDFnseSz1OMqLexFXO_45FnO-EGa3ADM0S2g@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 19:57:53 -0000

On 1/4/14 10:54 AM, Scott Brim wrote:
> Yes. I thought that would be the NEXT step after this draft. But
> let's not skip this one. The next will take a bit of time, so let's
> publish this one so the world can see our position.  

So it's a position statement, not a process standard?

Melinda


From brian.e.carpenter@gmail.com  Sat Jan  4 12:01:14 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C67E01AE0A6 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 12:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cdSHNvwQNnlN for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 12:01:13 -0800 (PST)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7C48B1AE099 for <ietf@ietf.org>; Sat,  4 Jan 2014 12:01:13 -0800 (PST)
Received: by mail-pb0-f45.google.com with SMTP id rp16so16909172pbb.18 for <ietf@ietf.org>; Sat, 04 Jan 2014 12:01:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5wqJIse7S0oCF/eVLV5vQF/9C6gpwvmdpbyzSTzj3ik=; b=nArJ7PO/uL5osZx7IMyiYVMLKy7xQHnwv3Rw93aPpQLn+gZb6nISTCYeC8ocEzw/E4 rBQ3AGR5T3gOf97uGWpMulqWAdCuqsXXN7VvnDImvNg23Ebo2IJFS7Jf3Vcx0WBBVWNb ZoeVYVTbzGDNUtB+vzJlYyJyiyoT/jjWnHVqJr7r7f3RaE5kSVl1F6GNEFbHOtlpLgju goOpLPi6xTy4gj7ff0gNWA+GPYsIyLCPzplbwAbdfllDPbWrWop/DdH78exQtUnON8Hb IO78KTrXW1zqIaYN/DkrqBzfNkBtzMmsBxX8QyjhcoUF6t58p8T+QJFwc4+6O4tTWj2G AV9Q==
X-Received: by 10.68.136.66 with SMTP id py2mr16657454pbb.112.1388865665904; Sat, 04 Jan 2014 12:01:05 -0800 (PST)
Received: from [192.168.178.21] (184.196.69.111.dynamic.snap.net.nz. [111.69.196.184]) by mx.google.com with ESMTPSA id hz10sm117659210pbc.36.2014.01.04.12.01.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Jan 2014 12:01:04 -0800 (PST)
Message-ID: <52C8687D.1090700@gmail.com>
Date: Sun, 05 Jan 2014 09:01:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>, <52C8304E.3080802@cs.tcd.ie> <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com>
In-Reply-To: <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 20:01:15 -0000

On 05/01/2014 08:14, Stewart Bryant (stbryant) wrote:
> 
> Sent from my iPad
> 
>> On 4 Jan 2014, at 16:01, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>>
>>
>>
>>> On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
>>> I have been wondering whether a simple update to "A Guide to Writing
>>> A Security Considerations Section" is all that is needed to address
>>> the problem in hand?
>> After a bit of offlist mail with Stewart, it turns out I had
>> misinterpreted the above.
>>
>> I now believe (haven't quite confirmed, but its a fine idea
>> anyway so worth raising here) that what Stewart meant was
>> not to open up 3552 and add this text, (which'd take years) but
>> rather to make the RFC resulting from this draft be just another
>> part of BCP72 (aka RFC 3552).
> 
> Yes, that is what I meant. An RFC that says updates RFC3552 in
> the top left corner, and provides advise on this security issue in
> the same manner and style that RFC3552 deals with all the other
> important security issues.

But, RFC 3552 has a lot of technical meat, and RFC 3365 has quite
specific technical content too. I don't see the present draft as being
in that category at all.

I agree that we need equivalents of those two RFCs for this issue.
There's technical analysis heading in that direction in RFC 6973
and there's draft-trammell-perpass-ppa, but work remains to be done.

    Brian

    Brian



From scott.brim@gmail.com  Sat Jan  4 12:52:38 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04E0B1AE0A0 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 12:52:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crGlQBFNcwGp for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 12:52:37 -0800 (PST)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id EDFB91AE087 for <ietf@ietf.org>; Sat,  4 Jan 2014 12:52:36 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id j17so17548332oag.28 for <ietf@ietf.org>; Sat, 04 Jan 2014 12:52:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qxJ6NNbSjP6Pca3UJps3VkkZaECT+0svQ84XofnUl9w=; b=k+iPsXnw1X9SEicaBPW1vVp2Gx6sIA1uq3Lg2npOSgi569CJYo+xYfjcU2CGV1ZkJB PE+NU3tep8C3BgNoLh/rdeoHSItq7K+9zMEJnpT2yoKxgnItGl3o8AAcYIfYhSl5+gsR sTjQWS3gcvcIV0O993vHy+/7pAKCPek/CQ0k1Xnt61sa+QCNDkHWJNCyow9qZJYwZ8Rh C3dBh3ig4avOvNJqI7adYJefIxwT7q4fHrXqRIEHL8LQutNrPmTZjDxSUCkmmKeO8JWZ SKO+qal86awnGd/E4twWolOaRPdxt5QrHgYAkksgOXtJhfRmHCWSLZXUxT32KDsQ4NIP qKqA==
X-Received: by 10.182.49.166 with SMTP id v6mr65338858obn.13.1388868749033; Sat, 04 Jan 2014 12:52:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sat, 4 Jan 2014 12:52:08 -0800 (PST)
In-Reply-To: <52C867B4.9030500@gmail.com>
References: <26734.1388770438@erosen-linux> <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <52C8304E.3080802@cs.tcd.ie> <7B81CDDA-5CFC-4BA0-819B-C14143FAD7F9@cisco.com> <CAPv4CP8yWNyTxVYDFnseSz1OMqLexFXO_45FnO-EGa3ADM0S2g@mail.gmail.com> <52C867B4.9030500@gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 4 Jan 2014 15:52:08 -0500
Message-ID: <CAPv4CP-1Aupk7PtuXMHXF0Tx_Jjzs7098dDFGPUtnyuJgw5E0w@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: Melinda Shore <melinda.shore@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 20:52:38 -0000

On Sat, Jan 4, 2014 at 2:57 PM, Melinda Shore <melinda.shore@gmail.com> wrote:
> On 1/4/14 10:54 AM, Scott Brim wrote:
>> Yes. I thought that would be the NEXT step after this draft. But
>> let's not skip this one. The next will take a bit of time, so let's
>> publish this one so the world can see our position.
>
> So it's a position statement, not a process standard?

Well, my guess (not being a primary contributor) is that there is a
process change: we're going to give more heed to privacy in security
considerations.

From paf@frobbit.se  Sat Jan  4 13:52:18 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07EF01AE090 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 13:52:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.788
X-Spam-Level: 
X-Spam-Status: No, score=-1.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4UKRDjgtnjCR for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 13:52:16 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 92F081AE00E for <ietf@ietf.org>; Sat,  4 Jan 2014 13:52:15 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::2194:bf39:6fa5:5a33] (unknown [IPv6:2a02:80:3ffc:0:2194:bf39:6fa5:5a33]) by mail.frobbit.se (Postfix) with ESMTPSA id 13A3421EC4; Sat,  4 Jan 2014 22:52:06 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_1AACA9FA-3208-413B-A598-969ED9C5F9B9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IANA blog article
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CAMm+Lwjhkpeh_Oz3o0=fK3KewtOQ7bWBq0LCrjzp_PYnn0P3jA@mail.gmail.com>
Date: Sat, 4 Jan 2014 22:52:05 +0100
Message-Id: <67800BA8-C595-4730-ADC1-5AAE3DBD61B7@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <CAMm+Lwjhkpeh_Oz3o0=fK3KewtOQ7bWBq0LCrjzp_PYnn0P3jA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 21:52:18 -0000

--Apple-Mail=_1AACA9FA-3208-413B-A598-969ED9C5F9B9
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_6037D7C3-B50C-4DB9-A5A2-52E2EAA10EC2"


--Apple-Mail=_6037D7C3-B50C-4DB9-A5A2-52E2EAA10EC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On 4 jan 2014, at 18:15, Phillip Hallam-Baker <hallam@gmail.com> wrote:

> Please read my words as carefully as a wrote them.

I did :-)

> There are excellent reasons why variable length IPv6 addresses would =
have been a bad idea. That is why I separated considerations for IP =
layer, DNS and Applications.=20
>=20
> At the application layer, the concerns are very different. Variable =
length identifiers are not a problem. We use them in RFC822, ASN.1, XML =
and JSON.

I do not see we MUST have variable length addresses in whatever protocol =
we have.

In DNS for example, we do not. Yes, lots of them, but not unlimited =
number of them.

   Patrik


--Apple-Mail=_6037D7C3-B50C-4DB9-A5A2-52E2EAA10EC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 4 =
jan 2014, at 18:15, Phillip Hallam-Baker &lt;<a =
href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; =
wrote:<br><div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-family: LucidaSans-Typewriter; =
font-size: 10px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;">Please read my words as carefully as a wrote =
them.</div></blockquote><div><br></div>I did =
:-)</div><div><br><blockquote type=3D"cite"><div style=3D"font-family: =
LucidaSans-Typewriter; font-size: 10px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">There are excellent reasons why =
variable length IPv6 addresses would have been a bad idea. That is why I =
separated considerations for IP layer, DNS and =
Applications.&nbsp;</div><div style=3D"font-family: =
LucidaSans-Typewriter; font-size: 10px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;"><br></div><div style=3D"font-family:=
 LucidaSans-Typewriter; font-size: 10px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">At the application layer, the =
concerns are very different. Variable length identifiers are not a =
problem. We use them in RFC822, ASN.1, XML and =
JSON.</div></blockquote><br></div><div>I do not see we MUST have =
variable length addresses in whatever protocol we =
have.</div><div><br></div><div>In DNS for example, we do not. Yes, lots =
of them, but not unlimited number of =
them.</div><div><br></div><div>&nbsp; =
&nbsp;Patrik</div><div><br></div></body></html>=

--Apple-Mail=_6037D7C3-B50C-4DB9-A5A2-52E2EAA10EC2--

--Apple-Mail=_1AACA9FA-3208-413B-A598-969ED9C5F9B9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSyIKFrMabGguI180RAhbPAJ45Zvo3Wsc82WfyWfk5MT07aUGfsACdEEpm
Nve3eT3wjr6F8loZbMuWgd0=
=SKNH
-----END PGP SIGNATURE-----

--Apple-Mail=_1AACA9FA-3208-413B-A598-969ED9C5F9B9--

From dhc@dcrocker.net  Sat Jan  4 14:01:42 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25D911AE090 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2Hxwt-a5US8H for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:01:41 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 482C91AE00E for <ietf@ietf.org>; Sat,  4 Jan 2014 14:01: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 s04M1PLl024646 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Jan 2014 14:01:28 -0800
Message-ID: <52C88458.80102@dcrocker.net>
Date: Sat, 04 Jan 2014 13:59:52 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Design Considerations (was - Re: IANA blog article)
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
In-Reply-To: <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 04 Jan 2014 14:01:28 -0800 (PST)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 22:01:42 -0000

On 1/4/2014 1:31 AM, Patrik Fältström wrote:
> What is needed is that the specification do have a consequence analysis regarding expansion of use.


This statement probably should serve as a touchstone to the general 
topic of seeking "design considerations" for new specifications and for 
any "interesting" features or choices that are made.

(Whether such a discussion is part of the specification itself, part of 
a separate document, or merely a highlighted part of the working group 
archive, is a separate issue.)

However pressing groups to make it possible for these considerations to 
be easily reviewed by others could be at least as interesting as getting 
groups to do more/better privacy considerations...

This would not pre-determine the content of acceptable discussion -- 
such as demanding variable- or fixed-length values -- but it presses the 
group to be thoughtful enough to defend and document its choices ahead 
of the choices' being challenged.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From paf@frobbit.se  Sat Jan  4 14:14:18 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5953D1AE0A9 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRadsyPWfG3d for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:14:17 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 1C3221AE00E for <ietf@ietf.org>; Sat,  4 Jan 2014 14:14:17 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::2194:bf39:6fa5:5a33] (unknown [IPv6:2a02:80:3ffc:0:2194:bf39:6fa5:5a33]) by mail.frobbit.se (Postfix) with ESMTPSA id 28CB71FDDE; Sat,  4 Jan 2014 23:14:08 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_7077D380-6BE0-463D-A023-BFB7C9CDB428"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Design Considerations (was - Re: IANA blog article)
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <52C88458.80102@dcrocker.net>
Date: Sat, 4 Jan 2014 23:14:05 +0100
Message-Id: <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <52C88458.80102@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 22:14:18 -0000

--Apple-Mail=_7077D380-6BE0-463D-A023-BFB7C9CDB428
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Not a complaint on Dave or anyone else specifically in this thread BUT:

1. Jari posted a blog post about IANA, and I ask myself why IETF (yes, =
"we") can not stay focused

2. Jari explicitly said where comments where to be sent, and it was not =
this list

Now, to the very interesting topic we are discussing ;-)

On 4 jan 2014, at 22:59, Dave Crocker <dhc@dcrocker.net> wrote:

> On 1/4/2014 1:31 AM, Patrik F=E4ltstr=F6m wrote:
>> What is needed is that the specification do have a consequence =
analysis regarding expansion of use.
>=20
> This statement probably should serve as a touchstone to the general =
topic of seeking "design considerations" for new specifications and for =
any "interesting" features or choices that are made.
>=20
> (Whether such a discussion is part of the specification itself, part =
of a separate document, or merely a highlighted part of the working =
group archive, is a separate issue.)
>=20
> However pressing groups to make it possible for these considerations =
to be easily reviewed by others could be at least as interesting as =
getting groups to do more/better privacy considerations...
>=20
> This would not pre-determine the content of acceptable discussion -- =
such as demanding variable- or fixed-length values -- but it presses the =
group to be thoughtful enough to defend and document its choices ahead =
of the choices' being challenged.

Yes, but I was more thinking of how good it would be *if* we start talk =
about scaling seriously in the form of the designer would talk about =
what design criteria was part of the design, and(!) what suggestions =
there are about changes if/when the address space is not large enough.

   Patrik


--Apple-Mail=_7077D380-6BE0-463D-A023-BFB7C9CDB428
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSyIetrMabGguI180RAgoOAJ98CuqDlZA3Ry1MH8UxcwZmfrQFoACfRwyR
2XddskMTFMKd5VSnqxHbaM4=
=Oxw+
-----END PGP SIGNATURE-----

--Apple-Mail=_7077D380-6BE0-463D-A023-BFB7C9CDB428--

From dhc@dcrocker.net  Sat Jan  4 14:23:53 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2CD91AE0AA; Sat,  4 Jan 2014 14:23:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMqkQWdPVTvU; Sat,  4 Jan 2014 14:23:52 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 312C81AE00E; Sat,  4 Jan 2014 14:23:52 -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 s04MNe0G024934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Jan 2014 14:23:44 -0800
Message-ID: <52C88990.3070209@dcrocker.net>
Date: Sat, 04 Jan 2014 14:22:08 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, The IESG <iesg-secretary@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <m2d2k8lffa.wl%randy@psg.com>
In-Reply-To: <m2d2k8lffa.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 04 Jan 2014 14:23:44 -0800 (PST)
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 22:23:54 -0000

On 1/3/2014 5:11 PM, Randy Bush wrote:
> this draft could be used by those nasty ADs to abuse working groups and
> draft authors.  perhaps if it is experimental.


Even if such pointedly mocking behavior were professionally acceptable, 
the effectiveness of the pseudo-echoing taunt is undermined by its basic 
misapplication.

The current draft is seeking Informational, not BCP.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From dhc@dcrocker.net  Sat Jan  4 14:35:31 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7BC1AE0AA for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:35:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eC8537ONCoD6 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:35:29 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A34291AE0A7 for <ietf@ietf.org>; Sat,  4 Jan 2014 14:35:29 -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 s04MZGtg025038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 4 Jan 2014 14:35:20 -0800
Message-ID: <52C88C48.8070106@dcrocker.net>
Date: Sat, 04 Jan 2014 14:33:44 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.com>
In-Reply-To: <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.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.66]); Sat, 04 Jan 2014 14:35:20 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 04 Jan 2014 22:35:31 -0000

Michael,

Thanks for the comments.  Responding strictly on my own behalf:


On 1/3/2014 9:32 AM, Scharf, Michael (Michael) wrote:
> First, the document could perhaps mention that during the adoption of
> a draft there can be a discussion about the planned status (e.g., STD
> vs. EXP), even if the status can change later in the process. In
> TCPM, this is almost always the case, and therefore the chairs have
> to consider the planned status as one question when creating/adopting
> a WG draft.

This sounds like another bullet in the Section 2.2. Criteria for 
Adoption list.  Possibly:

    *  Does the intended status of the document seem reasonable to the
       working group?


> Second, I am not sure if the following statement in Section 2.2 could
> be detailed a bit:
>
> *  Is there strong working group support for working on the draft?
>
> Actually, in TCPM, the "working group support for working on the
> draft" is often not the most important criteria for adoption. The key
> one is the more specific question whether there indeed "working group
> energy for contributing and reviewing". For instance, sometimes, we
> have the following situation: The community really likes a new,
> interesting idea, and the WG therefore really wants that "somebody"
> works out all the nasty protocol details that a full spec would
> require. This is typically left to the authors of the individual
> document proposing this idea. Yet, since TCPM deals with a core
> Internet protocol, having a WG document also implies that the WG
> should indeed verify this spec, e.g., in all the corner cases that
> can occur in a complex protocol. And, surprise, surprise, finding
> volunteers for that is often more difficult than finding people that
> really like an idea and want the WG to work on it... As a result, the
> chairs have to think about the completion of any new WG document
> quite a bit in advance...

Hmmm.  Certainly a reasonable scenario, IMO, but I would have thought 
the current draft covers what you describe.

The fact that you don't see that leaves me unclear how to fix this, so 
that there's no doubt it is considered a legitimate scenario.

      1. The document discusses the difference between having the 
document be author-driven vs. working-driven, in Section 3.

      2. I think of the wg reviewing effort you describe as "working on 
the draft" and hence qualifying under the bullet you quote.

Best I can think of is to ask you for suggested text changes/additions.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From simon@josefsson.org  Sat Jan  4 14:51:11 2014
Return-Path: <simon@josefsson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 026C51AE094 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.149
X-Spam-Level: *
X-Spam-Status: No, score=1.149 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_SE=0.35, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vi401zCE0itB for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 14:51:10 -0800 (PST)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) by ietfa.amsl.com (Postfix) with ESMTP id CC3CB1AE00E for <ietf@ietf.org>; Sat,  4 Jan 2014 14:51:09 -0800 (PST)
Received: from latte.josefsson.org (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id s04MoxhT013075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sat, 4 Jan 2014 23:51:01 +0100
Date: Sat, 4 Jan 2014 23:50:58 +0100
From: Simon Josefsson <simon@josefsson.org>
To: ietf@ietf.org
Subject: Necrotizing Fasciitis
Message-ID: <20140104235058.5b9ec017@latte.josefsson.org>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.97.8 at duva.sjd.se
X-Virus-Status: Clean
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jan 2014 22:51:11 -0000

If anyone wonders why they haven't received any responses from me
lately, below is the answer.

http://blog.josefsson.org/2014/01/05/necrotizing-fasciitis/

/Simon

From hallam@gmail.com  Sat Jan  4 18:44:35 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16D1E1AE0DC for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 18:44:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnaX5sJgtr6l for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 18:44:33 -0800 (PST)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 1C31B1AE090 for <ietf@ietf.org>; Sat,  4 Jan 2014 18:44:32 -0800 (PST)
Received: by mail-lb0-f171.google.com with SMTP id w7so9207928lbi.30 for <ietf@ietf.org>; Sat, 04 Jan 2014 18:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=crDdyfEA09EUxwdJSfayBoB346FN/44FYLFIEFAJJtE=; b=MEdK3iGrJuoromyUENQpJraQCrAUHi1waJ5Lm68pUqnL2k957tj+kbeApTUbV8W5m1 h32hI+lLxCFsZKd1DeFks64Ka8IL7hijw1hNI8Rl18JkHcLXokqDg6L22HefbG5dWye/ r4rDSpkb+ER98OesM6dLwlmhodtbwiFLhFnQoxF8HZwyw4pao2WoYD6yBmnpm5yDZlwo 5JWIkQ9eaTlr6TAZOAK96zgAteWg0UJdYHFCcHFqZeTyDuWB9capS03K0zkm7O5GzSJw FNZw3yb3CrIH75z3+q88bOZGpuujYlXuwQf7klayc7ZvWNlgEO88gqxTpXhYmCebflDu 3/1g==
MIME-Version: 1.0
X-Received: by 10.112.143.163 with SMTP id sf3mr37855049lbb.20.1388889864557;  Sat, 04 Jan 2014 18:44:24 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sat, 4 Jan 2014 18:44:24 -0800 (PST)
In-Reply-To: <67800BA8-C595-4730-ADC1-5AAE3DBD61B7@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <CAMm+Lwjhkpeh_Oz3o0=fK3KewtOQ7bWBq0LCrjzp_PYnn0P3jA@mail.gmail.com> <67800BA8-C595-4730-ADC1-5AAE3DBD61B7@frobbit.se>
Date: Sat, 4 Jan 2014 21:44:24 -0500
Message-ID: <CAMm+Lwg5iA8Hnw-hWQWr5cJ8hEzK4LPwD4AvYoGx8dmYXST8yA@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=089e01227a0c0259cb04ef301f93
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 02:44:35 -0000

--089e01227a0c0259cb04ef301f93
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Sat, Jan 4, 2014 at 4:52 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote=
:

> On 4 jan 2014, at 18:15, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
> Please read my words as carefully as a wrote them.
>
>
> I did :-)
>
> There are excellent reasons why variable length IPv6 addresses would have
> been a bad idea. That is why I separated considerations for IP layer, DNS
> and Applications.
>
> At the application layer, the concerns are very different. Variable lengt=
h
> identifiers are not a problem. We use them in RFC822, ASN.1, XML and JSON=
.
>
>
> I do not see we MUST have variable length addresses in whatever protocol
> we have.
>
> In DNS for example, we do not. Yes, lots of them, but not unlimited numbe=
r
> of them.
>

In my original post I set out three cases, IP, DNS and everything else. I
stated that the extensibility requirement should apply as a MUST only to
everything else and that it should only apply to DNS if there was a major
backwards incompatible change.

The response I got was that people cut the post to say all code points
should be effectively unlimited and then gave first IP as an example and
now you are giving DNS as an example.


DNS is not an application layer protocol, it is one of the layers on which
applications build.


--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Sat, Jan 4, 2014 at 4:52 PM, Patrik F=E4ltstr=F6m <span dir=3D"l=
tr">&lt;<a href=3D"mailto:paf@frobbit.se" target=3D"_blank">paf@frobbit.se<=
/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 style=3D"word-wrap:break-word"><div cla=
ss=3D"im">On 4 jan 2014, at 18:15, Phillip Hallam-Baker &lt;<a href=3D"mail=
to:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt; wrote:<br>
</div><div><div class=3D"im"><br><blockquote type=3D"cite"><div style=3D"fo=
nt-family:LucidaSans-Typewriter;font-size:10px;font-style:normal;font-varia=
nt:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-=
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spa=
cing:0px">
Please read my words as carefully as a wrote them.</div></blockquote><div><=
br></div></div>I did :-)</div><div class=3D"im"><div><br><blockquote type=
=3D"cite"><div style=3D"font-family:LucidaSans-Typewriter;font-size:10px;fo=
nt-style:normal;font-variant:normal;font-weight:normal;letter-spacing:norma=
l;line-height:normal;text-align:start;text-indent:0px;text-transform:none;w=
hite-space:normal;word-spacing:0px">
There are excellent reasons why variable length IPv6 addresses would have b=
een a bad idea. That is why I separated considerations for IP layer, DNS an=
d Applications.=A0</div><div style=3D"font-family:LucidaSans-Typewriter;fon=
t-size:10px;font-style:normal;font-variant:normal;font-weight:normal;letter=
-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-tr=
ansform:none;white-space:normal;word-spacing:0px">
<br></div><div style=3D"font-family:LucidaSans-Typewriter;font-size:10px;fo=
nt-style:normal;font-variant:normal;font-weight:normal;letter-spacing:norma=
l;line-height:normal;text-align:start;text-indent:0px;text-transform:none;w=
hite-space:normal;word-spacing:0px">
At the application layer, the concerns are very different. Variable length =
identifiers are not a problem. We use them in RFC822, ASN.1, XML and JSON.<=
/div></blockquote><br></div></div><div>I do not see we MUST have variable l=
ength addresses in whatever protocol we have.</div>
<div><br></div><div>In DNS for example, we do not. Yes, lots of them, but n=
ot unlimited number of them.</div></div></blockquote><div><br></div><div>In=
 my original post I set out three cases, IP, DNS and everything else. I sta=
ted that the extensibility requirement should apply as a MUST only to every=
thing else and that it should only apply to DNS if there was a major backwa=
rds incompatible change.</div>
<div><br></div><div>The response I got was that people cut the post to say =
all code points should be effectively unlimited and then gave first IP as a=
n example and now you are giving DNS as an example.=A0</div><div><br></div>
<div><br></div><div>DNS is not an application layer protocol, it is one of =
the layers on which applications build.=A0</div><div>=A0</div></div><div><b=
r></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallamba=
ker.com/</a><br>

</div></div>

--089e01227a0c0259cb04ef301f93--

From bmanning@isi.edu  Sat Jan  4 22:17:04 2014
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13E351A1F71 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 22:17:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.038
X-Spam-Level: 
X-Spam-Status: No, score=-3.038 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KBGN9Oe2mvFq for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 22:17:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 67CD21A1F61 for <ietf@ietf.org>; Sat,  4 Jan 2014 22:17:02 -0800 (PST)
Received: from [192.168.1.7] (h27.129.49.24.static.bajabb.com [24.49.129.27] (may be forged)) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s056G61B021311 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 4 Jan 2014 22:16:16 -0800 (PST)
Subject: Re: IANA blog article
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\))
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
Date: Sat, 4 Jan 2014 22:16:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se>
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1816)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 06:17:04 -0000

Jari, you can=92t be serious.  unlimited means -without- limit, not just =
the limits of your imagination.
Patrick,  perhaps more to the point, the ramifications (consequence =
analysis) of managing transitions between variable code/address realms. =20=

Its not just expansion, its flow between larger/smaller, and =
smaller/larger.
we are back to NAT/ALGs _again_

/bill
Neca eos omnes.  Deus suos agnoscet.

On 4January2014Saturday, at 1:31, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:

>=20
> On 4 jan 2014, at 09:29, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
>>> One important change is that every future application protocol =
proposal should be required to have an effectively unlimited code space =
for assignment.
>>=20
>> Agree.
>=20
> I do not agree regarding the term "unlimited".
>=20
> What is needed is that the specification do have a consequence =
analysis regarding expansion of use.
>=20
>   Patrik
>=20


From paf@frobbit.se  Sat Jan  4 23:48:47 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 702621AC828 for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 23:48:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NdVFIH_PvJ5T for <ietf@ietfa.amsl.com>; Sat,  4 Jan 2014 23:48:46 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 3D7141AC7F3 for <ietf@ietf.org>; Sat,  4 Jan 2014 23:48:46 -0800 (PST)
Received: from [192.168.1.10] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 3A09C21253; Sun,  5 Jan 2014 08:48:37 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_F93F79EC-2A4F-4133-9FE9-40D90FD1FAB9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Necrotizing Fasciitis
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20140104235058.5b9ec017@latte.josefsson.org>
Date: Sun, 5 Jan 2014 08:48:35 +0100
Message-Id: <C3617134-D9F2-4B79-AD72-313CA0BCAC5E@frobbit.se>
References: <20140104235058.5b9ec017@latte.josefsson.org>
To: Simon Josefsson <simon@josefsson.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 07:48:47 -0000

--Apple-Mail=_F93F79EC-2A4F-4133-9FE9-40D90FD1FAB9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 4 jan 2014, at 23:50, Simon Josefsson <simon@josefsson.org> wrote:

> If anyone wonders why they haven't received any responses from me
> lately, below is the answer.
>=20
> http://blog.josefsson.org/2014/01/05/necrotizing-fasciitis/

Simon,

Correct priorities. Take care of you, your family and your friends. =
There is always time for work later, when you feel ready.

Best,

   Patrik


--Apple-Mail=_F93F79EC-2A4F-4133-9FE9-40D90FD1FAB9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSyQ5TrMabGguI180RAlDCAJwLo+PLkma7tF9TUVdruNOqHSJGIgCeOS+Z
r1ezuoV6EV8nZ3MCtK/B4hQ=
=NQ/C
-----END PGP SIGNATURE-----

--Apple-Mail=_F93F79EC-2A4F-4133-9FE9-40D90FD1FAB9--

From paf@frobbit.se  Sun Jan  5 00:06:33 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86EF41AC863 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 00:06:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znGWgP6XZbcF for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 00:06:32 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 78E481AC828 for <ietf@ietf.org>; Sun,  5 Jan 2014 00:06:32 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::2194:bf39:6fa5:5a33] (unknown [IPv6:2a02:80:3ffc:0:2194:bf39:6fa5:5a33]) by mail.frobbit.se (Postfix) with ESMTPSA id 0539C2079E; Sun,  5 Jan 2014 09:06:23 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_B1A52BA6-9530-4483-A849-D9659091833B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IANA blog article
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu>
Date: Sun, 5 Jan 2014 09:06:23 +0100
Message-Id: <E7E9F0F5-878D-41EF-B963-180188E6756A@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu>
To: Bill Manning <bmanning@isi.edu>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 08:06:33 -0000

--Apple-Mail=_B1A52BA6-9530-4483-A849-D9659091833B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 5 jan 2014, at 07:16, manning bill <bmanning@isi.edu> wrote:

> Jari, you can=92t be serious.  unlimited means -without- limit, not =
just the limits of your imagination.

Bill, it was not Jari, it was Phillip Hallam-Baker that said =
"unlimited", which I objected to.

   Patrik


--Apple-Mail=_B1A52BA6-9530-4483-A849-D9659091833B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSyRJ/rMabGguI180RAlGAAJ9FycHYzkquYflybv/bQA7N1GM9QwCeNb50
F2YHmeGRWbmkShrP0JB8lqM=
=Hhbd
-----END PGP SIGNATURE-----

--Apple-Mail=_B1A52BA6-9530-4483-A849-D9659091833B--

From sm@elandsys.com  Sun Jan  5 03:25:10 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFEF01AE0F6 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 03:25:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5fSlWXQ6blIV for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 03:25: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 AFAFC1AE0EC for <ietf@ietf.org>; Sun,  5 Jan 2014 03:25:08 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.224]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s05BOdSc027968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Jan 2014 03:24:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388921096; bh=SoHPRuMtG03gIBx6ih7JNhcmiKVkoTBT5iWDZ3VZulA=; h=Date:To:From:Subject:In-Reply-To:References; b=4WANpw3nYBxnOia5M4qtg/xE2Ee0UQG0UGKGz6ZAOMFekjBPbAZrSzzWg4U54i69Y aZu2RTPAzCYXqlMp3Y/tKL6gdHmBMhvpzH+fs8VAhCOPJid4IkI3FxoqOiADGTIhtd IVic5NYLyuFyYClgb97qrXek910G+Y3NXbPbLWwk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1388921096; i=@elandsys.com; bh=SoHPRuMtG03gIBx6ih7JNhcmiKVkoTBT5iWDZ3VZulA=; h=Date:To:From:Subject:In-Reply-To:References; b=k610yAjlVu+tEAJjTXo8+5xHuUHWF+ogpeP/FJaBWB2uYGBimZCHD6kwpyMlNLkXS e0mRLsNauimc+bqM5O6mBm3jsYTwQLpFiDKVwKugs6rIJhK5nZFTw1Im3LR5/hB5Ek lGwyzPfWnomDJgxnS6LN6dRa7r09EE1BA199XgDg=
Message-Id: <6.2.5.6.2.20140105002400.0b5f3c20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 05 Jan 2014 03:01:13 -0800
To: ietf@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
References: <20140103151454.20579.95323.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 11:25:11 -0000

Hi Dave, Adrian,
At 07:14 03-01-2014, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Creating an IETF Working Group Draft'
>   <draft-crocker-id-adoption-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

Thanks for writing this document.  Over a year ago there was a 
discussion on the a working group mailing list about the (WG) 
adoption of a draft.  It highlighted that a significant number of 
participants do not share the same view of what they are being asked 
when there is a call for adoption of a draft.  The lack of 
documentation, whether formal or informal, makes it difficult for 
someone new to understand what is being asked.  I don't have a strong 
opinion about whether the documentation should be in a Wiki or a RFC.

 From Section 1.2:

   "A core premise of IETF working groups is that the working group has
    final authority over the content of its documents, within the
    constraints of the working group charter.  No individual has special
    authority for the content."

This can be interpreted in different ways.  It has been stated that 
the document editor is responsible for ensuring that a draft 
accurately reflects the decisions that have been made by the working 
group.  The above text can be read as meaning that the document 
editor does not have any authority over the editorial changes.  An 
alternative would be to drop the "no individual ..." sentence.

In Section 3:

   "NOTE:    The distinction between an 'author' and an 'editor' is, at
       best, subjective.  A simplistic rule of thumb is that editors tend
       to do the mechanics of incorporating working group detail, whereas
       tend to create the detail, subject to working group approval."

The word "authors" may be missing before "whereas tend ...".

In Section 4:

   "Absent charter restrictions, a working group is free to create new
    documents."

Such decisions can be controversial.  It is stated (in another 
document) that a charter
is a contract between a working group and the IETF to perform a set 
of tasks.  As an example, a charter might not mention that the 
working group can work on standardizing X.  The working group Chair 
posts a message about the intent to adopt a draft about standardizing 
X.  It might not be clear to some participants that the working group 
intended to take on such work as that task was not mentioned in the 
charter.  To say it differently, a person may consider the new 
document as something minimal where the administrative overhead is 
not worth the effort; someone else might consider that he or she has 
not been given a fair chance to submit a proposal (see competing 
draft discussed in Section 5.2).

In Section 4:

   "It is not required that all drafts start as the effort of an idividual."

There is a typo for "individual".

In Section 5:

   "If the working group has already adopted an I-D on a specific
    topic, the posting of a new individual I-D on the same topic
    could be seen as an attack on the working group processes or
    decisions.  However, posting an I-D is often a good way to put
    new ideas into concrete form and into the public domain for
    consideration and discussion."

As a nit the draft is not in the public domain.  That term is 
sometimes read as "no one owns or controls the material in any 
way".  The quoted text mentions that posting a new (individual) draft 
can be seen as an attack but it is a good way to put ideas in 
concrete form.  It is like saying doing X is good but if a person 
does X the person will look bad.  It is not clear what the guide to 
common practice is.

Regards,
S. Moonesamy  


From ron.even.tlv@gmail.com  Sun Jan  5 04:32:40 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBA41AE3E7; Sun,  5 Jan 2014 04:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2YviX7tnTVdf; Sun,  5 Jan 2014 04:32:38 -0800 (PST)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id C6B171AE3E4; Sun,  5 Jan 2014 04:32:37 -0800 (PST)
Received: by mail-ee0-f48.google.com with SMTP id e49so7296692eek.21 for <multiple recipients>; Sun, 05 Jan 2014 04:32:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=tbsLjjtvpKtvKwpX93zJjgzORyUjpxLVOGZXnkDnhKo=; b=1IjC70AOyXMUVxzqHi9EgMdcjGw96fegPHIov42cd4nRWFZ9AWRu+X5F7yveoLjF0i zKmdTMJ1hcRa8yxTLGPmG8JBYLAR5sI1pFZWZEU/hOIshgGEoa//n1d+wym/J5J/+7/H NT5xIDZ5XAJAl8nrplgglxRrFxVHzOSCqmGePzIhuGAWaGOHrdDOhsKWe7UfJNDAmqu1 t9RsbpszFhWj+omWu7mAJRqZqqyyoNHAA8KABU/oBdet/OShY+kzurS+AIjh7H2UoHVz 475YQr5jKR17krSAk8fFg8tdimBk/vM7FtbIIa4EMXeQPDQSYn+xSsBQLbKQ6GjbdloJ 2KQA==
X-Received: by 10.14.194.131 with SMTP id m3mr84100400een.2.1388925149359; Sun, 05 Jan 2014 04:32:29 -0800 (PST)
Received: from RoniE ([109.64.17.204]) by mx.google.com with ESMTPSA id a51sm161747789eeh.8.2014.01.05.04.32.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 05 Jan 2014 04:32:28 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-idr-extcomm-iana.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-idr-extcomm-iana-02
Date: Sun, 5 Jan 2014 14:28:49 +0200
Message-ID: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0BB4_01CF0A22.7573E890"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8KEZjLiHThTsGxQfWaz2m0UstXsA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 12:32:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0BB4_01CF0A22.7573E890
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-idr-extcomm-iana-02

Reviewer: Roni Even

Review Date:2014-1-5

IETF LC End Date: 

IESG Telechat date: 2014-1-9

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

1.	I assume that the text in the IANA registry will reflect that the
old registries are close and point at the ones that replace them.  I noticed
that the document was prepared in cooperation with IANA so I assume that
there will be no problems.

 


------=_NextPart_000_0BB4_01CF0A22.7573E890
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1212841117;
	mso-list-type:hybrid;
	mso-list-template-ids:1031841726 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"'>draft-ietf-idr-extcomm-iana-02<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:2014&#8211;1-5<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: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: 2014-1-9<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 a standard track 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'>I =
assume that the text in the IANA registry will reflect that the old =
registries are close and point at the ones that replace them.&nbsp; I =
noticed that the document was prepared in cooperation with IANA so I =
assume that there will be no problems.<o:p></o:p></li></ol><p =
class=3DMsoNormal><span lang=3DHE dir=3DRTL =
style=3D'font-family:"Arial","sans-serif"'><o:p>&nbsp;</o:p></span></p></=
div></body></html>
------=_NextPart_000_0BB4_01CF0A22.7573E890--


From lear@cisco.com  Sun Jan  5 04:56:14 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADC711AE52C for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 04:56:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJt0L7z6iOwP for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 04:56:13 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id D2B191AE52B for <ietf@ietf.org>; Sun,  5 Jan 2014 04:56:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1869; q=dns/txt; s=iport; t=1388926565; x=1390136165; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Z2A314XGfBmH90LROnURs05XEZHFLMvXPuFw2PKj51g=; b=LhdCXgenUfioPVhTTNFHSrtYEbtkO5ykkszRS/oItdnNTSnB4BknPR51 HRViQUExngCNrpySJquDvlVejuMeJKsTMlyOYA8I6GQHZXDO1e6o7xBH7 um1X5YUOYR8yMDIGnkM8XEUTbTKJRe5PFAOQfM0m4iLp7gTUADPaKAtEm o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAApVyVKQ/khL/2dsb2JhbABYgwuEC7YtgQwWdIIlAQEBAwEjSA0BBQsLGgIFFgsCAgkDAgECASsaBgEMAQcBAYd4CKopggyXOheBKY1mB4JvgUgBA5gXkhWDLjs
X-IronPort-AV: E=Sophos;i="4.95,607,1384300800";  d="scan'208";a="2534112"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 05 Jan 2014 12:56:03 +0000
Received: from mctiny.local ([10.61.207.114]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s05Cu2dT020058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Jan 2014 12:56:02 GMT
Message-ID: <52C95664.9080607@cisco.com>
Date: Sun, 05 Jan 2014 13:56:04 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IANA blog article
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <CAMm+LwgpCRUrA5qDpASP2FWGjfhmpWRGW_wvg=5ccMTW0SGX+Q@mail.gmail.com>
In-Reply-To: <CAMm+LwgpCRUrA5qDpASP2FWGjfhmpWRGW_wvg=5ccMTW0SGX+Q@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 12:56:14 -0000

Hi Phillip,


On 1/4/14 7:43 PM, Phillip Hallam-Baker wrote:

> IETF should only endorse a single core set of algorithms with a
> maximum of one preferred and one alternative algorithm and this should
> be an IETF consensus, not a WG consensus. A WG might add in additional
> recommendations to support legacy interop, for example 3DES is still a
> defacto requirement for S/MIME.

The 1+1 approach seems a good ideal from an interoperability
perspective.  What we the IETF lack is sufficient expertise to "endorse"
crypto.  Yes we have some people who know some stuff, but not at the
heavy math end of it, which is where you want it.  The benefit of
developing this expertise would be that there could be a go-to place
that is viewed by governments without the need to develop their own
specifications or endorse "in country" specifications.  But that will
take a long time.  This could also be done elsewhere, but the key would
be to follow the OpenStand principles.

How this stuff is endorsed (e.g., an IETF working group or by the whole
of the IETF) is an interesting question.  The question that must be
answered is whether all of our specifications would make use of the same
algorithm in the same way.  If the answer is yes, then we can shut down
registries.  I fear the answer is no, but the aspiration is still a good
one, when it is possible.  Arguably what you are really getting at is
that we need to have the right common building blocks to handle all of
encryption (e.g., TLS, S/MIME, and a few others).  Developers want to
reuse code.  My personal experience is that I have perhaps re-used code
(maybe as we all have) in ways that it was really not intended to be
used, hoping that the semantics were sufficiently close to intended use
(think RFC-5218 and "wildly successful").

Ok, that's my Sunday blather.

Eliot

From hallam@gmail.com  Sun Jan  5 09:36:14 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E647F1AF156 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 09:36:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IdtfoiRQhoe for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 09:36:12 -0800 (PST)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 024711AF150 for <ietf@ietf.org>; Sun,  5 Jan 2014 09:36:11 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id b8so9396358lan.13 for <ietf@ietf.org>; Sun, 05 Jan 2014 09:36:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5Wj8qzkZ6Y7uyw9xAHLNZ5KTTaZakGfs3U+9ndFMzz4=; b=POurqx/7j1jWzsNsAohEzNLP1dz9P3xbC2TADweCEdgCRupvNYxffoizrk8tKnncmB dwk/CSN2+7Ilp5YpPBQ5dFQluI+EyMUjZMgfaW/kQ2FaDDz+YFHqeZ18ZhvsQKskP24c UkaVOSOrl0DdmH6G84ZMtQwgf6j/zRUnW0eHYpPj4+ldjlneaofoZMyYG8pUdsZuUWdh 3N+7pxF5ipk7fD2cE12jDqgAUEwmw2WcJnRi99tnJLpjWvNbKv6ODZu4KMYNpGY/yMJc HMuBlcHvke1jon705EJPkRyZXLgRspcmU6Jm/VjoV2sExOYZOZrmfZWR6hTL9PUlT/LI 1jTw==
MIME-Version: 1.0
X-Received: by 10.112.138.70 with SMTP id qo6mr1784661lbb.34.1388943363187; Sun, 05 Jan 2014 09:36:03 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sun, 5 Jan 2014 09:36:03 -0800 (PST)
In-Reply-To: <E7E9F0F5-878D-41EF-B963-180188E6756A@frobbit.se>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu> <E7E9F0F5-878D-41EF-B963-180188E6756A@frobbit.se>
Date: Sun, 5 Jan 2014 12:36:03 -0500
Message-ID: <CAMm+Lwh3Zi3y7RhVOsD_nbqNrNkgXWgOwARHk5Gxa+EjfAgPvw@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=089e0112c02cc6a8b704ef3c93ea
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Bill Manning <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 17:36:15 -0000

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

One of the points that I should have made in response to Jari is that a
major limitation in his thinking is that he sets out the function of IANA
as an IETF support service rather than an Internet support service.

The distinction is important as there is no reason that IANA should only be
used by the IETF. The IETF is not the only Internet standards making
organization and I hope to see many, many more. There is a natural limit to
the size of organizations and the IETF is at that point. So are OASIS and
W3C. We cannot attempt to scale the development of cool Internet uses by
increasing the size of the IETF and it is counterproductive to try.

If we look at the wider context, there are now communities focused on
single applications that are roughly the size of IETF areas. The Linux
plumbers is the size of the IETF at a similar stage in IETF growth. They
will soon grow to about the same size.


We can't scale organizations but we CAN scale the IANA. The function of the
protocol registries is simply to avoid ambiguous name assignments. Why
limit scope to just protocol?


On Sun, Jan 5, 2014 at 3:06 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrote=
:

>
> On 5 jan 2014, at 07:16, manning bill <bmanning@isi.edu> wrote:
>
> > Jari, you can=92t be serious.  unlimited means -without- limit, not jus=
t
> the limits of your imagination.
>
> Bill, it was not Jari, it was Phillip Hallam-Baker that said "unlimited",
> which I objected to.
>

And I excluded the very protocols you used as examples in your counter
argument. So complaining about Bill mistaking attribution is a bit rich.

And I said 'effectively' unlimited which means without effective limit,
i.e. sufficiently large that there is no conceivable circumstance in which
we would need more. So suggesting that the identifiers need to be
infinitely long is yet another straw man.

RFC822 header tags are not in fact unlimited, I can't remember the limit
offhand but for practical purposes it is 20 bytes. But that is still enough
space to encode a 100bit random identifier in base32 which is certainly
'effectively unlimited'.


The test is whether the risk of code point exhaustion is justification for
limiting registrations. If someone can make the argument that 'we might run
out' then obviously the number of code points is not effectively unlimited.

What I am trying to get away from here is the expectation that every
protocol is going to have a separate registry for every item that might
need to be identified.

Shaving a few bytes should not be an excuse to create a new ongoing
maintenance requirement for IANA and creating an extensibility nightmare
which is what short fixed length codes do.


Now what we could do that would achieve most goals for most people would be
to have a single registry of text labels. Each entry would have four pieces
of information:

1) The label itself
2) A unique numeric code
3) The purpose for which the label is defined
4) References

So "AES" would have the entry

"AES"  4242  Algorithm/Encryption  FIPS-yada-yada

There might then be additional information in the Algorithm/Encryption
registry which would continue to provide additional information (e.g. the
OID assignment, modes etc).




Signup would be by simply entering filling out a web form, similar to the
allocation of OID arcs.


The advantage of this approach is that if someone wants to simply reserve a
label to prevent a conflicting use, this is easily done. It is not even
necessary to specify the use.

The numeric codes can be used for the handful of protocols where byte
shaving is a real concern. A new protocol using the technique would have to
make provision for allowing 64 bit codes but it is unlikely the
registrations would exceed a 4 byte space any time soon.

Another use for the codes would be to define an OID assignment and a URI
form of the same label. Since some codes already have OID and URI forms,
these need to be tracked but that would be best done separately.

I would do this with two registries, one for OIDs, the other for URIs which
would list the code points that are synonyms for codes listed in the text
label table and whether they are canonical.


The current situation suffers from the hierarchical fallacy which is the
mistaken belief that it is useful to separate identifiers by category. The
prime example of this failed notion being the .com, .net and .org
registries in DNS which do nothing but confuse.

Separating the registration of encryption algorithms from other crypto
algorithms does not help because it should be obvious that if FOO is a
symmetric encryption algorithm identifier, it cant be a digest algorithm
either. It is also the case but somewhat less obvious that the FOO label
can't then be a RFC821 command or a RFC822 header either. At least not
unless the use of FOO in the other context is completely specified and
constrained by the symmetric encryption spec.


If we rationalize the operation of IANA we can reduce the amount of work
required in both the IETF space and the IANA. More importantly we can
encourage all the other standards organizations to rely on IANA to register
code points.

--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr">One of the points that I should have made in response to J=
ari is that a major limitation in his thinking is that he sets out the func=
tion of IANA as an IETF support service rather than an Internet support ser=
vice.<div>
<br></div><div>The distinction is important as there is no reason that IANA=
 should only be used by the IETF. The IETF is not the only Internet standar=
ds making organization and I hope to see many, many more. There is a natura=
l limit to the size of organizations and the IETF is at that point. So are =
OASIS and W3C. We cannot attempt to scale the development of cool Internet =
uses by increasing the size of the IETF and it is counterproductive to try.=
</div>
<div><br></div><div>If we look at the wider context, there are now communit=
ies focused on single applications that are roughly the size of IETF areas.=
 The Linux plumbers is the size of the IETF at a similar stage in IETF grow=
th. They will soon grow to about the same size.</div>
<div><br></div><div><br></div><div>We can&#39;t scale organizations but we =
CAN scale the IANA. The function of the protocol registries is simply to av=
oid ambiguous name assignments. Why limit scope to just protocol?<br><div c=
lass=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Sun, Jan 5, 2014 at 3:06 AM, Patrik F=
=E4ltstr=F6m <span dir=3D"ltr">&lt;<a href=3D"mailto:paf@frobbit.se" target=
=3D"_blank">paf@frobbit.se</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<div class=3D"im"><br>
On 5 jan 2014, at 07:16, manning bill &lt;<a href=3D"mailto:bmanning@isi.ed=
u">bmanning@isi.edu</a>&gt; wrote:<br>
<br>
&gt; Jari, you can=92t be serious. =A0unlimited means -without- limit, not =
just the limits of your imagination.<br>
<br>
</div>Bill, it was not Jari, it was Phillip Hallam-Baker that said &quot;un=
limited&quot;, which I objected to.<br></blockquote><div><br></div><div>And=
 I excluded the very protocols you used as examples in your counter argumen=
t. So complaining about Bill mistaking attribution is a bit rich.<br>
</div><div><br></div><div>And I said &#39;effectively&#39; unlimited which =
means without effective limit, i.e. sufficiently large that there is no con=
ceivable circumstance in which we would need more. So suggesting that the i=
dentifiers need to be infinitely long is yet another straw man.</div>
<div><br></div><div>RFC822 header tags are not in fact unlimited, I can&#39=
;t remember the limit offhand but for practical purposes it is 20 bytes. Bu=
t that is still enough space to encode a 100bit random identifier in base32=
 which is certainly &#39;effectively unlimited&#39;.</div>
<div><br></div><div><br></div><div>The test is whether the risk of code poi=
nt exhaustion is justification for limiting registrations. If someone can m=
ake the argument that &#39;we might run out&#39; then obviously the number =
of code points is not effectively unlimited.</div>
<div><br></div><div>What I am trying to get away from here is the expectati=
on that every protocol is going to have a separate registry for every item =
that might need to be identified.=A0</div><div><br></div><div>Shaving a few=
 bytes should not be an excuse to create a new ongoing maintenance requirem=
ent for IANA and creating an extensibility nightmare which is what short fi=
xed length codes do.</div>
</div><div><br></div><div><br></div><div>Now what we could do that would ac=
hieve most goals for most people would be to have a single registry of text=
 labels. Each entry would have four pieces of information:</div><div><br>
</div><div>1) The label itself=A0</div><div>2) A unique numeric code</div><=
div>3) The purpose for which the label is defined</div><div>4) References</=
div><div><br></div><div>So &quot;AES&quot; would have the entry</div><div>
<br></div><div>&quot;AES&quot; =A04242 =A0Algorithm/Encryption =A0FIPS-yada=
-yada</div><div><br></div><div>There might then be additional information i=
n the Algorithm/Encryption registry which would continue to provide additio=
nal information (e.g. the OID assignment, modes etc).</div>
<div><br></div><div><br></div><div><br></div><div><br></div><div>Signup wou=
ld be by simply entering filling out a web form, similar to the allocation =
of OID arcs.</div><div><br></div><div><br></div><div>The advantage of this =
approach is that if someone wants to simply reserve a label to prevent a co=
nflicting use, this is easily done. It is not even necessary to specify the=
 use.</div>
<div><br></div><div>The numeric codes can be used for the handful of protoc=
ols where byte shaving is a real concern. A new protocol using the techniqu=
e would have to make provision for allowing 64 bit codes but it is unlikely=
 the registrations would exceed a 4 byte space any time soon.</div>
<div><br></div><div>Another use for the codes would be to define an OID ass=
ignment and a URI form of the same label. Since some codes already have OID=
 and URI forms, these need to be tracked but that would be best done separa=
tely.</div>
<div><br></div><div>I would do this with two registries, one for OIDs, the =
other for URIs which would list the code points that are synonyms for codes=
 listed in the text label table and whether they are canonical.</div><div>
<br></div><div><br></div><div>The current situation suffers from the hierar=
chical fallacy which is the mistaken belief that it is useful to separate i=
dentifiers by category. The prime example of this failed notion being the .=
com, .net and .org registries in DNS which do nothing but confuse.</div>
<div><br></div><div>Separating the registration of encryption algorithms fr=
om other crypto algorithms does not help because it should be obvious that =
if FOO is a symmetric encryption algorithm identifier, it cant be a digest =
algorithm either. It is also the case but somewhat less obvious that the FO=
O label can&#39;t then be a RFC821 command or a RFC822 header either. At le=
ast not unless the use of FOO in the other context is completely specified =
and constrained by the symmetric encryption spec.</div>
<div><br></div><div><br></div><div>If we rationalize the operation of IANA =
we can reduce the amount of work required in both the IETF space and the IA=
NA. More importantly we can encourage all the other standards organizations=
 to rely on IANA to register code points.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div></div>

--089e0112c02cc6a8b704ef3c93ea--

From dhc@dcrocker.net  Sun Jan  5 10:27:37 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D92661AF39E for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:27:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-33tZ1nvbGy for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:27:36 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 749991AF39D for <ietf@ietf.org>; Sun,  5 Jan 2014 10:27:36 -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 s05IRLLg017295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Jan 2014 10:27:25 -0800
Message-ID: <52C9A3AB.7090206@dcrocker.net>
Date: Sun, 05 Jan 2014 10:25:47 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Subject: Focus (was Re: Design Considerations (was - Re: IANA blog article))
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <52C88458.80102@dcrocker.net> <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se>
In-Reply-To: <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 05 Jan 2014 10:27:25 -0800 (PST)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Jan 2014 18:27:38 -0000

On 1/4/2014 2:14 PM, Patrik Fältström wrote:
> 1. Jari posted a blog post about IANA, and I ask myself why IETF (yes, "we") can not stay focused


Email group discussions are easily distracted because:

    1) the group often does not share a strong sense of needing to stay 
focused, and

    2) no one carries the task of trying to help the group stay focused.

Neither of these is special to this mailing list, and we have all seen 
face-to-face meetings suffer the same problem.  However in normal group 
meetings, there is usually pressure to be productive.  We we typically 
have someone driving discussion and getting group agreement to have the 
focus created by that driving.

If we want IETF discussions to do a better job of staying focused, we 
need for a topic to have a facilitator who presses for that focus and we 
need them to do the usual summarizing and polling that we use elsewhere 
in the IETF.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From michael.scharf@alcatel-lucent.com  Sun Jan  5 10:30:40 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280261AF3A3 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qrbu7zmr2kJs for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:30:37 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id B7CA21AE052 for <ietf@ietf.org>; Sun,  5 Jan 2014 10:30:37 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s05IUNXO023554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 5 Jan 2014 12:30:24 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s05IUNqw018653 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 5 Jan 2014 19:30:23 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.70]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Sun, 5 Jan 2014 19:30:23 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Topic: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Index: AQHPCJaajVeEAzcLjk6SIrRU7XqAIJpzKCC6gAHv/ACAAU/IIA==
Date: Sun, 5 Jan 2014 18:30:21 +0000
Message-ID: <655C07320163294895BBADA28372AF5D1562D4@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.com>, <52C88C48.8070106@dcrocker.net>
In-Reply-To: <52C88C48.8070106@dcrocker.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [155.132.188.47]
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 18:30:40 -0000

Hi Dave,=0A=
=0A=
Yes, a statement like "Does the intended status of the document seem reason=
able to the working group?" in Section 2.2 would make sense a lot of sense =
to me. This is what I was looking for.=0A=
=0A=
I agree that the WG energy and willingness to review is somehow part of "wo=
rking on the draft", but I still wonder whether it can be made more explici=
tly. I am not sure whether it belongs to Section 3, which is about authors/=
editors selection. WG energy also seems somehow orthogonal to most other se=
ctions. Here is one idea for specific text (there are other options as well=
): If it is hard to find reviewers for a given topic, the document will inh=
erently move forward rather slowely... So, what about the following questio=
n in Section 2.2:=0A=
=0A=
  * After adoption, is it likely that the document will move forward in a r=
easonable timeframe, e.g., as defined by a charter milestone? =0A=
=0A=
In general, I don't have a particularly strong opinion on my second point, =
and I don't strongly insist on a change of the draft.=0A=
=0A=
Thanks=0A=
=0A=
Michael=0A=
=0A=
________________________________________=0A=
Von: Dave Crocker [dhc@dcrocker.net]=0A=
Gesendet: Samstag, 4. Januar 2014 23:33=0A=
An: Scharf, Michael (Michael); ietf@ietf.org=0A=
Betreff: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IET=
F Working Group Draft) to Informational RFC=0A=
=0A=
Michael,=0A=
=0A=
Thanks for the comments.  Responding strictly on my own behalf:=0A=
=0A=
=0A=
On 1/3/2014 9:32 AM, Scharf, Michael (Michael) wrote:=0A=
> First, the document could perhaps mention that during the adoption of=0A=
> a draft there can be a discussion about the planned status (e.g., STD=0A=
> vs. EXP), even if the status can change later in the process. In=0A=
> TCPM, this is almost always the case, and therefore the chairs have=0A=
> to consider the planned status as one question when creating/adopting=0A=
> a WG draft.=0A=
=0A=
This sounds like another bullet in the Section 2.2. Criteria for=0A=
Adoption list.  Possibly:=0A=
=0A=
    *  Does the intended status of the document seem reasonable to the=0A=
       working group?=0A=
=0A=
=0A=
> Second, I am not sure if the following statement in Section 2.2 could=0A=
> be detailed a bit:=0A=
>=0A=
> *  Is there strong working group support for working on the draft?=0A=
>=0A=
> Actually, in TCPM, the "working group support for working on the=0A=
> draft" is often not the most important criteria for adoption. The key=0A=
> one is the more specific question whether there indeed "working group=0A=
> energy for contributing and reviewing". For instance, sometimes, we=0A=
> have the following situation: The community really likes a new,=0A=
> interesting idea, and the WG therefore really wants that "somebody"=0A=
> works out all the nasty protocol details that a full spec would=0A=
> require. This is typically left to the authors of the individual=0A=
> document proposing this idea. Yet, since TCPM deals with a core=0A=
> Internet protocol, having a WG document also implies that the WG=0A=
> should indeed verify this spec, e.g., in all the corner cases that=0A=
> can occur in a complex protocol. And, surprise, surprise, finding=0A=
> volunteers for that is often more difficult than finding people that=0A=
> really like an idea and want the WG to work on it... As a result, the=0A=
> chairs have to think about the completion of any new WG document=0A=
> quite a bit in advance...=0A=
=0A=
Hmmm.  Certainly a reasonable scenario, IMO, but I would have thought=0A=
the current draft covers what you describe.=0A=
=0A=
The fact that you don't see that leaves me unclear how to fix this, so=0A=
that there's no doubt it is considered a legitimate scenario.=0A=
=0A=
      1. The document discusses the difference between having the=0A=
document be author-driven vs. working-driven, in Section 3.=0A=
=0A=
      2. I think of the wg reviewing effort you describe as "working on=0A=
the draft" and hence qualifying under the bullet you quote.=0A=
=0A=
Best I can think of is to ask you for suggested text changes/additions.=0A=
=0A=
=0A=
d/=0A=
=0A=
--=0A=
Dave Crocker=0A=
Brandenburg InternetWorking=0A=
bbiw.net=0A=

From dhc@dcrocker.net  Sun Jan  5 10:45:09 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F18ED1AF41F for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NWkN8G9c7vnA for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 10:45:07 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6BB331AF41A for <ietf@ietf.org>; Sun,  5 Jan 2014 10:45:07 -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 s05Iif5h017509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 5 Jan 2014 10:44:44 -0800
Message-ID: <52C9A7BA.5050109@dcrocker.net>
Date: Sun, 05 Jan 2014 10:43:06 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org, Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140105002400.0b5f3c20@resistor.net>
In-Reply-To: <6.2.5.6.2.20140105002400.0b5f3c20@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.66]); Sun, 05 Jan 2014 10:44:45 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 05 Jan 2014 18:45:09 -0000

On 1/5/2014 3:01 AM, S Moonesamy wrote:
>  From Section 1.2:
>
>    "A core premise of IETF working groups is that the working group has
>     final authority over the content of its documents, within the
>     constraints of the working group charter.  No individual has special
>     authority for the content."
>
> This can be interpreted in different ways.  It has been stated that the
> document editor is responsible for ensuring that a draft accurately
> reflects the decisions that have been made by the working group.  The
> above text can be read as meaning that the document editor does not have
> any authority over the editorial changes.  An alternative would be to
> drop the "no individual ..." sentence.

Frankly, that sentence is what motivated the paragraph.  The IETF 
periodically has a problem with an author who thinks that their 
judgement carries more weight than the working group's.  This paragraph 
is meant to remind us all that authors are not the final authority for 
content.

If A is an employee of B, A has job responsibilities.  But those 
responsibilities do not (usually) include having more authority over the 
work than B.  A is (merely) and agent of B.

(And B is probably an agent of C.  Everybody works for somebody.  They 
should probably write a song about that.)

An author is appointed by the Chair, but works for the working group and 
the working group has final authority, not the author.  Note that WG 
Guidelines and Procedures (RFC 2418) already makes this point:

      6.1. WG Chair
      ...
      Document development

       Working groups produce documents and documents need authors. The
       Chair must make sure that authors of WG documents incorporate
       changes as agreed to by the WG (see section 6.3).


I'm not sure how to have the text make this point more clearly in the draft.


> In Section 3:
>
>    "NOTE:    The distinction between an 'author' and an 'editor' is, at
>        best, subjective.  A simplistic rule of thumb is that editors tend
>        to do the mechanics of incorporating working group detail, whereas
>        tend to create the detail, subject to working group approval."
>
> The word "authors" may be missing before "whereas tend ...".

You're the third person to note this.  I think that counts as consensus...


> In Section 4:
>
>    "Absent charter restrictions, a working group is free to create new
>     documents."
>
> Such decisions can be controversial.  It is stated (in another document)

Working Group Guidelines & Procedures


> that a charter
> is a contract between a working group and the IETF to perform a set of
> tasks.  As an example, a charter might not mention that the working
> group can work on standardizing X.  The working group Chair posts a
> message about the intent to adopt a draft about standardizing X.  It
> might not be clear to some participants that the working group intended
> to take on such work as that task was not mentioned in the charter.  To
> say it differently, a person may consider the new document as something
> minimal where the administrative overhead is not worth the effort;
> someone else might consider that he or she has not been given a fair
> chance to submit a proposal (see competing draft discussed in Section 5.2).

Interesting point.

I believe working groups often do things like adding a document, or 
splitting a document into two or even combining documents, without 
changing their charter.  I guess I've understood the essential question 
for changing the charter to be when the substance of the group's work is 
changed.

To the extent that a scenario, of the type you describe, causes debate 
within a working group, I would think that it's usually healthy for the 
group, since it can produce better clarity about the group's work.

I'm not sure a document like the current draft should seem to be more 
precise on this than it currently is.  In other words, yes, the 
controversy/confusion you cite happens, but we probably should not 
change the current draft to affect that.


> In Section 5:
>
>    "If the working group has already adopted an I-D on a specific
>     topic, the posting of a new individual I-D on the same topic
>     could be seen as an attack on the working group processes or
>     decisions.  However, posting an I-D is often a good way to put
>     new ideas into concrete form and into the public domain for
>     consideration and discussion."
>
> As a nit the draft is not in the public domain.  That term is sometimes

hmmm. yeah.  Strange wording choice, especially since as you note the 
phrase is a formal term of art.  No memory of what produced that 
wording.  I think better wording would be:

       However, posting an I-D is often a good way to put
       new ideas into concrete form, for public
       consideration and discussion."


> read as "no one owns or controls the material in any way".  The quoted
> text mentions that posting a new (individual) draft can be seen as an
> attack but it is a good way to put ideas in concrete form.  It is like
> saying doing X is good but if a person does X the person will look bad.
> It is not clear what the guide to common practice is.

The paragraph is meant to counter-act the reaction people sometimes 
have, that posting an alternative draft is automatically a bad thing, by 
noting that it can be a valid form of commenting on an existing, other 
draft.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From brian.e.carpenter@gmail.com  Sun Jan  5 11:01:46 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 835571AF4DF for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 11:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90slBzBi3Rkm for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 11:01:44 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 829451AF4DE for <ietf@ietf.org>; Sun,  5 Jan 2014 11:01:44 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id lf10so17826451pab.28 for <ietf@ietf.org>; Sun, 05 Jan 2014 11:01:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4EIh5xqnqo7dLmDosx1unn/neAi/+Y4+HFmC38wl6tg=; b=NRIwlP+7d4SGd1f8yKDzI0yi8N/W9uvL/DTD5v31gxVc2GLPvCMmHqL4z9+f6CIa0W iOROYQGCBLjpCAlhML1OUtRY4175icEOhajcLAL4FpQ+Bzhu7KBInpfUsRLY9oa+1mAj z5L7g2oXzuCbfs6xmuZFYQxDQ0ETGLZMoSFwsvjAzWFK9QF9F+6xIR1OE7kdXXBWNUdD C2ws13hlF0x3PsSfK50b844YS/XtoHiead8ISNtKyJ1br4PBlnaprk9PkdMuJKB8oNu2 dPR4ROU35NnhWMube+6axNQk0qQgWLYFgqBDxg6attPD+OZOt2Us2MhjYTIm4vJcqIaj S5lg==
X-Received: by 10.68.221.233 with SMTP id qh9mr117865953pbc.103.1388948496456;  Sun, 05 Jan 2014 11:01:36 -0800 (PST)
Received: from [192.168.178.21] (97.197.69.111.dynamic.snap.net.nz. [111.69.197.97]) by mx.google.com with ESMTPSA id da3sm68281691pbc.30.2014.01.05.11.01.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 05 Jan 2014 11:01:35 -0800 (PST)
Message-ID: <52C9AC09.3010600@gmail.com>
Date: Mon, 06 Jan 2014 08:01:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: IANA blog article
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu> <E7E9F0F5-878D-41EF-B963-180188E6756A@frobbit.se> <CAMm+Lwh3Zi3y7RhVOsD_nbqNrNkgXWgOwARHk5Gxa+EjfAgPvw@mail.gmail.com>
In-Reply-To: <CAMm+Lwh3Zi3y7RhVOsD_nbqNrNkgXWgOwARHk5Gxa+EjfAgPvw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Bill Manning <bmanning@isi.edu>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 19:01:46 -0000

Phill, that is built into clause 1 of our MoU with ICANN (RFC 2860).
I assume that when the IETF Chair writes about IANA, he's writing
about the part of IANA that we control under that MoU.

    Brian

On 06/01/2014 06:36, Phillip Hallam-Baker wrote:
> One of the points that I should have made in response to Jari is that a=

> major limitation in his thinking is that he sets out the function of IA=
NA
> as an IETF support service rather than an Internet support service.
>=20
> The distinction is important as there is no reason that IANA should onl=
y be
> used by the IETF. The IETF is not the only Internet standards making
> organization and I hope to see many, many more. There is a natural limi=
t to
> the size of organizations and the IETF is at that point. So are OASIS a=
nd
> W3C. We cannot attempt to scale the development of cool Internet uses b=
y
> increasing the size of the IETF and it is counterproductive to try.
>=20
> If we look at the wider context, there are now communities focused on
> single applications that are roughly the size of IETF areas. The Linux
> plumbers is the size of the IETF at a similar stage in IETF growth. The=
y
> will soon grow to about the same size.
>=20
>=20
> We can't scale organizations but we CAN scale the IANA. The function of=
 the
> protocol registries is simply to avoid ambiguous name assignments. Why
> limit scope to just protocol?
>=20
>=20
> On Sun, Jan 5, 2014 at 3:06 AM, Patrik F=C3=A4ltstr=C3=B6m <paf@frobbit=
=2Ese> wrote:
>=20
>> On 5 jan 2014, at 07:16, manning bill <bmanning@isi.edu> wrote:
>>
>>> Jari, you can=E2=80=99t be serious.  unlimited means -without- limit,=
 not just
>> the limits of your imagination.
>>
>> Bill, it was not Jari, it was Phillip Hallam-Baker that said "unlimite=
d",
>> which I objected to.
>>
>=20
> And I excluded the very protocols you used as examples in your counter
> argument. So complaining about Bill mistaking attribution is a bit rich=
=2E
>=20
> And I said 'effectively' unlimited which means without effective limit,=

> i.e. sufficiently large that there is no conceivable circumstance in wh=
ich
> we would need more. So suggesting that the identifiers need to be
> infinitely long is yet another straw man.
>=20
> RFC822 header tags are not in fact unlimited, I can't remember the limi=
t
> offhand but for practical purposes it is 20 bytes. But that is still en=
ough
> space to encode a 100bit random identifier in base32 which is certainly=

> 'effectively unlimited'.
>=20
>=20
> The test is whether the risk of code point exhaustion is justification =
for
> limiting registrations. If someone can make the argument that 'we might=
 run
> out' then obviously the number of code points is not effectively unlimi=
ted.
>=20
> What I am trying to get away from here is the expectation that every
> protocol is going to have a separate registry for every item that might=

> need to be identified.
>=20
> Shaving a few bytes should not be an excuse to create a new ongoing
> maintenance requirement for IANA and creating an extensibility nightmar=
e
> which is what short fixed length codes do.
>=20
>=20
> Now what we could do that would achieve most goals for most people woul=
d be
> to have a single registry of text labels. Each entry would have four pi=
eces
> of information:
>=20
> 1) The label itself
> 2) A unique numeric code
> 3) The purpose for which the label is defined
> 4) References
>=20
> So "AES" would have the entry
>=20
> "AES"  4242  Algorithm/Encryption  FIPS-yada-yada
>=20
> There might then be additional information in the Algorithm/Encryption
> registry which would continue to provide additional information (e.g. t=
he
> OID assignment, modes etc).
>=20
>=20
>=20
>=20
> Signup would be by simply entering filling out a web form, similar to t=
he
> allocation of OID arcs.
>=20
>=20
> The advantage of this approach is that if someone wants to simply reser=
ve a
> label to prevent a conflicting use, this is easily done. It is not even=

> necessary to specify the use.
>=20
> The numeric codes can be used for the handful of protocols where byte
> shaving is a real concern. A new protocol using the technique would hav=
e to
> make provision for allowing 64 bit codes but it is unlikely the
> registrations would exceed a 4 byte space any time soon.
>=20
> Another use for the codes would be to define an OID assignment and a UR=
I
> form of the same label. Since some codes already have OID and URI forms=
,
> these need to be tracked but that would be best done separately.
>=20
> I would do this with two registries, one for OIDs, the other for URIs w=
hich
> would list the code points that are synonyms for codes listed in the te=
xt
> label table and whether they are canonical.
>=20
>=20
> The current situation suffers from the hierarchical fallacy which is th=
e
> mistaken belief that it is useful to separate identifiers by category. =
The
> prime example of this failed notion being the .com, .net and .org
> registries in DNS which do nothing but confuse.
>=20
> Separating the registration of encryption algorithms from other crypto
> algorithms does not help because it should be obvious that if FOO is a
> symmetric encryption algorithm identifier, it cant be a digest algorith=
m
> either. It is also the case but somewhat less obvious that the FOO labe=
l
> can't then be a RFC821 command or a RFC822 header either. At least not
> unless the use of FOO in the other context is completely specified and
> constrained by the symmetric encryption spec.
>=20
>=20
> If we rationalize the operation of IANA we can reduce the amount of wor=
k
> required in both the IETF space and the IANA. More importantly we can
> encourage all the other standards organizations to rely on IANA to regi=
ster
> code points.
>=20


From hallam@gmail.com  Sun Jan  5 11:47:52 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FCF1AF673 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 11:47:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1r8O_ywonj62 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 11:47:49 -0800 (PST)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2781AF674 for <ietf@ietf.org>; Sun,  5 Jan 2014 11:47:48 -0800 (PST)
Received: by mail-la0-f42.google.com with SMTP id ec20so9448422lab.1 for <ietf@ietf.org>; Sun, 05 Jan 2014 11:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XHvWjJ7GQ5V+9XGAgAf374rxaL0c/JbHGwEnx5m0d/I=; b=KhrDzFS9oi2RcGaQd93mUNLeKlS14eikCq8n97TZ0Qq4/cnEJtZr/CkBVnGBQibLz5 E5uG6Hm5CmbA9lV/DDnDtdWlzMfta9cVyRPpq8esfXx/kIoB9sdYmkM7zvH4KjUV9oFk hR3jjUGVh28Tl8m2ZZeF6N3n8ddwjt4I4LB4X+w4S0Rkoiam3rpwzRjBTt6Q3F9bbpJO 3aZXBkQND7+XpuMYHBRasQTBPVHra43M4lCHcNYOM+yQGOpZrugv59oI78kWE48n9F48 x9HW7CGtbW0Rt9ZIdQqAfYR/9cZyCpvTYyi9hJ4fsCYTTP4JK53J+0lnVRNLw/68s+81 ODhQ==
MIME-Version: 1.0
X-Received: by 10.112.168.199 with SMTP id zy7mr181048lbb.68.1388951259571; Sun, 05 Jan 2014 11:47:39 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sun, 5 Jan 2014 11:47:39 -0800 (PST)
In-Reply-To: <52C9AC09.3010600@gmail.com>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <E8FD5637-9B77-4486-9D42-4B43AB8EC9E2@isi.edu> <E7E9F0F5-878D-41EF-B963-180188E6756A@frobbit.se> <CAMm+Lwh3Zi3y7RhVOsD_nbqNrNkgXWgOwARHk5Gxa+EjfAgPvw@mail.gmail.com> <52C9AC09.3010600@gmail.com>
Date: Sun, 5 Jan 2014 14:47:39 -0500
Message-ID: <CAMm+LwiZXodo3XBocP=Z7rBt8FMUtQGY5pBzVZ3qc6DuFh3PHw@mail.gmail.com>
Subject: Re: IANA blog article
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c269146fec5804ef3e6afe
Cc: Bill Manning <bmanning@isi.edu>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 19:47:52 -0000

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

I know it is there in theory from the IETF end and in practice at the IANA
end. I didn't see Jari advancing that as a goal in the article.

But that theory does not quite align with the current registry organization
with the crypto alg registries aligned to protocols rather than being
generic identifiers. And there is still an element that believes that the
purpose of the IETF is to protect the Internet from the mistakes of bad
wizards.


What I am doing is thinking through what it would take to make the theory a
reality. Right now we have a bizarre situation where W3C takes the IETF
crypto alg names, splices a URL prefix on the front and cuts a new URL.

The DANE folk just tried to define alg identifiers for their spec and found
that there were four different labels defined for SHA-2, 256 bit in the
IETF already.



On Sun, Jan 5, 2014 at 2:01 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Phill, that is built into clause 1 of our MoU with ICANN (RFC 2860).
> I assume that when the IETF Chair writes about IANA, he's writing
> about the part of IANA that we control under that MoU.
>
>     Brian
>
> On 06/01/2014 06:36, Phillip Hallam-Baker wrote:
> > One of the points that I should have made in response to Jari is that a
> > major limitation in his thinking is that he sets out the function of IA=
NA
> > as an IETF support service rather than an Internet support service.
> >
> > The distinction is important as there is no reason that IANA should onl=
y
> be
> > used by the IETF. The IETF is not the only Internet standards making
> > organization and I hope to see many, many more. There is a natural limi=
t
> to
> > the size of organizations and the IETF is at that point. So are OASIS a=
nd
> > W3C. We cannot attempt to scale the development of cool Internet uses b=
y
> > increasing the size of the IETF and it is counterproductive to try.
> >
> > If we look at the wider context, there are now communities focused on
> > single applications that are roughly the size of IETF areas. The Linux
> > plumbers is the size of the IETF at a similar stage in IETF growth. The=
y
> > will soon grow to about the same size.
> >
> >
> > We can't scale organizations but we CAN scale the IANA. The function of
> the
> > protocol registries is simply to avoid ambiguous name assignments. Why
> > limit scope to just protocol?
> >
> >
> > On Sun, Jan 5, 2014 at 3:06 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> w=
rote:
> >
> >> On 5 jan 2014, at 07:16, manning bill <bmanning@isi.edu> wrote:
> >>
> >>> Jari, you can=92t be serious.  unlimited means -without- limit, not j=
ust
> >> the limits of your imagination.
> >>
> >> Bill, it was not Jari, it was Phillip Hallam-Baker that said
> "unlimited",
> >> which I objected to.
> >>
> >
> > And I excluded the very protocols you used as examples in your counter
> > argument. So complaining about Bill mistaking attribution is a bit rich=
.
> >
> > And I said 'effectively' unlimited which means without effective limit,
> > i.e. sufficiently large that there is no conceivable circumstance in
> which
> > we would need more. So suggesting that the identifiers need to be
> > infinitely long is yet another straw man.
> >
> > RFC822 header tags are not in fact unlimited, I can't remember the limi=
t
> > offhand but for practical purposes it is 20 bytes. But that is still
> enough
> > space to encode a 100bit random identifier in base32 which is certainly
> > 'effectively unlimited'.
> >
> >
> > The test is whether the risk of code point exhaustion is justification
> for
> > limiting registrations. If someone can make the argument that 'we might
> run
> > out' then obviously the number of code points is not effectively
> unlimited.
> >
> > What I am trying to get away from here is the expectation that every
> > protocol is going to have a separate registry for every item that might
> > need to be identified.
> >
> > Shaving a few bytes should not be an excuse to create a new ongoing
> > maintenance requirement for IANA and creating an extensibility nightmar=
e
> > which is what short fixed length codes do.
> >
> >
> > Now what we could do that would achieve most goals for most people woul=
d
> be
> > to have a single registry of text labels. Each entry would have four
> pieces
> > of information:
> >
> > 1) The label itself
> > 2) A unique numeric code
> > 3) The purpose for which the label is defined
> > 4) References
> >
> > So "AES" would have the entry
> >
> > "AES"  4242  Algorithm/Encryption  FIPS-yada-yada
> >
> > There might then be additional information in the Algorithm/Encryption
> > registry which would continue to provide additional information (e.g. t=
he
> > OID assignment, modes etc).
> >
> >
> >
> >
> > Signup would be by simply entering filling out a web form, similar to t=
he
> > allocation of OID arcs.
> >
> >
> > The advantage of this approach is that if someone wants to simply
> reserve a
> > label to prevent a conflicting use, this is easily done. It is not even
> > necessary to specify the use.
> >
> > The numeric codes can be used for the handful of protocols where byte
> > shaving is a real concern. A new protocol using the technique would hav=
e
> to
> > make provision for allowing 64 bit codes but it is unlikely the
> > registrations would exceed a 4 byte space any time soon.
> >
> > Another use for the codes would be to define an OID assignment and a UR=
I
> > form of the same label. Since some codes already have OID and URI forms=
,
> > these need to be tracked but that would be best done separately.
> >
> > I would do this with two registries, one for OIDs, the other for URIs
> which
> > would list the code points that are synonyms for codes listed in the te=
xt
> > label table and whether they are canonical.
> >
> >
> > The current situation suffers from the hierarchical fallacy which is th=
e
> > mistaken belief that it is useful to separate identifiers by category.
> The
> > prime example of this failed notion being the .com, .net and .org
> > registries in DNS which do nothing but confuse.
> >
> > Separating the registration of encryption algorithms from other crypto
> > algorithms does not help because it should be obvious that if FOO is a
> > symmetric encryption algorithm identifier, it cant be a digest algorith=
m
> > either. It is also the case but somewhat less obvious that the FOO labe=
l
> > can't then be a RFC821 command or a RFC822 header either. At least not
> > unless the use of FOO in the other context is completely specified and
> > constrained by the symmetric encryption spec.
> >
> >
> > If we rationalize the operation of IANA we can reduce the amount of wor=
k
> > required in both the IETF space and the IANA. More importantly we can
> > encourage all the other standards organizations to rely on IANA to
> register
> > code points.
> >
>
>


--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr">I know it is there in theory from the IETF end and in prac=
tice at the IANA end. I didn&#39;t see Jari advancing that as a goal in the=
 article.<div><br></div><div>But that theory does not quite align with the =
current registry organization with the crypto alg registries aligned to pro=
tocols rather than being generic identifiers. And there is still an element=
 that believes that the purpose of the IETF is to protect the Internet from=
 the mistakes of bad wizards.</div>
<div><br></div><div><br></div><div>What I am doing is thinking through what=
 it would take to make the theory a reality. Right now we have a bizarre si=
tuation where W3C takes the IETF crypto alg names, splices a URL prefix on =
the front and cuts a new URL.</div>
<div><br></div><div>The DANE folk just tried to define alg identifiers for =
their spec and found that there were four different labels defined for SHA-=
2, 256 bit in the IETF already.</div><div><br></div></div><div class=3D"gma=
il_extra">
<br><br><div class=3D"gmail_quote">On Sun, Jan 5, 2014 at 2:01 PM, Brian E =
Carpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.c=
om" target=3D"_blank">brian.e.carpenter@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">
Phill, that is built into clause 1 of our MoU with ICANN (RFC 2860).<br>
I assume that when the IETF Chair writes about IANA, he&#39;s writing<br>
about the part of IANA that we control under that MoU.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 Brian<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
On 06/01/2014 06:36, Phillip Hallam-Baker wrote:<br>
&gt; One of the points that I should have made in response to Jari is that =
a<br>
&gt; major limitation in his thinking is that he sets out the function of I=
ANA<br>
&gt; as an IETF support service rather than an Internet support service.<br=
>
&gt;<br>
&gt; The distinction is important as there is no reason that IANA should on=
ly be<br>
&gt; used by the IETF. The IETF is not the only Internet standards making<b=
r>
&gt; organization and I hope to see many, many more. There is a natural lim=
it to<br>
&gt; the size of organizations and the IETF is at that point. So are OASIS =
and<br>
&gt; W3C. We cannot attempt to scale the development of cool Internet uses =
by<br>
&gt; increasing the size of the IETF and it is counterproductive to try.<br=
>
&gt;<br>
&gt; If we look at the wider context, there are now communities focused on<=
br>
&gt; single applications that are roughly the size of IETF areas. The Linux=
<br>
&gt; plumbers is the size of the IETF at a similar stage in IETF growth. Th=
ey<br>
&gt; will soon grow to about the same size.<br>
&gt;<br>
&gt;<br>
&gt; We can&#39;t scale organizations but we CAN scale the IANA. The functi=
on of the<br>
&gt; protocol registries is simply to avoid ambiguous name assignments. Why=
<br>
&gt; limit scope to just protocol?<br>
&gt;<br>
&gt;<br>
&gt; On Sun, Jan 5, 2014 at 3:06 AM, Patrik F=E4ltstr=F6m &lt;<a href=3D"ma=
ilto:paf@frobbit.se">paf@frobbit.se</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; On 5 jan 2014, at 07:16, manning bill &lt;<a href=3D"mailto:bmanni=
ng@isi.edu">bmanning@isi.edu</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;&gt; Jari, you can=92t be serious. =A0unlimited means -without- lim=
it, not just<br>
&gt;&gt; the limits of your imagination.<br>
&gt;&gt;<br>
&gt;&gt; Bill, it was not Jari, it was Phillip Hallam-Baker that said &quot=
;unlimited&quot;,<br>
&gt;&gt; which I objected to.<br>
&gt;&gt;<br>
&gt;<br>
&gt; And I excluded the very protocols you used as examples in your counter=
<br>
&gt; argument. So complaining about Bill mistaking attribution is a bit ric=
h.<br>
&gt;<br>
&gt; And I said &#39;effectively&#39; unlimited which means without effecti=
ve limit,<br>
&gt; i.e. sufficiently large that there is no conceivable circumstance in w=
hich<br>
&gt; we would need more. So suggesting that the identifiers need to be<br>
&gt; infinitely long is yet another straw man.<br>
&gt;<br>
&gt; RFC822 header tags are not in fact unlimited, I can&#39;t remember the=
 limit<br>
&gt; offhand but for practical purposes it is 20 bytes. But that is still e=
nough<br>
&gt; space to encode a 100bit random identifier in base32 which is certainl=
y<br>
&gt; &#39;effectively unlimited&#39;.<br>
&gt;<br>
&gt;<br>
&gt; The test is whether the risk of code point exhaustion is justification=
 for<br>
&gt; limiting registrations. If someone can make the argument that &#39;we =
might run<br>
&gt; out&#39; then obviously the number of code points is not effectively u=
nlimited.<br>
&gt;<br>
&gt; What I am trying to get away from here is the expectation that every<b=
r>
&gt; protocol is going to have a separate registry for every item that migh=
t<br>
&gt; need to be identified.<br>
&gt;<br>
&gt; Shaving a few bytes should not be an excuse to create a new ongoing<br=
>
&gt; maintenance requirement for IANA and creating an extensibility nightma=
re<br>
&gt; which is what short fixed length codes do.<br>
&gt;<br>
&gt;<br>
&gt; Now what we could do that would achieve most goals for most people wou=
ld be<br>
&gt; to have a single registry of text labels. Each entry would have four p=
ieces<br>
&gt; of information:<br>
&gt;<br>
&gt; 1) The label itself<br>
&gt; 2) A unique numeric code<br>
&gt; 3) The purpose for which the label is defined<br>
&gt; 4) References<br>
&gt;<br>
&gt; So &quot;AES&quot; would have the entry<br>
&gt;<br>
&gt; &quot;AES&quot; =A04242 =A0Algorithm/Encryption =A0FIPS-yada-yada<br>
&gt;<br>
&gt; There might then be additional information in the Algorithm/Encryption=
<br>
&gt; registry which would continue to provide additional information (e.g. =
the<br>
&gt; OID assignment, modes etc).<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Signup would be by simply entering filling out a web form, similar to =
the<br>
&gt; allocation of OID arcs.<br>
&gt;<br>
&gt;<br>
&gt; The advantage of this approach is that if someone wants to simply rese=
rve a<br>
&gt; label to prevent a conflicting use, this is easily done. It is not eve=
n<br>
&gt; necessary to specify the use.<br>
&gt;<br>
&gt; The numeric codes can be used for the handful of protocols where byte<=
br>
&gt; shaving is a real concern. A new protocol using the technique would ha=
ve to<br>
&gt; make provision for allowing 64 bit codes but it is unlikely the<br>
&gt; registrations would exceed a 4 byte space any time soon.<br>
&gt;<br>
&gt; Another use for the codes would be to define an OID assignment and a U=
RI<br>
&gt; form of the same label. Since some codes already have OID and URI form=
s,<br>
&gt; these need to be tracked but that would be best done separately.<br>
&gt;<br>
&gt; I would do this with two registries, one for OIDs, the other for URIs =
which<br>
&gt; would list the code points that are synonyms for codes listed in the t=
ext<br>
&gt; label table and whether they are canonical.<br>
&gt;<br>
&gt;<br>
&gt; The current situation suffers from the hierarchical fallacy which is t=
he<br>
&gt; mistaken belief that it is useful to separate identifiers by category.=
 The<br>
&gt; prime example of this failed notion being the .com, .net and .org<br>
&gt; registries in DNS which do nothing but confuse.<br>
&gt;<br>
&gt; Separating the registration of encryption algorithms from other crypto=
<br>
&gt; algorithms does not help because it should be obvious that if FOO is a=
<br>
&gt; symmetric encryption algorithm identifier, it cant be a digest algorit=
hm<br>
&gt; either. It is also the case but somewhat less obvious that the FOO lab=
el<br>
&gt; can&#39;t then be a RFC821 command or a RFC822 header either. At least=
 not<br>
&gt; unless the use of FOO in the other context is completely specified and=
<br>
&gt; constrained by the symmetric encryption spec.<br>
&gt;<br>
&gt;<br>
&gt; If we rationalize the operation of IANA we can reduce the amount of wo=
rk<br>
&gt; required in both the IETF space and the IANA. More importantly we can<=
br>
&gt; encourage all the other standards organizations to rely on IANA to reg=
ister<br>
&gt; code points.<br>
&gt;<br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--001a11c269146fec5804ef3e6afe--

From abdussalambaryun@gmail.com  Sun Jan  5 12:13:18 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0220D1AF76F for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 12:13:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiYziX_PpjMR for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 12:13:15 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id BBEFA1AF770 for <ietf@ietf.org>; Sun,  5 Jan 2014 12:13:15 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id z10so17243672pdj.16 for <ietf@ietf.org>; Sun, 05 Jan 2014 12:13:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pyv+fVflP8Y8sdOCZRBezdyqD6Vqqs7hlIrmZTyelhc=; b=vJ5Kj6Dosl0ry8g60JVD4KqoL67QQCWnDmR9b4Zq8GpOPq/i5BS0dmp1YaVLhb9zye zPnOg0KTeMqzThpeFrtQXce5Rlh6UxXgeDhYDq54ioNyWugAX6V1t7G8Uen3vkGFpgfj sVbg3XmO43IGKhIL/yHAiGr2Qu1tBBF07xfQVXGp7SmUrlIb9BpCd4hhplvrXNOUIU2F 7chSELrr+OprSstg25mFi7JH7jAsghBbTROslyY+VLskivkNIydyReJ0PvIz4DfckZDw IIDtkDLocQHqkiHGEYwpTWOx/JesR01XGGg4D0616v49WYJWAhl9RLZP1IbJiopGrpDN WrmA==
MIME-Version: 1.0
X-Received: by 10.68.134.98 with SMTP id pj2mr118279913pbb.110.1388952787746;  Sun, 05 Jan 2014 12:13:07 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Sun, 5 Jan 2014 12:13:07 -0800 (PST)
In-Reply-To: <52C9A3AB.7090206@dcrocker.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <52C88458.80102@dcrocker.net> <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se> <52C9A3AB.7090206@dcrocker.net>
Date: Sun, 5 Jan 2014 21:13:07 +0100
Message-ID: <CADnDZ8-WVVAaygT40hkP-YcAavsPemeVKviJrc1Pq0QLL_YBeA@mail.gmail.com>
Subject: Re: Focus (was Re: Design Considerations (was - Re: IANA blog article))
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b10cf4d86042d04ef3ec57e
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 20:13:18 -0000

--047d7b10cf4d86042d04ef3ec57e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

I already asked/suggested the general area director to have WGs in the area
because I want focus as well, but I don't mind your suggestion to have
facilitators that help focus in discussion or to guide productivity. I
already commented in the 2013 review thread that the area need
more organise.

AB

On Sunday, January 5, 2014, Dave Crocker wrote:

> On 1/4/2014 2:14 PM, Patrik F=E4ltstr=F6m wrote:
>
>> 1. Jari posted a blog post about IANA, and I ask myself why IETF (yes,
>> "we") can not stay focused
>>
>
>
> Email group discussions are easily distracted because:
>
>    1) the group often does not share a strong sense of needing to stay
> focused, and
>
>    2) no one carries the task of trying to help the group stay focused.
>
> Neither of these is special to this mailing list, and we have all seen
> face-to-face meetings suffer the same problem.  However in normal group
> meetings, there is usually pressure to be productive.  We we typically ha=
ve
> someone driving discussion and getting group agreement to have the focus
> created by that driving.
>
> If we want IETF discussions to do a better job of staying focused, we nee=
d
> for a topic to have a facilitator who presses for that focus and we need
> them to do the usual summarizing and polling that we use elsewhere in the
> IETF.
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

<br>I already asked/suggested=A0the general area director to have WGs in th=
e area because I want focus as well, but I don&#39;t mind your suggestion t=
o have facilitators that help focus in discussion or to guide=A0productivit=
y. I already commented in the 2013 review thread that the area need more=A0=
organise.<div>
<br></div><div>AB</div><div><br>On Sunday, January 5, 2014, Dave Crocker  w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">On 1/4/2014 2:14 PM, Patrik F=E4lts=
tr=F6m wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
1. Jari posted a blog post about IANA, and I ask myself why IETF (yes, &quo=
t;we&quot;) can not stay focused<br>
</blockquote>
<br>
<br>
Email group discussions are easily distracted because:<br>
<br>
=A0 =A01) the group often does not share a strong sense of needing to stay =
focused, and<br>
<br>
=A0 =A02) no one carries the task of trying to help the group stay focused.=
<br>
<br>
Neither of these is special to this mailing list, and we have all seen face=
-to-face meetings suffer the same problem. =A0However in normal group meeti=
ngs, there is usually pressure to be productive. =A0We we typically have so=
meone driving discussion and getting group agreement to have the focus crea=
ted by that driving.<br>

<br>
If we want IETF discussions to do a better job of staying focused, we need =
for a topic to have a facilitator who presses for that focus and we need th=
em to do the usual summarizing and polling that we use elsewhere in the IET=
F.<br>

<br>
d/<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</blockquote></div>

--047d7b10cf4d86042d04ef3ec57e--

From sm@elandsys.com  Sun Jan  5 17:28:09 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC0161ADED5 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 17:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LArm76YLuOpw for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 17:28: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 6BF0E1ADEBE for <ietf@ietf.org>; Sun,  5 Jan 2014 17:28:08 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.235.219]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s061Rhxh000963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Jan 2014 17:27:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388971676; bh=4E3U8qpXYRRIOVP6jUgavOYIYwVIkQOe3xovXvVqkUY=; h=Date:To:From:Subject:Cc; b=V/t8G5JnVGoUJo1+2MChI9g+1O86T4MDRnwLlL3xtRnhpncVE1jz/VMz4qIBjem5S 1UFjlB77FhMkmNy6yVJN/w8norOKcxHH259LiCG6griMHDByk05b+cEdc4SHuCPlov gqUl+SZos4mJ7rkzJDYFddMFSrDmFPZOf13Ygbeg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1388971676; i=@elandsys.com; bh=4E3U8qpXYRRIOVP6jUgavOYIYwVIkQOe3xovXvVqkUY=; h=Date:To:From:Subject:Cc; b=plf+IL892HXuusQbIyLxgePuvA1LHch6JLlC/XnEHumLfcW8sQU1ibgon6ZN+GWen sJa6UBYcjMT6Dtp3ln6dD8Fk4A7WfaobgAgfCkVDH/Pg/aXEELSC2oPlhE+ZAxXv0w mJf3/lfc9O614/1v8ZRRDa8ohcf5a9BCg4hivn8s=
Message-Id: <6.2.5.6.2.20140105172610.0d327a10@elandsys.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 05 Jan 2014 17:27:07 -0800
To: Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 01:28:10 -0000

Hi Dave,
At 10:43 05-01-2014, Dave Crocker wrote:
>I'm not sure how to have the text make this point more clearly in the draft.

Thanks for the explanation.  I am okay with no changes.

>You're the third person to note this.  I think that counts as consensus...

:-)

>I believe working groups often do things like adding a document, or 
>splitting a document into two or even combining documents, without 
>changing their charter.  I guess I've understood the essential 
>question for changing the charter to be when the substance of the 
>group's work is changed.
>
>To the extent that a scenario, of the type you describe, causes 
>debate within a working group, I would think that it's usually 
>healthy for the group, since it can produce better clarity about the 
>group's work.
>
>I'm not sure a document like the current draft should seem to be 
>more precise on this than it currently is.  In other words, yes, the 
>controversy/confusion you cite happens, but we probably should not 
>change the current draft to affect that.

I am okay with the above.

>hmmm. yeah.  Strange wording choice, especially since as you note 
>the phrase is a formal term of art.  No memory of what produced that 
>wording.  I think better wording would be:
>
>       However, posting an I-D is often a good way to put
>       new ideas into concrete form, for public
>       consideration and discussion."

The (above) wording is fine.

>The paragraph is meant to counter-act the reaction people sometimes 
>have, that posting an alternative draft is automatically a bad 
>thing, by noting that it can be a valid form of commenting on an 
>existing, other draft.

Ok.

Regards,
S. Moonesamy  


From hallam@gmail.com  Sun Jan  5 21:14:57 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E56D1ADF92 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 21:14:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjoLbUmqsKjL for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 21:14:55 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5AA1ADED5 for <ietf@ietf.org>; Sun,  5 Jan 2014 21:14:55 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id n7so9546424lam.35 for <ietf@ietf.org>; Sun, 05 Jan 2014 21:14:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=A7b+uyx6qSbgcnS7mJXpI3Xx1mXI0JmNAZFFo++S6ow=; b=ZENhP2tsFeBOx7U5St6O2vwNYisG0IcTgY/Q2guZMBFSVn1sRLbMU1KCq6sc6F3g8K c+dQ99xDKKXxdJH8QqS0piGjtnbcHgAtvbZ3bsO6K+Bx479irFku9A6CdvvK03gEnIFw 5qxGuM8iiw2vjJSIxPUfIY2Dl0g8hpZZo+oOTJxnbmV3UU3IvTp2U70+FXAFnMnk98+K fb3rQlIE0KrFwtDCI/J215JNlh5DgAGyVOdy2w4SXYjDkoO3b9Pvn5a3wjXff5qmrU54 6KmaTmFtKLvELkLBz62fXm1CA9MfV0nZ7QCAkMWaOCV1my9eWwkk5EfgdUKlFWz7Sr5E PiAg==
MIME-Version: 1.0
X-Received: by 10.112.138.98 with SMTP id qp2mr18095lbb.82.1388985286075; Sun, 05 Jan 2014 21:14:46 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sun, 5 Jan 2014 21:14:45 -0800 (PST)
In-Reply-To: <52C9A3AB.7090206@dcrocker.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <52C88458.80102@dcrocker.net> <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se> <52C9A3AB.7090206@dcrocker.net>
Date: Mon, 6 Jan 2014 00:14:45 -0500
Message-ID: <CAMm+Lwh4LGzg2Ctij3XmKAuQa-GJKaiez4idcXZyzky9f2MT0w@mail.gmail.com>
Subject: Re: Focus (was Re: Design Considerations (was - Re: IANA blog article))
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0116049e93288604ef46568d
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 05:14:57 -0000

--089e0116049e93288604ef46568d
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

What Jari posted:

" What is IANA, how does it work, how is it related to the IETF, and how
has it evolved over time? How will it evolve in the future, and how can you
participate in the discussion?"

Excuse me but when someone invites me to engage in an open ended
conversation about the future of an Internet institution I intend to do
precisely that.



On Sun, Jan 5, 2014 at 1:25 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 1/4/2014 2:14 PM, Patrik F=E4ltstr=F6m wrote:
>
>> 1. Jari posted a blog post about IANA, and I ask myself why IETF (yes,
>> "we") can not stay focused
>>
>
>
> Email group discussions are easily distracted because:
>
>    1) the group often does not share a strong sense of needing to stay
> focused, and
>
>    2) no one carries the task of trying to help the group stay focused.
>
> Neither of these is special to this mailing list, and we have all seen
> face-to-face meetings suffer the same problem.  However in normal group
> meetings, there is usually pressure to be productive.  We we typically ha=
ve
> someone driving discussion and getting group agreement to have the focus
> created by that driving.
>
> If we want IETF discussions to do a better job of staying focused, we nee=
d
> for a topic to have a facilitator who presses for that focus and we need
> them to do the usual summarizing and polling that we use elsewhere in the
> IETF.
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>



--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr">What Jari posted:<div><br></div><div>&quot;<span style=3D"=
font-family:arial,sans-serif;font-size:16px">=A0What is IANA, how does it w=
ork, how is it related to the IETF, and how has it evolved over time? How w=
ill it evolve in the future, and how can you participate in the discussion?=
&quot;</span></div>
<div><font face=3D"arial, sans-serif"><span style=3D"font-size:16px"><br></=
span></font></div><div><font face=3D"arial, sans-serif"><span style=3D"font=
-size:16px">Excuse me but when someone invites me to engage in an open ende=
d conversation about the future of an Internet institution I intend to do p=
recisely that.</span></font></div>
<div><font face=3D"arial, sans-serif"><span style=3D"font-size:16px"><br></=
span></font></div><div><font face=3D"arial, sans-serif"><span style=3D"font=
-size:16px"><br></span></font></div><div><font face=3D"arial, sans-serif"><=
span style=3D"font-size:16px"><br>
</span></font></div><div><div class=3D"gmail_extra"><div class=3D"gmail_quo=
te">On Sun, Jan 5, 2014 at 1:25 PM, Dave Crocker <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">On 1/4/2014 2:14 PM, Patrik F=E4ltstr=F6m wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
1. Jari posted a blog post about IANA, and I ask myself why IETF (yes, &quo=
t;we&quot;) can not stay focused<br>
</blockquote>
<br>
<br>
Email group discussions are easily distracted because:<br>
<br>
=A0 =A01) the group often does not share a strong sense of needing to stay =
focused, and<br>
<br>
=A0 =A02) no one carries the task of trying to help the group stay focused.=
<br>
<br>
Neither of these is special to this mailing list, and we have all seen face=
-to-face meetings suffer the same problem. =A0However in normal group meeti=
ngs, there is usually pressure to be productive. =A0We we typically have so=
meone driving discussion and getting group agreement to have the focus crea=
ted by that driving.<br>

<br>
If we want IETF discussions to do a better job of staying focused, we need =
for a topic to have a facilitator who presses for that focus and we need th=
em to do the usual summarizing and polling that we use elsewhere in the IET=
F.<span class=3D""><font color=3D"#888888"><br>

<br>
d/<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div></div></div>

--089e0116049e93288604ef46568d--

From daedulus@btconnect.com  Mon Jan  6 02:45:08 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A75571ADF93 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 02:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TH2mFZQeGG1n for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 02:45:06 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe006.messaging.microsoft.com [213.199.154.209]) by ietfa.amsl.com (Postfix) with ESMTP id C94651ADF8F for <ietf@ietf.org>; Mon,  6 Jan 2014 02:45:05 -0800 (PST)
Received: from mail42-am1-R.bigfish.com (10.3.201.243) by AM1EHSOBE005.bigfish.com (10.3.204.25) with Microsoft SMTP Server id 14.1.225.22; Mon, 6 Jan 2014 10:44:56 +0000
Received: from mail42-am1 (localhost [127.0.0.1])	by mail42-am1-R.bigfish.com (Postfix) with ESMTP id C955920007E; Mon,  6 Jan 2014 10:44:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT003.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zzbb2dI98dI9371I542I1432I1447Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah1fc6hzz8275ch1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h2327h2336h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(24454002)(51914003)(13464003)(479174003)(377454003)(51704005)(199002)(189002)(31966008)(47446002)(74502001)(74662001)(19580395003)(83322001)(19580405001)(74366001)(66066001)(65816001)(80022001)(56776001)(63696002)(47776003)(54316002)(77096001)(77156001)(33646001)(62236002)(50466002)(59766001)(77982001)(53806001)(74706001)(76796001)(76786001)(42186004)(76482001)(44716002)(79102001)(46102001)(74876001)(51856001)(4396001)(49866001)(47736001)(50986001)(47976001)(50226001)(44736004)(89996001)(81542001)(84392001)(81342001)(90146001)(56816005)(87266001)(23756003)(87976001)(69226001)(80976001)(85852003)(83072002)(88136002)(62966002)(85306002)(14496001)(61296002)(87286001)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB244; H:DBXPRD0611HT003.eurprd06.prod.outlook.com; CLIP:157.56.254.85; FPR:; RD:InfoNoRecords; A:0; MX:1; LANG:en; 
Received: from mail42-am1 (localhost.localdomain [127.0.0.1]) by mail42-am1 (MessageSwitch) id 1389005093987088_25800; Mon,  6 Jan 2014 10:44:53 +0000 (UTC)
Received: from AM1EHSMHS011.bigfish.com (unknown [10.3.201.247])	by mail42-am1.bigfish.com (Postfix) with ESMTP id BCA6B460063;	Mon,  6 Jan 2014 10:44:43 +0000 (UTC)
Received: from AM2PRD0710HT003.eurprd07.prod.outlook.com (157.56.249.213) by AM1EHSMHS011.bigfish.com (10.3.207.111) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 6 Jan 2014 10:44:43 +0000
Received: from AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154) by AM2PRD0710HT003.eurprd07.prod.outlook.com (10.255.165.38) with Microsoft SMTP Server (TLS) id 14.16.395.1; Mon, 6 Jan 2014 10:44:43 +0000
Received: from DBXPRD0611HT003.eurprd06.prod.outlook.com (157.56.254.85) by AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154) with Microsoft SMTP Server (TLS) id 15.0.842.7; Mon, 6 Jan 2014 10:44:42 +0000
Message-ID: <018c01cf0acb$c5974de0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>, <dcrocker@bbiw.net>, <ietf@ietf.org>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.com>, <52C88C48.8070106@dcrocker.net> <655C07320163294895BBADA28372AF5D1562D4@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Date: Mon, 6 Jan 2014 10:29:36 +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-ClientProxiedBy: DBXPR07CA005.eurprd07.prod.outlook.com (10.255.191.163) To AM3PR07MB244.eurprd07.prod.outlook.com (10.242.18.154)
X-Forefront-PRVS: 0083A7F08A
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 10:45:08 -0000

<inline <tp>>

----- Original Message -----
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: <dcrocker@bbiw.net>; <ietf@ietf.org>
Sent: Sunday, January 05, 2014 6:30 PM

Hi Dave,

Yes, a statement like "Does the intended status of the document seem
reasonable to the working group?" in Section 2.2 would make sense a lot
of sense to me. This is what I was looking for.

I agree that the WG energy and willingness to review is somehow part of
"working on the draft", but I still wonder whether it can be made more
explicitly. I am not sure whether it belongs to Section 3, which is
about authors/editors selection. WG energy also seems somehow orthogonal
to most other sections. Here is one idea for specific text (there are
other options as well): If it is hard to find reviewers for a given
topic, the document will inherently move forward rather slowely... So,
what about the following question in Section 2.2:

<tp>
Michael

I track TCPM and so know of your approach, but other WGs are at the
other end of the spectrum, seeming almost to say
 - noone has said anything so we will adopt this I-D
 - noone has said anything so we will move to WGLC
 - noone has said anything so we will move this to the IESG
even when dealing with core Internet Procotols.

I have not analysed the results but suspect that the output of such WG
lead to more IETF LC comments or more errata or more -bis or ...

But there is an enormous spectrum.  Another example is a limit on the
cache size of WG I-Ds - no further I-Ds can be adopted until one of the
current ones has been handed on to the IESG; this, for me, is the worst
approach so far - perhaps sound business management practice but not so
sound engineering, at least from my perspective.

So, the concern as alway with these process I-Ds is that they tend to
become overprescriptive and reduce the quality or rate or both of the
work that the IETF does.

A good process I-D is one that seeks to eliminate bad practice, one that
increases the mean by focussing on the minima, one that seeks to remove
the defective WG Chair behaviour - or if that proves impractical, remove
the WG Chair :-(  Ones that seek to promote best practice usually
constrain the good practioners too much, prevent us from finding better
ways of working.

Tom Petch


  * After adoption, is it likely that the document will move forward in
a reasonable timeframe, e.g., as defined by a charter milestone?

In general, I don't have a particularly strong opinion on my second
point, and I don't strongly insist on a change of the draft.

Thanks

Michael

________________________________________
Von: Dave Crocker [dhc@dcrocker.net]
Gesendet: Samstag, 4. Januar 2014 23:33
An: Scharf, Michael (Michael); ietf@ietf.org
Betreff: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an
IETF Working Group Draft) to Informational RFC

Michael,

Thanks for the comments.  Responding strictly on my own behalf:


On 1/3/2014 9:32 AM, Scharf, Michael (Michael) wrote:
> First, the document could perhaps mention that during the adoption of
> a draft there can be a discussion about the planned status (e.g., STD
> vs. EXP), even if the status can change later in the process. In
> TCPM, this is almost always the case, and therefore the chairs have
> to consider the planned status as one question when creating/adopting
> a WG draft.

This sounds like another bullet in the Section 2.2. Criteria for
Adoption list.  Possibly:

    *  Does the intended status of the document seem reasonable to the
       working group?


> Second, I am not sure if the following statement in Section 2.2 could
> be detailed a bit:
>
> *  Is there strong working group support for working on the draft?
>
> Actually, in TCPM, the "working group support for working on the
> draft" is often not the most important criteria for adoption. The key
> one is the more specific question whether there indeed "working group
> energy for contributing and reviewing". For instance, sometimes, we
> have the following situation: The community really likes a new,
> interesting idea, and the WG therefore really wants that "somebody"
> works out all the nasty protocol details that a full spec would
> require. This is typically left to the authors of the individual
> document proposing this idea. Yet, since TCPM deals with a core
> Internet protocol, having a WG document also implies that the WG
> should indeed verify this spec, e.g., in all the corner cases that
> can occur in a complex protocol. And, surprise, surprise, finding
> volunteers for that is often more difficult than finding people that
> really like an idea and want the WG to work on it... As a result, the
> chairs have to think about the completion of any new WG document
> quite a bit in advance...

Hmmm.  Certainly a reasonable scenario, IMO, but I would have thought
the current draft covers what you describe.

The fact that you don't see that leaves me unclear how to fix this, so
that there's no doubt it is considered a legitimate scenario.

      1. The document discusses the difference between having the
document be author-driven vs. working-driven, in Section 3.

      2. I think of the wg reviewing effort you describe as "working on
the draft" and hence qualifying under the bullet you quote.

Best I can think of is to ask you for suggested text changes/additions.


d/

--
Dave Crocker
Brandenburg InternetWorking
bbiw.net



From jari.arkko@piuha.net  Mon Jan  6 04:02:50 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E3CF1AD6C1 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 04:02:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsNcNRXX3-48 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 04:02:48 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 69F751AD627 for <ietf@ietf.org>; Mon,  6 Jan 2014 04:02:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id A02682CEB6; Mon,  6 Jan 2014 14:02: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 HiIBKKK6rA_d; Mon,  6 Jan 2014 14:02:37 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D986D2CC5D; Mon,  6 Jan 2014 14:02:35 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Focus (was Re: Design Considerations (was - Re: IANA blog article))
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+Lwh4LGzg2Ctij3XmKAuQa-GJKaiez4idcXZyzky9f2MT0w@mail.gmail.com>
Date: Mon, 6 Jan 2014 04:02:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F8E56EE-CF72-4F43-BC35-53A342E05EEE@piuha.net>
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net> <540764A3-BEC1-4A63-9D2E-2750C70AEB05@frobbit.se> <52C88458.80102@dcrocker.net> <26970E15-2B22-47FA-AABD-82921BF37C16@frobbit.se> <52C9A3AB.7090206@dcrocker.net> <CAMm+Lwh4LGzg2Ctij3XmKAuQa-GJKaiez4idcXZyzky9f2MT0w@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 12:02:50 -0000

I don't mind discussion branching off to new directions, sometimes we =
discover useful new things because of that. Phillip had an angle about =
this topic that I think is worthwhile to think about.

Of course, it doesn't take away the need to discuss other angles. How we =
manage registries that we still need continues to be an important topic. =
We've gotten some feedback on that on this and the IAB list, and =
hopefully we'll get some more. One of my goals with the article was to =
get that discussion started, and draw attention to Olaf's document. =
Please keep those comments coming.

(And maybe there's a lesson there for other things that come up during =
the discussion. Writing a draft and making a proposal, building support =
for it are good things.)

Jari


From jari.arkko@piuha.net  Mon Jan  6 04:44:56 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF8571ADFA3; Mon,  6 Jan 2014 04:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OEbMxqrCfaal; Mon,  6 Jan 2014 04:44:55 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5951AE19D; Mon,  6 Jan 2014 04:42:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF13D2CEB6; Mon,  6 Jan 2014 14:42:11 +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 hVs_-C9p1yMc; Mon,  6 Jan 2014 14:42:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D2C9B2CC5D; Mon,  6 Jan 2014 14:42:09 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Gen-ART review of draft-ietf-idr-extcomm-iana-02
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
Date: Mon, 6 Jan 2014 04:42:08 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <F03C7242-19B2-4705-81EF-0B42E4BCE990@piuha.net>
References: <0bb301cf0a11$b1ea5540$15beffc0$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-idr-extcomm-iana.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 12:44:57 -0000

Roni: thank you for your review of this document. The Gen-ART reviews =
are important for me to decide whether I need to look at the document in =
more detail, and often provide useful comments that the authors use to =
improve their documents.

I have placed a no-objection position for this document for the upcoming =
IESG telechat, based on your review and my own quick review. Thank you =
for writing a clear document for a set of complex registries.

> =95 I assume that the text in the IANA registry will reflect that the =
old registries are close and point at the ones that replace them.  I =
noticed that the document was prepared in cooperation with IANA so I =
assume that there will be no problems.

FWIW, even if there had not been IANA involvement earlier, IANA also =
reviews all documents as they come through approval to the IESG, so if =
there was a problem then we'd hear about it. In this case Pearl said:

> IANA OK.  Comments in tracker.
> IANA Actions - YES


Jari


From peter@bsdly.net  Fri Jan  3 10:12:25 2014
Return-Path: <peter@bsdly.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5071ADFC4; Fri,  3 Jan 2014 10:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IduCj_ZGnqid; Fri,  3 Jan 2014 10:12:23 -0800 (PST)
Received: from skapet.bsdly.net (cl-426.sto-01.se.sixxs.net [IPv6:2001:16d8:ff00:1a9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5BD1AC3FA; Fri,  3 Jan 2014 10:12:23 -0800 (PST)
Received: from [192.168.103.44] (helo=deeperthought.bsdly.net) by skapet.bsdly.net with esmtp (Exim 4.80.1) (envelope-from <peter@bsdly.net>) id 1Vz9EB-0002zk-Sd; Fri, 03 Jan 2014 19:12:14 +0100
To: ietf@ietf.org
Subject: Re: RETRACTION: Last Call: Progressing RFCs 5343, 5590, 5991, and 6353 to Internet Standard
References: <20140103180641.30180.68094.idtracker@ietfa.amsl.com>
From: peter@bsdly.net (Peter N. M. Hansteen)
Date: Fri, 03 Jan 2014 19:12:05 +0100
In-Reply-To: <20140103180641.30180.68094.idtracker@ietfa.amsl.com> (IETF Secretariat's message of "Fri, 03 Jan 2014 10:06:41 -0800")
Message-ID: <8761q1aqa2.fsf@deeperthought.bsdly.net>
User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.22 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Mon, 06 Jan 2014 08:11:48 -0800
Cc: isms@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jan 2014 18:12:26 -0000

This begs the question: 

Do the withdrawal requests contain any publishable specifics as to why
these status changes should not go forward?

Yours,
Peter N. M. Hansteen

IETF Secretariat <ietf-secretariat@ietf.org> writes:

> The following Last Call has been withdrawn by request of the area director:
>
> The IESG has received a request from multiple participants to make
> the following status changes:
>
> - RFC5343 from Draft Standard to Internet Standard
>     (Simple Network Management Protocol (SNMP) Context EngineID
> Discovery)
>
> - RFC5991 from Proposed Standard to Internet Standard
>     (Teredo Security Updates)
>
> - RFC5590 from Draft Standard to Internet Standard
>     (Transport Subsystem for the Simple Network Management Protocol
> (SNMP))
>
> - RFC6353 from Draft Standard to Internet Standard
>     (Transport Layer Security (TLS) Transport Model for the Simple
> Network Management Protocol (SNMP))
>

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

From sm@elandsys.com  Sun Jan  5 13:43:47 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738CE1AC3FA for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 13:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.428
X-Spam-Level: 
X-Spam-Status: No, score=-1.428 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_NXDOMAIN=0.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gx652xfmckNQ for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 13:43:46 -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 7A54E1ACCE8 for <ietf@ietf.org>; Sun,  5 Jan 2014 13:43:46 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.235.219]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s05LhI7M003467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Jan 2014 13:43:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1388958214; bh=tfuSCvv1mm6lZCtar8njnwJmCjrH7B2+zBMM70yxJ3s=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ckTot+tZGaQsVVsUYv9+WDjkKyjncQh7HnkcscOCRunv1doLSXebKuImDGMxPIDRu iT5D68s8sGdwXeeVHHibdm5DgMxCnqcFv5d32LbruZIv3rQx1AsrrW24qzTa3peM8W l91Lpg0kFnmLVsSu4kjZRC/ReMW9EpoXGeA6ZJKE=
Message-Id: <6.2.5.6.2.20140105113154.0cfe8450@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 05 Jan 2014 11:46:47 -0800
To: Adrian Farrel <adrian@olddog.co.uk>, Dave Crocker <dcrocker@bbiw.net>
From: S Moonesamy <sm@+ietfelandsys.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
In-Reply-To: <52C9A7BA.5050109@dcrocker.net>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <6.2.5.6.2.20140105002400.0b5f3c20@resistor.net> <52C9A7BA.5050109@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Mailman-Approved-At: Mon, 06 Jan 2014 08:12:02 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 21:43:47 -0000

Hi Dave,
At 10:43 05-01-2014, Dave Crocker wrote:
>I'm not sure how to have the text make this point more clearly in the draft.

Thanks for the explanation.  I am okay with no changes.

>You're the third person to note this.  I think that counts as consensus...

:-)

>I believe working groups often do things like adding a document, or 
>splitting a document into two or even combining documents, without 
>changing their charter.  I guess I've understood the essential 
>question for changing the charter to be when the substance of the 
>group's work is changed.
>
>To the extent that a scenario, of the type you describe, causes 
>debate within a working group, I would think that it's usually 
>healthy for the group, since it can produce better clarity about the 
>group's work.
>
>I'm not sure a document like the current draft should seem to be 
>more precise on this than it currently is.  In other words, yes, the 
>controversy/confusion you cite happens, but we probably should not 
>change the current draft to affect that.

I am okay with the above.

>hmmm. yeah.  Strange wording choice, especially since as you note 
>the phrase is a formal term of art.  No memory of what produced that 
>wording.  I think better wording would be:
>
>       However, posting an I-D is often a good way to put
>       new ideas into concrete form, for public
>       consideration and discussion."

The (above) wording is fine.

>The paragraph is meant to counter-act the reaction people sometimes 
>have, that posting an alternative draft is automatically a bad 
>thing, by noting that it can be a valid form of commenting on an 
>existing, other draft.

Ok.

Regards,
S. Moonesamy 


From tglassey@earthlink.net  Sun Jan  5 12:59:47 2014
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF0C41AF8B7 for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 12:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.162
X-Spam-Level: 
X-Spam-Status: No, score=0.162 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89jX5-YbKbrA for <ietf@ietfa.amsl.com>; Sun,  5 Jan 2014 12:59:45 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id A1A911AF8B6 for <ietf@ietf.org>; Sun,  5 Jan 2014 12:59:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=E8APbW7OIBUoV7QI7/IxTh433Vm+OSAGdkh6pKN7f3j60V2Gs87roNRz3mKPCyjX; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.134.155] (helo=[192.168.0.4]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1VzunI-0001UM-RN for ietf@ietf.org; Sun, 05 Jan 2014 15:59:36 -0500
Message-ID: <52C9C7B6.9000705@earthlink.net>
Date: Sun, 05 Jan 2014 12:59:34 -0800
From: TGLASSEY <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: IETF Specification for FREE SPEECH BOX, a device designed for covert access of the Internet to post key information
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79a5f200a27173af0a7095cbe09df32056350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.134.155
X-Mailman-Approved-At: Mon, 06 Jan 2014 08:12:20 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jan 2014 20:59:47 -0000

Since the IETF is moving into use of its protocols and standards I want 
to propose an interesting potential here - its for the creation of a WG 
who's work product would be a system to provide covert web-based access 
to a thing called a Free Speech Platform.

The system will integrate other IETF protocols as an example of 
something that can be done in the interest of ensuring the freedom of 
speech.

todd

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

Personal Email - Disclaimers Apply


From hallam@gmail.com  Mon Jan  6 08:20:59 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D6DA1AE097 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 08:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F2kqwXI7AYuB for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 08:20:57 -0800 (PST)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2A31C1AE059 for <ietf@ietf.org>; Mon,  6 Jan 2014 08:20:56 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id c11so10101420lbj.1 for <ietf@ietf.org>; Mon, 06 Jan 2014 08:20:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=1CBKqABwUEv0PIDCCgtwW2xxXAZ2bbJmfFmscclLVeQ=; b=d3Yi6ZVWxSjKtgs/rE9RfB77BuTvl+CZn9f+1J5A/tdUAw9Q6tLui9mJzUsG0kivUA sWWZtfaj584Ssj8eYy9PWf7fsX5uJ1DPiVXdhW0uk632sOTHqIc7/VY6fselHgHbfCXm +R3+FC2xwZa09A5Wx1IZy4XYRht2CO1s71oq1eTi1pTOm10GOeZFx9biVku6X7txNGgW +rJyOUQFAl59IQl5Vq2BUx+3nPqhHgDOcJ3haF8VazzzfMN3diyek4IDQ3CyPF8xoxVc yJYdrBV90+PQ4aRLDaUpkrbsJUpxNZJLclgrlxPRIkcEE74NdzR9+BR5bHPz7K6hiHQS 4HlA==
MIME-Version: 1.0
X-Received: by 10.112.138.70 with SMTP id qo6mr1358477lbb.34.1389025248023; Mon, 06 Jan 2014 08:20:48 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Mon, 6 Jan 2014 08:20:47 -0800 (PST)
Date: Mon, 6 Jan 2014 11:20:47 -0500
Message-ID: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com>
Subject: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0112c02c7e17bd04ef4fa47e
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 16:20:59 -0000

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

Following up on Jari's post, I think it would be a prudent political move
to split the IANA functions so that assignment of IP addresses is separate
from the protocol registry functions. The motivation behind this is to
protect the IETF.

Like the DNS, the allocation of IP address space and BGP parameters is a
potential control point. It is thus an activity that is at the eye of the
storm as far as Internet governance goes. That can't be helped and isn't
our problem. Governments can and should argue over the governance of a
control point that could potentially cripple their economies if abused in a
trade war.

The allocation of protocol parameters is not a control point since there is
no enforcement mechanism. Nobody is going to take notice if IANA were to
ever refuse to register a content type or an algorithm under political
pressure.

So if Iceland develops its own word processor and wants to register the
content type, the US government cannot protect Microsoft from competition
by passing a law that tells IANA not to issue a content-type.
Alternatively, if the NSA was to instruct IANA to refuse to register code
points required by Brazil's new email security scheme the effort would be
an obvious waste of time.

Abusing control of allocations in the IP, DNS and BGP spaces would also be
difficult to maintain but the switching costs are much higher and the
outcome is not so obvious. That dispute is certain to continue.


The problem the current situation creates is that because half of the IANA
function intersects with IETF activities and half with ICANN type
activities, the combination brings IETF into the line of fire in disputes
where it can better serve all sides by being neutral.

There is already a defacto split since the IANA operates the protocol
registry under contract with IETF and the IP/BGP registries under contract
with the DoC. The IETF might propose protocol changes that would impact the
numbers registry but the same is equally true of ICANN. Similarly, the IETF
could de facto reserve chunks of IPv6 space (and in fact does still
controls 7/8th of the total space) just as it can de facto attempt to grab
TLDs if it chooses. But this is a consequence of the fact that it is much
easier to fork a chunk of namespaces than is generally admitted.

So splitting IANA in two would have little operational impact but ensures
that there is a clear boundary between the governance of Internet control
points which is clearly in ICANN space and the governance of Internet
standards which is clearly separate from it.

The only practical impact would be changing the name of the protocol
registry. It would still be maintained by the same people, etc. Since the
protocol registries are not only numbers, the name Internet Assigned
Registry Authority (IARA) would be more appropriate in any case.


Logically, the thing to do would be for ICANN to rename the IP/BGP side of
IANA but that would not have the same protective effect politically.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><div>Following up on Jari&#39;s post, I think it would be =
a prudent political move to split the IANA functions so that assignment of =
IP addresses is separate from the protocol registry functions. The motivati=
on behind this is to protect the IETF.</div>
<div><br></div><div>Like the DNS, the allocation of IP address space and BG=
P parameters is a potential control point. It is thus an activity that is a=
t the eye of the storm as far as Internet governance goes. That can&#39;t b=
e helped and isn&#39;t our problem. Governments can and should argue over t=
he governance of a control point that could potentially cripple their econo=
mies if abused in a trade war.=A0</div>
<div><br></div><div>The allocation of protocol parameters is not a control =
point since there is no enforcement mechanism. Nobody is going to take noti=
ce if IANA were to ever refuse to register a content type or an algorithm u=
nder political pressure.</div>
<div><br></div><div>So if Iceland develops its own word processor and wants=
 to register the content type, the US government cannot protect Microsoft f=
rom competition by passing a law that tells IANA not to issue a content-typ=
e. Alternatively, if the NSA was to instruct IANA to refuse to register cod=
e points required by Brazil&#39;s new email security scheme the effort woul=
d be an obvious waste of time.</div>
<div><br></div><div>Abusing control of allocations in the IP, DNS and BGP s=
paces would also be difficult to maintain but the switching costs are much =
higher and the outcome is not so obvious. That dispute is certain to contin=
ue.</div>
<div><br></div><div><br></div><div>The problem the current situation create=
s is that because half of the IANA function intersects with IETF activities=
 and half with ICANN type activities, the combination brings IETF into the =
line of fire in disputes where it can better serve all sides by being neutr=
al.</div>
<div><br></div><div>There is already a defacto split since the IANA operate=
s the protocol registry under contract with IETF and the IP/BGP registries =
under contract with the DoC. The IETF might propose protocol changes that w=
ould impact the numbers registry but the same is equally true of ICANN. Sim=
ilarly, the IETF could de facto reserve chunks of IPv6 space (and in fact d=
oes still controls 7/8th of the total space) just as it can de facto attemp=
t to grab TLDs if it chooses. But this is a consequence of the fact that it=
 is much easier to fork a chunk of namespaces than is generally admitted.</=
div>
<div><br></div><div>So splitting IANA in two would have little operational =
impact but ensures that there is a clear boundary between the governance of=
 Internet control points which is clearly in ICANN space and the governance=
 of Internet standards which is clearly separate from it.</div>
<br clear=3D"all"><div>The only practical impact would be changing the name=
 of the protocol registry. It would still be maintained by the same people,=
 etc. Since the protocol registries are not only numbers, the name Internet=
 Assigned Registry Authority (IARA) would be more appropriate in any case.<=
/div>
<div><br></div><div><br></div><div>Logically, the thing to do would be for =
ICANN to rename the IP/BGP side of IANA but that would not have the same pr=
otective effect politically.</div><div><br></div><div><br></div>-- <br>
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--089e0112c02c7e17bd04ef4fa47e--

From michael.scharf@alcatel-lucent.com  Mon Jan  6 08:21:20 2014
Return-Path: <michael.scharf@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2EF21AE0BE for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 08:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07WDDM1gIJ93 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 08:21:12 -0800 (PST)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id CB96F1AE0B5 for <ietf@ietf.org>; Mon,  6 Jan 2014 08:21:12 -0800 (PST)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s06GKvp3024471 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 6 Jan 2014 10:20:58 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s06GKuPm010518 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 6 Jan 2014 17:20:56 +0100
Received: from FR712WXCHMBA15.zeu.alcatel-lucent.com ([169.254.7.70]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 6 Jan 2014 17:20:56 +0100
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>
To: "t.p." <daedulus@btconnect.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Topic: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
Thread-Index: AQHPCJaajVeEAzcLjk6SIrRU7XqAIJpzKCC6gAHv/ACAAU/IIIABH6cRgABNuOE=
Date: Mon, 6 Jan 2014 16:20:56 +0000
Message-ID: <655C07320163294895BBADA28372AF5D157178@FR712WXCHMBA15.zeu.alcatel-lucent.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <655C07320163294895BBADA28372AF5D155BF3@FR712WXCHMBA15.zeu.alcatel-lucent.com>, <52C88C48.8070106@dcrocker.net> <655C07320163294895BBADA28372AF5D1562D4@FR712WXCHMBA15.zeu.alcatel-lucent.com>, <018c01cf0acb$c5974de0$4001a8c0@gateway.2wire.net>
In-Reply-To: <018c01cf0acb$c5974de0$4001a8c0@gateway.2wire.net>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [155.132.188.47]
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 16:21:20 -0000

Hi Tom,=0A=
=0A=
Obviously WGs operate very differently. My observation when reading draft-c=
rocker-id-adoption-05 was that it has a lot of good thoughts - and that is =
why I find the document indeed useful. I just want to feed back some additi=
onal questions that I sometimes have to deal with, under the assumptions th=
at other WGs may run into similar questions from time to time, too. Obvious=
ly, that assumption might be wrong, and I stated this already in my initial=
 posting. I don't want to start a process discussion.=0A=
=0A=
But, for what it is worth, I don't understand why mentioning a question abo=
ut the intended status of a document as well as a question on the milestone=
 deadline would "constrain the good practioners". I have to deal with both =
questions each time we adopt a new draft as WG document, and I thought it c=
ould be useful to have them in the kind of checklist that draft-crocker-id-=
adoption provides. For instance, both questions are also valid ones for a W=
G that adopts all drafts nobody objects to.=0A=
=0A=
Thanks=0A=
=0A=
Michael=0A=
=0A=
________________________________________=0A=
Von: t.p. [daedulus@btconnect.com]=0A=
Gesendet: Montag, 6. Januar 2014 11:29=0A=
An: Scharf, Michael (Michael); dcrocker@bbiw.net; ietf@ietf.org=0A=
Betreff: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IET=
F Working Group Draft) to Informational RFC=0A=
=0A=
<inline <tp>>=0A=
=0A=
----- Original Message -----=0A=
From: "Scharf, Michael (Michael)" <michael.scharf@alcatel-lucent.com>=0A=
To: <dcrocker@bbiw.net>; <ietf@ietf.org>=0A=
Sent: Sunday, January 05, 2014 6:30 PM=0A=
=0A=
Hi Dave,=0A=
=0A=
Yes, a statement like "Does the intended status of the document seem=0A=
reasonable to the working group?" in Section 2.2 would make sense a lot=0A=
of sense to me. This is what I was looking for.=0A=
=0A=
I agree that the WG energy and willingness to review is somehow part of=0A=
"working on the draft", but I still wonder whether it can be made more=0A=
explicitly. I am not sure whether it belongs to Section 3, which is=0A=
about authors/editors selection. WG energy also seems somehow orthogonal=0A=
to most other sections. Here is one idea for specific text (there are=0A=
other options as well): If it is hard to find reviewers for a given=0A=
topic, the document will inherently move forward rather slowely... So,=0A=
what about the following question in Section 2.2:=0A=
=0A=
<tp>=0A=
Michael=0A=
=0A=
I track TCPM and so know of your approach, but other WGs are at the=0A=
other end of the spectrum, seeming almost to say=0A=
 - noone has said anything so we will adopt this I-D=0A=
 - noone has said anything so we will move to WGLC=0A=
 - noone has said anything so we will move this to the IESG=0A=
even when dealing with core Internet Procotols.=0A=
=0A=
I have not analysed the results but suspect that the output of such WG=0A=
lead to more IETF LC comments or more errata or more -bis or ...=0A=
=0A=
But there is an enormous spectrum.  Another example is a limit on the=0A=
cache size of WG I-Ds - no further I-Ds can be adopted until one of the=0A=
current ones has been handed on to the IESG; this, for me, is the worst=0A=
approach so far - perhaps sound business management practice but not so=0A=
sound engineering, at least from my perspective.=0A=
=0A=
So, the concern as alway with these process I-Ds is that they tend to=0A=
become overprescriptive and reduce the quality or rate or both of the=0A=
work that the IETF does.=0A=
=0A=
A good process I-D is one that seeks to eliminate bad practice, one that=0A=
increases the mean by focussing on the minima, one that seeks to remove=0A=
the defective WG Chair behaviour - or if that proves impractical, remove=0A=
the WG Chair :-(  Ones that seek to promote best practice usually=0A=
constrain the good practioners too much, prevent us from finding better=0A=
ways of working.=0A=
=0A=
Tom Petch=0A=
=0A=
=0A=
  * After adoption, is it likely that the document will move forward in=0A=
a reasonable timeframe, e.g., as defined by a charter milestone?=0A=
=0A=
In general, I don't have a particularly strong opinion on my second=0A=
point, and I don't strongly insist on a change of the draft.=0A=
=0A=
Thanks=0A=
=0A=
Michael=0A=
=0A=
________________________________________=0A=
Von: Dave Crocker [dhc@dcrocker.net]=0A=
Gesendet: Samstag, 4. Januar 2014 23:33=0A=
An: Scharf, Michael (Michael); ietf@ietf.org=0A=
Betreff: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an=0A=
IETF Working Group Draft) to Informational RFC=0A=
=0A=
Michael,=0A=
=0A=
Thanks for the comments.  Responding strictly on my own behalf:=0A=
=0A=
=0A=
On 1/3/2014 9:32 AM, Scharf, Michael (Michael) wrote:=0A=
> First, the document could perhaps mention that during the adoption of=0A=
> a draft there can be a discussion about the planned status (e.g., STD=0A=
> vs. EXP), even if the status can change later in the process. In=0A=
> TCPM, this is almost always the case, and therefore the chairs have=0A=
> to consider the planned status as one question when creating/adopting=0A=
> a WG draft.=0A=
=0A=
This sounds like another bullet in the Section 2.2. Criteria for=0A=
Adoption list.  Possibly:=0A=
=0A=
    *  Does the intended status of the document seem reasonable to the=0A=
       working group?=0A=
=0A=
=0A=
> Second, I am not sure if the following statement in Section 2.2 could=0A=
> be detailed a bit:=0A=
>=0A=
> *  Is there strong working group support for working on the draft?=0A=
>=0A=
> Actually, in TCPM, the "working group support for working on the=0A=
> draft" is often not the most important criteria for adoption. The key=0A=
> one is the more specific question whether there indeed "working group=0A=
> energy for contributing and reviewing". For instance, sometimes, we=0A=
> have the following situation: The community really likes a new,=0A=
> interesting idea, and the WG therefore really wants that "somebody"=0A=
> works out all the nasty protocol details that a full spec would=0A=
> require. This is typically left to the authors of the individual=0A=
> document proposing this idea. Yet, since TCPM deals with a core=0A=
> Internet protocol, having a WG document also implies that the WG=0A=
> should indeed verify this spec, e.g., in all the corner cases that=0A=
> can occur in a complex protocol. And, surprise, surprise, finding=0A=
> volunteers for that is often more difficult than finding people that=0A=
> really like an idea and want the WG to work on it... As a result, the=0A=
> chairs have to think about the completion of any new WG document=0A=
> quite a bit in advance...=0A=
=0A=
Hmmm.  Certainly a reasonable scenario, IMO, but I would have thought=0A=
the current draft covers what you describe.=0A=
=0A=
The fact that you don't see that leaves me unclear how to fix this, so=0A=
that there's no doubt it is considered a legitimate scenario.=0A=
=0A=
      1. The document discusses the difference between having the=0A=
document be author-driven vs. working-driven, in Section 3.=0A=
=0A=
      2. I think of the wg reviewing effort you describe as "working on=0A=
the draft" and hence qualifying under the bullet you quote.=0A=
=0A=
Best I can think of is to ask you for suggested text changes/additions.=0A=
=0A=
=0A=
d/=0A=
=0A=
--=0A=
Dave Crocker=0A=
Brandenburg InternetWorking=0A=
bbiw.net=0A=
=0A=
=0A=

From ahmedbakhat@pta.gov.pk  Mon Jan  6 09:05:03 2014
Return-Path: <ahmedbakhat@pta.gov.pk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D634A1AE100 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 09:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.044
X-Spam-Level: ***
X-Spam-Status: No, score=3.044 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqOJRzCWXgqz for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 09:05:01 -0800 (PST)
Received: from mail.pta.gov.pk (unknown [202.83.166.248]) by ietfa.amsl.com (Postfix) with ESMTP id 343E21AE111 for <ietf@ietf.org>; Mon,  6 Jan 2014 09:04:59 -0800 (PST)
Subject: AUTO: Ahmed Bakhat Masood is out of the office. (returning 01/08/2014)
Auto-Submitted: auto-generated
From: Ahmed Bakhat Masood <ahmedbakhat@pta.gov.pk>
To: ietf@ietf.org
Message-ID: <OF022DB1F9.57BBDD59-ON45257C58.005DB0B9-45257C58.005DB0B9@pta.gov.pk>
Date: Mon, 6 Jan 2014 22:03:20 +0500
X-MIMETrack: Serialize by Router on PTASrv002/PTA/PK(Release 8.5.3|September 15, 2011) at 01/06/2014 10:03:25 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 17:05:04 -0000

I am out of the office until 01/08/2014.

I will not be able to respond to your mail. For urgent queries, please
contact Mr. Shageel Ahmed Dy Director (ICT) at shargeel@pta.gov.pk or Mr.
Anwar Zeb IT Officer at anwar@pta.gov.pk


Note: This is an automated response to your message  "ietf Digest, Vol 68,
Issue 30" sent on 01/06/2014 5:02:51 PM.

This is the only notification you will receive while this person is away.


From superuser@gmail.com  Mon Jan  6 10:17:33 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168601AE152; Mon,  6 Jan 2014 10:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pcY8YZ024WNG; Mon,  6 Jan 2014 10:17:31 -0800 (PST)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF871AE151; Mon,  6 Jan 2014 10:17:30 -0800 (PST)
Received: by mail-wg0-f48.google.com with SMTP id z12so15850164wgg.15 for <multiple recipients>; Mon, 06 Jan 2014 10:17:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jfwaIM93gJwDdwCcIwOM8mi6LQUx/yBrtzESgk6MdCE=; b=EBlOeSVjPlPCoy4PGNMZu/ma9LVGBPlPqA0zEex1km8vmyMAwwTQxcVbDVaSr5DTj2 5vVr5mKKCIC/N2vW6uwtSjEuoKBYG64XSQnFZir+sNp3cTs32nz0gUbxruZqQXXsk26+ B9116R+N4aGLXmp2YLwgRCafPSVGv204sstqPmPf6RIuj2noSOQ4V98rtLS7iLKDYmvH eSfNwgmHMPQQPRmesn2rpX8Md4sK9ICZzOdR2VGGJiWEb4e5jSjEabHCvAEzjBscEKbF X6xuDnGBcng+opGOOxirdXe687DRxQaUzH+/5Rsv/d/3S3mzcFi8iwzLgdpOI7T7XfRw mpjw==
MIME-Version: 1.0
X-Received: by 10.194.77.7 with SMTP id o7mr35410183wjw.35.1389032241675; Mon, 06 Jan 2014 10:17:21 -0800 (PST)
Received: by 10.180.84.106 with HTTP; Mon, 6 Jan 2014 10:17:21 -0800 (PST)
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
Date: Mon, 6 Jan 2014 10:17:21 -0800
Message-ID: <CAL0qLwaHSO5GHMXa3+WbmNnJKnfXHr9S+WAn9t7H1zLwEPp-VQ@mail.gmail.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bfd05fc58c45f04ef5145fe
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 18:17:33 -0000

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

On Fri, Jan 3, 2014 at 7:14 AM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Creating an IETF Working Group Draft'
>   <draft-crocker-id-adoption-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 2014-01-31. 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 productive output of an IETF working group is documents, as
>    mandated by the working group's charter.  When a working group is
>    ready to develop a particular document, the most common mechanism is
>    for it to "adopt" an existing document as a starting point.  The
>    document that a working group adopts and then develops further is
>    based on initial input at varying levels of maturity.  An initial
>    working group draft might be a document already in wide use, or it
>    might be a blank sheet, wholly created by the working group, or it
>    might represent any level of maturity in between.  This document
>    discusses how a working group typically handles the formal documents
>    that it targets for publication.
>

I think this generally looks good, especially given SM's comments and
Dave's replies.  A few other minor points:

The process for adoption described in Section 2.1 is obsolete, as I
understand it.  I believe the current process is to have the
authors/editors submit the -00 version to the tracker, and the tracker will
block publication until a WG co-chair approves.  I also believe the
"replaced-by" step is now available via the tracker to WG chairs, so
there's no need to contact the secretariat.

The document needs a spell check ("idividual", for example).

Along the lines of the above: What do people think about documents that
describe how the tools work, other than the ones that explicitly define the
tools?  If the datatracker evolves in the near future, the tools-specific
remarks of this document could become obsolete.  Might it be better to talk
about tools-specific processes more in the abstract?

That's all that jumped out at me.

-MSK

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

<div dir=3D"ltr">On Fri, Jan 3, 2014 at 7:14 AM, The IESG <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secr=
etary@ietf.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The IESG has received a request from an individual submitter to consider<br=
>
the following document:<br>
- &#39;Creating an IETF Working Group Draft&#39;<br>
=A0 &lt;draft-crocker-id-adoption-05.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 href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2014-01=
-31. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=A0 =A0The productive output of an IETF working group is documents, as<br>
=A0 =A0mandated by the working group&#39;s charter. =A0When a working group=
 is<br>
=A0 =A0ready to develop a particular document, the most common mechanism is=
<br>
=A0 =A0for it to &quot;adopt&quot; an existing document as a starting point=
. =A0The<br>
=A0 =A0document that a working group adopts and then develops further is<br=
>
=A0 =A0based on initial input at varying levels of maturity. =A0An initial<=
br>
=A0 =A0working group draft might be a document already in wide use, or it<b=
r>
=A0 =A0might be a blank sheet, wholly created by the working group, or it<b=
r>
=A0 =A0might represent any level of maturity in between. =A0This document<b=
r>
=A0 =A0discusses how a working group typically handles the formal documents=
<br>
=A0 =A0that it targets for publication.<br></blockquote><div><br></div><div=
>I think this generally looks good, especially given SM&#39;s comments and =
Dave&#39;s replies.=A0 A few other minor points:<br><br></div><div>The proc=
ess for adoption described in Section 2.1 is obsolete, as I understand it.=
=A0 I believe the current process is to have the authors/editors submit the=
 -00 version to the tracker, and the tracker will block publication until a=
 WG co-chair approves.=A0 I also believe the &quot;replaced-by&quot; step i=
s now available via the tracker to WG chairs, so there&#39;s no need to con=
tact the secretariat.<br>
<br></div><div>The document needs a spell check (&quot;idividual&quot;, for=
 example).<br><br></div><div>Along the lines of the above: What do people t=
hink about documents that describe how the tools work, other than the ones =
that explicitly define the tools?=A0 If the datatracker evolves in the near=
 future, the tools-specific remarks of this document could become obsolete.=
=A0 Might it be better to talk about tools-specific processes more in the a=
bstract?<br>
<br></div><div>That&#39;s all that jumped out at me.<br></div><div><br></di=
v><div>-MSK<br></div><div><br>=A0<br></div></div></div></div>

--047d7bfd05fc58c45f04ef5145fe--

From brian.e.carpenter@gmail.com  Mon Jan  6 11:12:26 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5465A1AE1C0 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 11:12:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqStZ0YNcWzJ for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 11:12:24 -0800 (PST)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2031AE1BB for <ietf@ietf.org>; Mon,  6 Jan 2014 11:12:24 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fa1so19051516pad.3 for <ietf@ietf.org>; Mon, 06 Jan 2014 11:12:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=fu1AoybLWpJOc+rbn1jM7ipvmt+jO/je6HxAvz9RG+c=; b=HuLAwzTFgIsEyL/f7cIHRQrS/efLVMs3K/HDUuW932cZVf4nZY/7lwJ4ZK+U4un+5Z 6x6M2wDdZAqjn+TX1hezAVW0YoUqsulUAEvwjXCpMPhhCnOho8G9hLuePuUit9cmMyTt 5Z/qZGas6YPP1J1RdYNkmJmjHVNyTk5suuf/y4VbKfi3NeTBn0H7spOpPq2nrcVginXj t/N+kUHTNIMeI2uwAHgCaqampcmsjwZFFxhJvCEu7rnck/c3fd9+eLX/wy9oZuDkG3BF b1fdtKTh3J5MkKOj3y2ke5owBHwf+nXibb6U8hN1pDzDd8++6iZFYXhpi7f8eEVmiC+t pgvA==
X-Received: by 10.66.25.36 with SMTP id z4mr53187paf.101.1389035535900; Mon, 06 Jan 2014 11:12:15 -0800 (PST)
Received: from [192.168.178.21] (122.195.69.111.dynamic.snap.net.nz. [111.69.195.122]) by mx.google.com with ESMTPSA id wp8sm130617249pbc.26.2014.01.06.11.12.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jan 2014 11:12:15 -0800 (PST)
Message-ID: <52CB0010.5010407@gmail.com>
Date: Tue, 07 Jan 2014 08:12:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com>
In-Reply-To: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 19:12:26 -0000

On 07/01/2014 05:20, Phillip Hallam-Baker wrote:
> Following up on Jari's post, I think it would be a prudent political move
> to split the IANA functions so that assignment of IP addresses is separate
> from the protocol registry functions. The motivation behind this is to
> protect the IETF.

Actually the reason we included explosive bolts in the IETF-ICANN MoU was
to protect the IETF in this way. (By "explosive bolts" I mean the unilateral
6 months notice.) I'm not sure why would need to blow the bolts in adavance
of an emergency.

> Like the DNS, the allocation of IP address space and BGP parameters is a
> potential control point. 

The MoU contains no exception to IETF control for BGP parameters.
And to be clear, the IETF retains control of "assignments of domain
names for technical uses", so DNS asignments and IP address assignments
are on exactly the same footing: IANA functions where the IETF has
agreed that "policy issues are outside the scope of this MOU." That
is not the case for BGP parameters. Since AS numbers are not in short
supply, and are allocated by IANA upon "RIR request to the IANA or IETF
Review" I can't see why we would want to change anything.

    Brian

> It is thus an activity that is at the eye of the
> storm as far as Internet governance goes. That can't be helped and isn't
> our problem. Governments can and should argue over the governance of a
> control point that could potentially cripple their economies if abused in a
> trade war.
> 
> The allocation of protocol parameters is not a control point since there is
> no enforcement mechanism. Nobody is going to take notice if IANA were to
> ever refuse to register a content type or an algorithm under political
> pressure.
> 
> So if Iceland develops its own word processor and wants to register the
> content type, the US government cannot protect Microsoft from competition
> by passing a law that tells IANA not to issue a content-type.
> Alternatively, if the NSA was to instruct IANA to refuse to register code
> points required by Brazil's new email security scheme the effort would be
> an obvious waste of time.
> 
> Abusing control of allocations in the IP, DNS and BGP spaces would also be
> difficult to maintain but the switching costs are much higher and the
> outcome is not so obvious. That dispute is certain to continue.
> 
> 
> The problem the current situation creates is that because half of the IANA
> function intersects with IETF activities and half with ICANN type
> activities, the combination brings IETF into the line of fire in disputes
> where it can better serve all sides by being neutral.
> 
> There is already a defacto split since the IANA operates the protocol
> registry under contract with IETF and the IP/BGP registries under contract
> with the DoC. The IETF might propose protocol changes that would impact the
> numbers registry but the same is equally true of ICANN. Similarly, the IETF
> could de facto reserve chunks of IPv6 space (and in fact does still
> controls 7/8th of the total space) just as it can de facto attempt to grab
> TLDs if it chooses. But this is a consequence of the fact that it is much
> easier to fork a chunk of namespaces than is generally admitted.
> 
> So splitting IANA in two would have little operational impact but ensures
> that there is a clear boundary between the governance of Internet control
> points which is clearly in ICANN space and the governance of Internet
> standards which is clearly separate from it.
> 
> The only practical impact would be changing the name of the protocol
> registry. It would still be maintained by the same people, etc. Since the
> protocol registries are not only numbers, the name Internet Assigned
> Registry Authority (IARA) would be more appropriate in any case.
> 
> 
> Logically, the thing to do would be for ICANN to rename the IP/BGP side of
> IANA but that would not have the same protective effect politically.
> 
> 

From hallam@gmail.com  Mon Jan  6 11:58:56 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7361AE1A2 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 11:58:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QGD5sfR8T-kd for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 11:58:54 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id E27C91AE159 for <ietf@ietf.org>; Mon,  6 Jan 2014 11:58:53 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id c11so10075887lbj.37 for <ietf@ietf.org>; Mon, 06 Jan 2014 11:58:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=m0HRLs3dyLhkV1BROjVJziBo/83lvnBAuzWhjfOEKxs=; b=vcmb1+Req3LizSYrUpLrKcHtGtFjhmPnkF2ejz/hw7VO3XjVecfc/C9MeAl9dhAurX qexnQ4N15WJtHV9odAPa1Ve+22vc78cRL8xtHE88GotqRpr+zMPdePJstOMVGEwBQc1h Vjqg5YiYTZQWMxaC0n+y9FQ91DIPRN8ngh7IMhkjyzG0Z/R6Wp/vdj81T9n7j50XkLbi oy/1LE1rYanOkH9jEWl2m1TPMMvIOcrP3FuJ/S84aHxE5GN+S+0KWKFozKvidKBZYbOK Sw0QPQ2vcdrZFW1E48uo0H2Bp7mvr6N1sDLyW+wYiu0e3DjdR0MoPCvHeULS6R3B6SpP OIFA==
MIME-Version: 1.0
X-Received: by 10.152.5.8 with SMTP id o8mr33074lao.89.1389038324665; Mon, 06 Jan 2014 11:58:44 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Mon, 6 Jan 2014 11:58:44 -0800 (PST)
In-Reply-To: <52CB0010.5010407@gmail.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com>
Date: Mon, 6 Jan 2014 14:58:44 -0500
Message-ID: <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e01419b06ebd39904ef52af9c
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 19:58:56 -0000

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

On Mon, Jan 6, 2014 at 2:12 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 07/01/2014 05:20, Phillip Hallam-Baker wrote:
> > Following up on Jari's post, I think it would be a prudent political move
> > to split the IANA functions so that assignment of IP addresses is
> separate
> > from the protocol registry functions. The motivation behind this is to
> > protect the IETF.
>
> Actually the reason we included explosive bolts in the IETF-ICANN MoU was
> to protect the IETF in this way. (By "explosive bolts" I mean the
> unilateral
> 6 months notice.) I'm not sure why would need to blow the bolts in adavance
> of an emergency.


I am not suggesting changing the operation of the registry or taking it
away from ICANN which is what I would see as 'blowing the bolts'.

I am suggesting painting a new sign for the protocol side of the functions.

The closest analogy I have is that in Vermont during hunting season it is
very common to find a cow with 'COW' painted on the side in big white
letters. The reason for this is that there is a particular type of 'hunter'
who comes up from the city once a year with his mates, a large quantity of
beer and an injudicious quantity of firearms and ammunition. They are
liable shoot anything that moves. Labeling the livestock is the best way to
mitigate the losses.


> > Like the DNS, the allocation of IP address space and BGP parameters is a
> > potential control point.
>
> The MoU contains no exception to IETF control for BGP parameters.
> And to be clear, the IETF retains control of "assignments of domain
> names for technical uses", so DNS asignments and IP address assignments
> are on exactly the same footing: IANA functions where the IETF has
> agreed that "policy issues are outside the scope of this MOU." That
> is not the case for BGP parameters. Since AS numbers are not in short
> supply, and are allocated by IANA upon "RIR request to the IANA or IETF
> Review" I can't see why we would want to change anything.
>

The vulnerability is to folk whose knowledge of the IETF and IANA is
equivalent to the weekend hunter types. It is important to take the issue
off the table.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jan 6, 2014 at 2:12 PM, Brian E Carpenter <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian=
.e.carpenter@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 07/01/2014 05:20, Phill=
ip Hallam-Baker wrote:<br>
&gt; Following up on Jari&#39;s post, I think it would be a prudent politic=
al move<br>
&gt; to split the IANA functions so that assignment of IP addresses is sepa=
rate<br>
&gt; from the protocol registry functions. The motivation behind this is to=
<br>
&gt; protect the IETF.<br>
<br>
</div>Actually the reason we included explosive bolts in the IETF-ICANN MoU=
 was<br>
to protect the IETF in this way. (By &quot;explosive bolts&quot; I mean the=
 unilateral<br>
6 months notice.) I&#39;m not sure why would need to blow the bolts in adav=
ance<br>
of an emergency.</blockquote><div><br></div><div>I am not suggesting changi=
ng the operation of the registry or taking it away from ICANN which is what=
 I would see as &#39;blowing the bolts&#39;.</div><div><br></div><div>
I am suggesting painting a new sign for the protocol side of the functions.=
</div><div><br></div><div>The closest analogy I have is that in Vermont dur=
ing hunting season it is very common to find a cow with &#39;COW&#39; paint=
ed on the side in big white letters. The reason for this is that there is a=
 particular type of &#39;hunter&#39; who comes up from the city once a year=
 with his mates, a large quantity of beer and an injudicious quantity of fi=
rearms and ammunition. They are liable shoot anything that moves. Labeling =
the livestock is the best way to mitigate the losses.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
&gt; Like the DNS, the allocation of IP address space and BGP parameters is=
 a<br>
&gt; potential control point.<br>
<br>
</div>The MoU contains no exception to IETF control for BGP parameters.<br>
And to be clear, the IETF retains control of &quot;assignments of domain<br=
>
names for technical uses&quot;, so DNS asignments and IP address assignment=
s<br>
are on exactly the same footing: IANA functions where the IETF has<br>
agreed that &quot;policy issues are outside the scope of this MOU.&quot; Th=
at<br>
is not the case for BGP parameters. Since AS numbers are not in short<br>
supply, and are allocated by IANA upon &quot;RIR request to the IANA or IET=
F<br>
Review&quot; I can&#39;t see why we would want to change anything.<br></blo=
ckquote><div><br></div><div>The vulnerability is to folk whose knowledge of=
 the IETF and IANA is equivalent to the weekend hunter types. It is importa=
nt to take the issue off the table.</div>
<div>=A0</div></div><div><br></div>-- <br>Website: <a href=3D"http://hallam=
baker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e01419b06ebd39904ef52af9c--

From jcurran@istaff.org  Mon Jan  6 12:51:28 2014
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77AAC1AE1CB for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 12:51:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BdMfBffazjIi for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 12:51:26 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6B25B1AE152 for <ietf@ietf.org>; Mon,  6 Jan 2014 12:51:26 -0800 (PST)
Received: from [38.88.12.58] (helo=[10.1.201.38]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1W0H8n-000KoK-Q2; Mon, 06 Jan 2014 20:51:17 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 38.88.12.58
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/2UbFDP1LcTDWfrtJRMBI4
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Split the IANA functions?
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com>
Date: Mon, 6 Jan 2014 15:51:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 20:51:28 -0000

On Jan 6, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> I am not suggesting changing the operation of the registry or taking =
it away from ICANN which is what I would see as 'blowing the bolts'.
>=20
> I am suggesting painting a new sign for the protocol side of the =
functions.
>=20
> The closest analogy I have is that in Vermont during hunting season it =
is very common to find a cow with 'COW' painted on the side in big white =
letters. The reason for this is that there is a particular type of =
'hunter' who comes up from the city once a year with his mates, a large =
quantity of beer and an injudicious quantity of firearms and ammunition. =
They are liable shoot anything that moves. Labeling the livestock is the =
best way to mitigate the losses.
> ...

It is admirable goal, i.e. setup things so that the IETF is truly doing =
just technical coordination,=20
and thus does not attract any government/policy attention... However, it =
does sort of presume=20
that the "protocol development side" stays away from such public policy =
matters, does it not?

Alas, the success of the Internet actually preempts any reasonable =
chance of creating competing=20
protocols and approaches that will achieve similar success - basic =
network economies make=20
interoperability with (and therefore adoption of) IETF-specified =
protocols a near absolute=20
requirement for successful global deployment.  For example, if the IETF =
decides that certain=20
protocol should be encrypted by default, then governments have to live =
with that outcome;
 i.e. arguing that there is any meaningful workaround is specious.

What happens when the IETF makes a decision that particular "public =
policy" requirements=20
are _to be considered_ (perpass), or specifically _not to be considered_ =
(RFC 2804) in protocol
development?   Such is the equivalent of exercising a "control point" =
(your term) on the Internet,=20
and one that's entirely with respect to protocol development matters =
(not names or numbers). =20
The fact that there is not an "enforcement mechanism" doesn't preclude =
the control point aspects;=20
i.e. if there's an IETF consensus (quite appropriately) that pervasive =
surveillance activities are
"a technical attack that should be mitigated in the design of IETF =
protocols", then governments
are impacted by that public policy decision of the IETF.=20

> The vulnerability is to folk whose knowledge of the IETF and IANA is =
equivalent to the weekend hunter types. It is important to take the =
issue off the table.

See above.  The IETF would also need to truly be neutral (and not imbed =
publicl policy values
into protocol requirements) in order to take the issue off the table.  =
Trying to separate the IANA=20
tasks with the theoretical goal of technical purity thus would mean not =
advancing some fairly
important social values, and these already put the IETF into the =
cross-hairs due to the control
aspects.

/John

Disclaimer: My views alone.


From narten@us.ibm.com  Mon Jan  6 13:37:22 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98EC71AE260 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 13:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xucfqAh_V4hi for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 13:37:21 -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 DF3921AE251 for <ietf@ietf.org>; Mon,  6 Jan 2014 13:37:20 -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>; Mon, 6 Jan 2014 16:37:11 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 6 Jan 2014 16:37:09 -0500
Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 39BCF38C8045 for <ietf@ietf.org>; Mon,  6 Jan 2014 16:37:09 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s06Lb9rI9699776 for <ietf@ietf.org>; Mon, 6 Jan 2014 21:37:09 GMT
Received: from d01av02.pok.ibm.com (localhost [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s06Lb8eu017959 for <ietf@ietf.org>; Mon, 6 Jan 2014 16:37:08 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-92-51.mts.ibm.com [9.65.92.51]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s06Lb7aU017907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Jan 2014 16:37:08 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s06Lb6jG017519; Mon, 6 Jan 2014 16:37:07 -0500
Message-Id: <201401062137.s06Lb6jG017519@cichlid.raleigh.ibm.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
In-reply-to: <20131216175534.1390.8446.idtracker@ietfa.amsl.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com>
Comments: In-reply-to The IESG <iesg-secretary@ietf.org> message dated "Mon, 16 Dec 2013 09:55:34 -0800."
Date: Mon, 06 Jan 2014 16:37:06 -0500
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14010621-7182-0000-0000-0000097CCDD0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 21:37:22 -0000

Overall, this document looks good. But a couple of suggestions.

As a general comment, I think the document should include a reference
wherever it states what a policy is (as defined elswhere).

>    Reservations of special-purpose AS Numbers are made through Internet
>    Standards actions.

Citation of where that policy is defined?

But then later, the document says::

> 3.  IANA Considerations
> 
>    "IETF Review" as defined in [RFC5226] is required to reserve special-
>    purpose AS numbers, IPv4 addresses, or IPv6 addresses.  Reserved AS
>    numbers, IPv4 addresses, or IPv6 addresses may be designated to
>    support testing, IETF experimental activities, or other special uses
>    (e.g., anycast).  These reservations are recorded in the relevant

which contradicts the previous statement.

Also, would be good to cite all the individual RFCs when restating
what the policy is for each registries listed above.

>    Reservation of special-purpose IPv4 addresses are made through
>    Internet Standards actions.  Reserved IPv4 unicast addresses are
>    registered in the Special Purpose IP address registries [RFC6890].

Citation for first sentence?

>    The vast bulk of the IPv6 address space (approximately 7/8ths of the
>    whole address space) is reserved by the IETF, with the expectation

For first sentence, cite where that reservation/delegation was made
(i.e., RFC 3513).

Thomas


From stephen.farrell@cs.tcd.ie  Mon Jan  6 14:45:20 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7D5B1AE29A for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 14:45:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0OtXwrf5ZxM for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 14:45:19 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 585CF1AE2A7 for <ietf@ietf.org>; Mon,  6 Jan 2014 14:45:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 6C4B5BE33; Mon,  6 Jan 2014 22:45:09 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lbgp3p9sd00M; Mon,  6 Jan 2014 22:45:08 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.52.213]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 50A07BE35; Mon,  6 Jan 2014 22:45:08 +0000 (GMT)
Message-ID: <52CB31F4.3090703@cs.tcd.ie>
Date: Mon, 06 Jan 2014 22:45:08 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
In-Reply-To: <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 22:45:21 -0000

On 01/06/2014 08:51 PM, John Curran wrote:
> 
> What happens when the IETF makes a decision that particular "public policy" requirements 
> are _to be considered_ (perpass), or specifically _not to be considered_ (RFC 2804) in protocol
> development? 

I think that's a mis-characterisation. IMO both of those are cases
where there are sound technical reasons for the IETF to do, or not
do, work. Yes, those have impacts, but the public policy angle (if
that's the right term) is a side-effect and is not the reason for
the decision.

S.

From hallam@gmail.com  Mon Jan  6 14:59:02 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13DF51AE2B1 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 14:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level: 
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVmvxa9WhMyj for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 14:58:59 -0800 (PST)
Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECAF1AE2AA for <ietf@ietf.org>; Mon,  6 Jan 2014 14:58:59 -0800 (PST)
Received: by mail-lb0-f177.google.com with SMTP id q8so10098748lbi.8 for <ietf@ietf.org>; Mon, 06 Jan 2014 14:58:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=grHMJZB9GdU88H3FkWUe3p0m0qlSEcA8uj6LGzsFLAA=; b=rrOSDekvNU3yygwJB8cNHt7YyC+cxcaSXsB23eTdeTgurgOLrUM48QOweVXsBQtnYv bucpY69hVlbk6wCo5uywQbqLiQBBzsAkdYTc9DsO/AWsi2gCt0IkCUY9zsSWzIGY8cLE sOe6SaWQBvxbFlAe5Awcwr56uhrw8LUzibMWhoqe8pksOnTOaGQxwH2CX27YMqNsUDzN 6jmebp0MyE/GIlOglnltJ72lmLSmPlNYIzvNRhabWyhVzXS1kj2boBUoowdo7Qhy7AoM 7SbP1oJA5uU7rUHOsrCNZW8KuV7UJl1b3OHwuDz7NnrgE6owi3DtJJK5TRegjJxOHuk8 98Kw==
MIME-Version: 1.0
X-Received: by 10.152.5.8 with SMTP id o8mr798lao.89.1389049130276; Mon, 06 Jan 2014 14:58:50 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Mon, 6 Jan 2014 14:58:50 -0800 (PST)
In-Reply-To: <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
Date: Mon, 6 Jan 2014 17:58:50 -0500
Message-ID: <CAMm+LwgOCn8rF3ui6JBgskKe411tNbP98D8hYx9ZbicYZv5Cuw@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Curran <jcurran@istaff.org>
Content-Type: multipart/alternative; boundary=089e01419b06fc5ca004ef5533b1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 22:59:02 -0000

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

On Mon, Jan 6, 2014 at 3:51 PM, John Curran <jcurran@istaff.org> wrote:

> On Jan 6, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
> > I am not suggesting changing the operation of the registry or taking it
> away from ICANN which is what I would see as 'blowing the bolts'.
> >
> > I am suggesting painting a new sign for the protocol side of the
> functions.
> >
> > The closest analogy I have is that in Vermont during hunting season it
> is very common to find a cow with 'COW' painted on the side in big white
> letters. The reason for this is that there is a particular type of 'hunter'
> who comes up from the city once a year with his mates, a large quantity of
> beer and an injudicious quantity of firearms and ammunition. They are
> liable shoot anything that moves. Labeling the livestock is the best way to
> mitigate the losses.
> > ...
>
> It is admirable goal, i.e. setup things so that the IETF is truly doing
> just technical coordination,
> and thus does not attract any government/policy attention... However, it
> does sort of presume
> that the "protocol development side" stays away from such public policy
> matters, does it not?
>

No, I am very aware of the public policy dimension in my protocol work. I
am in the security area, I remember the cryptowars.

The question that should be asked is why the IETF gets targeted in the way
W3C and OASIS do not. I think that the confusion of the IETF role in all
things ICANN is the main reason.


W3C and OASIS also do crypto work and the security area is actually rather
more likely than others to 'go walkabout'. There is no point in a
government trying to capture our standards forum because we can always
create another.

The much bigger problem has been the effect of governments trying to
promote security protocols inside IETF that are designed to meet government
security needs at the expense of the general good. I really don't care if
fixing OCSP would require the DoD to upgrade the certificate server they
use despite the fact that the supplier went out of business a decade ago.

As an industry we already get together and rewrite specifications that we
think are nonsense. PKIX says that name constraints MUST be marked
critical, the industry consensus and running code says that they are not.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jan 6, 2014 at 3:51 PM, John Curran <span dir=3D"ltr">&lt;<=
a href=3D"mailto:jcurran@istaff.org" target=3D"_blank">jcurran@istaff.org</=
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 Jan 6, 2014, at 2:58 PM=
, Phillip Hallam-Baker &lt;<a href=3D"mailto:hallam@gmail.com">hallam@gmail=
.com</a>&gt; wrote:<br>

<br>
&gt; I am not suggesting changing the operation of the registry or taking i=
t away from ICANN which is what I would see as &#39;blowing the bolts&#39;.=
<br>
&gt;<br>
&gt; I am suggesting painting a new sign for the protocol side of the funct=
ions.<br>
&gt;<br>
&gt; The closest analogy I have is that in Vermont during hunting season it=
 is very common to find a cow with &#39;COW&#39; painted on the side in big=
 white letters. The reason for this is that there is a particular type of &=
#39;hunter&#39; who comes up from the city once a year with his mates, a la=
rge quantity of beer and an injudicious quantity of firearms and ammunition=
. They are liable shoot anything that moves. Labeling the livestock is the =
best way to mitigate the losses.<br>

</div>&gt; ...<br>
<br>
It is admirable goal, i.e. setup things so that the IETF is truly doing jus=
t technical coordination,<br>
and thus does not attract any government/policy attention... However, it do=
es sort of presume<br>
that the &quot;protocol development side&quot; stays away from such public =
policy matters, does it not?<br></blockquote><div><br></div><div>No, I am v=
ery aware of the public policy dimension in my protocol work. I am in the s=
ecurity area, I remember the cryptowars.</div>
<div><br></div><div>The question that should be asked is why the IETF gets =
targeted in the way W3C and OASIS do not. I think that the confusion of the=
 IETF role in all things ICANN is the main reason.</div><div><br></div>
<div><br></div><div>W3C and OASIS also do crypto work and the security area=
 is actually rather more likely than others to &#39;go walkabout&#39;. Ther=
e is no point in a government trying to capture our standards forum because=
 we can always create another.</div>
<div><br></div><div>The much bigger problem has been the effect of governme=
nts trying to promote security protocols inside IETF that are designed to m=
eet government security needs at the expense of the general good. I really =
don&#39;t care if fixing OCSP would require the DoD to upgrade the certific=
ate server they use despite the fact that the supplier went out of business=
 a decade ago.</div>
<div><br></div><div>As an industry we already get together and rewrite spec=
ifications that we think are nonsense. PKIX says that name constraints MUST=
 be marked critical, the industry consensus and running code says that they=
 are not.</div>
</div><div><br></div><div><br></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e01419b06fc5ca004ef5533b1--

From l.wood@surrey.ac.uk  Mon Jan  6 15:03:54 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2634D1AE2BF for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:03:54 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LhHQGDa7bnhh for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:03:51 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id D1A441AD8D5 for <ietf@ietf.org>; Mon,  6 Jan 2014 15:03:50 -0800 (PST)
Received: from [85.158.137.99:51157] by server-14.bemta-3.messagelabs.com id 9A/2D-06105-D463BC25; Mon, 06 Jan 2014 23:03:41 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-217.messagelabs.com!1389049420!17573288!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13520 invoked from network); 6 Jan 2014 23:03:41 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-12.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 6 Jan 2014 23:03:41 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 6 Jan 2014 23:03:40 +0000
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <jcurran@istaff.org>, <hallam@gmail.com>
Date: Mon, 6 Jan 2014 23:03:39 +0000
Subject: RE: Split the IANA functions?
Thread-Topic: Split the IANA functions?
Thread-Index: Ac8LMRDB+gKuNXtjTWSxafMwyM3R5gAAZfu3
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346A8@EXMB01CMS.surrey.ac.uk>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>, <52CB31F4.3090703@cs.tcd.ie>
In-Reply-To: <52CB31F4.3090703@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 23:03:54 -0000

Both perpass and RFC2804 are political reactions to the public environment.

To characterize either of them as technically motivated is disingenuous. Ne=
ither outlines
a technical approach.

>From RFC2804:
   These questions are believed to be irrelevant to the policy outlined
   in this memo.

See? policy.

>From draft-farrell-perpass-attack-03:

   The technical plenary of the November 2013 IETF meeting
   [IETF88Plenary] discussed pervasive monitoring (or surveillance)
   which requires the monitoring party to take actions that are
   indistinguishable from an attack on Internet communications.
   Participants at that meeting therefore expressed strong agreement
   that this was an attack that should be mitigated where possible via
   the design of protocols that make pervasive monitoring significantly
   more expensive or infeasible.  This Best Current Practice (BCP, see
   [RFC2026] Section 5) formally documents that consensus.

again, policy, pure and simple.

The usual claim that the IETF is a technical organisation that doesn't do p=
oliticics
is itself a disingenuous political position...

The public policy angle is the prime motivation for the existence of these
documents. It is not a side-effect.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 06 January 2014 22:45
To: John Curran; Phillip Hallam-Baker
Cc: IETF Discussion Mailing List
Subject: Re: Split the IANA functions?

On 01/06/2014 08:51 PM, John Curran wrote:
>
> What happens when the IETF makes a decision that particular "public polic=
y" requirements
> are _to be considered_ (perpass), or specifically _not to be considered_ =
(RFC 2804) in protocol
> development?

I think that's a mis-characterisation. IMO both of those are cases
where there are sound technical reasons for the IETF to do, or not
do, work. Yes, those have impacts, but the public policy angle (if
that's the right term) is a side-effect and is not the reason for
the decision.

S.

From abdussalambaryun@gmail.com  Mon Jan  6 15:14:17 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06241AE2D0 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:14:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4
X-Spam-Level: 
X-Spam-Status: No, score=-4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgsvmCgthAS4 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:14:15 -0800 (PST)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B11AE1AD8CD for <ietf@ietf.org>; Mon,  6 Jan 2014 15:14:15 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id w10so18718909pde.20 for <ietf@ietf.org>; Mon, 06 Jan 2014 15:14:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Pquuhc0Jryd5a0n0k0Gr4rpK0uXtxnPM3/odLyLJb/c=; b=lzj7aROxnTGjLkhBAvq+HUXSSjGJVceZ8kfecq7Q27vbAeOWpY0lbieRFGicgD5fAo NfrYIDz4Kr1d3FFEjtkf38l+0P/EDx4L41P5dROmopfEGEL1yUX5b6aHzuticoBsX51m Q8MVbANwkcFs1JRjFd76QjNHUYkigELZL0u8LvF0pnO/kU7BajtApzi7b8mIvHygKt7T TpsvOz8YB2oznJfsjWlYQp3SmuHCfM2YlYpTQWK1L17Qzgly/57gqJ5a35EE5kNPxvdA 5ik+Ejpqr2qcRQtkfA5m2svvRJDIgm8TSTeV/dB+HdHKZOaj7zYjtmBnAiaKQiJ6gvW0 2szw==
MIME-Version: 1.0
X-Received: by 10.68.164.4 with SMTP id ym4mr85058018pbb.53.1389050047061; Mon, 06 Jan 2014 15:14:07 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Mon, 6 Jan 2014 15:14:06 -0800 (PST)
In-Reply-To: <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org>
Date: Tue, 7 Jan 2014 00:14:06 +0100
Message-ID: <CADnDZ8_NUzZJUBUoOcpwmQ7CZTSkFd_o_rF0C-qByAYabHK5Ow@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John Curran <jcurran@istaff.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 23:14:17 -0000

I agree with you,

IETF should consider policies for designing protocols/technologies for
the public user community in all regions with diversity and fareness.
If the IETF still does not know how to solve attacks on the
internet/design/practice, so why will it allow separting related IANA
functions.

The first message in the thread suggests the motivation is to protect
IETF but what about protecting the Internet users in the world.

AB

On 1/6/14, John Curran <jcurran@istaff.org> wrote:
> On Jan 6, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>> I am not suggesting changing the operation of the registry or taking it
>> away from ICANN which is what I would see as 'blowing the bolts'.
>>
>> I am suggesting painting a new sign for the protocol side of the
>> functions.
>>
>> The closest analogy I have is that in Vermont during hunting season it is
>> very common to find a cow with 'COW' painted on the side in big white
>> letters. The reason for this is that there is a particular type of
>> 'hunter' who comes up from the city once a year with his mates, a large
>> quantity of beer and an injudicious quantity of firearms and ammunition.
>> They are liable shoot anything that moves. Labeling the livestock is the
>> best way to mitigate the losses.
>> ...
>
> It is admirable goal, i.e. setup things so that the IETF is truly doing just
> technical coordination,
> and thus does not attract any government/policy attention... However, it
> does sort of presume
> that the "protocol development side" stays away from such public policy
> matters, does it not?
>
> Alas, the success of the Internet actually preempts any reasonable chance of
> creating competing
> protocols and approaches that will achieve similar success - basic network
> economies make
> interoperability with (and therefore adoption of) IETF-specified protocols a
> near absolute
> requirement for successful global deployment.  For example, if the IETF
> decides that certain
> protocol should be encrypted by default, then governments have to live with
> that outcome;
>  i.e. arguing that there is any meaningful workaround is specious.
>
> What happens when the IETF makes a decision that particular "public policy"
> requirements
> are _to be considered_ (perpass), or specifically _not to be considered_
> (RFC 2804) in protocol
> development?   Such is the equivalent of exercising a "control point" (your
> term) on the Internet,
> and one that's entirely with respect to protocol development matters (not
> names or numbers).
> The fact that there is not an "enforcement mechanism" doesn't preclude the
> control point aspects;
> i.e. if there's an IETF consensus (quite appropriately) that pervasive
> surveillance activities are
> "a technical attack that should be mitigated in the design of IETF
> protocols", then governments
> are impacted by that public policy decision of the IETF.
>
>> The vulnerability is to folk whose knowledge of the IETF and IANA is
>> equivalent to the weekend hunter types. It is important to take the issue
>> off the table.
>
> See above.  The IETF would also need to truly be neutral (and not imbed
> publicl policy values
> into protocol requirements) in order to take the issue off the table.
> Trying to separate the IANA
> tasks with the theoretical goal of technical purity thus would mean not
> advancing some fairly
> important social values, and these already put the IETF into the cross-hairs
> due to the control
> aspects.
>
> /John
>
> Disclaimer: My views alone.
>
>

From lberger@labn.net  Mon Jan  6 15:41:46 2014
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EB471AE338 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T58S8g9sRLgs for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 15:41:45 -0800 (PST)
Received: from alt-proxy6.mail.unifiedlayer.com (alt-proxy6.mail.unifiedlayer.com [66.147.245.65]) by ietfa.amsl.com (Postfix) with SMTP id CA5951AE337 for <ietf@ietf.org>; Mon,  6 Jan 2014 15:41:44 -0800 (PST)
Received: (qmail 5369 invoked by uid 0); 6 Jan 2014 23:41:31 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy14.mail.unifiedlayer.com with SMTP; 6 Jan 2014 23:41: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=gldf/3zDjkEqfBdH3uqlpAPdalGbeReDJ4MuxV4YwVI=;  b=T7MD4OR1TxyFEJjgXWw/Nj+9TRDYWssJRhqQOjgxcbS9J/EMPrumHQFcwibQkQAWo8OfH3v2dozgjlA7pHSW66yBIeiEEqihasv/IvGlei+nHr/UFEAkPQZZL43Y5iL0;
Received: from box313.bluehost.com ([69.89.31.113]:49702 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.80) (envelope-from <lberger@labn.net>) id 1W0JnW-0002te-QD; Mon, 06 Jan 2014 16:41:30 -0700
Message-ID: <52CB3F28.4070100@labn.net>
Date: Mon, 06 Jan 2014 18:41:28 -0500
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Russ Housley' <housley@vigilsec.com>,  draft-ietf-mpls-tp-p2mp-framework.all@tools.ietf.org
Subject: Re: Gen-ART review of draft-ietf-mpls-tp-p2mp-framework-05
References: <58B0075F-C7C4-457C-A2A4-DC12CA39281F@vigilsec.com> <008d01cf0950$d86d2920$89477b60$@olddog.co.uk>
In-Reply-To: <008d01cf0950$d86d2920$89477b60$@olddog.co.uk>
X-Enigmail-Version: 1.6
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: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jan 2014 23:41:46 -0000

Russ/Adrian,

A couple of editorial points:

On 1/4/2014 8:28 AM, Adrian Farrel wrote:
> Hi Russ,
> 
> Thanks for the review.

Agreed!

> 
...

> 
>> Other Comments:
>>
>> In the first sentence of Section 1, please define MPLS-TP as follows:
>> OLD:
>>    The Multiprotocol Label Switching Transport Profile is the ...
>> NEW:
>>    The Multiprotocol Label Switching Transport Profile (MPLS-TP) is ...
> 
> Sure.
> 
>> Please add TE-LSP to the terms defined in Section 1.2.
> 
> Sure.
Actually, this is a good catch as it really should say: "Traffic
Engineered P2MP LSP" and "Traffic Engineered multipoint-to-multipoint LSPs".

> 
>> In Section 5.1, I cannot understand this sentence:
>>>
>>>  Per [RFC6373], the definitions of P2MP, [RFC4875], and GMPLS
>>>  recovery, [RFC4872] and [RFC4873], do not explicitly cover their
>>>  interactions.
>>>
>> I think that the references are getting in the way.  I think the
>> message is: "the definitions of P2MP and GMPLS recovery do not
>> explicitly cover their interactions."  If I am correct, then some
>> commas need to be removed.
> 
> Yes, you're right. And a minor rewrite could make this even clearer.
> 

How about:
[RFC6373] notes that recovery techniques for Traffic Engineered P2MP
LSPs are not formally defined, and such that a definition is needed.   A
formal definition will be based on existing RFCs and may not require any
new protocol mechanisms but, nonetheless, should be documented. GMPLS
recovery is defined in [RFC4872] and [RFC4873]. Protection of P2MP LSPs
is also discussed in [RFC6372] Section 4.7.3.

>> The phrase "MPLS Transport Profile" appears many places, and it would
>> be easier if they were replaces with "MPLS-TP" for consistency.
> 

Sure.

> OK

We'll have a version ready to go soon and will coordinate with Adrian on
publication.

Thanks again,
Lou


From dhc@dcrocker.net  Mon Jan  6 15:51:46 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 793CA1AE364; Mon,  6 Jan 2014 15:51:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JROVVzUYINuS; Mon,  6 Jan 2014 15:51:45 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0A5311AE346; Mon,  6 Jan 2014 15:51:45 -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 s06NpV1h013075 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Jan 2014 15:51:35 -0800
Message-ID: <52CB4124.9030801@dcrocker.net>
Date: Mon, 06 Jan 2014 15:49:56 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>, ietf <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <CAL0qLwaHSO5GHMXa3+WbmNnJKnfXHr9S+WAn9t7H1zLwEPp-VQ@mail.gmail.com>
In-Reply-To: <CAL0qLwaHSO5GHMXa3+WbmNnJKnfXHr9S+WAn9t7H1zLwEPp-VQ@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.66]); Mon, 06 Jan 2014 15:51:35 -0800 (PST)
Cc: IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 06 Jan 2014 23:51:46 -0000

On 1/6/2014 10:17 AM, Murray S. Kucherawy wrote:
> The process for adoption described in Section 2.1 is obsolete, as I
> understand it.  I believe the current process is to have the
> authors/editors submit the -00 version to the tracker, and the tracker
> will block publication until a WG co-chair approves.  I also believe the
> "replaced-by" step is now available via the tracker to WG chairs, so
> there's no need to contact the secretariat.


I think this highlights the need for some documentation on the use of 
the tracker, explicitly covering some specific scenarios such as this one.

The -adoption document is meant to focus on the working group side of 
things.

So I'd wish that the portion of -adoption that gives sequences for the 
tracker could, instead, simply cite a tracker document. The draft 
provides detail about using the tracker only because there does not 
appear to be any existing documentation to point to.  (The only existing 
document is an RFC that specifies requirements, not procedures.)  And 
just so there is no confusion:  what is needed is more than a document 
of individual functions; there needs to be instruction for accomplishing 
common /sequences/. That is, how to combine the individual functions.

Absent that, here's the change to -adoption that covers what Murray has 
highlighted:


>           1.  Inform the working group of the intent.
>
>           2.  Check for known IPR that needs to be disclosed, using some
>               technique like those described in [RFC6702]
>
>           3.  Obtain working group rough consensus.
>
>           4.  Choose document editors.
>
>           5.  Pre-approve the document as an Internet Draft, using
>               [Approval].
>
>           6.  Tell the editors to submit the -00 version of the document.
>
>           7.  Request Secretariat to ensure that the Datatracker records
>               that the old internet-draft has been replaced by the new
>               working group draft.
>
>           8.  Enjoy the ensuing working group discussion...
>

becomes:

       1.  Inform the working group of the intent.

       2.  Check for known IPR that needs to be disclosed, using some
           technique like those described in [RFC6702]

       3.  Obtain working group rough consensus.

       4.  Choose document editors.

       5.  Authors/editors submit the -00 version to the tracker;
           the tracker will block publication.

       6.  WG co-chair approves the draft to the tracker.

       7.  WG co-chair uses tracker "Replaced-By" featres, to indicate
           that that the old internet-draft has been replaced by the new
           working group draft.

       8.  Enjoy the ensuing working group discussion...


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jcurran@istaff.org  Mon Jan  6 16:16:51 2014
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96D41AE391 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 16:16:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ohs2j_66NhLe for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 16:16:47 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id ABE821AE390 for <ietf@ietf.org>; Mon,  6 Jan 2014 16:16:46 -0800 (PST)
Received: from pool-108-45-30-69.washdc.fios.verizon.net ([108.45.30.69] helo=[192.168.1.9]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1W0KLV-000Dj5-Uk; Tue, 07 Jan 2014 00:16:38 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.45.30.69
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX19AhXJxrX3c/J+9OR1JNySC
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Split the IANA functions?
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAMm+LwgOCn8rF3ui6JBgskKe411tNbP98D8hYx9ZbicYZv5Cuw@mail.gmail.com>
Date: Mon, 6 Jan 2014 19:16:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4ED70504-868E-460E-988D-4758D57DEA6C@istaff.org>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <CAMm+LwgOCn8rF3ui6JBgskKe411tNbP98D8hYx9ZbicYZv5Cuw@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 00:16:52 -0000

On Jan 6, 2014, at 5:58 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> The question that should be asked is why the IETF gets targeted in the =
way W3C and OASIS do not. I think that the confusion of the IETF role in =
all things ICANN is the main reason.

You keep making that assertion, and I'll agree that the IETF is targeted =
more frequently
because of the policy aspects of its work.  That doesn't mean =
governments don't watch
the policy aspects of W3C (e.g. DNT), only that much less of that work =
has public policy
implications, and hence there are less mutual encounters.

Note - the other reason that IP and DNS names get more attention is =
because there are=20
international treaty organizations which operate in apparently similar =
spaces, i.e. it's not
necessarily the result of actual interest by governments in the public =
policy implications=20
of the IETF's work, but an expression of inter-organanization dynamics.  =
The W3C has=20
not been honored with having any helpful friends similar in nature to =
the ITU and WIPO.

FYI,
/John

Disclaimer: My views alone.




From jcurran@istaff.org  Mon Jan  6 17:28:09 2014
Return-Path: <jcurran@istaff.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90C901AE3B4 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 17:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUuesRKdEz9b for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 17:28:07 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id B85DF1AE3AB for <ietf@ietf.org>; Mon,  6 Jan 2014 17:28:07 -0800 (PST)
Received: from pool-108-45-30-69.washdc.fios.verizon.net ([108.45.30.69] helo=[192.168.1.9]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1W0LSY-000CYT-3Z; Tue, 07 Jan 2014 01:27:58 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.45.30.69
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/ywzFgso6pSAC4J7pb4BwQ
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Split the IANA functions?
From: John Curran <jcurran@istaff.org>
In-Reply-To: <52CB31F4.3090703@cs.tcd.ie>
Date: Mon, 6 Jan 2014 20:27:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0B57AB63-CA73-42BD-94C3-E20983FF4432@istaff.org>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1827)
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 01:28:09 -0000

On Jan 6, 2014, at 5:45 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> On 01/06/2014 08:51 PM, John Curran wrote:
>>=20
>> What happens when the IETF makes a decision that particular "public =
policy" requirements=20
>> are _to be considered_ (perpass), or specifically _not to be =
considered_ (RFC 2804) in protocol
>> development?=20
>=20
> I think that's a mis-characterisation. IMO both of those are cases
> where there are sound technical reasons for the IETF to do, or not
> do, work. Yes, those have impacts, but the public policy angle (if
> that's the right term) is a side-effect and is not the reason for
> the decision.

Stephen -=20
=20
 I did not mean to imply that the primary driver was the IETF taking
 on a public policy matter; only that the decision being made (even=20
 if on a sound technical basis) have real public policy implications,=20
 and thus will attract interest of many non-technical parties, including
 governments.

/John

Disclaimer: My views alone.



From brian.e.carpenter@gmail.com  Mon Jan  6 19:16:08 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EEE41AE3E1 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c81BKA4w7xZi for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:16:06 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCD51AE3E0 for <ietf@ietf.org>; Mon,  6 Jan 2014 19:16:06 -0800 (PST)
Received: by mail-pa0-f50.google.com with SMTP id kp14so17578439pab.37 for <ietf@ietf.org>; Mon, 06 Jan 2014 19:15:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=2gZDHRGBplbAOiaMdAr71U1qpYh/klg7/Kc22qN5EhI=; b=UtDE9AvxfgN5Dnvt5i/tKX6vdyszSug+FqR2jWe87nQOYyDVRB9QdzSGwJOfiDShaM rrgB+eN2LduS05U79tQvTa2QdvEAJzcOE3FjOv9lrsjm2JzAbTlKabyxRQ2eU3Hu1A0n wyq8qr+/Ic09JpluBtCU6Bx76fwK9oScQ9ZC5RgHusmm6u7SH0QmdUUxRhnkPqMTq/JE pnnsz3oWa3jRZDJSjgYvCRv6eyOYdsbT9CXpORmFXiGeEQzmxRrGMMqlhUaPiNCCVWaV 1+RVhmm8HwXo5V52ZDshBaVq399iyetxrExbafWO28TtwBe3jXkRoMlorXt+Ixv9GGgL HHCg==
X-Received: by 10.66.160.195 with SMTP id xm3mr2153463pab.93.1389064557575; Mon, 06 Jan 2014 19:15:57 -0800 (PST)
Received: from [192.168.178.21] (122.195.69.111.dynamic.snap.net.nz. [111.69.195.122]) by mx.google.com with ESMTPSA id ik1sm132191960pbc.9.2014.01.06.19.15.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Jan 2014 19:15:56 -0800 (PST)
Message-ID: <52CB716E.6090205@gmail.com>
Date: Tue, 07 Jan 2014 16:15:58 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Curran <jcurran@istaff.org>
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <0B57AB63-CA73-42BD-94C3-E20983FF4432@istaff.org>
In-Reply-To: <0B57AB63-CA73-42BD-94C3-E20983FF4432@istaff.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 03:16:08 -0000

On 07/01/2014 14:27, John Curran wrote:
> On Jan 6, 2014, at 5:45 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>> On 01/06/2014 08:51 PM, John Curran wrote:
>>> What happens when the IETF makes a decision that particular "public policy" requirements 
>>> are _to be considered_ (perpass), or specifically _not to be considered_ (RFC 2804) in protocol
>>> development? 
>> I think that's a mis-characterisation. IMO both of those are cases
>> where there are sound technical reasons for the IETF to do, or not
>> do, work. Yes, those have impacts, but the public policy angle (if
>> that's the right term) is a side-effect and is not the reason for
>> the decision.
> 
> Stephen - 
>  
>  I did not mean to imply that the primary driver was the IETF taking
>  on a public policy matter; only that the decision being made (even 
>  if on a sound technical basis) have real public policy implications, 
>  and thus will attract interest of many non-technical parties, including
>  governments.

Of course, this has been true of every major technology innovation for
the last couple of thousand years, once the technology pervades society.
So we shouldn't be surprised or alarmed when public policy implications
of IETF technical decisions show up.

It's certainly true that in the current case, and the cases of RFC 1984
and 2804, there were public events and debates prior to the IETF taking
a position. I don't see why we should be worried by that either, as long
as we take technically based decisions that help the Internet work better.

    Brian

From stewe@stewe.org  Mon Jan  6 19:41:33 2014
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC7491AE405 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MB7vbm0RaU5C for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:41:30 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0205.outbound.protection.outlook.com [207.46.163.205]) by ietfa.amsl.com (Postfix) with ESMTP id 1F96A1AE3F0 for <ietf@ietf.org>; Mon,  6 Jan 2014 19:41:29 -0800 (PST)
Received: from CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) by CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) with Microsoft SMTP Server (TLS) id 15.0.842.7; Tue, 7 Jan 2014 03:41:06 +0000
Received: from CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.85]) by CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.85]) with mapi id 15.00.0842.003; Tue, 7 Jan 2014 03:41:06 +0000
From: Stephan Wenger <stewe@stewe.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
Thread-Topic: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
Thread-Index: AQHPC1pKwZEVzU2IZEyDjduKKyG37Q==
Date: Tue, 7 Jan 2014 03:41:04 +0000
Message-ID: <CEF0A2FD.3ED34%stewe@stewe.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [50.174.124.99]
x-forefront-prvs: 008421A8FF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(189002)(479174003)(53754006)(199002)(52604005)(51704005)(24454002)(47446002)(80976001)(63696002)(66066001)(85306002)(56816005)(90146001)(59766001)(15975445006)(65816001)(77982001)(81816001)(56776001)(87266001)(19580395003)(81542001)(15202345003)(54316002)(47976001)(31966008)(74502001)(2656002)(74662001)(83322001)(80022001)(74366001)(79102001)(4396001)(50986001)(36756003)(46102001)(69226001)(47736001)(49866001)(77096001)(81342001)(19580405001)(76176001)(81686001)(85852003)(87936001)(83072002)(53806001)(76482001)(74876001)(76796001)(76786001)(74706001)(54356001)(51856001)(42262001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR07MB363; H:CO1PR07MB363.namprd07.prod.outlook.com; CLIP:50.174.124.99; FPR:; RD:InfoNoRecords; MX:1; A:0; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <E07919A3ED3A9849BF8C5C9A36823C97@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 03:41:34 -0000

Hi all,
As the time window for the last call comes to a close shortly, I want to
chime in.  This is going to be my first and last message on this
subject--I will not have time to argue my viewpoints due to other, for me
more important, commitments.

I=B9m against publishing this draft in any form.  I=B9m convinced, based on
the mailing list discussion up to now, and on my own reading, that
publishing this draft has more risks than benefits for myself and for the
IETF.  Here are a few condensed points.

1. My personal risk/benefit equation:
The main disconnect I see in the draft is its implicit assumption that an
=B3attack=B2 is a Bad Thing.  It=B9s an implicit assumption, because after =
the
very  clear definition for =B3attack=B2 provided in section 1, the draft
immediately jumps to the subject of the need for the IETF to work towards
mitigation, which implies that there is something (namely the =B3attack")
that needs to be mitigated.  That is an immensely political statement that
has not been addressed in the draft.  There are countless examples where
=B3attacks=B2 (as defined in the draft) have saved lives and generally have
done good to the world.  I=B9m personally convinced that, on balance, the
world would be a much worse place without =B3attacks=B2 than with.  Without
=B3attacks=B2, we would probably not have safe mass transportation, terrori=
st
of different colour would run wild, organized crime would be widespread,
and so on.  I DO WANT my communication to be =B3attackable=B2 (albeit not
necessarily easily attackable), based on the assumption that, generally
speaking, me, being a moderately good guy myself, will probably not be
subject to too many attacks by the good guys because my views are
generally better aligned with the good guys than with the bad guys.  Even
if the good guys were spying on me, they could hardly use that information
in a way that would hurt me.  OTOH, I want that the communication of the
bad guys, be they terrorists, organized crime or whatever, to be broken
into, and their schemes to be disrupted by law enforcement, before they
have a chance to attack (without quotes) me in the very real sense of
flying bullets and blown up planes.  For that, I=B9m willing to accept that
the bad guys can break my communication as well.  This logic obviously
works best, today, when living in a western democracy (like I do),
generally trusting the government (as I do), and having the resources and
the will to fight (like I think I have) if I am =B3attacked=B2 by the
government or anyone else for illegitimate reasons (Note that I didn=B9t
write =B3illegal=B2).=20
Note that I have labeled this section =B3My personal risk/benefit equation=
=B2.
 I can fully understand if others set other priorities.  However, I
participate in the IETF as well, and my viewpoint should (and. I=B9m quite
confident, will) be taken into account as those of others, despite it
being perhaps somewhat politically incorrect in the current climate.

2. IETF=B9s risk/benefit equation
2.a declaring consensus on something like this.  The assertion in the
document that it represents IETF consensus (based on the plenary) has
already been competently challenged.  No need to repeat.  But let me add
that in this case we have an even stronger problem with the =B3silent
majority=B2 than usual.  I could imagine that a large percentage of the IET=
F
participants, especially those living in areas less fortunate than the
western democracies, cannot voice their opinion safely and freely, even if
they wished.  As stated above, I believe this is an immensely political
draft (for the reason that it makes implicit assumptions), and some folks
have to be more careful than others commenting.  I carefully tried to stay
away speculating what their view may be, and I invite others to do the
same--this is not only a political but also a cultural question.
2.b there is the further risk that even more of our standards get silently
disregarded in large parts of the world, potentially leading to less
interoperability and an even more pronounced split between a =B3western
democracy Internet=B2 and =B3rest of the world Internet".  Already, there a=
re
countries where any form of encryption of media data and emails is
forbidden, and one goes to jail (or worse) if one does.  I don=B9t say that
this is a good thing, but fighting the situation is once more an immensely
political process, and I don=B9t think the IETF is particularly good at
that, nor does it need to be.
2.c for my own work in the IETF, I do not want to see yet another opening
that potentially allows the security lobby to require me to load up my own
drafts, which have nothing to do with security, with additional security
oriented language.  I=B9m not a security guy.  I don=B9t care about pervasi=
ve
monitoring; I view it generally as beneficial (see above).  Why should I
have answers ready when competent others ask me questions about it?  Why
should I see my documents delayed for this stuff?  They may well be very
good documents in what they are describing.  We have enough boilerplate
and process already, thank you.
2.d risk of misrepresentation by the media.  The language of the draft is
flashy enough to invite misrepresentation by the media.  It cannot be in
the interest of the IETF to see one of its future core docs (process BCPs
are just that, right?) be misinterpreted by journalists, many of which
probably having spent even less time with this doc than myself.
2.e as for the benefits, where are they?  The IETF would be viewed in
certain progressive circles in the western democracies as sensitive
people, especially in year 1 past Snowden.  (I=B9m not so sure how we would
look in year 1 after the next large scale terrorist attack.)  The security
guys would have more work.  Nothing against good biz-dev, but does it
really have to be an IETF BCP? :-)  What else?  Nothing comes to my mind.

Thanks for reading.

Best regards,
Stephan=20


On 12/3/13, 20:45, "Jari Arkko" <jari.arkko@piuha.net> wrote:

>I wanted to draw your attention on this last call:
>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Pervasive Monitoring is an Attack'
>>  <draft-farrell-perpass-attack-02.txt> as Best Current Practice
>>=20
>> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/
>
>
>It is a short read and important, so please comment. The last call ends
>in four weeks and covers holiday time, but we'll deal with this document
>on the January 9th telechat in the IESG, so in practice there should be
>enough time to comment.
>
>I would like to see this document as a high-level policy we have on
>dealing with this particular type of vulnerabilities in the Internet. A
>little bit like RFC 3365 "Danvers Doctrine" was on weak vs. strong
>security. Please remember that the details and tradeoffs for specific
>solutions are for our WGs to consider and not spelled out here. The draft
>does say "where possible" - I do not want to give the impression that our
>technology can either fully prevent all vulnerabilities or do it in all
>situations. There are obviously aspects that do not relate to
>communications security (like access to content by your peer) and there
>are many practical considerations that may not make it possible to
>provide additional privacy protection even when we are talking about the
>communications part. But I do believe we need to consider these
>vulnerabilities and do our best.
>
>Jari
>


From wzhang@cisco.com  Mon Jan  6 19:59:17 2014
Return-Path: <wzhang@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65B7F1AE41E for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FptxdXqxvjEL for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 19:59:15 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id CA01B1AE412 for <ietf@ietf.org>; Mon,  6 Jan 2014 19:59:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3847; q=dns/txt; s=iport; t=1389067147; x=1390276747; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=y4+GCdrc4TtrvpFomb8J20tgioJ1EC+ZTUkxD+B5aOc=; b=BwEJ03c3+8pDjet8E5YsdNk6UmVENbQnGx30hCMqqt6knpDcR1qxPGN6 v8ywyVwShMc+x7bfsxVkYSxMPx3PVj6sazbgEo2uBCIEDuSm3BG+xyoNe fybu1HJ8VwgSWl//Znw9q/D2a2W126dNIOqa5sy5E49GPuWrtKXk6Es5b I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFANh6y1KtJXHA/2dsb2JhbABOCoMLOFW5Y4EOFnSCJQEBAQQ6NBcEAgEIEQQBAQsUCQcyFAkIAgQTCBOHaQ3DaheOMys4BoMegRMElDOFFJBlgW+BPoIq
X-IronPort-AV: E=Sophos;i="4.95,616,1384300800"; d="scan'208";a="10962433"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-5.cisco.com with ESMTP; 07 Jan 2014 03:59:06 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s073x6ni011725 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Tue, 7 Jan 2014 03:59:06 GMT
Received: from xmb-aln-x11.cisco.com ([169.254.6.26]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Mon, 6 Jan 2014 21:59:06 -0600
From: "Wen Zhang (wzhang)" <wzhang@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in  UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in  UDP) to Proposed Standard
Thread-Index: AQHPC1t36YfXY5vgVkiuer8dxagavZp4oVjg
Date: Tue, 7 Jan 2014 03:59:06 +0000
Message-ID: <9578445A783CDA4BB56A3D77ED02FE88203AEA12@xmb-aln-x11.cisco.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com>
In-Reply-To: <20140102151419.4692.48031.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.255.125]
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 03:59:17 -0000

Hi,

Here are a few comments/feedback on the draft:

1. Section 3. Encapsulation in UDP

I'd like to see the source port allocation requirements stated in a more ex=
plicit manner. The draft seems to imply the udp source port should vary on =
a per-flow basis in order to achieve the load-
sharing goal, so maybe we can state exactly that? ie., I would prefer the f=
ollowing sentence to read:

Source Port of UDP

     This field contains a 16-bit entropy value that is
     generated by the ingress PE router to uniquely identify
     an MPLS flow. What algorithm...

2. Section 6 Security Considerations

For the security aspects, I'd like to see a better problem description. To =
me the problem is not so much of how to address integrity and privacy for M=
PLS-over-UDP, but rather what _new_ problem is introduced with MPLS-over-UD=
P that native mpls or other mpls encapsulation solutions doesn't have. In o=
ther words, is integrity/privacy a bigger problem for mpls-over-udp than pl=
ain mpls,
and why? or how the solution makes security an easier or harder problem? On=
 the surface, the security concern should be no more or less than what's al=
ready stated in RFC-4023 (MPLS in IP or GRE).

3. I think the IPSec vs. DTLS discussion can use a bit more clarity without=
 going into too much protocol discussion between the two. I would suggest t=
he following change in the text:

=3D=3D=3D=3D
In the case where any of the above security issues is concerned, the MPLS-i=
n-UDP tunnels SHOULD be secured with IPsec or DTLS. Both protocols should s=
atisfy the authentication, integrity, and confidentiality security requirem=
ents. IPSec was designed as network security mechanism for Internet Protoco=
ls, and therefore resides at the network layer. As such, if the tunnel is s=
ecured with IPsec, the UDP header would not be visible to P routers anymore=
 in either IPSec tunnel or transport mode. As a result, the meaning of adop=
ting MPLS-in-UDP encapsulation format as an alternative to MPLS-in-GRE and =
MPLS-in-IP encapsulation formats is lost. By comparison, DTLS is better sui=
ted for application security and can better preserve network and transport =
layer protocol information.
Specifically, if DTLS is used, the destination port of the UDP header will =
be filled with a value (TBD2) indicating MPLS with DTLS and the source port=
 can still be used as an entropy field for load sharing purposes.=20
=3D=3D=3D=3D

Thanks,
Wen


-----Original Message-----
From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of Th=
e IESG
Sent: Thursday, January 02, 2014 10:14 AM
To: IETF-Announce
Cc: mpls@ietf.org
Subject: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in =
UDP) to Proposed Standard


The IESG has received a request from the Multiprotocol Label Switching WG
(mpls) to consider the following document:
- 'Encapsulating MPLS in UDP'
   <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final=
 comments on this action. Please send substantive comments to the ietf@ietf=
.org mailing lists by 2014-01-16. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract

    This document specifies an IP-based encapsulation for MPLS, called
    MPLS-in-UDP (User Datagram Protocol).


The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-mpls-in-udp/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-mpls-in-udp/ballot/


The following IPR Declarations may be related to this I-D:

    http://datatracker.ietf.org/ipr/1941/
    http://datatracker.ietf.org/ipr/2198/

From lear@cisco.com  Mon Jan  6 22:02:46 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88BF1ADFA9 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 22:02:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-P81fpyjwV1 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 22:02:45 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8471ADFA2 for <ietf@ietf.org>; Mon,  6 Jan 2014 22:02:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1859; q=dns/txt; s=iport; t=1389074556; x=1390284156; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=whY47d0DTrNHkhfsjB3EdBWvXzklhixTF6+m9HvPluE=; b=fO6hpCXymPgVD2qG+d+nrfADct6EcnH7LaBhjVnnVO/Gx55SWVc64LVO /74jDF9tWnirTnNJ8HHSArmev6/w4P5OoBT58SzyTgynQ+NENgai2nbg1 KTe7lByO6ntWxUrzhksA74kW8ywDODhJTDtUaineZt5YNT+F+H49wGHHn U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhIFAC6Yy1KQ/khR/2dsb2JhbABYgwuEC7NdgwiBDBZ0giUBAQEEI1YQCxgCAgUhAgIPAkYGAQwBBwEBEIdwqVuaHxeBKY1YB4JvgUgBA5NxQoNkkhWDLjs
X-IronPort-AV: E=Sophos;i="4.95,617,1384300800";  d="scan'208";a="2599887"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 07 Jan 2014 06:02:35 +0000
Received: from ams3-vpn-dhcp4971.cisco.com (ams3-vpn-dhcp4971.cisco.com [10.61.83.106]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0762YO9029821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 06:02:35 GMT
Message-ID: <52CB987A.20300@cisco.com>
Date: Tue, 07 Jan 2014 07:02:34 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, John Curran <jcurran@istaff.org>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie>
In-Reply-To: <52CB31F4.3090703@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 06:02:47 -0000

Hi,


On 1/6/14 11:45 PM, Stephen Farrell wrote:
>
> On 01/06/2014 08:51 PM, John Curran wrote:
>> What happens when the IETF makes a decision that particular "public policy" requirements 
>> are _to be considered_ (perpass), or specifically _not to be considered_ (RFC 2804) in protocol
>> development? 
> I think that's a mis-characterisation. IMO both of those are cases
> where there are sound technical reasons for the IETF to do, or not
> do, work. Yes, those have impacts, but the public policy angle (if
> that's the right term) is a side-effect and is not the reason for
> the decision.
>

Why do we state that confidentiality is important to pursue in our
protocols?  That is a political decision made by the community.  We then
layer on top of that decision technical requirements.  IMHO it's a very
important and good political decision.  We struggle with such decisions
all the time.  That there is a single root is both a technical AND a
political decision.  ICANN wouldn't be quite the political focal point
if there were a reasonable technical approach that scaled to the size of
the Internet that allowed for multiple roots.  As a community we know
this and have accepted it.

That pervasive surveillance can be used for good or bad reduces the
political element in as much as we're not saying any particular use is
good or bad.  That as a matter of IETF policy we may view it on the
whole as a bad thing is itself a political decision because it is
fundamentally tied to confidentiality and privacy (which is even more a
political area than confidentiality).

Nothing is wrong with making political decisions from time to time, when
it's important to do so, in order to see to a growing Internet that
provides benefit to the broader society.

Eliot
ps: I'll have more to say about perpass later today.

From dhc@dcrocker.net  Mon Jan  6 22:22:52 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A726C1AE443 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 22:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXTvqgutakeL for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 22:22:50 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D2DD41AE442 for <ietf@ietf.org>; Mon,  6 Jan 2014 22:22:50 -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 s076Mcdd006601 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 6 Jan 2014 22:22:42 -0800
Message-ID: <52CB9CCF.3070001@dcrocker.net>
Date: Mon, 06 Jan 2014 22:21:03 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com>
In-Reply-To: <52CB987A.20300@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 06 Jan 2014 22:22:42 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 07 Jan 2014 06:22:52 -0000

On 1/6/2014 10:02 PM, Eliot Lear wrote:
> Why do we state that confidentiality is important to pursue in our
> protocols?  That is a political decision made by the community.  We then
> layer on top of that decision technical requirements.  IMHO it's a very
> important and good political decision.  We struggle with such decisions
> all the time.  That there is a single root is both a technical AND a
> political decision.


Almost any group decision can legitimately be characterized as 
"political".  The decision will favor some and work to the detriment of 
others.  Hence the decision has a component that can be classed as 
exercising "power".

But the reference to politics is distinctly unhelpful for the IETF. 
Whatever the knowledge and experience of our participants individually, 
as a group we lack meaningful, coherent language or practice with it.

What we do have is experience being guided by design criteria stated in 
terms of engineering politics, not social politics.  We tends towards 
greater efficiency, robustness, etc.  This include permitting use of 
various security-related mechanisms for authentication, confidentiality, 
etc.  Political language might cast that as saying that the IETF "favors 
protection of participant data".

But really we are simply taking directives from those who consume our 
work and we are trying to design solutions that satisfy the directives.

There is a community desire to create better participant protections 
from pervasive monitoring.  To be honest, there is also some community 
desire to /permit/ pervasive monitoring.  We choose to listen to our 
"customers" -- that is, those who buy and use what we produce -- rather 
than third-party actors who might favor ensuring that pervasive 
monitoring be made easy.

That choice can be classed as political, but really, we're just 
listening to our market...

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From lear@cisco.com  Mon Jan  6 23:00:55 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8A071ADFB9 for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 23:00:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCa728h5qJrb for <ietf@ietfa.amsl.com>; Mon,  6 Jan 2014 23:00:54 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 32B081ADFB6 for <ietf@ietf.org>; Mon,  6 Jan 2014 23:00:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3178; q=dns/txt; s=iport; t=1389078046; x=1390287646; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=k6ct05kLHpuqHB32a/aHzg9SU6syMKVIUtZ0/srUdDk=; b=FNPsNpH1VcJLcae/KSpNptV/pALycyCrLnRtz/xDjMbQLeSmT2vTNHUy OU4suy9T3KQ/gOuPlaiseUIm2TjCLjW5xYOxovK/l7Nizp8nJSfCT5gLi 5nNxGiVJnr34MCucz1I3/iNrELeaneoh6yXRjCEixGjeQFIR+Zjnyi7GR Q=;
X-IronPort-AV: E=Sophos;i="4.95,617,1384300800";  d="scan'208";a="2602616"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 07 Jan 2014 07:00:45 +0000
Received: from ams3-vpn-dhcp4971.cisco.com (ams3-vpn-dhcp4971.cisco.com [10.61.83.106]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0770idA006989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 07:00:44 GMT
Message-ID: <52CBA61C.5090803@cisco.com>
Date: Tue, 07 Jan 2014 08:00:44 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, "Stewart Bryant (stbryant)" <stbryant@cisco.com>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <52C8304E.3080802@cs.tcd.ie>
In-Reply-To: <52C8304E.3080802@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 07:00:56 -0000

Stephen,

Speaking only for myself, of course, with two caveats I support the
publication of this draft.  The first is that I would prefer still that
it be informational.  There just isn't sufficient elaboration in this
work to support BCP, nor could we get that elaboration if we want this
draft to go out soon.  I also propose a one word change below.

On 1/4/14 5:01 PM, Stephen Farrell wrote:
>
> On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
>> I have been wondering whether a simple update to "A Guide to Writing
>> A Security Considerations Section" is all that is needed to address
>> the problem in hand?
> After a bit of offlist mail with Stewart, it turns out I had
> misinterpreted the above.
>
> I now believe (haven't quite confirmed, but its a fine idea
> anyway so worth raising here) that what Stewart meant was
> not to open up 3552 and add this text, (which'd take years) but
> rather to make the RFC resulting from this draft be just another
> part of BCP72 (aka RFC 3552).
>
> (In case folks don't know, BCPs can be made up of multiple RFCs,
> e.g. BCP 10 [1] is like that.)
>
> I think that's quite an interesting idea, and would probably only
> require adding a sentence or two to relate this text to that in 3552
> (which is currently all of BCP72). I'd certainly have no problem
> were that the outcome.
>
> I guess that just might help folks with concerns that as a new BCP
> this might be over zealously applied.
>
> But I'm not sure - would that in fact help anyone with such concerns?
>

There is an impedance mismatch between RFC-3552, which contains
substantially more specific guidance â€“ with examples â€“ on how to deal
with security considerations after a long and trying period of
establishing that procedure, and the new requirements we see in this
document, which are of a very general nature, and where the threat is
not yet well understood.

As Stewart wrote, -03 is considerably better than previous versions. 
You've laid out a test in -03, which I believe is the key to the draft:

>    Those developing IETF specifications need to be able to describe how
>    they have considered pervasive monitoring, and, if the attack is
>    relevant to the work to be published, be able to justify related
>    design decisions.  This does not mean a new "pervasive monitoring
>    considerations" section is needed in IETF documentation.  It means
>    that, if asked, there needs to be a good answer to the question "is
>    pervasive monitoring relevant to this work and if so how has it been
>    addressed?"

The first sentence is perfectly clear.  The 2nd sentence is perfectly
clear.  I would prefer that the question in the 3rd sentence read "how
has this been considered?"  This is consistent with the 1st sentence
with regard to justifications, and also gives us time to more properly
evaluate the threat model.  I hope the IAB and W3C workshop will further
advance our understanding so that more guidance is available.

If this change is made, then the BCP is what I would class "good
enough", even though my preference would be for Informational.

Eliot


From abdussalambaryun@gmail.com  Tue Jan  7 01:51:51 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F311ADF22 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 01:51:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvxNDSLOG2eY for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 01:51:50 -0800 (PST)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 917821AD8EC for <ietf@ietf.org>; Tue,  7 Jan 2014 01:51:50 -0800 (PST)
Received: by mail-pd0-f181.google.com with SMTP id p10so160012pdj.12 for <ietf@ietf.org>; Tue, 07 Jan 2014 01:51:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4fwScPAHEjNuZikaXZ8I5ioPS/uS0fWqEaS4jGCQfcU=; b=E8UpTFHWI8cy49Q3ZvW/FkWScd8ZxptPa1Jqh1EKDU/1pVlx1Gjg0tZ3pzkfWPIgLu nb+RmwReDU/ImMXbGeVNhMtVZ1quDuJRUgqnUaKdZaHxJabBMm8NCcpjWl5VLbQlkbHT LXeC9jzc15fXO6wTAObegYGtGBYAUXyFSndUSiqGFM9qzmuUiHU3fk+D/utewZqAmChH 3wy4UpzaKgttOkAzbRUwIxq22caVpjkr2KwDW/303Te8QfX8nfwGF+WMI++ri5MtKBTz GvFkjNQe7ClU9t/nY9nfLxuCvxD9nYJAXzMOHuF11ihTI5Cl9qKsvi14Ux2oLVP9FD0j njTA==
MIME-Version: 1.0
X-Received: by 10.66.154.75 with SMTP id vm11mr4169325pab.124.1389088301726; Tue, 07 Jan 2014 01:51:41 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Tue, 7 Jan 2014 01:51:41 -0800 (PST)
In-Reply-To: <52CB9CCF.3070001@dcrocker.net>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <52CB9CCF.3070001@dcrocker.net>
Date: Tue, 7 Jan 2014 10:51:41 +0100
Message-ID: <CADnDZ8-GcBOAszCFHzD_iJN3Jgw1NbQ_731_v3xkT=zNAVz57g@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 09:51:51 -0000

On 1/7/14, Dave Crocker <dhc@dcrocker.net> wrote:

> We choose to listen to our
> "customers" -- that is, those who buy and use what we produce -- rather
> than third-party actors who might favor ensuring that pervasive
> monitoring be made easy.

Who are the IETF customers? can be: a majority of diverse individual
users of the Internet, a minority of large organisations, and a
majority of small/medium organisations (all have different purposes,
not ignoring possible attackers).

>
> That choice can be classed as political, but really, we're just
> listening to our market...

What is/are the IETF market(s), or should IETF be getting fees from its markets?
Each world region has its own answers.

Political decisions is not the problem, it happens as output of any
organisation, the problem is that IETF is not diversified enough !!!

AB

From stephen.farrell@cs.tcd.ie  Tue Jan  7 04:45:18 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AAE51AE005 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 04:45:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8QCPOf9r-Rp for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 04:45:15 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 067881ADBD4 for <ietf@ietf.org>; Tue,  7 Jan 2014 04:45:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1E963BE51; Tue,  7 Jan 2014 12:45:05 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KUujonALgyQ; Tue,  7 Jan 2014 12:45:03 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.52.213]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 74E3EBE50; Tue,  7 Jan 2014 12:45:03 +0000 (GMT)
Message-ID: <52CBF6CF.6020708@cs.tcd.ie>
Date: Tue, 07 Jan 2014 12:45:03 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>,  "Stewart Bryant (stbryant)" <stbryant@cisco.com>, Melinda Shore <melinda.shore@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com> <52C8304E.3080802@cs.tcd.ie> <52CBA61C.5090803@cisco.com>
In-Reply-To: <52CBA61C.5090803@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 12:45:18 -0000

Hi Eliot,

Great that -03 works better for you too. I'd have no problem
with your additional change. (I'll let Jari tell me what he
wants wrt that when the LC's done, but have noted it in my
working copy.)

S.

On 01/07/2014 07:00 AM, Eliot Lear wrote:
> Stephen,
> 
> Speaking only for myself, of course, with two caveats I support the
> publication of this draft.  The first is that I would prefer still that
> it be informational.  There just isn't sufficient elaboration in this
> work to support BCP, nor could we get that elaboration if we want this
> draft to go out soon.  I also propose a one word change below.
> 
> On 1/4/14 5:01 PM, Stephen Farrell wrote:
>>
>> On 01/03/2014 08:36 PM, Stewart Bryant (stbryant) wrote:
>>> I have been wondering whether a simple update to "A Guide to Writing
>>> A Security Considerations Section" is all that is needed to address
>>> the problem in hand?
>> After a bit of offlist mail with Stewart, it turns out I had
>> misinterpreted the above.
>>
>> I now believe (haven't quite confirmed, but its a fine idea
>> anyway so worth raising here) that what Stewart meant was
>> not to open up 3552 and add this text, (which'd take years) but
>> rather to make the RFC resulting from this draft be just another
>> part of BCP72 (aka RFC 3552).
>>
>> (In case folks don't know, BCPs can be made up of multiple RFCs,
>> e.g. BCP 10 [1] is like that.)
>>
>> I think that's quite an interesting idea, and would probably only
>> require adding a sentence or two to relate this text to that in 3552
>> (which is currently all of BCP72). I'd certainly have no problem
>> were that the outcome.
>>
>> I guess that just might help folks with concerns that as a new BCP
>> this might be over zealously applied.
>>
>> But I'm not sure - would that in fact help anyone with such concerns?
>>
> 
> There is an impedance mismatch between RFC-3552, which contains
> substantially more specific guidance â€“ with examples â€“ on how to deal
> with security considerations after a long and trying period of
> establishing that procedure, and the new requirements we see in this
> document, which are of a very general nature, and where the threat is
> not yet well understood.
> 
> As Stewart wrote, -03 is considerably better than previous versions. 
> You've laid out a test in -03, which I believe is the key to the draft:
> 
>>    Those developing IETF specifications need to be able to describe how
>>    they have considered pervasive monitoring, and, if the attack is
>>    relevant to the work to be published, be able to justify related
>>    design decisions.  This does not mean a new "pervasive monitoring
>>    considerations" section is needed in IETF documentation.  It means
>>    that, if asked, there needs to be a good answer to the question "is
>>    pervasive monitoring relevant to this work and if so how has it been
>>    addressed?"
> 
> The first sentence is perfectly clear.  The 2nd sentence is perfectly
> clear.  I would prefer that the question in the 3rd sentence read "how
> has this been considered?"  This is consistent with the 1st sentence
> with regard to justifications, and also gives us time to more properly
> evaluate the threat model.  I hope the IAB and W3C workshop will further
> advance our understanding so that more guidance is available.
> 
> If this change is made, then the BCP is what I would class "good
> enough", even though my preference would be for Informational.
> 
> Eliot
> 
> 
> 

From hallam@gmail.com  Tue Jan  7 05:18:30 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F101AE042 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 05:18:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2RLMZmFdC8zr for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 05:18:27 -0800 (PST)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6530A1AE00F for <ietf@ietf.org>; Tue,  7 Jan 2014 05:18:27 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id b8so96183lan.27 for <ietf@ietf.org>; Tue, 07 Jan 2014 05:18:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=4pM55U5f2SuN3jW9HLpBRGbTx5swIKXWIgku8YulkM8=; b=O/DR5/UmZTuYsnM5Uszumj1N886DlWtPgMWjxBlxsNgoF09wGxI2ARDC0vm1pvr5B+ qaQETWagKNylk5iKxzGHrR76nrVzBLLYECjFymJ+n00w3rOG9kQh7eeDOxc/SLXYvC+C tPZxkGH8P8haBAJlhtcd62fPxky96AQDb4xf6m8X0QBM9WjhPuBXFvXEIHtJCB1ic8gQ KckOWXQGcxFmNU5Aap41klCMFZxMm+yedr/QP4GbF4SgpUU2RxaHJQR7lGSBtBf5L4/G Zq6mf/UyBu4TAZm0Cdhy+rN46qZ9fgnXpgdPGC+jYRGDEJiJu4sJFFUa61tElLL5ep89 PLYQ==
MIME-Version: 1.0
X-Received: by 10.112.201.197 with SMTP id kc5mr2541610lbc.64.1389100697965; Tue, 07 Jan 2014 05:18:17 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Tue, 7 Jan 2014 05:18:17 -0800 (PST)
In-Reply-To: <52CB987A.20300@cisco.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com>
Date: Tue, 7 Jan 2014 08:18:17 -0500
Message-ID: <CAMm+LwjtqnW_Gt0y9Qb6z6dz7T0cb7bJRN73=RB6VSp+i=cQZQ@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary=001a11c2662ea8daa504ef613529
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 13:18:30 -0000

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

On Tue, Jan 7, 2014 at 1:02 AM, Eliot Lear <lear@cisco.com> wrote:

> Hi,
>
>
> On 1/6/14 11:45 PM, Stephen Farrell wrote:
> >
> > On 01/06/2014 08:51 PM, John Curran wrote:
> >> What happens when the IETF makes a decision that particular "public
> policy" requirements
> >> are _to be considered_ (perpass), or specifically _not to be
> considered_ (RFC 2804) in protocol
> >> development?
> > I think that's a mis-characterisation. IMO both of those are cases
> > where there are sound technical reasons for the IETF to do, or not
> > do, work. Yes, those have impacts, but the public policy angle (if
> > that's the right term) is a side-effect and is not the reason for
> > the decision.
> >
>
> Why do we state that confidentiality is important to pursue in our
> protocols?  That is a political decision made by the community.  We then
> layer on top of that decision technical requirements.  IMHO it's a very
> important and good political decision.  We struggle with such decisions
> all the time.  That there is a single root is both a technical AND a
> political decision.  ICANN wouldn't be quite the political focal point
> if there were a reasonable technical approach that scaled to the size of
> the Internet that allowed for multiple roots.  As a community we know
> this and have accepted it.
>

It isn't the single technical root that creates the political focal point,
that would be quite easy to fix.

It is the uniform namespace that creates the political focal point, the
fact that a label has to resolve to the same resource in every part of the
net. That issue is then compounded by the entirely unnecessary and
unfortunate decision to introduce hierarchy at the root level. The problems
would have been much less if the only TLD was .com. That is, no CC TLDs, no
.NET, no .org, everything in one big bucket with the only hierarchy being
at the network level.




> That pervasive surveillance can be used for good or bad reduces the
> political element in as much as we're not saying any particular use is
> good or bad.  That as a matter of IETF policy we may view it on the
> whole as a bad thing is itself a political decision because it is
> fundamentally tied to confidentiality and privacy (which is even more a
> political area than confidentiality).
>

The problem isn't 'politics'. The problem is the degree of specificity in
the decisions made.

The IETF is not deciding whether there will be passive surveillance in one
country but not another. All the IETF can do is to provide tools that
empower individuals to protect their own privacy and to empower providers
to protect the privacy of customers.

That is very different from the decision as to whether Muggins should have
their registrar affiliation withdrawn because Boggins claims that they are
a dirty filthy spammer.


There is a political element to all the work but the decisions to do with
IP address and BGP AS numbers and DNS numbers are very different in
character from the type of decisions IETF makes.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jan 7, 2014 at 1:02 AM, Eliot Lear <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<div><div class=3D"h5"><br>
<br>
On 1/6/14 11:45 PM, Stephen Farrell wrote:<br>
&gt;<br>
&gt; On 01/06/2014 08:51 PM, John Curran wrote:<br>
&gt;&gt; What happens when the IETF makes a decision that particular &quot;=
public policy&quot; requirements<br>
&gt;&gt; are _to be considered_ (perpass), or specifically _not to be consi=
dered_ (RFC 2804) in protocol<br>
&gt;&gt; development?<br>
&gt; I think that&#39;s a mis-characterisation. IMO both of those are cases=
<br>
&gt; where there are sound technical reasons for the IETF to do, or not<br>
&gt; do, work. Yes, those have impacts, but the public policy angle (if<br>
&gt; that&#39;s the right term) is a side-effect and is not the reason for<=
br>
&gt; the decision.<br>
&gt;<br>
<br>
</div></div>Why do we state that confidentiality is important to pursue in =
our<br>
protocols? =A0That is a political decision made by the community. =A0We the=
n<br>
layer on top of that decision technical requirements. =A0IMHO it&#39;s a ve=
ry<br>
important and good political decision. =A0We struggle with such decisions<b=
r>
all the time. =A0That there is a single root is both a technical AND a<br>
political decision. =A0ICANN wouldn&#39;t be quite the political focal poin=
t<br>
if there were a reasonable technical approach that scaled to the size of<br=
>
the Internet that allowed for multiple roots. =A0As a community we know<br>
this and have accepted it.<br></blockquote><div><br></div><div>It isn&#39;t=
 the single technical root that creates the political focal point, that wou=
ld be quite easy to fix.=A0</div><div><br></div><div>It is the uniform name=
space that creates the political focal point, the fact that a label has to =
resolve to the same resource in every part of the net. That issue is then c=
ompounded by the entirely unnecessary and unfortunate decision to introduce=
 hierarchy at the root level. The problems would have been much less if the=
 only TLD was .com. That is, no CC TLDs, no .NET, no .org, everything in on=
e big bucket with the only hierarchy being at the network level.</div>
<div><br></div><div><br></div><div>=A0<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
That pervasive surveillance can be used for good or bad reduces the<br>
political element in as much as we&#39;re not saying any particular use is<=
br>
good or bad. =A0That as a matter of IETF policy we may view it on the<br>
whole as a bad thing is itself a political decision because it is<br>
fundamentally tied to confidentiality and privacy (which is even more a<br>
political area than confidentiality).<br></blockquote><div><br></div><div>T=
he problem isn&#39;t &#39;politics&#39;. The problem is the degree of speci=
ficity in the decisions made.</div><div><br></div><div>The IETF is not deci=
ding whether there will be passive surveillance in one country but not anot=
her. All the IETF can do is to provide tools that empower individuals to pr=
otect their own privacy and to empower providers to protect the privacy of =
customers.</div>
<div><br></div><div>That is very different from the decision as to whether =
Muggins should have their registrar affiliation withdrawn because Boggins c=
laims that they are a dirty filthy spammer.</div><div><br></div><div><br>
</div><div>There is a political element to all the work but the decisions t=
o do with IP address and BGP AS numbers and DNS numbers are very different =
in character from the type of decisions IETF makes.</div><div><br></div>
<div>=A0</div></div>-- <br>Website: <a href=3D"http://hallambaker.com/">htt=
p://hallambaker.com/</a><br>
</div></div>

--001a11c2662ea8daa504ef613529--

From stephen.farrell@cs.tcd.ie  Tue Jan  7 05:28:27 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 482561ADF38 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 05:28:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DxI5OYezKZg for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 05:28:24 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7131ADBD4 for <ietf@ietf.org>; Tue,  7 Jan 2014 05:28:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B9EE3BE51; Tue,  7 Jan 2014 13:28:14 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4iQbT-4HhzJ; Tue,  7 Jan 2014 13:28:12 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.52.213]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 41E86BE50; Tue,  7 Jan 2014 13:28:12 +0000 (GMT)
Message-ID: <52CC00EA.70404@cs.tcd.ie>
Date: Tue, 07 Jan 2014 13:28:10 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephan Wenger <stewe@stewe.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
References: <CEF0A2FD.3ED34%stewe@stewe.org>
In-Reply-To: <CEF0A2FD.3ED34%stewe@stewe.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 13:28:27 -0000

Hi Stephan,

Some non-trivial points below, but actually I think your posting
is a great example of why the IETF needs this draft published.
If we do not get that done, then anyone proposing to consider or
mitigate pervasive monitoring is liable to have to re-litigate
this entire debate in whatever WG is involved, because absent an
IETF consensus position on this, you and those who agree with you
will, holding the position you do, feel bound to question such
work, which could be quite disruptive overall. (I'm not saying
you'd be disruptive btw, the ultimate fault if any lies with the
signals intelligence agencies IMO.)

On 01/07/2014 03:41 AM, Stephan Wenger wrote:
> Hi all,
> As the time window for the last call comes to a close shortly, I want to
> chime in.  This is going to be my first and last message on this
> subject--I will not have time to argue my viewpoints due to other, for me
> more important, commitments.
> 
> I¹m against publishing this draft in any form.  I¹m convinced, based on
> the mailing list discussion up to now, and on my own reading, that
> publishing this draft has more risks than benefits for myself and for the
> IETF.  Here are a few condensed points.
> 
> 1. My personal risk/benefit equation:
> The main disconnect I see in the draft is its implicit assumption that an
> ³attack² is a Bad Thing.  

Actually no that terminology (more fully explained in RFC 4949) is
standard in computer security/risk analysis in general and has been
since before my time, so for 40 years or more. While you may not be
a "security guy" that terminology is sufficiently widespread that
I'm very surprised that you don't already know its meaning. What
you're asking would be similar to asking to re-interpret the term
octet and should be similarly regarded IMO.

> It¹s an implicit assumption, because after the
> very  clear definition for ³attack² provided in section 1, the draft
> immediately jumps to the subject of the need for the IETF to work towards
> mitigation, which implies that there is something (namely the ³attack")
> that needs to be mitigated.  That is an immensely political statement that
> has not been addressed in the draft.  There are countless examples where
> ³attacks² (as defined in the draft) have saved lives and generally have
> done good to the world.  

There are countless examples of when falling over saved lives too.
That doesn't mean falling over is a good plan.

> I¹m personally convinced that, on balance, the
> world would be a much worse place without ³attacks² than with.  

I see. So you're all for hacking into Belagcom then? I'm sure they'll
be a little sad to hear that. Esp. if the next attacker is not a
government agency.

> Without
> ³attacks², we would probably not have safe mass transportation, terrorist
> of different colour would run wild, organized crime would be widespread,
> and so on.  I DO WANT my communication to be ³attackable² (albeit not
> necessarily easily attackable), 

So you would like security mechanisms with government-backdoors
but that are hard for anyone else? I want a pony:-)

But seriously, we don't know of a way to do that. Please see
RFCs 1984 and 2804 for some IETF history on that.

> based on the assumption that, generally
> speaking, me, being a moderately good guy myself, will probably not be
> subject to too many attacks by the good guys because my views are
> generally better aligned with the good guys than with the bad guys.  Even
> if the good guys were spying on me, they could hardly use that information
> in a way that would hurt me.  

That's optimistic.

> OTOH, I want that the communication of the
> bad guys, be they terrorists, organized crime or whatever, to be broken
> into, and their schemes to be disrupted by law enforcement, before they
> have a chance to attack (without quotes) me in the very real sense of
> flying bullets and blown up planes.  For that, I¹m willing to accept that
> the bad guys can break my communication as well.  This logic obviously
> works best, today, when living in a western democracy (like I do),
> generally trusting the government (as I do), and having the resources and
> the will to fight (like I think I have) if I am ³attacked² by the
> government or anyone else for illegitimate reasons (Note that I didn¹t
> write ³illegal²). 
>
> Note that I have labeled this section ³My personal risk/benefit equation².
>  I can fully understand if others set other priorities.  However, I
> participate in the IETF as well, and my viewpoint should (and. I¹m quite
> confident, will) be taken into account as those of others, despite it
> being perhaps somewhat politically incorrect in the current climate.

That's fair. I'd guess you're fairly clearly in the rough in that
respect. But, taking contrarian views into account here (as should
be done) does not mean making contrarians happy. In this case, as
soon as there are a significant number of people who do not share
your views (and there are) and who would like not to be so vulnerable
to pervasive monitoring, then I think that viewpoint wins, in terms
of what the IETF should be considering and the technical proposals
that we develop since only then is it possible to satisfy both sets
of opinions on this topic. (Folks such as yourself can turn things
off, but the other set can only turn things on after they've been
defined and implemented.)

And in labelling your own view as currently "politically incorrect"
you are accepting that most participants do not share your view,
which implicitly therefore also accepts that the IETF should be
working to develop mitigations to pervasive monitoring as explained
above. The logical position for a self-recognised contrarian such
as yourself is therefore in fact to support the draft!

> 
> 2. IETF¹s risk/benefit equation
> 2.a declaring consensus on something like this.  The assertion in the
> document that it represents IETF consensus (based on the plenary) has
> already been competently challenged.  No need to repeat.  

I'm sorry but that's wrong. First, nobody asserted that the
plenary in Vancouver means that this draft already has consensus.
Second, the plenary in Vancouver did happen, so claiming that it
can be ignored is not credible.

>From my POV, I consider the Vancouver plenary in the same way as
I'd consider a huge set (hundreds) of +1 mail messages - there's
no thoughtful statement that the draft captures the hums correctly,
but the draft IMO fairly obviously does that at least imperfectly,
so those hums can be considered to be +1 messages. And in saying
that I do consider a +1 mail as only being a very weak contribution
to establishing rough consensus. I'm not sure how or if Jari will
factor the hums in Vancouver into his evaluation of this LC, but
pretending they never happened would be very wrong.

> But let me add
> that in this case we have an even stronger problem with the ³silent
> majority² than usual.  I could imagine that a large percentage of the IETF
> participants, especially those living in areas less fortunate than the
> western democracies, cannot voice their opinion safely and freely, even if
> they wished.  

I've no idea what you mean. If you're saying that people in "less
fortunate" areas are less likely to oppose this draft then I think
that's silly.

> As stated above, I believe this is an immensely political
> draft (for the reason that it makes implicit assumptions), and some folks
> have to be more careful than others commenting.  I carefully tried to stay
> away speculating what their view may be, and I invite others to do the
> same--this is not only a political but also a cultural question.

In fact, you are speculating above.

> 2.b there is the further risk that even more of our standards get silently
> disregarded in large parts of the world, potentially leading to less
> interoperability and an even more pronounced split between a ³western
> democracy Internet² and ³rest of the world Internet".  Already, there are
> countries where any form of encryption of media data and emails is
> forbidden, and one goes to jail (or worse) if one does.  

I hear that from time to time. Never accompanied with references though.
And RFC 1984 is our position on that, this draft is not needed.

> I don¹t say that
> this is a good thing, but fighting the situation is once more an immensely
> political process, and I don¹t think the IETF is particularly good at
> that, nor does it need to be.
> 2.c for my own work in the IETF, I do not want to see yet another opening
> that potentially allows the security lobby to require me to load up my own
> drafts, which have nothing to do with security, with additional security
> oriented language.  I¹m not a security guy.  I don¹t care about pervasive
> monitoring; I view it generally as beneficial (see above).  Why should I
> have answers ready when competent others ask me questions about it?  Why
> should I see my documents delayed for this stuff?  They may well be very
> good documents in what they are describing.  We have enough boilerplate
> and process already, thank you.

The draft does not require any new boilerplate or process. 2c seems
to be back to you personal view.

> 2.d risk of misrepresentation by the media.  The language of the draft is
> flashy enough to invite misrepresentation by the media.  It cannot be in
> the interest of the IETF to see one of its future core docs (process BCPs
> are just that, right?) be misinterpreted by journalists, many of which
> probably having spent even less time with this doc than myself.

I just disagree about flashy. Its fairly boring now:-)

Readers of RFCs can always mis-represent them. Your claim amounts
to a claim that we should never say anything I think. And you don't
even quote a single sentence that you say could be misrepresented
or that is "flashy." That's not really credible as a criticism.

> 2.e as for the benefits, where are they?  The IETF would be viewed in
> certain progressive circles in the western democracies as sensitive
> people, especially in year 1 past Snowden.  (I¹m not so sure how we would
> look in year 1 after the next large scale terrorist attack.)  The security
> guys would have more work.  Nothing against good biz-dev, but does it
> really have to be an IETF BCP? :-)  What else?  Nothing comes to my mind.

See the top-post for one benefit.

Those who do think that attacks are bad things will see benefits
in terms of being less vulnerable.

S.

> 
> Thanks for reading.
> 
> Best regards,
> Stephan 
> 
> 
> On 12/3/13, 20:45, "Jari Arkko" <jari.arkko@piuha.net> wrote:
> 
>> I wanted to draw your attention on this last call:
>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Pervasive Monitoring is an Attack'
>>>  <draft-farrell-perpass-attack-02.txt> as Best Current Practice
>>>
>>> http://datatracker.ietf.org/doc/draft-farrell-perpass-attack/
>>
>>
>> It is a short read and important, so please comment. The last call ends
>> in four weeks and covers holiday time, but we'll deal with this document
>> on the January 9th telechat in the IESG, so in practice there should be
>> enough time to comment.
>>
>> I would like to see this document as a high-level policy we have on
>> dealing with this particular type of vulnerabilities in the Internet. A
>> little bit like RFC 3365 "Danvers Doctrine" was on weak vs. strong
>> security. Please remember that the details and tradeoffs for specific
>> solutions are for our WGs to consider and not spelled out here. The draft
>> does say "where possible" - I do not want to give the impression that our
>> technology can either fully prevent all vulnerabilities or do it in all
>> situations. There are obviously aspects that do not relate to
>> communications security (like access to content by your peer) and there
>> are many practical considerations that may not make it possible to
>> provide additional privacy protection even when we are talking about the
>> communications part. But I do believe we need to consider these
>> vulnerabilities and do our best.
>>
>> Jari
>>
> 
> 
> 

From melinda.shore@gmail.com  Tue Jan  7 06:14:13 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FA921AE016 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBZlH2Uzv30c for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:14:11 -0800 (PST)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 33F091ADF66 for <ietf@ietf.org>; Tue,  7 Jan 2014 06:14:11 -0800 (PST)
Received: by mail-pb0-f52.google.com with SMTP id uo5so169217pbc.39 for <ietf@ietf.org>; Tue, 07 Jan 2014 06:14:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=rbUtl3HHndbBtHUQEOkwe9tG2jHPXmzjb17qahZGlvc=; b=hooi8yiCVXmM4+yCHvgXDU130bjcSUWtkvskEkjsCQFEIy8RzOf08ka3LJgdtS2p/R dy1P5UaGaNTuvrprwljo6w+ZbzjTXZSNPnk4kOG5ia8IpmQL5sp+jQ5oTLivk+zfkuWy XerZVoSDfmZ+CABjrN9F38TjVFb6HxnSvGuBKAdtAgz65BBpEvybJXNFsLfyvfGNkBxl dLh+knEawd/96CKo5/QbEZg1FWlc+LwhHlAQzPg+SGYf+Ck8VeyKqs5lDQPdcrtOiRXD hDU6rbk/kWgfJ4cMSRJoQ/VGNsdIMDlWVFI5+kJYAqEqWIHFkFhxdXJ1GUon1YlX9oFU ujLg==
X-Received: by 10.68.201.71 with SMTP id jy7mr43322164pbc.47.1389104042580; Tue, 07 Jan 2014 06:14:02 -0800 (PST)
Received: from spandex.local (63-140-83-106.nwc.dsl.dynamic.acsalaska.net. [63.140.83.106]) by mx.google.com with ESMTPSA id qf7sm178475784pac.14.2014.01.07.06.14.00 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Jan 2014 06:14:01 -0800 (PST)
Message-ID: <52CC0BA6.5090404@gmail.com>
Date: Tue, 07 Jan 2014 05:13: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/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
References: <CEF0A2FD.3ED34%stewe@stewe.org> <52CC00EA.70404@cs.tcd.ie>
In-Reply-To: <52CC00EA.70404@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 14:14:13 -0000

On 1/7/14 4:28 AM, Stephen Farrell wrote:
> Hi Stephan,
[ ... ]
>> I¹m personally convinced that, on balance, the
>> world would be a much worse place without ³attacks² than with.  
> 
> I see. So you're all for hacking into Belagcom then? I'm sure they'll
> be a little sad to hear that. Esp. if the next attacker is not a
> government agency.

I think that it's pretty clear to most of us that, whether or
not we think that government eavesdropping should be trivially
easy, that thinking that the ability for them to do so is not
the same thing that thinking that attacks from other malefactors
would be a good thing.  It'd be somewhat more compelling to argue
that enabling trivially easy eavesdropping by one party enables
it for another, which I also think is a more correct argument.
If I were Stephan I'd be reading what you wrote and thinking
"No, that's not what I think - Stephen's wrong" rather than
"Stephen has a point."

At a minimum it might be good to argue what's been actually
written rather than to impute all sorts of views to someone
and then argue against those.

At any rate I do think that we can probably discuss this without
people who disagree with you being characterized as naive,
enthusiasts of various sorts of attacks, etc.

At any rate I don't agree with much of what Stephan has written
but I do agree that there appears to be some risk that consensus
is likely to be asserted despite what seem to me to be some
significant disagreements over publication status.

Melinda


From ajs@anvilwalrusden.com  Tue Jan  7 06:44:25 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033BD1AD9B8 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z_nvzAB7fBOa for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:44:24 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E2A8E1AD8EC for <ietf@ietf.org>; Tue,  7 Jan 2014 06:44:23 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 981AE8A031 for <ietf@ietf.org>; Tue,  7 Jan 2014 14:44:14 +0000 (UTC)
Date: Tue, 7 Jan 2014 09:44:12 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Split the IANA functions?
Message-ID: <20140107144412.GB11068@mx1.yitter.info>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52CB987A.20300@cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 14:44:25 -0000

On Tue, Jan 07, 2014 at 07:02:34AM +0100, Eliot Lear wrote:
> That there is a single root is both a technical AND a
> political decision. 

I have to disagree with this.  The uniqueness of the root is not a
political decision.  It's a fact of mathematics.  DNS is a tree.
There's one root.

Now, one might argue that choosing this kind of name space was a
political decision.  I might buy that argument (I don't know).  There's
good reason to suppose that there was at least some organizational
principle behind the decision in favour of a hierarchical namespace.
There were technical constraints too, I think: I don't believe a fully
peer to peer system was practical in the network environment of the
1980s.  But if we wanted to call anything that had non-technical
elements in it "political", then the selection of the DNS
(hierarchical) name space was in that sense political.

This is not to say that the single root doesn't have additional
political implications.  But I will not concede that this is some
contingent fact of the DNS that could be otherwise.  The particular
root we have could be different.  That there is a single root could
not.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From stephen.farrell@cs.tcd.ie  Tue Jan  7 06:45:48 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8576E1ADBC9 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:45:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rQiJ-ViHNerx for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:45:47 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 253BA1AD8EC for <ietf@ietf.org>; Tue,  7 Jan 2014 06:45:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 0077BBE50; Tue,  7 Jan 2014 14:45:37 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hH-OzJpHqG03; Tue,  7 Jan 2014 14:45:33 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.52.213]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B06B1BE3F; Tue,  7 Jan 2014 14:45:31 +0000 (GMT)
Message-ID: <52CC130B.5030004@cs.tcd.ie>
Date: Tue, 07 Jan 2014 14:45:31 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
References: <CEF0A2FD.3ED34%stewe@stewe.org> <52CC00EA.70404@cs.tcd.ie> <52CC0BA6.5090404@gmail.com>
In-Reply-To: <52CC0BA6.5090404@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 14:45:48 -0000

On 01/07/2014 02:13 PM, Melinda Shore wrote:
> On 1/7/14 4:28 AM, Stephen Farrell wrote:
>> Hi Stephan,
> [ ... ]
>>> I¹m personally convinced that, on balance, the
>>> world would be a much worse place without ³attacks² than with.  
>>
>> I see. So you're all for hacking into Belagcom then? I'm sure they'll
>> be a little sad to hear that. Esp. if the next attacker is not a
>> government agency.
> 
> I think that it's pretty clear to most of us that, whether or
> not we think that government eavesdropping should be trivially
> easy, that thinking that the ability for them to do so is not
> the same thing that thinking that attacks from other malefactors
> would be a good thing.  It'd be somewhat more compelling to argue
> that enabling trivially easy eavesdropping by one party enables
> it for another, which I also think is a more correct argument.
> If I were Stephan I'd be reading what you wrote and thinking
> "No, that's not what I think - Stephen's wrong" rather than
> "Stephen has a point."
> 
> At a minimum it might be good to argue what's been actually
> written rather than to impute all sorts of views to someone
> and then argue against those.
> 
> At any rate I do think that we can probably discuss this without
> people who disagree with you being characterized as naive,
> enthusiasts of various sorts of attacks, etc.

Well you're probably right that the way I phrased the Belgacom
point above was a bit aggressive, (and sorry for that folks),
but it is valid - in that case an active hacking attack seems
to have been used to setup a later passive attack. And I do think
Stephan's mail was naive in at least that it seems to consider
that network elements can distinguish between good and bad guys.

> At any rate I don't agree with much of what Stephan has written
> but I do agree that there appears to be some risk that consensus
> is likely to be asserted despite what seem to me to be some
> significant disagreements over publication status.

Figuring that out is Jari's job, I'm just an interested author
here. (Albeit a quite energised author:-)

S.


> 
> Melinda
> 
> 
> 

From lear@cisco.com  Tue Jan  7 06:58:43 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4128F1AD935 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:58:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qh4ZgEriqiWp for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 06:58:42 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 20D301AD8CD for <ietf@ietf.org>; Tue,  7 Jan 2014 06:58:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=275; q=dns/txt; s=iport; t=1389106713; x=1390316313; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=fSwed78OeDVPuIBzMmI5zWIVMEt5TQ+lWvW9RiJJFnw=; b=E2aQV9kuyzym823ICFifLsT8XAofqsX2VsHLRYf1fEpHWl2JjD/bTfsc zq0yRgEs8AQvFbT/bhZqeKZAzFvuHIpVAJ4agqbPR7GDbDfleFBONa9LN BuehDbr/WilfAphZCw2OJ8h1i0lKTVq/7RpkdziccAona2nhg01odqQx9 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAE4VzFKQ/khL/2dsb2JhbABZgwuEC4lArSWBEBZ0giYBAQQjVRELDgwCBRYLAgIJAwIBAgErGgYBDAgBAYgAqhSaJheBKY1igm+BSAEDmBeSFYMuOw
X-IronPort-AV: E=Sophos;i="4.95,619,1384300800";  d="scan'208";a="3293588"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 07 Jan 2014 14:58:32 +0000
Received: from mctiny.local ([10.61.211.253]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s07EwWnf032155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 14:58:32 GMT
Message-ID: <52CC1618.1090605@cisco.com>
Date: Tue, 07 Jan 2014 15:58:32 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
In-Reply-To: <20140107144412.GB11068@mx1.yitter.info>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 14:58:43 -0000

Andrew,

It's clear that I wasn't clear.  Deciding on a tree structure has
political implications, be that DNS, RPKI, or other (and there are
other).  To ignore those implications would be unwise.  They are weighed
against technical considerations, as always.

Eliot

From d3e3e3@gmail.com  Tue Jan  7 07:19:27 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBC21ADEB1 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 07:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level: 
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56MRfPXays-4 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 07:19:26 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 427181ADBD7 for <ietf@ietf.org>; Tue,  7 Jan 2014 07:19:26 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id wn1so282253obc.19 for <ietf@ietf.org>; Tue, 07 Jan 2014 07:19:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=n+QWSwy6hCmuaUV4qlyd2xZVbMzFjaiFTGc6/QfPsgQ=; b=C0xbWluJ4UjdXyPwjn1a/j3q4+PfcEHLdigtlNtwVSYGjohQtrK7gQC8EO6DGzJSXc 7r+691atlOO/Aj39paaqMo7Ub5ljLIXKbgthmcFHhLjHD42QKrrNhlgqn3Yhsd16lCRA cUq7Nb9hsKJwzCkryQNaUD8UWYw/OWnxWt80bThGaZjWFxny82H1K2DlOVHeKRkQDmGC Hkzzw8GR5mi8okmXvTxQARdUr+YmK8/jHnEqyJWcgAx7uZlxMDy6GW/1QpcUVh9j19a7 iiGw6cJy/szgoXSnP6sggSNV9o3Ble6eKMUEzi5x8+u7eDbPrDoaKTeOG8I3Rlz5RluS WUGQ==
X-Received: by 10.60.136.132 with SMTP id qa4mr711529oeb.68.1389107957318; Tue, 07 Jan 2014 07:19:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Tue, 7 Jan 2014 07:18:56 -0800 (PST)
In-Reply-To: <24105.1388766859@erosen-linux>
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 7 Jan 2014 10:18:56 -0500
Message-ID: <CAF4+nEHDNC-aQCY6r1zceb=7hOW4JmfnMWDWZSEM6gJLTSDF9Q@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 15:19:27 -0000

On Fri, Jan 3, 2014 at 11:34 AM, Eric Rosen <erosen@cisco.com> wrote:
>
> Stewart> The -03 text is a significant improvement, but I still fear the
> Stewart> impact of single issue technical politics on the output of our
> Stewart> document stream.
>
> Let's face it, the draft is nothing but a political manifesto, and the IETF
> has no business even considering it.  It is also clear from this discussion
> that there is no consensus, even rough consensus, in favor.

Anyone who has been around in the IETF long enough has seen this
before. Rabid opposition to real consideration of strong security. I
have seen yelling at plenaries. I've heard people say how the IETF
will be destroyed or become irrelevant if we don't bow to the US
Government rules. Etc.

If you want to distort the word "political" to try to characterize
this, I don't care that much. This draft is completely in line with
the previous admirable IETF engineering positions on security.

> Note the tone taken by proponents of the draft.  ... one cannot determine from the draft what the actual impact on IETF process is ... claim the support of a "silent majority" ...

Note the tone taken by opponents of the draft. Gross distortions and
mischaracterization of the draft. I hope people reading the IETF
discussion list, if they care about this issue, will actually read the
draft and see what it actually says, which is pretty reasonable.

The intended effect on IETF process is clear enough to me from the
document, at least in version -03.

Determining consensus is an all-sources, kind of thing and the person
judging consensus is entirely within their rights to take into account
meeting, mailing list, personal discussions, etc. I am in the
consensus in supporting this draft and I an not being silent.

>
>...

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

From paf@frobbit.se  Tue Jan  7 08:03:43 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562A81ADFA6 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z_5XRsDhOIy4 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:03:42 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 235E91ADF72 for <ietf@ietf.org>; Tue,  7 Jan 2014 08:03:42 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::2087:3375:684d:61f8] (unknown [IPv6:2a02:80:3ffc:0:2087:3375:684d:61f8]) by mail.frobbit.se (Postfix) with ESMTPSA id 9303E206A0; Tue,  7 Jan 2014 17:03:31 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_B60BA311-0084-4FA8-AFEB-895E320336E1"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Split the IANA functions?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <52CC1618.1090605@cisco.com>
Date: Tue, 7 Jan 2014 17:03:30 +0100
Message-Id: <886B4045-4115-489E-8127-3F3B9A233119@frobbit.se>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 16:03:43 -0000

--Apple-Mail=_B60BA311-0084-4FA8-AFEB-895E320336E1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 7 jan 2014, at 15:58, Eliot Lear <lear@cisco.com> wrote:

> Andrew,
>=20
> It's clear that I wasn't clear.  Deciding on a tree structure has
> political implications, be that DNS, RPKI, or other (and there are
> other).  To ignore those implications would be unwise.  They are =
weighed
> against technical considerations, as always.
>=20
> Eliot

One have to go back to the basics for requirements of identifiers, and =
one of them has to do with uniqueness (others are persistence, human =
readability, lookup mechanisms, scale, stability, homogeneity, ability =
to do searches, inverse functions, and more...). Uniqueness can be local =
or global. And global uniqueness can in turn, if that is necessary, be =
done in an opportunistic way or a fool proof way. If one really need =
guaranteed global uniqueness and at the same time easy lookups (but not =
searches, inverse and other things) global distributed hierarchal =
allocation is a very efficient way of doing it.

What I think you say Eliot is that when one look at the requirements on =
whatever name space is designed, one have to take also political =
arguments into account. That I agree with.

But for some set of requirements, doing things in a different way than =
hierarchal delegated allocation is darn difficult. Instead one have to =
work around the political problems by (as you say) not ignoring them, =
but understanding the issues exist and design around them.

   Patrik


--Apple-Mail=_B60BA311-0084-4FA8-AFEB-895E320336E1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSzCVSrMabGguI180RAiXaAKCaJnJLHIV4EiDVkqu4AjGrwO7LOwCfZj86
p/NNxVIdTujRBAvpmjswm5c=
=qtkS
-----END PGP SIGNATURE-----

--Apple-Mail=_B60BA311-0084-4FA8-AFEB-895E320336E1--

From avri@ella.com  Tue Jan  7 07:27:44 2014
Return-Path: <avri@ella.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2ACA1ADF72 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 07:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUUZ0QJRuDdQ for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 07:27:42 -0800 (PST)
Received: from atl4mhob12.myregisteredsite.com (atl4mhob12.myregisteredsite.com [209.17.115.50]) by ietfa.amsl.com (Postfix) with ESMTP id C73251ADF6D for <ietf@ietf.org>; Tue,  7 Jan 2014 07:27:42 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob12.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s07FRWxK001890 for <ietf@ietf.org>; Tue, 7 Jan 2014 10:27:32 -0500
Received: (qmail 5373 invoked by uid 0); 7 Jan 2014 15:27:32 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?192.168.15.109?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 7 Jan 2014 15:27:32 -0000
Date: Tue, 07 Jan 2014 10:27:30 -0500
Subject: Re: Split the IANA functions?
Message-ID: <667offmffdw4wef4wh9ofns3.1389108450398@email.android.com>
Importance: normal
From: avri doria <avri@ella.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_8764175946230600"
X-Mailman-Approved-At: Tue, 07 Jan 2014 08:07:02 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 15:27:45 -0000

----_com.android.email_8764175946230600
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGksCgpJIHRob3VnaHQgdGhlIG9ubHkgcmVhc29uIHRoZSBETlMgcm9vdCBpcyBhIHNpbmdsZSBy
b290IGFuZCBub3QgYSBiYW55YW4gbGlrZSByb290LCBpcyBiZWNhdXNlIGNsYXNzZXMgZG9uJ3Qg
cmVhbGx5IHdvcmsgYW5kIHRoZXJlIGhhcyBiZWVuIGEgcG9saXRpY2FsIChidXNpbmVzcywgZWNv
bm9taWMgZXRjICkgdGVuZGVuY3kgKGhhcmQgdG8gY2FsbCBpdCBkZWNpc2lvbikgdG8gbm90IGZp
eCBvciByZXBsYWNlLgoKCmF2cmkKClNlbnQgZnJvbSBhIFQtTW9iaWxlIDRHIExURSBEZXZpY2UK
Ci0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS0KRnJvbTogQW5kcmV3IFN1bGxpdmFu
IDxhanNAYW52aWx3YWxydXNkZW4uY29tPiAKRGF0ZTowMS8wNy8yMDE0ICAwOTo0NCAgKEdNVC0w
NTowMCkgClRvOiBpZXRmQGlldGYub3JnIApTdWJqZWN0OiBSZTogU3BsaXQgdGhlIElBTkEgZnVu
Y3Rpb25zPyAKCk9uIFR1ZSwgSmFuIDA3LCAyMDE0IGF0IDA3OjAyOjM0QU0gKzAxMDAsIEVsaW90
IExlYXIgd3JvdGU6Cj4gVGhhdCB0aGVyZSBpcyBhIHNpbmdsZSByb290IGlzIGJvdGggYSB0ZWNo
bmljYWwgQU5EIGEKPiBwb2xpdGljYWwgZGVjaXNpb24uIAoKSSBoYXZlIHRvIGRpc2FncmVlIHdp
dGggdGhpcy7CoCBUaGUgdW5pcXVlbmVzcyBvZiB0aGUgcm9vdCBpcyBub3QgYQpwb2xpdGljYWwg
ZGVjaXNpb24uwqAgSXQncyBhIGZhY3Qgb2YgbWF0aGVtYXRpY3MuwqAgRE5TIGlzIGEgdHJlZS4K
VGhlcmUncyBvbmUgcm9vdC4KCk5vdywgb25lIG1pZ2h0IGFyZ3VlIHRoYXQgY2hvb3NpbmcgdGhp
cyBraW5kIG9mIG5hbWUgc3BhY2Ugd2FzIGEKcG9saXRpY2FsIGRlY2lzaW9uLsKgIEkgbWlnaHQg
YnV5IHRoYXQgYXJndW1lbnQgKEkgZG9uJ3Qga25vdykuwqAgVGhlcmUncwpnb29kIHJlYXNvbiB0
byBzdXBwb3NlIHRoYXQgdGhlcmUgd2FzIGF0IGxlYXN0IHNvbWUgb3JnYW5pemF0aW9uYWwKcHJp
bmNpcGxlIGJlaGluZCB0aGUgZGVjaXNpb24gaW4gZmF2b3VyIG9mIGEgaGllcmFyY2hpY2FsIG5h
bWVzcGFjZS4KVGhlcmUgd2VyZSB0ZWNobmljYWwgY29uc3RyYWludHMgdG9vLCBJIHRoaW5rOiBJ
IGRvbid0IGJlbGlldmUgYSBmdWxseQpwZWVyIHRvIHBlZXIgc3lzdGVtIHdhcyBwcmFjdGljYWwg
aW4gdGhlIG5ldHdvcmsgZW52aXJvbm1lbnQgb2YgdGhlCjE5ODBzLsKgIEJ1dCBpZiB3ZSB3YW50
ZWQgdG8gY2FsbCBhbnl0aGluZyB0aGF0IGhhZCBub24tdGVjaG5pY2FsCmVsZW1lbnRzIGluIGl0
ICJwb2xpdGljYWwiLCB0aGVuIHRoZSBzZWxlY3Rpb24gb2YgdGhlIEROUwooaGllcmFyY2hpY2Fs
KSBuYW1lIHNwYWNlIHdhcyBpbiB0aGF0IHNlbnNlIHBvbGl0aWNhbC4KClRoaXMgaXMgbm90IHRv
IHNheSB0aGF0IHRoZSBzaW5nbGUgcm9vdCBkb2Vzbid0IGhhdmUgYWRkaXRpb25hbApwb2xpdGlj
YWwgaW1wbGljYXRpb25zLsKgIEJ1dCBJIHdpbGwgbm90IGNvbmNlZGUgdGhhdCB0aGlzIGlzIHNv
bWUKY29udGluZ2VudCBmYWN0IG9mIHRoZSBETlMgdGhhdCBjb3VsZCBiZSBvdGhlcndpc2UuwqAg
VGhlIHBhcnRpY3VsYXIKcm9vdCB3ZSBoYXZlIGNvdWxkIGJlIGRpZmZlcmVudC7CoCBUaGF0IHRo
ZXJlIGlzIGEgc2luZ2xlIHJvb3QgY291bGQKbm90LgoKQmVzdCByZWdhcmRzLAoKQQoKLS0gCkFu
ZHJldyBTdWxsaXZhbgphanNAYW52aWx3YWxydXNkZW4uY29tCgo=

----_com.android.email_8764175946230600
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keSA+PGRpdj5IaSw8L2Rpdj48ZGl2Pjxi
cj48L2Rpdj48ZGl2PkkgdGhvdWdodCB0aGUgb25seSByZWFzb24gdGhlIEROUyByb290IGlzIGEg
c2luZ2xlIHJvb3QgYW5kIG5vdCBhIGJhbnlhbiBsaWtlIHJvb3QsIGlzIGJlY2F1c2UgY2xhc3Nl
cyBkb24ndCByZWFsbHkgd29yayBhbmQgdGhlcmUgaGFzIGJlZW4gYSBwb2xpdGljYWwgKGJ1c2lu
ZXNzLCBlY29ub21pYyBldGMgKSB0ZW5kZW5jeSAoaGFyZCB0byBjYWxsIGl0IGRlY2lzaW9uKSB0
byBub3QgZml4IG9yIHJlcGxhY2UuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+
PGRpdiBzdHlsZT0iZm9udC1zaXplOjc1JSI+YXZyaTwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6
ZTo3NSUiPjxicj48L2Rpdj48ZGl2IHN0eWxlPSJmb250LXNpemU6NzUlIj5TZW50IGZyb20gYSBU
LU1vYmlsZSA0RyBMVEUgRGV2aWNlPC9kaXY+PGJyPjxicj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNz
YWdlIC0tLS0tLS0tPGJyPkZyb206IEFuZHJldyBTdWxsaXZhbiA8YWpzQGFudmlsd2FscnVzZGVu
LmNvbT4gPGJyPkRhdGU6MDEvMDcvMjAxNCAgMDk6NDQgIChHTVQtMDU6MDApIDxicj5UbzogaWV0
ZkBpZXRmLm9yZyA8YnI+U3ViamVjdDogUmU6IFNwbGl0IHRoZSBJQU5BIGZ1bmN0aW9ucz8gPGJy
Pjxicj5PbiBUdWUsIEphbiAwNywgMjAxNCBhdCAwNzowMjozNEFNICswMTAwLCBFbGlvdCBMZWFy
IHdyb3RlOjxicj4mZ3Q7IFRoYXQgdGhlcmUgaXMgYSBzaW5nbGUgcm9vdCBpcyBib3RoIGEgdGVj
aG5pY2FsIEFORCBhPGJyPiZndDsgcG9saXRpY2FsIGRlY2lzaW9uLiA8YnI+PGJyPkkgaGF2ZSB0
byBkaXNhZ3JlZSB3aXRoIHRoaXMuJm5ic3A7IFRoZSB1bmlxdWVuZXNzIG9mIHRoZSByb290IGlz
IG5vdCBhPGJyPnBvbGl0aWNhbCBkZWNpc2lvbi4mbmJzcDsgSXQncyBhIGZhY3Qgb2YgbWF0aGVt
YXRpY3MuJm5ic3A7IEROUyBpcyBhIHRyZWUuPGJyPlRoZXJlJ3Mgb25lIHJvb3QuPGJyPjxicj5O
b3csIG9uZSBtaWdodCBhcmd1ZSB0aGF0IGNob29zaW5nIHRoaXMga2luZCBvZiBuYW1lIHNwYWNl
IHdhcyBhPGJyPnBvbGl0aWNhbCBkZWNpc2lvbi4mbmJzcDsgSSBtaWdodCBidXkgdGhhdCBhcmd1
bWVudCAoSSBkb24ndCBrbm93KS4mbmJzcDsgVGhlcmUnczxicj5nb29kIHJlYXNvbiB0byBzdXBw
b3NlIHRoYXQgdGhlcmUgd2FzIGF0IGxlYXN0IHNvbWUgb3JnYW5pemF0aW9uYWw8YnI+cHJpbmNp
cGxlIGJlaGluZCB0aGUgZGVjaXNpb24gaW4gZmF2b3VyIG9mIGEgaGllcmFyY2hpY2FsIG5hbWVz
cGFjZS48YnI+VGhlcmUgd2VyZSB0ZWNobmljYWwgY29uc3RyYWludHMgdG9vLCBJIHRoaW5rOiBJ
IGRvbid0IGJlbGlldmUgYSBmdWxseTxicj5wZWVyIHRvIHBlZXIgc3lzdGVtIHdhcyBwcmFjdGlj
YWwgaW4gdGhlIG5ldHdvcmsgZW52aXJvbm1lbnQgb2YgdGhlPGJyPjE5ODBzLiZuYnNwOyBCdXQg
aWYgd2Ugd2FudGVkIHRvIGNhbGwgYW55dGhpbmcgdGhhdCBoYWQgbm9uLXRlY2huaWNhbDxicj5l
bGVtZW50cyBpbiBpdCAicG9saXRpY2FsIiwgdGhlbiB0aGUgc2VsZWN0aW9uIG9mIHRoZSBETlM8
YnI+KGhpZXJhcmNoaWNhbCkgbmFtZSBzcGFjZSB3YXMgaW4gdGhhdCBzZW5zZSBwb2xpdGljYWwu
PGJyPjxicj5UaGlzIGlzIG5vdCB0byBzYXkgdGhhdCB0aGUgc2luZ2xlIHJvb3QgZG9lc24ndCBo
YXZlIGFkZGl0aW9uYWw8YnI+cG9saXRpY2FsIGltcGxpY2F0aW9ucy4mbmJzcDsgQnV0IEkgd2ls
bCBub3QgY29uY2VkZSB0aGF0IHRoaXMgaXMgc29tZTxicj5jb250aW5nZW50IGZhY3Qgb2YgdGhl
IEROUyB0aGF0IGNvdWxkIGJlIG90aGVyd2lzZS4mbmJzcDsgVGhlIHBhcnRpY3VsYXI8YnI+cm9v
dCB3ZSBoYXZlIGNvdWxkIGJlIGRpZmZlcmVudC4mbmJzcDsgVGhhdCB0aGVyZSBpcyBhIHNpbmds
ZSByb290IGNvdWxkPGJyPm5vdC48YnI+PGJyPkJlc3QgcmVnYXJkcyw8YnI+PGJyPkE8YnI+PGJy
Pi0tIDxicj5BbmRyZXcgU3VsbGl2YW48YnI+YWpzQGFudmlsd2FscnVzZGVuLmNvbTxicj48YnI+
PC9ib2R5Pg==

----_com.android.email_8764175946230600--



From dhc@dcrocker.net  Tue Jan  7 08:08:44 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B7171AE00A for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Pc0H7-1X8gB for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:08:42 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E9F051ADFF8 for <ietf@ietf.org>; Tue,  7 Jan 2014 08:08:42 -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 s07G8TuX016315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Jan 2014 08:08:32 -0800
Message-ID: <52CC261C.4030104@dcrocker.net>
Date: Tue, 07 Jan 2014 08:06:52 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
In-Reply-To: <20140107144412.GB11068@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 07 Jan 2014 08:08:32 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 07 Jan 2014 16:08:44 -0000

On 1/7/2014 6:44 AM, Andrew Sullivan wrote:
> Now, one might argue that choosing this kind of name space was a
> political decision.  I might buy that argument (I don't know).  There's
> good reason to suppose that there was at least some organizational
> principle behind the decision in favour of a hierarchical namespace.


As many folks remember, around 15 years ago, when ICANN was being 
formed, there was a strong constituency in favor of more than one root. 
  The problem with their arguments was that either their designs ensured 
chaotic name ambiguity, or they were simply moving the single root to an 
automated mechanism rather than an administered process.

So the 'political' decisions about the existing DNS technology have been 
such things as ensuring name uniqueness, administrative scaling and 
query scaling.  The design of the DNS and the design of its 
administrative structure derive from these operational requirements.

None of this is really 'political' in the way that people tend to use 
the term.  In practical terms, there hasn't been any choice.  No 
alternative design has been put forward that is viable at scale.

IMO, to be meaningfully political, a decision needs to represent 
meaingful choice among significantly different alternatives.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From adrian@olddog.co.uk  Tue Jan  7 08:13:57 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 729651ADF9B for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:13:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.847
X-Spam-Level: 
X-Spam-Status: No, score=0.847 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXp3MxAF2vFw for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:13:55 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 973F81ADF98 for <ietf@ietf.org>; Tue,  7 Jan 2014 08:13:55 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s07GDjZJ029510 for <ietf@ietf.org>; Tue, 7 Jan 2014 16:13:45 GMT
Received: from 950129200 (14.21.90.92.rev.sfr.net [92.90.21.14]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s07GDhPW029500 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 7 Jan 2014 16:13:45 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Last call debate on draft-farrell-perpass-attack
Date: Tue, 7 Jan 2014 16:13:46 -0000
Message-ID: <015901cf0bc3$72bb75d0$58326170$@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: Ac8Lw2szjkgNuRQwSuKh07AWp1OQiw==
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 16:13:57 -0000

Hi,

I want to weigh in supporting the publication of this document.

I was a document author and then WG chair in CCAMP at a time when it was
exceeding hard to get a GMPLS RFC published because the security considerations
for GMPLS "were not properly documented". I can confess that I became very
disillusioned with the IETF process and with the serving Security ADs at the
time. It took a lot of discussion for me to be convinced that the ADs were doing
what they genuinely thought was best for the Internet (even though they were
wrong ;-)

But it was not the existence of any document describing security consideration
sections that enabled the ADs to block publication. Nor was it some wrinkle in
the process. It was the right and proper process that enables ADs to worry about
the impact on the stability (which includes security) of the Internet when
looking at publication requests. Furthermore, it was not the process per se that
was at fault, it was the enthusiasm of the ADs, and *that* was perfectly
possible to handle using the existing processes (although it was a steep
learning curve for me) and normal discussions about which we should never be
defensive or paranoid.

So, why do I rake up the past now?

This document in its current form does not, IMHO, represent a tool that can be
used by any AD to block or cause delay to the publication of any RFC. If
anything, it provides assistance to authors to enable them to think about some
new yet key issues and include the right discussions in their documents. The
document goes nowhere near as far as RFC 5706 in "dictating" what has to be
documented in a protocol spec yet I don't recall any fuss about that document.
Far from it: this document simply describes the landscape, explains how privacy
attacks may be happening, and indicates that the authors think that such attacks
should be considered in the design of protocols.

And there is a get-out-of-jail-free card that I would find perfectly acceptable:

   This does not mean a new "pervasive monitoring
   considerations" section is needed in IETF documentation.  It means
   that, if asked, there needs to be a good answer to the question "is
   pervasive monitoring relevant to this work and if so how has it been
   addressed?"

Note that that discussion can be in the shepherd write-up, on the mailing list,
in a conversation with the Sec AD during evaluation or (and only if the
authors/WG want to) in the I-D.

I do not find the discussions of opinions voiced against this I-D to be
convincing, and I support its publication.

Thanks,
Adrian




From hallam@gmail.com  Tue Jan  7 08:29:17 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8441ADF98 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-_uxOaW3RDB for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 08:29:14 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 85E611ADF72 for <ietf@ietf.org>; Tue,  7 Jan 2014 08:29:14 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id eh20so283719lab.19 for <ietf@ietf.org>; Tue, 07 Jan 2014 08:29:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HOvfg3i/O49/mipn6mBo3OWgofyf2HMkdCtBA6l1aFs=; b=hM5wgBLmGFdFScMTCkU4p0QQGY/3Mir3CoE+mV3XEs9E0oYDYd6eRSBtWl1yahAX0X MNauU2sd3q3owZMAIZmTbnlKW6q7LbavuESgz+uAwNjDgUSW2oD7OwR4S1zhEVteet5W 1sUQ/3X48Idr/GFiKxMy0hVVnmtDX7RRSSdCBMr/Edh1tIVjafRf0qggLuSXyOp7KzvQ aBYvoZsmzvSuupl/sQcE05MNmI0ueQXutR7hi5q6PWa0DsThgdr2T1xEyKgaJYaOl7fM pRYopF/W/+ebw16/xnZCucUDZy+M0ESKGOhf4f+mYNbmQsCKR59S/cMieDGbqULMTITo MRxQ==
MIME-Version: 1.0
X-Received: by 10.112.138.70 with SMTP id qo6mr3746441lbb.34.1389112144978; Tue, 07 Jan 2014 08:29:04 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Tue, 7 Jan 2014 08:29:04 -0800 (PST)
In-Reply-To: <20140107144412.GB11068@mx1.yitter.info>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
Date: Tue, 7 Jan 2014 11:29:04 -0500
Message-ID: <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com>
Subject: Re: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=089e0112c02cf469e304ef63df54
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 16:29:17 -0000

--089e0112c02cf469e304ef63df54
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 7, 2014 at 9:44 AM, Andrew Sullivan <ajs@anvilwalrusden.com>wro=
te:

> On Tue, Jan 07, 2014 at 07:02:34AM +0100, Eliot Lear wrote:
> > That there is a single root is both a technical AND a
> > political decision.
>
> I have to disagree with this.  The uniqueness of the root is not a
> political decision.  It's a fact of mathematics.  DNS is a tree.
> There's one root.
>

It didn't have to be a tree, it could have been something else, we could
still change it.

You might think that there is no other possible technical solution but that
is a failure of imagination rather than a fact. It might even be the best
technical solution but the definition of 'best' is with respect to
requirements.


A lot of the 'technical' arguments that are made against demands made by
Russia, China, etc. are actually technical choices and it undermines our
position when people falsely claim that there is no alternative.

I am currently at a conference where Fadi Chehad=E9 just talked about Russi=
a
asking to host a root server and he led the audience to believe that there
could only be 13 servers. So I had to correct him and point out that Russia
already has a DNS server due to anycast and what we are actually arguing
about is a root service, an abstract construct.

There is of course no technical reason that the number of services is
limited to 13. We can have as many as there are institutions willing to run
them at an acceptable level of reliability.

Putin's technical advisor is probably telling Putin that the westerner's
claims of technical limitations are bogus and he would be right.


The argument against more root servers is political, not technical and the
politics are rather more complex than just 'should Russia have one'.

At the moment the root is small and the load relatively light. In fact the
legitimate load is essentially zero. The root zone could probably be
distributed as a flat file, it isn't large, it doesn't change very much.
Certainly it is nothing like .com. The only real issue in root server
management is dealing with the load from the DoS attacks which are awesome
in scale.

The main consequence of expanding the root zone is that the root zone
operators would constrain future development of the DNS. The root zone is
going to grow with the new TLDs. When the number of TLDs reaches a certain
point there will be a tipping point and there will be pressure to open up.

Having a hundred root operators would greatly constrain those changes, But
that might in part be why Russia and China want a seat at that table

This is not to say that the single root doesn't have additional
> political implications.  But I will not concede that this is some
> contingent fact of the DNS that could be otherwise.  The particular
> root we have could be different.  That there is a single root could
> not.
>

Uniformity of the name space is the essential criteria. The Web can't work
on UUCP bang path addressing.

Describing this as having a single root conflates a large number of issues
and essentially commits to a particular conclusion. A uniform namespace is
a requirement, a single 'root' is not.



--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jan 7, 2014 at 9:44 AM, Andrew Sullivan <span dir=3D"ltr">&=
lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwal=
rusden.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">On Tue, Jan 07, 2014 at 07:02:34AM +0100=
, Eliot Lear wrote:<br>

&gt; That there is a single root is both a technical AND a<br>
&gt; political decision.<br>
<br>
</div>I have to disagree with this. =A0The uniqueness of the root is not a<=
br>
political decision. =A0It&#39;s a fact of mathematics. =A0DNS is a tree.<br=
>
There&#39;s one root.<br></blockquote><div><br></div><div>It didn&#39;t hav=
e to be a tree, it could have been something else, we could still change it=
.</div><div><br></div><div>You might think that there is no other possible =
technical solution but that is a failure of imagination rather than a fact.=
 It might even be the best technical solution but the definition of &#39;be=
st&#39; is with respect to requirements.=A0</div>
<div><br></div><div><br></div><div>A lot of the &#39;technical&#39; argumen=
ts that are made against demands made by Russia, China, etc. are actually t=
echnical choices and it undermines our position when people falsely claim t=
hat there is no alternative.</div>
<div><br></div><div>I am currently at a conference where Fadi Chehad=E9 jus=
t talked about Russia asking to host a root server and he led the audience =
to believe that there could only be 13 servers. So I had to correct him and=
 point out that Russia already has a DNS server due to anycast and what we =
are actually arguing about is a root service, an abstract construct.</div>
<div><br></div><div>There is of course no technical reason that the number =
of services is limited to 13. We can have as many as there are institutions=
 willing to run them at an acceptable level of reliability.</div><div><br>
</div><div>Putin&#39;s technical advisor is probably telling Putin that the=
 westerner&#39;s claims of technical limitations are bogus and he would be =
right.</div><div><br></div><div><br></div><div>The argument against more ro=
ot servers is political, not technical and the politics are rather more com=
plex than just &#39;should Russia have one&#39;.</div>
<div><br></div><div>At the moment the root is small and the load relatively=
 light. In fact the legitimate load is essentially zero. The root zone coul=
d probably be distributed as a flat file, it isn&#39;t large, it doesn&#39;=
t change very much. Certainly it is nothing like .com. The only real issue =
in root server management is dealing with the load from the DoS attacks whi=
ch are awesome in scale.</div>
<div><br></div><div>The main consequence of expanding the root zone is that=
 the root zone operators would constrain future development of the DNS. The=
 root zone is going to grow with the new TLDs. When the number of TLDs reac=
hes a certain point there will be a tipping point and there will be pressur=
e to open up.</div>
<div><br></div><div>Having a hundred root operators would greatly constrain=
 those changes, But that might in part be why Russia and China want a seat =
at that table=A0</div><div><br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(2=
04,204,204);border-left-style:solid;padding-left:1ex">
This is not to say that the single root doesn&#39;t have additional<br>
political implications. =A0But I will not concede that this is some<br>
contingent fact of the DNS that could be otherwise. =A0The particular<br>
root we have could be different. =A0That there is a single root could<br>
not.<br></blockquote><div><br></div><div>Uniformity of the name space is th=
e essential criteria. The Web can&#39;t work on UUCP bang path addressing.<=
/div><div><br></div><div>Describing this as having a single root conflates =
a large number of issues and essentially commits to a particular conclusion=
. A uniform namespace is a requirement, a single &#39;root&#39; is not.</di=
v>
</div><div><br></div><div><br></div><div><br></div>-- <br>Website: <a href=
=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0112c02cf469e304ef63df54--

From ned+ietf@mauve.mrochek.com  Tue Jan  7 09:28:32 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7FC71AE085 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I839uzfYUWN0 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:28:30 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7771ADF4B for <ietf@ietf.org>; Tue,  7 Jan 2014 09:28:30 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P2V8MQOO6O0029R0@mauve.mrochek.com> for ietf@ietf.org; Tue, 7 Jan 2014 09:23:19 -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 <01P2SI6PLQJK0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 7 Jan 2014 09:23:12 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P2V8MN121I0000AS@mauve.mrochek.com>
Date: Tue, 07 Jan 2014 08:52:18 -0800 (PST)
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
In-reply-to: "Your message dated Tue, 07 Jan 2014 10:18:56 -0500" <CAF4+nEHDNC-aQCY6r1zceb=7hOW4JmfnMWDWZSEM6gJLTSDF9Q@mail.gmail.com>
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux> <CAF4+nEHDNC-aQCY6r1zceb=7hOW4JmfnMWDWZSEM6gJLTSDF9Q@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 17:28:33 -0000

Donald Eastlake <d3e3e3@gmail.com> wrote:

> On Fri, Jan 3, 2014 at 11:34 AM, Eric Rosen <erosen@cisco.com> wrote:
> >
> > Stewart> The -03 text is a significant improvement, but I still fear the
> > Stewart> impact of single issue technical politics on the output of our
> > Stewart> document stream.
> >
> > Let's face it, the draft is nothing but a political manifesto, and the IETF
> > has no business even considering it.  It is also clear from this discussion
> > that there is no consensus, even rough consensus, in favor.

All this quibbling over whether or not the document is political, a manifesto,
or whatever, seems pretty pointless to me. All I care about is what the
document says and given that, what the likely effects of having this document
as a BCP are going to be.

> Anyone who has been around in the IETF long enough has seen this
> before. Rabid opposition to real consideration of strong security. I
> have seen yelling at plenaries. I've heard people say how the IETF
> will be destroyed or become irrelevant if we don't bow to the US
> Government rules. Etc.

The fact that there has been opposition to previous statements about security
does not mean that the opposition to the document at hand has the same
character. The burden of proof for that would be on you and others making
this claim, and thus far I don't see any evidence being presented to support
this underlying claim.

In my own case, I fully supported the publication of RFCs 1984 (weak keys) and
2804 (wiretapping) - the two previous statements of this sort this document
cites. I also argued for the imposition of mandatory to implement ciphersuites
in TLS. And so on - I don't think I've exactly been an opponent of strong
security.

And yet I strongly oppose publication of this document as a BCP. I think it
should be published as an informational document instead. (I should note that I
find the idea of publishing this as experimental to be intriguing, but given
the confusion that has surrounded previous experiments I think this course is
too risky for something this important.)

I find this document to be too vague to function properly as a BCP, and I don't
think we have a sufficient understanding of the tradeoffs involved in making
pervasive monitoring more difficult to write a proper BCP at the present time.
And if anything, hasty and ill-considered changes may make monitoring easier,
not harder.

I think the course advocated by Dave Crocker is the correct one: Publish this
as an informational policy statement, and then work through the policy on
subsequent specifications. Then, once we believe we have a sufficient grasp of
how this actually plays out, write a BCP. (Dave, I think this summarizes your
position, but if not, apologies for getting it wrong.)

I also note that RFCs 1984 and 2804 were both published as informational. Maybe
I missed it, but I find nothing in the document itself that explains why this
time is different and publication as BCP is warranted.

> If you want to distort the word "political" to try to characterize
> this, I don't care that much. This draft is completely in line with
> the previous admirable IETF engineering positions on security.

Which would argue for handling this one the same way, would it not?

> > Note the tone taken by proponents of the draft.  ... one cannot determine
> > from the draft what the actual impact on IETF process is ... claim the support
> > of a "silent majority" ...

(This is really off topic, but since you raised the issue, I'll make one
comment about it. I have no intention of discussing this further.)

The tone taken by both sides in this argument has been quite poor. That said,
my impression has been that there has been more impugning of motives from
supporters than from opponents.

> Note the tone taken by opponents of the draft. Gross distortions and
> mischaracterization of the draft. I hope people reading the IETF
> discussion list, if they care about this issue, will actually read the
> draft and see what it actually says, which is pretty reasonable.

What the draft says is reasonable IMO, but that's really beside the point. The
problem is what the draft does not say. It says we're going to take action to
mitigate attacks but doesn't say how this is going to be done. That vagueness
is fine for an architectural policy statement but leaves far too much leeway
for a BCP.

> The intended effect on IETF process is clear enough to me from the
> document, at least in version -03.

I have no doubt the intentions here are good. But all too often intended and
actual results diverge.

				Ned

From ajs@anvilwalrusden.com  Tue Jan  7 09:39:54 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6EF61AE06E for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.758
X-Spam-Level: *
X-Spam-Status: No, score=1.758 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pM3U_KGSUT06 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:39:53 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 102281AE069 for <ietf@ietf.org>; Tue,  7 Jan 2014 09:39:52 -0800 (PST)
Received: from mx1.yitter.info (nat-07-mht.dyndns.com [216.146.45.246]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id D5E118A031 for <ietf@ietf.org>; Tue,  7 Jan 2014 17:39:43 +0000 (UTC)
Date: Tue, 7 Jan 2014 12:39:42 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Split the IANA functions?
Message-ID: <20140107173942.GE11538@mx1.yitter.info>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 17:39:55 -0000

On Tue, Jan 07, 2014 at 11:29:04AM -0500, Phillip Hallam-Baker wrote:
> It didn't have to be a tree, it could have been something else, we could
> still change it.

Gee, Phill, I love it when people elide the exact point I made when
selectively quoting, and then chide me for not having made that point.

Yes, it could be something else.  In the logically-possible world in
which I am a mud puddle, I spend less time responding to emails about
the nature of naming on the Internet.  But both the naming system on
the Internet and I (perhaps unhappily for one of us) exist in this
world.  The Internet as it stands uses the DNS, a tree-structured name
space.  A tree-structured name space has, by definition, a unique
root, due to the math in this universe.[1],[2]

> Describing this as having a single root conflates a large number of issues
> and essentially commits to a particular conclusion. A uniform namespace is
> a requirement, a single 'root' is not.

I wasn't claiming a single root is a requirement for a uniform name
space; I don't care about that question.  I was suggesting that, given
that we have the DNS and it is the name system that is actually
deployed, we have right now a requirement for a unique root in that
name system.  If you want to make up a new non-DNS naming system and
deploy it and get the world to use it, please go nuts.  I have plenty
of complaints about the DNS and the way it works.  I suggest that the
history of IPv6 deployment prior to the actual exhaustion of the IPv4
number space gives us a pretty good lesson in the likelihood of non-DNS
global naming taking off without some killer feature.  In my opinion,
"Doesn't make Vladimir Putin grumpy," is unlikely to be the killer
feature that will cause people to change whatever invisible naming
system they use to bootstrap the applications on their tablets or find
Google or Bing.

Best regards,

A
 

[1] To acknowledge Avri's point elsewhere in this thread, yes, it is
possible to have a different CLASS with different RDATA at the name
owner name and RRTYPE.  The name space is still tree shaped with a
unique root, in that the owner names persist across all CLASSes.  This
is perhaps not quite as obvious as one would like in RFCs 1034, 1035,
and maybe 2181.  DNSEXT attempted to do something about this a few
years ago, but we didn't get any traction so we gave up. 

It is undoubtedly the case that there was some reason people didn't do
something about the difficulties with CLASSes.  One of the explanations,
of course, is that if we were going to fix the DNS at that basic a
level, we might as well replace it completely with something else that
doesn't have the properties we'd be trying to repair.

[2] I refuse to have a position on whether there is a logically
possible world in which mathematical tree structures do not by
definition have a single root.  Possible-worlds semantics over
mathematical proofs was probably too hard for me when I actually did
possible-worlds semantics work, and by now I've forgotten most of that
Latin.

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jari.arkko@piuha.net  Tue Jan  7 09:45:45 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 067761AE0AF for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rv3mHRV2ktDJ for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:45:43 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A35321AE0AE for <ietf@ietf.org>; Tue,  7 Jan 2014 09:45:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 897872CC61 for <ietf@ietf.org>; Tue,  7 Jan 2014 19:45:34 +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 uo-tnQvwzPBU for <ietf@ietf.org>; Tue,  7 Jan 2014 19:45:30 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7F4922CC48 for <ietf@ietf.org>; Tue,  7 Jan 2014 19:45:29 +0200 (EET)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 1net nominations, scope, discussions
Message-Id: <64686BAF-C43F-4D82-8622-EF2E475BBDAD@piuha.net>
Date: Tue, 7 Jan 2014 09:45:27 -0800
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 17:45:45 -0000

This is not an IETF issue as such, but some of you may care, so I wanted =
a raise awareness of some discussions on the 1net list as well as an =
ongoing call for nominations.

Technical community nominations for 1net and Brazil meeting committees: =
http://1net-mail.1net.org/pipermail/discuss/2013-December/000063.html =
(ISOC, to close on Jan 10)

Discussion of scope and purpose of 1net, see, e.g., =
http://1net-mail.1net.org/pipermail/discuss/2014-January/000644.html or =
http://1net-mail.1net.org/pipermail/discuss/2013-December/000346.html or =
http://1net-mail.1net.org/pipermail/discuss/2014-January/000630.html or =
many others...

Summary of discussions on the list so far: =
http://www.slideshare.net/lphinojosa/1net-discuss

Jari


From kent@bbn.com  Tue Jan  7 09:56:39 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E711AE0BF for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:56:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HL0FOxII3yRz for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:56:36 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE6B1AE077 for <ietf@ietf.org>; Tue,  7 Jan 2014 09:56:36 -0800 (PST)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:50601) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1W0at8-000AgK-Tq for ietf@ietf.org; Tue, 07 Jan 2014 12:56:27 -0500
Message-ID: <52CC3FCA.6080500@bbn.com>
Date: Tue, 07 Jan 2014 12:56:26 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IANA blog article
References: <EBB673AA-7240-4650-AAC3-51B8142B3DEF@ietf.org> <CAMm+Lwj44s4zUwDcDDW0WzRPTo6fUueRu7vZRjenisNoHg6cRg@mail.gmail.com> <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
In-Reply-To: <839AD4D5-433F-44CC-8976-38FB57EDEBCA@piuha.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 17:56:40 -0000

Jari,
>> Another is that application protocols should be required to reuse code points from common registries rather than define their own.
>>
>> At the moment we have separate crypto registries for TLS, IPSEC, PEM, PKIX and XML Digital Signature. The JOSE folk want to create another. There should be a policy that tells people from the start that there will be no new crypto registries.
> Here I am not so sure. Registries for adding specific crypto algorithms are not merely number allocations; they go with specifications and code that actually runs, say, AES on IPsec or AES on TLS. It is not entirely clear to me that crypto across different protocols and use cases should proceed in lock step. And even if it were useful, it is a difficult change to make retroactively, when the code points in different protocols started out differently.
I concur with your observation wrt crypto algs. One size (alg or even 
key length) does
not fit all. When we introduce new protocols we have more flexibility in 
adopting new
algs and it may make sense to mandate support for them. For existing 
protocols
insisting that new algs be supported impose a greater burden and perhaps 
a long
transition  process.  In some contexts a suite of new algs can be 
incrementally
deployed with minimal impact, whereas in other contexts changes must be 
adopted
globally.

Steve



From kent@bbn.com  Tue Jan  7 09:59:21 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83FFC1AE0CA for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:59:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.346
X-Spam-Level: 
X-Spam-Status: No, score=-2.346 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=2.393] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6JFUVbVmq6A for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 09:59:20 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 5856E1AE0B4 for <ietf@ietf.org>; Tue,  7 Jan 2014 09:59:20 -0800 (PST)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:50602) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1W0avn-000Ahu-Aj for ietf@ietf.org; Tue, 07 Jan 2014 12:59:11 -0500
Message-ID: <52CC406F.9050806@bbn.com>
Date: Tue, 07 Jan 2014 12:59:11 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <26734.1388770438@erosen-linux>, <52C708C3.3050301@gmail.com> <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
In-Reply-To: <C35AA8FB-D9F6-4EED-A87E-484E063EA7FD@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 17:59:21 -0000

Stewart,

> I have been wondering whether a simple update to "A Guide to Writing A Security Considerations Section" is all that is needed to address the problem in hand?
>
> Stewart
Good question.

RFC 3552 contains a threat model, and we need to update that threat model.
The I-D just released by Richard Barnes et al. seems to addressing that.
If we were to combine a new threat model, which explicitly accounts
for PM, with updated security considerations guidance, then I think we would
have what Stephen's doc alludes to at the end, i.e., guidance to RFC authors
on what we now consider to be the threat environment, and what we believe
needs to be done, vis-a-vis topics address in each security-relevant RFC.

That may argue for Stephen's doc being Informational, maybe even transient,
as the real focus is on what we will do in response to declaring PM a
serious concern.

Steve

From drc@virtualized.org  Tue Jan  7 10:34:30 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEB291AE10F for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:34:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YY02_VLB52Zm for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:34:27 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id B6C9C1ADEB1 for <ietf@ietf.org>; Tue,  7 Jan 2014 10:34:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 2A62C84CED; Tue,  7 Jan 2014 13:34:18 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 97859-06; Tue,  7 Jan 2014 13:34:17 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 43BEC84B42; Tue,  7 Jan 2014 13:34:16 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_05327F0C-68E5-4D2A-A413-A92F92A181E5"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Split the IANA functions?
From: David Conrad <drc@virtualized.org>
In-Reply-To: <667offmffdw4wef4wh9ofns3.1389108450398@email.android.com>
Date: Tue, 7 Jan 2014 10:34:11 -0800
Message-Id: <F371C3CF-9493-45D2-A83B-2CC53BD333CE@virtualized.org>
References: <667offmffdw4wef4wh9ofns3.1389108450398@email.android.com>
To: avri doria <avri@ella.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 18:34:30 -0000

--Apple-Mail=_05327F0C-68E5-4D2A-A413-A92F92A181E5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Avri,

On Jan 7, 2014, at 7:27 AM, avri doria <avri@ella.com> wrote:
> I thought the only reason the DNS root is a single root and not a =
banyan like root, is because classes don't really work and there has =
been a political (business, economic etc ) tendency (hard to call it =
decision) to not fix or replace.

Using classes simply moves the single root up to the IANA class =
registry.  Classes work fine: the minor issues to deal with are that =
there is no applications that support a way to make distinctions on =
classes, some widely deployed DNS servers do not support classes, no DNS =
UIs or DNS-based systems support classes (and we can't even get simple =
RR types like type 99/SPF supported to the point we've apparently =
deprecated the use of that RR type), and, in order to use classes, we'd =
have to figure out some way to get people's pointy haired bosses to =
understand that <class123>:phbporn.com is _not_ <class666>:phbporn.com.  =
=46rom my (perhaps a bit cynical) perspective, the ship has not only =
sailed on the use of classes, but it has hit an iceberg and sunk long =
ago.

Regards,
-drc




--Apple-Mail=_05327F0C-68E5-4D2A-A413-A92F92A181E5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSzEijAAoJENV6ebf0/4rXWRYH/R2twapyisrRt1HHAmH8nZoD
YPYSsIIxEx0Ps2MQ535nSLcHUf5FhutGiB3oGbxGvdegdVLP1Isx6sXi3IBYG2aA
iejw5yk4xZOMwP1qHtiWrJEux5wCn7+eYWPJS1GQhsOEV/v0OMUO4slzIeHCcFyX
KSVlogyEp4YEeLgQhnmB7/xLLV5500yHoTiowRjRKFtxZvh7W4PNdcnupx3lRW0B
6r8/MnNxjZzl9BlxwmWoTT/ajdLuJ85l3ywSbV2K8JaTVuJ+GG8FqVofZ8tw/1pb
btMUzrwy++L5urJyMGbh1GHpdJp32Bu8dAB3TCEMqarF+M5P9vWNJfdRxEwprz0=
=i1Kr
-----END PGP SIGNATURE-----

--Apple-Mail=_05327F0C-68E5-4D2A-A413-A92F92A181E5--

From kent@bbn.com  Tue Jan  7 10:40:50 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F731AE104 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ToB2YP5Jnkzk for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:40:48 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id AFFAB1AE069 for <ietf@ietf.org>; Tue,  7 Jan 2014 10:40:48 -0800 (PST)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:50607) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1W0bZv-000B6g-D6 for ietf@ietf.org; Tue, 07 Jan 2014 13:40:39 -0500
Message-ID: <52CC4A27.3090208@bbn.com>
Date: Tue, 07 Jan 2014 13:40:39 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Split the IANA functions?
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com>
In-Reply-To: <52CB987A.20300@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 18:40:50 -0000

Eliot,
>
> Why do we state that confidentiality is important to pursue in our
> protocols?  That is a political decision made by the community.  We then
> layer on top of that decision technical requirements.  IMHO it's a very
> important and good political decision.
Confidentiality is not an IETF-specific notion.  Long ago (mid-80's) the
ISO published a doc, ISO 7498-2, which describes security services and
mechanisms. That doc defines confidentiality as a security service, and
encryption as a mechanism that can be used to implement the service.

The same doc defines authentication, (data) integrity, access control
and other security services, with several variants of each service to
be more precise. It also includes a description of numerous security
mechanisms.  While 7498-2 is not perfect, it does demonstrate that a
large community (after all, it's an ISO doc) viewed these services as
generally desirable characteristics for communication systems. Thus
when the IETF says (as we did long ago in 3552) that confidentiality
(and authentication and integrity) are good things, we are consistent
with long-established principles that extend far beyond our standards
environment.

I see the political aspect of our current discussion as how we choose to
make tradeoffs between the security and privacy aspects of our protocols,
vs. other aspects of protocol design and network operation. Stephen's
doc does not address these tradeoffs in any detail. So, if we avoid terms
(near the end of the doc) that might appear to establish the rules for
evaluating these tradeoffs, we can make a statement that is not perceived
as political. Most means of effecting PM are attacks, as per 3552. This
ought not be viewed as a debate relative to our previous docs. I'd
prefer if this doc noted that, and explained what aspects of PM don't
neatly fall under the old threat model, thus providing a motivation for
a new threat model.  That way this doc can be seen a a simple statement of
the consensus from Vancouver, and an indication that the IETF has plans
to address concerns about PM, as established by the consensus.

Steve

From jari.arkko@piuha.net  Tue Jan  7 10:44:57 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A5731AE11B for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:44:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUiwrO-kzX_A for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:44:55 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE511AE122 for <ietf@ietf.org>; Tue,  7 Jan 2014 10:44:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 458362CC5D; Tue,  7 Jan 2014 20:44:42 +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 NjLnxaUQrQ3r; Tue,  7 Jan 2014 20:44:41 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id EC2C12CC48; Tue,  7 Jan 2014 20:44:40 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last call debate on draft-farrell-perpass-attack
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <015901cf0bc3$72bb75d0$58326170$@olddog.co.uk>
Date: Tue, 7 Jan 2014 10:44:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B505AB7-E810-447A-B423-8381AE6E4A5B@piuha.net>
References: <015901cf0bc3$72bb75d0$58326170$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 18:44:57 -0000

Thanks, Adrian - this matches pretty closely my own thoughts as well, =
but you put it in very clear words.

And to be honest - we do see over-eager ADs at times (as we sometimes =
also see over-eager authors, chairs, or working groups=85) and I've been =
over-eager myself at times. Hopefully less often nowadays with more =
perspective. We all make mistakes. But I've yet to witness a situation =
where reasonable discussion could not resolve the situation, not to =
mention the availability of appeals, nomcom comments, recalls, etc. In =
any case, as Adrian points out, this document provides no tools for a =
misbehaving person to use as an argument.

Jari


From narten@us.ibm.com  Tue Jan  7 10:48:35 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 195091AE112 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jx4flJz5rmWo for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:48:33 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id CD1361AE069 for <ietf@ietf.org>; Tue,  7 Jan 2014 10:48:32 -0800 (PST)
Received: from /spool/local by e8.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, 7 Jan 2014 13:48:23 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Tue, 7 Jan 2014 13:48:21 -0500
Received: from b01cxnp23032.gho.pok.ibm.com (b01cxnp23032.gho.pok.ibm.com [9.57.198.27]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 50B1E38C8045 for <ietf@ietf.org>; Tue,  7 Jan 2014 13:48:20 -0500 (EST)
Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by b01cxnp23032.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s07ImKH35571036 for <ietf@ietf.org>; Tue, 7 Jan 2014 18:48:20 GMT
Received: from d01av05.pok.ibm.com (localhost [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s07ImJqB017349 for <ietf@ietf.org>; Tue, 7 Jan 2014 13:48:20 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-118-133.mts.ibm.com [9.65.118.133]) by d01av05.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s07ImIPq017258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Jan 2014 13:48:19 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s07ImHqx004058; Tue, 7 Jan 2014 13:48:18 -0500
Message-Id: <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: DNS heirarchy, multiple roots, etc [was Re: Split the IANA functions?]
In-reply-to: <20140107173942.GE11538@mx1.yitter.info>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com> <20140107173942.GE11538@mx1.yitter.info>
Comments: In-reply-to Andrew Sullivan <ajs@anvilwalrusden.com> message dated "Tue, 07 Jan 2014 12:39:42 -0500."
Date: Tue, 07 Jan 2014 13:48:17 -0500
From: Thomas Narten <narten@us.ibm.com>
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14010718-0320-0000-0000-0000021FB2FE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 18:48:35 -0000

+1 to Andrew's comments.

To further emphasize a key point, the core issue is that the DNS *name
space* is hierarchical. That has nothing to do with roots and how
things are implemented underneath the covers. The name space itself is
hierarchical -- that is where the "mathematics" come in.

That means that someone or something has to decide what names are
allowed at the top of the hierarchy. That means you have to have some
entitity (e.g., ICANN) that says ".com" is OK, ".bozo" is not.

Sure, one can come up with all sorts of clever
schemes/algorithms/processes for deciding what names should be allowed
(and who owns them), but fundamentally, someone or something has to
decide (e.g., you need an ICANN). And I can guarantee you that no
matter how the decision is made, someone or some group will scream
"not fair", "corrupt", etc., etc. when they aren't able to get their
name.

So any talk about having a different/better naming scheme is really
just wishful thinking and a mostly a waste of everybody's time. If
there was a better system, some set of smart folk would surely have
already clued the rest of us in on what that was. Anyone remember Tim
Bass?

Thomas

Andrew Sullivan <ajs@anvilwalrusden.com> writes:

> On Tue, Jan 07, 2014 at 11:29:04AM -0500, Phillip Hallam-Baker wrote:
> > It didn't have to be a tree, it could have been something else, we could
> > still change it.

> Gee, Phill, I love it when people elide the exact point I made when
> selectively quoting, and then chide me for not having made that point.

> Yes, it could be something else.  In the logically-possible world in
> which I am a mud puddle, I spend less time responding to emails about
> the nature of naming on the Internet.  But both the naming system on
> the Internet and I (perhaps unhappily for one of us) exist in this
> world.  The Internet as it stands uses the DNS, a tree-structured name
> space.  A tree-structured name space has, by definition, a unique
> root, due to the math in this universe.[1],[2]

> > Describing this as having a single root conflates a large number of issues
> > and essentially commits to a particular conclusion. A uniform namespace is
> > a requirement, a single 'root' is not.

> I wasn't claiming a single root is a requirement for a uniform name
> space; I don't care about that question.  I was suggesting that, given
> that we have the DNS and it is the name system that is actually
> deployed, we have right now a requirement for a unique root in that
> name system.  If you want to make up a new non-DNS naming system and
> deploy it and get the world to use it, please go nuts.  I have plenty
> of complaints about the DNS and the way it works.  I suggest that the
> history of IPv6 deployment prior to the actual exhaustion of the IPv4
> number space gives us a pretty good lesson in the likelihood of non-DNS
> global naming taking off without some killer feature.  In my opinion,
> "Doesn't make Vladimir Putin grumpy," is unlikely to be the killer
> feature that will cause people to change whatever invisible naming
> system they use to bootstrap the applications on their tablets or find
> Google or Bing.

> Best regards,

> A
>  

> [1] To acknowledge Avri's point elsewhere in this thread, yes, it is
> possible to have a different CLASS with different RDATA at the name
> owner name and RRTYPE.  The name space is still tree shaped with a
> unique root, in that the owner names persist across all CLASSes.  This
> is perhaps not quite as obvious as one would like in RFCs 1034, 1035,
> and maybe 2181.  DNSEXT attempted to do something about this a few
> years ago, but we didn't get any traction so we gave up. 

> It is undoubtedly the case that there was some reason people didn't do
> something about the difficulties with CLASSes.  One of the explanations,
> of course, is that if we were going to fix the DNS at that basic a
> level, we might as well replace it completely with something else that
> doesn't have the properties we'd be trying to repair.

> [2] I refuse to have a position on whether there is a logically
> possible world in which mathematical tree structures do not by
> definition have a single root.  Possible-worlds semantics over
> mathematical proofs was probably too hard for me when I actually did
> possible-worlds semantics work, and by now I've forgotten most of that
> Latin.

> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com


From derhoermi@gmx.net  Tue Jan  7 10:55:24 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1CA1ADBC9 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UW6pF5yCb40E for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 10:55:22 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id ECBC81AD935 for <ietf@ietf.org>; Tue,  7 Jan 2014 10:55:21 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.17.224]) by mail.gmx.com (mrgmx101) with ESMTPA (Nemesis) id 0Lat5o-1VYAoZ3KIK-00kMCr for <ietf@ietf.org>; Tue, 07 Jan 2014 19:55:12 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice (StW)
Date: Tue, 07 Jan 2014 19:55:08 +0100
Message-ID: <b1joc99kjai99hhtrdgf1q4mbhesl6bned@hive.bjoern.hoehrmann.de>
References: <CEF0A2FD.3ED34%stewe@stewe.org> <52CC00EA.70404@cs.tcd.ie>
In-Reply-To: <52CC00EA.70404@cs.tcd.ie>
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-Provags-ID: V03:K0:EpbidX5DLy86PK98g9Lu9JsDYmLAmyA1kYhrZTCSUba9M8nfTML emcHtbfK5bcKcOBEEYdJJhRnltEtTQZy8WqTjbnCv5AsQXNhylrp5YDXSp+skcfwKdnGMbi AWTTWkF7G9LemQlT+eg+11n6XZNvNibem1adjTSoamz5fOnEW1syme5gTIrXSxGyUtHiyVR iRdzHLrwV0Uat8/0O8WaQ==
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 18:55:24 -0000

* Stephen Farrell wrote:
>I see. So you're all for hacking into Belagcom then? I'm sure they'll
>be a little sad to hear that. Esp. if the next attacker is not a
>government agency.

Sounds like a Belgian spy master calling for more pervasive monitoring.
-- 
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 worley@shell01.TheWorld.com  Tue Jan  7 11:09:31 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A381AE124 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HY3ETsJv9bjI for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:09:30 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id EA81B1AE123 for <ietf@ietf.org>; Tue,  7 Jan 2014 11:09:29 -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 s07J9H3B021729; Tue, 7 Jan 2014 14:09:20 -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 s07J9HeI2338042; Tue, 7 Jan 2014 14:09:17 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s07J9HIc2337165; Tue, 7 Jan 2014 14:09:17 -0500 (EST)
Date: Tue, 7 Jan 2014 14:09:17 -0500 (EST)
Message-Id: <201401071909.s07J9HIc2337165@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: TGLASSEY <tglassey@earthlink.net>
In-reply-to: <52C9C7B6.9000705@earthlink.net> (tglassey@earthlink.net)
Subject: Re: IETF Specification for FREE SPEECH BOX, a device designed for covert access of the Internet to post key information
References: <52C9C7B6.9000705@earthlink.net>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 19:09:31 -0000

> From: TGLASSEY <tglassey@earthlink.net>
> 
> Since the IETF is moving into use of its protocols and standards I want 
> to propose an interesting potential here - its for the creation of a WG 
> who's work product would be a system to provide covert web-based access 
> to a thing called a Free Speech Platform.

The obvious question is whether there is a significant number of
people interested on working on it.

The less obvious question is whether there would be any standards
generated, as opposed to generating a software system.  (Software
system projects are not done by the IETF, but there are other
organizations that do that.)

Dale

From paf@frobbit.se  Tue Jan  7 11:20:38 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABF681AE139 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:20:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rpan2UJuzA5J for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:20:36 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 847871AE13A for <ietf@ietf.org>; Tue,  7 Jan 2014 11:20:36 -0800 (PST)
Received: from [IPv6:2a02:80:3ffc::2087:3375:684d:61f8] (unknown [IPv6:2a02:80:3ffc:0:2087:3375:684d:61f8]) by mail.frobbit.se (Postfix) with ESMTPSA id 369CF1FFF3; Tue,  7 Jan 2014 20:20:25 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_E50D8ACC-195A-48D5-9DDE-56D084D271A9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: DNS heirarchy, multiple roots, etc [was Re: Split the IANA functions?]
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com>
Date: Tue, 7 Jan 2014 20:20:24 +0100
Message-Id: <F1995B65-C462-45CB-A761-FD325FC77697@frobbit.se>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com> <20140107173942.GE11538@mx1.yitter.info> <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 19:20:38 -0000

--Apple-Mail=_E50D8ACC-195A-48D5-9DDE-56D084D271A9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 7 jan 2014, at 19:48, Thomas Narten <narten@us.ibm.com> wrote:

> So any talk about having a different/better naming scheme is really
> just wishful thinking and a mostly a waste of everybody's time. If
> there was a better system, some set of smart folk would surely have
> already clued the rest of us in on what that was. Anyone remember Tim
> Bass?

On top of that (if you look at some arguments that "change is needed") I =
would like to know what the problem really is. And yes, I am happy(?) =
to, and have tried to, understand what the problem is.

As others have explained, often "the problem" has to do with =
misunderstanding of how Internet and DNS works. In other cases it has to =
do with real issues, like the actual decision making process for what =
strings can exist.

When knowing what the problem is, there is often not much disagreement =
on the fact improvements can be made. But more disagreements in what the =
best path forward is. But THAT discussion is much more fruitful and =
effective than just saying "things must change".

   Patrik


--Apple-Mail=_E50D8ACC-195A-48D5-9DDE-56D084D271A9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSzFN4rMabGguI180RAoZJAJ9CtsF7zFatT3wZkRQPHSQ0MqdPawCgkSVf
v/HC624qCRfuwUVFEd2u+pY=
=Ab2r
-----END PGP SIGNATURE-----

--Apple-Mail=_E50D8ACC-195A-48D5-9DDE-56D084D271A9--

From gih@apnic.net  Tue Jan  7 11:21:06 2014
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3F31AE142 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:21:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhushmvoSP_3 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 11:21:04 -0800 (PST)
Received: from so-mailgw.apnic.net (so-mailgw.apnic.net [IPv6:2001:dd8:a:3::230]) by ietfa.amsl.com (Postfix) with SMTP id 710931AE13B for <ietf@ietf.org>; Tue,  7 Jan 2014 11:21:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path; bh=dkQ0BiAAUeCDmvV9nJpRhzCcStBoSCoGjemzKMghMkM=; b=rOhNUCV8s+sqQfdsAcdHxIg/2C05ML+DKwGXSH29KsxOCEQ7G8PAgcr7uHdiTk9JdI9RGlkn0a0YR PAvFBXBNzQWQgJKkbR1EHzI3XmBFPu+kmtr0N4/7R9HWkjBDub/Ty3AtYky22bYTB+Pe4N1xk8mgqH pL2thDFZBkcidtlo=
Received: from NXMDA1.org.apnic.net (unknown [203.119.93.247]) by so-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Wed,  8 Jan 2014 05:20:50 +1000 (EST)
Received: from [10.100.1.12] (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 8 Jan 2014 05:20:50 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org>
Date: Wed, 8 Jan 2014 06:20:46 +1100
Content-Transfer-Encoding: quoted-printable
Message-ID: <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 19:21:06 -0000

> Specific comments:
>=20
> Section 2.1, second paragraph:
>=20
>   The allocation and registration functions for all non-reserved AS
>   numbers are handled by the Internet Numbers Registry System in
>   accordance with policies developed by the Regional Internet
>   Registries (RIRs).
>=20
> I might suggest:
>=20
> "The allocation and registration functions for all non-reserved AS =
numbers are currently handled by the Internet Numbers Registry System in =
accordance with policies developed via the Regional Internet Registries' =
(RIRs) public policy development processes."
>=20
> Section 2.2, first paragraph:
>=20
>   The allocation and registration functions for all non-reserved
>   globally unique unicast IPv4 unicast addresses are handled by the
>   Internet Numbers Registry System in accordance with policies
>   developed by the Regional Internet Registries (RIRs).
>=20
> Similar to the previous suggestion (dropping a redundant 'unicast'):
>=20
> "The allocation and registration functions for all non-reserved =
globally unique unicast IPv4 addresses are currently handled by the =
Internet Numbers Registry System in accordance with policies developed =
via the RIRs' public policy development processes."
>=20
> Section 2.3, second paragraph:
>=20
>   The allocation and registration functions for all non-reserved
>   globally unique unicast IPv6 unicast addresses are handled by the
>   Internet Numbers Registry System in accordance with policies
>   developed by the Regional Internet Registries (RIRs).
>=20
> Similar to the previous suggestion (also dropping a redundant =
'unicast'):
>=20
> "The allocation and registration functions for all non-reserved =
globally unique unicast IPv6 addresses are currently handled by the =
Internet Numbers Registry System in accordance with policies developed =
via the RIRs' public policy development processes."


In all three cases you are proposing to change "are handled" to "are =
currently handled"

Could you kindly explain the rationale for this proposed change in =
wording, as the subtle distinction between the two terms is, I'm afraid, =
somewhat lost on me.

regards,

   Geoff



From dhc@dcrocker.net  Tue Jan  7 12:00:41 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE8F1AE1E7 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6cVzLmMfV6iz for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:00:39 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0FDB71AE1A9 for <ietf@ietf.org>; Tue,  7 Jan 2014 12:00:34 -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 s07JxqJc019952 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Jan 2014 11:59:55 -0800
Message-ID: <52CC5C57.4040902@dcrocker.net>
Date: Tue, 07 Jan 2014 11:58:15 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux> <CAF4+nEHDNC-aQCY6r1zceb=7hOW4JmfnMWDWZSEM6gJLTSDF9Q@mail.gmail.com> <01P2V8MN121I0000AS@mauve.mrochek.com>
In-Reply-To: <01P2V8MN121I0000AS@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.66]); Tue, 07 Jan 2014 11:59:55 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 07 Jan 2014 20:00:41 -0000

On 1/7/2014 8:52 AM, ned+ietf@mauve.mrochek.com wrote:
> I find this document to be too vague to function properly as a BCP, and I don't
> think we have a sufficient understanding of the tradeoffs involved in making
> pervasive monitoring more difficult to write a proper BCP at the present time.
> And if anything, hasty and ill-considered changes may make monitoring easier,
> not harder.
>
> I think the course advocated by Dave Crocker is the correct one: Publish this
> as an informational policy statement, and then work through the policy on
> subsequent specifications. Then, once we believe we have a sufficient grasp of
> how this actually plays out, write a BCP. (Dave, I think this summarizes your
> position, but if not, apologies for getting it wrong.)


I've advocated Experimental, though I've thought Informational would 
also be ok.  On further reflection from people's comment, I now think 
Informational would be the sufficient and safer choice.

The more important issue is that the draft does usefully introduce the 
topic of PM to IETF work.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From drc@virtualized.org  Tue Jan  7 12:03:52 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5091AE17E for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:03:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t3S96uDcVmaE for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:03:51 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0E91AE18D for <ietf@ietf.org>; Tue,  7 Jan 2014 12:03:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 176C184B42; Tue,  7 Jan 2014 15:03:38 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 99529-01; Tue,  7 Jan 2014 15:03:36 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id E976784CED; Tue,  7 Jan 2014 15:03:34 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_16D429B6-66E9-4E3C-AC3D-5DC441464B9A"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net>
Date: Tue, 7 Jan 2014 12:03:30 -0800
Message-Id: <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:03:52 -0000

--Apple-Mail=_16D429B6-66E9-4E3C-AC3D-5DC441464B9A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Geoff,

On Jan 7, 2014, at 11:20 AM, Geoff Huston <gih@apnic.net> wrote:
> In all three cases you are proposing to change "are handled" to "are =
currently handled"

Yep.

> Could you kindly explain the rationale for this proposed change in =
wording, as the subtle distinction between the two terms is, I'm afraid, =
somewhat lost on me.

RFC 7020 describes the Internet Numbers Registry as it exists today and =
talks about the evolution system, indicating that the system "can evolve =
to meet the changing demands of the global Internet community."  As this =
draft bills itself as a companion to 7020, indicating that the various =
allocation and registration functions are _currently_ performed by the =
RIRs (implying that this might change in the future as the system =
evolves) seems appropriate.  I've found (particularly with experiences =
related to RFC 2050) that is is useful to be explicit about the =
distinction between "current" and an implied "permanent".

Regards,
-drc


--Apple-Mail=_16D429B6-66E9-4E3C-AC3D-5DC441464B9A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSzF2TAAoJENV6ebf0/4rXzfwIAIwnirdQmQw0BARQm4aQokAF
miNE0bdKYl8dkgtbe/fsmpBdJ6mBc84bG7eTBwSQLSY7nxcXZvICbYrvdGqVCNc/
EaS6SHz5DeL+tYV0JZDYE7oyCRXjWrWxHkYxwy4As3o/knNZ4AdEw+ICxBUWShvz
O8zb4vgJ6UEHEmUmBglXEYA5AOXVeOiuGe6d4Zq5zltLjBRGZ6cLpV5FWpvIiqc3
69HOFRppi/YkmEF/HrLoNiJAyX0SZndor1Q6Z9M7cvp5iiytpeVe9ZcW8pVxP4xB
Q986bUiWbmCYaac1VTkmqK00ienDfOIcbQntCEWq6awdvbKbFmsUtN6l+nRaPtI=
=M6ij
-----END PGP SIGNATURE-----

--Apple-Mail=_16D429B6-66E9-4E3C-AC3D-5DC441464B9A--

From gih@apnic.net  Tue Jan  7 12:13:08 2014
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B28FF1AE188 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pOP6Le12wOv for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 12:13:06 -0800 (PST)
Received: from so-mailgw.apnic.net (so-mailgw.apnic.net [IPv6:2001:dd8:a:3::230]) by ietfa.amsl.com (Postfix) with SMTP id 491061AE15D for <ietf@ietf.org>; Tue,  7 Jan 2014 12:13:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path; bh=g26Yn3sdAI0RhQPnSK7IlAysROovc8deu0CvluZh/gw=; b=6zF75J9zQBxzwZY0L0p75Gn1uZX8IT8lGabDWoQCS2/fEH3gJk4uIMN3tJMpjb4CXIIP0J9NXREIb mbqpkEA8nQAiGpgVqEnJ3r6afgYjKCgYifPakABEmEEMiAM5WY/xQSgY5U6HH89BWP7RxGiuE77j3d bqAfvtW4b/vORnaE=
Received: from NXMDA1.org.apnic.net (unknown [203.119.93.247]) by so-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Wed,  8 Jan 2014 06:12:53 +1000 (EST)
Received: from [10.100.1.12] (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 8 Jan 2014 06:12:53 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org>
Date: Wed, 8 Jan 2014 07:12:49 +1100
Content-Transfer-Encoding: quoted-printable
Message-ID: <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net> <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 20:13:08 -0000

On 8 Jan 2014, at 7:03 am, David Conrad <drc@virtualized.org> wrote:

> Geoff,
>=20
> On Jan 7, 2014, at 11:20 AM, Geoff Huston <gih@apnic.net> wrote:
>> In all three cases you are proposing to change "are handled" to "are =
currently handled"
>=20
> Yep.
>=20
>> Could you kindly explain the rationale for this proposed change in =
wording, as the subtle distinction between the two terms is, I'm afraid, =
somewhat lost on me.
>=20
> RFC 7020 describes the Internet Numbers Registry as it exists today =
and talks about the evolution system, indicating that the system "can =
evolve to meet the changing demands of the global Internet community."  =
As this draft bills itself as a companion to 7020, indicating that the =
various allocation and registration functions are _currently_ performed =
by the RIRs (implying that this might change in the future as the system =
evolves) seems appropriate.  I've found (particularly with experiences =
related to RFC 2050) that is is useful to be explicit about the =
distinction between "current" and an implied "permanent".


I'm reminded of a discussion (probably on this list) some time ago when =
kre reminded me that all RFCs can be updated or obsoleted in the future =
by subsequent RFCs. I read this draft in a different sense, in that the =
text in this draft is a description of a here and now state of affairs =
that will presumably exist in the future until updated or obsoleted by a =
subsequent RFC, much the same as the fate of RFC2050 I suppose.

regards,
   Geoff




From simon@josefsson.org  Tue Jan  7 14:45:35 2014
Return-Path: <simon@josefsson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46EE51AE21B for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 14:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.648
X-Spam-Level: 
X-Spam-Status: No, score=0.648 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5oCWPxmPUjso for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 14:45:33 -0800 (PST)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) by ietfa.amsl.com (Postfix) with ESMTP id 32FC51AE211 for <ietf@ietf.org>; Tue,  7 Jan 2014 14:45:32 -0800 (PST)
Received: from latte.josefsson.org (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id s07MjJjo026199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Jan 2014 23:45:21 +0100
Date: Tue, 7 Jan 2014 23:45:18 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Patrik =?ISO-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>
Subject: Re: Necrotizing Fasciitis
Message-ID: <20140107234518.1bf460a7@latte.josefsson.org>
In-Reply-To: <C3617134-D9F2-4B79-AD72-313CA0BCAC5E@frobbit.se>
References: <20140104235058.5b9ec017@latte.josefsson.org> <C3617134-D9F2-4B79-AD72-313CA0BCAC5E@frobbit.se>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/Xo73oKPXqWBlzwGNU9CrzMz"; protocol="application/pgp-signature"
X-Virus-Scanned: clamav-milter 0.97.8 at duva.sjd.se
X-Virus-Status: Clean
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 22:45:35 -0000

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

Thank you Patrik.  The prognosis is good, so you won't get rid of me
that easily. :-)

/Simon

You wrote:

> On 4 jan 2014, at 23:50, Simon Josefsson <simon@josefsson.org> wrote:
>=20
> > If anyone wonders why they haven't received any responses from me
> > lately, below is the answer.
> >=20
> > http://blog.josefsson.org/2014/01/05/necrotizing-fasciitis/
>=20
> Simon,
>=20
> Correct priorities. Take care of you, your family and your friends.
> There is always time for work later, when you feel ready.
>=20
> Best,
>=20
>    Patrik
>=20


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

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

iQEcBAEBAgAGBQJSzIN+AAoJEGDO5xEQXnIuQjAIAIyOTD/qBH5NkKwYDlN7e2PZ
6NdmGKwbreaoBQ70Zb0ZZmq5/m6+T6FBXTXeergs8lqAgr8gr2vEsIeLOPN1Rhyg
2ujNDhCV7q8JI0pjnf72GA5eZbpZ9Xhb3XmNDVitu/QLOqbO4QUM2/LrEyVyjYBI
/239YcAjCak3Iyqgz4TkB9GBEdnorfmJg+1CEvGSRag/KxfFxTpoHRRIwNed0eM0
aQtvvJJNh/HPrXL3xAUunhg8c/sg6Cxq3n3C66fSChAV3WrK00sX/7x9zVBsRdDr
hvsFBedCDq5k5JHvLnyQ8ItZDvIRJDMhW0InmNnMHR3F9K600vFIKfqsEWunVYQ=
=mbWx
-----END PGP SIGNATURE-----

--Sig_/Xo73oKPXqWBlzwGNU9CrzMz--

From john-ietf@jck.com  Tue Jan  7 15:00:12 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5431AE0DA for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 15:00:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.838
X-Spam-Level: 
X-Spam-Status: No, score=-2.838 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MpsO7ynrRNZk for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 15:00:10 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 30FC61AE015 for <ietf@ietf.org>; Tue,  7 Jan 2014 15:00:10 -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 1W0fcs-000604-70; Tue, 07 Jan 2014 17:59:58 -0500
Date: Tue, 07 Jan 2014 17:59:53 -0500
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>, Thomas Narten <narten@us.ibm.com>
Subject: Re: DNS heirarchy, multiple roots, etc [was Re: Split the IANA functions?]
Message-ID: <C73014CDDA02050C322DC7F9@JcK-HP8200.jck.com>
In-Reply-To: <F1995B65-C462-45CB-A761-FD325FC77697@frobbit.se>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com> <20140107173942.GE11538@mx1.yitter.info> <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com> <F1995B65-C462-45CB-A761-FD325FC77697@frobbit.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 23:00:12 -0000

--On Tuesday, January 07, 2014 20:20 +0100 Patrik =
F=C3=A4ltstr=C3=B6m
<paf@frobbit.se> wrote:

> On 7 jan 2014, at 19:48, Thomas Narten <narten@us.ibm.com>
> wrote:
>=20
>> So any talk about having a different/better naming scheme is
>> really just wishful thinking and a mostly a waste of
>> everybody's time. If there was a better system, some set of
>> smart folk would surely have already clued the rest of us in
>> on what that was. Anyone remember Tim Bass?
>=20
> On top of that (if you look at some arguments that "change is
> needed") I would like to know what the problem really is. And
> yes, I am happy(?) to, and have tried to, understand what the
> problem is.
>=20
> As others have explained, often "the problem" has to do with
> misunderstanding of how Internet and DNS works. In other cases
> it has to do with real issues, like the actual decision making
> process for what strings can exist.
>=20
> When knowing what the problem is, there is often not much
> disagreement on the fact improvements can be made. But more
> disagreements in what the best path forward is. But THAT
> discussion is much more fruitful and effective than just
> saying "things must change".

While agreeing with this and with most of Thomas's and Andrew's
comments, I think there are a few substantive problems that can
be easily identified and that keep coming back (I do not
consider arguments about who controls the root of a strict
hierarchy to be substantive, no matter how entertaining they
become).   Most of them are associated with expectations of the
DNS that it, as a strictly hierarchical system with one name per
node, one-way links, and fairly weak aliases, cannot satisfy. =20

For example, we see repeated requests (or "requirements",
demands, or fantasies) about treating two (or more) names as so
identical that retrievals or actions that affect one of them
affect the others.  It is certainly within the state of the art
to do that in a strictly hierarchical  system.  Hierarchical
database and file systems with support for those relationships
have been around for close to 50 years if not longer.  But it
isn't a modification that can be patched into the DNS -- it just
isn't going to happen without replacing the DNS.  Some of the
people who make those requests can be educated; others prefer to
believe that, if only they repeat their demands often enough and
loudly enough, they will get their way.

Similarly, we see repeated requests (etc.) for search and
matching systems that are context-dependent based on either
locations in the hierarchy or hints/ specifications stored in
the hierarchy itself.  Again, it is possible to design a
hierarchical system to do that but almost certainly not possible
to retrofit it into the current DNS. =20

There are other examples, typically involving other types of
search and matching procedures, that can't be done in the DNS
because they are incompatible with a strict hierarchy.  Using
them would either require replacing the DNS with something
entirely different (and probably less suitable for unique
identifiers of network objects) or layering a separate system on
top of the DNS (depending on one's perspective, it could be
argued that contemporary search engines serve that role and the
problem is solved).

I suggest that the things that these examples and others have in
common are:

(i) They cannot be realized within the DNS as we know it, even
if some hypothetical replacement system could accommodate some
or all of them.

(ii) Under the best of circumstances, deploying a replacement
system would be a long, slow, and painful process.  Independent
of the difficulty of deploying such a system (including thinking
through transition issues), it is almost certain that taking
advantage of the requested features of a new system would
require different parameters in the query/lookup process and
that would, in turn, require updating every application on the
Internet.

(iii) The people advocating the changes implied by those
examples are either ignorant of the reasons for (i) and (ii) or
aren't willing to admit to and deal with those reasons.

(iv) When we have tried to stimulate interest in the community
about various solutions and approaches, including the "above
DNS" ones that are, IMO, the most plausible from a deployment
and adoption standpoint, we generally discover that there isn't
any such interest, especially once people understand what would
actually be involved.

best,
   john


From drc@virtualized.org  Tue Jan  7 16:07:03 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4809D1AE247 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 16:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 035f2mydpXWq for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 16:07:01 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 39BC41AE0DA for <ietf@ietf.org>; Tue,  7 Jan 2014 16:07:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id CF0DE84CED; Tue,  7 Jan 2014 19:06:51 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 01607-02; Tue,  7 Jan 2014 19:06:51 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 6700984B42; Tue,  7 Jan 2014 19:06:49 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_61ED3424-3CF6-49E4-9E09-F7406DBD4162"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net>
Date: Tue, 7 Jan 2014 16:06:47 -0800
Message-Id: <438A344B-28FE-40E5-B04C-7ED5A0815B60@virtualized.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net> <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org> <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 00:07:03 -0000

--Apple-Mail=_61ED3424-3CF6-49E4-9E09-F7406DBD4162
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Geoff,

On Jan 7, 2014, at 12:12 PM, Geoff Huston <gih@apnic.net> wrote:
> I'm reminded of a discussion (probably on this list) some time ago =
when kre reminded me that all RFCs can be updated or obsoleted in the =
future by subsequent RFCs.

True, albeit whether their being updated/obsoleted in a timely matter is =
a separate issue (noting 2050, published in 1996, didn't get moved to =
Historic until 2013 despite questionable relevance of a majority of text =
in that RFC to the current allocation system).

>  I read this draft in a different sense, in that the text in this =
draft is a description of a here and now state of affairs that will =
presumably exist in the future until updated or obsoleted by a =
subsequent RFC, much the same as the fate of RFC2050 I suppose.

And my suggested edits merely makes the point explicit that this is the =
case. I believe minimizing ambiguity in RFCs is a good thing. I have =
seen/experienced far too many cases of "As is written in the Holy 2050" =
as justification to feel comfortable in relying on people reading the =
draft/RFC 'correctly'.

Regards,
-drc




--Apple-Mail=_61ED3424-3CF6-49E4-9E09-F7406DBD4162
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSzJaXAAoJENV6ebf0/4rXYl8IAPF93ZN8RJpMIMk+1xf1Y7xI
E0reJjTI7efC1JXDdplMzL3hz/kl/IxmqqWi7+7UbuzKK9SLvGD+jl248K6G5pvp
28Z8zC29coV39etsMucx99S4mQVMr+YO6DrKQv/sEgEz9x2QvrPfw9KZ0vaXPlJA
U6JKTunnGvJHBBPBfeQUqSEutDZK6dn8z6eUSO/xNPQroJKpA6G2Z+3+MCZAwUre
yoXFYG2gopR3xLq+CqhOZUUGktL0HPfIMSFUVKWNo6lqKheZnjtmC/oCe2U1U0oG
JBgSeFM1N+EB1ELGxyiAEKveq9HigdaQmGlsyzp6k9hiZeV14utoaKTzR5oGIaE=
=SF3S
-----END PGP SIGNATURE-----

--Apple-Mail=_61ED3424-3CF6-49E4-9E09-F7406DBD4162--

From gih@apnic.net  Tue Jan  7 16:55:51 2014
Return-Path: <gih@apnic.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB0021AE267 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 16:55:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WdstQX9ay3-T for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 16:55:50 -0800 (PST)
Received: from so-mailgw.apnic.net (so-mailgw.apnic.net [IPv6:2001:dd8:a:3::230]) by ietfa.amsl.com (Postfix) with SMTP id 863A11AE262 for <ietf@ietf.org>; Tue,  7 Jan 2014 16:55:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path; bh=M07vlI2d3sd1TrIe8ZUsKdCCCs/za1e2mJVtT5ysnRs=; b=Zfak0/TLhDlJtqp93M93+7Ni0MCfM6AHpTvxzZkEatk6D5Fzua3vzkzQmcxbDF4jHj1Uo+ILwqm/w sI93aFA6xnb6Ti9pNHC61CQybPX6CQVi+zY7Fly+IUDTPRsgG3WTZDddVbyloEHhVJoIqleTGNc8rP KPOwmyAyAr/u3cgE=
Received: from NXMDA1.org.apnic.net (unknown [203.119.93.247]) by so-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Wed,  8 Jan 2014 10:55:36 +1000 (EST)
Received: from [100.46.117.84] (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Wed, 8 Jan 2014 10:55:34 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <438A344B-28FE-40E5-B04C-7ED5A0815B60@virtualized.org>
Date: Wed, 8 Jan 2014 11:55:27 +1100
Content-Transfer-Encoding: quoted-printable
Message-ID: <AB92F2C0-161F-451A-9125-230EA02B16D9@apnic.net>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net> <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org> <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net> <438A344B-28FE-40E5-B04C-7ED5A0815B60@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 00:55:52 -0000

On 8 Jan 2014, at 11:06 am, David Conrad <drc@virtualized.org> wrote:

> Geoff,
>=20
> On Jan 7, 2014, at 12:12 PM, Geoff Huston <gih@apnic.net> wrote:
>> I'm reminded of a discussion (probably on this list) some time ago =
when kre reminded me that all RFCs can be updated or obsoleted in the =
future by subsequent RFCs.
>=20
> True, albeit whether their being updated/obsoleted in a timely matter =
is a separate issue (noting 2050, published in 1996, didn't get moved to =
Historic until 2013 despite questionable relevance of a majority of text =
in that RFC to the current allocation system).
>=20
>> I read this draft in a different sense, in that the text in this =
draft is a description of a here and now state of affairs that will =
presumably exist in the future until updated or obsoleted by a =
subsequent RFC, much the same as the fate of RFC2050 I suppose.
>=20
> And my suggested edits merely makes the point explicit that this is =
the case. I believe minimizing ambiguity in RFCs is a good thing. I have =
seen/experienced far too many cases of "As is written in the Holy 2050" =
as justification to feel comfortable in relying on people reading the =
draft/RFC 'correctly'.
>=20

ok - I guess it's style - I prefer the shorter version with the common =
understanding that NO RFC is written in the ink of eternal truth, but I =
can live with either.

regards,

  Geoff



From hallam@gmail.com  Tue Jan  7 17:14:51 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 834651AE18B for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 17:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DrbrEGBqBDPo for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 17:14:49 -0800 (PST)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id CB0691AE107 for <ietf@ietf.org>; Tue,  7 Jan 2014 17:14:48 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id mc6so671196lab.26 for <ietf@ietf.org>; Tue, 07 Jan 2014 17:14:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nZ0zPtf5HzEa6V4qD75BTXeo6b0bHILNwdpGfDIlPxg=; b=mjGFZ+dx0yuinBGjRk5JbreFIZ7PDc4T4sBifMIOXSzrDS5eyoLCOBpwOmDo1wa+ty d1Vxj0BBmBkdOqGCNN3DUbGNFXoomKzep5eA+l29DshCYFzNoj4EaJiBA8V4HcZNJolh zU4VAThr/56IcEHIh1tSrtcTg+bUV+lbA0dsxOyYn7S0kdrefq1PjLVFn8/6OKtvGJFq pMepqwop5y/oJALqA0KJdsW8yu8atE4wJ97vX1IoFnWfeCmLptRMu0YYcJjDYYVX/u1d b5IOGLi+o2pyUiLJgJ3O9c8py+QX4C499nzgsQVDJbzaVv8Sha8Wn4kVuuzDyu6Rz039 0J3Q==
MIME-Version: 1.0
X-Received: by 10.112.201.197 with SMTP id kc5mr3816803lbc.64.1389143679104; Tue, 07 Jan 2014 17:14:39 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Tue, 7 Jan 2014 17:14:39 -0800 (PST)
In-Reply-To: <C73014CDDA02050C322DC7F9@JcK-HP8200.jck.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com> <20140107173942.GE11538@mx1.yitter.info> <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com> <F1995B65-C462-45CB-A761-FD325FC77697@frobbit.se> <C73014CDDA02050C322DC7F9@JcK-HP8200.jck.com>
Date: Tue, 7 Jan 2014 20:14:39 -0500
Message-ID: <CAMm+LwiO6hw8-qm_o6U6xEHV91zC=4fUK9_8YuTC4mjGSACUJw@mail.gmail.com>
Subject: Re: DNS heirarchy, multiple roots, etc [was Re: Split the IANA functions?]
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c2662e88facc04ef6b376f
Cc: Thomas Narten <narten@us.ibm.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 01:14:51 -0000

--001a11c2662e88facc04ef6b376f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 7, 2014 at 5:59 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, January 07, 2014 20:20 +0100 Patrik F=E4ltstr=F6m
> <paf@frobbit.se> wrote:
>
> > On 7 jan 2014, at 19:48, Thomas Narten <narten@us.ibm.com>
> > wrote:
> >
> >> So any talk about having a different/better naming scheme is
> >> really just wishful thinking and a mostly a waste of
> >> everybody's time. If there was a better system, some set of
> >> smart folk would surely have already clued the rest of us in
> >> on what that was. Anyone remember Tim Bass?
> >
> > On top of that (if you look at some arguments that "change is
> > needed") I would like to know what the problem really is. And
> > yes, I am happy(?) to, and have tried to, understand what the
> > problem is.
> >
> > As others have explained, often "the problem" has to do with
> > misunderstanding of how Internet and DNS works. In other cases
> > it has to do with real issues, like the actual decision making
> > process for what strings can exist.
> >
> > When knowing what the problem is, there is often not much
> > disagreement on the fact improvements can be made. But more
> > disagreements in what the best path forward is. But THAT
> > discussion is much more fruitful and effective than just
> > saying "things must change".
>
> While agreeing with this and with most of Thomas's and Andrew's
> comments, I think there are a few substantive problems that can
> be easily identified and that keep coming back (I do not
> consider arguments about who controls the root of a strict
> hierarchy to be substantive, no matter how entertaining they
> become).   Most of them are associated with expectations of the
> DNS that it, as a strictly hierarchical system with one name per
> node, one-way links, and fairly weak aliases, cannot satisfy.
>

That is a much better argument.

What I was trying to object to is the use of 'mathematical possibility' as
a slapdown as if the design of the DNS were so perfect that anyone
proposing an alternative approach is a complete fool.

That sort of argument can work inside IETF but it looks really bad when it
is made in an external forum where the audience does not start from the
same assumptions as to what is immutable fact.


The choices are constrained by the legacy technical infrastructure and the
requirements.



> For example, we see repeated requests (or "requirements",
> demands, or fantasies) about treating two (or more) names as so
> identical that retrievals or actions that affect one of them
> affect the others.  It is certainly within the state of the art
> to do that in a strictly hierarchical  system.  Hierarchical
> database and file systems with support for those relationships
> have been around for close to 50 years if not longer.  But it
> isn't a modification that can be patched into the DNS -- it just
> isn't going to happen without replacing the DNS.  Some of the
> people who make those requests can be educated; others prefer to
> believe that, if only they repeat their demands often enough and
> loudly enough, they will get their way.
>

This is a better statement but the statement suggests that the problem is
only in the DNS infrastructure when the problem is also with the clients
that try to make lookups. For names to be useful, they have to work
predictably which means that at minimum they need to work the same with
every app on a given machine. Changes to the semantics of names will only
take effect after all the clients that perform recursive DNS resolution are
updated. And there are many of those now.

Yes, making two names look the same is also an example of the general cache
coherency problem, but Soviet science may believe it has an answer to that.



--=20
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jan 7, 2014 at 5:59 PM, John C Klensin <span dir=3D"ltr">&l=
t;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.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 Tuesday, January 07, 2014 20:20 +0100 Patrik F=E4ltstr=F6m<br>
<div><div class=3D"h5">&lt;<a href=3D"mailto:paf@frobbit.se">paf@frobbit.se=
</a>&gt; wrote:<br>
<br>
&gt; On 7 jan 2014, at 19:48, Thomas Narten &lt;<a href=3D"mailto:narten@us=
.ibm.com">narten@us.ibm.com</a>&gt;<br>
&gt; wrote:<br>
&gt;<br>
&gt;&gt; So any talk about having a different/better naming scheme is<br>
&gt;&gt; really just wishful thinking and a mostly a waste of<br>
&gt;&gt; everybody&#39;s time. If there was a better system, some set of<br=
>
&gt;&gt; smart folk would surely have already clued the rest of us in<br>
&gt;&gt; on what that was. Anyone remember Tim Bass?<br>
&gt;<br>
&gt; On top of that (if you look at some arguments that &quot;change is<br>
&gt; needed&quot;) I would like to know what the problem really is. And<br>
&gt; yes, I am happy(?) to, and have tried to, understand what the<br>
&gt; problem is.<br>
&gt;<br>
&gt; As others have explained, often &quot;the problem&quot; has to do with=
<br>
&gt; misunderstanding of how Internet and DNS works. In other cases<br>
&gt; it has to do with real issues, like the actual decision making<br>
&gt; process for what strings can exist.<br>
&gt;<br>
&gt; When knowing what the problem is, there is often not much<br>
&gt; disagreement on the fact improvements can be made. But more<br>
&gt; disagreements in what the best path forward is. But THAT<br>
&gt; discussion is much more fruitful and effective than just<br>
&gt; saying &quot;things must change&quot;.<br>
<br>
</div></div>While agreeing with this and with most of Thomas&#39;s and Andr=
ew&#39;s<br>
comments, I think there are a few substantive problems that can<br>
be easily identified and that keep coming back (I do not<br>
consider arguments about who controls the root of a strict<br>
hierarchy to be substantive, no matter how entertaining they<br>
become). =A0 Most of them are associated with expectations of the<br>
DNS that it, as a strictly hierarchical system with one name per<br>
node, one-way links, and fairly weak aliases, cannot satisfy.<br></blockquo=
te><div><br></div><div>That is a much better argument.</div><div><br></div>=
<div>What I was trying to object to is the use of &#39;mathematical possibi=
lity&#39; as a slapdown as if the design of the DNS were so perfect that an=
yone proposing an alternative approach is a complete fool.</div>
<div><br></div><div>That sort of argument can work inside IETF but it looks=
 really bad when it is made in an external forum where the audience does no=
t start from the same assumptions as to what is immutable fact.</div><div>
<br></div><div><br></div><div>The choices are constrained by the legacy tec=
hnical infrastructure and the requirements.=A0</div><div><br></div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">

For example, we see repeated requests (or &quot;requirements&quot;,<br>
demands, or fantasies) about treating two (or more) names as so<br>
identical that retrievals or actions that affect one of them<br>
affect the others. =A0It is certainly within the state of the art<br>
to do that in a strictly hierarchical =A0system. =A0Hierarchical<br>
database and file systems with support for those relationships<br>
have been around for close to 50 years if not longer. =A0But it<br>
isn&#39;t a modification that can be patched into the DNS -- it just<br>
isn&#39;t going to happen without replacing the DNS. =A0Some of the<br>
people who make those requests can be educated; others prefer to<br>
believe that, if only they repeat their demands often enough and<br>
loudly enough, they will get their way.<br></blockquote><div><br></div><div=
>This is a better statement but the statement suggests that the problem is =
only in the DNS infrastructure when the problem is also with the clients th=
at try to make lookups. For names to be useful, they have to work predictab=
ly which means that at minimum they need to work the same with every app on=
 a given machine. Changes to the semantics of names will only take effect a=
fter all the clients that perform recursive DNS resolution are updated. And=
 there are many of those now.</div>
<div><br></div><div>Yes, making two names look the same is also an example =
of the general cache coherency problem, but Soviet science may believe it h=
as an answer to that.</div><div><br></div></div><div><br></div><div><br>
</div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambake=
r.com/</a><br>
</div></div>

--001a11c2662e88facc04ef6b376f--

From l.wood@surrey.ac.uk  Tue Jan  7 20:32:38 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 025951AE2BE for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 20:32:38 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4S3KSxMtP5EJ for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 20:32:35 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id 700B61AE2BA for <ietf@ietf.org>; Tue,  7 Jan 2014 20:32:35 -0800 (PST)
Received: from [195.245.230.131:15664] by server-2.bemta-3.messagelabs.com id 07/CA-17329-9D4DCC25; Wed, 08 Jan 2014 04:32:25 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-78.messagelabs.com!1389155544!22096893!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30718 invoked from network); 8 Jan 2014 04:32:25 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-2.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jan 2014 04:32:25 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 8 Jan 2014 04:32:24 +0000
From: <l.wood@surrey.ac.uk>
To: <jari.arkko@piuha.net>, <adrian@olddog.co.uk>
Date: Wed, 8 Jan 2014 04:31:35 +0000
Subject: RE: Last call debate on draft-farrell-perpass-attack
Thread-Topic: Last call debate on draft-farrell-perpass-attack
Thread-Index: Ac8L2J566WAfoCiYS8SS83g99IcfOAAUeXix
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346AA@EXMB01CMS.surrey.ac.uk>
References: <015901cf0bc3$72bb75d0$58326170$@olddog.co.uk>, <3B505AB7-E810-447A-B423-8381AE6E4A5B@piuha.net>
In-Reply-To: <3B505AB7-E810-447A-B423-8381AE6E4A5B@piuha.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 04:32:38 -0000

> In any case, as Adrian points out, this document provides no tools for a =
misbehaving person to use as an argument.

which clearly says 'not BCP, this is informational' to me.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Jari Arkko [jari.arkko@piuh=
a.net]
Sent: 07 January 2014 18:44
To: adrian@olddog.co.uk
Cc: ietf@ietf.org
Subject: Re: Last call debate on draft-farrell-perpass-attack

Thanks, Adrian - this matches pretty closely my own thoughts as well, but y=
ou put it in very clear words.

And to be honest - we do see over-eager ADs at times (as we sometimes also =
see over-eager authors, chairs, or working groups=85) and I've been over-ea=
ger myself at times. Hopefully less often nowadays with more perspective. W=
e all make mistakes. But I've yet to witness a situation where reasonable d=
iscussion could not resolve the situation, not to mention the availability =
of appeals, nomcom comments, recalls, etc. In any case, as Adrian points ou=
t, this document provides no tools for a misbehaving person to use as an ar=
gument.

Jari


From garbakora@gmail.com  Tue Jan  7 23:42:10 2014
Return-Path: <garbakora@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FBAD1AE313; Tue,  7 Jan 2014 23:42:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8GFU-5Bnz9Y; Tue,  7 Jan 2014 23:42:09 -0800 (PST)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 11D801AE30D; Tue,  7 Jan 2014 23:42:08 -0800 (PST)
Received: by mail-qc0-f179.google.com with SMTP id i8so1178267qcq.10 for <multiple recipients>; Tue, 07 Jan 2014 23:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y84hJ6qNnfABqQg5BhWnAN9F21dA+2lrnCuDSV0Wpbg=; b=B0rfJvgqXSodpvUI3sRe7f8Mi6Uua1W4Y0Gal/cFBgVQOpJXrny3XmhdvtJIEx/JJG +mQtY4ad7An34D5Ptb+/KNEUrbspoHb2foCL2eHSWrIRmBuDutvIp5ztZQHdrt4lBxrN 7NbGapEZ0qLWNTnmK4FTI3Utl/PaIvEsBvrC1WFpe7J9vgmFvxbzGWHkYDkd2ZvYhj36 MBTrJ62KtFapnopqTFM6io0IECCb8euTuWkLk+/il5Xvcy2Lzuk15tpTwMMcM4BrmlKw HFGrg2cHl8RRJ/cFQywaqIsYppveaMjFpHp4XI7pk5gYzsCGO6lSDnVqINJrjx+BI2xW DOqw==
MIME-Version: 1.0
X-Received: by 10.49.48.69 with SMTP id j5mr205231311qen.71.1389166919825; Tue, 07 Jan 2014 23:41:59 -0800 (PST)
Received: by 10.96.133.202 with HTTP; Tue, 7 Jan 2014 23:41:59 -0800 (PST)
In-Reply-To: <20140106183110.21204.41408.idtracker@ietfa.amsl.com>
References: <20140106183110.21204.41408.idtracker@ietfa.amsl.com>
Date: Wed, 8 Jan 2014 08:41:59 +0100
Message-ID: <CA+bJALpDij1ToFsQXtJoMM+mmmYFY=N0f_hRLkNGVJa2CBOz1w@mail.gmail.com>
Subject: Re: WG Action: Conclusion of ADSL MIB (adslmib)
From: GARBA KORA TAMSIRD BELLO <garbakora@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: adslmib@ietf.org, IETF Announcement List <ietf-announce@ietf.org>, menachemdodge1@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 07:42:10 -0000

hello every one just to say i want discrive to this mailing.
i do not want to receive any message .

sincerely yours

2014/1/6, IESG Secretary <iesg-secretary@ietf.org>:
> The ADSL MIB (adslmib) Working Group in the Operations and Management
> Area has concluded. The IESG contact persons are Benoit Claise and Joel
> Jaeggli.
>
> The mailing list will remain open.
>

From lars@netapp.com  Wed Jan  8 02:21:50 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3441AE1D2; Wed,  8 Jan 2014 02:21:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CX4kapA9sL_D; Wed,  8 Jan 2014 02:21:48 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A21701AE1D9; Wed,  8 Jan 2014 02:21:47 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,623,1384329600";  d="asc'?scan'208";a="94680269"
Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx11-out.netapp.com with ESMTP; 08 Jan 2014 02:21:38 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Wed, 8 Jan 2014 02:21:38 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: IETF <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMA
Date: Wed, 8 Jan 2014 10:21:37 +0000
Message-ID: <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com>
In-Reply-To: <20140102151419.4692.48031.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_36C4746D-8644-40AC-AC97-DAF2E1204EE1"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 10:21:50 -0000

--Apple-Mail=_36C4746D-8644-40AC-AC97-DAF2E1204EE1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> - 'Encapsulating MPLS in UDP'
>  <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard


this document needs to describe how it addresses the issues raised in =
BCP145 (RFC5405). It already contains some text about messages sizes and =
congestion considerations, which is great. Unfortunately, the text about =
congestion considerations is not fully in line with RFC5405.

Lars

--Apple-Mail=_36C4746D-8644-40AC-AC97-DAF2E1204EE1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUs0msNZcnpRveo1xAQJmVgP/Ru+CWqFvoJjk+SPEXBDvVhBIAafFlril
t49xr5u64LhTLeFxjtLGX41P1mitCFWV5euqgi2ixkpxIP9OxfCpMKAqLUF/o6/w
GL6hw/fa5gB8yCiOBr3/H4h4HyNNJOGm66i7Y30Q5PhGSPhnr/E5essJBwHq9pZb
kO+3844idqY=
=2mpd
-----END PGP SIGNATURE-----

--Apple-Mail=_36C4746D-8644-40AC-AC97-DAF2E1204EE1--

From mariainesrobles@googlemail.com  Wed Jan  8 04:04:26 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D26501AE34B for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 04:04:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyzeLOpaQCev for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 04:04:25 -0800 (PST)
Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 534681AE2AA for <ietf@ietf.org>; Wed,  8 Jan 2014 04:04:25 -0800 (PST)
Received: by mail-wg0-f54.google.com with SMTP id n12so1365509wgh.9 for <ietf@ietf.org>; Wed, 08 Jan 2014 04:04:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=HuycS/8cZfw70UxuK3oL4r1pLXegDjwDKgmM+9Tqm8M=; b=a26ZfJck9oZyL8Vyau9nzpKjqFP3xkBDQRXB18uovGRnTNbiigwl4tf9rq9nPzbrL8 GhPEFWjaoLxceKrxC8H8F9UT5ufC4oZZkcy+e+C68Ee63ulcNSYgVM3TxuklUOrd151V Zpv40sNj5A4NJZcVE2L7pH7mYB5NGVtqCDVwQeyMs2CUgIv7Y8VAnnVesouOJVox2BJh kRtUt4BePBdHbb82tbbbf/Lpq5+ent4gYnTRW7+xIE1mn0CA1V72G4vUQprADbb8tmVr 1LfCeCzz0g9skELRh7YhKzwHDekw2oUW3b/R6rKmIJdqk7RiirvxnH3FwXVNC+pD//aC zG3w==
MIME-Version: 1.0
X-Received: by 10.180.13.74 with SMTP id f10mr20980525wic.34.1389182655751; Wed, 08 Jan 2014 04:04:15 -0800 (PST)
Received: by 10.216.44.144 with HTTP; Wed, 8 Jan 2014 04:04:15 -0800 (PST)
Date: Wed, 8 Jan 2014 10:04:15 -0200
Message-ID: <CAP+sJUdEK1kni3PqwzfnAykQpxsFUsxUr2p8MPQmQR-9S_pvog@mail.gmail.com>
Subject: I-D Action: draft-moonesamy-ietf-conduct-3184bis-06
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c24a94b9697a04ef744aba
Cc: S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 12:04:27 -0000

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

Hello,

A new version has been submitted for draft-moonesamy-ietf-conduct-3184bis.

Please any comments are very welcome,

Kind Regards,

Ines Robles.

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

[http://www.ietf.org/mail-archive/web/i-d-announce/current/msg55777.html]

A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : IETF Guidelines for Conduct
        Author          : S. Moonesamy
	Filename        : draft-moonesamy-ietf-conduct-3184bis-06.txt
	Pages           : 6
	Date            : 2014-01-06

Abstract:
   This document provides a set of guidelines for personal interaction
   in the Internet Engineering Task Force.  The guidelines recognize the
   diversity of IETF participants, emphasize the value of mutual
   respect, and stress the broad applicability of our work.

   This document is an updated version of the guidelines for conduct
   originally published in RFC 3184.


The IETF datatracker status page for this draft
is:https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/

There's also a htmlized version available
at:http://tools.ietf.org/html/draft-moonesamy-ietf-conduct-3184bis-06

A diff from the previous version is available
at:http://www.ietf.org/rfcdiff?url2=draft-moonesamy-ietf-conduct-3184bis-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP
at:ftp://ftp.ietf.org/internet-drafts/

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

<div dir=3D"ltr">Hello,<div><br></div><div style>A new version=A0<span styl=
e=3D"font-family:arial,sans-serif;font-size:13px">has been submitted for dr=
aft-moonesamy-ietf-conduct-</span><span style=3D"font-family:arial,sans-ser=
if;font-size:13px">3184bis.</span></div>
<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Please any comments are very welcome,</span></div><div style><span=
 style=3D"font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">Kind Regards,</span></div><div style><span style=3D"font-family:ar=
ial,sans-serif;font-size:13px"><br></span></div><div style><span style=3D"f=
ont-family:arial,sans-serif;font-size:13px">Ines Robles.</span></div>
<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><span style=3D"font-family:arial,sans-serif;font-si=
ze:13px">------------------------------------------------------------------=
----------------------------------------------</span></div>
<div style><span style=3D"font-family:arial,sans-serif;font-size:13px"><br>=
</span></div><div style><pre style=3D"color:rgb(0,0,0)">[<a href=3D"http://=
www.ietf.org/mail-archive/web/i-d-announce/current/msg55777.html">http://ww=
w.ietf.org/mail-archive/web/i-d-announce/current/msg55777.html</a>]</pre>
<pre style=3D"color:rgb(0,0,0)">A New Internet-Draft is available from the =
on-line Internet-Drafts directories.


        Title           : IETF Guidelines for Conduct
        Author          : S. Moonesamy
	Filename        : draft-moonesamy-ietf-conduct-3184bis-06.txt
	Pages           : 6
	Date            : 2014-01-06

Abstract:
   This document provides a set of guidelines for personal interaction
   in the Internet Engineering Task Force.  The guidelines recognize the
   diversity of IETF participants, emphasize the value of mutual
   respect, and stress the broad applicability of our work.

   This document is an updated version of the guidelines for conduct
   originally published in RFC 3184.


The IETF datatracker status page for this draft is:
<a rel=3D"nofollow" href=3D"https://datatracker.ietf.org/doc/draft-moonesam=
y-ietf-conduct-3184bis/">https://datatracker.ietf.org/doc/draft-moonesamy-i=
etf-conduct-3184bis/</a>

There&#39;s also a htmlized version available at:
<a rel=3D"nofollow" href=3D"http://tools.ietf.org/html/draft-moonesamy-ietf=
-conduct-3184bis-06">http://tools.ietf.org/html/draft-moonesamy-ietf-conduc=
t-3184bis-06</a>

A diff from the previous version is available at:
<a rel=3D"nofollow" href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-moones=
amy-ietf-conduct-3184bis-06">http://www.ietf.org/rfcdiff?url2=3Ddraft-moone=
samy-ietf-conduct-3184bis-06</a>


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org">tools.ietf.org</a>.

Internet-Drafts are also available by anonymous FTP at:
<a rel=3D"nofollow" href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.=
ietf.org/internet-drafts/</a>
</pre><div><br></div></div></div>

--001a11c24a94b9697a04ef744aba--

From suzworldwide@gmail.com  Wed Jan  8 05:06:13 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC221AE390 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 05:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xoM89UyEzh1r for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 05:06:11 -0800 (PST)
Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD581AE382 for <ietf@ietf.org>; Wed,  8 Jan 2014 05:06:10 -0800 (PST)
Received: by mail-qc0-f180.google.com with SMTP id w7so1339118qcr.11 for <ietf@ietf.org>; Wed, 08 Jan 2014 05:06:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6oY3MB1pQVNdb1eQhsARqkPLEScCvGpyePOiHofFOvI=; b=UfpcWjtdq6iMrar/nrOD+C9dBoEa2gX/3V9dFqWhoT6tbNRryYwy4DfhIXl2Sxo02G TxZ1w2XIsIMdYKXsKFy/02mprJ1BqjWH+1AKJUaZEw/vEGqFshM8meJuQqvp9TqpZ4AK KUfCnU45RSjY+ojg3t/p8jc059toETknQujPmh0NYkDNnaLD1382R2gE8cGPdkbeJE02 WJMbMBkSbCi4bJUOjZj3ic23foOkb9jMWePY/TeZMiB0MraU8iYx3RxtenF/P2hVbjrn FNfRLLqsMI+S+VYMMZLvxan/Ud5IKAGlXxKaRdRUYRFgMHH6+ar7GV+1xH0chEDPtKfr 6f0g==
X-Received: by 10.49.34.167 with SMTP id a7mr8223091qej.25.1389186361815; Wed, 08 Jan 2014 05:06:01 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id g10sm882424qaf.9.2014.01.08.05.06.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 05:06:01 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: DNS heirarchy, multiple roots, etc [was Re: Split the IANA functions?]
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <CAMm+LwiO6hw8-qm_o6U6xEHV91zC=4fUK9_8YuTC4mjGSACUJw@mail.gmail.com>
Date: Wed, 8 Jan 2014 08:06:00 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D50A2FC8-88B8-4482-99E9-9C23B3E9F1DE@gmail.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <CAMm+Lwiqtsp13NeR0kXeWaN3SAn7856_5VtopwMP1JWw0ohzVg@mail.gmail.com> <20140107173942.GE11538@mx1.yitter.info> <201401071848.s07ImHqx004058@cichlid.raleigh.ibm.com> <F1995B65-C462-45CB-A761-FD325FC77697@frobbit.se> <C73014CDDA02050C322DC7F9@JcK-HP8200.jck.com> <CAMm+LwiO6hw8-qm_o6U6xEHV91zC=4fUK9_8YuTC4mjGSACUJw@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: John C Klensin <john-ietf@jck.com>, Thomas Narten <narten@us.ibm.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?windows-1252?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 13:06:13 -0000

Colleagues,=20

On the DNS discussion generally: I respectfully suggest it tends to be =
more productive if we are careful with terminology, in distinguishing =
among different facets or aspects of DNS.

1.There=92s no hard limit on the number of physical devices or diverse =
locations where we can put nameservers to provide the service (IP-based =
anycast). There=92s probably a limit beyond which adding more service =
points adds to administrative overhead without improving the service. I =
haven=92t done the math; I suspect someone has, most likely a large DNS =
or CDN operator. The constraints on where they're measurably useful are =
also driven by operational concerns like available connectivity, which =
in the case of the root are tied to the contents of the zone and other =
larger policy concerns but very indirectly.

2. There=92s a functional limit in the DNS to how many NS records one =
can have for a zone. It may be meaningful to say that number is larger =
than 13 for the root, now, if one assumes widespread usefulness of EDNS0 =
(essentially, full penetration e2e of the ability to handle larger =
packet sizes than originally specified in the DNS, since we have to be =
careful about the implementation details of response truncation, packet =
sizes, etc.), but there=92s still likely an upper bound. There are also =
protocol consequences to selecting which NS set to share for a zone as a =
subset of possible ones (answers won=92t always be consistent). Those =
are protocol issues, and not specific to the root. (The operational =
limitation above is also relevant to the number of NS records/service =
points, in that at some point the nth new service point is measurably =
useful and the n+1=92th isn=92t.) This is primarily a matter of the DNS =
protocol, and the IETF is where people work on the protocol.

3. What people are usually talking about when they argue about =
=93alternate roots=94 is not how many servers or how many named service =
points we can have, which are operational and protocol matters, but the =
namespace=97 what goes in the tree, where, with what characteristics, =
and who decides. And traditionally, this is where IANA is most directly =
involved, and generally where the strictly policy-based tussles ICANN =
engages in appear. The way we=92ve structured DNS data, including =
certain of its key advantages, there=92s one such namespace, and bad =
things (relative to the original requirements, which seem to persist to =
a very meaningful degree today) start to happen if it=92s fragmented or =
inconsistent. As John's comments note, there are also other =
characteristics of the namespace, chosen early, that have had =
significant policy consequences. Some are easily separable from the =
on-the-wire protocol and operational considerations; some aren't.=20

We can discuss any or all of these things in the context of IANA and the =
root, but I suspect that the discussion will be more useful if we make =
some distinctions among them. Otherwise we=92ll continue to have a world =
where, for example, people believe that having control of a named =
service point for DNS resolution service for the root of the namespace =
gives them some meaningful degree of control over what=92s in the =
namespace as it appears in the public or global context, even though as =
a matter of both protocol and operations, that=92s simply not true.

It's also probably useful to have further discussion in another venue. =
The DNSOP WG is meant for discussions/work on DNS operational =
characteristics, scalability, best practices, etc. The DNSEXT WG is =
closed but there's still a mailing list, probably best suited for =
protocol discussion on DNS.=20

best,
Suzanne

On Jan 7, 2014, at 8:14 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:
>=20
> What I was trying to object to is the use of 'mathematical =
possibility' as a slapdown as if the design of the DNS were so perfect =
that anyone proposing an alternative approach is a complete fool.
>=20
> That sort of argument can work inside IETF but it looks really bad =
when it is made in an external forum where the audience does not start =
from the same assumptions as to what is immutable fact.
>=20
>=20
> The choices are constrained by the legacy technical infrastructure and =
the requirements.=20


From tglassey@earthlink.net  Tue Jan  7 13:19:13 2014
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33AFC1AE1F9 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 13:19:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBc0I5vpJDy6 for <ietf@ietfa.amsl.com>; Tue,  7 Jan 2014 13:19:11 -0800 (PST)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id 9FBCC1AE1CF for <ietf@ietf.org>; Tue,  7 Jan 2014 13:19:11 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=kc4h8g3Z+9SMOVidVN/j1TnFcTIBjsh5n5kqQY4jWgVCAJykJhWnXC6/T+vWrZye; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.134.155] (helo=[192.168.0.4]) by elasmtp-mealy.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1W0e3C-0000SY-2d; Tue, 07 Jan 2014 16:19:02 -0500
Message-ID: <52CC6F4E.4060906@earthlink.net>
Date: Tue, 07 Jan 2014 13:19:10 -0800
From: TGLASSEY <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: IETF Specification for FREE SPEECH BOX, a device designed for covert access of the Internet to post key information
References: <52C9C7B6.9000705@earthlink.net> <201401071909.s07J9HIc2337165@shell01.TheWorld.com>
In-Reply-To: <201401071909.s07J9HIc2337165@shell01.TheWorld.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec798f2b6e368e8ddd27a6a1d74167eff165350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.134.155
X-Mailman-Approved-At: Wed, 08 Jan 2014 08:03:01 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jan 2014 21:19:13 -0000

On 1/7/2014 11:09 AM, Dale R. Worley wrote:
>> From: TGLASSEY <tglassey@earthlink.net>
>>
>> Since the IETF is moving into use of its protocols and standards I want
>> to propose an interesting potential here - its for the creation of a WG
>> who's work product would be a system to provide covert web-based access
>> to a thing called a Free Speech Platform.
> The obvious question is whether there is a significant number of
> people interested on working on it.
>
> The less obvious question is whether there would be any standards
> generated, as opposed to generating a software system.  (Software
> system projects are not done by the IETF, but there are other
> organizations that do that.)
>
> Dale
>
>
The French for instance mandate legal access to the Internet. In the 
real world that means an electrical process and access to ports 80 and 
443 based http at a minimum one would think.

The issue here is really more of whether the IETF wants to extend its 
footprint into systems as some WG's have started forays into.


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

Personal Email - Disclaimers Apply


From bclaise@cisco.com  Wed Jan  8 08:37:37 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 726A51ADFA2; Wed,  8 Jan 2014 08:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.038
X-Spam-Level: 
X-Spam-Status: No, score=-15.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qNPuDoV9PZy; Wed,  8 Jan 2014 08:37:34 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id A18631ADF38; Wed,  8 Jan 2014 08:37:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14663; q=dns/txt; s=iport; t=1389199044; x=1390408644; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=6U/PsXVSETmYL7arIobnuTBRtQrJgHV2eOdSAL04grg=; b=LwKnvfoKckjvAc4zKQSphobltQPC41kwEGyf67/zj3oR38twYGbVH3oa x1U5iMXcOB+MYyLJf0dpaYBQqNDjIyFK1f9fx0bc0StKizg3kB0/P3URY VzP8RoCH2febRN7/tbfruCi2bt6h8mM+mDoKrZ+z8lwyYlKxH0SpgD6Ym Y=;
X-IronPort-AV: E=Sophos;i="4.95,625,1384300800"; d="scan'208,217";a="37834655"
Received: from vla196-nat.cisco.com (HELO bgl-core-3.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 08 Jan 2014 16:37:19 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by bgl-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s08GbHWS027175; Wed, 8 Jan 2014 16:37:18 GMT
Message-ID: <52CD7EBD.4090506@cisco.com>
Date: Wed, 08 Jan 2014 17:37:17 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: NETMOD Working Group <netmod@ietf.org>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database YANG Module) to Proposed Standard
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com>
In-Reply-To: <52A1ACEF.6080307@cisco.com>
Content-Type: multipart/alternative; boundary="------------040502070305050605050600"
Cc: SM <sm@resistor.net>, Paul Eggert <eggert@cs.ucla.edu>, IETF-Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 16:37:37 -0000

This is a multi-part message in MIME format.
--------------040502070305050605050600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

Sadly, I have not seen a reply to this one.
So let me start the discussion, copying both the ietf-discussion and the 
netmod WG mailers.
See in-line.
> Dear all,
>
> Here is some feedback from the IETF discussion list.
> I would appreciate if the author and document shepherd could follow 
> up. Ideally on the IETF discussion list.
>
> Regards, Benoit
>
>
> -------- Original Message --------
> Subject: 	Re: Last Call: <draft-ietf-netmod-iana-timezones-03.txt> 
> (IANA Timezone Database YANG Module) to Proposed Standard
> Date: 	Tue, 3 Dec 2013 19:36:31 -0800
> From: 	SM <sm@resistor.net>
> To: 	<ietf@ietf.org>
>
>
>
> At 12:46 03-12-2013, The IESG wrote:
> >The IESG has received a request from the NETCONF Data Modeling Language
> >WG (netmod) to consider the following document:
> >- 'IANA Timezone Database YANG Module'
> >   <draft-ietf-netmod-iana-timezones-03.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-12-17. Exceptionally, comments may be
>
> There is the following question in the document shepherd write-up:
>
>    Why is this the proper type of RFC?
>
> I did not see an answer to that question.
Not sure what you propose here. Proposed Standard seems right to me.
 From http://www.rfc-editor.org/RFCoverview.html


        RFC Categories

    Each RFC has a "category" or "status" designation. The possible
    categories (see *RFC 2026*
    <http://www.rfc-editor.org/rfc/rfc2026.txt> "The Internet Standards
    Process -- Revision 3") are:

      * INTERNET STANDARD, DRAFT STANDARD (deprecated; see RFC 6410
        <http://www.rfc-editor.org/rfc/rfc6410.txt>), PROPOSED STANDARD

        These are /Standards Track/ documents, official specifications
        of the Internet protocol suite defined by the Internet
        Engineering Task Force (IETF) <http://www.ietf.org> and its
        steering group the IESG.

      * BEST CURRENT PRACTICE

        These are official guidelines and recommendations, but not
        standards, from the IETF.

      * INFORMATIONAL, EXPERIMENTAL

        These non-standards documents may originate in the IETF or may
        be independent submissions.

      * HISTORIC

        These are former standards that have been actively deprecated.

>
> The WGLC was from 5 July to 22 July.  There wasn't any comments
> during the WGLC.  The only comment I found was one posted on 9 August.
>
> In Section 1:
>
>    "The iana-timezones YANG module defines the iana-
>     timezone type, which is a serialization of the existing IANA Time
>     Zone registry [RFC6557] into YANG format."
>
> The terminology in RFC 6557 defines a TZ Database sometimes referred
> to as the "Olson Database".  There isn't any mention of a "IANA Time
> Zone registry".  I suggest using the same name as in RFC 6557.
That makes sense.
>
> >From Section 3:
>
>    'The iana-timezones module is intended to reflect the IANA "timezone
>     database" [RFC6557].  When a timezone location is added to the
>     database, the "iana-timezone" enumeration MUST be updated as defined
>     in RFC 6020 Section 10 to add the newly created timezone location to
>     the enumeration.  The new "enum" statement MUST be added to the
>     "iana-timezone" typedef with the same name as the newly added
>     timezone location.  A new enum value MUST be allocated by IANA and
>     applied to the newly created enum entry.  New entries MAY be placed
>     in any order in the enumeration as long as the previously assigned
>     enumeration values are not changed.
>
>     If a timezone location is removed from the IANA timezone database,
>     the corresponding existing enum statement is kept and a status
>     statement is added to mark the enum entry as 'obsolete'.'
>
> The maintainer of the TZ database is responsible for the TZ
> Database.  The person does not work for IANA.
Correct, but see BCP 175: Procedures for Maintaining the Time Zone Database:
<http://www.iana.org/go/rfc6557>

    The TZ Coordinator is an IANA Designated Expert

Are you questioning the term "IANA timezone database", which should be "TZ Database" according to BCP 175?

> I don't think that
> IANA keeps track of the contents of the TZ Database as it was not
> asked to do that work.
I think it does: http://www.iana.org/time-zones
> I don't see the value of using RFC 2119 key
> word for the IANA Considerations.

>
> I suggest not creating the registry proposed in this draft.  The TZ
> database has strived to keep out of political issues.  Adding such a
> registry will pave the way for such issues.
Well, we need to specify the system clock in the following YANG module 
(https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/), and 
hence we require a way to represent the TZ in YANG.

Regards, Benoit
>
> Regards,
> -sm
>
> .
>
>
>
>
>
> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod


--------------040502070305050605050600
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Dear all,<br>
      <br>
      Sadly, I have not seen a reply to this one.<br>
      So let me start the discussion, copying both the ietf-discussion
      and the netmod WG mailers.<br>
      See in-line.<br>
    </div>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      Dear all,<br>
      <br>
      Here is some feedback from the IETF discussion list.<br>
      I would appreciate if the author and document shepherd could
      follow up. Ideally on the IETF discussion list.<br>
      <br>
      Regards, Benoit<br>
      <div class="moz-forward-container"><br>
        <br>
        -------- Original Message --------
        <table class="moz-email-headers-table" cellpadding="0"
          cellspacing="0" border="0">
          <tbody>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:

              </th>
              <td>Re: Last Call:
                &lt;draft-ietf-netmod-iana-timezones-03.txt&gt; (IANA
                Timezone Database YANG Module) to Proposed Standard</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date:
              </th>
              <td>Tue, 3 Dec 2013 19:36:31 -0800</td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From:
              </th>
              <td>SM <a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:sm@resistor.net">&lt;sm@resistor.net&gt;</a></td>
            </tr>
            <tr>
              <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
              <td><a moz-do-not-send="true"
                  class="moz-txt-link-rfc2396E"
                  href="mailto:ietf@ietf.org">&lt;ietf@ietf.org&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <pre>At 12:46 03-12-2013, The IESG wrote:
&gt;The IESG has received a request from the NETCONF Data Modeling Language
&gt;WG (netmod) to consider the following document:
&gt;- 'IANA Timezone Database YANG Module'
&gt;   &lt;draft-ietf-netmod-iana-timezones-03.txt&gt; as Proposed Standard
&gt;
&gt;The IESG plans to make a decision in the next few weeks, and solicits
&gt;final comments on this action. Please send substantive comments to the
&gt;<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2013-12-17. Exceptionally, comments may be

There is the following question in the document shepherd write-up:

  Why is this the proper type of RFC?

I did not see an answer to that question.</pre>
      </div>
    </blockquote>
    Not sure what you propose here. Proposed Standard seems right to me.<br>
    From <a class="moz-txt-link-freetext" href="http://www.rfc-editor.org/RFCoverview.html">http://www.rfc-editor.org/RFCoverview.html</a><br>
    <blockquote>
      <h2><a name="categories">RFC Categories</a></h2>
      <p>
        Each RFC has a "category" or "status" designation. The possible
        categories
        (see <a href="http://www.rfc-editor.org/rfc/rfc2026.txt"><b>RFC
            2026</b></a> "The Internet Standards Process -- Revision 3")
        are:
      </p>
      <ul>
        <li>
          INTERNET STANDARD, DRAFT STANDARD (deprecated;
          see <a href="http://www.rfc-editor.org/rfc/rfc6410.txt">RFC
            6410</a>), PROPOSED STANDARD
          <p>
            These are <i>Standards Track</i> documents, official
            specifications of
            the Internet protocol suite defined by the
            <a href="http://www.ietf.org">Internet Engineering Task
              Force
              (IETF)</a>
            and its steering group the IESG.
          </p>
        </li>
        <li>
          BEST CURRENT PRACTICE
          <p>
            These are official guidelines and recommendations, but not
            standards, from the IETF.
          </p>
        </li>
        <li>
          INFORMATIONAL, EXPERIMENTAL
          <p>
            These non-standards documents may originate in the IETF or
            may be
            independent submissions.
          </p>
        </li>
        <li>
          HISTORIC
          <p>
            These are former standards that have been actively
            deprecated.
          </p>
        </li>
      </ul>
    </blockquote>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>

The WGLC was from 5 July to 22 July.  There wasn't any comments 
during the WGLC.  The only comment I found was one posted on 9 August.

In Section 1:

  "The iana-timezones YANG module defines the iana-
   timezone type, which is a serialization of the existing IANA Time
   Zone registry [RFC6557] into YANG format."

The terminology in RFC 6557 defines a TZ Database sometimes referred 
to as the "Olson Database".  There isn't any mention of a "IANA Time 
Zone registry".  I suggest using the same name as in RFC 6557.</pre>
      </div>
    </blockquote>
    That makes sense.<br>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>

&gt;From Section 3:

  'The iana-timezones module is intended to reflect the IANA "timezone
   database" [RFC6557].  When a timezone location is added to the
   database, the "iana-timezone" enumeration MUST be updated as defined
   in RFC 6020 Section 10 to add the newly created timezone location to
   the enumeration.  The new "enum" statement MUST be added to the
   "iana-timezone" typedef with the same name as the newly added
   timezone location.  A new enum value MUST be allocated by IANA and
   applied to the newly created enum entry.  New entries MAY be placed
   in any order in the enumeration as long as the previously assigned
   enumeration values are not changed.

   If a timezone location is removed from the IANA timezone database,
   the corresponding existing enum statement is kept and a status
   statement is added to mark the enum entry as 'obsolete'.'

The maintainer of the TZ database is responsible for the TZ 
Database.  The person does not work for IANA.  </pre>
      </div>
    </blockquote>
    Correct, but see <a href="http://www.iana.org/go/rfc6557">BCP 175:
      Procedures for Maintaining the Time Zone Database:<br>
    </a>
    <pre class="newpage">   The TZ Coordinator is an IANA Designated Expert

Are you questioning the term "IANA timezone database", which should be "TZ Database" according to BCP 175?
</pre>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>I don't think that 
IANA keeps track of the contents of the TZ Database as it was not 
asked to do that work.  </pre>
      </div>
    </blockquote>
    I think it does: <a class="moz-txt-link-freetext" href="http://www.iana.org/time-zones">http://www.iana.org/time-zones</a>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>I don't see the value of using RFC 2119 key 
word for the IANA Considerations.</pre>
      </div>
    </blockquote>
    <br>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>

I suggest not creating the registry proposed in this draft.  The TZ 
database has strived to keep out of political issues.  Adding such a 
registry will pave the way for such issues.</pre>
      </div>
    </blockquote>
    Well, we need to specify the system clock in the following YANG
    module
    (<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/">https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/</a>),
    and hence we require a way to represent the TZ in YANG.<br>
    <br>
    Regards, Benoit<br>
    <blockquote cite="mid:52A1ACEF.6080307@cisco.com" type="cite">
      <div class="moz-forward-container">
        <pre>

Regards,
-sm 

.

</pre>
        <br>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
netmod mailing list
<a class="moz-txt-link-abbreviated" href="mailto:netmod@ietf.org">netmod@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/netmod">https://www.ietf.org/mailman/listinfo/netmod</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040502070305050605050600--

From andy@yumaworks.com  Wed Jan  8 09:09:32 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754921AE049 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 09:09:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NiB_7GnJlkB for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 09:09:29 -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 25BFF1AE044 for <ietf@ietf.org>; Wed,  8 Jan 2014 09:09:24 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id cm18so1502840qab.12 for <ietf@ietf.org>; Wed, 08 Jan 2014 09:09:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9RzXXPFNiyp35Y7J+A0ufHLetJh6OiDUcHNI1hAbuGY=; b=hi6ON4wbh2GEJjlxYm8Jx9C4YbzqC5osrtuh6EhxI+8JxBiShyNuHylyw6Cojr7Jyj YbLeuyLxupxfM3xl4bDirp53q66i9HbQdl02QOUHMDNFe7Glerk9lcJ87p4FVmVOXIGu l17rG9ydryxsoECcQQxk28UCmRFeIJKewCGoQ7PEbbyAwvwa7+xApOj8GwneZw0AIt48 qU90UJcmDQELM5o1R26xvu15P8uwC2R6MPV5dZb6D8fxfGMy2MudgqmlcmhaKhIzSY5q clivmtlydBdeCjh0BQJPyfyCdEoxlk1ZWy+eu7b+nEF18Qa1ophhjQaOlodJEVuxluzy kWDg==
X-Gm-Message-State: ALoCoQkhAiTu+0kYuj2R5YCfOYdYgNhBqQF+9Zjr3OX1PtF03hKzOHaVLsvig+ZltUhvf5ZByh3q
MIME-Version: 1.0
X-Received: by 10.49.2.170 with SMTP id 10mr214464610qev.24.1389200954628; Wed, 08 Jan 2014 09:09:14 -0800 (PST)
Received: by 10.140.48.75 with HTTP; Wed, 8 Jan 2014 09:09:14 -0800 (PST)
In-Reply-To: <52CD7EBD.4090506@cisco.com>
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com>
Date: Wed, 8 Jan 2014 09:09:14 -0800
Message-ID: <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database YANG Module) to Proposed Standard
From: Andy Bierman <andy@yumaworks.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b6da3d46c327e04ef788de1
Cc: SM <sm@resistor.net>, Paul Eggert <eggert@cs.ucla.edu>, IETF-Discussion list <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 17:09:32 -0000

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

Hi,

By "this one" I assume you mean the question "Why Proposed Standard?"

This YANG module is meant to be imported by other standard YANG modules,
which creates a normative reference in each importing RFC. We try to avoid
standard modules that rely on non-standard modules. At first, (e.g, RFC
5277,
RFC 5717) the YANG modules were not normative. But since 2010,
(RFC 6020) all YANG modules are normative and XSD is no longer used.


Andy


On Wed, Jan 8, 2014 at 8:37 AM, Benoit Claise <bclaise@cisco.com> wrote:

>  Dear all,
>
> Sadly, I have not seen a reply to this one.
> So let me start the discussion, copying both the ietf-discussion and the
> netmod WG mailers.
> See in-line.
>
> Dear all,
>
> Here is some feedback from the IETF discussion list.
> I would appreciate if the author and document shepherd could follow up.
> Ideally on the IETF discussion list.
>
> Regards, Benoit
>
>
> -------- Original Message --------  Subject: Re: Last Call:
> <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database YANG
> Module) to Proposed Standard  Date: Tue, 3 Dec 2013 19:36:31 -0800  From: SM
> <sm@resistor.net> <sm@resistor.net>  To: <ietf@ietf.org> <ietf@ietf.org>
>
> At 12:46 03-12-2013, The IESG wrote:
> >The IESG has received a request from the NETCONF Data Modeling Language
> >WG (netmod) to consider the following document:
> >- 'IANA Timezone Database YANG Module'
> >   <draft-ietf-netmod-iana-timezones-03.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-12-17. Exceptionally, comments may be
>
> There is the following question in the document shepherd write-up:
>
>   Why is this the proper type of RFC?
>
> I did not see an answer to that question.
>
>  Not sure what you propose here. Proposed Standard seems right to me.
> From http://www.rfc-editor.org/RFCoverview.html
>
> RFC Categories
>
> Each RFC has a "category" or "status" designation. The possible categories
> (see *RFC 2026* <http://www.rfc-editor.org/rfc/rfc2026.txt> "The Internet
> Standards Process -- Revision 3") are:
>
>    - INTERNET STANDARD, DRAFT STANDARD (deprecated; see RFC 6410<http://www.rfc-editor.org/rfc/rfc6410.txt>),
>    PROPOSED STANDARD
>
>    These are *Standards Track* documents, official specifications of the
>    Internet protocol suite defined by the Internet Engineering Task Force
>    (IETF) <http://www.ietf.org> and its steering group the IESG.
>     - BEST CURRENT PRACTICE
>
>    These are official guidelines and recommendations, but not standards,
>    from the IETF.
>     - INFORMATIONAL, EXPERIMENTAL
>
>    These non-standards documents may originate in the IETF or may be
>    independent submissions.
>     - HISTORIC
>
>    These are former standards that have been actively deprecated.
>
>   The WGLC was from 5 July to 22 July.  There wasn't any comments
> during the WGLC.  The only comment I found was one posted on 9 August.
>
> In Section 1:
>
>   "The iana-timezones YANG module defines the iana-
>    timezone type, which is a serialization of the existing IANA Time
>    Zone registry [RFC6557] into YANG format."
>
> The terminology in RFC 6557 defines a TZ Database sometimes referred
> to as the "Olson Database".  There isn't any mention of a "IANA Time
> Zone registry".  I suggest using the same name as in RFC 6557.
>
>  That makes sense.
>
>  >From Section 3:
>
>   'The iana-timezones module is intended to reflect the IANA "timezone
>    database" [RFC6557].  When a timezone location is added to the
>    database, the "iana-timezone" enumeration MUST be updated as defined
>    in RFC 6020 Section 10 to add the newly created timezone location to
>    the enumeration.  The new "enum" statement MUST be added to the
>    "iana-timezone" typedef with the same name as the newly added
>    timezone location.  A new enum value MUST be allocated by IANA and
>    applied to the newly created enum entry.  New entries MAY be placed
>    in any order in the enumeration as long as the previously assigned
>    enumeration values are not changed.
>
>    If a timezone location is removed from the IANA timezone database,
>    the corresponding existing enum statement is kept and a status
>    statement is added to mark the enum entry as 'obsolete'.'
>
> The maintainer of the TZ database is responsible for the TZ
> Database.  The person does not work for IANA.
>
>  Correct, but see BCP 175: Procedures for Maintaining the Time Zone
> Database:
>  <http://www.iana.org/go/rfc6557>
>
>    The TZ Coordinator is an IANA Designated Expert
>
> Are you questioning the term "IANA timezone database", which should be "TZ Database" according to BCP 175?
>
>  I don't think that
> IANA keeps track of the contents of the TZ Database as it was not
> asked to do that work.
>
>  I think it does: http://www.iana.org/time-zones
>
>  I don't see the value of using RFC 2119 key
> word for the IANA Considerations.
>
>
>  I suggest not creating the registry proposed in this draft.  The TZ
> database has strived to keep out of political issues.  Adding such a
> registry will pave the way for such issues.
>
>  Well, we need to specify the system clock in the following YANG module (
> https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/), and
> hence we require a way to represent the TZ in YANG.
>
> Regards, Benoit
>
>  Regards,
> -sm
>
> .
>
>
>
>
>
>
> _______________________________________________
> netmod mailing listnetmod@ietf.orghttps://www.ietf.org/mailman/listinfo/netmod
>
>
>

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

<div dir=3D"ltr">Hi,<div><br></div><div>By &quot;this one&quot; I assume yo=
u mean the question &quot;Why Proposed Standard?&quot;</div><div><br></div>=
<div>This YANG module is meant to be imported by other standard YANG module=
s,</div>
<div>which creates a normative reference in each importing RFC. We try to a=
void</div><div>standard modules that rely on non-standard modules. At first=
, (e.g, RFC 5277,</div><div>RFC 5717) the YANG modules were not normative. =
But since 2010,</div>
<div>(RFC 6020) all YANG modules are normative and XSD is no longer used.</=
div><div><div class=3D"gmail_extra"><br><br>Andy</div><div class=3D"gmail_e=
xtra"><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">O=
n Wed, Jan 8, 2014 at 8:37 AM, Benoit Claise <span dir=3D"ltr">&lt;<a href=
=3D"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.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">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div>Dear all,<br>
      <br>
      Sadly, I have not seen a reply to this one.<br>
      So let me start the discussion, copying both the ietf-discussion
      and the netmod WG mailers.<br>
      See in-line.<br>
    </div>
    <blockquote type=3D"cite">
     =20
      Dear all,<br>
      <br>
      Here is some feedback from the IETF discussion list.<br>
      I would appreciate if the author and document shepherd could
      follow up. Ideally on the IETF discussion list.<br>
      <br>
      Regards, Benoit<br>
      <div><br>
        <br>
        -------- Original Message --------
        <table cellpadding=3D"0" cellspacing=3D"0" border=3D"0">
          <tbody>
            <tr>
              <th align=3D"RIGHT" nowrap valign=3D"BASELINE">Subject:

              </th>
              <td>Re: Last Call:
                &lt;draft-ietf-netmod-iana-timezones-03.txt&gt; (IANA
                Timezone Database YANG Module) to Proposed Standard</td>
            </tr>
            <tr>
              <th align=3D"RIGHT" nowrap valign=3D"BASELINE">Date:
              </th>
              <td>Tue, 3 Dec 2013 19:36:31 -0800</td>
            </tr>
            <tr>
              <th align=3D"RIGHT" nowrap valign=3D"BASELINE">From:
              </th>
              <td>SM <a href=3D"mailto:sm@resistor.net" target=3D"_blank">&=
lt;sm@resistor.net&gt;</a></td>
            </tr>
            <tr>
              <th align=3D"RIGHT" nowrap valign=3D"BASELINE">To: </th>
              <td><a href=3D"mailto:ietf@ietf.org" target=3D"_blank">&lt;ie=
tf@ietf.org&gt;</a></td>
            </tr>
          </tbody>
        </table>
        <br>
        <br>
        <pre>At 12:46 03-12-2013, The IESG wrote:
&gt;The IESG has received a request from the NETCONF Data Modeling Language
&gt;WG (netmod) to consider the following document:
&gt;- &#39;IANA Timezone Database YANG Module&#39;
&gt;   &lt;draft-ietf-netmod-iana-timezones-03.txt&gt; as Proposed Standard
&gt;
&gt;The IESG plans to make a decision in the next few weeks, and solicits
&gt;final comments on this action. Please send substantive comments to the
&gt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> ma=
iling lists by 2013-12-17. Exceptionally, comments may be

There is the following question in the document shepherd write-up:

  Why is this the proper type of RFC?

I did not see an answer to that question.</pre>
      </div>
    </blockquote>
    Not sure what you propose here. Proposed Standard seems right to me.<br=
>
    From <a href=3D"http://www.rfc-editor.org/RFCoverview.html" target=3D"_=
blank">http://www.rfc-editor.org/RFCoverview.html</a><br>
    <blockquote>
      <h2><a name=3D"14372b760faf8661_categories">RFC Categories</a></h2>
      <p>
        Each RFC has a &quot;category&quot; or &quot;status&quot; designati=
on. The possible
        categories
        (see <a href=3D"http://www.rfc-editor.org/rfc/rfc2026.txt" target=
=3D"_blank"><b>RFC
            2026</b></a> &quot;The Internet Standards Process -- Revision 3=
&quot;)
        are:
      </p>
      <ul>
        <li>
          INTERNET STANDARD, DRAFT STANDARD (deprecated;
          see <a href=3D"http://www.rfc-editor.org/rfc/rfc6410.txt" target=
=3D"_blank">RFC
            6410</a>), PROPOSED STANDARD
          <p>
            These are <i>Standards Track</i> documents, official
            specifications of
            the Internet protocol suite defined by the
            <a href=3D"http://www.ietf.org" target=3D"_blank">Internet Engi=
neering Task
              Force
              (IETF)</a>
            and its steering group the IESG.
          </p>
        </li>
        <li>
          BEST CURRENT PRACTICE
          <p>
            These are official guidelines and recommendations, but not
            standards, from the IETF.
          </p>
        </li>
        <li>
          INFORMATIONAL, EXPERIMENTAL
          <p>
            These non-standards documents may originate in the IETF or
            may be
            independent submissions.
          </p>
        </li>
        <li>
          HISTORIC
          <p>
            These are former standards that have been actively
            deprecated.
          </p>
        </li>
      </ul>
    </blockquote>
    <blockquote type=3D"cite">
      <div>
        <pre>The WGLC was from 5 July to 22 July.  There wasn&#39;t any com=
ments=20
during the WGLC.  The only comment I found was one posted on 9 August.

In Section 1:

  &quot;The iana-timezones YANG module defines the iana-
   timezone type, which is a serialization of the existing IANA Time
   Zone registry [RFC6557] into YANG format.&quot;

The terminology in RFC 6557 defines a TZ Database sometimes referred=20
to as the &quot;Olson Database&quot;.  There isn&#39;t any mention of a &qu=
ot;IANA Time=20
Zone registry&quot;.  I suggest using the same name as in RFC 6557.</pre>
      </div>
    </blockquote>
    That makes sense.<br>
    <blockquote type=3D"cite">
      <div>
        <pre>&gt;From Section 3:

  &#39;The iana-timezones module is intended to reflect the IANA &quot;time=
zone
   database&quot; [RFC6557].  When a timezone location is added to the
   database, the &quot;iana-timezone&quot; enumeration MUST be updated as d=
efined
   in RFC 6020 Section 10 to add the newly created timezone location to
   the enumeration.  The new &quot;enum&quot; statement MUST be added to th=
e
   &quot;iana-timezone&quot; typedef with the same name as the newly added
   timezone location.  A new enum value MUST be allocated by IANA and
   applied to the newly created enum entry.  New entries MAY be placed
   in any order in the enumeration as long as the previously assigned
   enumeration values are not changed.

   If a timezone location is removed from the IANA timezone database,
   the corresponding existing enum statement is kept and a status
   statement is added to mark the enum entry as &#39;obsolete&#39;.&#39;

The maintainer of the TZ database is responsible for the TZ=20
Database.  The person does not work for IANA.  </pre>
      </div>
    </blockquote>
    Correct, but see <a href=3D"http://www.iana.org/go/rfc6557" target=3D"_=
blank">BCP 175:
      Procedures for Maintaining the Time Zone Database:<br>
    </a>
    <pre>   The TZ Coordinator is an IANA Designated Expert

Are you questioning the term &quot;IANA timezone database&quot;, which shou=
ld be &quot;TZ Database&quot; according to BCP 175?
</pre>
    <blockquote type=3D"cite">
      <div>
        <pre>I don&#39;t think that=20
IANA keeps track of the contents of the TZ Database as it was not=20
asked to do that work.  </pre>
      </div>
    </blockquote>
    I think it does: <a href=3D"http://www.iana.org/time-zones" target=3D"_=
blank">http://www.iana.org/time-zones</a>
    <blockquote type=3D"cite">
      <div>
        <pre>I don&#39;t see the value of using RFC 2119 key=20
word for the IANA Considerations.</pre>
      </div>
    </blockquote>
    <br>
    <blockquote type=3D"cite">
      <div>
        <pre>I suggest not creating the registry proposed in this draft.  T=
he TZ=20
database has strived to keep out of political issues.  Adding such a=20
registry will pave the way for such issues.</pre>
      </div>
    </blockquote>
    Well, we need to specify the system clock in the following YANG
    module
    (<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-netmod-system-m=
gmt/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-netmod-=
system-mgmt/</a>),
    and hence we require a way to represent the TZ in YANG.<br>
    <br>
    Regards, Benoit<br>
    <blockquote type=3D"cite">
      <div>
        <pre>Regards,
-sm=20

.

</pre>
        <br>
      </div>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
netmod mailing list
<a href=3D"mailto:netmod@ietf.org" target=3D"_blank">netmod@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/netmod" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/netmod</a>
</pre>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div></div></div>

--047d7b6da3d46c327e04ef788de1--

From randy@psg.com  Wed Jan  8 12:46:18 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9BCE1AE140 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 12:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fU8yTGJ7AelQ for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 12:46:17 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 484711AE155 for <ietf@ietf.org>; Wed,  8 Jan 2014 12:46:17 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W100o-0005dX-Cm; Wed, 08 Jan 2014 20:46:03 +0000
Date: Thu, 09 Jan 2014 05:46:01 +0900
Message-ID: <m2mwj6b3sm.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Geoff Huston <gih@apnic.net>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
In-Reply-To: <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <D4E43FF3-AA65-4748-B0AF-F514CE920FDA@apnic.net> <F64C7692-B21E-4DAF-85F6-8F98C502C0A7@virtualized.org> <6172D4D0-591E-45D5-9E2D-2F5246E06D61@apnic.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Thu_Jan__9_05:45:55_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 20:46:18 -0000

--pgp-sign-Multipart_Thu_Jan__9_05:45:55_2014-1
Content-Type: text/plain; charset=US-ASCII

> I'm reminded of a discussion (probably on this list) some time ago
> when kre reminded me that all RFCs can be updated or obsoleted in the
> future by subsequent RFCs. I read this draft in a different sense, in
> that the text in this draft is a description of a here and now state
> of affairs that will presumably exist in the future until updated or
> obsoleted by a subsequent RFC, much the same as the fate of RFC2050 I
> suppose.

wrong venue.  should you want to non-ietf parts of the iana function,
you do not want to go through the ietf process.

randy
--pgp-sign-Multipart_Thu_Jan__9_05:45:55_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJSzbkIAAoJEMzMBey4OgLt9xUH/A1EMbFfdMsZAxI1CSSBhhf3
Sq5fZ6yYBGYv6Z3Zr1SjqLxHlMPZKFadwYFx1/MmOQdtSpapgDTBVfYPHvXgc4TI
eUNmhxZe5qEuTgJU50FRsiOPhQoIqbmjd//sdNqqdaPZ9FQnAS7WlKjQP3pNc3wD
UfX8lLgvJQElHAs2DntDdxNLJ6uDgtaDi2FiGCZdkF6gHClc3Xzkp3GHGCZJzyBQ
I9lHIUzknlBDVk3rnUiTjKLjm3xSAzj23h4bitlrTIPglleRr333Ho/2WL52Ifd7
sv/J7E4h1TxZhS/qvpJ9U2169NQloZuf7nPeJcdoljiY4ZkMeHcNiT1nDFM1kDE=
=IykG
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Thu_Jan__9_05:45:55_2014-1--

From l.wood@surrey.ac.uk  Wed Jan  8 12:59:13 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89E4B1AE19F; Wed,  8 Jan 2014 12:59:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DfNcPG_8kwJ3; Wed,  8 Jan 2014 12:59:11 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.115]) by ietfa.amsl.com (Postfix) with ESMTP id 603861AE100; Wed,  8 Jan 2014 12:59:10 -0800 (PST)
Received: from [193.109.255.147:15484] by server-11.bemta-14.messagelabs.com id A6/64-20576-41CBDC25; Wed, 08 Jan 2014 20:59:00 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-72.messagelabs.com!1389214739!13084435!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5931 invoked from network); 8 Jan 2014 20:59:00 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-15.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 8 Jan 2014 20:59:00 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Wed, 8 Jan 2014 20:58:03 +0000
From: <l.wood@surrey.ac.uk>
To: <gorry@erg.abdn.ac.uk>
Date: Wed, 8 Jan 2014 20:58:01 +0000
Subject: RE: [tsvwg] Milestones changed for tsvwg WG
Thread-Topic: [tsvwg] Milestones changed for tsvwg WG
Thread-Index: Ac8McOrPAmy3B+wRTqai/gWVt+nHRAAPUE6Y
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346AC@EXMB01CMS.surrey.ac.uk>
References: <20140107202040.22438.54920.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F1240847E63346AB@EXMB01CMS.surrey.ac.uk>, <9e9147aa7183c016db4888691f1ef46d.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <9e9147aa7183c016db4888691f1ef46d.squirrel@www.erg.abdn.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: lisp@ietf.org, jnc@mit.edu, tsvwg@ietf.org, lucy.yong@huawei.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 20:59:13 -0000

Zero UDP checksums are being selected for convenience, without an appreciat=
ion
of the overall effects and  costs on other traffic. I see this is occurring=
 in both tsvwg
and lisp, and it's probably happening elsewhere:

>From the recently adopted by tsvwg draft:
http://tools.ietf.org/html/draft-yong-tsvwg-gre-in-udp-encap-02
   To simplify packet processing at the tunnel egress, packets destined
   to this assigned UDP destination port [TBD] SHOULD have their UDP
   checksum and Sequence flags set to zero because the egress tunnel
   only needs to identify this protocol.  Although IPv6 [RFC2460]
   restricts the processing a packet with the UDP checksum of zero,
   [RFC6935] and [RFC6936] relax this constraint to allow the zero UDP
   checksum.

from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
   The UDP checksum is zero because the inner packet usually already has
   a end-end checksum, and the outer checksum adds no value.  [Saltzer]

(That's a misreading of Saltzer - the UDP checksum is also protecting again=
st
misdelivery and pseudoheader corruption, and 'usually' is not a good defenc=
e.
For shame, Noel.)

After all, the best examples of end2end systems failure are with zero check=
sums
at the endhosts.

The TCP and UDP checksums catch significant numbers of errors, e.g. Stone's
work:
http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf
and some of those errors will appear in the headers, where they will send
the data to other ports and destinations.

The potential for polluting other ports and applications because
there is no pseudoheader demultiplexing sanity check is there.

IPv6 leaving this check implemented  on a per-transport basis has opened th=
e door,
and rewriting that section of RFC2460 in RFC6935 has taken the door off its=
 hinges.
These RFCs break the minimal multiplexing pseudoheader sanity check that RF=
C2460
offered; IPv6 is a mess in so many ways, but making it worse?=20

I think publishing RFC6935 and 6936 and letting in zero checksums again to =
IPv6
was a mistake, frankly. (alas, I wasn't paying much attention at the time -=
 moving
countries etc.)

A strong recommendation that UDP-Lite covering headers offers minimal compu=
tation
overhead on tunnelled packets while protecting against polluting other port=
s is one
solution, while acknowledging deployment limitations. Section 2.4 of RFC696=
 is mostly there.
But zero UDP checksums should always come with copious warnings on the effe=
cts not on the
carried traffic, which can have its own payload checks, but on traffic shar=
ing the network
with traffic delivered with zero UDP checksums. Drafts relying on zero
checksums should be discouraged, not adopted by workgroups.

It's a tragedy of the commons, but the I'm-alright-Jack engineers who want=
=20
zero udp checksums for their traffic, and do protect against the effects of=
 zero
checksums on their own payloads, won't care about effects on other traffic.
Hey, maybe this should be treated as an attack, which falls under perpass? =
That
should get it attention...

tsvwg needs to give (or get) some careful input on the implications here.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
Sent: 08 January 2014 12:55
To: Wood L  Dr (Electronic Eng)
Cc: tsvwg@ietf.org
Subject: Re: [tsvwg] Milestones changed for tsvwg WG

Lloyd,

Here is a little context... which could help. The IETF agreed to update
the UDP checksum behaviour for IPv6 in RFC 6935, but only subject to the
applicability specified in RFC 6936.

One of the reasons why a simple encapsulation like this needs to be done
in tsvwg is to minimise the end-to-end implications on other traffic.
Sure, using a zero checksum has such implications, and my own first
concern is that the new GRE-in-UDP work follows the applicability
statement in RFC 6936. To me, it seems the authors are heading this way -
but maybe more help is needed. It would be no bad thing to highlight the
implications of using zero checksums on other traffic.

Gorry

> Am I the only one who finds putting zero checksums in proposed standards
> to be a worrying
> trend?
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: tsvwg [tsvwg-bounces@ietf.org] On Behalf Of IETF Secretariat
> [ietf-secretariat-reply@ietf.org]
> Sent: 07 January 2014 20:20
> To: tsvwg@ietf.org
> Subject: [tsvwg] Milestones changed for tsvwg WG
>
> Added milestone "Submit 'Specification of GRE in UDP encapsulation' to
> IESG as a PS RFC", due December 2014.
>
> URL: http://datatracker.ietf.org/wg/tsvwg/charter/
>



From bmanning@isi.edu  Wed Jan  8 13:08:38 2014
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909CB1AE5E5 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 13:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rArNcItlBJEA for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 13:08:36 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 0F1261AE5E3 for <ietf@ietf.org>; Wed,  8 Jan 2014 13:08:36 -0800 (PST)
Received: from [198.32.4.180] ([198.32.4.180]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s08L7EwS022309 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 8 Jan 2014 13:07:28 -0800 (PST)
Subject: Re: Split the IANA functions?
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <20140107144412.GB11068@mx1.yitter.info>
Date: Wed, 8 Jan 2014 13:07:12 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1827)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 21:08:38 -0000

Andrew, I think I will have to disagree with you in your over =
simplification.
There can be/ have been multiple roots in the DNS - HOWEVER, there is a =
always a single root _per class_.
One root for IN, one root for CH, one for HS,  etc=85

These days, every class but IN is vestigial, so it is easy to conflate =
the IN class with the DNS as a whole. =20

/bill  -picking nits-
Neca eos omnes.  Deus suos agnoscet.

On 7January2014Tuesday, at 6:44, Andrew Sullivan =
<ajs@anvilwalrusden.com> wrote:

> On Tue, Jan 07, 2014 at 07:02:34AM +0100, Eliot Lear wrote:
>> That there is a single root is both a technical AND a
>> political decision.=20
>=20
> I have to disagree with this.  The uniqueness of the root is not a
> political decision.  It's a fact of mathematics.  DNS is a tree.
> There's one root.
>=20
> Now, one might argue that choosing this kind of name space was a
> political decision.  I might buy that argument (I don't know).  =
There's
> good reason to suppose that there was at least some organizational
> principle behind the decision in favour of a hierarchical namespace.
> There were technical constraints too, I think: I don't believe a fully
> peer to peer system was practical in the network environment of the
> 1980s.  But if we wanted to call anything that had non-technical
> elements in it "political", then the selection of the DNS
> (hierarchical) name space was in that sense political.
>=20
> This is not to say that the single root doesn't have additional
> political implications.  But I will not concede that this is some
> contingent fact of the DNS that could be otherwise.  The particular
> root we have could be different.  That there is a single root could
> not.
>=20
> Best regards,
>=20
> A
>=20
> --=20
> Andrew Sullivan
> ajs@anvilwalrusden.com


From farinacci@gmail.com  Wed Jan  8 13:51:18 2014
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 916251ACC84; Wed,  8 Jan 2014 13:51:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j98PBs1n47hA; Wed,  8 Jan 2014 13:51:17 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCB01A1F71; Wed,  8 Jan 2014 13:51:17 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id up15so2111744pbc.24 for <multiple recipients>; Wed, 08 Jan 2014 13:51:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6CfPUAZfFn/+/opiIcjKVXjHh8IQgudBOfNV5wM4OiA=; b=nrW/c63QVJBhHBh1qYret4T1rRzu08NCWOPfnLQJQovYfurSMyePbif82szCrr4kaC gHUXtYJRpBtm9sYPNGlYCB6YCvI/BZQkwIvGDuxfYVw55YsRUzaSkHvvmXabEibJi0aB P8ext7dtAYxiCTcR8lc2RQU2qG7ghxQNs7+c0yYQd5C6zbB3iTMDJxBPCSGajlygX7wt z8M5yUEkPWSHjIfQXoNNWoWl3gmwSzztBRfWuxNMujn8gsNRhUfPoVYFDEHpjQ67VY8c i5iSR9fJI4jvxhccos4roYOzhJUdC3ON8ds+O+mfIM3tBrIPQ6uakv95ylcQqLFE+moG RYXA==
X-Received: by 10.66.27.42 with SMTP id q10mr12093722pag.65.1389217868320; Wed, 08 Jan 2014 13:51:08 -0800 (PST)
Received: from [172.21.60.107] ([167.235.252.130]) by mx.google.com with ESMTPSA id yi10sm6076992pab.8.2014.01.08.13.51.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Jan 2014 13:51:06 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: [lisp] [tsvwg] Milestones changed for tsvwg WG
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346AC@EXMB01CMS.surrey.ac.uk>
Date: Wed, 8 Jan 2014 13:51:04 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F2165C4-3322-416F-913D-1443C4443E81@gmail.com>
References: <20140107202040.22438.54920.idtracker@ietfa.amsl.com> <290E20B455C66743BE178C5C84F1240847E63346AB@EXMB01CMS.surrey.ac.uk>, <9e9147aa7183c016db4888691f1ef46d.squirrel@www.erg.abdn.ac.uk> <290E20B455C66743BE178C5C84F1240847E63346AC@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1827)
Cc: gorry@erg.abdn.ac.uk, ietf@ietf.org, jnc@mit.edu, LISP mailing list list <lisp@ietf.org>, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 21:51:18 -0000

> Zero UDP checksums are being selected for convenience, without an =
appreciation
> of the overall effects and  costs on other traffic. I see this is =
occurring in both tsvwg
> and lisp, and it's probably happening elsewhere:

For the LISP working group, or at least for this author, Zero UDP =
checksums were selected out of practicality, performance practicality.

Dino


From david.black@emc.com  Wed Jan  8 15:21:25 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CF061AD939; Wed,  8 Jan 2014 15:21:25 -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=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TdoKzYCdpBhx; Wed,  8 Jan 2014 15:21:23 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E62051AD948; Wed,  8 Jan 2014 15:21:21 -0800 (PST)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s08NL9TS002915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Jan 2014 18:21:10 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s08NL9TS002915
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389223270; bh=OUxIZcRUGquTocbJ0OIOXDvQn5k=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=enVMQYqyAJkvLwHELR9jIkRaA7GAWkd1Ff+wO8FLRisgUshou14CNHU79+He2m/Wa y9ydupMrfmH7RNRGFQ1gaq/OGeU0aloP+dTcmw4QSbsL5qponoChqsxm/fOQMdf02J rUoWK5zPeS6RjPYFfc8Vdjbdx0YNiFavT4EyWu7I=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s08NL9TS002915
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd05.lss.emc.com (RSA Interceptor); Wed, 8 Jan 2014 15:20:55 -0800
Received: from mxhub25.corp.emc.com (mxhub25.corp.emc.com [10.254.110.181]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s08NKsDh028930 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 8 Jan 2014 18:20:54 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub25.corp.emc.com ([10.254.110.181]) with mapi; Wed, 8 Jan 2014 18:20:53 -0500
From: "Black, David" <david.black@emc.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>
Date: Wed, 8 Jan 2014 18:20:52 -0500
Subject: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8MyEHqITdMSvN0R8qKanlihQAy2g==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
X-RSA-Classifications: public
Cc: "ietf@ietf.org" <ietf@ietf.org>, "jnc@mit.edu" <jnc@mit.edu>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 23:21:25 -0000

Lloyd,

<tsvwg WG co-chair hat OFF>

This is only at the draft adoption stage - the tsvwg WG gets to take a hard
look at the zero checksum conditions in the gre-in-udp-encap draft and
make sure that they're right (the WG could even remove the support for
zero checksums) - that's among the good reasons for adopting the draft
in tsvwg as opposed to elsewhere.  =20

Speaking of elsewhere, draft-ietf-mpls-in-udp is in IETF Last Call and has
language allowing zero UDP checksums - I might suggest that you (and anyone
else who cares about this topic) go read that draft and consider whether
making Last Call comments would be appropriate.

Thanks,
--David
</tsvwg WG co-chair hat OFF>

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.ac=
.uk
> Sent: Wednesday, January 08, 2014 3:58 PM
> To: gorry@erg.abdn.ac.uk
> Cc: lisp@ietf.org; jnc@mit.edu; tsvwg@ietf.org; ietf@ietf.org
> Subject: Re: [tsvwg] Milestones changed for tsvwg WG
>=20
> Zero UDP checksums are being selected for convenience, without an appreci=
ation
> of the overall effects and  costs on other traffic. I see this is occurri=
ng in
> both tsvwg
> and lisp, and it's probably happening elsewhere:
>=20
> From the recently adopted by tsvwg draft:
> http://tools.ietf.org/html/draft-yong-tsvwg-gre-in-udp-encap-02
>    To simplify packet processing at the tunnel egress, packets destined
>    to this assigned UDP destination port [TBD] SHOULD have their UDP
>    checksum and Sequence flags set to zero because the egress tunnel
>    only needs to identify this protocol.  Although IPv6 [RFC2460]
>    restricts the processing a packet with the UDP checksum of zero,
>    [RFC6935] and [RFC6936] relax this constraint to allow the zero UDP
>    checksum.
>=20
> from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
>    The UDP checksum is zero because the inner packet usually already has
>    a end-end checksum, and the outer checksum adds no value.  [Saltzer]
>=20
> (That's a misreading of Saltzer - the UDP checksum is also protecting aga=
inst
> misdelivery and pseudoheader corruption, and 'usually' is not a good defe=
nce.
> For shame, Noel.)
>=20
> After all, the best examples of end2end systems failure are with zero
> checksums
> at the endhosts.
>=20
> The TCP and UDP checksums catch significant numbers of errors, e.g. Stone=
's
> work:
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pd=
f
> and some of those errors will appear in the headers, where they will send
> the data to other ports and destinations.
>=20
> The potential for polluting other ports and applications because
> there is no pseudoheader demultiplexing sanity check is there.
>=20
> IPv6 leaving this check implemented  on a per-transport basis has opened =
the
> door,
> and rewriting that section of RFC2460 in RFC6935 has taken the door off i=
ts
> hinges.
> These RFCs break the minimal multiplexing pseudoheader sanity check that
> RFC2460
> offered; IPv6 is a mess in so many ways, but making it worse?
>=20
> I think publishing RFC6935 and 6936 and letting in zero checksums again t=
o
> IPv6
> was a mistake, frankly. (alas, I wasn't paying much attention at the time=
 -
> moving
> countries etc.)
>=20
> A strong recommendation that UDP-Lite covering headers offers minimal
> computation
> overhead on tunnelled packets while protecting against polluting other po=
rts
> is one
> solution, while acknowledging deployment limitations. Section 2.4 of RFC6=
96 is
> mostly there.
> But zero UDP checksums should always come with copious warnings on the ef=
fects
> not on the
> carried traffic, which can have its own payload checks, but on traffic sh=
aring
> the network
> with traffic delivered with zero UDP checksums. Drafts relying on zero
> checksums should be discouraged, not adopted by workgroups.
>=20
> It's a tragedy of the commons, but the I'm-alright-Jack engineers who wan=
t
> zero udp checksums for their traffic, and do protect against the effects =
of
> zero
> checksums on their own payloads, won't care about effects on other traffi=
c.
> Hey, maybe this should be treated as an attack, which falls under perpass=
?
> That
> should get it attention...
>=20
> tsvwg needs to give (or get) some careful input on the implications here.
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
> Sent: 08 January 2014 12:55
> To: Wood L  Dr (Electronic Eng)
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] Milestones changed for tsvwg WG
>=20
> Lloyd,
>=20
> Here is a little context... which could help. The IETF agreed to update
> the UDP checksum behaviour for IPv6 in RFC 6935, but only subject to the
> applicability specified in RFC 6936.
>=20
> One of the reasons why a simple encapsulation like this needs to be done
> in tsvwg is to minimise the end-to-end implications on other traffic.
> Sure, using a zero checksum has such implications, and my own first
> concern is that the new GRE-in-UDP work follows the applicability
> statement in RFC 6936. To me, it seems the authors are heading this way -
> but maybe more help is needed. It would be no bad thing to highlight the
> implications of using zero checksums on other traffic.
>=20
> Gorry
>=20
> > Am I the only one who finds putting zero checksums in proposed standard=
s
> > to be a worrying
> > trend?
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: tsvwg [tsvwg-bounces@ietf.org] On Behalf Of IETF Secretariat
> > [ietf-secretariat-reply@ietf.org]
> > Sent: 07 January 2014 20:20
> > To: tsvwg@ietf.org
> > Subject: [tsvwg] Milestones changed for tsvwg WG
> >
> > Added milestone "Submit 'Specification of GRE in UDP encapsulation' to
> > IESG as a PS RFC", due December 2014.
> >
> > URL: http://datatracker.ietf.org/wg/tsvwg/charter/
> >
>=20
>=20


From ajs@anvilwalrusden.com  Wed Jan  8 15:21:44 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76FB21AD986 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 15:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.459
X-Spam-Level: 
X-Spam-Status: No, score=0.459 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_45=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGB9VTG-P-Ce for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 15:21:43 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 865791AD945 for <ietf@ietf.org>; Wed,  8 Jan 2014 15:21:42 -0800 (PST)
Received: from mx1.yitter.info (nat-02-mht.dyndns.com [216.146.45.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 6963B8A031 for <ietf@ietf.org>; Wed,  8 Jan 2014 23:21:32 +0000 (UTC)
Date: Wed, 8 Jan 2014 18:21:30 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Split the IANA functions?
Message-ID: <20140108232130.GN13117@mx1.yitter.info>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 23:21:44 -0000

So that I don't have to keep replying to this off list:

On Wed, Jan 08, 2014 at 01:07:12PM -0800, manning bill wrote:

> There can be/ have been multiple roots in the DNS - HOWEVER, there is a always a single root _per class_.
> One root for IN, one root for CH, one for HS,  etcâ€¦

Right.  Except it turns out that CNAME and DNAME are specified in
terms of names and not name+class, so at the very least the class
boundaries are not as clean as we would like.

As you note, in any case, all anyone uses is IN.  

Best,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From jnc@mercury.lcs.mit.edu  Wed Jan  8 15:32:47 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B58B01ADBCE; Wed,  8 Jan 2014 15:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A_402t1afOl9; Wed,  8 Jan 2014 15:32:45 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id AA4201ADBCD; Wed,  8 Jan 2014 15:32:45 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1651018C15B; Wed,  8 Jan 2014 18:32:36 -0500 (EST)
To: ietf@ietf.org, lisp@ietf.org, tsvwg@ietf.org
Subject: RE: [tsvwg] Milestones changed for tsvwg WG
Message-Id: <20140108233236.1651018C15B@mercury.lcs.mit.edu>
Date: Wed,  8 Jan 2014 18:32:36 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jan 2014 23:32:47 -0000

    > From: <l.wood@surrey.ac.uk>

    > from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
    >
    >   The UDP checksum is zero because the inner packet usually already has
    >   a end-end checksum, and the outer checksum adds no value.  [Saltzer]

    > (That's a misreading of Saltzer - the UDP checksum is also protecting
    > against misdelivery and pseudoheader corruption

If the content above the UDP header in this case were that of some sort of
application, you'd be right.

But it's not.

The UDP, outer and inner IP headers of LISP _together_ are effectively a
layer three header ('get the packet from the source host to the destination
host - and that's all, ffffolks - no reliability of any kind'). So the fact
that it's not providing protection against misdelivery is... _exactly_ like
the service that bare IPvN provides.

In fact, since IPv6 doesn't even _have_ a header checksum, UDP in LISP is
doing exactly what IPv6 does. Are you now claiming that IPv6 is fundamentally
defective because it doesn't have a header checksum to guard against packet
mis-delivery?

    > and 'usually' is not a good defence

To say it at slightly greater length, 'the inner packet _either_ already has
an end-end checksum (the usual case), in which case adding another one is of
little or no value, _or_ the sender deliverately sent their packet _without_
an end-end checksum, in which case they are _no worse off_ than they were
before the packet was encapsulated'.

It's not the internetwork layer's job to second-guess the users; we can assume
that if someone sent a packet without an end-end checksum, they must have
worked out that for whatever they are doing, it's OK to leave it out.


Note that I am solely answering regarding the omission of UDP checksums when
UDP is used as part of the internetworking layer, for encapsulating traffic.
I have not considered, and make no statement about, use of zero checksums
in other ways/places.

	Noel

From kre@munnari.OZ.AU  Wed Jan  8 16:11:15 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D46D41ADE88 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 16:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.333
X-Spam-Level: 
X-Spam-Status: No, score=0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.538] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQV5oJBNhnM1 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 16:11:14 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC5D1ADE86 for <ietf@ietf.org>; Wed,  8 Jan 2014 16:11:14 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0906TYd007938; Thu, 9 Jan 2014 07:06:50 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0906M0V023749; Thu, 9 Jan 2014 07:06:23 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: manning bill <bmanning@isi.edu>
Subject: Re: Split the IANA functions?
In-Reply-To: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Jan 2014 07:06:22 +0700
Message-ID: <2520.1389225982@perseus.noi.kre.to>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 00:11:16 -0000

    Date:        Wed, 8 Jan 2014 13:07:12 -0800
    From:        manning bill <bmanning=40isi.edu>
    Message-ID:  <94F13021-48B9-4CE9-995A-1081DC75A52D=40isi.edu>

  =7C There can be/ have been multiple roots in the DNS - HOWEVER, there =
is
  =7C a always a single root _per class_.

I'm not sure that's correct.   Nor do I know it is incorrect.  Classes
were (and are) so under-specified that exactly how they were intended to
work (if there was ever a clear and understood interpretation of that)
seems lost in the mists of time.

Another interpretation is that classes operate more like BIND's implement=
ation
of views - that is allow different data for the same types in the same
namespace - except without requiring the server to guess bases on source
address of the query which set of data is required.

I am not even certain I am convinced whether the set of available types
is global, or varies per class, nor whether the same lookup algorithm app=
lies
(does A =3D=3D a in all classes?)  Probably, but who knows.

But even if you're correct, then conceptually, what is now isi.edu simply=

becomes isi.edu.internet. (whether actually written that way or not) and
then the set of classes would become the =22top level domains=22, and we'=
re
back at a single tree, with a single root, that root being a list of all =
of
the classes.

There really is no way out of this - people wanting multiple roots really=

just want to change who controls that rot - usually to someone they consi=
der
friendly to themselves (like themselves) rather than someone that they co=
nsider
the enemy (ietf/iana/icann/...)

kre


From l.wood@surrey.ac.uk  Wed Jan  8 18:35:57 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44AC91ADFBB; Wed,  8 Jan 2014 18:35:57 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a64W_Uos6myx; Wed,  8 Jan 2014 18:35:54 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.164]) by ietfa.amsl.com (Postfix) with ESMTP id ADBCF1ADFE3; Wed,  8 Jan 2014 18:35:53 -0800 (PST)
Received: from [85.158.137.99:37087] by server-4.bemta-3.messagelabs.com id 91/31-10414-FFA0EC25; Thu, 09 Jan 2014 02:35:43 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-217.messagelabs.com!1389234942!20866842!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18408 invoked from network); 9 Jan 2014 02:35:42 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-14.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 02:35:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 9 Jan 2014 02:35:41 +0000
From: <l.wood@surrey.ac.uk>
To: <jnc@mercury.lcs.mit.edu>, <ietf@ietf.org>, <lisp@ietf.org>, <tsvwg@ietf.org>
Date: Thu, 9 Jan 2014 02:35:41 +0000
Subject: RE: [tsvwg] Milestones changed for tsvwg WG
Thread-Topic: [tsvwg] Milestones changed for tsvwg WG
Thread-Index: Ac8MyfzxG8ethIThS5asfP1FdUu3hwAFvWo7
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346AD@EXMB01CMS.surrey.ac.uk>
References: <20140108233236.1651018C15B@mercury.lcs.mit.edu>
In-Reply-To: <20140108233236.1651018C15B@mercury.lcs.mit.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 02:35:57 -0000

Noel,

I'm claiming that IPv6 has only the pseudoheader checksum to prevent misdel=
ivery,
as the header checksum was removed from v6 (rather than simply covering non=
-mutable fields,
and leaving out TTL).

When a UDP checksum is set to zero, there is a risk to the payload traffic =
carried - which,
as you point out, is protected against for the carried traffic if it has it=
s own checksum,
which is at a higher layer and more end-to-end.

However (and this is the subtle point), while the carried traffic is protec=
ted against
corruption if the packet is delivered to LISP, any IP/UDP header corruption=
 goes
undetected at the endhost because the pseudoheader checksum has been disabl=
ed.
This does not matter for your application; the header corruption takes
the packet to some other destination/port, so you don't see it; it's just a=
 drop as
far as you are concerned. But it matters for whatever actually receives
that corrupted packet on e.g. an altered port value. How do they detect and=
 reject it
from their stream?

Bare IPv4 has the header checksum, so at least you can tell the endhost is =
probably
right. But sans UDP checksum, there's no (weak) ports check.
IPv6 has no header checksum, so unchecked corruption to header or ports can=
 take
the packet anywhere.

> It's not the internetwork layer's job to second-guess the users; we can a=
ssume
> that if someone sent a packet without an end-end checksum, they must have
> worked out that for whatever they are doing, it's OK to leave it out.

For what they're doing, but not for what everyone else is doing. Sure, LISP=
 or
tunnels are fine, but odd behaviour on other applications at the same endpo=
ints
(or, with IPv6, in the same network) caused by missent packets with corrupt=
ed UDP
packets? Hey, not your problem. Hey, you're working just fine.

It's pollution and tragedy of the commons, basically.

When you send with a zero UDP checksum, it's possible for the packet to be
received and processed anywhere.

Secondguessing users who don't understand the problems they create IS
the internetwork layer's job.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Noel Chiappa [jnc@mercury.l=
cs.mit.edu]
Sent: 08 January 2014 23:32
To: ietf@ietf.org; lisp@ietf.org; tsvwg@ietf.org
Cc: jnc@mercury.lcs.mit.edu
Subject: RE: [tsvwg] Milestones changed for tsvwg WG

    > From: <l.wood@surrey.ac.uk>

    > from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
    >
    >   The UDP checksum is zero because the inner packet usually already h=
as
    >   a end-end checksum, and the outer checksum adds no value.  [Saltzer=
]

    > (That's a misreading of Saltzer - the UDP checksum is also protecting
    > against misdelivery and pseudoheader corruption

If the content above the UDP header in this case were that of some sort of
application, you'd be right.

But it's not.

The UDP, outer and inner IP headers of LISP _together_ are effectively a
layer three header ('get the packet from the source host to the destination
host - and that's all, ffffolks - no reliability of any kind'). So the fact
that it's not providing protection against misdelivery is... _exactly_ like
the service that bare IPvN provides.

In fact, since IPv6 doesn't even _have_ a header checksum, UDP in LISP is
doing exactly what IPv6 does. Are you now claiming that IPv6 is fundamental=
ly
defective because it doesn't have a header checksum to guard against packet
mis-delivery?

    > and 'usually' is not a good defence

To say it at slightly greater length, 'the inner packet _either_ already ha=
s
an end-end checksum (the usual case), in which case adding another one is o=
f
little or no value, _or_ the sender deliverately sent their packet _without=
_
an end-end checksum, in which case they are _no worse off_ than they were
before the packet was encapsulated'.

It's not the internetwork layer's job to second-guess the users; we can ass=
ume
that if someone sent a packet without an end-end checksum, they must have
worked out that for whatever they are doing, it's OK to leave it out.


Note that I am solely answering regarding the omission of UDP checksums whe=
n
UDP is used as part of the internetworking layer, for encapsulating traffic=
.
I have not considered, and make no statement about, use of zero checksums
in other ways/places.

        Noel

From jmh@joelhalpern.com  Wed Jan  8 18:47:36 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309241AE032; Wed,  8 Jan 2014 18:47:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvCP_TO1Ywd5; Wed,  8 Jan 2014 18:47:34 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD581AE02D; Wed,  8 Jan 2014 18:47:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 346FA1D4E59; Wed,  8 Jan 2014 18:47:25 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-134-71.clppva.east.verizon.net [70.106.134.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 8ED6E1C5CC1; Wed,  8 Jan 2014 18:47:23 -0800 (PST)
Message-ID: <52CE0DB9.50408@joelhalpern.com>
Date: Wed, 08 Jan 2014 21:47:21 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, jnc@mercury.lcs.mit.edu, ietf@ietf.org,  lisp@ietf.org, tsvwg@ietf.org
Subject: Re: [lisp] [tsvwg] Milestones changed for tsvwg WG
References: <20140108233236.1651018C15B@mercury.lcs.mit.edu> <290E20B455C66743BE178C5C84F1240847E63346AD@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346AD@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 02:47:36 -0000

Rather than repeat the arguments, might I ask that you read RFCs 6935 
and 6936, which represent the IETFs conclusion about this topic?

The LISP work complies with the requirements of those RFCs.

Yours,
Joel

On 1/8/14 9:35 PM, l.wood@surrey.ac.uk wrote:
> Noel,
>
> I'm claiming that IPv6 has only the pseudoheader checksum to prevent misdelivery,
> as the header checksum was removed from v6 (rather than simply covering non-mutable fields,
> and leaving out TTL).
>
> When a UDP checksum is set to zero, there is a risk to the payload traffic carried - which,
> as you point out, is protected against for the carried traffic if it has its own checksum,
> which is at a higher layer and more end-to-end.
>
> However (and this is the subtle point), while the carried traffic is protected against
> corruption if the packet is delivered to LISP, any IP/UDP header corruption goes
> undetected at the endhost because the pseudoheader checksum has been disabled.
> This does not matter for your application; the header corruption takes
> the packet to some other destination/port, so you don't see it; it's just a drop as
> far as you are concerned. But it matters for whatever actually receives
> that corrupted packet on e.g. an altered port value. How do they detect and reject it
> from their stream?
>
> Bare IPv4 has the header checksum, so at least you can tell the endhost is probably
> right. But sans UDP checksum, there's no (weak) ports check.
> IPv6 has no header checksum, so unchecked corruption to header or ports can take
> the packet anywhere.
>
>> It's not the internetwork layer's job to second-guess the users; we can assume
>> that if someone sent a packet without an end-end checksum, they must have
>> worked out that for whatever they are doing, it's OK to leave it out.
>
> For what they're doing, but not for what everyone else is doing. Sure, LISP or
> tunnels are fine, but odd behaviour on other applications at the same endpoints
> (or, with IPv6, in the same network) caused by missent packets with corrupted UDP
> packets? Hey, not your problem. Hey, you're working just fine.
>
> It's pollution and tragedy of the commons, basically.
>
> When you send with a zero UDP checksum, it's possible for the packet to be
> received and processed anywhere.
>
> Secondguessing users who don't understand the problems they create IS
> the internetwork layer's job.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Noel Chiappa [jnc@mercury.lcs.mit.edu]
> Sent: 08 January 2014 23:32
> To: ietf@ietf.org; lisp@ietf.org; tsvwg@ietf.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: RE: [tsvwg] Milestones changed for tsvwg WG
>
>      > From: <l.wood@surrey.ac.uk>
>
>      > from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
>      >
>      >   The UDP checksum is zero because the inner packet usually already has
>      >   a end-end checksum, and the outer checksum adds no value.  [Saltzer]
>
>      > (That's a misreading of Saltzer - the UDP checksum is also protecting
>      > against misdelivery and pseudoheader corruption
>
> If the content above the UDP header in this case were that of some sort of
> application, you'd be right.
>
> But it's not.
>
> The UDP, outer and inner IP headers of LISP _together_ are effectively a
> layer three header ('get the packet from the source host to the destination
> host - and that's all, ffffolks - no reliability of any kind'). So the fact
> that it's not providing protection against misdelivery is... _exactly_ like
> the service that bare IPvN provides.
>
> In fact, since IPv6 doesn't even _have_ a header checksum, UDP in LISP is
> doing exactly what IPv6 does. Are you now claiming that IPv6 is fundamentally
> defective because it doesn't have a header checksum to guard against packet
> mis-delivery?
>
>      > and 'usually' is not a good defence
>
> To say it at slightly greater length, 'the inner packet _either_ already has
> an end-end checksum (the usual case), in which case adding another one is of
> little or no value, _or_ the sender deliverately sent their packet _without_
> an end-end checksum, in which case they are _no worse off_ than they were
> before the packet was encapsulated'.
>
> It's not the internetwork layer's job to second-guess the users; we can assume
> that if someone sent a packet without an end-end checksum, they must have
> worked out that for whatever they are doing, it's OK to leave it out.
>
>
> Note that I am solely answering regarding the omission of UDP checksums when
> UDP is used as part of the internetworking layer, for encapsulating traffic.
> I have not considered, and make no statement about, use of zero checksums
> in other ways/places.
>
>          Noel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>

From l.wood@surrey.ac.uk  Wed Jan  8 18:54:05 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 113901ADFB8; Wed,  8 Jan 2014 18:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OtXIixq79gKm; Wed,  8 Jan 2014 18:54:02 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 72B961ADF9B; Wed,  8 Jan 2014 18:54:01 -0800 (PST)
Received: from [195.245.231.67:2938] by server-13.bemta-5.messagelabs.com id D3/2F-11357-F3F0EC25; Thu, 09 Jan 2014 02:53:51 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-82.messagelabs.com!1389236031!27740369!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29235 invoked from network); 9 Jan 2014 02:53:51 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-7.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 02:53:51 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 9 Jan 2014 02:53:50 +0000
From: <l.wood@surrey.ac.uk>
To: <jmh@joelhalpern.com>, <jnc@mercury.lcs.mit.edu>, <ietf@ietf.org>, <lisp@ietf.org>, <tsvwg@ietf.org>
Date: Thu, 9 Jan 2014 02:50:12 +0000
Subject: RE: [lisp] [tsvwg] Milestones changed for tsvwg WG
Thread-Topic: [lisp] [tsvwg] Milestones changed for tsvwg WG
Thread-Index: Ac8M5SfFwysDKxJjT0ik/TWXtnegxAAAFyaP
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346AF@EXMB01CMS.surrey.ac.uk>
References: <20140108233236.1651018C15B@mercury.lcs.mit.edu> <290E20B455C66743BE178C5C84F1240847E63346AD@EXMB01CMS.surrey.ac.uk>, <52CE0DB9.50408@joelhalpern.com>
In-Reply-To: <52CE0DB9.50408@joelhalpern.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 02:54:05 -0000

Joel,

I'd already read them, I explicitly referenced them in my mail that prompte=
d Noel's reply
(text not included below, I see - copy
at http://www.ietf.org/mail-archive/web/ietf/current/msg85351.html )
and I have explained where those RFCs have gone wrong.

Those proposed standards are written from the perspective of the tunnel use=
r, not the rest of the network.
Tunnel user is fine and unaffected, rest of the network bears the pollution=
 costs.

regards

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Joel M. Halpern [jmh@joelhalpern.com]
Sent: 09 January 2014 02:47
To: Wood L  Dr (Electronic Eng); jnc@mercury.lcs.mit.edu; ietf@ietf.org; li=
sp@ietf.org; tsvwg@ietf.org
Subject: Re: [lisp] [tsvwg] Milestones changed for tsvwg WG

Rather than repeat the arguments, might I ask that you read RFCs 6935
and 6936, which represent the IETFs conclusion about this topic?

The LISP work complies with the requirements of those RFCs.

Yours,
Joel

On 1/8/14 9:35 PM, l.wood@surrey.ac.uk wrote:
> Noel,
>
> I'm claiming that IPv6 has only the pseudoheader checksum to prevent misd=
elivery,
> as the header checksum was removed from v6 (rather than simply covering n=
on-mutable fields,
> and leaving out TTL).
>
> When a UDP checksum is set to zero, there is a risk to the payload traffi=
c carried - which,
> as you point out, is protected against for the carried traffic if it has =
its own checksum,
> which is at a higher layer and more end-to-end.
>
> However (and this is the subtle point), while the carried traffic is prot=
ected against
> corruption if the packet is delivered to LISP, any IP/UDP header corrupti=
on goes
> undetected at the endhost because the pseudoheader checksum has been disa=
bled.
> This does not matter for your application; the header corruption takes
> the packet to some other destination/port, so you don't see it; it's just=
 a drop as
> far as you are concerned. But it matters for whatever actually receives
> that corrupted packet on e.g. an altered port value. How do they detect a=
nd reject it
> from their stream?
>
> Bare IPv4 has the header checksum, so at least you can tell the endhost i=
s probably
> right. But sans UDP checksum, there's no (weak) ports check.
> IPv6 has no header checksum, so unchecked corruption to header or ports c=
an take
> the packet anywhere.
>
>> It's not the internetwork layer's job to second-guess the users; we can =
assume
>> that if someone sent a packet without an end-end checksum, they must hav=
e
>> worked out that for whatever they are doing, it's OK to leave it out.
>
> For what they're doing, but not for what everyone else is doing. Sure, LI=
SP or
> tunnels are fine, but odd behaviour on other applications at the same end=
points
> (or, with IPv6, in the same network) caused by missent packets with corru=
pted UDP
> packets? Hey, not your problem. Hey, you're working just fine.
>
> It's pollution and tragedy of the commons, basically.
>
> When you send with a zero UDP checksum, it's possible for the packet to b=
e
> received and processed anywhere.
>
> Secondguessing users who don't understand the problems they create IS
> the internetwork layer's job.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Noel Chiappa [jnc@mercury=
.lcs.mit.edu]
> Sent: 08 January 2014 23:32
> To: ietf@ietf.org; lisp@ietf.org; tsvwg@ietf.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: RE: [tsvwg] Milestones changed for tsvwg WG
>
>      > From: <l.wood@surrey.ac.uk>
>
>      > from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
>      >
>      >   The UDP checksum is zero because the inner packet usually alread=
y has
>      >   a end-end checksum, and the outer checksum adds no value.  [Salt=
zer]
>
>      > (That's a misreading of Saltzer - the UDP checksum is also protect=
ing
>      > against misdelivery and pseudoheader corruption
>
> If the content above the UDP header in this case were that of some sort o=
f
> application, you'd be right.
>
> But it's not.
>
> The UDP, outer and inner IP headers of LISP _together_ are effectively a
> layer three header ('get the packet from the source host to the destinati=
on
> host - and that's all, ffffolks - no reliability of any kind'). So the fa=
ct
> that it's not providing protection against misdelivery is... _exactly_ li=
ke
> the service that bare IPvN provides.
>
> In fact, since IPv6 doesn't even _have_ a header checksum, UDP in LISP is
> doing exactly what IPv6 does. Are you now claiming that IPv6 is fundament=
ally
> defective because it doesn't have a header checksum to guard against pack=
et
> mis-delivery?
>
>      > and 'usually' is not a good defence
>
> To say it at slightly greater length, 'the inner packet _either_ already =
has
> an end-end checksum (the usual case), in which case adding another one is=
 of
> little or no value, _or_ the sender deliverately sent their packet _witho=
ut_
> an end-end checksum, in which case they are _no worse off_ than they were
> before the packet was encapsulated'.
>
> It's not the internetwork layer's job to second-guess the users; we can a=
ssume
> that if someone sent a packet without an end-end checksum, they must have
> worked out that for whatever they are doing, it's OK to leave it out.
>
>
> Note that I am solely answering regarding the omission of UDP checksums w=
hen
> UDP is used as part of the internetworking layer, for encapsulating traff=
ic.
> I have not considered, and make no statement about, use of zero checksums
> in other ways/places.
>
>          Noel
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>

From l.wood@surrey.ac.uk  Wed Jan  8 19:00:00 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609DE1AE098 for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 19:00:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WaenYr1-CTHI for <ietf@ietfa.amsl.com>; Wed,  8 Jan 2014 18:59:58 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.142]) by ietfa.amsl.com (Postfix) with ESMTP id 897451AE030 for <ietf@ietf.org>; Wed,  8 Jan 2014 18:59:57 -0800 (PST)
Received: from [195.245.231.67:5848] by server-6.bemta-5.messagelabs.com id 0C/C9-16310-3A01EC25; Thu, 09 Jan 2014 02:59:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-82.messagelabs.com!1389236387!35269059!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27475 invoked from network); 9 Jan 2014 02:59:47 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-12.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 02:59:47 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Thu, 9 Jan 2014 02:59:29 +0000
From: <l.wood@surrey.ac.uk>
To: <david.black@emc.com>, <gorry@erg.abdn.ac.uk>
Date: Thu, 9 Jan 2014 02:59:28 +0000
Subject: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: AQHPDObQGmJ4SKwhQk6QfMrFWtjgXA==
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org, mpls@ietf.org, jnc@mit.edu, lisp@ietf.org, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 03:00:00 -0000

Thanks, David.

Apart from the pollute-other-ports aspect that I've discussed in
other mails, MPLS itself is not self-checking (GRE is for header and
payload -  if its optional checksum is used.) Without checking,  corrupt
the MPLS label, send it to another tunnel. Without checking, corrupt the
UDP port, send the packet elsewhere and pollute another port and stream.

I see L. Yong and X. Xu, who are coauthors of=20
draft-yong-tsvwg-gre-in-udp-encap,
are also authors of
draft-ietf-mpls-in-udp
which again plays fast and loose with UDP checksums.

This is clearly a widespread problem, and the reliability of the internet i=
s
being undermined.

We can class UDP zero checksum use as an attacks on other streams and
services, if that helps. Reliability is an unfashionable topic, but an atta=
ck?
That must be mitigated immediately.

Because they specify zero UDP checksums,=20
I oppose publication of draft-ietf-mpls-in-udp in its current form
I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current=
 form.
I oppose the IETF lisp documents.

regards
Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Black, David [david.black@emc.com]
Sent: 08 January 2014 23:20
To: Wood L  Dr (Electronic Eng); gorry@erg.abdn.ac.uk
Cc: lisp@ietf.org; jnc@mit.edu; tsvwg@ietf.org; ietf@ietf.org
Subject: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG=
)

Lloyd,

<tsvwg WG co-chair hat OFF>

This is only at the draft adoption stage - the tsvwg WG gets to take a hard
look at the zero checksum conditions in the gre-in-udp-encap draft and
make sure that they're right (the WG could even remove the support for
zero checksums) - that's among the good reasons for adopting the draft
in tsvwg as opposed to elsewhere.

Speaking of elsewhere, draft-ietf-mpls-in-udp is in IETF Last Call and has
language allowing zero UDP checksums - I might suggest that you (and anyone
else who cares about this topic) go read that draft and consider whether
making Last Call comments would be appropriate.

Thanks,
--David
</tsvwg WG co-chair hat OFF>

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of l.wood@surrey.ac=
.uk
> Sent: Wednesday, January 08, 2014 3:58 PM
> To: gorry@erg.abdn.ac.uk
> Cc: lisp@ietf.org; jnc@mit.edu; tsvwg@ietf.org; ietf@ietf.org
> Subject: Re: [tsvwg] Milestones changed for tsvwg WG
>
> Zero UDP checksums are being selected for convenience, without an appreci=
ation
> of the overall effects and  costs on other traffic. I see this is occurri=
ng in
> both tsvwg
> and lisp, and it's probably happening elsewhere:
>
> From the recently adopted by tsvwg draft:
> http://tools.ietf.org/html/draft-yong-tsvwg-gre-in-udp-encap-02
>    To simplify packet processing at the tunnel egress, packets destined
>    to this assigned UDP destination port [TBD] SHOULD have their UDP
>    checksum and Sequence flags set to zero because the egress tunnel
>    only needs to identify this protocol.  Although IPv6 [RFC2460]
>    restricts the processing a packet with the UDP checksum of zero,
>    [RFC6935] and [RFC6936] relax this constraint to allow the zero UDP
>    checksum.
>
> from http://tools.ietf.org/html/draft-ietf-lisp-introduction-03
>    The UDP checksum is zero because the inner packet usually already has
>    a end-end checksum, and the outer checksum adds no value.  [Saltzer]
>
> (That's a misreading of Saltzer - the UDP checksum is also protecting aga=
inst
> misdelivery and pseudoheader corruption, and 'usually' is not a good defe=
nce.
> For shame, Noel.)
>
> After all, the best examples of end2end systems failure are with zero
> checksums
> at the endhosts.
>
> The TCP and UDP checksums catch significant numbers of errors, e.g. Stone=
's
> work:
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pd=
f
> and some of those errors will appear in the headers, where they will send
> the data to other ports and destinations.
>
> The potential for polluting other ports and applications because
> there is no pseudoheader demultiplexing sanity check is there.
>
> IPv6 leaving this check implemented  on a per-transport basis has opened =
the
> door,
> and rewriting that section of RFC2460 in RFC6935 has taken the door off i=
ts
> hinges.
> These RFCs break the minimal multiplexing pseudoheader sanity check that
> RFC2460
> offered; IPv6 is a mess in so many ways, but making it worse?
>
> I think publishing RFC6935 and 6936 and letting in zero checksums again t=
o
> IPv6
> was a mistake, frankly. (alas, I wasn't paying much attention at the time=
 -
> moving countries etc.)
>
> A strong recommendation that UDP-Lite covering headers offers minimal
> computation
> overhead on tunnelled packets while protecting against polluting other po=
rts
> is one
> solution, while acknowledging deployment limitations. Section 2.4 of RFC6=
96 is
> mostly there.
> But zero UDP checksums should always come with copious warnings on the ef=
fects
> not on the
> carried traffic, which can have its own payload checks, but on traffic sh=
aring
> the network
> with traffic delivered with zero UDP checksums. Drafts relying on zero
> checksums should be discouraged, not adopted by workgroups.
>
> It's a tragedy of the commons, but the I'm-alright-Jack engineers who wan=
t
> zero udp checksums for their traffic, and do protect against the effects =
of
> zero
> checksums on their own payloads, won't care about effects on other traffi=
c.
> Hey, maybe this should be treated as an attack, which falls under perpass=
?
> That
> should get it attention...
>
> tsvwg needs to give (or get) some careful input on the implications here.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: gorry@erg.abdn.ac.uk [gorry@erg.abdn.ac.uk]
> Sent: 08 January 2014 12:55
> To: Wood L  Dr (Electronic Eng)
> Cc: tsvwg@ietf.org
> Subject: Re: [tsvwg] Milestones changed for tsvwg WG
>
> Lloyd,
>
> Here is a little context... which could help. The IETF agreed to update
> the UDP checksum behaviour for IPv6 in RFC 6935, but only subject to the
> applicability specified in RFC 6936.
>
> One of the reasons why a simple encapsulation like this needs to be done
> in tsvwg is to minimise the end-to-end implications on other traffic.
> Sure, using a zero checksum has such implications, and my own first
> concern is that the new GRE-in-UDP work follows the applicability
> statement in RFC 6936. To me, it seems the authors are heading this way -
> but maybe more help is needed. It would be no bad thing to highlight the
> implications of using zero checksums on other traffic.
>
> Gorry
>
> > Am I the only one who finds putting zero checksums in proposed standard=
s
> > to be a worrying
> > trend?
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: tsvwg [tsvwg-bounces@ietf.org] On Behalf Of IETF Secretariat
> > [ietf-secretariat-reply@ietf.org]
> > Sent: 07 January 2014 20:20
> > To: tsvwg@ietf.org
> > Subject: [tsvwg] Milestones changed for tsvwg WG
> >
> > Added milestone "Submit 'Specification of GRE in UDP encapsulation' to
> > IESG as a PS RFC", due December 2014.
> >
> > URL: http://datatracker.ietf.org/wg/tsvwg/charter/
> >
>
>


From randy@psg.com  Wed Jan  8 23:51:55 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4ADB51AE11A; Wed,  8 Jan 2014 23:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oANByb7vVI-F; Wed,  8 Jan 2014 23:51:54 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 154B21AE08E; Wed,  8 Jan 2014 23:51:54 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W1AOt-0007Zj-Ra; Thu, 09 Jan 2014 07:51:36 +0000
Date: Thu, 09 Jan 2014 16:51:33 +0900
Message-ID: <m2d2k1a8ze.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: <l.wood@surrey.ac.uk>
Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Thu_Jan__9_16:51:26_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 07:51:55 -0000

--pgp-sign-Multipart_Thu_Jan__9_16:51:26_2014-1
Content-Type: text/plain; charset=US-ASCII

> Because they specify zero UDP checksums,
> I oppose publication of draft-ietf-mpls-in-udp in its current form
> I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current form.
> I oppose the IETF lisp documents.

lloyd,

i think i understand your position.  but i disagree with preventing wg
adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
see wg adoption as how we get to discuss and work on a document, not as
approval of the document.  as david said, i think we need to discuss it
so we can decide if it should be fixed.  to do so, we have to adopt it.

randy
--pgp-sign-Multipart_Thu_Jan__9_16:51:26_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJSzlUEAAoJEMzMBey4OgLtpjYH/iM5qSYEPIFoK6ay0D9mYB/t
gqH8nCOV6Kw+E9VWgwfPs2fwtuLboUrxn4aJF3M84FCDcg1pFks7d6g2d3EDx5wJ
KLcpcq9Kg+hAdU+oWYAkmT+aA3HtEdCysVqMlo15G4Cm46TI2VycKEBAzhCGe1ue
C8j66MfVUCIrIqLeZEAb6mzXUsqpzZnNKaGBtatHp/4TGMWGllwCVC/va46IvKWE
6aYtgxWUDO4g07Iu/c7SdJQcQHUh58o785Nyc7jhuEXTV6DTJe6Rtte+aXOr0hmU
blDwmEf5ixrkuT4YO+mPoKpgmwMk4VLxcpt22pe29VRmS9DDiVtckX3KXgoPJsc=
=IiRO
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Thu_Jan__9_16:51:26_2014-1--

From bclaise@cisco.com  Wed Jan  8 23:58:15 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF61B1AE145; Wed,  8 Jan 2014 23:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U0F0_F-11_h7; Wed,  8 Jan 2014 23:58:12 -0800 (PST)
Received: from bgl-iport-3.cisco.com (bgl-iport-3.cisco.com [72.163.197.27]) by ietfa.amsl.com (Postfix) with ESMTP id 31B1C1AE143; Wed,  8 Jan 2014 23:58:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20061; q=dns/txt; s=iport; t=1389254282; x=1390463882; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=6WCVAPa3maq1sHtO/JJd0o4tWBakjf1u8JfDoCiN05w=; b=JhmffVA3gkKRm6uexBq8r7USywb7r5HX5+/4LMm3ntZUh38DgKjbfyph T67pacqKQEmbO2A6eGYRCFuX4PT/+aaYBFG29jOtjLzICJcevLy7WRToW r1ON87X1vL4SLEzD0WMBeO21gYziW5NsLN46h/gG0ZFFUD5vAj0+viKsL c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqUEAAVWzlJIo8UY/2dsb2JhbABZg0OJMbAZT4EjdIIlAQEBBAEBAWgDCgEMBAsRAwECAQkWBAQHCQMCAQIBFR8JCAYNAQUCAQEFh3sNxGkXjiMRAT8RBgEGA4QuBIVXhwSHWINkhkV7hR2FOIFvgT87gTU
X-IronPort-AV: E=Sophos;i="4.95,629,1384300800"; d="scan'208,217";a="3268602"
Received: from vla196-nat.cisco.com (HELO bgl-core-2.cisco.com) ([72.163.197.24]) by bgl-iport-3.cisco.com with ESMTP; 09 Jan 2014 07:57:59 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by bgl-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s097vtdR014026; Thu, 9 Jan 2014 07:57:56 GMT
Message-ID: <52CE5683.5050907@cisco.com>
Date: Thu, 09 Jan 2014 08:57:55 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database YANG Module) to Proposed Standard
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net>	<52A1ACEF.6080307@cisco.com>	<52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com>
In-Reply-To: <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010505080609040308070900"
Cc: SM <sm@resistor.net>, Paul Eggert <eggert@cs.ucla.edu>, IETF-Discussion list <ietf@ietf.org>, NETMOD Working Group <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 07:58:16 -0000

This is a multi-part message in MIME format.
--------------010505080609040308070900
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Andy,
> Hi,
>
> By "this one" I assume you mean the question "Why Proposed Standard?"
I meant the other questions in this email, most importantly.
>
> This YANG module is meant to be imported by other standard YANG modules,
> which creates a normative reference in each importing RFC. We try to avoid
> standard modules that rely on non-standard modules. At first, (e.g, 
> RFC 5277,
> RFC 5717) the YANG modules were not normative. But since 2010,
> (RFC 6020) all YANG modules are normative and XSD is no longer used.
Thanks for your answer.

Regards, Benoit
>
>
> Andy
>
>
> On Wed, Jan 8, 2014 at 8:37 AM, Benoit Claise <bclaise@cisco.com 
> <mailto:bclaise@cisco.com>> wrote:
>
>     Dear all,
>
>     Sadly, I have not seen a reply to this one.
>     So let me start the discussion, copying both the ietf-discussion
>     and the netmod WG mailers.
>     See in-line.
>>     Dear all,
>>
>>     Here is some feedback from the IETF discussion list.
>>     I would appreciate if the author and document shepherd could
>>     follow up. Ideally on the IETF discussion list.
>>
>>     Regards, Benoit
>>
>>
>>     -------- Original Message --------
>>     Subject: 	Re: Last Call:
>>     <draft-ietf-netmod-iana-timezones-03.txt> (IANA Timezone Database
>>     YANG Module) to Proposed Standard
>>     Date: 	Tue, 3 Dec 2013 19:36:31 -0800
>>     From: 	SM <sm@resistor.net> <mailto:sm@resistor.net>
>>     To: 	<ietf@ietf.org> <mailto:ietf@ietf.org>
>>
>>
>>
>>     At 12:46 03-12-2013, The IESG wrote:
>>     >The IESG has received a request from the NETCONF Data Modeling Language
>>     >WG (netmod) to consider the following document:
>>     >- 'IANA Timezone Database YANG Module'
>>     >   <draft-ietf-netmod-iana-timezones-03.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  <mailto:ietf@ietf.org>  mailing lists by 2013-12-17. Exceptionally, comments may be
>>
>>     There is the following question in the document shepherd write-up:
>>
>>        Why is this the proper type of RFC?
>>
>>     I did not see an answer to that question.
>     Not sure what you propose here. Proposed Standard seems right to me.
>     From http://www.rfc-editor.org/RFCoverview.html
>
>
>             RFC Categories
>
>         Each RFC has a "category" or "status" designation. The
>         possible categories (see *RFC 2026*
>         <http://www.rfc-editor.org/rfc/rfc2026.txt> "The Internet
>         Standards Process -- Revision 3") are:
>
>           * INTERNET STANDARD, DRAFT STANDARD (deprecated; see RFC
>             6410 <http://www.rfc-editor.org/rfc/rfc6410.txt>),
>             PROPOSED STANDARD
>
>             These are /Standards Track/ documents, official
>             specifications of the Internet protocol suite defined by
>             the Internet Engineering Task Force (IETF)
>             <http://www.ietf.org> and its steering group the IESG.
>
>           * BEST CURRENT PRACTICE
>
>             These are official guidelines and recommendations, but not
>             standards, from the IETF.
>
>           * INFORMATIONAL, EXPERIMENTAL
>
>             These non-standards documents may originate in the IETF or
>             may be independent submissions.
>
>           * HISTORIC
>
>             These are former standards that have been actively
>             deprecated.
>
>>     The WGLC was from 5 July to 22 July.  There wasn't any comments
>>     during the WGLC.  The only comment I found was one posted on 9 August.
>>
>>     In Section 1:
>>
>>        "The iana-timezones YANG module defines the iana-
>>         timezone type, which is a serialization of the existing IANA Time
>>         Zone registry [RFC6557] into YANG format."
>>
>>     The terminology in RFC 6557 defines a TZ Database sometimes referred
>>     to as the "Olson Database".  There isn't any mention of a "IANA Time
>>     Zone registry".  I suggest using the same name as in RFC 6557.
>     That makes sense.
>>     >From Section 3:
>>
>>        'The iana-timezones module is intended to reflect the IANA "timezone
>>         database" [RFC6557].  When a timezone location is added to the
>>         database, the "iana-timezone" enumeration MUST be updated as defined
>>         in RFC 6020 Section 10 to add the newly created timezone location to
>>         the enumeration.  The new "enum" statement MUST be added to the
>>         "iana-timezone" typedef with the same name as the newly added
>>         timezone location.  A new enum value MUST be allocated by IANA and
>>         applied to the newly created enum entry.  New entries MAY be placed
>>         in any order in the enumeration as long as the previously assigned
>>         enumeration values are not changed.
>>
>>         If a timezone location is removed from the IANA timezone database,
>>         the corresponding existing enum statement is kept and a status
>>         statement is added to mark the enum entry as 'obsolete'.'
>>
>>     The maintainer of the TZ database is responsible for the TZ
>>     Database.  The person does not work for IANA.
>     Correct, but see BCP 175: Procedures for Maintaining the Time Zone
>     Database:
>     <http://www.iana.org/go/rfc6557>
>
>         The TZ Coordinator is an IANA Designated Expert
>
>     Are you questioning the term "IANA timezone database", which should be "TZ Database" according to BCP 175?
>
>>     I don't think that
>>     IANA keeps track of the contents of the TZ Database as it was not
>>     asked to do that work.
>     I think it does: http://www.iana.org/time-zones
>>     I don't see the value of using RFC 2119 key
>>     word for the IANA Considerations.
>
>>     I suggest not creating the registry proposed in this draft.  The TZ
>>     database has strived to keep out of political issues.  Adding such a
>>     registry will pave the way for such issues.
>     Well, we need to specify the system clock in the following YANG
>     module
>     (https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/),
>     and hence we require a way to represent the TZ in YANG.
>
>     Regards, Benoit
>>     Regards,
>>     -sm
>>
>>     .
>>
>>
>>
>>
>>
>>     _______________________________________________
>>     netmod mailing list
>>     netmod@ietf.org  <mailto:netmod@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/netmod
>
>


--------------010505080609040308070900
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Andy,<br>
    </div>
    <blockquote
cite="mid:CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr">Hi,
        <div><br>
        </div>
        <div>By "this one" I assume you mean the question "Why Proposed
          Standard?"</div>
      </div>
    </blockquote>
    I meant the other questions in this email, most importantly.<br>
    <blockquote
cite="mid:CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>This YANG module is meant to be imported by other standard
          YANG modules,</div>
        <div>which creates a normative reference in each importing RFC.
          We try to avoid</div>
        <div>standard modules that rely on non-standard modules. At
          first, (e.g, RFC 5277,</div>
        <div>RFC 5717) the YANG modules were not normative. But since
          2010,</div>
        <div>(RFC 6020) all YANG modules are normative and XSD is no
          longer used.</div>
      </div>
    </blockquote>
    Thanks for your answer.<br>
    <br>
    Regards, Benoit<br>
    <blockquote
cite="mid:CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div class="gmail_extra"><br>
            <br>
            Andy</div>
          <div class="gmail_extra"><br>
          </div>
          <div class="gmail_extra"><br>
            <div class="gmail_quote">On Wed, Jan 8, 2014 at 8:37 AM,
              Benoit Claise <span dir="ltr">&lt;<a
                  moz-do-not-send="true" href="mailto:bclaise@cisco.com"
                  target="_blank">bclaise@cisco.com</a>&gt;</span>
              wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div bgcolor="#FFFFFF" text="#000000">
                  <div>Dear all,<br>
                    <br>
                    Sadly, I have not seen a reply to this one.<br>
                    So let me start the discussion, copying both the
                    ietf-discussion and the netmod WG mailers.<br>
                    See in-line.<br>
                  </div>
                  <blockquote type="cite"> Dear all,<br>
                    <br>
                    Here is some feedback from the IETF discussion list.<br>
                    I would appreciate if the author and document
                    shepherd could follow up. Ideally on the IETF
                    discussion list.<br>
                    <br>
                    Regards, Benoit<br>
                    <div><br>
                      <br>
                      -------- Original Message --------
                      <table cellpadding="0" cellspacing="0" border="0">
                        <tbody>
                          <tr>
                            <th align="RIGHT" nowrap="nowrap"
                              valign="BASELINE">Subject: </th>
                            <td>Re: Last Call:
                              &lt;draft-ietf-netmod-iana-timezones-03.txt&gt;
                              (IANA Timezone Database YANG Module) to
                              Proposed Standard</td>
                          </tr>
                          <tr>
                            <th align="RIGHT" nowrap="nowrap"
                              valign="BASELINE">Date: </th>
                            <td>Tue, 3 Dec 2013 19:36:31 -0800</td>
                          </tr>
                          <tr>
                            <th align="RIGHT" nowrap="nowrap"
                              valign="BASELINE">From: </th>
                            <td>SM <a moz-do-not-send="true"
                                href="mailto:sm@resistor.net"
                                target="_blank">&lt;sm@resistor.net&gt;</a></td>
                          </tr>
                          <tr>
                            <th align="RIGHT" nowrap="nowrap"
                              valign="BASELINE">To: </th>
                            <td><a moz-do-not-send="true"
                                href="mailto:ietf@ietf.org"
                                target="_blank">&lt;ietf@ietf.org&gt;</a></td>
                          </tr>
                        </tbody>
                      </table>
                      <br>
                      <br>
                      <pre>At 12:46 03-12-2013, The IESG wrote:
&gt;The IESG has received a request from the NETCONF Data Modeling Language
&gt;WG (netmod) to consider the following document:
&gt;- 'IANA Timezone Database YANG Module'
&gt;   &lt;draft-ietf-netmod-iana-timezones-03.txt&gt; as Proposed Standard
&gt;
&gt;The IESG plans to make a decision in the next few weeks, and solicits
&gt;final comments on this action. Please send substantive comments to the
&gt;<a moz-do-not-send="true" href="mailto:ietf@ietf.org" target="_blank">ietf@ietf.org</a> mailing lists by 2013-12-17. Exceptionally, comments may be

There is the following question in the document shepherd write-up:

  Why is this the proper type of RFC?

I did not see an answer to that question.</pre>
                    </div>
                  </blockquote>
                  Not sure what you propose here. Proposed Standard
                  seems right to me.<br>
                  From <a moz-do-not-send="true"
                    href="http://www.rfc-editor.org/RFCoverview.html"
                    target="_blank">http://www.rfc-editor.org/RFCoverview.html</a><br>
                  <blockquote>
                    <h2><a moz-do-not-send="true"
                        name="14372b760faf8661_categories">RFC
                        Categories</a></h2>
                    <p> Each RFC has a "category" or "status"
                      designation. The possible categories (see <a
                        moz-do-not-send="true"
                        href="http://www.rfc-editor.org/rfc/rfc2026.txt"
                        target="_blank"><b>RFC 2026</b></a> "The
                      Internet Standards Process -- Revision 3") are: </p>
                    <ul>
                      <li> INTERNET STANDARD, DRAFT STANDARD
                        (deprecated; see <a moz-do-not-send="true"
                          href="http://www.rfc-editor.org/rfc/rfc6410.txt"
                          target="_blank">RFC 6410</a>), PROPOSED
                        STANDARD
                        <p> These are <i>Standards Track</i> documents,
                          official specifications of the Internet
                          protocol suite defined by the <a
                            moz-do-not-send="true"
                            href="http://www.ietf.org" target="_blank">Internet
                            Engineering Task Force (IETF)</a> and its
                          steering group the IESG. </p>
                      </li>
                      <li> BEST CURRENT PRACTICE
                        <p> These are official guidelines and
                          recommendations, but not standards, from the
                          IETF. </p>
                      </li>
                      <li> INFORMATIONAL, EXPERIMENTAL
                        <p> These non-standards documents may originate
                          in the IETF or may be independent submissions.
                        </p>
                      </li>
                      <li> HISTORIC
                        <p> These are former standards that have been
                          actively deprecated. </p>
                      </li>
                    </ul>
                  </blockquote>
                  <blockquote type="cite">
                    <div>
                      <pre>The WGLC was from 5 July to 22 July.  There wasn't any comments 
during the WGLC.  The only comment I found was one posted on 9 August.

In Section 1:

  "The iana-timezones YANG module defines the iana-
   timezone type, which is a serialization of the existing IANA Time
   Zone registry [RFC6557] into YANG format."

The terminology in RFC 6557 defines a TZ Database sometimes referred 
to as the "Olson Database".  There isn't any mention of a "IANA Time 
Zone registry".  I suggest using the same name as in RFC 6557.</pre>
                    </div>
                  </blockquote>
                  That makes sense.<br>
                  <blockquote type="cite">
                    <div>
                      <pre>&gt;From Section 3:

  'The iana-timezones module is intended to reflect the IANA "timezone
   database" [RFC6557].  When a timezone location is added to the
   database, the "iana-timezone" enumeration MUST be updated as defined
   in RFC 6020 Section 10 to add the newly created timezone location to
   the enumeration.  The new "enum" statement MUST be added to the
   "iana-timezone" typedef with the same name as the newly added
   timezone location.  A new enum value MUST be allocated by IANA and
   applied to the newly created enum entry.  New entries MAY be placed
   in any order in the enumeration as long as the previously assigned
   enumeration values are not changed.

   If a timezone location is removed from the IANA timezone database,
   the corresponding existing enum statement is kept and a status
   statement is added to mark the enum entry as 'obsolete'.'

The maintainer of the TZ database is responsible for the TZ 
Database.  The person does not work for IANA.  </pre>
                    </div>
                  </blockquote>
                  Correct, but see <a moz-do-not-send="true"
                    href="http://www.iana.org/go/rfc6557"
                    target="_blank">BCP 175: Procedures for Maintaining
                    the Time Zone Database:<br>
                  </a>
                  <pre>   The TZ Coordinator is an IANA Designated Expert

Are you questioning the term "IANA timezone database", which should be "TZ Database" according to BCP 175?
</pre>
                  <blockquote type="cite">
                    <div>
                      <pre>I don't think that 
IANA keeps track of the contents of the TZ Database as it was not 
asked to do that work.  </pre>
                    </div>
                  </blockquote>
                  I think it does: <a moz-do-not-send="true"
                    href="http://www.iana.org/time-zones"
                    target="_blank">http://www.iana.org/time-zones</a>
                  <blockquote type="cite">
                    <div>
                      <pre>I don't see the value of using RFC 2119 key 
word for the IANA Considerations.</pre>
                    </div>
                  </blockquote>
                  <br>
                  <blockquote type="cite">
                    <div>
                      <pre>I suggest not creating the registry proposed in this draft.  The TZ 
database has strived to keep out of political issues.  Adding such a 
registry will pave the way for such issues.</pre>
                    </div>
                  </blockquote>
                  Well, we need to specify the system clock in the
                  following YANG module (<a moz-do-not-send="true"
                    href="https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/"
                    target="_blank">https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/</a>),

                  and hence we require a way to represent the TZ in
                  YANG.<br>
                  <br>
                  Regards, Benoit<br>
                  <blockquote type="cite">
                    <div>
                      <pre>Regards,
-sm 

.

</pre>
                      <br>
                    </div>
                    <br>
                    <br>
                    <fieldset></fieldset>
                    <br>
                    <pre>_______________________________________________
netmod mailing list
<a moz-do-not-send="true" href="mailto:netmod@ietf.org" target="_blank">netmod@ietf.org</a>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/netmod" target="_blank">https://www.ietf.org/mailman/listinfo/netmod</a>
</pre>
                  </blockquote>
                  <br>
                </div>
              </blockquote>
            </div>
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------010505080609040308070900--

From l.wood@surrey.ac.uk  Thu Jan  9 00:09:16 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E52A71AE06F; Thu,  9 Jan 2014 00:09:15 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gG1Cmobgtscu; Thu,  9 Jan 2014 00:09:13 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.176]) by ietfa.amsl.com (Postfix) with ESMTP id CCA661AE06D; Thu,  9 Jan 2014 00:09:12 -0800 (PST)
Received: from [195.245.230.131:54618] by server-16.bemta-3.messagelabs.com id 39/23-26128-E195EC25; Thu, 09 Jan 2014 08:09:02 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1389254942!29878430!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31345 invoked from network); 9 Jan 2014 08:09:02 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 9 Jan 2014 08:09:02 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 9 Jan 2014 08:09:01 +0000
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>
Date: Thu, 9 Jan 2014 08:06:57 +0000
Subject: RE: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8ND6LbmabIHemQQc6QHOWUwU/54gAAiHqr
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346B5@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>, <m2d2k1a8ze.wl%randy@psg.com>
In-Reply-To: <m2d2k1a8ze.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 08:09:16 -0000

Randy,

okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get con=
sensus on  it. And then the authors can adopt that consensus for mpls-in-ud=
p, which overlaps in authorship...

thanks,

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Randy Bush [randy@psg.com]
Sent: 09 January 2014 07:51
To: Wood L  Dr (Electronic Eng)
Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org=
; jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsv=
wg] Milestones changed for tsvwg WG)

> Because they specify zero UDP checksums,
> I oppose publication of draft-ietf-mpls-in-udp in its current form
> I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its curre=
nt form.
> I oppose the IETF lisp documents.

lloyd,

i think i understand your position.  but i disagree with preventing wg
adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
see wg adoption as how we get to discuss and work on a document, not as
approval of the document.  as david said, i think we need to discuss it
so we can decide if it should be fixed.  to do so, we have to adopt it.

randy

From sm@resistor.net  Thu Jan  9 02:19:22 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FDD41AE231; Thu,  9 Jan 2014 02:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBXfG4kOhoGa; Thu,  9 Jan 2014 02:19:20 -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 AE1B81AE1C7; Thu,  9 Jan 2014 02:19:20 -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 s09AIdLH022553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 02:18:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389262726; bh=64uf2V4TqXeAJ+4mPGZXemkoysQgNQc3hmM8BS79Zc0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xM0T01d4iMmYP4bBzz1AOOC/nytuux2uzdkImFmW/G0N3yxhoWKl/fs49iGekRZ0W C6/yidH2hsBCXBqpVwJ0nLSwI0ViBfQwfSPysFT6FCnCk1VfxxxI/+7mj0u+Xqyrr2 HpE4GBcqyURISef8c3blbchX4SBM3xUg9a4VAy9A=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1389262726; i=@resistor.net; bh=64uf2V4TqXeAJ+4mPGZXemkoysQgNQc3hmM8BS79Zc0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ae+PJpVSgFCuhQblAJwn255CRJ7dzi8BpfSOjxzgI4kjh0xbb/jUocWxCv2L7OkI4 19QVpOaHiNnqCLcF6gNNyYCyAqFGiRcpFT0+tSyRAjju93sk9b+GQjRMkGlPFjlnn+ EY1gHj4qoF5PYDYz/f12ez1TksHBvbyO+bFbVEFA=
Message-Id: <6.2.5.6.2.20140108233958.0a849e58@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Jan 2014 02:16:38 -0800
To: Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>
From: SM <sm@resistor.net>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
In-Reply-To: <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com>
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 10:19:22 -0000

Hi Benoit, Andy,
At 08:37 08-01-2014, Benoit Claise wrote:
>Not sure what you propose here. Proposed Standard seems right to me.
> From http://www.rfc-editor.org/RFCoverview.html
>
>RFC Categories
>
>Each RFC has a "category" or "status" designation. The possible 
>categories (see RFC 2026 "The Internet Standards Process -- Revision 3") are:
>INTERNET STANDARD, DRAFT STANDARD (deprecated; see RFC 6410), 
>PROPOSED STANDARD
>
>These are Standards Track documents, official specifications of the 
>Internet protocol suite defined by the Internet Engineering Task 
>Force (IETF) and its steering group the IESG.
>BEST CURRENT PRACTICE
>
>These are official guidelines and recommendations, but not 
>standards, from the IETF.
>INFORMATIONAL, EXPERIMENTAL
>
>These non-standards documents may originate in the IETF or may be 
>independent submissions.
>HISTORIC
>
>These are former standards that have been actively deprecated.

At 09:09 08-01-2014, Andy Bierman wrote:
>By "this one" I assume you mean the question "Why Proposed Standard?"
>
>This YANG module is meant to be imported by other standard YANG modules,
>which creates a normative reference in each importing RFC. We try to avoid
>standard modules that rely on non-standard modules. At first, (e.g, RFC 5277,
>RFC 5717) the YANG modules were not normative. But since 2010,
>(RFC 6020) all YANG modules are normative and XSD is no longer used.

I included the comment from Andy Bierman above as it is also related 
to the document status.

If I understood the argument, it is that this YANG module would be 
referenced by other standard YANG modules and that is why the 
intended status is "Proposed Standard".  The argument from Benoit 
Claise is that the document is on the Standards Track as it is an 
official specification of the Internet protocol suite defined by the 
Internet Engineering Task Force.  I'll consider the question as 
addressed as the matter could be argued that way.

>>The WGLC was from 5 July to 22 July.  There wasn't any comments
>>during the WGLC.  The only comment I found was one posted on 9 August.

According to the write-up, the "document has strong consensus".  In 
my opinion that determination is questionable.

>Correct, but see BCP 175: Procedures for Maintaining the Time Zone Database:
>
>    The TZ Coordinator is an IANA Designated Expert
>
>Are you questioning the term "IANA timezone database", which should 
>be "TZ Database" according to BCP 175?

I suggested using the same name as in RFC 6557.

TZ locations can be controversial every now and then.  There have 
been discussions about having a (TZ) location for an island inhabited 
by penguins. :-)   There have been arguments about changing a 
location as a matter of national pride.  There has been an attempt to 
take up a TZ mailing list disagreement with IANA.  IETF 
standardization of this information makes it look official and paves 
the way for governance questions.

>I think it does: http://www.iana.org/time-zones

What I meant was that IANA provides hosting services.  IANA does not 
track the changes.

>Well, we need to specify the system clock in the following YANG 
>module 
>(https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/), 
>and hence we require a way to represent the TZ in YANG.

Would it be possible to use "timezone-utc-offset" only and not have 
"timezone-location"?  RFC 5277 references RFC 3339 for time zones.

Regards,
-sm



From adrian@olddog.co.uk  Thu Jan  9 02:22:07 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78C701AE1AE; Thu,  9 Jan 2014 02:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVl5ZX95-Aw7; Thu,  9 Jan 2014 02:22:04 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3AF1AE23A; Thu,  9 Jan 2014 02:22:04 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s09ALoZl029262; Thu, 9 Jan 2014 10:21:50 GMT
Received: from 950129200 (15.21.90.92.rev.sfr.net [92.90.21.15]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s09ALjKd029119 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jan 2014 10:21:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>, <randy@psg.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>, <m2d2k1a8ze.wl%randy@psg.com> <290E20B455C66743BE178C5C84F1240847E63346B5@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346B5@EXMB01CMS.surrey.ac.uk>
Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Date: Thu, 9 Jan 2014 10:21:44 -0000
Message-ID: <012801cf0d24$9b80b180$d2821480$@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: AQLp3cWoqiSzZKGjmFXJEPC82F9z6gH14gYaAYJCBgICOkjTg5gY93Xw
Content-Language: en-gb
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 10:22:07 -0000

Lloyd and Randy,

With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls, so
thanks for the comments.

We did take the precaution of sending this I-D for an early TSV Directorate
review because of the concern about a number of factors and the overlap with
tsvwg work, but the review came back "clean". Of course, such a review is just
one person, so this conversation is good.

Wrt zero checksum, where do you stand on nested checksums? There is some claim
that they represent a waste of processing. I am not convinced by that when each
layer is using dedicated hardware (that can presumably process checksums at line
speed), but I am interested in the consequences for cheap hardware and for
software implementations (as have been claimed to be some of the motivations for
this work).

Other TSV-related issues that surely pop up are:
- allocation of ports for foo-in-UDP
- congestion control

Please note that there are a number of I-Ds that you missed in your broad sweep
of "I am opposed". You should probably look at the NVGRE and VXLAN work (which I
think is lurking around the NVO3 working group) because that is also looking at
UDP encaps of a tunnelling protocol.

Thanks,
Adrian

Health warnings:
I am responsible AD for draft-ietf-mpls-in-udp
I am a co-author of the gre-in-udp draft.

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
> Sent: 09 January 2014 08:07
> To: randy@psg.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com;
> tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:
> [tsvwg] Milestones changed for tsvwg WG)
> 
> Randy,
> 
> okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
> consensus on  it. And then the authors can adopt that consensus for
mpls-in-udp,
> which overlaps in authorship...
> 
> thanks,
> 
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Randy Bush [randy@psg.com]
> Sent: 09 January 2014 07:51
> To: Wood L  Dr (Electronic Eng)
> Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org;
> jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
> Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg]
> Milestones changed for tsvwg WG)
> 
> > Because they specify zero UDP checksums,
> > I oppose publication of draft-ietf-mpls-in-udp in its current form
> > I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current
> form.
> > I oppose the IETF lisp documents.
> 
> lloyd,
> 
> i think i understand your position.  but i disagree with preventing wg
> adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
> see wg adoption as how we get to discuss and work on a document, not as
> approval of the document.  as david said, i think we need to discuss it
> so we can decide if it should be fixed.  to do so, we have to adopt it.
> 
> randy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From j.schoenwaelder@jacobs-university.de  Thu Jan  9 02:58:22 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9311AE135; Thu,  9 Jan 2014 02:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.788
X-Spam-Level: 
X-Spam-Status: No, score=-2.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F_FiawAYF1aV; Thu,  9 Jan 2014 02:58:20 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id D4D1E1AE157; Thu,  9 Jan 2014 02:58:19 -0800 (PST)
Received: from localhost (demetrius3.jacobs-university.de [212.201.44.48]) by hermes.jacobs-university.de (Postfix) with ESMTP id F420D20075; Thu,  9 Jan 2014 11:58:09 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius3.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id NRZ4WVpXzanz; Thu,  9 Jan 2014 11:58:09 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 082A520035; Thu,  9 Jan 2014 11:58:09 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 3E88D2A7F78C; Thu,  9 Jan 2014 11:58:06 +0100 (CET)
Date: Thu, 9 Jan 2014 11:58:05 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: SM <sm@resistor.net>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
Message-ID: <20140109105804.GA44893@elstar.local>
Mail-Followup-To: SM <sm@resistor.net>, Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>, ietf@ietf.org, netmod@ietf.org
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com> <6.2.5.6.2.20140108233958.0a849e58@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20140108233958.0a849e58@resistor.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Andy Bierman <andy@yumaworks.com>, netmod@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 10:58:22 -0000

On Thu, Jan 09, 2014 at 02:16:38AM -0800, SM wrote:
> 
> >>The WGLC was from 5 July to 22 July.  There wasn't any comments
> >>during the WGLC.  The only comment I found was one posted on 9 August.
> 
> According to the write-up, the "document has strong consensus".  In
> my opinion that determination is questionable.
> 

People want to be able to configure timezones using the timezone
naming scheme commonly supported by operating systems (e.g.,
Europe/Paris). This document defines a serialization of the timezone
names into YANG format for this purpose. I believe there was indeed
strong concensus on this in the WG.

> TZ locations can be controversial every now and then.  There have
> been discussions about having a (TZ) location for an island
> inhabited by penguins. :-)   There have been arguments about
> changing a location as a matter of national pride.  There has been
> an attempt to take up a TZ mailing list disagreement with IANA.
> IETF standardization of this information makes it look official and
> paves the way for governance questions.

This document aims at establishing an IANA maintained serialization of
whatever list of names the timezone database contains. It does not
change the way the TZ coordinator, an IANA Designated Expert, takes
decisions. Perhaps this needs to be stated more explicit.

So far (in the MIB world), the initial versions of IANA maintained
modules were published as Proposed Standards on the standards track
(although the only thing that really remains valid over time are the
IANA considerations, which however often require the initial module to
be available). We simply followed this practice.

> >Well, we need to specify the system clock in the following YANG
> >module
> >(https://datatracker.ietf.org/doc/draft-ietf-netmod-system-mgmt/),
> >and hence we require a way to represent the TZ in YANG.
> 
> Would it be possible to use "timezone-utc-offset" only and not have
> "timezone-location"?  RFC 5277 references RFC 3339 for time zones.

There was concensus in the WG that it is desirable to configure
timezones by name (e.g., Europe/Paris) instead of having only hard
coded UTC offsets - the benefits should be obvious.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From stbryant@cisco.com  Thu Jan  9 02:59:23 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598A31AE135; Thu,  9 Jan 2014 02:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZAx0xcNlXw_k; Thu,  9 Jan 2014 02:59:21 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 81E0A1AE215; Thu,  9 Jan 2014 02:59:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=399; q=dns/txt; s=iport; t=1389265152; x=1390474752; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Qbe2VRt6TGgmdKkwK0vrwchK/iSeGfGGNd3cr1ckZPM=; b=EO/vraLAtH2nDac172HbQ2TDFlN02f4DmnCrHJqkVioUI1jQsn84Vnk1 fK/OaPU/lMpgniKE//8hSFdp+pOXCUXQlWRxN6lBmilOL50soeCMsXGVo fYQJuSyS65zUyPh569yL7IjwaRZYktZDplPX7s6H7jmeUFcuwWe9aMH2Q w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAHWAzlKQ/khL/2dsb2JhbABZDoJ9ulOBEBZ0giUBAQEEOEABEAsYCRYECwkDAgECAUUHDAEFAgEBiADFEBePBQeENwEDmBeSFYFvfz8
X-IronPort-AV: E=Sophos;i="4.95,630,1384300800";  d="scan'208";a="3380445"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 09 Jan 2014 10:59:10 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s09Ax9RB017045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 10:59:10 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s09Ax8Lc029902; Thu, 9 Jan 2014 10:59:08 GMT
Message-ID: <52CE80FC.9060306@cisco.com>
Date: Thu, 09 Jan 2014 10:59:08 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, david.black@emc.com, gorry@erg.abdn.ac.uk
Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mpls@ietf.org, tsvwg@ietf.org, jnc@mit.edu, ietf@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 10:59:23 -0000

On 09/01/2014 02:59, l.wood@surrey.ac.uk wrote:
> MPLS itself is not self-checking (GRE is for header and
> payload -  if its optional checksum is used.) Without checking,  corrupt
> the MPLS label, send it to another tunnel.
Lloyd

I would be interested in what operators are observing in their
network, because I have never heard a concern expressed that this
was happening.

- Stewart

From john-ietf@jck.com  Thu Jan  9 03:50:51 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E0E61AE21D for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 03:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIhRbeFH3r8n for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 03:50:48 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 88ED11AE157 for <ietf@ietf.org>; Thu,  9 Jan 2014 03:50:48 -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 1W1E8C-00096G-8V; Thu, 09 Jan 2014 06:50:36 -0500
Date: Thu, 09 Jan 2014 06:50:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: DNS design (was: Re: Split the IANA functions?)
Message-ID: <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com>
In-Reply-To: <52CC1618.1090605@cisco.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 11:50:51 -0000

--On Tuesday, January 07, 2014 15:58 +0100 Eliot Lear
<lear@cisco.com> wrote:

> Andrew,
> 
> It's clear that I wasn't clear.  Deciding on a tree structure
> has political implications, be that DNS, RPKI, or other (and
> there are other).  To ignore those implications would be
> unwise.  They are weighed against technical considerations, as
> always.
>...

Eliot,

In the hope of focusing the discussion a bit, I think it would
be more accurate to say that "having a tree structure...r
"having decided on a tree structure...".

It feels a little strange for me to be defending the DNS design
because I've never been a huge fan of some aspects of it, but a
little bit of insight into the context of those decisions may be
helpful.

I was not involved in the DNS design process, but I was doing
work on databases, including distributed databases, at the time
in the early to mid-1980s.  Against the backdrop of the database
state of the art at the time, if one started with design
criteria of approximately:

-- replacing the name-to-address and
	name-to-limited-supplementary-information functions of
	the Host Table without significant loss of functionality
-- having a hierarchical name structure (which does not,
	itself, imply a hierarchical database)
-- having something that could be administratively
	distributed at multiple levels of the name structure
-- having a distributed database that could be plausibly
	implemented without lock-commit-acknowledge or
	journal-based update facilities
-- having an arrangement that would facilitate local
	caching, not just for performance but as a mechanism to
	allow systems that were temporarily disconnected from
	all or part of the network to keep functioning reasonably
-- The result needed to be plausible for non-specialists
	to implement in a way that would interoperable.
	
Most of the above are documented in the various pre-DNS papers.
Most are also pretty obvious.  Given how bad some
implementations have been, there is a pretty good case to be
made that the design failed on the last criterion, but a
non-hierarchical alternative, especially given the then state of
the art, would have been much worse in that regard.

There just were not a lot of choices other than a hierarchical
database system.  The designers could have made some different
choices within the general hierarchical model, some of which I
hinted about in my earlier note.  I don't know if those
alternatives were even considered (and suspect most of them were
not).   But the decision to use a hierarchical model, again
given the state of the art, had to be pretty much determined by
those  design criteria.

I think a choice between something that meets the criteria and
is comparatively simple, robust, understandable, and
implementable and something that is much more complex and/or
that lacks robustness against network interruptions is an
engineering choice (and an obvious one).  One could argue that
it is political, but that requires arguing either that every
decision the involves either implementation or operational
economics or other operational issues is political.  

One could also argue that the criteria were wrong and that "no
central administrative or coordination function" should have
been a requirement.  But that requirement would be a very
difficult one technically even today and the environment at the
time -- IANA existed well before the DNS and was generally
trusted and the DNS design was a lot less centralized than its
predecessor-- just didn't call for it.  So, except with extremes
of hindsight about what we might like to have had today given an
evolution path that certainly could not have been accurately
anticipated at the time, I think it is hard to argue that the
omission of a "no central..." criterion was political at the
time.

Of course, one can say today that the technical/ engineering
decisions made then have political implications today but, given
the right set of conditions, that could be true of almost any
decision or fact, as the history of ignorant legislative efforts
to change PI or modify the speed of light amply illustrate.   It
doesn't retroactively make the decisions themselves political as
others have implied.

Finally, with regard to CLASSes just being treated as a another
level of the hiararchy, a sort of super-root... Again, I wasn't
there, no only not there for the DNS design effort but not
involved in the Chaosnet and Hesiod implementations that have
been the major examples of actually deployed and actively used
examples of CLASSes.  But it is clear to me from both reading
the specs and what little I know of those implementations that
kre is correct and the capability is badly underspecified.  I
think there are even some errors in what the spec does appear to
say.  But getting from there to either "there is a political
problem because CLASSes don't work" in the presence of
counterexamples to "don't work" or  "CLASSes just create another
level of the tree with the same properties in all CLASSes that
the CLASS=IN [sub]tree has" seems to me to be a huge stretch
that is not really justified by either implementation history or
the spec.

Just my opinion, of course.

best,
    john


From stbryant@cisco.com  Thu Jan  9 04:08:58 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7861AE092; Thu,  9 Jan 2014 04:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1MiTxQP-0ggZ; Thu,  9 Jan 2014 04:08:56 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 855E01ADF52; Thu,  9 Jan 2014 04:08:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=478; q=dns/txt; s=iport; t=1389269326; x=1390478926; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=6TFNL/i3NO0Be9C+OxWBBxbGoqGq75F7IjQQAg9OjH4=; b=Mp8Vka/qzKqcutS+2Pd23V2bUukZ6qLqQR7wJ4qn8m3NglHWIXTtf2va sGOZLT2MpmzfOEG4AwKtdQsiAakKlXRBFSY2z9Ka5+BnQvXAxV2kERbdr UKnHxD2dbmJ6J2LGaMW9NwSrQLWm4qBqK3KPS/STuJflI8UOZNpff82/5 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFAPCQzlKQ/khM/2dsb2JhbABZgwu3S4MIgREWdIIlAQEBBDhAARALGAkWDwkDAgECAUUHDAEHAQGIAMR4F48FB4Q3AQOYF5IVgy0
X-IronPort-AV: E=Sophos;i="4.95,630,1384300800";  d="scan'208";a="3383896"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 09 Jan 2014 12:08:45 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s09C8iYO006013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 12:08:45 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s09C8h6p005115; Thu, 9 Jan 2014 12:08:43 GMT
Message-ID: <52CE914B.7070506@cisco.com>
Date: Thu, 09 Jan 2014 12:08:43 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: mark.tinka@seacom.mu, mpls@ietf.org
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk> <52CE80FC.9060306@cisco.com> <201401091303.53239.mark.tinka@seacom.mu>
In-Reply-To: <201401091303.53239.mark.tinka@seacom.mu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 12:08:58 -0000

On 09/01/2014 11:03, Mark Tinka wrote:
> On Thursday, January 09, 2014 12:59:08 PM Stewart Bryant
> wrote:
>
>> I would be interested in what operators are observing in
>> their network, because I have never heard a concern
>> expressed that this was happening.
> You mean for native MPLS, or for encapsulated MPLS?
>
> Mark.
Hi Mark,

Either or both.

I am interested in how often in practice MPLS packets get
misdelivered due to label corruption.

- Stewart

From hallam@gmail.com  Thu Jan  9 05:27:43 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065C41AE2CB for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 05:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XZ8tQC3x_I4m for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 05:27:40 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 92E2A1AE2E2 for <ietf@ietf.org>; Thu,  9 Jan 2014 05:27:37 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id w7so2273229lbi.24 for <ietf@ietf.org>; Thu, 09 Jan 2014 05:27:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jjymjOmqk9qZzwULaM/J0P4Wiln5/5fkYCuz83h6+AA=; b=l2/BSRDbEpF+WKe65uFW+B87Bom7cFH9xj/TUEkBJFiSwS20xVWlnXiMMInjucijiO WZtRbcnGBJpHl2uNOLPY938hAeiSwTyOtrW5kUXMTlYmROsJYBF9v0lzJjqe/c032T8J Q5TG+sII1FuZO0rBA32cOBzB+bi6zvl2cAF/etb+FQioqonS50I/HcQMuZ1cB+WHzlc7 lQ+vtrKCYXAuy4ncj7MzqnE39sOyPXWAUo9N/cp/mzqplD4z9hTyfh2wszFZHgygsp9W 33dTbkUteWfG2/lTksmrGVNC2b27X/a/FdO+g23M1weJbUa+mxSwFiNriwyj70EAqeiC 2PwQ==
MIME-Version: 1.0
X-Received: by 10.112.138.70 with SMTP id qo6mr1211942lbb.34.1389274047322; Thu, 09 Jan 2014 05:27:27 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Thu, 9 Jan 2014 05:27:27 -0800 (PST)
In-Reply-To: <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@cisco.com> <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com>
Date: Thu, 9 Jan 2014 08:27:27 -0500
Message-ID: <CAMm+Lwis6bBgm83pfU+yK+NQYn4G5bQUYTXQLAM8VKgHZdp6gA@mail.gmail.com>
Subject: Re: DNS design (was: Re: Split the IANA functions?)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e0112c02c161ef504ef8992a3
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 13:27:43 -0000

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

On Thu, Jan 9, 2014 at 6:50 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Tuesday, January 07, 2014 15:58 +0100 Eliot Lear
> <lear@cisco.com> wrote:
>
> > Andrew,
> >
> > It's clear that I wasn't clear.  Deciding on a tree structure
> > has political implications, be that DNS, RPKI, or other (and
> > there are other).  To ignore those implications would be
> > unwise.  They are weighed against technical considerations, as
> > always.
> >...
>
> Eliot,
>
> In the hope of focusing the discussion a bit, I think it would
> be more accurate to say that "having a tree structure...r
> "having decided on a tree structure...".
>
> It feels a little strange for me to be defending the DNS design
> because I've never been a huge fan of some aspects of it, but a
> little bit of insight into the context of those decisions may be
> helpful.
>
> I was not involved in the DNS design process, but I was doing
> work on databases, including distributed databases, at the time
> in the early to mid-1980s.  Against the backdrop of the database
> state of the art at the time, if one started with design
> criteria of approximately:
>
> -- replacing the name-to-address and
>         name-to-limited-supplementary-information functions of
>         the Host Table without significant loss of functionality
> -- having a hierarchical name structure (which does not,
>         itself, imply a hierarchical database)
> -- having something that could be administratively
>         distributed at multiple levels of the name structure
> -- having a distributed database that could be plausibly
>         implemented without lock-commit-acknowledge or
>         journal-based update facilities
> -- having an arrangement that would facilitate local
>         caching, not just for performance but as a mechanism to
>         allow systems that were temporarily disconnected from
>         all or part of the network to keep functioning reasonably
> -- The result needed to be plausible for non-specialists
>         to implement in a way that would interoperable.
>
> Most of the above are documented in the various pre-DNS papers.
> Most are also pretty obvious.  Given how bad some
> implementations have been, there is a pretty good case to be
> made that the design failed on the last criterion, but a
> non-hierarchical alternative, especially given the then state of
> the art, would have been much worse in that regard.
>
> There just were not a lot of choices other than a hierarchical
> database system.  The designers could have made some different
> choices within the general hierarchical model, some of which I
> hinted about in my earlier note.  I don't know if those
> alternatives were even considered (and suspect most of them were
> not).   But the decision to use a hierarchical model, again
> given the state of the art, had to be pretty much determined by
> those  design criteria.
>
> I think a choice between something that meets the criteria and
> is comparatively simple, robust, understandable, and
> implementable and something that is much more complex and/or
> that lacks robustness against network interruptions is an
> engineering choice (and an obvious one).  One could argue that
> it is political, but that requires arguing either that every
> decision the involves either implementation or operational
> economics or other operational issues is political.
>
> One could also argue that the criteria were wrong and that "no
> central administrative or coordination function" should have
> been a requirement.  But that requirement would be a very
> difficult one technically even today and the environment at the
> time -- IANA existed well before the DNS and was generally
> trusted and the DNS design was a lot less centralized than its
> predecessor-- just didn't call for it.  So, except with extremes
> of hindsight about what we might like to have had today given an
> evolution path that certainly could not have been accurately
> anticipated at the time, I think it is hard to argue that the
> omission of a "no central..." criterion was political at the
> time.
>
> Of course, one can say today that the technical/ engineering
> decisions made then have political implications today but, given
> the right set of conditions, that could be true of almost any
> decision or fact, as the history of ignorant legislative efforts
> to change PI or modify the speed of light amply illustrate.   It
> doesn't retroactively make the decisions themselves political as
> others have implied.
>
> Finally, with regard to CLASSes just being treated as a another
> level of the hiararchy, a sort of super-root... Again, I wasn't
> there, no only not there for the DNS design effort but not
> involved in the Chaosnet and Hesiod implementations that have
> been the major examples of actually deployed and actively used
> examples of CLASSes.  But it is clear to me from both reading
> the specs and what little I know of those implementations that
> kre is correct and the capability is badly underspecified.  I
> think there are even some errors in what the spec does appear to
> say.  But getting from there to either "there is a political
> problem because CLASSes don't work" in the presence of
> counterexamples to "don't work" or  "CLASSes just create another
> level of the tree with the same properties in all CLASSes that
> the CLASS=IN [sub]tree has" seems to me to be a huge stretch
> that is not really justified by either implementation history or
> the spec.
>

+1

Some of the constraints on the DNS system are set by existing technology.

But some of the constraints are not and it greatly damages ICANN when I see
the head of ICANN making misleading technical arguments to claim that a
particular outcome is impossible as I saw on Tuesday this week.

When pressed he withdrew his original claim and announced that he has hired
the original architect of DNS to perform a thorough re-evaluation of the
architecture and design asking if things could be done differently.
Presumably because the original architects of Internet services are well
known for their enthusiasm for re-imagining and re-engineering their
deployed legacy designs.


Another variation of the bogus technical argument is 'we can't do X because
it would allow Russia to do Y and increase control.'

It may not be turned on all the time but we know that when it suits them,
Russia simply diverts traffic in Russia for ALL DNS root services to
servers of their own. They used that capability to effect during the
Georgia crisis.


When I was up at Oxford, Lord Marshall came to tell lies about the nuclear
power program. Papers released since during the attempt to privatize
nuclear power show that Marshall knew or should have known that the
technical arguments he was making were untrue.

Due to climate change we might actually need to build new nuclear capacity
but the incontrovertible fact that the UK establishment lied early and lied
often about the safety and economics of the program has created means that
the necessary level of trust is simply not there.


Technical arguments that can only be understood by experts are actually
weak ones.


Oh and one more thing. For years people have tried to ridicule my concern
that US control of ICANN might result in the Cuba or Palestine CC TLD codes
being dropped out of the root zone.

Anyone who has been following US politics this week will know that emails
from the private office of a Governor previously one of the frontrunners
for the 2016 presidential nomination prove beyond doubt that the Governor's
minions shut down part of the busiest bridge in the world for a petty act
of political revenge. While we can't do very much about the risk that a
person of that type would gain control of the NSA we can and should make
sure that the Internet institutions are protected against that type of
politician.

-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jan 9, 2014 at 6:50 AM, John C Klensin <span dir=3D"ltr">&l=
t;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.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 Tuesday, January 07, 2014 15:58 +0100 Eliot Lear<br>
&lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:<br>
<br>
&gt; Andrew,<br>
&gt;<br>
&gt; It&#39;s clear that I wasn&#39;t clear. =A0Deciding on a tree structur=
e<br>
&gt; has political implications, be that DNS, RPKI, or other (and<br>
&gt; there are other). =A0To ignore those implications would be<br>
&gt; unwise. =A0They are weighed against technical considerations, as<br>
&gt; always.<br>
&gt;...<br>
<br>
Eliot,<br>
<br>
In the hope of focusing the discussion a bit, I think it would<br>
be more accurate to say that &quot;having a tree structure...r<br>
&quot;having decided on a tree structure...&quot;.<br>
<br>
It feels a little strange for me to be defending the DNS design<br>
because I&#39;ve never been a huge fan of some aspects of it, but a<br>
little bit of insight into the context of those decisions may be<br>
helpful.<br>
<br>
I was not involved in the DNS design process, but I was doing<br>
work on databases, including distributed databases, at the time<br>
in the early to mid-1980s. =A0Against the backdrop of the database<br>
state of the art at the time, if one started with design<br>
criteria of approximately:<br>
<br>
-- replacing the name-to-address and<br>
=A0 =A0 =A0 =A0 name-to-limited-supplementary-information functions of<br>
=A0 =A0 =A0 =A0 the Host Table without significant loss of functionality<br=
>
-- having a hierarchical name structure (which does not,<br>
=A0 =A0 =A0 =A0 itself, imply a hierarchical database)<br>
-- having something that could be administratively<br>
=A0 =A0 =A0 =A0 distributed at multiple levels of the name structure<br>
-- having a distributed database that could be plausibly<br>
=A0 =A0 =A0 =A0 implemented without lock-commit-acknowledge or<br>
=A0 =A0 =A0 =A0 journal-based update facilities<br>
-- having an arrangement that would facilitate local<br>
=A0 =A0 =A0 =A0 caching, not just for performance but as a mechanism to<br>
=A0 =A0 =A0 =A0 allow systems that were temporarily disconnected from<br>
=A0 =A0 =A0 =A0 all or part of the network to keep functioning reasonably<b=
r>
-- The result needed to be plausible for non-specialists<br>
=A0 =A0 =A0 =A0 to implement in a way that would interoperable.<br>
<br>
Most of the above are documented in the various pre-DNS papers.<br>
Most are also pretty obvious. =A0Given how bad some<br>
implementations have been, there is a pretty good case to be<br>
made that the design failed on the last criterion, but a<br>
non-hierarchical alternative, especially given the then state of<br>
the art, would have been much worse in that regard.<br>
<br>
There just were not a lot of choices other than a hierarchical<br>
database system. =A0The designers could have made some different<br>
choices within the general hierarchical model, some of which I<br>
hinted about in my earlier note. =A0I don&#39;t know if those<br>
alternatives were even considered (and suspect most of them were<br>
not). =A0 But the decision to use a hierarchical model, again<br>
given the state of the art, had to be pretty much determined by<br>
those =A0design criteria.<br>
<br>
I think a choice between something that meets the criteria and<br>
is comparatively simple, robust, understandable, and<br>
implementable and something that is much more complex and/or<br>
that lacks robustness against network interruptions is an<br>
engineering choice (and an obvious one). =A0One could argue that<br>
it is political, but that requires arguing either that every<br>
decision the involves either implementation or operational<br>
economics or other operational issues is political.<br>
<br>
One could also argue that the criteria were wrong and that &quot;no<br>
central administrative or coordination function&quot; should have<br>
been a requirement. =A0But that requirement would be a very<br>
difficult one technically even today and the environment at the<br>
time -- IANA existed well before the DNS and was generally<br>
trusted and the DNS design was a lot less centralized than its<br>
predecessor-- just didn&#39;t call for it. =A0So, except with extremes<br>
of hindsight about what we might like to have had today given an<br>
evolution path that certainly could not have been accurately<br>
anticipated at the time, I think it is hard to argue that the<br>
omission of a &quot;no central...&quot; criterion was political at the<br>
time.<br>
<br>
Of course, one can say today that the technical/ engineering<br>
decisions made then have political implications today but, given<br>
the right set of conditions, that could be true of almost any<br>
decision or fact, as the history of ignorant legislative efforts<br>
to change PI or modify the speed of light amply illustrate. =A0 It<br>
doesn&#39;t retroactively make the decisions themselves political as<br>
others have implied.<br>
<br>
Finally, with regard to CLASSes just being treated as a another<br>
level of the hiararchy, a sort of super-root... Again, I wasn&#39;t<br>
there, no only not there for the DNS design effort but not<br>
involved in the Chaosnet and Hesiod implementations that have<br>
been the major examples of actually deployed and actively used<br>
examples of CLASSes. =A0But it is clear to me from both reading<br>
the specs and what little I know of those implementations that<br>
kre is correct and the capability is badly underspecified. =A0I<br>
think there are even some errors in what the spec does appear to<br>
say. =A0But getting from there to either &quot;there is a political<br>
problem because CLASSes don&#39;t work&quot; in the presence of<br>
counterexamples to &quot;don&#39;t work&quot; or =A0&quot;CLASSes just crea=
te another<br>
level of the tree with the same properties in all CLASSes that<br>
the CLASS=3DIN [sub]tree has&quot; seems to me to be a huge stretch<br>
that is not really justified by either implementation history or<br>
the spec.<br></blockquote><div><br></div><div>+1=A0</div><div><br></div><di=
v>Some of the constraints on the DNS system are set by existing technology.=
=A0</div><div><br></div><div>But some of the constraints are not and it gre=
atly damages ICANN when I see the head of ICANN making misleading technical=
 arguments to claim that a particular outcome is impossible as I saw on Tue=
sday this week.</div>
<div><br></div><div>When pressed he withdrew his original claim and announc=
ed that he has hired the original architect of DNS to perform a thorough re=
-evaluation of the architecture and design asking if things could be done d=
ifferently. Presumably because the original architects of Internet services=
 are well known for their enthusiasm for re-imagining and re-engineering th=
eir deployed legacy designs.</div>
<div><br></div><div><br></div><div>Another variation of the bogus technical=
 argument is &#39;we can&#39;t do X because it would allow Russia to do Y a=
nd increase control.&#39;</div><div><br></div><div>It may not be turned on =
all the time but we know that when it suits them, Russia simply diverts tra=
ffic in Russia for ALL DNS root services to servers of their own. They used=
 that capability to effect during the Georgia crisis.=A0</div>
<div><br></div><div><br></div><div>When I was up at Oxford, Lord Marshall c=
ame to tell lies about the nuclear power program. Papers released since dur=
ing the attempt to privatize nuclear power show that Marshall knew or shoul=
d have known that the technical arguments he was making were untrue.</div>
<div><br></div><div>Due to climate change we might actually need to build n=
ew nuclear capacity but the incontrovertible fact that the UK establishment=
 lied early and lied often about the safety and economics of the program ha=
s created means that the necessary level of trust is simply not there.</div=
>
<div><br></div></div><div><br></div><div>Technical arguments that can only =
be understood by experts are actually weak ones.</div><div><br></div><div><=
br></div><div>Oh and one more thing. For years people have tried to ridicul=
e my concern that US control of ICANN might result in the Cuba or Palestine=
 CC TLD codes being dropped out of the root zone.</div>
<div><br></div><div>Anyone who has been following US politics this week wil=
l know that emails from the private office of a Governor previously one of =
the frontrunners for the 2016 presidential nomination prove beyond doubt th=
at the Governor&#39;s minions shut down part of the busiest bridge in the w=
orld for a petty act of political revenge. While we can&#39;t do very much =
about the risk that a person of that type would gain control of the NSA we =
can and should make sure that the Internet institutions are protected again=
st that type of politician.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--089e0112c02c161ef504ef8992a3--

From stephen.farrell@cs.tcd.ie  Thu Jan  9 05:55:44 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60F211AE2F8 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 05:55:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.438
X-Spam-Level: 
X-Spam-Status: No, score=-4.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6GYfc2v02zfv for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 05:55:42 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id ACB051AE24D for <ietf@ietf.org>; Thu,  9 Jan 2014 05:55:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E392EBE47 for <ietf@ietf.org>; Thu,  9 Jan 2014 13:55:31 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jAQp8bBMDJVW for <ietf@ietf.org>; Thu,  9 Jan 2014 13:55:31 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id C3DD6BE38 for <ietf@ietf.org>; Thu,  9 Jan 2014 13:55:31 +0000 (GMT)
Message-ID: <52CEAA53.1090102@cs.tcd.ie>
Date: Thu, 09 Jan 2014 13:55:31 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Fwd: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org>
In-Reply-To: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org>
X-Enigmail-Version: 1.6
X-Forwarded-Message-Id: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 13:55:44 -0000

Folks, submissions are starting to roll in so this is
a reminder to send yours by Jan 15. We'll be posting
more logistics next week(-ish) as well in case you're
wondering.

Thanks,
S.


-------- Original Message --------
Subject: W3C/IAB workshop on Strengthening the Internet Against
Pervasive Monitoring (STRINT)
Date: Sun, 1 Dec 2013 10:48:15 -0500
From: IAB Chair <iab-chair@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
CC: IAB <iab@iab.org>, IETF <ietf@ietf.org>


W3C/IAB workshop on Strengthening the Internet
Against Pervasive Monitoring (STRINT)
======================================

Logistics/Dates:

Submissions due: Jan 15 2014
Invitations issued: Jan 31 2014
Workshop Date: Feb 28 (pm) & Mar 1 (am) 2014
	To be Confirmed - could be all day Mar 1
Location: Central London, UK. IETF Hotel or nearby (TBC)
For queries, contact: stephen.farrell@cs.tcd.ie, tech@strews.eu
Send submissions to: group-strint-submission@w3.org
Workshop web site: http://www.w3.org/2014/strint/

The Vancouver IETF plenary concluded that pervasive monitoring
represents an attack on the Internet, and the IETF has begun to
carry out various of the more obvious actions [1] required to
try to handle this attack. However, there are additional much
more complex questions arising that need further consideration
before any additional concrete plans can be made.

The W3C and IAB will therefore host a one-day workshop on the
topic of "Strengthening the Internet Against Pervasive
Monitoring" before IETF-89 in London in March 2014, with support
from the EU FP7 STREWS [2] project.

Pervasive monitoring targets protocol data that we also need for
network manageability and security. This data is captured and
correlated with other data. There is an open problem as to how
to enhance protocols so as to maintain network manageability and
security but still limit data capture and correlation.

The overall goal of the workshop is to steer IETF and W3C work
so as to be able to improve or "strengthen" the Internet in the
face of pervasive monitoring.  A workshop report in the form of
an IAB RFC will be produced after the event.

Technical questions for the workshop include:

- What are the pervasive monitoring threat models, and what is
  their effect on web and Internet protocol security and privacy?
- What is needed so that web developers can better consider the
  pervasive monitoring context?
- How are WebRTC and IoT impacted, and how can they be better
  protected? Are other key Internet and web technologies
  potentially impacted?
- What gaps exist in current tool sets and operational best
  practices that could address some of these potential impacts?
- What trade-offs exist between strengthening measures, (e.g.
  more encryption) and performance, operational or network
  management issues?
- How do we guard against pervasive monitoring while maintaining
  network manageability?
- Can lower layer changes (e.g., to IPv6, LISP, MPLS) or
  additions to overlay networks help?
- How realistic is it to not be fingerprintable on the web and
  Internet?
- How can W3C, the IETF and the IRTF better deal with new
  cryptographic algorithm proposals in future?
- What are the practical benefits and limits of "opportunistic
  encryption"?
- Can we deploy end-to-end crypto for email, SIP, the web, all
  TCP applications or other applications so that we mitigate
  pervasive monitoring usefully?
- How might pervasive monitoring take form or be addressed in
  embedded systems or different industrial verticals?
- How do we reconcile caching, proxies and other intermediaries
  with end-to-end encryption?
- Can we obfuscate metadata with less overhead than TOR?
- Considering meta-data: are there relevant differences between
  protocol artefacts, message sizes and patterns and payloads?

Position papers (maximum of 5 pages using 10pt font or any
length Internet-Drafts) from academia, industry and others that
focus on the broader picture and that warrant the kind of
extended discussion that a full day workshop offers are the most
welcome. Papers that reflect experience based on running code
and deployed services are also very welcome. Papers that are
proposals for point-solutions are less useful in this context,
and can simply be submitted as Internet-Drafts and discussed on
relevant IETF or W3C lists, e.g. the IETF perpass list. [3]

The workshop will be by invitation only. Those wishing to attend
should submit a position paper or Internet-Draft.  All inputs
submitted and considered relevant will be published on the
workshop web page. The organisers (STREWS project participants,
IAB and W3C staff) will decide whom to invite based on the
submissions received.  Sessions will be organized according to
content, and not every accepted submission or invited attendee
will have an opportunity to present as the intent is to foster
discussion and not simply to have a sequence of presentations.

[1] http://down.dsg.cs.tcd.ie/misc/perpass.txt
[2] http://www.strews.eu/
[3] https://www.ietf.org/mailman/listinfo/perpass







From lear@cisco.com  Thu Jan  9 06:47:41 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C481AE36F for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 06:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.439
X-Spam-Level: 
X-Spam-Status: No, score=-9.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_52=0.6, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NNJJX8Bg3A8J for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 06:47:40 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6642F1AE338 for <ietf@ietf.org>; Thu,  9 Jan 2014 06:47:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5804; q=dns/txt; s=iport; t=1389278850; x=1390488450; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=2fvuq22OicTEA+lm/BMHjTdGGPjY9NHxppuiVyH71Xc=; b=ZCSCK20DA7npO7GXAz5ao9smF05qNrwC0SC/VDnx69dhdm6lC6ZnvzjB U+DsQ54jduUCHMSNKZiGaDgzDU66b6gvI9QQWXroJq3VG799nhwfpZoGg HfPTeP2CFDZ0qPPpVzZZwCOF0wAq1A3jgeafsDe5+v2SC8GM6qgJNYm2f A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlEFAEa1zlKQ/khL/2dsb2JhbABZgwuEDLZDgQ8WdIIlAQEBBB0GVRELGAICBRYLAgIJAwIBAgErGgYBDAYCAQGIAKl/mlsXgSmNBF+Cb4FIAQOYF5IVgy47gSwk
X-IronPort-AV: E=Sophos;i="4.95,631,1384300800";  d="scan'208";a="3391927"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 09 Jan 2014 14:47:29 +0000
Received: from mctiny.local ([10.61.171.89]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s09ElSwb024660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 14:47:28 GMT
Message-ID: <52CEB680.4010706@cisco.com>
Date: Thu, 09 Jan 2014 15:47:28 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: DNS design
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@cisco.com> <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com>
In-Reply-To: <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 14:47:42 -0000

John,

Just to be clear, I was using DNS as an example.  We can always question
design decisions we've made.  I believe that Andrew and others may be
interested in doing just that, but not from the top down (as it were).

Eliot

On 1/9/14 12:50 PM, John C Klensin wrote:
>
> --On Tuesday, January 07, 2014 15:58 +0100 Eliot Lear
> <lear@cisco.com> wrote:
>
>> Andrew,
>>
>> It's clear that I wasn't clear.  Deciding on a tree structure
>> has political implications, be that DNS, RPKI, or other (and
>> there are other).  To ignore those implications would be
>> unwise.  They are weighed against technical considerations, as
>> always.
>> ...
> Eliot,
>
> In the hope of focusing the discussion a bit, I think it would
> be more accurate to say that "having a tree structure...r
> "having decided on a tree structure...".
>
> It feels a little strange for me to be defending the DNS design
> because I've never been a huge fan of some aspects of it, but a
> little bit of insight into the context of those decisions may be
> helpful.
>
> I was not involved in the DNS design process, but I was doing
> work on databases, including distributed databases, at the time
> in the early to mid-1980s.  Against the backdrop of the database
> state of the art at the time, if one started with design
> criteria of approximately:
>
> -- replacing the name-to-address and
> 	name-to-limited-supplementary-information functions of
> 	the Host Table without significant loss of functionality
> -- having a hierarchical name structure (which does not,
> 	itself, imply a hierarchical database)
> -- having something that could be administratively
> 	distributed at multiple levels of the name structure
> -- having a distributed database that could be plausibly
> 	implemented without lock-commit-acknowledge or
> 	journal-based update facilities
> -- having an arrangement that would facilitate local
> 	caching, not just for performance but as a mechanism to
> 	allow systems that were temporarily disconnected from
> 	all or part of the network to keep functioning reasonably
> -- The result needed to be plausible for non-specialists
> 	to implement in a way that would interoperable.
> 	
> Most of the above are documented in the various pre-DNS papers.
> Most are also pretty obvious.  Given how bad some
> implementations have been, there is a pretty good case to be
> made that the design failed on the last criterion, but a
> non-hierarchical alternative, especially given the then state of
> the art, would have been much worse in that regard.
>
> There just were not a lot of choices other than a hierarchical
> database system.  The designers could have made some different
> choices within the general hierarchical model, some of which I
> hinted about in my earlier note.  I don't know if those
> alternatives were even considered (and suspect most of them were
> not).   But the decision to use a hierarchical model, again
> given the state of the art, had to be pretty much determined by
> those  design criteria.
>
> I think a choice between something that meets the criteria and
> is comparatively simple, robust, understandable, and
> implementable and something that is much more complex and/or
> that lacks robustness against network interruptions is an
> engineering choice (and an obvious one).  One could argue that
> it is political, but that requires arguing either that every
> decision the involves either implementation or operational
> economics or other operational issues is political.  
>
> One could also argue that the criteria were wrong and that "no
> central administrative or coordination function" should have
> been a requirement.  But that requirement would be a very
> difficult one technically even today and the environment at the
> time -- IANA existed well before the DNS and was generally
> trusted and the DNS design was a lot less centralized than its
> predecessor-- just didn't call for it.  So, except with extremes
> of hindsight about what we might like to have had today given an
> evolution path that certainly could not have been accurately
> anticipated at the time, I think it is hard to argue that the
> omission of a "no central..." criterion was political at the
> time.
>
> Of course, one can say today that the technical/ engineering
> decisions made then have political implications today but, given
> the right set of conditions, that could be true of almost any
> decision or fact, as the history of ignorant legislative efforts
> to change PI or modify the speed of light amply illustrate.   It
> doesn't retroactively make the decisions themselves political as
> others have implied.
>
> Finally, with regard to CLASSes just being treated as a another
> level of the hiararchy, a sort of super-root... Again, I wasn't
> there, no only not there for the DNS design effort but not
> involved in the Chaosnet and Hesiod implementations that have
> been the major examples of actually deployed and actively used
> examples of CLASSes.  But it is clear to me from both reading
> the specs and what little I know of those implementations that
> kre is correct and the capability is badly underspecified.  I
> think there are even some errors in what the spec does appear to
> say.  But getting from there to either "there is a political
> problem because CLASSes don't work" in the presence of
> counterexamples to "don't work" or  "CLASSes just create another
> level of the tree with the same properties in all CLASSes that
> the CLASS=IN [sub]tree has" seems to me to be a huge stretch
> that is not really justified by either implementation history or
> the spec.
>
> Just my opinion, of course.
>
> best,
>     john
>
>
>


From andrew.hutton@unify.com  Thu Jan  9 06:49:48 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCA21AE39C; Thu,  9 Jan 2014 06:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQPmvEQ9MD0S; Thu,  9 Jan 2014 06:49:43 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 835A71AE364; Thu,  9 Jan 2014 06:49:43 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id A47971EB85C2; Thu,  9 Jan 2014 15:49:33 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.126]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0123.003; Thu, 9 Jan 2014 15:49:30 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Russ Housley <housley@vigilsec.com>, "draft-ietf-siprec-architecture.all@tools.ietf.org" <draft-ietf-siprec-architecture.all@tools.ietf.org>
Subject: RE: Gen-ART review of draft-ietf-siprec-architecture-11
Thread-Topic: Gen-ART review of draft-ietf-siprec-architecture-11
Thread-Index: AQHPCKVRfiG9pNCJ2kOTJueeYg99Wpp8glyg
Date: Thu, 9 Jan 2014 14:49:30 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17C9D8A2@MCHP04MSX.global-ad.net>
References: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
In-Reply-To: <200D1BD7-800E-4F28-A4FD-C509B0F2EEC6@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 14:49:48 -0000

Hi Russ,

Personally I can see that your suggested change to the text would result in=
 more clarity.

I would be happy to make this change.

Regards
Andy




> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: 03 January 2014 17:00
> To: draft-ietf-siprec-architecture.all@tools.ietf.org
> Cc: gen-art@ietf.org; ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-siprec-architecture-11
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-siprec-architecture-11
> Reviewer: Russ Housley
> Review Date: 2014-01-03
> IETF LC End Date: 2013-10-01
> IESG Telechat date: 2014-01-09
>=20
> Summary:
>=20
> Thank you for addressing the issues raised in my previous review.
> This document is ready for publication as an Informational RFC.
>=20
> Major Concerns:  None.
>=20
> Minor Concerns:  None.
>=20
> Editorial Comments:
>=20
> The changes to Section 3.2.4 to resolve my earlier comment have
> introduced a clarity problem.  I suggest a minor rewording to fix it.
>=20
> 3.2.4.  Media Stream Mixing
>=20
>    In a basic session involving only audio there are typically two
>    audio/RTP streams between the two UAs involved transporting media in
>    each direction.  When recording this media, the two streams may be
>    mixed or not mixed at the SRC before being transmitted to the SRS.
>    In the case when they are not mixed, two separate streams are sent
>    to the SRS.  In the mixed case, a single mixed media stream is sent
>    to the SRS.  However, in the case when the media streams are not
>    mixed, the SDP offer sent to the SRS must describe two separate
>    media streams.


From prvs=0079a20b32=johnl@taugh.com  Thu Jan  9 07:09:30 2014
Return-Path: <prvs=0079a20b32=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FC3E1AE3C8 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 07:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGVyWpx3KJ1a for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 07:09:28 -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 9C5501AE191 for <ietf@ietf.org>; Thu,  9 Jan 2014 07:09:28 -0800 (PST)
Received: (qmail 43427 invoked from network); 9 Jan 2014 15:09:18 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 9 Jan 2014 15:09:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=b64f.52cebb9e.k1312; i=johnl%iecc.com@submit.iecc.com; bh=psMiT2ZsTpVq2AYpn1SyNKTHCKOHKOnbXdUHnPWeH3U=; b=Q7hOVl+NlYcN+xDAgIfsPS/CrZ1sbTIojkUgLUVoBD38vWdkAy3V5m1KuaqLmJiK2BSmOrPHGiXnAQDA1PLNStouVoxaOAMtKZLgSZxDxhR+7roCdndfR/s1xzhsnYFS2zEYuFLEX2jaQrp0IogVSvRV/kb1p00kpjQyLXso2iaELoG/HprmuSFy+ShXwceYtYVHth1KfmzMK9sN7JuaU0pDXKEE7QbDRGRqwjbTRXS7bU6LiJB+fa6NPHqNAY4o
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=b64f.52cebb9e.k1312; olt=johnl%iecc.com@submit.iecc.com; bh=psMiT2ZsTpVq2AYpn1SyNKTHCKOHKOnbXdUHnPWeH3U=; b=JeBfshnn7Il8FsgwVN54ZX/9wiPX5qlhdYsZAujLpiZ9v6k7pnnp11bauFtFcA+PLJqSbag03Ss+c7uTSXLPmOCGonKbzWWDAZKemH9O4BT7Gl245QrMx9J+MsDrQyj8qDtsYaKz0O2kZOTAOZFcUH+5fvPI/PmDrdoT08A6H2XeU2+15OrdL+vIwKcMgelYl8gKqNb7Uod3ABONjqg3oEPAre8Ete6XXUaNXCs2XPq0LlVliqqtEXIgD8Z3MUZP
Received: from joyce.dhcp.intranet ([155.70.23.45]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 09 Jan 2014 15:09:18 -0000
Date: 9 Jan 2014 10:09:15 -0500
Message-ID: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "IETF general list" <ietf@ietf.org>
Subject: Multi-homed BCP38
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 15:09:30 -0000

I was at a meeting talking to ops people from some large ISPs, who tell me 
that when they tell their large customers about BCP 38, the customers say 
forget it, because they're multihomed.  I gather the situation is 
typically that the customer has multiple address ranges, say from 
providers A and B.  Normally traffic from range A goes out through 
provider A, and vice-versa, except sometimes when it doesn't.  Sometimes 
it's failover, or it may be deliberate asymmetic routing.  The customers 
may not be running BGP, or if they do, they don't want to announce range A 
to provider B for business reasons I don't entirely understand but that 
are not going away.

The ISPs tell me that the customers are often ISPs themselves, so there 
are lots of address ranges, far more than anyone could track manually even 
if they wanted to.

I see BCP 84, which is now ten years old.  The ISPs are aware of it, but 
it doesn't seem to have done the trick.  I can think of some hacks to 
pseudo-announce ranges for filtering purposes, but surely I am not the 
only person to have noticed this problem.  What have people done to 
address this issue?*  I figure the first thing to do is to understand 
what's failed before.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

* - other than calling the customers stupid, which they are not, and is 
not helpful


From paf@frobbit.se  Thu Jan  9 07:44:02 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 509951AE357 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 07:44:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6qEkn2JusS8e for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 07:44:01 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 069281AE32B for <ietf@ietf.org>; Thu,  9 Jan 2014 07:44:01 -0800 (PST)
Received: from [172.18.243.118] (w193-11-200-249.eduroam.sunet.se [193.11.200.249]) by mail.frobbit.se (Postfix) with ESMTPSA id 9DDFE1FE4C; Thu,  9 Jan 2014 16:43:50 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_8F777165-26DE-4ADC-8BDC-F07EA5BD1E53"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Multi-homed BCP38
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
Date: Thu, 9 Jan 2014 16:43:49 +0100
Message-Id: <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 15:44:02 -0000

--Apple-Mail=_8F777165-26DE-4ADC-8BDC-F07EA5BD1E53
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Not being an IP-routing person, but chair of SSAC in ICANN, I hear =
people for the reasons you bring up are more in favor of a mechanism =
where one talk about explicitly "filtering at the edge of the Internet" =
and not at every point where routes are exchanged.

Because of this, please also include SAC004 in your investigation.

<https://www.icann.org/en/groups/ssac/documents/sac-004-en.htm>

   Patrik

On 9 jan 2014, at 16:09, John R Levine <johnl@taugh.com> wrote:

> I was at a meeting talking to ops people from some large ISPs, who =
tell me that when they tell their large customers about BCP 38, the =
customers say forget it, because they're multihomed.  I gather the =
situation is typically that the customer has multiple address ranges, =
say from providers A and B.  Normally traffic from range A goes out =
through provider A, and vice-versa, except sometimes when it doesn't.  =
Sometimes it's failover, or it may be deliberate asymmetic routing.  The =
customers may not be running BGP, or if they do, they don't want to =
announce range A to provider B for business reasons I don't entirely =
understand but that are not going away.
>=20
> The ISPs tell me that the customers are often ISPs themselves, so =
there are lots of address ranges, far more than anyone could track =
manually even if they wanted to.
>=20
> I see BCP 84, which is now ten years old.  The ISPs are aware of it, =
but it doesn't seem to have done the trick.  I can think of some hacks =
to pseudo-announce ranges for filtering purposes, but surely I am not =
the only person to have noticed this problem.  What have people done to =
address this issue?*  I figure the first thing to do is to understand =
what's failed before.
>=20
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
>=20
> * - other than calling the customers stupid, which they are not, and =
is not helpful
>=20


--Apple-Mail=_8F777165-26DE-4ADC-8BDC-F07EA5BD1E53
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSzsO1rMabGguI180RAvEHAJ987lzDiflIhSufggWIX7P7WUVFggCdEDuY
dxYCyzi6xA4cz/P155T8LPA=
=tvRL
-----END PGP SIGNATURE-----

--Apple-Mail=_8F777165-26DE-4ADC-8BDC-F07EA5BD1E53--

From mark.tinka@seacom.mu  Thu Jan  9 03:04:32 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AED91AE26D; Thu,  9 Jan 2014 03:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0OVBMb7fXizw; Thu,  9 Jan 2014 03:04:30 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id DD01E1AE262; Thu,  9 Jan 2014 03:04:28 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W1DOz-0002Gm-N2; Thu, 09 Jan 2014 13:03:53 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org, stbryant@cisco.com
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Date: Thu, 9 Jan 2014 13:03:52 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk> <52CE80FC.9060306@cisco.com>
In-Reply-To: <52CE80FC.9060306@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart6950898.q6vmhhEH7r"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401091303.53239.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Thu, 09 Jan 2014 08:05:24 -0800
Cc: gorry@erg.abdn.ac.uk, lisp@ietf.org, tsvwg@ietf.org, david.black@emc.com, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 11:04:34 -0000

--nextPart6950898.q6vmhhEH7r
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Thursday, January 09, 2014 12:59:08 PM Stewart Bryant=20
wrote:

> I would be interested in what operators are observing in
> their network, because I have never heard a concern
> expressed that this was happening.

You mean for native MPLS, or for encapsulated MPLS?

Mark.

--nextPart6950898.q6vmhhEH7r
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJSzoIZAAoJEGcZuYTeKm+Gxx8QAImaR5aEcX9avA5B3dKrYbe4
AeGqeUKtVCjkZt9/p91LkMPXcRd9QcQzjfprDRwW0LT6PT9tkFWS/N6dep6ZZQ8x
UytAYCUVqEngI3El7p+LvSt97JW+n97/9aFRA6hD65av/PwOG4Y1M97rEP2qsnGu
pXG4TrZ+uJ28bjtXwahgHnhjKgF2Wu5rTSrdWpfShRRlYPsrMjFAw2gkOqGqwQGH
D1CUFnv8e3V2hj+rS9sWRf+qjGsqm5I273kLn6ryX6XBdjE+qZTDptdIXo43+/2I
qJsemitPOydyM4y8qCYL33dyLYUlFTMhW6IOakX4lzNPCPgcoTIqeJvjZHECT1hn
IcHZGgMDxVlbQgLIoGqmdHGLN5BQsHUfIWIkZLbn4ftaJ8oqFm8ZhWvGgLgxiZ2I
1p/87+rm9/6hnYPWdZOY2XlZ8yKEQbEQs6zalpvselUq7Ydk20JxtF74v5nuUIfx
N+WtjEYqGIhNCbiN68MRxyHWj1Ojlojo0W45raE+Cz5vmkQM6O4vpKUXue0BbLkR
2l3EjbusFbnJMzTR5B2qHFALS+EADIuoSxfdqSfUNQTYR1/K/z/te8g5fQbci6VW
WcP28pMwG48YGE8N2pyk/Rsk0wISDgtJ9Vu+mOzsDllAkQmMKRyDUpJKc2VepmhF
zgaLCG2+5qg/tLsKEs9G
=nW7X
-----END PGP SIGNATURE-----

--nextPart6950898.q6vmhhEH7r--

From mark.tinka@seacom.mu  Thu Jan  9 04:37:35 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C601AE215; Thu,  9 Jan 2014 04:37:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udwRene6NZUG; Thu,  9 Jan 2014 04:37:34 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id BD7E31AD8CD; Thu,  9 Jan 2014 04:37:31 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W1ErA-00037O-Os; Thu, 09 Jan 2014 14:37:04 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: stbryant@cisco.com
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Date: Thu, 9 Jan 2014 14:36:56 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com>
In-Reply-To: <52CE914B.7070506@cisco.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2216786.Gj6lG7fHB8"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401091437.04245.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Thu, 09 Jan 2014 08:05:35 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 12:37:35 -0000

--nextPart2216786.Gj6lG7fHB8
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant=20
wrote:

> Either or both.

I can only speak to native MPLS, as I've never run tunneled=20
MPLS.

> I am interested in how often in practice MPLS packets get
> misdelivered due to label corruption.

Well, first of all, routers would need to report corrupted=20
MPLS frames so operators can glean this data. This isn't=20
something I've come across, but it would be good to find=20
some kind of way to count this across interfaces, if the=20
routers can detect and report them.

The known issue about mis-delivery of MPLS frames is poorly-
sized MTU interfaces. I have no empirical data as to how=20
this can corrupt successive MPLS frames that may fit into=20
the transit MTU. But in this case, as with any Layer 2=20
traffic, not enough MTU =3D dropped frame.

Mark.

--nextPart2216786.Gj6lG7fHB8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJSzpfwAAoJEGcZuYTeKm+G5SAQALfNbYG3PYHbT7QCKV8dprMp
ryTPEndCuPuAlpjpfqZDscQSjn0K4F2wIofJN48CBDHC7ivhfBCuQUpNFbP+jYln
04mV9pEhM6urzKZQUgpq/GdMmUVG03loq8TPhZV6gT+3+hO26SnDwl8VzqdafaGi
K/e0qSuuwmlVKnN+ywhHTOwd+5r3mJPE6fZpSHByjjRz1EDPIgUptg8Cf5Wcz3uP
QlC0DM0drEYwZn+jzOOScv6Zvb+8/Z7e3zdFmLHIWYAi4xM89lWCNShU7bQNDwvp
Wc6gIFMaPY0A8Vj2gy1x61jf/PCXk69xSXt7n4tPTn4oRSMSfKFShInklxWmVtsq
wmM6D2QieXMB0lRrXzXSSnjJMvsNuhICqNy7FwI9MFfJEXFo/nsc13xZHnHf0VKV
tdCnlQheOehwK3qmZyg4OQiBIoQ10MRK4e/qgU9hyXJQrzResVAmf5HpiE1ZFIQH
AtQdcfd3PBvxrTO6p8NLRja7hPZ9CLu554Sz6Z2DA12mD/KZAkTbpz5bef4/fTSH
IPRz9VBwLeJEJQr1yg4aIK8p46TPNwMKvJjLsowydmb6PUo70JVmYKUPolbCYs8A
9KpuLtPk4miCEbIpRNLYOVFnJGCqnOsH0WmkDJFqCV0G+jESv7hZWnbU4nCnmtnO
lwX81Wa/2rU7Z/g6WUnW
=MplW
-----END PGP SIGNATURE-----

--nextPart2216786.Gj6lG7fHB8--

From prvs=0079a20b32=johnl@taugh.com  Thu Jan  9 08:10:09 2014
Return-Path: <prvs=0079a20b32=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AC71AE416 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:10:09 -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=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pwP_CnFL5IcL for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:10:08 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 585D61ADF7F for <ietf@ietf.org>; Thu,  9 Jan 2014 08:10:08 -0800 (PST)
Received: (qmail 54606 invoked from network); 9 Jan 2014 16:09:58 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 9 Jan 2014 16:09:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=ceb1.52cec9d6.k1312; i=johnl%iecc.com@submit.iecc.com; bh=9qL+RUiM6Pd51ZdCtOwsOkiZ0/bUQFeQ8N450J4BzJM=; b=gvt6uK5j6Np31o8LHbuq8K3OKEdsecnZqTZ/fr0i6yVXacYKQA6Xp0lKfVZII19hBtWXKw52G4I7qqGro/ZgoRgY3Xn8uKUwqmREiGRiwdoghn0HNCJblqI6EaBlRhhn6jmJThiqMsXenNh+57ISxDOJPaOESsbl5uKyihH6E7Fs4Ysjws3ToK75NaVS1sv8maAQuaOtBPLfrgr3UanVgiOOe19SwtWEV9nHuB1WSqs6OCkIaROtJxFmGt0QFm46
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=ceb1.52cec9d6.k1312; olt=johnl%iecc.com@submit.iecc.com; bh=9qL+RUiM6Pd51ZdCtOwsOkiZ0/bUQFeQ8N450J4BzJM=; b=qAxGQ12mrUjEQLh2oqDaUH5WbEv4nWs7vK6k+hfqK1Firxn3/uZU1gz3D527BZxtcBJ9j5UPr8LFOPGBqNyawZb6NUupUuvVlVh/MxM8d/wOVz0CkBPNWmGJFBCMdMyNwdjN3oBKxjLHmaFuDmwmDKZhBxJCVAWy6g8SeltWlsjv2DHefjL4HsGZuC9SViGKP/Kdcks//5T2XVc2jAjFQcPTwVw3kZP00a3jAkZMJi8FvzUC7rrmi6PQjUtOlxYu
Received: from joyce.dhcp.intranet ([155.70.23.45]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 09 Jan 2014 16:09:57 -0000
Date: 9 Jan 2014 11:09:55 -0500
Message-ID: <alpine.BSF.2.00.1401091109300.5419@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?=" <paf@frobbit.se>
Subject: Re: Multi-homed BCP38
In-Reply-To: <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-662924268-1389283797=:5419"
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:10:10 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-662924268-1389283797=:5419
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 9 Jan 2014, Patrik FÃ¤ltstrÃ¶m wrote:

> Not being an IP-routing person, but chair of SSAC in ICANN, I hear people for the reasons you bring up are more in favor of a mechanism where one talk about explicitly "filtering at the edge of the Internet" and not at every point where routes are exchanged.
>
> Because of this, please also include SAC004 in your investigation.
>
> <https://www.icann.org/en/groups/ssac/documents/sac-004-en.htm>

I see it mentions the exact scenario I mentioned, but then says "This is 
only a slight complication and does not invalidate the approach."  Maybe 
it was slight in 2002, but it seems to be more than slight now.

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

From jnc@mercury.lcs.mit.edu  Thu Jan  9 08:16:12 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E29621AE045; Thu,  9 Jan 2014 08:16:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.738
X-Spam-Level: 
X-Spam-Status: No, score=-4.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1D3k685dDqi; Thu,  9 Jan 2014 08:16:11 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 699851ADF7D; Thu,  9 Jan 2014 08:16:11 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 73C8D18C0BF; Thu,  9 Jan 2014 11:16:01 -0500 (EST)
To: ietf@ietf.org
Subject: RE: [tsvwg] Milestones changed for tsvwg WG
Message-Id: <20140109161601.73C8D18C0BF@mercury.lcs.mit.edu>
Date: Thu,  9 Jan 2014 11:16:01 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: tsvwg@ietf.org, jnc@mercury.lcs.mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:16:13 -0000

    > From: <l.wood@surrey.ac.uk>

    > any IP/UDP header corruption goes undetected at the endhost because the
    > pseudoheader checksum has been disabled. .. the header corruption takes
    > the packet to some other destination/port, so you don't see it; it's
    > just a drop as far as you are concerned. But it matters for whatever
    > actually receives that corrupted packet on e.g. an altered port value.
    > ...
    > odd behaviour on other applications at the same endpoints (or, with
    > IPv6, in the same network) caused by missent packets with corrupt ed
    > UDP packets? Hey, not your problem. Hey, you're working just fine.
    > It's pollution and tragedy of the commons, basically.
    > When you send with a zero UDP checksum, it's possible for the packet to
    > be received and processed anywhere.

Outlawing use of non-checksummed UDP for tunnels isn't going to _guarantee_
that such packets never show up at a host: malicious or buggy software could
also generate them - as could whatever is hypothetically damaging
non-checksummed UDP tunnel packets.

So hosts have to be able to deal with such packets anyway.

The only question left, then, is 'is this happening often enough to present a
significant processing load to the innocent bystanders' (which I agree would
be problematic). But here I echo Stewart Bryant: what data is there that this
is actually happening often enough to be a problem?

And along those lines, I'm looking at the 'incoming traffic' light on my cable
modem, and it's blinking constantly - port scanners and such, I assume. A few
stray tunnel packets would be lost in that flood.

	Noel

From loa@pi.nu  Thu Jan  9 08:17:21 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62A941AD68A; Thu,  9 Jan 2014 08:17:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mjlRICDVIyjD; Thu,  9 Jan 2014 08:17:19 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 104661AE373; Thu,  9 Jan 2014 08:17:19 -0800 (PST)
Received: from [192.168.1.5] (unknown [119.95.157.254]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id CD075180145E; Thu,  9 Jan 2014 17:17:04 +0100 (CET)
Message-ID: <52CECB7B.3090200@pi.nu>
Date: Fri, 10 Jan 2014 00:16:59 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: mark.tinka@seacom.mu, stbryant@cisco.com
Subject: misdelivered mpls packets - Was: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu>
In-Reply-To: <201401091437.04245.mark.tinka@seacom.mu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:17:21 -0000

Changed the subject line !

On 2014-01-09 20:36, Mark Tinka wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled
> MPLS.
>
>> I am interested in how often in practice MPLS packets get
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted
> MPLS frames so operators can glean this data. This isn't
> something I've come across, but it would be good to find
> some kind of way to count this across interfaces, if the
> routers can detect and report them.

This would be possible to do with MPLS-TP OAM, wouldn't it?

/Loa
>
> The known issue about mis-delivery of MPLS frames is poorly-
> sized MTU interfaces. I have no empirical data as to how
> this can corrupt successive MPLS frames that may fit into
> the transit MTU. But in this case, as with any Layer 2
> traffic, not enough MTU = dropped frame.
>
> Mark.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64

From adrian@olddog.co.uk  Thu Jan  9 08:19:22 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D41FD1ADF7D for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2acABbEKmGUz for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:19:21 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 5264C1ADF70 for <ietf@ietf.org>; Thu,  9 Jan 2014 08:19:21 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s09GJAtC007235; Thu, 9 Jan 2014 16:19:11 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s09GJ8LQ007210 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jan 2014 16:19:09 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'John R Levine'" <johnl@taugh.com>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se> <alpine.BSF.2.00.1401091109300.5419@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1401091109300.5419@joyce.lan>
Subject: RE: Multi-homed BCP38
Date: Thu, 9 Jan 2014 16:19:07 -0000
Message-ID: <02b201cf0d56$86d183e0$94748ba0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH1BbaxUhL/5/K6YO6HSDDaiXvTZwG9LUDhAlAQ2oCaEDY1oA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: 'IETF general list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:19:23 -0000

John,

Coming at this from a different perspective and not sure it is relevant =
to the question you asked, but this seems to be one of the problems that =
Homenet is trying to solve and is giving rise to "new" routing concepts =
within the home network in order to hit the right egress homing point.

Adrian


From tjc@ecs.soton.ac.uk  Thu Jan  9 08:23:49 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF231AE44B for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.759
X-Spam-Level: 
X-Spam-Status: No, score=-1.759 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGmx1meFcB3E for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:23:47 -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 69A491AE00D for <ietf@ietf.org>; Thu,  9 Jan 2014 08:23:47 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s09GNZsL025472; Thu, 9 Jan 2014 16:23:35 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s09GNZsL025472
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1389284615; bh=AZ3m9X67PsluKVJ/1vOGJzIxuT0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=qPcdUU/ZIoLs/rPbkVWRdmSJDVsancpTQfdCPN3oat+ocOJEIyTiiFarcodvDptTt kG0HV1E+QSeTgW58LILThCWg6wkFZbTNsMurDIzoaL6FozfwDQcQ91mFOuUzF0JJSl s51xyeBvjbzX0QWH8aLdOjmfYUfzbd2+Ey7iIKcs=
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 q08GNZ0959655954YQ ret-id none; Thu, 09 Jan 2014 16:23:35 +0000
Received: from tjc-vpn.ecs.soton.ac.uk (tjc-vpn.ecs.soton.ac.uk [152.78.236.241]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s09GNVKE027942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jan 2014 16:23:32 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Multi-homed BCP38
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <02b201cf0d56$86d183e0$94748ba0$@olddog.co.uk>
Date: Thu, 9 Jan 2014 16:23:36 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|b842ba90f0fee84ad8745e3ec00d4678q08GNZ03tjc|ecs.soton.ac.uk|EC671EA8-FDC2-4B31-83C0-5930157DB26E@ecs.soton.ac.uk>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se> <alpine.BSF.2.00.1401091109300.5419@joyce.lan> <02b201cf0d56$86d183e0$94748ba0$@olddog.co.uk> <EC671EA8-FDC2-4B31-83C0-5930157DB26E@ecs.soton.ac.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q08GNZ095965595400; tid=q08GNZ0959655954YQ; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s09GNZsL025472
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: 'John R Levine' <johnl@taugh.com>, 'IETF general list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:23:49 -0000

On 9 Jan 2014, at 16:19, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> John,
>=20
> Coming at this from a different perspective and not sure it is =
relevant to the question you asked, but this seems to be one of the =
problems that Homenet is trying to solve and is giving rise to "new" =
routing concepts within the home network in order to hit the right =
egress homing point.

Indeed, though that may require extensions to support routing based on =
both src & dst addresses.  There have been presentations about that at =
the last two or three homenet WG sessions.

Tim=

From scott.brim@gmail.com  Thu Jan  9 08:53:15 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 494C11AE02A for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:53:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S7_6ZypIxmTg for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 08:53:14 -0800 (PST)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5E1D71ADF7D for <ietf@ietf.org>; Thu,  9 Jan 2014 08:53:14 -0800 (PST)
Received: by mail-oa0-f54.google.com with SMTP id o6so3691357oag.13 for <ietf@ietf.org>; Thu, 09 Jan 2014 08:53:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=mzbIju+5myg+7GklpSFR5raSCUWdomLdsCCUHJp7qy4=; b=tq5WCDhMF66PwTfM5r2c3FHPnoZlmGhp4tc1wB1gmSJQbWlMSJu7H53dPsHLt81cIH qvkaQG+3N1vhUTtImqyBMyYYi3G/oqClkP+3tgujXLxJUtDXY+iLen/p1CtkIqkp42Wa EqaNJwqTx+nduytRxMzn71eUweG9j9oqogsB0iaQ/ufUYQatjihXqsN2rV2F2XCd08zi vYrUOaCfAww2xXUZM9pcwiHY9QlhhTgnVEa8Y1sfprdoob+vROXgPq+eGS45nIXKZoBt 2ZMpo8DTuDrxe2mEhFtFkb6LsF2nsylp7UQrL2ZvH3vscOZGxJE8hG1ElM1u3GQgTG+P mRlw==
X-Received: by 10.60.174.167 with SMTP id bt7mr2121151oec.54.1389286384686; Thu, 09 Jan 2014 08:53:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 9 Jan 2014 08:52:44 -0800 (PST)
In-Reply-To: <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 9 Jan 2014 11:52:44 -0500
Message-ID: <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com>
Subject: Re: Multi-homed BCP38
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 16:53:15 -0000

On Thu, Jan 9, 2014 at 10:43 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:
> Not being an IP-routing person, but chair of SSAC in ICANN, I hear people=
 for the reasons you bring up are more in favor of a mechanism where one ta=
lk about explicitly "filtering at the edge of the Internet" and not at ever=
y point where routes are exchanged.

Where is "the edge"? Is there a boundary outside of your control that
you truly trust? Even if there's supposedly unbreakable filtering at
most of the edge, wouldn't you want to do your own filtering as well?

It looks like the sites John talked to are multihomed, NOT doing
routing at their edge (??), and yet wanting to filter? I don't think
you get all three of those.

Scott

From ogud@ogud.com  Thu Jan  9 09:09:40 2014
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7241ADFA4 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AhA6_ZwDbspu for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:09:38 -0800 (PST)
Received: from smtp86.ord1c.emailsrvr.com (smtp86.ord1c.emailsrvr.com [108.166.43.86]) by ietfa.amsl.com (Postfix) with ESMTP id B6CCB1ADF96 for <ietf@ietf.org>; Thu,  9 Jan 2014 09:09:38 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 346C25020F for <ietf@ietf.org>; Thu,  9 Jan 2014 12:09:29 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 04C0850224 for <ietf@ietf.org>; Thu,  9 Jan 2014 12:09:28 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Multiple Namespaces Re: Split the IANA functions?
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <2520.1389225982@perseus.noi.kre.to>
Date: Thu, 9 Jan 2014 12:09:28 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:09:41 -0000

On Jan 8, 2014, at 7:06 PM, Robert Elz <kre@munnari.oz.au> wrote:

>    Date:        Wed, 8 Jan 2014 13:07:12 -0800
>    From:        manning bill <bmanning@isi.edu>
>    Message-ID:  <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
>=20
>  | There can be/ have been multiple roots in the DNS - HOWEVER, there =
is
>  | a always a single root _per class_.
>=20
> I'm not sure that's correct.   Nor do I know it is incorrect.  Classes
> were (and are) so under-specified that exactly how they were intended =
to
> work (if there was ever a clear and understood interpretation of that)
> seems lost in the mists of time.
>=20
<snip>=20
> There really is no way out of this - people wanting multiple roots =
really
> just want to change who controls that rot - usually to someone they =
consider
> friendly to themselves (like themselves) rather than someone that they =
consider
> the enemy (ietf/iana/icann/...)
>=20
> kre
>=20


The fundamental problem with multiple namespaces we have now is "how =
does one express what namespace the name is in?"

Some people have tried to do this with postfix (eg. .onion or .local)
Others have said look first in namespace X then in namespace Y (MDNS)

Another signifiant problem is how to provide a programming interface to =
lookups in the new namespaces,=20
for expediency people frequently start out by extending the functions =
that look up in DNS.=20

Personally I think that if we want to to become serious about supporting =
multiple namespaces we need guidelines on:
	How new namespaces are identified=20
	How to "register" namespace identifiers and operators of the =
namespace root (if applicable) as well as how names=20
		are registered/selected in the namespace. I use the word =
register here loosely, as I do not know if anything other than=20
	        centralized service will work to avoid conflicts.=20
	On top of existing name lookup functions we need a multiplexer =
function that understands how to access=20
		the namespace and calls appropriate lookup functions=20
	Automated discovery of how to use new namespaces without this =
new namespaces will take a long time to deploy.
	How/If to support Meta Namespaces i.e. check a series of =
namespaces in either in a particular order and use first match OR
	       lookup in parallel in a number of name spaces.=20

The difference in lookup function could be DNS vs  DNS for different =
class vs Distributed hash.=20
In the first and second case we can in theory use the same functions but =
with different starting point and different cache (if one is present)=20
in the third case a different function is needed.=20

<potentially moving into solution space to make a point, this is NOT A =
FORMAL PROPOSAL>=20

No matter how we do the identification of name spaces other than DNS in =
class IN, postfix IMHO is the wrong answer.=20

One possibility is to use a prefix, something like GNU##freedom.eff     =
(## picked at random as separator)=20
to express that lookup should take place in the namespace GNU for host =
freedom.eff. =20
The advantage of a prefix is that it appears in a better location for a =
namespace multiplexing function when it is parsing the string and in =
theory
the namespace multiplexing function does not need to understand the rest =
of the string past the namespace identifier.=20

Thus in this notation DNS###tools.ietf.org is the corresponding =
expression for looking up the host name: tools.ietf.org in class IN of =
DNS,

On a billboard or web page this would become either =
https://DNS##tools.ietf.org or DNS##https://tools.ietf.org depending if =
we put the
protocol or Namespace first.=20

Working out a timeline to complete an effort to make all of this work is =
left as an exercise to the reader=20

	Olafur



From sm@resistor.net  Thu Jan  9 09:17:11 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D981AE432; Thu,  9 Jan 2014 09:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZJahfGxCz8IR; Thu,  9 Jan 2014 09:17:09 -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 4BFA51AE446; Thu,  9 Jan 2014 09:17: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 s09HGO5l013101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 09:16:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389287796; bh=x87d+bJQ38QI3fFzdenRbWaPzPHdfjF9omleGbo3iXE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k3OgvhVVwsZ/vl6DtETu70cnGXFj5h9R8XHVpB+yuzciC7EBUSUbaf8Vks3jyageS VT8DNKfeaweWuZiKOPDEseFEGF+awVgMs178BTJ7RMihX9pbCYwyiZTxvFNhj6ifv+ 4AmAhINJ54dvNmhNy2kifq6p8H8r88ZpvAM6gqAg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1389287796; i=@resistor.net; bh=x87d+bJQ38QI3fFzdenRbWaPzPHdfjF9omleGbo3iXE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Juk0lAKcmM0LsogZAHYfBGl6I+8FywQvP2ZHkCrmWcGn5M0aD548A8Nu38dB7t6sK lk+XFFmFvUFC3iK8BnJppvXMpPwWO9GtabqDD6ySn3Ehyalq/mQ8ZG9DiVHsfAvo6W 3wmoNyoeQffg184F5/cYaJrIvby6sJVRgGmFvX/Q=
Message-Id: <6.2.5.6.2.20140109051548.0a951040@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Jan 2014 07:47:46 -0800
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
From: SM <sm@resistor.net>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
In-Reply-To: <20140109105804.GA44893@elstar.local>
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com> <6.2.5.6.2.20140108233958.0a849e58@resistor.net> <20140109105804.GA44893@elstar.local>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Andy Bierman <andy@yumaworks.com>, netmod@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:17:11 -0000

Hi Juergen,
At 02:58 09-01-2014, Juergen Schoenwaelder wrote:
>People want to be able to configure timezones using the timezone
>naming scheme commonly supported by operating systems (e.g.,
>Europe/Paris). This document defines a serialization of the timezone
>names into YANG format for this purpose. I believe there was indeed
>strong concensus on this in the WG.

There was a message about a quick poll [1] to adopt 
draft-lange-netmod-iana-timezones-01 on 2 July, 2012.  Three persons 
expressed their support and the WG Chair expressed his support as a 
technical contributor [2]; there weren't any message objecting to 
adoption.  There were two comments [3][4] on 30 July, 2012.  There 
was a WG Last Call announcement [5] and two reminders [6][7] about 
it. There was a message [8] on 12 November, 2013 from a WG 
participant (I am not taking into account the message from the author 
and one of the WG Chairs).  My comment about the determination of 
consensus being questionable is based on the messages in the NETMOD 
mailing list archive.

>This document aims at establishing an IANA maintained serialization of
>whatever list of names the timezone database contains. It does not
>change the way the TZ coordinator, an IANA Designated Expert, takes
>decisions. Perhaps this needs to be stated more explicit.

There is a thread at 
http://mm.icann.org/pipermail/tz/2012-May/017711.html  The problem is 
not changing the way things are done.  I would describe the current 
TZ approach as keeping the TZ information up-to-date by posting a 
(software) release every now and then.  It works for me.

>So far (in the MIB world), the initial versions of IANA maintained
>modules were published as Proposed Standards on the standards track
>(although the only thing that really remains valid over time are the
>IANA considerations, which however often require the initial module to
>be available). We simply followed this practice.

If I understood correctly the YANG module defined in the draft 
creates IANA-registered timezones based on public domain [9] 
information about timezones.  IANA is then asked to keep the 
IANA-registered timezones up-to-date.  That sounds okay if the 
politics about time are not taken into consideration [10][11][12].

>There was concensus in the WG that it is desirable to configure
>timezones by name (e.g., Europe/Paris) instead of having only hard
>coded UTC offsets - the benefits should be obvious.

I agree that there can be benefits to that approach.  I could not 
find the (mailing list) message where that WG decision was taken.

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/netmod/current/msg06810.html
2. http://www.ietf.org/mail-archive/web/netmod/current/msg06841.html
3. http://www.ietf.org/mail-archive/web/netmod/current/msg06932.html
4. http://www.ietf.org/mail-archive/web/netmod/current/msg06933.html
5. http://www.ietf.org/mail-archive/web/netmod/current/msg08327.html
6. http://www.ietf.org/mail-archive/web/netmod/current/msg08333.html
7. http://www.ietf.org/mail-archive/web/netmod/current/msg08335.html
8. http://www.ietf.org/mail-archive/web/netmod/current/msg08694.html
9. ftp://ftp.iana.org/tz/tz-link.html
10. 
http://www.theguardian.com/news/datablog/2013/sep/26/spain-countries-wrong-time-zone
11. http://972mag.com/the-worlds-only-ethnic-time-zone/81006/
12. 
http://www.theblaze.com/stories/2013/09/22/just-wait-until-you-see-how-apples-new-operating-system-lists-jerusalem/ 


From john-ietf@jck.com  Thu Jan  9 09:24:52 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5877A1AE3E2 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HKeuQYJ-5aR8 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:24:47 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B0A251AE43A for <ietf@ietf.org>; Thu,  9 Jan 2014 09:24:47 -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 1W1JLS-0009Sy-56 for ietf@ietf.org; Thu, 09 Jan 2014 12:24:38 -0500
Date: Thu, 09 Jan 2014 12:24:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Upcoming change to announcement email header fields (using old header)
Message-ID: <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com>
In-Reply-To: <20140109140002.11063.48808.idtracker@ietfa.amsl.com>
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:24:52 -0000

--On Thursday, January 09, 2014 06:00 -0800 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> We will soon be changing the header fields used in IETF Last
> Call messages sent to the IETF Announce mailing list.
>...
> This message will be repeated daily using both the old and new
> header. This instance of the message was sent using the old
> header. Please ensure you receive both versions.
> These messages will cease, and all Last Call messages to this
> list will switch to using the new header on or shortly after
> 2014-01-24.
>...
> The specific changes are:
>...
> New:
> 
>    From: The IESG <noreply@ietf.org>
>    To: IETF-Announce:;
>    Reply-To: IETF Discussion List <ietf@ietf.org>
> 
> and the message sent using the New header fields will also be 
> Bcc-ed to <ietf-announce@ietf.org>

Folks,

Three observations based on some small experience with Internet
mail and various MUAs.

(1) If someone is going to have or detect problems with this
change, it would be very useful to identify what you are putting
in the envelope, especially the backward-pointing parts of the
envelope.  If someone had to start tracking through logs to
identify what happened to a missing message, knowing, e.g.,
whether ietf or AMS domains were being used in EHLO and MAIL
command arguments might be a big help.

(2) Especially given the history of configuration failures that
have periodically allowed random parties to post messages or
replies to IETF-Announce, the reasons for the change in "From:"
and "Reply-to;" fields are obvious and probably should have been
thought of and adopted years ago.  The posting filters will
still be needed (I hope we are not going to rely on the security
through obscurity of a secret address), but this should at least
stop the accidents.

However, despite the fact that group syntax, including that for
empty lists, has been part of the mail header specs for well
over 30 years, we know that many systems have had trouble with
messages that contain only an empty group indication.  Those
systems are not just non-conforming MUA or mailstore
implementations (or MTAs that violate the SMTP spec and look at
headers in transit) or antispam systems of various qualities.
They including a variety of coded and ad hoc mail classification
and filtering arrangements that may require special arrangements
for such addresses.   Given the risks and potential problems,
I'd like to hear a little more justification for switching to
group syntax than the apparent "the IESG  decided on this and is
announcing it to the community".

(3) If someone actually does discover that they have a problem
and are dependent on a third-party supplier to get it patched, 2
1/2 weeks are unlikely to be sufficient.

I hope this comment doesn't turn into a distraction, but, when
announcements like this appear with no prior discussion with the
community, I wonder what the process was that produced the
decision and whether we've abandoned the principle that the IESG
is supposed to be steering and determining and reflecting
community consensus, not making decisions and pronouncements in
secret and top-down.

    best,
   john




From dave@cridland.net  Thu Jan  9 09:39:37 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8CB1AE049 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xJwe166azELq for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:39:36 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 35AE01AE02E for <ietf@ietf.org>; Thu,  9 Jan 2014 09:39:36 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id wm4so3626767obc.10 for <ietf@ietf.org>; Thu, 09 Jan 2014 09:39:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=36NSCD0b+YMtSsj2fMsLr57+syVFA4IRfmQytolJ4cM=; b=CXe7n048Sd2b56s46EcDYItOmgij065Hdb7JOemkqqvQzCJZzlYOv8/mWr4xVOxlBT 9DIkrum0Wpy4A5be+///gJ1vmTRjeXm6lgnUqHsoj04kNSQsvOXpSVT2+srwS60wzB5P 8/o2Ouofxv2cyOchJU6Cjfc3nfgYduYgWQvPw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=36NSCD0b+YMtSsj2fMsLr57+syVFA4IRfmQytolJ4cM=; b=SV78+7+ur49KSwMpy6tG+CN9hpFlN/PSFbxxUm9UqzfJKzgBPGbSkXhXcEezFqrzGN Ytp/ZfsiPGeWz4vIqi9jeSyWJW5NQpzyS0WUpMSUWdMbDn286PLlONt9GBmbrkdK63qs XQV1AYpzecEpbn2WpYDvq6EcrfxZ6/ueKIFPP1RnVmgIEBZV5NzuVc0VFvESq9Carz5L 7hEJZ2BNPihb2biI6t8fVcbUJcRsIDxh8QKEc1RTW1bBdgD3/sHeMDqpdh3ueZ8YIOGk /IZVwxjHvyoIrvyPaPRI7jkGrZj+O6jyz7vGi+6RO+Ajr2BLI+ncoF69RtUvvJsEmFia +Ezw==
X-Gm-Message-State: ALoCoQlXCpBEXJtoHuizbWLVQn9wIGjG+vcLZilHcu5BcPZQPCzl2PxLii2VhqBT0j+13ArHgEoS
MIME-Version: 1.0
X-Received: by 10.182.18.102 with SMTP id v6mr2095979obd.71.1389289166447; Thu, 09 Jan 2014 09:39:26 -0800 (PST)
Received: by 10.60.55.138 with HTTP; Thu, 9 Jan 2014 09:39:26 -0800 (PST)
In-Reply-To: <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com>
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com>
Date: Thu, 9 Jan 2014 17:39:26 +0000
Message-ID: <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.gmail.com>
Subject: Re: Upcoming change to announcement email header fields (using old header)
From: Dave Cridland <dave@cridland.net>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11c339e642b36504ef8d1760
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:39:37 -0000

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

On Thu, Jan 9, 2014 at 5:24 PM, John C Klensin <john-ietf@jck.com> wrote:

> Three observations based on some small experience with Internet
> mail and various MUAs.
>
>
I'll add one.

Much as I adore the almost wonderful irony of "The IESG" having an address
of <noreply@ietf.org> - especially in the light of John's closing comment
there - many MUAs will then cheerfully offer that as an address for "The
IESG".

If that is a dev-null address, as noreply@ often implies, it'll become a
self-fulfilling prophecy of sorts. You might want a different phrase, there
- "IESG Announcements", or something.

Dave.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jan 9, 2014 at 5:24 PM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D=
"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Three observations based on some small exper=
ience with Internet<br>
mail and various MUAs.<br>
<br></blockquote><div><br></div><div>I&#39;ll add one.</div><div><br></div>=
<div>Much as I adore the almost wonderful irony of &quot;The IESG&quot; hav=
ing an address of &lt;<a href=3D"mailto:noreply@ietf.org">noreply@ietf.org<=
/a>&gt; - especially in the light of John&#39;s closing comment there - man=
y MUAs will then cheerfully offer that as an address for &quot;The IESG&quo=
t;.</div>
<div><br></div><div>If that is a dev-null address, as noreply@ often implie=
s, it&#39;ll become a self-fulfilling prophecy of sorts. You might want a d=
ifferent phrase, there - &quot;IESG Announcements&quot;, or something.</div=
>
<div><br></div><div>Dave.</div></div></div></div>

--001a11c339e642b36504ef8d1760--

From john-ietf@jck.com  Thu Jan  9 09:49:05 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F7F1AE05D for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eQZdy5UvHs2m for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 09:49:04 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 48C041ADFA3 for <ietf@ietf.org>; Thu,  9 Jan 2014 09:49:04 -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 1W1Jiu-0009V4-Th; Thu, 09 Jan 2014 12:48:52 -0500
Date: Thu, 09 Jan 2014 12:48:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: DNS design
Message-ID: <29A7BEB33E32EC9D427500ED@JcK-HP8200.jck.com>
In-Reply-To: <52CEB680.4010706@cisco.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@cisco.com> <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com> <52CEB680.4010706@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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:49:05 -0000

--On Thursday, January 09, 2014 15:47 +0100 Eliot Lear
<lear@cisco.com> wrote:

> John,
> 
> Just to be clear, I was using DNS as an example.  We can
> always question design decisions we've made.  I believe that
> Andrew and others may be interested in doing just that, but
> not from the top down (as it were).

Certainly we can, and should, question design decisions we've
made, if only to learn from them.  For the same reason, I also
think it is appropriate to review and question the goal and
constraint decisions that drive those design decisions

But I think two points are relevant when we start doing so:

(1) The observation that a decision may have political
implications -- at present or at some point in the future-- does
not make the decision itself political rather than technical.
For the IETF's work, political considerations are best
incorporated into goal and constraint spaces rather than leading
us into an argument about the basis on which those decisions are
made.

(2) Unless one is either trying to learn in the hope of doing a
better job on future designs or likes purely theoretical
discussions about the circumstances that would prevail in some
alternate reality, it seems to me that discussions of the
implications of trying to deploy redesigned versions of
something should be considered as part of the constraint space
for any results of questioning design decisions.   Our track
record for deployment of incompatible replacements for things
that work even moderately well has been, IMO, poor enough to
give us considerable pause if, e.g., someone proposes to take
"questioning design decisions" toward an effort to redesign,
reimplement, and redeploy the DNS.  My own hypothesis about that
is that the DNS we have is pretty much the DNS we are going to
have and that it would serve the broader community well if we
both accepted that and because more aggressive about saying "not
a good idea, find some other facility to use as a base" when
ideas come along that require violations of important principles
of the design.

best,
   john




From huubatwork@gmail.com  Thu Jan  9 09:59:07 2014
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3916B1AE037; Thu,  9 Jan 2014 09:59:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i1w5ISvsAUPS; Thu,  9 Jan 2014 09:59:05 -0800 (PST)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0BF7D1ADF8C; Thu,  9 Jan 2014 09:59:04 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id h10so1618109eak.16 for <multiple recipients>; Thu, 09 Jan 2014 09:58:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/vxgliJ4X1BuIFdyXzXCO5LYDKB3JmRy977VfMjxC08=; b=Qvy5cbOwTeQylcAQEAQy1Y9jxlAyMpOL5lHPHMRL5/6PYHD2n9rLnBZXszwVqj3L2n x2Sdv+5vZEhOrVF4F2ZBS8CkAIj1yaikwWLX319/ehTNukfKDlwKBY6hAtr7cmmTp52W oq9IckDe5Wv6OrQ2uquUx0BukzkIWv8qyGu/TpbFefMsUqp23SZMXWvtCKtUPAhgliMY nP+IFp9iNRh4W3N3zW5N+iddX20XQsYVGWH5mJptPp8EHOCJfRO+cM+2cOa3FFRrkAKw FcNXGzHFpS/Vg6D9BzdMiNX69HKBZS5FqN6+m3B0C2Pst1HBpTctxYRpDq7+zd6dH9gj 6r/w==
X-Received: by 10.14.5.194 with SMTP id 42mr4690805eel.100.1389290335030; Thu, 09 Jan 2014 09:58:55 -0800 (PST)
Received: from McAsterix.local (g215085.upc-g.chello.nl. [80.57.215.85]) by mx.google.com with ESMTPSA id v1sm7582058eef.9.2014.01.09.09.58.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 09:58:54 -0800 (PST)
Message-ID: <52CEE358.1050309@gmail.com>
Date: Thu, 09 Jan 2014 18:58:48 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Subject: Re: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu> <7347100B5761DC41A166AC17F22DF1121B743FDC@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B743FDC@eusaamb103.ericsson.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:59:07 -0000

Hello Greg,

You wrote:

> I think that you're referring to Connectivity Verification in
 > MPLS-TP (RFC 6428). It would only detect mis-connection
 > but would not count leaked in frames.

Indeed.
However, there is the Loss Measurement tool which can be used
to count dropped and mis-delivered packets.

Note that the CV tool in G.8113.1 includes packet loss counting.

> Such problem may be more apparent in Segment Routing (SPRING WG).
 > Perhaps CV should be a requirement in SR OAM.

Indeed.

Regards, Huub.




-- 
*****************************************************************
               è¯·è®°ä½�ï¼Œä½ æ˜¯ç‹¬ä¸€æ— äºŒçš„ï¼Œå°±åƒ�å…¶ä»–æ¯�ä¸€ä¸ªäººä¸€æ ·

From scott.brim@gmail.com  Thu Jan  9 10:06:17 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC081AE067 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:06:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g6eFsoXdgRie for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:06:15 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9EF0F1AE123 for <ietf@ietf.org>; Thu,  9 Jan 2014 10:06:15 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id gq1so3644444obb.3 for <ietf@ietf.org>; Thu, 09 Jan 2014 10:06:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/NHzHtRFGfPyj6HuVDHm7hOmNgWuztyOU0xzx4+Zvc8=; b=FYpwC9aVsg+nPmvkujgjS1+5NfOmStiZYTwXd0VupI0xXBG7rQFl0vK1F9nBIG/NaY cFB9fXj7NB1e6qPHSTakZx24HxCdOkHi1onwZN6mRA27K+zgs+DMJSuep18t8pGCh1Ia spW//Om850SoE0RzvNyGJv9ywEbxbJ1CYvE7R5lI0EAy2EMf8FFaet+XB+RqY4GTHJCg ieK2I55UkDDLfVqRotvt05Bj4d3d3ImS12DmFO20Ldx5Z/+L2ma9DRuj2Qxc9dLF5JgV vk3cZEAC9DVRO0pa7Qisb+2JoRENFZA3z4QMp0t8UNUCEtKP5YNUKQCbIYUxwu15za4k rdYA==
X-Received: by 10.182.166.40 with SMTP id zd8mr3287599obb.25.1389290765904; Thu, 09 Jan 2014 10:06:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 9 Jan 2014 10:05:45 -0800 (PST)
In-Reply-To: <52CC5C57.4040902@dcrocker.net>
References: <52C5C204.60708@cs.tcd.ie> <24105.1388766859@erosen-linux> <CAF4+nEHDNC-aQCY6r1zceb=7hOW4JmfnMWDWZSEM6gJLTSDF9Q@mail.gmail.com> <01P2V8MN121I0000AS@mauve.mrochek.com> <52CC5C57.4040902@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 9 Jan 2014 13:05:45 -0500
Message-ID: <CAPv4CP8ZKpRFZRa_USa=NgoRa6C5icD-V7EZPOXUzAqU6VZQNg@mail.gmail.com>
Subject: Re: Last Call: <draft-farrell-perpass-attack-02.txt> (Pervasive Monitoring is an Attack) to Best Current Practice
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 18:06:17 -0000

On Tue, Jan 7, 2014 at 2:58 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> I've advocated Experimental, though I've thought Informational would also be
> ok.  On further reflection from people's comment, I now think Informational
> would be the sufficient and safer choice.

There's nothing to experiment on, nothing to report back on. It tends
toward Informational.

The inclination to make it a BCP would come from the fact that it's
the basis for extending an existing BCP. However, it does not actually
do the extending, it just sets the stage and the direction.

As I said before (on some thread) I now believe this should be
published as informational and then when a more specific BCP-level
draft is written, this one can be reiterated in a section near the
top.

> The more important issue is that the draft does usefully introduce the topic
> of PM to IETF work.

Yes. Any status is acceptable to me, let's just get it out.

Scott

From christopher.morrow@gmail.com  Thu Jan  9 10:33:59 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84BA21AE08A for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:33:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Foj84DRfT08L for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:33:57 -0800 (PST)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 62F231AE075 for <ietf@ietf.org>; Thu,  9 Jan 2014 10:33:56 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id n7so2460268lam.2 for <ietf@ietf.org>; Thu, 09 Jan 2014 10:33:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=XSqa4TRBzDV9JaJxJoD49XkBtzS+yUWTOzw11UEObhY=; b=V+z9ZADHbN7SRKZ+kiAzZudRJEfl1+VMhPVG5Q2xmumeoYtfo64wSop2VmGMdAlKYL g7i338uQdnBLuzyVyQT1FkhvaHqCV0ucparPy+AKnk24ZfJL0tHMP/vgHO7uvCuSgQxy XO/LjDviIBaItooiYWoHi0RTubbFepaSDpeYywA3yEJiDz0DAOQjHc06xS5eDxqa6fTi AND7vSXPP83hhJQTWxnwUInRrQo4L7+Y4A1lCgnirVcB3K9r08OnFhMqPuR6OhgKaZxX bs0QsEukQm1gn5juHmrZorpPf1TnO4R2cMiiLuz1awDAnFCgcTAUat83E0PGpIij9VQT C+wQ==
MIME-Version: 1.0
X-Received: by 10.112.155.198 with SMTP id vy6mr337983lbb.91.1389292426092; Thu, 09 Jan 2014 10:33:46 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.37.170 with HTTP; Thu, 9 Jan 2014 10:33:46 -0800 (PST)
In-Reply-To: <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se> <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com>
Date: Thu, 9 Jan 2014 13:33:46 -0500
X-Google-Sender-Auth: OEpjJpWXcr2h_jAKKI8wbwJtGS0
Message-ID: <CAL9jLaZSOwAcsX8PQyS9PpE+EBT02pm27FAejxHhiHf=c2iUeg@mail.gmail.com>
Subject: Re: Multi-homed BCP38
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 18:33:59 -0000

On Thu, Jan 9, 2014 at 11:52 AM, Scott Brim <scott.brim@gmail.com> wrote:
> On Thu, Jan 9, 2014 at 10:43 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wr=
ote:
>> Not being an IP-routing person, but chair of SSAC in ICANN, I hear peopl=
e for the reasons you bring up are more in favor of a mechanism where one t=
alk about explicitly "filtering at the edge of the Internet" and not at eve=
ry point where routes are exchanged.
>
> Where is "the edge"? Is there a boundary outside of your control that

ideally a customer filters at every LAN port ... that way it's pretty
simple to tell what you should be filtering :)

after that it'd be nice if their egress port to 'internet' included:
"permit ip MYSRC any"
so that in case of internal issues with config consistency/etc they
still don't leak out bad sources.

At the 'ISP' level, this sort of thing is practical really only at the
customer link, it's not super practical to filter on links between
ISPs (maybe it is for TierX but not Tier X-M)...

> you truly trust? Even if there's supposedly unbreakable filtering at
> most of the edge, wouldn't you want to do your own filtering as well?

sure, can you define the filter between (for pathological cases)
Level3 and ATT ? or NTT and Cogent?

it gets much harder to do this in a not-super-brittle way pretty
quickly at that level of the network hierarchy :(

> It looks like the sites John talked to are multihomed, NOT doing
> routing at their edge (??), and yet wanting to filter? I don't think

that's not clear, from john's description at least.

> you get all three of those.

For some of the cases John is talking about it's probably 'hard' to do
the filter, but for many folk as long as you are already filtering the
routes the 'customer' sends (and you ARE doing that, right? you dont'
want to be PCCW do you? :) ) it's pretty darned simple to just filter
inbound properly there. (or for the customer to properly egress filter
to you, since they know the routes because they told you the routes)

-chris

From prvs=0079baa316=johnl@iecc.com  Thu Jan  9 10:53:08 2014
Return-Path: <prvs=0079baa316=johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBED1AE0EE for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level: 
X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9BijDKTG02Fe for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:53:05 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id BEA711AE07A for <ietf@ietf.org>; Thu,  9 Jan 2014 10:53:04 -0800 (PST)
Received: (qmail 85312 invoked from network); 9 Jan 2014 18:46:13 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Jan 2014 18:46:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=52ceee74.xn--3zv.k1310; i=johnl@user.iecc.com; bh=82ulMKgXsK7mwa9XyD6zQKjxML6o0i5GTnDsad5Ipkw=; b=bgz8M+SN/g/zgVq31KWAv9lHTRZ1XkPHTcs4ln1Lg9ZDdgLSRGYsR8d2d4ZG8eZaCfoGdNcwvJsC6eNJqm+Vq69eSzhIijdbvsfdc1xCG1JmH8Kyay1X15znUUahoaAm733x6f1vpezBbL7+nEtc8AMgJ0q0XtO5w1FTAGcSC7urnTgSmE/ril6HuYEuisZBNnbbWbhZKByqmEUmcJUKDa86FxtDNLcUSIgqHRgqlMA6wgnIH3QA6FEpsXlGmaig
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; s=52ceee74.xn--3zv.k1310; olt=johnl@user.iecc.com; bh=82ulMKgXsK7mwa9XyD6zQKjxML6o0i5GTnDsad5Ipkw=; b=Dxa1LH4TJa68V7VA7m5yU2sk/qmUjD6MWDhEl7eaevyI9I9CNZ/hYY7v60OYDDZ6TnaND5EfhV44nmGL+X3xQ+I6komwKVKYD2mCj1z1bKfjOl06EsJqaenQfRsKcjVwuSZzguJKmAerHieVrPyDZX6RdCE31RvqB1RCOQl2LQ7Ds4IAX7PQxQaikkTsnbLM/cWstzfsKTzy++mvLyLGf7oZWwb+w8Se1m1MNk/JiAnhhbIOv90MwbTdQwKBTSLs
Date: 9 Jan 2014 18:45:50 -0000
Message-ID: <20140109184550.6121.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Multi-homed BCP38
In-Reply-To: <CAL9jLaZSOwAcsX8PQyS9PpE+EBT02pm27FAejxHhiHf=c2iUeg@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 18:53:08 -0000

>> It looks like the sites John talked to are multihomed, NOT doing
>> routing at their edge (??), and yet wanting to filter? I don't think
>
>that's not clear, from john's description at least.

I can ask (the meeting's not over yet) but I gather that these are
multihomed customers who don't do BGP.  The ISP knows what ranges it's
routing to the customer, but it doesn't know what ranges are routed to
the same customer by someone else.

R's,
John

From christopher.morrow@gmail.com  Thu Jan  9 10:57:29 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D261AE073 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uSl2udFBrD95 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 10:57:28 -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 517DA1ADBD7 for <ietf@ietf.org>; Thu,  9 Jan 2014 10:57:28 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id c6so2502552lan.14 for <ietf@ietf.org>; Thu, 09 Jan 2014 10:57:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YZDNBPQ1AVjTOnCQUdxXWPsp42AMzBSG4lzKhF2Ym9g=; b=FevVfSagV2DD32g3rwqIpsrv3f1JGFeYLw/a0axkWqlbEFkeWLYqCqvqSa3U2IokwW ce259g6dmULNug6iX2pdjX3cXJZ/CvB7hvc4kSwWQPBCKh1x2Bkj9UA+Q4Z+bBK4qkPD mZ0SnAHYf9Tqyw2w6zPBqWFvnb90ZMUhGkshb2asM9kd5j/6rL3axvo3Kg5phoLjS8vV 2oDRs9A5EO7S3C3+ErOXQ5zdGOvQcXgqjD8+ptwG6WjeICL05Deu/lswoZpCBt6BWHsQ Pcj+FtiLM0OJ4V7aa15/ncutM0Ay/Igf5r+zE4Mbmdg5oABUqJ6JRwPeNcIBcbed6YbL 6JKw==
MIME-Version: 1.0
X-Received: by 10.152.4.162 with SMTP id l2mr1945680lal.75.1389293838016; Thu, 09 Jan 2014 10:57:18 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.37.170 with HTTP; Thu, 9 Jan 2014 10:57:17 -0800 (PST)
In-Reply-To: <20140109184550.6121.qmail@joyce.lan>
References: <CAL9jLaZSOwAcsX8PQyS9PpE+EBT02pm27FAejxHhiHf=c2iUeg@mail.gmail.com> <20140109184550.6121.qmail@joyce.lan>
Date: Thu, 9 Jan 2014 13:57:17 -0500
X-Google-Sender-Auth: MLEXxF9dw4svLlIdBOPnRu6YlUY
Message-ID: <CAL9jLaZ84dPWNMbNPYzT-0E1MziZ+K4mh3U5EzAa8hz6j=1cKw@mail.gmail.com>
Subject: Re: Multi-homed BCP38
From: Christopher Morrow <morrowc.lists@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 18:57:30 -0000

On Thu, Jan 9, 2014 at 1:45 PM, John Levine <johnl@taugh.com> wrote:
>>> It looks like the sites John talked to are multihomed, NOT doing
>>> routing at their edge (??), and yet wanting to filter? I don't think
>>
>>that's not clear, from john's description at least.
>
> I can ask (the meeting's not over yet) but I gather that these are
> multihomed customers who don't do BGP.  The ISP knows what ranges it's
> routing to the customer, but it doesn't know what ranges are routed to
> the same customer by someone else.

if they don't do bgp .. .then you'd expect only static routing and
thus you know exactly what they ought to be sourcing.

There are pathological (aka: stupid) cases of multihomed to 2 isps,
getting static-routing of each isp's PA space on only that one ISP...
and default routing up both pipes... but really that's just broken and
dumb, so getting customers to fix this by filtering is a fine answer.

-chris

From prvs=0079a20b32=johnl@taugh.com  Thu Jan  9 11:00:36 2014
Return-Path: <prvs=0079a20b32=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAE371AE07A for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z-2EJca4KZ0H for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:00:35 -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 2A6DA1AE4B7 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:00:35 -0800 (PST)
Received: (qmail 87625 invoked from network); 9 Jan 2014 19:00:25 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 9 Jan 2014 19:00:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=10f22.52cef1c9.k1312; i=johnl%iecc.com@submit.iecc.com; bh=bXaCv8/TsHy1hn2aJRSIf/bK6caB/1LpPTRI7sv6NFM=; b=j20yBJPbGgmbcVqcEfe+tWPLUZLml4OA32XhZCQXDljT0g5oP9ByhHVDdTekDaif+os76imkCFSfFud8HpQ/NGZmRl3uMssMNWPuuaVinfCFuZdXW94VmtfdVblMELIx3MpvC2EaAIcI+T4lJiwsX0nkREQl0FHr6E08Z5vYDKLdBDwWBNxqUswPFW8Z97ntg4IQVO8V44uOBgsjI/b5aaE66jFvTeEgMLt2L6p1PnmVq1b6C3/OT+5YbGsSmGIi
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=10f22.52cef1c9.k1312; olt=johnl%iecc.com@submit.iecc.com; bh=bXaCv8/TsHy1hn2aJRSIf/bK6caB/1LpPTRI7sv6NFM=; b=JcdLBpjTWx+LDrYoAoyA6Fu+1o4Mm4lVGvdvrZd5z04Xhx3EHwAViF2zJP39Hb1avKyy/9K0f8RUeWwIp8e7XoChYC2i6U4Kg4iJcyUmmA4gtILJcvXaaDcP8ko+O9JrDT0hjf5CJ5+Qe+OhU2LQFUqYmWPe0+FvLFRvwtabBErLEisgS4haB51IhaxgoTJdvPMg0fRSECuTW1wVUvpslGS8Zleu9e8iKlYxYf8UcoaVR26nZm0Th3p6THTHmCCT
Received: from joyce.dhcp.intranet ([155.70.23.45]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 09 Jan 2014 19:00:24 -0000
Date: 9 Jan 2014 14:00:22 -0500
Message-ID: <alpine.BSF.2.00.1401091359170.13876@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Christopher Morrow" <morrowc.lists@gmail.com>
Subject: Re: Multi-homed BCP38
In-Reply-To: <CAL9jLaZ84dPWNMbNPYzT-0E1MziZ+K4mh3U5EzAa8hz6j=1cKw@mail.gmail.com>
References: <CAL9jLaZSOwAcsX8PQyS9PpE+EBT02pm27FAejxHhiHf=c2iUeg@mail.gmail.com> <20140109184550.6121.qmail@joyce.lan> <CAL9jLaZ84dPWNMbNPYzT-0E1MziZ+K4mh3U5EzAa8hz6j=1cKw@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:00:37 -0000

> There are pathological (aka: stupid) cases of multihomed to 2 isps,
> getting static-routing of each isp's PA space on only that one ISP...
> and default routing up both pipes... but really that's just broken and
> dumb, so getting customers to fix this by filtering is a fine answer.

As I said in the original message, calling the customers stupid is not 
useful.

They know they're doing asymmetrical routing, and they're paying the ISP a 
lot of money to do so.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

From christopher.morrow@gmail.com  Thu Jan  9 11:04:13 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3713C1AE058 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:04:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l_0NnzgfKfIF for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:04:11 -0800 (PST)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 824701ADFB2 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:04:11 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id eh20so278180lab.3 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:04:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=428gOPgCf1VnOyfoxDch6JiL+EaxZoCNH9GZGhZQXOA=; b=CQoH5AMgVTrS5IEtptRl83vllTyMJGxEgmsYgkMpEJd7VYJUQj0JJ7m6LpK3LR7+Wi SCKaFaUX+R6BxTvC5eI/3HhUhHepEx0ysnvhSaWTP0CHXzQL7CP1MJRWB438/VVrCcjU c9UMvesqExJxxtzyfQwQXxqIQOjGEsiX+q0Lh41D9B00JlSZ2Pcx0rhnsulsCkxCGDL/ S6UB5ITv7WnTBLGPenXk+fz4oeyuCOW4F48pp1iPmN4cmeDrhzm9CePS/F0xNMXSKl5u 19UmhsEevvh+724yAGlbuwWnMRyirnV/25m2/AT9gMZpdjTN9WaVWqJ0HPP4bLZ9E7t0 9t5w==
MIME-Version: 1.0
X-Received: by 10.112.148.104 with SMTP id tr8mr1947013lbb.42.1389294241014; Thu, 09 Jan 2014 11:04:01 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.37.170 with HTTP; Thu, 9 Jan 2014 11:04:00 -0800 (PST)
In-Reply-To: <alpine.BSF.2.00.1401091359170.13876@joyce.lan>
References: <CAL9jLaZSOwAcsX8PQyS9PpE+EBT02pm27FAejxHhiHf=c2iUeg@mail.gmail.com> <20140109184550.6121.qmail@joyce.lan> <CAL9jLaZ84dPWNMbNPYzT-0E1MziZ+K4mh3U5EzAa8hz6j=1cKw@mail.gmail.com> <alpine.BSF.2.00.1401091359170.13876@joyce.lan>
Date: Thu, 9 Jan 2014 14:04:00 -0500
X-Google-Sender-Auth: FtUmsz5pbW1lgegXC8FJ6dPok_c
Message-ID: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com>
Subject: Re: Multi-homed BCP38
From: Christopher Morrow <morrowc.lists@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:04:13 -0000

On Thu, Jan 9, 2014 at 2:00 PM, John R Levine <johnl@taugh.com> wrote:
>> There are pathological (aka: stupid) cases of multihomed to 2 isps,
>> getting static-routing of each isp's PA space on only that one ISP...
>> and default routing up both pipes... but really that's just broken and
>> dumb, so getting customers to fix this by filtering is a fine answer.
>
>
> As I said in the original message, calling the customers stupid is not
> useful.

right, my assumption is that some marketting/pr/customer-service
person would actually tell the customers a form of: "Hey, do you like
reliability? we do to... we also like cleaner internets, we're going
to filter outbound traffic from you for the sources we should  see
from you, currently that's: A/24 and B/24... if we should add more,
speak up by <60days from now>"

> They know they're doing asymmetrical routing, and they're paying the ISP a
> lot of money to do so.
>

sure, they are also paying for reliability and lack of problems with
the traffic they send, so making that part the star, not their
stupidty is probably the way forward.

>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.

From sm@resistor.net  Thu Jan  9 11:04:23 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B27431AE0E5 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:04:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uP2SJJOuE1H0 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:04: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 80C2F1AE102 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:04:21 -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 s09J42ew022916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Jan 2014 11:04:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389294249; bh=tuXHF9pTIOszihQakWaiabiDciAFb08JhjnG6/bhwo4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=G5xGIOjmxNULmBHaETT0apeA+sW/NGHHtb/1SRg4Ydd1MFovQ9Y043BMgaiRVHez+ Dfhk7vpzBy4jsV5CUHuaxH4FPvYbisAait88AppOXNMf5ibCLNLhn5Tow5LiXqYIVn B3a36fiLmCJM1oIou9mUrVkACOKAjRFT5ojgl4oE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1389294249; i=@resistor.net; bh=tuXHF9pTIOszihQakWaiabiDciAFb08JhjnG6/bhwo4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QRWfW+3R3CUU4524kaB+mo3DunNhklU65qvfh5iIYLjFoVjuk7Rv+KC2qU5uobiRr 2+TAtjgGHf6bULKsMT7ZLbf9VnzFjGwLeneLs9b8/ieAiDSh5x5KLLBMb1T8gRlZ85 GxFZ6fKOq3jq191v5FRXbfojgaWcDnafkqQPztGs=
Message-Id: <6.2.5.6.2.20140109103707.0b95b440@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 09 Jan 2014 10:59:35 -0800
To: Dave Cridland <dave@cridland.net>
From: SM <sm@resistor.net>
Subject: Re: Upcoming change to announcement email header fields (using old header)
In-Reply-To: <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.g mail.com>
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com> <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.gmail.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:04:23 -0000

Hi Dave,
At 09:39 09-01-2014, Dave Cridland wrote:
>Much as I adore the almost wonderful irony of "The IESG" having an 
>address of <noreply@ietf.org> - especially in the light of John's 
>closing comment there - many MUAs will then cheerfully offer that as 
>an address for "The IESG".

:-)

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

>If that is a dev-null address, as noreply@ often implies, it'll 
>become a self-fulfilling prophecy of sorts. You might want a 
>different phrase, there - "IESG Announcements", or something.

My guess about the problem is that people choose "Reply to 
All".  That generates more mail for iesg-secretary@.  Using a few 
(sieve) rules might alleviate the problem.

Regards,
-sm 


From andy@yumaworks.com  Thu Jan  9 11:05:29 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF1AF1AE4C5 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:05:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KRQEg_QF_uyX for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:05:26 -0800 (PST)
Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5061AE4C1 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:05:23 -0800 (PST)
Received: by mail-qa0-f48.google.com with SMTP id i13so3124449qae.21 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:05:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=9jqPM8SiHHWIyMZcwRJkrKbpOakxR7MFy9C5p092R/8=; b=cPvm/8GXt8k7Di96WTn5Gazzz7xNFEGmK7SQzFL6JhG290lEYiSP70NVYNSVxNa3FZ dipb9zHWfmG+Kvph5JGqAdvgcd3AOXuzSv98BeGKpyOZLRi6kyPGvGXv1rK1Nb4T6CyT /rwMrOLa2BMHoTmfvF4VF9yF+tYk/ddKbBWYYlxTLzOM1DYSp63Yei+dpRTLQ8GgsMER Sw6Rfy2U9XK6LSQX0zABG+mgpZeOvwfS1vGUBteLatDqQ1zdvvt9CKaWRZgaj5WA491D 1l4vdkvOAo0DFUBuOBxDIZizxuPP/xFqBzZ32WsfTQtbahCGhNqhVwYK9Vr9p7eyANKb QCAw==
X-Gm-Message-State: ALoCoQmkCZgVMR8M8vOSGR+ZEa/802usb+wiU8z+DTnxntQrMlGmv5QWnrKlMamEDVRk0XZe5FtU
MIME-Version: 1.0
X-Received: by 10.49.84.105 with SMTP id x9mr10557787qey.65.1389294313332; Thu, 09 Jan 2014 11:05:13 -0800 (PST)
Received: by 10.140.48.75 with HTTP; Thu, 9 Jan 2014 11:05:13 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140109051548.0a951040@resistor.net>
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com> <6.2.5.6.2.20140108233958.0a849e58@resistor.net> <20140109105804.GA44893@elstar.local> <6.2.5.6.2.20140109051548.0a951040@resistor.net>
Date: Thu, 9 Jan 2014 11:05:13 -0800
Message-ID: <CABCOCHTF4=zhwd25TWxh1pM8h_Tw2==WehDHuJaPPYMm3XWVUg@mail.gmail.com>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
From: Andy Bierman <andy@yumaworks.com>
To: SM <sm@resistor.net>
Content-Type: multipart/alternative; boundary=047d7bdc0ef00910c904ef8e4a86
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, IETF discussion list <ietf@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:05:29 -0000

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

Hi,

On Thu, Jan 9, 2014 at 7:47 AM, SM <sm@resistor.net> wrote:

> Hi Juergen,
> At 02:58 09-01-2014, Juergen Schoenwaelder wrote:
>
>> People want to be able to configure timezones using the timezone
>> naming scheme commonly supported by operating systems (e.g.,
>> Europe/Paris). This document defines a serialization of the timezone
>> names into YANG format for this purpose. I believe there was indeed
>> strong concensus on this in the WG.
>>
>
> There was a message about a quick poll [1] to adopt
> draft-lange-netmod-iana-timezones-01 on 2 July, 2012.  Three persons
> expressed their support and the WG Chair expressed his support as a
> technical contributor [2]; there weren't any message objecting to adoption.
>  There were two comments [3][4] on 30 July, 2012.  There was a WG Last Call
> announcement [5] and two reminders [6][7] about it. There was a message [8]
> on 12 November, 2013 from a WG participant (I am not taking into account
> the message from the author and one of the WG Chairs).  My comment about
> the determination of consensus being questionable is based on the messages
> in the NETMOD mailing list archive.
>
>  This document aims at establishing an IANA maintained serialization of
>> whatever list of names the timezone database contains. It does not
>> change the way the TZ coordinator, an IANA Designated Expert, takes
>> decisions. Perhaps this needs to be stated more explicit.
>>
>
> There is a thread at http://mm.icann.org/pipermail/tz/2012-May/017711.html The problem is not changing the way things are done.  I would describe the
> current TZ approach as keeping the TZ information up-to-date by posting a
> (software) release every now and then.  It works for me.
>
>  So far (in the MIB world), the initial versions of IANA maintained
>> modules were published as Proposed Standards on the standards track
>> (although the only thing that really remains valid over time are the
>> IANA considerations, which however often require the initial module to
>> be available). We simply followed this practice.
>>
>
> If I understood correctly the YANG module defined in the draft creates
> IANA-registered timezones based on public domain [9] information about
> timezones.  IANA is then asked to keep the IANA-registered timezones
> up-to-date.  That sounds okay if the politics about time are not taken into
> consideration [10][11][12].
>
>  There was concensus in the WG that it is desirable to configure
>> timezones by name (e.g., Europe/Paris) instead of having only hard
>> coded UTC offsets - the benefits should be obvious.
>>
>
> I agree that there can be benefits to that approach.  I could not find the
> (mailing list) message where that WG decision was taken.
>
>
After reading the IANA Considerations section closer, I have some concerns
about the use of a YANG enumeration. This section does not say who must
update the enumeration typedef and republish the RFC containing the new
YANG module, every time the TZ database is changed.
Is it the NETMOD WG? IANA?

This may not be a practical long-term solution.
The purpose of a YANG enumeration type is to allow a well-constrained
value set that can be machine-validated.  If the data type was a string
instead of an enumeration, there would be no IANA coupling or republishing
(or YANG-based machine validation). The description-stmt can say a leaf
using this data type MUST match a value in the TZ database.

The draft (sec. 3.1) also says to change the status of the old enum to
obsolete
and add a new enum, in order to change the name.  YANG definitions are
supposed to transition from current to deprecated, not current to obsolete.



> Regards,
> -sm
>


Andy


>
> 1. http://www.ietf.org/mail-archive/web/netmod/current/msg06810.html
> 2. http://www.ietf.org/mail-archive/web/netmod/current/msg06841.html
> 3. http://www.ietf.org/mail-archive/web/netmod/current/msg06932.html
> 4. http://www.ietf.org/mail-archive/web/netmod/current/msg06933.html
> 5. http://www.ietf.org/mail-archive/web/netmod/current/msg08327.html
> 6. http://www.ietf.org/mail-archive/web/netmod/current/msg08333.html
> 7. http://www.ietf.org/mail-archive/web/netmod/current/msg08335.html
> 8. http://www.ietf.org/mail-archive/web/netmod/current/msg08694.html
> 9. ftp://ftp.iana.org/tz/tz-link.html
> 10. http://www.theguardian.com/news/datablog/2013/sep/26/
> spain-countries-wrong-time-zone
> 11. http://972mag.com/the-worlds-only-ethnic-time-zone/81006/
> 12. http://www.theblaze.com/stories/2013/09/22/just-wait-
> until-you-see-how-apples-new-operating-system-lists-jerusalem/
>

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

<div dir=3D"ltr">Hi,<br><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Thu, Jan 9, 2014 at 7:47 AM, SM <span dir=3D"ltr">&lt;<a href=3D"=
mailto:sm@resistor.net" target=3D"_blank">sm@resistor.net</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
Hi Juergen,<br>
At 02:58 09-01-2014, Juergen Schoenwaelder wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
People want to be able to configure timezones using the timezone<br>
naming scheme commonly supported by operating systems (e.g.,<br>
Europe/Paris). This document defines a serialization of the timezone<br>
names into YANG format for this purpose. I believe there was indeed<br>
strong concensus on this in the WG.<br>
</blockquote>
<br>
There was a message about a quick poll [1] to adopt draft-lange-netmod-iana=
-<u></u>timezones-01 on 2 July, 2012. =A0Three persons expressed their supp=
ort and the WG Chair expressed his support as a technical contributor [2]; =
there weren&#39;t any message objecting to adoption. =A0There were two comm=
ents [3][4] on 30 July, 2012. =A0There was a WG Last Call announcement [5] =
and two reminders [6][7] about it. There was a message [8] on 12 November, =
2013 from a WG participant (I am not taking into account the message from t=
he author and one of the WG Chairs). =A0My comment about the determination =
of consensus being questionable is based on the messages in the NETMOD mail=
ing list archive.<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
This document aims at establishing an IANA maintained serialization of<br>
whatever list of names the timezone database contains. It does not<br>
change the way the TZ coordinator, an IANA Designated Expert, takes<br>
decisions. Perhaps this needs to be stated more explicit.<br>
</blockquote>
<br>
There is a thread at <a href=3D"http://mm.icann.org/pipermail/tz/2012-May/0=
17711.html" target=3D"_blank">http://mm.icann.org/pipermail/<u></u>tz/2012-=
May/017711.html</a> =A0The problem is not changing the way things are done.=
 =A0I would describe the current TZ approach as keeping the TZ information =
up-to-date by posting a (software) release every now and then. =A0It works =
for me.<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
So far (in the MIB world), the initial versions of IANA maintained<br>
modules were published as Proposed Standards on the standards track<br>
(although the only thing that really remains valid over time are the<br>
IANA considerations, which however often require the initial module to<br>
be available). We simply followed this practice.<br>
</blockquote>
<br>
If I understood correctly the YANG module defined in the draft creates IANA=
-registered timezones based on public domain [9] information about timezone=
s. =A0IANA is then asked to keep the IANA-registered timezones up-to-date. =
=A0That sounds okay if the politics about time are not taken into considera=
tion [10][11][12].<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
There was concensus in the WG that it is desirable to configure<br>
timezones by name (e.g., Europe/Paris) instead of having only hard<br>
coded UTC offsets - the benefits should be obvious.<br>
</blockquote>
<br>
I agree that there can be benefits to that approach. =A0I could not find th=
e (mailing list) message where that WG decision was taken.<br>
<br></blockquote><div><br></div><div>After reading the IANA Considerations =
section closer, I have some concerns</div><div>about the use of a YANG enum=
eration. This section does not say who must</div><div>update the enumeratio=
n typedef and republish the RFC containing the new</div>
<div>YANG module, every time the TZ database is changed.</div><div>Is it th=
e NETMOD WG? IANA?</div><div><br></div><div>This may not be a practical lon=
g-term solution.</div><div>The purpose of a YANG enumeration type is to all=
ow a well-constrained</div>
<div>value set that can be machine-validated. =A0If the data type was a str=
ing</div><div>instead of an enumeration, there would be no IANA coupling or=
 republishing</div><div>(or YANG-based machine validation). The description=
-stmt can say a leaf</div>
<div>using this data type MUST match a value in the TZ database.</div><div>=
<br></div><div>The draft (sec. 3.1) also says to change the status of the o=
ld enum to obsolete</div><div>and add a new enum, in order to change the na=
me. =A0YANG definitions are</div>
<div>supposed to transition from current to deprecated, not current to obso=
lete.</div><div><br></div><div>=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards,<br>
-sm<br></blockquote><div><br></div><div><br></div><div>Andy</div><div>=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<br>
1. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg06810.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg06810.html</a><br>
2. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg06841.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg06841.html</a><br>
3. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg06932.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg06932.html</a><br>
4. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg06933.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg06933.html</a><br>
5. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg08327.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg08327.html</a><br>
6. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg08333.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg08333.html</a><br>
7. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg08335.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg08335.html</a><br>
8. <a href=3D"http://www.ietf.org/mail-archive/web/netmod/current/msg08694.=
html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/netmod/=
current/<u></u>msg08694.html</a><br>
9. <a href=3D"ftp://ftp.iana.org/tz/tz-link.html" target=3D"_blank">ftp://f=
tp.iana.org/tz/tz-link.<u></u>html</a><br>
10. <a href=3D"http://www.theguardian.com/news/datablog/2013/sep/26/spain-c=
ountries-wrong-time-zone" target=3D"_blank">http://www.theguardian.com/<u><=
/u>news/datablog/2013/sep/26/<u></u>spain-countries-wrong-time-<u></u>zone<=
/a><br>

11. <a href=3D"http://972mag.com/the-worlds-only-ethnic-time-zone/81006/" t=
arget=3D"_blank">http://972mag.com/the-worlds-<u></u>only-ethnic-time-zone/=
81006/</a><br>
12. <a href=3D"http://www.theblaze.com/stories/2013/09/22/just-wait-until-y=
ou-see-how-apples-new-operating-system-lists-jerusalem/" target=3D"_blank">=
http://www.theblaze.com/<u></u>stories/2013/09/22/just-wait-<u></u>until-yo=
u-see-how-apples-new-<u></u>operating-system-lists-<u></u>jerusalem/</a> <b=
r>

</blockquote></div><br></div></div>

--047d7bdc0ef00910c904ef8e4a86--

From brian.e.carpenter@gmail.com  Thu Jan  9 11:13:47 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E20A21ADFB2 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:13:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0FFSG6Q79LUy for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:13:46 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0361AE005 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:13:46 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id kq14so3681606pab.34 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:13:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IL2PsBQkGvqe52h2FaNovcmNUA7gVggGrTcXaR1JG9Q=; b=mQ4wRx0R1vnPbKj56umVPiARJnnBnihkFcCNheCaCKsAec5/XTC7K1PviMaqS1nYvK yzgpobsvgGZtKcvButkfagXb/7hweVY+pUnGQe5BTbX4GC2kFpyRzjg89L+URwiJ/SJ7 dEmZdWNoIJdo5G4ka6EWrSxnFpcIIOBEKsuLDm6wVzLRNRmAuwESWdWX3hBhtJBQmDd3 0NZDWdGf4piV4XRoaubwpsA2Xo6layLhuU7jxgWq4VHTRxYHdzFarkhLEqVr/pILoaRT rU5x8C8ZvQo9e0YhamuoSwKClQwlOOjtlvAhU1LSe1R4KuqX6jjU35OjAFI/mUyfSVEQ DfWA==
X-Received: by 10.68.211.102 with SMTP id nb6mr5712301pbc.39.1389294816865; Thu, 09 Jan 2014 11:13:36 -0800 (PST)
Received: from [192.168.178.21] (164.199.69.111.dynamic.snap.net.nz. [111.69.199.164]) by mx.google.com with ESMTPSA id ns7sm1542415pbc.32.2014.01.09.11.13.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 11:13:36 -0800 (PST)
Message-ID: <52CEF4E9.1070505@gmail.com>
Date: Fri, 10 Jan 2014 08:13:45 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com>
In-Reply-To: <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:13:48 -0000

> Working out a timeline to complete an effort to make all of this work is left as an exercise to the reader

Since it's an infinite regression (any N namespaces can be converted to a single
namespace by adding N unique suffixes or prefixes) I think the timescale
is infinite.

Seriously. We have a perfectly fine unambiguous namespace. Enough already.

   Brian

From prvs=0079baa316=johnl@iecc.com  Thu Jan  9 11:18:21 2014
Return-Path: <prvs=0079baa316=johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D21A71AE072 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level: 
X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PlomUEyMe1ZL for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:18:20 -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 4A3461ADFB2 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:18:20 -0800 (PST)
Received: (qmail 91009 invoked from network); 9 Jan 2014 19:18:10 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 9 Jan 2014 19:18:10 -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; s=52cef5f1.xn--yuvv84g.k1310; i=johnl@user.iecc.com; bh=msU43eJmwI40jLCSjWM7TwLTSscWN7EifjU4A+fFHf8=; b=ack8ULYexrLdHpGRqnZo1TVf1CY/TlSLiCFjN04gvykeMReUMz1ZRkO2xzX2KoICS7HmhIBoHaAoGKcjrSs2Qqu5UndkO/Ixjnk70cOFpAMksMXds7f1SY9eMa80+8kGhwz0MwbYfkxaj9peORE8S/UHaYfsDudbTTXLdlKny/ApFH4xPRdcblpgSHvYqBMuvZYXRWPuX1D533qTxpLWPXnNQjgU0nJvk7HX8aapLFbSQBGN3u7fT/1Z3xqH/h4z
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; s=52cef5f1.xn--yuvv84g.k1310; olt=johnl@user.iecc.com; bh=msU43eJmwI40jLCSjWM7TwLTSscWN7EifjU4A+fFHf8=; b=FXKqM756CVXxzwmFfbzc+Hyfc+NL42yKF6VHxca2sIjwnDYtzMDanN/fonmNW+tLxp5GhMzARYr17EEahSH7Bb7oRcGVZbYAjISN7ToVxSU4lIRnwkgr1GjXG22Te0gmEYAKEWEsURwG1d5czBEw/918AJFW0MeX5y26/tlez/G1g9Zp3p1b6g0Nri953ND1r3SMyHyGZAhqJ/GqRxxoRzIRetjOlNa3IFD1OJoiQuS03KlMhRx0+drpDylwUM1e
Date: 9 Jan 2014 19:17:47 -0000
Message-ID: <20140109191747.20009.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Multi-homed BCP38
In-Reply-To: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:18:22 -0000

>right, my assumption is that some marketting/pr/customer-service
>person would actually tell the customers a form of: "Hey, do you like
>reliability? we do to... we also like cleaner internets, we're going
>to filter outbound traffic from you for the sources we should  see
>from you, currently that's: A/24 and B/24... if we should add more,
>speak up by <60days from now>"

The ISP says the customer responds "if you're not willing to handle
our 20 gigabit account, we're sure we can find someone else who can."

Also, if you'll review the messages to which you're responding, you'll
note that the customer is often an ISP with customers of its own so
there are far too many ranges to handle manually.

R's,
John

From christopher.morrow@gmail.com  Thu Jan  9 11:21:13 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6328D1AE456 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:21:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XD6ttdO4obIX for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:21:12 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id ADD9D1AE41B for <ietf@ietf.org>; Thu,  9 Jan 2014 11:21:11 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id b8so781874lan.19 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:21:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=z8SwCwZagI5a1L2nwnunMqOTiXBc/XJ6hO/cDgd0T3g=; b=oqDuMf4PTQP9G5lrVrUM1ihkvEWDeAEL/Dz3PzlvBaPEESYyKKwk9rl6atNqyaByiV lmYtvkH2x6X0BZax24chxCZMb3WfJBr8mman+TxgZ/iJagE0cctnOJ+zgvRl6Ycvjzij ELRgYy8t2hS3m9uX86UD0RtI8CjWFU66Xgh8DTWfgSUzgotebxsJvJr3mlZD5g/XFlLc 8YuQrpliacuJLyjGWAhjEYciNF69a4gozZn0qS3yLCItAyzEABhsfKMbA7puCU1cnxJi uWT7Ja7uXW3aCNF2zg4cyTQ4CBTw1+9rsJXEfZfprDCPAG8M+k0xs9LLgXouAvJBV3ds 5uTw==
MIME-Version: 1.0
X-Received: by 10.112.159.132 with SMTP id xc4mr1939789lbb.62.1389295261405; Thu, 09 Jan 2014 11:21:01 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.37.170 with HTTP; Thu, 9 Jan 2014 11:21:01 -0800 (PST)
In-Reply-To: <20140109191747.20009.qmail@joyce.lan>
References: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com> <20140109191747.20009.qmail@joyce.lan>
Date: Thu, 9 Jan 2014 14:21:01 -0500
X-Google-Sender-Auth: vNu2arwdzQ7MUMJbjyvBQM85B5o
Message-ID: <CAL9jLaZVsAKhT0hc-5PvR_BzYrBzPUZPCz3qSgU8f31K08tT8w@mail.gmail.com>
Subject: Re: Multi-homed BCP38
From: Christopher Morrow <morrowc.lists@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:21:13 -0000

On Thu, Jan 9, 2014 at 2:17 PM, John Levine <johnl@taugh.com> wrote:
>>right, my assumption is that some marketting/pr/customer-service
>>person would actually tell the customers a form of: "Hey, do you like
>>reliability? we do to... we also like cleaner internets, we're going
>>to filter outbound traffic from you for the sources we should  see
>>from you, currently that's: A/24 and B/24... if we should add more,
>>speak up by <60days from now>"
>
> The ISP says the customer responds "if you're not willing to handle
> our 20 gigabit account, we're sure we can find someone else who can."
>
> Also, if you'll review the messages to which you're responding, you'll
> note that the customer is often an ISP with customers of its own so
> there are far too many ranges to handle manually.

yup, as I said, for the case of ISP to ISP (at a point) it's pretty
hard to keep the filtering proper/reliable, so I'd pass on most of
that.

for static customers though, it's pretty simple and for them and their
isp to sort this out.

-chris

From brian.e.carpenter@gmail.com  Thu Jan  9 11:30:59 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8CC1AE0BF for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:30:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w0Iefa2DR2-M for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:30:57 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 48F7A1AE0B4 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:30:57 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id q10so3591692pdj.11 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:30:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=47pXPNuwA8Bj7OV0ACx7JaKG25vgVaooZ9BuJjHjgRo=; b=THvEzNPWftJQPIFbwejIxugUV/24BpXS/zHuLKlFetQWK8ZBkXHKdM2tHXqvWxyNdk BJ3jGIamM8uqyJdNoW1UyZBvihyVXCaceX5yl4rzB7x1eXJSOw+kmKp0sGpbAzfCYtGf QB/6g9DMSXy/dSzlHjtPjc+gYpBj65crGCqg0qaCTBoXVryt3en9QhzVdAmchNBfy8AW oOJkomHigPIx2XjG9XAvXRNhMMVd7WHBc6NP+7y5TugA5a7vOJoGjU45MA7I7DNpEkU6 SdR53YoBK8mMpbFM+1da+w2ccVk/p3cJX4a5gtAwqjzeulCC3aYD4ys7WTzwmyB/lqFC 0ojA==
X-Received: by 10.68.143.231 with SMTP id sh7mr5831706pbb.7.1389295847793; Thu, 09 Jan 2014 11:30:47 -0800 (PST)
Received: from [192.168.178.21] (164.199.69.111.dynamic.snap.net.nz. [111.69.199.164]) by mx.google.com with ESMTPSA id de1sm11917848pbc.7.2014.01.09.11.30.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 11:30:46 -0800 (PST)
Message-ID: <52CEF8EF.3040102@gmail.com>
Date: Fri, 10 Jan 2014 08:30:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Multi-homed BCP38
References: <20140109184550.6121.qmail@joyce.lan>
In-Reply-To: <20140109184550.6121.qmail@joyce.lan>
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:30:59 -0000

On 10/01/2014 07:45, John Levine wrote:
>>> It looks like the sites John talked to are multihomed, NOT doing
>>> routing at their edge (??), and yet wanting to filter? I don't think
>> that's not clear, from john's description at least.
> 
> I can ask (the meeting's not over yet) but I gather that these are
> multihomed customers who don't do BGP.  The ISP knows what ranges it's
> routing to the customer, but it doesn't know what ranges are routed to
> the same customer by someone else.

This is not a new problem; we certainly discussed it in the multi6 WG
ten years ago:
http://tools.ietf.org/html/draft-huitema-multi6-ingress-filtering-00

Actually it's one of the reasons that multi6 led to shim6, which mainly
avoids this problem (but is disliked by ISPs for other reasons).

    Brian

From joelja@bogus.com  Thu Jan  9 11:35:40 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA8F1AE0B4 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8jZIviHzDpAg for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:35:38 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 15ABF1AE09C for <ietf@ietf.org>; Thu,  9 Jan 2014 11:35:38 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s09JZRZ5068049 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 9 Jan 2014 19:35:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <52CEF9FA.1000504@bogus.com>
Date: Thu, 09 Jan 2014 11:35:22 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
Subject: Re: Multi-homed BCP38
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lvNpG2STXVUvq6EuRfxfrJu0M2o3tamSQ"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Thu, 09 Jan 2014 19:35:28 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:35:40 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--lvNpG2STXVUvq6EuRfxfrJu0M2o3tamSQ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On 1/9/14, 7:09 AM, John R Levine wrote:
> I was at a meeting talking to ops people from some large ISPs, who tell=

> me that when they tell their large customers about BCP 38, the customer=
s
> say forget it, because they're multihomed.  I gather the situation is
> typically that the customer has multiple address ranges, say from
> providers A and B.  Normally traffic from range A goes out through
> provider A, and vice-versa, except sometimes when it doesn't.  Sometime=
s
> it's failover, or it may be deliberate asymmetic routing.  The customer=
s
> may not be running BGP, or if they do, they don't want to announce rang=
e
> A to provider B for business reasons I don't entirely understand but
> that are not going away.
>=20
> The ISPs tell me that the customers are often ISPs themselves, so there=

> are lots of address ranges, far more than anyone could track manually
> even if they wanted to.
>=20
> I see BCP 84, which is now ten years old.  The ISPs are aware of it, bu=
t
> it doesn't seem to have done the trick.  I can think of some hacks to
> pseudo-announce ranges for filtering purposes, but surely I am not the
> only person to have noticed this problem.  What have people done to
> address this issue?*  I figure the first thing to do is to understand
> what's failed before.

Peers the do URPF strict, and also having regionally distinct prefix
range advertisements (e.g. we peer in multiple regions) for peers  are a
problem e.g. due to internal issues traffic that was flowing through a
port where the prefix was announced is now flowing towards me through a
port which it is not, likewise in the other direction, in a case where
the out of region prefix would due to local pref be reached via a
transit provider, if the transit route goes away  may well blackhole at
the other peer if it instead crosses your backbone to another exit. We
use loose to prevent this in the inboud direction with those peers  we
also announce covering agregates to particular URPF strict peer.


> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
>=20
> * - other than calling the customers stupid, which they are not, and is=

> not helpful
>=20



--lvNpG2STXVUvq6EuRfxfrJu0M2o3tamSQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLO+foACgkQ8AA1q7Z/VrJMJACfUl45DzCg5b6aHAgDaEwVWMd7
rkAAnR2GQIexzSX0gymYR0hu8gIkVwQW
=l+IU
-----END PGP SIGNATURE-----

--lvNpG2STXVUvq6EuRfxfrJu0M2o3tamSQ--

From drc@virtualized.org  Thu Jan  9 11:41:09 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40581AE542 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yAclPcVBtzl8 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:41:08 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id EA53A1AE541 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:41:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 0B3C284B42; Thu,  9 Jan 2014 14:40:55 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 28278-04; Thu,  9 Jan 2014 14:40:54 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 29DC78445C; Thu,  9 Jan 2014 14:40:53 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_282946E1-63F1-446F-AE57-C72AE4EBC395"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
From: David Conrad <drc@virtualized.org>
In-Reply-To: <52CEF4E9.1070505@gmail.com>
Date: Thu, 9 Jan 2014 11:40:52 -0800
Message-Id: <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com> <52CEF4E9.1070505@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:41:09 -0000

--Apple-Mail=_282946E1-63F1-446F-AE57-C72AE4EBC395
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jan 9, 2014, at 11:13 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> Working out a timeline to complete an effort to make all of this work =
is left as an exercise to the reader
>=20
> Since it's an infinite regression (any N namespaces can be converted =
to a single
> namespace by adding N unique suffixes or prefixes) I think the =
timescale
> is infinite.
>=20
> Seriously. We have a perfectly fine unambiguous namespace. Enough =
already.

The problem is that this issue keeps repeating, particularly in (shall =
we say) non-technical venues. In a private message I semi-seriously =
suggested someone should write an RFC that deprecates classes other than =
IN.  However, I'm beginning to think this might not be that bad of an =
idea -- at least there would be a document that the non-technical folks =
who keep raising the issue could be pointed at...

Regards,
-drc


--Apple-Mail=_282946E1-63F1-446F-AE57-C72AE4EBC395
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJSzvtEAAoJENV6ebf0/4rXj9YH/2g6lllt0fDkhEzeXdfk7XwR
m4FYWEThbFY8fSuVQhfEsL8suMyt80Pj613LwStXsiapO5GAPCPOUsbWCi5Y+LKa
Sff7oYaB+DZR1NZ3bdrI/aseCSztAEq8yrckGj9bWsO4TundBkWm2e9VSwFg7eu6
cLTssqdZYkvPNbq7RTFI5o1SS3urVLz1StikUT04Uu67iKH3YWpJr//WbwZabqmp
wDQXEW4C9BbHutWJUiiZJr+4saSbx4QIane1io3it/bC8nrMmpaWmCO04f/653Vv
RG8V1dsOgaRmcO/ZayS5TxkKLRAgt5AVrE5e1NmYOutSchCp8TgEucB5WNmjWMc=
=5TtK
-----END PGP SIGNATURE-----

--Apple-Mail=_282946E1-63F1-446F-AE57-C72AE4EBC395--

From fred@cisco.com  Thu Jan  9 11:55:48 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF5A1AE408 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.039
X-Spam-Level: 
X-Spam-Status: No, score=-115.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhzgwqYH5xwj for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 11:55:46 -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 71DFB1AE3D5 for <ietf@ietf.org>; Thu,  9 Jan 2014 11:55:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2790; q=dns/txt; s=iport; t=1389297337; x=1390506937; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=2LrFgdndKEExpycyLFSxvrp+v3skBEHkj3BwynErPnM=; b=Z5ncY09sj0kB73Ab2/xgXAY6zAGjpizKONyUj+T1Kv1i39OH8uIR5Sca 9gJzU8LmME52zYEDSpm5Vm0TcFGBVltStkWR5pJKBIMiCWlq4rnkReM04 vP2ELhz5nEFIt1vSgP5B9hFTXdyX22R7vX8XKbiTCTAcGPJ717weJTYmB A=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjEFABX+zlKtJV2b/2dsb2JhbABZgws4VqBfBwGYWoEUFnSCJQEBAQMBeQULAgEIRjIlAgQOBQ6HbggNvH0BhgYXjwUHgySBEwSQM4ExhjOBMJBlgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,633,1384300800";  d="asc'?scan'208";a="296345627"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP; 09 Jan 2014 19:55:36 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s09JtakC029228 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 9 Jan 2014 19:55:36 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.86]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0123.003; Thu, 9 Jan 2014 13:55:36 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: John R Levine <johnl@taugh.com>
Subject: Re: Multi-homed BCP38
Thread-Topic: Multi-homed BCP38
Thread-Index: AQHPDUzosHm2Io2q+0midFiC3JbkZpp9M4CA
Date: Thu, 9 Jan 2014 19:55:36 +0000
Message-ID: <A6DD18F1-0C5B-4142-AF62-936C36D7378B@cisco.com>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1401090943270.929@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.156.48.192]
Content-Type: multipart/signed; boundary="Apple-Mail=_D2B28EED-3A28-404E-9E25-B8B8D7C9B866"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 19:55:48 -0000

--Apple-Mail=_D2B28EED-3A28-404E-9E25-B8B8D7C9B866
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jan 9, 2014, at 7:09 AM, John R Levine <johnl@taugh.com> wrote:

> I was at a meeting talking to ops people from some large ISPs, who =
tell me that when they tell their large customers about BCP 38, the =
customers say forget it, because they're multihomed.  I gather the =
situation is typically that the customer has multiple address ranges, =
say from providers A and B.  Normally traffic from range A goes out =
through provider A, and vice-versa, except sometimes when it doesn't.  =
Sometimes it's failover, or it may be deliberate asymmetic routing.  The =
customers may not be running BGP, or if they do, they don't want to =
announce range A to provider B for business reasons I don't entirely =
understand but that are not going away.
>=20
> The ISPs tell me that the customers are often ISPs themselves, so =
there are lots of address ranges, far more than anyone could track =
manually even if they wanted to.
>=20
> I see BCP 84, which is now ten years old.  The ISPs are aware of it, =
but it doesn't seem to have done the trick.  I can think of some hacks =
to pseudo-announce ranges for filtering purposes, but surely I am not =
the only person to have noticed this problem.  What have people done to =
address this issue?*  I figure the first thing to do is to understand =
what's failed before.

There are some drafts you may find interesting:

http://tools.ietf.org/html/draft-boutier-homenet-source-specific-routing
http://tools.ietf.org/html/draft-troan-homenet-sadr
http://tools.ietf.org/html/draft-baker-ipv6-isis-dst-src-routing
http://tools.ietf.org/html/draft-baker-ipv6-ospf-dst-src-routing
http://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
http://tools.ietf.org/html/draft-xu-homenet-traffic-class
http://tools.ietf.org/html/draft-xu-homenet-twod-ip-routing

Homenet has been looking at this from the perspective of egress routing =
in residential multihoming. I have been looking at it more from =
source/destination routing in OSPF/IS-IS, for which "egress routing" and =
"residential multihoming" are special cases.

--Apple-Mail=_D2B28EED-3A28-404E-9E25-B8B8D7C9B866
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFSzv63bjEdbHIsm0MRAnDQAKCo1m5LpAaUT91ZiVTMWDv0N8EWmgCfXlSM
brWwo6GOvQp1ezkChBvGFjE=
=IZbl
-----END PGP SIGNATURE-----

--Apple-Mail=_D2B28EED-3A28-404E-9E25-B8B8D7C9B866--

From paf@frobbit.se  Thu Jan  9 12:04:33 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D71BB1AE11C for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 12:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xbvZlUqbtKHg for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 12:04:33 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id DFCA31AE0C9 for <ietf@ietf.org>; Thu,  9 Jan 2014 12:04:32 -0800 (PST)
Received: from [192.168.1.27] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id AF64B20652; Thu,  9 Jan 2014 21:04:22 +0100 (CET)
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se> <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A57A7E3-D807-4F4B-A10E-70A6F46B2365@frobbit.se>
X-Mailer: iPad Mail (11B554a)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
Subject: Re: Multi-homed BCP38
Date: Thu, 9 Jan 2014 21:04:23 +0100
To: Scott Brim <scott.brim@gmail.com>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 20:04:34 -0000

> On 9 jan 2014, at 17:52, Scott Brim <scott.brim@gmail.com> wrote:
>=20
> Where is "the edge"? Is there a boundary outside of your control that
> you truly trust? Even if there's supposedly unbreakable filtering at
> most of the edge, wouldn't you want to do your own filtering as well?
>=20
> It looks like the sites John talked to are multihomed, NOT doing
> routing at their edge (??), and yet wanting to filter? I don't think
> you get all three of those.

Oh, boy, why do I try to explain what I have in my head... ;-)

I agree that is a problem, but those people being multi homed should filter,=
 and, that should be included in contracts, enforced etc. However you as ups=
tream detect filtering is not happening.

I thought the main difference had to be with the difference between edge of y=
our AS and nodes that really are only single homed, where the latter should h=
ave filter on their upstream.

Anyway, I just wanted to point out the SSAC document, and let others interpr=
et.

   Patrik


From agmalis@gmail.com  Thu Jan  9 12:12:50 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5CF1AE049; Thu,  9 Jan 2014 12:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqN6D8ojfnmc; Thu,  9 Jan 2014 12:12:47 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D37071AE10B; Thu,  9 Jan 2014 12:12:46 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k4so808264qaq.15 for <multiple recipients>; Thu, 09 Jan 2014 12:12:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LX/HdHP0vU4UfmPFt9sL8qmvL7+dWijc3NcyMBigIq0=; b=GJkU5aztNSdOByof9ww/pNN0+ndJZVX2SbcKG2xcqv/mRlQswQaYiehnqeW8bZ6IxB Dhj2dJ59Ut7RXDW5pw2+4YoYjLPivWqCV3EPwBQlpK22wiD8J2l9RQ4MPd1PbwTm4z+Y exALqeeveVSTv5Ad1u0r51Aud3+tzRK1y8nzwFtyL+MHTEkXJQQ+T7saAuLDBkMjFBxV Gf2YnEEHAy/wxsHDTwTYJ9lUpimIi5+hiV4Cq10V+SaFv3Zd1jUcsVkHzEdCzSv9+5BN ast+lwlMZD5/G9Hwm5rQBecYfkRZw8s5S4GeVXXJz9CalhLSIACWclOjNaD2yj/1RVQ3 f5cg==
X-Received: by 10.224.72.81 with SMTP id l17mr298105qaj.88.1389298356984; Thu, 09 Jan 2014 12:12:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.120.130 with HTTP; Thu, 9 Jan 2014 12:12:16 -0800 (PST)
In-Reply-To: <201401091437.04245.mark.tinka@seacom.mu>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 9 Jan 2014 15:12:16 -0500
Message-ID: <CAA=duU0=kCOi3nbzkKYgrLr7Y-F6Mj_u838dDWhFSguPi9FGYw@mail.gmail.com>
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
To: mark.tinka@seacom.mu
Content-Type: text/plain; charset=ISO-8859-1
Cc: gorry@erg.abdn.ac.uk, "mpls@ietf.org" <mpls@ietf.org>, LISP mailing list list <lisp@ietf.org>, david.black@emc.com, tsvwg@ietf.org, Stewart Bryant <stbryant@cisco.com>, jnc@mit.edu, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 20:12:50 -0000

I suspect the only way that we can count "misdelivered" MPLS packets
is by looking for missing packets at the receiver, such as by using
the sequence number in the PW control word, TCP, or UDP header,
depending on the MPLS LSP payload.

Thinking about the consequences of an MPLS label somehow becoming
corrupted in transit, nothing will happen until the corrupted label
reaches the top of the stack. At that time, either the packet will be
dropped because the corrupted label isn't in the local LIB, or it is
in the database and the packet will be most likely forwarded out of
the wrong interface, to be dropped at the next label pop because the
label now at the top of the stack is most likely not in that router's
LIB.

Eventually, the packet will most likely be dropped in the network, or
there is a small but nonzero probability that it will be delivered to
an incorrect non-MPLS external interface after the last label has been
popped. If the payload was a globally routable IP packet (not in an IP
VPN) and PHP is in use, then the IP forwarding lookup in the LER may
get the packet to the right place (which will most probably be not on
that particular LER).

Even if PHP isn't in use, if the external interface happens to be to
another router in the same IP address space, then again IP forwarding
may get the packet to the right place.

Of course, it could be a PW control word that gets corrupted, in which
case the packets would reach the PW termination point, but would fail
the sequence number check if the sequence number is in use and that's
the part of the CW that was corrupted.

I don't think anything really bad happens if an entropy label is corrupted.

An interesting thought experiment.

Cheers,
Andy

On Thu, Jan 9, 2014 at 7:36 AM, Mark Tinka <mark.tinka@seacom.mu> wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled
> MPLS.
>
>> I am interested in how often in practice MPLS packets get
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted
> MPLS frames so operators can glean this data. This isn't
> something I've come across, but it would be good to find
> some kind of way to count this across interfaces, if the
> routers can detect and report them.
>
> The known issue about mis-delivery of MPLS frames is poorly-
> sized MTU interfaces. I have no empirical data as to how
> this can corrupt successive MPLS frames that may fit into
> the transit MTU. But in this case, as with any Layer 2
> traffic, not enough MTU = dropped frame.
>
> Mark.
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

From paul.hoffman@vpnc.org  Thu Jan  9 13:04:04 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57EF21AE0F9 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 13:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.747
X-Spam-Level: 
X-Spam-Status: No, score=-0.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, J_CHICKENPOX_52=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RT1TXUPQcyvZ for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 13:04:03 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 51F2C1AE118 for <ietf@ietf.org>; Thu,  9 Jan 2014 13:04:03 -0800 (PST)
Received: from [10.20.30.90] (50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s09KhrP1050441 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 9 Jan 2014 13:43:55 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-51-230.dsl.dynamic.fusionbroadband.com [50.1.51.230] claimed to be [10.20.30.90]
Content-Type: multipart/signed; boundary="Apple-Mail=_C7F8BEFC-B5DD-4F36-A929-FEB74808625D"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
Date: Thu, 9 Jan 2014 13:03:35 -0800
Message-Id: <5E189F2C-29A2-446D-A77E-A5185349AAD3@vpnc.org>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com> <52CEF4E9.1070505@gmail.com> <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 21:04:04 -0000

--Apple-Mail=_C7F8BEFC-B5DD-4F36-A929-FEB74808625D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jan 9, 2014, at 11:40 AM, David Conrad <drc@virtualized.org> wrote:

> On Jan 9, 2014, at 11:13 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>> Working out a timeline to complete an effort to make all of this =
work is left as an exercise to the reader
>>=20
>> Since it's an infinite regression (any N namespaces can be converted =
to a single
>> namespace by adding N unique suffixes or prefixes) I think the =
timescale
>> is infinite.
>>=20
>> Seriously. We have a perfectly fine unambiguous namespace. Enough =
already.
>=20
> The problem is that this issue keeps repeating, particularly in (shall =
we say) non-technical venues. In a private message I semi-seriously =
suggested someone should write an RFC that deprecates classes other than =
IN.  However, I'm beginning to think this might not be that bad of an =
idea -- at least there would be a document that the non-technical folks =
who keep raising the issue could be pointed at...

I would propose exactly the opposite document: "Want your own namespace? =
Here are most of the known the pros and cons of owning your own DNS =
CLASS." Talk about the know pitfalls, but don't assume that those =
pitfalls are fatal for a given scenario. Give out the new classes =
liberally for a few years. The result might be someone else really does =
find good uses for them, and takes pressure of CLASS=3DIN for some =
things that really shouldn't be in the global Internet.

--Paul Hoffman

--Apple-Mail=_C7F8BEFC-B5DD-4F36-A929-FEB74808625D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJSzw6rAAoJEJz/fXByZmLZhlUIAKoTzsRdGrmIwNE0kIddzxhk
k/x/3Tqup8BZOPq78IZckN91FhwVvPtWEXXxk4ZLyza9Rq8hyVmadFgagWT0Vldu
+ZmYkAEmaUohio/RGOAPXYMFNV6txqg4dBcaPQfKUNkCQ1NUajrT0AaQVdvWbvFb
jo7NXR9LIEIa1mdqVJjNZ2YsyykgwGlXHdPgqg0Vbekecy+jn5Yf3/ZHpNgpwV9e
94PKnvmPLwxLsiKwbUVJpixsU/LzF75ZkfIMfwi7Ba0CUfmT1qaB8ae9D4k/yIP0
RRGcrZsdl9T0OqibROHUNLEq5KwAF6xS8YgfToHds+FYXVnPZohYRU34/Mu6ofQ=
=5WKf
-----END PGP SIGNATURE-----

--Apple-Mail=_C7F8BEFC-B5DD-4F36-A929-FEB74808625D--

From dhc@dcrocker.net  Thu Jan  9 13:19:08 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E4A1AE118 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 13:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cfneaFIF0tEp for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 13:19:06 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BC70D1AE057 for <ietf@ietf.org>; Thu,  9 Jan 2014 13:19:06 -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 s09LIq15030533 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 9 Jan 2014 13:18:55 -0800
Message-ID: <52CF11D7.5040209@dcrocker.net>
Date: Thu, 09 Jan 2014 13:17:11 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: David Conrad <drc@virtualized.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com> <52CEF4E9.1070505@gmail.com> <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
In-Reply-To: <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 09 Jan 2014 13:18:56 -0800 (PST)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 21:19:08 -0000

On 1/9/2014 11:40 AM, David Conrad wrote:
> The problem is that this issue keeps repeating, particularly in (shall we say) non-technical venues. In a private message I semi-seriously suggested someone should write an RFC that deprecates classes other than IN.  However, I'm beginning to think this might not be that bad of an idea -- at least there would be a document that the non-technical folks who keep raising the issue could be pointed at...


The premise to your line of thinking is that deprecating other classes 
will reduce these periodic demands for new name spaces.

One of the benefits of having had so many of these cycles of demands, 
over the last 15+ years, is that we can see that straightforward 
technical discussion and explanation does not dissuade the proponents. 
They want what they want and they reject information that counters what 
they want.

As I've become too fond of suggesting, the real requirement here is to 
move the work back onto those seeking the change.

      It is /their/ burden to do the work of proposing and specifying 
the change, in sufficient technical detail.

      It is /their/ burden to do the detail work of explaining how it 
can be viable.

      It is /their/ burden to recruit sufficient community support.

For the rest of us, the only burden is to put the burden back onto those 
folk.  Rather than saying "that won't work" and rather than trying to 
explain why it won't work, and rather than trying to narrow their 
opportunities for making criticisms, we merely need to recite some 
version of the above litany.

If they are so certain what they want is viable, they need to do the 
work of making it viable.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From marka@isc.org  Thu Jan  9 14:11:52 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322841AC404 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.139
X-Spam-Level: 
X-Spam-Status: No, score=-7.139 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV2RK2CGvkH4 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:11:50 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id D85E71AC4AB for <ietf@ietf.org>; Thu,  9 Jan 2014 14:11:49 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id E027F2383F5; Thu,  9 Jan 2014 22:11:28 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 81BC7160475; Thu,  9 Jan 2014 22:21:57 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 54953160459; Thu,  9 Jan 2014 22:21:57 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 4178BCA3464; Fri, 10 Jan 2014 09:12:44 +1100 (EST)
To: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
From: Mark Andrews <marka@isc.org>
References: <alpine.BSF.2.00.1401090943270.929@joyce.lan> <D093D134-76D6-4A0D-ADBF-5AF129309F19@frobbit.se> <CAPv4CP-BQySqb8iXDObT0zAzxxbZ_z6CpVRQAJ-Rk5ev_XjexA@mail.gmail.com> <0A57A7E3-D807-4F4B-A10E-70A6F46B2365@frobbit.se>
Subject: Re: Multi-homed BCP38
In-reply-to: Your message of "Thu, 09 Jan 2014 21:04:23 +0100." <0A57A7E3-D807-4F4B-A10E-70A6F46B2365@frobbit.se>
Date: Fri, 10 Jan 2014 09:12:43 +1100
Message-Id: <20140109221244.4178BCA3464@rock.dv.isc.org>
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 22:11:52 -0000

SIDR should in the end make this easier to automate.

Once your customers have certs that cover the range of addresses
they are allocated they can announce those address ranges as valid
sources to the other ISP securely similarly to the way they can
anounce they want those address ranges routed to them.

BCP 38 can be securely automated if we are willing to spend engineering
effort to achieve it.

Mark

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

From ned+ietf@mauve.mrochek.com  Thu Jan  9 14:29:54 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC1461AC4A7 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:29:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8x2e1i8HZXI5 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:29:53 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 719F61AC421 for <ietf@ietf.org>; Thu,  9 Jan 2014 14:29:53 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P2YBQ0GIPC002P4Y@mauve.mrochek.com> for ietf@ietf.org; Thu, 9 Jan 2014 14:24:38 -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 <01P2SI6PLQJK0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 9 Jan 2014 14:24:30 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P2YBPWNC5G0000AS@mauve.mrochek.com>
Date: Thu, 09 Jan 2014 14:22:47 -0800 (PST)
Subject: Re: Upcoming change to announcement email header fields (using old header)
In-reply-to: "Your message dated Thu, 09 Jan 2014 10:59:35 -0800" <6.2.5.6.2.20140109103707.0b95b440@resistor.net>
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com> <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.gmail.com> <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.g> <mail.com@missing-host.mrochek.com> <6.2.5.6.2.20140109103707.0b95b440@resistor.net>
To: SM <sm@resistor.net>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 22:29:55 -0000

> Hi Dave,
> At 09:39 09-01-2014, Dave Cridland wrote:
> >Much as I adore the almost wonderful irony of "The IESG" having an
> >address of <noreply@ietf.org> - especially in the light of John's
> >closing comment there - many MUAs will then cheerfully offer that as
> >an address for "The IESG".

> :-)

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

> >If that is a dev-null address, as noreply@ often implies, it'll
> >become a self-fulfilling prophecy of sorts. You might want a
> >different phrase, there - "IESG Announcements", or something.

> My guess about the problem is that people choose "Reply to
> All".  That generates more mail for iesg-secretary@.  Using a few
> (sieve) rules might alleviate the problem.

There's even a sieve draft in WGLC that may be relevant:

    draft-ietf-appsawg-sieve-duplicate-02.txt

				Ned

From hallam@gmail.com  Thu Jan  9 14:58:54 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD551AC421 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qZpsRwPQqDhZ for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 14:58:52 -0800 (PST)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id BF0881ACD00 for <ietf@ietf.org>; Thu,  9 Jan 2014 14:58:50 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id x18so2874739lbi.31 for <ietf@ietf.org>; Thu, 09 Jan 2014 14:58:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VOjia0gbtW9rKGYRFZmRyJg73k27EHTborjGz/bK25g=; b=ZjedYOHA8mtwnkDjFO7JOSsxMv37nG2FUKGs7l6sz5tVqd2+7aUC8B6m19VcodVkvz LqbPBljIy5ZhPTjmnYlA1wti41OGJOLc5k8v4L0Jm8HIVmfKKCNWDp7ztW0vm6y0VFE3 24YgWNM0XpjpzOo/AmBvpqM+puyE/Q2nWFVp+JfNjwAjnZkNLBLm+cLeTkkvovWCsqiR wRNL4Z4j4WKCEcKTH8CO+Nb54uxc7cwV036bvD2fgr70XxWZLKOL6nBKBHDDs/ZtsXix xC7VuJ99waPROCUXX3PQ8jC8fAycxCGGYNh3WoXgJtthnBYUdETrTRrLiV9/UQQXG7TP nB+Q==
MIME-Version: 1.0
X-Received: by 10.152.120.7 with SMTP id ky7mr1385024lab.83.1389308320321; Thu, 09 Jan 2014 14:58:40 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Thu, 9 Jan 2014 14:58:40 -0800 (PST)
In-Reply-To: <52CF11D7.5040209@dcrocker.net>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com> <52CEF4E9.1070505@gmail.com> <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org> <52CF11D7.5040209@dcrocker.net>
Date: Thu, 9 Jan 2014 17:58:40 -0500
Message-ID: <CAMm+Lwg=n8y20Q9K1stXvASxbn=u6GJwUGyjhENTCDAisiJTvA@mail.gmail.com>
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0117690dea940304ef918cb9
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 22:58:54 -0000

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

On Thu, Jan 9, 2014 at 4:17 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 1/9/2014 11:40 AM, David Conrad wrote:
>
>> The problem is that this issue keeps repeating, particularly in (shall we
>> say) non-technical venues. In a private message I semi-seriously suggested
>> someone should write an RFC that deprecates classes other than IN.
>>  However, I'm beginning to think this might not be that bad of an idea --
>> at least there would be a document that the non-technical folks who keep
>> raising the issue could be pointed at...
>>
>
>
> The premise to your line of thinking is that deprecating other classes
> will reduce these periodic demands for new name spaces.
>
> One of the benefits of having had so many of these cycles of demands, over
> the last 15+ years, is that we can see that straightforward technical
> discussion and explanation does not dissuade the proponents. They want what
> they want and they reject information that counters what they want.
>
> As I've become too fond of suggesting, the real requirement here is to
> move the work back onto those seeking the change.
>
>      It is /their/ burden to do the work of proposing and specifying the
> change, in sufficient technical detail.
>
>      It is /their/ burden to do the detail work of explaining how it can
> be viable.
>
>      It is /their/ burden to recruit sufficient community support.
>
> For the rest of us, the only burden is to put the burden back onto those
> folk.  Rather than saying "that won't work" and rather than trying to
> explain why it won't work, and rather than trying to narrow their
> opportunities for making criticisms, we merely need to recite some version
> of the above litany.
>
> If they are so certain what they want is viable, they need to do the work
> of making it viable.


+1

This is the way to deal with technical issues. Just lay out the facts and
make sure that every fact that is laid out is completely supportable.

When people draw the conclusion that 'X is impossible', people like me take
that as a challenge.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Jan 9, 2014 at 4:17 PM, Dave Crocker <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.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">On 1/9/2014 11:40 AM, Davi=
d Conrad wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The problem is that this issue keeps repeating, particularly in (shall we s=
ay) non-technical venues. In a private message I semi-seriously suggested s=
omeone should write an RFC that deprecates classes other than IN. =A0Howeve=
r, I&#39;m beginning to think this might not be that bad of an idea -- at l=
east there would be a document that the non-technical folks who keep raisin=
g the issue could be pointed at...<br>

</blockquote>
<br>
<br></div>
The premise to your line of thinking is that deprecating other classes will=
 reduce these periodic demands for new name spaces.<br>
<br>
One of the benefits of having had so many of these cycles of demands, over =
the last 15+ years, is that we can see that straightforward technical discu=
ssion and explanation does not dissuade the proponents. They want what they=
 want and they reject information that counters what they want.<br>

<br>
As I&#39;ve become too fond of suggesting, the real requirement here is to =
move the work back onto those seeking the change.<br>
<br>
=A0 =A0 =A0It is /their/ burden to do the work of proposing and specifying =
the change, in sufficient technical detail.<br>
<br>
=A0 =A0 =A0It is /their/ burden to do the detail work of explaining how it =
can be viable.<br>
<br>
=A0 =A0 =A0It is /their/ burden to recruit sufficient community support.<br=
>
<br>
For the rest of us, the only burden is to put the burden back onto those fo=
lk. =A0Rather than saying &quot;that won&#39;t work&quot; and rather than t=
rying to explain why it won&#39;t work, and rather than trying to narrow th=
eir opportunities for making criticisms, we merely need to recite some vers=
ion of the above litany.<br>

<br>
If they are so certain what they want is viable, they need to do the work o=
f making it viable.</blockquote><div><br></div><div>+1</div><div><br></div>=
<div>This is the way to deal with technical issues. Just lay out the facts =
and make sure that every fact that is laid out is completely supportable.</=
div>
<div><br></div><div>When people draw the conclusion that &#39;X is impossib=
le&#39;, people like me take that as a challenge.</div><div>=A0</div></div>=
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>

</div></div>

--089e0117690dea940304ef918cb9--

From chair@ietf.org  Thu Jan  9 15:08:56 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762221ACC82; Thu,  9 Jan 2014 15:08:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHXJ-Rh5unwP; Thu,  9 Jan 2014 15:08:55 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB6C1A1F58; Thu,  9 Jan 2014 15:08:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id C8EBFA617B; Thu,  9 Jan 2014 15:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w4oNzp-NQD9r; Thu,  9 Jan 2014 15:06:56 -0800 (PST)
Received: from [10.30.0.140] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 22FCFA60C8; Thu,  9 Jan 2014 15:06:55 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Call for feedback for the IAOC appointment by the IESG
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Fri, 10 Jan 2014 01:08:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8A4EDF3-5053-4781-8261-8A35D9DAA542@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "<ietf@ietf.org> Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF Chair <chair@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 23:08:56 -0000

Ole Jacobsen is the IAOC member that was appointed by the IESG, and his =
two-year term is up in March.  The IESG is starting the process to fill =
this seat in March 2014, with the term ending in March 2016.

The IESG is responsible for filling one seat every other year per BCP =
101. The call for candidates and desirable qualifications was in =
http://www.ietf.org/mail-archive/web/ietf-announce/current/msg12224.html

The following candidates have put their names forward:

Tobias Gondrom
Chris Griffiths
Ole Jacobsen
John Levine
Tina Tsou

Please send your remarks in confidence about any or all candidates to =
chair@ietf.org.  We thank you in advance for your help. Please provide =
the feedback by Jan 22nd, 2014.

Note: The nomcom process is ongoing in parallel for another IAOC seat. =
If the nomcom process results in one of these persons being selected, =
the IESG will naturally reduce this list by one.

Best regards,
Jari Arkko
IETF Chair=

From jari.arkko@piuha.net  Thu Jan  9 15:18:00 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC3C51AC421 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 15:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ufp5w1SoG2IX for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 15:17:59 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 06CB71A1F58 for <ietf@ietf.org>; Thu,  9 Jan 2014 15:17:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 14F0C2CC61 for <ietf@ietf.org>; Fri, 10 Jan 2014 01:17:49 +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 12nAnmi05guu for <ietf@ietf.org>; Fri, 10 Jan 2014 01:17:47 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7C1022CC48 for <ietf@ietf.org>; Fri, 10 Jan 2014 01:17:47 +0200 (EET)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: HTTP 2.0 blog article
Message-Id: <A798828E-522E-4AAF-AF32-AF5551476446@piuha.net>
Date: Fri, 10 Jan 2014 01:17:47 +0200
To: "<ietf@ietf.org> Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 23:18:00 -0000

In my today's blog entry I wanted to draw attention to Mark Nottingham=92s=
 excellent blog article about strengthening HTTP.

My entry is at http://www.ietf.org/blog/2014/01/http-2-0/ and Mark's =
article is at =
http://www.mnot.net/blog/2014/01/04/strengthening_http_a_personal_view

Jari


From mariainesrobles@googlemail.com  Thu Jan  9 17:16:48 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 009B61ADF10 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.777
X-Spam-Level: 
X-Spam-Status: No, score=-0.777 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_74=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EqmjmfRs9Q6H for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:16:45 -0800 (PST)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 61D6A1AD8EB for <ietf@ietf.org>; Thu,  9 Jan 2014 17:16:45 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id u57so3334975wes.14 for <ietf@ietf.org>; Thu, 09 Jan 2014 17:16:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=kmCPEqxmiv63Ir24/7ML8yvZdcGL37GI+a+m4XkZC4s=; b=dBEYALY71iSPQnX3CLDYi3uFHcf7ZmJ9I70LuE090M/T4vib2jG3+jJd3UP5xhedDZ sUucqqIg1t3iqnNJ0i254rQeFwk/Uc2P8LICi125qAuESKdIOBKpeSkLvN7ninCyXw6p 3EZ9XvHSFJYrLe1mLXSEGgSx9xBQJN4mQTwmueHXp7s06aqE63lpSyWd4X4GqY4dw4rL PIHg3SAJBGqmq5I2TbgVlbffKP4bB22igfNQXlyH+Y1tts2ZuZgK3Msc7Dz3aKyWLODT vHWgobqZudORv07KYWFZizDjns4QLVrtZJVzNLAbhH3TZQf1akq7z6DjRVkhDlCKrBb/ 3DAA==
MIME-Version: 1.0
X-Received: by 10.180.86.9 with SMTP id l9mr62367wiz.20.1389316595100; Thu, 09 Jan 2014 17:16:35 -0800 (PST)
Received: by 10.216.44.144 with HTTP; Thu, 9 Jan 2014 17:16:34 -0800 (PST)
Date: Thu, 9 Jan 2014 23:16:34 -0200
Message-ID: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044287be21b21704ef937af8
Cc: S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 01:16:48 -0000

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

*Hello,The IESG approved the draft-moonesamy-ietf-conduct-3184bis-06
<https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/>,
including these new changes:Section 3 (foreseeable was replaced by
foreseen)OLD:=93However it is to be noted that there is an expectation that
no one shall ever knowingly contribute advice or   text that may affect the
security of the Internet without describing all known or foreseeable risks
and threats to potential implementers and users. =94NEW: =93However it is t=
o be
noted that there is an expectation that no one shall ever knowingly
contribute advice or   text that may affect the security of the Internet
without describing all known or foreseen risks and threats to potential
implementers and users. =94Section 4:The word "adversely" which was added t=
o
the last sentence in Section 4.Please note, that due to this new version,
the AD give until Tuesday next week to provide comments before send the
draft to the RFC Editor.Thank you and Kind Regards,Ines Robles.*


2013/11/8 <ietf-request@ietf.org>

>
>    5. Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>       (IETF     Guidelines for Conduct) to Best Current Practice
>       (Brian E Carpenter)
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 09 Nov 2013 08:33:14 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> To: S Moonesamy <sm+ietf@elandsys.com>
> Cc: ietf@ietf.org
> Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>         (IETF   Guidelines for Conduct) to Best Current Practice
> Message-ID: <527D3C7A.1060200@gmail.com>
> Content-Type: text/plain; charset=3DUTF-8
>
> That works for me.
>
> Thanks
>    Brian
>
> On 09/11/2013 07:03, S Moonesamy wrote:
> > Hi Brian,
> > At 18:58 07-11-2013, Brian E Carpenter wrote:
> >> Fair enough. But people do need to respect the shortage of time. How
> >> about
> >> "Working Group meetings run on a very limited time schedule,
> >> and sometimes participants have to limit their questions.
> >> The work of the group will continue on the mailing list, and
> >> questions can be asked and answered on the list."
> >
> > How about:
> >
> >    IETF participants read the relevant Internet-Drafts, RFCs, and
> >    email archives beforehand, in order to familiarize themselves
> >    with the technology under discussion.  Working Group sessions
> >    run on a very limited time schedule, and sometimes participants
> >    have to limit their questions.  The work of the group will
> >    continue on the mailing list, and questions can be asked and
> >    answered on the mailing list.  It can be a challenge when
> >    attending a new working group without knowing the history of
> >    longstanding Working Group debates.  Information about a working
> >    group including its charter and milestones is available on the
> >    IETF Tools web site [TOOLS] or from the working group chair.
> >
> > Regards,
> > S. Moonesamy
> > .
> >
>
>
> ------------------------------
>
> _______________________________________________
> ietf mailing list
> ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> End of ietf Digest, Vol 66, Issue 60
> ************************************
>

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

<div dir=3D"ltr"><b id=3D"docs-internal-guid-5e9fc2de-79ad-cd51-2059-b96428=
f529ff" style=3D"font-weight:normal"><p dir=3D"ltr" style=3D"line-height:1.=
15;margin-top:0pt;margin-bottom:0pt"><span style=3D"vertical-align:baseline=
;white-space:pre-wrap"><font face=3D"arial, helvetica, sans-serif" color=3D=
"#000000">Hello,</font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><div><b style=
=3D"font-weight:normal"><font face=3D"arial, helvetica, sans-serif" color=
=3D"#000000"><br></font></b></div></font><p dir=3D"ltr" style=3D"line-heigh=
t:1.15;margin-top:0pt;margin-bottom:0pt">
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><span style=
=3D"vertical-align:baseline;white-space:pre-wrap">The IESG </span><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap">approved</span><span st=
yle=3D"vertical-align:baseline;white-space:pre-wrap"> the <a href=3D"https:=
//datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/">draft-moo=
nesamy-ietf-conduct-3184bis-06</a>, including these new changes:</span></fo=
nt></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Section 3 (foreseeable was replaced =
by foreseen)</font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">OLD:</font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">=93However it is to be noted that th=
ere is an expectation that no one shall ever knowingly contribute advice or=
<br class=3D"">
 =A0=A0text that may affect the security of the Internet without describing=
 all known or foreseeable risks and threats to potential implementers and u=
sers. =94</font></span></p><font face=3D"arial, helvetica, sans-serif" colo=
r=3D"#000000"><br>
<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">NEW: </font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><font fac=
e=3D"arial, helvetica, sans-serif" color=3D"#000000"><span style=3D"vertica=
l-align:baseline;white-space:pre-wrap">=93However it is to be noted that th=
ere is an expectation that no one shall ever knowingly contribute advice or=
<br class=3D"">
 =A0=A0text that may affect the security of the Internet without describing=
 all known or </span><span style=3D"vertical-align:baseline;white-space:pre=
-wrap">foreseen</span><span style=3D"vertical-align:baseline;white-space:pr=
e-wrap"> risks and threats to potential implementers and users. =94</span><=
/font></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Section 4:</font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">The word &quot;adversely&quot; which=
 was added to the last sentence in Section 4.</font></span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></p><font=
 face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br>
<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">Please note, that due to th=
is new version, the AD give until Tuesday next week to provide comments bef=
ore send the draft to the RFC Editor.</font></span></p>
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></p><font=
 face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br>
<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">Thank you and Kind Regards,=
</font></span></p>
<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Ines Robles.</font></span></p>
<div><span style=3D"vertical-align:baseline;white-space:pre-wrap"><font fac=
e=3D"arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></di=
v></b><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/11=
/8  <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf-request@ietf.org" target=
=3D"_blank">ietf-request@ietf.org</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><br>
=A0 =A05. Re: Last Call: &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt=
;<br>
=A0 =A0 =A0 (IETF =A0 =A0 Guidelines for Conduct) to Best Current Practice<=
br>
=A0 =A0 =A0 (Brian E Carpenter)<br>
<br><br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sat, 09 Nov 2013 08:33:14 +1300<br>
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;<br>
To: S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com">sm+ietf@eland=
sys.com</a>&gt;<br>
Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Subject: Re: Last Call: &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt;=
<br>
=A0 =A0 =A0 =A0 (IETF =A0 Guidelines for Conduct) to Best Current Practice<=
br>
Message-ID: &lt;<a href=3D"mailto:527D3C7A.1060200@gmail.com">527D3C7A.1060=
200@gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3DUTF-8<br>
<br>
That works for me.<br>
<br>
Thanks<br>
=A0 =A0Brian<br>
<br>
On 09/11/2013 07:03, S Moonesamy wrote:<br>
&gt; Hi Brian,<br>
&gt; At 18:58 07-11-2013, Brian E Carpenter wrote:<br>
&gt;&gt; Fair enough. But people do need to respect the shortage of time. H=
ow<br>
&gt;&gt; about<br>
&gt;&gt; &quot;Working Group meetings run on a very limited time schedule,<=
br>
&gt;&gt; and sometimes participants have to limit their questions.<br>
&gt;&gt; The work of the group will continue on the mailing list, and<br>
&gt;&gt; questions can be asked and answered on the list.&quot;<br>
&gt;<br>
&gt; How about:<br>
&gt;<br>
&gt; =A0 =A0IETF participants read the relevant Internet-Drafts, RFCs, and<=
br>
&gt; =A0 =A0email archives beforehand, in order to familiarize themselves<b=
r>
&gt; =A0 =A0with the technology under discussion. =A0Working Group sessions=
<br>
&gt; =A0 =A0run on a very limited time schedule, and sometimes participants=
<br>
&gt; =A0 =A0have to limit their questions. =A0The work of the group will<br=
>
&gt; =A0 =A0continue on the mailing list, and questions can be asked and<br=
>
&gt; =A0 =A0answered on the mailing list. =A0It can be a challenge when<br>
&gt; =A0 =A0attending a new working group without knowing the history of<br=
>
&gt; =A0 =A0longstanding Working Group debates. =A0Information about a work=
ing<br>
&gt; =A0 =A0group including its charter and milestones is available on the<=
br>
&gt; =A0 =A0IETF Tools web site [TOOLS] or from the working group chair.<br=
>
&gt;<br>
&gt; Regards,<br>
&gt; S. Moonesamy<br>
&gt; .<br>
&gt;<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ietf mailing list<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
<br>
End of ietf Digest, Vol 66, Issue 60<br>
************************************<br>
</blockquote></div><br></div></div>

--f46d044287be21b21704ef937af8--

From mariainesrobles@googlemail.com  Thu Jan  9 17:24:31 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 584CA1ADF50 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:24:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMDVVHKWLzPM for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:24:28 -0800 (PST)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 7550B1ACC87 for <ietf@ietf.org>; Thu,  9 Jan 2014 17:24:28 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id t60so3484378wes.18 for <ietf@ietf.org>; Thu, 09 Jan 2014 17:24:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xQjshFk3c2ndTEDyAiVkEhZNn66UQOymkj/WGF+TEh4=; b=H3ehjh1LTvKzcJOP3enNQKY/Fk/yhM2MrbamNwgWaJx93cQv3bvTJwgaAdLq+f5ffT F1EZr8QsfGwqznZr2LFWiSq68QapRWZF43Bbj+1msxRPNukFWkyieQYwWFePRaf0o9KK jMdzqv14uo/J7GWDJReAJyUMmlgKm4Tj0m/we1dGimQ+e+KK8dAUoDeRD1bNoaWJ9C5g 7t+cbCx4sgrQWvyoWkMj5xhif4WziXIy8wSxUkf+xBZCKTdNN/BxH9kAOVcCR9b5Wajk kObw4SCO0UHYtv/upV+b3alGOq7lbKMn+QA0nDHrRcuneDREwvb8tGu7wUVNCF0dcFaV QEyw==
MIME-Version: 1.0
X-Received: by 10.180.86.9 with SMTP id l9mr83984wiz.20.1389317058239; Thu, 09 Jan 2014 17:24:18 -0800 (PST)
Received: by 10.216.44.144 with HTTP; Thu, 9 Jan 2014 17:24:18 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140109172031.0ba64140@elandnews.com>
References: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com> <6.2.5.6.2.20140109172031.0ba64140@elandnews.com>
Date: Thu, 9 Jan 2014 23:24:18 -0200
Message-ID: <CAP+sJUdRTWnh2RLmPxb05jL7HChqq5MJSyGaGnTD6eTWFGOb8g@mail.gmail.com>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=f46d044287bebca34804ef9395c2
Cc: S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 01:24:31 -0000

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

Hello,

Please disregard the previous email, this is the correct one:

Section 3:

1- foreseeable was replaced by foreseen
2- adversely was added.

This is the existing text in Section 3:

  "However it is to be noted that there is an expectation that no one
   shall ever knowingly contribute advice or text that may affect the
   security of the Internet without describing all known or foreseeable
   risks and threats to potential implementers and users."

And the new text:

   However it is to be noted that there is an expectation that no one
   shall ever knowingly contribute advice or text that may adversely
   affect the security of the Internet without describing all known or
   foreseen risks and threats to potential implementers and users.



*Please note, that due to this new version, the AD give until Tuesday next
week to provide comments before send the draft to the RFC Editor. Thanks
and Regards, Ines Robles. *
2014/1/9 Ines Robles <mariainesrobles@googlemail.com>

>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Hello, The IESG approved the draft-moonesamy-ietf-conduct-3184bis-06
> <https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/>,
> including these new changes: Section 3 (foreseeable was replaced by
> foreseen) OLD: =93However it is to be noted that there is an expectation =
that
> no one shall ever knowingly contribute advice or   text that may affect t=
he
> security of the Internet without describing all known or foreseeable risk=
s
> and threats to potential implementers and users. =94 NEW: =93However it i=
s to
> be noted that there is an expectation that no one shall ever knowingly
> contribute advice or   text that may affect the security of the Internet
> without describing all known or foreseen risks and threats to potential
> implementers and users. =94 Section 4: The word "adversely" which was add=
ed
> to the last sentence in Section 4. Please note, that due to this new
> version, the AD give until Tuesday next week to provide comments before
> send the draft to the RFC Editor. Thank you and Kind Regards, Ines Robles=
. *
>
>
> 2013/11/8 <ietf-request@ietf.org>
>
>>
>>    5. Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>>       (IETF     Guidelines for Conduct) to Best Current Practice
>>       (Brian E Carpenter)
>>
>>
>> ------------------------------
>>
>> Message: 5
>> Date: Sat, 09 Nov 2013 08:33:14 +1300
>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> To: S Moonesamy <sm+ietf@elandsys.com>
>> Cc: ietf@ietf.org
>> Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>>         (IETF   Guidelines for Conduct) to Best Current Practice
>> Message-ID: <527D3C7A.1060200@gmail.com>
>> Content-Type: text/plain; charset=3DUTF-8
>>
>> That works for me.
>>
>> Thanks
>>    Brian
>>
>> On 09/11/2013 07:03, S Moonesamy wrote:
>> > Hi Brian,
>> > At 18:58 07-11-2013, Brian E Carpenter wrote:
>> >> Fair enough. But people do need to respect the shortage of time. How
>> >> about
>> >> "Working Group meetings run on a very limited time schedule,
>> >> and sometimes participants have to limit their questions.
>> >> The work of the group will continue on the mailing list, and
>> >> questions can be asked and answered on the list."
>> >
>> > How about:
>> >
>> >    IETF participants read the relevant Internet-Drafts, RFCs, and
>> >    email archives beforehand, in order to familiarize themselves
>> >    with the technology under discussion.  Working Group sessions
>> >    run on a very limited time schedule, and sometimes participants
>> >    have to limit their questions.  The work of the group will
>> >    continue on the mailing list, and questions can be asked and
>> >    answered on the mailing list.  It can be a challenge when
>> >    attending a new working group without knowing the history of
>> >    longstanding Working Group debates.  Information about a working
>> >    group including its charter and milestones is available on the
>> >    IETF Tools web site [TOOLS] or from the working group chair.
>> >
>> > Regards,
>> > S. Moonesamy
>> > .
>> >
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> ietf mailing list
>> ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
>> End of ietf Digest, Vol 66, Issue 60
>> ************************************
>>
>
>

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

<div dir=3D"ltr">Hello,<div><br></div><div>Please disregard the previous em=
ail, this is the correct one:</div><div><br></div><div>Section 3:=A0</div><=
div><br></div><div>1- foreseeable was replaced by foreseen</div><div>2- adv=
ersely was added.=A0</div>

<div><br></div><div><span style=3D"font-family:arial,sans-serif;font-size:1=
3px">This is the existing text in Section 3:</span><br style=3D"font-family=
:arial,sans-serif;font-size:13px"><br style=3D"font-family:arial,sans-serif=
;font-size:13px">

<span style=3D"font-family:arial,sans-serif;font-size:13px">=A0 &quot;Howev=
er it is to be noted that there is an expectation that no one</span><br sty=
le=3D"font-family:arial,sans-serif;font-size:13px"><span style=3D"font-fami=
ly:arial,sans-serif;font-size:13px">=A0 =A0shall ever knowingly contribute =
advice or text that may affect the</span><br style=3D"font-family:arial,san=
s-serif;font-size:13px">

<span style=3D"font-family:arial,sans-serif;font-size:13px">=A0 =A0security=
 of the Internet without describing all known or foreseeable</span><br styl=
e=3D"font-family:arial,sans-serif;font-size:13px"><span style=3D"font-famil=
y:arial,sans-serif;font-size:13px">=A0 =A0risks and threats to potential im=
plementers and users.&quot;</span><br style=3D"font-family:arial,sans-serif=
;font-size:13px">

<br style=3D"font-family:arial,sans-serif;font-size:13px"><span style=3D"fo=
nt-family:arial,sans-serif;font-size:13px">And the new text:</span><br styl=
e=3D"font-family:arial,sans-serif;font-size:13px"><br style=3D"font-family:=
arial,sans-serif;font-size:13px">

<span style=3D"font-family:arial,sans-serif;font-size:13px">=A0 =A0However =
it is to be noted that there is an expectation that no one</span><br style=
=3D"font-family:arial,sans-serif;font-size:13px"><span style=3D"font-family=
:arial,sans-serif;font-size:13px">=A0 =A0shall ever knowingly contribute ad=
vice or text that may adversely</span><br style=3D"font-family:arial,sans-s=
erif;font-size:13px">

<span style=3D"font-family:arial,sans-serif;font-size:13px">=A0 =A0affect t=
he security of the Internet without describing all known or</span><br style=
=3D"font-family:arial,sans-serif;font-size:13px"><span style=3D"font-family=
:arial,sans-serif;font-size:13px">=A0 =A0foreseen risks and threats to pote=
ntial implementers and users.</span><br style=3D"font-family:arial,sans-ser=
if;font-size:13px">

<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><b style=3D=
"font-weight:normal"><p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0p=
t;margin-bottom:0pt"><span style=3D"vertical-align:baseline;white-space:pre=
-wrap"><font face=3D"arial, helvetica, sans-serif" color=3D"#000000">Please=
 note, that due to this new version, the AD give until Tuesday next week to=
 provide comments before send the draft to the RFC Editor.</font></span></p=
>

<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></p><p st=
yle=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">

<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">Thanks and Regards,</font><=
/span></p><p style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><s=
pan style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"ar=
ial, helvetica, sans-serif" color=3D"#000000"><br>

</font></span></p><p style=3D"line-height:1.15;margin-top:0pt;margin-bottom=
:0pt"><span style=3D"vertical-align:baseline;white-space:pre-wrap"><font fa=
ce=3D"arial, helvetica, sans-serif" color=3D"#000000">Ines Robles.</font></=
span></p>

</b><br><div class=3D"gmail_quote">2014/1/9 Ines  Robles <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mariainesrobles@googlemail.com" target=3D"_blank">mar=
iainesrobles@googlemail.com</a>&gt;</span><br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-co=
lor:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div dir=3D"ltr"><b style=3D"font-weight:normal"><p dir=3D"ltr" style=3D"li=
ne-height:1.15;margin-top:0pt;margin-bottom:0pt"><span style=3D"vertical-al=
ign:baseline;white-space:pre-wrap"><font face=3D"arial, helvetica, sans-ser=
if" color=3D"#000000">Hello,</font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><div><b style=
=3D"font-weight:normal"><font face=3D"arial, helvetica, sans-serif" color=
=3D"#000000"><br></font></b></div></font><p dir=3D"ltr" style=3D"line-heigh=
t:1.15;margin-top:0pt;margin-bottom:0pt">


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><span style=
=3D"vertical-align:baseline;white-space:pre-wrap">The IESG </span><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap">approved</span><span st=
yle=3D"vertical-align:baseline;white-space:pre-wrap"> the <a href=3D"https:=
//datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/" target=3D=
"_blank">draft-moonesamy-ietf-conduct-3184bis-06</a>, including these new c=
hanges:</span></font></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Section 3 (foreseeable was replaced =
by foreseen)</font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">OLD:</font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">=93However it is to be noted that th=
ere is an expectation that no one shall ever knowingly contribute advice or=
<br>


 =A0=A0text that may affect the security of the Internet without describing=
 all known or foreseeable risks and threats to potential implementers and u=
sers. =94</font></span></p><font face=3D"arial, helvetica, sans-serif" colo=
r=3D"#000000"><br>


<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">NEW: </font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><font fac=
e=3D"arial, helvetica, sans-serif" color=3D"#000000"><span style=3D"vertica=
l-align:baseline;white-space:pre-wrap">=93However it is to be noted that th=
ere is an expectation that no one shall ever knowingly contribute advice or=
<br>


 =A0=A0text that may affect the security of the Internet without describing=
 all known or </span><span style=3D"vertical-align:baseline;white-space:pre=
-wrap">foreseen</span><span style=3D"vertical-align:baseline;white-space:pr=
e-wrap"> risks and threats to potential implementers and users. =94</span><=
/font></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Section 4:</font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">The word &quot;adversely&quot; which=
 was added to the last sentence in Section 4.</font></span></p>


<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></p><font=
 face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br>


<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">Please note, that due to th=
is new version, the AD give until Tuesday next week to provide comments bef=
ore send the draft to the RFC Editor.</font></span></p>


<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></p><font=
 face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br>


<span style=3D"vertical-align:baseline;white-space:pre-wrap"></span></font>=
<p dir=3D"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"=
arial, helvetica, sans-serif" color=3D"#000000">Thank you and Kind Regards,=
</font></span></p>


<font face=3D"arial, helvetica, sans-serif" color=3D"#000000"><br><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"></span></font><p dir=3D=
"ltr" style=3D"line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"vertical-align:baseline;white-space:pre-wrap"><font face=3D"arial, he=
lvetica, sans-serif" color=3D"#000000">Ines Robles.</font></span></p>


<div><span style=3D"vertical-align:baseline;white-space:pre-wrap"><font fac=
e=3D"arial, helvetica, sans-serif" color=3D"#000000"><br></font></span></di=
v></b><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2013/11=
/8  <span dir=3D"ltr">&lt;<a href=3D"mailto:ietf-request@ietf.org" target=
=3D"_blank">ietf-request@ietf.org</a>&gt;</span><br>


<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><br>
=A0 =A05. Re: Last Call: &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt=
;<br>
=A0 =A0 =A0 (IETF =A0 =A0 Guidelines for Conduct) to Best Current Practice<=
br>
=A0 =A0 =A0 (Brian E Carpenter)<br>
<br><br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sat, 09 Nov 2013 08:33:14 +1300<br>
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;<br>
To: S Moonesamy &lt;<a href=3D"mailto:sm%2Bietf@elandsys.com" target=3D"_bl=
ank">sm+ietf@elandsys.com</a>&gt;<br>
Cc: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br=
>
Subject: Re: Last Call: &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt;=
<br>
=A0 =A0 =A0 =A0 (IETF =A0 Guidelines for Conduct) to Best Current Practice<=
br>
Message-ID: &lt;<a href=3D"mailto:527D3C7A.1060200@gmail.com" target=3D"_bl=
ank">527D3C7A.1060200@gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=3DUTF-8<br>
<br>
That works for me.<br>
<br>
Thanks<br>
=A0 =A0Brian<br>
<br>
On 09/11/2013 07:03, S Moonesamy wrote:<br>
&gt; Hi Brian,<br>
&gt; At 18:58 07-11-2013, Brian E Carpenter wrote:<br>
&gt;&gt; Fair enough. But people do need to respect the shortage of time. H=
ow<br>
&gt;&gt; about<br>
&gt;&gt; &quot;Working Group meetings run on a very limited time schedule,<=
br>
&gt;&gt; and sometimes participants have to limit their questions.<br>
&gt;&gt; The work of the group will continue on the mailing list, and<br>
&gt;&gt; questions can be asked and answered on the list.&quot;<br>
&gt;<br>
&gt; How about:<br>
&gt;<br>
&gt; =A0 =A0IETF participants read the relevant Internet-Drafts, RFCs, and<=
br>
&gt; =A0 =A0email archives beforehand, in order to familiarize themselves<b=
r>
&gt; =A0 =A0with the technology under discussion. =A0Working Group sessions=
<br>
&gt; =A0 =A0run on a very limited time schedule, and sometimes participants=
<br>
&gt; =A0 =A0have to limit their questions. =A0The work of the group will<br=
>
&gt; =A0 =A0continue on the mailing list, and questions can be asked and<br=
>
&gt; =A0 =A0answered on the mailing list. =A0It can be a challenge when<br>
&gt; =A0 =A0attending a new working group without knowing the history of<br=
>
&gt; =A0 =A0longstanding Working Group debates. =A0Information about a work=
ing<br>
&gt; =A0 =A0group including its charter and milestones is available on the<=
br>
&gt; =A0 =A0IETF Tools web site [TOOLS] or from the working group chair.<br=
>
&gt;<br>
&gt; Regards,<br>
&gt; S. Moonesamy<br>
&gt; .<br>
&gt;<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
ietf mailing list<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
<br>
<br>
End of ietf Digest, Vol 66, Issue 60<br>
************************************<br>
</blockquote></div><br></div></div>
</blockquote></div><br></div></div></div>

--f46d044287bebca34804ef9395c2--

From ggm@algebras.org  Thu Jan  9 17:29:30 2014
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD231ACCFA for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:29:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dp-LPvBU3gcm for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 17:29:26 -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 C2E5E1ADF44 for <ietf@ietf.org>; Thu,  9 Jan 2014 17:29:26 -0800 (PST)
Received: by mail-pb0-f41.google.com with SMTP id jt11so3762820pbb.14 for <ietf@ietf.org>; Thu, 09 Jan 2014 17:29:17 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ocznyrzyB9Cy2buTXOaPRks6W6r5U1cnJcmTnO5X2RY=; b=VzZ+Vm3GPFVROHQgFLXdtSBlRT3GyUG+X8t8+Jy6hFP9o7JRgotKM9GGkVZL//vxvn nR+2Di1bpDKS6Kwx7ZB8A40x16HL9WF6rX/cK8KdopikMxAo1x8WRgyTUgjjQFjKoTo6 /DRcEfD5SWgZfx9N6OeGQKyymdxJT/ySQg/IM34znY/NAtyX7irFdqhEayfO9qa9zUo0 sWAGQq8hswx5IDXG0vylDN3XaA3+AFRBCjhBKrHZKgSm5gmlxrBEB6g2Fml3II8pOKIN ohYbKbQMq47DYm6eB2taaYQ+n1gpgNTkmTmWlbj+G+BdWjtiYT/3/MF1VGzf2nmlpNIB /RNg==
X-Gm-Message-State: ALoCoQkQSGp0tz0ie7gYkifbByoInmqxOB6ZQ9gUQ0sCdBz/SR+eN8jwou5zeKKWj0I90ocy7ZjN
MIME-Version: 1.0
X-Received: by 10.68.201.226 with SMTP id kd2mr7243154pbc.157.1389317357103; Thu, 09 Jan 2014 17:29:17 -0800 (PST)
Received: by 10.70.87.144 with HTTP; Thu, 9 Jan 2014 17:29:17 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:345c:4d26:1ab0:bfb4]
In-Reply-To: <29A7BEB33E32EC9D427500ED@JcK-HP8200.jck.com>
References: <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info> <52CC1618.1090605@cisco.com> <9F439EC8447B582E1625CB73@JcK-HP8200.jck.com> <52CEB680.4010706@cisco.com> <29A7BEB33E32EC9D427500ED@JcK-HP8200.jck.com>
Date: Fri, 10 Jan 2014 11:29:17 +1000
Message-ID: <CAKr6gn3-bYxpUU4Jrbjde-3dWs6PbdsHXsjA20KTgaxWzS+=_w@mail.gmail.com>
Subject: Re: DNS design
From: George Michaelson <ggm@algebras.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=e89a8ff1c37a8d079404ef93a7e2
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 01:29:30 -0000

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

it is worth bearing in mind that the namespace of wide use before DNS was
email, and for many had already been made a tree. explicit hop-paths
persisted alongside initiatives like honey-danber and user@host forms, the
latter having adopted dot-separated labels under a tree form, well before
widespread adoption of port 53. almost all conversations around 'how do we
glue this external mail service in' wound up assuming a new top-level
domain such as .BITNET to create a clean tree entrypoint for an otherwise
unconstrained/unknown namespace.


On Fri, Jan 10, 2014 at 3:48 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Thursday, January 09, 2014 15:47 +0100 Eliot Lear
> <lear@cisco.com> wrote:
>
> > John,
> >
> > Just to be clear, I was using DNS as an example.  We can
> > always question design decisions we've made.  I believe that
> > Andrew and others may be interested in doing just that, but
> > not from the top down (as it were).
>
> Certainly we can, and should, question design decisions we've
> made, if only to learn from them.  For the same reason, I also
> think it is appropriate to review and question the goal and
> constraint decisions that drive those design decisions
>
> But I think two points are relevant when we start doing so:
>
> (1) The observation that a decision may have political
> implications -- at present or at some point in the future-- does
> not make the decision itself political rather than technical.
> For the IETF's work, political considerations are best
> incorporated into goal and constraint spaces rather than leading
> us into an argument about the basis on which those decisions are
> made.
>
> (2) Unless one is either trying to learn in the hope of doing a
> better job on future designs or likes purely theoretical
> discussions about the circumstances that would prevail in some
> alternate reality, it seems to me that discussions of the
> implications of trying to deploy redesigned versions of
> something should be considered as part of the constraint space
> for any results of questioning design decisions.   Our track
> record for deployment of incompatible replacements for things
> that work even moderately well has been, IMO, poor enough to
> give us considerable pause if, e.g., someone proposes to take
> "questioning design decisions" toward an effort to redesign,
> reimplement, and redeploy the DNS.  My own hypothesis about that
> is that the DNS we have is pretty much the DNS we are going to
> have and that it would serve the broader community well if we
> both accepted that and because more aggressive about saying "not
> a good idea, find some other facility to use as a base" when
> ideas come along that require violations of important principles
> of the design.
>
> best,
>    john
>
>
>
>

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

<div dir=3D"ltr">it is worth bearing in mind that the namespace of wide use=
 before DNS was email, and for many had already been made a tree. explicit =
hop-paths persisted alongside initiatives like honey-danber and user@host f=
orms, the latter having adopted dot-separated labels under a tree form, wel=
l before widespread adoption of port 53. almost all conversations around &#=
39;how do we glue this external mail service in&#39; wound up assuming a ne=
w top-level domain such as .BITNET to create a clean tree entrypoint for an=
 otherwise unconstrained/unknown namespace.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Jan 1=
0, 2014 at 3:48 AM, John C Klensin <span dir=3D"ltr">&lt;<a href=3D"mailto:=
john-ietf@jck.com" target=3D"_blank">john-ietf@jck.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
<br>
<br>
--On Thursday, January 09, 2014 15:47 +0100 Eliot Lear<br>
<div class=3D"im">&lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&=
gt; wrote:<br>
<br>
&gt; John,<br>
&gt;<br>
&gt; Just to be clear, I was using DNS as an example. =A0We can<br>
&gt; always question design decisions we&#39;ve made. =A0I believe that<br>
&gt; Andrew and others may be interested in doing just that, but<br>
&gt; not from the top down (as it were).<br>
<br>
</div>Certainly we can, and should, question design decisions we&#39;ve<br>
made, if only to learn from them. =A0For the same reason, I also<br>
think it is appropriate to review and question the goal and<br>
constraint decisions that drive those design decisions<br>
<br>
But I think two points are relevant when we start doing so:<br>
<br>
(1) The observation that a decision may have political<br>
implications -- at present or at some point in the future-- does<br>
not make the decision itself political rather than technical.<br>
For the IETF&#39;s work, political considerations are best<br>
incorporated into goal and constraint spaces rather than leading<br>
us into an argument about the basis on which those decisions are<br>
made.<br>
<br>
(2) Unless one is either trying to learn in the hope of doing a<br>
better job on future designs or likes purely theoretical<br>
discussions about the circumstances that would prevail in some<br>
alternate reality, it seems to me that discussions of the<br>
implications of trying to deploy redesigned versions of<br>
something should be considered as part of the constraint space<br>
for any results of questioning design decisions. =A0 Our track<br>
record for deployment of incompatible replacements for things<br>
that work even moderately well has been, IMO, poor enough to<br>
give us considerable pause if, e.g., someone proposes to take<br>
&quot;questioning design decisions&quot; toward an effort to redesign,<br>
reimplement, and redeploy the DNS. =A0My own hypothesis about that<br>
is that the DNS we have is pretty much the DNS we are going to<br>
have and that it would serve the broader community well if we<br>
both accepted that and because more aggressive about saying &quot;not<br>
a good idea, find some other facility to use as a base&quot; when<br>
ideas come along that require violations of important principles<br>
of the design.<br>
<br>
best,<br>
=A0 =A0john<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--e89a8ff1c37a8d079404ef93a7e2--

From l.wood@surrey.ac.uk  Thu Jan  9 20:22:23 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A34CB1AE001; Thu,  9 Jan 2014 20:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxwNkA2w2dQi; Thu,  9 Jan 2014 20:22:20 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.118]) by ietfa.amsl.com (Postfix) with ESMTP id D307E1ADF5C; Thu,  9 Jan 2014 20:22:19 -0800 (PST)
Received: from [193.109.255.147:34109] by server-14.bemta-14.messagelabs.com id E5/D4-12628-1757FC25; Fri, 10 Jan 2014 04:22:09 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-72.messagelabs.com!1389327728!11897647!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 2107 invoked from network); 10 Jan 2014 04:22:09 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-8.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 10 Jan 2014 04:22:09 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 10 Jan 2014 04:22:08 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>, <david.i.allan@ericsson.com>
Date: Fri, 10 Jan 2014 04:19:24 +0000
Subject: RE: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Topic: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Index: Ac8Nqj4MGzqvYffaRlKHQ/vzzrnSnQAEObyx
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346B8@EXMB01CMS.surrey.ac.uk>
References: Your message of "Thu, 09 Jan 2014 20:26:27 +0000." <E6C17D2345AC7A45B7D054D407AA205C391FEA0A@eusaamb105.ericsson.se>, <201401100217.s0A2Hv4I081006@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401100217.s0A2Hv4I081006@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org, tsvwg@ietf.org, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 04:22:23 -0000

The origin of this discussion is zero UDP checksums and
http://www.ietf.org/mail-archive/web/ietf/current/msg85354.html

I suggest reading Jonathan Stone's papers and PhD thesis for a good
understanding of where errors can come from.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: mpls [mpls-bounces@ietf.org] On Behalf Of Curtis Villamizar [curtis@i=
pv6.occnc.com]
Sent: 10 January 2014 02:17
To: David Allan I
Cc: mpls@ietf.org; tsvwg@ietf.org; lisp@ietf.org; ietf@ietf.org
Subject: Re: [mpls] misdelivered mpls packets - Was: Re:        draft-ietf-=
mpls-in-udp was RE: gre-in-udp draft

Since we are all top posting ...

For counting dropped packets LM OAM is what you need.  CV doesn't do
that.  Direct LM will give best results on a per LSP basis but
requires forwarding chip support to do so.

I also don't know the origin of this discussion.

>> I am interested in how often in practice MPLS packets get
>> misdelivered due to label corruption.

Not very often if ever at least for major vendor products.  I don't
know if second tier or third tier players have bugs.

(Very often circa 2000 or earlier particularly with one specific
vendor and with one provider who made things much worse by mucking
with the ILM through management plane, but that is ancient history).

Bit rot in TCAM or SRAM is very rare.  Bit rot in circa 1980s DRAM was
a problem.  Bit rot in modern non-ECC DRAM is rare.  Bit rot in modern
ECC DRAM is very rare.  Therefore to have a bad ILM you need bugs.

Curtis


In message <E6C17D2345AC7A45B7D054D407AA205C391FEA0A@eusaamb105.ericsson.se=
>
David Allan I writes:

Hi  (trimmed received list)

I'm not sure what the starting point of this dialog is, but I can at least =
say Greg is right on the CV front, it only detects and does not measure mis=
direction.

The only other possibility to count anything is a "no ILM" condition where =
the label value is unrecognized by the receiving LSR, which IMO could not b=
e made authoritative if it is label values in either the frame or the NHLFE=
 and not exclusively next hops that is corrupted.

Cheers
D

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Thursday, January 09, 2014 9:30 AM
To: Loa Andersson; mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; davi=
d.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
Subject: Re: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in=
-udp was RE: gre-in-udp draft

Hi Loa, et al.,
I think that you're referring to Connectivity Verification in MPLS-TP (RFC =
6428). It would only detect mis-connection but would not count leaked in fr=
ames.

Such problem may be more apparent in Segment Routing (SPRING WG). Perhaps C=
V should be a requirement in SR OAM.

        Regards,
                Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Thursday, January 09, 2014 8:17 AM
To: mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com=
; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp=
 was RE: gre-in-udp draft

Changed the subject line !

On 2014-01-09 20:36, Mark Tinka wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled MPLS.
>
>> I am interested in how often in practice MPLS packets get
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted MPLS frames
> so operators can glean this data. This isn't something I've come
> across, but it would be good to find some kind of way to count this
> across interfaces, if the routers can detect and report them.

This would be possible to do with MPLS-TP OAM, wouldn't it?

/Loa
>
> The known issue about mis-delivery of MPLS frames is poorly- sized MTU
> interfaces. I have no empirical data as to how this can corrupt
> successive MPLS frames that may fit into the transit MTU. But in this
> case, as with any Layer 2 traffic, not enough MTU =3D dropped frame.
>
> Mark.
>

--


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From narten@us.ibm.com  Thu Jan  9 21:53:19 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E198A1ADFB8 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 21:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMzzNiAu4SSK for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 21:53:18 -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 BB4851AD9AC for <ietf@ietf.org>; Thu,  9 Jan 2014 21:53:17 -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, 10 Jan 2014 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, 10 Jan 2014 00:53:04 -0500
Received: from b01cxnp22033.gho.pok.ibm.com (b01cxnp22033.gho.pok.ibm.com [9.57.198.23]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 13AF7C90026 for <ietf@ietf.org>; Fri, 10 Jan 2014 00:53:02 -0500 (EST)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by b01cxnp22033.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0A5r4YN66715704 for <ietf@ietf.org>; Fri, 10 Jan 2014 05:53:04 GMT
Received: from d01av03.pok.ibm.com (localhost [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0A5r4rm024620 for <ietf@ietf.org>; Fri, 10 Jan 2014 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0A5r3Os024599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 10 Jan 2014 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s0A5r3RK029041 for <ietf@ietf.org>; Fri, 10 Jan 2014 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s0A5r3F6028993 for ietf@ietf.org; Fri, 10 Jan 2014 00:53:03 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201401100553.s0A5r3F6028993@rotala.raleigh.ibm.com>
Date: Fri, 10 Jan 2014 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-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14011005-5806-0000-0000-000023D53E92
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 05:53:20 -0000

Total of 228 messages in the last 7 days.
 
script run at: Fri Jan 10 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.02% |   16 | 12.46% |   237981 | hallam@gmail.com
  4.82% |   11 |  5.16% |    98475 | l.wood@surrey.ac.uk
  4.82% |   11 |  4.00% |    76450 | dhc@dcrocker.net
  3.95% |    9 |  3.98% |    75957 | stephen.farrell@cs.tcd.ie
  4.39% |   10 |  3.50% |    66856 | paf@frobbit.se
  3.95% |    9 |  3.58% |    68329 | brian.e.carpenter@gmail.com
  3.51% |    8 |  3.09% |    58963 | scott.brim@gmail.com
  3.51% |    8 |  2.69% |    51313 | jari.arkko@piuha.net
  2.63% |    6 |  2.52% |    48038 | drc@virtualized.org
  2.63% |    6 |  2.19% |    41742 | adrian@olddog.co.uk
  2.19% |    5 |  2.19% |    41747 | lear@cisco.com
  2.19% |    5 |  2.15% |    41119 | john-ietf@jck.com
  1.32% |    3 |  2.76% |    52613 | mariainesrobles@googlemail.com
  2.19% |    5 |  1.71% |    32699 | johnl@taugh.com
  1.75% |    4 |  1.68% |    31995 | abdussalambaryun@gmail.com
  1.75% |    4 |  1.53% |    29204 | sm+ietf@elandsys.com
  0.88% |    2 |  2.36% |    45134 | bclaise@cisco.com
  1.75% |    4 |  1.49% |    28371 | stbryant@cisco.com
  1.75% |    4 |  1.41% |    26858 | morrowc.lists@gmail.com
  1.75% |    4 |  1.31% |    25065 | ajs@anvilwalrusden.com
  1.75% |    4 |  1.29% |    24621 | derhoermi@gmx.net
  1.75% |    4 |  1.27% |    24343 | randy@psg.com
  1.32% |    3 |  1.68% |    32037 | turners@ieca.com
  1.32% |    3 |  1.65% |    31538 | michael.scharf@alcatel-lucent.com
  0.88% |    2 |  2.04% |    38878 | andy@yumaworks.com
  1.32% |    3 |  1.37% |    26189 | narten@us.ibm.com
  1.32% |    3 |  1.28% |    24424 | sm@resistor.net
  1.32% |    3 |  1.15% |    22005 | gih@apnic.net
  1.32% |    3 |  1.13% |    21503 | agmalis@gmail.com
  1.32% |    3 |  1.07% |    20420 | jcurran@istaff.org
  1.32% |    3 |  1.05% |    20002 | ted.lemon@nominum.com
  1.32% |    3 |  1.01% |    19357 | melinda.shore@gmail.com
  1.32% |    3 |  0.96% |    18387 | kent@bbn.com
  1.32% |    3 |  0.86% |    16504 | jnc@mercury.lcs.mit.edu
  0.88% |    2 |  0.80% |    15327 | ned+ietf@mauve.mrochek.com
  0.88% |    2 |  0.73% |    13861 | erosen@cisco.com
  0.88% |    2 |  0.69% |    13158 | mark.tinka@seacom.mu
  0.88% |    2 |  0.67% |    12712 | loa@pi.nu
  0.88% |    2 |  0.67% |    12707 | bmanning@isi.edu
  0.88% |    2 |  0.66% |    12553 | housley@vigilsec.com
  0.88% |    2 |  0.63% |    12049 | tglassey@earthlink.net
  0.88% |    2 |  0.57% |    10849 | chair@ietf.org
  0.88% |    2 |  0.57% |    10801 | simon@josefsson.org
  0.44% |    1 |  0.70% |    13393 | stewe@stewe.org
  0.44% |    1 |  0.69% |    13193 | daedulus@btconnect.com
  0.44% |    1 |  0.68% |    12931 | ron.even.tlv@gmail.com
  0.44% |    1 |  0.64% |    12238 | ggm@algebras.org
  0.44% |    1 |  0.63% |    12054 | david.black@emc.com
  0.44% |    1 |  0.58% |    11035 | superuser@gmail.com
  0.44% |    1 |  0.56% |    10622 | suzworldwide@gmail.com
  0.44% |    1 |  0.53% |    10107 | avri@ella.com
  0.44% |    1 |  0.52% |     9925 | jmh@joelhalpern.com
  0.44% |    1 |  0.51% |     9807 | hsantos@isdg.net
  0.44% |    1 |  0.51% |     9774 | wzhang@cisco.com
  0.44% |    1 |  0.46% |     8827 | ogud@ogud.com
  0.44% |    1 |  0.45% |     8652 | fred@cisco.com
  0.44% |    1 |  0.42% |     7983 | j.schoenwaelder@jacobs-university.de
  0.44% |    1 |  0.41% |     7845 | dave@cridland.net
  0.44% |    1 |  0.41% |     7806 | joelja@bogus.com
  0.44% |    1 |  0.41% |     7790 | paul.hoffman@vpnc.org
  0.44% |    1 |  0.41% |     7776 | tbray@textuality.com
  0.44% |    1 |  0.39% |     7380 | lberger@labn.net
  0.44% |    1 |  0.38% |     7252 | d3e3e3@gmail.com
  0.44% |    1 |  0.36% |     6928 | tjc@ecs.soton.ac.uk
  0.44% |    1 |  0.36% |     6895 | sm@+ietfelandsys.com
  0.44% |    1 |  0.36% |     6881 | andrew.hutton@unify.com
  0.44% |    1 |  0.35% |     6711 | huubatwork@gmail.com
  0.44% |    1 |  0.35% |     6659 | kre@munnari.oz.au
  0.44% |    1 |  0.34% |     6450 | mcr+ietf@sandelman.ca
  0.44% |    1 |  0.33% |     6248 | farinacci@gmail.com
  0.44% |    1 |  0.32% |     6187 | lars@netapp.com
  0.44% |    1 |  0.30% |     5819 | peter@bsdly.net
  0.44% |    1 |  0.30% |     5639 | marka@isc.org
  0.44% |    1 |  0.29% |     5574 | garbakora@gmail.com
  0.44% |    1 |  0.28% |     5341 | worley@ariadne.com
  0.44% |    1 |  0.24% |     4621 | ahmedbakhat@pta.gov.pk
--------+------+--------+----------+------------------------
100.00% |  228 |100.00% |  1909477 | Total


From presnick@qti.qualcomm.com  Thu Jan  9 22:36:50 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30ADC1AD603 for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 22:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.839
X-Spam-Level: 
X-Spam-Status: No, score=-4.839 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c9fNX1ZctD5I for <ietf@ietfa.amsl.com>; Thu,  9 Jan 2014 22:36:48 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id E6E511ACCFE for <ietf@ietf.org>; Thu,  9 Jan 2014 22:36:47 -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=1389335799; x=1420871799; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kNcvzSsFe7lGkcZuFMcbqEeqpO/1T0mfTUgFtslRQ3k=; b=t9jV9P/0BgEQUI7OtEY0bdNALmHynGrCSIo6oYgLp2YVCZhcmBxsPHjc FiaO8sErb021XHQBwW1hl3F4J5ar34ylhlZA21O8c3ERWfExH6HrnmwWt 3NrywmAioWhCivR/lgvebU5LTqxsxX34eVht/D7NExlh+Tf+cgJerm9Xy U=;
X-IronPort-AV: E=McAfee;i="5400,1158,7313"; a="7055338"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine01.qualcomm.com with ESMTP; 09 Jan 2014 22:36:39 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7313"; a="25133122"
Received: from nasanexhc10.na.qualcomm.com ([172.30.48.3]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Jan 2014 22:36:37 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc10.na.qualcomm.com (172.30.48.3) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 22:36:37 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 9 Jan 2014 22:36:36 -0800
Message-ID: <52CF94F2.2060309@qti.qualcomm.com>
Date: Fri, 10 Jan 2014 00:36:34 -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: Upcoming change to announcement email header fields (using old header)
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com> <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.gmail.com> <6.2.5.6.2.20140109103707.0b95b440@resistor.net>
In-Reply-To: <6.2.5.6.2.20140109103707.0b95b440@resistor.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 06:36:50 -0000

On 1/9/14 11:24 AM, John C Klensin wrote:

> However, despite the fact that group syntax, including that for
> empty lists, has been part of the mail header specs for well
> over 30 years, we know that many systems have had trouble with
> messages that contain only an empty group indication.  Those
> systems are not just non-conforming MUA or mailstore
> implementations (or MTAs that violate the SMTP spec and look at
> headers in transit) or antispam systems of various qualities.
> They including a variety of coded and ad hoc mail classification
> and filtering arrangements that may require special arrangements
> for such addresses.   Given the risks and potential problems,
> I'd like to hear a little more justification for switching to
> group syntax...

John, several people were spoken to, including myself, and my 
understanding along with what I heard of the current collective wisdom 
was that the number of such custom coded systems that would be adversely 
affected by an empty group address in the To: field and actual addresses 
in the From: and Reply-To: (albeit the From: containing a bit-bucket 
address) would be exceedingly small and at pretty low risk. So my 
recommendation to the tools team was to go ahead with the experiment.

(As you may have been aware, there was an earlier attempt to change the 
headers of announce messages, but it -- unfortunately -- happened 
without an experimental phase. But most of the problems there had to do 
with normal filters that were unprepared for the change. Hence the 
experimental step this time.)

If we discover problems, we'll figure out something differently. But 
there are downsides to including bogus addresses (as against empty 
groups) in To: fields, so I think this is worth the attempt.

> than the apparent "the IESG  decided on this and is announcing it to the community".
>    

Most of the IESG was not involved in "deciding" this. The tools team 
worked with Barry and I, and we all consulted with other folks (well 
known to you) and recommended the experiment go forward. And to address 
your later comment: We don't want tools work (or other administrative 
activities) to require open IETF list discussions for every change, so 
sometimes the admin folks will consult with senior and experienced 
members of the community and go ahead with experiments of this sort. 
That it came out as an "IESG" announcement in this case is really 
accidental: The tools team asked the IESG for its approval (and the Apps 
ADs' advice) because the email messages at issue were IESG 
announcements. But this was far from some sort of super-secret top-down 
pronouncement. I'm sorry that it appeared that way.

> (3) If someone actually does discover that they have a problem
> and are dependent on a third-party supplier to get it patched, 2
> 1/2 weeks are unlikely to be sufficient.
>    

Fair enough. I think extending the experiment would not be a big deal.

On 1/9/14 12:59 PM, SM wrote:
> My guess about the problem is that people choose "Reply to All".  That 
> generates more mail for iesg-secretary@.  Using a few (sieve) rules 
> might alleviate the problem.

It's not just a "more mail for iesg-secretary@" problem. Email to that 
address goes directly into a ticketing system, which unfortunately 
generates a new ticket if the subject line does not contain the correct 
ticket number. Then the secretariat has to go back and combine the 
tickets if the replies were relevant to the secretariat, or toss them if 
they were replies intended for the IETF list. Furthermore, you get 
bounces generated from the announce list (which persist when you get 
replies to replies), though sometimes you get the random message slip 
through to the announce list because of accidental non-moderation of the 
message. Not all of these can be handled (easily) with a simple sieve 
script.

Again, if the experiment flops, we'll re-group. But I'm somewhat hopeful.

pr

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


From mansaxel@besserwisser.org  Fri Jan 10 00:33:20 2014
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 569571ACC89 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 00:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.439
X-Spam-Level: 
X-Spam-Status: No, score=-4.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S-K0-ni0EtTE for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 00:33:18 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [192.36.115.55]) by ietfa.amsl.com (Postfix) with ESMTP id 464E21AC7F3 for <ietf@ietf.org>; Fri, 10 Jan 2014 00:33:18 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id EB9FD9E62; Fri, 10 Jan 2014 09:33:06 +0100 (CET)
Date: Fri, 10 Jan 2014 09:33:06 +0100
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: John Levine <johnl@taugh.com>
Subject: Re: Multi-homed BCP38
Message-ID: <20140110083306.GI7517@besserwisser.org>
References: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com> <20140109191747.20009.qmail@joyce.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="poJSiGMzRSvrLGLs"
Content-Disposition: inline
In-Reply-To: <20140109191747.20009.qmail@joyce.lan>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 08:33:20 -0000

--poJSiGMzRSvrLGLs
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Multi-homed BCP38 Date: Thu, Jan 09, 2014 at 07:17:47PM -0000 =
Quoting John Levine (johnl@taugh.com):
=20
> Also, if you'll review the messages to which you're responding, you'll
> note that the customer is often an ISP with customers of its own so
> there are far too many ranges to handle manually.

An "ISP" who does not understand and use BGP is probably not serious. Were
I in the business of selling Internet connectivity (and I'm not, I'm a
multihomed customer who does speak BGP with my upstreams) I'd look at such
potential customers with a mixture of suspicion and badly hidden contempt.

Which is not constructive,  quarter-of-year-cash-flow-wise, but it is
indeed better for the Internet. IMNSHO. And, in the long run, there is
a definitive cost associated with running crap setups like multihoming
without a proper dynamic routing protocol.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
I can't decide which WRONG TURN to make first!!  I wonder if BOB
GUCCIONE has these problems!

--poJSiGMzRSvrLGLs
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iEYEARECAAYFAlLPsEIACgkQ02/pMZDM1cX9hQCfYIO0QowO4F1Bql8Euvt9iL+e
t3MAnipctsDY3aJAH/AOu8dFToVJubLD
=FwbO
-----END PGP SIGNATURE-----

--poJSiGMzRSvrLGLs--

From lars@netapp.com  Fri Jan 10 00:47:47 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2241AD0F0; Fri, 10 Jan 2014 00:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id scnrZ1SSCbdp; Fri, 10 Jan 2014 00:47:46 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id EC1D51A9313; Fri, 10 Jan 2014 00:47:45 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,637,1384329600";  d="asc'?scan'208";a="95233738"
Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx11-out.netapp.com with ESMTP; 10 Jan 2014 00:47:36 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Fri, 10 Jan 2014 00:47:35 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gA==
Date: Fri, 10 Jan 2014 08:47:35 +0000
Message-ID: <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_83EDAABB-5D4B-4EB6-8739-F7B6E64D302C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 08:47:47 -0000

--Apple-Mail=_83EDAABB-5D4B-4EB6-8739-F7B6E64D302C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

that sounds good. What congestion control are you going to be specifying =
for your tunnel?

Lars

On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:

> Hi Lars,
>=20
> Thanks a lot for your comments.
>=20
> I wonder whether the following modified text for Congestion =
Consideration section is OK from your point of view:
>=20
> Since the MPLS-in-UDP encapsulation causes MPLS packets to be =
forwarded through "UDP tunnels", the congestion control guidelines for =
UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. =
Specifically, MPLS can carry a number of different protocols as =
payloads. When the payload traffic is IP-based and =
congestion-controlled, the UDP tunnel SHOULD NOT employ its own =
congestion control mechanism, because congestion losses of tunneled =
traffic will already trigger an appropriate congestion response at the =
original senders of the tunneled traffic. When the payload traffic is =
not known to be IP-based, or is known to be IP-based but not =
congestion-controlled, the UDP tunnel SHOULD employ an appropriate =
congestion control mechanism. Furthermore, because UDP tunnels are =
usually bulk-transfer applications as far as the intermediate routers =
are concerned, the guidelines as defined in Section 3.1.1 of [RFC5405] =
SHOULD apply.
>=20
> Best regards,
> Xiaohu
>=20
>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>> =B7=A2=BC=FE=C8=CB: mpls [mailto:mpls-bounces@ietf.org] =B4=FA=B1=ED =
Eggert, Lars
>> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA1=D4=C28=C8=D5 18:22
>> =CA=D5=BC=FE=C8=CB: IETF
>> =B3=AD=CB=CD: mpls@ietf.org
>> =D6=F7=CC=E2: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> =
(Encapsulating MPLS
>> in UDP) to Proposed Standard
>>=20
>> Hi,
>>=20
>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
>>> - 'Encapsulating MPLS in UDP'
>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
>>=20
>>=20
>> this document needs to describe how it addresses the issues raised in =
BCP145
>> (RFC5405). It already contains some text about messages sizes and =
congestion
>> considerations, which is great. Unfortunately, the text about =
congestion
>> considerations is not fully in line with RFC5405.
>>=20
>> Lars


--Apple-Mail=_83EDAABB-5D4B-4EB6-8739-F7B6E64D302C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUs+zpNZcnpRveo1xAQI5UwP/UXw1WuO+svt2Ths4EVAoNk1bxViGvtj8
8BVNQWdO2x9+99SO08qE2unslZJLdE7CiIQqKhbepSw3DIy2zXXjtNRj8tmDLvTt
cTaMq7CRnwvf48202Yklmy2xCQ2PgT4qa3M8yJ3QPp12ejEqi3SFQWC8dIh4+UDL
6l2K3HMkK+Q=
=T5qM
-----END PGP SIGNATURE-----

--Apple-Mail=_83EDAABB-5D4B-4EB6-8739-F7B6E64D302C--

From stbryant@cisco.com  Fri Jan 10 01:16:09 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B24341ADBE5; Fri, 10 Jan 2014 01:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.25
X-Spam-Level: 
X-Spam-Status: No, score=-7.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_CHARSET_FARAWAY=2.45, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F5WWUgbbWk6U; Fri, 10 Jan 2014 01:16:07 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id A9D201ACCFF; Fri, 10 Jan 2014 01:16:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2578; q=dns/txt; s=iport; t=1389345357; x=1390554957; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uMgQFsVuArum1DXQg86uzbpQK6+XtgZVztJ0skbJ8SA=; b=L7EBd4RK/Ix02bMXEM0Om7A3xKzA2PBWu6EwOnFvbQXBa/PCCZgwuGLA AsbCmzWQ6gakTD2yx2DT76g0Qv5NCmwJiWyDXP9wItGaW+J/ejVrAli/4 1HOYQEl2NKpy6FqJMo+rysYlUNwdw8VdPhO0yeP+Snh1KWXy8ta8bx3v2 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FABm5z1KQ/khM/2dsb2JhbABZgws4g1S2QoEHFnSCJQEBAQQBAQFrCgEQCQIYBAUWBAQFAgkDAgECARUfEQYBCQMBBQIBAYgADYxGm2sImngXgSWNLTMHgmuBTASJEI8HkhWBb4E+
X-IronPort-AV: E=Sophos;i="4.95,637,1384300800";  d="scan'208";a="2762080"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 10 Jan 2014 09:15:56 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0A9Ftdp015696 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jan 2014 09:15:55 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0A9Frcj006408; Fri, 10 Jan 2014 09:15:54 GMT
Message-ID: <52CFBA49.8070500@cisco.com>
Date: Fri, 10 Jan 2014 09:15:53 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Xuxiaohu <xuxiaohu@huawei.com>, "Eggert, Lars" <lars@netapp.com>, IETF <ietf@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 09:16:09 -0000

RFC3985/6.5.  Congestion Considerations
may have some useful text.=20

We have a lot of deployment experience with
PWs and frankly I have never seen a congestion
complain raised from the field.

Stewart



On 10/01/2014 03:46, Xuxiaohu wrote:
> Hi Lars,
>
> Thanks a lot for your comments.
>
> I wonder whether the following modified text for Congestion Considerati=
on section is OK from your point of view:
>
> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarded=
 through "UDP tunnels", the congestion control guidelines for UDP tunnels=
 as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specificall=
y, MPLS can carry a number of different protocols as payloads. When the p=
ayload traffic is IP-based and congestion-controlled, the UDP tunnel SHOU=
LD NOT employ its own congestion control mechanism, because congestion lo=
sses of tunneled traffic will already trigger an appropriate congestion r=
esponse at the original senders of the tunneled traffic. When the payload=
 traffic is not known to be IP-based, or is known to be IP-based but not =
congestion-controlled, the UDP tunnel SHOULD employ an appropriate conges=
tion control mechanism. Furthermore, because UDP tunnels are usually bulk=
-transfer applications as far as the intermediate routers are concerned, =
the guidelines as defined in Section 3.1.1 of [RFC5405] SHOULD apply.
>
> Best regards,
> Xiaohu
>
>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
>> =B7=A2=BC=FE=C8=CB: mpls [mailto:mpls-bounces@ietf.org] =B4=FA=B1=ED E=
ggert, Lars
>> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA1=D4=C28=C8=D5 18:22
>> =CA=D5=BC=FE=C8=CB: IETF
>> =B3=AD=CB=CD: mpls@ietf.org
>> =D6=F7=CC=E2: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (E=
ncapsulating MPLS
>> in UDP) to Proposed Standard
>>
>> Hi,
>>
>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
>>> - 'Encapsulating MPLS in UDP'
>>>  <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
>>
>> this document needs to describe how it addresses the issues raised in =
BCP145
>> (RFC5405). It already contains some text about messages sizes and cong=
estion
>> considerations, which is great. Unfortunately, the text about congesti=
on
>> considerations is not fully in line with RFC5405.
>>
>> Lars
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


--=20
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From stbryant@cisco.com  Fri Jan 10 02:04:15 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5A461ACC82 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 02:04:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5zPxHJM69O-U for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 02:04:13 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id C6EC31ADF23 for <ietf@ietf.org>; Fri, 10 Jan 2014 02:04:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=20137; q=dns/txt; s=iport; t=1389348242; x=1390557842; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=EhZd3wsZKoLXe1QpG0CBvLlV14Q9TVG2tuEDPLor2u8=; b=T2ngzGb5yTB+GSS/FYeFpnOJwsuiGCKEH3xAd3P/G+5oBYGsXOZ2+4GZ x7jzDWyjfxwAq0LGznscY/IPGquo4LGRJG5/CrYHT6PEc9iPW6Vf7vzde 3KVGJWsCLRq55NL1D5Wz2mpYrCx5fZoQ7dgVIcTuph8cG1pRIxo/dbJei Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FADXEz1KQ/khR/2dsb2JhbABZgws4uheBBxZ0giUBAQEEAQEBawoBEAsOAwMBAgEJFgEDBAcJAwIBAgEPBh8JCAYBDAEFAgEBh2wDEQ2+Bw2FIReMcoExCgEGAS4REQYBBoJPgWIElDOBeIFsjFqFO4FvgT6BaAEIFw
X-IronPort-AV: E=Sophos;i="4.95,637,1384300800"; d="scan'208,217";a="3435008"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 10 Jan 2014 10:04:01 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0AA405J018873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jan 2014 10:04:01 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0AA3uv8009141; Fri, 10 Jan 2014 10:03:57 GMT
Message-ID: <52CFC58C.3020000@cisco.com>
Date: Fri, 10 Jan 2014 10:03:56 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ines Robles <mariainesrobles@googlemail.com>, ietf <ietf@ietf.org>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
References: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com>
In-Reply-To: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000901000705000007030600"
Cc: S Moonesamy <sm+ietf@elandsys.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 10:04:16 -0000

This is a multi-part message in MIME format.
--------------000901000705000007030600
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 10/01/2014 01:16, Ines Robles wrote:
> *
>
> Hello,
>
> *
> *
>
> The IESG approvedthe draft-moonesamy-ietf-conduct-3184bis-06 
> <https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/>, 
> including these new changes:
>
>
> Section 3 (foreseeable was replaced by foreseen)
>
>
> OLD:
>
>
> “However it is to be noted that there is an expectation that no one 
> shall ever knowingly contribute advice or
>   text that may affect the security of the Internet without describing 
> all known or foreseeable risks and threats to potential implementers 
> and users. ”
>
>
> NEW:
>
>
> “However it is to be noted that there is an expectation that no one 
> shall ever knowingly contribute advice or
>   text that may affect the security of the Internet without describing 
> all known or foreseenrisks and threats to potential implementers and 
> users. ”
>
> *
Surely the best you can hope for is:

*"..without describing all **of the **actual and potential risks and 
threats to implementers and users that they are aware of."

*The advice is by definition a best effort service.*

*- Stewart*
*
> *
>
> Section 4:
>
>
> The word "adversely" which was added to the last sentence in Section 4.
>
>
>
> Please note, that due to this new version, the AD give until Tuesday 
> next week to provide comments before send the draft to the RFC Editor.
>
>
>
> Thank you and Kind Regards,
>
>
> Ines Robles.
>
>
> *
>
>
> 2013/11/8 <ietf-request@ietf.org <mailto:ietf-request@ietf.org>>
>
>
>        5. Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>           (IETF     Guidelines for Conduct) to Best Current Practice
>           (Brian E Carpenter)
>
>
>     ------------------------------
>
>     Message: 5
>     Date: Sat, 09 Nov 2013 08:33:14 +1300
>     From: Brian E Carpenter <brian.e.carpenter@gmail.com
>     <mailto:brian.e.carpenter@gmail.com>>
>     To: S Moonesamy <sm+ietf@elandsys.com <mailto:sm%2Bietf@elandsys.com>>
>     Cc: ietf@ietf.org <mailto:ietf@ietf.org>
>     Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt>
>             (IETF   Guidelines for Conduct) to Best Current Practice
>     Message-ID: <527D3C7A.1060200@gmail.com
>     <mailto:527D3C7A.1060200@gmail.com>>
>     Content-Type: text/plain; charset=UTF-8
>
>     That works for me.
>
>     Thanks
>        Brian
>
>     On 09/11/2013 07:03, S Moonesamy wrote:
>     > Hi Brian,
>     > At 18:58 07-11-2013, Brian E Carpenter wrote:
>     >> Fair enough. But people do need to respect the shortage of
>     time. How
>     >> about
>     >> "Working Group meetings run on a very limited time schedule,
>     >> and sometimes participants have to limit their questions.
>     >> The work of the group will continue on the mailing list, and
>     >> questions can be asked and answered on the list."
>     >
>     > How about:
>     >
>     >    IETF participants read the relevant Internet-Drafts, RFCs, and
>     >    email archives beforehand, in order to familiarize themselves
>     >    with the technology under discussion.  Working Group sessions
>     >    run on a very limited time schedule, and sometimes participants
>     >    have to limit their questions.  The work of the group will
>     >    continue on the mailing list, and questions can be asked and
>     >    answered on the mailing list.  It can be a challenge when
>     >    attending a new working group without knowing the history of
>     >    longstanding Working Group debates.  Information about a working
>     >    group including its charter and milestones is available on the
>     >    IETF Tools web site [TOOLS] or from the working group chair.
>     >
>     > Regards,
>     > S. Moonesamy
>     > .
>     >
>
>
>     ------------------------------
>
>     _______________________________________________
>     ietf mailing list
>     ietf@ietf.org <mailto:ietf@ietf.org>
>     https://www.ietf.org/mailman/listinfo/ietf
>
>
>     End of ietf Digest, Vol 66, Issue 60
>     ************************************
>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------000901000705000007030600
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 10/01/2014 01:16, Ines Robles wrote:<br>
    </div>
    <blockquote
cite="mid:CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr"><b
          id="docs-internal-guid-5e9fc2de-79ad-cd51-2059-b96428f529ff"
          style="font-weight:normal">
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Hello,</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif">
            <div><b style="font-weight:normal"><font color="#000000"
                  face="arial, helvetica, sans-serif"><br>
                </font></b></div>
          </font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt">
            <font color="#000000" face="arial, helvetica, sans-serif"><span
                style="vertical-align:baseline;white-space:pre-wrap">The
                IESG </span><span
                style="vertical-align:baseline;white-space:pre-wrap">approved</span><span
                style="vertical-align:baseline;white-space:pre-wrap">
                the <a moz-do-not-send="true"
href="https://datatracker.ietf.org/doc/draft-moonesamy-ietf-conduct-3184bis/">draft-moonesamy-ietf-conduct-3184bis-06</a>,
                including these new changes:</span></font></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Section
                3 (foreseeable was replaced by foreseen)</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">OLD:</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">“However
                it is to be noted that there is an expectation that no
                one shall ever knowingly contribute advice or<br
                  class="">
                  text that may affect the security of the Internet
                without describing all known or foreseeable risks and
                threats to potential implementers and users. ”</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">NEW:
              </font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><font
              color="#000000" face="arial, helvetica, sans-serif"><span
                style="vertical-align:baseline;white-space:pre-wrap">“However
                it is to be noted that there is an expectation that no
                one shall ever knowingly contribute advice or<br
                  class="">
                  text that may affect the security of the Internet
                without describing all known or </span><span
                style="vertical-align:baseline;white-space:pre-wrap">foreseen</span><span
                style="vertical-align:baseline;white-space:pre-wrap">
                risks and threats to potential implementers and users. ”</span></font></p>
        </b></div>
    </blockquote>
    <font face="arial, helvetica, sans-serif">Surely the best you can
      hope for is:<br>
      <br>
    </font><b><span style="font-weight:normal"><font color="#000000"
          face="arial, helvetica, sans-serif"><span
            style="vertical-align:baseline;white-space:pre-wrap">"..without
            describing all </span></font></span></b><b><span
        style="font-weight:normal"><font color="#000000" face="arial,
          helvetica, sans-serif"><span
            style="vertical-align:baseline;white-space:pre-wrap">of the
          </span></font></span></b><b><span style="font-weight:normal"><font
          color="#000000" face="arial, helvetica, sans-serif"><span
            style="vertical-align:baseline;white-space:pre-wrap"></span><span
            style="vertical-align:baseline;white-space:pre-wrap">actual
            and potential risks and threats to implementers and users
            that they are aware of."<br>
            <br>
          </span></font></span></b><span style="font-weight:normal"><font
        color="#000000" face="arial, helvetica, sans-serif"><span
          style="vertical-align:baseline;white-space:pre-wrap">The
          advice is by definition a best effort service.</span></font></span><b><span
        style="font-weight:normal"><font color="#000000" face="arial,
          helvetica, sans-serif"><span
            style="vertical-align:baseline;white-space:pre-wrap"><br>
            <br>
          </span></font></span></b><span style="font-weight:normal"><font
        color="#000000" face="arial, helvetica, sans-serif"><span
          style="vertical-align:baseline;white-space:pre-wrap">- Stewart</span></font></span><b><span
        style="font-weight:normal"><font color="#000000" face="arial,
          helvetica, sans-serif"><span
            style="vertical-align:baseline;white-space:pre-wrap"><br>
          </span></font></span></b>
    <blockquote
cite="mid:CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com"
      type="cite">
      <div dir="ltr"><b
          id="docs-internal-guid-5e9fc2de-79ad-cd51-2059-b96428f529ff"
          style="font-weight:normal">
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Section
                4:</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">The
                word "adversely" which was added to the last sentence in
                Section 4.</font></span></p>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif"><br>
              </font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Please
                note, that due to this new version, the AD give until
                Tuesday next week to provide comments before send the
                draft to the RFC Editor.</font></span></p>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif"><br>
              </font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Thank
                you and Kind Regards,</font></span></p>
          <font color="#000000" face="arial, helvetica, sans-serif"><br>
            <span style="vertical-align:baseline;white-space:pre-wrap"></span></font>
          <p dir="ltr"
            style="line-height:1.15;margin-top:0pt;margin-bottom:0pt"><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif">Ines
                Robles.</font></span></p>
          <div><span
              style="vertical-align:baseline;white-space:pre-wrap"><font
                color="#000000" face="arial, helvetica, sans-serif"><br>
              </font></span></div>
        </b>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">2013/11/8 <span dir="ltr">&lt;<a
                moz-do-not-send="true"
                href="mailto:ietf-request@ietf.org" target="_blank">ietf-request@ietf.org</a>&gt;</span><br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
                 5. Re: Last Call:
              &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt;<br>
                    (IETF     Guidelines for Conduct) to Best Current
              Practice<br>
                    (Brian E Carpenter)<br>
              <br>
              <br>
              ------------------------------<br>
              <br>
              Message: 5<br>
              Date: Sat, 09 Nov 2013 08:33:14 +1300<br>
              From: Brian E Carpenter &lt;<a moz-do-not-send="true"
                href="mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
              To: S Moonesamy &lt;<a moz-do-not-send="true"
                href="mailto:sm%2Bietf@elandsys.com">sm+ietf@elandsys.com</a>&gt;<br>
              Cc: <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a><br>
              Subject: Re: Last Call:
              &lt;draft-moonesamy-ietf-conduct-3184bis-03.txt&gt;<br>
                      (IETF   Guidelines for Conduct) to Best Current
              Practice<br>
              Message-ID: &lt;<a moz-do-not-send="true"
                href="mailto:527D3C7A.1060200@gmail.com">527D3C7A.1060200@gmail.com</a>&gt;<br>
              Content-Type: text/plain; charset=UTF-8<br>
              <br>
              That works for me.<br>
              <br>
              Thanks<br>
                 Brian<br>
              <br>
              On 09/11/2013 07:03, S Moonesamy wrote:<br>
              &gt; Hi Brian,<br>
              &gt; At 18:58 07-11-2013, Brian E Carpenter wrote:<br>
              &gt;&gt; Fair enough. But people do need to respect the
              shortage of time. How<br>
              &gt;&gt; about<br>
              &gt;&gt; "Working Group meetings run on a very limited
              time schedule,<br>
              &gt;&gt; and sometimes participants have to limit their
              questions.<br>
              &gt;&gt; The work of the group will continue on the
              mailing list, and<br>
              &gt;&gt; questions can be asked and answered on the list."<br>
              &gt;<br>
              &gt; How about:<br>
              &gt;<br>
              &gt;    IETF participants read the relevant
              Internet-Drafts, RFCs, and<br>
              &gt;    email archives beforehand, in order to familiarize
              themselves<br>
              &gt;    with the technology under discussion.  Working
              Group sessions<br>
              &gt;    run on a very limited time schedule, and sometimes
              participants<br>
              &gt;    have to limit their questions.  The work of the
              group will<br>
              &gt;    continue on the mailing list, and questions can be
              asked and<br>
              &gt;    answered on the mailing list.  It can be a
              challenge when<br>
              &gt;    attending a new working group without knowing the
              history of<br>
              &gt;    longstanding Working Group debates.  Information
              about a working<br>
              &gt;    group including its charter and milestones is
              available on the<br>
              &gt;    IETF Tools web site [TOOLS] or from the working
              group chair.<br>
              &gt;<br>
              &gt; Regards,<br>
              &gt; S. Moonesamy<br>
              &gt; .<br>
              &gt;<br>
              <br>
              <br>
              ------------------------------<br>
              <br>
              _______________________________________________<br>
              ietf mailing list<br>
              <a moz-do-not-send="true" href="mailto:ietf@ietf.org">ietf@ietf.org</a><br>
              <a moz-do-not-send="true"
                href="https://www.ietf.org/mailman/listinfo/ietf"
                target="_blank">https://www.ietf.org/mailman/listinfo/ietf</a><br>
              <br>
              <br>
              End of ietf Digest, Vol 66, Issue 60<br>
              ************************************<br>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------000901000705000007030600--

From john-ietf@jck.com  Fri Jan 10 02:17:56 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F20671ADF7F for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 02:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndOaUPcSPYQN for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 02:17:53 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 882A21ADD9A for <ietf@ietf.org>; Fri, 10 Jan 2014 02:17:53 -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 1W1Z9b-000App-JI; Fri, 10 Jan 2014 05:17:27 -0500
Date: Fri, 10 Jan 2014 05:17:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, SM <sm@resistor.net>
Subject: Re: Upcoming change to announcement email header fields (using old header)
Message-ID: <DA016D4BFE21D7D3C0746C48@JcK-HP8200.jck.com>
In-Reply-To: <52CF94F2.2060309@qti.qualcomm.com>
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com> <CAKHUCzwcVsZOpY54zE0Xa0Aain=PiCzxgke-=bbC4vo_B=8g4w@mail.gmail.com> <6.2.5.6.2.20140109103707.0b95b440@resistor.net> <52CF94F2.2060309@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 10:17:56 -0000

--On Friday, January 10, 2014 00:36 -0600 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> On 1/9/14 11:24 AM, John C Klensin wrote:
> 
>> However, despite the fact that group syntax, including that
>> for empty lists, has been part of the mail header specs for
>> well over 30 years, we know that many systems have had
>> trouble with messages that contain only an empty group
>> indication.  Those systems are not just non-conforming MUA or
>> mailstore implementations (or MTAs that violate the SMTP spec
>> and look at headers in transit) or antispam systems of
>> various qualities. They including a variety of coded and ad
>> hoc mail classification and filtering arrangements that may
>> require special arrangements for such addresses.   Given the
>> risks and potential problems, I'd like to hear a little more
>> justification for switching to group syntax...
> 
> John, several people were spoken to, including myself, and my
> understanding along with what I heard of the current
> collective wisdom was that the number of such custom coded
> systems that would be adversely affected by an empty group
> address in the To: field and actual addresses in the From: and
> Reply-To: (albeit the From: containing a bit-bucket address)
> would be exceedingly small and at pretty low risk. So my
> recommendation to the tools team was to go ahead with the
> experiment.

If this is an experiment, the announcement doesn't make that
clear.  There is no statement of how to report issues that can't
easily be fixed, etc., just a date certain for the switchover.

As to "exceedingly small", are you measuring percentages?
Absolute numbers?  How many contributors and reviewers is the
IESG prepared to lose if they can't get announcements with a
reasonable amount of effort?  A few hundred (a small number
relative to the size of the IETF-Announce distribution)?  A few
dozen (an "exceedingly small" number on the same scale)?  Ten?

>...
 
>> than the apparent "the IESG  decided on this and is
>> announcing it to the community".

> Most of the IESG was not involved in "deciding" this. The
> tools team worked with Barry and I, and we all consulted with
> other folks (well known to you) and recommended the experiment
> go forward. And to address your later comment: We don't want
> tools work (or other administrative activities) to require
> open IETF list discussions for every change, so sometimes the
> admin folks will consult with senior and experienced members
> of the community and go ahead with experiments of this sort.
> That it came out as an "IESG" announcement in this case is
> really accidental: The tools team asked the IESG for its
> approval (and the Apps ADs' advice) because the email messages
> at issue were IESG announcements. But this was far from some
> sort of super-secret top-down pronouncement. I'm sorry that it
> appeared that way.
 
>> (3) If someone actually does discover that they have a problem
>> and are dependent on a third-party supplier to get it
>> patched, 2 1/2 weeks are unlikely to be sufficient.

> Fair enough. I think extending the experiment would not be a
> big deal.

Again, the announcement didn't imply an experiment to me, only a
"here it comes, get ready or be prepared to lose" declaration.

> On 1/9/14 12:59 PM, SM wrote:
>> My guess about the problem is that people choose "Reply to
>> All".  That  generates more mail for iesg-secretary@.  Using
>> a few (sieve) rules  might alleviate the problem.
> 
> It's not just a "more mail for iesg-secretary@" problem. Email
> to that address goes directly into a ticketing system, which
> unfortunately generates a new ticket if the subject line does
> not contain the correct ticket number. Then the secretariat
> has to go back and combine the tickets if the replies were
> relevant to the secretariat, or toss them if they were replies
> intended for the IETF list. Furthermore, you get bounces
> generated from the announce list (which persist when you get
> replies to replies), though sometimes you get the random
> message slip through to the announce list because of
> accidental non-moderation of the message. Not all of these can
> be handled (easily) with a simple sieve script.

It also creates the impression that the IESG Secretary is
responsible for the announcement and that messages questioning
the contents of the announcement should be sent to that address.
No accidents involved.  As you may know, I made that assumption
after a perceived problem some days ago and, assuming that "IESG
Secretary" was actually a human (she certainly was the last time
I talked with her), even copied the "action" address, thereby
generating two tickets.   So putting that particular address
there is clearly a bad idea.  But that conclusion justifies the
new "noreply" address and an ingress filter at ietf.org which
discards any mail sent to that address, not the rest of the
changes.

> Again, if the experiment flops, we'll re-group. But I'm
> somewhat hopeful.

Thanks for the reply.

   best,
     john



From daedulus@btconnect.com  Fri Jan 10 04:43:43 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C56571ADFC5 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 04:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hiI1QlzXBlp1 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 04:43:42 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe001.messaging.microsoft.com [65.55.88.11]) by ietfa.amsl.com (Postfix) with ESMTP id 16CB11ADF66 for <ietf@ietf.org>; Fri, 10 Jan 2014 04:43:41 -0800 (PST)
Received: from mail174-tx2-R.bigfish.com (10.9.14.235) by TX2EHSOBE008.bigfish.com (10.9.40.28) with Microsoft SMTP Server id 14.1.225.22; Fri, 10 Jan 2014 12:43:31 +0000
Received: from mail174-tx2 (localhost [127.0.0.1])	by mail174-tx2-R.bigfish.com (Postfix) with ESMTP id 9480A100157;	Fri, 10 Jan 2014 12:43:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -17
X-BigFish: PS-17(zz62a3I98dI9371I936eI542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah1fc6hzz1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h2327h2336h2438h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(199002)(189002)(252514010)(377424004)(377454003)(51704005)(13464003)(24454002)(87976001)(88136002)(77096001)(85852003)(85306002)(14496001)(19580405001)(80976001)(87266001)(84392001)(76786001)(83322001)(83072002)(19580395003)(90146001)(33646001)(56816005)(51856001)(4396001)(87286001)(81342001)(77156001)(69226001)(89996001)(74662001)(46102001)(76482001)(74502001)(50226001)(47446002)(59766001)(77982001)(62236002)(54316002)(79102001)(56776001)(44716002)(23756003)(53806001)(62966002)(31966008)(50466002)(76796001)(74876001)(81542001)(63696002)(42186004)(44736004)(74366001)(49866001)(50986001)(47976001)(74706001)(47776003)(92566001)(92726001)(65816001)(47736001)(61296002)(80022001)(66066001)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB252; H:DB3PRD0210HT003.eurprd02.prod.outlook.com; CLIP:157.56.253.69; FPR:; RD:InfoNoRecords; A:0; MX:1; LANG:en; 
Received: from mail174-tx2 (localhost.localdomain [127.0.0.1]) by mail174-tx2 (MessageSwitch) id 1389357810214525_3547; Fri, 10 Jan 2014 12:43:30 +0000 (UTC)
Received: from TX2EHSMHS005.bigfish.com (unknown [10.9.14.241])	by mail174-tx2.bigfish.com (Postfix) with ESMTP id 2E3623C0049; Fri, 10 Jan 2014 12:43:30 +0000 (UTC)
Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by TX2EHSMHS005.bigfish.com (10.9.99.105) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 10 Jan 2014 12:43:29 +0000
Received: from DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) by AM2PRD0710HT004.eurprd07.prod.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.395.1; Fri, 10 Jan 2014 12:43:16 +0000
Received: from DB3PRD0210HT003.eurprd02.prod.outlook.com (157.56.253.69) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.842.7; Fri, 10 Jan 2014 12:43:15 +0000
Message-ID: <00af01cf0e00$fb3b7380$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Loa Andersson <loa@pi.nu>, <stbryant@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu>
Subject: Re: misdelivered mpls packets - Was: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Date: Fri, 10 Jan 2014 12:39:10 +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.69]
X-ClientProxiedBy: DBXPR07CA008.eurprd07.prod.outlook.com (10.255.191.166) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 00872B689F
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: gorry@erg.abdn.ac.uk, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 12:43:44 -0000

----- Original Message -----
From: "Loa Andersson" <loa@pi.nu>
To: <mark.tinka@seacom.mu>; <stbryant@cisco.com>
Cc: <gorry@erg.abdn.ac.uk>; <mpls@ietf.org>; <ietf@ietf.org>;
<david.black@emc.com>; <tsvwg@ietf.org>; <jnc@mit.edu>; <lisp@ietf.org>
Sent: Thursday, January 09, 2014 4:16 PM
> Changed the subject line !
<trimmed the distribution>
>
> On 2014-01-09 20:36, Mark Tinka wrote:
> > On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> > wrote:
> >
> >> Either or both.
> >
> > I can only speak to native MPLS, as I've never run tunneled
> > MPLS.
> >
> >> I am interested in how often in practice MPLS packets get
> >> misdelivered due to label corruption.
> >
> > Well, first of all, routers would need to report corrupted
> > MPLS frames so operators can glean this data. This isn't
> > something I've come across, but it would be good to find
> > some kind of way to count this across interfaces, if the
> > routers can detect and report them.
>
> This would be possible to do with MPLS-TP OAM, wouldn't it?

I think not.  There was a lot of discussion back in 2008/2009 on the
MPLS-TP list about the loss of source address information in MPLS and
how that could be fixed in MPLS but AFAIK nothing was done about it.

At the time, it was misconfiguration defects that were the motivation -
a packet arrives at the wrong place but how on earth can you tell who
sent it and so tell them about it? - but an MPLS label corrupted in
transit would do just as well.

At the same time, I remember well the nervousness of switching from X.25
to Frame Relay, where the assumption was that links were so reliable
that error detection and recovery could safely be left to the higher
layers, that it was no longer needed at the link layer.  That
nervousness seems not to have been justified; perhaps it is not now.

Tom Petch







> /Loa
> >
> > The known issue about mis-delivery of MPLS frames is poorly-
> > sized MTU interfaces. I have no empirical data as to how
> > this can corrupt successive MPLS frames that may fit into
> > the transit MTU. But in this case, as with any Layer 2
> > traffic, not enough MTU = dropped frame.
> >
> > Mark.
> >
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
>



From prvs=0080583cfb=johnl@taugh.com  Fri Jan 10 06:12:25 2014
Return-Path: <prvs=0080583cfb=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ABA61AE081 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 06:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.492
X-Spam-Level: 
X-Spam-Status: No, score=-1.492 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, MIME_8BIT_HEADER=0.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xXtPtfjk6PE7 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 06:12:24 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id DB19F1ADF90 for <ietf@ietf.org>; Fri, 10 Jan 2014 06:12:23 -0800 (PST)
Received: (qmail 80955 invoked from network); 10 Jan 2014 14:12:12 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 10 Jan 2014 14:12:12 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=16679.52cfffbc.k1312; i=johnl%iecc.com@submit.iecc.com; bh=y0oaYPr3PFU0PrRun95TxWsXIEdYc9ewY6+Kwl/AEe4=; b=fzXWlSTDcbLATNnO4W96ruty+rfQGqZ/rtljT/9QhGhP0XCyK87W0M+XgAHPOeMK04myF8GDVYLQyYeTZd5tHrFwcNE2EJoxKrq2k8oVwcKQiXvscLNfBea1l+36Uvso+2ujkopsWq1IMFnBNsuTPU/C3T/PpBGLvfpHSN1N6odAWe7NWsJ5yer30ODoanUQAX8xrMln6KxVuZFZhvOBOJkZYK1g/T5CzmIlcYvJpRIc5+vID4fWUin60NDv0vCd
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=16679.52cfffbc.k1312; olt=johnl%iecc.com@submit.iecc.com; bh=y0oaYPr3PFU0PrRun95TxWsXIEdYc9ewY6+Kwl/AEe4=; b=lLrdFX5AuPsIv0g143WNTRKHuPuPoeI3mKW3w1QY4i/lQrSy6SBFXsgQ0idb7SGZDYryZJlfj5B/ukhKn84l1nzwAJMtLPd3XtrUVnXeZvq6NqNIXFutAXdeQHWabGVYyUPfKNr3Y5FKwcUDLohFThlnIkBeGSEJD0o5bFQxy98tKJCWPmVyYAzkQDWoJNv3aZjMTn+etBJ3hxTUzhif/OglsXbEYYI7Ain6LZ23lkQmUBJS+HYgc4M75kH1JbDY
Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 10 Jan 2014 14:12:12 -0000
Date: 10 Jan 2014 09:12:11 -0500
Message-ID: <alpine.BSF.2.00.1401100911270.14012@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "=?UTF-8?Q?M=C3=A5ns_Nilsson?=" <mansaxel@besserwisser.org>
Subject: Re: Multi-homed BCP38
In-Reply-To: <20140110083306.GI7517@besserwisser.org>
References: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com> <20140109191747.20009.qmail@joyce.lan> <20140110083306.GI7517@besserwisser.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 14:12:25 -0000

> Subject: Re: Multi-homed BCP38 Date: Thu, Jan 09, 2014 at 07:17:47PM -0000 Quoting John Levine (johnl@taugh.com):
>
>> Also, if you'll review the messages to which you're responding, you'll
>> note that the customer is often an ISP with customers of its own so
>> there are far too many ranges to handle manually.
>
> An "ISP" who does not understand and use BGP is probably not serious.

It must be nice to live in a world where you can turn away customers who 
pay a lot of money, just because they're not serious enough.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

From jmh@joelhalpern.com  Fri Jan 10 07:37:05 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D1A21AE09E; Fri, 10 Jan 2014 07:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.887
X-Spam-Level: 
X-Spam-Status: No, score=0.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CKGWm1xEdHDa; Fri, 10 Jan 2014 07:37:00 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 7312D1AE08E; Fri, 10 Jan 2014 07:37:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id D78DB6200B8; Fri, 10 Jan 2014 07:36:50 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E83231C02DA; Fri, 10 Jan 2014 07:36:42 -0800 (PST)
Message-ID: <52D01383.2080509@joelhalpern.com>
Date: Fri, 10 Jan 2014 10:36:35 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>
In-Reply-To: <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 15:37:05 -0000

Maybe I am completely missing things, but this looks wrong.
If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
control will make it more likely that the service won't work.  Is that
really the goal?

We do not perform congestion control on MPLS LSPs.
Assuming that a UDP tunnel is carrying just MPLS and was established
just for MPLS, why would we expect it to behave differently than an MPLS
LSP running over the exact same path, carrying the exact same traffic?

Yours,
Joel

On 1/10/14 3:47 AM, Eggert, Lars wrote:
> Hi,
> 
> that sounds good. What congestion control are you going to be specifying for your tunnel?
> 
> Lars
> 
> On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> 
>> Hi Lars,
>>
>> Thanks a lot for your comments.
>>
>> I wonder whether the following modified text for Congestion Consideration section is OK from your point of view:
>>
>> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarded through "UDP tunnels", the congestion control guidelines for UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically, MPLS can carry a number of different protocols as payloads. When the payload traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NOT employ its own congestion control mechanism, because congestion losses of tunneled traffic will already trigger an appropriate congestion response at the original senders of the tunneled traffic. When the payload traffic is not known to be IP-based, or is known to be IP-based but not congestion-controlled, the UDP tunnel SHOULD employ an appropriate congestion control mechanism. Furthermore, because UDP tunnels are usually bulk-transfer applications as far as the intermediate routers are concerned, the guidelines as defined in Section 3.1.1 of [RFC5405] SHOULD apply.
>>
>> Best regards,
>> Xiaohu
>>
>>> -----ÓÊ¼þÔ­¼þ-----
>>> ·¢¼þÈË: mpls [mailto:mpls-bounces@ietf.org] ´ú±í Eggert, Lars
>>> ·¢ËÍÊ±¼ä: 2014Äê1ÔÂ8ÈÕ 18:22
>>> ÊÕ¼þÈË: IETF
>>> ³­ËÍ: mpls@ietf.org
>>> Ö÷Ìâ: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS
>>> in UDP) to Proposed Standard
>>>
>>> Hi,
>>>
>>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
>>>> - 'Encapsulating MPLS in UDP'
>>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
>>>
>>>
>>> this document needs to describe how it addresses the issues raised in BCP145
>>> (RFC5405). It already contains some text about messages sizes and congestion
>>> considerations, which is great. Unfortunately, the text about congestion
>>> considerations is not fully in line with RFC5405.
>>>
>>> Lars
> 

From lars@netapp.com  Fri Jan 10 08:09:58 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB821AE0B0; Fri, 10 Jan 2014 08:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ld306yLTqEvc; Fri, 10 Jan 2014 08:09:56 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id AB2EF1AE074; Fri, 10 Jan 2014 08:09:56 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,639,1384329600";  d="asc'?scan'208";a="95307383"
Received: from vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) by mx11-out.netapp.com with ESMTP; 10 Jan 2014 08:09:45 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.03.0123.003; Fri, 10 Jan 2014 08:09:45 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Joel Halpern <jmh@joelhalpern.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQIA=
Date: Fri, 10 Jan 2014 16:09:45 +0000
Message-ID: <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com>
In-Reply-To: <52D01383.2080509@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_314DE890-78FD-4040-92CF-9007B2DDAACD"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 16:09:58 -0000

--Apple-Mail=_314DE890-78FD-4040-92CF-9007B2DDAACD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

On 2014-1-10, at 16:36, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> Maybe I am completely missing things, but this looks wrong.
> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> control will make it more likely that the service won't work.  Is that
> really the goal?
>=20
> We do not perform congestion control on MPLS LSPs.
> Assuming that a UDP tunnel is carrying just MPLS and was established
> just for MPLS, why would we expect it to behave differently than an =
MPLS
> LSP running over the exact same path, carrying the exact same traffic?

we've been rehashing this discussion several times over the years, e.g., =
for PWE, AMT, etc. In order to carry fixed-rate or otherwise =
non-congestion-controlled traffic over unprovisioned general Internet =
paths, there needs to be some sort of basic congestion control =
mechanism, like a circuit breaker.

The whole point of running MPLS is to create networks in which paths are =
provisionable, so this is usually not an issue. But if you start =
sticking MPLS inside of UDP, those packets can go anywhere on the net, =
so you need mechanisms to control the rate of that traffic if it causes =
congestion, or at the very least you need to be able to stop the traffic =
if it creates severe congestion.

Lars

--Apple-Mail=_314DE890-78FD-4040-92CF-9007B2DDAACD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtAbRdZcnpRveo1xAQKbZwP+IUK3JgbtrPeA/EPYWCZorxenzX/vl9Sv
qmgKPHdsu1nYPDq40+6sEDT6VAK3tdFyf6zdfYqd2mG4e9tl1TqH6w09nGogL8s4
9YMT/V7Vr3/pTeiH1eto5f9I2awxne7KgQzVGE6Rf1fdlS7gHNWbJ2JM/dfYI2q+
Vt6xaM88vFo=
=CwSc
-----END PGP SIGNATURE-----

--Apple-Mail=_314DE890-78FD-4040-92CF-9007B2DDAACD--

From scott.brim@gmail.com  Fri Jan 10 08:32:43 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC0B1ADF82; Fri, 10 Jan 2014 08:32:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UlsNJGgmvQnh; Fri, 10 Jan 2014 08:32:40 -0800 (PST)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5AD1AD627; Fri, 10 Jan 2014 08:32:40 -0800 (PST)
Received: by mail-oa0-f51.google.com with SMTP id m1so5250696oag.38 for <multiple recipients>; Fri, 10 Jan 2014 08:32:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=165ZdF+2oX1Ye1xTkK5qqQyAKPRPFKPwMcXRdeMRvyo=; b=lRYwYVdrE18UOEisnEDE8EM6qCL+E1AhAncmKUlyotZ5LHsDedid5LWOQUO315mQXJ cPdRuRtpqzcqUD89B5nnq9GMFKqXiRFflD7F6XoD4vVdmvvc5WpLbrbDDtuNcveo26g1 9q/W1f9EEJfLercEr0aW0iEZI2JvXcW12HDi3biIOQyLqc9LsRIaj28hOHnFsNit1gJ9 SVxj8XU+RlJM3YXkucypP9xNgY60XjzFhZa5mydmNto4/t4Vhu5ptPc7Jl++1kxzcdvQ P5v01iBTnxDsRXZjAxQAvBzklGFULOIESKiQ8UdqkS4JBzhCRDzSOfobtWdkq+g9o23o qWeA==
X-Received: by 10.60.174.167 with SMTP id bt7mr7596938oec.54.1389371550528; Fri, 10 Jan 2014 08:32:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 10 Jan 2014 08:32:10 -0800 (PST)
In-Reply-To: <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 10 Jan 2014 11:32:10 -0500
Message-ID: <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 16:32:43 -0000

I don't think it's right to try to solve this in MPLS, because MPLS is
not a forwarding protocol - it's a connectivity protocol. In any use
of UDP, congestion control is either left to something above UDP or
ignored (left to queue management). Similarly, you want the client of
MPLS to be responsible for managing its traffic. MPLS gives you paths,
it doesn't push packets over them.

Scott


On Fri, Jan 10, 2014 at 11:09 AM, Eggert, Lars <lars@netapp.com> wrote:
> Hi,
>
> On 2014-1-10, at 16:36, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>> Maybe I am completely missing things, but this looks wrong.
>> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
>> control will make it more likely that the service won't work.  Is that
>> really the goal?
>>
>> We do not perform congestion control on MPLS LSPs.
>> Assuming that a UDP tunnel is carrying just MPLS and was established
>> just for MPLS, why would we expect it to behave differently than an MPLS
>> LSP running over the exact same path, carrying the exact same traffic?
>
> we've been rehashing this discussion several times over the years, e.g., =
for PWE, AMT, etc. In order to carry fixed-rate or otherwise non-congestion=
-controlled traffic over unprovisioned general Internet paths, there needs =
to be some sort of basic congestion control mechanism, like a circuit break=
er.
>
> The whole point of running MPLS is to create networks in which paths are =
provisionable, so this is usually not an issue. But if you start sticking M=
PLS inside of UDP, those packets can go anywhere on the net, so you need me=
chanisms to control the rate of that traffic if it causes congestion, or at=
 the very least you need to be able to stop the traffic if it creates sever=
e congestion.
>
> Lars

From sm@elandsys.com  Fri Jan 10 08:40:03 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB02A1AE12F for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 08:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level: 
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.538, T_DKIM_INVALID=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWqKbJ1JfMLW for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 08:40:02 -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 5F7941ACCE2 for <ietf@ietf.org>; Fri, 10 Jan 2014 08:40:02 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.128.22]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s0AGdNon021310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Jan 2014 08:39:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389371976; bh=q1h2nTbNgLDyJK+3JEfMiidvUkKSMOC9XiCOfWIdy8Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OpvWr+mN2YdfjkYMxI4XNNlYI0zybq7otJ2RNEVbmRIu8mQ46R4Ge5WLXv5Px0UzL uabIymPCHS2tcBkKXi5+oQwWeduBZij0JKz9thBxhyFddJT48W0y4HuSWXUdSHB/6X LJtfBahTAEH9RkmyChmW2/2Jjq4tED424N2CBuIM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1389371976; i=@elandsys.com; bh=q1h2nTbNgLDyJK+3JEfMiidvUkKSMOC9XiCOfWIdy8Q=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SnwwhmsQ2I+TuK2s+aRWJsskTsaRcCz5+/18/FUKFys5Lq3lzuxE6wydTeM26jLI+ M6dZnzNqGzu4n4OcBYIJKBPcZHQNibS+9FEZcb+jk5OTJmXO14fdNTRM9IwO6NwYN8 z7s7oAnjF34RTU+WIIY+PbUKotof8CP/5foAFH9I=
Message-Id: <6.2.5.6.2.20140110071957.0a8de258@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 10 Jan 2014 07:28:07 -0800
To: stbryant@cisco.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
In-Reply-To: <52CFC58C.3020000@cisco.com>
References: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com> <52CFC58C.3020000@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Ines Robles <mariainesrobles@googlemail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 16:40:04 -0000

Hi Stewart,
At 02:03 10-01-2014, Stewart Bryant wrote:
>Surely the best you can hope for is:
>
>"..without describing all of the actual and potential risks and 
>threats to implementers and users that they are aware of."
>
>The advice is by definition a best effort service.

Agreed.

I'll replace the last sentence in Section 3 with:

    However it is to be noted that there is an expectation that no one
    shall ever knowingly contribute advice or text that may adversely
    affect the security of the Internet without describing all known
    or foreseen risks and threats to potential implementers and users
    that they are aware of.

Regards,
S. Moonesamy 


From hsantos@isdg.net  Fri Jan 10 08:56:58 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3601ADFB9 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 08:56:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KTuhPRjDQz4m for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 08:56:55 -0800 (PST)
Received: from mail.santronics.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 56E6C1ADF46 for <ietf@ietf.org>; Fri, 10 Jan 2014 08:56:55 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5562; t=1389372999; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=+LhxQtjgwoZicYiNGNG5GnWijSs=; b=GpQQsxjVQOsaMr8jGi56 eYavnb8IZJk5xmWg2+8MZs9Q7EJ+/3TTCpulMHG7vnF+FaON53x3zxmzZZ+KD5Vm q2mmzP0CwAoTzZkz6p8aXFwlVNXjtS5lb88+A0LM28JwUHiapAiagNpsKne83Dp/ sC7Ll3N0b4INSeHFWsjVORo=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 10 Jan 2014 11:56:38 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2950472063.34546.5664; Fri, 10 Jan 2014 11:56:37 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5562; t=1389372441; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ZMDoE3K iKPGcI62RgR7N+CUjJm++5t1dP2Wi0XBNKqc=; b=VNi2ssml3Q/PEI63gZ6FII6 TQ/u3yU3wBw8S5cLgJ+dHUf/M0WfmNWNR87zOIgNGgj2Y6xuSTg4mtKKy6u3nN7t 18r5Zr/yGmP8Dj4t2iOnyg+VoII0Z2hmcYX6xmVC+n2xf7F6cFBw3higA1Q7LukJ g6oO55OYeU3CyXsGXEXM=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 10 Jan 2014 11:47:21 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2396787067.9.5064; Fri, 10 Jan 2014 11:47:20 -0500
Message-ID: <52D02649.9040808@isdg.net>
Date: Fri, 10 Jan 2014 11:56:41 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Upcoming change to announcement email header fields (using old header)
References: <20140109140002.11063.48808.idtracker@ietfa.amsl.com> <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.com>
In-Reply-To: <9FEE69B9CA3597B2B488C4BF@JcK-HP8200.jck.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 16:56:58 -0000

Hi,

I hope I am not butting in on something here, but our Mailing List 
Software (MLS) is among those that offers a "Reply-To: <list-address>" 
list admin option for a submission distribution.   This was done 
primarily because early on most, if not all MUAs, had UI reply buttons 
such as:

    REPLY        -> goes to Reply-To:, if any, otherwise From:
    REPLY TO ALL -> goes to all originating fields, From:, Reply-To:, Cc:

So for the layman end-user whose natural response action was to click 
a REPLY, the response went direct to the author and not the mailing 
list which is what he probably wanted.

On the other hand, he had to be aware of this and click REPLY TO ALL 
and now he had to be keen to the idea of multiple replies, whether to 
edit the fields (reduce to the list address) or not, consider who does 
it piss off, who doesn't care one bit about it, it varies here, or 
whether he wanted to make sure the author got his response and not 
depend on someone always reading the list, etc, etc.

So there was many "mail reply ergonomic" reasons for having special 
Reply-To: feature in mailing list -- to better support the MUAs.

After all, a Mailing list is technically a kludge for using the 
direct/private, one to one, mail system as opposed to NNTP which is 
naturally a Groupware, one to many framework.

Having this feature was a god-send for us (for support mailing lists) 
and for our customers using our MLS.

But it was a sensitive concept with some, who didn't like the idea 
that an author defined Reply-To: header was effectively altered for a 
list distribution.  So there was pros and cons, and by far, IMO the 
pros outweigh the cons.

Today, what I have noticed is that more and more updated MUAs are 
supporting 5322.the List-* headers which most list distributions now 
add.  Now you see a third button with some of the modern MUAs:

    REPLY TO LIST -> uses the list-post: header

I presume the REPLY TO LIST button would be disabled if the List-Post: 
header is missing.

So perhaps the changes below should note that there are LIST-* headers 
that modern RFC-based internet MUAS "SHOULD" be using.

Thanks

--
HLS



On 1/9/2014 12:24 PM, John C Klensin wrote:
>
>
> --On Thursday, January 09, 2014 06:00 -0800 The IESG
> <iesg-secretary@ietf.org> wrote:
>
>>
>> We will soon be changing the header fields used in IETF Last
>> Call messages sent to the IETF Announce mailing list.
>> ...
>> This message will be repeated daily using both the old and new
>> header. This instance of the message was sent using the old
>> header. Please ensure you receive both versions.
>> These messages will cease, and all Last Call messages to this
>> list will switch to using the new header on or shortly after
>> 2014-01-24.
>> ...
>> The specific changes are:
>> ...
>> New:
>>
>>     From: The IESG <noreply@ietf.org>
>>     To: IETF-Announce:;
>>     Reply-To: IETF Discussion List <ietf@ietf.org>
>>
>> and the message sent using the New header fields will also be
>> Bcc-ed to <ietf-announce@ietf.org>
>
> Folks,
>
> Three observations based on some small experience with Internet
> mail and various MUAs.
>
> (1) If someone is going to have or detect problems with this
> change, it would be very useful to identify what you are putting
> in the envelope, especially the backward-pointing parts of the
> envelope.  If someone had to start tracking through logs to
> identify what happened to a missing message, knowing, e.g.,
> whether ietf or AMS domains were being used in EHLO and MAIL
> command arguments might be a big help.
>
> (2) Especially given the history of configuration failures that
> have periodically allowed random parties to post messages or
> replies to IETF-Announce, the reasons for the change in "From:"
> and "Reply-to;" fields are obvious and probably should have been
> thought of and adopted years ago.  The posting filters will
> still be needed (I hope we are not going to rely on the security
> through obscurity of a secret address), but this should at least
> stop the accidents.
>
> However, despite the fact that group syntax, including that for
> empty lists, has been part of the mail header specs for well
> over 30 years, we know that many systems have had trouble with
> messages that contain only an empty group indication.  Those
> systems are not just non-conforming MUA or mailstore
> implementations (or MTAs that violate the SMTP spec and look at
> headers in transit) or antispam systems of various qualities.
> They including a variety of coded and ad hoc mail classification
> and filtering arrangements that may require special arrangements
> for such addresses.   Given the risks and potential problems,
> I'd like to hear a little more justification for switching to
> group syntax than the apparent "the IESG  decided on this and is
> announcing it to the community".
>
> (3) If someone actually does discover that they have a problem
> and are dependent on a third-party supplier to get it patched, 2
> 1/2 weeks are unlikely to be sufficient.
>
> I hope this comment doesn't turn into a distraction, but, when
> announcements like this appear with no prior discussion with the
> community, I wonder what the process was that produced the
> decision and whether we've abandoned the principle that the IESG
> is supposed to be steering and determining and reflecting
> community consensus, not making decisions and pronouncements in
> secret and top-down.
>
>      best,
>     john
>
>
>
>
>

-- 
HLS



From curtis@ipv6.occnc.com  Thu Jan  9 18:18:18 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3653D1ADF8A; Thu,  9 Jan 2014 18:18:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6UI_-fdkPL0; Thu,  9 Jan 2014 18:18:15 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id C5B7F1ADF65; Thu,  9 Jan 2014 18:18:14 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0A2Hv4I081006; Thu, 9 Jan 2014 21:17:57 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401100217.s0A2Hv4I081006@maildrop2.v6ds.occnc.com>
To: David Allan I <david.i.allan@ericsson.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
In-reply-to: Your message of "Thu, 09 Jan 2014 20:26:27 +0000." <E6C17D2345AC7A45B7D054D407AA205C391FEA0A@eusaamb105.ericsson.se>
Date: Thu, 09 Jan 2014 21:17:57 -0500
X-Mailman-Approved-At: Fri, 10 Jan 2014 08:58:02 -0800
Cc: Gregory Mirsky <gregory.mirsky@ericsson.com>, "mpls@ietf.org" <mpls@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 10 Jan 2014 02:18:18 -0000

Since we are all top posting ...

For counting dropped packets LM OAM is what you need.  CV doesn't do
that.  Direct LM will give best results on a per LSP basis but
requires forwarding chip support to do so.

I also don't know the origin of this discussion.

>> I am interested in how often in practice MPLS packets get 
>> misdelivered due to label corruption.

Not very often if ever at least for major vendor products.  I don't
know if second tier or third tier players have bugs.

(Very often circa 2000 or earlier particularly with one specific
vendor and with one provider who made things much worse by mucking
with the ILM through management plane, but that is ancient history).

Bit rot in TCAM or SRAM is very rare.  Bit rot in circa 1980s DRAM was
a problem.  Bit rot in modern non-ECC DRAM is rare.  Bit rot in modern
ECC DRAM is very rare.  Therefore to have a bad ILM you need bugs.

Curtis


In message <E6C17D2345AC7A45B7D054D407AA205C391FEA0A@eusaamb105.ericsson.se>
David Allan I writes:

Hi  (trimmed received list)

I'm not sure what the starting point of this dialog is, but I can at least say Greg is right on the CV front, it only detects and does not measure misdirection. 

The only other possibility to count anything is a "no ILM" condition where the label value is unrecognized by the receiving LSR, which IMO could not be made authoritative if it is label values in either the frame or the NHLFE and not exclusively next hops that is corrupted.

Cheers
D

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Thursday, January 09, 2014 9:30 AM
To: Loa Andersson; mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
Subject: Re: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft

Hi Loa, et al.,
I think that you're referring to Connectivity Verification in MPLS-TP (RFC 6428). It would only detect mis-connection but would not count leaked in frames.

Such problem may be more apparent in Segment Routing (SPRING WG). Perhaps CV should be a requirement in SR OAM.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Thursday, January 09, 2014 8:17 AM
To: mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft

Changed the subject line !

On 2014-01-09 20:36, Mark Tinka wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled MPLS.
>
>> I am interested in how often in practice MPLS packets get 
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted MPLS frames 
> so operators can glean this data. This isn't something I've come 
> across, but it would be good to find some kind of way to count this 
> across interfaces, if the routers can detect and report them.

This would be possible to do with MPLS-TP OAM, wouldn't it?

/Loa
>
> The known issue about mis-delivery of MPLS frames is poorly- sized MTU 
> interfaces. I have no empirical data as to how this can corrupt 
> successive MPLS frames that may fit into the transit MTU. But in this 
> case, as with any Layer 2 traffic, not enough MTU = dropped frame.
>
> Mark.
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From david.i.allan@ericsson.com  Thu Jan  9 12:26:46 2014
Return-Path: <david.i.allan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA701AE425; Thu,  9 Jan 2014 12:26:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8avMEAKu9fRr; Thu,  9 Jan 2014 12:26:44 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 18DCF1AE411; Thu,  9 Jan 2014 12:26:44 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-25-52cf05f6cddf
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id A7.B2.23183.6F50FC25; Thu,  9 Jan 2014 21:26:31 +0100 (CET)
Received: from EUSAAMB105.ericsson.se ([147.117.188.122]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0347.000; Thu, 9 Jan 2014 15:26:28 -0500
From: David Allan I <david.i.allan@ericsson.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: RE: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Topic: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Index: AQHPDVZP/GN/wtlIskG6flItphhfHpp8+h2A///ZBGA=
Date: Thu, 9 Jan 2014 20:26:27 +0000
Message-ID: <E6C17D2345AC7A45B7D054D407AA205C391FEA0A@eusaamb105.ericsson.se>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu> <7347100B5761DC41A166AC17F22DF1121B743FDC@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B743FDC@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrGLMWRmVeSWpSXmKPExsUyuXRPoO531vNBBn+/2Fg82zifxWLKWXWL W0tXsloce3OXzYHFY8mSn0wBjFFcNimpOZllqUX6dglcGac3rGUuOCtR0XnmKnMD41vhLkYO DgkBE4mNU3y7GDmBTDGJC/fWs3UxcnEICRxhlJjU/ZkVwlnGKLG9eQ0rSBWbgIHEnv9fGEES IgK7GCXuHp7PApIQFsiSWH5mCjvIVBGBbImXS/1BwiICVhKrLpxmB7FZBFQklk7bzAhi8wr4 Snze/B9q21wmif8Lf4Et4BTwk3i5YyaYzQh00vdTa5hAbGYBcYlbT+YzQZwqILFkz3lmCFtU 4uXjf6wQtrLE9zmPWCDqdSQW7P7EBmFrSyxb+JoZYrGgxMmZT1gmMIrOQjJ2FpKWWUhaZiFp WcDIsoqRo7Q4tSw33chgEyMwLo5JsOnuYNzz0vIQozQHi5I475e3zkFCAumJJanZqakFqUXx RaU5qcWHGJk4OKUaGK13Jj+/q3D3CuvaH6GzePcUJ4YsSD8e9vmMu4rwlU8eGTUd+1pLTET2 XJ706sDkAEc+TpnvZ+rebPgYzHXUy/3qzbXtlif2TxIImFamcj3n9/2KrOCQ8z5Fts3iQos/ 1Mmuc/gWs+ZOBUPe5IKbIvNY5lq13bv2RidlQsXD+isrLRMPL5OynabEUpyRaKjFXFScCABg f1O7WQIAAA==
X-Mailman-Approved-At: Fri, 10 Jan 2014 08:58:27 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 20:26:46 -0000

Hi  (trimmed received list)

I'm not sure what the starting point of this dialog is, but I can at least =
say Greg is right on the CV front, it only detects and does not measure mis=
direction.=20

The only other possibility to count anything is a "no ILM" condition where =
the label value is unrecognized by the receiving LSR, which IMO could not b=
e made authoritative if it is label values in either the frame or the NHLFE=
 and not exclusively next hops that is corrupted.

Cheers
D

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Thursday, January 09, 2014 9:30 AM
To: Loa Andersson; mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; davi=
d.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
Subject: Re: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in=
-udp was RE: gre-in-udp draft

Hi Loa, et al.,
I think that you're referring to Connectivity Verification in MPLS-TP (RFC =
6428). It would only detect mis-connection but would not count leaked in fr=
ames.

Such problem may be more apparent in Segment Routing (SPRING WG). Perhaps C=
V should be a requirement in SR OAM.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Thursday, January 09, 2014 8:17 AM
To: mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com=
; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp=
 was RE: gre-in-udp draft

Changed the subject line !

On 2014-01-09 20:36, Mark Tinka wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled MPLS.
>
>> I am interested in how often in practice MPLS packets get=20
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted MPLS frames=20
> so operators can glean this data. This isn't something I've come=20
> across, but it would be good to find some kind of way to count this=20
> across interfaces, if the routers can detect and report them.

This would be possible to do with MPLS-TP OAM, wouldn't it?

/Loa
>
> The known issue about mis-delivery of MPLS frames is poorly- sized MTU=20
> interfaces. I have no empirical data as to how this can corrupt=20
> successive MPLS frames that may fit into the transit MTU. But in this=20
> case, as with any Layer 2 traffic, not enough MTU =3D dropped frame.
>
> Mark.
>

--=20


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From gregory.mirsky@ericsson.com  Thu Jan  9 09:30:40 2014
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6752D1AE453; Thu,  9 Jan 2014 09:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58YQRyTm8sna; Thu,  9 Jan 2014 09:30:38 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id 47A731AE3DC; Thu,  9 Jan 2014 09:30:38 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-26-52cedcb16bbb
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id E5.D8.23183.1BCDEC25; Thu,  9 Jan 2014 18:30:26 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0347.000; Thu, 9 Jan 2014 12:30:28 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: Loa Andersson <loa@pi.nu>, "mark.tinka@seacom.mu" <mark.tinka@seacom.mu>,  "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Topic: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Thread-Index: AQHPDVZPwlV5fcTOlUKeWNcLbDwLU5p8pA3g
Date: Thu, 9 Jan 2014 17:30:27 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B743FDC@eusaamb103.ericsson.se>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091303.53239.mark.tinka@seacom.mu> <52CE914B.7070506@cisco.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu>
In-Reply-To: <52CECB7B.3090200@pi.nu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupnkeLIzCtJLcpLzFFi42KZXLonUHfTnXNBBj928FhsPbyW3eJ122xG i2cb57NYvP23gdViyll1i39z5zBb3Fu7mN3i1tKVrBbnns5htDj25i6bA5fHlN8bWT2OHJnN 4tHz+QWTx5IlP5k8ms4cZfaYNb2NzaPz2kT2APYoLpuU1JzMstQifbsEroyFx8+yFCwUqDix 5jlbA+Mnni5GTg4JAROJhklrmSBsMYkL99azdTFycQgJHGGU2PPhFDOEs4xR4uNOiCo2ASOJ Fxt72EFsEYFKiV/TdoF1MAu0M0lcWrsULCEskCWx/MwUIJsDqChb4uVSf4h6I4knX9sZQWwW ARWJ+5fug9m8Ar4Ssz4cg9p8k1Hi5/x7YHM4BVQlnh2aAGYzAp33/dQasCOYBcQlbj2ZD3W2 gMSSPeeZIWxRiZeP/7FC2MoS3+c8YoGo15FYsPsTG4StLbFs4WtmiMWCEidnPmGZwCg2C8nY WUhaZiFpmYWkZQEjyypGjtLi1LLcdCODTYzASD0mwaa7g3HPS8tDjNIcLErivF/eOgcJCaQn lqRmp6YWpBbFF5XmpBYfYmTi4JRqYLQqtLg5+02N5cIWkw+vvas/s66qeqbzTmWD16e8W89e Nbn9rZit/tq4a7rK3B9xHoGxv1h3TWb8tCJykWN++PVNu623PGY9LRp/cPe+NqaJDw6fK2D7 cv5SgfgG5VeT2xqU22wDJV0T3P+zq+9pnKzD1rxcWVmzNGlzx6kXFzc/+PH1T+lb9yVKLMUZ iYZazEXFiQBNPZh5ogIAAA==
X-Mailman-Approved-At: Fri, 10 Jan 2014 08:59:08 -0800
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "david.black@emc.com" <david.black@emc.com>, "jnc@mit.edu" <jnc@mit.edu>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 17:30:40 -0000

Hi Loa, et al.,
I think that you're referring to Connectivity Verification in MPLS-TP (RFC =
6428). It would only detect mis-connection but would not count leaked in fr=
ames.

Such problem may be more apparent in Segment Routing (SPRING WG). Perhaps C=
V should be a requirement in SR OAM.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Loa Andersson
Sent: Thursday, January 09, 2014 8:17 AM
To: mark.tinka@seacom.mu; stbryant@cisco.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com=
; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: [mpls] misdelivered mpls packets - Was: Re: draft-ietf-mpls-in-udp=
 was RE: gre-in-udp draft

Changed the subject line !

On 2014-01-09 20:36, Mark Tinka wrote:
> On Thursday, January 09, 2014 02:08:43 PM Stewart Bryant
> wrote:
>
>> Either or both.
>
> I can only speak to native MPLS, as I've never run tunneled MPLS.
>
>> I am interested in how often in practice MPLS packets get=20
>> misdelivered due to label corruption.
>
> Well, first of all, routers would need to report corrupted MPLS frames=20
> so operators can glean this data. This isn't something I've come=20
> across, but it would be good to find some kind of way to count this=20
> across interfaces, if the routers can detect and report them.

This would be possible to do with MPLS-TP OAM, wouldn't it?

/Loa
>
> The known issue about mis-delivery of MPLS frames is poorly- sized MTU=20
> interfaces. I have no empirical data as to how this can corrupt=20
> successive MPLS frames that may fit into the transit MTU. But in this=20
> case, as with any Layer 2 traffic, not enough MTU =3D dropped frame.
>
> Mark.
>

--=20


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From mark.tinka@seacom.mu  Thu Jan  9 10:48:49 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26F401AE525; Thu,  9 Jan 2014 10:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jXsUnWvkCvLP; Thu,  9 Jan 2014 10:48:47 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id 192301AE52B; Thu,  9 Jan 2014 10:48:45 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W1KeO-0005FL-Qh; Thu, 09 Jan 2014 20:48:16 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: Loa Andersson <loa@pi.nu>
Subject: Re: misdelivered mpls packets - Was: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
Date: Thu, 9 Jan 2014 20:48:15 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu>
In-Reply-To: <52CECB7B.3090200@pi.nu>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart7202981.cQ0BC7dWJg"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401092048.16168.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Fri, 10 Jan 2014 08:59:35 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, stbryant@cisco.com, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 18:48:49 -0000

--nextPart7202981.cQ0BC7dWJg
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Thursday, January 09, 2014 06:16:59 PM Loa Andersson=20
wrote:

> This would be possible to do with MPLS-TP OAM, wouldn't
> it?

Sorry, no experience.=20

I don't personally like MPLS-TP :-), but happy to hear of=20
any experiences from those that do.

Mark.

--nextPart7202981.cQ0BC7dWJg
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJSzu7wAAoJEGcZuYTeKm+GfxkP/ArGFtdiH9YpCn6vMqW+OJ5k
mIhR4Hhpu7DUOXHXVwUw1f24fUU/RrMdPvveiLFo6LJmWLo/w8D7fY9IvP+KXlu/
XFSth1OZOKHRQw27LHHm9iZKURnreMitSZnJ+dFyAsZHTOAyPHshBvDY1oYbKvbK
qcPASfq+BXrQ2PfAkfWCXWYVHthS47FxFpcTxDOzLffnjhcAgxbb/eR75ieU34TY
wa+tGlvgrb4D4THEJ5gHZiOWBR4Mtt/4bsNRAL8FKlX4UtcYYiuF++xYNQhPpQnB
0IJ/OFCWOb4/cB71hpe4STjrE2++CayAXExFM5f6Ypi+woNdynKOq56V36E2gOZe
F32sX23IJ8cvU2yEOjYRkLtGnrsYGHlcl9kSh/t1gs5mCxq6yMiJFkwYyzrsv6Nz
gTPmE4V16jpBQMb7Ojx3fJ1td0ltOlbJS32ITvbH0AWrlbCeybzn5NjDtNiDtIJO
F+s21T3YPyII8xP7CELn5i06HxQKo81BuahYAv9cI8Nom6FsPUEAAMMe9Si43sLg
tgbqtrfC2hox9xH83SiN4wboJZs/QeTeaaKSwgRBVtiM+rI1dVZahSBwSTKpCoxH
fgG/fU1ssPcPdnuq2C7/UUMB5dYqfAwGugimChhJcnmEAMwYbeyoEu9WNq0cyHCC
L43oBc1rSsXS51qjJLZW
=aFJ/
-----END PGP SIGNATURE-----

--nextPart7202981.cQ0BC7dWJg--

From mbj@tail-f.com  Thu Jan  9 13:51:42 2014
Return-Path: <mbj@tail-f.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF0B1AE0C0; Thu,  9 Jan 2014 13:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPf8Py69DHUY; Thu,  9 Jan 2014 13:51:41 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [109.74.15.94]) by ietfa.amsl.com (Postfix) with ESMTP id EC8181A1F66; Thu,  9 Jan 2014 13:51:40 -0800 (PST)
Received: from localhost (unknown [193.12.32.88]) by mail.tail-f.com (Postfix) with ESMTPSA id 3ACC5240C289; Thu,  9 Jan 2014 22:51:30 +0100 (CET)
Date: Thu, 09 Jan 2014 22:51:29 +0100 (CET)
Message-Id: <20140109.225129.336419021.mbj@tail-f.com>
To: andy@yumaworks.com
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <CABCOCHTF4=zhwd25TWxh1pM8h_Tw2==WehDHuJaPPYMm3XWVUg@mail.gmail.com>
References: <20140109105804.GA44893@elstar.local> <6.2.5.6.2.20140109051548.0a951040@resistor.net> <CABCOCHTF4=zhwd25TWxh1pM8h_Tw2==WehDHuJaPPYMm3XWVUg@mail.gmail.com>
X-Mailer: Mew version 6.5rc2 on Emacs 23.4 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 10 Jan 2014 09:00:17 -0800
Cc: sm@resistor.net, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 21:51:42 -0000

Andy Bierman <andy@yumaworks.com> wrote:
> Hi,
> 
> On Thu, Jan 9, 2014 at 7:47 AM, SM <sm@resistor.net> wrote:
> 
> > Hi Juergen,
> > At 02:58 09-01-2014, Juergen Schoenwaelder wrote:
> >
> >> People want to be able to configure timezones using the timezone
> >> naming scheme commonly supported by operating systems (e.g.,
> >> Europe/Paris). This document defines a serialization of the timezone
> >> names into YANG format for this purpose. I believe there was indeed
> >> strong concensus on this in the WG.
> >>
> >
> > There was a message about a quick poll [1] to adopt
> > draft-lange-netmod-iana-timezones-01 on 2 July, 2012.  Three persons
> > expressed their support and the WG Chair expressed his support as a
> > technical contributor [2]; there weren't any message objecting to adoption.
> >  There were two comments [3][4] on 30 July, 2012.  There was a WG Last Call
> > announcement [5] and two reminders [6][7] about it. There was a message [8]
> > on 12 November, 2013 from a WG participant (I am not taking into account
> > the message from the author and one of the WG Chairs).  My comment about
> > the determination of consensus being questionable is based on the messages
> > in the NETMOD mailing list archive.
> >
> >  This document aims at establishing an IANA maintained serialization of
> >> whatever list of names the timezone database contains. It does not
> >> change the way the TZ coordinator, an IANA Designated Expert, takes
> >> decisions. Perhaps this needs to be stated more explicit.
> >>
> >
> > There is a thread at http://mm.icann.org/pipermail/tz/2012-May/017711.html
> > The problem is not changing the way things are done.  I would describe the
> > current TZ approach as keeping the TZ information up-to-date by posting a
> > (software) release every now and then.  It works for me.
> >
> >  So far (in the MIB world), the initial versions of IANA maintained
> >> modules were published as Proposed Standards on the standards track
> >> (although the only thing that really remains valid over time are the
> >> IANA considerations, which however often require the initial module to
> >> be available). We simply followed this practice.
> >>
> >
> > If I understood correctly the YANG module defined in the draft creates
> > IANA-registered timezones based on public domain [9] information about
> > timezones.  IANA is then asked to keep the IANA-registered timezones
> > up-to-date.  That sounds okay if the politics about time are not taken into
> > consideration [10][11][12].

Yes.  The idea is to extract the names from the published TZ database
and list them in a YANG module.  Nothing more.  Entries cannot be
added directly to the YANG module; they will always just mirror what's
in the TZ database.

> >  There was concensus in the WG that it is desirable to configure
> >> timezones by name (e.g., Europe/Paris) instead of having only hard
> >> coded UTC offsets - the benefits should be obvious.
> >>
> >
> > I agree that there can be benefits to that approach.  I could not find the
> > (mailing list) message where that WG decision was taken.
> >
> >
> After reading the IANA Considerations section closer, I have some concerns
> about the use of a YANG enumeration. This section does not say who must
> update the enumeration typedef and republish the RFC containing the new
> YANG module, every time the TZ database is changed.
> Is it the NETMOD WG? IANA?

I think it is clear that the intention is that is IANA.  But of course
it could be clarified.  Maybe it should even say that it is the
responsibility of the TZ Coordinator.  However, this must presumably
be verified with him first.

> This may not be a practical long-term solution.
> The purpose of a YANG enumeration type is to allow a well-constrained
> value set that can be machine-validated.  If the data type was a string
> instead of an enumeration, there would be no IANA coupling or republishing
> (or YANG-based machine validation). The description-stmt can say a leaf
> using this data type MUST match a value in the TZ database.

If it is not feasible to maintain a YANG "mirror" of the timezone
names from the TZ database, then I guess we can use a string.  I
prefer the formal enumeration though.

> The draft (sec. 3.1) also says to change the status of the old enum to
> obsolete
> and add a new enum, in order to change the name.  YANG definitions are
> supposed to transition from current to deprecated, not current to obsolete.

RFC 6020, section 10, explicitly allows a definition to go from
current to obsolete:

   o  A "status" statement may be added, or changed from "current" to
      "deprecated" or "obsolete", or from "deprecated" to "obsolete".


/martin

From xuxiaohu@huawei.com  Thu Jan  9 19:46:27 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 836C81AE004; Thu,  9 Jan 2014 19:46:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level: 
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZYX0prRW3cO; Thu,  9 Jan 2014 19:46:26 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD271ADFAF; Thu,  9 Jan 2014 19:46:25 -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.7-GA FastPath queued) with ESMTP id BCI66147; Fri, 10 Jan 2014 03:46:14 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 03:45:36 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 03:46:13 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Fri, 10 Jan 2014 11:46:07 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Eggert, Lars" <lars@netapp.com>, IETF <ietf@ietf.org>
Subject: re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw
Date: Fri, 10 Jan 2014 03:46:07 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com>
In-Reply-To: <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 10 Jan 2014 09:01:06 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 03:46:27 -0000

SGkgTGFycywNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIGNvbW1lbnRzLg0KDQpJIHdvbmRlciB3
aGV0aGVyIHRoZSBmb2xsb3dpbmcgbW9kaWZpZWQgdGV4dCBmb3IgQ29uZ2VzdGlvbiBDb25zaWRl
cmF0aW9uIHNlY3Rpb24gaXMgT0sgZnJvbSB5b3VyIHBvaW50IG9mIHZpZXc6DQoNClNpbmNlIHRo
ZSBNUExTLWluLVVEUCBlbmNhcHN1bGF0aW9uIGNhdXNlcyBNUExTIHBhY2tldHMgdG8gYmUgZm9y
d2FyZGVkIHRocm91Z2ggIlVEUCB0dW5uZWxzIiwgdGhlIGNvbmdlc3Rpb24gY29udHJvbCBndWlk
ZWxpbmVzIGZvciBVRFAgdHVubmVscyBhcyBkZWZpbmVkIGluIFNlY3Rpb24gMy4xLjMgb2YgW1JG
QzU0MDVdIFNIT1VMRCBiZSBmb2xsb3dlZC4gU3BlY2lmaWNhbGx5LCBNUExTIGNhbiBjYXJyeSBh
IG51bWJlciBvZiBkaWZmZXJlbnQgcHJvdG9jb2xzIGFzIHBheWxvYWRzLiBXaGVuIHRoZSBwYXls
b2FkIHRyYWZmaWMgaXMgSVAtYmFzZWQgYW5kIGNvbmdlc3Rpb24tY29udHJvbGxlZCwgdGhlIFVE
UCB0dW5uZWwgU0hPVUxEIE5PVCBlbXBsb3kgaXRzIG93biBjb25nZXN0aW9uIGNvbnRyb2wgbWVj
aGFuaXNtLCBiZWNhdXNlIGNvbmdlc3Rpb24gbG9zc2VzIG9mIHR1bm5lbGVkIHRyYWZmaWMgd2ls
bCBhbHJlYWR5IHRyaWdnZXIgYW4gYXBwcm9wcmlhdGUgY29uZ2VzdGlvbiByZXNwb25zZSBhdCB0
aGUgb3JpZ2luYWwgc2VuZGVycyBvZiB0aGUgdHVubmVsZWQgdHJhZmZpYy4gV2hlbiB0aGUgcGF5
bG9hZCB0cmFmZmljIGlzIG5vdCBrbm93biB0byBiZSBJUC1iYXNlZCwgb3IgaXMga25vd24gdG8g
YmUgSVAtYmFzZWQgYnV0IG5vdCBjb25nZXN0aW9uLWNvbnRyb2xsZWQsIHRoZSBVRFAgdHVubmVs
IFNIT1VMRCBlbXBsb3kgYW4gYXBwcm9wcmlhdGUgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlz
bS4gRnVydGhlcm1vcmUsIGJlY2F1c2UgVURQIHR1bm5lbHMgYXJlIHVzdWFsbHkgYnVsay10cmFu
c2ZlciBhcHBsaWNhdGlvbnMgYXMgZmFyIGFzIHRoZSBpbnRlcm1lZGlhdGUgcm91dGVycyBhcmUg
Y29uY2VybmVkLCB0aGUgZ3VpZGVsaW5lcyBhcyBkZWZpbmVkIGluIFNlY3Rpb24gMy4xLjEgb2Yg
W1JGQzU0MDVdIFNIT1VMRCBhcHBseS4NCg0KQmVzdCByZWdhcmRzLA0KWGlhb2h1DQoNCj4gLS0t
LS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogbXBscyBbbWFpbHRvOm1wbHMtYm91bmNlc0BpZXRm
Lm9yZ10gtPqx7SBFZ2dlcnQsIExhcnMNCj4gt6LLzcqxvOQ6IDIwMTTE6jHUwjjI1SAxODoyMg0K
PiDK1bz+yMs6IElFVEYNCj4gs63LzTogbXBsc0BpZXRmLm9yZw0KPiDW98ziOiBSZTogW21wbHNd
IExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGlu
ZyBNUExTDQo+IGluIFVEUCkgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IEhpLA0KPiANCj4g
T24gMjAxNC0xLTIsIGF0IDE2OjE0LCBUaGUgSUVTRyA8aWVzZy1zZWNyZXRhcnlAaWV0Zi5vcmc+
IHdyb3RlOg0KPiA+IC0gJ0VuY2Fwc3VsYXRpbmcgTVBMUyBpbiBVRFAnDQo+ID4gIDxkcmFmdC1p
ZXRmLW1wbHMtaW4tdWRwLTA0LnR4dD4gYXMgUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IA0KPiB0
aGlzIGRvY3VtZW50IG5lZWRzIHRvIGRlc2NyaWJlIGhvdyBpdCBhZGRyZXNzZXMgdGhlIGlzc3Vl
cyByYWlzZWQgaW4gQkNQMTQ1DQo+IChSRkM1NDA1KS4gSXQgYWxyZWFkeSBjb250YWlucyBzb21l
IHRleHQgYWJvdXQgbWVzc2FnZXMgc2l6ZXMgYW5kIGNvbmdlc3Rpb24NCj4gY29uc2lkZXJhdGlv
bnMsIHdoaWNoIGlzIGdyZWF0LiBVbmZvcnR1bmF0ZWx5LCB0aGUgdGV4dCBhYm91dCBjb25nZXN0
aW9uDQo+IGNvbnNpZGVyYXRpb25zIGlzIG5vdCBmdWxseSBpbiBsaW5lIHdpdGggUkZDNTQwNS4N
Cj4gDQo+IExhcnMNCg==

From xuxiaohu@huawei.com  Fri Jan 10 02:07:05 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A3401ADF7F; Fri, 10 Jan 2014 02:07:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7TsOjR_Z2SOJ; Fri, 10 Jan 2014 02:07:03 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id D01A61ADF6D; Fri, 10 Jan 2014 02:07:01 -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.7-GA FastPath queued) with ESMTP id BCI93416; Fri, 10 Jan 2014 10:06:51 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 10:06:11 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 10:06:49 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Fri, 10 Jan 2014 18:06:41 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: =?gb2312?B?tPC4tDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50?= =?gb2312?B?eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMgaW4gVURQKSB0byBQcm9wb3NlZCBT?= =?gb2312?Q?tandard?=
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw///RhoCAAJa00A==
Date: Fri, 10 Jan 2014 10:06:41 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08243BB4@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>
In-Reply-To: <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 10 Jan 2014 09:01:06 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 10:07:05 -0000

SGkgTGFycywNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBFZ2dlcnQsIExhcnMg
W21haWx0bzpsYXJzQG5ldGFwcC5jb21dDQo+ILeiy83KsbzkOiAyMDE0xOox1MIxMMjVIDE2OjQ4
DQo+IMrVvP7IyzogWHV4aWFvaHUNCj4gs63LzTogSUVURjsgbXBsc0BpZXRmLm9yZw0KPiDW98zi
OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50eHQ+IChFbmNhcHN1
bGF0aW5nIE1QTFMgaW4gVURQKQ0KPiB0byBQcm9wb3NlZCBTdGFuZGFyZA0KPiANCj4gSGksDQo+
IA0KPiB0aGF0IHNvdW5kcyBnb29kLiBXaGF0IGNvbmdlc3Rpb24gY29udHJvbCBhcmUgeW91IGdv
aW5nIHRvIGJlIHNwZWNpZnlpbmcgZm9yDQo+IHlvdXIgdHVubmVsPw0KDQpJTUhPLCB0aGlzIGlz
IGEgY29tbW9uIGlzc3VlIHdpdGggYW55IG90aGVyIGVuY2Fwc3VsYXRpb25zIGZvciBNUExTIGFu
ZCBldmVuIG90aGVyIGFwcGxpY2F0aW9ucyBvZiBVRFAgdHVubmVscyAuIE9mIGNvdXJzZSwgdGhl
IGZvbGxvd2luZyB0ZXh0IGNvdWxkIGJlIGFkZGVkIGlmIHdlIGJlbGlldmUgaXQncyBuZWNlc3Nh
cnk6IA0KDQogICAiLi4uYXBwbGljYXRpb25zIHRoYXQgdXNlcyB0aGUgZW5jYXBzdWxhdGlvbiBh
cyBzcGVjaWZpZWQgaW4gdGhpcw0KICAgZG9jdW1lbnQgU0hPVUxEIG1vbml0b3IgdGhlIHBhY2tl
dCBsb3NzIHJhdGUgdG8gZW5zdXJlIHRoYXQgaXQgaXMNCiAgIHdpdGhpbiBhY2NlcHRhYmxlIHBh
cmFtZXRlcnMuIFBhY2tldCBsb3NzIGlzIGNvbnNpZGVyZWQgYWNjZXB0YWJsZQ0KICAgaWYgYSBU
Q1AgZmxvdyBhY3Jvc3MgdGhlIHNhbWUgbmV0d29yayBwYXRoIHVuZGVyIHRoZSBzYW1lIG5ldHdv
cmsNCiAgIGNvbmRpdGlvbnMgd291bGQgYWNoaWV2ZSBhbiBhdmVyYWdlIHRocm91Z2hwdXQsIG1l
YXN1cmVkIG9uIGENCiAgIHJlYXNvbmFibGUgdGltZXNjYWxlLCB0aGF0IGlzIG5vdCBsZXNzIHRo
YW4gdGhhdCBvZiB0aGUgTVBMUy1pbi1VRFAgZmxvdy4NCiAgIFRoZSBjb21wYXJpc29uIHRvIFRD
UCBjYW5ub3QgYmUgc3BlY2lmaWVkIGV4YWN0bHksIGJ1dCBpcyBpbnRlbmRlZCBhcw0KICAgYW4g
Im9yZGVyLW9mLW1hZ25pdHVkZSIgY29tcGFyaXNvbiBpbiB0aW1lc2NhbGUgYW5kIHRocm91Z2hw
dXQuDQoNCiAgIEluIGVzc2VuY2UsIHRoaXMgcmVxdWlyZW1lbnQgc3RhdGVzIHRoYXQgaXQgaXMN
CiAgIG5vdCBhY2NlcHRhYmxlIHRvIGRlcGxveSBhbiBhcHBsaWNhdGlvbiB1c2luZyB0aGUgZW5j
YXBzdWxhdGlvbg0KICAgc3BlY2lmaWVkIGluIHRoaXMgZG9jdW1lbnQgb24gdGhlIGJlc3QtZWZm
b3J0IEludGVybmV0LCB3aGljaA0KICAgY29uc3VtZXMgYmFuZHdpZHRoIGFyYml0cmFyaWx5IGFu
ZCBkb2VzIG5vdCBjb21wZXRlIGZhaXJseSB3aXRoIFRDUA0KICAgd2l0aGluIGFuIG9yZGVyIG9m
IG1hZ25pdHVkZS4gT25lIG1ldGhvZCBvZiBkZXRlcm1pbmluZyBhbg0KICAgYWNjZXB0YWJsZSBi
YW5kd2lkdGggaXMgZGVzY3JpYmVkIGluIFtSRkMzNDQ4XS4gIg0KDQpCZXN0IHJlZ2FyZHMsDQpY
aWFvaHUNCg0KDQo+IExhcnMNCj4gDQo+IE9uIDIwMTQtMS0xMCwgYXQgNDo0NiwgWHV4aWFvaHUg
PHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0KPiANCj4gPiBIaSBMYXJzLA0KPiA+DQo+ID4g
VGhhbmtzIGEgbG90IGZvciB5b3VyIGNvbW1lbnRzLg0KPiA+DQo+ID4gSSB3b25kZXIgd2hldGhl
ciB0aGUgZm9sbG93aW5nIG1vZGlmaWVkIHRleHQgZm9yIENvbmdlc3Rpb24gQ29uc2lkZXJhdGlv
bg0KPiBzZWN0aW9uIGlzIE9LIGZyb20geW91ciBwb2ludCBvZiB2aWV3Og0KPiA+DQo+ID4gU2lu
Y2UgdGhlIE1QTFMtaW4tVURQIGVuY2Fwc3VsYXRpb24gY2F1c2VzIE1QTFMgcGFja2V0cyB0byBi
ZSBmb3J3YXJkZWQNCj4gdGhyb3VnaCAiVURQIHR1bm5lbHMiLCB0aGUgY29uZ2VzdGlvbiBjb250
cm9sIGd1aWRlbGluZXMgZm9yIFVEUCB0dW5uZWxzIGFzDQo+IGRlZmluZWQgaW4gU2VjdGlvbiAz
LjEuMyBvZiBbUkZDNTQwNV0gU0hPVUxEIGJlIGZvbGxvd2VkLiBTcGVjaWZpY2FsbHksIE1QTFMN
Cj4gY2FuIGNhcnJ5IGEgbnVtYmVyIG9mIGRpZmZlcmVudCBwcm90b2NvbHMgYXMgcGF5bG9hZHMu
IFdoZW4gdGhlIHBheWxvYWQgdHJhZmZpYw0KPiBpcyBJUC1iYXNlZCBhbmQgY29uZ2VzdGlvbi1j
b250cm9sbGVkLCB0aGUgVURQIHR1bm5lbCBTSE9VTEQgTk9UIGVtcGxveSBpdHMNCj4gb3duIGNv
bmdlc3Rpb24gY29udHJvbCBtZWNoYW5pc20sIGJlY2F1c2UgY29uZ2VzdGlvbiBsb3NzZXMgb2Yg
dHVubmVsZWQNCj4gdHJhZmZpYyB3aWxsIGFscmVhZHkgdHJpZ2dlciBhbiBhcHByb3ByaWF0ZSBj
b25nZXN0aW9uIHJlc3BvbnNlIGF0IHRoZSBvcmlnaW5hbA0KPiBzZW5kZXJzIG9mIHRoZSB0dW5u
ZWxlZCB0cmFmZmljLiBXaGVuIHRoZSBwYXlsb2FkIHRyYWZmaWMgaXMgbm90IGtub3duIHRvIGJl
DQo+IElQLWJhc2VkLCBvciBpcyBrbm93biB0byBiZSBJUC1iYXNlZCBidXQgbm90IGNvbmdlc3Rp
b24tY29udHJvbGxlZCwgdGhlIFVEUA0KPiB0dW5uZWwgU0hPVUxEIGVtcGxveSBhbiBhcHByb3By
aWF0ZSBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtLg0KPiBGdXJ0aGVybW9yZSwgYmVjYXVz
ZSBVRFAgdHVubmVscyBhcmUgdXN1YWxseSBidWxrLXRyYW5zZmVyIGFwcGxpY2F0aW9ucyBhcyBm
YXINCj4gYXMgdGhlIGludGVybWVkaWF0ZSByb3V0ZXJzIGFyZSBjb25jZXJuZWQsIHRoZSBndWlk
ZWxpbmVzIGFzIGRlZmluZWQgaW4gU2VjdGlvbg0KPiAzLjEuMSBvZiBbUkZDNTQwNV0gU0hPVUxE
IGFwcGx5Lg0KPiA+DQo+ID4gQmVzdCByZWdhcmRzLA0KPiA+IFhpYW9odQ0KPiA+DQo+ID4+IC0t
LS0t08q8/tStvP4tLS0tLQ0KPiA+PiC3orz+yMs6IG1wbHMgW21haWx0bzptcGxzLWJvdW5jZXNA
aWV0Zi5vcmddILT6se0gRWdnZXJ0LCBMYXJzDQo+ID4+ILeiy83KsbzkOiAyMDE0xOox1MI4yNUg
MTg6MjINCj4gPj4gytW8/sjLOiBJRVRGDQo+ID4+ILOty806IG1wbHNAaWV0Zi5vcmcNCj4gPj4g
1vfM4jogUmU6IFttcGxzXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTA0LnR4
dD4NCj4gPj4gKEVuY2Fwc3VsYXRpbmcgTVBMUyBpbiBVRFApIHRvIFByb3Bvc2VkIFN0YW5kYXJk
DQo+ID4+DQo+ID4+IEhpLA0KPiA+Pg0KPiA+PiBPbiAyMDE0LTEtMiwgYXQgMTY6MTQsIFRoZSBJ
RVNHIDxpZXNnLXNlY3JldGFyeUBpZXRmLm9yZz4gd3JvdGU6DQo+ID4+PiAtICdFbmNhcHN1bGF0
aW5nIE1QTFMgaW4gVURQJw0KPiA+Pj4gPGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQudHh0PiBh
cyBQcm9wb3NlZCBTdGFuZGFyZA0KPiA+Pg0KPiA+Pg0KPiA+PiB0aGlzIGRvY3VtZW50IG5lZWRz
IHRvIGRlc2NyaWJlIGhvdyBpdCBhZGRyZXNzZXMgdGhlIGlzc3VlcyByYWlzZWQgaW4NCj4gPj4g
QkNQMTQ1IChSRkM1NDA1KS4gSXQgYWxyZWFkeSBjb250YWlucyBzb21lIHRleHQgYWJvdXQgbWVz
c2FnZXMgc2l6ZXMNCj4gPj4gYW5kIGNvbmdlc3Rpb24gY29uc2lkZXJhdGlvbnMsIHdoaWNoIGlz
IGdyZWF0LiBVbmZvcnR1bmF0ZWx5LCB0aGUNCj4gPj4gdGV4dCBhYm91dCBjb25nZXN0aW9uIGNv
bnNpZGVyYXRpb25zIGlzIG5vdCBmdWxseSBpbiBsaW5lIHdpdGggUkZDNTQwNS4NCj4gPj4NCj4g
Pj4gTGFycw0KDQo=

From xuxiaohu@huawei.com  Fri Jan 10 02:07:35 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81DA71ACD04; Fri, 10 Jan 2014 02:07:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAQk_Ozv6tkZ; Fri, 10 Jan 2014 02:07:33 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 39CBF1AD7C0; Fri, 10 Jan 2014 02:07:33 -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.7-GA FastPath queued) with ESMTP id BCI93476; Fri, 10 Jan 2014 10:07:23 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 10:06:39 +0000
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 10 Jan 2014 10:07:16 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Fri, 10 Jan 2014 18:07:14 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "Eggert, Lars" <lars@netapp.com>, IETF <ietf@ietf.org>
Subject: =?gb2312?B?tPC4tDogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1pbi11?= =?gb2312?B?ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGluZyBNUExTIGluIFVEUCkgdG8gUHJv?= =?gb2312?Q?posed_Standard?=
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw///ZboCAAJRTEA==
Date: Fri, 10 Jan 2014 10:07:13 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08243BC5@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <52CFBA49.8070500@cisco.com>
In-Reply-To: <52CFBA49.8070500@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 10 Jan 2014 09:01:07 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 10:07:35 -0000

SGkgU3Rld2FydCwNCg0KVGhhbmtzIGZvciB0aGF0IGluZm9ybWF0aW9uIGFuZCBJIHdpbGwgbG9v
ayBhdCBpdC4NCg0KQmVzdCByZWdhcmRzLA0KWGlhb2h1DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0t
DQo+ILeivP7IyzogU3Rld2FydCBCcnlhbnQgW21haWx0bzpzdGJyeWFudEBjaXNjby5jb21dDQo+
ILeiy83KsbzkOiAyMDE0xOox1MIxMMjVIDE3OjE2DQo+IMrVvP7IyzogWHV4aWFvaHU7IEVnZ2Vy
dCwgTGFyczsgSUVURg0KPiCzrcvNOiBtcGxzQGlldGYub3JnDQo+INb3zOI6IFJlOiBbbXBsc10g
TGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50eHQ+IChFbmNhcHN1bGF0aW5n
IE1QTFMNCj4gaW4gVURQKSB0byBQcm9wb3NlZCBTdGFuZGFyZA0KPiANCj4gUkZDMzk4NS82LjUu
ICBDb25nZXN0aW9uIENvbnNpZGVyYXRpb25zDQo+IG1heSBoYXZlIHNvbWUgdXNlZnVsIHRleHQu
DQo+IA0KPiBXZSBoYXZlIGEgbG90IG9mIGRlcGxveW1lbnQgZXhwZXJpZW5jZSB3aXRoIFBXcyBh
bmQgZnJhbmtseSBJIGhhdmUgbmV2ZXIgc2Vlbg0KPiBhIGNvbmdlc3Rpb24gY29tcGxhaW4gcmFp
c2VkIGZyb20gdGhlIGZpZWxkLg0KPiANCj4gU3Rld2FydA0KPiANCj4gDQo+IA0KPiBPbiAxMC8w
MS8yMDE0IDAzOjQ2LCBYdXhpYW9odSB3cm90ZToNCj4gPiBIaSBMYXJzLA0KPiA+DQo+ID4gVGhh
bmtzIGEgbG90IGZvciB5b3VyIGNvbW1lbnRzLg0KPiA+DQo+ID4gSSB3b25kZXIgd2hldGhlciB0
aGUgZm9sbG93aW5nIG1vZGlmaWVkIHRleHQgZm9yIENvbmdlc3Rpb24gQ29uc2lkZXJhdGlvbg0K
PiBzZWN0aW9uIGlzIE9LIGZyb20geW91ciBwb2ludCBvZiB2aWV3Og0KPiA+DQo+ID4gU2luY2Ug
dGhlIE1QTFMtaW4tVURQIGVuY2Fwc3VsYXRpb24gY2F1c2VzIE1QTFMgcGFja2V0cyB0byBiZSBm
b3J3YXJkZWQNCj4gdGhyb3VnaCAiVURQIHR1bm5lbHMiLCB0aGUgY29uZ2VzdGlvbiBjb250cm9s
IGd1aWRlbGluZXMgZm9yIFVEUCB0dW5uZWxzIGFzDQo+IGRlZmluZWQgaW4gU2VjdGlvbiAzLjEu
MyBvZiBbUkZDNTQwNV0gU0hPVUxEIGJlIGZvbGxvd2VkLiBTcGVjaWZpY2FsbHksIE1QTFMNCj4g
Y2FuIGNhcnJ5IGEgbnVtYmVyIG9mIGRpZmZlcmVudCBwcm90b2NvbHMgYXMgcGF5bG9hZHMuIFdo
ZW4gdGhlIHBheWxvYWQgdHJhZmZpYw0KPiBpcyBJUC1iYXNlZCBhbmQgY29uZ2VzdGlvbi1jb250
cm9sbGVkLCB0aGUgVURQIHR1bm5lbCBTSE9VTEQgTk9UIGVtcGxveSBpdHMNCj4gb3duIGNvbmdl
c3Rpb24gY29udHJvbCBtZWNoYW5pc20sIGJlY2F1c2UgY29uZ2VzdGlvbiBsb3NzZXMgb2YgdHVu
bmVsZWQNCj4gdHJhZmZpYyB3aWxsIGFscmVhZHkgdHJpZ2dlciBhbiBhcHByb3ByaWF0ZSBjb25n
ZXN0aW9uIHJlc3BvbnNlIGF0IHRoZSBvcmlnaW5hbA0KPiBzZW5kZXJzIG9mIHRoZSB0dW5uZWxl
ZCB0cmFmZmljLiBXaGVuIHRoZSBwYXlsb2FkIHRyYWZmaWMgaXMgbm90IGtub3duIHRvIGJlDQo+
IElQLWJhc2VkLCBvciBpcyBrbm93biB0byBiZSBJUC1iYXNlZCBidXQgbm90IGNvbmdlc3Rpb24t
Y29udHJvbGxlZCwgdGhlIFVEUA0KPiB0dW5uZWwgU0hPVUxEIGVtcGxveSBhbiBhcHByb3ByaWF0
ZSBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtLg0KPiBGdXJ0aGVybW9yZSwgYmVjYXVzZSBV
RFAgdHVubmVscyBhcmUgdXN1YWxseSBidWxrLXRyYW5zZmVyIGFwcGxpY2F0aW9ucyBhcyBmYXIN
Cj4gYXMgdGhlIGludGVybWVkaWF0ZSByb3V0ZXJzIGFyZSBjb25jZXJuZWQsIHRoZSBndWlkZWxp
bmVzIGFzIGRlZmluZWQgaW4gU2VjdGlvbg0KPiAzLjEuMSBvZiBbUkZDNTQwNV0gU0hPVUxEIGFw
cGx5Lg0KPiA+DQo+ID4gQmVzdCByZWdhcmRzLA0KPiA+IFhpYW9odQ0KPiA+DQo+ID4+IC0tLS0t
08q8/tStvP4tLS0tLQ0KPiA+PiC3orz+yMs6IG1wbHMgW21haWx0bzptcGxzLWJvdW5jZXNAaWV0
Zi5vcmddILT6se0gRWdnZXJ0LCBMYXJzDQo+ID4+ILeiy83KsbzkOiAyMDE0xOox1MI4yNUgMTg6
MjINCj4gPj4gytW8/sjLOiBJRVRGDQo+ID4+ILOty806IG1wbHNAaWV0Zi5vcmcNCj4gPj4g1vfM
4jogUmU6IFttcGxzXSBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTA0LnR4dD4N
Cj4gPj4gKEVuY2Fwc3VsYXRpbmcgTVBMUyBpbiBVRFApIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQo+
ID4+DQo+ID4+IEhpLA0KPiA+Pg0KPiA+PiBPbiAyMDE0LTEtMiwgYXQgMTY6MTQsIFRoZSBJRVNH
IDxpZXNnLXNlY3JldGFyeUBpZXRmLm9yZz4gd3JvdGU6DQo+ID4+PiAtICdFbmNhcHN1bGF0aW5n
IE1QTFMgaW4gVURQJw0KPiA+Pj4gIDxkcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTA0LnR4dD4gYXMg
UHJvcG9zZWQgU3RhbmRhcmQNCj4gPj4NCj4gPj4gdGhpcyBkb2N1bWVudCBuZWVkcyB0byBkZXNj
cmliZSBob3cgaXQgYWRkcmVzc2VzIHRoZSBpc3N1ZXMgcmFpc2VkIGluDQo+ID4+IEJDUDE0NSAo
UkZDNTQwNSkuIEl0IGFscmVhZHkgY29udGFpbnMgc29tZSB0ZXh0IGFib3V0IG1lc3NhZ2VzIHNp
emVzDQo+ID4+IGFuZCBjb25nZXN0aW9uIGNvbnNpZGVyYXRpb25zLCB3aGljaCBpcyBncmVhdC4g
VW5mb3J0dW5hdGVseSwgdGhlDQo+ID4+IHRleHQgYWJvdXQgY29uZ2VzdGlvbiBjb25zaWRlcmF0
aW9ucyBpcyBub3QgZnVsbHkgaW4gbGluZSB3aXRoIFJGQzU0MDUuDQo+ID4+DQo+ID4+IExhcnMN
Cj4gPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiA+
IG1wbHMgbWFpbGluZyBsaXN0DQo+ID4gbXBsc0BpZXRmLm9yZw0KPiA+IGh0dHBzOi8vd3d3Lmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vbXBscw0KPiANCj4gDQo+IC0tDQo+IEZvciBjb3Jwb3Jh
dGUgbGVnYWwgaW5mb3JtYXRpb24gZ28gdG86DQo+IA0KPiBodHRwOi8vd3d3LmNpc2NvLmNvbS93
ZWIvYWJvdXQvZG9pbmdfYnVzaW5lc3MvbGVnYWwvY3JpL2luZGV4Lmh0bWwNCj4gDQoNCg==

From gregory.mirsky@ericsson.com  Fri Jan 10 10:24:16 2014
Return-Path: <gregory.mirsky@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B00F1AE16E; Fri, 10 Jan 2014 10:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Stf5jOuFacCl; Fri, 10 Jan 2014 10:24:14 -0800 (PST)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id A0D771AE037; Fri, 10 Jan 2014 10:24:14 -0800 (PST)
X-AuditID: c618062d-b7f278e000005a8f-15-52d03ac08793
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 18.65.23183.0CA30D25; Fri, 10 Jan 2014 19:24:01 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0347.000; Fri, 10 Jan 2014 13:24:03 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "Eggert, Lars" <lars@netapp.com>, Joel Halpern <jmh@joelhalpern.com>
Subject: RE: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDi/NnXFwG1Tc20SQPsVMzJPOgJp+RLFA
Date: Fri, 10 Jan 2014 18:24:02 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
In-Reply-To: <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.135]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrDLMWRmVeSWpSXmKPExsUyuXRPgu5BqwtBBu+2iFo82zifxeLjqTdM Fi9e97BY3Fq6ktWBxWPJkp9MHuemfGf0mPHpC1sAcxSXTUpqTmZZapG+XQJXxtJFO1gLbvJX 7H/+hrmB8SpPFyMnh4SAicSHtscsELaYxIV769lAbCGBI4wSDb3mEPZyRonN61NAbDYBI4kX G3vYQWwRAQ+Jz2t3g9nMApYSR2cfAusVFsiSeHDnByNETbbEwZ07mSBsI4ndG16A1bMIqErM a20Dq+EV8JW4suYG0A1cQLvOMkm0HN0I1sApYCdx9exusKGMQMd9P7WGCWKZuMStJ/OZII4W kFiy5zwzhC0q8fLxP1YIW1ni+5xHLBD1OhILdn9ig7C1JZYtfM0MsVhQ4uTMJywTGMVmIRk7 C0nLLCQts5C0LGBkWcXIUVqcWpabbmSwiREYQ8ck2HR3MO55aXmIUZqDRUmc98tb5yAhgfTE ktTs1NSC1KL4otKc1OJDjEwcnFINjApCTtufOf+s3/L4q8N+myW71rWGZztMymF6lrgx8Ouu Hwx7Tp3aI7s5WaXK9B1b64ReBstPS8vlGoWubOsTuq9w4fuEN0XcW9wt3QUvynJoeMqxc79k 2CK63KJL6oUJp5DQThuZtCda55yv96zQeTBvyuNzX9u0hSK6ji/b/7Myd/1V2QMHliuxFGck GmoxFxUnAgBF/cFlbwIAAA==
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 18:24:16 -0000

Hi Lars,
I think that " The whole point of running MPLS is to create networks in whi=
ch paths are provisionable, so this is usually not an issue." is only parti=
ally correct. LDP-based MPLS network is not provisionable and LSPs follow I=
P best route selection. Explicit signaling of LSP is achievable in (G)MPLS =
by using RSVP(-TE) signaling.

	Regards,
		Greg

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Eggert, Lars
Sent: Friday, January 10, 2014 8:10 AM
To: Joel Halpern
Cc: mpls@ietf.org; IETF
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Hi,

On 2014-1-10, at 16:36, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> Maybe I am completely missing things, but this looks wrong.
> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion=20
> control will make it more likely that the service won't work.  Is that=20
> really the goal?
>=20
> We do not perform congestion control on MPLS LSPs.
> Assuming that a UDP tunnel is carrying just MPLS and was established=20
> just for MPLS, why would we expect it to behave differently than an=20
> MPLS LSP running over the exact same path, carrying the exact same traffi=
c?

we've been rehashing this discussion several times over the years, e.g., fo=
r PWE, AMT, etc. In order to carry fixed-rate or otherwise non-congestion-c=
ontrolled traffic over unprovisioned general Internet paths, there needs to=
 be some sort of basic congestion control mechanism, like a circuit breaker=
.

The whole point of running MPLS is to create networks in which paths are pr=
ovisionable, so this is usually not an issue. But if you start sticking MPL=
S inside of UDP, those packets can go anywhere on the net, so you need mech=
anisms to control the rate of that traffic if it causes congestion, or at t=
he very least you need to be able to stop the traffic if it creates severe =
congestion.

Lars

From scott.brim@gmail.com  Fri Jan 10 12:42:19 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F361AE12A; Fri, 10 Jan 2014 12:42:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id febzYUiKQLhd; Fri, 10 Jan 2014 12:42:18 -0800 (PST)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E672D1AE124; Fri, 10 Jan 2014 12:42:17 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id l6so5579663oag.19 for <multiple recipients>; Fri, 10 Jan 2014 12:42:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=moG0yemAQwwvJIWbwjt1o1ztST01ymzMWqGDB9RKYEQ=; b=hMx+Y11JeUSseArOuA3sP/D3RQ7P7fbrOtKAS7/yyIhP6UCutPragbQFvA7hF8XEnx 7fnoJG1/eKcJpktmEzvC2KmAkwPJV83Rusj+UGgceHqID1pKarMkMYaKcZaQTxS6+d5I utUjBmmm4jI8NGGHDtErI1RIfis8PXZf4IcfDnAs4RsGCKb8ukkaGhdQxdsz5VuwLQ9G H8fQ9wQuP/1ClIOZG0Eo42rbEaWadDrpMG/RgJEQMUyFA2vREwheZWK+EnQ+BPxXUmBB sbb7KVc7Kp2wh1CCSoktop1JQgP/PwCO0h9IE+JT+eDNW+SrveJ9X/St1LxoY5jRq/6J 72Gw==
X-Received: by 10.60.136.196 with SMTP id qc4mr9638611oeb.41.1389386527805; Fri, 10 Jan 2014 12:42:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 10 Jan 2014 12:41:47 -0800 (PST)
In-Reply-To: <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 10 Jan 2014 15:41:47 -0500
Message-ID: <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Edward Crabbe <edc@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 20:42:19 -0000

On Fri, Jan 10, 2014 at 3:14 PM, Edward Crabbe <edc@google.com> wrote:
> +1
>
> Let the encapsulated transport protocols take care of the congestion
> end-to-end.

Xu Xiaohu proposed a good paragraph:
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=75392&tid=1389386424

From jmh@joelhalpern.com  Fri Jan 10 12:48:03 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3168A1AE116; Fri, 10 Jan 2014 12:48:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6SXdvSz7JJzX; Fri, 10 Jan 2014 12:48:01 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id D6B6A1AE0C6; Fri, 10 Jan 2014 12:48:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 35F061C0D2E; Fri, 10 Jan 2014 12:47:52 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 29102620DAE; Fri, 10 Jan 2014 12:47:51 -0800 (PST)
Message-ID: <52D05C75.3050505@joelhalpern.com>
Date: Fri, 10 Jan 2014 15:47:49 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, Edward Crabbe <edc@google.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com> <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com>
In-Reply-To: <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 20:48:03 -0000

The problem with taht paragraph is that it assumes that the UDP 
encapsulator knows what the payload is.
It seems to me that one could easily be applying the UDP in any one of a 
number of cases where the payload will not be known.
So the requirement in the paragraph seems at best difficult to meet.

And has been noted, this seems to place an expectation on UDP 
encapsulated MPLS that is not present for MPLS itself, when the traffic 
is not known to be IP.

Yours,
Joel

On 1/10/14 3:41 PM, Scott Brim wrote:
> On Fri, Jan 10, 2014 at 3:14 PM, Edward Crabbe <edc@google.com> wrote:
>> +1
>>
>> Let the encapsulated transport protocols take care of the congestion
>> end-to-end.
>
> Xu Xiaohu proposed a good paragraph:
> https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=75392&tid=1389386424
>

From scott.brim@gmail.com  Fri Jan 10 13:32:36 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC371AE1E1; Fri, 10 Jan 2014 13:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYyHLZzaosdI; Fri, 10 Jan 2014 13:32:34 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 30AFD1AE1D3; Fri, 10 Jan 2014 13:32:33 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id vb8so5301438obc.8 for <multiple recipients>; Fri, 10 Jan 2014 13:32:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FQc3/hCV61AVpz/i8uWVPiJiCv37btbVGsRN2qG2ZcM=; b=Ls7/51+a09ybWl1R3ILoQBG3lfy67av0R/vd/vT8kl67Eg2F/47+AllcbHs4QXF8xu xTuNb5ZUYDCjK8LPpWTBdOX4Lv+f17x8+hl5i9jVYWCKL9Xk3fweg0pZD+jISdMWxMf7 Nk9V6ZkobBk9mfhrfH/gzy1T04XIFbMvVQpa2KZb4RIYG/ONblZmVPAWrEiVZ7SPpxzd 1DuGF7+S8Zum6LzGQb6jS8/ClvV7wQVv49aFxPE06yoRwm/qZ4BYo5LDPOn10G4rSzWH 6Mc0cWuB9zojk3KsZLYjiQCl5TaaKeRGn23uz0pNAQwMGHiGptWyMC3uzkDjiwpPRTnq ZFNg==
X-Received: by 10.60.174.167 with SMTP id bt7mr8891124oec.54.1389389543027; Fri, 10 Jan 2014 13:32:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 10 Jan 2014 13:32:02 -0800 (PST)
In-Reply-To: <52D05C75.3050505@joelhalpern.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com> <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com> <52D05C75.3050505@joelhalpern.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 10 Jan 2014 16:32:02 -0500
Message-ID: <CAPv4CP_33OU-s+8xt9t5voAtiXMS3pw2+67w9=FxpS2cAOmDeg@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 21:32:36 -0000

On Fri, Jan 10, 2014 at 3:47 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> The problem with taht paragraph is that it assumes that the UDP encapsulator
> knows what the payload is.
> It seems to me that one could easily be applying the UDP in any one of a
> number of cases where the payload will not be known.
> So the requirement in the paragraph seems at best difficult to meet.
>
> And has been noted, this seems to place an expectation on UDP encapsulated
> MPLS that is not present for MPLS itself, when the traffic is not known to
> be IP.

OK good point - so we invoke the end-to-end argument on MPLS's behalf.

From randy@psg.com  Fri Jan 10 13:32:51 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5757D1AE1F1; Fri, 10 Jan 2014 13:32:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8YqSJsXt4R1; Fri, 10 Jan 2014 13:32:47 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 745E11AE1C4; Fri, 10 Jan 2014 13:32:47 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W1jgm-00052S-IS; Fri, 10 Jan 2014 21:32:25 +0000
Date: Sat, 11 Jan 2014 06:32:22 +0900
Message-ID: <m2vbxr34m1.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Tinka <mark.tinka@seacom.mu>
Subject: Re: misdelivered mpls packets - Was: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft
In-Reply-To: <201401092048.16168.mark.tinka@seacom.mu>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <201401091437.04245.mark.tinka@seacom.mu> <52CECB7B.3090200@pi.nu> <201401092048.16168.mark.tinka@seacom.mu>
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: multipart/signed; boundary="pgp-sign-Multipart_Sat_Jan_11_06:32:17_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: gorry@erg.abdn.ac.uk, ietf@ietf.org, tsvwg@ietf.org, david.black@emc.com, jnc@mit.edu, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 21:32:51 -0000

--pgp-sign-Multipart_Sat_Jan_11_06:32:17_2014-1
Content-Type: text/plain; charset=US-ASCII

what may scare me most about this discussion is the lack of p in mpls
vns.  you just sent my very sensitive unencrypted packet to some very
bad place.
--pgp-sign-Multipart_Sat_Jan_11_06:32:17_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJS0GbmAAoJEMzMBey4OgLthBgH/3xr9a04RpbAoDRHj3cRHU3L
KE5JoBpvZtM1IlN56nt0/tbAns27BrXBLJkHRTYHYlbsa0U8APC5dNYk964zatiO
z+kryHsFOQVjW7x7SdMwjuIDLE6zlYdZd2buReZIF0g1NulJIqEsiSq6NEhFR/Lu
06uoysfaspBKRFU1X7LO312dX8dU7baFhWMrbHlpQs64Nof+pa7L6rJuFKZvVToR
NUiqHQrE8UnSB+Gtqki/JqRMHiF5emaGpZqlU6OlS1NXR42WrKM1ITWrJXeqONzf
gHJVmXmU10q5bRHbZHyo+mk8gKJ604mCJAk9uXMY7FWz4NqgsO1CCdR/wTm0EHA=
=hNpY
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Sat_Jan_11_06:32:17_2014-1--

From lars@netapp.com  Fri Jan 10 22:23:33 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B120D1AE041; Fri, 10 Jan 2014 22:23:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toHCxHOIb8YU; Fri, 10 Jan 2014 22:23:32 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1101AE035; Fri, 10 Jan 2014 22:23:32 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,642,1384329600";  d="asc'?scan'208";a="95450478"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 10 Jan 2014 22:23:21 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Fri, 10 Jan 2014 22:23:21 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAAPhcAgAAHp4CAAAGvgIAADFsAgACUVIA=
Date: Sat, 11 Jan 2014 06:23:20 +0000
Message-ID: <AAA47C6B-C06B-4C95-9D7E-4A7BAA40E480@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com> <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com> <52D05C75.3050505@joelhalpern.com> <CAPv4CP_33OU-s+8xt9t5voAtiXMS3pw2+67w9=FxpS2cAOmDeg@mail.gmail.com>
In-Reply-To: <CAPv4CP_33OU-s+8xt9t5voAtiXMS3pw2+67w9=FxpS2cAOmDeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.116]
Content-Type: multipart/signed; boundary="Apple-Mail=_F03B8410-331A-4839-BADD-9F7B10C21371"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jan 2014 06:23:33 -0000

--Apple-Mail=_F03B8410-331A-4839-BADD-9F7B10C21371
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-1-10, at 22:32, Scott Brim <scott.brim@gmail.com> wrote:
> OK good point - so we invoke the end-to-end argument on MPLS's behalf.

look at it the other way. =46rom the viewpoint of the rest of the net, =
you are an application using UDP. Such applications need to follow a set =
of principles we have IETF consensus on (RFC5405).

By encapsulating MPLS in UDP, you are changing the game. That traffic =
can now appear on any Internet path, and not just inside provisioned =
networks. Because of that, you need a mechanism to detect if you are =
causing congestion, and a mechanism to react to it.

And it *is* a requirement on the encapsulator, because from the =
perspective of the rest of the net, that is the application that =
generates the UDP traffic.

Lars

--Apple-Mail=_F03B8410-331A-4839-BADD-9F7B10C21371
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtDjP9ZcnpRveo1xAQJiQAP/Ytgorv2DhWWGHAudxHLokDsN5Na53mhY
Xh6G1ABbKcf3KMHrEEv8XgmSmQb9+zeyQRx1YKvsWTeCabZB/y1e27Q98ziTPO3I
nuQvjxKZMscJ/sohP0SizTy9710q81fTlfFJ2wWapKlafOCdYG588Q7LEkMaTvs5
PafkaLpsaDE=
=tle/
-----END PGP SIGNATURE-----

--Apple-Mail=_F03B8410-331A-4839-BADD-9F7B10C21371--

From mansaxel@besserwisser.org  Fri Jan 10 22:49:41 2014
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B11F71AE082 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 22:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dCyo87ND5Uf1 for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 22:49:40 -0800 (PST)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id DED371AE070 for <ietf@ietf.org>; Fri, 10 Jan 2014 22:49:39 -0800 (PST)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 85EC29E66; Sat, 11 Jan 2014 07:49:28 +0100 (CET)
Date: Sat, 11 Jan 2014 07:49:28 +0100
From: mansaxel@besserwisser.org
To: John R Levine <johnl@taugh.com>
Subject: Re: Multi-homed BCP38
Message-ID: <20140111064928.GA7838@besserwisser.org>
References: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com> <20140109191747.20009.qmail@joyce.lan> <20140110083306.GI7517@besserwisser.org> <alpine.BSF.2.00.1401100911270.14012@joyce.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1401100911270.14012@joyce.lan>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jan 2014 06:49:41 -0000

--DocE+STaALJfprDB
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Multi-homed BCP38 Date: Fri, Jan 10, 2014 at 09:12:11AM -0500 =
Quoting John R Levine (johnl@taugh.com):
> >Subject: Re: Multi-homed BCP38 Date: Thu, Jan 09, 2014 at 07:17:47PM -00=
00 Quoting John Levine (johnl@taugh.com):
> >
> >>Also, if you'll review the messages to which you're responding, you'll
> >>note that the customer is often an ISP with customers of its own so
> >>there are far too many ranges to handle manually.
> >
> >An "ISP" who does not understand and use BGP is probably not serious.
>=20
> It must be nice to live in a world where you can turn away customers
> who pay a lot of money, just because they're not serious enough.

The ISP business is not really a high profit margin one. Some customers
are a loss. The tendency of wanting to multihome without running a routing
protocol is a good indicator of lower profit margin. If for nothing else
then for the increased support load.

There used to be threshold problems with getting AS numbers and such, but t=
he=20
increased AS number space helps a lot.  The arguments against DTRT are weak=
er.=20

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
GOOD-NIGHT, everybody ... Now I have to go administer FIRST-AID to my
pet LEISURE SUIT!!

--DocE+STaALJfprDB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iEYEARECAAYFAlLQ6XgACgkQ02/pMZDM1cVikgCcDvEXj1FaVYYBqbCO1FXkubT2
82oAn18u/68EpUbq9MFo1CNaOuJho61K
=bRYZ
-----END PGP SIGNATURE-----

--DocE+STaALJfprDB--

From prvs=008189ecb6=johnl@taugh.com  Fri Jan 10 23:10:13 2014
Return-Path: <prvs=008189ecb6=johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BC51AE0BC for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 23:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHCYN6a-TkYp for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 23:10:11 -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 BB6781ACCEE for <ietf@ietf.org>; Fri, 10 Jan 2014 23:10:11 -0800 (PST)
Received: (qmail 60478 invoked from network); 11 Jan 2014 07:10:01 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 11 Jan 2014 07:10:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=159d4.52d0ee48.k1312; i=johnl%iecc.com@submit.iecc.com; bh=NyLYT7SZckfvXRmheRgAHOPvYF5pl7l/wG87XumRbgM=; b=ZeNR6Oldsk8WlPzexIWTr2mtO/L1CKpCFL5pajnZ/xAZ03LruXo3NFAuCUWPzazIyHiWg/WY+LIQHblUJiRPFYUSKEls4S32mNtdElDgVqREd4VPwuNVyNRSUpYtDWIrSm3tnSPpMw9j032HDClTQd2aiMvNZseAp9s6nLp/ZCyY6PV6nAbmGNIJR83MRVi5qx9XhriHKDuZffLTP1RhajD2GSV17ep9lo9qQXxh3B6JHVhW2p0kXAUl9uRgnDoS
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=159d4.52d0ee48.k1312; olt=johnl%iecc.com@submit.iecc.com; bh=NyLYT7SZckfvXRmheRgAHOPvYF5pl7l/wG87XumRbgM=; b=CRsOYkntdqZnd4ClgzzOJRuPSt0bHIFNcwF4I7NCMUoXgKBKjNoJX7wvautu2uieORaNn0gY/DZKgrP/NM6uTDmPSgggCp/ksaoYkFUUdddHzXvGby1Uou86gk48Wto7zK7NOQ0fEfxzGmx/DKDOf6NTY7N5x7mMQAEZG6pZ7c0vuFThpKkHVu8Z7yeIxboI7+4oPlw6eoLcbQI0tOrCpQKtuXHtxCwXZZbCAA7feMMcA3to+ChyKyHg9VqOhxt+
Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 11 Jan 2014 07:10:00 -0000
Date: 11 Jan 2014 02:09:59 -0500
Message-ID: <alpine.BSF.2.00.1401110209040.19746@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: mansaxel@besserwisser.org
Subject: Re: Multi-homed BCP38
In-Reply-To: <20140111064928.GA7838@besserwisser.org>
References: <CAL9jLabYb59=EuSynERFr51aei+j5vt2RvWFaQAUWtp6RtUUQQ@mail.gmail.com> <20140109191747.20009.qmail@joyce.lan> <20140110083306.GI7517@besserwisser.org> <alpine.BSF.2.00.1401100911270.14012@joyce.lan> <20140111064928.GA7838@besserwisser.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jan 2014 07:10:13 -0000

>>>> Also, if you'll review the messages to which you're responding, you'll
>>>> note that the customer is often an ISP with customers of its own so
>>>> there are far too many ranges to handle manually.
>>>
>>> An "ISP" who does not understand and use BGP is probably not serious.
>>
>> It must be nice to live in a world where you can turn away customers
>> who pay a lot of money, just because they're not serious enough.
>
> The ISP business is not really a high profit margin one. Some customers
> are a loss. The tendency of wanting to multihome without running a routing
> protocol is a good indicator of lower profit margin. If for nothing else
> then for the increased support load.

It must be nice to live in a world where you know the profit margins of 
American ISPs better than they do.

By the way, not all of the multi-homed customers we're talking about are 
small ISPs, although some are.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

From sm@resistor.net  Sat Jan 11 00:43:51 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA33A1AE01C; Sat, 11 Jan 2014 00:43:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aKvR8U8-vGR0; Sat, 11 Jan 2014 00:43:50 -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 C347A1ADF94; Sat, 11 Jan 2014 00:43:50 -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 s0B8hV6B025282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Jan 2014 00:43:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389429820; bh=C6Z8t+l83M+TYdKDvTg0SjC8XRQpcB0h11Y1GnArE08=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QWD2CVKdDy6B66m1kfVcEeiszC3M0M1qUkRToxlsBS4xGa9Nco3XvdT36Kj6DoL8k do0r+RNSSU/ehGipG3iY/C0aACtGVeQf1FxElAdzfCOs9yu2fK8k5RsDb4ZxuV6ytA vMXjFUmmsvsubR77ZD9SsKR6ePXCzUFHFSudJLz0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1389429820; i=@resistor.net; bh=C6Z8t+l83M+TYdKDvTg0SjC8XRQpcB0h11Y1GnArE08=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qZvvpOpxcECNCgYLmXyNF5KUxjE+YKQF7rb+5YY7f2usVXTymv9YSv57NxwXSS9X5 /Oc7tbGsg3tpxwX6ObxUYM1+7/1y7OQhZiAtrJVFEra7VgOS8O4cs+6ym+3Qk+iF8Q P3w2dyM9nCD8yAW6y70D1H79dx0Cx+CZiFnZlKzM=
Message-Id: <6.2.5.6.2.20140111002617.06fe52c8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 11 Jan 2014 00:43:17 -0800
To: Andy Bierman <andy@yumaworks.com>
From: SM <sm@resistor.net>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
In-Reply-To: <CABCOCHTF4=zhwd25TWxh1pM8h_Tw2==WehDHuJaPPYMm3XWVUg@mail.g mail.com>
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com> <6.2.5.6.2.20140108233958.0a849e58@resistor.net> <20140109105804.GA44893@elstar.local> <6.2.5.6.2.20140109051548.0a951040@resistor.net> <CABCOCHTF4=zhwd25TWxh1pM8h_Tw2==WehDHuJaPPYMm3XWVUg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>, ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jan 2014 08:43:51 -0000

Hi Andy,
At 11:05 09-01-2014, Andy Bierman wrote:
>After reading the IANA Considerations section closer, I have some concerns
>about the use of a YANG enumeration. This section does not say who must
>update the enumeration typedef and republish the RFC containing the new
>YANG module, every time the TZ database is changed.
>Is it the NETMOD WG? IANA?

That would be IANA.  There is a comment from IANA about what it is 
being asked to do.  There hasn't been any public reply from the 
author of the draft.

The Last Call was announced on December 3, 2013.  The only responses 
have been from the Area Director, one of the working group Chairs, 
Martin Bjorklund and Andy Bierman.  If the document is published as a 
RFC it will be said to represent the consensus of the IETF ...

Regards,
-sm 


From l.wood@surrey.ac.uk  Sat Jan 11 18:59:58 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 550E71ACCF8; Sat, 11 Jan 2014 18:59:58 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E7Cl-HXCPHrL; Sat, 11 Jan 2014 18:59:56 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0441AD8EB; Sat, 11 Jan 2014 18:59:54 -0800 (PST)
Received: from [195.245.231.67:12094] by server-17.bemta-5.messagelabs.com id 91/A7-19152-F1502D25; Sun, 12 Jan 2014 02:59:43 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-13.tower-82.messagelabs.com!1389495582!35539380!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24692 invoked from network); 12 Jan 2014 02:59:42 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-13.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jan 2014 02:59:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sun, 12 Jan 2014 02:59:42 +0000
From: <l.wood@surrey.ac.uk>
To: <adrian@olddog.co.uk>, <randy@psg.com>
Date: Sun, 12 Jan 2014 02:59:41 +0000
Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: AQLp3cWoqiSzZKGjmFXJEPC82F9z6gH14gYaAYJCBgICOkjTg5gY93XwgAQ4kWA=
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <290E20B455C66743BE178C5C84F1240847E63346B0@EXMB01CMS.surrey.ac.uk>, <m2d2k1a8ze.wl%randy@psg.com> <290E20B455C66743BE178C5C84F1240847E63346B5@EXMB01CMS.surrey.ac.uk>, <012801cf0d24$9b80b180$d2821480$@olddog.co.uk>
In-Reply-To: <012801cf0d24$9b80b180$d2821480$@olddog.co.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 02:59:58 -0000

On nested checksums, the question is how they are nested; it's a matter
of scope. With a bunch of checksums checking only a payload and any
inner checksums like Russian Matryoshka dolls, the end-to-end argument
tells us that for reliable receipt of the payload, only the innermost check=
sum
matters.

But here, we are not solely checking the payload, but information on how to
deliver and identify that payload - and while an outer Ethernet CRC is acro=
ss
the last link, the UDP checksum, though weak, provides a check on the IP
addresses and UDP ports (via the  pseudoheader check) and MPLS stack
from UDP/IP source to UDP/IP destination (and the payload, which is the bit
everyone focuses on as the performance hit as redundant and a processing
cost when the payload has its own check, and the bit that UDP-Lite can leav=
e out).

Nothing else checks that scope. The scope is wider, and affects the network
as a whole. Errors in these unchecked fields lead to misdirection and lead =
to
misdelivery. Or pollution of other ports.

The MPLS assumption is that it's protected and checked by a strong link CRC=
 like
Ethernet, and checked/regenerated by stack processing between hops; here,
in a path context, with zero UDP checksums MPLS has no checking at all.

"consequences for cheap hardware and for software implementations"

I'm sorry, when was MPLS cheap?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Adrian Farrel [adrian@olddog.co.uk]
Sent: 09 January 2014 10:21
To: Wood L  Dr (Electronic Eng); randy@psg.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com=
; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: R=
E: [tsvwg] Milestones changed for tsvwg WG)

Lloyd and Randy,

With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls=
, so
thanks for the comments.

We did take the precaution of sending this I-D for an early TSV Directorate
review because of the concern about a number of factors and the overlap wit=
h
tsvwg work, but the review came back "clean". Of course, such a review is j=
ust
one person, so this conversation is good.

Wrt zero checksum, where do you stand on nested checksums? There is some cl=
aim
that they represent a waste of processing. I am not convinced by that when =
each
layer is using dedicated hardware (that can presumably process checksums at=
 line
speed), but I am interested in the consequences for cheap hardware and for
software implementations (as have been claimed to be some of the motivation=
s for
this work).

Other TSV-related issues that surely pop up are:
- allocation of ports for foo-in-UDP
- congestion control

Please note that there are a number of I-Ds that you missed in your broad s=
weep
of "I am opposed". You should probably look at the NVGRE and VXLAN work (wh=
ich I
think is lurking around the NVO3 working group) because that is also lookin=
g at
UDP encaps of a tunnelling protocol.

Thanks,
Adrian

Health warnings:
I am responsible AD for draft-ietf-mpls-in-udp
I am a co-author of the gre-in-udp draft.

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.u=
k
> Sent: 09 January 2014 08:07
> To: randy@psg.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.c=
om;
> tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was:=
 RE:
> [tsvwg] Milestones changed for tsvwg WG)
>
> Randy,
>
> okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
> consensus on  it. And then the authors can adopt that consensus for
mpls-in-udp,
> which overlaps in authorship...
>
> thanks,
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Randy Bush [randy@psg.com]
> Sent: 09 January 2014 07:51
> To: Wood L  Dr (Electronic Eng)
> Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.o=
rg;
> jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
> Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [t=
svwg]
> Milestones changed for tsvwg WG)
>
> > Because they specify zero UDP checksums,
> > I oppose publication of draft-ietf-mpls-in-udp in its current form
> > I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its cur=
rent
> form.
> > I oppose the IETF lisp documents.
>
> lloyd,
>
> i think i understand your position.  but i disagree with preventing wg
> adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
> see wg adoption as how we get to discuss and work on a document, not as
> approval of the document.  as david said, i think we need to discuss it
> so we can decide if it should be fixed.  to do so, we have to adopt it.
>
> randy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From ron.even.tlv@gmail.com  Sun Jan 12 04:37:14 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 977131ADED7; Sun, 12 Jan 2014 04:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XzVYH_dWL-SF; Sun, 12 Jan 2014 04:37:12 -0800 (PST)
Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id EF2871AD738; Sun, 12 Jan 2014 04:37:11 -0800 (PST)
Received: by mail-ea0-f177.google.com with SMTP id n15so2840461ead.8 for <multiple recipients>; Sun, 12 Jan 2014 04:37:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=zIa5p7O5Qp3j9Ac4piQlJALHO6C8x2rim4+sGVq1PR0=; b=XKocWa5W0aypVBlY+w5CnZmUfjX3yIbLvLZDo9xJar2lD7lVPnvdPcRcAZCAgMIrY/ O05wEDbSftMsmTnCbjMugkdhhabsXSqdn1xd8KjZqy4ZP7H77gGrpeALOHBGtuwgvm6B IVdMSgtwAjynmjGIGdq09SwjHzWKfzaZYjylzCk/MTpqPAj4z5kb0BK/EZz+VMv9e+0I OD3bDpM+5pUdSqN3AD4PrGcD0TKBD35l5uhoA9YePl9ZFD97znbmImYSDXzyNCIoHCVb c6P5b8RzROh2T1Yu2KzFvAzcCZFi+Q773ZVl2W+D//5CyLrpLWXf7Yx37DZvpER0JPe3 Q8tw==
X-Received: by 10.15.51.13 with SMTP id m13mr2294734eew.103.1389530220943; Sun, 12 Jan 2014 04:37:00 -0800 (PST)
Received: from RoniE ([109.64.17.204]) by mx.google.com with ESMTPSA id o13sm30735504eex.19.2014.01.12.04.36.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 12 Jan 2014 04:37:00 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-in-udp.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-in-udp-04
Date: Sun, 12 Jan 2014 14:33:13 +0200
Message-ID: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_10B1_01CF0FA3.3FF795F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8PkQgMv9aHcPU1QKqHAKnrA2qEzA==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 12:37:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_10B1_01CF0FA3.3FF795F0
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-mpls-in-udp-04

Reviewer: Roni Even

Review Date:2014-1-12

IETF LC End Date: 2014-1-16

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments

1.       The abstract section can be expanded with text from the first
paragraph of the introduction providing more information about usage

2.       The congestion section may need some text on UDP congestion
support, maybe reference RFC4505 but I am also OK with most of the current
text.

 

 


------=_NextPart_000_10B1_01CF0FA3.3FF795F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:.5in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:246115313;
	mso-list-type:hybrid;
	mso-list-template-ids:1460930480 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:&n=
bsp; </span><span style=3D'font-family:"Courier =
New"'>draft-ietf-mpls-in-udp-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:2014&#8211;1-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: 2014&#8211;1-16<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
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=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The abstract section can =
be expanded with text from the first paragraph of the introduction =
providing more information about usage<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>The congestion section =
may need some text on UDP congestion support, maybe reference RFC4505 =
but I am also OK with most of the current text.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_10B1_01CF0FA3.3FF795F0--


From hallam@gmail.com  Sun Jan 12 08:02:15 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD991ADFD7 for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 08:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.701
X-Spam-Level: *
X-Spam-Status: No, score=1.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_PHARMACY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RKp0FMI_Mw-1 for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 08:02:14 -0800 (PST)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id CEB131ADF24 for <ietf@ietf.org>; Sun, 12 Jan 2014 08:02:13 -0800 (PST)
Received: by mail-la0-f52.google.com with SMTP id c6so696756lan.39 for <ietf@ietf.org>; Sun, 12 Jan 2014 08:02:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GaWLO3rCOij6wMBRVoU6NE7sKmgddUi9w86H/rRGhVo=; b=WiFesLgCN5X9kLdScfgeQ623O/Q91e6HXeYjphwGCIs/+9E/1caS1PTrnAKIPw3ziA XYUaGIa1PbCcFZqj0ipGGEnXadIa/Ol2eEtc5VoHgSoh9i4zefiRRS8LP6P1Ltp8VASh IhQR6RmL/Kflz/XFCy6h5yBqEp1PQ7UOrOxZHq17gr8YfPpNOfgzPX6U/vupn2ywhEZ8 7KJeprCiZ5cpAZpycVlZOuLrt3sixQQ/SLUhIHLl7jVNoFqwyZ/LQAYZvN9XQorGATQC e0cAIvlWSBnSgH1msnFxBuR8TcqZPoHI0UQGsjJ0Y+nY/VcO4/nXhDQCkIH+vmIqqwwr E5Yw==
MIME-Version: 1.0
X-Received: by 10.152.20.6 with SMTP id j6mr8288437lae.8.1389542522181; Sun, 12 Jan 2014 08:02:02 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Sun, 12 Jan 2014 08:02:02 -0800 (PST)
Date: Sun, 12 Jan 2014 11:02:02 -0500
Message-ID: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
Subject: A DNS security issue that might actually have impact eventually
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e013d20346f5d2f04efc81407
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 16:02:16 -0000

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

In recent news there have been two cases of DNS registrars being 'ordered'
to take down domain names and lock them against transfer. The city of
London police case is well known. There is also a Pharmacy industry group
asserting the 'right' to take down sites without a court order or any form
of due process.

http://www.techdirt.com/articles/20140110/12140025836/pharmacy-lobbyists-lie-to-registrars-if-we-complain-about-site-it-must-be-taken-down-no-questions-asked.shtml

What is worrying here is not just the lack of oversight in these particular
cases. If these practices become a regular occurrence they are going to be
interpreted as an attack and countermeasures will begin to emerge.

We have indeed already seen the emergence of one such countermeasure
'Namecoin' which applies Bitcoin to "replace" the DNS and according to some
this also "deprecates" the WebPKI.

The main application for Namecoin appears to be the same as the main
application for Bitcoin itself: Enabling the dotcom revolution to finally
extend to the provision of recreational pharmaceuticals. But the Namecoin
technology if successful would also be used for much more including
applications most of us support (dissident speech against authoritarian
regimes) and applications none of us support (child abuse, etc.).

At the moment use of Namecoin is restricted to a particular niche and is
unlikely to gain widespread acceptance. It is also a technology designed by
geeks for geeks in the finest tradition of calling anyone who can't grock
it a luser.

But if the principle of due process comes under further attack, we are
going to find ourselves in a different domain and the demand for a naming
infrastructure that is not exposed to the risk of arbitrary search and
seizure will grow.



-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><div>In recent news there have been two cases of DNS regis=
trars being &#39;ordered&#39; to take down domain names and lock them again=
st transfer. The city of London police case is well known. There is also a =
Pharmacy industry group asserting the &#39;right&#39; to take down sites wi=
thout a court order or any form of due process.</div>
<div><br></div><div><a href=3D"http://www.techdirt.com/articles/20140110/12=
140025836/pharmacy-lobbyists-lie-to-registrars-if-we-complain-about-site-it=
-must-be-taken-down-no-questions-asked.shtml">http://www.techdirt.com/artic=
les/20140110/12140025836/pharmacy-lobbyists-lie-to-registrars-if-we-complai=
n-about-site-it-must-be-taken-down-no-questions-asked.shtml</a><br>
</div><div><br></div><div>What is worrying here is not just the lack of ove=
rsight in these particular cases. If these practices become a regular occur=
rence they are going to be interpreted as an attack and countermeasures wil=
l begin to emerge.</div>
<div><br></div><div>We have indeed already seen the emergence of one such c=
ountermeasure &#39;Namecoin&#39; which applies Bitcoin to &quot;replace&quo=
t; the DNS and according to some this also &quot;deprecates&quot; the WebPK=
I.</div>
<div><br></div><div>The main application for Namecoin appears to be the sam=
e as the main application for Bitcoin itself: Enabling the dotcom revolutio=
n to finally extend to the provision of recreational pharmaceuticals. But t=
he Namecoin technology if successful would also be used for much more inclu=
ding applications most of us support (dissident speech against authoritaria=
n regimes) and applications none of us support (child abuse, etc.).</div>
<div><br></div><div>At the moment use of Namecoin is restricted to a partic=
ular niche and is unlikely to gain widespread acceptance. It is also a tech=
nology designed by geeks for geeks in the finest tradition of calling anyon=
e who can&#39;t grock it a luser.</div>
<div><br></div><div>But if the principle of due process comes under further=
 attack, we are going to find ourselves in a different domain and the deman=
d for a naming infrastructure that is not exposed to the risk of arbitrary =
search and seizure will grow.</div>
<div><br></div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"=
http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--089e013d20346f5d2f04efc81407--

From randy@psg.com  Sun Jan 12 13:43:05 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54CB11A1DFA for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 13:43:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.539
X-Spam-Level: 
X-Spam-Status: No, score=-0.539 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KjEXba1F_Pvd for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 13:43:03 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id BB63D1A1521 for <ietf@ietf.org>; Sun, 12 Jan 2014 13:43:03 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W2Snz-0004nd-3U; Sun, 12 Jan 2014 21:42:51 +0000
Date: Mon, 13 Jan 2014 06:42:49 +0900
Message-ID: <m261povpuu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: A DNS security issue that might actually have impact eventually
In-Reply-To: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
References: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Mon_Jan_13_06:42:45_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 21:43:05 -0000

--pgp-sign-Multipart_Mon_Jan_13_06:42:45_2014-1
Content-Type: text/plain; charset=US-ASCII

the internet was a disruptive technology, and has been used for good,
bad, and indifferent.  thanks to societal forces, ongoing development of
disrupptive tools is at the edge, not the core.  bitcoin, namecoin, ...
are new disruptive technologies routing around the ossification,
cooption, and greed of the internet by LEO, NSA, ICANN, MPAA, ....
these new tools will be used for good, bad, and indifferent.

the tools which worry me are the ones where the use is only bad, e.g.
the spymall catalog.

> But if the principle of due process comes under further attack, we are
> going to find ourselves in a different domain and the demand for a
> naming infrastructure that is not exposed to the risk of arbitrary
> search and seizure will grow.

yup.  i think of it as the internet body's white blood cells trying to
heal us from disease.

randy
--pgp-sign-Multipart_Mon_Jan_13_06:42:45_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJS0wxYAAoJEMzMBey4OgLtgC4H/RR6pDBkbBSS6PZZoIcTnYNJ
oOe8hDSU5UlxJBLEOgEhvQ6giVX3C+7X+ZM8L7ku4k84nLykDwgZGkJp2G5QSv2u
cNw7E9J1Dds3bcNLmG6lEV+uT/ts25T9rwOP8Lqf2RagfNP2gSRLj6dxSoVk0Fk2
Iwa0ghbqPaf9lefOT36ScwdmYvWkqUhqStdyU+xO1hS/tjw+gwObYLlUOkL/jT90
21nkox/0UoelSjQAki0xYvcx1i8/ISVc0nIDqAKmRetbvWFztegykksBqYpq7jWd
18C9JNvmB2L2gWaT62pntuygNDqIICW29/y4jdEpmDGfqspeoKlHQPKBaKuhD0I=
=KDHs
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Mon_Jan_13_06:42:45_2014-1--

From jari.arkko@piuha.net  Sun Jan 12 14:43:49 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6486D1A1F74 for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 14:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I6kxdygwfx6r for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 14:43:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 66CE41A1F61 for <ietf@ietf.org>; Sun, 12 Jan 2014 14:43:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 303ED2CEB6; Mon, 13 Jan 2014 00:43:35 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YDBepM5akxn; Mon, 13 Jan 2014 00:43:34 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0D3D72CC48; Mon, 13 Jan 2014 00:43:33 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-moonesamy-ietf-conduct-3184bis-03.txt> (IETF Guidelines for Conduct) to Best Current Practice
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20140110071957.0a8de258@elandnews.com>
Date: Sun, 12 Jan 2014 23:43:35 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <9097FD6D-CB4F-4EB6-B1C7-422B69A40E6D@piuha.net>
References: <CAP+sJUfS=fAOS2E2nYE_d0MiytcnYz4zA3eKOZ4n+E8=c2y7hw@mail.gmail.com> <52CFC58C.3020000@cisco.com> <6.2.5.6.2.20140110071957.0a8de258@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1510)
Cc: Ines Robles <mariainesrobles@googlemail.com>, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 22:43:49 -0000

> I'll replace the last sentence in Section 3 with:
> 
>   However it is to be noted that there is an expectation that no one
>   shall ever knowingly contribute advice or text that may adversely
>   affect the security of the Internet without describing all known
>   or foreseen risks and threats to potential implementers and users
>   that they are aware of.

Works for me, at least.

Jari


From brian.e.carpenter@gmail.com  Sun Jan 12 19:32:53 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A5AE1ADBCC for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 19:32:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kY3kPySEovIX for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 19:32:51 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 6BE6E1AD8EB for <ietf@ietf.org>; Sun, 12 Jan 2014 19:32:51 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id fa1so153957pad.41 for <ietf@ietf.org>; Sun, 12 Jan 2014 19:32:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5alnky80L3Chr5b5/C6LWsYFQjj0D20JnxjHa9jEmqM=; b=h8F4eoEXohBtmI7Bct17B0T3M92kXZs6ssEMAD0CCKJ4eIYxuwxFPznvu4CHDho1Qf 1QErOr+kLuqw7tbGg3kMdIDRMhYRM68GxKCKB2n2hIg5F2JmRmTFhv0zdg/zfUNwWQrK EhK/7w7dic8cgNSSyGgk7JXhsXSWxNrAg4UHiMJJ3MSK3wA1IUOVreF9gx1nLIkDvx2P 4gzwUNkFQQ/Jta4kLjRe7akWbq4Du6Yy192rLBRkhni/S0h5gA2tDNCSlG4znKtbHNsQ oNw+y3QZNIi2QrWmGRi7sE3zlGunuuahZ2Vb7JHhNw884DeVHT3vjrbtYo/XzpWYvLRA aKRw==
X-Received: by 10.66.217.133 with SMTP id oy5mr27436829pac.46.1389583960725; Sun, 12 Jan 2014 19:32:40 -0800 (PST)
Received: from [192.168.178.23] (72.197.69.111.dynamic.snap.net.nz. [111.69.197.72]) by mx.google.com with ESMTPSA id jp3sm34098462pbc.36.2014.01.12.19.32.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 Jan 2014 19:32:39 -0800 (PST)
Message-ID: <52D35E54.8090204@gmail.com>
Date: Mon, 13 Jan 2014 16:32:36 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: draft-crocker-id-adoption@tools.ietf.org,  IETF discussion list <ietf@ietf.org>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
In-Reply-To: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 03:32:53 -0000

Hi,

I'm sorry to come late to this draft. It's very useful but
I have a few comments.

> Working groups use this mechanism
> for producing their official output, per Section 7.2 of [RFC2418] 

Perhaps this also needs to refer to Section 2.2 of [RFC2026] which
is the basic description of I-Ds.

>    draft-ietf-<wgname>-...

Maybe it's mentioned later, but I think a warning that this
convention is not always followed would be useful.
(If you doubt me, check draft-rosen-rph-reg-policy, a sipcore
draft that I recently reviewed for Gen-ART.)

> In formal terms, a working group raises and discusses each item of
> document content.  For difficult topics and/or difficult working
> group dynamics, this is the required mode.  It is laborious, but
> diligent, and it validates progress at each step along the way.

Excuse me if I describe this text as turgid; it's certainly hard to
read. Does it mean the following?

 In theory, a working group considers each item in a document and
 possibly modifies it before approval. For difficult topics, or for
 cases where the working group is contentious, there is no alternative
 to discussing each item. This is a laborious process requiring great
 diligence, and it validates progress at each step along the way.

> *  Can an Individual I-D be under the care of a WG?

How about adding

 *  Can a WG I-D become an Individual I-D?

>    When there is an existing document and the chairs want to propose
>    adopting it as a new working group document

There are two paths to this point:

1. The existing document was solicited by the WG, because it corresponds
to an item in the WG charter, and the normal expectation is that the
document will be adopted.

2. The existing document was unsolicited, and might even require a charter
update.

> Adoption, not approval:    The document is not required to already
> contain a complete and/or sufficient solution, although of
> course this can be helpful.

Also, adoption does not guarantee eventual publication as
an RFC; the WG could later abandon the document.

> 5.1. Individual I-Ds Under WG Care
...
> Typically such documents are handled according to normal, internal
> working group process management.  However matters of ownership,
> working group final approval, and the like are all subject to
> negotiation amongst the document authors, working group and area
> directors.

I am not so sure about that "typically". In fact I'm confused by
what you mean. If I write draft-carpenter-6man-foobar, and 6man
is interested in it, it will end up as draft-ietf-6man-foobar.
If 6man isn't interested in it, and I decide to pursue it, it's
possible I will submit it to an AD, with or without the 6man
chairs being helpful, or maybe I'll submit it to the Independent
Series Editor. But I don't know what you mean about such a draft
being handled *under its individual name* according to normal
working group process management, unless it's been adopted but
not renamed (like draft-rosen-rph-reg-policy).

Regards
   Brian Carpenter


From randy@psg.com  Sun Jan 12 22:35:09 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DB601AE049 for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 22:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qfYQJ7Fq0V56 for <ietf@ietfa.amsl.com>; Sun, 12 Jan 2014 22:35:07 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id C9E5B1AE048 for <ietf@ietf.org>; Sun, 12 Jan 2014 22:35:07 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W2b6u-0006ty-1q; Mon, 13 Jan 2014 06:34:56 +0000
Date: Mon, 13 Jan 2014 15:34:54 +0900
Message-ID: <m2iotos835.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
In-Reply-To: <52D35E54.8090204@gmail.com>
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com> <52D35E54.8090204@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: multipart/signed; boundary="pgp-sign-Multipart_Mon_Jan_13_15:34:51_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 06:35:09 -0000

--pgp-sign-Multipart_Mon_Jan_13_15:34:51_2014-1
Content-Type: text/plain; charset=US-ASCII

> In theory, a working group considers each item in a document and
> possibly modifies it before approval.

if you mean approval as in wglc, indeed.  if you mean approval as a wg
draft to be worked on by the wg, hell no.  the purpose of a wg adopting
a draft is specifically so it can go through it with a fine toothed
comb, get consensus, and get it in publishable shape.

randy
--pgp-sign-Multipart_Mon_Jan_13_15:34:51_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJS04kOAAoJEMzMBey4OgLtjz8H/A7nhWmG7hpfFF6K9s0GcVIA
4abYk9U4SIpQOIql/Pj319SYDxesifcbaeQFvMbkrfBVDfbCrMwTQPqVJqAuQOXU
sKRIUCoRjiWpKi82EXXa2DFziiiGZZm7OlBc0skhcG4YTqg8gaS76mrmq7gWa/IH
Alr8QX+PpuxKuGHedGYE4lbLoEGBodQFuZZ2p6uV7csoFRqtjpuEzawlqd36kr4O
HDEgJ/F9gMCPkv9pxgqt9VQ1DID87YYuPvvMyq70m515aniv/nzs0xm26PPjsQpF
Sou7Hj0YHlFZlcMFYXg9lYyCdICY42Mqm0zMHSsE50MD90IdIbDhbgCyShWFYFg=
=EzPq
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Mon_Jan_13_15:34:51_2014-1--

From lars@netapp.com  Mon Jan 13 00:50:20 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CF951ADF7A; Mon, 13 Jan 2014 00:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGMaXgZLYPmw; Mon, 13 Jan 2014 00:50:18 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id F35CE1AE070; Mon, 13 Jan 2014 00:50:17 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,651,1384329600";  d="asc'?scan'208";a="95683981"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 13 Jan 2014 00:50:07 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 00:50:07 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoA=
Date: Mon, 13 Jan 2014 08:50:06 +0000
Message-ID: <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 08:50:20 -0000

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

On 2014-1-13, at 4:40, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>> I don't think it's right to try to solve this in MPLS, because MPLS =
is not a
>> forwarding protocol - it's a connectivity protocol.

right, MPLS is the wrong place to address is. The UDP encaps/decaps =
function needs to have this functionality.

>> In any use of UDP, congestion
>> control is either left to something above UDP or ignored (left to =
queue
>> management).

There are several cases, see Section 3.1.3 of RFC5405. MPLS-over-UDP can =
fall into any of the three cases, depending on what traffic is inside =
the LSP being encapsulated.=20

You'll notice that RFC5405 for the first case - encapsulation of =
IP-based congestion controlled "normal" Internet traffic - even says =
that the tunnel SHOULD NOT employ any congestion control scheme of its =
own. Having layered control loops fighting is not productive.

The issue with MPLS-in-UDP (and GRE-in-UDP, and any other encaps scheme =
that can carry non-IP traffic) are with cases two and three. When the =
workload that is being encapsulated isn't known to be congestion =
controlled by its endpoints, it is the obligation of the tunnel to =
detect congestion and react to it by reducing the traffic volume. =
Because for the rest of the network, that tunnel is the UDP sender, and =
we have IETF consensus that we don't want UDP senders that don't react =
to congestion on the net. (That's one of the main reasons for the =
existence of the RMCAT WG - we don't want non-congestion-controlled RTP =
media traffic on the net.)

The key difference between putting MPLS e.g. into IP compared to putting =
it into UDP is that once it's in UDP, it can go pretty much anywhere on =
the net, because UDP traverses NATs and firewalls much more easily than =
IP traffic with a rare protocol number does.

>> Similarly, you want the client of MPLS to be responsible for
>> managing its traffic. MPLS gives you paths, it doesn't push packets =
over them.

Right. However, once you slap a UDP header on a packet during =
encapsulation, you now subjected yourself to the rules for Internet UDP =
senders. Those are documented in RFC5405, and require the tunnel to =
implement some sort of congestion detection and control. I'd personally =
consider a circuit breaker mechanism sufficient, like RTP and I think =
PWE are using.

> Fully agree. The congestion control should be performed either by the =
UDP tunnel itself or the client of MPLS. In the former case, it'd better =
to specify the practical congestion control mechanisms (if there were =
any) in a generic draft (e.g., RFC5405bis) and then any use of the UDP =
tunnel could refer to that generic draft with regard to congestion =
control.

The general concept of a circuit breaker is easy enough that it doesn't =
really need to be written down. And it wouldn't be possible to describe =
it in a generic fashion, because congestion detection is typically =
specific to the protocol being encapsulated (e.g., RTP uses RTCP =
feedback to derive loss information, etc.) And the reaction to =
congestion is also dependent on the protocol being encapsulated (does it =
support multiple rates or only on/off, what timescales are OK for =
reaction, etc.)

> In the latter case, if the client of MPLS is TCP-friendly, that is =
great. Otherwise (e.g., circuit emulation service), it shouldn't be =
deployed on the Internet at all, just as has been pointed out in =
RFC3985, therefore there is no need for any specific congestion control =
mechanism on the client.
>=20
>  "... In essence, this requirement states that it is
>   not acceptable to deploy an application (using PWE3 or any other
>   transport protocol) on the best-effort Internet, which consumes
>   bandwidth arbitrarily and does not compete fairly with TCP within an
>   order of magnitude." (quoted from Section 6.5 of RFC3985)
>=20
> The above choice seems no conflict with the following congestion =
control guidelines as quoted from Section 3.1.1 of RFC5405, as those =
non-TCP-friendly traffic would be transported over a provisioned path, =
rather than on the Internet.
>=20
>   "...Finally, some bulk transfer applications may choose not to =
implement
>   any congestion control mechanism and instead rely on transmitting
>   across reserved path capacity.  This might be an acceptable choice
>   for a subset of restricted networking environments, but is by no
>   means a safe practice for operation in the Internet."

How is that in conflict? Both quotes say that Internet traffic needs =
congestion control, which is a restatement of RFC2914.

Lars

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtOovdZcnpRveo1xAQICtAP+IEcc32eXYdPz7se0PX+ytfYOjHW1ExJt
bF/Wc+1umMc/GXbLL9tf8fKJdSpe/+ZUhuL6WpYG9BoptbI0uCsWCCH98/WP7BUI
Bzf3SgJE1Qxpv+HNXTtYV1OuKJuYxp4p6Lgujkz1aGtiT1VfpBjX7a5e2D290dCp
Kwtms72DUPw=
=PeLB
-----END PGP SIGNATURE-----

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D--

From lars@netapp.com  Mon Jan 13 01:37:33 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69ADC1AE055; Mon, 13 Jan 2014 01:37:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0L8_sTzC5O3s; Mon, 13 Jan 2014 01:37:32 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 62F831ADF91; Mon, 13 Jan 2014 01:37:32 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,651,1384329600";  d="asc'?scan'208";a="95688395"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 13 Jan 2014 01:37:21 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 01:37:21 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAAdiAIAABdIA
Date: Mon, 13 Jan 2014 09:37:20 +0000
Message-ID: <F9BB353A-2F3E-49CB-9D01-7DF6E4DBB9D1@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_D834C883-FFDC-432B-B9B4-215915D1A122"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 09:37:33 -0000

--Apple-Mail=_D834C883-FFDC-432B-B9B4-215915D1A122
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

On 2014-1-13, at 10:16, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> No conflict at all. What I meant is: for those clients of MPLS which =
are not TCP-friendly (case 2&3 as described in Section 3.1.3 of =
RFC5405), they should never be transported over the unprovisioned path =
(e.g., the Internet). Insteads, they should only be transported over a =
provisioned path in a restricted networking environment. As a result, =
there is no need for the congestion control mechanism for them.

ah, sorry! I misread "The above choice seems no conflict" in your =
sentence as "The above choice seems TO conflict". Oops.

Lars

--Apple-Mail=_D834C883-FFDC-432B-B9B4-215915D1A122
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtOz0NZcnpRveo1xAQLiZwQAlvXyzXRgiebzdR+moRumQVl30K/ldWsd
NPlF/NlG1KkrMM69dyAjfdGHEcQZ1uZcpYt6/YoCsUIDITBt5wtU+HORyGijGAj2
1AH9NT2GHUyZPLg5lcRM3oCJ0odc9LnKlItH32s5bpRVFDmVjeh6/ba/4r2th/He
cNDPjMtU9WE=
=Ba1T
-----END PGP SIGNATURE-----

--Apple-Mail=_D834C883-FFDC-432B-B9B4-215915D1A122--

From lars@netapp.com  Mon Jan 13 01:42:25 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA901ADF91; Mon, 13 Jan 2014 01:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISxiETNSJuqI; Mon, 13 Jan 2014 01:42:24 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 6F4961ADE71; Mon, 13 Jan 2014 01:42:24 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,651,1384329600";  d="asc'?scan'208";a="95688805"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 13 Jan 2014 01:42:13 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Mon, 13 Jan 2014 01:42:13 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAAdiAIAAByqA
Date: Mon, 13 Jan 2014 09:42:12 +0000
Message-ID: <B4EBCDAD-CD64-41F9-9D5B-D7FE903AC195@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com>
In-Reply-To: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_6A8AC501-152C-4A56-8A49-10A38055B6D9"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 09:42:25 -0000

--Apple-Mail=_6A8AC501-152C-4A56-8A49-10A38055B6D9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

On 2014-1-13, at 10:16, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> No conflict at all. What I meant is: for those clients of MPLS which =
are not TCP-friendly (case 2&3 as described in Section 3.1.3 of =
RFC5405), they should never be transported over the unprovisioned path =
(e.g., the Internet). Insteads, they should only be transported over a =
provisioned path in a restricted networking environment. As a result, =
there is no need for the congestion control mechanism for them.

I agree, but I think we need a safety mechanism when such traffic does =
end up on the general Internet (because operators may not read the RFC, =
or there may be configuration errors, etc.)

Even when running inside a provisioned domain, you probably want some =
sort of safety net, like a circuit breaker that detects if your tunnel =
is experiencing/causing severe congestion, and shut it down.

Lars

--Apple-Mail=_6A8AC501-152C-4A56-8A49-10A38055B6D9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtO08dZcnpRveo1xAQI95gQAgLVnN1A0dhbDOGTouXbI1mLZ7ybfAIZn
hnyIX57k2pEI3Bbz7NsNK8GDf5EX6RWKl7Y7yqHVrVTIzJ0H1uzguq83gYoOg30l
5JLcybhzrfbH5DxqkmAXtGTRsoqNtNCqVBDOk8lFHzBlrA9vFkZ2T+kUZwC8rvyJ
aHAw6LWx2qU=
=aTe9
-----END PGP SIGNATURE-----

--Apple-Mail=_6A8AC501-152C-4A56-8A49-10A38055B6D9--

From Alexander.Vainshtein@ecitele.com  Sun Jan 12 01:42:37 2014
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE0C1ADEB7; Sun, 12 Jan 2014 01:42:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LBD5QGBIMzi1; Sun, 12 Jan 2014 01:42:34 -0800 (PST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0081.outbound.protection.outlook.com [213.199.154.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3A54A1AD8ED; Sun, 12 Jan 2014 01:42:31 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB530.eurprd03.prod.outlook.com (10.242.109.154) with Microsoft SMTP Server (TLS) id 15.0.851.11; Sun, 12 Jan 2014 09:42:14 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Sun, 12 Jan 2014 09:42:14 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Eggert, Lars" <lars@netapp.com>, Scott Brim <scott.brim@gmail.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDi/Q1tWkYFyrTkep2zSq03bWq5p+JqQAgAA+GACAAAemgIAAAbCAgAAMWwCAAJRxAIABu3dQ
Date: Sun, 12 Jan 2014 09:42:13 +0000
Message-ID: <bd9e01b03ed34795afb2f3b679a18cc2@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com> <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com> <52D05C75.3050505@joelhalpern.com> <CAPv4CP_33OU-s+8xt9t5voAtiXMS3pw2+67w9=FxpS2cAOmDeg@mail.gmail.com> <AAA47C6B-C06B-4C95-9D7E-4A7BAA40E480@netapp.com>
In-Reply-To: <AAA47C6B-C06B-4C95-9D7E-4A7BAA40E480@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 008960E8EC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(24454002)(252514010)(377454003)(51704005)(13464003)(377424004)(189002)(199002)(46102001)(74366001)(85852003)(47446002)(80022001)(65816001)(53806001)(79102001)(66066001)(33646001)(85306002)(87936001)(2656002)(54316002)(49866001)(51856001)(76482001)(31966008)(76796001)(87266001)(56776001)(54356001)(74316001)(63696002)(74662001)(69226001)(81342001)(81686001)(47976001)(74502001)(19580395003)(83072002)(80976001)(83322001)(19580405001)(74706001)(74876001)(81816001)(59766001)(50986001)(4396001)(47736001)(76576001)(77982001)(81542001)(76786001)(56816005)(92566001)(90146001)(15975445006)(93136001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB530; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:147.234.56.21; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:07:32 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>, "Stewart Bryant \(stbryant@cisco.com\)" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 09:42:38 -0000

Lars, Scott and all,

First, a piece of history.

Congestion control considerations have been a major point of contention bet=
ween the (then) leadership of the Transport Area and the PWE3 WG (that has =
started in the Transport Area, then migrated to Internet Area and finally a=
rrived to the Routing Area).  A congestion control framework document is st=
ill listed as one of the goals of this WG even if the target date has passe=
d and the draft that was supposed to deal with the subject (https://datatra=
cker.ietf.org/doc/draft-ietf-pwe3-congestion-frmwk) has expired almost 4 ye=
ars ago.

TDM PWs which, for historical reasons, have always included encapsulations =
over UDP/IP, have been one of the focal points of this contention with DISC=
USS by one of the then Transport Area directors in the process of the IESG =
approval of the first of these documents. Eventually, this contention has b=
een resolved by adding a dedicated Congestion Control section to RFC 4553. =
This section introduced several guards against congestion being created by =
excessive deployment of TDM PWs and provided specific guidelines for  imple=
menting a congestion prevention mechanism (specific to TDM PWs).=20

Going back to the draft in question...

Encapsulating  MPLS in UDP looks to me like a far-going extension of runnin=
g TDM PWs over UDP/IP. The main differences, as I see them, are:

- General MPLS-in-UDP flows can be "BW-greedy" while TDM PWs are not
- Congestion detection for these flows by the encapsulation endpoints (pres=
umably called "applications using MPLS/UDP encapsulation" in the ) is much =
more problematic, nor is it clear to me, how backpressure  between these en=
dpoints can operate even if congestion were detected

The text I have found in the Congestion Considerations section of the draft=
 recognizes potential for congestion created by MPLS/UDP flows, and even ca=
lls for a mandatory additional congestion control mechanism. However, I cou=
ld not find any guidelines (or even hints) that would help an implementer t=
o create such a mechanism.  So I'd say that with regard to congestion contr=
ol this draft does not meet the standard that has been expected (years ago =
from now) from the TDM PW drafts.=20

My 2c,
       Sasha=20
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Eggert, Lars
> Sent: Saturday, January 11, 2014 8:23 AM
> To: Scott Brim
> Cc: mpls@ietf.org; IETF
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> Hi,
>=20
> On 2014-1-10, at 22:32, Scott Brim <scott.brim@gmail.com> wrote:
> > OK good point - so we invoke the end-to-end argument on MPLS's behalf.
>=20
> look at it the other way. From the viewpoint of the rest of the net, you =
are an
> application using UDP. Such applications need to follow a set of principl=
es we
> have IETF consensus on (RFC5405).
>=20
> By encapsulating MPLS in UDP, you are changing the game. That traffic can
> now appear on any Internet path, and not just inside provisioned networks=
.
> Because of that, you need a mechanism to detect if you are causing
> congestion, and a mechanism to react to it.
>=20
> And it *is* a requirement on the encapsulator, because from the perspecti=
ve
> of the rest of the net, that is the application that generates the UDP tr=
affic.
>=20
> Lars

From curtis@ipv6.occnc.com  Sun Jan 12 10:09:22 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 209DE1ADF7D; Sun, 12 Jan 2014 10:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmWCUiK9SE2P; Sun, 12 Jan 2014 10:09:19 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 183821ADF7C; Sun, 12 Jan 2014 10:09:18 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0CI91Y1053969; Sun, 12 Jan 2014 13:09:01 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401121809.s0CI91Y1053969@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
In-reply-to: Your message of "Sun, 12 Jan 2014 02:59:41 +0000." <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
Date: Sun, 12 Jan 2014 13:09:01 -0500
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:07:47 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, adrian@olddog.co.uk, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 12 Jan 2014 18:09:22 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> On nested checksums, the question is how they are nested; it's a matter
> of scope. With a bunch of checksums checking only a payload and any
> inner checksums like Russian Matryoshka dolls, the end-to-end argument
> tells us that for reliable receipt of the payload, only the innermost checksum
> matters.
>  
> But here, we are not solely checking the payload, but information on how to
> deliver and identify that payload - and while an outer Ethernet CRC is across
> the last link, the UDP checksum, though weak, provides a check on the IP
> addresses and UDP ports (via the  pseudoheader check) and MPLS stack
> from UDP/IP source to UDP/IP destination (and the payload, which is the bit
> everyone focuses on as the performance hit as redundant and a processing
> cost when the payload has its own check, and the bit that UDP-Lite can leave out).
>  
> Nothing else checks that scope. The scope is wider, and affects the network
> as a whole. Errors in these unchecked fields lead to misdirection and lead to
> misdelivery. Or pollution of other ports.
>  
> The MPLS assumption is that it's protected and checked by a strong link CRC like
> Ethernet, and checked/regenerated by stack processing between hops; here,
> in a path context, with zero UDP checksums MPLS has no checking at all.

That UDP would be running over IP over Ethernet or POS or GFP or ...

There is no layer-2 currently in use that does not have a robust FCS,
generally a 32 FCS and therefore the MPLS assumption of checking at a
lower layer is still valid.

Curtis


> "consequences for cheap hardware and for software implementations"
>  
> I'm sorry, when was MPLS cheap?
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Adrian Farrel [adrian@olddog.co.uk]
> Sent: 09 January 2014 10:21
> To: Wood L  Dr (Electronic Eng); randy@psg.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>  
> Lloyd and Randy,
>  
> With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls, so
> thanks for the comments.
>  
> We did take the precaution of sending this I-D for an early TSV Directorate
> review because of the concern about a number of factors and the overlap with
> tsvwg work, but the review came back "clean". Of course, such a review is just
> one person, so this conversation is good.
>  
> Wrt zero checksum, where do you stand on nested checksums? There is some claim
> that they represent a waste of processing. I am not convinced by that when each
> layer is using dedicated hardware (that can presumably process checksums at line
> speed), but I am interested in the consequences for cheap hardware and for
> software implementations (as have been claimed to be some of the motivations for
> this work).
>  
> Other TSV-related issues that surely pop up are:
> - allocation of ports for foo-in-UDP
> - congestion control
>  
> Please note that there are a number of I-Ds that you missed in your broad sweep
> of "I am opposed". You should probably look at the NVGRE and VXLAN work (which I
> think is lurking around the NVO3 working group) because that is also looking at
> UDP encaps of a tunnelling protocol.
>  
> Thanks,
> Adrian
>  
> Health warnings:
> I am responsible AD for draft-ietf-mpls-in-udp
> I am a co-author of the gre-in-udp draft.
>  
> > -----Original Message-----
> > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
> > Sent: 09 January 2014 08:07
> > To: randy@psg.com
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com;
> > tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> > Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:
> > [tsvwg] Milestones changed for tsvwg WG)
> >
> > Randy,
> >
> > okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
> > consensus on  it. And then the authors can adopt that consensus for
> mpls-in-udp,
> > which overlaps in authorship...
> >
> > thanks,
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: Randy Bush [randy@psg.com]
> > Sent: 09 January 2014 07:51
> > To: Wood L  Dr (Electronic Eng)
> > Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org;
> > jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
> > Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg]
> > Milestones changed for tsvwg WG)
> >
> > > Because they specify zero UDP checksums,
> > > I oppose publication of draft-ietf-mpls-in-udp in its current form
> > > I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current
> > form.
> > > I oppose the IETF lisp documents.
> >
> > lloyd,
> >
> > i think i understand your position.  but i disagree with preventing wg
> > adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
> > see wg adoption as how we get to discuss and work on a document, not as
> > approval of the document.  as david said, i think we need to discuss it
> > so we can decide if it should be fixed.  to do so, we have to adopt it.
> >
> > randy

From curtis@ipv6.occnc.com  Sun Jan 12 10:37:37 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DBCD1AE00C; Sun, 12 Jan 2014 10:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_82=0.6, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJnoHHCrCFIc; Sun, 12 Jan 2014 10:37:36 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id BB9AB1ADFE6; Sun, 12 Jan 2014 10:37:35 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0CIbGKE054334; Sun, 12 Jan 2014 13:37:16 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401121837.s0CIbGKE054334@maildrop2.v6ds.occnc.com>
To: mark.tinka@seacom.mu
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: OT was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
In-reply-to: Your message of "Sun, 12 Jan 2014 14:26:23 +0200." <201401121426.23719.mark.tinka@seacom.mu>
Date: Sun, 12 Jan 2014 13:37:16 -0500
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:08:17 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 12 Jan 2014 18:37:37 -0000

In message <201401121426.23719.mark.tinka@seacom.mu>
Mark Tinka writes:
 
> On Sunday, January 12, 2014 04:59:41 AM l.wood@surrey.ac.uk
> wrote:
>  
> > The MPLS assumption is that it's protected and checked by
> > a strong link CRC like Ethernet, and checked/regenerated
> > by stack processing between hops; here, in a path
> > context, with zero UDP checksums MPLS has no checking at
> > all.
>  
> Right, which is probably why routers today can count badly
> checksum'ed Ethernet frames, but don't have the equivalent
> for MPLS.
>  
> > I'm sorry, when was MPLS cheap?
>  
> Current-generation ASIC's have no problem forwarding MPLS
> frames at wire rate. One could go so far as to say that MPLS
> has allowed vendors to make cheaper line cards also because
> IP FIB's and traffic queues can be scaled down dramatically
> (not that I'd every buy such line cards, but...).
>  
> Mark.


Perhaps if you actully worked for a company that made line cards you
would not make the above statement.

Many of the big router vendors use the same TCAM hardware for MPLS
lookups as they do for IP lookups.  Doing the lookup is not the rate
limiting factor even in hardware that has an ILM SRAM table and some
form of radix based lookup.  All of the hardwre I've seen in the last
15 years or so forwards MPLS and IP at the same rate.  ... Except IPv6
before they decided to waste the lower half of the address space with
40 quintilion host in a bridged subnet and you really did have to look
at the whole 128 bits.  Back when forwarding was done in software
(circa 1995) your statement would have been true if MPLS preceeded
forwarding ASICs which it did not.

Also the statement "Current-generation ASIC's have no problem
forwarding MPLS frames at wire rate" is not true for most (or all)
hardware with 40 byte payloads (even with plus 4 with TCP SACK plus 4
if MPLS) and 100 Gb/s interfaces.  It is true for "average packet
size" traffic and on most hardware only true if bursts of 40 byte
packets are very limited in duration.

Curtis

From edc@google.com  Fri Jan 10 12:15:17 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3DE11AE1FA for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 12:15:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D1J9tn5POHQL for <ietf@ietfa.amsl.com>; Fri, 10 Jan 2014 12:15:15 -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 82EFA1AE1E8 for <ietf@ietf.org>; Fri, 10 Jan 2014 12:15:15 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id w62so4523929wes.20 for <ietf@ietf.org>; Fri, 10 Jan 2014 12:15:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Hf5/fpB19PPfk+FSGxeMnrQwJZrRFwb9PX8n8bCKxuo=; b=Jfo7uOeRco3InsSCqLhr4qvvgFWpul4/tsxwodTvfR5kbP4Ml8u/1BBnY3TvyDjs/2 coSCoRBk+Uwib2OayM+DhQ1c/RElJPy9WrFTpvAdbcyKjVQD20EB3zRoyzRDVrD1hQsD WcKQKc2hm3ZgQRSYO/G/tXbJHhAwaQks873bHoUjODPN/Nn/CO59nbkvgFB/3s4k7gN8 txCiehehYFKQZG4RN5YsXEsm40crTGplRj7ZOVUA6/sOi30xy/eMtC6nKk6CiCNjIELh wHsZgfAGxkYwtbUEzq/Z6j8XY2wqV1kgH0YEvB06JFPMPElur6mc8kYGoRYbKeDWvEnE da7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Hf5/fpB19PPfk+FSGxeMnrQwJZrRFwb9PX8n8bCKxuo=; b=lIyvnqLTuFUpFJyOLGZQ6CyE6QVUHl7efRAEwgwRFxC/Gbx8NY7nNqSSeN3QwrzBc+ LbcKOGt5bP46/cw65mYcyqOJGXkMd0Y6HhFYwzbVWJzfg2mkGXWECAJTCDqNuM07twvS 4AMBaZS6wE9kZcqQibM3vPvks5iBoTBocmAi/97JuVn6dT+dGwRDKgd3/YlcsHxvPyfs xl+9w6YEYRYfdvdUGcuOKe0Ph1r9YGnrlcsFY2P/nGpk9vFCC9MXEQGtXlasNNB8iO5q qYLhM2uR++8pVcMT1qBHBDiE7BDP8hFiTLKdBzBo53CkBCbArEjirqBtd03yIFSIoks1 AH5g==
X-Gm-Message-State: ALoCoQkH+YTgBW/4HxpKrkI33a8mAlpR49ITrWpHDallfN8zTQ0r1JkL8WmANNDta6vWd7rz8jQReLJAYVW/c5E9YA9hbZsk1CLm2Ewd5vHEdSmAYPYK4oYDiu2D5rHwk0dvbtF+BSX8/yVPdi/pDGHftb7oqRA+LgHd0gEH5VLpQ/FfhdFvcDoCPrqnH0mj72Pzdxj9IRWA
X-Received: by 10.180.93.169 with SMTP id cv9mr4447242wib.3.1389384905056; Fri, 10 Jan 2014 12:15:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Fri, 10 Jan 2014 12:14:24 -0800 (PST)
In-Reply-To: <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com>
From: Edward Crabbe <edc@google.com>
Date: Fri, 10 Jan 2014 12:14:24 -0800
Message-ID: <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c7fc0b917d704efa361e2
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:09:49 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jan 2014 20:15:18 -0000

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

+1

Let the encapsulated transport protocols take care of the congestion
end-to-end.


On Fri, Jan 10, 2014 at 8:32 AM, Scott Brim <scott.brim@gmail.com> wrote:

> I don't think it's right to try to solve this in MPLS, because MPLS is
> not a forwarding protocol - it's a connectivity protocol. In any use
> of UDP, congestion control is either left to something above UDP or
> ignored (left to queue management). Similarly, you want the client of
> MPLS to be responsible for managing its traffic. MPLS gives you paths,
> it doesn't push packets over them.
>
> Scott
>
>
> On Fri, Jan 10, 2014 at 11:09 AM, Eggert, Lars <lars@netapp.com> wrote:
> > Hi,
> >
> > On 2014-1-10, at 16:36, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> >> Maybe I am completely missing things, but this looks wrong.
> >> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> >> control will make it more likely that the service won't work.  Is that
> >> really the goal?
> >>
> >> We do not perform congestion control on MPLS LSPs.
> >> Assuming that a UDP tunnel is carrying just MPLS and was established
> >> just for MPLS, why would we expect it to behave differently than an MPLS
> >> LSP running over the exact same path, carrying the exact same traffic?
> >
> > we've been rehashing this discussion several times over the years, e.g.,
> for PWE, AMT, etc. In order to carry fixed-rate or otherwise
> non-congestion-controlled traffic over unprovisioned general Internet
> paths, there needs to be some sort of basic congestion control mechanism,
> like a circuit breaker.
> >
> > The whole point of running MPLS is to create networks in which paths are
> provisionable, so this is usually not an issue. But if you start sticking
> MPLS inside of UDP, those packets can go anywhere on the net, so you need
> mechanisms to control the rate of that traffic if it causes congestion, or
> at the very least you need to be able to stop the traffic if it creates
> severe congestion.
> >
> > Lars
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

<div dir=3D"ltr">+1=A0<div><br></div><div>Let the encapsulated transport pr=
otocols take care of the congestion end-to-end. =A0</div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Jan 10, 2014 at=
 8:32 AM, Scott Brim <span dir=3D"ltr">&lt;<a href=3D"mailto:scott.brim@gma=
il.com" target=3D"_blank">scott.brim@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">I don&#39;t think it&#39;s right to try to s=
olve this in MPLS, because MPLS is<br>
not a forwarding protocol - it&#39;s a connectivity protocol. In any use<br=
>
of UDP, congestion control is either left to something above UDP or<br>
ignored (left to queue management). Similarly, you want the client of<br>
MPLS to be responsible for managing its traffic. MPLS gives you paths,<br>
it doesn&#39;t push packets over them.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Scott<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Fri, Jan 10, 2014 at 11:09 AM, Eggert, Lars &lt;<a href=3D"mailto:lars@n=
etapp.com">lars@netapp.com</a>&gt; wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; On 2014-1-10, at 16:36, Joel M. Halpern &lt;<a href=3D"mailto:jmh@joel=
halpern.com">jmh@joelhalpern.com</a>&gt; wrote:<br>
&gt;&gt; Maybe I am completely missing things, but this looks wrong.<br>
&gt;&gt; If the MPLS LSP is carrying fixed rate pseudo-wires, adding conges=
tion<br>
&gt;&gt; control will make it more likely that the service won&#39;t work. =
=A0Is that<br>
&gt;&gt; really the goal?<br>
&gt;&gt;<br>
&gt;&gt; We do not perform congestion control on MPLS LSPs.<br>
&gt;&gt; Assuming that a UDP tunnel is carrying just MPLS and was establish=
ed<br>
&gt;&gt; just for MPLS, why would we expect it to behave differently than a=
n MPLS<br>
&gt;&gt; LSP running over the exact same path, carrying the exact same traf=
fic?<br>
&gt;<br>
&gt; we&#39;ve been rehashing this discussion several times over the years,=
 e.g., for PWE, AMT, etc. In order to carry fixed-rate or otherwise non-con=
gestion-controlled traffic over unprovisioned general Internet paths, there=
 needs to be some sort of basic congestion control mechanism, like a circui=
t breaker.<br>


&gt;<br>
&gt; The whole point of running MPLS is to create networks in which paths a=
re provisionable, so this is usually not an issue. But if you start stickin=
g MPLS inside of UDP, those packets can go anywhere on the net, so you need=
 mechanisms to control the rate of that traffic if it causes congestion, or=
 at the very least you need to be able to stop the traffic if it creates se=
vere congestion.<br>


&gt;<br>
&gt; Lars<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">_______________________=
________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><br>
</div></div></blockquote></div><br></div>

--f46d043c7fc0b917d704efa361e2--

From farinacci@gmail.com  Sun Jan 12 13:37:16 2014
Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F6C11AE013; Sun, 12 Jan 2014 13:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNZFc2qXT733; Sun, 12 Jan 2014 13:37:15 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 1F34B1ADFF3; Sun, 12 Jan 2014 13:37:15 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id fb1so303109pad.38 for <multiple recipients>; Sun, 12 Jan 2014 13:37:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Hy0NAgTRz5/l6EPUl9CUfcPwWnRgwo5S+Vd1yW7irlc=; b=c8QwbDetVyvewmjJIiDiUYhvNHCiLfTxZB7CtqMNvpxZxqmYZkYKl84QQFvqtEEe0t 7dzxqYXB/uW/eFmIioRTk426DyS+ueO/YgRHQVZFXXsGW/gTaTvfe6TglpQiHi3kLTHE 3NFrhiSIxOvk8jbcZRl81d3/QSmmnOfRjbMPBPmI8wsT+T/hkEKJfxHFsh25wap674HF iuM+H4Hixw9gpGMLwVrHz3KpTGiz+CmSnx4ET7cYaFcDyaScl/TrwoKQyJWEi1i6bdWN xYOoUieMBixPWhu+Aoe1JuneE/h4qmMMrjm5j4J1GvsUzklLeBIN3n6XEaNT30Yu+9s7 6O1w==
X-Received: by 10.66.136.107 with SMTP id pz11mr26215058pab.118.1389562624528;  Sun, 12 Jan 2014 13:37:04 -0800 (PST)
Received: from [192.168.1.15] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPSA id sy10sm42330439pac.15.2014.01.12.13.37.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 12 Jan 2014 13:37:03 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
From: Dino Farinacci <farinacci@gmail.com>
X-Mailer: iPhone Mail (11B554a)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346BE@EXMB01CMS.surrey.ac.uk>
Date: Sun, 12 Jan 2014 13:37:04 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C03C9145-2F11-47F4-80DC-A387E4987DDD@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <012801cf0d24$9b80b180$d2821480$@olddog.co.uk> <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk> <201401121426.23719.mark.tinka@seacom.mu> <290E20B455C66743BE178C5C84F1240847E63346BE@EXMB01CMS.surrey.ac.uk>
To: "<l.wood@surrey.ac.uk>" <l.wood@surrey.ac.uk>
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:11:11 -0800
Cc: "<mark.tinka@seacom.mu>" <mark.tinka@seacom.mu>, "<mpls@ietf.org>" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "david.black@emc.com" <david.black@emc.com>, "jnc@mit.edu" <jnc@mit.edu>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 21:37:16 -0000

> Do any routers count TCP/UDP checksum failures, much less
> expose the count via SNMP?

Typically they do but only for packets destined to them. Much like hosts wou=
ld check the header checksum.=20

Dino=

From l.wood@surrey.ac.uk  Sun Jan 12 13:27:07 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 242AF1ACC85; Sun, 12 Jan 2014 13:27:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ytbGuU5rCF86; Sun, 12 Jan 2014 13:27:04 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id 3DDA91A1DFA; Sun, 12 Jan 2014 13:27:03 -0800 (PST)
Received: from [195.245.231.67:56026] by server-11.bemta-5.messagelabs.com id 75/AE-23268-B9803D25; Sun, 12 Jan 2014 21:26:51 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-82.messagelabs.com!1389562011!29053243!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6226 invoked from network); 12 Jan 2014 21:26:51 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jan 2014 21:26:51 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Sun, 12 Jan 2014 21:26:50 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Sun, 12 Jan 2014 21:22:58 +0000
Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8PwWaHPFhUsU0dTLGXrrfKJuvBpAAGxCQx
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
References: Your message of "Sun, 12 Jan 2014 02:59:41 +0000." <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>, <201401121809.s0CI91Y1053969@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401121809.s0CI91Y1053969@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:11:40 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, adrian@olddog.co.uk, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 21:27:07 -0000

Curtis

I suggest reading Stone's work, particularly
''When The CRC and TCP Checksum Disagree'
for discussion of corruption.

Particularly its conclusions: 'In the internet, that means
we are sending large volumes of incorrect data without
anyone noticing'.

The Layer-2 check is per link, not end-to-end. That matters.

The MPLS assumption is that it crosses a link with a frame
checksum. Putting MPLS over UDP breaks that assumption.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 12 January 2014 18:09
To: Wood L  Dr (Electronic Eng)
Cc: adrian@olddog.co.uk; randy@psg.com; gorry@erg.abdn.ac.uk; mpls@ietf.org=
; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@iet=
f.org
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: R=
E: [tsvwg] Milestones changed for tsvwg WG)

In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:

> On nested checksums, the question is how they are nested; it's a matter
> of scope. With a bunch of checksums checking only a payload and any
> inner checksums like Russian Matryoshka dolls, the end-to-end argument
> tells us that for reliable receipt of the payload, only the innermost che=
cksum
> matters.
>
> But here, we are not solely checking the payload, but information on how =
to
> deliver and identify that payload - and while an outer Ethernet CRC is ac=
ross
> the last link, the UDP checksum, though weak, provides a check on the IP
> addresses and UDP ports (via the  pseudoheader check) and MPLS stack
> from UDP/IP source to UDP/IP destination (and the payload, which is the b=
it
> everyone focuses on as the performance hit as redundant and a processing
> cost when the payload has its own check, and the bit that UDP-Lite can le=
ave out).
>
> Nothing else checks that scope. The scope is wider, and affects the netwo=
rk
> as a whole. Errors in these unchecked fields lead to misdirection and lea=
d to
> misdelivery. Or pollution of other ports.
>
> The MPLS assumption is that it's protected and checked by a strong link C=
RC like
> Ethernet, and checked/regenerated by stack processing between hops; here,
> in a path context, with zero UDP checksums MPLS has no checking at all.

That UDP would be running over IP over Ethernet or POS or GFP or ...

There is no layer-2 currently in use that does not have a robust FCS,
generally a 32 FCS and therefore the MPLS assumption of checking at a
lower layer is still valid.

Curtis


> "consequences for cheap hardware and for software implementations"
>
> I'm sorry, when was MPLS cheap?
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Adrian Farrel [adrian@olddog.co.uk]
> Sent: 09 January 2014 10:21
> To: Wood L  Dr (Electronic Eng); randy@psg.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.c=
om; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was:=
 RE: [tsvwg] Milestones changed for tsvwg WG)
>
> Lloyd and Randy,
>
> With respect to draft-ietf-mpls-in-udp, this is why we have IETF last cal=
ls, so
> thanks for the comments.
>
> We did take the precaution of sending this I-D for an early TSV Directora=
te
> review because of the concern about a number of factors and the overlap w=
ith
> tsvwg work, but the review came back "clean". Of course, such a review is=
 just
> one person, so this conversation is good.
>
> Wrt zero checksum, where do you stand on nested checksums? There is some =
claim
> that they represent a waste of processing. I am not convinced by that whe=
n each
> layer is using dedicated hardware (that can presumably process checksums =
at line
> speed), but I am interested in the consequences for cheap hardware and fo=
r
> software implementations (as have been claimed to be some of the motivati=
ons for
> this work).
>
> Other TSV-related issues that surely pop up are:
> - allocation of ports for foo-in-UDP
> - congestion control
>
> Please note that there are a number of I-Ds that you missed in your broad=
 sweep
> of "I am opposed". You should probably look at the NVGRE and VXLAN work (=
which I
> think is lurking around the NVO3 working group) because that is also look=
ing at
> UDP encaps of a tunnelling protocol.
>
> Thanks,
> Adrian
>
> Health warnings:
> I am responsible AD for draft-ietf-mpls-in-udp
> I am a co-author of the gre-in-udp draft.
>
> > -----Original Message-----
> > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac=
.uk
> > Sent: 09 January 2014 08:07
> > To: randy@psg.com
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc=
.com;
> > tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> > Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (wa=
s: RE:
> > [tsvwg] Milestones changed for tsvwg WG)
> >
> > Randy,
> >
> > okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
> > consensus on  it. And then the authors can adopt that consensus for
> mpls-in-udp,
> > which overlaps in authorship...
> >
> > thanks,
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: Randy Bush [randy@psg.com]
> > Sent: 09 January 2014 07:51
> > To: Wood L  Dr (Electronic Eng)
> > Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf=
.org;
> > jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
> > Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: =
[tsvwg]
> > Milestones changed for tsvwg WG)
> >
> > > Because they specify zero UDP checksums,
> > > I oppose publication of draft-ietf-mpls-in-udp in its current form
> > > I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its c=
urrent
> > form.
> > > I oppose the IETF lisp documents.
> >
> > lloyd,
> >
> > i think i understand your position.  but i disagree with preventing wg
> > adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongl=
y
> > see wg adoption as how we get to discuss and work on a document, not as
> > approval of the document.  as david said, i think we need to discuss it
> > so we can decide if it should be fixed.  to do so, we have to adopt it.
> >
> > randy

From l.wood@surrey.ac.uk  Sun Jan 12 13:34:38 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5221ACC85; Sun, 12 Jan 2014 13:34:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_82=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVmWS-M1eOCv; Sun, 12 Jan 2014 13:34:37 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.176]) by ietfa.amsl.com (Postfix) with ESMTP id 122891A1DFA; Sun, 12 Jan 2014 13:34:35 -0800 (PST)
Received: from [85.158.137.99:24782] by server-16.bemta-3.messagelabs.com id DD/1B-26128-F5A03D25; Sun, 12 Jan 2014 21:34:23 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-217.messagelabs.com!1389562463!21261411!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1644 invoked from network); 12 Jan 2014 21:34:23 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-10.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 12 Jan 2014 21:34:23 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 12 Jan 2014 21:34:23 +0000
From: <l.wood@surrey.ac.uk>
To: <mark.tinka@seacom.mu>, <mpls@ietf.org>
Date: Sun, 12 Jan 2014 21:32:28 +0000
Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8PkY4DGIVCbttAQXqJ2uFOHpC4TAATD1BS
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346BE@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <012801cf0d24$9b80b180$d2821480$@olddog.co.uk> <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>, <201401121426.23719.mark.tinka@seacom.mu>
In-Reply-To: <201401121426.23719.mark.tinka@seacom.mu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:11:55 -0800
Cc: gorry@erg.abdn.ac.uk, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, adrian@olddog.co.uk, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 21:34:38 -0000

> Right, which is probably why routers today can count badly
> checksum'ed Ethernet frames, but don't have the equivalent
> for MPLS.

If Ethernet frames keep failing the check, you know you
have a local problem that needs fixing. That's why it's
instrumented.

Do any routers count TCP/UDP checksum failures, much less
expose the count via SNMP?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Mark Tinka [mark.tinka@seacom.mu]
Sent: 12 January 2014 12:26
To: mpls@ietf.org
Cc: Wood L  Dr (Electronic Eng); adrian@olddog.co.uk; randy@psg.com; gorry@=
erg.abdn.ac.uk; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.=
edu; tsvwg@ietf.org
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: R=
E: [tsvwg] Milestones changed for tsvwg WG)

On Sunday, January 12, 2014 04:59:41 AM l.wood@surrey.ac.uk
wrote:

> The MPLS assumption is that it's protected and checked by
> a strong link CRC like Ethernet, and checked/regenerated
> by stack processing between hops; here, in a path
> context, with zero UDP checksums MPLS has no checking at
> all.

Right, which is probably why routers today can count badly
checksum'ed Ethernet frames, but don't have the equivalent
for MPLS.

> I'm sorry, when was MPLS cheap?

Current-generation ASIC's have no problem forwarding MPLS
frames at wire rate. One could go so far as to say that MPLS
has allowed vendors to make cheaper line cards also because
IP FIB's and traffic queues can be scaled down dramatically
(not that I'd every buy such line cards, but...).

Mark.

From l.wood@surrey.ac.uk  Sun Jan 12 16:48:05 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18EEE1ACCD9; Sun, 12 Jan 2014 16:48: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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zu0P8HFOgrYa; Sun, 12 Jan 2014 16:48:02 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id D3F281ACC91; Sun, 12 Jan 2014 16:48:01 -0800 (PST)
Received: from [195.245.231.67:64589] by server-17.bemta-5.messagelabs.com id 32/F2-19152-6B733D25; Mon, 13 Jan 2014 00:47:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-82.messagelabs.com!1389574069!29061545!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27567 invoked from network); 13 Jan 2014 00:47:49 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 13 Jan 2014 00:47:49 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 13 Jan 2014 00:47:48 +0000
From: <l.wood@surrey.ac.uk>
To: <farinacci@gmail.com>
Date: Mon, 13 Jan 2014 00:45:52 +0000
Subject: RE: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Topic: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Thread-Index: Ac8P3nEsYE8Z6DG8TdaYBKdC9S/GqwAGl7Nt
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk>
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <012801cf0d24$9b80b180$d2821480$@olddog.co.uk> <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk> <201401121426.23719.mark.tinka@seacom.mu> <290E20B455C66743BE178C5C84F1240847E63346BE@EXMB01CMS.surrey.ac.uk>, <C03C9145-2F11-47F4-80DC-A387E4987DDD@gmail.com>
In-Reply-To: <C03C9145-2F11-47F4-80DC-A387E4987DDD@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:12:20 -0800
Cc: mark.tinka@seacom.mu, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, gorry@erg.abdn.ac.uk, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 00:48:05 -0000

Really, you'd want to expose the pseudoheader check at endhosts; a well-ins=
trumented Linux box could tell you a lot
about checksum failures.

But in this case, a router would be decapping UDP/MPLS tunnels as an endpoi=
nt, so could report on checksum failures -
if the checksum wasn't zero.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Dino Farinacci [farinacci@gmail.com]
Sent: 12 January 2014 21:37
To: Wood L  Dr (Electronic Eng)
Cc: <mark.tinka@seacom.mu>; <mpls@ietf.org>; gorry@erg.abdn.ac.uk; lisp@iet=
f.org; david.black@emc.com; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; iet=
f@ietf.org
Subject: Re: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft =
(was: RE: [tsvwg] Milestones changed for tsvwg WG)

> Do any routers count TCP/UDP checksum failures, much less
> expose the count via SNMP?

Typically they do but only for packets destined to them. Much like hosts wo=
uld check the header checksum.

Dino

From mark.tinka@seacom.mu  Sun Jan 12 04:18:37 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166281AE064; Sun, 12 Jan 2014 04:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VMdSo1dvBmMt; Sun, 12 Jan 2014 04:18:36 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id 689541AE063; Sun, 12 Jan 2014 04:18:35 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W2JzY-0007Lo-9i; Sun, 12 Jan 2014 14:18:12 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Date: Sun, 12 Jan 2014 14:18:11 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
In-Reply-To: <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1774670.NvQXsO8Ws6"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401121418.11663.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:12:35 -0800
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 12:18:37 -0000

--nextPart1774670.NvQXsO8Ws6
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Friday, January 10, 2014 06:09:45 PM Eggert, Lars wrote:

> The whole point of running MPLS is to create networks in
> which paths are provisionable, so this is usually not an
> issue. But if you start sticking MPLS inside of UDP,
> those packets can go anywhere on the net, so you need
> mechanisms to control the rate of that traffic if it
> causes congestion, or at the very least you need to be
> able to stop the traffic if it creates severe
> congestion.

What most networks do is just police/shape traffic at=20
whatever rate you can afford to pay for, as it enters/leaves=20
the provider's network.

As MPLS is in UDP, all the provider sees is IP, as they=20
should. I don't think there will be any "special treatment"=20
to UDP traffic carrying MPLS, vs. UDP traffic carrying other=20
payloads.

Mark.

--nextPart1774670.NvQXsO8Ws6
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS0ogDAAoJEGcZuYTeKm+GNwUQAKqmgi/s/GOux2SsrGgl8dtx
ByeO/hYWj/fdoEK/9df1sHScLJAKCuIRc4/fi5d3u55wCNsJz5MzRj1AFGi1R3qB
785Di7CpJp3bG07Dg8JsigD0zGuO/cNgHvxORzoxMmCWx4+pFwehnArVtK+PtF/T
6ltzFhadSABcWB1oTNcNjTD9/rNjJ1X0FJ9VLAyQ5Nox9GN531Nj5a4bpNVzh/NW
7g/XvQT507qft/JX5keNE/JGze860sqbD2fLo1p+OMiTkTBe6Ap9zsguGQ3bawD9
iICakUhtv22/oRC5HBGgPXYgvIkMZTFlzzhPTuu1By1KEguQWyHLwQMIIbo4/yKs
t5+K58FN+dWISc2mfjTy9m4q2xqGfeBI8sc4m+SaUqSnKYX4SvEdqaOwIi1o/7x5
I2IVQCnZ84lDFNTkvoPoWQzIPpBL9+XVX3dAnIxl4uEGSOvf1UHtkC19Q1vmAGA1
dzx16M7VIPkkisZMrPnGLkg8ocMq7kNESxTlicqxlRDBA/QCp3pagMrnelO3bfis
Uffvw+Al0gnmMarr7QeEvM2fFLbZ6jaQzM/6zTlAl3Q1LdUE/tp3L1sD+euME+Ue
AhRO0TQnp6tJCAhprogG5mQwCZccc8DecBFMb6a9RqvLCvCXmHNr2gp3+JBmg2sw
b3VNSBLcO00cC2as80jP
=H7Wl
-----END PGP SIGNATURE-----

--nextPart1774670.NvQXsO8Ws6--

From mark.tinka@seacom.mu  Sun Jan 12 04:26:51 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BAA1AE071; Sun, 12 Jan 2014 04:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level: 
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_82=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1oiHRm9zhHE; Sun, 12 Jan 2014 04:26:50 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id 0544D1AE06E; Sun, 12 Jan 2014 04:26:50 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W2K7U-0007Rm-A2; Sun, 12 Jan 2014 14:26:24 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Date: Sun, 12 Jan 2014 14:26:23 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <8D3D17ACE214DC429325B2B98F3AE712026EF305B4@MX15A.corp.emc.com> <012801cf0d24$9b80b180$d2821480$@olddog.co.uk> <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2145601.e0txlHMqRJ"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401121426.23719.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:14:30 -0800
Cc: gorry@erg.abdn.ac.uk, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, adrian@olddog.co.uk, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 12:26:51 -0000

--nextPart2145601.e0txlHMqRJ
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Sunday, January 12, 2014 04:59:41 AM l.wood@surrey.ac.uk=20
wrote:

> The MPLS assumption is that it's protected and checked by
> a strong link CRC like Ethernet, and checked/regenerated
> by stack processing between hops; here, in a path
> context, with zero UDP checksums MPLS has no checking at
> all.

Right, which is probably why routers today can count badly=20
checksum'ed Ethernet frames, but don't have the equivalent=20
for MPLS.

> I'm sorry, when was MPLS cheap?

Current-generation ASIC's have no problem forwarding MPLS=20
frames at wire rate. One could go so far as to say that MPLS=20
has allowed vendors to make cheaper line cards also because=20
IP FIB's and traffic queues can be scaled down dramatically=20
(not that I'd every buy such line cards, but...).

Mark.

--nextPart2145601.e0txlHMqRJ
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS0onvAAoJEGcZuYTeKm+GO5YQAKFRVfaAIFXCOBY/gYZEQwQ4
iqdsoVfKH8J2qPY4ESdk/Z5CCABTXCQDSFSUicGPXZirZX0kQNF6aIOEbBhob6D9
dV8Hmg9Wn20xRMhhseBU1MSWld1W+TV00fxFGfkUUm34FP+ijm/qbyMaJxnugYqz
QAtb7BDpI2PG3TiinXyWgmBrc3qKNEvSpkn/HIA9VWKlQmIoXEWXc+l6s9BzfC86
c2WrExvW2iEHfIwcJkcnX1hIQ9NVsVjzrj95XVYBb9oiyknhjrDGrsmBSyyvAgRB
6dTY/4o2hPK7gBr98srtaK+C35ak7aLvezj0PBfHbgQ2lF7Bk6fe3tN+ps4BKthg
zsAn4+6qR+XOdZhzXx2kyaZe/PfFdFU/kKqVAQejn7BG4/etiWFm1pGSqSoVDMtc
zqvN6tNyIYMNRSZGNZl6UZdX5ACG3Ta1T/WKTy/sO17SGES9gNxIZ8my7xH/FBeo
Abxq3RVs6eAzgV05pDX92LBNvD94PxVbmQmKvWOWNl6VZpjV5h+mO4mKGdeR+p7G
OVTQx1IR9zDYO5eJPz7v4n62P/BfIwzeVLlJBYFpmQNRvhtFLrn5R3u72WOahhZO
JPZPAHqkLcfB/ScR3ulmt7zzUUr9zYUXsAzsINaGPDOekoVllVt5eNKOjKNw3Z45
IJ2hUIVy2S2BkNc2rk6+
=A+bb
-----END PGP SIGNATURE-----

--nextPart2145601.e0txlHMqRJ--

From mark.tinka@seacom.mu  Sun Jan 12 04:44:50 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE571ADF64; Sun, 12 Jan 2014 04:44:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xiiZZcop7tVB; Sun, 12 Jan 2014 04:44:49 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id 4162D1AD738; Sun, 12 Jan 2014 04:44:48 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W2KP1-0007bN-Rc; Sun, 12 Jan 2014 14:44:31 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Date: Sun, 12 Jan 2014 14:44:30 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1658773.OO1ujn9OSz"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401121444.31194.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:14:56 -0800
Cc: Gregory Mirsky <gregory.mirsky@ericsson.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 12:44:50 -0000

--nextPart1658773.OO1ujn9OSz
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Friday, January 10, 2014 08:24:02 PM Gregory Mirsky=20
wrote:

> Hi Lars,
> I think that " The whole point of running MPLS is to
> create networks in which paths are provisionable, so
> this is usually not an issue." is only partially
> correct. LDP-based MPLS network is not provisionable and
> LSPs follow IP best route selection. Explicit signaling
> of LSP is achievable in (G)MPLS by using RSVP(-TE)
> signaling.

Greg, I think we can delineate provisioning from whether it=20
is dynamic or explicit.

MPLS LSP's are all pre-provisioned, because of the FEC's=20
created. Whether those FEC's are dynamically or explicitly=20
provisioned is a separate issue.

Mark.

--nextPart1658773.OO1ujn9OSz
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS0o4vAAoJEGcZuYTeKm+G4BIP/A3d2PbMI89e/C862l9Ivxbb
nAMEK5/Hgw5hJOwa1DmunQyYY4rqzujhp5B6vWBj8NWcUKPC4g8J2pEV9alrAv6o
w1VgNRUNlsZGdQUMX4BzT85qc12aZixMXyS/P1bxkygYBZDrqJa45NL248eYhk+B
oKR2nWBK63+ou7H0YPe+tvSbOuMrlI71/cV9t9CHkGDAbfmE0kFcx5o8Eqbinnu7
2bF/fIvplS49JlJBKl7jmMHcn6k+2CSBDGXWZCcR8IaSTQiC0zYMHeSHHUfZxDXl
i/5Y7/OqE6+B7CCTOgA7QHnW6/oDZosYoD42A6JKGUB3Unn+PHKGWFC6Da0Y4uMr
PA4Av67abQibhxmTVk9Cc8K5VUBWC7mh/0I/H19HJcKOv9+WCMuXarxMr1EjaUPn
45mVcVj6YNQYosxbjgCyzOElGoGjE/I1thQDnOOy732coQjwyp6PziE8sqwTdR7Y
5XExETCYHxXZ/ee8VkVkNHoGCW3fvd3Xx+VwfJoOIRse9QAtbnHx1S39xg1NLeg4
cRN0lBXth7sjUzlj+428IAgnPU3dkl0ewhj05IjMwJ2s+0Dijxyy3isPh4UsmxzJ
18oqt+Qn1aWGp0XhpYZNjJO9ZcjeQnSs1h5tWkWS/UVSsFX+2BxQLSX2LUpFTvyh
mA3BqKaZog9VXk+CYMBg
=VqrV
-----END PGP SIGNATURE-----

--nextPart1658773.OO1ujn9OSz--

From mark.tinka@seacom.mu  Sun Jan 12 11:05:13 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41C2B1AE013; Sun, 12 Jan 2014 11:05:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OQSton2cP-ZI; Sun, 12 Jan 2014 11:05:10 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id C693A1AE012; Sun, 12 Jan 2014 11:05:09 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W2QKz-0000ia-1E; Sun, 12 Jan 2014 21:04:45 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: curtis@ipv6.occnc.com
Subject: Re: OT was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Date: Sun, 12 Jan 2014 21:04:40 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <201401121837.s0CIbGKE054334@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401121837.s0CIbGKE054334@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1564113.ZqtHiklPLi"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401122104.44370.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:15:43 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jan 2014 19:05:13 -0000

--nextPart1564113.ZqtHiklPLi
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Sunday, January 12, 2014 08:37:16 PM Curtis Villamizar=20
wrote:

> Perhaps if you actully worked for a company that made
> line cards you would not make the above statement.

I work for an operator that pays real money to deploy and=20
use those line cards, and I make it my business to know what=20
I'm paying for.

> Many of the big router vendors use the same TCAM hardware
> for MPLS lookups as they do for IP lookups.  Doing the
> lookup is not the rate limiting factor even in hardware
> that has an ILM SRAM table and some form of radix based
> lookup.  All of the hardwre I've seen in the last 15
> years or so forwards MPLS and IP at the same rate.

Which was exactly my point - unless you somehow missed that.

> ...
> Except IPv6 before they decided to waste the lower half
> of the address space with 40 quintilion host in a
> bridged subnet and you really did have to look at the
> whole 128 bits.

It is no secret that forwarding of IPv6 packets on some=20
vendor equipment is about half the rate of IPv4 or MPLS. But=20
then again, because MPLS control planes are IPv4-driven=20
today, I'm hoping I didn't have to be explicit about not=20
including IPv6 in that group, on this list.

> Back when forwarding was done in
> software (circa 1995) your statement would have been
> true if MPLS preceeded forwarding ASICs which it did
> not.

You might not know that line cards from C like the LSP=20
(Label Switch Processor) and much of the PFE from J's PTX=20
are forwarding engines that have been made cheaper by=20
reducing the IP FIB on the assumption that all traffic will=20
be carried in MPLS. This is, obviously, an assumption I do=20
not support because:

	- I run IPv6 natively, and at the moment, there are
	  no production-grade IPv6 control planes for MPLS.

	- It assumes providers will run 6PE (in which case,
	  IPv6 traffic enjoys MPLS and IPv6 wire rate
	  forwarding speeds).

I do not buy such line cards because for anyone running=20
native IPv6, you could potentially run out of FIB slots to=20
host IPv6 routes.

That is why I say MPLS has allowed vendors to put out=20
cheaper line cards compared to the costs of those which have=20
large IPv4/IPv6 scale. Because MPLS forwarding is so=20
mainstream, there is no additional cost associated with=20
forwarding rates similar to IPv4. So much of the cost of=20
line cards is in QoS queues and routing FIB slots (and MPLS-
biased line cards are stripped of that, hence making them=20
cheaper).

> Also the statement "Current-generation ASIC's have no
> problem forwarding MPLS frames at wire rate" is not true
> for most (or all) hardware with 40 byte payloads (even
> with plus 4 with TCP SACK plus 4 if MPLS) and 100 Gb/s
> interfaces.  It is true for "average packet size"
> traffic and on most hardware only true if bursts of 40
> byte packets are very limited in duration.

C'mon, Curtis. Everybody knows this already. Moreover, real=20
world IP traffic is not all 40 bytes.

If operators have doubts about what forwarding engines can=20
do below 128 bytes, that is what PoC labs are for before you=20
buy. And even then, several operators accept the=20
restrictions up to a certain point, because the lab and real=20
life vary significantly.

Mark.

--nextPart1564113.ZqtHiklPLi
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS0udMAAoJEGcZuYTeKm+GxhUQAKZAROVv7BygnH/5UIS6z5Zz
2NMk2GFbUL3p4hFWjOVwBSqhi6FVc6KRWpBynXlBTDJBaJIZfkD5HjBT7ZSr6m94
jYQLXeznNF1GnDMii8nA+n5kOQFahbOR21aKzm/GI/DUyH7dsqckHnZYy+K8m7cO
ZmCPDuNV5BAba5Gsi7vFXFHak6z8dLqQWKzeUt7/im2HGCOphGQOhUXWuqqvgUFH
lhh5H2JIntXJniCGsibbqBy5lTNviZ4qH2smXeFHjmPOyBzfRpBoYn82KJz6avry
vunb+Ki1G0si+PPpbSv+rq8NE+i2RbH5/4cHjwPMhtNYYwu9LAEgZn2tLEialh56
TAui8DVpNZIJlH16IOn1gvIoEaridKeZsf4aT+0NwGr1jkc+P1AWEq6xse8o5Vqq
XmnS/YmGLuCdknuzQzuIHzmmhdscDsw5LoCmd+Hel4tY3CvbcdGzMsaCWolADPke
69UX7tMuH8N8E499aiorT377kOn5yfOdSXEx8O4hRpPMoEbtQ4L1Q10XWrTJij3l
1tq7v0wy+TnZUGWzltMj+OWbCbfrwGx8j6KY3MjK29UkTtSswsR2s8WPHdoANlt+
oyk7v8XVbHt0/obgA3R1aPlrOHOx2U81LkBn4D+NlvAOeD5SbS7V+4l+NLgD6BZ0
6WmISwj1cO2CivbvsM38
=tmsD
-----END PGP SIGNATURE-----

--nextPart1564113.ZqtHiklPLi--

From xuxiaohu@huawei.com  Sun Jan 12 18:13:01 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA6D31ACCE8; Sun, 12 Jan 2014 18:13:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98qSy6Gt0ND8; Sun, 12 Jan 2014 18:12:58 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 227621A1F64; Sun, 12 Jan 2014 18:12:57 -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.7-GA FastPath queued) with ESMTP id AZW40990; Mon, 13 Jan 2014 02:12:44 +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.3.158.1; Mon, 13 Jan 2014 02:11:57 +0000
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 02:12:42 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 10:12:39 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "Eggert, Lars" <lars@netapp.com>, Joel Halpern <jmh@joelhalpern.com>
Subject: =?gb2312?B?tPC4tDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50?= =?gb2312?B?eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMgaW4gVURQKSB0byBQcm9wb3NlZCBT?= =?gb2312?Q?tandard?=
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw///RhoCAAHJGgIAACUSAgAAlhQCABCkZ8A==
Date: Mon, 13 Jan 2014 02:12:38 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824422A@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B7447E4@eusaamb103.ericsson.se>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:16:10 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 02:13:01 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogbXBscyBbbWFpbHRvOm1wbHMtYm91
bmNlc0BpZXRmLm9yZ10gtPqx7SBHcmVnb3J5IE1pcnNreQ0KPiC3osvNyrG85DogMjAxNMTqMdTC
MTHI1SAyOjI0DQo+IMrVvP7IyzogRWdnZXJ0LCBMYXJzOyBKb2VsIEhhbHBlcm4NCj4gs63LzTog
bXBsc0BpZXRmLm9yZzsgSUVURg0KPiDW98ziOiBSZTogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0
LWlldGYtbXBscy1pbi11ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGluZyBNUExTDQo+IGluIFVEUCkg
dG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IEhpIExhcnMsDQo+IEkgdGhpbmsgdGhhdCAiIFRo
ZSB3aG9sZSBwb2ludCBvZiBydW5uaW5nIE1QTFMgaXMgdG8gY3JlYXRlIG5ldHdvcmtzIGluIHdo
aWNoDQo+IHBhdGhzIGFyZSBwcm92aXNpb25hYmxlLCBzbyB0aGlzIGlzIHVzdWFsbHkgbm90IGFu
IGlzc3VlLiIgaXMgb25seSBwYXJ0aWFsbHkgY29ycmVjdC4NCj4gTERQLWJhc2VkIE1QTFMgbmV0
d29yayBpcyBub3QgcHJvdmlzaW9uYWJsZSBhbmQgTFNQcyBmb2xsb3cgSVAgYmVzdCByb3V0ZQ0K
PiBzZWxlY3Rpb24uIEV4cGxpY2l0IHNpZ25hbGluZyBvZiBMU1AgaXMgYWNoaWV2YWJsZSBpbiAo
RylNUExTIGJ5IHVzaW5nIFJTVlAoLVRFKQ0KPiBzaWduYWxpbmcuDQoNCisxLiBXaXRoIHRoZSBy
ZXBsYWNlbWVudCBvZiBhIExEUC1iYXNlZCBMU1AgdHVubmVsIGJ5IGFuIElQLWJhc2VkIHR1bm5l
bCAoZS5nLiwgTVBMUy1pbi1HUkUsIE1QTFMtaW4tSVAgb3IgTVBMUy1pbi1VRFApLCB0aGUgcGF0
aCB0aGF0IHRoZSB0cmFmZmljIHRyYXZlbHMgdGhyb3VnaCBpcyBub3QgY2hhbmdlZCBhdCBhbGwu
DQoNCkJlc3QgcmVnYXJkcywNClhpYW9odQ0KDQo+IAlSZWdhcmRzLA0KPiAJCUdyZWcNCj4gDQo+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IG1wbHMgW21haWx0bzptcGxzLWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBFZ2dlcnQsIExhcnMNCj4gU2VudDogRnJpZGF5
LCBKYW51YXJ5IDEwLCAyMDE0IDg6MTAgQU0NCj4gVG86IEpvZWwgSGFscGVybg0KPiBDYzogbXBs
c0BpZXRmLm9yZzsgSUVURg0KPiBTdWJqZWN0OiBSZTogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0
LWlldGYtbXBscy1pbi11ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGluZw0KPiBNUExTIGluIFVEUCkg
dG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+IEhpLA0KPiANCj4gT24gMjAxNC0xLTEwLCBhdCAx
NjozNiwgSm9lbCBNLiBIYWxwZXJuIDxqbWhAam9lbGhhbHBlcm4uY29tPiB3cm90ZToNCj4gPiBN
YXliZSBJIGFtIGNvbXBsZXRlbHkgbWlzc2luZyB0aGluZ3MsIGJ1dCB0aGlzIGxvb2tzIHdyb25n
Lg0KPiA+IElmIHRoZSBNUExTIExTUCBpcyBjYXJyeWluZyBmaXhlZCByYXRlIHBzZXVkby13aXJl
cywgYWRkaW5nIGNvbmdlc3Rpb24NCj4gPiBjb250cm9sIHdpbGwgbWFrZSBpdCBtb3JlIGxpa2Vs
eSB0aGF0IHRoZSBzZXJ2aWNlIHdvbid0IHdvcmsuICBJcyB0aGF0DQo+ID4gcmVhbGx5IHRoZSBn
b2FsPw0KPiA+DQo+ID4gV2UgZG8gbm90IHBlcmZvcm0gY29uZ2VzdGlvbiBjb250cm9sIG9uIE1Q
TFMgTFNQcy4NCj4gPiBBc3N1bWluZyB0aGF0IGEgVURQIHR1bm5lbCBpcyBjYXJyeWluZyBqdXN0
IE1QTFMgYW5kIHdhcyBlc3RhYmxpc2hlZA0KPiA+IGp1c3QgZm9yIE1QTFMsIHdoeSB3b3VsZCB3
ZSBleHBlY3QgaXQgdG8gYmVoYXZlIGRpZmZlcmVudGx5IHRoYW4gYW4NCj4gPiBNUExTIExTUCBy
dW5uaW5nIG92ZXIgdGhlIGV4YWN0IHNhbWUgcGF0aCwgY2FycnlpbmcgdGhlIGV4YWN0IHNhbWUg
dHJhZmZpYz8NCj4gDQo+IHdlJ3ZlIGJlZW4gcmVoYXNoaW5nIHRoaXMgZGlzY3Vzc2lvbiBzZXZl
cmFsIHRpbWVzIG92ZXIgdGhlIHllYXJzLCBlLmcuLCBmb3IgUFdFLA0KPiBBTVQsIGV0Yy4gSW4g
b3JkZXIgdG8gY2FycnkgZml4ZWQtcmF0ZSBvciBvdGhlcndpc2Ugbm9uLWNvbmdlc3Rpb24tY29u
dHJvbGxlZA0KPiB0cmFmZmljIG92ZXIgdW5wcm92aXNpb25lZCBnZW5lcmFsIEludGVybmV0IHBh
dGhzLCB0aGVyZSBuZWVkcyB0byBiZSBzb21lIHNvcnQgb2YNCj4gYmFzaWMgY29uZ2VzdGlvbiBj
b250cm9sIG1lY2hhbmlzbSwgbGlrZSBhIGNpcmN1aXQgYnJlYWtlci4NCj4gDQo+IFRoZSB3aG9s
ZSBwb2ludCBvZiBydW5uaW5nIE1QTFMgaXMgdG8gY3JlYXRlIG5ldHdvcmtzIGluIHdoaWNoIHBh
dGhzIGFyZQ0KPiBwcm92aXNpb25hYmxlLCBzbyB0aGlzIGlzIHVzdWFsbHkgbm90IGFuIGlzc3Vl
LiBCdXQgaWYgeW91IHN0YXJ0IHN0aWNraW5nIE1QTFMgaW5zaWRlDQo+IG9mIFVEUCwgdGhvc2Ug
cGFja2V0cyBjYW4gZ28gYW55d2hlcmUgb24gdGhlIG5ldCwgc28geW91IG5lZWQgbWVjaGFuaXNt
cyB0bw0KPiBjb250cm9sIHRoZSByYXRlIG9mIHRoYXQgdHJhZmZpYyBpZiBpdCBjYXVzZXMgY29u
Z2VzdGlvbiwgb3IgYXQgdGhlIHZlcnkgbGVhc3QgeW91DQo+IG5lZWQgdG8gYmUgYWJsZSB0byBz
dG9wIHRoZSB0cmFmZmljIGlmIGl0IGNyZWF0ZXMgc2V2ZXJlIGNvbmdlc3Rpb24uDQo+IA0KPiBM
YXJzDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
IG1wbHMgbWFpbGluZyBsaXN0DQo+IG1wbHNAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo=

From xuxiaohu@huawei.com  Sun Jan 12 19:40:41 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1401AD8F9; Sun, 12 Jan 2014 19:40:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov1hr5t2B58t; Sun, 12 Jan 2014 19:40:40 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id CACC91AD6C1; Sun, 12 Jan 2014 19:40:38 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AZW46192; Mon, 13 Jan 2014 03:40:27 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 03:39:48 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 03:40:24 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 11:40:18 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Scott Brim <scott.brim@gmail.com>, "Eggert, Lars" <lars@netapp.com>
Subject: =?gb2312?B?tPC4tDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50?= =?gb2312?B?eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMgaW4gVURQKSB0byBQcm9wb3NlZCBT?= =?gb2312?Q?tandard?=
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw///RhoCAAHJGgIAACUSAgAAGQwCABFBrUA==
Date: Mon, 13 Jan 2014 03:40:17 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com>
In-Reply-To: <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@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.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:16:54 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 03:40:42 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogU2NvdHQgQnJpbSBbbWFpbHRvOnNj
b3R0LmJyaW1AZ21haWwuY29tXQ0KPiC3osvNyrG85DogMjAxNMTqMdTCMTHI1SAwOjMyDQo+IMrV
vP7IyzogRWdnZXJ0LCBMYXJzDQo+ILOty806IEpvZWwgSGFscGVybjsgbXBsc0BpZXRmLm9yZzsg
WHV4aWFvaHU7IElFVEYNCj4g1vfM4jogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1p
bi11ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGluZyBNUExTIGluIFVEUCkNCj4gdG8gUHJvcG9zZWQg
U3RhbmRhcmQNCj4gDQo+IEkgZG9uJ3QgdGhpbmsgaXQncyByaWdodCB0byB0cnkgdG8gc29sdmUg
dGhpcyBpbiBNUExTLCBiZWNhdXNlIE1QTFMgaXMgbm90IGENCj4gZm9yd2FyZGluZyBwcm90b2Nv
bCAtIGl0J3MgYSBjb25uZWN0aXZpdHkgcHJvdG9jb2wuIEluIGFueSB1c2Ugb2YgVURQLCBjb25n
ZXN0aW9uDQo+IGNvbnRyb2wgaXMgZWl0aGVyIGxlZnQgdG8gc29tZXRoaW5nIGFib3ZlIFVEUCBv
ciBpZ25vcmVkIChsZWZ0IHRvIHF1ZXVlDQo+IG1hbmFnZW1lbnQpLiBTaW1pbGFybHksIHlvdSB3
YW50IHRoZSBjbGllbnQgb2YgTVBMUyB0byBiZSByZXNwb25zaWJsZSBmb3INCj4gbWFuYWdpbmcg
aXRzIHRyYWZmaWMuIE1QTFMgZ2l2ZXMgeW91IHBhdGhzLCBpdCBkb2Vzbid0IHB1c2ggcGFja2V0
cyBvdmVyIHRoZW0uDQoNCkZ1bGx5IGFncmVlLiBUaGUgY29uZ2VzdGlvbiBjb250cm9sIHNob3Vs
ZCBiZSBwZXJmb3JtZWQgZWl0aGVyIGJ5IHRoZSBVRFAgdHVubmVsIGl0c2VsZiBvciB0aGUgY2xp
ZW50IG9mIE1QTFMuIEluIHRoZSBmb3JtZXIgY2FzZSwgaXQnZCBiZXR0ZXIgdG8gc3BlY2lmeSB0
aGUgcHJhY3RpY2FsIGNvbmdlc3Rpb24gY29udHJvbCBtZWNoYW5pc21zIChpZiB0aGVyZSB3ZXJl
IGFueSkgaW4gYSBnZW5lcmljIGRyYWZ0IChlLmcuLCBSRkM1NDA1YmlzKSBhbmQgdGhlbiBhbnkg
dXNlIG9mIHRoZSBVRFAgdHVubmVsIGNvdWxkIHJlZmVyIHRvIHRoYXQgZ2VuZXJpYyBkcmFmdCB3
aXRoIHJlZ2FyZCB0byBjb25nZXN0aW9uIGNvbnRyb2wuIEluIHRoZSBsYXR0ZXIgY2FzZSwgaWYg
dGhlIGNsaWVudCBvZiBNUExTIGlzIFRDUC1mcmllbmRseSwgdGhhdCBpcyBncmVhdC4gT3RoZXJ3
aXNlIChlLmcuLCBjaXJjdWl0IGVtdWxhdGlvbiBzZXJ2aWNlKSwgaXQgc2hvdWxkbid0IGJlIGRl
cGxveWVkIG9uIHRoZSBJbnRlcm5ldCBhdCBhbGwsIGp1c3QgYXMgaGFzIGJlZW4gcG9pbnRlZCBv
dXQgaW4gUkZDMzk4NSwgdGhlcmVmb3JlIHRoZXJlIGlzIG5vIG5lZWQgZm9yIGFueSBzcGVjaWZp
YyBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtIG9uIHRoZSBjbGllbnQuDQogICANCiAgIi4u
LiBJbiBlc3NlbmNlLCB0aGlzIHJlcXVpcmVtZW50IHN0YXRlcyB0aGF0IGl0IGlzDQogICBub3Qg
YWNjZXB0YWJsZSB0byBkZXBsb3kgYW4gYXBwbGljYXRpb24gKHVzaW5nIFBXRTMgb3IgYW55IG90
aGVyDQogICB0cmFuc3BvcnQgcHJvdG9jb2wpIG9uIHRoZSBiZXN0LWVmZm9ydCBJbnRlcm5ldCwg
d2hpY2ggY29uc3VtZXMNCiAgIGJhbmR3aWR0aCBhcmJpdHJhcmlseSBhbmQgZG9lcyBub3QgY29t
cGV0ZSBmYWlybHkgd2l0aCBUQ1Agd2l0aGluIGFuDQogICBvcmRlciBvZiBtYWduaXR1ZGUuIiAo
cXVvdGVkIGZyb20gU2VjdGlvbiA2LjUgb2YgUkZDMzk4NSkNCg0KVGhlIGFib3ZlIGNob2ljZSBz
ZWVtcyBubyBjb25mbGljdCB3aXRoIHRoZSBmb2xsb3dpbmcgY29uZ2VzdGlvbiBjb250cm9sIGd1
aWRlbGluZXMgYXMgcXVvdGVkIGZyb20gU2VjdGlvbiAzLjEuMSBvZiBSRkM1NDA1LCBhcyB0aG9z
ZSBub24tVENQLWZyaWVuZGx5IHRyYWZmaWMgd291bGQgYmUgdHJhbnNwb3J0ZWQgb3ZlciBhIHBy
b3Zpc2lvbmVkIHBhdGgsIHJhdGhlciB0aGFuIG9uIHRoZSBJbnRlcm5ldC4NCg0KICAgIi4uLkZp
bmFsbHksIHNvbWUgYnVsayB0cmFuc2ZlciBhcHBsaWNhdGlvbnMgbWF5IGNob29zZSBub3QgdG8g
aW1wbGVtZW50DQogICBhbnkgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlzbSBhbmQgaW5zdGVh
ZCByZWx5IG9uIHRyYW5zbWl0dGluZw0KICAgYWNyb3NzIHJlc2VydmVkIHBhdGggY2FwYWNpdHku
ICBUaGlzIG1pZ2h0IGJlIGFuIGFjY2VwdGFibGUgY2hvaWNlDQogICBmb3IgYSBzdWJzZXQgb2Yg
cmVzdHJpY3RlZCBuZXR3b3JraW5nIGVudmlyb25tZW50cywgYnV0IGlzIGJ5IG5vDQogICBtZWFu
cyBhIHNhZmUgcHJhY3RpY2UgZm9yIG9wZXJhdGlvbiBpbiB0aGUgSW50ZXJuZXQuIg0KDQpCZXN0
IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiBTY290dA0KPiANCj4gDQo+IE9uIEZyaSwgSmFuIDEwLCAy
MDE0IGF0IDExOjA5IEFNLCBFZ2dlcnQsIExhcnMgPGxhcnNAbmV0YXBwLmNvbT4gd3JvdGU6DQo+
ID4gSGksDQo+ID4NCj4gPiBPbiAyMDE0LTEtMTAsIGF0IDE2OjM2LCBKb2VsIE0uIEhhbHBlcm4g
PGptaEBqb2VsaGFscGVybi5jb20+IHdyb3RlOg0KPiA+PiBNYXliZSBJIGFtIGNvbXBsZXRlbHkg
bWlzc2luZyB0aGluZ3MsIGJ1dCB0aGlzIGxvb2tzIHdyb25nLg0KPiA+PiBJZiB0aGUgTVBMUyBM
U1AgaXMgY2FycnlpbmcgZml4ZWQgcmF0ZSBwc2V1ZG8td2lyZXMsIGFkZGluZw0KPiA+PiBjb25n
ZXN0aW9uIGNvbnRyb2wgd2lsbCBtYWtlIGl0IG1vcmUgbGlrZWx5IHRoYXQgdGhlIHNlcnZpY2Ug
d29uJ3QNCj4gPj4gd29yay4gIElzIHRoYXQgcmVhbGx5IHRoZSBnb2FsPw0KPiA+Pg0KPiA+PiBX
ZSBkbyBub3QgcGVyZm9ybSBjb25nZXN0aW9uIGNvbnRyb2wgb24gTVBMUyBMU1BzLg0KPiA+PiBB
c3N1bWluZyB0aGF0IGEgVURQIHR1bm5lbCBpcyBjYXJyeWluZyBqdXN0IE1QTFMgYW5kIHdhcyBl
c3RhYmxpc2hlZA0KPiA+PiBqdXN0IGZvciBNUExTLCB3aHkgd291bGQgd2UgZXhwZWN0IGl0IHRv
IGJlaGF2ZSBkaWZmZXJlbnRseSB0aGFuIGFuDQo+ID4+IE1QTFMgTFNQIHJ1bm5pbmcgb3ZlciB0
aGUgZXhhY3Qgc2FtZSBwYXRoLCBjYXJyeWluZyB0aGUgZXhhY3Qgc2FtZSB0cmFmZmljPw0KPiA+
DQo+ID4gd2UndmUgYmVlbiByZWhhc2hpbmcgdGhpcyBkaXNjdXNzaW9uIHNldmVyYWwgdGltZXMg
b3ZlciB0aGUgeWVhcnMsIGUuZy4sIGZvcg0KPiBQV0UsIEFNVCwgZXRjLiBJbiBvcmRlciB0byBj
YXJyeSBmaXhlZC1yYXRlIG9yIG90aGVyd2lzZQ0KPiBub24tY29uZ2VzdGlvbi1jb250cm9sbGVk
IHRyYWZmaWMgb3ZlciB1bnByb3Zpc2lvbmVkIGdlbmVyYWwgSW50ZXJuZXQgcGF0aHMsDQo+IHRo
ZXJlIG5lZWRzIHRvIGJlIHNvbWUgc29ydCBvZiBiYXNpYyBjb25nZXN0aW9uIGNvbnRyb2wgbWVj
aGFuaXNtLCBsaWtlIGENCj4gY2lyY3VpdCBicmVha2VyLg0KPiA+DQo+ID4gVGhlIHdob2xlIHBv
aW50IG9mIHJ1bm5pbmcgTVBMUyBpcyB0byBjcmVhdGUgbmV0d29ya3MgaW4gd2hpY2ggcGF0aHMg
YXJlDQo+IHByb3Zpc2lvbmFibGUsIHNvIHRoaXMgaXMgdXN1YWxseSBub3QgYW4gaXNzdWUuIEJ1
dCBpZiB5b3Ugc3RhcnQgc3RpY2tpbmcgTVBMUyBpbnNpZGUNCj4gb2YgVURQLCB0aG9zZSBwYWNr
ZXRzIGNhbiBnbyBhbnl3aGVyZSBvbiB0aGUgbmV0LCBzbyB5b3UgbmVlZCBtZWNoYW5pc21zIHRv
DQo+IGNvbnRyb2wgdGhlIHJhdGUgb2YgdGhhdCB0cmFmZmljIGlmIGl0IGNhdXNlcyBjb25nZXN0
aW9uLCBvciBhdCB0aGUgdmVyeSBsZWFzdCB5b3UNCj4gbmVlZCB0byBiZSBhYmxlIHRvIHN0b3Ag
dGhlIHRyYWZmaWMgaWYgaXQgY3JlYXRlcyBzZXZlcmUgY29uZ2VzdGlvbi4NCj4gPg0KPiA+IExh
cnMNCg==

From xuxiaohu@huawei.com  Sun Jan 12 23:07:18 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414781AE050; Sun, 12 Jan 2014 23:07:18 -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=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xD8FXE6wBVYI; Sun, 12 Jan 2014 23:07:16 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B1FAD1AE04C; Sun, 12 Jan 2014 23:07:15 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCK83381; Mon, 13 Jan 2014 07:07:03 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 07:06:24 +0000
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 07:07:00 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 15:06:54 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-mpls-in-udp.all@tools.ietf.org" <draft-ietf-mpls-in-udp.all@tools.ietf.org>
Subject: =?gb2312?B?tPC4tDogR2VuLUFSVCBMQyByZXZpZXcgb2YgZHJhZnQtaWV0Zi1tcGxzLWlu?= =?gb2312?Q?-udp-04?=
Thread-Topic: Gen-ART LC review of draft-ietf-mpls-in-udp-04
Thread-Index: Ac8PkQgMv9aHcPU1QKqHAKnrA2qEzAAnLfyA
Date: Mon, 13 Jan 2014 07:06:53 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433B@NKGEML512-MBS.china.huawei.com>
References: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
In-Reply-To: <10b001cf0f92$7c6ddb90$754992b0$@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:17:07 -0800
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 07:07:18 -0000

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

SGkgUm9uaSwNCg0KVGhhbmtzIGEgbG90IGZvciB5b3VyIEdlbi1BUlQgcmV2aWV3IGFuZCBjb21t
ZW50cy4gWW91ciBjb21tZW50cyB3b3VsZCBiZSBjb25zaWRlcmVkIGluIHRoZSBuZXh0IHJldmlz
aW9uLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0Kt6K8/sjLOiBSb25pIEV2ZW4gW21haWx0
bzpyb24uZXZlbi50bHZAZ21haWwuY29tXQ0Kt6LLzcqxvOQ6IDIwMTTE6jHUwjEyyNUgMjA6MzMN
CsrVvP7IyzogZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC5hbGxAdG9vbHMuaWV0Zi5vcmcNCrOty806
IGdlbi1hcnRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCtb3zOI6IEdlbi1BUlQgTEMgcmV2aWV3
IG9mIGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFS
VCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tncm91bmQgb24gR2VuLUFSVCwgcGxl
YXNlIHNlZSB0aGUgRkFRIGF0IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NClBsZWFzZSByZXNvbHZlIHRoZXNlIGNvbW1lbnRzIGFsb25n
IHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cyB5b3UgbWF5IHJlY2VpdmUuDQoNCkRv
Y3VtZW50OiAgZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNA0KDQpSZXZpZXdlcjogUm9uaSBFdmVu
DQoNClJldmlldyBEYXRlOjIwMTSoQzEtMTINCg0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNKhDMS0x
Ng0KDQpJRVNHIFRlbGVjaGF0IGRhdGU6DQoNCg0KDQpTdW1tYXJ5OiBUaGlzIGRyYWZ0IGlzIGFs
bW9zdCByZWFkeSBmb3IgcHVibGljYXRpb24gYXMgYSBzdGFuZGFyZCB0cmFjayBSRkMuDQoNCg0K
DQoNCg0KTWFqb3IgaXNzdWVzOg0KDQoNCg0KTWlub3IgaXNzdWVzOg0KDQoNCg0KDQpOaXRzL2Vk
aXRvcmlhbCBjb21tZW50cw0KDQoxLiAgICAgICBUaGUgYWJzdHJhY3Qgc2VjdGlvbiBjYW4gYmUg
ZXhwYW5kZWQgd2l0aCB0ZXh0IGZyb20gdGhlIGZpcnN0IHBhcmFncmFwaCBvZiB0aGUgaW50cm9k
dWN0aW9uIHByb3ZpZGluZyBtb3JlIGluZm9ybWF0aW9uIGFib3V0IHVzYWdlDQoNCjIuICAgICAg
IFRoZSBjb25nZXN0aW9uIHNlY3Rpb24gbWF5IG5lZWQgc29tZSB0ZXh0IG9uIFVEUCBjb25nZXN0
aW9uIHN1cHBvcnQsIG1heWJlIHJlZmVyZW5jZSBSRkM0NTA1IGJ1dCBJIGFtIGFsc28gT0sgd2l0
aCBtb3N0IG9mIHRoZSBjdXJyZW50IHRleHQuDQoNCg0K

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

<html>
<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:SimSun;
	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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:36.0pt;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:SimSun;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:246115313;
	mso-list-type:hybrid;
	mso-list-template-ids:1460930480 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:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:0cm;}
ul
	{margin-bottom:0cm;}
--></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:16.0pt;line-=
height:115%;color:#1F497D">Hi Roni,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Thanks a lot for your Gen-ART review and comment=
s. Your comments would be considered in the next revision.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Best regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D">Xiaohu<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"font-size:16.0pt;line-=
height:115%;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:0cm;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size:10.0pt;font-family:SimSun">=B7=A2=BC=FE=C8=CB<s=
pan lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" style=3D"font-si=
ze:10.0pt;font-family:SimSun"> Roni Even [mailto:ron.even.tlv@gmail.com]
<br>
</span><b><span style=3D"font-size:10.0pt;font-family:SimSun">=B7=A2=CB=CD=
=CA=B1=BC=E4<span lang=3D"EN-US">:</span></span></b><span lang=3D"EN-US" st=
yle=3D"font-size:10.0pt;font-family:SimSun"> 2014</span><span style=3D"font=
-size:10.0pt;font-family:SimSun">=C4=EA<span lang=3D"EN-US">1</span>=D4=C2<=
span lang=3D"EN-US">12</span>=C8=D5<span lang=3D"EN-US">
 20:33<br>
</span><b>=CA=D5=BC=FE=C8=CB<span lang=3D"EN-US">:</span></b><span lang=3D"=
EN-US"> draft-ietf-mpls-in-udp.all@tools.ietf.org<br>
</span><b>=B3=AD=CB=CD<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> gen-art@ietf.org; ietf@ietf.org<br>
</span><b>=D6=F7=CC=E2<span lang=3D"EN-US">:</span></b><span lang=3D"EN-US"=
> Gen-ART LC review of draft-ietf-mpls-in-udp-04<o:p></o:p></span></span></=
p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
<span lang=3D"EN-US">I am the assigned Gen-ART reviewer for this draft. For=
 background on Gen-ART, please see the FAQ at &lt;</span><span lang=3D"EN-U=
S"><a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" targ=
et=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&g=
t;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Please resolve these comments a=
long with any other Last Call comments you may receive.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:&nbsp;
</span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">d=
raft-ietf-mpls-in-udp-04<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer: Roni Even<o=
:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review Date:2014=A8C1=
-12<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF LC End Date: 201=
4=A8C1-16<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG Telechat date:
<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary: This draft i=
s almost ready for publication as a standard track RFC.<o:p></o:p></span></=
p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major issues:<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor issues:<o:p></o=
:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"font-size:11.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Nits/editorial comments<o:p></o=
:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">The abstract section ca=
n be expanded with text from the first paragraph of the introduction provid=
ing more information about usage<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo2"><![if !supportLists]><span lang=3D"EN-US"><span style=3D"mso-list:=
Ignore">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]><span lang=3D"EN-US">The congestion section =
may need some text on UDP congestion support, maybe reference RFC4505 but I=
 am also OK with most of the current text.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824433BNKGEML512MBSchi_--

From xuxiaohu@huawei.com  Mon Jan 13 01:16:55 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2A081AE0AF; Mon, 13 Jan 2014 01:16:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gA-8fgQphADM; Mon, 13 Jan 2014 01:16:52 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 84F471ADF81; Mon, 13 Jan 2014 01:16:51 -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.7-GA FastPath queued) with ESMTP id BCK96578; Mon, 13 Jan 2014 09:16:40 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 09:15:48 +0000
Received: from NKGEML408-HUB.china.huawei.com (10.98.56.39) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 13 Jan 2014 09:16:34 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml408-hub.china.huawei.com ([10.98.56.39]) with mapi id 14.03.0158.001; Mon, 13 Jan 2014 17:16:30 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: =?gb2312?B?tPC4tDogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50?= =?gb2312?B?eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMgaW4gVURQKSB0byBQcm9wb3NlZCBT?= =?gb2312?Q?tandard?=
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPDJU4xcLOVIDgI0yv/bpzgg7Unpp9UGqw///RhoCAAHJGgIAACUSAgAAGQwCABFBrUP//5XoAgACK6gA=
Date: Mon, 13 Jan 2014 09:16:30 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
In-Reply-To: <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Mon, 13 Jan 2014 07:18:22 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 09:16:56 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogRWdnZXJ0LCBMYXJzIFttYWlsdG86
bGFyc0BuZXRhcHAuY29tXQ0KPiC3osvNyrG85DogMjAxNMTqMdTCMTPI1SAxNjo1MA0KPiDK1bz+
yMs6IFh1eGlhb2h1DQo+ILOty806IFNjb3R0IEJyaW07IEpvZWwgSGFscGVybjsgbXBsc0BpZXRm
Lm9yZzsgSUVURg0KPiDW98ziOiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVk
cC0wNC50eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMgaW4gVURQKQ0KPiB0byBQcm9wb3NlZCBTdGFu
ZGFyZA0KPiANCj4gSGksDQo+IA0KPiBPbiAyMDE0LTEtMTMsIGF0IDQ6NDAsIFh1eGlhb2h1IDx4
dXhpYW9odUBodWF3ZWkuY29tPiB3cm90ZToNCj4gPj4gSSBkb24ndCB0aGluayBpdCdzIHJpZ2h0
IHRvIHRyeSB0byBzb2x2ZSB0aGlzIGluIE1QTFMsIGJlY2F1c2UgTVBMUw0KPiA+PiBpcyBub3Qg
YSBmb3J3YXJkaW5nIHByb3RvY29sIC0gaXQncyBhIGNvbm5lY3Rpdml0eSBwcm90b2NvbC4NCj4g
DQo+IHJpZ2h0LCBNUExTIGlzIHRoZSB3cm9uZyBwbGFjZSB0byBhZGRyZXNzIGlzLiBUaGUgVURQ
IGVuY2Fwcy9kZWNhcHMgZnVuY3Rpb24NCj4gbmVlZHMgdG8gaGF2ZSB0aGlzIGZ1bmN0aW9uYWxp
dHkuDQo+IA0KPiA+PiBJbiBhbnkgdXNlIG9mIFVEUCwgY29uZ2VzdGlvbg0KPiA+PiBjb250cm9s
IGlzIGVpdGhlciBsZWZ0IHRvIHNvbWV0aGluZyBhYm92ZSBVRFAgb3IgaWdub3JlZCAobGVmdCB0
bw0KPiA+PiBxdWV1ZSBtYW5hZ2VtZW50KS4NCj4gDQo+IFRoZXJlIGFyZSBzZXZlcmFsIGNhc2Vz
LCBzZWUgU2VjdGlvbiAzLjEuMyBvZiBSRkM1NDA1LiBNUExTLW92ZXItVURQIGNhbiBmYWxsDQo+
IGludG8gYW55IG9mIHRoZSB0aHJlZSBjYXNlcywgZGVwZW5kaW5nIG9uIHdoYXQgdHJhZmZpYyBp
cyBpbnNpZGUgdGhlIExTUCBiZWluZw0KPiBlbmNhcHN1bGF0ZWQuDQo+IA0KPiBZb3UnbGwgbm90
aWNlIHRoYXQgUkZDNTQwNSBmb3IgdGhlIGZpcnN0IGNhc2UgLSBlbmNhcHN1bGF0aW9uIG9mIElQ
LWJhc2VkDQo+IGNvbmdlc3Rpb24gY29udHJvbGxlZCAibm9ybWFsIiBJbnRlcm5ldCB0cmFmZmlj
IC0gZXZlbiBzYXlzIHRoYXQgdGhlIHR1bm5lbA0KPiBTSE9VTEQgTk9UIGVtcGxveSBhbnkgY29u
Z2VzdGlvbiBjb250cm9sIHNjaGVtZSBvZiBpdHMgb3duLiBIYXZpbmcgbGF5ZXJlZA0KPiBjb250
cm9sIGxvb3BzIGZpZ2h0aW5nIGlzIG5vdCBwcm9kdWN0aXZlLg0KPiANCj4gVGhlIGlzc3VlIHdp
dGggTVBMUy1pbi1VRFAgKGFuZCBHUkUtaW4tVURQLCBhbmQgYW55IG90aGVyIGVuY2FwcyBzY2hl
bWUNCj4gdGhhdCBjYW4gY2Fycnkgbm9uLUlQIHRyYWZmaWMpIGFyZSB3aXRoIGNhc2VzIHR3byBh
bmQgdGhyZWUuIFdoZW4gdGhlIHdvcmtsb2FkDQo+IHRoYXQgaXMgYmVpbmcgZW5jYXBzdWxhdGVk
IGlzbid0IGtub3duIHRvIGJlIGNvbmdlc3Rpb24gY29udHJvbGxlZCBieSBpdHMNCj4gZW5kcG9p
bnRzLCBpdCBpcyB0aGUgb2JsaWdhdGlvbiBvZiB0aGUgdHVubmVsIHRvIGRldGVjdCBjb25nZXN0
aW9uIGFuZCByZWFjdCB0byBpdA0KPiBieSByZWR1Y2luZyB0aGUgdHJhZmZpYyB2b2x1bWUuIEJl
Y2F1c2UgZm9yIHRoZSByZXN0IG9mIHRoZSBuZXR3b3JrLCB0aGF0IHR1bm5lbA0KPiBpcyB0aGUg
VURQIHNlbmRlciwgYW5kIHdlIGhhdmUgSUVURiBjb25zZW5zdXMgdGhhdCB3ZSBkb24ndCB3YW50
IFVEUCBzZW5kZXJzDQo+IHRoYXQgZG9uJ3QgcmVhY3QgdG8gY29uZ2VzdGlvbiBvbiB0aGUgbmV0
LiAoVGhhdCdzIG9uZSBvZiB0aGUgbWFpbiByZWFzb25zIGZvcg0KPiB0aGUgZXhpc3RlbmNlIG9m
IHRoZSBSTUNBVCBXRyAtIHdlIGRvbid0IHdhbnQgbm9uLWNvbmdlc3Rpb24tY29udHJvbGxlZCBS
VFANCj4gbWVkaWEgdHJhZmZpYyBvbiB0aGUgbmV0LikNCj4gDQo+IFRoZSBrZXkgZGlmZmVyZW5j
ZSBiZXR3ZWVuIHB1dHRpbmcgTVBMUyBlLmcuIGludG8gSVAgY29tcGFyZWQgdG8gcHV0dGluZyBp
dA0KPiBpbnRvIFVEUCBpcyB0aGF0IG9uY2UgaXQncyBpbiBVRFAsIGl0IGNhbiBnbyBwcmV0dHkg
bXVjaCBhbnl3aGVyZSBvbiB0aGUgbmV0LA0KPiBiZWNhdXNlIFVEUCB0cmF2ZXJzZXMgTkFUcyBh
bmQgZmlyZXdhbGxzIG11Y2ggbW9yZSBlYXNpbHkgdGhhbiBJUCB0cmFmZmljIHdpdGgNCj4gYSBy
YXJlIHByb3RvY29sIG51bWJlciBkb2VzLg0KPiANCj4gPj4gU2ltaWxhcmx5LCB5b3Ugd2FudCB0
aGUgY2xpZW50IG9mIE1QTFMgdG8gYmUgcmVzcG9uc2libGUgZm9yIG1hbmFnaW5nDQo+ID4+IGl0
cyB0cmFmZmljLiBNUExTIGdpdmVzIHlvdSBwYXRocywgaXQgZG9lc24ndCBwdXNoIHBhY2tldHMg
b3ZlciB0aGVtLg0KPiANCj4gUmlnaHQuIEhvd2V2ZXIsIG9uY2UgeW91IHNsYXAgYSBVRFAgaGVh
ZGVyIG9uIGEgcGFja2V0IGR1cmluZyBlbmNhcHN1bGF0aW9uLA0KPiB5b3Ugbm93IHN1YmplY3Rl
ZCB5b3Vyc2VsZiB0byB0aGUgcnVsZXMgZm9yIEludGVybmV0IFVEUCBzZW5kZXJzLiBUaG9zZSBh
cmUNCj4gZG9jdW1lbnRlZCBpbiBSRkM1NDA1LCBhbmQgcmVxdWlyZSB0aGUgdHVubmVsIHRvIGlt
cGxlbWVudCBzb21lIHNvcnQgb2YNCj4gY29uZ2VzdGlvbiBkZXRlY3Rpb24gYW5kIGNvbnRyb2wu
IEknZCBwZXJzb25hbGx5IGNvbnNpZGVyIGEgY2lyY3VpdCBicmVha2VyDQo+IG1lY2hhbmlzbSBz
dWZmaWNpZW50LCBsaWtlIFJUUCBhbmQgSSB0aGluayBQV0UgYXJlIHVzaW5nLg0KPiANCj4gPiBG
dWxseSBhZ3JlZS4gVGhlIGNvbmdlc3Rpb24gY29udHJvbCBzaG91bGQgYmUgcGVyZm9ybWVkIGVp
dGhlciBieSB0aGUgVURQDQo+IHR1bm5lbCBpdHNlbGYgb3IgdGhlIGNsaWVudCBvZiBNUExTLiBJ
biB0aGUgZm9ybWVyIGNhc2UsIGl0J2QgYmV0dGVyIHRvIHNwZWNpZnkgdGhlDQo+IHByYWN0aWNh
bCBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtcyAoaWYgdGhlcmUgd2VyZSBhbnkpIGluIGEg
Z2VuZXJpYyBkcmFmdA0KPiAoZS5nLiwgUkZDNTQwNWJpcykgYW5kIHRoZW4gYW55IHVzZSBvZiB0
aGUgVURQIHR1bm5lbCBjb3VsZCByZWZlciB0byB0aGF0DQo+IGdlbmVyaWMgZHJhZnQgd2l0aCBy
ZWdhcmQgdG8gY29uZ2VzdGlvbiBjb250cm9sLg0KPiANCj4gVGhlIGdlbmVyYWwgY29uY2VwdCBv
ZiBhIGNpcmN1aXQgYnJlYWtlciBpcyBlYXN5IGVub3VnaCB0aGF0IGl0IGRvZXNuJ3QgcmVhbGx5
DQo+IG5lZWQgdG8gYmUgd3JpdHRlbiBkb3duLiBBbmQgaXQgd291bGRuJ3QgYmUgcG9zc2libGUg
dG8gZGVzY3JpYmUgaXQgaW4gYSBnZW5lcmljDQo+IGZhc2hpb24sIGJlY2F1c2UgY29uZ2VzdGlv
biBkZXRlY3Rpb24gaXMgdHlwaWNhbGx5IHNwZWNpZmljIHRvIHRoZSBwcm90b2NvbCBiZWluZw0K
PiBlbmNhcHN1bGF0ZWQgKGUuZy4sIFJUUCB1c2VzIFJUQ1AgZmVlZGJhY2sgdG8gZGVyaXZlIGxv
c3MgaW5mb3JtYXRpb24sIGV0Yy4pIEFuZA0KPiB0aGUgcmVhY3Rpb24gdG8gY29uZ2VzdGlvbiBp
cyBhbHNvIGRlcGVuZGVudCBvbiB0aGUgcHJvdG9jb2wgYmVpbmcNCj4gZW5jYXBzdWxhdGVkIChk
b2VzIGl0IHN1cHBvcnQgbXVsdGlwbGUgcmF0ZXMgb3Igb25seSBvbi9vZmYsIHdoYXQgdGltZXNj
YWxlcyBhcmUNCj4gT0sgZm9yIHJlYWN0aW9uLCBldGMuKQ0KPiANCj4gPiBJbiB0aGUgbGF0dGVy
IGNhc2UsIGlmIHRoZSBjbGllbnQgb2YgTVBMUyBpcyBUQ1AtZnJpZW5kbHksIHRoYXQgaXMgZ3Jl
YXQuIE90aGVyd2lzZQ0KPiAoZS5nLiwgY2lyY3VpdCBlbXVsYXRpb24gc2VydmljZSksIGl0IHNo
b3VsZG4ndCBiZSBkZXBsb3llZCBvbiB0aGUgSW50ZXJuZXQgYXQgYWxsLA0KPiBqdXN0IGFzIGhh
cyBiZWVuIHBvaW50ZWQgb3V0IGluIFJGQzM5ODUsIHRoZXJlZm9yZSB0aGVyZSBpcyBubyBuZWVk
IGZvciBhbnkNCj4gc3BlY2lmaWMgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlzbSBvbiB0aGUg
Y2xpZW50Lg0KPiA+DQo+ID4gICIuLi4gSW4gZXNzZW5jZSwgdGhpcyByZXF1aXJlbWVudCBzdGF0
ZXMgdGhhdCBpdCBpcw0KPiA+ICAgbm90IGFjY2VwdGFibGUgdG8gZGVwbG95IGFuIGFwcGxpY2F0
aW9uICh1c2luZyBQV0UzIG9yIGFueSBvdGhlcg0KPiA+ICAgdHJhbnNwb3J0IHByb3RvY29sKSBv
biB0aGUgYmVzdC1lZmZvcnQgSW50ZXJuZXQsIHdoaWNoIGNvbnN1bWVzDQo+ID4gICBiYW5kd2lk
dGggYXJiaXRyYXJpbHkgYW5kIGRvZXMgbm90IGNvbXBldGUgZmFpcmx5IHdpdGggVENQIHdpdGhp
biBhbg0KPiA+ICAgb3JkZXIgb2YgbWFnbml0dWRlLiIgKHF1b3RlZCBmcm9tIFNlY3Rpb24gNi41
IG9mIFJGQzM5ODUpDQo+ID4NCj4gPiBUaGUgYWJvdmUgY2hvaWNlIHNlZW1zIG5vIGNvbmZsaWN0
IHdpdGggdGhlIGZvbGxvd2luZyBjb25nZXN0aW9uIGNvbnRyb2wNCj4gZ3VpZGVsaW5lcyBhcyBx
dW90ZWQgZnJvbSBTZWN0aW9uIDMuMS4xIG9mIFJGQzU0MDUsIGFzIHRob3NlIG5vbi1UQ1AtZnJp
ZW5kbHkNCj4gdHJhZmZpYyB3b3VsZCBiZSB0cmFuc3BvcnRlZCBvdmVyIGEgcHJvdmlzaW9uZWQg
cGF0aCwgcmF0aGVyIHRoYW4gb24gdGhlDQo+IEludGVybmV0Lg0KPiA+DQo+ID4gICAiLi4uRmlu
YWxseSwgc29tZSBidWxrIHRyYW5zZmVyIGFwcGxpY2F0aW9ucyBtYXkgY2hvb3NlIG5vdCB0byBp
bXBsZW1lbnQNCj4gPiAgIGFueSBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtIGFuZCBpbnN0
ZWFkIHJlbHkgb24gdHJhbnNtaXR0aW5nDQo+ID4gICBhY3Jvc3MgcmVzZXJ2ZWQgcGF0aCBjYXBh
Y2l0eS4gIFRoaXMgbWlnaHQgYmUgYW4gYWNjZXB0YWJsZSBjaG9pY2UNCj4gPiAgIGZvciBhIHN1
YnNldCBvZiByZXN0cmljdGVkIG5ldHdvcmtpbmcgZW52aXJvbm1lbnRzLCBidXQgaXMgYnkgbm8N
Cj4gPiAgIG1lYW5zIGEgc2FmZSBwcmFjdGljZSBmb3Igb3BlcmF0aW9uIGluIHRoZSBJbnRlcm5l
dC4iDQo+IA0KPiBIb3cgaXMgdGhhdCBpbiBjb25mbGljdD8gQm90aCBxdW90ZXMgc2F5IHRoYXQg
SW50ZXJuZXQgdHJhZmZpYyBuZWVkcyBjb25nZXN0aW9uDQo+IGNvbnRyb2wsIHdoaWNoIGlzIGEg
cmVzdGF0ZW1lbnQgb2YgUkZDMjkxNC4NCg0KSGkgTGFycywNCg0KTm8gY29uZmxpY3QgYXQgYWxs
LiBXaGF0IEkgbWVhbnQgaXM6IGZvciB0aG9zZSBjbGllbnRzIG9mIE1QTFMgd2hpY2ggYXJlIG5v
dCBUQ1AtZnJpZW5kbHkgKGNhc2UgMiYzIGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDMuMS4zIG9m
IFJGQzU0MDUpLCB0aGV5IHNob3VsZCBuZXZlciBiZSB0cmFuc3BvcnRlZCBvdmVyIHRoZSB1bnBy
b3Zpc2lvbmVkIHBhdGggKGUuZy4sIHRoZSBJbnRlcm5ldCkuIEluc3RlYWRzLCB0aGV5IHNob3Vs
ZCBvbmx5IGJlIHRyYW5zcG9ydGVkIG92ZXIgYSBwcm92aXNpb25lZCBwYXRoIGluIGEgcmVzdHJp
Y3RlZCBuZXR3b3JraW5nIGVudmlyb25tZW50LiBBcyBhIHJlc3VsdCwgdGhlcmUgaXMgbm8gbmVl
ZCBmb3IgdGhlIGNvbmdlc3Rpb24gY29udHJvbCBtZWNoYW5pc20gZm9yIHRoZW0uDQoNCkJlc3Qg
cmVnYXJkcywNClhpYW9odQ0KDQo+IExhcnMNCg==

From jmh@joelhalpern.com  Mon Jan 13 07:51:59 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E181AE115; Mon, 13 Jan 2014 07:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5LWw16SU__M; Mon, 13 Jan 2014 07:51:58 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 796A11AE098; Mon, 13 Jan 2014 07:51:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id C9E631C06303; Mon, 13 Jan 2014 07:51:47 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 6F31B1C06304; Mon, 13 Jan 2014 07:51:46 -0800 (PST)
Message-ID: <52D40B91.8040101@joelhalpern.com>
Date: Mon, 13 Jan 2014 10:51:45 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
In-Reply-To: <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 15:51:59 -0000

Lars, are you really asking that the document say:
1) That the UDP encapsulation of MPLS can only be used when the devices
performing the encapsulation and decapsulation know what protocol (above
IP, if IP is being carried; above Ethernet and IP if the frame is
Ethernet carrying IP) is being used
2) That those devices need to engage in a congestion control protocol if
the carried packets are not TCP, SCTP, or DCCP?

Those both look like excessive and difficult requirements.  Which is
fine if our goal is to pretend we are telling folks not to use UDP
encapsulation of MPLS.  (I had not thought that was our goal.)

In practice, I simply do not see how anyone implementing this will pay
any attention to either requirement.

Yours,
Joel

On 1/13/14 3:50 AM, Eggert, Lars wrote:
> Hi,
> 
> On 2014-1-13, at 4:40, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>>> I don't think it's right to try to solve this in MPLS, because
>>> MPLS is not a forwarding protocol - it's a connectivity
>>> protocol.
> 
> right, MPLS is the wrong place to address is. The UDP encaps/decaps
> function needs to have this functionality.
> 
>>> In any use of UDP, congestion control is either left to something
>>> above UDP or ignored (left to queue management).
> 
> There are several cases, see Section 3.1.3 of RFC5405. MPLS-over-UDP
> can fall into any of the three cases, depending on what traffic is
> inside the LSP being encapsulated.
> 
> You'll notice that RFC5405 for the first case - encapsulation of
> IP-based congestion controlled "normal" Internet traffic - even says
> that the tunnel SHOULD NOT employ any congestion control scheme of
> its own. Having layered control loops fighting is not productive.
> 
> The issue with MPLS-in-UDP (and GRE-in-UDP, and any other encaps
> scheme that can carry non-IP traffic) are with cases two and three.
> When the workload that is being encapsulated isn't known to be
> congestion controlled by its endpoints, it is the obligation of the
> tunnel to detect congestion and react to it by reducing the traffic
> volume. Because for the rest of the network, that tunnel is the UDP
> sender, and we have IETF consensus that we don't want UDP senders
> that don't react to congestion on the net. (That's one of the main
> reasons for the existence of the RMCAT WG - we don't want
> non-congestion-controlled RTP media traffic on the net.)
> 
> The key difference between putting MPLS e.g. into IP compared to
> putting it into UDP is that once it's in UDP, it can go pretty much
> anywhere on the net, because UDP traverses NATs and firewalls much
> more easily than IP traffic with a rare protocol number does.
> 
>>> Similarly, you want the client of MPLS to be responsible for 
>>> managing its traffic. MPLS gives you paths, it doesn't push
>>> packets over them.
> 
> Right. However, once you slap a UDP header on a packet during
> encapsulation, you now subjected yourself to the rules for Internet
> UDP senders. Those are documented in RFC5405, and require the tunnel
> to implement some sort of congestion detection and control. I'd
> personally consider a circuit breaker mechanism sufficient, like RTP
> and I think PWE are using.
> 
>> Fully agree. The congestion control should be performed either by
>> the UDP tunnel itself or the client of MPLS. In the former case,
>> it'd better to specify the practical congestion control mechanisms
>> (if there were any) in a generic draft (e.g., RFC5405bis) and then
>> any use of the UDP tunnel could refer to that generic draft with
>> regard to congestion control.
> 
> The general concept of a circuit breaker is easy enough that it
> doesn't really need to be written down. And it wouldn't be possible
> to describe it in a generic fashion, because congestion detection is
> typically specific to the protocol being encapsulated (e.g., RTP uses
> RTCP feedback to derive loss information, etc.) And the reaction to
> congestion is also dependent on the protocol being encapsulated (does
> it support multiple rates or only on/off, what timescales are OK for
> reaction, etc.)
> 
>> In the latter case, if the client of MPLS is TCP-friendly, that is
>> great. Otherwise (e.g., circuit emulation service), it shouldn't be
>> deployed on the Internet at all, just as has been pointed out in
>> RFC3985, therefore there is no need for any specific congestion
>> control mechanism on the client.
>> 
>> "... In essence, this requirement states that it is not acceptable
>> to deploy an application (using PWE3 or any other transport
>> protocol) on the best-effort Internet, which consumes bandwidth
>> arbitrarily and does not compete fairly with TCP within an order of
>> magnitude." (quoted from Section 6.5 of RFC3985)
>> 
>> The above choice seems no conflict with the following congestion
>> control guidelines as quoted from Section 3.1.1 of RFC5405, as
>> those non-TCP-friendly traffic would be transported over a
>> provisioned path, rather than on the Internet.
>> 
>> "...Finally, some bulk transfer applications may choose not to
>> implement any congestion control mechanism and instead rely on
>> transmitting across reserved path capacity.  This might be an
>> acceptable choice for a subset of restricted networking
>> environments, but is by no means a safe practice for operation in
>> the Internet."
> 
> How is that in conflict? Both quotes say that Internet traffic needs
> congestion control, which is a restatement of RFC2914.
> 
> Lars
> 

From scott.brim@gmail.com  Mon Jan 13 11:10:14 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA31D1ADF48; Mon, 13 Jan 2014 11:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jthw63jgjqFi; Mon, 13 Jan 2014 11:10:12 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id A9A4F1ADF30; Mon, 13 Jan 2014 11:10:12 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id uz6so8076264obc.37 for <multiple recipients>; Mon, 13 Jan 2014 11:10:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=nE0na4ItdB7roaoNLWC4JjOVNLLfW/qhLCfvyE3UEXQ=; b=lqa4L45p5SdD7SXP1WgbjI61WR9adqvlsBCfwfFehj8HfbKR5cdPBJ+Z6cogsydyCU 4Emmkwek9/DDlKrgTn/eaynBpTWSoft4yjMG8D0vtOmiGQgkr28yi8oLdFfBltT+S/0w 78ck8CQskczAI6GrC78nIXJtCrQS601DSgpdMZhhi9UFK+lhqULKoCwEhVSjjBNu59Ka HCWVUkCz1YM9jQ43z+W7M+jUvbdicNmC3qROsml+rdeFErgj8i7MU9DGCSJyP8/PFTHb twsNKyKtB98qLpTZK3zVVTHIcvcos2+1M4rJdBAbTQhSbRa6aPpAO4FCwXTG/snLvDrX ZdYg==
X-Received: by 10.60.65.101 with SMTP id w5mr22007857oes.0.1389640200544; Mon, 13 Jan 2014 11:10:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 13 Jan 2014 11:09:40 -0800 (PST)
In-Reply-To: <52D40B91.8040101@joelhalpern.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 13 Jan 2014 14:09:40 -0500
Message-ID: <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 19:10:14 -0000

On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> Lars, are you really asking that the document say:
> 1) That the UDP encapsulation of MPLS can only be used when the devices
> performing the encapsulation and decapsulation know what protocol (above
> IP, if IP is being carried; above Ethernet and IP if the frame is
> Ethernet carrying IP) is being used
> 2) That those devices need to engage in a congestion control protocol if
> the carried packets are not TCP, SCTP, or DCCP?
>
> Those both look like excessive and difficult requirements.

I'm concerned about TCP-over-X.25 scenarios. If the lower layer
encapsulation does not know what congestion management is being used
above, and it does what would be best assuming there isn't any,
performance can truly suck.

How was this handled in other cases?

Saying UDP is a user of IP and thus must provide congestion control
would be fine if our layering were simple and UDP was Transport, but
in this case UDP is "lower layer", an encapsulation to extend the
reach of MPLS and whatever is running over it.

> Which is
> fine if our goal is to pretend we are telling folks not to use UDP
> encapsulation of MPLS.  (I had not thought that was our goal.)
>
> In practice, I simply do not see how anyone implementing this will pay
> any attention to either requirement.

Yes.

My inclination is that this is not fundamental architecture, and we
can afford to see if there's a problem before we solve it.

Scott

From stephen.farrell@cs.tcd.ie  Mon Jan 13 11:27:13 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9BED1ADF7F for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJKGdKTluaXS for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:27:10 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8B54E1ACCDA for <ietf@ietf.org>; Mon, 13 Jan 2014 11:27:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id B4127BE3E for <ietf@ietf.org>; Mon, 13 Jan 2014 19:26:57 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sFOZgI5Tluht for <ietf@ietf.org>; Mon, 13 Jan 2014 19:26:57 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 97557BE39 for <ietf@ietf.org>; Mon, 13 Jan 2014 19:26:57 +0000 (GMT)
Message-ID: <52D43E02.2010604@cs.tcd.ie>
Date: Mon, 13 Jan 2014 19:26:58 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: draft-farrell-perpass-attack edits for -04
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 19:27:13 -0000

Hi all,

Together with a bunch of folks who've commented on this,
we've been doing some edits to we hope better reflect
the list discussion over the last while and have a
pre-04 version [1] for folks to look at. (Thanks
especially to Dave Crocker and Steve Kent for detailed
suggestions.) There's a diff at [2].

We've also changed the body of the document so that
the resolution of the BCP vs Informational issue
should only require a change to the header. (For the
record, I don't personally mind if it ends up as an
IETF consensus informational document, even though I
do think it really is better as, and is, a BCP. I
figure that Jari has plenty of input on that already
anyway:-)

Note that these changes are not nits, they're relatively
substantive editorial changes, but at least IMO don't
weaken or strengthen the meat of the document, but
they do I think make it clearer and better.

Please let us know if we've messed up in any of
those edits.

The reason we're not yet pushing this out as -04 is
that, as we said when we posted -03, there was an
outstanding comment from Sam Hartman that hadn't been
addressed at all. I'll send a separate mail on that
now that Sam and I have what we think is change that
would handle his comment.

And once Jari tells us to, we'll shoot out -04.

Cheers,
S.

[1] http://down.dsg.cs.tcd.ie/misc/draft-farrell-perpass-attack-04.txt
[2]
http://tools.ietf.org/rfcdiff?url1=draft-farrell-perpass-attack-03.txt&url2=http://down.dsg.cs.tcd.ie/misc/draft-farrell-perpass-attack-04.txt

From stephen.farrell@cs.tcd.ie  Mon Jan 13 11:28:53 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528DF1ADF93 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3TyobNLlwsh for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:28:51 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9253D1ADF89 for <ietf@ietf.org>; Mon, 13 Jan 2014 11:28:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 5417ABE3E for <ietf@ietf.org>; Mon, 13 Jan 2014 19:28:40 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nv0ryJpMZFAm for <ietf@ietf.org>; Mon, 13 Jan 2014 19:28:40 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 30613BE39 for <ietf@ietf.org>; Mon, 13 Jan 2014 19:28:40 +0000 (GMT)
Message-ID: <52D43E69.6090001@cs.tcd.ie>
Date: Mon, 13 Jan 2014 19:28:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: draft-farrell-perpass-attack architecture issue
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 19:28:53 -0000

Hi all,

Sam raised an issue that we didn't handle in the -03
version. [1] After some offlist mail between us I think
that his issue would be resolved with a change such as
the one below, adding a new paragraph.

Should text like this be added to the document? FWIW,
I'd be ok with that, or with leaving this out and for
a slightly longer discussion of the topic to be part
of Richard et al's problem statement draft. [2]

Please say what you think.

The proposed change in OLD/NEW form is:

OLD

   Those developing IETF specifications need to be able to describe how
   they have considered pervasive monitoring, and, if the attack is
   relevant to the work to be published, be able to justify related
   design decisions.  This does not mean a new "pervasive monitoring
   considerations" section is needed in IETF documentation.  It means
   that, if asked, there needs to be a good answer to the question "is
   pervasive monitoring relevant to this work and if so how has it been
   considered?"

NEW

   Those developing IETF specifications need to be able to describe how
   they have considered pervasive monitoring, and, if the attack is
   relevant to the work to be published, be able to justify related
   design decisions.  This does not mean a new "pervasive monitoring
   considerations" section is needed in IETF documentation.  It means
   that, if asked, there needs to be a good answer to the question "is
   pervasive monitoring relevant to this work and if so how has it been
   considered?"

   In particular, architectural decisions, including which existing
   technology is re-used, significantly impact the vulnerability of
   a protocol to pervasive monitoring.  For example, if a protocol
   uses DNS to store information, then a passive attacker can observe
   the queries made to the DNS. Those developing IETF specifications
   therefore need to consider mitigating pervasive monitoring when
   making these architectural decisions and be prepared to justify
   their decisions.  Getting adequate, early review of architectural
   decisions including whether appropriate mitigation of pervasive
   monitoring can be made is important.  Revisiting these architectural
   decisions late in the process is very costly.

Thanks,
S.

[1] https://www.ietf.org/mail-archive/web/ietf/current/msg84996.html
[2] https://tools.ietf.org/html/draft-barnes-pervasive-problem


From scott.brim@gmail.com  Mon Jan 13 11:37:11 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88DA31ADFA0 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:37:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JduMGCHiZYLq for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 11:37:10 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1A81C1ADF92 for <ietf@ietf.org>; Mon, 13 Jan 2014 11:37:10 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id gq1so8155388obb.17 for <ietf@ietf.org>; Mon, 13 Jan 2014 11:36:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ivNJX0cKS4nm+PLy67hiXV/xvqdvp8umtcUMdug/Z6M=; b=AukZ2Em4WWWC0llrHWocjoO7OFjYYc/8gjdU9HrpzAPuSZDvhxN0cvwwynXmd8QYZf eaBrsnKCwJeRrJ6OyoUxHfkMqqXxJYlg0JjmMdjEMaAek3d8C1URUHMcaLfjqH+/Le9m /QWN2EXbpDvqpFAFCEMzo4BqaImmfPrRzxqynzfMZI7hko7nhj0WafXKoLCyE3hnWeTF icASdVSCf2ouK4OKPi1VDMIXlBsthh5sJiqwRoCqLDae7FxGEFSTHDmsz9ATg5xM8iYD 9CMnWkmnTDMxFdEDsGs8zgH3uIHkvygq9aYMQmj/g/0oWp5a0Iur4lq0FX/piHUY2/5l 7TbQ==
X-Received: by 10.60.65.5 with SMTP id t5mr22065600oes.19.1389641818902; Mon, 13 Jan 2014 11:36:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 13 Jan 2014 11:36:38 -0800 (PST)
In-Reply-To: <52D43E69.6090001@cs.tcd.ie>
References: <52D43E69.6090001@cs.tcd.ie>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 13 Jan 2014 14:36:38 -0500
Message-ID: <CAPv4CP_M0MUh1px2UiAzx-TD3f9aFVrQJek6we5TzMz1VFAB7Q@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 19:37:11 -0000

On Mon, Jan 13, 2014 at 2:28 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
>    In particular, architectural decisions, including which existing
>    technology is re-used, significantly impact the vulnerability of
>    a protocol to pervasive monitoring.  For example, if a protocol
>    uses DNS to store information, then a passive attacker can observe
>    the queries made to the DNS. Those developing IETF specifications
>    therefore need to consider mitigating pervasive monitoring when
>    making these architectural decisions and be prepared to justify
>    their decisions.  Getting adequate, early review of architectural
>    decisions including whether appropriate mitigation of pervasive
>    monitoring can be made is important.  Revisiting these architectural
>    decisions late in the process is very costly.

Not bad. FYI what got me started on privacy was when ILNP said
"Mobility? No problem, just keep your location updated in DNS".

This all looks good to me except for grammar in the first sentence:
"including which existing technology is re-used".  Do you mean
"including decisions on which existing technology to re-use"?
"including decisions where existing technology is re-used"?

Thanks ... Scott

From kent@bbn.com  Mon Jan 13 12:27:35 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 069281ADFBC for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 12:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxAbN8zDS8eY for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 12:27:32 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 696D81ADFB5 for <ietf@ietf.org>; Mon, 13 Jan 2014 12:27:32 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:50420 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1W2o6S-00007y-L1 for ietf@ietf.org; Mon, 13 Jan 2014 15:27:20 -0500
Message-ID: <52D44C28.4070803@bbn.com>
Date: Mon, 13 Jan 2014 15:27:20 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie>
In-Reply-To: <52D43E69.6090001@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 20:27:35 -0000

Stephen,
> OLD
>
>     Those developing IETF specifications need to be able to describe how
>     they have considered pervasive monitoring, and, if the attack is
>     relevant to the work to be published, be able to justify related
>     design decisions.  This does not mean a new "pervasive monitoring
>     considerations" section is needed in IETF documentation.  It means
>     that, if asked, there needs to be a good answer to the question "is
>     pervasive monitoring relevant to this work and if so how has it been
>     considered?"
>
> NEW
>
>     Those developing IETF specifications need to be able to describe how
>     they have considered pervasive monitoring, and, if the attack is
>     relevant to the work to be published, be able to justify related
>     design decisions.  This does not mean a new "pervasive monitoring
>     considerations" section is needed in IETF documentation.  It means
>     that, if asked, there needs to be a good answer to the question "is
>     pervasive monitoring relevant to this work and if so how has it been
>     considered?"
>
>     In particular, architectural decisions, including which existing
>     technology is re-used, significantly impact the vulnerability of
>     a protocol to pervasive monitoring.  For example, if a protocol
>     uses DNS to store information, then a passive attacker can observe
>     the queries made to the DNS. Those developing IETF specifications
>     therefore need to consider mitigating pervasive monitoring when
>     making these architectural decisions and be prepared to justify
>     their decisions.  Getting adequate, early review of architectural
>     decisions including whether appropriate mitigation of pervasive
>     monitoring can be made is important.  Revisiting these architectural
>     decisions late in the process is very costly.
>
Although I like including a good example, I worry that this example is
too narrow and may send the wrong message. I suggest using the rest of
Sam's text for para 2, but eliding the DNS example. (I say this because
a protocol may make use of the DNS in a way that I would not consider
to be "storing" info there, on behalf of the protocol.)

Steve

From dhc@dcrocker.net  Mon Jan 13 12:33:02 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852851AE026 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 12:33:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vv3vOaoH-kxg for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 12:33:01 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3B90E1AE01C for <ietf@ietf.org>; Mon, 13 Jan 2014 12:33:01 -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 s0DKWidj031540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 13 Jan 2014 12:32:47 -0800
Message-ID: <52D44D67.2090704@dcrocker.net>
Date: Mon, 13 Jan 2014 12:32:39 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Kent <kent@bbn.com>, ietf@ietf.org
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D44C28.4070803@bbn.com>
In-Reply-To: <52D44C28.4070803@bbn.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 13 Jan 2014 12:32:47 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 13 Jan 2014 20:33:02 -0000

On 1/13/2014 12:27 PM, Stephen Kent wrote:
>>
> Although I like including a good example, I worry that this example is
> too narrow and may send the wrong message. I suggest using the rest of
> Sam's text for para 2, but eliding the DNS example. (I say this because
> a protocol may make use of the DNS in a way that I would not consider
> to be "storing" info there, on behalf of the protocol.)


For a topic this broad and this poorly understood -- poorly understood 
by me and folk like me, at least -- what I take from this exchange is 
that examples either need to demonstrate the richness and even nuance of 
concerns or else they need to be absent.

That is, there need to be a collection of examples that touch different 
parts of the space -- sufficiently to show how varied and challenging 
the space is -- or else the level of detail represented by examples 
needs to be deferred to a discussion piece.

Single, simple examples make sense for narrow, simple issues.  This one 
ain't that.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hartmans@mit.edu  Mon Jan 13 13:05:06 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1ADA1ADFE2 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:05:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSkBzUwBWHyB for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:05:05 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 168D21ADFC3 for <ietf@ietf.org>; Mon, 13 Jan 2014 13:05:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 91C6120503; Mon, 13 Jan 2014 16:02:25 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M07jHc3dkiP2; Mon, 13 Jan 2014 16:02:25 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 13 Jan 2014 16:02:25 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id AF197836D4; Mon, 13 Jan 2014 16:04:52 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D44C28.4070803@bbn.com> <52D44D67.2090704@dcrocker.net>
Date: Mon, 13 Jan 2014 16:04:52 -0500
In-Reply-To: <52D44D67.2090704@dcrocker.net> (Dave Crocker's message of "Mon,  13 Jan 2014 12:32:39 -0800")
Message-ID: <tslzjmzvbij.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 21:05:06 -0000

I'd prefer to have an example present if we can come up with one, but
will be OK if we discover that's too hard.
I do beleive the example is the weakest part of the text I proposed

From hsantos@isdg.net  Mon Jan 13 13:13:06 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1491F1AE185 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qJMz1ZEZtErY for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:13:03 -0800 (PST)
Received: from winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 9B86C1AE15D for <ietf@ietf.org>; Mon, 13 Jan 2014 13:13:03 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1703; t=1389647570; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=3v7vNeoIsFd1FR2hCRSHQCQQIY4=; b=OY8Op3SQlGFT9E1DMpAu tP3lBxVRo3z05w1UJnmDY0jFjXcF+zhodfNw+UWffnO4W56PuSqMVd9z+Oq+zhDx pHysREGOKCNJ+BBmw4PkfqOHxa+u6BArxopgevY5ETA1u8cD8ljjFeTChL9LRcvZ 9TVnH4+1dzfkhYz6xE/uC4A=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 13 Jan 2014 16:12:50 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3225040265.40492.4752; Mon, 13 Jan 2014 16:12:49 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1703; t=1389647008; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Kn8iZFI ihN7GvEoXpKXbYjlVw8YrY65l4z6c3WaaEs8=; b=n/r8IQXCbIZR9U5WNgj/GSM BwT99YVS9hxE3m4qN7LPyCw80uwGehVhHfeEomL25ldvpN1dwc6GRnZhYqTcgluN Ko/szXCnKG94iDSapBE7U0uMT+z0mwauqehhC19IxLUjgzz+Hd0zGOi3MP6fE04T iLdpJaIE2Ve3OsQ+QDa4=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 13 Jan 2014 16:03:28 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2671353442.9.744; Mon, 13 Jan 2014 16:03:26 -0500
Message-ID: <52D456CF.3040001@isdg.net>
Date: Mon, 13 Jan 2014 16:12:47 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie>
In-Reply-To: <52D43E69.6090001@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 21:13:06 -0000

On 1/13/2014 2:28 PM, Stephen Farrell wrote:

> NEW
>
>     Those developing IETF specifications need to be able to describe how
>     they have considered pervasive monitoring, and, if the attack is
>     relevant to the work to be published, be able to justify related
>     design decisions.  This does not mean a new "pervasive monitoring
>     considerations" section is needed in IETF documentation.  It means
>     that, if asked, there needs to be a good answer to the question "is
>     pervasive monitoring relevant to this work and if so how has it been
>     considered?"
>
>     In particular, architectural decisions, including which existing
>     technology is re-used, significantly impact the vulnerability of
>     a protocol to pervasive monitoring.  For example, if a protocol
>     uses DNS to store information, then a passive attacker can observe
>     the queries made to the DNS. Those developing IETF specifications
>     therefore need to consider mitigating pervasive monitoring when
>     making these architectural decisions and be prepared to justify
>     their decisions.  Getting adequate, early review of architectural
>     decisions including whether appropriate mitigation of pervasive
>     monitoring can be made is important.  Revisiting these architectural
>     decisions late in the process is very costly.

I agree with others that the example probably needs work. Its not 
generic enough.  If this is a BCP, that specific example can come back 
latter in debates as to what level of security/privacy needs to be 
considered, i.e. are we worry about storage (private data leaks) or 
the insecure transmission methods or both?   So IMO, keeping it makes 
the argument for informational status stronger.


-- 
HLS



From lear@cisco.com  Mon Jan 13 13:20:08 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6FF1AE199 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:20:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MEpmomp-DxJA for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:20:06 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id E30561AE196 for <ietf@ietf.org>; Mon, 13 Jan 2014 13:20:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2977; q=dns/txt; s=iport; t=1389647995; x=1390857595; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=XmUn8DVAXwj5pAnwdapDxignwccmggFFPqwJxTl/lxM=; b=R+doOmCSf4mVlNyP0mBZT1kfiJsOm4veIK2wVb1iHaqOGkhIWL1ddWg5 JvoX3p8Lgc4BfQt9eArPOEZ+SEVQ7scE0RarcM209jwAFjhkditnFAWJW 6AjYqhMzBXCxbm2vYLWXtaH1tCgV32fdlaJMVyxMWWg34PO/XRp1OlKOE c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFANxX1FKQ/khN/2dsb2JhbABagwuEDLZ1gRoWdIIlAQEBBCNVEQsSBgICBRYLAgIJAwIBAgErDA4GAQwIAQGIAKoqmmMXgSmNDQEBVoJvgUgBA5gXkhWDLjuBNQ
X-IronPort-AV: E=Sophos;i="4.95,655,1384300800";  d="scan'208";a="2910926"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 13 Jan 2014 21:19:54 +0000
Received: from mctiny.local ([10.61.195.210]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0DLJqsM022162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Jan 2014 21:19:52 GMT
Message-ID: <52D45877.9090501@cisco.com>
Date: Mon, 13 Jan 2014 22:19:51 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie>
In-Reply-To: <52D43E69.6090001@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 21:20:08 -0000

Hi Stephen,

I oppose the change for reasons I state below:

On 1/13/14 8:28 PM, Stephen Farrell wrote:
> Hi all,
>
> Sam raised an issue that we didn't handle in the -03
> version. [1] After some offlist mail between us I think
> that his issue would be resolved with a change such as
> the one below, adding a new paragraph.
>
> Should text like this be added to the document? FWIW,
> I'd be ok with that, or with leaving this out and for
> a slightly longer discussion of the topic to be part
> of Richard et al's problem statement draft. [2]
>
> Please say what you think.
>
> The proposed change in OLD/NEW form is:
>
> OLD
>
>    Those developing IETF specifications need to be able to describe how
>    they have considered pervasive monitoring, and, if the attack is
>    relevant to the work to be published, be able to justify related
>    design decisions.  This does not mean a new "pervasive monitoring
>    considerations" section is needed in IETF documentation.  It means
>    that, if asked, there needs to be a good answer to the question "is
>    pervasive monitoring relevant to this work and if so how has it been
>    considered?"
>
> NEW
>
>    Those developing IETF specifications need to be able to describe how
>    they have considered pervasive monitoring, and, if the attack is
>    relevant to the work to be published, be able to justify related
>    design decisions.  This does not mean a new "pervasive monitoring
>    considerations" section is needed in IETF documentation.  It means
>    that, if asked, there needs to be a good answer to the question "is
>    pervasive monitoring relevant to this work and if so how has it been
>    considered?"
>
>    In particular, architectural decisions, including which existing
>    technology is re-used, significantly impact the vulnerability of
>    a protocol to pervasive monitoring.  For example, if a protocol
>    uses DNS to store information, then a passive attacker can observe
>    the queries made to the DNS. Those developing IETF specifications
>    therefore need to consider mitigating pervasive monitoring when
>    making these architectural decisions and be prepared to justify
>    their decisions.  Getting adequate, early review of architectural
>    decisions including whether appropriate mitigation of pervasive
>    monitoring can be made is important.  Revisiting these architectural
>    decisions late in the process is very costly.
>

While the sentiment isn't bad it's a bit of a truism, and the example
isn't good, since in large part the information shared through DNS can
often and more accurately (albeit not always) be gleaned through other
means (flow state, for instance).  Once again I return to what I have
said previously: developers of specifications should examine this on a
case by case basis (at least for now), weigh whatever tradeoffs they
uncover, and move forward from there.

Eliot

From scott.brim@gmail.com  Mon Jan 13 13:25:44 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476931AE000 for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AsikgVw1Tb1k for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:25:43 -0800 (PST)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id DD25B1ADFFB for <ietf@ietf.org>; Mon, 13 Jan 2014 13:25:42 -0800 (PST)
Received: by mail-oa0-f52.google.com with SMTP id o6so8643883oag.39 for <ietf@ietf.org>; Mon, 13 Jan 2014 13:25:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ipH+SqecyNuCZ3LDINFD1nF3VUYOpEt0/M6biWZIvOE=; b=j9RrF1rH0uvSOdAl8HDbAXb0WukwfWPEPBe30hucneCfgAur7TApH/KqmptDFk7GK8 Zvu/1vXKiVEEsUVTDZ+jtB1NpiWCav5VklvjsQ1ugLcG5KLmDR+oVM8iqTiQiusG913q 0OpE//YQbty2UuCEtYRz62O2b1ZPeOlbIRNrDPaVJzwSDJISjGf00syRQ0zrLC30BMRm 9mvhI6JMUCoATlQxstBCbL58zjy6oNdKUhvWtBdjxGoqx84D4Itpi9C+W8jzeDWu6oX7 7Qw0FhOPCER//iOvmrruolUikx/4cYA5HR5mUVbesVooE6Ae8W6upmFgxtZkKvT1uBJ6 m70Q==
X-Received: by 10.60.65.101 with SMTP id w5mr22471940oes.0.1389648331701; Mon, 13 Jan 2014 13:25:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 13 Jan 2014 13:25:11 -0800 (PST)
In-Reply-To: <52D456CF.3040001@isdg.net>
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 13 Jan 2014 16:25:11 -0500
Message-ID: <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
To: Hector Santos <hsantos@isdg.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 21:25:44 -0000

OK, if we're going to get stuck on the example, we should take it out.
As Sam said, it's the least necessary part.

I still think the phrase in the first sentence "including which
existing technology is re-used" could be better.

From brian.e.carpenter@gmail.com  Mon Jan 13 13:30:52 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95BD31AE1CC for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uywyNDbZJXuC for <ietf@ietfa.amsl.com>; Mon, 13 Jan 2014 13:30:50 -0800 (PST)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id A93551AE1CE for <ietf@ietf.org>; Mon, 13 Jan 2014 13:30:50 -0800 (PST)
Received: by mail-pb0-f42.google.com with SMTP id uo5so7890346pbc.1 for <ietf@ietf.org>; Mon, 13 Jan 2014 13:30:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=xmK9etwqRKeVzbPguc++McU1nQ1gHooRd0W7Cif0I0Y=; b=K1A9ss4aQKPeJF7iqh/Wy4yCJv+swxSHYRDk7UwOqQUflWb2/e70WRbynyO/7Y1FlN lLlnFDF7/ETLaaUGd+K3hBx3oZMZ1ItZGiV3FClA8uHtnN/punvycIzja7kVmDaLP0He nK+6u9P4jJhkdfmJhAdaxWch194B4We/sJJJpfXBpaOZbU8IjvnIDfY5mqiVebhWiUa4 CuXh5sdU7LDLp44qGUAKbhvtHWV8Is5ofR33TmWlVP8fjIzDjdR0v0HvaqTwHLjZgEkI yRJIHjvMEs4Oa5NZX3W3Ua/MVjl3t/T+/931LAnQq/z9MTmBlHn7F97vrRSUTfhT1jcr +1/Q==
X-Received: by 10.66.154.169 with SMTP id vp9mr31902301pab.39.1389648639655; Mon, 13 Jan 2014 13:30:39 -0800 (PST)
Received: from [192.168.178.23] (226.195.69.111.dynamic.snap.net.nz. [111.69.195.226]) by mx.google.com with ESMTPSA id zc5sm40342359pbc.41.2014.01.13.13.30.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Jan 2014 13:30:38 -0800 (PST)
Message-ID: <52D45AFE.7000006@gmail.com>
Date: Tue, 14 Jan 2014 10:30:38 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC
References: <20140103151454.20579.95323.idtracker@ietfa.amsl.com>	<52D35E54.8090204@gmail.com> <m2iotos835.wl%randy@psg.com>
In-Reply-To: <m2iotos835.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 21:30:52 -0000

On 13/01/2014 19:34, Randy Bush wrote:
>> In theory, a working group considers each item in a document and
>> possibly modifies it before approval.
> 
> if you mean approval as in wglc, indeed.  if you mean approval as a wg
> draft to be worked on by the wg, hell no.  the purpose of a wg adopting
> a draft is specifically so it can go through it with a fine toothed
> comb, get consensus, and get it in publishable shape.

Correct. s/approval/final approval/ might clarify.

   Brian

From l.wood@surrey.ac.uk  Tue Jan 14 00:33:09 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEA31AE01D; Tue, 14 Jan 2014 00:33:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.189
X-Spam-Level: 
X-Spam-Status: No, score=0.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iU0vtlwPB9Fu; Tue, 14 Jan 2014 00:33:06 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.164]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF011ACCE9; Tue, 14 Jan 2014 00:33:05 -0800 (PST)
Received: from [195.245.230.131:6188] by server-4.bemta-3.messagelabs.com id 3D/0C-10414-536F4D25; Tue, 14 Jan 2014 08:32:53 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-78.messagelabs.com!1389688372!33605148!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23810 invoked from network); 14 Jan 2014 08:32:52 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 14 Jan 2014 08:32:52 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Tue, 14 Jan 2014 08:32:52 +0000
From: <l.wood@surrey.ac.uk>
To: <jmh@joelhalpern.com>, <lars@netapp.com>, <xuxiaohu@huawei.com>
Date: Tue, 14 Jan 2014 08:28:05 +0000
Subject: RE: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8OGeG46c8oWHrkQO+L1tKxoi92vgC6Kp6g
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com>, <52D01383.2080509@joelhalpern.com>
In-Reply-To: <52D01383.2080509@joelhalpern.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 08:33:09 -0000

SXQgc3RhbmRzIHRvIHJlYXNvbiB0aGF0IGlmIHR1bm5lbGVycyBjYW4gdHVybiBvZmYgdWRwIGNo
ZWNrc3Vtcw0KYmVjYXVzZSB0aGVpciBwZXJmb3JtYW5jZSBpcyBkZWdyYWRlZCwgdGhleSBjYW4g
dHVybiBvZmYNCmNvbmdlc3Rpb24gY29udHJvbCBiZWNhdXNlIGl0IHdpbGwgZGVncmFkZSB0aGVp
ciBwZXJmb3JtYW5jZS4NCg0KUmVzdCBvZiB0aGUgaW50ZXJuZXQgZ2V0dGluZyBjb25nZXN0ZWQg
YW5kIGdldHRpbmcNCm1pc2RlbGl2ZXJlZCBjb3JydXB0ZWQgcGFja2V0cz8gUmVhbGx5IG5vdCB0
aGVpciBwcm9ibGVtLg0KDQpUaGVyZSBhcmUgaW1wb3J0YW50IHZlbmRvcnMgdHJ5aW5nIHRvIHNl
bGwgcHJvZHVjdHMgaGVyZSwNCmFuZCB0aGV5IG5lZWQgcGVyZm9ybWFuY2UgdG8gZG8gc28uDQpH
ZXQgd2l0aCB0aGUgcHJvZ3JhbSENCg0KTGxveWQgV29vZA0KaHR0cDovL2Fib3V0Lm1lL2xsb3lk
d29vZA0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRnJvbTogaWV0
ZiBbaWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9lbCBNLiBIYWxwZXJuIFtq
bWhAam9lbGhhbHBlcm4uY29tXQ0KU2VudDogMTAgSmFudWFyeSAyMDE0IDE1OjM2DQpUbzogRWdn
ZXJ0LCBMYXJzOyBYdXhpYW9odQ0KQ2M6IG1wbHNAaWV0Zi5vcmc7IElFVEYNClN1YmplY3Q6IFJl
OiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTA0LnR4dD4gKEVuY2Fwc3VsYXRp
bmcgTVBMUyBpbiBVRFApIHRvIFByb3Bvc2VkIFN0YW5kYXJkDQoNCk1heWJlIEkgYW0gY29tcGxl
dGVseSBtaXNzaW5nIHRoaW5ncywgYnV0IHRoaXMgbG9va3Mgd3JvbmcuDQpJZiB0aGUgTVBMUyBM
U1AgaXMgY2FycnlpbmcgZml4ZWQgcmF0ZSBwc2V1ZG8td2lyZXMsIGFkZGluZyBjb25nZXN0aW9u
DQpjb250cm9sIHdpbGwgbWFrZSBpdCBtb3JlIGxpa2VseSB0aGF0IHRoZSBzZXJ2aWNlIHdvbid0
IHdvcmsuICBJcyB0aGF0DQpyZWFsbHkgdGhlIGdvYWw/DQoNCldlIGRvIG5vdCBwZXJmb3JtIGNv
bmdlc3Rpb24gY29udHJvbCBvbiBNUExTIExTUHMuDQpBc3N1bWluZyB0aGF0IGEgVURQIHR1bm5l
bCBpcyBjYXJyeWluZyBqdXN0IE1QTFMgYW5kIHdhcyBlc3RhYmxpc2hlZA0KanVzdCBmb3IgTVBM
Uywgd2h5IHdvdWxkIHdlIGV4cGVjdCBpdCB0byBiZWhhdmUgZGlmZmVyZW50bHkgdGhhbiBhbiBN
UExTDQpMU1AgcnVubmluZyBvdmVyIHRoZSBleGFjdCBzYW1lIHBhdGgsIGNhcnJ5aW5nIHRoZSBl
eGFjdCBzYW1lIHRyYWZmaWM/DQoNCllvdXJzLA0KSm9lbA0KDQpPbiAxLzEwLzE0IDM6NDcgQU0s
IEVnZ2VydCwgTGFycyB3cm90ZToNCj4gSGksDQo+DQo+IHRoYXQgc291bmRzIGdvb2QuIFdoYXQg
Y29uZ2VzdGlvbiBjb250cm9sIGFyZSB5b3UgZ29pbmcgdG8gYmUgc3BlY2lmeWluZyBmb3IgeW91
ciB0dW5uZWw/DQo+DQo+IExhcnMNCj4NCj4gT24gMjAxNC0xLTEwLCBhdCA0OjQ2LCBYdXhpYW9o
dSA8eHV4aWFvaHVAaHVhd2VpLmNvbT4gd3JvdGU6DQo+DQo+PiBIaSBMYXJzLA0KPj4NCj4+IFRo
YW5rcyBhIGxvdCBmb3IgeW91ciBjb21tZW50cy4NCj4+DQo+PiBJIHdvbmRlciB3aGV0aGVyIHRo
ZSBmb2xsb3dpbmcgbW9kaWZpZWQgdGV4dCBmb3IgQ29uZ2VzdGlvbiBDb25zaWRlcmF0aW9uIHNl
Y3Rpb24gaXMgT0sgZnJvbSB5b3VyIHBvaW50IG9mIHZpZXc6DQo+Pg0KPj4gU2luY2UgdGhlIE1Q
TFMtaW4tVURQIGVuY2Fwc3VsYXRpb24gY2F1c2VzIE1QTFMgcGFja2V0cyB0byBiZSBmb3J3YXJk
ZWQgdGhyb3VnaCAiVURQIHR1bm5lbHMiLCB0aGUgY29uZ2VzdGlvbiBjb250cm9sIGd1aWRlbGlu
ZXMgZm9yIFVEUCB0dW5uZWxzIGFzIGRlZmluZWQgaW4gU2VjdGlvbiAzLjEuMyBvZiBbUkZDNTQw
NV0gU0hPVUxEIGJlIGZvbGxvd2VkLiBTcGVjaWZpY2FsbHksIE1QTFMgY2FuIGNhcnJ5IGEgbnVt
YmVyIG9mIGRpZmZlcmVudCBwcm90b2NvbHMgYXMgcGF5bG9hZHMuIFdoZW4gdGhlIHBheWxvYWQg
dHJhZmZpYyBpcyBJUC1iYXNlZCBhbmQgY29uZ2VzdGlvbi1jb250cm9sbGVkLCB0aGUgVURQIHR1
bm5lbCBTSE9VTEQgTk9UIGVtcGxveSBpdHMgb3duIGNvbmdlc3Rpb24gY29udHJvbCBtZWNoYW5p
c20sIGJlY2F1c2UgY29uZ2VzdGlvbiBsb3NzZXMgb2YgdHVubmVsZWQgdHJhZmZpYyB3aWxsIGFs
cmVhZHkgdHJpZ2dlciBhbiBhcHByb3ByaWF0ZSBjb25nZXN0aW9uIHJlc3BvbnNlIGF0IHRoZSBv
cmlnaW5hbCBzZW5kZXJzIG9mIHRoZSB0dW5uZWxlZCB0cmFmZmljLiBXaGVuIHRoZSBwYXlsb2Fk
IHRyYWZmaWMgaXMgbm90IGtub3duIHRvIGJlIElQLWJhc2VkLCBvciBpcyBrbm93biB0byBiZSBJ
UC1iYXNlZCBidXQgbm90IGNvbmdlc3Rpb24tY29udHJvbGxlZCwgdGhlIFVEUCB0dW5uZWwgU0hP
VUxEIGVtcGxveSBhbiBhcHByb3ByaWF0ZSBjb25nZXN0aW9uIGNvbnRyb2wgbWVjaGFuaXNtLiBG
dXJ0aGVybW9yZSwgYmVjYXVzZSBVRFAgdHVubmVscyBhcmUgdXN1YWxseSBidWxrLXRyYW5zZmVy
IGFwcGxpY2F0aW9ucyBhcyBmYXIgYXMgdGhlIGludGVybWVkaWF0ZSByb3V0ZXJzIGFyZSBjb25j
ZXJuZWQsIHRoZSBndWlkZWxpbmVzIGFzIGRlZmluZWQgaW4gU2VjdGlvbiAzLjEuMSBvZiBbUkZD
NTQwNV0gU0hPVUxEIGFwcGx5Lg0KPj4NCj4+IEJlc3QgcmVnYXJkcywNCj4+IFhpYW9odQ0KPj4N
Cj4+PiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4+PiC3orz+yMs6IG1wbHMgW21haWx0bzptcGxzLWJv
dW5jZXNAaWV0Zi5vcmddILT6se0gRWdnZXJ0LCBMYXJzDQo+Pj4gt6LLzcqxvOQ6IDIwMTTE6jHU
wjjI1SAxODoyMg0KPj4+IMrVvP7IyzogSUVURg0KPj4+ILOty806IG1wbHNAaWV0Zi5vcmcNCj4+
PiDW98ziOiBSZTogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQu
dHh0PiAoRW5jYXBzdWxhdGluZyBNUExTDQo+Pj4gaW4gVURQKSB0byBQcm9wb3NlZCBTdGFuZGFy
ZA0KPj4+DQo+Pj4gSGksDQo+Pj4NCj4+PiBPbiAyMDE0LTEtMiwgYXQgMTY6MTQsIFRoZSBJRVNH
IDxpZXNnLXNlY3JldGFyeUBpZXRmLm9yZz4gd3JvdGU6DQo+Pj4+IC0gJ0VuY2Fwc3VsYXRpbmcg
TVBMUyBpbiBVRFAnDQo+Pj4+IDxkcmFmdC1pZXRmLW1wbHMtaW4tdWRwLTA0LnR4dD4gYXMgUHJv
cG9zZWQgU3RhbmRhcmQNCj4+Pg0KPj4+DQo+Pj4gdGhpcyBkb2N1bWVudCBuZWVkcyB0byBkZXNj
cmliZSBob3cgaXQgYWRkcmVzc2VzIHRoZSBpc3N1ZXMgcmFpc2VkIGluIEJDUDE0NQ0KPj4+IChS
RkM1NDA1KS4gSXQgYWxyZWFkeSBjb250YWlucyBzb21lIHRleHQgYWJvdXQgbWVzc2FnZXMgc2l6
ZXMgYW5kIGNvbmdlc3Rpb24NCj4+PiBjb25zaWRlcmF0aW9ucywgd2hpY2ggaXMgZ3JlYXQuIFVu
Zm9ydHVuYXRlbHksIHRoZSB0ZXh0IGFib3V0IGNvbmdlc3Rpb24NCj4+PiBjb25zaWRlcmF0aW9u
cyBpcyBub3QgZnVsbHkgaW4gbGluZSB3aXRoIFJGQzU0MDUuDQo+Pj4NCj4+PiBMYXJzDQo+DQo=

From yakushev@google.com  Tue Jan 14 01:30:12 2014
Return-Path: <yakushev@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C69B41AE067 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 01:30:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JgQCurI5km4T for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 01:30:09 -0800 (PST)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5EAA11AE05F for <ietf@ietf.org>; Tue, 14 Jan 2014 01:30:09 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id f11so3136658qae.24 for <ietf@ietf.org>; Tue, 14 Jan 2014 01:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=v52X06pO7uLQMFRfJLqcdkF7Z58KmAeG1xHZJt2ls3w=; b=ONpch2pk+eqWKN59MjtqodMaWOk/oalJvD0DiMb6K0LlLjbpIgmu1/PBe1C152Xt+2 5Wr1O9uV0ntWcXfNwngdT4qRbLQV0P2ABCfKqAGGV/a6HWp9Yd6G8h3aN0u8RIg5i0ea 3/idwtPGeRwmO5vPa2OyjiQR7ZFA4xJpdCDvuKDRY0NtEqTgyzJQHvEBH89XlwzWHslO g669UlJCXZOn8fvfxi7sm5hto2fVfIcB8VpBA5lEiKMQHCvcueJ3r0nkY0hwN9FEsaOd iLhcux5vSQKzlX9NHFEtJ93g/UKS1AoLA9u68Ec0pjaekNdsGvRXy1y0CekNSZLOnrz+ FIIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=v52X06pO7uLQMFRfJLqcdkF7Z58KmAeG1xHZJt2ls3w=; b=anc7ZWuTLUwduK+RsA30HYNx+6x2l9krpAfdr9T3nTJ4+4ur5rdA9LJ4bceZyi0CmR mZt6rZtHtvMljBWzxz7mPN/SmzVOPJ8rvmEtto/r2Dm8REzYUsqX/kDaqmRezRyMstW0 sLFWuCiGd23HTjQj4MaNWtSxxoggCU02SjIvMNL98nkk8PQ2x5h/BUVHcOhD0RSHJxci N0iVh56fEHRJzmYZ6mIGIxmLHLaHEFNw4EHNt+J7T1ugNTwsMiKP82mTbay8O4O2PvP5 qKjAf1NDTTIp3w8E0lkOti8kDSSPjj8qGkPEShsq2zLcQ24nh7YLd6Rie6g2z2kkX+2x 4imQ==
X-Gm-Message-State: ALoCoQkaYLMBq3ZZ84q2T/stwrg4sAw+aHkfJ88HG8UNd+r0aGtbYwkOwrYnzKl/0p/mP/cLjZt7YC6/hq8s7eXBhFjA7av5/D3feS7vBMgzIqodS60ncuElvx7tnGaDl+WZFBNUFJs6CHWz9DV72f+V7rhLfLZx5CY6yj8edB77hqKizbkOkaF/BO6Rk54oqlIZLkw7I0xx
MIME-Version: 1.0
X-Received: by 10.229.84.201 with SMTP id k9mr972903qcl.18.1389691797218; Tue, 14 Jan 2014 01:29:57 -0800 (PST)
Received: by 10.229.140.135 with HTTP; Tue, 14 Jan 2014 01:29:57 -0800 (PST)
Date: Tue, 14 Jan 2014 10:29:57 +0100
Message-ID: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
Subject: Last Call <draft-daboo-icalendar-rscale> (Non-Gregorian Recurrence Rules in iCalendar) to Proposed Standard
From: Gregory Yakushev <yakushev@google.com>
To: Calsify <calsify@ietf.org>, ietf@ietf.org, Cyrus Daboo <cyrus@daboo.name>
Content-Type: multipart/alternative; boundary=001a1134536eebbeb504efead541
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 09:30:13 -0000

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

This is last call for
http://tools.ietf.org/html/draft-daboo-icalendar-rscale . The draft was
extensively discussed at CalConnect (http://calconnect.org/), previous IETF
discussion is on calsify@ietf.org .

The draft functionality is currently fully implemented in Google Calendar. You
can try it out using proprietary Google Calendar API:
1. Follow this link: http://goo.gl/tKTUQZ
2. Click on Oauth2.0 trigger in the upper right corner to authenticate
3. Enter your Google Calendar e-mail into calendarId field
4. Click Execute, you should get 200 OK
5. Now your non-Gregorian recurring event is visible in UI, embedded
calendar, and any client that doesn't do recurrence expansion by itself

Your comments are welcome,
Grisha

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

<div dir=3D"ltr">This is last call for=C2=A0<a href=3D"http://tools.ietf.or=
g/html/draft-daboo-icalendar-rscale">http://tools.ietf.org/html/draft-daboo=
-icalendar-rscale</a> . The draft was extensively discussed at CalConnect (=
<a href=3D"http://calconnect.org/">http://calconnect.org/</a>), previous IE=
TF discussion is on <a href=3D"mailto:calsify@ietf.org">calsify@ietf.org</a=
> .=C2=A0<div>
<br><div>The draft functionality is currently fully implemented in Google C=
alendar.=C2=A0<span style=3D"font-family:arial,sans-serif;font-size:13px">Y=
ou can try it out using proprietary Google Calendar API:</span></div><div><=
div style=3D"font-family:arial,sans-serif;font-size:13px">
1. Follow this link:=C2=A0<a href=3D"http://goo.gl/tKTUQZ" target=3D"_blank=
">http://goo.gl/tKTUQZ</a></div><div style=3D"font-family:arial,sans-serif;=
font-size:13px">2. Click on Oauth2.0 trigger in the upper right corner to a=
uthenticate</div>
<div style=3D"font-family:arial,sans-serif;font-size:13px">3. Enter your Go=
ogle Calendar e-mail into calendarId field</div><div style=3D"font-family:a=
rial,sans-serif;font-size:13px">4. Click Execute, you should get 200 OK</di=
v>
<div style=3D"font-family:arial,sans-serif;font-size:13px">5. Now your non-=
Gregorian recurring event is visible in UI, embedded calendar, and any clie=
nt that doesn&#39;t do recurrence expansion by itself</div></div><div><br>
</div></div><div>Your comments are welcome,</div><div>Grisha</div></div>

--001a1134536eebbeb504efead541--

From stbryant@cisco.com  Tue Jan 14 03:00:58 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27BBC1AE091; Tue, 14 Jan 2014 03:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uXw20RAIqpte; Tue, 14 Jan 2014 03:00:57 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id AD4EB1AE088; Tue, 14 Jan 2014 03:00:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=236; q=dns/txt; s=iport; t=1389697246; x=1390906846; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=/PtE82acgaZJPm2WLe90D+x7T9KcTUuw1MCaN8Tx2oI=; b=S6eN/nSpuCDwhx+PGPRO46Q1QDa+WC+A7OPRCrNdp6MH+Xt3ZcR+bwtd P5Hy3/Ngn4qm0lmJrF7ZHdz8vPWyY4bPM1OZsYeGvIHGDoufEnR7UE2aw TrVcln28JM+mdESPH4e4cp9+7MiCfQtoFERvsyfb9g6QRfkVmo3GQBPit g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah0FANMX1VKQ/khR/2dsb2JhbABagwu7YIESFnSCJQEBAQQ4QAEQCxgJFgQLCQMCAQIBRQYBDAEFAgEBiADFRhePBweENwEDmB6SFYFvgT4
X-IronPort-AV: E=Sophos;i="4.95,658,1384300800";  d="scan'208";a="2934106"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 14 Jan 2014 11:00:44 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0EB0iUm030735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 11:00:44 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0EB0fEC009012; Tue, 14 Jan 2014 11:00:42 GMT
Message-ID: <52D518D9.7010703@cisco.com>
Date: Tue, 14 Jan 2014 11:00:41 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com>
In-Reply-To: <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 11:00:58 -0000

On 13/01/2014 19:09, Scott Brim wrote:
> On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> I'm concerned about TCP-over-X.25 scenarios.
... and how many b/s of that exist in the universe!


Stewart

From scott.brim@gmail.com  Tue Jan 14 05:12:02 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 276F01AE0D2; Tue, 14 Jan 2014 05:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z5HCmf6PJhQP; Tue, 14 Jan 2014 05:11:57 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id C66EE1AE0D1; Tue, 14 Jan 2014 05:11:49 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id l6so9507208oag.23 for <multiple recipients>; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=26v0ajTFWiDpEIK5le1Spsm0vQYR1AbrRr6GeKfRa5c=; b=s8ch4Xo2M9/nrfir6BxgTMfsoNU2h3pYpHOIewwaJcNua0kJBVRyfoB+3g/zMjEjya pbJKE35LN1KY9Am/h0WZj8KTDBUh33Xoe4+7VcktZ6QQiGWTZMaVsvDOz49Dj89T4xrR ockbJU15HOjG4h5WTo8XlcMknRWtxh4OfbBTPhmwxDBDmu21Ex/QyZhUfszIuMLlww54 j5xc9N63VS8luliGcHzTNnmvLXeeq0su9aWF963KMVpopw+4AdYcmID8HCgwKoM1/s7y NCrj5C/BKlSLCIB4U5Xd/RhhqH4X65SPQ5lE7pGKgQi36KC5c7VrOsxKlWKJ1Egpn7qD STkA==
MIME-Version: 1.0
X-Received: by 10.60.174.167 with SMTP id bt7mr1019432oec.54.1389705098259; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 05:11:38 -0800 (PST)
In-Reply-To: <52D518D9.7010703@cisco.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com>
Date: Tue, 14 Jan 2014 08:11:38 -0500
Message-ID: <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
From: Scott Brim <scott.brim@gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=047d7bd6c03eb9759f04efedee24
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 13:12:02 -0000

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

On Jan 14, 2014 6:00 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>
> On 13/01/2014 19:09, Scott Brim wrote:
>>
>> On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com>
wrote:
>> I'm concerned about TCP-over-X.25 scenarios.
>
> ... and how many b/s of that exist in the universe!

Stewart: none that I know of, of course, but it was in production at a
significant time in Internet history and was one of our first experiences
with multiple layers each trying to provide transport control and thereby
destroying goodput. I'll never forget it. When I think of two layers each
trying to do congestion management,  with no way to coordinate with each
other, that's the first example that comes to mind.

Scott

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

<p dir=3D"ltr"><br>
On Jan 14, 2014 6:00 AM, &quot;Stewart Bryant&quot; &lt;<a href=3D"mailto:s=
tbryant@cisco.com">stbryant@cisco.com</a>&gt; wrote:<br>
&gt;<br>
&gt; On 13/01/2014 19:09, Scott Brim wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern &lt;<a href=3D"m=
ailto:jmh@joelhalpern.com">jmh@joelhalpern.com</a>&gt; wrote:<br>
&gt;&gt; I&#39;m concerned about TCP-over-X.25 scenarios.<br>
&gt;<br>
&gt; ... and how many b/s of that exist in the universe!</p>
<p dir=3D"ltr">Stewart: none that I know of, of course, but it was in produ=
ction at a significant time in Internet history and was one of our first ex=
periences with multiple layers each trying to provide transport control and=
 thereby destroying goodput. I&#39;ll never forget it. When I think of two =
layers each trying to do congestion management,=A0 with no way to coordinat=
e with each other, that&#39;s the first example that comes to mind. </p>

<p dir=3D"ltr">Scott</p>

--047d7bd6c03eb9759f04efedee24--

From scott.brim@gmail.com  Tue Jan 14 05:53:06 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A44A31AE067; Tue, 14 Jan 2014 05:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBxxQKrIyaTW; Tue, 14 Jan 2014 05:53:05 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0521ADFF8; Tue, 14 Jan 2014 05:53:04 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id va2so1594234obc.36 for <multiple recipients>; Tue, 14 Jan 2014 05:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=R9WF7lpqrHz3yUu/yk2w6R6UPhTp6zscBTqQRiySacA=; b=q3i1c7mmDf/VmKxR6QRZlKh5ZED3IQjWcFhdWBkq2Nwt7toCFw3DWVdZdgXSE9AUJt w7S8aKuFO76kaJ938QqcE+HdyBjB9vdecrPjZaURljI/Xc4PufJzJf90tfIYSJQlIqSy HcQEsDse/2YVFo3YwSZ1XLO1Gm3MBzX6a7qk2QSt6xGOAoh2AC3WAkwBdLnvtlxec4DF xHHjKzQ+hwwg1g1HuKZgGeX6IGvSownMv8jfJh3xb78hSfptdUA9fkJreNz1XH14tj0B 3g7MBwxvSDyBCPgOd24joQlaal6J+laJlrXJLNi6T68XFGcFMizNpRA/O7U4o6i5QIC5 tTvw==
X-Received: by 10.60.50.202 with SMTP id e10mr1126423oeo.39.1389707573469; Tue, 14 Jan 2014 05:52:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 05:52:33 -0800 (PST)
In-Reply-To: <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 08:52:33 -0500
Message-ID: <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 13:53:06 -0000

Now that I'm at a real keyboard, and since at least one person didn't
get what I was trying to say with my reference, let me try to explain
more clearly.

Transport is pretty arcane. We sometimes get it more or less right
when we're dealing with a single instance of it in endpoints and
routers/switches. In this case, if we add congestion management to the
encapsulating UDP, we have two possible instances of the same function
stacked on top of each other, where each has no way of knowing whether
the other exists, if so what it's doing, or if there's any way to
communicate with it. We have examples in the past where we have got
this badly wrong. IMHO this is more likely to be a problem than not.

The best architectural answer I can think of in this case is the one
with the least surprises built in: treat the lower level UDP as just
an encapsulation, not an intelligent transport protocol. Yes there
should be scope for congestion management but that is higher up, where
the endpoints come in to play.

Scott

On Tue, Jan 14, 2014 at 8:11 AM, Scott Brim <scott.brim@gmail.com> wrote:
>
> On Jan 14, 2014 6:00 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>>
>> On 13/01/2014 19:09, Scott Brim wrote:
>>>
>>> On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com>
>>> wrote:
>>> I'm concerned about TCP-over-X.25 scenarios.
>>
>> ... and how many b/s of that exist in the universe!
>
> Stewart: none that I know of, of course, but it was in production at a
> significant time in Internet history and was one of our first experiences
> with multiple layers each trying to provide transport control and thereby
> destroying goodput. I'll never forget it. When I think of two layers each
> trying to do congestion management,  with no way to coordinate with each
> other, that's the first example that comes to mind.
>
> Scott

From stbryant@cisco.com  Tue Jan 14 06:20:50 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6481AE077; Tue, 14 Jan 2014 06:20:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26nHzKMCFeqz; Tue, 14 Jan 2014 06:20:48 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 509C11ADF76; Tue, 14 Jan 2014 06:20:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2209; q=dns/txt; s=iport; t=1389709237; x=1390918837; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=YfXKPYRmwa5C/SxBI42KrVL1fSEBROnNPAWLSGBzDSg=; b=K9FwSFl2rYx9UNldm1n4+1TgdgxVSUuY1T8GfP0NVPlUm6I1yNgFxyA8 ++OcBv80itD9RO9LC2gxDXDzlvSSJuEZqTZISsM4+xcLEvFd79mBD3EFz ChmPg5zj6p2TqIBnaKntmyyQfRyfrX7tDxPUfdyHAngWkOCQ/bDvRNUvt Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAEtH1VKQ/khR/2dsb2JhbABagws4uyyBEhZ0giUBAQEEOEABEAsYCRYECwkDAgECAQ82Bg0BBQIBAYdsAxENvmoNhR0XjHSCEweENwSWMoFsjFqFO4FvgT4
X-IronPort-AV: E=Sophos;i="4.95,658,1384300800";  d="scan'208";a="3612131"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 14:20:36 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0EEKaKO029154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 14:20:36 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0EEKY8s019773; Tue, 14 Jan 2014 14:20:34 GMT
Message-ID: <52D547B2.1060302@cisco.com>
Date: Tue, 14 Jan 2014 14:20:34 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com>
In-Reply-To: <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 14:20:50 -0000

Yes, the inner (real) transport header is the only meaningful place
to apply congestion avoidance.

Stewart

On 14/01/2014 13:52, Scott Brim wrote:
> Now that I'm at a real keyboard, and since at least one person didn't
> get what I was trying to say with my reference, let me try to explain
> more clearly.
>
> Transport is pretty arcane. We sometimes get it more or less right
> when we're dealing with a single instance of it in endpoints and
> routers/switches. In this case, if we add congestion management to the
> encapsulating UDP, we have two possible instances of the same function
> stacked on top of each other, where each has no way of knowing whether
> the other exists, if so what it's doing, or if there's any way to
> communicate with it. We have examples in the past where we have got
> this badly wrong. IMHO this is more likely to be a problem than not.
>
> The best architectural answer I can think of in this case is the one
> with the least surprises built in: treat the lower level UDP as just
> an encapsulation, not an intelligent transport protocol. Yes there
> should be scope for congestion management but that is higher up, where
> the endpoints come in to play.
>
> Scott
>
> On Tue, Jan 14, 2014 at 8:11 AM, Scott Brim <scott.brim@gmail.com> wrote:
>> On Jan 14, 2014 6:00 AM, "Stewart Bryant" <stbryant@cisco.com> wrote:
>>> On 13/01/2014 19:09, Scott Brim wrote:
>>>> On Mon, Jan 13, 2014 at 10:51 AM, Joel M. Halpern <jmh@joelhalpern.com>
>>>> wrote:
>>>> I'm concerned about TCP-over-X.25 scenarios.
>>> ... and how many b/s of that exist in the universe!
>> Stewart: none that I know of, of course, but it was in production at a
>> significant time in Internet history and was one of our first experiences
>> with multiple layers each trying to provide transport control and thereby
>> destroying goodput. I'll never forget it. When I think of two layers each
>> trying to do congestion management,  with no way to coordinate with each
>> other, that's the first example that comes to mind.
>>
>> Scott
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From lars@netapp.com  Tue Jan 14 07:20:35 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F9D91AE026; Tue, 14 Jan 2014 07:20:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.44
X-Spam-Level: 
X-Spam-Status: No, score=-7.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rFw3jrPCtiB8; Tue, 14 Jan 2014 07:20:31 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id E85B21ADFB6; Tue, 14 Jan 2014 07:20:30 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,658,1384329600";  d="asc'?scan'208";a="136895002"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 14 Jan 2014 07:20:18 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Tue, 14 Jan 2014 07:20:18 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAHXQgIAAN0wAgAEJtoCAACSXAIAAC26AgAAH1ACAABCuAA==
Date: Tue, 14 Jan 2014 15:20:17 +0000
Message-ID: <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com>
In-Reply-To: <52D547B2.1060302@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_13952AFE-BD28-4845-B407-D230F9474A8E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 15:20:35 -0000

--Apple-Mail=_13952AFE-BD28-4845-B407-D230F9474A8E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1

On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
> Yes, the inner (real) transport header is the only meaningful place
> to apply congestion avoidance.

But what if the inner traffic isn't congestion controlled?

Lars

--Apple-Mail=_13952AFE-BD28-4845-B407-D230F9474A8E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtVVsdZcnpRveo1xAQJ1VAQAhxkwT+JiRKtboCUq5m++eRzf2BWOY+EM
EKCyI4ec05hvp4GAfHLZbbhyphMTCEN0WjFkToXQx4Tr8/a4VF85s8ct9QZvXcNd
ZnFPFW09w4jrMrgkabZN2KRvhNoyMGcRaTIjputkE4bOaeM6ivikUnD/CFDcfmwn
dHedORaWP8Q=
=HC0h
-----END PGP SIGNATURE-----

--Apple-Mail=_13952AFE-BD28-4845-B407-D230F9474A8E--

From jmh@joelhalpern.com  Tue Jan 14 07:24:29 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBEEB1ADFB6; Tue, 14 Jan 2014 07:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pr7SUocXc_io; Tue, 14 Jan 2014 07:24:26 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id A08111ADFAA; Tue, 14 Jan 2014 07:24:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 9EE901BD695C; Tue, 14 Jan 2014 07:24:15 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 4824E1BD6957; Tue, 14 Jan 2014 07:24:07 -0800 (PST)
Message-ID: <52D5568F.2070600@joelhalpern.com>
Date: Tue, 14 Jan 2014 10:23:59 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Stewart Bryant <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
In-Reply-To: <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 15:24:29 -0000

Isn't that basically the problem of the inner traffic sender, not the 
problem of the tunnel that is carrying the traffic?
Asking tunnel's to solve the problem of applications with undesirable 
behavior seems backwards.

Yours,
Joel

On 1/14/14 10:20 AM, Eggert, Lars wrote:
> On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
>> Yes, the inner (real) transport header is the only meaningful place
>> to apply congestion avoidance.
>
> But what if the inner traffic isn't congestion controlled?
>
> Lars
>

From lars@netapp.com  Tue Jan 14 07:29:52 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8C861AE0FB; Tue, 14 Jan 2014 07:29:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ftKSLCV8Zdhz; Tue, 14 Jan 2014 07:29:51 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A2B001AE0FA; Tue, 14 Jan 2014 07:29:50 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,658,1384329600";  d="asc'?scan'208";a="95978130"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 14 Jan 2014 07:29:39 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Tue, 14 Jan 2014 07:29:39 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Joel Halpern <jmh@joelhalpern.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAHXQgIAAN0wAgAEJtoCAACSXAIAAC26AgAAH1ACAABCuAIAAAQqAgAABkYA=
Date: Tue, 14 Jan 2014 15:29:38 +0000
Message-ID: <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com>
In-Reply-To: <52D5568F.2070600@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_366B3B18-1301-40E5-9069-EBD52038CD8A"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 15:29:52 -0000

--Apple-Mail=_366B3B18-1301-40E5-9069-EBD52038CD8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> Isn't that basically the problem of the inner traffic sender, not the =
problem of the tunnel that is carrying the traffic?

no, because the sender of the inner traffic may be blasting some L2 =
traffic, for an L2 where that is OK behavior. But that traffic is now =
being encapsulated inside UDP and can hence go anywhere on the net =
*without the sender being aware of this*.

> Asking tunnel's to solve the problem of applications with undesirable =
behavior seems backwards.

It is the *tunnel* that performs the encapsulation and allows that =
traffic to go places it couldn't before. And so it's the tunnel's =
responsibility to make sure that the traffic it injects into the =
Internet complies with the BCPs we have on congestion control.

Lars

--Apple-Mail=_366B3B18-1301-40E5-9069-EBD52038CD8A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtVX39ZcnpRveo1xAQJ0AgP/RUgABtrQKRfecW3gluWKiGeCCbPpbZN6
XnNk5HxFonwIqbBIks+LzLPUHdMs2cu2R6pgz+WBGjduBBto4acZQK9+kDaW5PCl
MtbLJPa26wtsKpQSudhghuM47F1RFTYFHZyOblAdMdeSQDzXa8AyLEfgIWvZYIXZ
wpf9ze0B3H8=
=z2Zb
-----END PGP SIGNATURE-----

--Apple-Mail=_366B3B18-1301-40E5-9069-EBD52038CD8A--

From scott.brim@gmail.com  Tue Jan 14 07:39:33 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E9D1AE026; Tue, 14 Jan 2014 07:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nO0StmABkHKl; Tue, 14 Jan 2014 07:39:31 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id A52BC1ADFC5; Tue, 14 Jan 2014 07:39:31 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id n16so9761708oag.36 for <multiple recipients>; Tue, 14 Jan 2014 07:39:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=qza43Jy0Kiz69LNr/wTvPX9ZiBCdI2k4nu0yFLoO+7c=; b=reN7efgFpOY2LmygEizwd6izGQaZr/MU7sTF3pgS0SYDPi1xsMzapPATcjitVD6ovX ZMyWL9DXKQzbvUqOuJp4jTW1YmThpQm4l7z7QhJcArR/6b4+tzQKN337ZrCB984+UG+L BuUeijx9NObcbAm2TnzBcPIHjQKHUaO9ndzny4KKzBunnZTirzBpa0F7gFn2CFwZoewz AfHqCne/wMTpNKHDSMLXMAsiS+A2vHP/pFOATYezkCxzvRMFo2IQEbvTaZMmfs7jX+Cc nUNUHJExeKkMYf1X0W+Y9TmdG/JRgBuq65+YXq6j315A2i1QNI1q09SomD9VnjeX6y3w DNSA==
X-Received: by 10.182.42.105 with SMTP id n9mr1564979obl.33.1389713960209; Tue, 14 Jan 2014 07:39:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 07:39:00 -0800 (PST)
In-Reply-To: <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 10:39:00 -0500
Message-ID: <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 15:39:33 -0000

Lars, I know we're repeating arguments from the last decade. The
choice is between (1) specifying congestion control around the
substrate UDP that can be turned off if it causes problems, or (2)
specifying nothing at this time and adding it later if operators want
it.

I guess if this can be written as a SHOULD, up to the implementor's
discretion, then okay.

Scott

On Tue, Jan 14, 2014 at 10:29 AM, Eggert, Lars <lars@netapp.com> wrote:
> Hi,
>
> On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>> Isn't that basically the problem of the inner traffic sender, not the pr=
oblem of the tunnel that is carrying the traffic?
>
> no, because the sender of the inner traffic may be blasting some L2 traff=
ic, for an L2 where that is OK behavior. But that traffic is now being enca=
psulated inside UDP and can hence go anywhere on the net *without the sende=
r being aware of this*.
>
>> Asking tunnel's to solve the problem of applications with undesirable be=
havior seems backwards.
>
> It is the *tunnel* that performs the encapsulation and allows that traffi=
c to go places it couldn't before. And so it's the tunnel's responsibility =
to make sure that the traffic it injects into the Internet complies with th=
e BCPs we have on congestion control.
>
> Lars

From jmh@joelhalpern.com  Tue Jan 14 07:49:05 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE0D61AE09C; Tue, 14 Jan 2014 07:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rnCSlRHlw0Z; Tue, 14 Jan 2014 07:49:03 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id AC34E1ADF7F; Tue, 14 Jan 2014 07:49:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 606CB1BD707C; Tue, 14 Jan 2014 07:48:52 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 1F6B81BD7056; Tue, 14 Jan 2014 07:48:47 -0800 (PST)
Message-ID: <52D55C5C.80001@joelhalpern.com>
Date: Tue, 14 Jan 2014 10:48:44 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
In-Reply-To: <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 15:49:06 -0000

So a customer buys an Ethernet service from an operator.  And it is 
delivered via MPLS.  Possibly across some other operators (Internet as a 
Service.)
If it is tunneled in IP, or GRE (with or without MPLS), then that is fine.
But if I add a UDP header I must suddenly add congestion control at the 
point I add the UDP header?

I can understand (disagree with, but understand) Llyod's argument that 
the UDP header may reach a host, so the checksum might be an issue.  I 
think taht is dealt with by the fact that the host will drop packets 
with 0 UDP checksums.  But I understand the increased reach concern there.

For congestion control?  Adding an in-network control loop?  When the 
UDP encapsulator may not even know what the service is being used for? 
And so is probably more likely to apply an inner congestion control to a 
TCP stream running over IP over Ethernet over MPLS over UDP as to some 
unconstrained flow?

Yours,
Joel

On 1/14/14 10:29 AM, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>> Isn't that basically the problem of the inner traffic sender, not the problem of the tunnel that is carrying the traffic?
>
> no, because the sender of the inner traffic may be blasting some L2 traffic, for an L2 where that is OK behavior. But that traffic is now being encapsulated inside UDP and can hence go anywhere on the net *without the sender being aware of this*.
>
>> Asking tunnel's to solve the problem of applications with undesirable behavior seems backwards.
>
> It is the *tunnel* that performs the encapsulation and allows that traffic to go places it couldn't before. And so it's the tunnel's responsibility to make sure that the traffic it injects into the Internet complies with the BCPs we have on congestion control.
>
> Lars
>

From lars@netapp.com  Tue Jan 14 08:06:37 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C49C71AE110; Tue, 14 Jan 2014 08:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.44
X-Spam-Level: 
X-Spam-Status: No, score=-7.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xvQ2TnPvHlji; Tue, 14 Jan 2014 08:06:35 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id E1F7E1AE0DC; Tue, 14 Jan 2014 08:06:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,658,1384329600";  d="asc'?scan'208";a="136906970"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx12-out.netapp.com with ESMTP; 14 Jan 2014 08:06:24 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Tue, 14 Jan 2014 08:06:23 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAHXQgIAAN0wAgAEJtoCAACSXAIAAC26AgAAH1ACAABCuAIAAAQqAgAABkYCAAAKhAIAAB6KA
Date: Tue, 14 Jan 2014 16:06:21 +0000
Message-ID: <C54B4791-A023-4512-84C6-50869BBE9B66@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_5882EB94-8DA2-4AB3-A5E8-C5B083388DB5"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:06:38 -0000

--Apple-Mail=_5882EB94-8DA2-4AB3-A5E8-C5B083388DB5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-1-14, at 16:39, Scott Brim <scott.brim@gmail.com> wrote:
> Lars, I know we're repeating arguments from the last decade. The
> choice is between (1) specifying congestion control around the
> substrate UDP that can be turned off if it causes problems, or (2)
> specifying nothing at this time and adding it later if operators want
> it.
>=20
> I guess if this can be written as a SHOULD, up to the implementor's
> discretion, then okay.

I don't think we can leave this up to implementors discretion. We've had =
IETF consensus that Internet communication requires congestion control =
at least since RFC2914. A circuit breaker mechanisms seems =
straightforward to implement.

As is, I object to this document going forward. The minor benefits of =
getting some better load balancing for MPLS are far outweighed by the =
risks.

(I'm also going to shut up now, and let others speak. I think I've said =
my bit.)

Lars

--Apple-Mail=_5882EB94-8DA2-4AB3-A5E8-C5B083388DB5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtVge9ZcnpRveo1xAQKNnQP9H2LA07dypoVIEYhTCAqM4K2FsYc57jt5
qLo6yyLub6Gy9Uc2/3GgcTKWynfhlOSXGeu1dLAVN2o2ha41gjDRzYiKn9G6lsEI
TAfzpLg7Wl0eSCJu0MmB2gommG/YfShWX5hSkmFx+T2q5aqd7NHb8WHagyChQb+A
d+nUXryn4+o=
=APg3
-----END PGP SIGNATURE-----

--Apple-Mail=_5882EB94-8DA2-4AB3-A5E8-C5B083388DB5--

From Alexander.Vainshtein@ecitele.com  Tue Jan 14 08:00:27 2014
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF841AE017; Tue, 14 Jan 2014 08:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pO1Kzly_Sx9l; Tue, 14 Jan 2014 08:00:24 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0015.outbound.protection.outlook.com [213.199.154.15]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAD81AE101; Tue, 14 Jan 2014 08:00:23 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB530.eurprd03.prod.outlook.com (10.242.109.154) with Microsoft SMTP Server (TLS) id 15.0.851.11; Tue, 14 Jan 2014 16:00:10 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Tue, 14 Jan 2014 16:00:09 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: Scott Brim <scott.brim@gmail.com>, "Eggert, Lars" <lars@netapp.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPEBE8NB1HxYhr0E+Bh7qVSMaw6pqCWMcAgAB1zoCAADdMAIABCbaAgAAklwCAAAtugIAAB9QAgAAQr4CAAAEJgIAAAZQAgAACngCAAAKz0A==
Date: Tue, 14 Jan 2014 16:00:09 +0000
Message-ID: <fb5a586214884523916e710c5096592e@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 0091C8F1EB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(689001)(679001)(779001)(252514010)(377454003)(24454002)(51704005)(13464003)(377424004)(189002)(199002)(85852003)(80022001)(65816001)(81686001)(74366001)(47446002)(49866001)(51856001)(54316002)(33646001)(53806001)(79102001)(46102001)(87936001)(2656002)(47976001)(74316001)(56776001)(31966008)(76482001)(76796001)(54356001)(63696002)(69226001)(74662001)(81342001)(19580395003)(85306002)(87266001)(74502001)(80976001)(83072002)(19580405001)(83322001)(74706001)(81816001)(74876001)(50986001)(4396001)(59766001)(47736001)(66066001)(76576001)(77982001)(81542001)(76786001)(56816005)(92566001)(15975445006)(90146001)(93136001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB530; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:147.234.56.21; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:12:36 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:00:27 -0000

Lars, Scott and all,
IMHO and FWIW the problem is not between congestion control requirements be=
ing specified as SHOULD or MUST.
Specifying some functionality as SHOULD without describing (even in a non-n=
ormative way) how this functionality could be implemented because the proto=
col specified does not provide any hooks for it is indeed meaningless.
This is the way to guarantee that this functionality will never be implemen=
ted even if we discover that in some cases it is needed.

In the case of congestion control the minimal required hooks are:

1. Ability to detect congestion at the tail-end of the tunnel
2. Ability to pass this information to the head-end of the tunnel.

To the best of my understanding, proposed protocol does not provide any of =
these hooks. Hence specifying any requirements for congestion control does =
not make any sense to me regardless of the level of these requirements (MUS=
T, SHOULD or MAY) - these requirements cannot be implemented without some r=
edesign of the protocol.

I would also like to note that the declared purpose of the protocol is simp=
lification of ECMP. One of the reasons to use ECMP is that the "fat" flow c=
annot get the required BW on any specific link...=20

Regards,
       Sasha=20
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Scott Brim
> Sent: Tuesday, January 14, 2014 5:39 PM
> To: Eggert, Lars
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> Lars, I know we're repeating arguments from the last decade. The choice i=
s
> between (1) specifying congestion control around the substrate UDP that c=
an
> be turned off if it causes problems, or (2) specifying nothing at this ti=
me and
> adding it later if operators want it.
>=20
> I guess if this can be written as a SHOULD, up to the implementor's
> discretion, then okay.
>=20
> Scott
>=20
> On Tue, Jan 14, 2014 at 10:29 AM, Eggert, Lars <lars@netapp.com> wrote:
> > Hi,
> >
> > On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> >> Isn't that basically the problem of the inner traffic sender, not the
> problem of the tunnel that is carrying the traffic?
> >
> > no, because the sender of the inner traffic may be blasting some L2 tra=
ffic,
> for an L2 where that is OK behavior. But that traffic is now being
> encapsulated inside UDP and can hence go anywhere on the net *without
> the sender being aware of this*.
> >
> >> Asking tunnel's to solve the problem of applications with undesirable
> behavior seems backwards.
> >
> > It is the *tunnel* that performs the encapsulation and allows that traf=
fic to
> go places it couldn't before. And so it's the tunnel's responsibility to =
make
> sure that the traffic it injects into the Internet complies with the BCPs=
 we
> have on congestion control.
> >
> > Lars
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From Alexander.Vainshtein@ecitele.com  Tue Jan 14 08:05:39 2014
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A07F1AE0FC; Tue, 14 Jan 2014 08:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AgibuoPPVc-q; Tue, 14 Jan 2014 08:05:37 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0012.outbound.protection.outlook.com [213.199.154.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3BAB61AE0DC; Tue, 14 Jan 2014 08:05:35 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB531.eurprd03.prod.outlook.com (10.242.109.155) with Microsoft SMTP Server (TLS) id 15.0.851.11; Tue, 14 Jan 2014 16:05:22 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Tue, 14 Jan 2014 16:05:22 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPEBE8NB1HxYhr0E+Bh7qVSMaw6pqCWMcAgAB1zoCAADdMAIABCbaAgAAklwCAAAtugIAAB9QAgAAQr4CAAAEJgIAAAZQAgAAFVgCAAANwMA==
Date: Tue, 14 Jan 2014 16:05:21 +0000
Message-ID: <5b1067567abb40dca321c071a751d552@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D55C5C.80001@joelhalpern.com>
In-Reply-To: <52D55C5C.80001@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 0091C8F1EB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(689001)(679001)(779001)(377424004)(13464003)(51704005)(189002)(199002)(479174003)(377454003)(24454002)(252514010)(54356001)(53806001)(79102001)(49866001)(76796001)(54316002)(76786001)(50986001)(46102001)(63696002)(47976001)(65816001)(51856001)(83322001)(80976001)(19580395003)(47736001)(19580405001)(33646001)(93136001)(81816001)(56776001)(59766001)(92566001)(77982001)(76482001)(76576001)(74876001)(87936001)(31966008)(81686001)(4396001)(80022001)(81342001)(87266001)(85306002)(66066001)(69226001)(74662001)(2656002)(56816005)(15975445006)(83072002)(81542001)(90146001)(47446002)(74706001)(74366001)(74502001)(74316001)(85852003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB531; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:147.234.56.21; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:12:51 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:05:39 -0000

Joel,
You have said (and I fully agree with you) that the UDP encapsulator does n=
ot even know (in some cases) what the service is for.
If this is the case, how will the UDP encapsulator assign entropy source UD=
P ports to specific MPLS packets it encapsulates without breaking reorderin=
g-sensitive micro-flows within this service?

Regards,
       Sasha=20
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302


> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Joel M. Halpern
> Sent: Tuesday, January 14, 2014 5:49 PM
> To: Eggert, Lars
> Cc: mpls@ietf.org; Scott Brim; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> So a customer buys an Ethernet service from an operator.  And it is deliv=
ered
> via MPLS.  Possibly across some other operators (Internet as a
> Service.)
> If it is tunneled in IP, or GRE (with or without MPLS), then that is fine=
.
> But if I add a UDP header I must suddenly add congestion control at the p=
oint
> I add the UDP header?
>=20
> I can understand (disagree with, but understand) Llyod's argument that th=
e
> UDP header may reach a host, so the checksum might be an issue.  I think
> taht is dealt with by the fact that the host will drop packets with 0 UDP
> checksums.  But I understand the increased reach concern there.
>=20
> For congestion control?  Adding an in-network control loop?  When the UDP
> encapsulator may not even know what the service is being used for?
> And so is probably more likely to apply an inner congestion control to a =
TCP
> stream running over IP over Ethernet over MPLS over UDP as to some
> unconstrained flow?
>=20
> Yours,
> Joel
>=20
> On 1/14/14 10:29 AM, Eggert, Lars wrote:
> > Hi,
> >
> > On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> >> Isn't that basically the problem of the inner traffic sender, not the
> problem of the tunnel that is carrying the traffic?
> >
> > no, because the sender of the inner traffic may be blasting some L2 tra=
ffic,
> for an L2 where that is OK behavior. But that traffic is now being
> encapsulated inside UDP and can hence go anywhere on the net *without
> the sender being aware of this*.
> >
> >> Asking tunnel's to solve the problem of applications with undesirable
> behavior seems backwards.
> >
> > It is the *tunnel* that performs the encapsulation and allows that traf=
fic to
> go places it couldn't before. And so it's the tunnel's responsibility to =
make
> sure that the traffic it injects into the Internet complies with the BCPs=
 we
> have on congestion control.
> >
> > Lars
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From gorry@erg.abdn.ac.uk  Mon Jan 13 12:32:00 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0031AE000; Mon, 13 Jan 2014 12:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DqlW6hSFAr4Q; Mon, 13 Jan 2014 12:31:56 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB0B1AE1A0; Mon, 13 Jan 2014 12:31:56 -0800 (PST)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 8F1972B41C8; Mon, 13 Jan 2014 20:31:43 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Mon, 13 Jan 2014 20:31:43 -0000
Message-ID: <d1a533cd99f57d03c357cfbd21625856.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201401131911.s0DJBC1o079251@maildrop2.v6ds.occnc.com>
References: <201401131911.s0DJBC1o079251@maildrop2.v6ds.occnc.com>
Date: Mon, 13 Jan 2014 20:31:43 -0000
Subject: Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
From: gorry@erg.abdn.ac.uk
To: curtis@ipv6.occnc.com
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:13:12 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, farinacci@gmail.com, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jan 2014 20:32:00 -0000

>
> One of the reasons that IPv6 (rfc2460) dropped the header checksum
> that was in IPv4 is that with link layers all doing FCS it served no
> purpose.
>  For the same reason TCP and UDP checksums server no purpose.
>
That's not what I understood, it is needed for endpoint delivery
verification. But in this case, TCP & UDP checksums incorporate the IP
address info in the pseudo header, and this was thought sufficient.

> The link layer checksum fails and the packet is dropped.  Since this
> is usually not at the last hop (often a local Ethernet) but instead in
> a WAN link, the packet never arrives at the destination for anything
> to count IP header or TCP or UDP checksum errors.
>
Again, that presumes that everything above the link works flawlessly,
which isn't always the case.

> Also all of the following handle both data integrity and congestion
> avoidance the same way:
>
>   UDP over IP over Ethernet
>   UDP over IP over MPLS over Ethernet
>   UDP over IP over MPLS over UDP over IP over Ethernet
>   s/Ethernet/{POS,GFP,etc}/ for all of the above
>   s/^UDP over IP/PW/ for all of the above
>
> In all of the above cases data integrity is handled by the link layer.
> In all of the above cases congestion avoidance is handled by the
> application (or not at all).  Whether MPLS is carried directly over a
> link layer or over UDP/IP over a link layer makes no difference.
>
RFC 6936 section 3.1 says more about what happens when packets happen to
be mis-delivered to the wrong host or socket.

> Curtis
>

Gorry

> In message
> <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>
>> Really, you'd want to expose the pseudoheader check at endhosts; a
>> well-instrumented Linux box could tell you a lot
>> about checksum failures.
>>
>> But in this case, a router would be decapping UDP/MPLS tunnels as an
>> endpoint, so could report on checksum failures -
>> if the checksum wasn't zero.
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: Dino Farinacci [farinacci@gmail.com]
>> Sent: 12 January 2014 21:37
>> To: Wood L  Dr (Electronic Eng)
>> Cc: <mark.tinka@seacom.mu>; <mpls@ietf.org>; gorry@erg.abdn.ac.uk;
>> lisp@ietf.org; david.black@emc.com; randy@psg.com; tsvwg@ietf.org;
>> jnc@mit.edu; ietf@ietf.org
>> Subject: Re: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp
>> draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>>
>> > Do any routers count TCP/UDP checksum failures, much less
>> > expose the count via SNMP?
>>
>> Typically they do but only for packets destined to them. Much like hosts
>> would check the header checksum.
>>
>> Dino
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>



From mark.tinka@seacom.mu  Tue Jan 14 08:10:33 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EED6D1AE125; Tue, 14 Jan 2014 08:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.989
X-Spam-Level: 
X-Spam-Status: No, score=-0.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_82=0.6] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VqBBn0Qgq4sF; Tue, 14 Jan 2014 08:10:28 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-jnb.za.seacomnet.com [41.87.104.245]) by ietfa.amsl.com (Postfix) with ESMTP id A97D51AE10D; Tue, 14 Jan 2014 08:10:25 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W36Ye-0001n8-K5; Tue, 14 Jan 2014 18:09:40 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: curtis@ipv6.occnc.com
Subject: Re: OT was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
Date: Tue, 14 Jan 2014 18:09:36 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <201401141550.s0EFojHp098066@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401141550.s0EFojHp098066@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2936459.czVGkbzpV0"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401141809.40038.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:13:33 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:10:33 -0000

--nextPart2936459.czVGkbzpV0
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Tuesday, January 14, 2014 05:50:45 PM Curtis Villamizar=20
wrote:

> None of the equipment I have worked on (a while back) or
> the chips we evaluated recently had such a problem for
> IPv6 using only the top 64 bits for forwarding.  An
> argument was made in the early 2000s (by me and others)
> that if we allocated global routes only from the top 64
> bits all equipment at that time could forward at
> essentially the same rate as for IPv4.  The reaction
> from the IPv6 community was to completely throw away the
> bottom half of the address and make it the host part.

Agree.

> There are chips for which looking at a 32 bit prefix or a
> 64 bit prefix is done within the same pipeline and
> therefore takes the same amount of time.  Other chips
> which parallelize packet handling budget enough
> microengines to get the job done (only a part of which
> is the MPLS ILM or IP destination lookup).

Agree.

> Those line cards (and designs I was recently involved in)
> assume what has historically been called a BGP-free
> core.  Only the IGP routes are carried in the core.  BGP
> is mapped onto the IGP routes.  MPLS carries traffic
> across the core.  The core has no BGP routes and
> therefore needs a lot fewer entries and the ILM can be
> put into SRAM rather than use a TCAM and only a small
> set of IP routes needs to be supported.

Yes, but a "proper" BGP-free core is only true for IPv4.

If you are running a native IPv6 backbone, you can't support=20
a BGP-free core for IPv6 (I'll just call it a BGPv6-free=20
core, for typing brevity).

The only way you can have a BGPv6-free core is to do 6PE,=20
and like I mentioned before, I don't like tunneled IPv6 (but=20
lots of other providers do it, good for them).

> That is done to eliminate a need for large external DRAM
> or TCAM which itself and the SERDES needed to go off
> chip produces heat and requires power, board space, and
> cooling and therefore reduces density. Putting more
> simple filters in the core also helps increase density.
> It is more a power to operate and floor space per Gb/s
> issue.

All good and well, but where do my native BGPv6 routes go?

> For the most part IP/MPLS transport equipment seems to be
> going this way, though some people are stuck on MPLS-TP
> and trying to build a L2 overlay.

I think MPLS-TP is a way for the incumbents to migrate to=20
Ethernet and still keep their ITU point-to-point-everything=20
way of life that they know and love, but let's not digress=20
:-)...

C have had the LSP forwarding engine for about three years=20
now. I've never once considered buying it (and I always=20
support new tech.), and most of my friends that I know=20
closely haven't either. I have no doubt that some operators=20
have bought it, but I have no empirical data to know how=20
quickly it's flying off the shelves.

J's PTX and C's new NCS will continue this trend, but=20
without implementing IPv6 control planes for MPLS (and the=20
requisite data plane support), those of us that run native=20
IPv6 will never have a BGPv6-free core.

So I can only afford line cards and forwarding engines that=20
don't skimp on FIB, so I can sleep at night knowing my IPv6=20
network won't fall over.

> If you go back to before 2000 at least one provider built
> a BGP-free core over Frame Relay, but FR itself soon
> died and the overlay didn't scale well.  Some providers
> wanted to do this over MPLS but the RSVP-TE restoration
> times were too long and the fallback to IP routing was
> still needed to make up for that.

Was before my time, but I can appreciate that :-).

> Unless you run a BGP-free core, whether IPv4 or IPv6.=20
> Then you have plenty of FIB space.

Again, without 6PE, no-can-do for BGPv6.

> You put forwarding at full rate and cheaper line cards in
> the same paragraph with no mention of smaller FIB size
> due to eliminating the BGP routes.

Because without FIB's, where will the native BGPv6 routes=20
go?

> OK ... so this is all interesting but I've lost the
> connection between this discussion and
> draft-ietf-mpls-in-udp.  Hence the OT in the subject.=20
> Would you please remind me what that connection was.

I agree, this is quickly getting off topic, but the source=20
was:

*****

On Sunday, January 12, 2014 04:59:41 AM l.wood@surrey.ac.uk=20
wrote:

> The MPLS assumption is that it's protected and checked by
> a strong link CRC like Ethernet, and checked/regenerated
> by stack processing between hops; here, in a path
> context, with zero UDP checksums MPLS has no checking at
> all.

Right, which is probably why routers today can count badly=20
checksum'ed Ethernet frames, but don't have the equivalent=20
for MPLS.

> I'm sorry, when was MPLS cheap?

Current-generation ASIC's have no problem forwarding MPLS=20
frames at wire rate. One could go so far as to say that MPLS=20
has allowed vendors to make cheaper line cards also because=20
IP FIB's and traffic queues can be scaled down dramatically=20
(not that I'd every buy such line cards, but...).

Mark.

*****

Cheers,

Mark.

--nextPart2936459.czVGkbzpV0
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS1WFDAAoJEGcZuYTeKm+G12UP/0I3a8sOQVTRN8GjYlxB/IgO
qaxNAchFW+dmsGEMWa5WC2V3LRsmBpUQwREBm8E6ADbULv2CdP7ixqnIVgSirESR
6JSX0MkRsiqW34VaOEa7u77c4+6iIuMS/O7lskPiKYjBZdjg3up2Xd5xlDUe+1OH
8N0MDRooTem/2HI3BFxeFD6Y5ulVNVTVahAA/Qj4juSR9OicRjWTAiBiWBowNxyP
sasLrnjZZHtD5rBYPSzGlEwaOcx3kfBaop2KBETIfPWNtJyRwkdA01Ad7O9M27kv
0lzt/EJESlL0wueAlKP6kjhNPMm6C8ZlVwPW6LiU+C24BWrP0e2tdLTAN0mSzqVy
ChLQERyaO0m1qOHRa+VZ1zZv/GwzRNjU4nEZqKsVaqhOSKpYT6/fI+fKGA8aRjGS
hChWOmui0lI/4WsJ9otSNxq+/3TCXcP3ySVHNifik1a+6mU24GGkiWJpAGP1/CPT
javmyEYsSRa7OGoSw34W9+SLhDBh99960fLhWaLIo3LMhEss48NZQJK7ybALh2DE
wzItalLP6MSJhGVhKU16hSWZsCys7kGh7f16g3EbLwH27MzXIa1eDsIQmOCSyWd1
j7NXyEzOHUHrp18tFlbGeOwYGE9iFPXzLFIEedGFYoLMozpJ/gz1zHpmTgxFoJaR
v6AhFuv/Q8w8gax0TQjA
=uf6R
-----END PGP SIGNATURE-----

--nextPart2936459.czVGkbzpV0--

From stbryant@cisco.com  Tue Jan 14 06:18:04 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB721ADFB6; Tue, 14 Jan 2014 06:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ua1uMtRFCfyR; Tue, 14 Jan 2014 06:18:02 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 94CBA1AE0CC; Tue, 14 Jan 2014 06:18:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1432; q=dns/txt; s=iport; t=1389709071; x=1390918671; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xplMTCVHK+awtKhL4j4qiFjX/qRtqYJJ+mcb0t8TCPQ=; b=MuL0HLKsGkW5uirCYPkznboY49qOHPXgW1qQEDK9jvECFkZim4P5dFQj gYywe5wX3lfnKFI3dNFamUDHbJVbDZhWgxMvrEYJqm/AxRzXdIMbZ45kw qgFso1FA2vyhLudcRmcx+rG63QMVHt7/jE5OTI6tBoaMTFmxkuBSDuwgP s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FACVG1VKQ/khL/2dsb2JhbABaDoJ9uFeDDoESFnSCJgEBBDhAARALIRYECwkDAgECAUUHDAEHAQGIAMQrF48HB4Q3AQOYHpIVgW9/Pw
X-IronPort-AV: E=Sophos;i="4.95,658,1384300800";  d="scan'208";a="3611960"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 14:17:49 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0EEHnZI012590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 14:17:49 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0EEHkTl019554; Tue, 14 Jan 2014 14:17:47 GMT
Message-ID: <52D5470A.9020002@cisco.com>
Date: Tue, 14 Jan 2014 14:17:46 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, curtis@ipv6.occnc.com
Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
References: Your message of "Sun, 12 Jan 2014 02:59:41 +0000." <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>, <201401121809.s0CI91Y1053969@maildrop2.v6ds.occnc.com> <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:15:15 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, david.black@emc.com, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 14:18:04 -0000

Lloyd

I have just read the Stone paper and I have some significant
concerns about its validity with modern h/w. Certainly it
is hard to credit the notion that the  error rate
is in the range 1:1000 to 1:32000 as reported by the authors.

The paper was written in 2000 with hardware that would have
have been designed in the mid 1990s. In that era, h/w was
far more marginal, with performance traded against signal
integrity, and indeed a lot less signal integrity measurement
and simulation took place at both board and chip level. This
was also the era where metastability was just beginning to
become widely understood, and its lack of understanding
would be a possible source of DMA errors.

I therefore do not think we should place much reliance
on this paper, but should instead look at the rather more
modern statistics.

Such statistics ought to be readily available by looking at
the tcp/udp c/s error stats in hosts and routers. As a tiny
and perhaps erroneous sample I looked at three Macs
in the office here and the tcp c/s error stats were
313/29144518, 0/3000000, 0/5000000. Only one of those
three systems got within a factor of 3 of the lowest error
rate reported by Stone.

Bottom line, it seems that we could use more recent data
and then an understanding of how important these low
background error rates are in the tunneling application that
we are considering here.

- Stewart











From wes@mti-systems.com  Tue Jan 14 08:22:31 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6622B1AE118 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 08:22:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxIl5-k63uBD for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 08:22:29 -0800 (PST)
Received: from atl4mhob08.myregisteredsite.com (atl4mhob08.myregisteredsite.com [209.17.115.46]) by ietfa.amsl.com (Postfix) with ESMTP id A65B51AE10D for <ietf@ietf.org>; Tue, 14 Jan 2014 08:22:23 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob08.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s0EGMATc004368 for <ietf@ietf.org>; Tue, 14 Jan 2014 11:22:10 -0500
Received: (qmail 17092 invoked by uid 0); 14 Jan 2014 16:22:10 -0000
X-TCPREMOTEIP: 107.48.137.115
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.48.137.115) by 0 with ESMTPA; 14 Jan 2014 16:22:10 -0000
Message-ID: <52D5642A.7090103@mti-systems.com>
Date: Tue, 14 Jan 2014 11:22:02 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <CAPv4CP_3DmjZQN=LQmV53-8HsZDHukpdu0Lyuh9KwOgXQ-v=EQ@mail.gmail.com> <C54B4791-A023-4512-84C6-50869BBE9B66@netapp.com>
In-Reply-To: <C54B4791-A023-4512-84C6-50869BBE9B66@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 16:22:31 -0000

On 1/14/2014 11:06 AM, Eggert, Lars wrote:
> Hi,
> 
> On 2014-1-14, at 16:39, Scott Brim <scott.brim@gmail.com> wrote:
>> Lars, I know we're repeating arguments from the last decade. The
>> choice is between (1) specifying congestion control around the
>> substrate UDP that can be turned off if it causes problems, or (2)
>> specifying nothing at this time and adding it later if operators want
>> it.
>>
>> I guess if this can be written as a SHOULD, up to the implementor's
>> discretion, then okay.
> 
> I don't think we can leave this up to implementors discretion. We've had IETF consensus that Internet communication requires congestion control at least since RFC2914. A circuit breaker mechanisms seems straightforward to implement.
> 
> As is, I object to this document going forward. The minor benefits of getting some better load balancing for MPLS are far outweighed by the risks.
> 
> (I'm also going to shut up now, and let others speak. I think I've said my bit.)
> 


I'm in basic agreement.

Assuming we might all agree that there are conceivable scenarios where
a circuit breaker mechanism would be useful, is the real issue that
we don't all agree that it could be implemented in a way that's not
burdensome and doesn't degrade performance unnecessarily?

Or is there still fundamental disagreement about whether the scenarios
where the circuit breaker is useful are even valid?

-- 
Wes Eddy
MTI Systems

From xuxiaohu@huawei.com  Mon Jan 13 19:32:35 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBB131AD986; Mon, 13 Jan 2014 19:32:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.55
X-Spam-Level: *
X-Spam-Status: No, score=1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, CN_BODY_35=0.339, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FP__vBDA7iQa; Mon, 13 Jan 2014 19:32:32 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 83B371AD8DC; Mon, 13 Jan 2014 19:32:30 -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.7-GA FastPath queued) with ESMTP id BCL68367; Tue, 14 Jan 2014 03:32:17 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 14 Jan 2014 03:31:26 +0000
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 14 Jan 2014 03:32:15 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Tue, 14 Jan 2014 11:32:10 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>, "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: =?gb2312?B?tPC4tDogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1pbi11?= =?gb2312?B?ZHAtMDQudHh0PiAoRW5jYXBzdWxhdGluZyBNUExTIGluIFVEUCkgdG8gUHJv?= =?gb2312?Q?posed_Standard?=
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPEMiG7ChTi8dU4kyxN0iU+aYNwZqDihaw
Date: Tue, 14 Jan 2014 03:32:09 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08244868@NKGEML512-MBS.china.huawei.com>
References: Your message of "Mon, 13 Jan 2014 10:51:45 -0500." <52D40B91.8040101@joelhalpern.com> <201401140132.s0E1Wkit084822@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401140132.s0E1Wkit084822@maildrop2.v6ds.occnc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:29:51 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 03:32:35 -0000

SGkgQ3VydGlzIGFuZCBKb2VsLA0KDQpUaGFua3MgYSBsb3QgZm9yIHlvdXIgZGV0YWlsZWQgY29t
bWVudHMuDQoNCkhpIExhcnMsDQoNCkkgd29uZGVyIHdoZXRoZXIgdGhlIGZvbGxvd2luZyBjb21w
cm9taXNlZCB0ZXh0IGZvciB0aGUgQ29uZ2VzdGlvbiBDb25zaWRlcmF0aW9uIHNlY3Rpb24gb2Yg
dGhpcyBkb2MgaXMgcm91Z2hseSBhY2NlcHRhYmxlIHRvIHlvdS4NCg0KU2luY2UgdGhlIE1QTFMt
aW4tVURQIGVuY2Fwc3VsYXRpb24gY2F1c2VzIE1QTFMgcGFja2V0cyB0byBiZSBmb3J3YXJkZWQg
dGhyb3VnaCAiVURQIHR1bm5lbHMiLCB0aGUgY29uZ2VzdGlvbiBjb250cm9sIGd1aWRlbGluZXMg
Zm9yIFVEUCB0dW5uZWxzIGFzIGRlZmluZWQgaW4gU2VjdGlvbiAzLjEuMyBvZiBbUkZDNTQwNV0g
U0hPVUxEIGJlIGZvbGxvd2VkLiBTcGVjaWZpY2FsbHksIE1QTFMgY2FuIGNhcnJ5IGEgbnVtYmVy
IG9mIGRpZmZlcmVudCBwcm90b2NvbHMgYXMgcGF5bG9hZHMuIFdoZW4gdGhlIE1QTFMgcGF5bG9h
ZCB0cmFmZmljIGlzIElQLWJhc2VkIGFuZCBjb25nZXN0aW9uLWNvbnRyb2xsZWQsIHRoZSBVRFAg
dHVubmVsIFNIT1VMRCBOT1QgZW1wbG95IGl0cyBvd24gY29uZ2VzdGlvbiBjb250cm9sIG1lY2hh
bmlzbSwgYmVjYXVzZSBjb25nZXN0aW9uIGxvc3NlcyBvZiB0dW5uZWxlZCB0cmFmZmljIHdpbGwg
YWxyZWFkeSB0cmlnZ2VyIGFuIGFwcHJvcHJpYXRlIGNvbmdlc3Rpb24gcmVzcG9uc2UgYXQgdGhl
IG9yaWdpbmFsIHNlbmRlcnMgb2YgdGhlIHR1bm5lbGVkIHRyYWZmaWMuIFdoZW4gdGhlIE1QTFMg
cGF5bG9hZCB0cmFmZmljIGlzIG5vdCBrbm93biB0byBiZSBJUC1iYXNlZCwgb3IgaXMga25vd24g
dG8gYmUgSVAtYmFzZWQgYnV0IG5vdCBjb25nZXN0aW9uLWNvbnRyb2xsZWQsIHRoZSBVRFAgdHVu
bmVsIFNIT1VMRCBlbXBsb3kgYW4gYXBwcm9wcmlhdGUgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hh
bmlzbSB3aGljaCBpcyBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50Lg0KDQpCZXN0
IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiAtLS0tLdPKvP7Urbz+LS0tLS0NCj4gt6K8/sjLOiBDdXJ0
aXMgVmlsbGFtaXphciBbbWFpbHRvOmN1cnRpc0BpcHY2Lm9jY25jLmNvbV0NCj4gt6LLzcqxvOQ6
IDIwMTTE6jHUwjE0yNUgOTozMw0KPiDK1bz+yMs6IEpvZWwgTS4gSGFscGVybg0KPiCzrcvNOiBF
Z2dlcnQsIExhcnM7IFh1eGlhb2h1OyBtcGxzQGlldGYub3JnOyBTY290dCBCcmltOyBJRVRGDQo+
INb3zOI6IFJlOiBbbXBsc10gTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi1tcGxzLWluLXVkcC0wNC50
eHQ+IChFbmNhcHN1bGF0aW5nIE1QTFMNCj4gaW4gVURQKSB0byBQcm9wb3NlZCBTdGFuZGFyZA0K
PiANCj4gDQo+IEluIG1lc3NhZ2UgPDUyRDQwQjkxLjgwNDAxMDFAam9lbGhhbHBlcm4uY29tPg0K
PiAiSm9lbCBNLiBIYWxwZXJuIiB3cml0ZXM6DQo+IA0KPiA+IExhcnMsIGFyZSB5b3UgcmVhbGx5
IGFza2luZyB0aGF0IHRoZSBkb2N1bWVudCBzYXk6DQo+ID4gMSkgVGhhdCB0aGUgVURQIGVuY2Fw
c3VsYXRpb24gb2YgTVBMUyBjYW4gb25seSBiZSB1c2VkIHdoZW4gdGhlDQo+ID4gZGV2aWNlcyBw
ZXJmb3JtaW5nIHRoZSBlbmNhcHN1bGF0aW9uIGFuZCBkZWNhcHN1bGF0aW9uIGtub3cgd2hhdA0K
PiA+IHByb3RvY29sIChhYm92ZSBJUCwgaWYgSVAgaXMgYmVpbmcgY2FycmllZDsgYWJvdmUgRXRo
ZXJuZXQgYW5kIElQIGlmDQo+ID4gdGhlIGZyYW1lIGlzIEV0aGVybmV0IGNhcnJ5aW5nIElQKSBp
cyBiZWluZyB1c2VkDQo+ID4gMikgVGhhdCB0aG9zZSBkZXZpY2VzIG5lZWQgdG8gZW5nYWdlIGlu
IGEgY29uZ2VzdGlvbiBjb250cm9sIHByb3RvY29sDQo+ID4gaWYgdGhlIGNhcnJpZWQgcGFja2V0
cyBhcmUgbm90IFRDUCwgU0NUUCwgb3IgRENDUD8NCj4gPg0KPiA+IFRob3NlIGJvdGggbG9vayBs
aWtlIGV4Y2Vzc2l2ZSBhbmQgZGlmZmljdWx0IHJlcXVpcmVtZW50cy4gIFdoaWNoIGlzDQo+ID4g
ZmluZSBpZiBvdXIgZ29hbCBpcyB0byBwcmV0ZW5kIHdlIGFyZSB0ZWxsaW5nIGZvbGtzIG5vdCB0
byB1c2UgVURQDQo+ID4gZW5jYXBzdWxhdGlvbiBvZiBNUExTLiAgKEkgaGFkIG5vdCB0aG91Z2h0
IHRoYXQgd2FzIG91ciBnb2FsLikNCj4gPg0KPiA+IEluIHByYWN0aWNlLCBJIHNpbXBseSBkbyBu
b3Qgc2VlIGhvdyBhbnlvbmUgaW1wbGVtZW50aW5nIHRoaXMgd2lsbCBwYXkNCj4gPiBhbnkgYXR0
ZW50aW9uIHRvIGVpdGhlciByZXF1aXJlbWVudC4NCj4gPg0KPiA+IFlvdXJzLA0KPiA+IEpvZWwN
Cj4gDQo+IA0KPiBKb2VsLA0KPiANCj4gSSBhZ3JlZSB0aGF0IHRoZSByZXF1aXJlbWVudCBmb3Ig
dGhlIGVxdWlwbWVudCB0byAia25vdyIgd2hhdCBpcyBpbiB0aGUgTVBMUw0KPiB0cmFmZmljIGlz
IHJpZGljdWxvdXMuICBBIHByb3ZpZGVyIGdlbmVyYWxseSBkb2VzIGtub3cgd2hldGhlciB0aGUg
dHJhZmZpYyB3aWxsIGJlDQo+IG1vc3RseSBJUCBvciBtb3N0bHkgUFcgYW5kIGlmIFBXIG1vc3Rs
eSBJUCBpbnNpZGUgdGhlIFBXLg0KPiANCj4gSWYgc3RhdGluZyB0aGF0IGltcGxlbWVudGF0aW9u
cyBTSE9VTEQgc3VwcG9ydCBhIGZvcm0gb2YgY29uZ2VzdGlvbiBjb250cm9sDQo+IHNhdGlzZmll
cyBMYXJzLCB0aGVuIGl0cyBmaW5lIHRvIGFkZCBpdC4gIEFuZCB0aGVuIGlnbm9yZSBpdC4NCj4g
DQo+IEV2ZW4gaWYgdGhlIGRvY3VtZW50IHNhaWQgTVVTVCBpdCBpcyBsaWtlbHkgdG8gYmUgaWdu
b3JlZCBpbiBwcmFjdGljZSB0aHJvdWdoIGENCj4gbm9uLVJGQyBjb21wbGlhbnQgY29uZmlndXJh
dGlvbiBrbm9iLg0KPiANCj4gQXMgdG8gd2hldGhlciBNUExTIHR1bm5lbGVkIHRyYWZmaWMgaW4g
VURQIGNvdWxkIGVuZCB1cCBvbiB0aGUgcGxhaW4gb2xkDQo+IEludGVybmV0LCB0aGF0IGlzIGV4
YWN0bHkgd2hhdCBtb3N0IHByb3ZpZGVycyBpbiBlZmZlY3QgZG8gdG9kYXkgd2l0aCBNUExTLiAg
VGhlDQo+IGhpZ2ggbWFyZ2luIGxlZ2FjeSBMMiBwcm90b2NvbHMsIHN1Y2ggYXMgVERNLCBBVE0s
IEZSLCBhbGwgcmlkZSBvbiBQVyBhbmQNCj4gTVBMUyBvdmVyIHRoZSB2ZXJ5IHNhbWUgaW5mcmFz
dHJ1Y3R1cmUgYXMgcGxhaW4gSVAuDQo+IFRoZSBsb3cgdHJhZmZpYyB2b2x1bWUgaGlnaCBwYXlp
bmcgdHJhZmZpYyBnZXRzIHF1ZXVlaW5nIHByaW9yaXR5IGJhc2VkIG9uDQo+IHBheWluZyBzbyBt
dWNoIGZvciBpdCBhbmQgYW4gZXhwZWN0YXRpb24gb2YgZ29vZCBvciBwZXJmZWN0IHNlcnZpY2Ug
YW5kIHRoZQ0KPiB0cmFmZmljIHZvbHVtZSBpcyBzbyBsb3cgdGhhdCB0aGUgcGxhaW4gSVAgdHJh
ZmZpYyBkb2Vzbid0IG5vdGljZS4gIElmIGEgVURQIGFuZCBJUA0KPiBoZWFkZXIgZ290IHN0dWNr
IGluIHRoZXJlLCBub3QgbXVjaCB3b3VsZCBjaGFuZ2UuICBBbmQgY2VydGFpbmx5IGFueQ0KPiBj
b25nZXN0aW9uIGNvbnRyb2wgd291bGQgYmUgZGlzYWJsZWQuDQo+IA0KPiBJZiBPVE9ILCBzb21l
IGVuZCBjdXN0b21lciBwdXQgdGhlaXIgTkZTdjQgb3ZlciBVRFAgc3RyZWFtIG9yIHRoZWlyDQo+
IGJpdHRvcnJlbnQgc3RyZWFtIG92ZXIgTVBMUyBvdmVyIFVEUCwgaXQgd291bGQgYmVoYXZlIGp1
c3QgdGhlIHNhbWUgKGp1c3QgYXMNCj4gYmFkbHkgYnV0IG5vIHdvcnNlKSBhcyBwbGFpbiBORlN2
NCBvdmVyIFVEUCBvdmVyIElQIG9yIHBsYWluIGJpdHRvcnJlbnQuICBObw0KPiBjaGFuZ2UuICBB
bmQgdGhlIG5ldHdvcmsgaG9zdGlsZSBiaXR0b3JyZW50IHNpdGUgaXNuJ3QgZ29pbmcgdG8gZW5h
YmxlDQo+IGNvbmdlc3Rpb24gY29udHJvbCBvbiB0aGUgVURQIHR1bm5lbCBlaXRoZXIuDQo+IA0K
PiBTbyB0aGlzIHdob2xlIGRpc2N1c3Npb24gaXMgb3ZlciBub3RoaW5nLiAgQnV0IGlmIHB1dHRp
bmcgYSBTSE9VTEQgaW4gYQ0KPiBkb2N1bWVudCBlbmRzIHRoZSBkaXNjdXNzaW9uLCBpdCBtaWdo
dCBiZSB3b3J0aCBpdC4gIFRoZSB0ZWNobmljYWwgc3RpY2t5IHBvaW50DQo+IGlzIGtub3dpbmcg
dGhhdCB0aGUgY29uZ2VzdGlvbiBpcyBvY2N1cmluZy4gIFBlcmhhcHMgYSBMTSBsaWtlIHBhY2tl
dCBvbg0KPiBhbm90aGVyIFVEUCBwb3J0IGNvdWxkIGJlIGV4Y2hhbmdlZCB3aXRoIHRoZSBzYW1l
IGNhdmVhdHMgYWJvdXQgaW5hY2N1cmFjeQ0KPiBpZiBpbXBsZW1lbnRlZCBpbiBzb2Z0d2FyZSBh
bmQgaW5hY2N1cmFjeSBpZiByZW9yZGVyaW5nIG9jY3VycywgYW5kIGENCj4gcmVjb21tZW5kYXRp
b24gY2FuIGJlIG1hZGUgdG8gZG8gc29tZXRoaW5nIHRvIGludHJvZHVjZSBkcm9wIGlmIGNvbmdl
c3Rpb24NCj4gaXMgaW5kaWNhdGVkIGJ5IHRoaXMgbWV0aG9kLiAgSG93IHRvIGludHJvZHVjZSBk
cm9wIHNob3VsZCBiZSBhbg0KPiBpbXBsZW1lbnRhdGlvbiBkZXRhaWwsIGEgZm9ybSBvZiBBUU0g
b3IgbGVha3kgYnVja2V0IGJlaW5nIHBvc3NpYmxlIGNob2ljZXMsDQo+IGJ1dCBlbnRpcmVseSBh
IGxvY2FsIG1hdHRlci4NCj4gU2luY2UgaXQgaXMgYSBTSE9VTEQgYW5kIGlmIG5vIHJlYWwgY3Vz
dG9tZXIgZXZlciB3YW50cyBpdCB3ZSBjYW4gYWxsIGp1c3QgaWdub3JlDQo+IGl0Lg0KPiANCj4g
Q3VydGlzDQo+IA0KPiANCj4gPiBPbiAxLzEzLzE0IDM6NTAgQU0sIEVnZ2VydCwgTGFycyB3cm90
ZToNCj4gPiA+IEhpLA0KPiA+ID4NCj4gPiA+IE9uIDIwMTQtMS0xMywgYXQgNDo0MCwgWHV4aWFv
aHUgPHh1eGlhb2h1QGh1YXdlaS5jb20+IHdyb3RlOg0KPiA+ID4+PiBJIGRvbid0IHRoaW5rIGl0
J3MgcmlnaHQgdG8gdHJ5IHRvIHNvbHZlIHRoaXMgaW4gTVBMUywgYmVjYXVzZQ0KPiA+ID4+PiBN
UExTIGlzIG5vdCBhIGZvcndhcmRpbmcgcHJvdG9jb2wgLSBpdCdzIGEgY29ubmVjdGl2aXR5IHBy
b3RvY29sLg0KPiA+ID4NCj4gPiA+IHJpZ2h0LCBNUExTIGlzIHRoZSB3cm9uZyBwbGFjZSB0byBh
ZGRyZXNzIGlzLiBUaGUgVURQIGVuY2Fwcy9kZWNhcHMNCj4gPiA+IGZ1bmN0aW9uIG5lZWRzIHRv
IGhhdmUgdGhpcyBmdW5jdGlvbmFsaXR5Lg0KPiA+ID4NCj4gPiA+Pj4gSW4gYW55IHVzZSBvZiBV
RFAsIGNvbmdlc3Rpb24gY29udHJvbCBpcyBlaXRoZXIgbGVmdCB0byBzb21ldGhpbmcNCj4gPiA+
Pj4gYWJvdmUgVURQIG9yIGlnbm9yZWQgKGxlZnQgdG8gcXVldWUgbWFuYWdlbWVudCkuDQo+ID4g
Pg0KPiA+ID4gVGhlcmUgYXJlIHNldmVyYWwgY2FzZXMsIHNlZSBTZWN0aW9uIDMuMS4zIG9mIFJG
QzU0MDUuIE1QTFMtb3Zlci1VRFANCj4gPiA+IGNhbiBmYWxsIGludG8gYW55IG9mIHRoZSB0aHJl
ZSBjYXNlcywgZGVwZW5kaW5nIG9uIHdoYXQgdHJhZmZpYyBpcw0KPiA+ID4gaW5zaWRlIHRoZSBM
U1AgYmVpbmcgZW5jYXBzdWxhdGVkLg0KPiA+ID4NCj4gPiA+IFlvdSdsbCBub3RpY2UgdGhhdCBS
RkM1NDA1IGZvciB0aGUgZmlyc3QgY2FzZSAtIGVuY2Fwc3VsYXRpb24gb2YNCj4gPiA+IElQLWJh
c2VkIGNvbmdlc3Rpb24gY29udHJvbGxlZCAibm9ybWFsIiBJbnRlcm5ldCB0cmFmZmljIC0gZXZl
biBzYXlzDQo+ID4gPiB0aGF0IHRoZSB0dW5uZWwgU0hPVUxEIE5PVCBlbXBsb3kgYW55IGNvbmdl
c3Rpb24gY29udHJvbCBzY2hlbWUgb2YNCj4gPiA+IGl0cyBvd24uIEhhdmluZyBsYXllcmVkIGNv
bnRyb2wgbG9vcHMgZmlnaHRpbmcgaXMgbm90IHByb2R1Y3RpdmUuDQo+ID4gPg0KPiA+ID4gVGhl
IGlzc3VlIHdpdGggTVBMUy1pbi1VRFAgKGFuZCBHUkUtaW4tVURQLCBhbmQgYW55IG90aGVyIGVu
Y2Fwcw0KPiA+ID4gc2NoZW1lIHRoYXQgY2FuIGNhcnJ5IG5vbi1JUCB0cmFmZmljKSBhcmUgd2l0
aCBjYXNlcyB0d28gYW5kIHRocmVlLg0KPiA+ID4gV2hlbiB0aGUgd29ya2xvYWQgdGhhdCBpcyBi
ZWluZyBlbmNhcHN1bGF0ZWQgaXNuJ3Qga25vd24gdG8gYmUNCj4gPiA+IGNvbmdlc3Rpb24gY29u
dHJvbGxlZCBieSBpdHMgZW5kcG9pbnRzLCBpdCBpcyB0aGUgb2JsaWdhdGlvbiBvZiB0aGUNCj4g
PiA+IHR1bm5lbCB0byBkZXRlY3QgY29uZ2VzdGlvbiBhbmQgcmVhY3QgdG8gaXQgYnkgcmVkdWNp
bmcgdGhlIHRyYWZmaWMNCj4gPiA+IHZvbHVtZS4gQmVjYXVzZSBmb3IgdGhlIHJlc3Qgb2YgdGhl
IG5ldHdvcmssIHRoYXQgdHVubmVsIGlzIHRoZSBVRFANCj4gPiA+IHNlbmRlciwgYW5kIHdlIGhh
dmUgSUVURiBjb25zZW5zdXMgdGhhdCB3ZSBkb24ndCB3YW50IFVEUCBzZW5kZXJzDQo+ID4gPiB0
aGF0IGRvbid0IHJlYWN0IHRvIGNvbmdlc3Rpb24gb24gdGhlIG5ldC4gKFRoYXQncyBvbmUgb2Yg
dGhlIG1haW4NCj4gPiA+IHJlYXNvbnMgZm9yIHRoZSBleGlzdGVuY2Ugb2YgdGhlIFJNQ0FUIFdH
IC0gd2UgZG9uJ3Qgd2FudA0KPiA+ID4gbm9uLWNvbmdlc3Rpb24tY29udHJvbGxlZCBSVFAgbWVk
aWEgdHJhZmZpYyBvbiB0aGUgbmV0LikNCj4gPiA+DQo+ID4gPiBUaGUga2V5IGRpZmZlcmVuY2Ug
YmV0d2VlbiBwdXR0aW5nIE1QTFMgZS5nLiBpbnRvIElQIGNvbXBhcmVkIHRvDQo+ID4gPiBwdXR0
aW5nIGl0IGludG8gVURQIGlzIHRoYXQgb25jZSBpdCdzIGluIFVEUCwgaXQgY2FuIGdvIHByZXR0
eSBtdWNoDQo+ID4gPiBhbnl3aGVyZSBvbiB0aGUgbmV0LCBiZWNhdXNlIFVEUCB0cmF2ZXJzZXMg
TkFUcyBhbmQgZmlyZXdhbGxzIG11Y2gNCj4gPiA+IG1vcmUgZWFzaWx5IHRoYW4gSVAgdHJhZmZp
YyB3aXRoIGEgcmFyZSBwcm90b2NvbCBudW1iZXIgZG9lcy4NCj4gPiA+DQo+ID4gPj4+IFNpbWls
YXJseSwgeW91IHdhbnQgdGhlIGNsaWVudCBvZiBNUExTIHRvIGJlIHJlc3BvbnNpYmxlIGZvcg0K
PiA+ID4+PiBtYW5hZ2luZyBpdHMgdHJhZmZpYy4gTVBMUyBnaXZlcyB5b3UgcGF0aHMsIGl0IGRv
ZXNuJ3QgcHVzaA0KPiA+ID4+PiBwYWNrZXRzIG92ZXIgdGhlbS4NCj4gPiA+DQo+ID4gPiBSaWdo
dC4gSG93ZXZlciwgb25jZSB5b3Ugc2xhcCBhIFVEUCBoZWFkZXIgb24gYSBwYWNrZXQgZHVyaW5n
DQo+ID4gPiBlbmNhcHN1bGF0aW9uLCB5b3Ugbm93IHN1YmplY3RlZCB5b3Vyc2VsZiB0byB0aGUg
cnVsZXMgZm9yIEludGVybmV0DQo+ID4gPiBVRFAgc2VuZGVycy4gVGhvc2UgYXJlIGRvY3VtZW50
ZWQgaW4gUkZDNTQwNSwgYW5kIHJlcXVpcmUgdGhlIHR1bm5lbA0KPiA+ID4gdG8gaW1wbGVtZW50
IHNvbWUgc29ydCBvZiBjb25nZXN0aW9uIGRldGVjdGlvbiBhbmQgY29udHJvbC4gSSdkDQo+ID4g
PiBwZXJzb25hbGx5IGNvbnNpZGVyIGEgY2lyY3VpdCBicmVha2VyIG1lY2hhbmlzbSBzdWZmaWNp
ZW50LCBsaWtlIFJUUA0KPiA+ID4gYW5kIEkgdGhpbmsgUFdFIGFyZSB1c2luZy4NCj4gPiA+DQo+
ID4gPj4gRnVsbHkgYWdyZWUuIFRoZSBjb25nZXN0aW9uIGNvbnRyb2wgc2hvdWxkIGJlIHBlcmZv
cm1lZCBlaXRoZXIgYnkNCj4gPiA+PiB0aGUgVURQIHR1bm5lbCBpdHNlbGYgb3IgdGhlIGNsaWVu
dCBvZiBNUExTLiBJbiB0aGUgZm9ybWVyIGNhc2UsDQo+ID4gPj4gaXQnZCBiZXR0ZXIgdG8gc3Bl
Y2lmeSB0aGUgcHJhY3RpY2FsIGNvbmdlc3Rpb24gY29udHJvbCBtZWNoYW5pc21zDQo+ID4gPj4g
KGlmIHRoZXJlIHdlcmUgYW55KSBpbiBhIGdlbmVyaWMgZHJhZnQgKGUuZy4sIFJGQzU0MDViaXMp
IGFuZCB0aGVuDQo+ID4gPj4gYW55IHVzZSBvZiB0aGUgVURQIHR1bm5lbCBjb3VsZCByZWZlciB0
byB0aGF0IGdlbmVyaWMgZHJhZnQgd2l0aA0KPiA+ID4+IHJlZ2FyZCB0byBjb25nZXN0aW9uIGNv
bnRyb2wuDQo+ID4gPg0KPiA+ID4gVGhlIGdlbmVyYWwgY29uY2VwdCBvZiBhIGNpcmN1aXQgYnJl
YWtlciBpcyBlYXN5IGVub3VnaCB0aGF0IGl0DQo+ID4gPiBkb2Vzbid0IHJlYWxseSBuZWVkIHRv
IGJlIHdyaXR0ZW4gZG93bi4gQW5kIGl0IHdvdWxkbid0IGJlIHBvc3NpYmxlDQo+ID4gPiB0byBk
ZXNjcmliZSBpdCBpbiBhIGdlbmVyaWMgZmFzaGlvbiwgYmVjYXVzZSBjb25nZXN0aW9uIGRldGVj
dGlvbiBpcw0KPiA+ID4gdHlwaWNhbGx5IHNwZWNpZmljIHRvIHRoZSBwcm90b2NvbCBiZWluZyBl
bmNhcHN1bGF0ZWQgKGUuZy4sIFJUUA0KPiA+ID4gdXNlcyBSVENQIGZlZWRiYWNrIHRvIGRlcml2
ZSBsb3NzIGluZm9ybWF0aW9uLCBldGMuKSBBbmQgdGhlDQo+ID4gPiByZWFjdGlvbiB0byBjb25n
ZXN0aW9uIGlzIGFsc28gZGVwZW5kZW50IG9uIHRoZSBwcm90b2NvbCBiZWluZw0KPiA+ID4gZW5j
YXBzdWxhdGVkIChkb2VzIGl0IHN1cHBvcnQgbXVsdGlwbGUgcmF0ZXMgb3Igb25seSBvbi9vZmYs
IHdoYXQNCj4gPiA+IHRpbWVzY2FsZXMgYXJlIE9LIGZvciByZWFjdGlvbiwgZXRjLikNCj4gPiA+
DQo+ID4gPj4gSW4gdGhlIGxhdHRlciBjYXNlLCBpZiB0aGUgY2xpZW50IG9mIE1QTFMgaXMgVENQ
LWZyaWVuZGx5LCB0aGF0IGlzDQo+ID4gPj4gZ3JlYXQuIE90aGVyd2lzZSAoZS5nLiwgY2lyY3Vp
dCBlbXVsYXRpb24gc2VydmljZSksIGl0IHNob3VsZG4ndCBiZQ0KPiA+ID4+IGRlcGxveWVkIG9u
IHRoZSBJbnRlcm5ldCBhdCBhbGwsIGp1c3QgYXMgaGFzIGJlZW4gcG9pbnRlZCBvdXQgaW4NCj4g
PiA+PiBSRkMzOTg1LCB0aGVyZWZvcmUgdGhlcmUgaXMgbm8gbmVlZCBmb3IgYW55IHNwZWNpZmlj
IGNvbmdlc3Rpb24NCj4gPiA+PiBjb250cm9sIG1lY2hhbmlzbSBvbiB0aGUgY2xpZW50Lg0KPiA+
ID4+DQo+ID4gPj4gIi4uLiBJbiBlc3NlbmNlLCB0aGlzIHJlcXVpcmVtZW50IHN0YXRlcyB0aGF0
IGl0IGlzIG5vdCBhY2NlcHRhYmxlDQo+ID4gPj4gdG8gZGVwbG95IGFuIGFwcGxpY2F0aW9uICh1
c2luZyBQV0UzIG9yIGFueSBvdGhlciB0cmFuc3BvcnQNCj4gPiA+PiBwcm90b2NvbCkgb24gdGhl
IGJlc3QtZWZmb3J0IEludGVybmV0LCB3aGljaCBjb25zdW1lcyBiYW5kd2lkdGgNCj4gPiA+PiBh
cmJpdHJhcmlseSBhbmQgZG9lcyBub3QgY29tcGV0ZSBmYWlybHkgd2l0aCBUQ1Agd2l0aGluIGFu
IG9yZGVyIG9mDQo+ID4gPj4gbWFnbml0dWRlLiIgKHF1b3RlZCBmcm9tIFNlY3Rpb24gNi41IG9m
IFJGQzM5ODUpDQo+ID4gPj4NCj4gPiA+PiBUaGUgYWJvdmUgY2hvaWNlIHNlZW1zIG5vIGNvbmZs
aWN0IHdpdGggdGhlIGZvbGxvd2luZyBjb25nZXN0aW9uDQo+ID4gPj4gY29udHJvbCBndWlkZWxp
bmVzIGFzIHF1b3RlZCBmcm9tIFNlY3Rpb24gMy4xLjEgb2YgUkZDNTQwNSwgYXMNCj4gPiA+PiB0
aG9zZSBub24tVENQLWZyaWVuZGx5IHRyYWZmaWMgd291bGQgYmUgdHJhbnNwb3J0ZWQgb3ZlciBh
DQo+ID4gPj4gcHJvdmlzaW9uZWQgcGF0aCwgcmF0aGVyIHRoYW4gb24gdGhlIEludGVybmV0Lg0K
PiA+ID4+DQo+ID4gPj4gIi4uLkZpbmFsbHksIHNvbWUgYnVsayB0cmFuc2ZlciBhcHBsaWNhdGlv
bnMgbWF5IGNob29zZSBub3QgdG8NCj4gPiA+PiBpbXBsZW1lbnQgYW55IGNvbmdlc3Rpb24gY29u
dHJvbCBtZWNoYW5pc20gYW5kIGluc3RlYWQgcmVseSBvbg0KPiA+ID4+IHRyYW5zbWl0dGluZyBh
Y3Jvc3MgcmVzZXJ2ZWQgcGF0aCBjYXBhY2l0eS4gIFRoaXMgbWlnaHQgYmUgYW4NCj4gPiA+PiBh
Y2NlcHRhYmxlIGNob2ljZSBmb3IgYSBzdWJzZXQgb2YgcmVzdHJpY3RlZCBuZXR3b3JraW5nDQo+
ID4gPj4gZW52aXJvbm1lbnRzLCBidXQgaXMgYnkgbm8gbWVhbnMgYSBzYWZlIHByYWN0aWNlIGZv
ciBvcGVyYXRpb24gaW4NCj4gPiA+PiB0aGUgSW50ZXJuZXQuIg0KPiA+ID4NCj4gPiA+IEhvdyBp
cyB0aGF0IGluIGNvbmZsaWN0PyBCb3RoIHF1b3RlcyBzYXkgdGhhdCBJbnRlcm5ldCB0cmFmZmlj
IG5lZWRzDQo+ID4gPiBjb25nZXN0aW9uIGNvbnRyb2wsIHdoaWNoIGlzIGEgcmVzdGF0ZW1lbnQg
b2YgUkZDMjkxNC4NCj4gPiA+DQo+ID4gPiBMYXJzDQo+ID4gPg0KPiA+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4gbXBscyBtYWlsaW5nIGxpc3QN
Cj4gPiBtcGxzQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tcGxzDQo=

From curtis@ipv6.occnc.com  Mon Jan 13 11:11:39 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFAA41AE005; Mon, 13 Jan 2014 11:11:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6kaCCNyruBj; Mon, 13 Jan 2014 11:11:37 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id A52B91AE008; Mon, 13 Jan 2014 11:11:36 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0DJBC1o079251; Mon, 13 Jan 2014 14:11:12 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401131911.s0DJBC1o079251@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] [lisp] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
In-reply-to: Your message of "Mon, 13 Jan 2014 00:45:52 +0000." <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk>
Date: Mon, 13 Jan 2014 14:11:12 -0500
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:30:04 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, farinacci@gmail.com, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 13 Jan 2014 19:11:39 -0000

One of the reasons that IPv6 (rfc2460) dropped the header checksum
that was in IPv4 is that with link layers all doing FCS it served no
purpose.  For the same reason TCP and UDP checksums server no purpose.

The link layer checksum fails and the packet is dropped.  Since this
is usually not at the last hop (often a local Ethernet) but instead in
a WAN link, the packet never arrives at the destination for anything
to count IP header or TCP or UDP checksum errors.

Also all of the following handle both data integrity and congestion
avoidance the same way:

  UDP over IP over Ethernet
  UDP over IP over MPLS over Ethernet
  UDP over IP over MPLS over UDP over IP over Ethernet
  s/Ethernet/{POS,GFP,etc}/ for all of the above
  s/^UDP over IP/PW/ for all of the above

In all of the above cases data integrity is handled by the link layer.
In all of the above cases congestion avoidance is handled by the
application (or not at all).  Whether MPLS is carried directly over a
link layer or over UDP/IP over a link layer makes no difference.

Curtis

In message <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> Really, you'd want to expose the pseudoheader check at endhosts; a well-instrumented Linux box could tell you a lot
> about checksum failures.
>  
> But in this case, a router would be decapping UDP/MPLS tunnels as an endpoint, so could report on checksum failures -
> if the checksum wasn't zero.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Dino Farinacci [farinacci@gmail.com]
> Sent: 12 January 2014 21:37
> To: Wood L  Dr (Electronic Eng)
> Cc: <mark.tinka@seacom.mu>; <mpls@ietf.org>; gorry@erg.abdn.ac.uk; lisp@ietf.org; david.black@emc.com; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; ietf@ietf.org
> Subject: Re: [lisp] [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>  
> > Do any routers count TCP/UDP checksum failures, much less
> > expose the count via SNMP?
>  
> Typically they do but only for packets destined to them. Much like hosts would check the header checksum.
>  
> Dino
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From curtis@ipv6.occnc.com  Mon Jan 13 12:31:25 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B5611AE000; Mon, 13 Jan 2014 12:31:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 90ay5x1IFPNC; Mon, 13 Jan 2014 12:31:23 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id C743A1ADFC3; Mon, 13 Jan 2014 12:31:22 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0DKV4iC081057; Mon, 13 Jan 2014 15:31:04 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401132031.s0DKV4iC081057@maildrop2.v6ds.occnc.com>
To: "Eggert, Lars" <lars@netapp.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 13 Jan 2014 08:50:06 +0000." <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
Date: Mon, 13 Jan 2014 15:31:04 -0500
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:33:40 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 13 Jan 2014 20:31:25 -0000

RFC5405

   However, if the IP traffic in the tunnel is known to not be
   congestion-controlled, additional measures are RECOMMENDED in order
   to limit the impact of the tunneled traffic on other traffic
   sharing the path.

RFC5405

   | for tunnels carrying IP Traffic,                        | 3.1.3   |
   | SHOULD NOT perform congestion control                   |         |
   |                                                         |         |
   | for non-IP tunnels or rate not determined by traffic,   | 3.1.3   |
   | SHOULD perform congestion control                       |         |

RECOMMENDED == SHOULD

IMHO the intended usage of MPLS over UDP, like the widespread usage of
PW, will not be deployed in a situation where congestion control is
applicable and therefore will not be deployed with congestion control.
And nothing bad will happen.  If we want to define an optional
congestion control in MPLS over UDP, that would meet the RFC5405
recommendation above.

Curtis


ps - Keep in mind that even for the case where Ethernet (L2VPN) over
PW over MPLS over UDP over IP over some L2 is run, the thing run over
the L2VPN Ethernet is predominantly IP.


In message <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com>
"Eggert, Lars" writes:

--===============1602757442944542782==
Content-Language: en-US
Content-Type: multipart/signed;
	boundary="Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D";
	protocol="application/pgp-signature"; micalg=pgp-sha1

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312

Hi,

On 2014-1-13, at 4:40, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>> I don't think it's right to try to solve this in MPLS, because MPLS =
is not a
>> forwarding protocol - it's a connectivity protocol.

right, MPLS is the wrong place to address is. The UDP encaps/decaps =
function needs to have this functionality.

>> In any use of UDP, congestion
>> control is either left to something above UDP or ignored (left to =
queue
>> management).

There are several cases, see Section 3.1.3 of RFC5405. MPLS-over-UDP can =
fall into any of the three cases, depending on what traffic is inside =
the LSP being encapsulated.=20

You'll notice that RFC5405 for the first case - encapsulation of =
IP-based congestion controlled "normal" Internet traffic - even says =
that the tunnel SHOULD NOT employ any congestion control scheme of its =
own. Having layered control loops fighting is not productive.

The issue with MPLS-in-UDP (and GRE-in-UDP, and any other encaps scheme =
that can carry non-IP traffic) are with cases two and three. When the =
workload that is being encapsulated isn't known to be congestion =
controlled by its endpoints, it is the obligation of the tunnel to =
detect congestion and react to it by reducing the traffic volume. =
Because for the rest of the network, that tunnel is the UDP sender, and =
we have IETF consensus that we don't want UDP senders that don't react =
to congestion on the net. (That's one of the main reasons for the =
existence of the RMCAT WG - we don't want non-congestion-controlled RTP =
media traffic on the net.)

The key difference between putting MPLS e.g. into IP compared to putting =
it into UDP is that once it's in UDP, it can go pretty much anywhere on =
the net, because UDP traverses NATs and firewalls much more easily than =
IP traffic with a rare protocol number does.

>> Similarly, you want the client of MPLS to be responsible for
>> managing its traffic. MPLS gives you paths, it doesn't push packets =
over them.

Right. However, once you slap a UDP header on a packet during =
encapsulation, you now subjected yourself to the rules for Internet UDP =
senders. Those are documented in RFC5405, and require the tunnel to =
implement some sort of congestion detection and control. I'd personally =
consider a circuit breaker mechanism sufficient, like RTP and I think =
PWE are using.

> Fully agree. The congestion control should be performed either by the =
UDP tunnel itself or the client of MPLS. In the former case, it'd better =
to specify the practical congestion control mechanisms (if there were =
any) in a generic draft (e.g., RFC5405bis) and then any use of the UDP =
tunnel could refer to that generic draft with regard to congestion =
control.

The general concept of a circuit breaker is easy enough that it doesn't =
really need to be written down. And it wouldn't be possible to describe =
it in a generic fashion, because congestion detection is typically =
specific to the protocol being encapsulated (e.g., RTP uses RTCP =
feedback to derive loss information, etc.) And the reaction to =
congestion is also dependent on the protocol being encapsulated (does it =
support multiple rates or only on/off, what timescales are OK for =
reaction, etc.)

> In the latter case, if the client of MPLS is TCP-friendly, that is =
great. Otherwise (e.g., circuit emulation service), it shouldn't be =
deployed on the Internet at all, just as has been pointed out in =
RFC3985, therefore there is no need for any specific congestion control =
mechanism on the client.
>=20
>  "... In essence, this requirement states that it is
>   not acceptable to deploy an application (using PWE3 or any other
>   transport protocol) on the best-effort Internet, which consumes
>   bandwidth arbitrarily and does not compete fairly with TCP within an
>   order of magnitude." (quoted from Section 6.5 of RFC3985)
>=20
> The above choice seems no conflict with the following congestion =
control guidelines as quoted from Section 3.1.1 of RFC5405, as those =
non-TCP-friendly traffic would be transported over a provisioned path, =
rather than on the Internet.
>=20
>   "...Finally, some bulk transfer applications may choose not to =
implement
>   any congestion control mechanism and instead rely on transmitting
>   across reserved path capacity.  This might be an acceptable choice
>   for a subset of restricted networking environments, but is by no
>   means a safe practice for operation in the Internet."

How is that in conflict? Both quotes say that Internet traffic needs =
congestion control, which is a restatement of RFC2914.

Lars

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtOovdZcnpRveo1xAQICtAP+IEcc32eXYdPz7se0PX+ytfYOjHW1ExJt
bF/Wc+1umMc/GXbLL9tf8fKJdSpe/+ZUhuL6WpYG9BoptbI0uCsWCCH98/WP7BUI
Bzf3SgJE1Qxpv+HNXTtYV1OuKJuYxp4p6Lgujkz1aGtiT1VfpBjX7a5e2D290dCp
Kwtms72DUPw=
=PeLB
-----END PGP SIGNATURE-----

--Apple-Mail=_F966CFC8-CF7E-4540-8EA2-FE7CAF7DBF1D--

--===============1602757442944542782==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1602757442944542782==--

From curtis@ipv6.occnc.com  Mon Jan 13 17:33:25 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E3EA1ADFC3; Mon, 13 Jan 2014 17:33:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D_pBWGmJUxAC; Mon, 13 Jan 2014 17:33:22 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 673321A8028; Mon, 13 Jan 2014 17:33:22 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0E1Wkit084822; Mon, 13 Jan 2014 20:32:47 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401140132.s0E1Wkit084822@maildrop2.v6ds.occnc.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 13 Jan 2014 10:51:45 -0500." <52D40B91.8040101@joelhalpern.com>
Date: Mon, 13 Jan 2014 20:32:46 -0500
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:34:30 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, Xuxiaohu <xuxiaohu@huawei.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 14 Jan 2014 01:33:25 -0000

In message <52D40B91.8040101@joelhalpern.com>
"Joel M. Halpern" writes:
 
> Lars, are you really asking that the document say:
> 1) That the UDP encapsulation of MPLS can only be used when the devices
> performing the encapsulation and decapsulation know what protocol (above
> IP, if IP is being carried; above Ethernet and IP if the frame is
> Ethernet carrying IP) is being used
> 2) That those devices need to engage in a congestion control protocol if
> the carried packets are not TCP, SCTP, or DCCP?
>  
> Those both look like excessive and difficult requirements.  Which is
> fine if our goal is to pretend we are telling folks not to use UDP
> encapsulation of MPLS.  (I had not thought that was our goal.)
>  
> In practice, I simply do not see how anyone implementing this will pay
> any attention to either requirement.
>  
> Yours,
> Joel


Joel,

I agree that the requirement for the equipment to "know" what is in
the MPLS traffic is ridiculous.  A provider generally does know
whether the traffic will be mostly IP or mostly PW and if PW mostly IP
inside the PW.

If stating that implementations SHOULD support a form of congestion
control satisfies Lars, then its fine to add it.  And then ignore it.

Even if the document said MUST it is likely to be ignored in practice
through a non-RFC compliant configuration knob.

As to whether MPLS tunneled traffic in UDP could end up on the plain
old Internet, that is exactly what most providers in effect do today
with MPLS.  The high margin legacy L2 protocols, such as TDM, ATM, FR,
all ride on PW and MPLS over the very same infrastructure as plain IP.
The low traffic volume high paying traffic gets queueing priority
based on paying so much for it and an expectation of good or perfect
service and the traffic volume is so low that the plain IP traffic
doesn't notice.  If a UDP and IP header got stuck in there, not much
would change.  And certainly any congestion control would be disabled.

If OTOH, some end customer put their NFSv4 over UDP stream or their
bittorrent stream over MPLS over UDP, it would behave just the same
(just as badly but no worse) as plain NFSv4 over UDP over IP or plain
bittorrent.  No change.  And the network hostile bittorrent site isn't
going to enable congestion control on the UDP tunnel either.

So this whole discussion is over nothing.  But if putting a SHOULD in
a document ends the discussion, it might be worth it.  The technical
sticky point is knowing that the congestion is occuring.  Perhaps a LM
like packet on another UDP port could be exchanged with the same
caveats about inaccuracy if implemented in software and inaccuracy if
reordering occurs, and a recommendation can be made to do something to
introduce drop if congestion is indicated by this method.  How to
introduce drop should be an implementation detail, a form of AQM or
leaky bucket being possible choices, but entirely a local matter.
Since it is a SHOULD and if no real customer ever wants it we can all
just ignore it.

Curtis


> On 1/13/14 3:50 AM, Eggert, Lars wrote:
> > Hi,
> > 
> > On 2014-1-13, at 4:40, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> >>> I don't think it's right to try to solve this in MPLS, because
> >>> MPLS is not a forwarding protocol - it's a connectivity
> >>> protocol.
> > 
> > right, MPLS is the wrong place to address is. The UDP encaps/decaps
> > function needs to have this functionality.
> > 
> >>> In any use of UDP, congestion control is either left to something
> >>> above UDP or ignored (left to queue management).
> > 
> > There are several cases, see Section 3.1.3 of RFC5405. MPLS-over-UDP
> > can fall into any of the three cases, depending on what traffic is
> > inside the LSP being encapsulated.
> > 
> > You'll notice that RFC5405 for the first case - encapsulation of
> > IP-based congestion controlled "normal" Internet traffic - even says
> > that the tunnel SHOULD NOT employ any congestion control scheme of
> > its own. Having layered control loops fighting is not productive.
> > 
> > The issue with MPLS-in-UDP (and GRE-in-UDP, and any other encaps
> > scheme that can carry non-IP traffic) are with cases two and three.
> > When the workload that is being encapsulated isn't known to be
> > congestion controlled by its endpoints, it is the obligation of the
> > tunnel to detect congestion and react to it by reducing the traffic
> > volume. Because for the rest of the network, that tunnel is the UDP
> > sender, and we have IETF consensus that we don't want UDP senders
> > that don't react to congestion on the net. (That's one of the main
> > reasons for the existence of the RMCAT WG - we don't want
> > non-congestion-controlled RTP media traffic on the net.)
> > 
> > The key difference between putting MPLS e.g. into IP compared to
> > putting it into UDP is that once it's in UDP, it can go pretty much
> > anywhere on the net, because UDP traverses NATs and firewalls much
> > more easily than IP traffic with a rare protocol number does.
> > 
> >>> Similarly, you want the client of MPLS to be responsible for 
> >>> managing its traffic. MPLS gives you paths, it doesn't push
> >>> packets over them.
> > 
> > Right. However, once you slap a UDP header on a packet during
> > encapsulation, you now subjected yourself to the rules for Internet
> > UDP senders. Those are documented in RFC5405, and require the tunnel
> > to implement some sort of congestion detection and control. I'd
> > personally consider a circuit breaker mechanism sufficient, like RTP
> > and I think PWE are using.
> > 
> >> Fully agree. The congestion control should be performed either by
> >> the UDP tunnel itself or the client of MPLS. In the former case,
> >> it'd better to specify the practical congestion control mechanisms
> >> (if there were any) in a generic draft (e.g., RFC5405bis) and then
> >> any use of the UDP tunnel could refer to that generic draft with
> >> regard to congestion control.
> > 
> > The general concept of a circuit breaker is easy enough that it
> > doesn't really need to be written down. And it wouldn't be possible
> > to describe it in a generic fashion, because congestion detection is
> > typically specific to the protocol being encapsulated (e.g., RTP uses
> > RTCP feedback to derive loss information, etc.) And the reaction to
> > congestion is also dependent on the protocol being encapsulated (does
> > it support multiple rates or only on/off, what timescales are OK for
> > reaction, etc.)
> > 
> >> In the latter case, if the client of MPLS is TCP-friendly, that is
> >> great. Otherwise (e.g., circuit emulation service), it shouldn't be
> >> deployed on the Internet at all, just as has been pointed out in
> >> RFC3985, therefore there is no need for any specific congestion
> >> control mechanism on the client.
> >> 
> >> "... In essence, this requirement states that it is not acceptable
> >> to deploy an application (using PWE3 or any other transport
> >> protocol) on the best-effort Internet, which consumes bandwidth
> >> arbitrarily and does not compete fairly with TCP within an order of
> >> magnitude." (quoted from Section 6.5 of RFC3985)
> >> 
> >> The above choice seems no conflict with the following congestion
> >> control guidelines as quoted from Section 3.1.1 of RFC5405, as
> >> those non-TCP-friendly traffic would be transported over a
> >> provisioned path, rather than on the Internet.
> >> 
> >> "...Finally, some bulk transfer applications may choose not to
> >> implement any congestion control mechanism and instead rely on
> >> transmitting across reserved path capacity.  This might be an
> >> acceptable choice for a subset of restricted networking
> >> environments, but is by no means a safe practice for operation in
> >> the Internet."
> > 
> > How is that in conflict? Both quotes say that Internet traffic needs
> > congestion control, which is a restatement of RFC2914.
> > 
> > Lars
> > 
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From curtis@ipv6.occnc.com  Tue Jan 14 07:51:17 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1BE1AE09C; Tue, 14 Jan 2014 07:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NTFsiqOmpGvp; Tue, 14 Jan 2014 07:51:14 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 395E81AE0DF; Tue, 14 Jan 2014 07:51:14 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0EFojHp098066; Tue, 14 Jan 2014 10:50:46 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401141550.s0EFojHp098066@maildrop2.v6ds.occnc.com>
To: mark.tinka@seacom.mu
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: OT was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
In-reply-to: Your message of "Sun, 12 Jan 2014 21:04:40 +0200." <201401122104.44370.mark.tinka@seacom.mu>
Date: Tue, 14 Jan 2014 10:50:45 -0500
X-Mailman-Approved-At: Tue, 14 Jan 2014 08:53:37 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 14 Jan 2014 15:51:17 -0000

In message <201401122104.44370.mark.tinka@seacom.mu>
Mark Tinka writes:
 
> On Sunday, January 12, 2014 08:37:16 PM Curtis Villamizar=20
> wrote:
>  
> > Perhaps if you actully worked for a company that made
> > line cards you would not make the above statement.
>  
> I work for an operator that pays real money to deploy and=20
> use those line cards, and I make it my business to know what=20
> I'm paying for.
>  
> > Many of the big router vendors use the same TCAM hardware
> > for MPLS lookups as they do for IP lookups.  Doing the
> > lookup is not the rate limiting factor even in hardware
> > that has an ILM SRAM table and some form of radix based
> > lookup.  All of the hardwre I've seen in the last 15
> > years or so forwards MPLS and IP at the same rate.
>  
> Which was exactly my point - unless you somehow missed that.

What you said was "Current-generation ASIC's have no problem
forwarding MPLS frames at wire rate".

Since you didn't mention IP packets I assumed you were making the 20
year old argument that MPLS forwarding was faster than IP.

> > ...
> > Except IPv6 before they decided to waste the lower half
> > of the address space with 40 quintilion host in a
> > bridged subnet and you really did have to look at the
> > whole 128 bits.
>  
> It is no secret that forwarding of IPv6 packets on some=20
> vendor equipment is about half the rate of IPv4 or MPLS. But=20
> then again, because MPLS control planes are IPv4-driven=20
> today, I'm hoping I didn't have to be explicit about not=20
> including IPv6 in that group, on this list.

None of the equipment I have worked on (a while back) or the chips we
evaluated recently had such a problem for IPv6 using only the top 64
bits for forwarding.  An argument was made in the early 2000s (by me
and others) that if we allocated global routes only from the top 64
bits all equipment at that time could forward at essentially the same
rate as for IPv4.  The reaction from the IPv6 community was to
completely throw away the bottom half of the address and make it the
host part.

There are chips for which looking at a 32 bit prefix or a 64 bit
prefix is done within the same pipeline and therefore takes the same
amount of time.  Other chips which parallelize packet handling budget
enough microengines to get the job done (only a part of which is the
MPLS ILM or IP destination lookup).

> > Back when forwarding was done in
> > software (circa 1995) your statement would have been
> > true if MPLS preceeded forwarding ASICs which it did
> > not.
>  
> You might not know that line cards from C like the LSP=20
> (Label Switch Processor) and much of the PFE from J's PTX=20
> are forwarding engines that have been made cheaper by=20
> reducing the IP FIB on the assumption that all traffic will=20
> be carried in MPLS. This is, obviously, an assumption I do=20
> not support because:

Those line cards (and designs I was recently involved in) assume what
has historically been called a BGP-free core.  Only the IGP routes are
carried in the core.  BGP is mapped onto the IGP routes.  MPLS carries
traffic across the core.  The core has no BGP routes and therefore
needs a lot fewer entries and the ILM can be put into SRAM rather than
use a TCAM and only a small set of IP routes needs to be supported.

That is done to eliminate a need for large external DRAM or TCAM which
itself and the SERDES needed to go off chip produces heat and requires
power, board space, and cooling and therefore reduces density.
Putting more simple filters in the core also helps increase density.
It is more a power to operate and floor space per Gb/s issue.

For the most part IP/MPLS transport equipment seems to be going this
way, though some people are stuck on MPLS-TP and trying to build a L2
overlay.

If you go back to before 2000 at least one provider built a BGP-free
core over Frame Relay, but FR itself soon died and the overlay didn't
scale well.  Some providers wanted to do this over MPLS but the
RSVP-TE restoration times were too long and the fallback to IP routing
was still needed to make up for that.

> 	- I run IPv6 natively, and at the moment, there are
> 	  no production-grade IPv6 control planes for MPLS.
>  
> 	- It assumes providers will run 6PE (in which case,
> 	  IPv6 traffic enjoys MPLS and IPv6 wire rate
> 	  forwarding speeds).
>  
> I do not buy such line cards because for anyone running=20
> native IPv6, you could potentially run out of FIB slots to=20
> host IPv6 routes.

Unless you run a BGP-free core, whether IPv4 or IPv6.  Then you have
plenty of FIB space.

> That is why I say MPLS has allowed vendors to put out=20
> cheaper line cards compared to the costs of those which have=20
> large IPv4/IPv6 scale. Because MPLS forwarding is so=20
> mainstream, there is no additional cost associated with=20
> forwarding rates similar to IPv4. So much of the cost of=20
> line cards is in QoS queues and routing FIB slots (and MPLS-
> biased line cards are stripped of that, hence making them=20
> cheaper).

You put forwarding at full rate and cheaper line cards in the same
paragraph with no mention of smaller FIB size due to eliminating the
BGP routes.

> > Also the statement "Current-generation ASIC's have no
> > problem forwarding MPLS frames at wire rate" is not true
> > for most (or all) hardware with 40 byte payloads (even
> > with plus 4 with TCP SACK plus 4 if MPLS) and 100 Gb/s
> > interfaces.  It is true for "average packet size"
> > traffic and on most hardware only true if bursts of 40
> > byte packets are very limited in duration.
>  
> C'mon, Curtis. Everybody knows this already. Moreover, real=20
> world IP traffic is not all 40 bytes.
>  
> If operators have doubts about what forwarding engines can=20
> do below 128 bytes, that is what PoC labs are for before you=20
> buy. And even then, several operators accept the=20
> restrictions up to a certain point, because the lab and real=20
> life vary significantly.
>  
> Mark.

OK ... so this is all interesting but I've lost the connection between
this discussion and draft-ietf-mpls-in-udp.  Hence the OT in the
subject.  Would you please remind me what that connection was.

Curtis

From hartmans@mit.edu  Tue Jan 14 11:33:29 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01BC1AE139 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:33:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cO4lqRahByCC for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:33:28 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA1D1AE10D for <ietf@ietf.org>; Tue, 14 Jan 2014 11:33:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 4547220511; Tue, 14 Jan 2014 14:30:46 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4p3_3zUi0lGr; Tue, 14 Jan 2014 14:30:45 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 14 Jan 2014 14:30:45 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id BB2D883788; Tue, 14 Jan 2014 14:33:15 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com>
Date: Tue, 14 Jan 2014 14:33:15 -0500
In-Reply-To: <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> (Scott Brim's message of "Mon, 13 Jan 2014 16:25:11 -0500")
Message-ID: <tsl4n56tl38.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 19:33:29 -0000

>>>>> "Scott" == Scott Brim <scott.brim@gmail.com> writes:

    Scott> OK, if we're going to get stuck on the example, we should
    Scott> take it out.  As Sam said, it's the least necessary part.

    Scott> I still think the phrase in the first sentence "including
    Scott> which existing technology is re-used" could be better.

Yeah, let's lose the example at this point.

I disagree with Eliot: I don't think the general statement is a truism
especially not in a BCP.
In particular we're:

* saying what point in the process you need to evaluate the
  architectural implications on your ability to   mittigate pervasive
  monitoring

* Reminding people to get appropriate review 

* Indicating that PM needs to be considered at the architectural
  decision level, not just late in the process.


I believe all that is important in a BCP, and strongly support that sort
of statement being in a BCP now.
I definitely don't want to see the example used as an argument against
BCP so let's lose it.

From scott.brim@gmail.com  Tue Jan 14 11:41:37 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0AE1ADF84 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGbvtAcVIpZG for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:41:36 -0800 (PST)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id EED671ADF9A for <ietf@ietf.org>; Tue, 14 Jan 2014 11:41:35 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wn1so83850obc.27 for <ietf@ietf.org>; Tue, 14 Jan 2014 11:41:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=D6hV13Xd2EiexjbwGsrvIcsDTImKPx7h6RKjgO5INOQ=; b=IFjX0q4S0lFPmr8rPiXBKr+eHEz9gI3m8tZylwQsNhoaJFo4dpriotTMuvyTO5PXmH cSX/tlMZfkrvlugoTuJlafjdQsYb3ckSNgqk8INvdQ7WAjYoQGSz3avQgYcXNAyxaT6B 2OxIuRmLZXjBXyvjaLlzreo1Om/GwPT4pYzPcH34O2xm8zv13Lu+ZVg5G3QAf1ze0hw7 vNL9KJ5UfcDfTiHcjvLNp30kdflBLaszXfnk88NJeq0jzgVqyVvEhrakZoOrAWw45zTy NYbjgBCudD2SXCj96ELXXwaMF1/IAFY/bmrcx5h03I3OJQ+Pq8D8sL/IVnJeX4D2VraK Hb0Q==
X-Received: by 10.60.65.101 with SMTP id w5mr2706181oes.0.1389728484434; Tue, 14 Jan 2014 11:41:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 11:41:04 -0800 (PST)
In-Reply-To: <tsl4n56tl38.fsf@mit.edu>
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 14:41:04 -0500
Message-ID: <CAPv4CP_yx=N1aMyyz33E9rbvc7WcszmM+G5zcF2b1Z8=AHxyHQ@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 19:41:37 -0000

On Tue, Jan 14, 2014 at 2:33 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>>>>>> "Scott" == Scott Brim <scott.brim@gmail.com> writes:
>
>     Scott> OK, if we're going to get stuck on the example, we should
>     Scott> take it out.  As Sam said, it's the least necessary part.
>
>     Scott> I still think the phrase in the first sentence "including
>     Scott> which existing technology is re-used" could be better.
>
> Yeah, let's lose the example at this point.
>
> I disagree with Eliot: I don't think the general statement is a truism
> especially not in a BCP.
> In particular we're:
>
> * saying what point in the process you need to evaluate the
>   architectural implications on your ability to   mittigate pervasive
>   monitoring
>
> * Reminding people to get appropriate review
>
> * Indicating that PM needs to be considered at the architectural
>   decision level, not just late in the process.
>
>
> I believe all that is important in a BCP, and strongly support that sort
> of statement being in a BCP now.
> I definitely don't want to see the example used as an argument against
> BCP so let's lose it.

Yes, all true.

Please drop what I said about ambiguity in the first sentence. It's
not worth stopping progress for.

Are we ready to move forward?

Scott

From lear@cisco.com  Tue Jan 14 11:45:53 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521281AE1A6 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:45:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CHsMBhf9E_H for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 11:45:52 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 10DAA1ADF83 for <ietf@ietf.org>; Tue, 14 Jan 2014 11:45:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=358; q=dns/txt; s=iport; t=1389728741; x=1390938341; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=lkzW3ItK9+izuot+noKcSE1ZlI7labQfV6hY4QVOCkY=; b=QbSkoA/XCVgptADipfhH2YNiIJqO3MZZBo+D2ku+/qcFyDfCQQr1Y6+y m6wxx+ADbUsF4OEJagN8rBquvElVLvRdKs7EQ+jJ5x3JAgG1AVcwZ+9Ll +aKmmrNyUM9OagqJi9AXfvCvjd3w+DvP3V+x2XcgjpJrPrNVQcnHJINLk E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8FAFGT1VKQ/khL/2dsb2JhbABaDoJ9hAy3ZYEXFnSCJgEBBCNVARALEggCBRYLAgIJAwIBAgEPHAwOBgEMAQUCAQGHbAMRqDeVZg2FYReBKYtLghMHgm+BSAEDljKBbIxahTuCbkA7
X-IronPort-AV: E=Sophos;i="4.95,659,1384300800";  d="scan'208";a="2954844"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 14 Jan 2014 19:45:40 +0000
Received: from mctiny.local ([10.61.167.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0EJjcbK001280 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 19:45:39 GMT
Message-ID: <52D593E2.7000202@cisco.com>
Date: Tue, 14 Jan 2014 20:45:38 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>, Scott Brim <scott.brim@gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu>
In-Reply-To: <tsl4n56tl38.fsf@mit.edu>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 19:45:53 -0000

On 1/14/14 8:33 PM, Sam Hartman wrote:

>>>>>> "Scott" == Scott Brim <scott.brim@gmail.com> writes:
>
> I disagree with Eliot: I don't think the general statement is a truism
> especially not in a BCP.

To test if it's a truism, replace perpass with anything else and see
what design consideration should be examined late in the process.

Eliot


From scott.brim@gmail.com  Tue Jan 14 13:03:08 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF6A71AE230 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 13:03:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KV6ehtrMKZeO for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 13:03:07 -0800 (PST)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2DD781AE255 for <ietf@ietf.org>; Tue, 14 Jan 2014 13:03:06 -0800 (PST)
Received: by mail-oa0-f51.google.com with SMTP id m1so201569oag.24 for <ietf@ietf.org>; Tue, 14 Jan 2014 13:02:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=s9dhyZ2sSYJgjj6mrlXsBG4JbDyJoFfJPH0+D9Ndw5c=; b=Y+YyKGqCYw5utCbQxvpz9cZeX83LkXX0CLQO24NaMtnYdAKcTt5M/MlRrERqCZ1tc9 oj26TSbQC0k7Rx3k6ngbnodrW2p3/7CGh7A/BLcSwykGBLH1jRrVGUJiErZQOnRkGu6j OgmDY4E72f9O6AuMYk5N7dXYteS0UeRYXtl/ZYtLStSei0WGWR20nMg+e+dMKr8S9A9H DotSscGEhX8Rub1AZc6BKgkqK7ti5W5yJB9TdMgmxUXSzZD+HQhD65nrA/Uzl6u/WQ/P MQDmhAIkAZKVM5FQ0FiBRHWwTGI62yNQGg8dbet23iSM46ZJvC/DAJMy64jUBz+ezSN6 29JQ==
X-Received: by 10.60.97.36 with SMTP id dx4mr2906136oeb.40.1389733374615; Tue, 14 Jan 2014 13:02:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 13:02:34 -0800 (PST)
In-Reply-To: <52D593E2.7000202@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu> <52D593E2.7000202@cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 16:02:34 -0500
Message-ID: <CAPv4CP9+qxAo7B0qr5VrvBdisFeU8E-C+KGgvNMTs=JTHPm8zA@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 21:03:08 -0000

Sorry, Eliot, I didn't understand it either, particularly about lateness.

The point of the paragraph is to declare PM to be something that
should be considered at architecture time, i.e. early in the design
process, when the fundamentals are worked out. (Personally I would
prefer to make it a general statement about "privacy", not just PM,
but I'm glad to get whatever I can.)  The statement is not that
architectural issues need to be considered early (that just begs the
question), but rather that PM needs to be considered an architectural
issue.

Scott

From l.wood@surrey.ac.uk  Tue Jan 14 13:45:25 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E321AE102; Tue, 14 Jan 2014 13:45:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level: 
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HRSZo3uZblw; Tue, 14 Jan 2014 13:45:21 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.169]) by ietfa.amsl.com (Postfix) with ESMTP id BE2BD1ADF99; Tue, 14 Jan 2014 13:45:20 -0800 (PST)
Received: from [85.158.137.99:20628] by server-9.bemta-3.messagelabs.com id F2/1A-13104-4EFA5D25; Tue, 14 Jan 2014 21:45:08 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-217.messagelabs.com!1389735907!21370390!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1957 invoked from network); 14 Jan 2014 21:45:07 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 14 Jan 2014 21:45:07 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 14 Jan 2014 21:44:30 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Tue, 14 Jan 2014 21:44:29 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8RatT0ErGP8P+xT9qHx2FSHtJ1FgAA+RYU
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.uk>
References: Your message of "Tue, 14 Jan 2014 08:28:05 +0000." <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>, <201401142054.s0EKsADA001944@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401142054.s0EKsADA001944@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, xuxiaohu@huawei.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 21:45:25 -0000

The HDLC part here is last link, not the scope of the whole path.
Any 'low' bit error rate given actually becomes quite high once
you consider no of bits per packet and line rate...

Do read Jonathan Stone's papers on where errors creep in -
not just in the link, by at any point along the path, including
regeneration



Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 14 January 2014 20:54
To: Wood L  Dr (Electronic Eng)
Cc: jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@huawei.com; mpls@ietf.or=
g; ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

In message <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:

> It stands to reason that if tunnelers can turn off udp checksums
> because their performance is degraded, they can turn off
> congestion control because it will degrade their performance.
>
> Rest of the internet getting congested and getting
> misdelivered corrupted packets? Really not their problem.
>
> There are important vendors trying to sell products here,
> and they need performance to do so.
> Get with the program!
>
> Lloyd Wood
> http://about.me/lloydwood


OK, perhaps if you are running MPLS/UDP/IP over HDLC and the HDLC
configuration is set to count FCS errors but not drop you will still
*really* need the UDP checksum.  Otherwise its isn't going to do much
for you.  Any checksum is really bad for some types of errors such as
chunk reordering and multiple bit errors.

Maybe on HDLC or PPP with 16 bit CRC you may see a low error rate, but
in theory that would be much less than 10^-5 since few multiple bit
errors will be coincidence match the CRC, even for a 16 bit CRC.

I suspect most routers would be able to do the checksum anyway and for
modern links if they come up with a zero error count that's fine.

<ot>

Modern OTN based transport networks use forward error correction FEC
which accounts for a fair amount of overhead and a lot of processing
gates on the receiving end.  The measure of effectiveness of given FEC
is in dB with 10 dB being a reduction of a factor of 10 in bit errors
and typical FEC in the high tens of dB.  The target corrected error
rate is often 10^-15 or one bit error in 24 hours for 10 Gb/s, one bit
error in 2.5 hours for 100 Gb/s.  Any link with corrected bit error
rates approaching 10^-12 is taken out of service.  This is roughly
equivalent to the old ES (errored seconds) and SES (severely errored
seconds) metric where a ES is one second with any bit errors and an
SES is one second with 10 or more errors (I think its 10).  More than
some number of ES or SES and a link is taken down.  The uncorrected
errors are passed through.

A packet may traverse an entire continent with 2-3 such links
separated by regeneration or could stop at a number of routers along
the way.  Typically today the router uses 10GbE or 100GbE (growing
use) which are then passed as a bit stream in the transport network.
At the other end the uncorrected errors from transport are picked up
by Ethernet 32 bit FCS.  Since a 32 bit FCS picks up 100% of single
bit errors and most instances where a small number of bits are in
error, and all but 1 in 2^32 where many bits are in error, few errors
are going to get through.  If GFP is used, the per packet FCS is
checked at each hop and for GFP-T also checked end to end.

A bad local ethernet is more likely to contribute an error (again
better than 1 in 2^32 detection is expected) due to something like a
bad CAT-{5,5e,6} connection or too many sharp turns.  A DSL or DOCSIS
link is also more likely to contribute an error.  With CRC32 on all
links and no bad hardware in between (ie: circa 1990s equipment with
no parity RAM and no correction on DMA, buses, etc) you would expect
on the order of 10^-8 errors (10^-9 per hop, a few errored hops).

For example, two hosts on my home LAN had non-zero tcp checksums.
Each had < 10^-6 packet error rate.  It is hard to tell if this is
host errors at the other end.  The only hosts I have with non-zero are
on the service provider DMZ LAN so that would include any bot attacks,
etc, where sending hosts could be old junk.  Host behind those have
zero UDP and TCP checksum errors.  This seems similar to Stewart's
quick check.

In the T1/T3 days the transport layer just had parity and just counted
parity errors.  Providers in those days were notorious for ignoring ES
and SES counters until the customer complained.  HDLC then had its 16
bit CRC, optional 32 bit.  If an ISP wasn't paying attention to their
HDLC error counters then it was up to the IP end customer to complain
and hope the problem got escallated rather than dropped.

</ot>

As to whether congestion control is in practice needed see
http://www.ietf.org/mail-archive/web/mpls/current/msg11222.html

Its fine to make them both optional and to make congestion control
mechanisms out of scope and the topic of a later document if needed.

Curtis



> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern [jmh@joel=
halpern.com]
> Sent: 10 January 2014 15:36
> To: Eggert, Lars; Xuxiaohu
> Cc: mpls@ietf.org; IETF
> Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MP=
LS in UDP) to Proposed Standard
>
> Maybe I am completely missing things, but this looks wrong.
> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> control will make it more likely that the service won't work.  Is that
> really the goal?
>
> We do not perform congestion control on MPLS LSPs.
> Assuming that a UDP tunnel is carrying just MPLS and was established
> just for MPLS, why would we expect it to behave differently than an MPLS
> LSP running over the exact same path, carrying the exact same traffic?
>
> Yours,
> Joel
>
> On 1/10/14 3:47 AM, Eggert, Lars wrote:
> > Hi,
> >
> > that sounds good. What congestion control are you going to be specifyin=
g for your tunnel?
> >
> > Lars
> >
> > On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> >
> >> Hi Lars,
> >>
> >> Thanks a lot for your comments.
> >>
> >> I wonder whether the following modified text for Congestion Considerat=
ion section is OK from your point of view:
> >>
> >> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarde=
d through "UDP tunnels", the congestion control guidelines for UDP tunnels =
as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically, =
MPLS can carry a number of different protocols as payloads. When the payloa=
d traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NOT =
employ its own congestion control mechanism, because congestion losses of t=
unneled traffic will already trigger an appropriate congestion response at =
the original senders of the tunneled traffic. When the payload traffic is n=
ot known to be IP-based, or is known to be IP-based but not congestion-cont=
rolled, the UDP tunnel SHOULD employ an appropriate congestion control mech=
anism. Furthermore, because UDP tunnels are usually bulk-transfer applicati=
ons as far as the intermediate routers are concerned, the guidelines as def=
ined in Section 3.1.1 of [RFC5405] SHOULD apply.
> >>
> >> Best regards,
> >> Xiaohu
> >>
> >>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> >>> =B7=A2=BC=FE=C8=CB: mpls [mailto:mpls-bounces@ietf.org] =B4=FA=B1=ED =
Eggert, Lars
> >>> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA1=D4=C28=C8=D5 18:22
> >>> =CA=D5=BC=FE=C8=CB: IETF
> >>> =B3=AD=CB=CD: mpls@ietf.org
> >>> =D6=F7=CC=E2: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (=
Encapsulating MPLS
> >>> in UDP) to Proposed Standard
> >>>
> >>> Hi,
> >>>
> >>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> >>>> - 'Encapsulating MPLS in UDP'
> >>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
> >>>
> >>>
> >>> this document needs to describe how it addresses the issues raised in=
 BCP145
> >>> (RFC5405). It already contains some text about messages sizes and con=
gestion
> >>> considerations, which is great. Unfortunately, the text about congest=
ion
> >>> considerations is not fully in line with RFC5405.
> >>>
> >>> Lars
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From fred@cisco.com  Tue Jan 14 13:45:48 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A52B01AE245; Tue, 14 Jan 2014 13:45:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.039
X-Spam-Level: 
X-Spam-Status: No, score=-115.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 88hM5Z4Nua3j; Tue, 14 Jan 2014 13:45:46 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 121491AE18B; Tue, 14 Jan 2014 13:45:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2669; q=dns/txt; s=iport; t=1389735933; x=1390945533; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Qztm/aaC677/65pQk8xped+U/y5kMvSpUwAwuWy4l+8=; b=CL1V1M+7BQz7L3D2ZibQeM6f3iYhc4qpODz/QrH6Hxw+7NpwWaS9yLtG W7shJstyqYL9GpUrhQD5UxdOtSsQ8JKgJXCUzhe50D9w7eEm3tzFLiNfi hTrRVNU8IfxIzbK+Mzuz4SrU4+OyykfoRZpmMxi/xjFNR7mLww+4556iB U=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj8FAFiv1VKtJV2Y/2dsb2JhbABRCYMLOFa6bIEYFnSCJQEBAQMBZxIFCwIBCBIcARcyFw4CBA4FDgyHYggNw3gXjixbBxIBgxGBEwSQN4ExAoY0gTCQZYMtgWoHFyI
X-IronPort-AV: E=Sophos;i="4.95,659,1384300800";  d="asc'?scan'208";a="297305395"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP; 14 Jan 2014 21:45:32 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0ELjWSp008760 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Jan 2014 21:45:32 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.86]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Tue, 14 Jan 2014 15:45:32 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: draft-farrell-perpass-attack architecture issue
Thread-Topic: draft-farrell-perpass-attack architecture issue
Thread-Index: AQHPEJW1zBILpAAtaEWpS3JElCG6BZqFJ00A
Date: Tue, 14 Jan 2014 21:45:31 +0000
Message-ID: <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie>
In-Reply-To: <52D43E69.6090001@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_BC463148-3AF9-4C49-A696-21C2858FD9E8"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 21:45:48 -0000

--Apple-Mail=_BC463148-3AF9-4C49-A696-21C2858FD9E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jan 13, 2014, at 11:28 AM, Stephen Farrell =
<stephen.farrell@cs.tcd.ie> wrote:

>  It means
>   that, if asked, there needs to be a good answer to the question "is
>   pervasive monitoring relevant to this work and if so how has it been
>   considered?"

Just a thought - that might be a good question to add to the shepherd's =
report.

In that case, I might suggest a minor change, however. We discuss =
"Pervasive monitoring" in a "big brother is watching" sense, and (at =
least in perpass) concern ourselves with data that could have been =
hidden had encryption or some other code used. I'll argue that, however =
dreadful Big Brother might be, location-based services can be a lot =
scarier.

=
http://online.wsj.com/news/articles/SB100014240527023034530045792906321289=
29194?mg=3Dreno64-wsj&url=3Dhttp%3A%2F%2Fonline.wsj.com%2Farticle%2FSB1000=
1424052702303453004579290632128929194.html

Data point: a lot of these operate without specific knowledge of an =
individual, but can. For example, the article talks a lot about =
aggregating information and providing it without identifying =
information. However, it goes on to say that if someone logs into a =
service using, for example, a Facebook identifier, they can remain =
identified to the system as they wander around in it. The messages =
themselves contain no identifying information per se, but they contain =
information that can be correlated back to that login. And the login =
wasn't "data in flight", it was "creating state with a service at rest".

So the question in the shepherd's report should not be "tell me you =
thought about the EU Data Retention Initiative and whether your =
protocol's data identifies an individual". It should be "what personal, =
equipment, or session identifiers, encrypted or otherwise, are carried =
in your protocol? How might they be correlated with offline data or =
otherwise used to infer the identity or behavior of an individual?"

--Apple-Mail=_BC463148-3AF9-4C49-A696-21C2858FD9E8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFS1a/6bjEdbHIsm0MRAhurAKDtvxj9XPvF4VngGVR9vledpu7tDwCcCxCV
dL1riZJE7BKAAqskTxsRilU=
=VIWb
-----END PGP SIGNATURE-----

--Apple-Mail=_BC463148-3AF9-4C49-A696-21C2858FD9E8--

From scott.brim@gmail.com  Tue Jan 14 14:10:10 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE8E11AE2BA; Tue, 14 Jan 2014 14:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lo2H1UrCaKu6; Tue, 14 Jan 2014 14:10:08 -0800 (PST)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9CB1AE2AA; Tue, 14 Jan 2014 14:10:07 -0800 (PST)
Received: by mail-oa0-f53.google.com with SMTP id i7so286809oag.26 for <multiple recipients>; Tue, 14 Jan 2014 14:09:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=MHIWFAi9eUIgZBDzwRJ533ehtjlZCRvtuR3Bb3pPAjw=; b=ZmyfUx77OBGiBoOp+p1OKu6mpwMyhQx4cGkBdEq19iy+5E2+JW/0F6dpqfAoNCjA6z 173EEs1dF83/t4uKUKApo6tMRtgSshe014bg2bQy1i2sfSI4BiL+mV3pH5SgP/C2OK5m C0yq9dFVuL+p+8TrnSNPfMgWcSAvlNmsDbYz4hEoaqg2gCz/n66+OgQxXCbTgPSFoRg1 4ujnkUjNlkup74tfbUrBvAkE5I49VH/i3O3t4cpexZXOwL9Ej0P0YIVrNSrLI/TJ1vNe dJy97O8Rj76uNe+NFKPeF/b8TlIVXMktq7i361Mbanvz6ig6Aw9up3/UjqKDxg42XBEu K+pA==
X-Received: by 10.60.174.167 with SMTP id bt7mr3178714oec.54.1389737396354; Tue, 14 Jan 2014 14:09:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 14 Jan 2014 14:09:36 -0800 (PST)
In-Reply-To: <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 14 Jan 2014 17:09:36 -0500
Message-ID: <CAPv4CP-1G3ff9SovQ5-puSbDhcznmLY2LDquNv+BCN9Xpk9trw@mail.gmail.com>
Subject: Re: [perpass] draft-farrell-perpass-attack architecture issue
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 22:10:10 -0000

On Tue, Jan 14, 2014 at 4:45 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> So the question in the shepherd's report should not be "tell me you thoug=
ht about the EU Data Retention Initiative and whether your protocol's data =
identifies an individual". It should be "what personal, equipment, or sessi=
on identifiers, encrypted or otherwise, are carried in your protocol? How m=
ight they be correlated with offline data or otherwise used to infer the id=
entity or behavior of an individual?"

The main problem is that: privacy issues are deeper than that, the
question could be misunderstood without a larger context, and there's
already a set of documents discussing most of that larger context (RFC
6973, the perpass problem statement draft, etc.).

The Document Shepherd Write-Up currently doesn't reference security
guidelines directly. Instead of asking a few specific questions in the
shepherd's writeup as you suggest, consider adding the privacy/perpass
docs to BCP 72 (which already includes RFC 3552) as they are approved,
and then optionally add a question to the shepherd's writeup that
refers to it, in order to emphasize the increased attention to the
issue.

Scott

From l.wood@surrey.ac.uk  Tue Jan 14 21:40:25 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE131ADEA6; Tue, 14 Jan 2014 21:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.261
X-Spam-Level: 
X-Spam-Status: No, score=-2.261 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3iad7TG8zw5; Tue, 14 Jan 2014 21:40:22 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5BE1ADEA0; Tue, 14 Jan 2014 21:40:20 -0800 (PST)
Received: from [195.245.230.131:15100] by server-5.bemta-3.messagelabs.com id 46/4F-25188-83F16D25; Wed, 15 Jan 2014 05:40:08 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-78.messagelabs.com!1389764407!32710652!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8400 invoked from network); 15 Jan 2014 05:40:07 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-11.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 15 Jan 2014 05:40:07 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Wed, 15 Jan 2014 05:40:00 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Wed, 15 Jan 2014 05:39:59 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8RkxlnzH0wNAEATBaHj60siCfQ0gAHrv95
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C9@EXMB01CMS.surrey.ac.uk>
References: Your message of "Tue, 14 Jan 2014 21:44:29 +0000." <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.uk>, <201401150142.s0F1gVJP006084@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401150142.s0F1gVJP006084@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, xuxiaohu@huawei.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 05:40:25 -0000

Curtis

http://lmgtfy.com/?q=3DJonathan+Stone+CRC+checksum

HDLC is just whatever is over the last hop. You said HDLC, I reused that as
an example.

Any link technology could be substituted - 10Mbps Ethernet, say, though
you'd criticise that as not being 10Gbps Ethernet and therefore out of date=
.

Again, the point is that the link check is not end-to-end, and that errors
can creep in from the most unexpected places. By analogy with security,
if I have security across each hop, why would I need security end-to-end?
I already have it across each hop! Each link is highly and absolutely
unrbreakably secure! What is this end-to-end of which you speak?

If you don't get that point because it's a bit abstract and timeless, that'=
s
fine. (and if you have to explain the joke, the joke wasn't funny.)
The link CRC doesn't apply across the entire path; do the maths for
the path and a series of concatenated links.

[As it happens, I'm familiar with UDP/IP/HDLC internet infrastructure insta=
lled
within the decade and  in daily operational use to deliver imagery from orb=
it.
But the paper I wrote on that dates from 2007, so is old and
won't be of interest to you.]

Wait, this thread is all about putting 90s MPLS technology over UDP
technology specified in 1980. Clearly, if MPLS has to rely on an older
technology in this way, the MPLS crowd should give up and go home.=20

We've learned repeatedly that zero checksums are a bad idea. IPv6
RFC2460:

        Unlike IPv4, when UDP packets are originated by an IPv6 node,
         the UDP checksum is not optional.  That is, whenever
         originating a UDP packet, an IPv6 node must compute a UDP
         checksum over the packet and the pseudo-header, and, if that
         computation yields a result of zero, it must be changed to hex
         FFFF for placement in the UDP header.  IPv6 receivers must
         discard UDP packets containing a zero checksum, and should log
         the error.

which RFC6935 simply rewote as inconvenient to tunnelers without
considering how it affected everything else in the network.

Those that do not learn from history are doomed to repeat it.
(Unless it's recent history, in which case they're doomed to reject it
as irrelevant.)

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 15 January 2014 01:42
To: Wood L  Dr (Electronic Eng)
Cc: curtis@ipv6.occnc.com; jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@h=
uawei.com; mpls@ietf.org; ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

In message <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:

> The HDLC part here is last link, not the scope of the whole path.  Any
> 'low' bit error rate given actually becomes quite high once you
> consider no of bits per packet and line rate...
>
> Do read Jonathan Stone's papers on where errors creep in - not just in
> the link, by at any point along the path, including regeneration
>
> Lloyd Wood


Lloyd,

There is no HDLC hop.  No one has used HDLC for internet
infrastructure in ages.  It was a joke, like Scott's comment on
wanting to use X.25.  HDLC was disappearing when the Stone/Partridge
Sigcomm 2000 paper was written.

Links please.  And how old is that paper?  Not another 15 year old
work is it?

If you have one bit error per day, how many packets do you lose that
day?  (hint: one).

If you have one bit error per day, how many undetactable packet errors
do you have?  (hint: crc32 gets all one bit errors, therefore zero).

10^-12 bit errors is one per 10 second on 100 Gb/s, one per 100 second
on 10 Gb/s and is generally considered high enough to take a link down
immediately.  A 1500 byte packet is 12,000 bits, about ~10^4.  That
would yield a packet rate as high as 10^-8 if bit errors were mostly
one bit error per packet.  In that case all errors would be
detectable.  It is only when there are a lot of bit errors or more per
packet that the CRC can be defeated and then its about 10^-9 chance.

So at an error rate much less than 10^-8 packets (tightly bunched
errors with multiple bit errors per packet) some 10^-9 might be
undetectable with a CRC32.  One packet every 10^6 seconds at 100 Gb/s
could have an undetectable error.  About one undetectable error a day
or one a week for continuous full out 100 Gb/s link.

Note that the same low error rate does not apply to a GbE or 10GbE
over colored optics over ROADM in the metro since there is no FEC
there.  It also may not apply to the enterprise or campus Ethernets.
In those hops the error rate is likely to be higher.  Needless to say,
wireless hops can have very high error rates.

This is why it could make sense to have the UDP checksum optional in
MPLS over UDP.  It wouldn't hurt to provide the checksums but in some
cases it might be OK to disable them.  That is what SHOULD is for in
an IETF document.

Curtis


> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 14 January 2014 20:54
> To: Wood L  Dr (Electronic Eng)
> Cc: jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@huawei.com; mpls@ietf.=
org; ietf@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting MPLS in UDP) to Proposed Standard
>
> In message <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.a=
c.uk>
> l.wood@surrey.ac.uk writes:
>
> > It stands to reason that if tunnelers can turn off udp checksums
> > because their performance is degraded, they can turn off
> > congestion control because it will degrade their performance.
> >
> > Rest of the internet getting congested and getting
> > misdelivered corrupted packets? Really not their problem.
> >
> > There are important vendors trying to sell products here,
> > and they need performance to do so.
> > Get with the program!
> >
> > Lloyd Wood
> > http://about.me/lloydwood
>
>
> OK, perhaps if you are running MPLS/UDP/IP over HDLC and the HDLC
> configuration is set to count FCS errors but not drop you will still
> *really* need the UDP checksum.  Otherwise its isn't going to do much
> for you.  Any checksum is really bad for some types of errors such as
> chunk reordering and multiple bit errors.
>
> Maybe on HDLC or PPP with 16 bit CRC you may see a low error rate, but
> in theory that would be much less than 10^-5 since few multiple bit
> errors will be coincidence match the CRC, even for a 16 bit CRC.
>
> I suspect most routers would be able to do the checksum anyway and for
> modern links if they come up with a zero error count that's fine.
>
> <ot>
>
> Modern OTN based transport networks use forward error correction FEC
> which accounts for a fair amount of overhead and a lot of processing
> gates on the receiving end.  The measure of effectiveness of given FEC
> is in dB with 10 dB being a reduction of a factor of 10 in bit errors
> and typical FEC in the high tens of dB.  The target corrected error
> rate is often 10^-15 or one bit error in 24 hours for 10 Gb/s, one bit
> error in 2.5 hours for 100 Gb/s.  Any link with corrected bit error
> rates approaching 10^-12 is taken out of service.  This is roughly
> equivalent to the old ES (errored seconds) and SES (severely errored
> seconds) metric where a ES is one second with any bit errors and an
> SES is one second with 10 or more errors (I think its 10).  More than
> some number of ES or SES and a link is taken down.  The uncorrected
> errors are passed through.
>
> A packet may traverse an entire continent with 2-3 such links
> separated by regeneration or could stop at a number of routers along
> the way.  Typically today the router uses 10GbE or 100GbE (growing
> use) which are then passed as a bit stream in the transport network.
> At the other end the uncorrected errors from transport are picked up
> by Ethernet 32 bit FCS.  Since a 32 bit FCS picks up 100% of single
> bit errors and most instances where a small number of bits are in
> error, and all but 1 in 2^32 where many bits are in error, few errors
> are going to get through.  If GFP is used, the per packet FCS is
> checked at each hop and for GFP-T also checked end to end.
>
> A bad local ethernet is more likely to contribute an error (again
> better than 1 in 2^32 detection is expected) due to something like a
> bad CAT-{5,5e,6} connection or too many sharp turns.  A DSL or DOCSIS
> link is also more likely to contribute an error.  With CRC32 on all
> links and no bad hardware in between (ie: circa 1990s equipment with
> no parity RAM and no correction on DMA, buses, etc) you would expect
> on the order of 10^-8 errors (10^-9 per hop, a few errored hops).
>
> For example, two hosts on my home LAN had non-zero tcp checksums.
> Each had < 10^-6 packet error rate.  It is hard to tell if this is
> host errors at the other end.  The only hosts I have with non-zero are
> on the service provider DMZ LAN so that would include any bot attacks,
> etc, where sending hosts could be old junk.  Host behind those have
> zero UDP and TCP checksum errors.  This seems similar to Stewart's
> quick check.
>
> In the T1/T3 days the transport layer just had parity and just counted
> parity errors.  Providers in those days were notorious for ignoring ES
> and SES counters until the customer complained.  HDLC then had its 16
> bit CRC, optional 32 bit.  If an ISP wasn't paying attention to their
> HDLC error counters then it was up to the IP end customer to complain
> and hope the problem got escallated rather than dropped.
>
> </ot>
>
> As to whether congestion control is in practice needed see
> http://www.ietf.org/mail-archive/web/mpls/current/msg11222.html
>
> Its fine to make them both optional and to make congestion control
> mechanisms out of scope and the topic of a later document if needed.
>
> Curtis
>
>
>
> > ________________________________________
> > From: ietf [ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern [jmh@jo=
elhalpern.com]
> > Sent: 10 January 2014 15:36
> > To: Eggert, Lars; Xuxiaohu
> > Cc: mpls@ietf.org; IETF
> > Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating =
MPLS in UDP) to Proposed Standard
> >
> > Maybe I am completely missing things, but this looks wrong.
> > If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> > control will make it more likely that the service won't work.  Is that
> > really the goal?
> >
> > We do not perform congestion control on MPLS LSPs.
> > Assuming that a UDP tunnel is carrying just MPLS and was established
> > just for MPLS, why would we expect it to behave differently than an MPL=
S
> > LSP running over the exact same path, carrying the exact same traffic?
> >
> > Yours,
> > Joel
> >
> > On 1/10/14 3:47 AM, Eggert, Lars wrote:
> > > Hi,
> > >
> > > that sounds good. What congestion control are you going to be specify=
ing for your tunnel?
> > >
> > > Lars
> > >
> > > On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> > >
> > >> Hi Lars,
> > >>
> > >> Thanks a lot for your comments.
> > >>
> > >> I wonder whether the following modified text for Congestion Consider=
ation section is OK from your point of view:
> > >>
> > >> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwar=
ded through "UDP tunnels", the congestion control guidelines for UDP tunnel=
s as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically=
, MPLS can carry a number of different protocols as payloads. When the payl=
oad traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NO=
T employ its own congestion control mechanism, because congestion losses of=
 tunneled traffic will already trigger an appropriate congestion response a=
t the original senders of the tunneled traffic. When the payload traffic is=
 not known to be IP-based, or is known to be IP-based but not congestion-co=
ntrolled, the UDP tunnel SHOULD employ an appropriate congestion control me=
chanism. Furthermore, because UDP tunnels are usually bulk-transfer applica=
tions as far as the intermediate routers are concerned, the guidelines as d=
efined in Section 3.1.1 of [RFC5405] SHOULD apply.
> > >>
> > >> Best regards,
> > >> Xiaohu
> > >>
> > >>> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > >>> =B7=A2=BC=FE=C8=CB: mpls [mailto:mpls-bounces@ietf.org] =B4=FA=B1=
=ED Eggert, Lars
> > >>> =B7=A2=CB=CD=CA=B1=BC=E4: 2014=C4=EA1=D4=C28=C8=D5 18:22
> > >>> =CA=D5=BC=FE=C8=CB: IETF
> > >>> =B3=AD=CB=CD: mpls@ietf.org
> > >>> =D6=F7=CC=E2: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt>=
 (Encapsulating MPLS
> > >>> in UDP) to Proposed Standard
> > >>>
> > >>> Hi,
> > >>>
> > >>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> > >>>> - 'Encapsulating MPLS in UDP'
> > >>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
> > >>>
> > >>>
> > >>> this document needs to describe how it addresses the issues raised =
in BCP145
> > >>> (RFC5405). It already contains some text about messages sizes and c=
ongestion
> > >>> considerations, which is great. Unfortunately, the text about conge=
stion
> > >>> considerations is not fully in line with RFC5405.
> > >>>
> > >>> Lars
> > >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
>
>

From l.wood@surrey.ac.uk  Tue Jan 14 21:46:42 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39191AE2D5; Tue, 14 Jan 2014 21:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzo_5OTM5n58; Tue, 14 Jan 2014 21:46:41 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 2645A1AE1BF; Tue, 14 Jan 2014 21:46:41 -0800 (PST)
Received: from [85.158.136.51:38639] by server-13.bemta-5.messagelabs.com id 56/97-11357-5B026D25; Wed, 15 Jan 2014 05:46:29 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-49.messagelabs.com!1389764788!23096706!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14276 invoked from network); 15 Jan 2014 05:46:28 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-16.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 15 Jan 2014 05:46:28 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 15 Jan 2014 05:46:27 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>, <lars@netapp.com>
Date: Wed, 15 Jan 2014 05:45:43 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8RjS132P0/ZYvoS3qqFjAC/swR5wAJ9pSN
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346CA@EXMB01CMS.surrey.ac.uk>
References: Your message of "Tue, 14 Jan 2014 15:29:38 +0000." <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>, <201401150100.s0F10C7J005674@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401150100.s0F10C7J005674@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 05:46:43 -0000

this draft should be about mpls in TCP - a TCP tunnel.

That will fix all congestion concerns.

I look forward to reading justification of why TCP checksums can be turned =
off.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: mpls [mpls-bounces@ietf.org] On Behalf Of Curtis Villamizar [curtis@i=
pv6.occnc.com]
Sent: 15 January 2014 01:00
To: Eggert, Lars
Cc: mpls@ietf.org; Scott Brim; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt>  (Encapsulat=
ing MPLS in UDP) to Proposed Standard

In message <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
"Eggert, Lars" writes:

> Hi,
>
> On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> > Isn't that basically the problem of the inner traffic sender, not the
> > problem of the tunnel that is carrying the traffic?
>
> no, because the sender of the inner traffic may be blasting some
> L2traffic, for an L2 where that is OK behavior. But that traffic is
> nowbeing encapsulated inside UDP and can hence go anywhere on the
> net*without the sender being aware of this*.

That application would be a PW application and it would be more
appropriate to fix that in PW if there is consensus for a need to do
so, which afaik there is not.

> > Asking tunnel's to solve the problem of applications with
> > undesirablebehavior seems backwards.
>
> It is the *tunnel* that performs the encapsulation and allows
> thattraffic to go places it couldn't before. And so it's the
> tunnel'sresponsibility to make sure that the traffic it injects into
> theInternet complies with the BCPs we have on congestion control.
>
> Lars

If it is a service provider encapsulating traffic within their own
network, then they know what they are doing.  That is the anticipated
use and among that community there is no consensus for need for
congestion control.

If it is some hostile hosts trying to send MPLS over UDP over IP,
they, being hostile, are going to disable any congestion control.
Besides, no hostile host has a T1 to tunnel over the Internet so they
would be sending the same traffic they would normally just send of UDP
over IP.

Anything made up of frames (Ethernet, ATM, FR) over PW over MPLS is
carrying IP and if frames drop, the IP applications see the drop and
behave just as they would for any drop.  (ATM shreadding thread to
/dev/null please).

If congestion aware or using a congestion aware transport, the top
level applications are still congestion aware.  If congestion
ignoreant, they are still congestion ignoreant.  If hostile, they are
still hostile.

Back to draft-ietf-mpls-in-udp.  I think the most recent text proposed
by the author is fine.

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

From abdussalambaryun@gmail.com  Tue Jan 14 21:47:00 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96C3E1AE2F1; Tue, 14 Jan 2014 21:47:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KYX1HXym6gOO; Tue, 14 Jan 2014 21:46:58 -0800 (PST)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 56CA81AE2EE; Tue, 14 Jan 2014 21:46:54 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so644332pde.41 for <multiple recipients>; Tue, 14 Jan 2014 21:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bBzQTB+LwOoLW+YEm/gsBwuvAVIRjw1l/CevGTLpWS0=; b=F32UKyeWTRTMdqfvFIyuJEc5eHw1Idlo8vVTs7fOLsDK0RsN60bDCgBTnRnNIx6IhA OROOQQ6JKEhR5IyGlRi2RXA9WH1+bEuVdQqsrIFcwKfKSmDHrd5JjEEsC4/fBKKyXwVD /BXMUR/sDbrmCrjHfQ/CcJV0Ug5xarPhgIwnhDs2SBlr4WF5G+w9QUfOT4HQ6nvSdyh1 jBZn4tIl9AoWraoFBLDUcTCT8F1O1Pn3gmXi0Bj8c6glhv0dx3kwDF9lcXhvMVA6n4Vf 5UA79F0Qyiun/U1gqm8irwZUuNflutYJDpz+QinYTwoo1jflfq5KU+fZsG+tY/zNYCIS tCUg==
MIME-Version: 1.0
X-Received: by 10.68.229.36 with SMTP id sn4mr315952pbc.23.1389764802895; Tue, 14 Jan 2014 21:46:42 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Tue, 14 Jan 2014 21:46:42 -0800 (PST)
In-Reply-To: <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com>
Date: Wed, 15 Jan 2014 06:46:42 +0100
Message-ID: <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 05:47:00 -0000

Thanks Fred,

The draft must include your questions, so that it can become a clear
initial-BCP, or a clear plan draft. IMHO, the initial-BCP draft is not
clear or not direct if it does not mention your questions,

AB

On 1/14/14, Fred Baker (fred) <fred@cisco.com> wrote:
>
> On Jan 13, 2014, at 11:28 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
> wrote:
>
>>  It means
>>   that, if asked, there needs to be a good answer to the question "is
>>   pervasive monitoring relevant to this work and if so how has it been
>>   considered?"
>
> Just a thought - that might be a good question to add to the shepherd's
> report.
>
> In that case, I might suggest a minor change, however. We discuss "Pervasive
> monitoring" in a "big brother is watching" sense, and (at least in perpass)
> concern ourselves with data that could have been hidden had encryption or
> some other code used. I'll argue that, however dreadful Big Brother might
> be, location-based services can be a lot scarier.
>
> http://online.wsj.com/news/articles/SB10001424052702303453004579290632128929194?mg=reno64-wsj&url=http%3A%2F%2Fonline.wsj.com%2Farticle%2FSB10001424052702303453004579290632128929194.html
>
> Data point: a lot of these operate without specific knowledge of an
> individual, but can. For example, the article talks a lot about aggregating
> information and providing it without identifying information. However, it
> goes on to say that if someone logs into a service using, for example, a
> Facebook identifier, they can remain identified to the system as they wander
> around in it. The messages themselves contain no identifying information per
> se, but they contain information that can be correlated back to that login.
> And the login wasn't "data in flight", it was "creating state with a service
> at rest".
>
> So the question in the shepherd's report should not be "tell me you thought
> about the EU Data Retention Initiative and whether your protocol's data
> identifies an individual". It should be "what personal, equipment, or
> session identifiers, encrypted or otherwise, are carried in your protocol?
> How might they be correlated with offline data or otherwise used to infer
> the identity or behavior of an individual?"
>

From fred@cisco.com  Wed Jan 15 00:01:09 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 400B91AE31D; Wed, 15 Jan 2014 00:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.039
X-Spam-Level: 
X-Spam-Status: No, score=-110.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J4LYxEZu0Syy; Wed, 15 Jan 2014 00:01:08 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) by ietfa.amsl.com (Postfix) with ESMTP id 09F921AE317; Wed, 15 Jan 2014 00:01:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1113; q=dns/txt; s=iport; t=1389772856; x=1390982456; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+qt8Wp8e3tnGjyXs5z30MckuWJ3rOqZie71mdJ/+jtc=; b=Dz/DSWC0m1spxmljGaLJeW7/xl2kxZYKQNj3tJ/jgJqaZZ5FDHvRd7Pf 1QAhvz6n1tXP2T9sW2Mc4KB/zfWQnb4NqcExvFvqlUPi25nMn+NXKTxEy SsBL35XzgXJNOZufpKYWyM2jMQoUfSgvtJGUvWHOZKYUwvbUUMKDC4iI0 s=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AikFAP8+1lKtJV2b/2dsb2JhbABagwuBDrp+gRUWdIIlAQEBBHkQAgEIEgYuIREXDgIEDgUOh2IDEb4ADYVhF4x0ghMHgySBEwSQN4ExhEqBbIxahTuDLYIq
X-IronPort-AV: E=Sophos;i="4.95,661,1384300800";  d="asc'?scan'208";a="12965277"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP; 15 Jan 2014 08:00:56 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0F80uTa025058 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 15 Jan 2014 08:00:56 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.230]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Wed, 15 Jan 2014 02:00:56 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
Thread-Topic: draft-farrell-perpass-attack architecture issue
Thread-Index: AQHPEJW1zBILpAAtaEWpS3JElCG6BZqFJ00AgACGcgCAACV9gA==
Date: Wed, 15 Jan 2014 08:00:55 +0000
Message-ID: <6F7415D3-E58B-46F4-BF51-9E139AD0FDC1@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com> <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com>
In-Reply-To: <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.117]
Content-Type: multipart/signed; boundary="Apple-Mail=_E2B94636-9C25-4B4E-992B-0ABB04F57931"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 08:01:09 -0000

--Apple-Mail=_E2B94636-9C25-4B4E-992B-0ABB04F57931
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jan 14, 2014, at 9:46 PM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:
> The draft must include your questions, so that it can become a clear =
initial-BCP, or a clear plan draft. IMHO, the initial-BCP draft is not =
clear or not direct if it does not mention your questions,

I'm just one. But from my perspective, it must not only ask them, but =
answer them or outline how the answers might be arrived at.

--Apple-Mail=_E2B94636-9C25-4B4E-992B-0ABB04F57931
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFS1kA1bjEdbHIsm0MRAn4kAJ4tDfNlopnuO0fH9gdHAmlVx7/sCwCgluoe
LB39jyXptfH/B2NJAY1Cqog=
=nDUX
-----END PGP SIGNATURE-----

--Apple-Mail=_E2B94636-9C25-4B4E-992B-0ABB04F57931--

From abdussalambaryun@gmail.com  Wed Jan 15 04:36:40 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13FF11AE06B; Wed, 15 Jan 2014 04:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcscUIeGyrwx; Wed, 15 Jan 2014 04:36:38 -0800 (PST)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 81E681ADF72; Wed, 15 Jan 2014 04:36:38 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id um1so1086045pbc.20 for <multiple recipients>; Wed, 15 Jan 2014 04:36:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kTc52thK6RbASixTX5QLvb+VHzbZ0jQh9st9YXYcNv0=; b=W5kneW7BkTAeBaRvkH/yYo6t9KxLghiuXs6wOqfOFalihD9sOTWTN6vvzK9OqadDG4 guemjpWR++0Xrp1MHUrKpKuSFt5gzRP9gWE5z/SHUdYyC+KeW5Td1hXBawhYEwa9Coo2 wT2zKp5bLJFs1y/tUYOEmKWrnjgIUPHK+mw0B5TWjeZOj4/s6GzRawYfAaZ4JEFcrJLt xfXsdjkaAJ8np52AMCtW53DxiQGlhv0m9KSobXQrCHBsX8ZFPN/fI7I1FQEHKTUFoieD EJl364t8ndC2+Ob8su3D8l6gvEUyaYVrGdVOMUIgIMAmAmwPf+G8K4OWJyl0KWlVAmxv 4gbQ==
MIME-Version: 1.0
X-Received: by 10.66.145.166 with SMTP id sv6mr2424454pab.31.1389789386936; Wed, 15 Jan 2014 04:36:26 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 15 Jan 2014 04:36:26 -0800 (PST)
In-Reply-To: <6F7415D3-E58B-46F4-BF51-9E139AD0FDC1@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com> <CADnDZ89sD-VtetCT6fcNrgzkjSMftZQpu+Khjpe8yPtVKnSqvA@mail.gmail.com> <6F7415D3-E58B-46F4-BF51-9E139AD0FDC1@cisco.com>
Date: Wed, 15 Jan 2014 13:36:26 +0100
Message-ID: <CADnDZ8-8voKSELyZPupppCQ-w5rVEzptieyt+rsUL69wKp-Ltg@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: multipart/alternative; boundary=047d7b6783f6b896fa04f0018e62
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 12:36:40 -0000

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

I agree with you but it seems like many ADs want this draft passed as BCP
(without stating it as initial or clear directions), so I may see many
others want to state directions, not much details, therefore, making strong
principle questions will make the initial draft effort clear and understood
to all participants and all directors ( I think that directors should work
more hard to make directions in the draft more clear to community).

AB

On Wednesday, January 15, 2014, Fred Baker (fred) wrote:

>
> On Jan 14, 2014, at 9:46 PM, Abdussalam Baryun <abdussalambaryun@gmail.com<javascript:;>>
> wrote:
> > The draft must include your questions, so that it can become a clear
> initial-BCP, or a clear plan draft. IMHO, the initial-BCP draft is not
> clear or not direct if it does not mention your questions,
>
> I'm just one. But from my perspective, it must not only ask them, but
> answer them or outline how the answers might be arrived at.
>

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

I agree with you but it seems like many ADs want this draft passed as BCP (=
without stating it as initial or clear directions),=A0so I may see many oth=
ers=A0want to state directions, not much details,=A0therefore, making stron=
g principle=A0questions will make the initial draft=A0effort clear and unde=
rstood to all participants and all directors ( I think=A0that directors sho=
uld work more hard to make directions in the draft more clear to community)=
.=A0<div>
<br><div>AB<br><br>On Wednesday, January 15, 2014, Fred Baker (fred)  wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><br>
On Jan 14, 2014, at 9:46 PM, Abdussalam Baryun &lt;<a href=3D"javascript:;"=
 onclick=3D"_e(event, &#39;cvml&#39;, &#39;abdussalambaryun@gmail.com&#39;)=
">abdussalambaryun@gmail.com</a>&gt; wrote:<br>
&gt; The draft must include your questions, so that it can become a clear i=
nitial-BCP, or a clear plan draft. IMHO, the initial-BCP draft is not clear=
 or not direct if it does not mention your questions,<br>
<br>
I&#39;m just one. But from my perspective, it must not only ask them, but a=
nswer them or outline how the answers might be arrived at.<br>
</blockquote></div></div>

--047d7b6783f6b896fa04f0018e62--

From Alexander.Vainshtein@ecitele.com  Wed Jan 15 03:54:33 2014
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B68F01AE099; Wed, 15 Jan 2014 03:54:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IOlBlzvmBw69; Wed, 15 Jan 2014 03:54:31 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0016.outbound.protection.outlook.com [213.199.154.16]) by ietfa.amsl.com (Postfix) with ESMTP id A4AF21AE085; Wed, 15 Jan 2014 03:54:30 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) with Microsoft SMTP Server (TLS) id 15.0.851.11; Wed, 15 Jan 2014 11:54:17 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Wed, 15 Jan 2014 11:54:17 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Topic: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Index: AQHPEeVeWllrh86W50KmWq92akl6n5qFqI4g
Date: Wed, 15 Jan 2014 11:54:17 +0000
Message-ID: <eaca6d98b34045ba9e08c43417507997@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com> <m2a9exmrja.wl%randy@psg.com> <52D67186.8080008@cisco.com>
In-Reply-To: <52D67186.8080008@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.234.56.21]
x-forefront-prvs: 00922518D8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(679001)(689001)(779001)(252514010)(51704005)(13464003)(24454002)(199002)(189002)(377454003)(479174003)(77982001)(65816001)(74662001)(80022001)(66066001)(79102001)(74366001)(92566001)(74876001)(76786001)(76576001)(76796001)(74502001)(63696002)(47446002)(31966008)(59766001)(81686001)(74316001)(56776001)(87266001)(85852003)(69226001)(54356001)(85306002)(76482001)(87936001)(56816005)(90146001)(83072002)(2656002)(46102001)(47976001)(81816001)(15975445006)(81342001)(50986001)(74706001)(93136001)(53806001)(51856001)(80976001)(83322001)(4396001)(54316002)(19580395003)(93516001)(49866001)(81542001)(19580405001)(47736001)(33646001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB532; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:147.234.56.21; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:18:41 -0800
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "jnc@mit.edu" <jnc@mit.edu>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:54:33 -0000

Stewart, and all,
I fully agree that UDP checksums is not a real-life issue with the protocol=
 in question. They could probably help to check corrupted packets if corrup=
tion happens when a packet passes thru a router (i.e. when the ingress data=
 link FCS has already been terminated and the egress data link FCS has not =
been generated yet). But this is hopefully rare - and since MPLS does not c=
are about it, why should the MPLS encapsulator care?

I also do not think that congestion control is a serious issue for this pro=
tocol, not in the least because the primary purpose of this protocol is ECM=
P.

But I would like to understand whether this protocol can really result in r=
easonable distribution of traffic. "Reasonable" means that (a) there is suf=
ficient entropy and (b) that the order in specific micro-flows is preserved=
. The draft skips this issue (unless you consider a recommendation to use a=
 fixed  randomly selected source port value if the tunnel does not need ECM=
P a valid answer) .

Any ideas as to how reasonable distribution of traffic  can be achieved wit=
h this protocol?=20

Regards,
       Sasha=20
Email: Alexander.Vainshtein@ecitele.com
Mobile: 054-9266302

> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Wednesday, January 15, 2014 1:31 PM
> To: Randy Bush
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org;
> wes@mti-systems.com; tsvwg@ietf.org; jnc@mit.edu
> Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gr=
e-in-
> udp draft (was: RE: Milestones changed for tsvwg WG))
>=20
> On 15/01/2014 11:08, Randy Bush wrote:
> > [ you insist on cc:ing me, so you get to endure my opinions ]
> >
> >> it seems that there are no valid statistics for the current Internet
> >> to sustain your case.
> > as we discussed privately, there seem to be no real measurements to
> > sustain any case.  this is all conjecturbation.
> >
> > what i do not understand is why, given the lack of solid evidence that
> > we are in a safe space, you and others are not willing to spend a few
> > euro cents to have a reasonable level of assurance at this layer.
> >
> > randy
> Randy,
>=20
> It is not a few cents, it is likely the re-engineering of a lot of silico=
n.
>=20
> The reason that UDP is of interest is that the on path silicon knows how =
to
> process it, for example it knows how to to ECMP it.
>=20
> The reason that the UDP c/s is a problem for a tunneler is that it needs =
to
> have access to the whole pkt to calculate the c/s, but as you know the si=
licon
> optimised that access away a long time ago.
>=20
> The alternative would be UDP-lite, but the ability of on path silicon to =
process
> that as competently and as completely as it processes UDP is by no means
> clear.
>=20
> - Stewart
>=20
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From curtis@ipv6.occnc.com  Tue Jan 14 09:06:40 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D00F1AE129; Tue, 14 Jan 2014 09:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FV6exKOHUBXZ; Tue, 14 Jan 2014 09:06:37 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id CDDC21AE0FF; Tue, 14 Jan 2014 09:06:36 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0EH6Fbo099057; Tue, 14 Jan 2014 12:06:15 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: OT (was Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))
In-reply-to: Your message of "Sun, 12 Jan 2014 21:22:58 +0000." <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
Date: Tue, 14 Jan 2014 12:06:15 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:19:21 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, adrian@olddog.co.uk, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 14 Jan 2014 17:06:40 -0000

Lloyd,

Maybe you should reread the paper too before citing it as evidence.
Check the date on it.  Check the cited causes of errors.

Packet traces from 1998 and 1999 are prehaps not so relevante today,
particularly wrt error rates due to hosts, router memories, and link
error rates.  Look at the cited caused of errors and realize that many
things have changed.

The largest single error in the paper (paerhaps as high as 99.9% of
the errors) was the ACK-of-FIN bug in Windows NT.  They may have fixed
that by now.  Other large causes were host hardware and host software
bugs (sent bad data in the first place).

One fifth of campus errors were caused by two hosts.  This is cited as
a bug in Mac OS on Powermac 8100, fixed at the time of publication.

A lot of host software errors are discussed, where the checksums are
sent bad and therefore will pass any router link FCS.

Sending host hardware errors were thought to be in large part caused
by no data integrity check on host DMA transfers.  I think progress
has been made on that front.  You can check PCIe.  It has a 32bit CRC
per lane in the link layer and retransmits on error.

Router memory errors was thought to play a large role in the non-host
part of the error rate in the paper.  Routers use ECC now.  Going that
far back they didn't always have parity RAM (and sometimes ran parity
disabled to avoid parity error reloads).

VJHC software errors?  Anyone still use VJHC?  Those errors should be
gone.

IP over HDLC over T1 missed a few errors at the link layer in those
days.  That could be true and occurances dependent on the providers.
In the paper that was thought to be a very small contributor.

Both HDLC and PPP had an option for 16 bit or 32 bit FCS.  Often 16
bit was used.  Some HDLC equipment could be and was configured to
count errors and send the packets on their way on the assumption that
it was better to count errors and deliver bad packets rather than
deliver no packet.  Perhaps also to hide packet loss.  Today all of
the link layers in use have 32 bit FCS and count and toss errored
packets.  In most equipment all of the memories have ECC and all of
the buses ECC or FCS if serialized.

It is now 14 years since that paper was published in Signcomm and 16
years since some of the observations.  Things have changed.  Nice bit
of nostangia but that paper may no longer be relevant.

Curtis

reference -
http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf

In message <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
> 
> Curtis
>  
> I suggest reading Stone's work, particularly
> ''When The CRC and TCP Checksum Disagree'
> for discussion of corruption.
>  
> Particularly its conclusions: 'In the internet, that means
> we are sending large volumes of incorrect data without
> anyone noticing'.
>  
> The Layer-2 check is per link, not end-to-end. That matters.
>  
> The MPLS assumption is that it crosses a link with a frame
> checksum. Putting MPLS over UDP breaks that assumption.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 12 January 2014 18:09
> To: Wood L  Dr (Electronic Eng)
> Cc: adrian@olddog.co.uk; randy@psg.com; gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>  
> In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>  
> > On nested checksums, the question is how they are nested; it's a matter
> > of scope. With a bunch of checksums checking only a payload and any
> > inner checksums like Russian Matryoshka dolls, the end-to-end argument
> > tells us that for reliable receipt of the payload, only the innermost checksum
> > matters.
> >
> > But here, we are not solely checking the payload, but information on how to
> > deliver and identify that payload - and while an outer Ethernet CRC is across
> > the last link, the UDP checksum, though weak, provides a check on the IP
> > addresses and UDP ports (via the  pseudoheader check) and MPLS stack
> > from UDP/IP source to UDP/IP destination (and the payload, which is the bit
> > everyone focuses on as the performance hit as redundant and a processing
> > cost when the payload has its own check, and the bit that UDP-Lite can leave out).
> >
> > Nothing else checks that scope. The scope is wider, and affects the network
> > as a whole. Errors in these unchecked fields lead to misdirection and lead to
> > misdelivery. Or pollution of other ports.
> >
> > The MPLS assumption is that it's protected and checked by a strong link CRC like
> > Ethernet, and checked/regenerated by stack processing between hops; here,
> > in a path context, with zero UDP checksums MPLS has no checking at all.
>  
> That UDP would be running over IP over Ethernet or POS or GFP or ...
>  
> There is no layer-2 currently in use that does not have a robust FCS,
> generally a 32 FCS and therefore the MPLS assumption of checking at a
> lower layer is still valid.
>  
> Curtis
>  
>  
> > "consequences for cheap hardware and for software implementations"
> >
> > I'm sorry, when was MPLS cheap?
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: Adrian Farrel [adrian@olddog.co.uk]
> > Sent: 09 January 2014 10:21
> > To: Wood L  Dr (Electronic Eng); randy@psg.com
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> > Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
> >
> > Lloyd and Randy,
> >
> > With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls, so
> > thanks for the comments.
> >
> > We did take the precaution of sending this I-D for an early TSV Directorate
> > review because of the concern about a number of factors and the overlap with
> > tsvwg work, but the review came back "clean". Of course, such a review is just
> > one person, so this conversation is good.
> >
> > Wrt zero checksum, where do you stand on nested checksums? There is some claim
> > that they represent a waste of processing. I am not convinced by that when each
> > layer is using dedicated hardware (that can presumably process checksums at line
> > speed), but I am interested in the consequences for cheap hardware and for
> > software implementations (as have been claimed to be some of the motivations for
> > this work).
> >
> > Other TSV-related issues that surely pop up are:
> > - allocation of ports for foo-in-UDP
> > - congestion control
> >
> > Please note that there are a number of I-Ds that you missed in your broad sweep
> > of "I am opposed". You should probably look at the NVGRE and VXLAN work (which I
> > think is lurking around the NVO3 working group) because that is also looking at
> > UDP encaps of a tunnelling protocol.
> >
> > Thanks,
> > Adrian
> >
> > Health warnings:
> > I am responsible AD for draft-ietf-mpls-in-udp
> > I am a co-author of the gre-in-udp draft.
> >
> > > -----Original Message-----
> > > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
> > > Sent: 09 January 2014 08:07
> > > To: randy@psg.com
> > > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com;
> > > tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> > > Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:
> > > [tsvwg] Milestones changed for tsvwg WG)
> > >
> > > Randy,
> > >
> > > okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
> > > consensus on  it. And then the authors can adopt that consensus for
> > mpls-in-udp,
> > > which overlaps in authorship...
> > >
> > > thanks,
> > >
> > > Lloyd Wood
> > > http://about.me/lloydwood
> > > ________________________________________
> > > From: Randy Bush [randy@psg.com]
> > > Sent: 09 January 2014 07:51
> > > To: Wood L  Dr (Electronic Eng)
> > > Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org;
> > > jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
> > > Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg]
> > > Milestones changed for tsvwg WG)
> > >
> > > > Because they specify zero UDP checksums,
> > > > I oppose publication of draft-ietf-mpls-in-udp in its current form
> > > > I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current
> > > form.
> > > > I oppose the IETF lisp documents.
> > >
> > > lloyd,
> > >
> > > i think i understand your position.  but i disagree with preventing wg
> > > adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
> > > see wg adoption as how we get to discuss and work on a document, not as
> > > approval of the document.  as david said, i think we need to discuss it
> > > so we can decide if it should be fixed.  to do so, we have to adopt it.
> > >
> > > randy


From curtis@ipv6.occnc.com  Tue Jan 14 09:25:50 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BAD1AE1EE for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 09:25:50 -0800 (PST)
X-Quarantine-ID: <0oNy9FbPcrHN>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char B4 hex): Subject: Re: \264\360\270\264: [mpls] Las[...]
X-Spam-Flag: NO
X-Spam-Score: -0.573
X-Spam-Level: 
X-Spam-Status: No, score=-0.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, SUBJECT_NEEDS_ENCODING=0.049, SUBJ_ILLEGAL_CHARS=1.518] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0oNy9FbPcrHN for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 09:25:50 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 233511AE19A for <ietf@ietf.org>; Tue, 14 Jan 2014 09:25:43 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0EHPN6T099308; Tue, 14 Jan 2014 12:25:23 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401141725.s0EHPN6T099308@maildrop2.v6ds.occnc.com>
To: Xuxiaohu <xuxiaohu@huawei.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: ´ð¸´: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 03:32:09 +0000." <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08244868@NKGEML512-MBS.china.huawei.com>
Date: Tue, 14 Jan 2014 12:25:23 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:19:58 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 14 Jan 2014 17:25:51 -0000

In message <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08244868@NKGEML512-MBS.china.huawei.com>
Xuxiaohu writes:
 
> Hi Curtis and Joel,
>  
> Thanks a lot for your detailed comments.
>  
> Hi Lars,
>  
> I wonder whether the following compromised text for the Congestion
> Consideration section of this doc is roughly acceptable to you.
>  
>    Since the MPLS-in-UDP encapsulation causes MPLS packets to be
>    forwarded through "UDP tunnels", the congestion control guidelines
>    for UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be
>    followed. Specifically, MPLS can carry a number of different
>    protocols as payloads. When the MPLS payload traffic is IP-based
>    and congestion-controlled, the UDP tunnel SHOULD NOT employ its own
>    congestion control mechanism, because congestion losses of tunneled
>    traffic will already trigger an appropriate congestion response at
>    the original senders of the tunneled traffic. When the MPLS payload
>    traffic is not known to be IP-based, or is known to be IP-based but
>    not congestion-controlled, the UDP tunnel SHOULD employ an
>    appropriate congestion control mechanism which is outside the scope
>    of this document.
> 
> Best regards,
> Xiaohu

This works for me.  If deployments indicate a need for congestion
control another document can be written.  I doubt it will be needed.
If someone (Lars perhaps) feels a pressing need to wirte a congestion
control for MPLS over UDP document (or for any tunneling over UDP)
regardless of deployment experience, then they can go ahead.

Whether it works for Lars may be the issue.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 14 12:54:32 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8CF1AE1A4; Tue, 14 Jan 2014 12:54:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trCvhlGHGOvf; Tue, 14 Jan 2014 12:54:29 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5071ADF99; Tue, 14 Jan 2014 12:54:29 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0EKsADA001944; Tue, 14 Jan 2014 15:54:11 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401142054.s0EKsADA001944@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 08:28:05 +0000." <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>
Date: Tue, 14 Jan 2014 15:54:10 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:20:11 -0800
Cc: mpls@ietf.org, xuxiaohu@huawei.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 14 Jan 2014 20:54:32 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> It stands to reason that if tunnelers can turn off udp checksums
> because their performance is degraded, they can turn off
> congestion control because it will degrade their performance.
>  
> Rest of the internet getting congested and getting
> misdelivered corrupted packets? Really not their problem.
>  
> There are important vendors trying to sell products here,
> and they need performance to do so.
> Get with the program!
>  
> Lloyd Wood
> http://about.me/lloydwood


OK, perhaps if you are running MPLS/UDP/IP over HDLC and the HDLC
configuration is set to count FCS errors but not drop you will still
*really* need the UDP checksum.  Otherwise its isn't going to do much
for you.  Any checksum is really bad for some types of errors such as
chunk reordering and multiple bit errors.

Maybe on HDLC or PPP with 16 bit CRC you may see a low error rate, but
in theory that would be much less than 10^-5 since few multiple bit
errors will be coincidence match the CRC, even for a 16 bit CRC.

I suspect most routers would be able to do the checksum anyway and for
modern links if they come up with a zero error count that's fine.

<ot>

Modern OTN based transport networks use forward error correction FEC
which accounts for a fair amount of overhead and a lot of processing
gates on the receiving end.  The measure of effectiveness of given FEC
is in dB with 10 dB being a reduction of a factor of 10 in bit errors
and typical FEC in the high tens of dB.  The target corrected error
rate is often 10^-15 or one bit error in 24 hours for 10 Gb/s, one bit
error in 2.5 hours for 100 Gb/s.  Any link with corrected bit error
rates approaching 10^-12 is taken out of service.  This is roughly
equivalent to the old ES (errored seconds) and SES (severely errored
seconds) metric where a ES is one second with any bit errors and an
SES is one second with 10 or more errors (I think its 10).  More than
some number of ES or SES and a link is taken down.  The uncorrected
errors are passed through.

A packet may traverse an entire continent with 2-3 such links
separated by regeneration or could stop at a number of routers along
the way.  Typically today the router uses 10GbE or 100GbE (growing
use) which are then passed as a bit stream in the transport network.
At the other end the uncorrected errors from transport are picked up
by Ethernet 32 bit FCS.  Since a 32 bit FCS picks up 100% of single
bit errors and most instances where a small number of bits are in
error, and all but 1 in 2^32 where many bits are in error, few errors
are going to get through.  If GFP is used, the per packet FCS is
checked at each hop and for GFP-T also checked end to end.

A bad local ethernet is more likely to contribute an error (again
better than 1 in 2^32 detection is expected) due to something like a
bad CAT-{5,5e,6} connection or too many sharp turns.  A DSL or DOCSIS
link is also more likely to contribute an error.  With CRC32 on all
links and no bad hardware in between (ie: circa 1990s equipment with
no parity RAM and no correction on DMA, buses, etc) you would expect
on the order of 10^-8 errors (10^-9 per hop, a few errored hops).

For example, two hosts on my home LAN had non-zero tcp checksums.
Each had < 10^-6 packet error rate.  It is hard to tell if this is
host errors at the other end.  The only hosts I have with non-zero are
on the service provider DMZ LAN so that would include any bot attacks,
etc, where sending hosts could be old junk.  Host behind those have
zero UDP and TCP checksum errors.  This seems similar to Stewart's
quick check.

In the T1/T3 days the transport layer just had parity and just counted
parity errors.  Providers in those days were notorious for ignoring ES
and SES counters until the customer complained.  HDLC then had its 16
bit CRC, optional 32 bit.  If an ISP wasn't paying attention to their
HDLC error counters then it was up to the IP end customer to complain
and hope the problem got escallated rather than dropped.

</ot>

As to whether congestion control is in practice needed see
http://www.ietf.org/mail-archive/web/mpls/current/msg11222.html

Its fine to make them both optional and to make congestion control
mechanisms out of scope and the topic of a later document if needed.

Curtis



> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern [jmh@joelhalpern.com]
> Sent: 10 January 2014 15:36
> To: Eggert, Lars; Xuxiaohu
> Cc: mpls@ietf.org; IETF
> Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> Maybe I am completely missing things, but this looks wrong.
> If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> control will make it more likely that the service won't work.  Is that
> really the goal?
>  
> We do not perform congestion control on MPLS LSPs.
> Assuming that a UDP tunnel is carrying just MPLS and was established
> just for MPLS, why would we expect it to behave differently than an MPLS
> LSP running over the exact same path, carrying the exact same traffic?
>  
> Yours,
> Joel
>  
> On 1/10/14 3:47 AM, Eggert, Lars wrote:
> > Hi,
> >
> > that sounds good. What congestion control are you going to be specifying for your tunnel?
> >
> > Lars
> >
> > On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> >
> >> Hi Lars,
> >>
> >> Thanks a lot for your comments.
> >>
> >> I wonder whether the following modified text for Congestion Consideration section is OK from your point of view:
> >>
> >> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarded through "UDP tunnels", the congestion control guidelines for UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically, MPLS can carry a number of different protocols as payloads. When the payload traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NOT employ its own congestion control mechanism, because congestion losses of tunneled traffic will already trigger an appropriate congestion response at the original senders of the tunneled traffic. When the payload traffic is not known to be IP-based, or is known to be IP-based but not congestion-controlled, the UDP tunnel SHOULD employ an appropriate congestion control mechanism. Furthermore, because UDP tunnels are usually bulk-transfer applications as far as the intermediate routers are concerned, the guidelines as defined in Section 3.1.1 of [RFC5405] SHOULD apply.
> >>
> >> Best regards,
> >> Xiaohu
> >>
> >>> -----ÓÊ¼þÔ­¼þ-----
> >>> ·¢¼þÈË: mpls [mailto:mpls-bounces@ietf.org] ´ú±í Eggert, Lars
> >>> ·¢ËÍÊ±¼ä: 2014Äê1ÔÂ8ÈÕ 18:22
> >>> ÊÕ¼þÈË: IETF
> >>> ³­ËÍ: mpls@ietf.org
> >>> Ö÷Ìâ: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS
> >>> in UDP) to Proposed Standard
> >>>
> >>> Hi,
> >>>
> >>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> >>>> - 'Encapsulating MPLS in UDP'
> >>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
> >>>
> >>>
> >>> this document needs to describe how it addresses the issues raised in BCP145
> >>> (RFC5405). It already contains some text about messages sizes and congestion
> >>> considerations, which is great. Unfortunately, the text about congestion
> >>> considerations is not fully in line with RFC5405.
> >>>
> >>> Lars
> >
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From curtis@ipv6.occnc.com  Tue Jan 14 16:40:55 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D21FE1AE194; Tue, 14 Jan 2014 16:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p8fZwABG8QJj; Tue, 14 Jan 2014 16:40:54 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 10B7F1ADF47; Tue, 14 Jan 2014 16:40:53 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F0eZXj005169; Tue, 14 Jan 2014 19:40:35 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150040.s0F0eZXj005169@maildrop2.v6ds.occnc.com>
To: "Eggert, Lars" <lars@netapp.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 15:20:17 +0000." <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
Date: Tue, 14 Jan 2014 19:40:34 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:20:39 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 00:40:56 -0000

In message <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
"Eggert, Lars" writes:
 
> On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
> > Yes, the inner (real) transport header is the only meaningful place
> > to apply congestion avoidance.
>  
> But what if the inner traffic isn't congestion controlled?
>  
> Lars


Lars,

The exact same thing will happen in all of the following cases:

  NON-congestion controlled application --over--
  UDP --over-- IP --over-- L2

  NON-congestion controlled application --over--
  UDP --over-- IP --over-- MPLS --over-- L2

  NON-congestion controlled application --over--
  UDP --over-- IP --over-- MPLS --over-- UDP --over-- IP --over-- L2

The non-congestion controlled application is what needs fixing.

It would be wrong to try to put congestion control at every layer
underneath the non-congestion controlled application except perhaps as
a transparent replacement for UDP and that is out of scope for a
draft-ietf-mpls-in-udp discussion.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 14 16:46:42 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7541AE1C9; Tue, 14 Jan 2014 16:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RS8B2miUdmOu; Tue, 14 Jan 2014 16:46:41 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id BA3E81AE1B0; Tue, 14 Jan 2014 16:46:40 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F0kQr8005435; Tue, 14 Jan 2014 19:46:26 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150046.s0F0kQr8005435@maildrop2.v6ds.occnc.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 10:23:59 -0500." <52D5568F.2070600@joelhalpern.com>
Date: Tue, 14 Jan 2014 19:46:26 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:20:57 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 00:46:42 -0000

In message <52D5568F.2070600@joelhalpern.com>
"Joel M. Halpern" writes:
 
> Isn't that basically the problem of the inner traffic sender, not the 
> problem of the tunnel that is carrying the traffic?
> Asking tunnel's to solve the problem of applications with undesirable 
> behavior seems backwards.
>  
> Yours,
> Joel


Or perhaps the job of some form of very fair AQM like SFQ.

Any tunneling complicates the AQM notion of what a flow is and
therefore may affect its assessment of what is fair in bad ways.

This too is out of scope for a draft-ietf-mpls-in-udp discussion.

Curtis


> On 1/14/14 10:20 AM, Eggert, Lars wrote:
> > On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
> >> Yes, the inner (real) transport header is the only meaningful place
> >> to apply congestion avoidance.
> >
> > But what if the inner traffic isn't congestion controlled?
> >
> > Lars

From curtis@ipv6.occnc.com  Tue Jan 14 17:00:27 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3901D1AE008; Tue, 14 Jan 2014 17:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_37=0.6, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PYBy_y0qPvtu; Tue, 14 Jan 2014 17:00:26 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id B20381ADFDD; Tue, 14 Jan 2014 17:00:25 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F10C7J005674; Tue, 14 Jan 2014 20:00:12 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150100.s0F10C7J005674@maildrop2.v6ds.occnc.com>
To: "Eggert, Lars" <lars@netapp.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 15:29:38 +0000." <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
Date: Tue, 14 Jan 2014 20:00:12 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:21:48 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 01:00:27 -0000

In message <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
"Eggert, Lars" writes:
 
> Hi,
>  
> On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> > Isn't that basically the problem of the inner traffic sender, not the 
> > problem of the tunnel that is carrying the traffic?
>  
> no, because the sender of the inner traffic may be blasting some
> L2traffic, for an L2 where that is OK behavior. But that traffic is
> nowbeing encapsulated inside UDP and can hence go anywhere on the
> net*without the sender being aware of this*.

That application would be a PW application and it would be more
appropriate to fix that in PW if there is consensus for a need to do
so, which afaik there is not.

> > Asking tunnel's to solve the problem of applications with
> > undesirablebehavior seems backwards.
>  
> It is the *tunnel* that performs the encapsulation and allows
> thattraffic to go places it couldn't before. And so it's the
> tunnel'sresponsibility to make sure that the traffic it injects into
> theInternet complies with the BCPs we have on congestion control.
>  
> Lars

If it is a service provider encapsulating traffic within their own
network, then they know what they are doing.  That is the anticipated
use and among that community there is no consensus for need for
congestion control.

If it is some hostile hosts trying to send MPLS over UDP over IP,
they, being hostile, are going to disable any congestion control.
Besides, no hostile host has a T1 to tunnel over the Internet so they
would be sending the same traffic they would normally just send of UDP
over IP.

Anything made up of frames (Ethernet, ATM, FR) over PW over MPLS is
carrying IP and if frames drop, the IP applications see the drop and
behave just as they would for any drop.  (ATM shreadding thread to
/dev/null please).

If congestion aware or using a congestion aware transport, the top
level applications are still congestion aware.  If congestion
ignoreant, they are still congestion ignoreant.  If hostile, they are
still hostile.

Back to draft-ietf-mpls-in-udp.  I think the most recent text proposed
by the author is fine.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 14 17:13:56 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51A4B1AE119; Tue, 14 Jan 2014 17:13:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdF59sbrdKAy; Tue, 14 Jan 2014 17:13:55 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id C1A6C1ADFD1; Tue, 14 Jan 2014 17:13:54 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F1DXSN005803; Tue, 14 Jan 2014 20:13:42 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150113.s0F1DXSN005803@maildrop2.v6ds.occnc.com>
To: Wesley Eddy <wes@mti-systems.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 11:22:02 -0500." <52D5642A.7090103@mti-systems.com>
Date: Tue, 14 Jan 2014 20:13:33 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:22:21 -0800
Cc: IETF discussion list <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 01:13:56 -0000

In message <52D5642A.7090103@mti-systems.com>
Wesley Eddy writes:
 
> On 1/14/2014 11:06 AM, Eggert, Lars wrote:
> > Hi,
> > 
> > On 2014-1-14, at 16:39, Scott Brim <scott.brim@gmail.com> wrote:
> >> Lars, I know we're repeating arguments from the last decade. The
> >> choice is between (1) specifying congestion control around the
> >> substrate UDP that can be turned off if it causes problems, or (2)
> >> specifying nothing at this time and adding it later if operators want
> >> it.
> >>
> >> I guess if this can be written as a SHOULD, up to the implementor's
> >> discretion, then okay.
> > 
> > I don't think we can leave this up to implementors discretion. We've had IETF consensus that Internet communication requires congestion control at least since RFC2914. A circuit breaker mechanisms seems straightforward to implement.
> > 
> > As is, I object to this document going forward. The minor benefits of getting some better load balancing for MPLS are far outweighed by the risks.
> > 
> > (I'm also going to shut up now, and let others speak. I think I've said my bit.)
> > 
>  
>  
> I'm in basic agreement.
>  
> Assuming we might all agree that there are conceivable scenarios where
> a circuit breaker mechanism would be useful, is the real issue that
> we don't all agree that it could be implemented in a way that's not
> burdensome and doesn't degrade performance unnecessarily?
>  
> Or is there still fundamental disagreement about whether the scenarios
> where the circuit breaker is useful are even valid?


A circuit breaker (drop all traffic on sign of congestion) at the MPLS
over UDP level would be the worst thing you could specify and IMO it
would guarentee zero implementations.

A circuit breaker might be appropriate for TDM over PW but nothing
else.  This makes sense because TDM cannot change its bandwidth so the
only choice is to shut it off.  TDM over PW is an application that can
run over MPLS (or GRE or L2TP).  The best place to put that circuit
breaker (if anywhere at all) is in TDM over PW.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 14 17:42:52 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14E131AE29F for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 17:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4n52dQruk5oP for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 17:42:49 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4301AE25B for <ietf@ietf.org>; Tue, 14 Jan 2014 17:42:49 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F1gVJP006084; Tue, 14 Jan 2014 20:42:31 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150142.s0F1gVJP006084@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 14 Jan 2014 21:44:29 +0000." <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.uk>
Date: Tue, 14 Jan 2014 20:42:31 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:22:39 -0800
Cc: mpls@ietf.org, ietf@ietf.org, xuxiaohu@huawei.com, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 01:42:52 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> The HDLC part here is last link, not the scope of the whole path.  Any
> 'low' bit error rate given actually becomes quite high once you
> consider no of bits per packet and line rate...
>  
> Do read Jonathan Stone's papers on where errors creep in - not just in
> the link, by at any point along the path, including regeneration
>  
> Lloyd Wood


Lloyd,

There is no HDLC hop.  No one has used HDLC for internet
infrastructure in ages.  It was a joke, like Scott's comment on
wanting to use X.25.  HDLC was disappearing when the Stone/Partridge
Sigcomm 2000 paper was written.

Links please.  And how old is that paper?  Not another 15 year old
work is it?

If you have one bit error per day, how many packets do you lose that
day?  (hint: one).

If you have one bit error per day, how many undetactable packet errors
do you have?  (hint: crc32 gets all one bit errors, therefore zero).

10^-12 bit errors is one per 10 second on 100 Gb/s, one per 100 second
on 10 Gb/s and is generally considered high enough to take a link down
immediately.  A 1500 byte packet is 12,000 bits, about ~10^4.  That
would yield a packet rate as high as 10^-8 if bit errors were mostly
one bit error per packet.  In that case all errors would be
detectable.  It is only when there are a lot of bit errors or more per
packet that the CRC can be defeated and then its about 10^-9 chance.

So at an error rate much less than 10^-8 packets (tightly bunched
errors with multiple bit errors per packet) some 10^-9 might be
undetectable with a CRC32.  One packet every 10^6 seconds at 100 Gb/s
could have an undetectable error.  About one undetectable error a day
or one a week for continuous full out 100 Gb/s link.

Note that the same low error rate does not apply to a GbE or 10GbE
over colored optics over ROADM in the metro since there is no FEC
there.  It also may not apply to the enterprise or campus Ethernets.
In those hops the error rate is likely to be higher.  Needless to say,
wireless hops can have very high error rates.

This is why it could make sense to have the UDP checksum optional in
MPLS over UDP.  It wouldn't hurt to provide the checksums but in some
cases it might be OK to disable them.  That is what SHOULD is for in
an IETF document.

Curtis


> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 14 January 2014 20:54
> To: Wood L  Dr (Electronic Eng)
> Cc: jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@huawei.com; mpls@ietf.org; ietf@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> In message <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>  
> > It stands to reason that if tunnelers can turn off udp checksums
> > because their performance is degraded, they can turn off
> > congestion control because it will degrade their performance.
> >
> > Rest of the internet getting congested and getting
> > misdelivered corrupted packets? Really not their problem.
> >
> > There are important vendors trying to sell products here,
> > and they need performance to do so.
> > Get with the program!
> >
> > Lloyd Wood
> > http://about.me/lloydwood
>  
>  
> OK, perhaps if you are running MPLS/UDP/IP over HDLC and the HDLC
> configuration is set to count FCS errors but not drop you will still
> *really* need the UDP checksum.  Otherwise its isn't going to do much
> for you.  Any checksum is really bad for some types of errors such as
> chunk reordering and multiple bit errors.
>  
> Maybe on HDLC or PPP with 16 bit CRC you may see a low error rate, but
> in theory that would be much less than 10^-5 since few multiple bit
> errors will be coincidence match the CRC, even for a 16 bit CRC.
>  
> I suspect most routers would be able to do the checksum anyway and for
> modern links if they come up with a zero error count that's fine.
>  
> <ot>
>  
> Modern OTN based transport networks use forward error correction FEC
> which accounts for a fair amount of overhead and a lot of processing
> gates on the receiving end.  The measure of effectiveness of given FEC
> is in dB with 10 dB being a reduction of a factor of 10 in bit errors
> and typical FEC in the high tens of dB.  The target corrected error
> rate is often 10^-15 or one bit error in 24 hours for 10 Gb/s, one bit
> error in 2.5 hours for 100 Gb/s.  Any link with corrected bit error
> rates approaching 10^-12 is taken out of service.  This is roughly
> equivalent to the old ES (errored seconds) and SES (severely errored
> seconds) metric where a ES is one second with any bit errors and an
> SES is one second with 10 or more errors (I think its 10).  More than
> some number of ES or SES and a link is taken down.  The uncorrected
> errors are passed through.
>  
> A packet may traverse an entire continent with 2-3 such links
> separated by regeneration or could stop at a number of routers along
> the way.  Typically today the router uses 10GbE or 100GbE (growing
> use) which are then passed as a bit stream in the transport network.
> At the other end the uncorrected errors from transport are picked up
> by Ethernet 32 bit FCS.  Since a 32 bit FCS picks up 100% of single
> bit errors and most instances where a small number of bits are in
> error, and all but 1 in 2^32 where many bits are in error, few errors
> are going to get through.  If GFP is used, the per packet FCS is
> checked at each hop and for GFP-T also checked end to end.
>  
> A bad local ethernet is more likely to contribute an error (again
> better than 1 in 2^32 detection is expected) due to something like a
> bad CAT-{5,5e,6} connection or too many sharp turns.  A DSL or DOCSIS
> link is also more likely to contribute an error.  With CRC32 on all
> links and no bad hardware in between (ie: circa 1990s equipment with
> no parity RAM and no correction on DMA, buses, etc) you would expect
> on the order of 10^-8 errors (10^-9 per hop, a few errored hops).
>  
> For example, two hosts on my home LAN had non-zero tcp checksums.
> Each had < 10^-6 packet error rate.  It is hard to tell if this is
> host errors at the other end.  The only hosts I have with non-zero are
> on the service provider DMZ LAN so that would include any bot attacks,
> etc, where sending hosts could be old junk.  Host behind those have
> zero UDP and TCP checksum errors.  This seems similar to Stewart's
> quick check.
>  
> In the T1/T3 days the transport layer just had parity and just counted
> parity errors.  Providers in those days were notorious for ignoring ES
> and SES counters until the customer complained.  HDLC then had its 16
> bit CRC, optional 32 bit.  If an ISP wasn't paying attention to their
> HDLC error counters then it was up to the IP end customer to complain
> and hope the problem got escallated rather than dropped.
>  
> </ot>
>  
> As to whether congestion control is in practice needed see
> http://www.ietf.org/mail-archive/web/mpls/current/msg11222.html
>  
> Its fine to make them both optional and to make congestion control
> mechanisms out of scope and the topic of a later document if needed.
>  
> Curtis
>  
>  
>  
> > ________________________________________
> > From: ietf [ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern [jmh@joelhalpern.com]
> > Sent: 10 January 2014 15:36
> > To: Eggert, Lars; Xuxiaohu
> > Cc: mpls@ietf.org; IETF
> > Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
> >
> > Maybe I am completely missing things, but this looks wrong.
> > If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> > control will make it more likely that the service won't work.  Is that
> > really the goal?
> >
> > We do not perform congestion control on MPLS LSPs.
> > Assuming that a UDP tunnel is carrying just MPLS and was established
> > just for MPLS, why would we expect it to behave differently than an MPLS
> > LSP running over the exact same path, carrying the exact same traffic?
> >
> > Yours,
> > Joel
> >
> > On 1/10/14 3:47 AM, Eggert, Lars wrote:
> > > Hi,
> > >
> > > that sounds good. What congestion control are you going to be specifying for your tunnel?
> > >
> > > Lars
> > >
> > > On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> > >
> > >> Hi Lars,
> > >>
> > >> Thanks a lot for your comments.
> > >>
> > >> I wonder whether the following modified text for Congestion Consideration section is OK from your point of view:
> > >>
> > >> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarded through "UDP tunnels", the congestion control guidelines for UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically, MPLS can carry a number of different protocols as payloads. When the payload traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NOT employ its own congestion control mechanism, because congestion losses of tunneled traffic will already trigger an appropriate congestion response at the original senders of the tunneled traffic. When the payload traffic is not known to be IP-based, or is known to be IP-based but not congestion-controlled, the UDP tunnel SHOULD employ an appropriate congestion control mechanism. Furthermore, because UDP tunnels are usually bulk-transfer applications as far as the intermediate routers are concerned, the guidelines as defined in Section 3.1.1 of [RFC5405] SHOULD apply.
> > >>
> > >> Best regards,
> > >> Xiaohu
> > >>
> > >>> -----ÓÊ¼þÔ­¼þ-----
> > >>> ·¢¼þÈË: mpls [mailto:mpls-bounces@ietf.org] ´ú±í Eggert, Lars
> > >>> ·¢ËÍÊ±¼ä: 2014Äê1ÔÂ8ÈÕ 18:22
> > >>> ÊÕ¼þÈË: IETF
> > >>> ³­ËÍ: mpls@ietf.org
> > >>> Ö÷Ìâ: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS
> > >>> in UDP) to Proposed Standard
> > >>>
> > >>> Hi,
> > >>>
> > >>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> > >>>> - 'Encapsulating MPLS in UDP'
> > >>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
> > >>>
> > >>>
> > >>> this document needs to describe how it addresses the issues raised in BCP145
> > >>> (RFC5405). It already contains some text about messages sizes and congestion
> > >>> considerations, which is great. Unfortunately, the text about congestion
> > >>> considerations is not fully in line with RFC5405.
> > >>>
> > >>> Lars
> > >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls
>  
>  

From curtis@ipv6.occnc.com  Tue Jan 14 19:30:06 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94431AE261; Tue, 14 Jan 2014 19:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PEO0_74N9T4p; Tue, 14 Jan 2014 19:30:02 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 37E571AE25B; Tue, 14 Jan 2014 19:30:01 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F3TX9p007369; Tue, 14 Jan 2014 22:29:34 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150329.s0F3TX9p007369@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))
In-reply-to: Your message of "Tue, 14 Jan 2014 21:57:20 +0000." <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk>
Date: Tue, 14 Jan 2014 22:29:33 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:22:51 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org, david.black@emc.com, tsvwg@ietf.org, stbryant@cisco.com, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 03:30:07 -0000

Lloyd,

At this point in time those who would know what error rates are for
current technologies are likely to be people who work for transport
vendors, router vendors, and operators and those are the type of
people you have been arguing with.  You don't really think that no one
has thought about improving error rates in 15 years, right?

That said, if an academic can do a direct measurement *today* the
results might add something to the discussion.  A paper that old adds
little for this particualar topic because too much has changed.

I anyone thought today's rates of undetectable errors were a problem
they would be adding something more robust such as a 64 bit CRC to
important link layers.  [Some bandwidth would be chewed up.  TCP ACK
packets would get bigger.  Mpps rates for "small packets" would be
easier to hit.  What's not to like. :-) ]

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:

I don't think sayng 'oh, that error source is no longer a problem' disproves
Stone's overall point about undetected errors, though the
examples he uses from the technology of the day are necessarily
dated. Dismissing the overall  point because the examples use obsolete
technology is throwing the baby out with the bathwater; a host-to-host
error check catches things that intermediate checks cannot.

Measuring error rates across end-to-end  Internet traffic is something that has
not received much attention , as error detection is not
instrumented well - hence citing Stone's published work,  in the absence
of awareness of anything newer (and as high profile/immediately recognisable
as sigcomm) in the area.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stewart Bryant [stbryant@cisco.com]
Sent: 14 January 2014 18:26
To: curtis@ipv6.occnc.com; Wood L  Dr (Electronic Eng)
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; lisp@ietf.org; david.black@emc.com; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu
Subject: Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))

I agree the paper is now obsolete.

Stewart


On 14/01/2014 17:06, Curtis Villamizar wrote:
> Lloyd,
>
> Maybe you should reread the paper too before citing it as evidence.
> Check the date on it.  Check the cited causes of errors.
>
> Packet traces from 1998 and 1999 are prehaps not so relevante today,
> particularly wrt error rates due to hosts, router memories, and link
> error rates.  Look at the cited caused of errors and realize that many
> things have changed.
>
> The largest single error in the paper (paerhaps as high as 99.9% of
> the errors) was the ACK-of-FIN bug in Windows NT.  They may have fixed
> that by now.  Other large causes were host hardware and host software
> bugs (sent bad data in the first place).
>
> One fifth of campus errors were caused by two hosts.  This is cited as
> a bug in Mac OS on Powermac 8100, fixed at the time of publication.
>
> A lot of host software errors are discussed, where the checksums are
> sent bad and therefore will pass any router link FCS.
>
> Sending host hardware errors were thought to be in large part caused
> by no data integrity check on host DMA transfers.  I think progress
> has been made on that front.  You can check PCIe.  It has a 32bit CRC
> per lane in the link layer and retransmits on error.
>
> Router memory errors was thought to play a large role in the non-host
> part of the error rate in the paper.  Routers use ECC now.  Going that
> far back they didn't always have parity RAM (and sometimes ran parity
> disabled to avoid parity error reloads).
>
> VJHC software errors?  Anyone still use VJHC?  Those errors should be
> gone.
>
> IP over HDLC over T1 missed a few errors at the link layer in those
> days.  That could be true and occurances dependent on the providers.
> In the paper that was thought to be a very small contributor.
>
> Both HDLC and PPP had an option for 16 bit or 32 bit FCS.  Often 16
> bit was used.  Some HDLC equipment could be and was configured to
> count errors and send the packets on their way on the assumption that
> it was better to count errors and deliver bad packets rather than
> deliver no packet.  Perhaps also to hide packet loss.  Today all of
> the link layers in use have 32 bit FCS and count and toss errored
> packets.  In most equipment all of the memories have ECC and all of
> the buses ECC or FCS if serialized.
>
> It is now 14 years since that paper was published in Signcomm and 16
> years since some of the observations.  Things have changed.  Nice bit
> of nostangia but that paper may no longer be relevant.
>
> Curtis
>
> reference -
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf
>
> In message <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>> Curtis
>>
>> I suggest reading Stone's work, particularly
>> ''When The CRC and TCP Checksum Disagree'
>> for discussion of corruption.
>>
>> Particularly its conclusions: 'In the internet, that means
>> we are sending large volumes of incorrect data without
>> anyone noticing'.
>>
>> The Layer-2 check is per link, not end-to-end. That matters.
>>
>> The MPLS assumption is that it crosses a link with a frame
>> checksum. Putting MPLS over UDP breaks that assumption.
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: Curtis Villamizar [curtis@ipv6.occnc.com]
>> Sent: 12 January 2014 18:09
>> To: Wood L  Dr (Electronic Eng)
>> Cc: adrian@olddog.co.uk; randy@psg.com; gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>>
>> In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
>> l.wood@surrey.ac.uk writes:
>>
>>> On nested checksums, the question is how they are nested; it's a matter
>>> of scope. With a bunch of checksums checking only a payload and any
>>> inner checksums like Russian Matryoshka dolls, the end-to-end argument
>>> tells us that for reliable receipt of the payload, only the innermost checksum
>>> matters.
>>>
>>> But here, we are not solely checking the payload, but information on how to
>>> deliver and identify that payload - and while an outer Ethernet CRC is across
>>> the last link, the UDP checksum, though weak, provides a check on the IP
>>> addresses and UDP ports (via the  pseudoheader check) and MPLS stack
>>> from UDP/IP source to UDP/IP destination (and the payload, which is the bit
>>> everyone focuses on as the performance hit as redundant and a processing
>>> cost when the payload has its own check, and the bit that UDP-Lite can leave out).
>>>
>>> Nothing else checks that scope. The scope is wider, and affects the network
>>> as a whole. Errors in these unchecked fields lead to misdirection and lead to
>>> misdelivery. Or pollution of other ports.
>>>
>>> The MPLS assumption is that it's protected and checked by a strong link CRC like
>>> Ethernet, and checked/regenerated by stack processing between hops; here,
>>> in a path context, with zero UDP checksums MPLS has no checking at all.
>>
>> That UDP would be running over IP over Ethernet or POS or GFP or ...
>>
>> There is no layer-2 currently in use that does not have a robust FCS,
>> generally a 32 FCS and therefore the MPLS assumption of checking at a
>> lower layer is still valid.
>>
>> Curtis
>>
>>
>>> "consequences for cheap hardware and for software implementations"
>>>
>>> I'm sorry, when was MPLS cheap?
>>>
>>> Lloyd Wood
>>> http://about.me/lloydwood
>>> ________________________________________
>>> From: Adrian Farrel [adrian@olddog.co.uk]
>>> Sent: 09 January 2014 10:21
>>> To: Wood L  Dr (Electronic Eng); randy@psg.com
>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>> Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>>>
>>> Lloyd and Randy,
>>>
>>> With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls, so
>>> thanks for the comments.
>>>
>>> We did take the precaution of sending this I-D for an early TSV Directorate
>>> review because of the concern about a number of factors and the overlap with
>>> tsvwg work, but the review came back "clean". Of course, such a review is just
>>> one person, so this conversation is good.
>>>
>>> Wrt zero checksum, where do you stand on nested checksums? There is some claim
>>> that they represent a waste of processing. I am not convinced by that when each
>>> layer is using dedicated hardware (that can presumably process checksums at line
>>> speed), but I am interested in the consequences for cheap hardware and for
>>> software implementations (as have been claimed to be some of the motivations for
>>> this work).
>>>
>>> Other TSV-related issues that surely pop up are:
>>> - allocation of ports for foo-in-UDP
>>> - congestion control
>>>
>>> Please note that there are a number of I-Ds that you missed in your broad sweep
>>> of "I am opposed". You should probably look at the NVGRE and VXLAN work (which I
>>> think is lurking around the NVO3 working group) because that is also looking at
>>> UDP encaps of a tunnelling protocol.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> Health warnings:
>>> I am responsible AD for draft-ietf-mpls-in-udp
>>> I am a co-author of the gre-in-udp draft.
>>>
>>>> -----Original Message-----
>>>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
>>>> Sent: 09 January 2014 08:07
>>>> To: randy@psg.com
>>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com;
>>>> tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:
>>>> [tsvwg] Milestones changed for tsvwg WG)
>>>>
>>>> Randy,
>>>>
>>>> okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
>>>> consensus on  it. And then the authors can adopt that consensus for
>>> mpls-in-udp,
>>>> which overlaps in authorship...
>>>>
>>>> thanks,
>>>>
>>>> Lloyd Wood
>>>> http://about.me/lloydwood
>>>> ________________________________________
>>>> From: Randy Bush [randy@psg.com]
>>>> Sent: 09 January 2014 07:51
>>>> To: Wood L  Dr (Electronic Eng)
>>>> Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org;
>>>> jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
>>>> Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg]
>>>> Milestones changed for tsvwg WG)
>>>>
>>>>> Because they specify zero UDP checksums,
>>>>> I oppose publication of draft-ietf-mpls-in-udp in its current form
>>>>> I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current
>>>> form.
>>>>> I oppose the IETF lisp documents.
>>>> lloyd,
>>>>
>>>> i think i understand your position.  but i disagree with preventing wg
>>>> adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
>>>> see wg adoption as how we get to discuss and work on a document, not as
>>>> approval of the document.  as david said, i think we need to discuss it
>>>> so we can decide if it should be fixed.  to do so, we have to adopt it.
>>>>
>>>> randy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> .
>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html



From curtis@ipv6.occnc.com  Tue Jan 14 19:44:11 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60CC1AE1EF; Tue, 14 Jan 2014 19:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2fVlAnyRXIR; Tue, 14 Jan 2014 19:44:09 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 952DB1AE1E2; Tue, 14 Jan 2014 19:44:09 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0F3hqwR007521; Tue, 14 Jan 2014 22:43:52 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401150343.s0F3hqwR007521@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Tue, 14 Jan 2014 23:05:14 +0000." <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
Date: Tue, 14 Jan 2014 22:43:52 -0500
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:23:08 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, stbryant@cisco.com, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 03:44:12 -0000

Lloyd,

The part about RFC 6936 section 3.1 most relevant might be:

   There is extensive experience with deployments using tunnel
   protocols in well-managed networks (e.g., corporate networks and
   service provider core networks).  This has shown the robustness of
   methods such as Pseudowire Emulation Edge-to-Edge (PWE3) and MPLS
   that do not employ a transport protocol checksum and that have not
   specified mechanisms to protect from corruption of the unprotected
   headers (such as the VPN Identifier in MPLS).  Reasons for the
   robustness may include:

If the rate of undetected modified packets is extremely low in
"well-managed networks", as we beleive is the case, then UDP checksums
won't change the situration much.

So why *not* make them optional if experience has shown they are not
needed in the types of deployments we are talking about.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
> 
> Stewart,
>  
> your 'I'm not in tunnel applications' suggests you've misunderstood
> the argument here. The point is not to protect the tunnel traffic
> (which can quite happily checksum itself), it is to protect everything
> else on the network from misdelivery. It's not the tunnel application,
> it's every application sharing the internet with the tunnel which
> has UDP checksums turned off. See all of  RFC 6936 section 3.1.
> Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.
>  
> And in IPv4 and IPv6, the pseudo-header checksum built into
> TCP and UDP is all we have. IPv6 deliberately copied v4 here.
>  
> > What is the error rate in modern h/w and network systems?
>  
> No-one measures end-to-end misdelivery. No-one knows.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Stewart Bryant [stbryant@cisco.com]
> Sent: 14 January 2014 22:46
> To: Wesley Eddy; Wood L  Dr (Electronic Eng); curtis@ipv6.occnc.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>  
> On 14/01/2014 22:07, Wesley Eddy wrote:
> > On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
> >> I don't think sayng 'oh, that error source is no longer a problem' disproves
> >> Stone's overall point about undetected errors, though the
> >> examples he uses from the technology of the day are necessarily
> >> dated. Dismissing the overall  point because the examples use obsolete
> >> technology is throwing the baby out with the bathwater; a host-to-host
> >> error check catches things that intermediate checks cannot.
> >>
> >> Measuring error rates across end-to-end  Internet traffic is something that has
> >> not received much attention , as error detection is not
> >> instrumented well - hence citing Stone's published work,  in the absence
> >> of awareness of anything newer (and as high profile/immediately recognisable
> >> as sigcomm) in the area.
> >>
> >
> > +1 ... the message in the paper is applicable to layered systems
> > and internetworks in general.  Changes in the link technology
> > since then don't invalidate it, especially since we know that
> > the technology not only changes rapidly, but also is always
> > growing in diverse directions, such that there things almost
> > universally true today may be turned on their heads tomorrow.
> >
> > Designs for stacking layers need to follow solid general
> > principles in order to be robust to changes (above and below).
> >
> Note that it is not only the link layer technology that has moved on,
> the signal integrity of the h/w at all stages of the design and
> implementation process has moved on.
>  
> Can we agree that the statistics in the paper are discredited?
>  
> If not, why not?
>  
> What is the error rate in modern h/w and network systems?
>  
> Is this significant in the application under consideration?
>  
> Finally if we are really concerned that we do actually need a
> c/s (I am not in tunnel applications) why are we still happy to
> use what is frankly a pathetic check in modern terms? Why
> for example are we not moving to something like
> the  Fletcher 64 bit c/s?
>  
> Stewart

From edc@google.com  Tue Jan 14 12:29:10 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF551AE197 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 12:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3_JFFVk9-lfR for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 12:29:08 -0800 (PST)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id F0DA91ADFCA for <ietf@ietf.org>; Tue, 14 Jan 2014 12:29:07 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id z12so892079wgg.18 for <ietf@ietf.org>; Tue, 14 Jan 2014 12:28:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=emwcLnFtoLgKjo5q6JqhNprCT2HKexy5UDuof5KMLCw=; b=P/0cr2aG9vjb1ucgDmqqLh3LTuqSGaYCxHEXzPqJ5WXydECk5G/xuLJzxloYT7zyMN J4IS25xX/mE/D/KYPSA9n1gDOL12aWEN36x7SGeKab5oqix59MZUYQoNF5b2AQq7otHM GMRBHCrC46SrauQk+dC/AG3x7Iuq69kfAppD4mXkMAaOc105G2hXtNSYQ/lAhDjLgoCe ujRYi2gwi6oJzm+/Rd3X2EAu42Vt9pRgcfn7pVOXLuWnhjCowa38apGL8ITQ4k8ouGpo 1NaQYMudteB0tMA8KSLPHzy/OvZSGyYh9Awa4R0eVQdMLOt5Bdxolewh8vu3JfnvupBF 7dCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=emwcLnFtoLgKjo5q6JqhNprCT2HKexy5UDuof5KMLCw=; b=JZ7fACtTg6lmOzXww0LTpFeCvU+DLhlIWFhgrlvQHmAOelthXg2ESHZirznuUnTGCb kHDaMZ9lBgzpm4W4FnjBMwY0KI2R7qC6uG9d3Wqs1wUDPZvYcA6BMK4JBctSjc1RqNjL mR8lyAovwxzI1M6tO3aO6DYq1sXMLhAjjd6HJLhIHxXAy2k5uhAGmjGGjLGmfnXr09ld cNvwGkeppG4hmCSlKr/G89xjwJlOjN0v+DgmGeezlNaAkWLoDhj4ixMD/2XPd6Fg3mTA 60gCayOi4YC4rUzJzk4OXRRtxgos4FsIZ9zf/l27h82AaYknD+Z3Bry+l35BPu+lShrP GdrA==
X-Gm-Message-State: ALoCoQmAvuZ+XeXbjk+eWTD8hf+tX3CpVY8Ho/Yeu5+uFI8RSIRNRfGvPmdpBWJVO/s1HD+d8/qNAIh28/XVDRtsLUR5mjk/3Bvj4p1SyPJGPRx1zkj+k4QIFwppFbFQIVlI2FNvbI18SHAhJgr1M061qQNguRvFidb4i2MxJkB19b0IThvjDsHxhIKE6cxnTOKA0MtTJZ62
X-Received: by 10.180.37.193 with SMTP id a1mr3942567wik.52.1389731336013; Tue, 14 Jan 2014 12:28:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Tue, 14 Jan 2014 12:28:14 -0800 (PST)
In-Reply-To: <52D5568F.2070600@joelhalpern.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com>
From: Edward Crabbe <edc@google.com>
Date: Tue, 14 Jan 2014 12:28:14 -0800
Message-ID: <CACKN6JG0zP6=XYUxG_F-uczQyRPv3p0t5p8vwK6Sy9AyTtjUnA@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=e89a8f502fa09ddfaf04eff40acb
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:24:50 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 20:29:10 -0000

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

+100

the same problem would exist with or without the additional encapsulation
(this includes any L2 encaps that may exist in the case of L2 tunelling.)
 The only difference is /reach/.  This same concern exists *most* common
tunnels types in the internet today.



On Tue, Jan 14, 2014 at 7:23 AM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> Isn't that basically the problem of the inner traffic sender, not the
> problem of the tunnel that is carrying the traffic?
> Asking tunnel's to solve the problem of applications with undesirable
> behavior seems backwards.
>
> Yours,
> Joel
>
>
> On 1/14/14 10:20 AM, Eggert, Lars wrote:
>
>> On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
>>
>>> Yes, the inner (real) transport header is the only meaningful place
>>> to apply congestion avoidance.
>>>
>>
>> But what if the inner traffic isn't congestion controlled?
>>
>> Lars
>>
>>  _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

<div dir=3D"ltr">+100<div><br></div><div>the same problem would exist with =
or without the additional encapsulation (this includes any L2 encaps that m=
ay exist in the case of L2 tunelling.) =A0The only difference is /reach/. =
=A0This same concern exists *most* common tunnels types in the internet tod=
ay.</div>

<div><br></div><div><br></div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Tue, Jan 14, 2014 at 7:23 AM, Joel M. Halpern <span dir=3D"=
ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">jmh@joelh=
alpern.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">Isn&#39;t that basically the problem of the =
inner traffic sender, not the problem of the tunnel that is carrying the tr=
affic?<br>



Asking tunnel&#39;s to solve the problem of applications with undesirable b=
ehavior seems backwards.<br>
<br>
Yours,<br>
Joel<div><div><br>
<br>
On 1/14/14 10:20 AM, Eggert, Lars wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 2014-1-14, at 15:20, Stewart Bryant &lt;<a href=3D"mailto:stbryant@cisco=
.com" target=3D"_blank">stbryant@cisco.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yes, the inner (real) transport header is the only meaningful place<br>
to apply congestion avoidance.<br>
</blockquote>
<br>
But what if the inner traffic isn&#39;t congestion controlled?<br>
<br>
Lars<br>
<br>
</blockquote></div></div><div><div>
______________________________<u></u>_________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/mpls</a><br>
</div></div></blockquote></div><br></div></div>

--e89a8f502fa09ddfaf04eff40acb--

From l.wood@surrey.ac.uk  Tue Jan 14 13:57:46 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C391AE2B8; Tue, 14 Jan 2014 13:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26j5X6uQdZK2; Tue, 14 Jan 2014 13:57:44 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.114]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0E41AE2AF; Tue, 14 Jan 2014 13:57:43 -0800 (PST)
Received: from [193.109.255.147:47627] by server-10.bemta-14.messagelabs.com id D6/81-20752-BC2B5D25; Tue, 14 Jan 2014 21:57:31 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-72.messagelabs.com!1389736650!13624939!3
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13873 invoked from network); 14 Jan 2014 21:57:30 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-14.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 14 Jan 2014 21:57:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 14 Jan 2014 21:57:21 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <curtis@ipv6.occnc.com>
Date: Tue, 14 Jan 2014 21:57:20 +0000
Subject: RE: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))
Thread-Topic: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))
Thread-Index: Ac8RVjUkh7p2kMNVSGWEekhrdASM3gAHBvko
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk>
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>, <52D58168.9060800@cisco.com>
In-Reply-To: <52D58168.9060800@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:25:10 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 21:57:46 -0000

I don't think sayng 'oh, that error source is no longer a problem' disprove=
s
Stone's overall point about undetected errors, though the
examples he uses from the technology of the day are necessarily
dated. Dismissing the overall  point because the examples use obsolete
technology is throwing the baby out with the bathwater; a host-to-host
error check catches things that intermediate checks cannot.

Measuring error rates across end-to-end  Internet traffic is something that=
 has
not received much attention , as error detection is not
instrumented well - hence citing Stone's published work,  in the absence
of awareness of anything newer (and as high profile/immediately recognisabl=
e
as sigcomm) in the area.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stewart Bryant [stbryant@cisco.com]
Sent: 14 January 2014 18:26
To: curtis@ipv6.occnc.com; Wood L  Dr (Electronic Eng)
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; lisp@ietf.org; davi=
d.black@emc.com; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu
Subject: Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp d=
raft (was: RE: [tsvwg] Milestones changed for tsvwg WG))

I agree the paper is now obsolete.

Stewart


On 14/01/2014 17:06, Curtis Villamizar wrote:
> Lloyd,
>
> Maybe you should reread the paper too before citing it as evidence.
> Check the date on it.  Check the cited causes of errors.
>
> Packet traces from 1998 and 1999 are prehaps not so relevante today,
> particularly wrt error rates due to hosts, router memories, and link
> error rates.  Look at the cited caused of errors and realize that many
> things have changed.
>
> The largest single error in the paper (paerhaps as high as 99.9% of
> the errors) was the ACK-of-FIN bug in Windows NT.  They may have fixed
> that by now.  Other large causes were host hardware and host software
> bugs (sent bad data in the first place).
>
> One fifth of campus errors were caused by two hosts.  This is cited as
> a bug in Mac OS on Powermac 8100, fixed at the time of publication.
>
> A lot of host software errors are discussed, where the checksums are
> sent bad and therefore will pass any router link FCS.
>
> Sending host hardware errors were thought to be in large part caused
> by no data integrity check on host DMA transfers.  I think progress
> has been made on that front.  You can check PCIe.  It has a 32bit CRC
> per lane in the link layer and retransmits on error.
>
> Router memory errors was thought to play a large role in the non-host
> part of the error rate in the paper.  Routers use ECC now.  Going that
> far back they didn't always have parity RAM (and sometimes ran parity
> disabled to avoid parity error reloads).
>
> VJHC software errors?  Anyone still use VJHC?  Those errors should be
> gone.
>
> IP over HDLC over T1 missed a few errors at the link layer in those
> days.  That could be true and occurances dependent on the providers.
> In the paper that was thought to be a very small contributor.
>
> Both HDLC and PPP had an option for 16 bit or 32 bit FCS.  Often 16
> bit was used.  Some HDLC equipment could be and was configured to
> count errors and send the packets on their way on the assumption that
> it was better to count errors and deliver bad packets rather than
> deliver no packet.  Perhaps also to hide packet loss.  Today all of
> the link layers in use have 32 bit FCS and count and toss errored
> packets.  In most equipment all of the memories have ECC and all of
> the buses ECC or FCS if serialized.
>
> It is now 14 years since that paper was published in Signcomm and 16
> years since some of the observations.  Things have changed.  Nice bit
> of nostangia but that paper may no longer be relevant.
>
> Curtis
>
> reference -
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pd=
f
>
> In message <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.a=
c.uk>
> l.wood@surrey.ac.uk writes:
>> Curtis
>>
>> I suggest reading Stone's work, particularly
>> ''When The CRC and TCP Checksum Disagree'
>> for discussion of corruption.
>>
>> Particularly its conclusions: 'In the internet, that means
>> we are sending large volumes of incorrect data without
>> anyone noticing'.
>>
>> The Layer-2 check is per link, not end-to-end. That matters.
>>
>> The MPLS assumption is that it crosses a link with a frame
>> checksum. Putting MPLS over UDP breaks that assumption.
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: Curtis Villamizar [curtis@ipv6.occnc.com]
>> Sent: 12 January 2014 18:09
>> To: Wood L  Dr (Electronic Eng)
>> Cc: adrian@olddog.co.uk; randy@psg.com; gorry@erg.abdn.ac.uk; mpls@ietf.=
org; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@=
ietf.org
>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was=
: RE: [tsvwg] Milestones changed for tsvwg WG)
>>
>> In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.=
ac.uk>
>> l.wood@surrey.ac.uk writes:
>>
>>> On nested checksums, the question is how they are nested; it's a matter
>>> of scope. With a bunch of checksums checking only a payload and any
>>> inner checksums like Russian Matryoshka dolls, the end-to-end argument
>>> tells us that for reliable receipt of the payload, only the innermost c=
hecksum
>>> matters.
>>>
>>> But here, we are not solely checking the payload, but information on ho=
w to
>>> deliver and identify that payload - and while an outer Ethernet CRC is =
across
>>> the last link, the UDP checksum, though weak, provides a check on the I=
P
>>> addresses and UDP ports (via the  pseudoheader check) and MPLS stack
>>> from UDP/IP source to UDP/IP destination (and the payload, which is the=
 bit
>>> everyone focuses on as the performance hit as redundant and a processin=
g
>>> cost when the payload has its own check, and the bit that UDP-Lite can =
leave out).
>>>
>>> Nothing else checks that scope. The scope is wider, and affects the net=
work
>>> as a whole. Errors in these unchecked fields lead to misdirection and l=
ead to
>>> misdelivery. Or pollution of other ports.
>>>
>>> The MPLS assumption is that it's protected and checked by a strong link=
 CRC like
>>> Ethernet, and checked/regenerated by stack processing between hops; her=
e,
>>> in a path context, with zero UDP checksums MPLS has no checking at all.
>>
>> That UDP would be running over IP over Ethernet or POS or GFP or ...
>>
>> There is no layer-2 currently in use that does not have a robust FCS,
>> generally a 32 FCS and therefore the MPLS assumption of checking at a
>> lower layer is still valid.
>>
>> Curtis
>>
>>
>>> "consequences for cheap hardware and for software implementations"
>>>
>>> I'm sorry, when was MPLS cheap?
>>>
>>> Lloyd Wood
>>> http://about.me/lloydwood
>>> ________________________________________
>>> From: Adrian Farrel [adrian@olddog.co.uk]
>>> Sent: 09 January 2014 10:21
>>> To: Wood L  Dr (Electronic Eng); randy@psg.com
>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc=
.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>> Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (wa=
s: RE: [tsvwg] Milestones changed for tsvwg WG)
>>>
>>> Lloyd and Randy,
>>>
>>> With respect to draft-ietf-mpls-in-udp, this is why we have IETF last c=
alls, so
>>> thanks for the comments.
>>>
>>> We did take the precaution of sending this I-D for an early TSV Directo=
rate
>>> review because of the concern about a number of factors and the overlap=
 with
>>> tsvwg work, but the review came back "clean". Of course, such a review =
is just
>>> one person, so this conversation is good.
>>>
>>> Wrt zero checksum, where do you stand on nested checksums? There is som=
e claim
>>> that they represent a waste of processing. I am not convinced by that w=
hen each
>>> layer is using dedicated hardware (that can presumably process checksum=
s at line
>>> speed), but I am interested in the consequences for cheap hardware and =
for
>>> software implementations (as have been claimed to be some of the motiva=
tions for
>>> this work).
>>>
>>> Other TSV-related issues that surely pop up are:
>>> - allocation of ports for foo-in-UDP
>>> - congestion control
>>>
>>> Please note that there are a number of I-Ds that you missed in your bro=
ad sweep
>>> of "I am opposed". You should probably look at the NVGRE and VXLAN work=
 (which I
>>> think is lurking around the NVO3 working group) because that is also lo=
oking at
>>> UDP encaps of a tunnelling protocol.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> Health warnings:
>>> I am responsible AD for draft-ietf-mpls-in-udp
>>> I am a co-author of the gre-in-udp draft.
>>>
>>>> -----Original Message-----
>>>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.a=
c.uk
>>>> Sent: 09 January 2014 08:07
>>>> To: randy@psg.com
>>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@em=
c.com;
>>>> tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (w=
as: RE:
>>>> [tsvwg] Milestones changed for tsvwg WG)
>>>>
>>>> Randy,
>>>>
>>>> okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's ge=
t
>>>> consensus on  it. And then the authors can adopt that consensus for
>>> mpls-in-udp,
>>>> which overlaps in authorship...
>>>>
>>>> thanks,
>>>>
>>>> Lloyd Wood
>>>> http://about.me/lloydwood
>>>> ________________________________________
>>>> From: Randy Bush [randy@psg.com]
>>>> Sent: 09 January 2014 07:51
>>>> To: Wood L  Dr (Electronic Eng)
>>>> Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@iet=
f.org;
>>>> jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
>>>> Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:=
 [tsvwg]
>>>> Milestones changed for tsvwg WG)
>>>>
>>>>> Because they specify zero UDP checksums,
>>>>> I oppose publication of draft-ietf-mpls-in-udp in its current form
>>>>> I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its c=
urrent
>>>> form.
>>>>> I oppose the IETF lisp documents.
>>>> lloyd,
>>>>
>>>> i think i understand your position.  but i disagree with preventing wg
>>>> adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strong=
ly
>>>> see wg adoption as how we get to discuss and work on a document, not a=
s
>>>> approval of the document.  as david said, i think we need to discuss i=
t
>>>> so we can decide if it should be fixed.  to do so, we have to adopt it=
.
>>>>
>>>> randy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> .
>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From l.wood@surrey.ac.uk  Tue Jan 14 15:05:58 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBBF1AE2D2; Tue, 14 Jan 2014 15:05:58 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqvsxLNQq3Rn; Tue, 14 Jan 2014 15:05:56 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.161]) by ietfa.amsl.com (Postfix) with ESMTP id 58F8E1AE2B1; Tue, 14 Jan 2014 15:05:55 -0800 (PST)
Received: from [195.245.230.131:34421] by server-1.bemta-3.messagelabs.com id 15/81-29598-5C2C5D25; Tue, 14 Jan 2014 23:05:41 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-78.messagelabs.com!1389740738!32661185!3
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10751 invoked from network); 14 Jan 2014 23:05:41 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-12.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 14 Jan 2014 23:05:41 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 14 Jan 2014 23:05:14 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <wes@mti-systems.com>, <curtis@ipv6.occnc.com>
Date: Tue, 14 Jan 2014 23:05:14 +0000
Subject: RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Topic: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Index: Ac8RenDjEgxt8NsvTwOY15/OAFCPrwAAX68d
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>, <52D58168.9060800@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk> <52D5B524.5080408@mti-systems.com>,<52D5BE37.4070301@cisco.com>
In-Reply-To: <52D5BE37.4070301@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:26:45 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 23:05:58 -0000

Stewart,

your 'I'm not in tunnel applications' suggests you've misunderstood
the argument here. The point is not to protect the tunnel traffic
(which can quite happily checksum itself), it is to protect everything
else on the network from misdelivery. It's not the tunnel application,
it's every application sharing the internet with the tunnel which
has UDP checksums turned off. See all of  RFC 6936 section 3.1.
Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.

And in IPv4 and IPv6, the pseudo-header checksum built into
TCP and UDP is all we have. IPv6 deliberately copied v4 here.

> What is the error rate in modern h/w and network systems?

No-one measures end-to-end misdelivery. No-one knows.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stewart Bryant [stbryant@cisco.com]
Sent: 14 January 2014 22:46
To: Wesley Eddy; Wood L  Dr (Electronic Eng); curtis@ipv6.occnc.com
Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; tsvw=
g@ietf.org; jnc@mit.edu; lisp@ietf.org
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-=
in-udp draft (was: RE: Milestones changed for tsvwg WG))

On 14/01/2014 22:07, Wesley Eddy wrote:
> On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
>> I don't think sayng 'oh, that error source is no longer a problem' dispr=
oves
>> Stone's overall point about undetected errors, though the
>> examples he uses from the technology of the day are necessarily
>> dated. Dismissing the overall  point because the examples use obsolete
>> technology is throwing the baby out with the bathwater; a host-to-host
>> error check catches things that intermediate checks cannot.
>>
>> Measuring error rates across end-to-end  Internet traffic is something t=
hat has
>> not received much attention , as error detection is not
>> instrumented well - hence citing Stone's published work,  in the absence
>> of awareness of anything newer (and as high profile/immediately recognis=
able
>> as sigcomm) in the area.
>>
>
> +1 ... the message in the paper is applicable to layered systems
> and internetworks in general.  Changes in the link technology
> since then don't invalidate it, especially since we know that
> the technology not only changes rapidly, but also is always
> growing in diverse directions, such that there things almost
> universally true today may be turned on their heads tomorrow.
>
> Designs for stacking layers need to follow solid general
> principles in order to be robust to changes (above and below).
>
Note that it is not only the link layer technology that has moved on,
the signal integrity of the h/w at all stages of the design and
implementation process has moved on.

Can we agree that the statistics in the paper are discredited?

If not, why not?

What is the error rate in modern h/w and network systems?

Is this significant in the application under consideration?

Finally if we are really concerned that we do actually need a
c/s (I am not in tunnel applications) why are we still happy to
use what is frankly a pathetic check in modern terms? Why
for example are we not moving to something like
the  Fletcher 64 bit c/s?

Stewart=

From l.wood@surrey.ac.uk  Tue Jan 14 21:21:44 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A33741AE2EE for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 21:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WwBg9ADkam0h for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 21:21:41 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.142]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9421AE2DF for <ietf@ietf.org>; Tue, 14 Jan 2014 21:21:41 -0800 (PST)
Received: from [195.245.231.67:43619] by server-6.bemta-5.messagelabs.com id E9/73-16310-8DA16D25; Wed, 15 Jan 2014 05:21:28 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-82.messagelabs.com!1389763287!33356230!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19034 invoked from network); 15 Jan 2014 05:21:27 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-6.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 15 Jan 2014 05:21:27 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 15 Jan 2014 05:21:27 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Wed, 15 Jan 2014 05:20:27 +0000
Subject: RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Topic: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Index: Ac8RpAQNDX8cAMV9TnqV5Ulgc44euAADXwfJ
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346C7@EXMB01CMS.surrey.ac.uk>
References: Your message of "Tue, 14 Jan 2014 23:05:14 +0000." <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>, <201401150343.s0F3hqwR007521@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401150343.s0F3hqwR007521@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:26:57 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, jnc@mit.edu, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 05:21:44 -0000

That's robustness _for the tunnelled traffic_.

Not for anything else sharing the network - that hasn't been instrumented a=
nd measured.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 15 January 2014 03:43
To: Wood L  Dr (Electronic Eng)
Cc: stbryant@cisco.com; wes@mti-systems.com; curtis@ipv6.occnc.com; gorry@e=
rg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; tsvwg@ietf.org;=
 jnc@mit.edu; lisp@ietf.org
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-=
in-udp draft (was: RE: Milestones changed for tsvwg WG))

Lloyd,

The part about RFC 6936 section 3.1 most relevant might be:

   There is extensive experience with deployments using tunnel
   protocols in well-managed networks (e.g., corporate networks and
   service provider core networks).  This has shown the robustness of
   methods such as Pseudowire Emulation Edge-to-Edge (PWE3) and MPLS
   that do not employ a transport protocol checksum and that have not
   specified mechanisms to protect from corruption of the unprotected
   headers (such as the VPN Identifier in MPLS).  Reasons for the
   robustness may include:

If the rate of undetected modified packets is extremely low in
"well-managed networks", as we beleive is the case, then UDP checksums
won't change the situration much.

So why *not* make them optional if experience has shown they are not
needed in the types of deployments we are talking about.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:
>
> Stewart,
>
> your 'I'm not in tunnel applications' suggests you've misunderstood
> the argument here. The point is not to protect the tunnel traffic
> (which can quite happily checksum itself), it is to protect everything
> else on the network from misdelivery. It's not the tunnel application,
> it's every application sharing the internet with the tunnel which
> has UDP checksums turned off. See all of  RFC 6936 section 3.1.
> Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.
>
> And in IPv4 and IPv6, the pseudo-header checksum built into
> TCP and UDP is all we have. IPv6 deliberately copied v4 here.
>
> > What is the error rate in modern h/w and network systems?
>
> No-one measures end-to-end misdelivery. No-one knows.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Stewart Bryant [stbryant@cisco.com]
> Sent: 14 January 2014 22:46
> To: Wesley Eddy; Wood L  Dr (Electronic Eng); curtis@ipv6.occnc.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; ts=
vwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gr=
e-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>
> On 14/01/2014 22:07, Wesley Eddy wrote:
> > On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
> >> I don't think sayng 'oh, that error source is no longer a problem' dis=
proves
> >> Stone's overall point about undetected errors, though the
> >> examples he uses from the technology of the day are necessarily
> >> dated. Dismissing the overall  point because the examples use obsolete
> >> technology is throwing the baby out with the bathwater; a host-to-host
> >> error check catches things that intermediate checks cannot.
> >>
> >> Measuring error rates across end-to-end  Internet traffic is something=
 that has
> >> not received much attention , as error detection is not
> >> instrumented well - hence citing Stone's published work,  in the absen=
ce
> >> of awareness of anything newer (and as high profile/immediately recogn=
isable
> >> as sigcomm) in the area.
> >>
> >
> > +1 ... the message in the paper is applicable to layered systems
> > and internetworks in general.  Changes in the link technology
> > since then don't invalidate it, especially since we know that
> > the technology not only changes rapidly, but also is always
> > growing in diverse directions, such that there things almost
> > universally true today may be turned on their heads tomorrow.
> >
> > Designs for stacking layers need to follow solid general
> > principles in order to be robust to changes (above and below).
> >
> Note that it is not only the link layer technology that has moved on,
> the signal integrity of the h/w at all stages of the design and
> implementation process has moved on.
>
> Can we agree that the statistics in the paper are discredited?
>
> If not, why not?
>
> What is the error rate in modern h/w and network systems?
>
> Is this significant in the application under consideration?
>
> Finally if we are really concerned that we do actually need a
> c/s (I am not in tunnel applications) why are we still happy to
> use what is frankly a pathetic check in modern terms? Why
> for example are we not moving to something like
> the  Fletcher 64 bit c/s?
>
> Stewart

From l.wood@surrey.ac.uk  Wed Jan 15 04:00:52 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE881AE35A; Wed, 15 Jan 2014 04:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXLAwN-sOj12; Wed, 15 Jan 2014 04:00:50 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.140]) by ietfa.amsl.com (Postfix) with ESMTP id 1E10F1AE099; Wed, 15 Jan 2014 04:00:48 -0800 (PST)
Received: from [85.158.136.51:52908] by server-4.bemta-5.messagelabs.com id 1A/93-26791-46876D25; Wed, 15 Jan 2014 12:00:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-49.messagelabs.com!1389787235!29314441!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 16991 invoked from network); 15 Jan 2014 12:00:35 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-10.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 15 Jan 2014 12:00:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 15 Jan 2014 12:00:35 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <randy@psg.com>
Date: Wed, 15 Jan 2014 11:57:18 +0000
Subject: RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Topic: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
Thread-Index: Ac8R5VMR2UUHMLGDRP+DhjlaFb7ztAAA52BF
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346CB@EXMB01CMS.surrey.ac.uk>
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com> <m2a9exmrja.wl%randy@psg.com>,<52D67186.8080008@cisco.com>
In-Reply-To: <52D67186.8080008@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:27:10 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, tsvwg@ietf.org, curtis@ipv6.occnc.com, jnc@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 12:00:52 -0000

you've got the perfect application to encourage UDP lite adoption and deplo=
yment here.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stewart Bryant [stbryant@cisco.com]
Sent: 15 January 2014 11:31
To: Randy Bush
Cc: Wood L  Dr (Electronic Eng); wes@mti-systems.com; curtis@ipv6.occnc.com=
; gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; jnc@m=
it.edu; lisp@ietf.org
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-=
in-udp draft (was: RE: Milestones changed for tsvwg WG))

On 15/01/2014 11:08, Randy Bush wrote:
> [ you insist on cc:ing me, so you get to endure my opinions ]
>
>> it seems that there are no valid statistics for the current Internet
>> to sustain your case.
> as we discussed privately, there seem to be no real measurements to
> sustain any case.  this is all conjecturbation.
>
> what i do not understand is why, given the lack of solid evidence that
> we are in a safe space, you and others are not willing to spend a few
> euro cents to have a reasonable level of assurance at this layer.
>
> randy
Randy,

It is not a few cents, it is likely the re-engineering of a lot
of silicon.

The reason that UDP is of interest is that the on path silicon
knows how to process it, for example it knows how to to ECMP it.

The reason that the UDP c/s is a problem for a tunneler is that
it needs to have access to the whole pkt to calculate the
c/s, but as you know the silicon optimised that access away
a long time ago.

The alternative would be UDP-lite, but the ability of on path
silicon to process that as competently and as completely as it
processes UDP is by no means clear.

- Stewart



From randy@psg.com  Wed Jan 15 03:08:44 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF32C1AE34D; Wed, 15 Jan 2014 03:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L-R--m2BjUPl; Wed, 15 Jan 2014 03:08:43 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5FD1AE078; Wed, 15 Jan 2014 03:08:43 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W3OKV-0005Bp-1G; Wed, 15 Jan 2014 11:08:16 +0000
Date: Wed, 15 Jan 2014 17:08:09 +0600
Message-ID: <m2a9exmrja.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant <stbryant@cisco.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-Reply-To: <52D66ABC.40606@cisco.com>
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.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: multipart/signed; boundary="pgp-sign-Multipart_Wed_Jan_15_17:08:04_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:27:31 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:08:45 -0000

--pgp-sign-Multipart_Wed_Jan_15_17:08:04_2014-1
Content-Type: text/plain; charset=US-ASCII

[ you insist on cc:ing me, so you get to endure my opinions ]

> it seems that there are no valid statistics for the current Internet
> to sustain your case.

as we discussed privately, there seem to be no real measurements to
sustain any case.  this is all conjecturbation.

what i do not understand is why, given the lack of solid evidence that
we are in a safe space, you and others are not willing to spend a few
euro cents to have a reasonable level of assurance at this layer.

randy
--pgp-sign-Multipart_Wed_Jan_15_17:08:04_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJS1mwYAAoJEMzMBey4OgLt1G8H/1ADrpB+HoSbUN8FTgBHlpk2
GeozioIalHzyBniV8tmqiBFYHwJZC35ylMPig8bCFuVXLpaiYPCUMcQQDb5w9Ck9
OKHupmxO5AiIbPR0PaTLCYzCHU/jNmhz+xMfAarlf8eJ3Nl0p9SdsNVn21GV7i1V
z3+OhlPPDojCxjjQj/9dUW6Cc1PKufrM9ius+eXGUO7iaWd34V5de2laJrM39lr6
yRtmQX9zdZKzfMqNztwAFOl5oK0696k2JlVQi5i2NcSRb6P/GrFZ4aFOgy+18yQ4
LB8gDRgaQ4IhhyVfPrZOZoL3Feukxm7cgRTnEHqJKz+0jhVzEIvmKNfDMe1A+m4=
=4bC4
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Wed_Jan_15_17:08:04_2014-1--

From stbryant@cisco.com  Tue Jan 14 10:27:06 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC6831AE101; Tue, 14 Jan 2014 10:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PJ9XYVg8YGXD; Tue, 14 Jan 2014 10:27:03 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id B34301AE06C; Tue, 14 Jan 2014 10:27:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9804; q=dns/txt; s=iport; t=1389724012; x=1390933612; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=buqbYsHxbFMGj5If0RKN8HQZ1bI9G1YZmgKQfkEtu+U=; b=D7OWqqQoq5EtZSzcvA/g8OnQP3PVO+/BKJZSS+1ncu4+fvcNSXNXMkj4 XtQqqPjqlZag4UMglgIZbRtZjqJJNuy6fS401+6re7VpTrPfk7iHUXVtj SVc7/pkH3ANj4Z8PZwgwEBcbATFRVA0XVrrlfMU1tkRRWSQSoot+chwle Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aq4FAPKA1VKQ/khN/2dsb2JhbABQCg6CfThQumSBFRZ0giUBAQECAgEBATUwBgoBDAQLEQQBAQEJFgQEBwkDAgECARUfAwEFCAcJAwEFAgEBiAAIBcQoF44rOiIHBoQxBJgegTCLLYU4gW9/Pw
X-IronPort-AV: E=Sophos;i="4.95,658,1384300800";  d="scan'208";a="3622779"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 18:26:50 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0EIQnea003901 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 18:26:50 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0EIQm2s008555; Tue, 14 Jan 2014 18:26:48 GMT
Message-ID: <52D58168.9060800@cisco.com>
Date: Tue, 14 Jan 2014 18:26:48 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, l.wood@surrey.ac.uk
Subject: Re: [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG))
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:27:47 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, ietf@ietf.org, david.black@emc.com, tsvwg@ietf.org, jnc@mit.edu, lisp@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 18:27:07 -0000

I agree the paper is now obsolete.

Stewart


On 14/01/2014 17:06, Curtis Villamizar wrote:
> Lloyd,
>
> Maybe you should reread the paper too before citing it as evidence.
> Check the date on it.  Check the cited causes of errors.
>
> Packet traces from 1998 and 1999 are prehaps not so relevante today,
> particularly wrt error rates due to hosts, router memories, and link
> error rates.  Look at the cited caused of errors and realize that many
> things have changed.
>
> The largest single error in the paper (paerhaps as high as 99.9% of
> the errors) was the ACK-of-FIN bug in Windows NT.  They may have fixed
> that by now.  Other large causes were host hardware and host software
> bugs (sent bad data in the first place).
>
> One fifth of campus errors were caused by two hosts.  This is cited as
> a bug in Mac OS on Powermac 8100, fixed at the time of publication.
>
> A lot of host software errors are discussed, where the checksums are
> sent bad and therefore will pass any router link FCS.
>
> Sending host hardware errors were thought to be in large part caused
> by no data integrity check on host DMA transfers.  I think progress
> has been made on that front.  You can check PCIe.  It has a 32bit CRC
> per lane in the link layer and retransmits on error.
>
> Router memory errors was thought to play a large role in the non-host
> part of the error rate in the paper.  Routers use ECC now.  Going that
> far back they didn't always have parity RAM (and sometimes ran parity
> disabled to avoid parity error reloads).
>
> VJHC software errors?  Anyone still use VJHC?  Those errors should be
> gone.
>
> IP over HDLC over T1 missed a few errors at the link layer in those
> days.  That could be true and occurances dependent on the providers.
> In the paper that was thought to be a very small contributor.
>
> Both HDLC and PPP had an option for 16 bit or 32 bit FCS.  Often 16
> bit was used.  Some HDLC equipment could be and was configured to
> count errors and send the packets on their way on the assumption that
> it was better to count errors and deliver bad packets rather than
> deliver no packet.  Perhaps also to hide packet loss.  Today all of
> the link layers in use have 32 bit FCS and count and toss errored
> packets.  In most equipment all of the memories have ECC and all of
> the buses ECC or FCS if serialized.
>
> It is now 14 years since that paper was published in Signcomm and 16
> years since some of the observations.  Things have changed.  Nice bit
> of nostangia but that paper may no longer be relevant.
>
> Curtis
>
> reference -
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf
>
> In message <290E20B455C66743BE178C5C84F1240847E63346BD@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>> Curtis
>>   
>> I suggest reading Stone's work, particularly
>> ''When The CRC and TCP Checksum Disagree'
>> for discussion of corruption.
>>   
>> Particularly its conclusions: 'In the internet, that means
>> we are sending large volumes of incorrect data without
>> anyone noticing'.
>>   
>> The Layer-2 check is per link, not end-to-end. That matters.
>>   
>> The MPLS assumption is that it crosses a link with a frame
>> checksum. Putting MPLS over UDP breaks that assumption.
>>   
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: Curtis Villamizar [curtis@ipv6.occnc.com]
>> Sent: 12 January 2014 18:09
>> To: Wood L  Dr (Electronic Eng)
>> Cc: adrian@olddog.co.uk; randy@psg.com; gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org; david.black@emc.com; jnc@mit.edu; tsvwg@ietf.org
>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>>   
>> In message <290E20B455C66743BE178C5C84F1240847E63346BA@EXMB01CMS.surrey.ac.uk>
>> l.wood@surrey.ac.uk writes:
>>   
>>> On nested checksums, the question is how they are nested; it's a matter
>>> of scope. With a bunch of checksums checking only a payload and any
>>> inner checksums like Russian Matryoshka dolls, the end-to-end argument
>>> tells us that for reliable receipt of the payload, only the innermost checksum
>>> matters.
>>>
>>> But here, we are not solely checking the payload, but information on how to
>>> deliver and identify that payload - and while an outer Ethernet CRC is across
>>> the last link, the UDP checksum, though weak, provides a check on the IP
>>> addresses and UDP ports (via the  pseudoheader check) and MPLS stack
>>> from UDP/IP source to UDP/IP destination (and the payload, which is the bit
>>> everyone focuses on as the performance hit as redundant and a processing
>>> cost when the payload has its own check, and the bit that UDP-Lite can leave out).
>>>
>>> Nothing else checks that scope. The scope is wider, and affects the network
>>> as a whole. Errors in these unchecked fields lead to misdirection and lead to
>>> misdelivery. Or pollution of other ports.
>>>
>>> The MPLS assumption is that it's protected and checked by a strong link CRC like
>>> Ethernet, and checked/regenerated by stack processing between hops; here,
>>> in a path context, with zero UDP checksums MPLS has no checking at all.
>>   
>> That UDP would be running over IP over Ethernet or POS or GFP or ...
>>   
>> There is no layer-2 currently in use that does not have a robust FCS,
>> generally a 32 FCS and therefore the MPLS assumption of checking at a
>> lower layer is still valid.
>>   
>> Curtis
>>   
>>   
>>> "consequences for cheap hardware and for software implementations"
>>>
>>> I'm sorry, when was MPLS cheap?
>>>
>>> Lloyd Wood
>>> http://about.me/lloydwood
>>> ________________________________________
>>> From: Adrian Farrel [adrian@olddog.co.uk]
>>> Sent: 09 January 2014 10:21
>>> To: Wood L  Dr (Electronic Eng); randy@psg.com
>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>> Subject: RE: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg] Milestones changed for tsvwg WG)
>>>
>>> Lloyd and Randy,
>>>
>>> With respect to draft-ietf-mpls-in-udp, this is why we have IETF last calls, so
>>> thanks for the comments.
>>>
>>> We did take the precaution of sending this I-D for an early TSV Directorate
>>> review because of the concern about a number of factors and the overlap with
>>> tsvwg work, but the review came back "clean". Of course, such a review is just
>>> one person, so this conversation is good.
>>>
>>> Wrt zero checksum, where do you stand on nested checksums? There is some claim
>>> that they represent a waste of processing. I am not convinced by that when each
>>> layer is using dedicated hardware (that can presumably process checksums at line
>>> speed), but I am interested in the consequences for cheap hardware and for
>>> software implementations (as have been claimed to be some of the motivations for
>>> this work).
>>>
>>> Other TSV-related issues that surely pop up are:
>>> - allocation of ports for foo-in-UDP
>>> - congestion control
>>>
>>> Please note that there are a number of I-Ds that you missed in your broad sweep
>>> of "I am opposed". You should probably look at the NVGRE and VXLAN work (which I
>>> think is lurking around the NVO3 working group) because that is also looking at
>>> UDP encaps of a tunnelling protocol.
>>>
>>> Thanks,
>>> Adrian
>>>
>>> Health warnings:
>>> I am responsible AD for draft-ietf-mpls-in-udp
>>> I am a co-author of the gre-in-udp draft.
>>>
>>>> -----Original Message-----
>>>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk
>>>> Sent: 09 January 2014 08:07
>>>> To: randy@psg.com
>>>> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; david.black@emc.com;
>>>> tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>>>> Subject: Re: [mpls] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE:
>>>> [tsvwg] Milestones changed for tsvwg WG)
>>>>
>>>> Randy,
>>>>
>>>> okay, let  tsvwg adopt draft-yong-tsvwg-gre-in-udp-encap, and let's get
>>>> consensus on  it. And then the authors can adopt that consensus for
>>> mpls-in-udp,
>>>> which overlaps in authorship...
>>>>
>>>> thanks,
>>>>
>>>> Lloyd Wood
>>>> http://about.me/lloydwood
>>>> ________________________________________
>>>> From: Randy Bush [randy@psg.com]
>>>> Sent: 09 January 2014 07:51
>>>> To: Wood L  Dr (Electronic Eng)
>>>> Cc: david.black@emc.com; gorry@erg.abdn.ac.uk; ietf@ietf.org; mpls@ietf.org;
>>>> jnc@mit.edu; lisp@ietf.org; tsvwg@ietf.org
>>>> Subject: Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: [tsvwg]
>>>> Milestones changed for tsvwg WG)
>>>>
>>>>> Because they specify zero UDP checksums,
>>>>> I oppose publication of draft-ietf-mpls-in-udp in its current form
>>>>> I oppose tsvwg adoption of draft-yong-tsvwg-gre-in-udp-encap in its current
>>>> form.
>>>>> I oppose the IETF lisp documents.
>>>> lloyd,
>>>>
>>>> i think i understand your position.  but i disagree with preventing wg
>>>> adoption of draft-yong-tsvwg-gre-in-udp-encap, mainly because i strongly
>>>> see wg adoption as how we get to discuss and work on a document, not as
>>>> approval of the document.  as david said, i think we need to discuss it
>>>> so we can decide if it should be fixed.  to do so, we have to adopt it.
>>>>
>>>> randy
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From stbryant@cisco.com  Tue Jan 14 14:46:31 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5EF1AE1DA; Tue, 14 Jan 2014 14:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FL7ahKNLKCyc; Tue, 14 Jan 2014 14:46:30 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id B44B91ADFF3; Tue, 14 Jan 2014 14:46:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2042; q=dns/txt; s=iport; t=1389739579; x=1390949179; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=b+SywIMTAblM9fWu2hAcy5jAKn01lzQaY41AddoBwHw=; b=cOu1uNj5AxFHOfLYjoNWnyhK4w0jOorac2i426vRM9UorERgDlLV9WXA xIkEVty/4owA6YAy1Gw00wMRxrPMEGJkeGM/ThzPb0ghWPjyOfMr/ayYy vIpmSj/F4iiyhhVJT9PzfAVmBiRPCcehQqUEQgQOA5B/yZY9o+CLAihhy 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj4FAAq91VKQ/khR/2dsb2JhbABaDoJ9u32BGRZ0giUBAQEEODwEARALDgoJFgQLCQMCAQIBRQYBDAEFAgEBiADEHxePBweENwEDlDiDZpIVgW9/Pw
X-IronPort-AV: E=Sophos;i="4.95,659,1384300800";  d="scan'208";a="3628620"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 14 Jan 2014 22:46:17 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0EMkHAi001167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Jan 2014 22:46:17 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0EMkFsF021730; Tue, 14 Jan 2014 22:46:15 GMT
Message-ID: <52D5BE37.4070301@cisco.com>
Date: Tue, 14 Jan 2014 22:46:15 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Wesley Eddy <wes@mti-systems.com>, l.wood@surrey.ac.uk, curtis@ipv6.occnc.com
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>, <52D58168.9060800@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk> <52D5B524.5080408@mti-systems.com>
In-Reply-To: <52D5B524.5080408@mti-systems.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:27:58 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 22:46:32 -0000

On 14/01/2014 22:07, Wesley Eddy wrote:
> On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
>> I don't think sayng 'oh, that error source is no longer a problem' disproves
>> Stone's overall point about undetected errors, though the
>> examples he uses from the technology of the day are necessarily
>> dated. Dismissing the overall  point because the examples use obsolete
>> technology is throwing the baby out with the bathwater; a host-to-host
>> error check catches things that intermediate checks cannot.
>>
>> Measuring error rates across end-to-end  Internet traffic is something that has
>> not received much attention , as error detection is not
>> instrumented well - hence citing Stone's published work,  in the absence
>> of awareness of anything newer (and as high profile/immediately recognisable
>> as sigcomm) in the area.
>>
>
> +1 ... the message in the paper is applicable to layered systems
> and internetworks in general.  Changes in the link technology
> since then don't invalidate it, especially since we know that
> the technology not only changes rapidly, but also is always
> growing in diverse directions, such that there things almost
> universally true today may be turned on their heads tomorrow.
>
> Designs for stacking layers need to follow solid general
> principles in order to be robust to changes (above and below).
>
Note that it is not only the link layer technology that has moved on,
the signal integrity of the h/w at all stages of the design and
implementation process has moved on.

Can we agree that the statistics in the paper are discredited?

If not, why not?

What is the error rate in modern h/w and network systems?

Is this significant in the application under consideration?

Finally if we are really concerned that we do actually need a
c/s (I am not in tunnel applications) why are we still happy to
use what is frankly a pathetic check in modern terms? Why
for example are we not moving to something like
the  Fletcher 64 bit c/s?

Stewart

From stbryant@cisco.com  Wed Jan 15 03:02:40 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 503701AE343; Wed, 15 Jan 2014 03:02:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.038
X-Spam-Level: 
X-Spam-Status: No, score=-10.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ht8tehBTC2RA; Wed, 15 Jan 2014 03:02:38 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id BEF471AE061; Wed, 15 Jan 2014 03:02:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12079; q=dns/txt; s=iport; t=1389783746; x=1390993346; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=ajcuDD8h7TBbs+OZZLo3Di3WoXtXcZR7hQVGnmaIaS4=; b=DyKNNHxL4EpK3YHIeZSImEcUoJB5eij8kG32fxysWZCWS/B1HzWJcSub FCqcrc8vQHBRfyymx57rKot3NN9faDuyMtynQ5EOf8OdQhoDwPhHJIk04 bt4To4k1KYX8TWBzncoBXo8NwzKzF4SjdE+L0npDCx2YAwhSmF1lYOg5s k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsFAO9p1lKQ/khM/2dsb2JhbABaDoI5RDhQuwKBFhZ0giUBAQEDAXQFBQsLEQQBAQEJGgsPAj4IBwwBBQIBAYd4CAgFxAAXjmUiBwaEMQSUOINmgTCLLYU4gW9/Pw
X-IronPort-AV: E=Sophos;i="4.95,662,1384300800"; d="scan'208,217";a="3655006"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 15 Jan 2014 11:02:24 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0FB2Ns5010692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jan 2014 11:02:23 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0FB2K4m022493; Wed, 15 Jan 2014 11:02:21 GMT
Message-ID: <52D66ABC.40606@cisco.com>
Date: Wed, 15 Jan 2014 11:02:20 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, wes@mti-systems.com, curtis@ipv6.occnc.com
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>, <52D58168.9060800@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk> <52D5B524.5080408@mti-systems.com>, <52D5BE37.4070301@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
Content-Type: multipart/alternative; boundary="------------090007090508030409010602"
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:28:10 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:02:40 -0000

This is a multi-part message in MIME format.
--------------090007090508030409010602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sent from my iPad

> On 14 Jan 2014, at 23:05,"l.wood@surrey.ac.uk"  <l.wood@surrey.ac.uk>  wrote:
>
> Stewart,
>
> your 'I'm not in tunnel applications' suggests you've misunderstood
> the argument here. The point is not to protect the tunnel traffic
> (which can quite happily checksum itself), it is to protect everything
> else on the network from misdelivery. It's not the tunnel application,
> it's every application sharing the internet with the tunnel which
> has UDP checksums turned off. See all of  RFC 6936 section 3.1.
> Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.
>
> And in IPv4 and IPv6, the pseudo-header checksum built into
> TCP and UDP is all we have. IPv6 deliberately copied v4 here.

Lloyd,

With the significant improvements in h/w design methodology
and the addressing of the s/w bugs that Curtis and I have been
explaining to you, it would seem that the fundamental
paper that underpins your argument is without credibility, and
by your own admission below, it seems that there are no
valid statistics for the current Internet to sustain your case.

Unless you can show that the misdelivery rate from this effect
exceeds the current rather high unwanted packet rate that
hosts need to fend off, I cannot see any basis to maintain
your assertion that the c/s is required in tunnel applications
to protect the rest of the net.

With regard to the IPv4, the IP checksum, which, in all router
implementations I have seen, is checked at every hop and
only incrementally changed, there is surely adequate
protection against misdelivery to another endpoint.

With regard to IPv6, I find it difficult to understand that
the threat is of any significance given that absence of demand
for the retrofit of a similar checksum in MPLS to protect
PEs and prevent the incorrect egress of traffic.

>> What is the error rate in modern h/w and network systems?
> No-one measures end-to-end misdelivery. No-one knows.

The upper bound is the packet loss rate less the congestion
discard rate. Do we have a figure for that?

Stewart

> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Stewart Bryant [stbryant@cisco.com]
> Sent: 14 January 2014 22:46
> To: Wesley Eddy; Wood L  Dr (Electronic Eng);curtis@ipv6.occnc.com
> Cc:gorry@erg.abdn.ac.uk;mpls@ietf.org;ietf@ietf.org;randy@psg.com;tsvwg@ietf.org;jnc@mit.edu;lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>
>> On 14/01/2014 22:07, Wesley Eddy wrote:
>>> On 1/14/2014 4:57 PM,l.wood@surrey.ac.uk  wrote:
>>> I don't think sayng 'oh, that error source is no longer a problem' disproves
>>> Stone's overall point about undetected errors, though the
>>> examples he uses from the technology of the day are necessarily
>>> dated. Dismissing the overall  point because the examples use obsolete
>>> technology is throwing the baby out with the bathwater; a host-to-host
>>> error check catches things that intermediate checks cannot.
>>>
>>> Measuring error rates across end-to-end  Internet traffic is something that has
>>> not received much attention , as error detection is not
>>> instrumented well - hence citing Stone's published work,  in the absence
>>> of awareness of anything newer (and as high profile/immediately recognisable
>>> as sigcomm) in the area.
>> +1 ... the message in the paper is applicable to layered systems
>> and internetworks in general.  Changes in the link technology
>> since then don't invalidate it, especially since we know that
>> the technology not only changes rapidly, but also is always
>> growing in diverse directions, such that there things almost
>> universally true today may be turned on their heads tomorrow.
>>
>> Designs for stacking layers need to follow solid general
>> principles in order to be robust to changes (above and below).
> Note that it is not only the link layer technology that has moved on,
> the signal integrity of the h/w at all stages of the design and
> implementation process has moved on.
>
> Can we agree that the statistics in the paper are discredited?
>
> If not, why not?
>
> What is the error rate in modern h/w and network systems?
>
> Is this significant in the application under consideration?
>
> Finally if we are really concerned that we do actually need a
> c/s (I am not in tunnel applications) why are we still happy to
> use what is frankly a pathetic check in modern terms? Why
> for example are we not moving to something like
> the  Fletcher 64 bit c/s?
>
> Stewart

.



-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


--------------090007090508030409010602
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-text-plain" wrap="true" graphical-quote="true"
      style="font-family: -moz-fixed; font-size: 12px;" lang="x-western">
      <pre wrap="">
Sent from my iPad

</pre>
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">On 14 Jan 2014, at 23:05, <a class="moz-txt-link-rfc2396E" href="mailto:l.wood@surrey.ac.uk">"l.wood@surrey.ac.uk"</a> <a class="moz-txt-link-rfc2396E" href="mailto:l.wood@surrey.ac.uk">&lt;l.wood@surrey.ac.uk&gt;</a> wrote:

Stewart,

your 'I'm not in tunnel applications' suggests you've misunderstood
the argument here. The point is not to protect the tunnel traffic
(which can quite happily checksum itself), it is to protect everything
else on the network from misdelivery. It's not the tunnel application,
it's every application sharing the internet with the tunnel which
has UDP checksums turned off. See all of  RFC 6936 section 3.1.
Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.

And in IPv4 and IPv6, the pseudo-header checksum built into
TCP and UDP is all we have. IPv6 deliberately copied v4 here.
</pre>
      </blockquote>
      <pre wrap="">Lloyd,

With the significant improvements in h/w design methodology
and the addressing of the s/w bugs that Curtis and I have been
explaining to you, it would seem that the fundamental
paper that underpins your argument is without credibility, and
by your own admission below, it seems that there are no 
valid statistics for the current Internet to sustain your case.

Unless you can show that the misdelivery rate from this effect
exceeds the current rather high unwanted packet rate that
hosts need to fend off, I cannot see any basis to maintain 
your assertion that the c/s is required in tunnel applications 
to protect the rest of the net.

With regard to the IPv4, the IP checksum, which, in all router
implementations I have seen, is checked at every hop and
only incrementally changed, there is surely adequate 
protection against misdelivery to another endpoint.

With regard to IPv6, I find it difficult to understand that
the threat is of any significance given that absence of demand
for the retrofit of a similar checksum in MPLS to protect
PEs and prevent the incorrect egress of traffic.

</pre>
      <blockquote type="cite" style="color: #000000;">
        <blockquote type="cite" style="color: #000000;">
          <pre wrap="">What is the error rate in modern h/w and network systems?
</pre>
        </blockquote>
        <pre wrap="">No-one measures end-to-end misdelivery. No-one knows.
</pre>
      </blockquote>
      <pre wrap="">The upper bound is the packet loss rate less the congestion
discard rate. Do we have a figure for that?

Stewart

</pre>
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">Lloyd Wood
<a class="moz-txt-link-freetext" href="http://about.me/lloydwood">http://about.me/lloydwood</a>
________________________________________
From: Stewart Bryant [<a class="moz-txt-link-abbreviated" href="mailto:stbryant@cisco.com">stbryant@cisco.com</a>]
Sent: 14 January 2014 22:46
To: Wesley Eddy; Wood L  Dr (Electronic Eng); <a class="moz-txt-link-abbreviated" href="mailto:curtis@ipv6.occnc.com">curtis@ipv6.occnc.com</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:gorry@erg.abdn.ac.uk">gorry@erg.abdn.ac.uk</a>; <a class="moz-txt-link-abbreviated" href="mailto:mpls@ietf.org">mpls@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:randy@psg.com">randy@psg.com</a>; <a class="moz-txt-link-abbreviated" href="mailto:tsvwg@ietf.org">tsvwg@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:jnc@mit.edu">jnc@mit.edu</a>; <a class="moz-txt-link-abbreviated" href="mailto:lisp@ietf.org">lisp@ietf.org</a>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))

</pre>
        <blockquote type="cite" style="color: #000000;">
          <pre wrap="">On 14/01/2014 22:07, Wesley Eddy wrote:
</pre>
          <blockquote type="cite" style="color: #000000;">
            <pre wrap="">On 1/14/2014 4:57 PM, <a class="moz-txt-link-abbreviated" href="mailto:l.wood@surrey.ac.uk">l.wood@surrey.ac.uk</a> wrote:
I don't think sayng 'oh, that error source is no longer a problem' disproves
Stone's overall point about undetected errors, though the
examples he uses from the technology of the day are necessarily
dated. Dismissing the overall  point because the examples use obsolete
technology is throwing the baby out with the bathwater; a host-to-host
error check catches things that intermediate checks cannot.

Measuring error rates across end-to-end  Internet traffic is something that has
not received much attention , as error detection is not
instrumented well - hence citing Stone's published work,  in the absence
of awareness of anything newer (and as high profile/immediately recognisable
as sigcomm) in the area.
</pre>
          </blockquote>
          <pre wrap="">+1 ... the message in the paper is applicable to layered systems
and internetworks in general.  Changes in the link technology
since then don't invalidate it, especially since we know that
the technology not only changes rapidly, but also is always
growing in diverse directions, such that there things almost
universally true today may be turned on their heads tomorrow.

Designs for stacking layers need to follow solid general
principles in order to be robust to changes (above and below).
</pre>
        </blockquote>
        <pre wrap="">Note that it is not only the link layer technology that has moved on,
the signal integrity of the h/w at all stages of the design and
implementation process has moved on.

Can we agree that the statistics in the paper are discredited?

If not, why not?

What is the error rate in modern h/w and network systems?

Is this significant in the application under consideration?

Finally if we are really concerned that we do actually need a
c/s (I am not in tunnel applications) why are we still happy to
use what is frankly a pathetic check in modern terms? Why
for example are we not moving to something like
the  Fletcher 64 bit c/s?

Stewart
</pre>
      </blockquote>
      <pre wrap="">.

</pre>
    </div>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

<a class="moz-txt-link-freetext" href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</a>

</pre>
  </body>
</html>

--------------090007090508030409010602--

From stbryant@cisco.com  Wed Jan 15 03:31:34 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1E31AE35F; Wed, 15 Jan 2014 03:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sUOUCgwX97T5; Wed, 15 Jan 2014 03:31:33 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 4D41A1AE35E; Wed, 15 Jan 2014 03:31:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1164; q=dns/txt; s=iport; t=1389785481; x=1390995081; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=up0UvBh6yHD7U+HgE9fAGIoHx81lC42/wIrmS7ggc90=; b=bulh0VR/VA9c110y44jV9LGZvY7ZEJagtPMVi3LPwz7RekcalnbmeYVc p01qfycr18VloSHVRsIFpsFLqSF7l1UTHTXNSSAScADzqGJqXqOKFCWMa +jvFNgeUJV/ja3UkgcsN4wOaqkNLI9PFRcPsndwBEvPWRVY0swpz9U3Oo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAJNw1lKQ/khR/2dsb2JhbABagwu4fIMOgRcWdIIlAQEBBDgxAQ4BEAsYCRYECwkDAgECAUUGDQEHAQGIAMQRF48HB4Q3AQOYHpIVgW+BPg
X-IronPort-AV: E=Sophos;i="4.95,662,1384300800";  d="scan'208";a="2986762"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 15 Jan 2014 11:31:20 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0FBVJnF019333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Jan 2014 11:31:20 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0FBVIHK024290; Wed, 15 Jan 2014 11:31:18 GMT
Message-ID: <52D67186.8080008@cisco.com>
Date: Wed, 15 Jan 2014 11:31:18 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com> <m2a9exmrja.wl%randy@psg.com>
In-Reply-To: <m2a9exmrja.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:28:28 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 11:31:34 -0000

On 15/01/2014 11:08, Randy Bush wrote:
> [ you insist on cc:ing me, so you get to endure my opinions ]
>
>> it seems that there are no valid statistics for the current Internet
>> to sustain your case.
> as we discussed privately, there seem to be no real measurements to
> sustain any case.  this is all conjecturbation.
>
> what i do not understand is why, given the lack of solid evidence that
> we are in a safe space, you and others are not willing to spend a few
> euro cents to have a reasonable level of assurance at this layer.
>
> randy
Randy,

It is not a few cents, it is likely the re-engineering of a lot
of silicon.

The reason that UDP is of interest is that the on path silicon
knows how to process it, for example it knows how to to ECMP it.

The reason that the UDP c/s is a problem for a tunneler is that
it needs to have access to the whole pkt to calculate the
c/s, but as you know the silicon optimised that access away
a long time ago.

The alternative would be UDP-lite, but the ability of on path
silicon to process that as competently and as completely as it
processes UDP is by no means clear.

- Stewart



From wes@mti-systems.com  Tue Jan 14 14:07:53 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B514A1AE2B6 for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 14:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XvVweknCorWE for <ietf@ietfa.amsl.com>; Tue, 14 Jan 2014 14:07:52 -0800 (PST)
Received: from atl4mhob03.myregisteredsite.com (atl4mhob03.myregisteredsite.com [209.17.115.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8451AE2B9 for <ietf@ietf.org>; Tue, 14 Jan 2014 14:07:51 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s0EM7cYt032765 for <ietf@ietf.org>; Tue, 14 Jan 2014 17:07:38 -0500
Received: (qmail 28498 invoked by uid 0); 14 Jan 2014 22:07:38 -0000
X-TCPREMOTEIP: 69.81.143.143
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.1.107?) (wes@mti-systems.com@69.81.143.143) by 0 with ESMTPA; 14 Jan 2014 22:07:38 -0000
Message-ID: <52D5B524.5080408@mti-systems.com>
Date: Tue, 14 Jan 2014 17:07:32 -0500
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, stbryant@cisco.com, curtis@ipv6.occnc.com
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
References: <201401141706.s0EH6Fbo099057@maildrop2.v6ds.occnc.com>, <52D58168.9060800@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346C5@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:28:41 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, jnc@mit.edu, tsvwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Jan 2014 22:07:53 -0000

On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
> I don't think sayng 'oh, that error source is no longer a problem' disproves
> Stone's overall point about undetected errors, though the
> examples he uses from the technology of the day are necessarily
> dated. Dismissing the overall  point because the examples use obsolete
> technology is throwing the baby out with the bathwater; a host-to-host
> error check catches things that intermediate checks cannot.
> 
> Measuring error rates across end-to-end  Internet traffic is something that has
> not received much attention , as error detection is not
> instrumented well - hence citing Stone's published work,  in the absence
> of awareness of anything newer (and as high profile/immediately recognisable
> as sigcomm) in the area.
> 


+1 ... the message in the paper is applicable to layered systems
and internetworks in general.  Changes in the link technology
since then don't invalidate it, especially since we know that
the technology not only changes rapidly, but also is always
growing in diverse directions, such that there things almost
universally true today may be turned on their heads tomorrow.

Designs for stacking layers need to follow solid general
principles in order to be robust to changes (above and below).

-- 
Wes Eddy
MTI Systems

From xuxiaohu@huawei.com  Tue Jan 14 19:07:04 2014
Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D1091AE1CD; Tue, 14 Jan 2014 19:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.95
X-Spam-Level: 
X-Spam-Status: No, score=-1.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8YfEzJwIAPB; Tue, 14 Jan 2014 19:07:02 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 977261AE1C5; Tue, 14 Jan 2014 19:07:01 -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.7-GA FastPath queued) with ESMTP id AZY31235; Wed, 15 Jan 2014 03:06:49 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 15 Jan 2014 03:05:57 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 15 Jan 2014 03:06:48 +0000
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.45]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Wed, 15 Jan 2014 11:06:44 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>, Wesley Eddy <wes@mti-systems.com>
Subject: re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPEY8CmZemCkyvYUuoIcxHPrslpZqFEdhw
Date: Wed, 15 Jan 2014 03:06:44 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08244E41@NKGEML512-MBS.china.huawei.com>
References: Your message of "Tue, 14 Jan 2014 11:22:02 -0500." <52D5642A.7090103@mti-systems.com> <201401150113.s0F1DXSN005803@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401150113.s0F1DXSN005803@maildrop2.v6ds.occnc.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Wed, 15 Jan 2014 08:31:30 -0800
Cc: IETF discussion list <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 03:07:04 -0000

DQoNCj4gLS0tLS3Tyrz+1K28/i0tLS0tDQo+ILeivP7IyzogbXBscyBbbWFpbHRvOm1wbHMtYm91
bmNlc0BpZXRmLm9yZ10gtPqx7SBDdXJ0aXMgVmlsbGFtaXphcg0KPiC3osvNyrG85DogMjAxNMTq
MdTCMTXI1SA5OjE0DQo+IMrVvP7IyzogV2VzbGV5IEVkZHkNCj4gs63LzTogU2NvdHQgQnJpbTsg
RWdnZXJ0LCBMYXJzOyBJRVRGIGRpc2N1c3Npb24gbGlzdDsgbXBsc0BpZXRmLm9yZw0KPiDW98zi
OiBSZTogW21wbHNdIExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtbXBscy1pbi11ZHAtMDQudHh0PiAo
RW5jYXBzdWxhdGluZyBNUExTDQo+IGluIFVEUCkgdG8gUHJvcG9zZWQgU3RhbmRhcmQNCj4gDQo+
IA0KPiBJbiBtZXNzYWdlIDw1MkQ1NjQyQS43MDkwMTAzQG10aS1zeXN0ZW1zLmNvbT4NCj4gV2Vz
bGV5IEVkZHkgd3JpdGVzOg0KPiANCj4gPiBPbiAxLzE0LzIwMTQgMTE6MDYgQU0sIEVnZ2VydCwg
TGFycyB3cm90ZToNCj4gPiA+IEhpLA0KPiA+ID4NCj4gPiA+IE9uIDIwMTQtMS0xNCwgYXQgMTY6
MzksIFNjb3R0IEJyaW0gPHNjb3R0LmJyaW1AZ21haWwuY29tPiB3cm90ZToNCj4gPiA+PiBMYXJz
LCBJIGtub3cgd2UncmUgcmVwZWF0aW5nIGFyZ3VtZW50cyBmcm9tIHRoZSBsYXN0IGRlY2FkZS4g
VGhlDQo+ID4gPj4gY2hvaWNlIGlzIGJldHdlZW4gKDEpIHNwZWNpZnlpbmcgY29uZ2VzdGlvbiBj
b250cm9sIGFyb3VuZCB0aGUNCj4gPiA+PiBzdWJzdHJhdGUgVURQIHRoYXQgY2FuIGJlIHR1cm5l
ZCBvZmYgaWYgaXQgY2F1c2VzIHByb2JsZW1zLCBvciAoMikNCj4gPiA+PiBzcGVjaWZ5aW5nIG5v
dGhpbmcgYXQgdGhpcyB0aW1lIGFuZCBhZGRpbmcgaXQgbGF0ZXIgaWYgb3BlcmF0b3JzDQo+ID4g
Pj4gd2FudCBpdC4NCj4gPiA+Pg0KPiA+ID4+IEkgZ3Vlc3MgaWYgdGhpcyBjYW4gYmUgd3JpdHRl
biBhcyBhIFNIT1VMRCwgdXAgdG8gdGhlIGltcGxlbWVudG9yJ3MNCj4gPiA+PiBkaXNjcmV0aW9u
LCB0aGVuIG9rYXkuDQo+ID4gPg0KPiA+ID4gSSBkb24ndCB0aGluayB3ZSBjYW4gbGVhdmUgdGhp
cyB1cCB0byBpbXBsZW1lbnRvcnMgZGlzY3JldGlvbi4gV2UndmUgaGFkDQo+IElFVEYgY29uc2Vu
c3VzIHRoYXQgSW50ZXJuZXQgY29tbXVuaWNhdGlvbiByZXF1aXJlcyBjb25nZXN0aW9uIGNvbnRy
b2wgYXQgbGVhc3QNCj4gc2luY2UgUkZDMjkxNC4gQSBjaXJjdWl0IGJyZWFrZXIgbWVjaGFuaXNt
cyBzZWVtcyBzdHJhaWdodGZvcndhcmQgdG8NCj4gaW1wbGVtZW50Lg0KPiA+ID4NCj4gPiA+IEFz
IGlzLCBJIG9iamVjdCB0byB0aGlzIGRvY3VtZW50IGdvaW5nIGZvcndhcmQuIFRoZSBtaW5vciBi
ZW5lZml0cyBvZiBnZXR0aW5nDQo+IHNvbWUgYmV0dGVyIGxvYWQgYmFsYW5jaW5nIGZvciBNUExT
IGFyZSBmYXIgb3V0d2VpZ2hlZCBieSB0aGUgcmlza3MuDQo+ID4gPg0KPiA+ID4gKEknbSBhbHNv
IGdvaW5nIHRvIHNodXQgdXAgbm93LCBhbmQgbGV0IG90aGVycyBzcGVhay4gSSB0aGluayBJJ3Zl
DQo+ID4gPiBzYWlkIG15IGJpdC4pDQo+ID4gPg0KPiA+DQo+ID4NCj4gPiBJJ20gaW4gYmFzaWMg
YWdyZWVtZW50Lg0KPiA+DQo+ID4gQXNzdW1pbmcgd2UgbWlnaHQgYWxsIGFncmVlIHRoYXQgdGhl
cmUgYXJlIGNvbmNlaXZhYmxlIHNjZW5hcmlvcyB3aGVyZQ0KPiA+IGEgY2lyY3VpdCBicmVha2Vy
IG1lY2hhbmlzbSB3b3VsZCBiZSB1c2VmdWwsIGlzIHRoZSByZWFsIGlzc3VlIHRoYXQgd2UNCj4g
PiBkb24ndCBhbGwgYWdyZWUgdGhhdCBpdCBjb3VsZCBiZSBpbXBsZW1lbnRlZCBpbiBhIHdheSB0
aGF0J3Mgbm90DQo+ID4gYnVyZGVuc29tZSBhbmQgZG9lc24ndCBkZWdyYWRlIHBlcmZvcm1hbmNl
IHVubmVjZXNzYXJpbHk/DQo+ID4NCj4gPiBPciBpcyB0aGVyZSBzdGlsbCBmdW5kYW1lbnRhbCBk
aXNhZ3JlZW1lbnQgYWJvdXQgd2hldGhlciB0aGUgc2NlbmFyaW9zDQo+ID4gd2hlcmUgdGhlIGNp
cmN1aXQgYnJlYWtlciBpcyB1c2VmdWwgYXJlIGV2ZW4gdmFsaWQ/DQo+IA0KPiANCj4gQSBjaXJj
dWl0IGJyZWFrZXIgKGRyb3AgYWxsIHRyYWZmaWMgb24gc2lnbiBvZiBjb25nZXN0aW9uKSBhdCB0
aGUgTVBMUyBvdmVyIFVEUA0KPiBsZXZlbCB3b3VsZCBiZSB0aGUgd29yc3QgdGhpbmcgeW91IGNv
dWxkIHNwZWNpZnkgYW5kIElNTyBpdCB3b3VsZCBndWFyZW50ZWUNCj4gemVybyBpbXBsZW1lbnRh
dGlvbnMuDQo+IA0KPiBBIGNpcmN1aXQgYnJlYWtlciBtaWdodCBiZSBhcHByb3ByaWF0ZSBmb3Ig
VERNIG92ZXIgUFcgYnV0IG5vdGhpbmcgZWxzZS4gIFRoaXMNCj4gbWFrZXMgc2Vuc2UgYmVjYXVz
ZSBURE0gY2Fubm90IGNoYW5nZSBpdHMgYmFuZHdpZHRoIHNvIHRoZSBvbmx5IGNob2ljZSBpcyB0
bw0KPiBzaHV0IGl0IG9mZi4gIFRETSBvdmVyIFBXIGlzIGFuIGFwcGxpY2F0aW9uIHRoYXQgY2Fu
IHJ1biBvdmVyIE1QTFMgKG9yIEdSRSBvcg0KPiBMMlRQKS4gIFRoZSBiZXN0IHBsYWNlIHRvIHB1
dCB0aGF0IGNpcmN1aXQgYnJlYWtlciAoaWYgYW55d2hlcmUgYXQgYWxsKSBpcyBpbiBURE0NCj4g
b3ZlciBQVy4NCg0KSSBjb3VsZG4ndCBhZ3JlZSBtb3JlIHdpdGggQ3VydGlzJ3MgcG9pbnQuIFNp
bmNlIFJGQzM5ODUgaGFzIGFscmVhZHkgbWFkZSBhIGRldGFpbGVkIGRlc2NyaXB0aW9uIG9mIGNv
bmdlc3Rpb24gY29uc2lkZXJhdGlvbnMgYWJvdXQgUFdzLCBpdCBzZWVtcyB0aGF0IHRoZSBzaW1w
bGVzdCB3YXkgaXMganVzdCB0byBhZGQgYSByZWZlcmVuY2UgdG8gdGhhdCBSRkMgaW4gdGhpcyBk
b2MsIGluIGFkZGl0aW9uIHRvIHRoZSB0ZXh0IEkgaGF2ZSBwcm9wb3NlZCBpbiBhIHByZXZpb3Vz
IGVtYWlsLiBUaGUgYWR2YW50YWdlIG9mIHRoaXMgY2hvaWNlIGlzOiBzaW5jZSB0aGVyZSBpcyBv
bmx5IG9uZSBwbGFjZSB3aGVyZSB0aGUgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlzbSBmb3Ig
TVBMUy9QVyB0cmFmZmljIGlzIHNwZWNpZmllZCwgaXQncyBtdWNoIGVhc2llciBmb3Igb3BlcmF0
b3JzIGFuZCBpbXBsZW1lbnRvcnMgdG8gcmVmZXIuIEluIGFkZGl0aW9uLCBvbmNlIGEgbW9yZSBw
cmFjdGljYWwgY29uZ2VzdGlvbiBjb250cm9sIG1lY2hhbmlzbSB3YXMgZm91bmQgaW4gdGhlIGZ1
dHVyZSwgaXQgb25seSBuZWVkcyB0byB1cGRhdGUgb25lIFJGQywgcmF0aGVyIHRoYW4gdXBkYXRp
bmcgbWFueSBSRkNzLg0KDQpCZXN0IHJlZ2FyZHMsDQpYaWFvaHUNCg0KPiBDdXJ0aXMNCj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gbXBscyBtYWls
aW5nIGxpc3QNCj4gbXBsc0BpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21wbHMNCg==

From hartmans@mit.edu  Wed Jan 15 08:40:36 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9D11AE3C3 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 08:40:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HDLZhKs-a8f9 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 08:40:35 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3612B1AE3C1 for <ietf@ietf.org>; Wed, 15 Jan 2014 08:40:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 02DC620640; Wed, 15 Jan 2014 11:37:51 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50882dgNHbBK; Wed, 15 Jan 2014 11:37:50 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 15 Jan 2014 11:37:50 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8DD3F83788; Wed, 15 Jan 2014 11:40:22 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Eliot Lear <lear@cisco.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu> <52D593E2.7000202@cisco.com>
Date: Wed, 15 Jan 2014 11:40:22 -0500
In-Reply-To: <52D593E2.7000202@cisco.com> (Eliot Lear's message of "Tue, 14 Jan 2014 20:45:38 +0100")
Message-ID: <tsla9exryfd.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 16:40:36 -0000

>>>>> "Eliot" == Eliot Lear <lear@cisco.com> writes:

    Eliot> On 1/14/14 8:33 PM, Sam Hartman wrote:

    >>>>>>> "Scott" == Scott Brim <scott.brim@gmail.com> writes:
    >> 
    >> I disagree with Eliot: I don't think the general statement is a
    >> truism especially not in a BCP.

    Eliot> To test if it's a truism, replace perpass with anything else
    Eliot> and see what design consideration should be examined late in
    Eliot> the process.



I absolutely agree that general guidance of this form would be valuable
either in some general security BCP that the other security BCPs
reference or restated in the security BCPs.  Its lack in 4107 and BCP 61
is something that causes me problems as a WG chair and cause significant
difficulty for me as an AD.

we're not working on such a BCP now, so I'm trying to add the advice I
need to this BCP in order for it to work for me as a WG chair and
document author.

It's not so much a truism that we all agree to it.  I've definitely
worked with WGs that didn't want to consider these sorts of issues when
choosing technology and didn't seem to agree that they had to.  I do
hope it's enough of a truism that we can agree to say it in a consensus
document.  The idea that we should not say something because we agree
with it confuses me greatly.

From dhc@dcrocker.net  Wed Jan 15 09:01:27 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9551AE3F7 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 09:01:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWnkOemYQJ2Z for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 09:01:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4F51AE3F4 for <ietf@ietf.org>; Wed, 15 Jan 2014 09:01:26 -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 s0FH0uAA021857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Jan 2014 09:00:59 -0800
Message-ID: <52D6BEC1.4050204@dcrocker.net>
Date: Wed, 15 Jan 2014 09:00:49 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, Eliot Lear <lear@cisco.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu> <52D593E2.7000202@cisco.com> <CAPv4CP9+qxAo7B0qr5VrvBdisFeU8E-C+KGgvNMTs=JTHPm8zA@mail.gmail.com>
In-Reply-To: <CAPv4CP9+qxAo7B0qr5VrvBdisFeU8E-C+KGgvNMTs=JTHPm8zA@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.66]); Wed, 15 Jan 2014 09:01:00 -0800 (PST)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 15 Jan 2014 17:01:27 -0000

On 1/14/2014 1:02 PM, Scott Brim wrote:
> The point of the paragraph is to declare PM to be something that
> should be considered at architecture time, i.e. early in the design
> process,


Over the years, my own interest in the potential influence of security 
concerns in protocol development work has been less due to security 
benefits -- not that those aren't important -- but due to the increased 
discipline it ought to require in the development process.

Note that I said 'ought'.  Working groups are pretty erratic about doing 
architecture initially, then followed by details.  Not never, but also 
far from always.

In other words, a nice unintended consequence of PM concerns might be to 
press more regularly for that early, clear architecture work, if only to 
get that early, clear PM consideration...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Wed Jan 15 22:28:10 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8218C1AE1D1 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 22:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j1GUTnDPj4Zq for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 22:28:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A82AC1ADE7C for <ietf@ietf.org>; Wed, 15 Jan 2014 22:28:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F3A5A2CC5F; Thu, 16 Jan 2014 08:27:54 +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 qQf0C1bx3TFT; Thu, 16 Jan 2014 08:27:54 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4E1FB2CC48; Thu, 16 Jan 2014 08:27:54 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: draft-farrell-perpass-attack architecture issue
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <tslzjmzvbij.fsf@mit.edu>
Date: Thu, 16 Jan 2014 07:27:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A28C4AF-31D3-4DF7-8261-0F65B23CACB6@piuha.net>
References: <52D43E69.6090001@cs.tcd.ie> <52D44C28.4070803@bbn.com> <52D44D67.2090704@dcrocker.net> <tslzjmzvbij.fsf@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1510)
Cc: dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 06:28:10 -0000

I like the proposed addition (but would also like to avoid the example, =
which had several issues people have already pointed out).

Jari


From lear@cisco.com  Wed Jan 15 23:16:33 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF4FF1AE2D7 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 23:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DxdY9HHNTkZr for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 23:16:32 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 4A8A31AE1FA for <ietf@ietf.org>; Wed, 15 Jan 2014 23:16:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1055; q=dns/txt; s=iport; t=1389856580; x=1391066180; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=uv2Fev0YEVW5Ss/wf/2IDHyV+cVEleJH3K15arYd/kk=; b=D+v2gmhAn1A12gzUUum5bSWsMfj/YGVxE0yj36p0R+AgGQSbf3YsmD54 tJRpm9+fOKO/d977vOnIXX+eCoLhXRGqGzth4RhnqkUti4Oqsh95qnQ8n Kw+Ql70oeH+Q051eP/rLNE/Ld0k+EI5iYHSRUMqzIjOEbWj92Zj/TZJ6Y 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiIFAEqG11KQ/khL/2dsb2JhbABZDoJ9hAy4CoEQFnSCJQEBAQMBDhVCEwEQCxIGAgIFFgsCAgkDAgECASsMDgYNAQUCAQGHeAinf5tgF4EpjVYHgm+BSAEDlDqDZpIVgm5AOw
X-IronPort-AV: E=Sophos;i="4.95,666,1384300800";  d="scan'208";a="3029145"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-2.cisco.com with ESMTP; 16 Jan 2014 07:16:19 +0000
Received: from mctiny.local ([10.61.207.221]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0G7GI4f030629 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 07:16:19 GMT
Message-ID: <52D78742.9000604@cisco.com>
Date: Thu, 16 Jan 2014 08:16:18 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: draft-farrell-perpass-attack architecture issue
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net>	<CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com>	<tsl4n56tl38.fsf@mit.edu> <52D593E2.7000202@cisco.com> <tsla9exryfd.fsf@mit.edu>
In-Reply-To: <tsla9exryfd.fsf@mit.edu>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 07:16:33 -0000

On 1/15/14 5:40 PM, Sam Hartman wrote:
>>>>>> "Eliot" == Eliot Lear <lear@cisco.com> writes:

>
> I absolutely agree that general guidance of this form would be valuable
> either in some general security BCP that the other security BCPs
> reference or restated in the security BCPs. 

It is a basic precept of engineering that the earlier you spot a design
flaw, the less costly it is to address.  We needn't teach such basic
precepts in our series.

>
> we're not working on such a BCP now, so I'm trying to add the advice I
> need to this BCP in order for it to work for me as a WG chair and
> document author.

And as a working group chair you must balance ALL considerations and not
just this one.
> It's not so much a truism that we all agree to it.  I've definitely
> worked with WGs that didn't want to consider these sorts of issues when
> choosing technology and didn't seem to agree that they had to.

And I've seen participants all but derail working groups by solely
focusing on one design consideration.


Eliot

From stephen.farrell@cs.tcd.ie  Thu Jan 16 04:53:33 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A456E1AE337 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 04:53:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.438
X-Spam-Level: 
X-Spam-Status: No, score=-4.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6dmi3MCAJITb for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 04:53:31 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 36ED21AE336 for <ietf@ietf.org>; Thu, 16 Jan 2014 04:53:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 059A9BE25 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:53:18 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KMgZTE37qkR for <ietf@ietf.org>; Thu, 16 Jan 2014 12:53:17 +0000 (GMT)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id DB58EBE1C for <ietf@ietf.org>; Thu, 16 Jan 2014 12:53:17 +0000 (GMT)
Message-ID: <52D7D63E.7010506@cs.tcd.ie>
Date: Thu, 16 Jan 2014 12:53:18 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Re: Fwd: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie>
In-Reply-To: <52CEAA53.1090102@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 12:53:33 -0000

And as is traditional, we've added a few days:-)

Final deadline is end of Monday Jan 20 anywhere
on Earth (== 1200 UTC Jan 21). And that will be
a hard deadline.

There's also a bit more logistics stuff now at [1].

Cheers,
S.

[1] https://www.w3.org/2014/strint/

On 01/09/2014 01:55 PM, Stephen Farrell wrote:
> 
> Folks, submissions are starting to roll in so this is
> a reminder to send yours by Jan 15. We'll be posting
> more logistics next week(-ish) as well in case you're
> wondering.
> 
> Thanks,
> S.
> 
> 
> -------- Original Message --------
> Subject: W3C/IAB workshop on Strengthening the Internet Against
> Pervasive Monitoring (STRINT)
> Date: Sun, 1 Dec 2013 10:48:15 -0500
> From: IAB Chair <iab-chair@iab.org>
> To: IETF Announce <ietf-announce@ietf.org>
> CC: IAB <iab@iab.org>, IETF <ietf@ietf.org>
> 
> 
> W3C/IAB workshop on Strengthening the Internet
> Against Pervasive Monitoring (STRINT)
> ======================================
> 
> Logistics/Dates:
> 
> Submissions due: Jan 15 2014
> Invitations issued: Jan 31 2014
> Workshop Date: Feb 28 (pm) & Mar 1 (am) 2014
> 	To be Confirmed - could be all day Mar 1
> Location: Central London, UK. IETF Hotel or nearby (TBC)
> For queries, contact: stephen.farrell@cs.tcd.ie, tech@strews.eu
> Send submissions to: group-strint-submission@w3.org
> Workshop web site: http://www.w3.org/2014/strint/
> 
> The Vancouver IETF plenary concluded that pervasive monitoring
> represents an attack on the Internet, and the IETF has begun to
> carry out various of the more obvious actions [1] required to
> try to handle this attack. However, there are additional much
> more complex questions arising that need further consideration
> before any additional concrete plans can be made.
> 
> The W3C and IAB will therefore host a one-day workshop on the
> topic of "Strengthening the Internet Against Pervasive
> Monitoring" before IETF-89 in London in March 2014, with support
> from the EU FP7 STREWS [2] project.
> 
> Pervasive monitoring targets protocol data that we also need for
> network manageability and security. This data is captured and
> correlated with other data. There is an open problem as to how
> to enhance protocols so as to maintain network manageability and
> security but still limit data capture and correlation.
> 
> The overall goal of the workshop is to steer IETF and W3C work
> so as to be able to improve or "strengthen" the Internet in the
> face of pervasive monitoring.  A workshop report in the form of
> an IAB RFC will be produced after the event.
> 
> Technical questions for the workshop include:
> 
> - What are the pervasive monitoring threat models, and what is
>   their effect on web and Internet protocol security and privacy?
> - What is needed so that web developers can better consider the
>   pervasive monitoring context?
> - How are WebRTC and IoT impacted, and how can they be better
>   protected? Are other key Internet and web technologies
>   potentially impacted?
> - What gaps exist in current tool sets and operational best
>   practices that could address some of these potential impacts?
> - What trade-offs exist between strengthening measures, (e.g.
>   more encryption) and performance, operational or network
>   management issues?
> - How do we guard against pervasive monitoring while maintaining
>   network manageability?
> - Can lower layer changes (e.g., to IPv6, LISP, MPLS) or
>   additions to overlay networks help?
> - How realistic is it to not be fingerprintable on the web and
>   Internet?
> - How can W3C, the IETF and the IRTF better deal with new
>   cryptographic algorithm proposals in future?
> - What are the practical benefits and limits of "opportunistic
>   encryption"?
> - Can we deploy end-to-end crypto for email, SIP, the web, all
>   TCP applications or other applications so that we mitigate
>   pervasive monitoring usefully?
> - How might pervasive monitoring take form or be addressed in
>   embedded systems or different industrial verticals?
> - How do we reconcile caching, proxies and other intermediaries
>   with end-to-end encryption?
> - Can we obfuscate metadata with less overhead than TOR?
> - Considering meta-data: are there relevant differences between
>   protocol artefacts, message sizes and patterns and payloads?
> 
> Position papers (maximum of 5 pages using 10pt font or any
> length Internet-Drafts) from academia, industry and others that
> focus on the broader picture and that warrant the kind of
> extended discussion that a full day workshop offers are the most
> welcome. Papers that reflect experience based on running code
> and deployed services are also very welcome. Papers that are
> proposals for point-solutions are less useful in this context,
> and can simply be submitted as Internet-Drafts and discussed on
> relevant IETF or W3C lists, e.g. the IETF perpass list. [3]
> 
> The workshop will be by invitation only. Those wishing to attend
> should submit a position paper or Internet-Draft.  All inputs
> submitted and considered relevant will be published on the
> workshop web page. The organisers (STREWS project participants,
> IAB and W3C staff) will decide whom to invite based on the
> submissions received.  Sessions will be organized according to
> content, and not every accepted submission or invited attendee
> will have an opportunity to present as the intent is to foster
> discussion and not simply to have a sequence of presentations.
> 
> [1] http://down.dsg.cs.tcd.ie/misc/perpass.txt
> [2] http://www.strews.eu/
> [3] https://www.ietf.org/mailman/listinfo/perpass
> 
> 
> 
> 
> 
> 
> 
> 

From curtis@ipv6.occnc.com  Wed Jan 15 08:58:22 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4031B1AE0D4; Wed, 15 Jan 2014 08:58:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGXl277OMqp3; Wed, 15 Jan 2014 08:58:19 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7AF1AE017; Wed, 15 Jan 2014 08:58:19 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FGvsQ9019368; Wed, 15 Jan 2014 11:57:54 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401151657.s0FGvsQ9019368@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Wed, 15 Jan 2014 05:20:27 +0000." <290E20B455C66743BE178C5C84F1240847E63346C7@EXMB01CMS.surrey.ac.uk>
Date: Wed, 15 Jan 2014 11:57:54 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:06:58 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, curtis@ipv6.occnc.com, jnc@mit.edu, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 16:58:22 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346C7@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> That's robustness _for the tunnelled traffic_.
>  
> Not for anything else sharing the network - that hasn't been
> instrumented and measured.
>  
> Lloyd Wood
> http://about.me/lloydwood


The reason that MPLS and PWE3 are successfully deployed is that this
traffic is carried over "well-managed networks" as RFC 6936 puts it.

If a UDP and IP encapsulation is added, then nothing changes.

If the UDP encapsulation occurs on a lower end router, it is likely
that the whole packet is available on which to perform a checksum.  On
a really low end router the checksum is likely to be done in software.

If it occurs on a high end router then the part of the hardware that
can today modify checksums only, doesn't even have access to the
packet to do a checksum and put it into the front of the packet.
There are two reasons for this.

  1.  A lot of high end routers split off the top 128-256 bytes and
      send it to a decision engine which can call for header
      modifications.  The rest of the packet takes another path and is
      later concatonated before sending out.  This works fine for
      checksum modifications but does not work for creating a new
      checksum.

  2.  A lot of high end hardware, particularly hardware intended for
      high end enterprise and data centers, uses a technique called
      "cut-through".  The first 128-256 bytes go to a decision engine
      and get processed before the packet has been entirely received.
      The decision and header modifications are done and if there is
      no standing output queue, the header starts going out before all
      of the packet has been received.  This is done to reduce
      latency.  In these implementations if the incoming FCS is bad,
      an outgoing runt packet occurs.

In the second case the UDP header is sent before the bytes over which
the UDP header is computed are received.  That is a consequence of
putting the UDP checksum before the data.  L2 encapsulation put the
FCS after the data for this reason.

So what you are asking, a UDP checksum on a fresh new encapsulation is
impossible for some hardware.  [ps - thanks to an offline discussion
with Joel Halpern for bringing this up.]

Perhaps we need a new UDP with a robust FCS at the back of the
packet, but without that making a UDP checksum manditory for MPLS over
UDP is guarenteed to be ignored in some deployments and with no
adverse consequences.  Is that what we want?

Perhaps there can be discussion added to the draft to indicate why a
UDP checksum is desirable and why in some circumstances it may be
impossible to generate or difficult to check.  This along with a
SHOULD use a UDP checksum might be the best course of action.

Curtis


> ________________________________________
> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 15 January 2014 03:43
> To: Wood L  Dr (Electronic Eng)
> Cc: stbryant@cisco.com; wes@mti-systems.com; curtis@ipv6.occnc.com; gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>  
> Lloyd,
>  
> The part about RFC 6936 section 3.1 most relevant might be:
>  
>    There is extensive experience with deployments using tunnel
>    protocols in well-managed networks (e.g., corporate networks and
>    service provider core networks).  This has shown the robustness of
>    methods such as Pseudowire Emulation Edge-to-Edge (PWE3) and MPLS
>    that do not employ a transport protocol checksum and that have not
>    specified mechanisms to protect from corruption of the unprotected
>    headers (such as the VPN Identifier in MPLS).  Reasons for the
>    robustness may include:
>  
> If the rate of undetected modified packets is extremely low in
> "well-managed networks", as we beleive is the case, then UDP checksums
> won't change the situration much.
>  
> So why *not* make them optional if experience has shown they are not
> needed in the types of deployments we are talking about.
>  
> Curtis
>  
>  
> In message <290E20B455C66743BE178C5C84F1240847E63346C6@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
> >
> > Stewart,
> >
> > your 'I'm not in tunnel applications' suggests you've misunderstood
> > the argument here. The point is not to protect the tunnel traffic
> > (which can quite happily checksum itself), it is to protect everything
> > else on the network from misdelivery. It's not the tunnel application,
> > it's every application sharing the internet with the tunnel which
> > has UDP checksums turned off. See all of  RFC 6936 section 3.1.
> > Tunnel is fine, sideeffects of misdelivery  do not affect tunnel.
> >
> > And in IPv4 and IPv6, the pseudo-header checksum built into
> > TCP and UDP is all we have. IPv6 deliberately copied v4 here.
> >
> > > What is the error rate in modern h/w and network systems?
> >
> > No-one measures end-to-end misdelivery. No-one knows.
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: Stewart Bryant [stbryant@cisco.com]
> > Sent: 14 January 2014 22:46
> > To: Wesley Eddy; Wood L  Dr (Electronic Eng); curtis@ipv6.occnc.com
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; randy@psg.com; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> > Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
> >
> > On 14/01/2014 22:07, Wesley Eddy wrote:
> > > On 1/14/2014 4:57 PM, l.wood@surrey.ac.uk wrote:
> > >> I don't think sayng 'oh, that error source is no longer a problem' disproves
> > >> Stone's overall point about undetected errors, though the
> > >> examples he uses from the technology of the day are necessarily
> > >> dated. Dismissing the overall  point because the examples use obsolete
> > >> technology is throwing the baby out with the bathwater; a host-to-host
> > >> error check catches things that intermediate checks cannot.
> > >>
> > >> Measuring error rates across end-to-end  Internet traffic is something that has
> > >> not received much attention , as error detection is not
> > >> instrumented well - hence citing Stone's published work,  in the absence
> > >> of awareness of anything newer (and as high profile/immediately recognisable
> > >> as sigcomm) in the area.
> > >>
> > >
> > > +1 ... the message in the paper is applicable to layered systems
> > > and internetworks in general.  Changes in the link technology
> > > since then don't invalidate it, especially since we know that
> > > the technology not only changes rapidly, but also is always
> > > growing in diverse directions, such that there things almost
> > > universally true today may be turned on their heads tomorrow.
> > >
> > > Designs for stacking layers need to follow solid general
> > > principles in order to be robust to changes (above and below).
> > >
> > Note that it is not only the link layer technology that has moved on,
> > the signal integrity of the h/w at all stages of the design and
> > implementation process has moved on.
> >
> > Can we agree that the statistics in the paper are discredited?
> >
> > If not, why not?
> >
> > What is the error rate in modern h/w and network systems?
> >
> > Is this significant in the application under consideration?
> >
> > Finally if we are really concerned that we do actually need a
> > c/s (I am not in tunnel applications) why are we still happy to
> > use what is frankly a pathetic check in modern terms? Why
> > for example are we not moving to something like
> > the  Fletcher 64 bit c/s?
> >
> > Stewart


From curtis@ipv6.occnc.com  Wed Jan 15 10:35:44 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7231AE125 for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 10:35:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CN_BODY_35=0.339, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-tsk8iN8cRE for <ietf@ietfa.amsl.com>; Wed, 15 Jan 2014 10:35:41 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 209251AE3D4 for <ietf@ietf.org>; Wed, 15 Jan 2014 10:35:40 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FIZK1E020750; Wed, 15 Jan 2014 13:35:21 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401151835.s0FIZK1E020750@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Wed, 15 Jan 2014 05:39:59 +0000." <290E20B455C66743BE178C5C84F1240847E63346C9@EXMB01CMS.surrey.ac.uk>
Date: Wed, 15 Jan 2014 13:35:20 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:12 -0800
Cc: mpls@ietf.org, ietf@ietf.org, xuxiaohu@huawei.com, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 18:35:44 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346C9@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> Curtis
>  
> http://lmgtfy.com/?q=Jonathan+Stone+CRC+checksum

That is the Sigcomm 2000 paper that a number of people have said is no
longer relevant, in some cases giving quite a bit of detail about the
error causes in the paper and why these will be rare today.  I thought
you were refering to something more recent.

> HDLC is just whatever is over the last hop. You said HDLC, I reused that as
> an example.

I gave HDLC as an example because in 2000 it was in use and a source
of errors but in 2014 it is likely not to be in use just about
anywhere in North America and Europe at least.

> Any link technology could be substituted - 10Mbps Ethernet, say, though
> you'd criticise that as not being 10Gbps Ethernet and therefore out of date.

My point was that if you substituted 10Mbps Ethernet with a 32 bit
FCS, for HDLC which often just counted and passed along errored
packets, you would have far fewer errors, almost none.

> Again, the point is that the link check is not end-to-end, and that errors
> can creep in from the most unexpected places. By analogy with security,
> if I have security across each hop, why would I need security end-to-end?
> I already have it across each hop! Each link is highly and absolutely
> unrbreakably secure! What is this end-to-end of which you speak?

You have security end to end because someone may have a motivation to
monitor or alter your packet.

If you have robust L2 FCS, then there is no one with a motivation to
disable that FCS and corrupt your data.  If they did for MPLS carrying
IP, then there is a check, albiet not a great one, that might catch
it.  If the MPLS payload is PW carrying a L2 carrying IP, same
applies.

Note that if the PW payload is TDM, Ethernet, or most other L2, at
least a checksum if not more is available in the payload so the errors
would be detected and the customer of the PW would complain.  Those
types of complaints have been a complete non-issue.

> If you don't get that point because it's a bit abstract and timeless, that's
> fine. (and if you have to explain the joke, the joke wasn't funny.)
> The link CRC doesn't apply across the entire path; do the maths for
> the path and a series of concatenated links.

The joke is that you didn't realize any mention of HDLC being used
now, just like X.25 being used now, was a joke.  It actually isn't
funny at all, except perhaps until someone doesn't get it.

> [As it happens, I'm familiar with UDP/IP/HDLC internet infrastructure installed
> within the decade and  in daily operational use to deliver imagery from orbit.
> But the paper I wrote on that dates from 2007, so is old and
> won't be of interest to you.]

That is clearly the exception.  TDM is still alive and well in the
third world and in access parts of the developed world that have not
been upgraded but elsewhere alternative exist for terestrial Internet
and TDM is gone from any non-third world network core that I am aware
of.

So don't run MPLS over UDP without a UDP checksum *on that
infrastructure* if you can avoid it.  But for most modern
infrastructures MPLS over UDP without a UDP checksum would be fine.

We are asking for a SHOULD, not a MUST NOT wrt UDP checksum.

> Wait, this thread is all about putting 90s MPLS technology over UDP
> technology specified in 1980. Clearly, if MPLS has to rely on an older
> technology in this way, the MPLS crowd should give up and go home. 

And MPLS carried nothing but IP in those days so from a error
detection standpoint it was and still is a NOOP.

> We've learned repeatedly that zero checksums are a bad idea. IPv6
> RFC2460:
>  
>         Unlike IPv4, when UDP packets are originated by an IPv6 node,
>          the UDP checksum is not optional.  That is, whenever
>          originating a UDP packet, an IPv6 node must compute a UDP
>          checksum over the packet and the pseudo-header, and, if that
>          computation yields a result of zero, it must be changed to hex
>          FFFF for placement in the UDP header.  IPv6 receivers must
>          discard UDP packets containing a zero checksum, and should log
>          the error.
>  
> which RFC6935 simply rewote as inconvenient to tunnelers without
> considering how it affected everything else in the network.

How it affects other everything else in the network should be
considered before ignoring a SHOULD, as is always the case.

> Those that do not learn from history are doomed to repeat it.
> (Unless it's recent history, in which case they're doomed to reject it
> as irrelevant.)
>  
> Lloyd Wood
> http://about.me/lloydwood

Lloyd.  There are a lot of papers that are still relevant.  Almost all
of the causes of errors studied in the 2000 network.  Apparently an
exception is your HDLC infrastructure, and that would be gone too as
an issue if 32 bit CRC is enabled for HDLC and packets dropped on
error, not just counted.

That paper reported:

   2,209 M packets

   468,434 errors
   389,934 ACK-of-FIN bug (old Window NT bug, fixed)
    78,500 remaining
   Other errors cited but often not quantified
     CRLF replacement (thought to be Solaris bug)
     VJHC or other header comprssion bug
     possible PowerMac OS-X bug (fixed by publication)
     router memory error (ECC is used now)
     bad host DMA (PCIe has CRC32 today)

The paper has a breakdown by type of error and discussion of the
causes.  In some cases a particular type of error came mostly from a
small set of hosts but the cause is only likely to be host related
and the entire type of error category can't with certainty be
attributed to host error.

   Bad Hosts

      Another surprise in our traces was the large fraction of errors
      where are due to persistantly-misbehaving hosts.

In fact the paper says:

   In general, link errors should be caught by the CRC.  However there
   are cases where the link level protocol can interact to cause
   higher level checksum errors.  The most notable situation is header
   compression and we looked vigorously for errors of this sort.

Link errors are really not considered in the paper as a significant
source of errors.  Router memory and other hardware errors are cited
but with today's hardware those types of errors should also be gone.

I discussed the sources of errors in this paper previously in
  http://www.ietf.org/mail-archive/web/mpls/current/msg11247.html
You did respond to that but only by top posting and ignoring the
discussion in that email of the causes of errors in the paper.

"No longer relevant" does not mean "not good work".  It would be worth
it for the Stone/Partridge study to be repeated.  For this context it
would have to be with cooperation of a provider and over the type of
infrastructure that MPLS is intended to be run.

Curtis

> ________________________________________
> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 15 January 2014 01:42
> To: Wood L  Dr (Electronic Eng)
> Cc: curtis@ipv6.occnc.com; jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@huawei.com; mpls@ietf.org; ietf@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> In message <290E20B455C66743BE178C5C84F1240847E63346C4@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>  
> > The HDLC part here is last link, not the scope of the whole path.  Any
> > 'low' bit error rate given actually becomes quite high once you
> > consider no of bits per packet and line rate...
> >
> > Do read Jonathan Stone's papers on where errors creep in - not just in
> > the link, by at any point along the path, including regeneration
> >
> > Lloyd Wood
>  
>  
> Lloyd,
>  
> There is no HDLC hop.  No one has used HDLC for internet
> infrastructure in ages.  It was a joke, like Scott's comment on
> wanting to use X.25.  HDLC was disappearing when the Stone/Partridge
> Sigcomm 2000 paper was written.
>  
> Links please.  And how old is that paper?  Not another 15 year old
> work is it?
>  
> If you have one bit error per day, how many packets do you lose that
> day?  (hint: one).
>  
> If you have one bit error per day, how many undetactable packet errors
> do you have?  (hint: crc32 gets all one bit errors, therefore zero).
>  
> 10^-12 bit errors is one per 10 second on 100 Gb/s, one per 100 second
> on 10 Gb/s and is generally considered high enough to take a link down
> immediately.  A 1500 byte packet is 12,000 bits, about ~10^4.  That
> would yield a packet rate as high as 10^-8 if bit errors were mostly
> one bit error per packet.  In that case all errors would be
> detectable.  It is only when there are a lot of bit errors or more per
> packet that the CRC can be defeated and then its about 10^-9 chance.
>  
> So at an error rate much less than 10^-8 packets (tightly bunched
> errors with multiple bit errors per packet) some 10^-9 might be
> undetectable with a CRC32.  One packet every 10^6 seconds at 100 Gb/s
> could have an undetectable error.  About one undetectable error a day
> or one a week for continuous full out 100 Gb/s link.
>  
> Note that the same low error rate does not apply to a GbE or 10GbE
> over colored optics over ROADM in the metro since there is no FEC
> there.  It also may not apply to the enterprise or campus Ethernets.
> In those hops the error rate is likely to be higher.  Needless to say,
> wireless hops can have very high error rates.
>  
> This is why it could make sense to have the UDP checksum optional in
> MPLS over UDP.  It wouldn't hurt to provide the checksums but in some
> cases it might be OK to disable them.  That is what SHOULD is for in
> an IETF document.
>  
> Curtis
>  
>  
> > From: Curtis Villamizar [curtis@ipv6.occnc.com]
> > Sent: 14 January 2014 20:54
> > To: Wood L  Dr (Electronic Eng)
> > Cc: jmh@joelhalpern.com; lars@netapp.com; xuxiaohu@huawei.com; mpls@ietf.org; ietf@ietf.org
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
> >
> > In message <290E20B455C66743BE178C5C84F1240847E63346C3@EXMB01CMS.surrey.ac.uk>
> > l.wood@surrey.ac.uk writes:
> >
> > > It stands to reason that if tunnelers can turn off udp checksums
> > > because their performance is degraded, they can turn off
> > > congestion control because it will degrade their performance.
> > >
> > > Rest of the internet getting congested and getting
> > > misdelivered corrupted packets? Really not their problem.
> > >
> > > There are important vendors trying to sell products here,
> > > and they need performance to do so.
> > > Get with the program!
> > >
> > > Lloyd Wood
> > > http://about.me/lloydwood
> >
> >
> > OK, perhaps if you are running MPLS/UDP/IP over HDLC and the HDLC
> > configuration is set to count FCS errors but not drop you will still
> > *really* need the UDP checksum.  Otherwise its isn't going to do much
> > for you.  Any checksum is really bad for some types of errors such as
> > chunk reordering and multiple bit errors.
> >
> > Maybe on HDLC or PPP with 16 bit CRC you may see a low error rate, but
> > in theory that would be much less than 10^-5 since few multiple bit
> > errors will be coincidence match the CRC, even for a 16 bit CRC.
> >
> > I suspect most routers would be able to do the checksum anyway and for
> > modern links if they come up with a zero error count that's fine.
> >
> > <ot>
> >
> > Modern OTN based transport networks use forward error correction FEC
> > which accounts for a fair amount of overhead and a lot of processing
> > gates on the receiving end.  The measure of effectiveness of given FEC
> > is in dB with 10 dB being a reduction of a factor of 10 in bit errors
> > and typical FEC in the high tens of dB.  The target corrected error
> > rate is often 10^-15 or one bit error in 24 hours for 10 Gb/s, one bit
> > error in 2.5 hours for 100 Gb/s.  Any link with corrected bit error
> > rates approaching 10^-12 is taken out of service.  This is roughly
> > equivalent to the old ES (errored seconds) and SES (severely errored
> > seconds) metric where a ES is one second with any bit errors and an
> > SES is one second with 10 or more errors (I think its 10).  More than
> > some number of ES or SES and a link is taken down.  The uncorrected
> > errors are passed through.
> >
> > A packet may traverse an entire continent with 2-3 such links
> > separated by regeneration or could stop at a number of routers along
> > the way.  Typically today the router uses 10GbE or 100GbE (growing
> > use) which are then passed as a bit stream in the transport network.
> > At the other end the uncorrected errors from transport are picked up
> > by Ethernet 32 bit FCS.  Since a 32 bit FCS picks up 100% of single
> > bit errors and most instances where a small number of bits are in
> > error, and all but 1 in 2^32 where many bits are in error, few errors
> > are going to get through.  If GFP is used, the per packet FCS is
> > checked at each hop and for GFP-T also checked end to end.
> >
> > A bad local ethernet is more likely to contribute an error (again
> > better than 1 in 2^32 detection is expected) due to something like a
> > bad CAT-{5,5e,6} connection or too many sharp turns.  A DSL or DOCSIS
> > link is also more likely to contribute an error.  With CRC32 on all
> > links and no bad hardware in between (ie: circa 1990s equipment with
> > no parity RAM and no correction on DMA, buses, etc) you would expect
> > on the order of 10^-8 errors (10^-9 per hop, a few errored hops).
> >
> > For example, two hosts on my home LAN had non-zero tcp checksums.
> > Each had < 10^-6 packet error rate.  It is hard to tell if this is
> > host errors at the other end.  The only hosts I have with non-zero are
> > on the service provider DMZ LAN so that would include any bot attacks,
> > etc, where sending hosts could be old junk.  Host behind those have
> > zero UDP and TCP checksum errors.  This seems similar to Stewart's
> > quick check.
> >
> > In the T1/T3 days the transport layer just had parity and just counted
> > parity errors.  Providers in those days were notorious for ignoring ES
> > and SES counters until the customer complained.  HDLC then had its 16
> > bit CRC, optional 32 bit.  If an ISP wasn't paying attention to their
> > HDLC error counters then it was up to the IP end customer to complain
> > and hope the problem got escallated rather than dropped.
> >
> > </ot>
> >
> > As to whether congestion control is in practice needed see
> > http://www.ietf.org/mail-archive/web/mpls/current/msg11222.html
> >
> > Its fine to make them both optional and to make congestion control
> > mechanisms out of scope and the topic of a later document if needed.
> >
> > Curtis
> >
> >
> >
> > > ________________________________________
> > > From: ietf [ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern [jmh@joelhalpern.com]
> > > Sent: 10 January 2014 15:36
> > > To: Eggert, Lars; Xuxiaohu
> > > Cc: mpls@ietf.org; IETF
> > > Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
> > >
> > > Maybe I am completely missing things, but this looks wrong.
> > > If the MPLS LSP is carrying fixed rate pseudo-wires, adding congestion
> > > control will make it more likely that the service won't work.  Is that
> > > really the goal?
> > >
> > > We do not perform congestion control on MPLS LSPs.
> > > Assuming that a UDP tunnel is carrying just MPLS and was established
> > > just for MPLS, why would we expect it to behave differently than an MPLS
> > > LSP running over the exact same path, carrying the exact same traffic?
> > >
> > > Yours,
> > > Joel
> > >
> > > On 1/10/14 3:47 AM, Eggert, Lars wrote:
> > > > Hi,
> > > >
> > > > that sounds good. What congestion control are you going to be specifying for your tunnel?
> > > >
> > > > Lars
> > > >
> > > > On 2014-1-10, at 4:46, Xuxiaohu <xuxiaohu@huawei.com> wrote:
> > > >
> > > >> Hi Lars,
> > > >>
> > > >> Thanks a lot for your comments.
> > > >>
> > > >> I wonder whether the following modified text for Congestion Consideration section is OK from your point of view:
> > > >>
> > > >> Since the MPLS-in-UDP encapsulation causes MPLS packets to be forwarded through "UDP tunnels", the congestion control guidelines for UDP tunnels as defined in Section 3.1.3 of [RFC5405] SHOULD be followed. Specifically, MPLS can carry a number of different protocols as payloads. When the payload traffic is IP-based and congestion-controlled, the UDP tunnel SHOULD NOT employ its own congestion control mechanism, because congestion losses of tunneled traffic will already trigger an appropriate congestion response at the original senders of the tunneled traffic. When the payload traffic is not known to be IP-based, or is known to be IP-based but not congestion-controlled, the UDP tunnel SHOULD employ an appropriate congestion control mechanism. Furthermore, because UDP tunnels are usually bulk-transfer applications as far as the intermediate routers are concerned, the guidelines as defined in Section 3.1.1 of [RFC5405] SHOULD apply.
> > > >>
> > > >> Best regards,
> > > >> Xiaohu
> > > >>
> > > >>> -----ÓÊ¼þÔ­¼þ-----
> > > >>> ·¢¼þÈË: mpls [mailto:mpls-bounces@ietf.org] ´ú±í Eggert, Lars
> > > >>> ·¢ËÍÊ±¼ä: 2014Äê1ÔÂ8ÈÕ 18:22
> > > >>> ÊÕ¼þÈË: IETF
> > > >>> ³­ËÍ: mpls@ietf.org
> > > >>> Ö÷Ìâ: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS
> > > >>> in UDP) to Proposed Standard
> > > >>>
> > > >>> Hi,
> > > >>>
> > > >>> On 2014-1-2, at 16:14, The IESG <iesg-secretary@ietf.org> wrote:
> > > >>>> - 'Encapsulating MPLS in UDP'
> > > >>>> <draft-ietf-mpls-in-udp-04.txt> as Proposed Standard
> > > >>>
> > > >>>
> > > >>> this document needs to describe how it addresses the issues raised in BCP145
> > > >>> (RFC5405). It already contains some text about messages sizes and congestion
> > > >>> considerations, which is great. Unfortunately, the text about congestion
> > > >>> considerations is not fully in line with RFC5405.
> > > >>>
> > > >>> Lars
> > > >
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls


From curtis@ipv6.occnc.com  Wed Jan 15 11:20:13 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFFB1AE389; Wed, 15 Jan 2014 11:20:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_37=0.6, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hUfHYSR1KgAw; Wed, 15 Jan 2014 11:20:11 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id F38761AE378; Wed, 15 Jan 2014 11:20:10 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FJJuT0021269; Wed, 15 Jan 2014 14:19:56 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401151919.s0FJJuT0021269@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Wed, 15 Jan 2014 05:45:43 +0000." <290E20B455C66743BE178C5C84F1240847E63346CA@EXMB01CMS.surrey.ac.uk>
Date: Wed, 15 Jan 2014 14:19:56 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:54 -0800
Cc: mpls@ietf.org, ietf@ietf.org, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 19:20:13 -0000

Lloyd,

Suggesting MPLS over TCP brings us back to the X.25 comment.

You can do PPP in TCP.  It has the benefit of getting a tunnle past
firewalls.  It has the drawback of TCP over IP over PPP over TCP where
the upper and lower TCPs don't know about each other and interact,
with the upper TCP doing redundant retransmits and a lot of
unnecessary retransmits when the lower TCP is stalled.  As a host
solution this particular tunnel over TCP serves a purpose.

As a router solution, a tunnel over TCP would cause massive redundant
or unnecessary retransmits due to lots of TCP running over it unaware
that retransmits are occurring at a lower layer.

Another problem is the TCP state that would have to be held in
hardware.  Normally the router functions that use TCP are in the
control plane and in software.  All packets would also have to be
bufferred in hardware until acknowledged.

There are the save feasibility issues with a TCP checksum in most high
end hardware.

MPLS over TCP would likely be only feasible if done in software and
therefore is not an appropriate solution for the deployment scenarios
considered for MPLS over UDP.

There are congestion control mechanisms that would be feasible for
MPLS over UDP but mostly involve feedback, the programming of a leaky
bucket, aka traffic shaper, and (preferably) some form of AQM on the
shaper queue.  This would involve no retransmissions and use the types
of hardware building blocks available in forwarding chips.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346CA@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
> 
> this draft should be about mpls in TCP - a TCP tunnel.
>  
> That will fix all congestion concerns.
>  
> I look forward to reading justification of why TCP checksums can be turned off.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: mpls [mpls-bounces@ietf.org] On Behalf Of Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 15 January 2014 01:00
> To: Eggert, Lars
> Cc: mpls@ietf.org; Scott Brim; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt>  (Encapsulating MPLS in UDP) to Proposed Standard
>  
> In message <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
> "Eggert, Lars" writes:
>  
> > Hi,
> >
> > On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> > > Isn't that basically the problem of the inner traffic sender, not the
> > > problem of the tunnel that is carrying the traffic?
> >
> > no, because the sender of the inner traffic may be blasting some
> > L2traffic, for an L2 where that is OK behavior. But that traffic is
> > nowbeing encapsulated inside UDP and can hence go anywhere on the
> > net*without the sender being aware of this*.
>  
> That application would be a PW application and it would be more
> appropriate to fix that in PW if there is consensus for a need to do
> so, which afaik there is not.
>  
> > > Asking tunnel's to solve the problem of applications with
> > > undesirablebehavior seems backwards.
> >
> > It is the *tunnel* that performs the encapsulation and allows
> > thattraffic to go places it couldn't before. And so it's the
> > tunnel'sresponsibility to make sure that the traffic it injects into
> > theInternet complies with the BCPs we have on congestion control.
> >
> > Lars
>  
> If it is a service provider encapsulating traffic within their own
> network, then they know what they are doing.  That is the anticipated
> use and among that community there is no consensus for need for
> congestion control.
>  
> If it is some hostile hosts trying to send MPLS over UDP over IP,
> they, being hostile, are going to disable any congestion control.
> Besides, no hostile host has a T1 to tunnel over the Internet so they
> would be sending the same traffic they would normally just send of UDP
> over IP.
>  
> Anything made up of frames (Ethernet, ATM, FR) over PW over MPLS is
> carrying IP and if frames drop, the IP applications see the drop and
> behave just as they would for any drop.  (ATM shreadding thread to
> /dev/null please).
>  
> If congestion aware or using a congestion aware transport, the top
> level applications are still congestion aware.  If congestion
> ignoreant, they are still congestion ignoreant.  If hostile, they are
> still hostile.
>  
> Back to draft-ietf-mpls-in-udp.  I think the most recent text proposed
> by the author is fine.
>  
> Curtis
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From curtis@ipv6.occnc.com  Wed Jan 15 12:02:29 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E2231AE1A6; Wed, 15 Jan 2014 12:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BFERJXjAteJ6; Wed, 15 Jan 2014 12:02:28 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 30DF71AE199; Wed, 15 Jan 2014 12:02:28 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FK28cx022175; Wed, 15 Jan 2014 15:02:08 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152002.s0FK28cx022175@maildrop2.v6ds.occnc.com>
To: Randy Bush <randy@psg.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Wed, 15 Jan 2014 17:08:09 +0600." <m2a9exmrja.wl%randy@psg.com>
Date: Wed, 15 Jan 2014 15:02:07 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:54 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, Stewart Bryant <stbryant@cisco.com>, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:02:29 -0000

In message <m2a9exmrja.wl%randy@psg.com>
Randy Bush writes:
> 
> [ you insist on cc:ing me, so you get to endure my opinions ]

Not a problem (this time).  :-)

> > it seems that there are no valid statistics for the current Internet
> > to sustain your case.
>  
> as we discussed privately, there seem to be no real measurements to
> sustain any case.  this is all conjecturbation.
>  
> what i do not understand is why, given the lack of solid evidence that
> we are in a safe space, you and others are not willing to spend a few
> euro cents to have a reasonable level of assurance at this layer.
>  
> randy


Randy,

See http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
for reasons why routers would want to avoid having to fill in a
checksum.  It would have been more feasible for an FCS at the end of
the packet for these cases but the UDP checksum is in the front.

This entire discussion is over putting in a SHOULD rather than a MUST
in two places, UDP checksum and congestion control, plus deferring
defining the congestion control for MPLS over UDP until deployments
show a need for it.

Curtis

From curtis@ipv6.occnc.com  Wed Jan 15 12:05:53 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBC2C1AE389; Wed, 15 Jan 2014 12:05:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AVnar5yR1lmb; Wed, 15 Jan 2014 12:05:52 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 5B50A1AE373; Wed, 15 Jan 2014 12:05:52 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FK5VIU022303; Wed, 15 Jan 2014 15:05:31 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152005.s0FK5VIU022303@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Wed, 15 Jan 2014 11:57:18 +0000." <290E20B455C66743BE178C5C84F1240847E63346CB@EXMB01CMS.surrey.ac.uk>
Date: Wed, 15 Jan 2014 15:05:31 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:54 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, stbryant@cisco.com, jnc@mit.edu, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:05:54 -0000

Or perhaps UDP heavy with a FCS at the end and no checksum at all.

You do make a good point that perhaps UDP lite should be mentioned in
MPLS over UDP as an option.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346CB@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> you've got the perfect application to encourage UDP lite adoption and
> deployment here.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Stewart Bryant [stbryant@cisco.com]
> Sent: 15 January 2014 11:31
> To: Randy Bush
> Cc: Wood L  Dr (Electronic Eng); wes@mti-systems.com; curtis@ipv6.occnc.com; gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>  
> On 15/01/2014 11:08, Randy Bush wrote:
> > [ you insist on cc:ing me, so you get to endure my opinions ]
> >
> >> it seems that there are no valid statistics for the current Internet
> >> to sustain your case.
> > as we discussed privately, there seem to be no real measurements to
> > sustain any case.  this is all conjecturbation.
> >
> > what i do not understand is why, given the lack of solid evidence that
> > we are in a safe space, you and others are not willing to spend a few
> > euro cents to have a reasonable level of assurance at this layer.
> >
> > randy
> Randy,
>  
> It is not a few cents, it is likely the re-engineering of a lot
> of silicon.
>  
> The reason that UDP is of interest is that the on path silicon
> knows how to process it, for example it knows how to to ECMP it.
>  
> The reason that the UDP c/s is a problem for a tunneler is that
> it needs to have access to the whole pkt to calculate the
> c/s, but as you know the silicon optimised that access away
> a long time ago.
>  
> The alternative would be UDP-lite, but the ability of on path
> silicon to process that as competently and as completely as it
> processes UDP is by no means clear.
>  
> - Stewart


From curtis@ipv6.occnc.com  Wed Jan 15 12:34:59 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 413911AE19A; Wed, 15 Jan 2014 12:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cb0wpl-l9VAq; Wed, 15 Jan 2014 12:34:57 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1D1EB1AE0D5; Wed, 15 Jan 2014 12:34:57 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FKYYKO022696; Wed, 15 Jan 2014 15:34:34 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152034.s0FKYYKO022696@maildrop2.v6ds.occnc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Wed, 15 Jan 2014 11:54:17 +0000." <eaca6d98b34045ba9e08c43417507997@AM3PR03MB532.eurprd03.prod.outlook.com>
Date: Wed, 15 Jan 2014 15:34:34 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:54 -0800
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>, "jnc@mit.edu" <jnc@mit.edu>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:34:59 -0000

In message <eaca6d98b34045ba9e08c43417507997@AM3PR03MB532.eurprd03.prod.outlook.com>
Alexander Vainshtein writes:
> 
> Stewart, and all,
>  
> I fully agree that UDP checksums is not a real-life issue with the
> protocol in question. They could probably help to check corrupted
> packets if corruption happens when a packet passes thru a router
> (i.e. when the ingress data link FCS has already been terminated and
> the egress data link FCS has not been generated yet). But this is
> hopefully rare - and since MPLS does not care about it, why should the
> MPLS encapsulator care?

Why the MPLS over UDP encapsulation cares is in
http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html

> I also do not think that congestion control is a serious issue for
> this protocol, not in the least because the primary purpose of this
> protocol is ECMP.

The chips I had worked with all did a lookup and retrieved a next-hop
index.  That could point to a single hop or and entry into the
multipath hardware gunk (tables for some not so good implementations).

My guess is Stewart is concerned about hardware than can lookup an IP
adddress and do multipath but not do an MPLS ILM lookup and then do
multipath.  [I find that hard to believe since it would be tough to do
MPLS over a LAG.  Most chips that had not anticipated this could do
this with firmware changes because there was enough flexibility in the
hardware intended for LAG to get the job done.  Some might have
limitations with ECMP where component links of the ECMP were LAG.
OTOH the further you go back in time the more severe chip limitations
you will run into.]

IMHO the draft should remove the ECMP motivation from the introduction
and then there would be no need to debate this.  The draft need only
define the protocol.

> But I would like to understand whether this protocol can really result
> in reasonable distribution of traffic. "Reasonable" means that (a)
> there is sufficient entropy and (b) that the order in specific
> micro-flows is preserved. The draft skips this issue (unless you
> consider a recommendation to use a fixed randomly selected source port
> value if the tunnel does not need ECMP a valid answer) .
>  
> Any ideas as to how reasonable distribution of traffic can be achieved
> with this protocol?

ECMP has been around for a long time and providers carefully tune IGP
metrics to get a better but often not very good load balance with
ECMP.

With other multipath methods you can get non-equal load balance and
remove the equal cost limitiation but that might need more recent
hardware than Steward and others are faced with.

ECMP is a blunt tool.

> Regards,
>        Sasha 
> Email: Alexander.Vainshtein@ecitele.com
> Mobile: 054-9266302

Curtis


> > -----Original Message-----
> > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Stewart Bryant
> > Sent: Wednesday, January 15, 2014 1:31 PM
> > To: Randy Bush
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org;
> > wes@mti-systems.com; tsvwg@ietf.org; jnc@mit.edu
> > Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-
> > udp draft (was: RE: Milestones changed for tsvwg WG))
> > 
> > On 15/01/2014 11:08, Randy Bush wrote:
> > > [ you insist on cc:ing me, so you get to endure my opinions ]
> > >
> > >> it seems that there are no valid statistics for the current Internet
> > >> to sustain your case.
> > > as we discussed privately, there seem to be no real measurements to
> > > sustain any case.  this is all conjecturbation.
> > >
> > > what i do not understand is why, given the lack of solid evidence that
> > > we are in a safe space, you and others are not willing to spend a few
> > > euro cents to have a reasonable level of assurance at this layer.
> > >
> > > randy
> > Randy,
> > 
> > It is not a few cents, it is likely the re-engineering of a lot of silicon.
> > 
> > The reason that UDP is of interest is that the on path silicon knows how to
> > process it, for example it knows how to to ECMP it.
> > 
> > The reason that the UDP c/s is a problem for a tunneler is that it needs to
> > have access to the whole pkt to calculate the c/s, but as you know the silicon
> > optimised that access away a long time ago.
> > 
> > The alternative would be UDP-lite, but the ability of on path silicon to process
> > that as competently and as completely as it processes UDP is by no means
> > clear.
> > 
> > - Stewart

From curtis@ipv6.occnc.com  Wed Jan 15 12:49:07 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 848D51AE248; Wed, 15 Jan 2014 12:49:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id reuQK5rr6cLn; Wed, 15 Jan 2014 12:49:05 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3B9DA1AE0D5; Wed, 15 Jan 2014 12:49:04 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0FKmlsn022848; Wed, 15 Jan 2014 15:48:48 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401152048.s0FKmlsn022848@maildrop2.v6ds.occnc.com>
To: gorry@erg.abdn.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
In-reply-to: Your message of "Wed, 15 Jan 2014 20:18:11 +0000." <b09d482e8df3c33f97fa0c26a40393b8.squirrel@www.erg.abdn.ac.uk>
Date: Wed, 15 Jan 2014 15:48:47 -0500
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:07:54 -0800
Cc: mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, curtis@ipv6.occnc.com, jnc@mit.edu, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:49:07 -0000

In message <b09d482e8df3c33f97fa0c26a40393b8.squirrel@www.erg.abdn.ac.uk>
gorry@erg.abdn.ac.uk writes:
> 
> You may care to reference this to Section 2.2 of RFC 6936, which provides
> some background to where UDP-Lite may help, and some of the potential
> pitfalls.
>  
> Gorry


The right tool for the job but ...

Expect some pushback because older hardware looks at TCP and UDP in
the protocol field and then checks port numbers for ECMP load
balance.  That older hardware will not do this for UDP-Lite.

With MPLS over UDP, only the dest port number matters and the src port
number can be used like the MPLS Entropy Label.  That is about the
only thing that would not work in some networks with UDP-Lite.

IMHO it would be advantageous to provide the option to use UDP-Lite
rather than UDP with no checksum at all.  The section in RFC 6936
could be cited.  The limitation I mentioned could also be cited.

Curtis


> > Or perhaps UDP heavy with a FCS at the end and no checksum at all.
> >
> > You do make a good point that perhaps UDP lite should be mentioned in
> > MPLS over UDP as an option.
> >
> > Curtis
> >
> >
> > In message
> > <290E20B455C66743BE178C5C84F1240847E63346CB@EXMB01CMS.surrey.ac.uk>
> > l.wood@surrey.ac.uk writes:
> >
> >> you've got the perfect application to encourage UDP lite adoption and
> >> deployment here.
> >>
> >> Lloyd Wood
> >> http://about.me/lloydwood
> >> ________________________________________
> >> From: Stewart Bryant [stbryant@cisco.com]
> >> Sent: 15 January 2014 11:31
> >> To: Randy Bush
> >> Cc: Wood L  Dr (Electronic Eng); wes@mti-systems.com;
> >> curtis@ipv6.occnc.com; gorry@erg.abdn.ac.uk; mpls@ietf.org;
> >> ietf@ietf.org; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
> >> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE:
> >> gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
> >>
> >> On 15/01/2014 11:08, Randy Bush wrote:
> >> > [ you insist on cc:ing me, so you get to endure my opinions ]
> >> >
> >> >> it seems that there are no valid statistics for the current Internet
> >> >> to sustain your case.
> >> > as we discussed privately, there seem to be no real measurements to
> >> > sustain any case.  this is all conjecturbation.
> >> >
> >> > what i do not understand is why, given the lack of solid evidence that
> >> > we are in a safe space, you and others are not willing to spend a few
> >> > euro cents to have a reasonable level of assurance at this layer.
> >> >
> >> > randy
> >> Randy,
> >>
> >> It is not a few cents, it is likely the re-engineering of a lot
> >> of silicon.
> >>
> >> The reason that UDP is of interest is that the on path silicon
> >> knows how to process it, for example it knows how to to ECMP it.
> >>
> >> The reason that the UDP c/s is a problem for a tunneler is that
> >> it needs to have access to the whole pkt to calculate the
> >> c/s, but as you know the silicon optimised that access away
> >> a long time ago.
> >>
> >> The alternative would be UDP-lite, but the ability of on path
> >> silicon to process that as competently and as completely as it
> >> processes UDP is by no means clear.
> >>
> >> - Stewart


From gorry@erg.abdn.ac.uk  Wed Jan 15 12:18:26 2014
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94FFB1AE19A; Wed, 15 Jan 2014 12:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.739
X-Spam-Level: 
X-Spam-Status: No, score=-4.739 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tprr68sz72YW; Wed, 15 Jan 2014 12:18:24 -0800 (PST)
Received: from spey.erg.abdn.ac.uk (spey.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 119351AE112; Wed, 15 Jan 2014 12:18:24 -0800 (PST)
Received: from www.erg.abdn.ac.uk (blake.erg.abdn.ac.uk [139.133.210.30]) by spey.erg.abdn.ac.uk (Postfix) with ESMTPSA id 7E0802B4230; Wed, 15 Jan 2014 20:18:11 +0000 (GMT)
Received: from 212.159.18.54 (SquirrelMail authenticated user gorry) by www.erg.abdn.ac.uk with HTTP; Wed, 15 Jan 2014 20:18:11 -0000
Message-ID: <b09d482e8df3c33f97fa0c26a40393b8.squirrel@www.erg.abdn.ac.uk>
In-Reply-To: <201401152005.s0FK5VIU022303@maildrop2.v6ds.occnc.com>
References: <201401152005.s0FK5VIU022303@maildrop2.v6ds.occnc.com>
Date: Wed, 15 Jan 2014 20:18:11 -0000
Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
From: gorry@erg.abdn.ac.uk
To: curtis@ipv6.occnc.com
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Mailman-Approved-At: Thu, 16 Jan 2014 08:09:00 -0800
Cc: gorry@erg.abdn.ac.uk, mpls@ietf.org, lisp@ietf.org, ietf@ietf.org, tsvwg@ietf.org, jnc@mit.edu, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Jan 2014 20:18:26 -0000

You may care to reference this to Section 2.2 of RFC 6936, which provides
some background to where UDP-Lite may help, and some of the potential
pitfalls.

Gorry

>
> Or perhaps UDP heavy with a FCS at the end and no checksum at all.
>
> You do make a good point that perhaps UDP lite should be mentioned in
> MPLS over UDP as an option.
>
> Curtis
>
>
> In message
> <290E20B455C66743BE178C5C84F1240847E63346CB@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>
>> you've got the perfect application to encourage UDP lite adoption and
>> deployment here.
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: Stewart Bryant [stbryant@cisco.com]
>> Sent: 15 January 2014 11:31
>> To: Randy Bush
>> Cc: Wood L  Dr (Electronic Eng); wes@mti-systems.com;
>> curtis@ipv6.occnc.com; gorry@erg.abdn.ac.uk; mpls@ietf.org;
>> ietf@ietf.org; tsvwg@ietf.org; jnc@mit.edu; lisp@ietf.org
>> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE:
>> gre-in-udp draft (was: RE: Milestones changed for tsvwg WG))
>>
>> On 15/01/2014 11:08, Randy Bush wrote:
>> > [ you insist on cc:ing me, so you get to endure my opinions ]
>> >
>> >> it seems that there are no valid statistics for the current Internet
>> >> to sustain your case.
>> > as we discussed privately, there seem to be no real measurements to
>> > sustain any case.  this is all conjecturbation.
>> >
>> > what i do not understand is why, given the lack of solid evidence that
>> > we are in a safe space, you and others are not willing to spend a few
>> > euro cents to have a reasonable level of assurance at this layer.
>> >
>> > randy
>> Randy,
>>
>> It is not a few cents, it is likely the re-engineering of a lot
>> of silicon.
>>
>> The reason that UDP is of interest is that the on path silicon
>> knows how to process it, for example it knows how to to ECMP it.
>>
>> The reason that the UDP c/s is a problem for a tunneler is that
>> it needs to have access to the whole pkt to calculate the
>> c/s, but as you know the silicon optimised that access away
>> a long time ago.
>>
>> The alternative would be UDP-lite, but the ability of on path
>> silicon to process that as competently and as completely as it
>> processes UDP is by no means clear.
>>
>> - Stewart
>


From hsantos@isdg.net  Thu Jan 16 09:03:45 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016D11AE157 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:03:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.08
X-Spam-Level: 
X-Spam-Status: No, score=-103.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgXRekE4MtVA for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:03:40 -0800 (PST)
Received: from mail.catinthebox.net (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 67B7F1AE10F for <ietf@ietf.org>; Thu, 16 Jan 2014 09:03:40 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=7807; t=1389891802; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=npSpJhCjnS71Xx+0lOFnF5gZlvI=; b=pCk9CeQ0xCHzOXpmPaBx SCBn4BAlZAGqAdbiqsPZa05qYnIZU8oa7oYkdCPMfBK26qQHkVT4BqL8tKD72yJk +XxQPCXF6QfI4Gmp/GhscoCdka+UDRD7v6O0l5wf8icUtMhQOcUupW9kukHNwbeF buMWaJAIlZRlMiQ8buo6KxQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 16 Jan 2014 12:03:22 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3469268972.3.5540; Thu, 16 Jan 2014 12:03:20 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=7807; t=1389890933; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=CHbT4fi Yx2mnsBoFBbMSG5u2U4RVhK8xPFLwWBHD+ko=; b=jdHxGAIcHm+++rwIfqVJGdo EuaFnJsmsFoXHKX+v/GzOGm+nzYnagcHxz9KfBtml+twxM6dNIab64vdnJtPK0Pv gx5Fg6PM6IF/9x8VCwZWSaeL4pO4Aa4GsBek5O73piOj3vYMnoSCy5+A8SDfie87 rfKLsrxOmFmliGnuhpDw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 16 Jan 2014 11:48:53 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2915279802.9.9020; Thu, 16 Jan 2014 11:48:52 -0500
Message-ID: <52D80FAF.8040301@isdg.net>
Date: Thu, 16 Jan 2014 11:58:23 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Fwd: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie> <52D7D63E.7010506@cs.tcd.ie>
In-Reply-To: <52D7D63E.7010506@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:03:45 -0000

What I found interesting is the itemized STRINT question:

      How realistic is it to not be fingerprintable on the web and 
Internet?

Like its a foregone conclusion it is already too late.  If we are 
literally talking about "fingerprints" well, we already have a major 
vendor, probably the most significant one at present, that has opened 
that can of worms.  Of course, I'm referring to Apple's TouchID with 
the iPhone 5S.

Part of the problem in all this is the business, social engineering 
ethics in these architectural decisions, which is increasingly more 
market related.  So I wonder if its realistic to even ponder:

     As a security rule of thumb, should systems first consider NOT 
introducing
     "fingerprints" or identification methods without having 
protection for users?

Its a different way of thinking -- sometimes you just "Don't do it" 
unless you are 100% sure you can do it right.

Its a great idea, but surely it will be leverage, exploited and 
somehow, one way or another, inevitably, besides the advertisement 
market, the government, policing agencies will want access to the huge 
database of fingerprints or "identification tokens," of course, in the 
name of security, to search a person of interest for the closest match.

The IETF has the ethics document RFC1087.  I have asked if anyone 
believes this should be updated.  Surely this is tied to PM. Odd. It 
seems odd no one doesn't seem to think it needs to be updated.  I 
don't see the PM draft reference it.  Should it? I think so, and this 
RFC1087 document SHOULD be updated.

Anyway, we will be competing with business market pressures and these 
PM related issues most likely boil down to ethical principles which 
has changed over years.  We have new a new generation of 
"Infopreneurs" who surely do not have the same mindset for design 
engineering "taboos," in fact, its natural to consider that 
unrestricted communications is the norm.

--
HLS


On 1/16/2014 7:53 AM, Stephen Farrell wrote:
>
> And as is traditional, we've added a few days:-)
>
> Final deadline is end of Monday Jan 20 anywhere
> on Earth (== 1200 UTC Jan 21). And that will be
> a hard deadline.
>
> There's also a bit more logistics stuff now at [1].
>
> Cheers,
> S.
>
> [1] https://www.w3.org/2014/strint/
>
> On 01/09/2014 01:55 PM, Stephen Farrell wrote:
>>
>> Folks, submissions are starting to roll in so this is
>> a reminder to send yours by Jan 15. We'll be posting
>> more logistics next week(-ish) as well in case you're
>> wondering.
>>
>> Thanks,
>> S.
>>
>>
>> -------- Original Message --------
>> Subject: W3C/IAB workshop on Strengthening the Internet Against
>> Pervasive Monitoring (STRINT)
>> Date: Sun, 1 Dec 2013 10:48:15 -0500
>> From: IAB Chair <iab-chair@iab.org>
>> To: IETF Announce <ietf-announce@ietf.org>
>> CC: IAB <iab@iab.org>, IETF <ietf@ietf.org>
>>
>>
>> W3C/IAB workshop on Strengthening the Internet
>> Against Pervasive Monitoring (STRINT)
>> ======================================
>>
>> Logistics/Dates:
>>
>> Submissions due: Jan 15 2014
>> Invitations issued: Jan 31 2014
>> Workshop Date: Feb 28 (pm) & Mar 1 (am) 2014
>> 	To be Confirmed - could be all day Mar 1
>> Location: Central London, UK. IETF Hotel or nearby (TBC)
>> For queries, contact: stephen.farrell@cs.tcd.ie, tech@strews.eu
>> Send submissions to: group-strint-submission@w3.org
>> Workshop web site: http://www.w3.org/2014/strint/
>>
>> The Vancouver IETF plenary concluded that pervasive monitoring
>> represents an attack on the Internet, and the IETF has begun to
>> carry out various of the more obvious actions [1] required to
>> try to handle this attack. However, there are additional much
>> more complex questions arising that need further consideration
>> before any additional concrete plans can be made.
>>
>> The W3C and IAB will therefore host a one-day workshop on the
>> topic of "Strengthening the Internet Against Pervasive
>> Monitoring" before IETF-89 in London in March 2014, with support
>> from the EU FP7 STREWS [2] project.
>>
>> Pervasive monitoring targets protocol data that we also need for
>> network manageability and security. This data is captured and
>> correlated with other data. There is an open problem as to how
>> to enhance protocols so as to maintain network manageability and
>> security but still limit data capture and correlation.
>>
>> The overall goal of the workshop is to steer IETF and W3C work
>> so as to be able to improve or "strengthen" the Internet in the
>> face of pervasive monitoring.  A workshop report in the form of
>> an IAB RFC will be produced after the event.
>>
>> Technical questions for the workshop include:
>>
>> - What are the pervasive monitoring threat models, and what is
>>    their effect on web and Internet protocol security and privacy?
>> - What is needed so that web developers can better consider the
>>    pervasive monitoring context?
>> - How are WebRTC and IoT impacted, and how can they be better
>>    protected? Are other key Internet and web technologies
>>    potentially impacted?
>> - What gaps exist in current tool sets and operational best
>>    practices that could address some of these potential impacts?
>> - What trade-offs exist between strengthening measures, (e.g.
>>    more encryption) and performance, operational or network
>>    management issues?
>> - How do we guard against pervasive monitoring while maintaining
>>    network manageability?
>> - Can lower layer changes (e.g., to IPv6, LISP, MPLS) or
>>    additions to overlay networks help?
>> - How realistic is it to not be fingerprintable on the web and
>>    Internet?
>> - How can W3C, the IETF and the IRTF better deal with new
>>    cryptographic algorithm proposals in future?
>> - What are the practical benefits and limits of "opportunistic
>>    encryption"?
>> - Can we deploy end-to-end crypto for email, SIP, the web, all
>>    TCP applications or other applications so that we mitigate
>>    pervasive monitoring usefully?
>> - How might pervasive monitoring take form or be addressed in
>>    embedded systems or different industrial verticals?
>> - How do we reconcile caching, proxies and other intermediaries
>>    with end-to-end encryption?
>> - Can we obfuscate metadata with less overhead than TOR?
>> - Considering meta-data: are there relevant differences between
>>    protocol artefacts, message sizes and patterns and payloads?
>>
>> Position papers (maximum of 5 pages using 10pt font or any
>> length Internet-Drafts) from academia, industry and others that
>> focus on the broader picture and that warrant the kind of
>> extended discussion that a full day workshop offers are the most
>> welcome. Papers that reflect experience based on running code
>> and deployed services are also very welcome. Papers that are
>> proposals for point-solutions are less useful in this context,
>> and can simply be submitted as Internet-Drafts and discussed on
>> relevant IETF or W3C lists, e.g. the IETF perpass list. [3]
>>
>> The workshop will be by invitation only. Those wishing to attend
>> should submit a position paper or Internet-Draft.  All inputs
>> submitted and considered relevant will be published on the
>> workshop web page. The organisers (STREWS project participants,
>> IAB and W3C staff) will decide whom to invite based on the
>> submissions received.  Sessions will be organized according to
>> content, and not every accepted submission or invited attendee
>> will have an opportunity to present as the intent is to foster
>> discussion and not simply to have a sequence of presentations.
>>
>> [1] http://down.dsg.cs.tcd.ie/misc/perpass.txt
>> [2] http://www.strews.eu/
>> [3] https://www.ietf.org/mailman/listinfo/perpass
>>



From joelja@bogus.com  Thu Jan 16 09:07:11 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F6A1AE375; Thu, 16 Jan 2014 09:07:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b_F2I8GoTVFm; Thu, 16 Jan 2014 09:07:10 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9783C1AE364; Thu, 16 Jan 2014 09:07:10 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0GH6lff037145 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Jan 2014 17:06:48 GMT (envelope-from joelja@bogus.com)
Message-ID: <52D811A2.9070606@bogus.com>
Date: Thu, 16 Jan 2014 09:06:42 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Joel Halpern <jmh@joelhalpern.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
In-Reply-To: <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cuuPvSot3F6CMwfoP6dclG7jGku0IKmaJ"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Thu, 16 Jan 2014 17:06:48 +0000 (UTC)
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:07:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--cuuPvSot3F6CMwfoP6dclG7jGku0IKmaJ
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1/14/14, 7:29 AM, Eggert, Lars wrote:
> Hi,
>=20
> On 2014-1-14, at 16:23, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>> Isn't that basically the problem of the inner traffic sender, not
>> the problem of the tunnel that is carrying the traffic?
>=20
> no, because the sender of the inner traffic may be blasting some L2
> traffic, for an L2 where that is OK behavior. But that traffic is now
> being encapsulated inside UDP and can hence go anywhere on the net
> *without the sender being aware of this*.
>=20
>> Asking tunnel's to solve the problem of applications with
>> undesirable behavior seems backwards.
>=20
> It is the *tunnel* that performs the encapsulation and allows that
> traffic to go places it couldn't before. And so it's the tunnel's
> responsibility to make sure that the traffic it injects into the
> Internet complies with the BCPs we have on congestion control.

There seems assertion on the part of transport that tunnel endpoints
should be aware of congestion on intermediate hops. This seems to be the
assertion here, it certainly is with respect to AMT.  This  certainly
not a property that we demand of routers in other contexts.

my observations

  These tunnels are stateless

  The endpoints not the encapsulators have visibility into the
end-to-end loss
  latency properties of the path.

  the encapsulator is an intermediate hop, similar to any other router
in the path.


> Lars
>=20



--cuuPvSot3F6CMwfoP6dclG7jGku0IKmaJ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLYEaIACgkQ8AA1q7Z/VrJmNQCfTxdzgsVe2VFYTOvDoKBaBoJE
FNEAnArIl+tSQHM/GJIWvWRK1PTdvZP0
=mp6l
-----END PGP SIGNATURE-----

--cuuPvSot3F6CMwfoP6dclG7jGku0IKmaJ--

From lars@netapp.com  Thu Jan 16 09:20:04 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50A011AE3D3; Thu, 16 Jan 2014 09:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 885b57WWSJ5W; Thu, 16 Jan 2014 09:20:03 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 5B1C41AE3B2; Thu, 16 Jan 2014 09:20:03 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,668,1384329600";  d="asc'?scan'208";a="96430293"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 16 Jan 2014 09:19:51 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Thu, 16 Jan 2014 09:19:51 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Joel Jaeggli <joelja@bogus.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81hZzPPQlRcgk6ua2U45NfiYJp7LVMAgAK2KoCAAFQ2gIAAckuAgAAJQICAAAZIAIAD31WAgABWjoCAAHXQgIAAN0wAgAEJtoCAACSXAIAAC26AgAAH1ACAABCuAIAAAQqAgAABkYCAAz/MAIAAA6eA
Date: Thu, 16 Jan 2014 17:19:50 +0000
Message-ID: <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com>
In-Reply-To: <52D811A2.9070606@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_2C0E3627-B95F-40C6-B47D-E6E2ED1733A4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:20:04 -0000

--Apple-Mail=_2C0E3627-B95F-40C6-B47D-E6E2ED1733A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> These tunnels are stateless

yep. (But they don't have to be.)

>  The endpoints not the encapsulators have visibility into the
> end-to-end loss latency properties of the path.

Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 =
domains - where not reacting to congestion may be OK - can now go over =
the wider Internet, where this is not OK.

I'd be great if those apps would change. But in the meantime, it's the =
duty of the encapsulator - who enables this traffic to break out of an =
L2 domain and go over the wider net - to make sure the traffic it emits =
conforms to our BCPs.

>  the encapsulator is an intermediate hop, similar to any other router
> in the path.

It's not. For the rest of the network, that encapsulator is =
indistinguishable from any other app that sends UDP traffic.

UDP is a transport-layer protocol, and we have practices how it is to be =
used on the net. If you want to use it for encapsulation, you bind =
yourself to these BCPs.

Look at it the other way: if transport area folks would want to send =
MPLS packets into the network in some problematic way, I'm sure the =
routing and ops folks would not be amused.

Lars

--Apple-Mail=_2C0E3627-B95F-40C6-B47D-E6E2ED1733A4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUtgUs9ZcnpRveo1xAQLOoQQAu4C8E4L95wEG/1bGt2CrmxDFf23uBFzW
6+WaxtQdyehM64Cy1IKxfugZHGcz7dhylCuAzhBOhhMRgYdTsrwAqhKhuckOddtC
87DR0Ywq31R5Vib8EfqTMk9t5ekZqtskMG3zdkQVBiytHLNZtLRYqXx+71u4Hh+R
YHzHFyO2CKE=
=UzEf
-----END PGP SIGNATURE-----

--Apple-Mail=_2C0E3627-B95F-40C6-B47D-E6E2ED1733A4--

From stbryant@cisco.com  Thu Jan 16 09:35:41 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF0E1AE3B2; Thu, 16 Jan 2014 09:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.039
X-Spam-Level: 
X-Spam-Status: No, score=-10.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTcPCmXfVirS; Thu, 16 Jan 2014 09:35:40 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 016791AE171; Thu, 16 Jan 2014 09:35:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1647; q=dns/txt; s=iport; t=1389893728; x=1391103328; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=j48mynpc5hG6DbeSEhHkM39BT3WuQm+m2pQHoMW9puk=; b=fd+D/u2vKK6V/LJdKiDNdm+evxV5El/IZiWh/SkFXMPH6Z75L+ybPYU0 bSoDz514bBYlos56MzMtfjnr5fclECnY6UB7j5vdwYpDpxGvkMy1E/Q4t lCJli0ROg1ewA+qBBaINJ+famc6ZkFCY7D946IzPxM1V/Zo+tOkPXxBDE U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAF8X2FKQ/khL/2dsb2JhbABZgwu8GYEOFnSCJQEBAQQ4QAEQCxgJFgQLCQMCAQIBRQYBDAEFAgEBiADEaxeOJ1gHhDgBA5ghkheBb4E+gWg
X-IronPort-AV: E=Sophos;i="4.95,668,1384300800";  d="scan'208";a="3729242"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 16 Jan 2014 17:35:27 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0GHZQa5022059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 17:35:27 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0GHZPSY003228; Thu, 16 Jan 2014 17:35:25 GMT
Message-ID: <52D8185D.1010902@cisco.com>
Date: Thu, 16 Jan 2014 17:35:25 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Joel Jaeggli <joelja@bogus.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
In-Reply-To: <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:35:41 -0000

On 16/01/2014 17:19, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
>> These tunnels are stateless
> yep. (But they don't have to be.)
Ah, they do if they are to scale. State at speed is really hard. The sort
of systems we are talking about do things like pipeline counters
and it is loooooots of packets later before the counter is actually
incremented.
>>   The endpoints not the encapsulators have visibility into the
>> end-to-end loss latency properties of the path.
> Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domains - where not reacting to congestion may be OK - can now go over the wider Internet, where this is not OK.
>
> I'd be great if those apps would change. But in the meantime, it's the duty of the encapsulator - who enables this traffic to break out of an L2 domain and go over the wider net - to make sure the traffic it emits conforms to our BCPs.
>
>>   the encapsulator is an intermediate hop, similar to any other router
>> in the path.
> It's not. For the rest of the network, that encapsulator is indistinguishable from any other app that sends UDP traffic.
>
> UDP is a transport-layer protocol, and we have practices how it is to be used on the net. If you want to use it for encapsulation, you bind yourself to these BCPs.
>
> Look at it the other way: if transport area folks would want to send MPLS packets into the network in some problematic way, I'm sure the routing and ops folks would not be amused.
The root cause of the problem here is that UDP, has bifurcated into
a general purpose encapsulation.

Stewart


From Hannes.Tschofenig@gmx.net  Thu Jan 16 09:45:49 2014
Return-Path: <Hannes.Tschofenig@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053391AE0FC for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.438
X-Spam-Level: 
X-Spam-Status: No, score=-4.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IGg4jNKjr35 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:45:45 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 5493B1AE0A0 for <ietf@ietf.org>; Thu, 16 Jan 2014 09:45:45 -0800 (PST)
Received: from 3capp-gmx-bs42.server.lan ([172.19.170.94]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MgJFg-1VjYjK22go-00Ni3I for <ietf@ietf.org>; Thu, 16 Jan 2014 18:45:32 +0100
Received: from [217.140.96.21] by 3capp-gmx-bs42.server.lan with HTTP; Thu Jan 16 18:45:32 CET 2014
MIME-Version: 1.0
Message-ID: <trinity-9dcc39ff-4d43-4c01-bad0-97b06d73bdbd-1389894332308@3capp-gmx-bs42>
From: "Hannes Tschofenig" <Hannes.Tschofenig@gmx.net>
To: "Hector Santos" <hsantos@isdg.net>
Subject: Aw: Re: Fwd: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
Content-Type: text/plain; charset=UTF-8
Date: Thu, 16 Jan 2014 18:45:32 +0100 (CET)
Importance: normal
Sensitivity: Normal
In-Reply-To: <52D80FAF.8040301@isdg.net>
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie> <52D7D63E.7010506@cs.tcd.ie>, <52D80FAF.8040301@isdg.net>
Content-Transfer-Encoding: quoted-printable
X-UI-Message-Type: mail
X-Priority: 3
X-Provags-ID: V03:K0:JZF3tpX7cb5h0mN0QbmZoiowjzJqb4GhhWsYoD3Sbrl 3huWIPgzAosWKTxn8crTpg9rqomgDzONqvbwZjUHL9kOjyyRAG oxuunlN98OJqo2MrfVw5X2bLwkeEMPxU1vUy2LVIaxHSeFzQr2 ePYZbcrnKs8mk2Olr0/IIVjTVIYqLs9JaEkwsXSMt4rmelY/mj pqYFO8xCatAYHzXdFk6z/cQI9XVIE5/ggk5iEngpkxcWlRFaWJ B7NonZh/nUS1iRRGjq+/wPvIJ/Uac4otvo+SOevQ+R8id46j0Q ZX9db0=
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:45:49 -0000

Hi Hector,=C2=A0
=C2=A0
with fingerprinting we are actually referring to what is defined in RFC 69=
73 as:
=C2=A0
   $ Fingerprinting:  The process of an observer or attacker uniquely
      identifying (with a sufficiently high probability) a device or
      application instance based on multiple information elements
      communicated to the observer or attacker.  See [EFF].

There has been some work on that topic by the W3C and you can find an inte=
resting, work-in-progress document maintained by Nick Doty at:=C2=A0
http://w3c.github.io/fingerprinting-guidance/
=C2=A0
Fingerprinting has been discussed in the context of the Do Not Track work =
and is of particular interest to advertising companies.=20
=C2=A0
Ciao
Hannes
=C2=A0
=C2=A0
Gesendet:=C2=A0Donnerstag, 16. Januar 2014 um 16:58 Uhr
Von:=C2=A0"Hector Santos" <hsantos@isdg.net>
An:=C2=A0"Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc:=C2=A0IETF-Discussion <ietf@ietf.org>
Betreff:=C2=A0Re: Fwd: W3C/IAB workshop on Strengthening the Internet Agai=
nst Pervasive Monitoring (STRINT)
What I found interesting is the itemized STRINT question:

How realistic is it to not be fingerprintable on the web and
Internet?

Like its a foregone conclusion it is already too late. If we are
literally talking about "fingerprints" well, we already have a major
vendor, probably the most significant one at present, that has opened
that can of worms. Of course, I'm referring to Apple's TouchID with
the iPhone 5S.

Part of the problem in all this is the business, social engineering
ethics in these architectural decisions, which is increasingly more
market related. So I wonder if its realistic to even ponder:

As a security rule of thumb, should systems first consider NOT
introducing
"fingerprints" or identification methods without having
protection for users?

Its a different way of thinking -- sometimes you just "Don't do it"
unless you are 100% sure you can do it right.

Its a great idea, but surely it will be leverage, exploited and
somehow, one way or another, inevitably, besides the advertisement
market, the government, policing agencies will want access to the huge
database of fingerprints or "identification tokens," of course, in the
name of security, to search a person of interest for the closest match.

The IETF has the ethics document RFC1087. I have asked if anyone
believes this should be updated. Surely this is tied to PM. Odd. It
seems odd no one doesn't seem to think it needs to be updated. I
don't see the PM draft reference it. Should it? I think so, and this
RFC1087 document SHOULD be updated.

Anyway, we will be competing with business market pressures and these
PM related issues most likely boil down to ethical principles which
has changed over years. We have new a new generation of
"Infopreneurs" who surely do not have the same mindset for design
engineering "taboos," in fact, its natural to consider that
unrestricted communications is the norm.

--
HLS


On 1/16/2014 7:53 AM, Stephen Farrell wrote:
>
> And as is traditional, we've added a few days:-)
>
> Final deadline is end of Monday Jan 20 anywhere
> on Earth (=3D=3D 1200 UTC Jan 21). And that will be
> a hard deadline.
>
> There's also a bit more logistics stuff now at [1].
>
> Cheers,
> S.
>
> [1] https://www.w3.org/2014/strint/[https://www.w3.org/2014/strint/]
>
> On 01/09/2014 01:55 PM, Stephen Farrell wrote:
>>
>> Folks, submissions are starting to roll in so this is
>> a reminder to send yours by Jan 15. We'll be posting
>> more logistics next week(-ish) as well in case you're
>> wondering.
>>
>> Thanks,
>> S.
>>
>>
>> -------- Original Message --------
>> Subject: W3C/IAB workshop on Strengthening the Internet Against
>> Pervasive Monitoring (STRINT)
>> Date: Sun, 1 Dec 2013 10:48:15 -0500
>> From: IAB Chair <iab-chair@iab.org>
>> To: IETF Announce <ietf-announce@ietf.org>
>> CC: IAB <iab@iab.org>, IETF <ietf@ietf.org>
>>
>>
>> W3C/IAB workshop on Strengthening the Internet
>> Against Pervasive Monitoring (STRINT)
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>
>> Logistics/Dates:
>>
>> Submissions due: Jan 15 2014
>> Invitations issued: Jan 31 2014
>> Workshop Date: Feb 28 (pm) & Mar 1 (am) 2014
>> To be Confirmed - could be all day Mar 1
>> Location: Central London, UK. IETF Hotel or nearby (TBC)
>> For queries, contact: stephen.farrell@cs.tcd.ie, tech@strews.eu
>> Send submissions to: group-strint-submission@w3.org
>> Workshop web site: http://www.w3.org/2014/strint/[http://www.w3.org/201=
4/strint/]
>>
>> The Vancouver IETF plenary concluded that pervasive monitoring
>> represents an attack on the Internet, and the IETF has begun to
>> carry out various of the more obvious actions [1] required to
>> try to handle this attack. However, there are additional much
>> more complex questions arising that need further consideration
>> before any additional concrete plans can be made.
>>
>> The W3C and IAB will therefore host a one-day workshop on the
>> topic of "Strengthening the Internet Against Pervasive
>> Monitoring" before IETF-89 in London in March 2014, with support
>> from the EU FP7 STREWS [2] project.
>>
>> Pervasive monitoring targets protocol data that we also need for
>> network manageability and security. This data is captured and
>> correlated with other data. There is an open problem as to how
>> to enhance protocols so as to maintain network manageability and
>> security but still limit data capture and correlation.
>>
>> The overall goal of the workshop is to steer IETF and W3C work
>> so as to be able to improve or "strengthen" the Internet in the
>> face of pervasive monitoring. A workshop report in the form of
>> an IAB RFC will be produced after the event.
>>
>> Technical questions for the workshop include:
>>
>> - What are the pervasive monitoring threat models, and what is
>> their effect on web and Internet protocol security and privacy?
>> - What is needed so that web developers can better consider the
>> pervasive monitoring context?
>> - How are WebRTC and IoT impacted, and how can they be better
>> protected? Are other key Internet and web technologies
>> potentially impacted?
>> - What gaps exist in current tool sets and operational best
>> practices that could address some of these potential impacts?
>> - What trade-offs exist between strengthening measures, (e.g.
>> more encryption) and performance, operational or network
>> management issues?
>> - How do we guard against pervasive monitoring while maintaining
>> network manageability?
>> - Can lower layer changes (e.g., to IPv6, LISP, MPLS) or
>> additions to overlay networks help?
>> - How realistic is it to not be fingerprintable on the web and
>> Internet?
>> - How can W3C, the IETF and the IRTF better deal with new
>> cryptographic algorithm proposals in future?
>> - What are the practical benefits and limits of "opportunistic
>> encryption"?
>> - Can we deploy end-to-end crypto for email, SIP, the web, all
>> TCP applications or other applications so that we mitigate
>> pervasive monitoring usefully?
>> - How might pervasive monitoring take form or be addressed in
>> embedded systems or different industrial verticals?
>> - How do we reconcile caching, proxies and other intermediaries
>> with end-to-end encryption?
>> - Can we obfuscate metadata with less overhead than TOR?
>> - Considering meta-data: are there relevant differences between
>> protocol artefacts, message sizes and patterns and payloads?
>>
>> Position papers (maximum of 5 pages using 10pt font or any
>> length Internet-Drafts) from academia, industry and others that
>> focus on the broader picture and that warrant the kind of
>> extended discussion that a full day workshop offers are the most
>> welcome. Papers that reflect experience based on running code
>> and deployed services are also very welcome. Papers that are
>> proposals for point-solutions are less useful in this context,
>> and can simply be submitted as Internet-Drafts and discussed on
>> relevant IETF or W3C lists, e.g. the IETF perpass list. [3]
>>
>> The workshop will be by invitation only. Those wishing to attend
>> should submit a position paper or Internet-Draft. All inputs
>> submitted and considered relevant will be published on the
>> workshop web page. The organisers (STREWS project participants,
>> IAB and W3C staff) will decide whom to invite based on the
>> submissions received. Sessions will be organized according to
>> content, and not every accepted submission or invited attendee
>> will have an opportunity to present as the intent is to foster
>> discussion and not simply to have a sequence of presentations.
>>
>> [1] http://down.dsg.cs.tcd.ie/misc/perpass.txt[http://down.dsg.cs.tcd.i=
e/misc/perpass.txt]
>> [2] http://www.strews.eu/[http://www.strews.eu/]
>> [3] https://www.ietf.org/mailman/listinfo/perpass[https://www.ietf.org/=
mailman/listinfo/perpass]
>>

=C2=A0

From cabo@tzi.org  Thu Jan 16 09:57:32 2014
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8BB1A1F54 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:57:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKzXfPwPaZNR for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 09:57:31 -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 E7E901A16F0 for <ietf@ietf.org>; Thu, 16 Jan 2014 09:57:30 -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.5/8.14.5) with ESMTP id s0GHuen4023640; Thu, 16 Jan 2014 18:56:40 +0100 (CET)
Received: from [192.168.217.101] (p54891EB1.dip0.t-ipconnect.de [84.137.30.177]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id DD925BB2; Thu, 16 Jan 2014 18:56:39 +0100 (CET)
Subject: Re: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=windows-1252
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <52D80FAF.8040301@isdg.net>
Date: Thu, 16 Jan 2014 18:56:38 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8972FC08-18D6-4B17-8E53-78E087D8E8BE@tzi.org>
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie> <52D7D63E.7010506@cs.tcd.ie> <52D80FAF.8040301@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1827)
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 17:57:32 -0000

On 16 Jan 2014, at 17:58, Hector Santos <hsantos@isdg.net> wrote:

> The IETF has the ethics document RFC1087

Whoa.

=97 this is an IAB document, not an IETF document
=97 it=92s status is UNKNOWN
=97 if it had been assigned a more specific status, that would be =
HISTORIC
=97 it subject was about proper allocation of public resources for =
work-related activities:

"there is widespread dependence on the Internet
by its users for the support of day-to-day research activities.=94

"The U.S. Government sponsors of this system have a fiduciary
responsibility to the public to allocate government resources wisely
and effectively."

etc.

This is from a time where large parts of every-day human reality hadn=92t =
moved into the digital domain (and thus into the Internet) yet.  In =
1989, nobody would have thought about making the point that the =
integrity of the digital facets of your personality is the subject of a =
basic human right.  We are way beyond any question about that.

Gr=FC=DFe, Carsten


From sm@resistor.net  Thu Jan 16 10:19:16 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3561A1F63; Thu, 16 Jan 2014 10:19:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85h-ZbohK_L2; Thu, 16 Jan 2014 10:19: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 38E051A1F19; Thu, 16 Jan 2014 10:19: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 s0GIIQbi001534 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 10:18:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1389896317; bh=iB73rZ16jyLAcFdIrNywMBADqR+r7r7aNPcf7QZbVUg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=gILOAQJo/9v2cNVvIEx3uwI05CmJ6+0CkE94/lFcf0rsCX0XmAebhtYXVxkQq7KnQ HU4KfXA8KwsmF/5q3c1cz1L40k0rqjq7NFfMfQNnhrbDyvqlCKF6siFEOo2A6tkNdl BoaQjDpCVudRvQGOKYH72yXhPBmeLsW+zyJJih1U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1389896317; i=@resistor.net; bh=iB73rZ16jyLAcFdIrNywMBADqR+r7r7aNPcf7QZbVUg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OdBy20vKhqSc6Di7B5F56M9ejJaq+IWXeVQ/B1XzB311MrCeuKVY6jhuvKZ5b89kd eRyCiKr/ZAzWg1VBD0rIH0VEbwljj56nQMf9mYKvK8wPvT35UwigL2w0bcJe+1JgZK +SFs/CSwXhfmrv/x0cUOJYcpkh9aIRoK9KDeOi5Y=
Message-Id: <6.2.5.6.2.20140116095641.0bcc8b10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 16 Jan 2014 10:17:09 -0800
To: Paul Eggert <eggert@cs.ucla.edu>, Martin Bjorklund <mbj@tail-f.com>
From: SM <sm@resistor.net>
Subject: Re: technical discussion around draft-ietf-netmod-iana-timezone
In-Reply-To: <52D80720.80002@cs.ucla.edu> <20140116.184249.296066285.mbj@tail-f.com>
References: <20140116092825.GA1348@elstar.local> <52D800F1.20401@cs.ucla.edu> <20140116.170222.308250923.mbj@tail-f.com> <52D80720.80002@cs.ucla.edu> <52D800F1.20401@cs.ucla.edu> <20140116.170222.308250923.mbj@tail-f.com> <52D80720.80002@cs.ucla.edu> <20140116.184249.296066285.mbj@tail-f.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: netmod@ietf.org, andy@yumaworks.com, jeffrey.k.lange@ge.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 18:19:16 -0000

At 08:21 16-01-2014, Paul Eggert wrote:
>Martin Bjorklund wrote:
>
>>why is this a problem?
>
>Because people often use names that are not in zone.tab.
>Just today, for example, someone asked on the tz mailing
>about Asia/Calcutta, a name that's not in zone.tab but which
>does work.  Although Asia/Calcutta was formerly in zone.tab
>and so could presumably rely on a proleptic application of
>whatever deprecation procedure the YANG maintainers want to
>establish, some commonly-used names have never been in
>zone.tab -- US/Pacific is one example.
>
>More generally, there is a political burden in coming up
>with a "canonical" list of names.  This is a long story, one
>that's connected to conflicts between Israelis and
>Palestinians, between the Serbs and the Croats, etc.  If the
>YANG maintainers, whoever they are, want to address this
>problem, more power to them; but it's not a burden the TZ
>coordinator should have to take up.

At 09:42 16-01-2014, Martin Bjorklund wrote:
> > Palestinians, between the Serbs and the Croats, etc.  If the
> > YANG maintainers, whoever they are, want to address this
> > problem, more power to them; but it's not a burden the TZ
> > coordinator should have to take up.
>
>I am pretty sure noone wants to address this problem.  Again, we just
>want a version of zone.tab expressed in YANG.

I agree with what Paul Eggert wrote (see message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg85386.html for 
the political aspect).  The NETMOD Working Group could choose YANG 
maintainers to do the work instead of pushing the political burden to 
the TZ coordinator.

Regards,
-sm 


From hsantos@isdg.net  Thu Jan 16 10:23:23 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B839E1A1F4C for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 10:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MJq66u1QAqL9 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 10:23:21 -0800 (PST)
Received: from secure.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id C713B1A1F3D for <ietf@ietf.org>; Thu, 16 Jan 2014 10:23:20 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1961; t=1389896581; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=5C6jDR8lGlh3Sb9UXMbS/1HxKG4=; b=PE4a/iyIyoMg/KEF9JZl ovY8V8sOaoB5VaVAmUagWn8EcpY4yPZBbPFaEnDO4HRBi83pZBMjZr6cLfdVJPrk lUK1gdnpl/qvE4mvbaHjiH8uOMZj1nTjNWu/yGTsiaEwVfMMBfE81qVL4XGUCHv/ MzuL3BPbLP/U8FhuhIoj7Ks=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 16 Jan 2014 13:23:01 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3474049248.3.1908; Thu, 16 Jan 2014 13:23:01 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1961; t=1389896014; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=4eV8IqJ leCcS1h7kXxAnpDolPmQd68argj5IYhR54kc=; b=qMqH1lkRyNT87Fl3GLDzSuI OfBB0c9wlkVnWkC2k8DjHBdOXnnqOd16zXsmnYho0kuWR8XtZ9o5dcLMmPACt4is X+8L2YzVmb0EdoqD40decJYiRIzQsVY16CgQsupgcdndrKVrFmSA0C+6T7MronTu QcMOne0S4pGX52C+PHjA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 16 Jan 2014 13:13:34 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2920360114.9.8740; Thu, 16 Jan 2014 13:13:33 -0500
Message-ID: <52D82387.5050507@isdg.net>
Date: Thu, 16 Jan 2014 13:23:03 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie> <52D7D63E.7010506@cs.tcd.ie> <52D80FAF.8040301@isdg.net> <8972FC08-18D6-4B17-8E53-78E087D8E8BE@tzi.org>
In-Reply-To: <8972FC08-18D6-4B17-8E53-78E087D8E8BE@tzi.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 18:23:24 -0000

Hi Carsten,

Besides the idea my take was a little different from you, your points 
are well taken. But that may suggest the IETF now *really* does need 
an new "Ethics" document of its own.  I don't see how you separate it. 
  I guess I was among the few in 1989, who did consider these social 
engineering integrity issues in consumer product lines.

Its essentially what this proposed BCP (and reference docs) is asking, 
and this STRINT workshop (based on the itemized questions) wants us to 
consider -- asking developers (and reviewers) to have a greater look 
at the intent, the goals of proposed systems, the pros and cons, 
including conflict of interest matters, expecting engineering due 
diligence in regards to security/privacy matters. For the most part, 
question all things.

Thanks for your points.

--
HLS



On 1/16/2014 12:56 PM, Carsten Bormann wrote:
> On 16 Jan 2014, at 17:58, Hector Santos <hsantos@isdg.net> wrote:
>
>> The IETF has the ethics document RFC1087
>
> Whoa.
>
> ï¿½ this is an IAB document, not an IETF document
> ï¿½ itï¿½s status is UNKNOWN
> ï¿½ if it had been assigned a more specific status, that would be HISTORIC
> ï¿½ it subject was about proper allocation of public resources for work-related activities:
>
> "there is widespread dependence on the Internet
> by its users for the support of day-to-day research activities.ï¿½
>
> "The U.S. Government sponsors of this system have a fiduciary
> responsibility to the public to allocate government resources wisely
> and effectively."
>
> etc.
>
> This is from a time where large parts of every-day human reality hadnï¿½t moved into the digital domain (and thus into the Internet) yet.  In 1989, nobody would have thought about making the point that the integrity of the digital facets of your personality is the subject of a basic human right.  We are way beyond any question about that.
>
> Grï¿½ï¿½e, Carsten
>
>
>

-- 
HLS



From chair@ietf.org  Thu Jan 16 11:21:34 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC681AC499; Thu, 16 Jan 2014 11:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lFGZJr0NoRpf; Thu, 16 Jan 2014 11:21:33 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5F41A1F66; Thu, 16 Jan 2014 11:21:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id F29ACA60E7; Thu, 16 Jan 2014 11:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMfrS_JrZ4TO; Thu, 16 Jan 2014 11:19:05 -0800 (PST)
Received: from [10.30.0.138] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 1010CA60BA; Thu, 16 Jan 2014 11:19:04 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: REMINDER: BOF deadline coming up
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Thu, 16 Jan 2014 21:21:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F48FB135-DC1E-47B6-A399-64905DA730EA@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: Working Group Chairs <wgchairs@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Discussion" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 19:21:34 -0000

The IETF-89 deadline for new work proposals (BOF sessions) is coming up =
fast. The deadline is tomorrow, Friday, January 17th. See:

http://www.ietf.org/meeting/important-dates-2014.html#IETF89

Jari


From scott.brim@gmail.com  Thu Jan 16 12:02:14 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3871ACC87 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XMZnnln_lOhE for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:02:12 -0800 (PST)
Received: from mail-oa0-x22f.google.com (mail-oa0-x22f.google.com [IPv6:2607:f8b0:4003:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 8C8861AC404 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:02:12 -0800 (PST)
Received: by mail-oa0-f47.google.com with SMTP id m1so2272903oag.6 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:02:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UP+R6d/VKrXW+zCo/CNaqSN+ib9+DTO06FjNbUod0m8=; b=AfqkaPPWyW39+r+veSjgTzy7oH4ya91rYOqn+buvTaQ2Bd84UexLOCh3b16YCRz7kB HnW/COtQTKw5P5NB7QFgIEPS2R3OBxV6Gg+rodYgNUYoDlx1N43jxD9IsJah1CNsm8T2 RcwhWJnIkYfe7MmaIo4XvxAh+p+Ex+E308AS5gAUItZ9/xVJnDbGNcU1Rf4/Ntv0fLof 1wLudX7HH5fd+U2nVFhbOLyja44+SgfDreKuTND7jS/0dpzZ+y9o/y7raVmB2BrrqHeA tDuSJ1aJNX1q0HKFe6yaLWBfQndkYl0NKbmdawn/V4wYgb2VxDS5JH+Sp9ookGaM6uKx HrBQ==
X-Received: by 10.60.134.230 with SMTP id pn6mr157184oeb.40.1389902520321; Thu, 16 Jan 2014 12:02:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 12:01:40 -0800 (PST)
In-Reply-To: <8972FC08-18D6-4B17-8E53-78E087D8E8BE@tzi.org>
References: <2CD9CC27-4F4E-4BBF-B428-768A23D82B79@iab.org> <52CEAA53.1090102@cs.tcd.ie> <52D7D63E.7010506@cs.tcd.ie> <52D80FAF.8040301@isdg.net> <8972FC08-18D6-4B17-8E53-78E087D8E8BE@tzi.org>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 16 Jan 2014 15:01:40 -0500
Message-ID: <CAPv4CP_5+UvPShKEoUVqDtMvg+7bm_tvS+ugvq0syofUOfAF8g@mail.gmail.com>
Subject: Re: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)
To: Carsten Bormann <cabo@tzi.org>
Content-Type: multipart/alternative; boundary=047d7b471e6aff0f4404f01be5aa
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:02:14 -0000

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

It was a response to the RTM Worm.


On Thu, Jan 16, 2014 at 12:56 PM, Carsten Bormann <cabo@tzi.org> wrote:

> On 16 Jan 2014, at 17:58, Hector Santos <hsantos@isdg.net> wrote:
>
> > The IETF has the ethics document RFC1087
>
> Whoa.
>
> =97 this is an IAB document, not an IETF document
> =97 it=92s status is UNKNOWN
> =97 if it had been assigned a more specific status, that would be HISTORI=
C
> =97 it subject was about proper allocation of public resources for
> work-related activities:
>
> "there is widespread dependence on the Internet
> by its users for the support of day-to-day research activities.=94
>
> "The U.S. Government sponsors of this system have a fiduciary
> responsibility to the public to allocate government resources wisely
> and effectively."
>
> etc.
>
> This is from a time where large parts of every-day human reality hadn=92t
> moved into the digital domain (and thus into the Internet) yet.  In 1989,
> nobody would have thought about making the point that the integrity of th=
e
> digital facets of your personality is the subject of a basic human right.
>  We are way beyond any question about that.
>
> Gr=FC=DFe, Carsten
>
>

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

<div dir=3D"ltr">It was a response to the RTM Worm.</div><div class=3D"gmai=
l_extra"><br><br><div class=3D"gmail_quote">On Thu, Jan 16, 2014 at 12:56 P=
M, Carsten Bormann <span dir=3D"ltr">&lt;<a href=3D"mailto:cabo@tzi.org" ta=
rget=3D"_blank">cabo@tzi.org</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 16 Jan 2014, at 17:58, =
Hector Santos &lt;<a href=3D"mailto:hsantos@isdg.net">hsantos@isdg.net</a>&=
gt; wrote:<br>


<br>
&gt; The IETF has the ethics document RFC1087<br>
<br>
</div>Whoa.<br>
<br>
=97 this is an IAB document, not an IETF document<br>
=97 it=92s status is UNKNOWN<br>
=97 if it had been assigned a more specific status, that would be HISTORIC<=
br>
=97 it subject was about proper allocation of public resources for work-rel=
ated activities:<br>
<br>
&quot;there is widespread dependence on the Internet<br>
by its users for the support of day-to-day research activities.=94<br>
<br>
&quot;The U.S. Government sponsors of this system have a fiduciary<br>
responsibility to the public to allocate government resources wisely<br>
and effectively.&quot;<br>
<br>
etc.<br>
<br>
This is from a time where large parts of every-day human reality hadn=92t m=
oved into the digital domain (and thus into the Internet) yet. =A0In 1989, =
nobody would have thought about making the point that the integrity of the =
digital facets of your personality is the subject of a basic human right. =
=A0We are way beyond any question about that.<br>


<br>
Gr=FC=DFe, Carsten<br>
<br>
</blockquote></div><br></div>

--047d7b471e6aff0f4404f01be5aa--

From scott.brim@gmail.com  Thu Jan 16 12:08:14 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2EB51ACC80 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:08:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nHqNVTXhRL8e for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:08:13 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 23FCE1AC499 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:08:13 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id uy5so3335710obc.1 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:08:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=4n5Y9OrH7+O9jWemFHja3zQFNsby8igkuOcf9nwTI3k=; b=p6b0DOjkEW2tfjPsGs4O29BxIYQSYcQJOa97+iKoNZkJ5/Yy+epOmdeQcOr2sjSz6B sgaCRktOf9HkNZjqExRkuVcogz7HFsLnELGu993G6bFq5IhxILH98tu1S150Am6t1oXO DontEW8VFRomB1pA3HlWRA3kqDWHyaBBPxLJ7EWJdQ8VdIHcZeCADZ0hC5m1kgh8W9sI uIdjikEo53RuzSb90RNr02OhT/kntat469UcSNYa038Fv5F6gmYpfJ49YtP1zIDTBuxg nSPDoHsyhuEzzjCOONoddvPfnvkLyNmxx0n4zXVM7nujswNDubBWMAwMjGt8U2T6FbXC i+aA==
X-Received: by 10.60.115.138 with SMTP id jo10mr2627110oeb.71.1389902880888; Thu, 16 Jan 2014 12:08:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 16 Jan 2014 12:07:40 -0800 (PST)
In-Reply-To: <52D78742.9000604@cisco.com>
References: <52D43E69.6090001@cs.tcd.ie> <52D456CF.3040001@isdg.net> <CAPv4CP-ME9-C79e7gehQmPwvrq1SF0m6nH-dyBY-YPA_pvmREA@mail.gmail.com> <tsl4n56tl38.fsf@mit.edu> <52D593E2.7000202@cisco.com> <tsla9exryfd.fsf@mit.edu> <52D78742.9000604@cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 16 Jan 2014 15:07:40 -0500
Message-ID: <CAPv4CP9Kuq8FxwVO6rrA1QYenM8iqQX6Ej5VHK1vcNm9zCmAEA@mail.gmail.com>
Subject: Re: draft-farrell-perpass-attack architecture issue
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:08:15 -0000

On Thu, Jan 16, 2014 at 2:16 AM, Eliot Lear <lear@cisco.com> wrote:
>
> On 1/15/14 5:40 PM, Sam Hartman wrote:
>>>>>>> "Eliot" == Eliot Lear <lear@cisco.com> writes:
>
>>
>> I absolutely agree that general guidance of this form would be valuable
>> either in some general security BCP that the other security BCPs
>> reference or restated in the security BCPs.
>
> It is a basic precept of engineering that the earlier you spot a design
> flaw, the less costly it is to address.  We needn't teach such basic
> precepts in our series.

Then where should they be taught? Personally I prefer having the
fundamentals taught again and again rather than being in a single
place that most people have forgotten about. There are new people in
the IETF all the time, many of whom are new to this level of design. I
don't want to depend on ad hoc osmosis and "common knowledge" to get
the basic principles across.

>> we're not working on such a BCP now, so I'm trying to add the advice I
>> need to this BCP in order for it to work for me as a WG chair and
>> document author.
>
> And as a working group chair you must balance ALL considerations and not
> just this one.

Yes of course.

>> It's not so much a truism that we all agree to it.  I've definitely
>> worked with WGs that didn't want to consider these sorts of issues when
>> choosing technology and didn't seem to agree that they had to.
>
> And I've seen participants all but derail working groups by solely
> focusing on one design consideration.

If I'm understanding correctly, you're echoing the concern expressed a
week or two ago that the Security ADs were being given a Big Hammer
and tyrannical authority over every working group. No one is saying
this is the only architectural consideration - we have other RFCs on
protocol architecture. The text just says it really should be
considered. No?

Thanks ... Scott

From worley@shell01.TheWorld.com  Thu Jan 16 12:16:49 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C5A1AC499 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tQM4QpHNIU-u for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:16:47 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4CF1A1F6F for <ietf@ietf.org>; Thu, 16 Jan 2014 12:16:47 -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 s0GKGFC6005730 for <ietf@ietf.org>; Thu, 16 Jan 2014 15:16:17 -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 s0GKGF8q2950500 for <ietf@ietf.org>; Thu, 16 Jan 2014 15:16:15 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0GKGEoO2951294; Thu, 16 Jan 2014 15:16:14 -0500 (EST)
Date: Thu, 16 Jan 2014 15:16:14 -0500 (EST)
Message-Id: <201401162016.s0GKGEoO2951294@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com> (hallam@gmail.com)
Subject: Re: A DNS security issue that might actually have impact eventually
References: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:16:49 -0000

> From: Phillip Hallam-Baker <hallam@gmail.com>

> What is worrying here is not just the lack of oversight in these particular
> cases. If these practices become a regular occurrence they are going to be
> interpreted as an attack and countermeasures will begin to emerge.

What appears is that certain organizations have been asserting rights
that they don't have.  Which is really a rather common practice in the
real world.  The central problem, IMO, is that the registrar, Public
Domain Registry, fell for these assertions.

In a sense, the registrar had sufficient oversight applied to it, as
EasyDNS took them to arbitration and won.  But it shouldn't take that
much effort to get a registrar to follow the rules.

It seems that the oversight that is needed is to ensure that
registrars are sufficiently punished for not following the rules that
they do follow the rules.

The analogy is with other organizations that hold valuable property
belonging to others.  For instance, a bank holds money that belongs to
other people.  People would not be particularly surprised if a random
person walked into a bank and attempted to obtain the money that
belonged to another person.  But they would be aghast if the bank did
give it to them.

Dale

From christopher.morrow@gmail.com  Thu Jan 16 12:46:30 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC9111ACCEF for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_PHARMACY=1, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zP6NSU6YkEHX for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 12:46:29 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) by ietfa.amsl.com (Postfix) with ESMTP id 787291ABBB1 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:46:29 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id u14so2337684lbd.9 for <ietf@ietf.org>; Thu, 16 Jan 2014 12:46:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ugCrRg5k2v97vji6mJ+yzarVKrWk8WH0UqM/P/0T/6o=; b=lOKFKmpcK+Tv5RIhfCBpBbGJYbG/EvutmVUspueK45sQvA5YV0QkAADhy1E/gTSiZU 1ju2m6KYmHht3CCOEkfcTbPhMiZYmLiYd6a+Y2cWbY80uI44eUPRIFJYs4st5ssQHR5h MerAWBu4poLQXexSgpgMFejJbuOPqbxnbdOTGNlh19uxuMi9OCuCJL/S7iDo9DsNffjb dlpLd7GojAvO/ltD94LVdFUzX4B8rKZRb+RntmqAWLNQwLJGe+d051fN0qTJK+AtiaH2 cpnbVM0it9VW6XD9RI4GyQddM7EJTREASUJs1Y9PYUBDHqCXMKfb7VG/c0lu7ACFcFPT +ZQQ==
MIME-Version: 1.0
X-Received: by 10.152.5.199 with SMTP id u7mr2073060lau.48.1389905176318; Thu, 16 Jan 2014 12:46:16 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.37.170 with HTTP; Thu, 16 Jan 2014 12:46:16 -0800 (PST)
In-Reply-To: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
References: <CAMm+Lwimtgj9NZ55mcr=KWw+24gk8SDuAiMxpUfd71J2jA+mPA@mail.gmail.com>
Date: Thu, 16 Jan 2014 15:46:16 -0500
X-Google-Sender-Auth: i7Rhp_SXa0nhEGlxBmYTT3Sc_OY
Message-ID: <CAL9jLab3z=MY1CQLXOCw3iobqSswvUuz7U06JG6MBh0E4KZHkA@mail.gmail.com>
Subject: Re: A DNS security issue that might actually have impact eventually
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 20:46:31 -0000

On Sun, Jan 12, 2014 at 11:02 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> In recent news there have been two cases of DNS registrars being 'ordered'
> to take down domain names and lock them against transfer. The city of London
> police case is well known. There is also a Pharmacy industry group asserting
> the 'right' to take down sites without a court order or any form of due
> process.

this has been going on for ~5+ years now, DHS/ICE asserts this sort of
authority almost daily on com/net (at least)... and has gotten into
the press several times for 'bad' takedowns. (there was a rather loud
incident with: Rojadirecta.org in 2001)

I don't quite understand how the above 2 examples are any different,
it'd be nice if gov'ts would stop asserting this sort of control
method :( especially since it's not particularly effective at stopping
bad actors.

-chris

From rcallon@juniper.net  Thu Jan 16 14:32:41 2014
Return-Path: <rcallon@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 665891A1F76; Thu, 16 Jan 2014 14:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQ3yua-8N6Xc; Thu, 16 Jan 2014 14:32:39 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id 46EE61A1F62; Thu, 16 Jan 2014 14:32:38 -0800 (PST)
Received: from mail136-ch1-R.bigfish.com (10.43.68.242) by CH1EHSOBE021.bigfish.com (10.43.70.78) with Microsoft SMTP Server id 14.1.225.22; Thu, 16 Jan 2014 22:32:26 +0000
Received: from mail136-ch1 (localhost [127.0.0.1])	by mail136-ch1-R.bigfish.com (Postfix) with ESMTP id 8B542C0116;	Thu, 16 Jan 2014 22:32:26 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: VPS-26(z579ehz98dI9371I936eI15bfK542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah1fc6hzz1de098h1033IL8275bh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h9a9j1155h)
Received-SPF: pass (mail136-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rcallon@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(679001)(689001)(779001)(51704005)(377454003)(377424004)(55674002)(24454002)(199002)(189002)(13464003)(81686001)(33646001)(81816001)(79102001)(56776001)(80976001)(46102001)(77982001)(59766001)(66066001)(49866001)(47736001)(80022001)(47976001)(50986001)(63696002)(4396001)(65816001)(54356001)(54316002)(76482001)(19580395003)(51856001)(19580405001)(83322001)(53806001)(76796001)(76786001)(76576001)(85852003)(83072002)(92566001)(93136001)(74706001)(31966008)(47446002)(74502001)(74662001)(90146001)(93516002)(56816005)(2656002)(81542001)(87936001)(81342001)(74316001)(74366001)(85306002)(87266001)(69226001)(74876001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB635; H:CO2PR05MB636.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:; RD:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail136-ch1 (localhost.localdomain [127.0.0.1]) by mail136-ch1 (MessageSwitch) id 1389911544490974_30073; Thu, 16 Jan 2014 22:32:24 +0000 (UTC)
Received: from CH1EHSMHS015.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.236])	by mail136-ch1.bigfish.com (Postfix) with ESMTP id 707C938004A;	Thu, 16 Jan 2014 22:32:24 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS015.bigfish.com (10.43.70.15) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 16 Jan 2014 22:32:24 +0000
Received: from CO2PR05MB635.namprd05.prod.outlook.com (10.141.199.22) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.395.1; Thu, 16 Jan 2014 22:32:23 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) by CO2PR05MB635.namprd05.prod.outlook.com (10.141.199.22) with Microsoft SMTP Server (TLS) id 15.0.851.11; Thu, 16 Jan 2014 22:32:20 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) by CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) with mapi id 15.00.0851.011; Thu, 16 Jan 2014 22:32:20 +0000
From: Ross Callon <rcallon@juniper.net>
To: "Eggert, Lars" <lars@netapp.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81jtn8uxkZO2EiBZeT7DEf4ppp6pziAgAK2KYCAAFQ7gIAAckaAgAAJRICAAAZDAIAD31WAgABWkACAAHXPgIAAN0wAgAEJtoCAACSWAIAAC2+AgAAH1ACAABCvgIAAAQmAgAABlACAAz/IAIAAA6wAgABUpZA=
Date: Thu, 16 Jan 2014 22:32:19 +0000
Message-ID: <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
In-Reply-To: <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 0093C80C01
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 22:32:41 -0000

>> These tunnels are stateless
>
> yep. (But they don't have to be.)

The tunnels strictly speaking do not have to be stateless. However, if you =
want routers to actually implement them, and you want to scale in both forw=
arding speed and number of tunnels, then yes they do have to be stateless.=
=20

Ross
(speaking only as an individual contributor)=20

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Eggert, Lars
Sent: Thursday, January 16, 2014 12:20 PM
To: EXT - joelja@bogus.com
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Hi,

On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> These tunnels are stateless

yep. (But they don't have to be.)

>  The endpoints not the encapsulators have visibility into the
> end-to-end loss latency properties of the path.

Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domai=
ns - where not reacting to congestion may be OK - can now go over the wider=
 Internet, where this is not OK.

I'd be great if those apps would change. But in the meantime, it's the duty=
 of the encapsulator - who enables this traffic to break out of an L2 domai=
n and go over the wider net - to make sure the traffic it emits conforms to=
 our BCPs.

>  the encapsulator is an intermediate hop, similar to any other router
> in the path.

It's not. For the rest of the network, that encapsulator is indistinguishab=
le from any other app that sends UDP traffic.

UDP is a transport-layer protocol, and we have practices how it is to be us=
ed on the net. If you want to use it for encapsulation, you bind yourself t=
o these BCPs.

Look at it the other way: if transport area folks would want to send MPLS p=
ackets into the network in some problematic way, I'm sure the routing and o=
ps folks would not be amused.

Lars


From david.black@emc.com  Thu Jan 16 15:30:46 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445191AD8DC; Thu, 16 Jan 2014 15:30:46 -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=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8J2BoqhG88xP; Thu, 16 Jan 2014 15:30:43 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA971AD8F1; Thu, 16 Jan 2014 15:30:42 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0GNULYB011556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jan 2014 18:30:22 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0GNULYB011556
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1389915022; bh=IcrX37rbU6dLxyqQDK6Gr/DzMGM=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=XfMLFdqepTYNinQMvjQbRYdhNPnbPnU0uCDkiU/WMvtnqD0OOpl6A8tC0+GKikC3U xrTZzzWz6NBUISPoY1y9Ek+cNCDnFIrLtJMP+A9zUs8v81Tk+9SOzU1pvN9ZDF5QHT g6O/j5klzILfUmqvRhRwEOEuueQnViCcG+VImkyE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0GNULYB011556
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd04.lss.emc.com (RSA Interceptor); Thu, 16 Jan 2014 15:30:13 -0800
Received: from mxhub14.corp.emc.com (mxhub14.corp.emc.com [128.222.70.235]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0GNUBHm026761 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 16 Jan 2014 18:30:12 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub14.corp.emc.com ([128.222.70.235]) with mapi; Thu, 16 Jan 2014 18:30:11 -0500
From: "Black, David" <david.black@emc.com>
To: "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>, "attila.takacs@ericsson.com" <attila.takacs@ericsson.com>, "hejia@huawei.com" <hejia@huawei.com>, "don.fedyk@gmail.com" <don.fedyk@gmail.com>
Date: Thu, 16 Jan 2014 18:30:09 -0500
Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-12
Thread-Topic: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-12
Thread-Index: Ac8TEuVFfzpzNuIgSz6mj6KV0hTVBg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F04760D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public, Resumes
Cc: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jan 2014 23:30:46 -0000

The -12 version of this draft addresses the nits and editorial items
noted in the Gen-ART review of the -11 version.  It's ready for
RFC publication.

Thanks,
--David

> -----Original Message-----
> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of Black, David
> Sent: Sunday, December 29, 2013 9:51 PM
> To: General Area Review Team (gen-art@ietf.org); attila.takacs@ericsson.c=
om;
> donald.fedyk@alcatel-lucent.com; hejia@huawei.com
> Cc: adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ccamp-oam-configurati=
on-
> fwk-11
>=20
> One additional nit - Don Fedyk's email address listed in the draft does n=
ot
> work.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Sunday, December 29, 2013 9:46 PM
> > To: General Area Review Team (gen-art@ietf.org); attila.takacs@ericsson=
.com;
> > donald.fedyk@alcatel-lucent.com; hejia@huawei.com
> > Cc: Black, David; adrian@olddog.co.uk; ccamp@ietf.org; ietf@ietf.org
> > Subject: Gen-ART review of draft-ietf-ccamp-oam-configuration-fwk-11
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-ccamp-oam-configuration-fwk-11
> > Reviewer: David L. Black
> > Review Date: December 29, 2013
> > IETF LC End Date: January 5, 2014
> >
> > Summary: This draft is basically ready for publication, but has nits th=
at
> > should be fixed before publication.
> >
> > This draft describes the GMPLS framework for signaling OAM configuratio=
n,
> > and specifies additional RSVP elements to support that signaling.  Know=
ledge
> > of RSVP, and specifically RSVP-TE is assumed; beyond that, the draft is
> > complete, although it is very detailed - see editorial comment below on
> > Section 3.
> >
> > Nits/editorial comments:
> >
> > Sections 3.1-3.3 dive into the details very quickly.  They would be eas=
ier
> to
> > understand if there was an overview paragraph near the start of Section=
 3
> that
> > describes the roles of the two ADMIN_STATUS flags and the two LSP Attri=
butes
> > flags in OAM configuration (establishment, change/adjustment, deletion)
> before
> > the current text that contains the details of RSVP message processing.
> >
> > There are a number of instances of "(IANA to assign)" in section 4 that=
 the
> > RFC Editor will need to remove - an RFC Editor note to that effect shou=
ld
> > be inserted at the start of Section 4.
> >
> > Section 4.5 is necessarily incomplete on P2MP considerations, because (=
as
> > it says) "P2MP OAM mechanisms are very specific to the data plane
> technology".
> > It would be helpful if section 4.5 contained language indicating what a
> > specific data plane specification should include to completely specify
> > P2MP OAM configuration for that data plane.
> >
> > idnits 2.13.01 didn't find anything that needs attention.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From l.wood@surrey.ac.uk  Thu Jan 16 17:20:51 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE9D11AC421; Thu, 16 Jan 2014 17:20:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XiYWqPUW1Yja; Thu, 16 Jan 2014 17:20:49 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) by ietfa.amsl.com (Postfix) with ESMTP id 6369E1A9313; Thu, 16 Jan 2014 17:20:48 -0800 (PST)
Received: from [195.245.231.67:38745] by server-7.bemta-5.messagelabs.com id B3/5E-04824-36588D25; Fri, 17 Jan 2014 01:20:35 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-82.messagelabs.com!1389921634!28548228!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26895 invoked from network); 17 Jan 2014 01:20:34 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-7.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 17 Jan 2014 01:20:34 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 17 Jan 2014 01:20:34 +0000
From: <l.wood@surrey.ac.uk>
To: <rcallon@juniper.net>, <lars@netapp.com>
Date: Fri, 17 Jan 2014 01:19:41 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81jtn8uxkZO2EiBZeT7DEf4ppp6pziAgAK2KYCAAFQ7gIAAckaAgAAJRICAAAZDAIAD31WAgABWkACAAHXPgIAAN0wAgAEJtoCAACSWAIAAC2+AgAAH1ACAABCvgIAAAQmAgAABlACAAz/IAIAAA6wAgABUpZCAADFtow==
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346CE@EXMB01CMS.surrey.ac.uk>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>, <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com>
In-Reply-To: <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 01:20:52 -0000

Surely you mean minimised state?

The tunnels have to know where the other tunnel endpoint is - state. This i=
s distinct from having a congestion-aware state machine that e.g. TCP inclu=
des...

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: mpls [mpls-bounces@ietf.org] On Behalf Of Ross Callon [rcallon@junipe=
r.net]
Sent: 16 January 2014 22:32
To: Eggert, Lars
Cc: EXT - joelja@bogus.com; mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

>> These tunnels are stateless
>
> yep. (But they don't have to be.)

The tunnels strictly speaking do not have to be stateless. However, if you =
want routers to actually implement them, and you want to scale in both forw=
arding speed and number of tunnels, then yes they do have to be stateless.

Ross
(speaking only as an individual contributor)

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Eggert, Lars
Sent: Thursday, January 16, 2014 12:20 PM
To: EXT - joelja@bogus.com
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Hi,

On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> These tunnels are stateless

yep. (But they don't have to be.)

>  The endpoints not the encapsulators have visibility into the
> end-to-end loss latency properties of the path.

Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domai=
ns - where not reacting to congestion may be OK - can now go over the wider=
 Internet, where this is not OK.

I'd be great if those apps would change. But in the meantime, it's the duty=
 of the encapsulator - who enables this traffic to break out of an L2 domai=
n and go over the wider net - to make sure the traffic it emits conforms to=
 our BCPs.

>  the encapsulator is an intermediate hop, similar to any other router
> in the path.

It's not. For the rest of the network, that encapsulator is indistinguishab=
le from any other app that sends UDP traffic.

UDP is a transport-layer protocol, and we have practices how it is to be us=
ed on the net. If you want to use it for encapsulation, you bind yourself t=
o these BCPs.

Look at it the other way: if transport area folks would want to send MPLS p=
ackets into the network in some problematic way, I'm sure the routing and o=
ps folks would not be amused.

Lars

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

From l.wood@surrey.ac.uk  Thu Jan 16 19:06:37 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F691ADE87; Thu, 16 Jan 2014 19:06:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjEAOtZQdtJa; Thu, 16 Jan 2014 19:06:34 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id 3A20A1ADE86; Thu, 16 Jan 2014 19:06:33 -0800 (PST)
Received: from [85.158.136.51:60836] by server-1.bemta-5.messagelabs.com id 28/01-21065-D2E98D25; Fri, 17 Jan 2014 03:06:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-49.messagelabs.com!1389927980!23311593!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26557 invoked from network); 17 Jan 2014 03:06:20 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-16.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 17 Jan 2014 03:06:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 17 Jan 2014 03:06:20 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <lars@netapp.com>, <joelja@bogus.com>
Date: Fri, 17 Jan 2014 03:03:05 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8S4Wu6DFHO19nLS4OJGfloEdinxgATzjW0
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.uk>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>, <52D8185D.1010902@cisco.com>
In-Reply-To: <52D8185D.1010902@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 03:06:37 -0000

There's an opportunity to define a simple generic IPv6 encapsulating mechan=
ism a la UDP, but
with a payload checksum of varying coverage (header only, partial payload, =
full payload)
and with the (stronger than UDP) checksum placed at the end of the packet.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@ci=
sco.com]
Sent: 16 January 2014 17:35
To: Eggert, Lars; Joel Jaeggli
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

On 16/01/2014 17:19, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
>> These tunnels are stateless
> yep. (But they don't have to be.)
Ah, they do if they are to scale. State at speed is really hard. The sort
of systems we are talking about do things like pipeline counters
and it is loooooots of packets later before the counter is actually
incremented.
>>   The endpoints not the encapsulators have visibility into the
>> end-to-end loss latency properties of the path.
> Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 dom=
ains - where not reacting to congestion may be OK - can now go over the wid=
er Internet, where this is not OK.
>
> I'd be great if those apps would change. But in the meantime, it's the du=
ty of the encapsulator - who enables this traffic to break out of an L2 dom=
ain and go over the wider net - to make sure the traffic it emits conforms =
to our BCPs.
>
>>   the encapsulator is an intermediate hop, similar to any other router
>> in the path.
> It's not. For the rest of the network, that encapsulator is indistinguish=
able from any other app that sends UDP traffic.
>
> UDP is a transport-layer protocol, and we have practices how it is to be =
used on the net. If you want to use it for encapsulation, you bind yourself=
 to these BCPs.
>
> Look at it the other way: if transport area folks would want to send MPLS=
 packets into the network in some problematic way, I'm sure the routing and=
 ops folks would not be amused.
The root cause of the problem here is that UDP, has bifurcated into
a general purpose encapsulation.

Stewart


From narten@us.ibm.com  Thu Jan 16 21:53:20 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5471ADF81 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 21:53:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.439
X-Spam-Level: 
X-Spam-Status: No, score=-7.439 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5yxLBeGVGvk6 for <ietf@ietfa.amsl.com>; Thu, 16 Jan 2014 21:53:19 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6651ADF7E for <ietf@ietf.org>; Thu, 16 Jan 2014 21:53:19 -0800 (PST)
Received: from /spool/local by e34.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 16 Jan 2014 22:53:06 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 16 Jan 2014 22:53:04 -0700
Received: from b03cxnp08026.gho.boulder.ibm.com (b03cxnp08026.gho.boulder.ibm.com [9.17.130.18]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 9CD2519D8042 for <ietf@ietf.org>; Thu, 16 Jan 2014 22:52:54 -0700 (MST)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by b03cxnp08026.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0H5qpNG7733618 for <ietf@ietf.org>; Fri, 17 Jan 2014 06:52:51 +0100
Received: from d03av02.boulder.ibm.com (localhost [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0H5r3u5023031 for <ietf@ietf.org>; Thu, 16 Jan 2014 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0H5r2I5022984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 16 Jan 2014 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s0H5r25e014733 for <ietf@ietf.org>; Fri, 17 Jan 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s0H5r2vJ014687 for ietf@ietf.org; Fri, 17 Jan 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201401170553.s0H5r2vJ014687@rotala.raleigh.ibm.com>
Date: Fri, 17 Jan 2014 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-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14011705-1542-0000-0000-0000054E3DE1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 05:53:20 -0000

Total of 157 messages in the last 7 days.
 
script run at: Fri Jan 17 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 15.29% |   24 | 17.30% |   240154 | curtis@ipv6.occnc.com
  8.92% |   14 | 10.75% |   149235 | l.wood@surrey.ac.uk
  8.92% |   14 |  7.02% |    97422 | scott.brim@gmail.com
  6.37% |   10 |  8.23% |   114286 | stbryant@cisco.com
  5.73% |    9 |  7.16% |    99333 | xuxiaohu@huawei.com
  6.37% |   10 |  5.66% |    78623 | lars@netapp.com
  3.82% |    6 |  3.40% |    47165 | mark.tinka@seacom.mu
  3.18% |    5 |  2.82% |    39119 | jmh@joelhalpern.com
  2.55% |    4 |  3.01% |    41732 | hsantos@isdg.net
  2.55% |    4 |  2.89% |    40159 | alexander.vainshtein@ecitele.com
  2.55% |    4 |  1.74% |    24125 | randy@psg.com
  1.91% |    3 |  1.74% |    24143 | stephen.farrell@cs.tcd.ie
  1.91% |    3 |  1.53% |    21213 | lear@cisco.com
  1.91% |    3 |  1.30% |    18057 | hartmans-ietf@mit.edu
  1.27% |    2 |  1.62% |    22478 | edc@google.com
  1.27% |    2 |  1.19% |    16582 | gregory.mirsky@ericsson.com
  1.27% |    2 |  1.13% |    15734 | fred@cisco.com
  1.27% |    2 |  1.11% |    15375 | abdussalambaryun@gmail.com
  1.27% |    2 |  1.07% |    14921 | brian.e.carpenter@gmail.com
  1.27% |    2 |  1.07% |    14909 | gorry@erg.abdn.ac.uk
  1.27% |    2 |  1.00% |    13892 | wes@mti-systems.com
  1.27% |    2 |  0.99% |    13754 | sm@resistor.net
  1.27% |    2 |  0.98% |    13559 | johnl@taugh.com
  1.27% |    2 |  0.92% |    12727 | mansaxel@besserwisser.org
  1.27% |    2 |  0.86% |    11998 | dhc@dcrocker.net
  1.27% |    2 |  0.77% |    10663 | jari.arkko@piuha.net
  0.64% |    1 |  1.02% |    14144 | hannes.tschofenig@gmx.net
  0.64% |    1 |  0.98% |    13663 | ron.even.tlv@gmail.com
  0.64% |    1 |  0.79% |    10998 | rcallon@juniper.net
  0.64% |    1 |  0.75% |    10444 | narten@us.ibm.com
  0.64% |    1 |  0.73% |    10088 | daedulus@btconnect.com
  0.64% |    1 |  0.72% |    10022 | presnick@qti.qualcomm.com
  0.64% |    1 |  0.71% |     9894 | david.black@emc.com
  0.64% |    1 |  0.71% |     9849 | john-ietf@jck.com
  0.64% |    1 |  0.69% |     9547 | hallam@gmail.com
  0.64% |    1 |  0.67% |     9364 | mbj@tail-f.com
  0.64% |    1 |  0.67% |     9316 | david.i.allan@ericsson.com
  0.64% |    1 |  0.61% |     8470 | yakushev@google.com
  0.64% |    1 |  0.58% |     8039 | joelja@bogus.com
  0.64% |    1 |  0.49% |     6738 | kent@bbn.com
  0.64% |    1 |  0.47% |     6515 | farinacci@gmail.com
  0.64% |    1 |  0.45% |     6252 | morrowc.lists@gmail.com
  0.64% |    1 |  0.44% |     6171 | sm+ietf@elandsys.com
  0.64% |    1 |  0.44% |     6162 | cabo@tzi.org
  0.64% |    1 |  0.43% |     5982 | worley@ariadne.com
  0.64% |    1 |  0.36% |     5056 | chair@ietf.org
--------+------+--------+----------+------------------------
100.00% |  157 |100.00% |  1388072 | Total


From joelja@bogus.com  Thu Jan 16 23:38:40 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 880541ADFA8; Thu, 16 Jan 2014 23:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSkRdsFf0hGv; Thu, 16 Jan 2014 23:38:39 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2625B1ADFA7; Thu, 16 Jan 2014 23:38:39 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0H7cHHJ042299 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Jan 2014 07:38:18 GMT (envelope-from joelja@bogus.com)
Message-ID: <52D8DDE4.4020508@bogus.com>
Date: Thu, 16 Jan 2014 23:38:12 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
In-Reply-To: <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PTB8idFLvG0WvUqCJnR2Cn1E3EKCRKOsX"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Fri, 17 Jan 2014 07:38:19 +0000 (UTC)
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 07:38:40 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PTB8idFLvG0WvUqCJnR2Cn1E3EKCRKOsX
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1/16/14, 9:19 AM, Eggert, Lars wrote:
> Hi,
>=20
> On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
>> These tunnels are stateless
>=20
> yep. (But they don't have to be.)

They do in-fact have to be stateless with respect to the contents. They
will no doubt be created in a same distributed forwarding  engines that
currently do IP-MPLS encapsulation and L2-MPLS encapsulation. likewise
their decapsulation will occur in such devices.

> Look at it the other way: if transport area folks would want to send
> MPLS packets into the network in some problematic way, I'm sure the
> routing and ops folks would not be amused.

Today congestion occurs on MPLS networks. intermediate hops that are
congested have no choice but to drop packets.

> Lars
>=20



--PTB8idFLvG0WvUqCJnR2Cn1E3EKCRKOsX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLY3eQACgkQ8AA1q7Z/VrKRiACeNJwruJc6ZxAtze2GyK0NGi3j
etQAn1O9s33glGXzGVt/tTtvvEYq971f
=3puk
-----END PGP SIGNATURE-----

--PTB8idFLvG0WvUqCJnR2Cn1E3EKCRKOsX--

From joelja@bogus.com  Fri Jan 17 12:43:27 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1121AC829; Fri, 17 Jan 2014 12:43:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LE5mSixiKu7f; Fri, 17 Jan 2014 12:43:26 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 432D71AC3FA; Fri, 17 Jan 2014 12:43:26 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0HKh3Od046197 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 17 Jan 2014 20:43:04 GMT (envelope-from joelja@bogus.com)
Message-ID: <52D995D2.8080301@bogus.com>
Date: Fri, 17 Jan 2014 12:42:58 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: stbryant@cisco.com, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <52D8185D.1010902@cisco.com>
In-Reply-To: <52D8185D.1010902@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GuGkHp4QL3d7iFsdeIdh6Hbc3lHN8oka2"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Fri, 17 Jan 2014 20:43:04 +0000 (UTC)
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 20:43:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GuGkHp4QL3d7iFsdeIdh6Hbc3lHN8oka2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1/16/14, 9:35 AM, Stewart Bryant wrote:

>> Look at it the other way: if transport area folks would want to=20
>> send MPLS packets into the network in some problematic way, I'm=20
>> sure the routing and ops folks would not be amused.
> The root cause of the problem here is that UDP, has bifurcated into a
> general purpose encapsulation.

One observation with respect to general purpose use of UDP as an mpls
encapsulation on the internet as a whole that seems to have been missed
in this discussion is the rather dire prospects for MTU and potential for=

fragmentation. Effectively, assuring, that you do not need to fragment
requires as certain amount of coordination.

1500 mtu hops pretty effectively (imho) preclude the use of this
encapsulation on the internet as a whole (if encapsulated traffic is not
aware of a correspondingly lower MTU) this is especially true for L2vpn
where you don't have recourse to PMTUD). As the document notes (section 4=
)
preventing fragmentation is rather important.


> Stewart
>=20



--GuGkHp4QL3d7iFsdeIdh6Hbc3lHN8oka2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLZldIACgkQ8AA1q7Z/VrLhogCdHy2PVsXywjUA9w7lZE0MCNmy
xBsAnRqNZrp2CA75dUJgKFoiT8Aw8dMW
=JzkE
-----END PGP SIGNATURE-----

--GuGkHp4QL3d7iFsdeIdh6Hbc3lHN8oka2--

From l.wood@surrey.ac.uk  Fri Jan 17 15:02:52 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0F371ACCFC; Fri, 17 Jan 2014 15:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jq-S5rQz7nl1; Fri, 17 Jan 2014 15:02:50 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.152]) by ietfa.amsl.com (Postfix) with ESMTP id 16F501ACCEC; Fri, 17 Jan 2014 15:02:49 -0800 (PST)
Received: from [195.245.231.67:50151] by server-16.bemta-5.messagelabs.com id 59/ED-11843-C86B9D25; Fri, 17 Jan 2014 23:02:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-82.messagelabs.com!1389999756!28651413!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20611 invoked from network); 17 Jan 2014 23:02:36 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-7.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 17 Jan 2014 23:02:36 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 17 Jan 2014 23:02:35 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Fri, 17 Jan 2014 23:00:33 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8Tr7KVwfV8Zc1FQSC8mGxyu7YwzAAKDq3C
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D1@EXMB01CMS.surrey.ac.uk>
References: Your message of "Fri, 17 Jan 2014 03:03:05 +0000." <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.uk>, <201401171805.s0HI5kUC063603@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401171805.s0HI5kUC063603@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 23:02:52 -0000

Yes, it would be unreasonable for the router vendors themselves to design
something with a trailing checksum and pseudo-header check that would meet
their forwarding needs while ensuring reliability.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 17 January 2014 18:05
To: Wood L  Dr (Electronic Eng)
Cc: stbryant@cisco.com; lars@netapp.com; joelja@bogus.com; mpls@ietf.org; i=
etf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

In message <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:

> There's an opportunity to define a simple generic IPv6 encapsulating
> mechanism a la UDP, but with a payload checksum of varying coverage
> (header only, partial payload, full payload) and with the (stronger
> than UDP) checksum placed at the end of the packet.
>
> Lloyd Wood
> http://about.me/lloydwood


Go for it!

When a critical mass of routers hash on this new protocol number and
port space we'll let you know and the MPLS WG can obsolete MPLS over
UDP and replace it with MPLS over this new protocol.

Thanks for offering to write this.

Curtis


> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@=
cisco.com]
> Sent: 16 January 2014 17:35
> To: Eggert, Lars; Joel Jaeggli
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting MPLS in UDP) to Proposed Standard
>
> On 16/01/2014 17:19, Eggert, Lars wrote:
> > Hi,
> >
> > On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> >> These tunnels are stateless
> > yep. (But they don't have to be.)
> Ah, they do if they are to scale. State at speed is really hard. The sort
> of systems we are talking about do things like pipeline counters
> and it is loooooots of packets later before the counter is actually
> incremented.
> >>   The endpoints not the encapsulators have visibility into the
> >> end-to-end loss latency properties of the path.
> > Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 d=
omains - where not reacting to congestion may be OK - can now go over the w=
ider Internet, where this is not OK.
> >
> > I'd be great if those apps would change. But in the meantime, it's the =
duty of the encapsulator - who enables this traffic to break out of an L2 d=
omain and go over the wider net - to make sure the traffic it emits conform=
s to our BCPs.
> >
> >>   the encapsulator is an intermediate hop, similar to any other router
> >> in the path.
> > It's not. For the rest of the network, that encapsulator is indistingui=
shable from any other app that sends UDP traffic.
> >
> > UDP is a transport-layer protocol, and we have practices how it is to b=
e used on the net. If you want to use it for encapsulation, you bind yourse=
lf to these BCPs.
> >
> > Look at it the other way: if transport area folks would want to send MP=
LS packets into the network in some problematic way, I'm sure the routing a=
nd ops folks would not be amused.
> The root cause of the problem here is that UDP, has bifurcated into
> a general purpose encapsulation.
>
> Stewart
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From peter@akayla.com  Fri Jan 17 23:21:44 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22CD71A1F56; Fri, 17 Jan 2014 23:21:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level: 
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1tcia87JT9x; Fri, 17 Jan 2014 23:21:42 -0800 (PST)
Received: from p3plsmtpa07-09.prod.phx3.secureserver.net (p3plsmtpa07-09.prod.phx3.secureserver.net [173.201.192.238]) by ietfa.amsl.com (Postfix) with ESMTP id 5B72B1A1F1F; Fri, 17 Jan 2014 23:21:42 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa07-09.prod.phx3.secureserver.net with  id FKMR1n0061huGat01KMRgb; Sat, 18 Jan 2014 00:21:29 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-mpls-multipath-use.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-multipath-use-03
Date: Fri, 17 Jan 2014 23:21:28 -0800
Message-ID: <02d101cf141d$ea1a8f50$be4fadf0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8UHcdwianJ3UTFS4ylM1d/AUj2Sg==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jan 2014 07:21:44 -0000

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

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

Document: draft-ietf-mpls-multipath-use-03
Reviewer: Peter Yee
Review Date: January-16-2014
IETF LC End Date: January-17-2014
IESG Telechat date: January-23-2014

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

This document discusses multipath MPLS operations and describes the means of
supporting MPLS as a server layer for MPLS-TP and vice versa.  It lists
requirements and implications for these operations.


Nits:

General nits:

Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
consistency with RFC 2991.

In the usage RFCxxxx, use a space between RFC and xxxx except when used as a
reference, e.g., [RFCxxxx].

There are many unexplained acronyms without definition or reference.  Unless
these are abundantly clear to most readers, expand them on first usage and
provide a reference pointer where feasible.

Specific nits:

Page 1, Abstract, 2nd paragraph, 1st sentence: change "MPLS Entropy label"
to "the MPLS Entropy Label".

Page 2, Section 1, 1st paragraph,  1st sentence: delete the comma after
"traffic".

Page 2, Section 1, 1st paragraph, last sentence: change "load split" to
"load splitting".

Page 2, Section 1, 2nd paragraph, last sentence: hyphenate "fate sharing".

Page 3, Section 1, 1st paragraph, 1st sentence: hyphenate "equal cost".

Page 3, definition of "Loop Free Alternate Paths (LFA)": hyphenate "Loop
Free".

Page 3, definition of "Loop Free Alternate Paths (LFA), 1st sentence: change
the terminating period to a colon.

Page 4, Section 3.1, 1st paragraph, 1st sentence: change "date" to "data".

Page 4, Section 3.1, 1st paragraph, 2nd sentence: change the terminating
period to a colon.

Page 5, 1st full paragraph, 1st sentence: insert "Section 3.1.1" between
"[RFC5960]" and "paragraph 3".  Capitalize "paragraph".

Page 5, 1st full paragraph, 3rd sentence: same as previous instructions.

Page 5, 2nd paragraph, 2nd sentence: change ' "Section 1 Introduction"' to '
Section 1 ("Introduction")'.

Page 6, 1st paragraph, 3rd sentence: change ' "Section 2.9.4 Equal Cost
Multipath") to ' Section 2.9.4 ("Equal Cost Multipath")'.

Page 6, Section 3.2, 1st paragraph, 1st sentence: hyphenate "MPLS-TP
conformant" and delete the comma after "multipath".

Page 7, 2nd paragraph, 2nd sentence: change "A" to "An".

Page 7, 2nd paragraph, 5th and 6th sentences: change all occurrences of
"LSP" to "LSPs".

Page 7, 3rd paragraph, 2nd sentence: change "LSP" to "LSPs".

Page 7, 4th paragraph, 2nd sentence: change "LSR" to "LSRs".

Page 7, 5th paragraph: change all occurrences of "LSP" to "LSPs".

Page 7, 5th paragraph last sentence: change "co-existance" to "coexistence".

Page 8, 1st partial paragraph, 2nd full sentence: change all occurrences of
"LSP" to "LPSs" and change "LSR" to "LSRs".

Page 8, 2nd full paragraph: change all occurrences of "LSP" to "LSPs".

Page 8, 4th paragraph, 1st sentence: change "LSP" to "LSPs".

Page 8, 4th paragraph, 2nd sentence: is there a quantitative definition for
"very infrequent" that can be substituted or explained?

Page 8, 4th paragraph, 3rd sentence: change "presense" to "presence".
Insert "a" before "GAL".

Page 9, 1st partial paragraph: delete "label" following "EL" in two
locations.

Page 9, Section 4, 1st paragraph, 1st sentence: change first "LSP" to
"LSPs".  Change "a MPLS-TP" to "an MPLS-TP" unless MPLS is pronounced liked
"mipples" or something similar and not just spelled out.

Page 9, Section 4, 2nd paragraph: replace all occurrences of "LSP" with
"LSPs".

Page 9, Section 4, 2nd paragraph, 2nd sentence: insert "the" between "in"
and "number".

Page 9, Section 4, 2nd paragraph, 3rd sentence: change "ILM" to "ILMs".

Page 9, Section 4, 3rd paragraph, 1st sentence: change "Server Layer" to
"server layer" for consistency of usage.  Insert "of" between "use" and
"MPLS-TP".  Change "LSP" to "LSPs".

Page 9, Section 4, 3rd paragraph, 4th sentence: change "LSP" to "LSPs".

Page 9, Section 4, 3rd paragraph, 5th sentence: change "LSP" to "LSPs".
Change "capacity" to "capacities".  Insert "generally" before "not integer"
unless it is always the case that the capacity is not a multiple of 10 Gb/s.

Page 9, Section 4, 4th paragraph, 1st sentence: change "Server Layer" to
"server layer".

Page 10, Section 6, 2nd paragraph, 2nd sentence: hyphenate "high end" and
append a comma after that.  Hyphenate "packet processing".

Page 10, Section 6, 3rd paragraph, last sentence: same as previous
instructions.

Page 10, Section 8, 1st sentence: insert "a" between "of" and "framework".


I'm not particularly knowledgeable about MPLS, so I'm unable to express much
about the correctness of the operational points made in the document.

		-Peter Yee




From scott.brim@gmail.com  Sat Jan 18 12:41:59 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B4F1ADFB2; Sat, 18 Jan 2014 12:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bElx65-BpJLe; Sat, 18 Jan 2014 12:41:58 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 258571ADFB0; Sat, 18 Jan 2014 12:41:58 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp4so592121obc.2 for <multiple recipients>; Sat, 18 Jan 2014 12:41:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=nPeVYMZi4X8oKDE3pW+Qrv4MBL5tiQy2b03ZYGFM9eg=; b=U19wfrZS9MWi2hlDFj6v7rcT939XQ23wN5TQrggTDz8rRiQ97VWkgrkFa2Xf1gBXcd FFrybXrIDt/vvwLOTdVhFg5xfj729Jfh5N40I87lZLXowv8iK8gmOTdm7p91X0d8SugG +0Kfs7mv6pv5DwN+0B/0q3GlwfY9eEBz8kAbeyECJsJ1x8hYHWVMQV/+gvJxsz15duVg gbyOsJ4ODjtNVDrCE//DYb5SmJMqNLh1sfOaBFbwa+QVJ6Rm4vIVPp9r/KHwPhr3nudh S+Np2jodecvhU+pjAsiDlJTTVsRqCkL7dmAz7sea3mHgpHoH6s4iAx2IXxeHlT6GgSWd i9cw==
X-Received: by 10.182.102.7 with SMTP id fk7mr7978828obb.28.1390077705063; Sat, 18 Jan 2014 12:41:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sat, 18 Jan 2014 12:41:24 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 18 Jan 2014 15:41:24 -0500
Message-ID: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
Subject: Gen-Art telechat review of draft-farrell-perpass-attack-04
To: gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e015369f0d2126704f044afec
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jan 2014 20:41:59 -0000

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

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-farrell-perpass-attack-04
Reviewer: Scott Brim
Review Date: 2014-01-18
IETF LC End Date: 2013-12-31
IESG Telechat date: (if known): 2014-01-23

Summary: Ready

Major issues: none

Minor issues: none

Nits/editorial comments: There are editorial changes I could suggest, but
it's good enough.

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

<div dir=3D"ltr"><div><span style=3D"font-family:arial,sans-serif;font-size=
:12.727272033691406px">I am the assigned Gen-ART reviewer for this draft. F=
or background on</span><br style=3D"font-family:arial,sans-serif;font-size:=
12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Gen-ART, please see the FAQ at</span><br style=3D"font-family:arial,sans-s=
erif;font-size:12.727272033691406px"><span style=3D"font-family:arial,sans-=
serif;font-size:12.727272033691406px">&lt;=A0</span><a href=3D"http://wiki.=
tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank" style=3D"fon=
t-family:arial,sans-serif;font-size:12.727272033691406px">http://wiki.tools=
.ietf.org/<u></u>area/gen/trac/wiki/GenArtfaq</a><span style=3D"font-family=
:arial,sans-serif;font-size:12.727272033691406px">&gt;.</span><br style=3D"=
font-family:arial,sans-serif;font-size:12.727272033691406px">

<br style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"><=
span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">=
Please wait for direction from your document shepherd</span><br style=3D"fo=
nt-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>or AD before posting a new version of the draft.</span><br style=3D"font-f=
amily:arial,sans-serif;font-size:12.727272033691406px"><br style=3D"font-fa=
mily:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Document: draft-farrell-perpass-attack-04</span><br style=3D"font-family:a=
rial,sans-serif;font-size:12.727272033691406px"><span style=3D"font-family:=
arial,sans-serif;font-size:12.727272033691406px">Reviewer: Scott Brim</span=
><br style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Review Date: 2014-01-18</span><br style=3D"font-family:arial,sans-serif;fo=
nt-size:12.727272033691406px"><span style=3D"font-family:arial,sans-serif;f=
ont-size:12.727272033691406px">IETF LC End Date: 2013-12-31</span><br style=
=3D"font-family:arial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>IESG Telechat date: (if known): 2014-01-23</span><br style=3D"font-family:=
arial,sans-serif;font-size:12.727272033691406px"><br style=3D"font-family:a=
rial,sans-serif;font-size:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Summary: Ready</span><br style=3D"font-family:arial,sans-serif;font-size:1=
2.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-size:12=
.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Major issues: none</span><br style=3D"font-family:arial,sans-serif;font-si=
ze:12.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-siz=
e:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Minor issues: none</span><br style=3D"font-family:arial,sans-serif;font-si=
ze:12.727272033691406px"><br style=3D"font-family:arial,sans-serif;font-siz=
e:12.727272033691406px">

<span style=3D"font-family:arial,sans-serif;font-size:12.727272033691406px"=
>Nits/editorial comments: There are editorial changes I could suggest, but =
it&#39;s good enough.=A0</span></div></div>

--089e015369f0d2126704f044afec--

From jari.arkko@piuha.net  Sat Jan 18 12:53:28 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C571ADFB3; Sat, 18 Jan 2014 12:53:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKJRl8sRz4wJ; Sat, 18 Jan 2014 12:53:26 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E86041A1F79; Sat, 18 Jan 2014 12:53:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E3E602CC5D; Sat, 18 Jan 2014 22:53:11 +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 MZc5GEEJz606; Sat, 18 Jan 2014 22:53:11 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 59DEE2CC48; Sat, 18 Jan 2014 22:53:11 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
Date: Sat, 18 Jan 2014 22:53:12 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jan 2014 20:53:28 -0000

Thanks for your review, Scott.

Jari


From lear@cisco.com  Sun Jan 19 00:30:25 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4F31A8034; Sun, 19 Jan 2014 00:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.139
X-Spam-Level: 
X-Spam-Status: No, score=-8.139 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdt8IIL9HOGi; Sun, 19 Jan 2014 00:30:23 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id EA3FC1A1F7B; Sun, 19 Jan 2014 00:30:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5652; q=dns/txt; s=iport; t=1390120210; x=1391329810; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=jXVIzQrCfT0Oi3RVcfY3OxkoaM2eTqpycptsq1w1jqs=; b=R0VRpSzZ631asioSGD0cqQqbED1l93EQMfFpYj9tyWzjomujdeZ9dONj IHJQThe7xRTilOxYho/LtEJVBxeTYK9K7Gj4EcaInmkQ7nbNfyrdygPqz eMApbvR5TWVcX5SZLkqeVjoCaPhoUri+1LmwnuEpdxMkweANZS4fE8PIA o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFANeL21KQ/khL/2dsb2JhbABZgwuEC7g5gQYWdIIlAQEBAwEjVQEFCwsEHRYLAgIJAwIBAgFFBgEMAQcBAYd5CKdznCgXjn8Hgm+BSQSYIpIYgy47
X-IronPort-AV: E=Sophos;i="4.95,684,1384300800"; d="scan'208,217";a="3841992"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 19 Jan 2014 08:30:09 +0000
Received: from rtp-vpn4-845.cisco.com (rtp-vpn4-845.cisco.com [10.82.211.77]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0J8U4XI021152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);  Sun, 19 Jan 2014 08:30:07 GMT
Message-ID: <52DB8D0E.8000708@cisco.com>
Date: Sun, 19 Jan 2014 09:30:06 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
In-Reply-To: <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------050702060508070806070605"
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 08:30:26 -0000

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

Jari,

I oppose changes made to the document in the last round as stated
below.  If they remain, I would urge publication as Informational and
not BCP:

>    In particular, architectural decisions, including which existing
>    technology is re-used, may significantly impact the vulnerability of
>    a protocol to PM.  Those developing IETF specifications therefore
>    need to consider mitigating PM when making these architectural
>    decisions and be prepared to justify their decisions.  Getting
>    adequate, early review of architectural decisions including whether
>    appropriate mitigation of PM can be made is important.  Revisiting
>    these architectural decisions late in the process is very costly.

In the fact of a lack of common understanding regarding the threat, this
text can subject a working group to abuse and confusion.  This isn't
theoretical, as it has happened in the past that working group chairs
and area directors in particular have derailed efforts, setting
standardization and deployment of useful technology back years, and this
wasn't that long ago.

Let's make this discussion concrete with a few examples: the
implications may be that a working group chair or any participant
(although chairs are in a very good position to cause damage) could
insist that DHCP not be used to carry new attributes because there is no
common understanding of the scope of remediation that will be required. 
Before certain ADs roll their eyes, the discussion gets derailed as follows:

>> I propose the following DHCP option to configure my new frob.
<< But DHCP is transmitted in the clear.  Please justify this decision.
(or worse) << and by the way here is my very heavy weight alternative
that requires a valid cert chain
>> It's meant for the local wire.
<< But we don't know the scope of the attack.
...
...
>> Nevermind, I'll just use a vendor extension.  Goodbye.

Rinse and repeat with any other protocol that allows extensions.

It is fair to say that we should consider this threat at an
architectural level.  It's fair (albeit a truism) that finding design
flaws earlier in the process rather than later is less costly
(ENG-101).  Justification language like the above, however, is likely to
actively impede the IETF, as these sorts of things have in the past.

Eliot

--------------050702060508070806070605
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Jari,<br>
    <br>
    I oppose changes made to the document in the last round as stated
    below.Â  If they remain, I would urge publication as Informational
    and not BCP:<br>
    <br>
    <blockquote type="cite">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <pre class="newpage">   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.</pre>
    </blockquote>
    <br>
    In the fact of a lack of common understanding regarding the threat,
    this text can subject a working group to abuse and confusion.Â  This
    isn't theoretical, as it has happened in the past that working group
    chairs and area directors in particular have derailed efforts,
    setting standardization and deployment of useful technology back
    years, and this wasn't that long ago.<br>
    <br>
    Let's make this discussion concrete with a few examples: the
    implications may be that a working group chair or any participant
    (although chairs are in a very good position to cause damage) could
    insist that DHCP not be used to carry new attributes because there
    is no common understanding of the scope of remediation that will be
    required.Â  Before certain ADs roll their eyes, the discussion gets
    derailed as follows:<br>
    <br>
    &gt;&gt; I propose the following DHCP option to configure my new
    frob.<br>
    &lt;&lt; But DHCP is transmitted in the clear.Â  Please justify this
    decision.<br>
    (or worse) &lt;&lt; and by the way here is my very heavy weight
    alternative that requires a valid cert chain<br>
    &gt;&gt; It's meant for the local wire.<br>
    &lt;&lt; But we don't know the scope of the attack.<br>
    ...<br>
    ...<br>
    &gt;&gt; Nevermind, I'll just use a vendor extension.Â  Goodbye.<br>
    <br>
    Rinse and repeat with any other protocol that allows extensions.<br>
    <br>
    It is fair to say that we should consider this threat at an
    architectural level.Â  It's fair (albeit a truism) that finding
    design flaws earlier in the process rather than later is less costly
    (ENG-101).Â  Justification language like the above, however, is
    likely to actively impede the IETF, as these sorts of things have in
    the past.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------050702060508070806070605--

From l.wood@surrey.ac.uk  Sun Jan 19 00:44:07 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10E61AC404; Sun, 19 Jan 2014 00:44: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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nfJWmohPcnER; Sun, 19 Jan 2014 00:44:01 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id E0F641A1F7B; Sun, 19 Jan 2014 00:44:00 -0800 (PST)
Received: from [195.245.230.131:26705] by server-13.bemta-3.messagelabs.com id FB/D3-28603-3409BD25; Sun, 19 Jan 2014 08:43:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1390121026!34043651!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 30602 invoked from network); 19 Jan 2014 08:43:46 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 19 Jan 2014 08:43:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 19 Jan 2014 08:43:46 +0000
From: <l.wood@surrey.ac.uk>
To: <lear@cisco.com>, <jari.arkko@piuha.net>, <scott.brim@gmail.com>
Date: Sun, 19 Jan 2014 08:40:47 +0000
Subject: RE: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: Ac8U8MEok9fz/WlXRMWMb8h7UVlG7gAAWTgr
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D3@EXMB01CMS.surrey.ac.uk>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>, <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art@ietf.org, ietf@ietf.org, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 08:44:07 -0000

+1. if you must publish this, publish as informational, as previous referen=
ced security docs have been.

A doc that says 'you just haven't considered security enough' is not specif=
ying the details or scope of a best current practice that can be sensibly f=
ollowed.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Eliot Lear [lear@cisco.com]
Sent: 19 January 2014 08:30
To: Jari Arkko; Scott Brim
Cc: gen-art; IETF discussion list; draft-farrell-perpass-attack.all@tools.i=
etf.org
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04

Jari,

I oppose changes made to the document in the last round as stated below.  I=
f they remain, I would urge publication as Informational and not BCP:


   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.

In the fact of a lack of common understanding regarding the threat, this te=
xt can subject a working group to abuse and confusion.  This isn't theoreti=
cal, as it has happened in the past that working group chairs and area dire=
ctors in particular have derailed efforts, setting standardization and depl=
oyment of useful technology back years, and this wasn't that long ago.

Let's make this discussion concrete with a few examples: the implications m=
ay be that a working group chair or any participant (although chairs are in=
 a very good position to cause damage) could insist that DHCP not be used t=
o carry new attributes because there is no common understanding of the scop=
e of remediation that will be required.  Before certain ADs roll their eyes=
, the discussion gets derailed as follows:

>> I propose the following DHCP option to configure my new frob.
<< But DHCP is transmitted in the clear.  Please justify this decision.
(or worse) << and by the way here is my very heavy weight alternative that =
requires a valid cert chain
>> It's meant for the local wire.
<< But we don't know the scope of the attack.
...
...
>> Nevermind, I'll just use a vendor extension.  Goodbye.

Rinse and repeat with any other protocol that allows extensions.

It is fair to say that we should consider this threat at an architectural l=
evel.  It's fair (albeit a truism) that finding design flaws earlier in the=
 process rather than later is less costly (ENG-101).  Justification languag=
e like the above, however, is likely to actively impede the IETF, as these =
sorts of things have in the past.

Eliot

From jari.arkko@piuha.net  Sun Jan 19 05:04:01 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF061ADF26; Sun, 19 Jan 2014 05:04:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T53WdogRp6qs; Sun, 19 Jan 2014 05:03:59 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 73E2B1AD7C1; Sun, 19 Jan 2014 05:03:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C73232CC5F; Sun, 19 Jan 2014 15:03:43 +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 ywbBqCZpZdIN; Sun, 19 Jan 2014 15:03:43 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3441D2CC48; Sun, 19 Jan 2014 15:03:43 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [perpass] draft-farrell-perpass-attack architecture issue
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAPv4CP-1G3ff9SovQ5-puSbDhcznmLY2LDquNv+BCN9Xpk9trw@mail.gmail.com>
Date: Sun, 19 Jan 2014 15:03:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <00DB0CC4-5E6A-483C-8E18-B24526CAED71@piuha.net>
References: <52D43E69.6090001@cs.tcd.ie> <C19E19BF-B9A2-4EEB-8E77-DF0CAD548277@cisco.com> <CAPv4CP-1G3ff9SovQ5-puSbDhcznmLY2LDquNv+BCN9Xpk9trw@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: perpass <perpass@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 13:04:02 -0000

> The main problem is that: privacy issues are deeper than that, the
> question could be misunderstood without a larger context, and there's
> already a set of documents discussing most of that larger context (RFC
> 6973, the perpass problem statement draft, etc.).
>=20
> The Document Shepherd Write-Up currently doesn't reference security
> guidelines directly. Instead of asking a few specific questions in the
> shepherd's writeup as you suggest, consider adding the privacy/perpass
> docs to BCP 72 (which already includes RFC 3552) as they are approved,
> and then optionally add a question to the shepherd's writeup that
> refers to it, in order to emphasize the increased attention to the
> issue.

FWIW, I do not feel strongly about this topic but my personal opinion is =
that if we do something with the shepherd write-up, it should be on the =
general level outlined by Scott above. (But I think the documents =
themselves are more important than the write-ups. A few years down the =
road, I'm sure the reader like to know what the thinking on security was =
on such and such RFC. On any aspect of security, PM or otherwise. When =
there's something to say, of course, which isn't always.)

Jari


From stbryant@cisco.com  Sun Jan 19 10:17:38 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DACE41ACC80; Sun, 19 Jan 2014 10:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.039
X-Spam-Level: 
X-Spam-Status: No, score=-15.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2GzlSu0Gz0Mq; Sun, 19 Jan 2014 10:17:37 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 56CE61A1F76; Sun, 19 Jan 2014 10:17:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2582; q=dns/txt; s=iport; t=1390155444; x=1391365044; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=r2ZehbOMaAjDpohEXUIssEz5nwHUijh0u1iphl4Zvdk=; b=HA34Qi9c678pKgWW8ruoDji2YjgOMA3NJNVqaYsa/wA83h9DcZEHf/6k LQYAOHTpAyr3zwulI81XTdW0lBOuhOsAhL2Zla15FvGQFwD+M3lKz/UC6 jM4uicQSeUcIh2InjGGAJXnfKSlbtyRofM3Hb9GgCjONqg/4OQSgO35U7 k=;
X-IronPort-AV: E=Sophos;i="4.95,685,1384300800"; d="scan'208";a="298305467"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-7.cisco.com with ESMTP; 19 Jan 2014 18:17:24 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0JIHOhO010078 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jan 2014 18:17:24 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Sun, 19 Jan 2014 12:17:23 -0600
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: AQHPFI3E/nItobbHr0ey+uLOGq3uepqLWhMAgADCtgCAAD+Akg==
Date: Sun, 19 Jan 2014 18:17:22 +0000
Message-ID: <DAE99191-66E7-4C50-AF2B-24FDEE21EB7C@cisco.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net>, <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 18:17:39 -0000

I share these concern.

Stewart

Sent from my iPad

> On 19 Jan 2014, at 08:30, "Eliot Lear" <lear@cisco.com> wrote:
>=20
> Jari,
>=20
> I oppose changes made to the document in the last round as stated below. =
 If they remain, I would urge publication as Informational and not BCP:
>=20
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.
>=20
> In the fact of a lack of common understanding regarding the threat, this =
text can subject a working group to abuse and confusion.  This isn't theore=
tical, as it has happened in the past that working group chairs and area di=
rectors in particular have derailed efforts, setting standardization and de=
ployment of useful technology back years, and this wasn't that long ago.
>=20
> Let's make this discussion concrete with a few examples: the implications=
 may be that a working group chair or any participant (although chairs are =
in a very good position to cause damage) could insist that DHCP not be used=
 to carry new attributes because there is no common understanding of the sc=
ope of remediation that will be required.  Before certain ADs roll their ey=
es, the discussion gets derailed as follows:
>=20
> >> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative tha=
t requires a valid cert chain
> >> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
> >> Nevermind, I'll just use a vendor extension.  Goodbye.
>=20
> Rinse and repeat with any other protocol that allows extensions.
>=20
> It is fair to say that we should consider this threat at an architectural=
 level.  It's fair (albeit a truism) that finding design flaws earlier in t=
he process rather than later is less costly (ENG-101).  Justification langu=
age like the above, however, is likely to actively impede the IETF, as thes=
e sorts of things have in the past.
>=20
> Eliot

From adrian@olddog.co.uk  Sun Jan 19 10:51:44 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C09FF1ADF31 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 10:51:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOfgv3PMFw2h for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 10:51:43 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 297B81A1DFA for <ietf@ietf.org>; Sun, 19 Jan 2014 10:51:43 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0JIpSoJ023815; Sun, 19 Jan 2014 18:51:29 GMT
Received: from 950129200 (14.21.90.92.rev.sfr.net [92.90.21.14]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0JIpQWX023804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 19 Jan 2014 18:51:28 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com>
In-Reply-To: <20131216175534.1390.8446.idtracker@ietfa.amsl.com>
Subject: RE: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Date: Sun, 19 Jan 2014 18:51:30 -0000
Message-ID: <07d701cf1547$782166f0$686434d0$@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: AQGQWqUAg1FoaRx5MrXXqxtkR3Q4dpsJ2S8w
Content-Language: en-gb
X-TM-AS-MML: No
Cc: draft-housley-number-registries.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Jan 2014 18:51:45 -0000

Hi,

I was doing my telechat reviews for next Thursday and would have entered a
Discuss for his document but...

- there is no ballot
- the last call is still running

So here is my IETF last call review of this document :-)

Thanks,
Adrian

Section 2.1 says...

   Reservations of special-purpose AS Numbers are made through Internet
   Standards actions.

Section 2.2 says...

   Reservation of special-purpose IPv4 addresses are made through
   Internet Standards actions.

Section 2.3 says...

   Reservation of special-purpose IPv6 addresses are made through
   Internet Standards actions.

Section 3 says...

   "IETF Review" as defined in [RFC5226] is required to reserve special-
   purpose AS numbers, IPv4 addresses, or IPv6 addresses.

1. 2.1, 2.2, and 2.3 should have a reference to 5226
2. Section 3 contradicts 2.1, 2.2, and 2.3.
3. Why is Section 3 present since there are no instructions for IANA?



From stephen.farrell@cs.tcd.ie  Sun Jan 19 10:55:21 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1781ADF8A; Sun, 19 Jan 2014 10:55:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s_P8riCdnLxM; Sun, 19 Jan 2014 10:55:18 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 08FD51ADF84; Sun, 19 Jan 2014 10:55:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1363CBE24; Sun, 19 Jan 2014 18:54:58 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4+05lCTJm2z; Sun, 19 Jan 2014 18:54:56 +0000 (GMT)
Received: from [10.87.48.5] (unknown [86.46.27.208]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1B3C5BE25; Sun, 19 Jan 2014 18:54:54 +0000 (GMT)
Message-ID: <52DC1F71.80102@cs.tcd.ie>
Date: Sun, 19 Jan 2014 18:54:41 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>,  Scott Brim <scott.brim@gmail.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 18:55:21 -0000

On 01/19/2014 08:30 AM, Eliot Lear wrote:
> Jari,
> 
> I oppose changes made to the document in the last round as stated
> below.  If they remain, I would urge publication as Informational and
> not BCP:
> 
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.

I'm not particularly fussed if this is included or not. I'm ok with
Jari and/or the IESG figuring it out however they do.

> In the fact of a lack of common understanding regarding the threat, this
> text can subject a working group to abuse and confusion.  This isn't
> theoretical, as it has happened in the past that working group chairs
> and area directors in particular have derailed efforts, setting
> standardization and deployment of useful technology back years, and this
> wasn't that long ago.

To be honest that seems both overblown and unjustified to me.
I'm also entirely unconvinced by the example below and by your
analysis of how text that says nothing much new is somehow at
the same time horribly threatening. 'Abuse' and setting things
back years and the rest seem to me to bear no relationship to
the text in question. Best I can guess is that your fear of
over-zealous ADs causes you to read this text in some way that I
can't figure out, but that argument has been had already for
earlier text which seems to me entirely as strong as this text.

And that's why I included this in -04, it seemed to have support
from others and consideration of architecture is reasonable
and your objection is afaics nothing to do with the text itself
and hence invalid.

But as I said, I'm fine with this being resolved either way.

Cheers,
S.

> 
> Let's make this discussion concrete with a few examples: the
> implications may be that a working group chair or any participant
> (although chairs are in a very good position to cause damage) could
> insist that DHCP not be used to carry new attributes because there is no
> common understanding of the scope of remediation that will be required. 
> Before certain ADs roll their eyes, the discussion gets derailed as follows:
> 
>>> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative
> that requires a valid cert chain
>>> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
>>> Nevermind, I'll just use a vendor extension.  Goodbye.
> 
> Rinse and repeat with any other protocol that allows extensions.
> 
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.
> 
> Eliot
> 

From dhc@dcrocker.net  Sun Jan 19 11:48:16 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEAC1ADF78; Sun, 19 Jan 2014 11:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ppw2ixrsXhCn; Sun, 19 Jan 2014 11:48:14 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A39231ADF31; Sun, 19 Jan 2014 11:48:14 -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 s0JJlhYQ023839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 19 Jan 2014 11:47:46 -0800
Message-ID: <52DC2BD0.4000803@dcrocker.net>
Date: Sun, 19 Jan 2014 11:47:28 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
Subject: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 19 Jan 2014 11:47:47 -0800 (PST)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Jan 2014 19:48:16 -0000

On 1/19/2014 12:30 AM, Eliot Lear wrote:
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.


If I'm understanding this exchange, it hinges on the distinction between 
due consideration vs. appropriate design response.

Pressing to have work "consider" an issue early and thoughtfully makes 
sense for any topic that is as important as pervasive monitoring. 
Having IESG evaluation produce a blocking Discuss because an AD feels 
that the consideration was not sufficient or the resulting design flawed 
in terms of this issue is another matter.

The point I'm seeing Eliot make is that we don't have enough community 
understanding of the topic to be sure what constitutes appropriate 
design consideration.  So, in the face of such minimal community 
understanding, an AD's blocking progress would be whimsical at best.

Based on how new this topic is -- we don't even yet have stable and 
shared terminology for the problem space nor the solution space -- 
Eliot's concern isn't just valid, it's important.

We /do/ have a long track record of well-intentioned ADs asserting 
Discusses that are reasonable in the abstract but impractical for work 
in the IETF, especially when the topic is frankly still vague.

While the formal status of this document is relevant to the concern, the 
more important issue I see is our community sense that work going 
forward needs serious effort, but also an understanding that the basis 
for blocking specification needs to be extremely cautiously applied.

By way of trying to be practical about being practical, I'll suggest 
that any IESG blocks based on a concern about pervasive monitoring needs 
to reflect a consensus view of the IESG, not just the concern of a 
single AD....

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From jari.arkko@piuha.net  Sun Jan 19 13:21:36 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35561ADF96 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 13:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.038
X-Spam-Level: 
X-Spam-Status: No, score=-1.038 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtapEnww2AJT for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 13:21:33 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 826431ADF94 for <ietf@ietf.org>; Sun, 19 Jan 2014 13:21:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BEBC22CCC1; Sun, 19 Jan 2014 23:21:19 +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 nB01WPU0X_pv; Sun, 19 Jan 2014 23:21:19 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E71AF2CC48; Sun, 19 Jan 2014 23:21:18 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52DC2BD0.4000803@dcrocker.net>
Date: Sun, 19 Jan 2014 23:21:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1510)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 21:21:36 -0000

Thanks for this, Dave.=20

Here are some thoughts from my perspective. I'm not sure I agree that =
we've seen pattern of "well-intentioned but impractical" blocking =
Discusses from the IESG, but I think we've seen some cases. I know I =
have erred at times :-) But I think both the IETF and even me have =
learned over the years to do this a bit better. And we need to continue =
to watch for this, or perhaps even come up with better processes to =
defend against it.

I'd like to separate this phenomena a bit from the current draft, =
however. The basic problem is that the discuss criteria [1] that the =
IESG currently lives by states technical flaws are a valid reason for a =
Discuss. And that "technical flaw" isn't defined in any manner. It is =
not limited to BCP guidance, for instance. And even when there is a BCP, =
it almost never the case that there are rules that can be followed =
blindly. Unfortunately, the beauty (or flaw) is in the eye of the =
beholder. The raised concerned can range from ridiculous to Internet =
damaging. Say, from trivial design choices to totally missing congestion =
control in a situation where it would have been necessary. It is =
difficult to devise hard rules about what constitutes a flaw and a valid =
Discuss. And if it were possible, I'd have some more work for Henrik and =
a quick IESG re-org in the works :-) For now, we are stuck with using =
good judgement. Take that congestion control example - we often have to =
figure out if a particular concern applies in a specific setting. =
Congestion. Or security - not all security functions are relevant at all =
layers, for instance. And people might not agree where a specific case =
belongs to. One person may think a change was uncalled for where another =
might think it was crucial for the operation of the Internet.

And when there is an argument, the way we pretty much have to deal with =
these cases is through (1) discussion (2) community consensus and (3) =
complaints, appeals, nomcom, and recalls if nothing else helps.

FWIW, independent of this discussion I have personally reached the =
conclusion that the IETF needs to be more careful about anyone's =
personal opinion affecting the outcome. No one's personal preference =
should prevent informed consensus opinion from going forward. The first =
two items in the discuss non-criteria list are related to this, but =
could perhaps be stronger (they have some caveats). My recommended =
process for discussing something that IETF has informed consensus over =
is to take it up with the IETF and see what consensus comes out of it, =
rather than (say) an AD saying we need to do this or else.

Jari

[1] http://www.ietf.org/iesg/statement/discuss-criteria.html


From l.wood@surrey.ac.uk  Sun Jan 19 13:34:51 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3A581ADF96; Sun, 19 Jan 2014 13:34:51 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWwr4ArznaNa; Sun, 19 Jan 2014 13:34:48 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id D74501ADF92; Sun, 19 Jan 2014 13:34:47 -0800 (PST)
Received: from [195.245.230.131:63330] by server-2.bemta-3.messagelabs.com id B0/A7-17329-8E44CD25; Sun, 19 Jan 2014 21:34:32 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-78.messagelabs.com!1390167270!33925865!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29620 invoked from network); 19 Jan 2014 21:34:30 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-5.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 19 Jan 2014 21:34:30 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sun, 19 Jan 2014 21:34:29 +0000
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <lear@cisco.com>, <jari.arkko@piuha.net>, <scott.brim@gmail.com>
Date: Sun, 19 Jan 2014 21:34:28 +0000
Subject: RE: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: Ac8VSApEqInOZnNTRByucu6FJ5deEQAFBss1
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D4@EXMB01CMS.surrey.ac.uk>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>,<52DC1F71.80102@cs.tcd.ie>
In-Reply-To: <52DC1F71.80102@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: gen-art@ietf.org, ietf@ietf.org, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jan 2014 21:34:51 -0000

>> In the fact of a lack of common understanding regarding the threat, this
>> text can subject a working group to abuse and confusion.  This isn't
>> theoretical, as it has happened in the past that working group chairs
>> and area directors in particular have derailed efforts, setting
>> standardization and deployment of useful technology back years, and this
>> wasn't that long ago.

> To be honest that seems both overblown and unjustified to me.
> I'm also entirely unconvinced by the example below and by your
> analysis of how text that says nothing much new is somehow at
> the same time horribly threatening. 'Abuse' and setting things
> back years and the rest seem to me to bear no relationship to
> the text in question.

Stephen,

you might recall interrupting a couple of early presentations we
made on Saratoga to raise a (in hindsight pretty much spurious
and irrelevant) security issue. We could see that you would block
any further work there, and we moved Saratoga away from DTNRG.

DTNRG has since produced a security protocol, rather than
exploring the DTN problem space. It has, in my opinion, set
DTN research back years. DTNRG considered security at
every point.

I view this as an early example of Eliot's doubts.
If you'd had this document then, you'd be pointing at that as well.

The concern is justified. Raise the 'but it's not secure! It's
snoopable!' cry too much, and watch work either die in process,
or leave the IETF.

(Perpass still isn't a working group, is it?)

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 19 January 2014 18:54
To: Eliot Lear; Jari Arkko; Scott Brim
Cc: gen-art; IETF discussion list; draft-farrell-perpass-attack.all@tools.i=
etf.org
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04

On 01/19/2014 08:30 AM, Eliot Lear wrote:
> Jari,
>
> I oppose changes made to the document in the last round as stated
> below.  If they remain, I would urge publication as Informational and
> not BCP:
>
>>    In particular, architectural decisions, including which existing
>>    technology is re-used, may significantly impact the vulnerability of
>>    a protocol to PM.  Those developing IETF specifications therefore
>>    need to consider mitigating PM when making these architectural
>>    decisions and be prepared to justify their decisions.  Getting
>>    adequate, early review of architectural decisions including whether
>>    appropriate mitigation of PM can be made is important.  Revisiting
>>    these architectural decisions late in the process is very costly.

I'm not particularly fussed if this is included or not. I'm ok with
Jari and/or the IESG figuring it out however they do.

> In the fact of a lack of common understanding regarding the threat, this
> text can subject a working group to abuse and confusion.  This isn't
> theoretical, as it has happened in the past that working group chairs
> and area directors in particular have derailed efforts, setting
> standardization and deployment of useful technology back years, and this
> wasn't that long ago.

To be honest that seems both overblown and unjustified to me.
I'm also entirely unconvinced by the example below and by your
analysis of how text that says nothing much new is somehow at
the same time horribly threatening. 'Abuse' and setting things
back years and the rest seem to me to bear no relationship to
the text in question. Best I can guess is that your fear of
over-zealous ADs causes you to read this text in some way that I
can't figure out, but that argument has been had already for
earlier text which seems to me entirely as strong as this text.

And that's why I included this in -04, it seemed to have support
from others and consideration of architecture is reasonable
and your objection is afaics nothing to do with the text itself
and hence invalid.

But as I said, I'm fine with this being resolved either way.

Cheers,
S.

>
> Let's make this discussion concrete with a few examples: the
> implications may be that a working group chair or any participant
> (although chairs are in a very good position to cause damage) could
> insist that DHCP not be used to carry new attributes because there is no
> common understanding of the scope of remediation that will be required.
> Before certain ADs roll their eyes, the discussion gets derailed as follo=
ws:
>
>>> I propose the following DHCP option to configure my new frob.
> << But DHCP is transmitted in the clear.  Please justify this decision.
> (or worse) << and by the way here is my very heavy weight alternative
> that requires a valid cert chain
>>> It's meant for the local wire.
> << But we don't know the scope of the attack.
> ...
> ...
>>> Nevermind, I'll just use a vendor extension.  Goodbye.
>
> Rinse and repeat with any other protocol that allows extensions.
>
> It is fair to say that we should consider this threat at an
> architectural level.  It's fair (albeit a truism) that finding design
> flaws earlier in the process rather than later is less costly
> (ENG-101).  Justification language like the above, however, is likely to
> actively impede the IETF, as these sorts of things have in the past.
>
> Eliot
>

From huitema@microsoft.com  Sun Jan 19 16:49:32 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1CD21A0013; Sun, 19 Jan 2014 16:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.701
X-Spam-Level: 
X-Spam-Status: No, score=-0.701 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vdlQayAmpYgP; Sun, 19 Jan 2014 16:49:30 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id 5869E1A000D; Sun, 19 Jan 2014 16:49:30 -0800 (PST)
Received: from DM2PR03CA008.namprd03.prod.outlook.com (10.141.52.156) by BN1PR03MB236.namprd03.prod.outlook.com (10.255.200.28) with Microsoft SMTP Server (TLS) id 15.0.847.13; Mon, 20 Jan 2014 00:49:24 +0000
Received: from BY2FFO11FD044.protection.gbl (2a01:111:f400:7c0c::161) by DM2PR03CA008.outlook.office365.com (2a01:111:e400:2414::28) with Microsoft SMTP Server (TLS) id 15.0.847.13 via Frontend Transport; Mon, 20 Jan 2014 00:49:23 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD044.mail.protection.outlook.com (10.1.14.229) with Microsoft SMTP Server (TLS) id 15.0.847.12 via Frontend Transport; Mon, 20 Jan 2014 00:49:23 +0000
Received: from TK5EX14MBXC303.redmond.corp.microsoft.com ([169.254.3.123]) by TK5EX14MLTC102.redmond.corp.microsoft.com ([157.54.79.180]) with mapi id 14.03.0174.002; Mon, 20 Jan 2014 00:48:52 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>, Scott Brim <scott.brim@gmail.com>
Subject: RE: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: AQHPFI3ZW+Ddq54mlkqF92wuCJ/egpqK9X4AgADCtgCAAQvBAA==
Date: Mon, 20 Jan 2014 00:48:50 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA360668B6@TK5EX14MBXC303.redmond.corp.microsoft.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com>
In-Reply-To: <52DB8D0E.8000708@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.36]
Content-Type: multipart/alternative; boundary="_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_"
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(199002)(189002)(20776003)(44976005)(65816001)(63696002)(83322001)(6806004)(85306002)(66066001)(15975445006)(74366001)(74662001)(19580395003)(93136001)(74502001)(86362001)(53806001)(512874002)(93516002)(31966008)(47446002)(92566001)(74876001)(50986001)(77096001)(77982001)(47736001)(81342001)(2656002)(80022001)(51856001)(59766001)(19300405004)(79102001)(56816005)(74706001)(81686001)(76796001)(85852003)(90146001)(33656001)(87936001)(76482001)(69226001)(56776001)(54316002)(15202345003)(81542001)(81816001)(83072002)(71186001)(84326002)(4396001)(49866001)(87266001)(55846006)(54356001)(92726001)(46102001)(16236675002)(47976001)(80976001)(76786001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN1PR03MB236; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; RD:InfoDomainNonexistent; A:1; MX:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 00979FCB3A
X-OriginatorOrg: microsoft.com
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 00:49:33 -0000

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

Pj4gTmV2ZXJtaW5kLCBJJ2xsIGp1c3QgdXNlIGEgdmVuZG9yIGV4dGVuc2lvbi4gIEdvb2RieWUu
DQoNCj4gUmluc2UgYW5kIHJlcGVhdCB3aXRoIGFueSBvdGhlciBwcm90b2NvbCB0aGF0IGFsbG93
cyBleHRlbnNpb25zLg0KDQpUaGF04oCZcyBhIHZlcnkgcHJhY3RpY2FsIGNvbmNlcm4uIElmIHN0
YW5kYXJkIHNvbHV0aW9ucyBhcmUgdG9vIGhhcmQgdG8gZGV2ZWxvcCwgdGhlbiBwcm9kdWN0cyB3
aWxsIHVzZSBwcm9wcmlldGFyeSBzb2x1dGlvbnMgaW5zdGVhZCwgYW5kIHdlIHdpbGwgbm90IGhh
dmUgd29uIG11Y2ggZGVmZW5zZSBhZ2FpbnN0IHBlcnZhc2l2ZSBtb25pdG9yaW5nLg0KDQpJIHBl
cnNvbmFsbHkgYWdyZWUgd2l0aCB0aGUgZ2VuZXJhbCBpZGVhIHRoYXQgbmV3IGRldmVsb3BtZW50
cyBzaG91bGQgY29uc2lkZXIgUE0gYXMgcGFydCBvZiB0aGUgdGhyZWF0IG1vZGVsLiBCdXQgRWxs
aW90IG1ha2VzIGEgZ29vZCBwb2ludC4gSW4gcHJhY3RpY2UsIHRoZSBnb29kIHJldmlld3MgZG9u
4oCZdCBzdG9wIGF0IG5lZ2F0aXZlIGFkdmljZSwg4oCcZG9u4oCZdCBkbyB0aGlzIGJlY2F1c2Ug
dGhlIHNwb29rcyB3aWxsIHNub29wLuKAnSBUaGUgYmV0dGVyIHJldmlld3MgZ28gb24gd2l0aCDi
gJxkbyB0aGlzIGluc3RlYWQsIGl0IGlzIGFsbW9zdCBhcyBlYXN5IHRvIHVzZSBhbmQgaXQgcHJv
dmlkZXMgbXVjaCBiZXR0ZXIgcHJpdmFjeS7igJ0NCg0KSXQgd291bGQgYmUgaW50ZXJlc3Rpbmcg
dG8gbGlzdCB0aGUgc3BlY2lmaWMgcGF0dGVybnMgdGhhdCBhcmUgbW9zdCBsaWtlbHkgdG8gdHJp
Z2dlciB0aGUg4oCcYmFkIGJlY2F1c2Ugb2YgUE3igJ0gY29tbWVudHMsIGFuZCB0byBkZXZlbG9w
IHNlY3VyZSBhbHRlcm5hdGl2ZXMuIEZyb20gd2hhdCBJIHNlZSwgdGhlcmUgc2VlbXMgdG8gYmUg
dHdvIGJpZyBvZmZlbmRlcnMsIGxvZ3MgYW5kIGNvbmZpZ3VyYXRpb24uIFNvIG1heWJlIHdlIHNo
b3VsZCBkZXZlbG9wIGEgc2ltcGxlIHdheSB0byBhbm9ueW1pemUgbG9ncywgYW5kIGEgc2VjdXJl
IHdheSB0byBnZXQgY29uZmlndXJhdGlvbiBkYXRh4oCmDQoNCi0tIENocmlzdGlhbiBIdWl0ZW1h
DQoNCg0K

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7DQoJY29sb3I6YmxhY2s7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGlu
aw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIg
TmV3IjsNCgljb2xvcjpibGFjazt9DQpzcGFuLkhUTUxQcmVmb3JtYXR0ZWRDaGFyDQoJe21zby1z
dHlsZS1uYW1lOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIjsNCglmb250LWZhbWlseTpD
b25zb2xhczsNCgljb2xvcjpibGFjazt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUt
dHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYi
Ow0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEw
MjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAv
Pg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgYmdj
b2xvcj0id2hpdGUiIGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZn
dDsgTmV2ZXJtaW5kLCBJJ2xsIGp1c3QgdXNlIGEgdmVuZG9yIGV4dGVuc2lvbi4mbmJzcDsgR29v
ZGJ5ZS48YnI+DQo8YnI+DQo8c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+Jmd0OyA8L3NwYW4+
Umluc2UgYW5kIHJlcGVhdCB3aXRoIGFueSBvdGhlciBwcm90b2NvbCB0aGF0IGFsbG93cyBleHRl
bnNpb25zLjxicj4NCjxicj4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlRoYXTigJlzIGEgdmVy
eSBwcmFjdGljYWwgY29uY2Vybi4gSWYgc3RhbmRhcmQgc29sdXRpb25zIGFyZSB0b28gaGFyZCB0
byBkZXZlbG9wLCB0aGVuIHByb2R1Y3RzIHdpbGwgdXNlIHByb3ByaWV0YXJ5IHNvbHV0aW9ucyBp
bnN0ZWFkLCBhbmQgd2Ugd2lsbCBub3QgaGF2ZSB3b24NCiBtdWNoIGRlZmVuc2UgYWdhaW5zdCBw
ZXJ2YXNpdmUgbW9uaXRvcmluZy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgcGVyc29uYWxseSBhZ3JlZSB3aXRoIHRo
ZSBnZW5lcmFsIGlkZWEgdGhhdCBuZXcgZGV2ZWxvcG1lbnRzIHNob3VsZCBjb25zaWRlciBQTSBh
cyBwYXJ0IG9mIHRoZSB0aHJlYXQgbW9kZWwuIEJ1dCBFbGxpb3QgbWFrZXMgYSBnb29kIHBvaW50
LiBJbiBwcmFjdGljZSwgdGhlDQogZ29vZCByZXZpZXdzIGRvbuKAmXQgc3RvcCBhdCBuZWdhdGl2
ZSBhZHZpY2UsIOKAnGRvbuKAmXQgZG8gdGhpcyBiZWNhdXNlIHRoZSBzcG9va3Mgd2lsbCBzbm9v
cC7igJ0gVGhlIGJldHRlciByZXZpZXdzIGdvIG9uIHdpdGgg4oCcZG8gdGhpcyBpbnN0ZWFkLCBp
dCBpcyBhbG1vc3QgYXMgZWFzeSB0byB1c2UgYW5kIGl0IHByb3ZpZGVzIG11Y2ggYmV0dGVyIHBy
aXZhY3ku4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj5JdCB3b3VsZCBiZSBpbnRlcmVzdGluZyB0byBsaXN0IHRoZSBz
cGVjaWZpYyBwYXR0ZXJucyB0aGF0IGFyZSBtb3N0IGxpa2VseSB0byB0cmlnZ2VyIHRoZSDigJxi
YWQgYmVjYXVzZSBvZiBQTeKAnSBjb21tZW50cywgYW5kIHRvIGRldmVsb3Agc2VjdXJlIGFsdGVy
bmF0aXZlcy4NCiBGcm9tIHdoYXQgSSBzZWUsIHRoZXJlIHNlZW1zIHRvIGJlIHR3byBiaWcgb2Zm
ZW5kZXJzLCBsb2dzIGFuZCBjb25maWd1cmF0aW9uLiBTbyBtYXliZSB3ZSBzaG91bGQgZGV2ZWxv
cCBhIHNpbXBsZSB3YXkgdG8gYW5vbnltaXplIGxvZ3MsIGFuZCBhIHNlY3VyZSB3YXkgdG8gZ2V0
IGNvbmZpZ3VyYXRpb24gZGF0YeKApjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RDttc28tbGlnYXR1cmVzOnN0YW5kYXJkIj4t
LSBDaHJpc3RpYW4gSHVpdGVtYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_C91E67751B1EFF41B857DE2FE1F68ABA360668B6TK5EX14MBXC303r_--

From dhc@dcrocker.net  Sun Jan 19 16:56:27 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDAD1A000B for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 16:56:27 -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=[RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hqWsHkoZSYB4 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 16:56:26 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 667D61A0002 for <ietf@ietf.org>; Sun, 19 Jan 2014 16:56:26 -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 s0K0uMov028575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 19 Jan 2014 16:56:25 -0800
Message-ID: <52DC7429.7090006@dcrocker.net>
Date: Sun, 19 Jan 2014 16:56:09 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>, Eliot Lear <lear@cisco.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <C91E67751B1EFF41B857DE2FE1F68ABA360668B6@TK5EX14MBXC303.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA360668B6@TK5EX14MBXC303.redmond.corp.microsoft.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 19 Jan 2014 16:56:25 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 20 Jan 2014 00:56:27 -0000

On 1/19/2014 4:48 PM, Christian Huitema wrote:
> It would be interesting to list the specific patterns that are most
> likely to trigger the â€œbad because of PMâ€� comments, and to develop
> secure alternatives. From what I see, there seems to be two big
> offenders, logs and configuration. So maybe we should develop a simple
> way to anonymize logs, and a secure way to get configuration dataâ€¦


What an excellent point.  It highlights something we probably should 
pursue explicitly and aggressively:

    1.  Working on learning how to analyze PM concerns in specifications

    2.  Learning how to formulate PM defenses in designs

    3.  Diligently documenting what we learn

That is, we need to treat this topic as something we are all still 
developing an understanding of -- both the problem and its mitigation -- 
and therefore need to collaborate on.

Methinks these are two wikis we need...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From david.black@emc.com  Sun Jan 19 18:05:39 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883001A001E; Sun, 19 Jan 2014 18:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level: 
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCr5801aPxP3; Sun, 19 Jan 2014 18:05:36 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6FDF01A001A; Sun, 19 Jan 2014 18:05:36 -0800 (PST)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0K25Yvd013480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Jan 2014 21:05:35 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0K25Yvd013480
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390183536; bh=RlIwaCgcxaZAAgGUNUG0/bsXwdg=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=kjDFS9hXrOaoVRMkgd+XTBj1cM+o3H5Em63KeflvEAwr2o/uKz84mpaIXd1yzjJJs 7GxakTfNr4TmS7TRhYoxC6SvEK2N+ysrYGH1RjtH1EexR5A2SB7FUTLM9phG3Vs38j Rje0bWRUoeMtJArd9Kb+BGe5bVlOKajFrzs7Vutw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s0K25Yvd013480
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd53.lss.emc.com (RSA Interceptor); Sun, 19 Jan 2014 21:05:20 -0500
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0K25Jvf016830 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jan 2014 21:05:20 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Sun, 19 Jan 2014 21:05:19 -0500
From: "Black, David" <david.black@emc.com>
To: "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Date: Sun, 19 Jan 2014 21:05:17 -0500
Subject: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Topic: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Index: Ac8VhBCUJhyyOavTS8qcK8r/6tq29Q==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Cc: "draft-ietf-mpls-multipath-use.all@tools.ietf.org" <draft-ietf-mpls-multipath-use.all@tools.ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 02:05:39 -0000

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

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

I apologize for this review showing up a couple of days after the end of
IETF Last Call.

This draft discusses considerations for what are effectively MPLS-in-MPLS
tunnels for multipathing - an LSP carries another LSP, with the inner
(client) LSPs being distributed across multiple outer (server) LSPs that
use different paths.  This draft is motivated by considerations specific
to MPLS-TP that complicate multipathing when one of the two MPLS instances
is MPLS-TP.

I consider the following to be open issues that need attention (each
letter is used to tag the issue in the text that follows - [B] occurs
multiple times, as there are multiple aspect to that issue):

[A] Summary text in Introduction appears to be wrong.
[B] Section 3.2 needs a summary.
[C] Entropy label "sandwich" seems peculiar and at least needs an explanati=
on.
[D] Discussion of multipath impacts on MPLS OAM should be added to Section =
4.

--- Comments on draft text

[A] Section 1 (Introduction) 2nd paragraph:

   RFC 5654 requirement 33 requires the capability to carry a client
   MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC5654].
   This is possible in all cases with one exception.  When an MPLS LSP
   exceeds the capacity of any single component link it MAY be carried
   by a network using multipath techniques, but MAY NOT be carried by a
   single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
   imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
   fate sharing constraints and MPLS-TP LM OAM packet ordering
   constraints (see Section 3.1).

Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
exception appears to concern the reverse, and Section 4 on carrying MPLS
over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
Was the exception intended to be for an MPLS-TP LSP that exceeds the
capacity of any single component link?

Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's equivalent
to "MAY OR MAY NOT").  I think "cannot" was intended her, but "MUST NOT"
is another possibility.

[B] Section 3.2 contains a lot of useful details, but it could really use
a summary at the end on the options and recommendations for meeting the
four requirements (this summary could be a new Section 3.3).  It's a bit
difficult to discern what's going on, as I had to read this section more
than once in order to discern the following:

[C] In Section 3.2, use of an MPLS entropy label to meet requirement MP#1
requires that it be "below the MPLS-TP label" whereas, to meet requirement
MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LSP label"=
.
This combination appears to suggest "sandwiching" the MPLS-TP label between
two entropy labels that effectively carry the same information (albeit,
applied and removed at different places in the network) - was that intended=
?
This is important, as there seems to be no reasonable alternative
to the entropy label for meeting requirement MP#2, and the draft's
alternative to the entropy label for meeting requirement MP#1 is "some form
of configuration" - the entropy label would seem to be preferred to that
based on my reading of this draft and the comment in RFC 5706 section 2.2
that "Anything that can be configured can be misconfigured."

[B] A summary of requirements for implementation and deployment at the end
of Section 3.2 would have made this much more obvious.  That should be
provided in addition to addressing the above question about duplicate use
of the MPLS entropy label.

--- Relevant Q&A based on RFC 5706 Appendix A

I'm omitting management concerns, as both MPLS and MPLS-TP have extensive
management infrastructure, and this draft's notion of stacking LSPs so
that one instance of MPLS (or MPLS-TP) can be a server to (i.e., carry)
another is not novel to this draft.

A.1.1.  Has deployment been discussed?

[B] Yes, although Section 3.2 is weak on deployment requirements (some of
which are implementation requirements) and could use a summary.

A.1.2.  Has installation and initial setup been discussed?

No, although because this draft reuses existing functionality in different
configurations, this really reduces to the A.1.9 configuration question
below.  In practice, quite a bit of operator knowledge and insight is
required to get initial setup right, e.g., as traffic engineering LSPs to
avoid congestion problems (needed to meet requirement MP#3) requires
significant knowledge of network structure and expected traffic flows.
This should be obvious to anyone who works w/MPLS, but it's probably
worth stating for completeness.

A.1.6.  Have suggestions for verifying correct operation been discussed?

Yes and no.  Section 3.2 discusses OAM, and contains this important
requirement for OAM traffic:

   An Entropy Label must be used to insure that all of the
   MPLS-TP payload and OAM traffic are carried on the same component,
   except during very infrequent transitions due to load balancing.

[D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
Section 4; that should be added.

A.1.9.  Is configuration discussed?

[B] Not much. Configuration is required to meet requirements MP#3 and MP#4,
and is one of the options for MP#1.  A summary of what has to be configured
as part of the summary at the end of Section 3.2 would be a good idea.

A.2.* [skipped, see above]

A.3 Documentation

There's quite a bit of operational material contained in this draft; a
separate section on operations and management considerations would not
be appropriate.

There is a useful implementation status section which appears to imply
that MPLS-TP over MPLS is not currently deployable due to absence of
entropy label support, and because deployed MPLS equipment does not
generally support multipathing.  Nonetheless, data center experience
indicates significant value and widespread use of multipathing based
on link aggregation and ECMP; corresponding benefits can be expected
for use of multipathing in the Internet beyond data centers.

--- Editorial comments/nits:

- Section 3.1, after RFC 5960 quotes:

   [RFC5960] paragraph 3 requires that packets within a specific ordered

Insert "Section 3.1.1., before "paragraph 3" and likewise for "paragraph 6"
later in the same paragraph in the draft.

- Section 3.2, requirement MP#3:

   MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not be

"insure" -> "ensure" or "assure".  Surely this draft does not envision
operators taking out insurance policies on MPLS TP LSP behavior ;-).

- Section 3.2, last paragraph on p.8:

   An MPLS-TP LSP may not traverse multipath links on the path where
   MPLS-TP forwarding requirements cannot be met.

"may not" is meaningless - I believe "MUST NOT" was intended here.

- Section 4, middle of 3rd para:

Editorial suggestions for clarity:

OLD
            For those LSP that are larger than component link
    capacity, their capacity are not integer multiples of convenient
    capacity increments such as 10Gb/s.
NEW
            For those LSPs that are larger than a component link
   capacity, the LSP capacities need not be (and often are not)
   integer multiples of convenient capacity increments such as 10Gb/s.

In particular, "are not" seems wrong, as the "integer multiples"
case is possible, so I changed "are not" to "need not be (and often
are not)" in the suggested new text.

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


From l.wood@surrey.ac.uk  Sun Jan 19 18:35:53 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D291A0026 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 18:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XI-ctHa1oe4m for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 18:35:51 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id B4E0F1A001F for <ietf@ietf.org>; Sun, 19 Jan 2014 18:35:50 -0800 (PST)
Received: from [85.158.136.51:10997] by server-1.bemta-5.messagelabs.com id 88/EF-21065-68B8CD25; Mon, 20 Jan 2014 02:35:50 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-49.messagelabs.com!1390185349!23753970!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9516 invoked from network); 20 Jan 2014 02:35:49 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-4.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 20 Jan 2014 02:35:49 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 20 Jan 2014 02:35:49 +0000
From: <l.wood@surrey.ac.uk>
To: <dcrocker@bbiw.net>, <huitema@microsoft.com>, <lear@cisco.com>, <jari.arkko@piuha.net>
Date: Mon, 20 Jan 2014 02:35:22 +0000
Subject: RE: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: Ac8VfCdABJ7oR/IVR7y3yNqg5L5Y6AADB1sU
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D5@EXMB01CMS.surrey.ac.uk>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <C91E67751B1EFF41B857DE2FE1F68ABA360668B6@TK5EX14MBXC303.redmond.corp.microsoft.com>, <52DC7429.7090006@dcrocker.net>
In-Reply-To: <52DC7429.7090006@dcrocker.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 02:35:53 -0000

And when you can answer those three points, you'll have a BCP.

Until then, this is informational.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Dave Crocker [dhc@dcrocker.=
net]
Sent: 20 January 2014 00:56
To: Christian Huitema; Eliot Lear; Jari Arkko
Cc: IETF discussion list
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04

On 1/19/2014 4:48 PM, Christian Huitema wrote:
> It would be interesting to list the specific patterns that are most
> likely to trigger the =93bad because of PM=94 comments, and to develop
> secure alternatives. From what I see, there seems to be two big
> offenders, logs and configuration. So maybe we should develop a simple
> way to anonymize logs, and a secure way to get configuration data=85


What an excellent point.  It highlights something we probably should
pursue explicitly and aggressively:

    1.  Working on learning how to analyze PM concerns in specifications

    2.  Learning how to formulate PM defenses in designs

    3.  Diligently documenting what we learn

That is, we need to treat this topic as something we are all still
developing an understanding of -- both the problem and its mitigation --
and therefore need to collaborate on.

Methinks these are two wikis we need...

d/

--
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From david.black@emc.com  Sun Jan 19 19:30:38 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 531511A0023; Sun, 19 Jan 2014 19:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.164
X-Spam-Level: 
X-Spam-Status: No, score=0.164 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JfuNn8B0eEV; Sun, 19 Jan 2014 19:30:35 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 77D8A1A001F; Sun, 19 Jan 2014 19:30:35 -0800 (PST)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0K3USCQ012964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Jan 2014 22:30:31 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s0K3USCQ012964
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390188631; bh=ghRaPwbG9paVbA4AQIMVTuwKqco=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=tl47hZk9YoCepxFBFavWk7ql6RN9J666YJF4VhgMuVTogAFfEe67v3ccxw2rTXGzd GwNLpF7s1BboR9aGRGmTvGvjxvRRSw6aVaRMxxEmr/+lAlj/3GyPFlsUyYgvpNIfsR 1OC/6AscMgshcMP6RB6VUNgLq/OlcOJ5r9aLbFVw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s0K3USCQ012964
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd53.lss.emc.com (RSA Interceptor); Sun, 19 Jan 2014 22:30:13 -0500
Received: from mxhub04.corp.emc.com (mxhub04.corp.emc.com [10.254.141.106]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0K3UACp011719 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 19 Jan 2014 22:30:12 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub04.corp.emc.com ([10.254.141.106]) with mapi; Sun, 19 Jan 2014 22:30:10 -0500
From: "Black, David" <david.black@emc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Sun, 19 Jan 2014 22:30:08 -0500
Subject: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Topic: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Index: Ac8Vj+sUxkixdvZlQDyGimrIKN8dNQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F047824@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Cc: "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "Black, David" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 03:30:38 -0000

Sasha,

> But I would like to understand whether this protocol can really result in
> reasonable distribution of traffic. "Reasonable" means that (a) there is
> sufficient entropy and (b) that the order in specific micro-flows is
> preserved. The draft skips this issue (unless you consider a recommendati=
on to
> use a fixed  randomly selected source port value if the tunnel does not n=
eed
> ECMP a valid answer) .

Well, there's a bit more in the draft than just a "randomly selected" value=
,
as the ability to use ECMP on these tunnels is rather important (text quote=
d
is from Section 3 in the draft):

   The ingress device SHOULD set
   the UDP source port based on flow invariant fields from the payload
   header, otherwise it should be set to a randomly selected constant
   value, e.g. zero, to avoid packet flow reordering.  How a tunnel
   ingress generates entropy from the payload is outside the scope of
   this document.

I suppose that more discussion and examples of "flow invariant fields"
would be useful, although an attempt at a comprehensive listing would be
pointless, IMHO.  An important situation is one where the tunnel ingress
"knows" (because the network operator actually does know) what the protocol
stack(s) is/are for the encapsulated traffic (e.g., HTTP/TCP/IP/GRE/IP) and
hence can find the flow-invariant fields that it wants to use for that
(those) specific stack(s).

With good selection of flow-invariant fields wrt traffic mix, good
distribution is possible.

Thanks,
--David

> -----Original Message-----
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Alexander Vainsh=
tein
> Sent: Wednesday, January 15, 2014 6:54 AM
> To: stbryant@cisco.com
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; R=
andy
> Bush; jnc@mit.edu; lisp@ietf.org
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gr=
e-in-
> udp draft (was: RE: Milestones changed for tsvwg WG))
>=20
> Stewart, and all,
> I fully agree that UDP checksums is not a real-life issue with the protoc=
ol in
> question. They could probably help to check corrupted packets if corrupti=
on
> happens when a packet passes thru a router (i.e. when the ingress data li=
nk
> FCS has already been terminated and the egress data link FCS has not been
> generated yet). But this is hopefully rare - and since MPLS does not care
> about it, why should the MPLS encapsulator care?
>=20
> I also do not think that congestion control is a serious issue for this
> protocol, not in the least because the primary purpose of this protocol i=
s
> ECMP.
>=20
> But I would like to understand whether this protocol can really result in
> reasonable distribution of traffic. "Reasonable" means that (a) there is
> sufficient entropy and (b) that the order in specific micro-flows is
> preserved. The draft skips this issue (unless you consider a recommendati=
on to
> use a fixed  randomly selected source port value if the tunnel does not n=
eed
> ECMP a valid answer) .
>=20
> Any ideas as to how reasonable distribution of traffic  can be achieved w=
ith
> this protocol?
>=20
> Regards,
>        Sasha
> Email: Alexander.Vainshtein@ecitele.com
> Mobile: 054-9266302
>=20
> > -----Original Message-----
> > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Stewart Bryant
> > Sent: Wednesday, January 15, 2014 1:31 PM
> > To: Randy Bush
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org;
> > wes@mti-systems.com; tsvwg@ietf.org; jnc@mit.edu
> > Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: =
gre-
> in-
> > udp draft (was: RE: Milestones changed for tsvwg WG))
> >
> > On 15/01/2014 11:08, Randy Bush wrote:
> > > [ you insist on cc:ing me, so you get to endure my opinions ]
> > >
> > >> it seems that there are no valid statistics for the current Internet
> > >> to sustain your case.
> > > as we discussed privately, there seem to be no real measurements to
> > > sustain any case.  this is all conjecturbation.
> > >
> > > what i do not understand is why, given the lack of solid evidence tha=
t
> > > we are in a safe space, you and others are not willing to spend a few
> > > euro cents to have a reasonable level of assurance at this layer.
> > >
> > > randy
> > Randy,
> >
> > It is not a few cents, it is likely the re-engineering of a lot of sili=
con.
> >
> > The reason that UDP is of interest is that the on path silicon knows ho=
w to
> > process it, for example it knows how to to ECMP it.
> >
> > The reason that the UDP c/s is a problem for a tunneler is that it need=
s to
> > have access to the whole pkt to calculate the c/s, but as you know the
> silicon
> > optimised that access away a long time ago.
> >
> > The alternative would be UDP-lite, but the ability of on path silicon t=
o
> process
> > that as competently and as completely as it processes UDP is by no mean=
s
> > clear.
> >
> > - Stewart
> >
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@ietf.org
> > https://www.ietf.org/mailman/listinfo/mpls


From lear@cisco.com  Sun Jan 19 22:14:27 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79ACA1A0052 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 22:14:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.335
X-Spam-Level: 
X-Spam-Status: No, score=-7.335 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8VELlopuNa9 for <ietf@ietfa.amsl.com>; Sun, 19 Jan 2014 22:14:25 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id E3E791A004B for <ietf@ietf.org>; Sun, 19 Jan 2014 22:14:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11324; q=dns/txt; s=iport; t=1390198465; x=1391408065; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=WRp/2dWUgsbeA16fgEkrhpv+bmOmEcS6bYPtmGLYbCs=; b=Bq3dhO05aeiEA8LS1JB1M/rawIQIoWr72TJTFDMq1z78+fEP0fZ8L8pC A6ue9oj51vmRUHHTWndsKSDFJWzoRPDvvVbJ3w0BSkjU8nINmzjAqWYVJ YbSPuxucHWm83dhVJf1zBUxAS/Je6Eq3IJhDNhui/+hKnJlKPSy3NCgXy s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhAFAPu93FKQ/khN/2dsb2JhbABZgwuEC4VdsmKBCRZ0giUBAQEDASNJAQkDBQsLGAkaBwICDwJGBgEMAQcBARCHaQinc5tOF44nBFQHgm+BSQSYIpIYgW+BPzuBLA
X-IronPort-AV: E=Sophos;i="4.95,689,1384300800"; d="scan'208,217";a="3202563"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 20 Jan 2014 06:14:24 +0000
Received: from rtp-vpn6-1357.cisco.com (rtp-vpn6-1357.cisco.com [10.82.253.82]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0K6ELLs012896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jan 2014 06:14:23 GMT
Message-ID: <52DCBEBC.10806@cisco.com>
Date: Mon, 20 Jan 2014 07:14:20 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, dcrocker@bbiw.net
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net> <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net>
In-Reply-To: <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------040907030104010206020802"
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 06:14:27 -0000

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

Jari,

On 1/19/14, 10:21 PM, Jari Arkko wrote:
> But I think both the IETF and even me have learned over the years to do this a bit better. And we need to continue to watch for this, or perhaps even come up with better processes to defend against it.

I'm certain you've learned, Jari, although I do find myself repeating
one particular point:

Organizations DON'T learn; (some) people do.  We can build processes
into organizations that help us to either not repeat the mistakes we or
others have made, or to exacerbate matters.  In my experience it is
usually both, by the way, and you just hope that on the whole you've
made matters better.

Those of us who have learned, recognize the danger in the proposed text
to wedge a group, not simply because it could seemingly be used as a
sledgehammer as my earlier anecdote demonstrated (and I modified that
only slightly from what happened in ISMS), but because in this specific
circumstance we do not have a handle on the problem of pervasive
surveillance â€“ yet.

What do I mean when I make that statement?  It deserves justification
itself ;-)

We have in draft-farrell-perpass-attack a definition of what pervasive
surveillance is to us.  We do not yet understand, however, what our own
capabilities and limitations are in defending against it.  By negative
proof, had we this understanding the IAB would not be holding a joint
workshop with the W3C to gain it.  There is barely even a framework by
which we talk about pervasive surveillance.  We know that encrypting
data between the end user and a service somewhere off in the Internet
*may* provide some confidentiality, depending on the strength of the
encryption and a host of other factors.  We have some understanding of
the performance impact of encryption.

On the other hand, there is everyone's favorite catch-phrase:
meta-data.  That is, the 5-tuple in packets, the timing associated with
transmission and delivery, their size, and reasonable *engineering*
assumptions to make about where people can and will monitor.  We also
only have limited understanding of the performance impact on any
mitigations to avoid masking these qualities.

We also have but a limited understanding of when it is valuable to
encrypt and when such encryption would be negated by factors that we
find impractical to eliminate, such as traffic and timing attacks or
when the existence of later communication itself reveals the same
information (e.g., DNS queries followed by a connect()).

We have a limited understanding of how much of pervasive surveillance
should be addressed at the upper layers versus the lower layers. 
Encrypting once has a cost.  Encrypting several times has several times
that cost.  Encrypting end-to-end using the mechanisms we have today may
itself facilitate collection of metadata.

It should not be surprising that we don't know as much as we would like,
as we are still at the beginning of this process, just as we began the
process for security considerations so many years ago.  Right now our
job is to figure all of this out.  By "our" I mean that we all need to
be thinking about this problem, identifying risks, and discussing ways
to reduce them, while exposing what tradeoffs there are.  That's why I
like *most* of Stephen's draft (all of it but one paragraph, in fact),
and why I'm glad Stephen is chairing the workshop in London.

And while I'm glad you understand how ADs can go too far, you also have
to recognize that we have been down this path before with others, and it
has been very rocky.  Working group chairs are in a fine position to
make a muddle of things, and we (I speak of myself as well) do an even
better job of muddling when there is not community understanding of the
above problems.

And this brings us to Sam's proposed text:

>    Those developing IETF specifications therefore
>    need to consider mitigating PM when making these architectural
>    decisions and be prepared to justify their decisions.

We don't have the people or knowledge in place to reasonably evaluate
such justifications at this point.  The person who proposed this text
proposed an example that may well have been in error.  That is no fault
of his, really, because we are all learning.  But let's not encourage
huge architectural swings when we don't yet have a handle on what advice
should be given.  Discussion and careful consideration are important
now.  Getting ideas out there is good.  Testing them is great! Nailing
some of the obvious bits, like asking why certain information is
exposed, is fantastic.  Discussion about protocol selection is excellent.

But the words that are quoted are stronger than that.  They can be used
by chairs and others to shift the burden onto the proponent of a
proposal when we have no shared understanding of what needs to be
addressed.  That's too high a bar and will lead to well-intentioned â€“
but wrong â€“ engineering decisions.

Eliot


--------------040907030104010206020802
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Jari,<br>
    <br>
    <div class="moz-cite-prefix">On 1/19/14, 10:21 PM, Jari Arkko wrote:<br>
    </div>
    <blockquote
      cite="mid:B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net"
      type="cite">
      <pre wrap="">But I think both the IETF and even me have learned over the years to do this a bit better. And we need to continue to watch for this, or perhaps even come up with better processes to defend against it.</pre>
    </blockquote>
    <br>
    I'm certain you've learned, Jari, although I do find myself
    repeating one particular point:<br>
    <br>
    Organizations DON'T learn; (some) people do.Â  We can build processes
    into organizations that help us to either not repeat the mistakes we
    or others have made, or to exacerbate matters.Â  In my experience it
    is usually both, by the way, and you just hope that on the whole
    you've made matters better.<br>
    <br>
    Those of us who have learned, recognize the danger in the proposed
    text to wedge a group, not simply because it could seemingly be used
    as a sledgehammer as my earlier anecdote demonstrated (and I
    modified that only slightly from what happened in ISMS), but because
    in this specific circumstance we do not have a handle on the problem
    of pervasive surveillance â€“ yet.<br>
    <br>
    What do I mean when I make that statement?Â  It deserves
    justification itself ;-)<br>
    <br>
    We have in draft-farrell-perpass-attack a definition of what
    pervasive surveillance is to us.Â  We do not yet understand, however,
    what our own capabilities and limitations are in defending against
    it.Â  By negative proof, had we this understanding the IAB would not
    be holding a joint workshop with the W3C to gain it.Â  There is
    barely even a framework by which we talk about pervasive
    surveillance.Â  We know that encrypting data between the end user and
    a service somewhere off in the Internet <b>may</b> provide some
    confidentiality, depending on the strength of the encryption and a
    host of other factors.Â  We have some understanding of the
    performance impact of encryption.<br>
    <br>
    On the other hand, there is everyone's favorite catch-phrase:
    meta-data.Â  That is, the 5-tuple in packets, the timing associated
    with transmission and delivery, their size, and reasonable <b>engineering</b>
    assumptions to make about where people can and will monitor.Â  We
    also only have limited understanding of the performance impact on
    any mitigations to avoid masking these qualities.<br>
    <br>
    We also have but a limited understanding of when it is valuable to
    encrypt and when such encryption would be negated by factors that we
    find impractical to eliminate, such as traffic and timing attacks or
    when the existence of later communication itself reveals the same
    information (e.g., DNS queries followed by a connect()).<br>
    <br>
    We have a limited understanding of how much of pervasive
    surveillance should be addressed at the upper layers versus the
    lower layers.Â  Encrypting once has a cost.Â  Encrypting several times
    has several times that cost.Â  Encrypting end-to-end using the
    mechanisms we have today may itself facilitate collection of
    metadata.<br>
    <br>
    It should not be surprising that we don't know as much as we would
    like, as we are still at the beginning of this process, just as we
    began the process for security considerations so many years ago.Â 
    Right now our job is to figure all of this out.Â  By "our" I mean
    that we all need to be thinking about this problem, identifying
    risks, and discussing ways to reduce them, while exposing what
    tradeoffs there are.Â  That's why I like <b>most</b> of Stephen's
    draft (all of it but one paragraph, in fact), and why I'm glad
    Stephen is chairing the workshop in London.<br>
    <br>
    And while I'm glad you understand how ADs can go too far, you also
    have to recognize that we have been down this path before with
    others, and it has been very rocky.Â  Working group chairs are in a
    fine position to make a muddle of things, and we (I speak of myself
    as well) do an even better job of muddling when there is not
    community understanding of the above problems.<br>
    <br>
    And this brings us to Sam's proposed text:<br>
    <br>
    <blockquote type="cite">
      <pre wrap="">   Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.</pre>
    </blockquote>
    <br>
    We don't have the people or knowledge in place to reasonably
    evaluate such justifications at this point.Â  The person who proposed
    this text proposed an example that may well have been in error.Â 
    That is no fault of his, really, because we are all learning.Â  But
    let's not encourage huge architectural swings when we don't yet have
    a handle on what advice should be given.Â  Discussion and careful
    consideration are important now.Â  Getting ideas out there is good.Â 
    Testing them is great! Nailing some of the obvious bits, like asking
    why certain information is exposed, is fantastic.Â  Discussion about
    protocol selection is excellent.<br>
    <br>
    But the words that are quoted are stronger than that.Â  They can be
    used by chairs and others to shift the burden onto the proponent of
    a proposal when we have no shared understanding of what needs to be
    addressed.Â  That's too high a bar and will lead to well-intentioned
    â€“ but wrong â€“ engineering decisions.<br>
    <br>
    Eliot<br>
    <br>
  </body>
</html>

--------------040907030104010206020802--

From j.schoenwaelder@jacobs-university.de  Mon Jan 20 02:34:49 2014
Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2025E1A00EB; Mon, 20 Jan 2014 02:34:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.785
X-Spam-Level: 
X-Spam-Status: No, score=-2.785 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZdPTV8lbCC4; Mon, 20 Jan 2014 02:34:47 -0800 (PST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 87E931A00EA; Mon, 20 Jan 2014 02:34:47 -0800 (PST)
Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 9BBF420071; Mon, 20 Jan 2014 11:34:47 +0100 (CET)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id fRxbS4s_fFJM; Mon, 20 Jan 2014 11:34:47 +0100 (CET)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 3207D20026; Mon, 20 Jan 2014 11:34:47 +0100 (CET)
Received: by elstar.local (Postfix, from userid 501) id 44A832ABF8A4; Mon, 20 Jan 2014 11:34:45 +0100 (CET)
Date: Mon, 20 Jan 2014 11:34:45 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: SM <sm@resistor.net>
Subject: Re: [netmod] Fwd: Re: Last Call: <draft-ietf-netmod-iana-timezones-03
Message-ID: <20140120103445.GA44289@elstar.local>
Mail-Followup-To: SM <sm@resistor.net>, Benoit Claise <bclaise@cisco.com>, ietf@ietf.org, netmod@ietf.org
References: <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <6.2.5.6.2.20131203182446.06c04fa8@resistor.net> <52A1ACEF.6080307@cisco.com> <52CD7EBD.4090506@cisco.com> <CABCOCHQp+04OwEZ2rMZt6mvfboX-cnqSmhAE9rxFqd0NjmYdAg@mail.gmail.com> <6.2.5.6.2.20140108233958.0a849e58@resistor.net> <20140109105804.GA44893@elstar.local> <6.2.5.6.2.20140109051548.0a951040@resistor.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6.2.5.6.2.20140109051548.0a951040@resistor.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org, netmod@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 10:34:49 -0000

On Thu, Jan 09, 2014 at 07:47:46AM -0800, SM wrote:
 
> >There was concensus in the WG that it is desirable to configure
> >timezones by name (e.g., Europe/Paris) instead of having only hard
> >coded UTC offsets - the benefits should be obvious.
> 
> I agree that there can be benefits to that approach.  I could not
> find the (mailing list) message where that WG decision was taken.

SM,

there are no specific concensus calls for every leaf since this won't
scale. I do not recall having seen any issues raised on using timezone
names during the WG last calls. The timezone configuration using
timezone names has been in this document since its very beginning,
even before WG adoption, see draft-bierman-netmod-system-mgmt-00 (June
2, 2011).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

From adrian@olddog.co.uk  Mon Jan 20 02:41:58 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40FCB1A00CD; Mon, 20 Jan 2014 02:41:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HX5Rm-SJyT23; Mon, 20 Jan 2014 02:41:55 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id 847481A00CC; Mon, 20 Jan 2014 02:41:54 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0KAfphL027514; Mon, 20 Jan 2014 10:41:51 GMT
Received: from 950129200 (13.17.90.92.rev.sfr.net [92.90.17.13]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0KAfmQI027483 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 20 Jan 2014 10:41:50 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Black, David'" <david.black@emc.com>, <ops-dir@ietf.org>, <ietf@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
Subject: RE: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Date: Mon, 20 Jan 2014 10:41:51 -0000
Message-ID: <086201cf15cc$3ba0cf60$b2e26e20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKR0UxePs80B1Ib7vN/lALsvTEMeJkH9ELg
Content-Language: en-gb
X-TM-AS-MML: No
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 10:41:58 -0000

Thanks David,
Any review is better than no review :-)

Authors, this document is on Thursday's telechat and I would like to =
continue
with that plan.
Are you able to respond to David's review in double-quick time?

Thanks,
Adrian

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Black, David
> Sent: 20 January 2014 02:05
> To: ops-dir@ietf.org; ietf@ietf.org
> Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org; Black, David
> Subject: OPS-Dir review of draft-ietf-mpls-multipath-use-03
>=20
> I have reviewed this document as part of the operations directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> operations area directors.  Document editors and WG chairs should =
treat
> these comments just like any other last call comments.
>=20
> Summary:
> This draft is on the right track but has open issues, described in the =
review.
>=20
> I apologize for this review showing up a couple of days after the end =
of
> IETF Last Call.
>=20
> This draft discusses considerations for what are effectively =
MPLS-in-MPLS
> tunnels for multipathing - an LSP carries another LSP, with the inner
> (client) LSPs being distributed across multiple outer (server) LSPs =
that
> use different paths.  This draft is motivated by considerations =
specific
> to MPLS-TP that complicate multipathing when one of the two MPLS =
instances
> is MPLS-TP.
>=20
> I consider the following to be open issues that need attention (each
> letter is used to tag the issue in the text that follows - [B] occurs
> multiple times, as there are multiple aspect to that issue):
>=20
> [A] Summary text in Introduction appears to be wrong.
> [B] Section 3.2 needs a summary.
> [C] Entropy label "sandwich" seems peculiar and at least needs an =
explanation.
> [D] Discussion of multipath impacts on MPLS OAM should be added to =
Section 4.
>=20
> --- Comments on draft text
>=20
> [A] Section 1 (Introduction) 2nd paragraph:
>=20
>    RFC 5654 requirement 33 requires the capability to carry a client
>    MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer =
[RFC5654].
>    This is possible in all cases with one exception.  When an MPLS LSP
>    exceeds the capacity of any single component link it MAY be carried
>    by a network using multipath techniques, but MAY NOT be carried by =
a
>    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
>    imposed by MPLS-TP Operations, Administration, and Maintenance =
(OAM)
>    fate sharing constraints and MPLS-TP LM OAM packet ordering
>    constraints (see Section 3.1).
>=20
> Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> exception appears to concern the reverse, and Section 4 on carrying =
MPLS
> over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> Was the exception intended to be for an MPLS-TP LSP that exceeds the
> capacity of any single component link?
>=20
> Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's =
equivalent
> to "MAY OR MAY NOT").  I think "cannot" was intended her, but "MUST =
NOT"
> is another possibility.
>=20
> [B] Section 3.2 contains a lot of useful details, but it could really =
use
> a summary at the end on the options and recommendations for meeting =
the
> four requirements (this summary could be a new Section 3.3).  It's a =
bit
> difficult to discern what's going on, as I had to read this section =
more
> than once in order to discern the following:
>=20
> [C] In Section 3.2, use of an MPLS entropy label to meet requirement =
MP#1
> requires that it be "below the MPLS-TP label" whereas, to meet =
requirement
> MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LSP =
label".
> This combination appears to suggest "sandwiching" the MPLS-TP label =
between
> two entropy labels that effectively carry the same information =
(albeit,
> applied and removed at different places in the network) - was that =
intended?
> This is important, as there seems to be no reasonable alternative
> to the entropy label for meeting requirement MP#2, and the draft's
> alternative to the entropy label for meeting requirement MP#1 is "some =
form
> of configuration" - the entropy label would seem to be preferred to =
that
> based on my reading of this draft and the comment in RFC 5706 section =
2.2
> that "Anything that can be configured can be misconfigured."
>=20
> [B] A summary of requirements for implementation and deployment at the =
end
> of Section 3.2 would have made this much more obvious.  That should be
> provided in addition to addressing the above question about duplicate =
use
> of the MPLS entropy label.
>=20
> --- Relevant Q&A based on RFC 5706 Appendix A
>=20
> I'm omitting management concerns, as both MPLS and MPLS-TP have =
extensive
> management infrastructure, and this draft's notion of stacking LSPs so
> that one instance of MPLS (or MPLS-TP) can be a server to (i.e., =
carry)
> another is not novel to this draft.
>=20
> A.1.1.  Has deployment been discussed?
>=20
> [B] Yes, although Section 3.2 is weak on deployment requirements (some =
of
> which are implementation requirements) and could use a summary.
>=20
> A.1.2.  Has installation and initial setup been discussed?
>=20
> No, although because this draft reuses existing functionality in =
different
> configurations, this really reduces to the A.1.9 configuration =
question
> below.  In practice, quite a bit of operator knowledge and insight is
> required to get initial setup right, e.g., as traffic engineering LSPs =
to
> avoid congestion problems (needed to meet requirement MP#3) requires
> significant knowledge of network structure and expected traffic flows.
> This should be obvious to anyone who works w/MPLS, but it's probably
> worth stating for completeness.
>=20
> A.1.6.  Have suggestions for verifying correct operation been =
discussed?
>=20
> Yes and no.  Section 3.2 discusses OAM, and contains this important
> requirement for OAM traffic:
>=20
>    An Entropy Label must be used to insure that all of the
>    MPLS-TP payload and OAM traffic are carried on the same component,
>    except during very infrequent transitions due to load balancing.
>=20
> [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> Section 4; that should be added.
>=20
> A.1.9.  Is configuration discussed?
>=20
> [B] Not much. Configuration is required to meet requirements MP#3 and =
MP#4,
> and is one of the options for MP#1.  A summary of what has to be =
configured
> as part of the summary at the end of Section 3.2 would be a good idea.
>=20
> A.2.* [skipped, see above]
>=20
> A.3 Documentation
>=20
> There's quite a bit of operational material contained in this draft; a
> separate section on operations and management considerations would not
> be appropriate.
>=20
> There is a useful implementation status section which appears to imply
> that MPLS-TP over MPLS is not currently deployable due to absence of
> entropy label support, and because deployed MPLS equipment does not
> generally support multipathing.  Nonetheless, data center experience
> indicates significant value and widespread use of multipathing based
> on link aggregation and ECMP; corresponding benefits can be expected
> for use of multipathing in the Internet beyond data centers.
>=20
> --- Editorial comments/nits:
>=20
> - Section 3.1, after RFC 5960 quotes:
>=20
>    [RFC5960] paragraph 3 requires that packets within a specific =
ordered
>=20
> Insert "Section 3.1.1., before "paragraph 3" and likewise for =
"paragraph 6"
> later in the same paragraph in the draft.
>=20
> - Section 3.2, requirement MP#3:
>=20
>    MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not be
>=20
> "insure" -> "ensure" or "assure".  Surely this draft does not envision
> operators taking out insurance policies on MPLS TP LSP behavior ;-).
>=20
> - Section 3.2, last paragraph on p.8:
>=20
>    An MPLS-TP LSP may not traverse multipath links on the path where
>    MPLS-TP forwarding requirements cannot be met.
>=20
> "may not" is meaningless - I believe "MUST NOT" was intended here.
>=20
> - Section 4, middle of 3rd para:
>=20
> Editorial suggestions for clarity:
>=20
> OLD
>             For those LSP that are larger than component link
>     capacity, their capacity are not integer multiples of convenient
>     capacity increments such as 10Gb/s.
> NEW
>             For those LSPs that are larger than a component link
>    capacity, the LSP capacities need not be (and often are not)
>    integer multiples of convenient capacity increments such as 10Gb/s.
>=20
> In particular, "are not" seems wrong, as the "integer multiples"
> case is possible, so I changed "are not" to "need not be (and often
> are not)" in the suggested new text.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) =
293-7786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From lear@cisco.com  Mon Jan 20 05:55:58 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72BE61A0118 for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kCeiliXJ2QvQ for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:55:56 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1391A0162 for <ietf@ietf.org>; Mon, 20 Jan 2014 05:55:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1472; q=dns/txt; s=iport; t=1390226157; x=1391435757; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=G19Q9qnd2J0EJVKBcapjdfTLTCaPaxyZC9Bd3gibgJs=; b=lXwMKIoqVjdswAijQKjQPXcqa3IPEKWLvCcC5Gf3e295BcV65o38NkYA /YNEHntQQMFjLx/5xV6vGzaj3Gzr07V2N7g+QMhAi2BNJyJeIcqyLJJO9 vb12ILk1LlFraGD8/laLWwP2R5+C+gJNLQgOChAe8jUUhl+HAEkl5YUFM g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AisFAK0q3VKQ/khM/2dsb2JhbABZgwuEC7g/gQ0WdIImAQEEI1UBEAsaAgUWBAcCAgkDAgECAUUGAQwBBwEBiAGnc5tuF4EpjVYHgm+BSQEDmCKSGIFvgT87
X-IronPort-AV: E=Sophos;i="4.95,690,1384300800";  d="scan'208";a="3225866"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 20 Jan 2014 13:55:42 +0000
Received: from ams3-vpn-dhcp5273.cisco.com (ams3-vpn-dhcp5273.cisco.com [10.61.84.152]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0KDtf8J002190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jan 2014 13:55:41 GMT
Message-ID: <52DD2ADC.6030800@cisco.com>
Date: Mon, 20 Jan 2014 14:55:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, dcrocker@bbiw.net
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net> <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net> <52DCBEBC.10806@cisco.com>
In-Reply-To: <52DCBEBC.10806@cisco.com>
X-Enigmail-Version: 1.6
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 13:55:58 -0000

So... having written a bunch of stuff, someone has suggested to me an
alternative compromise offlist, as follows:

OLD:

   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions and be prepared to justify their decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.

NEW:

   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions.  Getting
   adequate, early review of architectural decisions including whether
   appropriate mitigation of PM can be made is important.  Revisiting
   these architectural decisions late in the process is very costly.


I can live with this, largely because everything there is true at the
general level. We're all going to learn to provide more specific advice
than this, however.  As I wrote, I am hoping that the STRING workshop
will help us make some headway.

Eliot

From lear@cisco.com  Mon Jan 20 05:57:31 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B8A1A016B for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfgHYvGPCMfu for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:57:30 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id C88AB1A0118 for <ietf@ietf.org>; Mon, 20 Jan 2014 05:57:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=444; q=dns/txt; s=iport; t=1390226250; x=1391435850; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=EF6/8Bm9K8Q+igcmTVeP4q39pKO5uMRWOUCmepbMgbY=; b=T3wUrWpmhMowvMXojhWOiagb6KJmeeD0xPJJRy691cKrKsJYc6+iIYt6 0L33/acuo+246ECjDbtO0QSYiP8aXVMk1r2z9Ij6FTOPWAgBGqMJZWLii kCd0MtwWd36YjDR8KZ81lASxbnQDl3K0XPaQ27X14LnvZVRAku0CXn104 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAK0q3VKQ/khM/2dsb2JhbABZgws4g1O3cE+BDRZ0giUBAQEEI1UBEAsYAgIFFgQHAgIJAwIBAgFFBgEMAQcBAQWHfA2nZptuF4EpjVYHgm+BSQEDmCKSGIFvgT87
X-IronPort-AV: E=Sophos;i="4.95,690,1384300800";  d="scan'208";a="3226000"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 20 Jan 2014 13:57:29 +0000
Received: from ams3-vpn-dhcp5273.cisco.com (ams3-vpn-dhcp5273.cisco.com [10.61.84.152]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0KDvSQG002706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jan 2014 13:57:29 GMT
Message-ID: <52DD2B48.5070002@cisco.com>
Date: Mon, 20 Jan 2014 14:57:28 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, dcrocker@bbiw.net
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net> <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net> <52DCBEBC.10806@cisco.com> <52DD2ADC.6030800@cisco.com>
In-Reply-To: <52DD2ADC.6030800@cisco.com>
X-Enigmail-Version: 1.6
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 13:57:31 -0000

Aiming for the top of the Narten list for the week...

On 1/20/14, 2:55 PM, Eliot Lear wrote:
>
>
> I can live with this, largely because everything there is true at the
> general level. We're all going to learn to provide more specific advice
> than this, however.  As I wrote, I am hoping that the STRING workshop
> will help us make some headway.
>

s/STRING/STRINT/

Eliot
[1] http://www.iab.org/activities/workshops/strint/

From jari.arkko@piuha.net  Mon Jan 20 05:59:06 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5340C1A0171 for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:59:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yc2m_QFMjJMk for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 05:59:05 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 10F111A0170 for <ietf@ietf.org>; Mon, 20 Jan 2014 05:59:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 019142CECD; Mon, 20 Jan 2014 15:59:05 +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 IQBppUH1ypbt; Mon, 20 Jan 2014 15:59:04 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 41E242CC48; Mon, 20 Jan 2014 15:59:04 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52DD2ADC.6030800@cisco.com>
Date: Mon, 20 Jan 2014 15:59:03 +0200
Content-Transfer-Encoding: 7bit
Message-Id: <0B929BF2-17B2-4377-BFB4-2B7D69C677D0@piuha.net>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net> <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net> <52DCBEBC.10806@cisco.com> <52DD2ADC.6030800@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 13:59:06 -0000

This would work for me. Thanks, Eliot.

Jari


From kent@bbn.com  Mon Jan 20 07:14:35 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A38071A0183 for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 07:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.736
X-Spam-Level: 
X-Spam-Status: No, score=-4.736 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V9jFl52xiHSa for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 07:14:34 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 11F1C1A00DE for <ietf@ietf.org>; Mon, 20 Jan 2014 07:14:34 -0800 (PST)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:54469) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1W5GYc-000O9U-5t for ietf@ietf.org; Mon, 20 Jan 2014 10:14:34 -0500
Message-ID: <52DD3D5C.5030207@bbn.com>
Date: Mon, 20 Jan 2014 10:14:36 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net>
In-Reply-To: <52DC2BD0.4000803@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 15:14:35 -0000

> On 1/19/2014 12:30 AM, Eliot Lear wrote:
>> It is fair to say that we should consider this threat at an
>> architectural level.  It's fair (albeit a truism) that finding design
>> flaws earlier in the process rather than later is less costly
>> (ENG-101).  Justification language like the above, however, is likely to
>> actively impede the IETF, as these sorts of things have in the past.
As one of the folks who suggested "address" vs. "consider" I now recant.

I am satisfied with "consider."

if anyone cares :-).

Steve


From scott.brim@gmail.com  Mon Jan 20 07:25:57 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93E31A01AE for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 07:25:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ccYfVyBV1IQm for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 07:25:56 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 845E31A018D for <ietf@ietf.org>; Mon, 20 Jan 2014 07:25:56 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so2228085obc.11 for <ietf@ietf.org>; Mon, 20 Jan 2014 07:25:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=A3dulNYJIGkG2EgdOp3s9g2Px2kWJ+eg2lL6TEYa5cM=; b=GsNXESXvVjDVQo947eUmXikZBwxGCgKXKnbxBTKBz9BjpS9vnGaHUqDKCFl4vgV1ej g7fdQky2f/1pM0PevoSy7Z826k1or3TgughSmnvVXie6q3kqljWoCYUJLY8QlJZGLoS2 oV7JFSHp9eYOW7X3M2/f8gcmkrmzlCdihXoWXowFdzvDcLYo6UinVIckdctPvR01yP/w U8XgQHvxoiaZNhkgkEAhRnDRyWfFUNC6BtdQx2Rb1xAXqlVGipzcJKMFU2dK0sbM+CJ2 IA8le2xSdnUrkLpoPUNAWhvnzsRSAgQW+9soewHP7LPfbitoj20eFMsX0xdy9sKEFgHN riBA==
X-Received: by 10.60.134.230 with SMTP id pn6mr6899804oeb.40.1390231556669; Mon, 20 Jan 2014 07:25:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 20 Jan 2014 07:25:36 -0800 (PST)
In-Reply-To: <52DD2ADC.6030800@cisco.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC2BD0.4000803@dcrocker.net> <B72AD13B-7A0B-4865-82FF-2E627EF69183@piuha.net> <52DCBEBC.10806@cisco.com> <52DD2ADC.6030800@cisco.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 20 Jan 2014 10:25:36 -0500
Message-ID: <CAPv4CP_JLT5ZKtFh3d=yz=Dm0aDYMSx9wXcSq=3FV8YttLK1ww@mail.gmail.com>
Subject: Re: Consideration vs. Blocking (was Re: Gen-Art telechat review of draft-farrell-perpass-attack-04)
To: Eliot Lear <lear@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 15:25:58 -0000

On Mon, Jan 20, 2014 at 8:55 AM, Eliot Lear <lear@cisco.com> wrote:
>    decisions and be prepared to justify their decisions.  Getting
...
>    decisions.  Getting

wfm

> the STRING workshop

I believe your daughter is just the right age for the delightful
"Letitia Rabbit's String Song", if you can find it.  Happy String!

Scott

From tnadeau@lucidvision.com  Mon Jan 20 07:29:25 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81B401A01B4; Mon, 20 Jan 2014 07:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.223
X-Spam-Level: ***
X-Spam-Status: No, score=3.223 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=1.157, J_CHICKENPOX_24=0.6, J_CHICKENPOX_34=0.6, J_CHICKENPOX_84=0.6, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6O2-0aJHFDk0; Mon, 20 Jan 2014 07:29:12 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5B00C1A01B9; Mon, 20 Jan 2014 07:29:11 -0800 (PST)
Received: from [192.168.1.115] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 47A8526BF074; Mon, 20 Jan 2014 10:29:11 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_6B2B593D-96C5-4FE4-AD09-6076CE6AEF7A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-ietf-opsawg-oam-overview-08.txt> (An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms) to Informational RFC
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <50F972FC.2030707@cisco.com>
Date: Mon, 20 Jan 2014 10:29:10 -0500
Message-Id: <6C3490D7-3727-41BA-8980-683DF84451A2@lucidvision.com>
References: <20130111193616.19158.16205.idtracker@ietfa.amsl.com> <50F437BF.8040005@cisco.com> <50F972FC.2030707@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1827)
Cc: "draft-ietf-opsawg-oam-overview@tools.ietf.org" <draft-ietf-opsawg-oam-overview@tools.ietf.org>, opsawg@ietf.org, IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 15:29:25 -0000

--Apple-Mail=_6B2B593D-96C5-4FE4-AD09-6076CE6AEF7A
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_37D55104-A690-4711-87D5-FDCA45807A2C"


--Apple-Mail=_37D55104-A690-4711-87D5-FDCA45807A2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


	Reviewing the current version of the draft (12), many of the =
comments below are still not addressed.

	--Tom



> Here is Tom Nadeau's feedback, forwarded with permission:
>=20
> Regards, Benoit
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
> Some general comments:
>=20
> I did not find any discussion around use of configuration within OAM =
mechanisms. This is clearly something that is happening in groups like =
PWE3 and CCAMP. The motivation for this should be explained and =
documented to at least guide these efforts.
> 2. There is no real discussion around the security aspects of these =
tools. Should there be?
>=20
> 3. While the document provides a nice taxonomy of various OAM tools, =
it does not really discuss the techniques for using them. I do not =
expect anything in detail, but it is not obvious that many of these =
tools can be orchestrated to form a "toolset" that can be used to do =
multi-layer OAM functions for services such as carrier Ethernet over =
VPLS over MPLS, for example.
>=20
> 4. It might be useful to at least mention in the performance metrics =
section, a discussion around the accuracy of these tools and how it =
depends on scale, implementation and network configurations.
>=20
>=20
> My detailed comments inline starting with TOM:
>=20
> --Tom
>=20
>=20
>=20
>=20
>=20
>=20
> Expires: July 2013                                Nokia Siemens =
Networks
>                                                            E. =
Bellagamba
>                                                                 =
Ericsson
>                                                            Y. =
Weingarten
>=20
>                                                          January 9, =
2013
>=20
>                               An Overview of
>         Operations, Administration, and Maintenance (OAM) Mechanisms
>                    draft-ietf-opsawg-oam-overview-08.txt
>=20
>=20
> Abstract
>=20
>    Operations, Administration, and Maintenance (OAM) is a general term
>    that refers to a toolset that can be used for fault detection and
>    isolation, and for performance measurement. OAM mechanisms have =
been
>    defined for various layers in the protocol stack, and are used with =
a
>    variety of protocols.
>=20
>    This document presents an overview of the OAM mechanisms that have
>    been defined and are currently being defined by the IETF.
>=20
> Status of this Memo
>=20
>    This Internet-Draft is submitted to IETF in full conformance with =
the
>    provisions of BCP 78 and BCP 79.
>=20
>    Internet-Drafts are working documents of the Internet Engineering
>    Task Force (IETF), its areas, and its working groups.  Note that
>    other groups may also distribute working documents as Internet-
>    Drafts.
>=20
>    Internet-Drafts are draft documents valid for a maximum of six =
months
>    and may be updated, replaced, or obsoleted by other documents at =
any
>    time.  It is inappropriate to use Internet-Drafts as reference
>    material or to cite them other than as "work in progress."
>=20
>    The list of current Internet-Drafts can be accessed at
>    http://www.ietf.org/ietf/1id-abstracts.txt.
>=20
>    The list of Internet-Draft Shadow Directories can be accessed at
>    http://www.ietf.org/shadow.html.
>=20
>    This Internet-Draft will expire on July 9, 2013.
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 1]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> Copyright Notice
>=20
>    Copyright (c) 2013 IETF Trust and the persons identified as the
>    document authors. All rights reserved.
>=20
>    This document is subject to BCP 78 and the IETF Trust's Legal
>    Provisions Relating to IETF Documents
>    (http://trustee.ietf.org/license-info) in effect on the date of
>    publication of this document. Please review these documents
>    carefully, as they describe your rights and restrictions with =
respect
>    to this document. Code Components extracted from this document must
>    include Simplified BSD License text as described in Section 4.e of
>    the Trust Legal Provisions and are provided without warranty as
>    described in the Simplified BSD License.
>=20
> Table of Contents
>=20
>=20
>    1. Introduction ................................................. 3
>       1.1. The Building Blocks of OAM .............................. 3
>       1.2. Forwarding Plane vs. Management Plane ................... 4
>       1.3. The OAM toolsets ........................................ 4
>       1.4. IETF OAM Documents ...................................... 6
>       1.5. Non-IETF OAM Documents ................................. 10
>    2. Basic Terminology ........................................... 12
>       2.1. Abbreviations .......................................... 12
>       2.2. Terminology used in OAM Standards ...................... 13
>          2.2.1. General Terms ..................................... 13
>          2.2.2. OAM Maintenance Entities .......................... 13
>          2.2.3. OAM Maintenance Points ............................ 14
>          2.2.4. Proactive and On-demand activation ................ 15
>          2.2.5. Connectivity Verification and Continuity Checks ... 15
>          2.2.6. Failures .......................................... 15
>    3. OAM Tools ................................................... 16
>       3.1. IP Ping and Traceroute ................................. 16
>          3.1.1. Ping .............................................. 16
>          3.1.2. Traceroute......................................... 16
>       3.2. Bidirectional Forwarding Detection (BFD) ............... 17
>          3.2.1. Overview .......................................... 17
>          3.2.2. BFD Control ....................................... 17
>          3.2.3. BFD Echo .......................................... 18
>       3.3. MPLS OAM ............................................... 18
>       3.4. MPLS-TP OAM ............................................ 19
>          3.4.1. Overview .......................................... 19
>          3.4.2. Generic Associated Channel ........................ 19
>          3.4.3. MPLS-TP OAM Toolset ............................... 20
>             3.4.3.1. Continuity Check and Connectivity Verification 20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 2]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>             3.4.3.2. Route Tracing ................................ 21
>             3.4.3.3. Lock Instruct ................................ 21
>             3.4.3.4. Lock Reporting ............................... 21
>             3.4.3.5. Alarm Reporting .............................. 21
>             3.4.3.6. Remote Defect Indication ..................... 22
>             3.4.3.7. Client Failure Indication .................... 22
>             3.4.3.8. Packet Loss Measurement (LM) ................. 22
>             3.4.3.9. Packet Delay Measurement (DM) ................ 22
>       3.5. PWE3 OAM ............................................... 23
>          3.5.1. PWE3 OAM using Virtual Circuit Connectivity =
Verification
>          (VCCV) ................................................... 23
>          3.5.2. PWE3 OAM using G-ACh .............................. 24
>       3.6. OWAMP and TWAMP......................................... 24
>          3.6.1. Overview .......................................... 24
>          3.6.2. Control and Test Protocols ........................ 24
>          3.6.3. OWAMP ............................................. 25
>          3.6.4. TWAMP ............................................. 26
>       3.7. Summary of OAM Functions ............................... 26
>    4. Security Considerations ..................................... 27
>    5. IANA Considerations ......................................... 27
>    6. Acknowledgments ............................................. 27
>    7. References .................................................. 28
>       7.1. Normative References ................................... 28
>       7.2. Informative References ................................. 31
>=20
> 1. Introduction
>=20
>    OAM is a general term that refers to a toolset for detecting,
>    isolating and reporting connection failures and performance
>    degradation.
>=20
>    This document summarizes the OAM tools and mechanisms defined in =
the
>    IETF.
>=20
>    The term OAM in this document refers to Operations, Administration
>    and Maintenance [OAM-Def], focusing on the forwarding plane of OAM.
>    Hence, management aspects are outside the scope of this document.
>=20
> TOM: This is a curious sentence to me since to me, OAM is management, =
or a subset of it.   Also, if you look at the referenced documents, =
there are many indirect references to MIBs, Netconf, etc=85 making this =
sentence further confusing. It might be helpful to explain more clearly =
that the authors here intended to not cover those things explicitly =
rather than grouping them arbitrarily under the definition of =
"management aspects"  Further, to clarify, it might be useful to expand =
on what "forwarding plane" is here just to be clear.   That is, is this =
"in band" or "out-of band" or both? Some of the tools referred to here =
also are part of the control AND data planes.=20
>=20
> 1.1. The Building Blocks of OAM
>=20
>    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).
>=20
>    This subsection provides a brief summary of the common tools used =
by
>    OAM protocols. An OAM protocol typically supports one or more of =
the
>    tools described below.
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 3]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    o Continuity Checking (CC):
>       Used for verifying the liveness of a connection between two MPs.
>=20
>    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.
>=20
>    o Path Discovery / Fault Localization:
>       An MP uses this mechanism to trace the route to a peer MP, i.e.,
>       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.
>=20
> TOM: The definition calls this "path discovery" but then talks about =
tracing routes. A better way of describing this in the paragraph would =
be that there I a use of path tracing in order to discover (or =
re-discover) paths that have been changed, created or destroyed. =20
>=20
>=20
>    o Performance Monitoring:
>       Consists of 3 main functions
>=20
>         o Loss Measurement (LM) - monitors the packet loss rate of a
>           connection.
>=20
>         o Delay Measurement (DM) - monitors the delay and delay
>           variation between MPs.
>=20
>         o Throughput measurement - monitors the throughput of a
>           connection.
>=20
> TOM: Along with the discussion above around path trace/discovery, it =
is imperative that paths be discovered (one way or another) in order to =
successfully d performance monitoring on those paths.
>=20
> 1.2. Forwarding Plane vs. Management Plane
>=20
>    While the OAM tools may, and quite often do, work in conjunction =
with
>    a control-plane or management plane, they are usually defined to be
>    independent of the control-plane.  The OAM tools communicate with =
the
>    management plane to raise alarms, and often the on-demand tools may
>    be activated by the management, e.g. to locate and localize =
problems.
>=20
>    The considerations of the control-plane maintenance tools or the
>    functionality of the management-plane are out of scope for this
>    document, which will concentrate on presenting the forwarding-plane
>    tools that are used for OAM.
>=20
> TOM: What about the data plane? For example, the GACH OAM type is such =
an example. VCCV also operates within the data plane after its =
configuration capabilities have been signaled.  It should also be =
mentioned that it is imperative that when required, OAM tools are =
capable of testing the actual data plane in as much accuracy as =
possible, but that they all should note how accurate.   Not all OAM =
tools are created equal.
>=20
>=20
> 1.3. The OAM toolsets
>=20
>    This memo provides an overview of the different sets of OAM
>    mechanisms defined by the IETF. It is intended for those with =
little
>    or no familiarity with the described mechanisms. The set of OAM
>    mechanisms described in this memo are applicable to IP unicast, =
MPLS,
>    pseudowires, and MPLS for the transport environment (MPLS-TP). =
While
>    OAM mechanisms that are applicable to other technologies exist, =
they
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 4]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    are beyond the scope of this memo. This document focuses on IETF
>    documents that have been published as RFCs, while other ongoing =
OAM-
>    related work is outside the scope.
>=20
>    The IETF has defined OAM protocols and mechanisms in several
>    different fronts:
>=20
>    o IP Ping and Traceroute:
>       Ping is a very simple and common application for failure =
diagnosis
>=20
> TOM: I am not sure the term "common" is necessary.
>=20
>       that uses ICMP Echo requests, as defined in [ICMPv4], and
>       [ICMPv6].
>       Traceroute ([TCPIP-Tools], [NetTools]) is an application that
>       allows users to trace the path between an IP source and an IP
>       destination, i.e., to identify the nodes along the path.
>=20
>    o BFD:
>       Bidirectional Forwarding Detection (BFD) is defined in [BFD] as =
a
>       framework for a lightweight generic OAM mechanism.  The =
intention
>       is to define a base mechanism that can be used with various
>       encapsulation types, network environments, and in various medium
>       types.
>=20
>    o MPLS OAM:
>       MPLS LSP Ping, as defined in [MPLS-OAM], [MPLS-OAM-FW] and [LSP-
>       Ping], is an OAM mechanism for point to point MPLS LSPs. It
>       includes two main functions: Ping and Traceroute.
>=20
>    o MPLS-TP OAM:
>       MPLS-TP OAM is defined in a set of RFCs. The OAM requirements =
for
>       MPLS Transport Profile (MPLS-TP) are defined in [MPLS-TP-OAM].
>       Each of the tools in the OAM toolset is defined in its own RFC, =
as
>       specified in Section 1.4.
>=20
>    o PWE3 OAM:
>       The PWE3 OAM architecture defines control channels that support
>       the use of existing IETF OAM tools to be used for a pseudowire
>       (PW).  The control channels that are defined in [VCCV] and =
[PW-G-
>       ACH] may be used in conjunction with ICMP Ping, LSP Ping, and =
BFD
>       to perform CC and CV functionality.  In addition the channels
>       support use of any of the MPLS-TP based OAM tools for completing
>       their respective OAM functionality for a PW.
>=20
>    o OWAMP and TWAMP:
>       The One Way Active Measurement Protocol (OWAMP) and the Two Way
>       Active Measurement Protocols (TWAMP) are two protocols defined =
in
>       the IP Performance Metrics (IPPM) working group in the IETF. =
These
>       protocols allow delay and packet loss measurement in IP =
networks.
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 5]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    This document summarizes the OAM mechanisms defined by the IETF. We
>    first present a comparison of the terminology used in various OAM
>    standards, and then summarize the OAM functions that each OAM
>    standard provides.
>=20
> 1.4. IETF OAM Documents
>=20
>    Table 1 summarizes the IETF OAM related RFCs discussed in this
>    document.
>=20
>    The table includes a "Type" column, specifying the nature of each =
of
>    the listed documents:
>=20
>    o Tool: documents that define an OAM tool or mechanism.
>=20
>    o Prof.: documents that define a profile or a variant for an OAM
>       tool that is defined in other documents.
>=20
>    o Inf.: documents that define an infrastructure that is used by OAM
>       tools.
>=20
>    o Misc.: other OAM related documents, e.g., OAM requirement and
>       framework documents.
>=20
>    =
+-----------+--------------------------------------+-----+----------+
>    |           | Title                                |Type | RFC      =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |IP Ping and| Internet Control Message Protocol    |Tool | RFC 792  =
|
>    |Traceroute | [ICMPv4]                             |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Internet Control Message Protocol    |Tool | RFC 4443 =
|
>    |           | (ICMPv6) for the Internet Protocol   |     |          =
|
>    |           | Version 6 (IPv6) Specification       |     |          =
|
>    |           | [ICMPv6]                             |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A Primer On Internet and TCP/IP      |Tool | RFC 2151 =
|
>    |           | Tools and Utilities [TCPIP-Tools]    |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | FYI on a Network Management Tool     |Tool | RFC 1147 =
|
>    |           | Catalog: Tools for Monitoring and    |     |          =
|
>    |           | Debugging TCP/IP Internets and       |     |          =
|
>    |           | Interconnected Devices [NetTools]    |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Extended ICMP to Support Multi-Part  |Tool | RFC 4884 =
|
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 6]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           | Messages [ICMP-MP]                   |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | ICMP Extensions for Multiprotocol    |Tool | RFC 4950 =
|
>    |           | Label Switching [ICMP-Ext]           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Extending ICMP for Interface and     |Tool | RFC 5837 =
|
>    |           | Next-Hop Identification [ICMP-Int]   |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |BFD        | Bidirectional Forwarding Detection   |Tool | RFC 5880 =
|
>    |           | [BFD]                                |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Bidirectional Forwarding Detection   |Prof.| RFC 5881 =
|
>    |           | (BFD) for IPv4 and IPv6 (Single Hop) |     |          =
|
>    |           | [BFD-IP]                             |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Generic Application of Bidirectional |Misc.| RFC 5882 =
|
>    |           | Forwarding Detection [BFD-Gen]       |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Bidirectional Forwarding Detection   |Prof.| RFC 5883 =
|
>    |           | (BFD) for Multihop Paths [BFD-Multi] |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Bidirectional Forwarding Detection   |Prof.| RFC 5884 =
|
>    |           | for MPLS Label Switched Paths (LSPs) |     |          =
|
>    |           | [BFD-LSP]                            |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Bidirectional Forwarding Detection   |Prof.| RFC 5885 =
|
>    |           | for the Pseudowire Virtual Circuit   |     |          =
|
>    |           | Connectivity Verification (VCCV)     |     |          =
|
>    |           | [BFD-VCCV]                           |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |MPLS OAM   | Operations and Management (OAM)      |Misc.| RFC 4377 =
|
>    |           | Requirements for Multi-Protocol Label|     |          =
|
>    |           | Switched (MPLS) Networks [MPLS-OAM]  |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A Framework for Multi-Protocol       |Misc.| RFC 4378 =
|
>    |           | Label Switching (MPLS) Operations    |     |          =
|
>    |           | and Management (OAM) [MPLS-OAM-FW]   |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Detecting Multi-Protocol Label       |Tool | RFC 4379 =
|
>    |           | Switched (MPLS) Data Plane Failures  |     |          =
|
>    |           | [LSP-Ping]                           |     |          =
|
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 7]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           =
+--------------------------------------+-----+----------+
>    |           | Operations and Management (OAM)      |Misc.| RFC 4687 =
|
>    |           | Requirements for Point-to-Multipoint |     |          =
|
>    |           | MPLS Networks [MPLS-P2MP]            |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |MPLS-TP    | Requirements for OAM in MPLS-TP      |Misc.| RFC 5860 =
|
>    |OAM        | [MPLS-TP-OAM]                        |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | MPLS Generic Associated Channel      |Inf. | RFC 5586 =
|
>    |           | [G-ACh]                              |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | MPLS-TP OAM Framework                |Misc.| RFC 6371 =
|
>    |           | [TP-OAM-FW]                          |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Proactive Connectivity Verification, |Tool | RFC 6428 =
|
>    |           | Continuity Check, and Remote Defect  |     |          =
|
>    |           | Indication for the MPLS Transport    |     |          =
|
>    |           | Profile [TP-CC-CV]                   |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | MPLS On-Demand Connectivity          |Tool | RFC 6426 =
|
>    |           | Verification and Route Tracing       |     |          =
|
>    |           | [OnDemand-CV]                        |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | MPLS Fault Management Operations,    |Tool | RFC 6427 =
|
>    |           | Administration, and Maintenance (OAM)|     |          =
|
>    |           | [TP-Fault]                           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | MPLS Transport Profile Lock Instruct |Tool | RFC 6435 =
|
>    |           | and Loopback Functions [Lock-Loop]   |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Packet Loss and Delay Measurement for|Tool | RFC 6374 =
|
>    |           | MPLS Networks [MPLS-LM-DM]           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A Packet Loss and Delay Measurement  |Prof.| RFC 6375 =
|
>    |           | Profile for MPLS-Based Transport     |     |          =
|
>    |           | Networks [TP-LM-DM]                  |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |PWE3 OAM   | Pseudowire Virtual Circuit           |Inf. | RFC 5085 =
|
>    |           | Connectivity Verification (VCCV):    |     |          =
|
>    |           | A Control Channel for Pseudowires    |     |          =
|
>    |           | [VCCV]                               |     |          =
|
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 8]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           =
+--------------------------------------+-----+----------+
>    |           | Bidirectional Forwarding Detection   |Prof.| RFC 5885 =
|
>    |           | for the Pseudowire Virtual Circuit   |     |          =
|
>    |           | Connectivity Verification (VCCV)     |     |          =
|
>    |           | [BFD-VCCV]                           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Using the Generic Associated Channel |Inf. | RFC 6423 =
|
>    |           | Label for Pseudowire in the MPLS     |     |          =
|
>    |           | Transport Profile (MPLS-TP)          |     |          =
|
>    |           | [PW-G-ACh]                           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Pseudowire (PW) Operations,          |Misc.| RFC 6310 =
|
>    |           | Administration, and Maintenance (OAM)|     |          =
|
>    |           | Message Mapping [PW-Map]             |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>    |OWAMP and  | A One-way Active Measurement Protocol|Tool | RFC 4656 =
|
>    |TWAMP      | [OWAMP]                              |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A Two-Way Active Measurement Protocol|Tool | RFC 5357 =
|
>    |           | [TWAMP]                              |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | Framework for IP Performance Metrics |Misc.| RFC 2330 =
|
>    |           | [IPPM-FW]                            |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | IPPM Metrics for Measuring           |Misc.| RFC 2678 =
|
>    |           | Connectivity [IPPM-Con]              |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A One-way Delay Metric for IPPM      |Misc.| RFC 2679 =
|
>    |           | [IPPM-1DM]                           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A One-way Packet Loss Metric for IPPM|Misc.| RFC 2680 =
|
>    |           | [IPPM-1LM]                           |     |          =
|
>    |           =
+--------------------------------------+-----+----------+
>    |           | A Round-trip Delay Metric for IPPM   |Misc.| RFC 2681 =
|
>    |           | [IPPM-2DM]                           |     |          =
|
>    =
+-----------+--------------------------------------+-----+----------+
>                  Table 1 Summary of IETF OAM Related RFCs
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                  [Page 9]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> 1.5. Non-IETF OAM Documents
>=20
>    In addition to the OAM mechanisms defined by the IETF, the IEEE and
>    ITU-T have also defined various OAM mechanisms that focus on
>    Ethernet, and various other transport network environments. These
>    various mechanisms, defined by the three standard organizations, =
are
>    often tightly coupled, and have had a mutual effect on each other.
>    The ITU-T and IETF have both defined OAM mechanisms for MPLS LSPs,
>    [ITU-T-Y1711] and [LSP-Ping]. The following OAM standards by the =
IEEE
>    and ITU-T are to some extent linked to IETF OAM mechanisms listed
>    above and are mentioned here only as reference material:
>=20
>    o OAM mechanisms for Ethernet based networks have been defined by
>       both the ITU-T in [ITU-T-Y1731], and by the IEEE in =
[IEEE802.1ag].
>       The IEEE 802.3 standard defines OAM for one-hop Ethernet links
>       [IEEE802.3ah].
>=20
>    o The ITU-T has defined OAM for MPLS LSPs in [ITU-T-Y1711], and
>       MPLS-TP OAM in [ITU-G8113.1] and [ITU-G8113.2].
>=20
>    Table 2 summarizes the OAM standards mentioned in this document. =
This
>    document focuses on IETF OAM standards, but these non-IETF =
standards
>    are referenced where relevant.
>=20
>    =
+-----------+--------------------------------------+---------------+
>    |           | Title                                |Standard/Draft =
|
>    =
+-----------+--------------------------------------+---------------+
>    |ITU-T      | Operation & Maintenance mechanism    | ITU-T Y.1711  =
|
>    |MPLS OAM   | for MPLS networks [ITU-T-Y1711]      |               =
|
>    |           =
+--------------------------------------+---------------+
>    |           | Assignment of the 'OAM Alert Label'  | RFC 3429      =
|
>    |           | for Multiprotocol Label Switching    |               =
|
>    |           | Architecture (MPLS) Operation and    |               =
|
>    |           | Maintenance (OAM) Functions          |               =
|
>    |           | [OAM-Label]                          |               =
|
>    |           |                                      |               =
|
>    |           |  Note: although this is an IETF      |               =
|
>    |           |  document, it is listed as one of the|               =
|
>    |           |  non-IETF OAM standards, since it    |               =
|
>    |           |  was defined as a complementary part |               =
|
>    |           |  of ITU-T Y.1711.                    |               =
|
>    =
+-----------+--------------------------------------+---------------+
>    |ITU-T      | Operations, administration and       |ITU-T G.8113.2 =
|
>    |MPLS-TP OAM| Maintenance mechanisms for MPLS-TP   |               =
|
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 10]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           | networks using the tools defined for |               =
|
>    |           | MPLS [ITU-G8113.2]                   |               =
|
>    |           |                                      |               =
|
>    |           |  Note: this document describes the   |               =
|
>    |           |  OAM toolset defined by the IETF for |               =
|
>    |           |  MPLS-TP, whereas ITU-T G.8113.1     |               =
|
>    |           |  describes the OAM toolset defined   |               =
|
>    |           |  by the ITU-T.                       |               =
|
>    |           =
+--------------------------------------+---------------+
>    |           | Operations, Administration and       |ITU-T G.8113.1 =
|
>    |           | Maintenance mechanism for MPLS-TP in |               =
|
>    |           | Packet Transport Network (PTN)       |               =
|
>    |           =
+--------------------------------------+---------------+
>    |           | Allocation of a Generic Associated   | RFC 6671      =
|
>    |           | Channel Type for ITU-T MPLS Transport|               =
|
>    |           | Profile Operation, Maintenance, and  |               =
|
>    |           | Administration (MPLS-TP OAM)         |               =
|
>    |           | [ITU-T-CT]                           |               =
|
>    |           |                                      |               =
|
>    |           |  Note: although this is an IETF      |               =
|
>    |           |  document, it is listed as one of the|               =
|
>    |           |  non-IETF OAM standards, since it    |               =
|
>    |           |  was defined as a complementary part |               =
|
>    |           |  of ITU-T G.8113.1.                  |               =
|
>    =
+-----------+--------------------------------------+---------------+
>    |ITU-T      | OAM Functions and Mechanisms for     |[ITU-T-Y1731]  =
|
>    |Ethernet   | Ethernet-based Networks              |               =
|
>    |OAM        |                                      |               =
|
>    =
+-----------+--------------------------------------+---------------+
>    |IEEE       | Connectivity Fault Management        | IEEE 802.1ag  =
|
>    |CFM        | [IEEE802.1ag]                        |               =
|
>    |           |                                      |               =
|
>    |           |  Note: CFM was originally published  |               =
|
>    |           |  as IEEE 802.1ag, but is now         |               =
|
>    |           |  incorporated in the 802.1Q standard.|               =
|
>    =
+-----------+--------------------------------------+---------------+
>    |IEEE       | Media Access Control Parameters,     | IEEE 802.3ah  =
|
>    |802.3      | Physical Layers, and Management      |               =
|
>    |link level | Parameters for Subscriber Access     |               =
|
>    |OAM        | Networks [IEEE802.3ah]               |               =
|
>    |           |                                      |               =
|
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 11]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           |  Note: link level OAM was originally |               =
|
>    |           |  defined in IEEE 802.3ah, and is now |               =
|
>    |           |  incorporated in the 802.3 standard. |               =
|
>    =
+-----------+--------------------------------------+---------------+
>          Table 2 Non-IETF OAM Standards Mentioned in this Document
>=20
> 2. Basic Terminology
>=20
> 2.1. Abbreviations
>=20
>    ACH    Associated Channel Header
>=20
>    AIS    Alarm Indication Signal
>=20
>    BFD    Bidirectional Forwarding Detection
>=20
>    CC     Continuity Check
>=20
>    CV     Connectivity Verification
>=20
>    DM     Delay Measurement
>=20
>    FEC    Forwarding Equivalence Class
>=20
>    GAL    Generic Associated Label
>=20
>    ICMP   Internet Control Message Protocol
>=20
>    LDP    Label Distribution Protocol
>=20
>    LM     Loss Measurement
>=20
>    LSP    Label Switched Path
>=20
>    ME     Maintenance Entity
>=20
>    MEG    Maintenance Entity Group
>=20
>    MEP    MEG End Point
>=20
>    MIP    MEG Intermediate Point
>=20
>    MP     Maintenance Point
>=20
>    MPLS   Multiprotocol Label Switching
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 12]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    MPLS-TP MPLS Transport Profile
>=20
>    MTU    Maximum Transmission Unit
>=20
>    OAM    Operations, Administration, and Maintenance
>=20
>    PW     Pseudowire
>=20
>    PWE3   Pseudowire Emulation Edge-to-Edge
>=20
>    RDI    Remote Defect Indication
>=20
>    TTL    Time To Live
>=20
>    VCCV   Virtual Circuit Connectivity Verification
>=20
>=20
> TOM: Why is this section not at the top of this document, as is =
customary for RFCs? =20
>=20
>=20
> 2.2. Terminology used in OAM Standards
>=20
> 2.2.1. General Terms
>=20
>    A wide variety of terms is used in various OAM standards. Each of =
the
>    OAM standards listed in the reference section includes a section =
that
>    defines terms relevant to that tool. A thesaurus of terminology for
>    MPLS-TP terms is presented in [TP-Term], and provides a good =
summary
>    of some of the OAM related terminology.
>=20
>    This section presents a comparison of the terms used in various OAM
>    standards, without fully quoting the definition of each term. For a
>    formal definition of each term, refer to the references at the end =
of
>    this document.
>=20
> 2.2.2. OAM Maintenance Entities
>=20
>    OAM tools are designed to monitor and manage a Maintenance Entity
>    (ME).  An ME, as defined in [TP-OAM-FW], defines a relationship
>    between two points of a transport path to which maintenance and
>    monitoring operations apply.
>=20
>    The following related terms are also quoted from [TP-OAM-FW]:
>=20
>    o MEP: The two points that define a maintenance entity.
>=20
>    o MEG: The collection of one or more MEs that belongs to the same
>       transport path and that are maintained and monitored as a group
>       are known as a Maintenance Entity Group (MEG).
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 13]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    o MIP: In between MEPs, there are zero or more intermediate points,
>       called Maintenance Entity Group Intermediate Points (MIPs).
>=20
>    A pair of MEPs engaged in an ME are connected by a communication
>    link, which may be one of several types of connection, e.g. a =
single
>    physical connection, a set of physical connections, or a virtual =
link
>    such as an MPLS LSP.
>=20
>    The term Maintenance Entity (ME) is used in ITU-T Recommendations
>    (e.g. [ITU-T-Y1731]), as well as in the MPLS-TP terminology =
([TP-OAM-
>    FW]). Various terms are used to refer to an ME. For example, BFD =
does
>    not explicitly use a term that is equivalent to ME, but rather uses
>    the term "session", referring to the relationship between two nodes
>    using a BFD protocol. The MPLS LSP Ping ([LSP-Ping]) terminology
>    simply uses the term "LSP" in this context.
>=20
>    MPLS-TP has defined the terms ME and Maintenance Entity Group (MEG)
>    in [TP-OAM-FW], similar to the terms defined by ITU-T.  A MEG =
allows
>    the monitoring of a compound set of MEs, for example when =
monitoring
>    a p2mp MEG that is considered to be the set of MEs between the root
>    and each individual destination MEP.
>=20
> 2.2.3. OAM Maintenance Points
>=20
>    A Maintenance Point (MP) is a functional entity that is defined at =
a
>    node in the network, and either initiates or reacts to OAM =
messages.
>    A Maintenance End Point (MEP) is one of the end points of an ME, =
and
>    can initiate OAM messages and respond to them. A Maintenance
>    Intermediate Point (MIP) is an intermediate point between two MEPs,
>    that does not generally initiate OAM frames (one exception to this =
is
>    the use of AIS notifications), but is able to respond to OAM frames
>    that are destined to it. A MIP in MPLS-TP identifies OAM packets
>    destined to it by the value of the TTL field in the OAM packet. The
>    term Maintenance Point is a general term for MEPs and MIPs.
>=20
>    The 802.1ag defines a finer distinction between Up MPs and Down =
MPs.
>    An MP is a bridge interface, that is monitored by an OAM protocol
>    either in the direction facing the network, or in the direction
>    facing the bridge. A Down MP is an MP that receives OAM packets =
from,
>    and transmits them to the direction of the network. An Up MP =
receives
>    OAM packets from, and transmits them to the direction of the =
bridging
>    entity.
>=20
>    MPLS-TP ([TP-OAM-FW]) uses a similar distinction on the placement =
of
>    the MP - either at the ingress, egress, or forwarding function of =
the
>    node (Down / Up MPs).  This placement is important for localization
>    of a connection failure.
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 14]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> 2.2.4. Proactive and On-demand activation
>=20
>    The different OAM tools may be used in one of two basic types of
>    activation:
>=20
>    o Proactive activation - indicates that the tool is activated on a
>       continual basis periodically, where messages are sent between =
the
>       two MEPs, and errors are detected when a certain number of
>       expected messages are not received.
>=20
>    o On-demand activation - indicates that the tool is activated
>       "manually" to detect a specific anomaly.  In this activation a
>       small number of OAM messages are sent by a MEP and the reply
>       message is received.
>=20
> 2.2.5. Connectivity Verification and Continuity Checks
>=20
>    Two distinct classes of failure management functions are used in =
OAM
>    protocols, connectivity verification and continuity checks. The
>    distinction between these terms is defined in [MPLS-TP-OAM], and is
>    used similarly in this document.
>=20
>    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.
>=20
>    A connectivity verification function allows an MP to check whether =
it
>    is connected to a peer MP or not. This function also allows the MP =
to
>    verify that messages from the peer MP are received through the
>    correct path, thereby verifying not only that the two MPs are
>    connected, but also that they are connected through the expected
>    path. This allows detection of unexpected topology changes. A
>    connectivity verification (CV) protocol typically uses a CV =
message,
>    followed by a CV reply that is sent back to the originator. A CV
>    function can be applied proactively or on-demand.
>=20
>    Connectivity verification and continuity checks are considered
>    complementary mechanisms, and are often used in conjunction with =
each
>    other.
>=20
> 2.2.6. Failures
>=20
>    The terms Failure, Fault, and Defect are used interchangeably in =
the
>    standards, referring to a malfunction that can be detected by a
>    connectivity or a continuity check. In some standards, such as
>    [IEEE802.1ag], there is no distinction between these terms, while =
in
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 15]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    other standards each of these terms refers to a different type of
>    malfunction.
>=20
>    The terminology used in IETF MPLS-TP OAM takes after the ITU-T, =
which
>    distinguishes between these terms in [ITU-T-G.806]; The term Fault
>    refers to an inability to perform a required action, e.g., an
>    unsuccessful attempt to deliver a packet. The term Defect refers to
>    an interruption in the normal operation, such as a consecutive =
period
>    of time where no packets are delivered successfully. The term =
Failure
>    refers to the termination of the required function. While a Defect
>    typically refers to a limited period of time, a failure refers to a
>    long period of time.
>=20
> 3. OAM Tools
>=20
> 3.1. IP Ping and Traceroute
>=20
> 3.1.1. Ping
>=20
>    Ping is a common network diagnosis application for IP networks that
>    uses ICMP. The ICMP Echo request/reply exchange is a connectivity
>    verification function for the Internet Protocol. The originator
>    transmits an ICMP Echo request packet, and the receiver replies =
with
>    an Echo reply. ICMP ping is defined in two variants, [ICMPv4] is =
used
>    for IPv4, and [ICMPv6] is used for IPv6.
>=20
> 3.1.2. Traceroute
>=20
>    Traceroute ([TCPIP-Tools], [NetTools]) is an application that =
allows
>    users to discover the path between an IP source and an IP
>    destination. Traceroute sends a sequence of UDP packets to UDP port
>    33434 at the destination. By default, Traceroute begins by sending
>    three packets (the number of packets is configurable in most
>    Traceroute implementations), each with an IP Time-To-Live (TTL) =
value
>    of one to the destination. These packets expire as soon as they =
reach
>    the first router in the path. That router responds by sending three
>    ICMP Time Exceeded Messages to the Traceroute application. =
Traceroute
>    now sends another three UDP packets, each with the TTL value of 2.
>    These messages cause the second router to return ICMP messages. =
This
>    process continues, with ever increasing values for the TTL field,
>    until the packets actually reach the destination. Because no
>    application listens to port 33434 at the destination, the =
destination
>    returns ICMP Destination Unreachable Messages indicating an
>    unreachable port. This event indicates to the Traceroute =
application
>    that it is finished.  The Traceroute program displays the =
round-trip
>    delay associated with each of the attempts.
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 16]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    Note that IP routing may be asymmetric. While Traceroute reveals =
the
>    path between a source and destination, it may not reveal the =
reverse
>    path.
>=20
>    A few ICMP extensions ([ICMP-Ext], [ICMP-MP], [ICMP-Int]) have been
>    defined in the context of Traceroute. These extensions augment the
>    ICMP Destination Unreachable message, and can be used by Traceroute
>    applications.
>=20
> 3.2. Bidirectional Forwarding Detection (BFD)
>=20
> 3.2.1. Overview
>=20
>    While multiple OAM mechanisms have been defined for various =
protocols
>    in the protocol stack, Bidirectional Forwarding Detection [BFD],
>    defined by the IETF BFD working group, is a generic OAM mechanism
>    that can be deployed over various encapsulating protocols, and in
>    various medium types. The IETF has defined variants of the protocol
>    for IP ([BFD-IP], [BFD-Multi]), for MPLS LSPs [BFD-LSP], and for =
PWE3
>    [BFD-VCCV]. The usage of BFD in MPLS-TP is defined in [MPLS-TP-CC-
>    CV].
>=20
>    BFD includes two main OAM functions, using two types of BFD =
packets:
>    BFD Control packets, and BFD Echo packets.
>=20
> 3.2.2. BFD Control
>=20
>    BFD supports a bidirectional continuity check, using BFD control
>    packets, that are exchanged within a BFD session. BFD sessions
>    operate in one of two modes:
>=20
>    o Asynchronous mode (i.e. proactive): in this mode BFD control
>       packets are sent periodically. When the receiver detects that no
>       BFD control packet have been received during a predetermined
>       period of time, a failure is detected.
>=20
>    o Demand mode: in this mode, BFD control packets are sent =
on-demand.
>       Upon need, a system initiates a series of BFD control packets to
>       verify the liveness of the session. BFD control packets are sent
>       independently in each direction.
>=20
>    Each of the end-points of the monitored path maintains its own
>    session identification, called a Discriminator, both of which are
>    included in the BFD Control Packets that are exchanged between the
>    end-points.  At the time of session establishment, the =
Discriminators
>    are exchanged between the two-end points.  In addition, the
>    transmission (and reception) rate is negotiated between the two =
end-
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 17]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    points, based on information included in the control packets.  =
These
>    transmission rates may be renegotiated during the session.
>=20
>    During normal operation of the session, i.e. no failures are
>    detected, the BFD session is in the Up state.  If no BFD Control
>    packets are received during a fixed period of time, called the
>=20
> TOM: Fixed, pre-configured or negotiated period of time (i.e.: BFD =
interval)
>=20
>    Detection Time, the session is declared to be Down. The detection
>    time is a function of the negotiated transmission time, and a
>    parameter called Detect Mult. Detect Mult determines the number of
>    missing BFD Control packets that cause the session to be declared =
as
>    Down. This parameter is included in the BFD Control packet.
>=20
> 3.2.3. BFD Echo
>=20
>    A BFD echo packet is sent to a peer system, and is looped back to =
the
>    originator. The echo function can be used proactively, or =
on-demand.
>=20
>    The BFD echo function has been defined in BFD for IPv4 and IPv6
>    ([BFD-IP]), but is not used in BFD for MPLS LSPs, PWs, or in BFD =
for
>    MPLS-TP.
>=20
> 3.3. MPLS OAM
>=20
>    The IETF MPLS working group has defined OAM for MPLS LSPs. The
>    requirements and framework of this effort are defined in [MPLS-OAM-
>    FW] and [MPLS-OAM], respectively. The corresponding OAM mechanism
>    defined, in this context, is LSP Ping [LSP-Ping].
>=20
>    LSP Ping is based on ICMP Ping and just like its predecessor may be
>    used in one of two modes:
>=20
>    o "Ping" mode: In this mode LSP ping is used for end-to-end
>       connectivity verification between two LERs.
>=20
>    o "Traceroute" mode: This mode is used for hop-by-hop fault
>       isolation.
>=20
>    LSP Ping extends the basic ICMP Ping operation (of data-plane
>    connectivity verification) with functionality to verify data-plane
>    vs. control-plane consistency for a Forwarding Equivalence Class
>    (FEC) and also Maximum Transmission Unit (MTU) problems. The
>    traceroute functionality may be used to isolate and localize the =
MPLS
>    faults, using the Time-to-live (TTL) indicator to incrementally
>    identify the sub-path of the LSP that is successfully traversed
>    before the faulty link or node.
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 18]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    It should be noted that LSP Ping supports unique identification of
>    the LSP within an addressing domain. The identification is checked
>    using the full FEC identification. LSP Ping is easily extensible to
>    include additional information needed to support new functionality,
>    by use of Type-Length-Value (TLV) constructs. The usage of TLVs is
>    typically not easy to perform in hardware, and is thus typically
>    handled by the control plane.
>=20
>    LSP Ping supports both asynchronous, as well as, on-demand
>    activation.
>=20
> 3.4. MPLS-TP OAM
>=20
> 3.4.1. Overview
>=20
>    The MPLS working group is currently working on defining the OAM
>    toolset that fulfills the requirements for MPLS-TP OAM. The full =
set
>    of requirements for MPLS-TP OAM are defined in [MPLS-TP-OAM], and
>    include both general requirements for the behavior of the OAM
>    mechanisms and a set of operations that should be supported by the
>    OAM toolset.  The set of mechanisms required are further elaborated
>    in [TP-OAM-FW], which describes the general architecture of the OAM
>    system as well as giving overviews of the functionality of the OAM
>    toolset.
>=20
>    Some of the basic requirements for the OAM toolset for MPLS-TP are:
>=20
>    o MPLS-TP OAM must be able to support both an IP based and non-IP
>       based environment. If the network is IP based, i.e. IP routing =
and
>       forwarding are available, then the MPLS-TP OAM toolset should =
rely
>       on the IP routing and forwarding capabilities. On the other =
hand,
>       in environments where IP functionality is not available, the OAM
>       tools must still be able to operate without dependence on IP
>       forwarding and routing.
>=20
>    o OAM packets and the user traffic are required to be congruent
>       (i.e. OAM packets are transmitted in-band) and there is a need =
to
>       differentiate OAM packets from user-plane ones. Inherent in this
>       requirement is the principle that MPLS-TP OAM be independent of
>       any existing control-plane, although it should not preclude use =
of
>       the control-plane functionality.
>=20
> 3.4.2. Generic Associated Channel
>=20
>    In order to address the requirement for in-band transmission of =
MPLS-
>    TP OAM traffic, MPLS-TP uses a Generic Associated Channel (G-ACh),
>    defined in [G-ACh] for LSP-based OAM traffic. This mechanism is =
based
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 19]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    on the same concepts as the PWE3 ACH and VCCV mechanisms.  However,
>    to address the needs of LSPs as differentiated from PW, the =
following
>    concepts were defined for [G-ACh]:
>=20
>    o An Associated Channel Header (ACH), that uses a format similar to
>       the PW Control Word, is a 4-byte header that is prepended to OAM
>       packets.
>=20
>    o A Generic Associated Label (GAL). The GAL is a reserved MPLS =
label
>       value (13) that indicates that the packet is an ACH packet and =
the
>       payload follows immediately after the label stack.
>=20
> 3.4.3. MPLS-TP OAM Toolset
>=20
>    To address the functionality that is required of the OAM toolset, =
the
>    MPLS WG conducted an analysis of the existing IETF and ITU-T OAM
>    mechanisms and their ability to fulfill the required functionality.
>    The conclusions of this analysis are documented in [OAM-Analys]. =
The
>    MPLS working group currently plans to use a mixture of OAM =
mechanisms
>    that are based on various existing standards, and adapt them to the
>    requirements of [MPLS-TP-OAM]. Some of the main building blocks of
>    this solution are based on:
>=20
>    o Bidirectional Forwarding Detection ([BFD], [BFD-LSP]) for
>       proactive continuity check and connectivity verification.
>=20
>    o LSP Ping as defined in [LSP-Ping] for on-demand connectivity
>       verification.
>=20
>    o New protocol packets, using G-ACH, to address different
>       functionality.
>=20
>    o Performance measurement protocols that are based on the
>       functionality that is described in [ITU-T-Y1731].
>=20
>    The following sub-sections describe the OAM tools defined for =
MPLS-TP
>    as described in [TP-OAM-FW].
>=20
> 3.4.3.1. Continuity Check and Connectivity Verification
>=20
>    Continuity Check and Connectivity Verification are presented in
>    Section 2.2.5. of this document.  As presented there, these tools =
may
>    be used either proactively or on-demand.  When using these tools
>    proactively, they are generally used in tandem.
>=20
>    For MPLS-TP there are two distinct tools, the proactive tool is
>    defined in [TP-CC-CV] while the on-demand tool is defined in
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 20]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    [OnDemand-CV].Proactively [MPLS-TP-OAM] states that the function
>    should allow the MEPs to monitor the liveness and connectivity of a
>    transport path. In on-demand mode, this function should support
>    monitoring between the MEPs and, in addition, between a MEP and =
MIP.
>    [TP-OAM-FW] highlights,  when performing Connectivity Verification,
>    the need for the CC-V messages to include unique identification of
>    the MEG that is being monitored and the MEP that originated the
>    message.
>=20
>    The proactive tool [TP-CC-CV] is based on extensions to BFD (see
>    Section 3.2. ) with the additional limitation that the transmission
>    and receiving rates are based on configuration by the operator.  =
The
>    on-demand tool [OnDemand-CV] is an adaptation of LSP Ping (see
>    Section 3.3. ) for the required behavior of MPLS-TP.
>=20
> 3.4.3.2. Route Tracing
>=20
>    [MPLS-TP-OAM] defines that there is a need for functionality that
>    would allow a path end-point to identify the intermediate and end-
>    points of the path. This function would be used in on-demand mode.
>    Normally, this path will be used for bidirectional PW, LSP, and
>    sections, however, unidirectional paths may be supported only if a
>    return path exists.  The tool for this is based on the LSP Ping =
(see
>    Section 3.3. ) functionality and is described in [OnDemand-CV].
>=20
> 3.4.3.3. Lock Instruct
>=20
>    The Lock Instruct function [Lock-Loop] is used to notify a =
transport
>    path end-point of an administrative need to disable the transport
>    path.  This functionality will generally be used in conjunction =
with
>    some intrusive OAM function, e.g. Performance measurement, =
Diagnostic
>    testing, to minimize the side-effect on user data traffic.
>=20
> 3.4.3.4. Lock Reporting
>=20
>    Lock Reporting is a function used by an end-point of a path to =
report
>    to its far-end end-point that a lock condition has been affected on
>    the path.
>=20
> 3.4.3.5. Alarm Reporting
>=20
>    Alarm Reporting is a function used by an intermediate point of a
>    path, that becomes aware of a fault on the path, to report to the
>    end-points of the path. [TP-OAM-FW] states that this may occur as a
>    result of a defect condition discovered at a server sub-layer. This
>    generates an Alarm Indication Signal (AIS) that continues until the
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 21]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    fault is cleared. The consequent action of this function is =
detailed
>    in [TP-OAM-FW].
>=20
> 3.4.3.6. Remote Defect Indication
>=20
>    Remote Defect Indication (RDI) is used proactively by a path end-
>    point to report to its peer end-point that a defect is detected on =
a
>    bidirectional connection between them. [MPLS-TP-OAM] points out =
that
>    this function may be applied to a unidirectional LSP only if there =
a
>    return path exists.  [TP-OAM-FW] points out that this function is
>    associated with the proactive CC-V function.
>=20
> 3.4.3.7. Client Failure Indication
>=20
>    Client Failure Indication (CFI) is defined in [MPLS-TP-OAM] to =
allow
>    the propagation information from one edge of the network to the
>    other. The information concerns a defect to a client, in the case
>    that the client does not support alarm notification.
>=20
> 3.4.3.8. Packet Loss Measurement (LM)
>=20
>    Packet Loss Measurement is a function used to verify the quality of
>    the service. This function indicates the ratio of packets that are
>    not delivered out of all packets that are transmitted by the path
>    source.
>=20
>    There are two possible ways of determining this measurement:
>=20
>    o Using OAM packets, it is possible to compute the statistics based
>       on a series of OAM packets. This, however, has the disadvantage =
of
>       being artificial, and may not be representative since part of =
the
>       packet loss may be dependent upon packet sizes.
>=20
> TOM: Not just packet sizes. Things like implementation (as I mentioned =
above with the comment about the accuracy or truthfulness of the data =
plane processing of OAM packets).  Doing very accurate RTT as a simple =
example, with just IP Pings, is a tricky thing to make work.  Also, it =
is important to mention that the scale in terms of number of packets, =
number of tests, etc=85 can and will impact these parameters too.
>=20
>=20
>    o Sending delimiting messages for the start and end of a =
measurement
>       period during which the source and sink of the path count the
>       packets transmitted and received. After the end delimiter, the
>       ratio would be calculated by the path OAM entity.
>=20
> 3.4.3.9. Packet Delay Measurement (DM)
>=20
>    Packet Delay Measurement is a function that is used to measure one-
>    way or two-way delay of a packet transmission between a pair of the
>    end-points of a path (PW, LSP, or Section). Where:
>=20
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 22]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    o One-way packet delay is the time elapsed from the start of
>       transmission of the first bit of the packet by a source node =
until
>       the reception of the last bit of that packet by the destination
>       node.
>=20
>    o Two-way packet delay is the time elapsed from the start of
>       transmission of the first bit of the packet by a source node =
until
>       the reception of the last bit of the loop-backed packet by the
>       same source node, when the loopback is performed at the packet's
>       destination node.
>=20
>    Similarly to the packet loss measurement this could be performed in
>    either of the two ways outlined above.
>=20
> 3.5. PWE3 OAM
>=20
> 3.5.1. PWE3 OAM using Virtual Circuit Connectivity Verification (VCCV)
>=20
>    VCCV, as defined in [VCCV], provides a means for end-to-end fault
>    detection and diagnostics tools to be extended for PWs (regardless =
of
>    the underlying tunneling technology). The VCCV switching function
>    provides a control channel associated with each PW (based on the PW
>    Associated Channel Header (ACH) which is defined in [PW-ACH]), and
>    allows transmitting the OAM packets in-band with PW data (using CC
>    Type 1: In-band VCCV).
>=20
>    VCCV currently supports the following OAM mechanisms: ICMP Ping, =
LSP
>    Ping, and BFD. ICMP and LSP Ping are IP encapsulated before being
>    sent over the PW ACH. BFD for VCCV [BFD-VCCV] supports two modes of
>    encapsulation - either IP/UDP encapsulated (with IP/UDP header) or
>    PW-ACH encapsulated (with no IP/UDP header) and provides support to
>    signal the AC status. The use of the VCCV control channel provides
>    the context, based on the MPLS-PW label, required to bind and
>    bootstrap the BFD session to a particular pseudo wire (FEC),
>    eliminating the need to exchange Discriminator values.
>=20
>    VCCV consists of two components: (1) signaled component to
>    communicate VCCV capabilities as part of VC label, and (2) =
switching
>    component to cause the PW payload to be treated as a control =
packet.
>=20
>    VCCV is not directly dependent upon the presence of a control =
plane.
>    The VCCV capability negotiation may be performed as part of the PW
>    signaling when LDP is used. In case of manual configuration of the
>    PW, it is the responsibility of the operator to set consistent
>    options at both ends.
>=20
> TOM: Might be helpful to note that the static mode was created =
specifically to handle the MPLS-TP cases where no control plane was a =
requirement. However, new use cases such as pure mobile backhaul, etc=85 =
find this functionality useful too.
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 23]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> 3.5.2. PWE3 OAM using G-ACh
>=20
>    As mentioned above, VCCV enables OAM for PWs by using a control
>    channel for OAM packets. When PWs are used in MPLS-TP networks,
>    rather than the control channels defined in VCCV, the G-ACh can be
>    used as an alternative control channel. The usage of the G-ACh for
>    PWs is defined in [PW-G-ACh].
>=20
> 3.6. OWAMP and TWAMP
>=20
> 3.6.1. Overview
>=20
>    The IPPM working group in the IETF defines common criteria and
>    metrics for measuring performance of IP traffic ([IPPM-FW]). Some =
of
>    the key RFCs published by this working group have defined metrics =
for
>    measuring connectivity [IPPM-Con], delay ([IPPM-1DM], [IPPM-2DM]),
>    and packet loss [IPPM-1LM].
>=20
>    Alternative protocols for performance measurement are defined, for
>    example, in MPLS-TP OAM ([MPLS-LM-DM], [TP-LM-DM]), and in Ethernet
>    OAM [ITU-T-Y1731].
>=20
>    The IPPM working group has defined not only metrics for performance
>    measurement, but also protocols that define how the measurement is
>    carried out. The One-way Active Measurement Protocol [OWAMP] and =
the
>    Two-Way Active Measurement Protocol [TWAMP] define a method and
>    protocol for measuring delay and packet loss in IP networks.
>=20
>    OWAMP [OWAMP] enables measurement of one-way characteristics of IP
>    networks, such as one-way packet loss and one-way delay.  For its
>    proper operation OWAMP requires accurate time of day setting at its
>    end points.
>=20
>    TWAMP [TWAMP] is a similar protocol that enables measurement of =
two-
>    way (round trip) characteristics.  TWAMP does not require accurate
>    time of day, and, furthermore, allows the use of a simple session
>    reflector, making it an attractive alternative to OWAMP.
>=20
>    OWAMP and TWAMP use two separate protocols: a Control plane =
protocol,
>    and a Test plane protocol.
>=20
> 3.6.2. Control and Test Protocols
>=20
>    OWAMP and TWAMP control protocols run over TCP, while the test
>    protocols run over UDP.  The purpose of the control protocols is to
>    initiate, start, and stop test sessions, and for OWAMP to fetch
>    results.  The test protocols introduce test packets (which contain
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 24]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    sequence numbers and timestamps) along the IP path under test
>    according to a schedule, and record statistics of packet arrival.
>    Multiple sessions may be simultaneously defined, each with a =
session
>    identifier, and defining the number of packets to be sent, the =
amount
>    of padding to be added (and thus the packet size), the start time,
>    and the send schedule (which can be either a constant time between
>    test packets or exponentially distributed pseudo-random). =
Statistics
>    recorded conform to the relevant IPPM RFCs.
>=20
>    OWAMP and TWAMP test traffic is designed with security in mind.  =
Test
>    packets are hard to detect because they are simply UDP streams
>    between negotiated port numbers, with potentially nothing static in
>    the packets.  OWAMP and TWAMP also include optional authentication
>    and encryption for both control and test packets.
>=20
> 3.6.3. OWAMP
>=20
>    OWAMP defines the following logical roles: Session-Sender, Session-
>    Receiver, Server, Control-Client, and Fetch-Client.  The Session-
>    Sender originates test traffic that is received by the Session-
>    Receiver.  The Server configures and manages the session, as well =
as
>    returning the results.  The Control-Client initiates requests for
>    test sessions, triggers their start, and may trigger their
>    termination.  The Fetch-Client requests the results of a completed
>    session.  Multiple roles may be combined in a single host - for
>    example, one host may play the roles of Control-Client, =
Fetch-Client,
>    and Session-Sender, and a second playing the roles of Server and
>    Session-Receiver.
>=20
>    In a typical OWAMP session the Control-Client establishes a TCP
>    connection to port 861 of the Server, which responds with a server
>    greeting message indicating supported security/integrity modes. The
>    Control-Client responds with the chosen communications mode and the
>    Server accepts the modes.  The Control-Client then requests and =
fully
>    describes a test session to which the Server responds with its
>    acceptance and supporting information.  More than one test session
>    may be requested with additional messages.  The Control-Client then
>    starts a test session and the Server acknowledges.  The Session-
>    Sender then sends test packets with pseudorandom padding to the
>    Session-Receiver until the session is complete or until the =
Control-
>    client stops the session.  Once finished, the Fetch-Client sends a
>    fetch request to the server, which responds with an acknowledgement
>    and immediately thereafter the result data.
>=20
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 25]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> 3.6.4. TWAMP
>=20
>    TWAMP defines the following logical roles: session-sender, session-
>    reflector, server, and control-client.  These are similar to the
>    OWAMP roles, except that the Session-Reflector does not collect any
>    packet information, and there is no need for a Fetch-Client.
>=20
>    In a typical TWAMP session the Control-Client establishes a TCP
>    connection to port 862 of the Server, and mode is negotiated as in
>    OWAMP.  The Control-Client then requests sessions and starts them.
>    The Session-Sender sends test packets with pseudorandom padding to
>    the Session-Reflector which returns them with insertion of
>    timestamps.
>=20
> 3.7. Summary of OAM Functions
>=20
>    Table 3 summarizes the OAM functions that are supported in each of
>    the categories that were analyzed in this section.
>=20
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
>    | Standard  |Continu|Connecti|Path    |Defect     |Perform|Other   =
|
>    |           |ity    |vity    |Discover|Indications|ance   =
|Function|
>    |           |Check  |Verifica|y       |           |Monitor|s       =
|
>    |           |       |tion    |        |           |ing    |        =
|
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
>    |IP Ping    |       |Echo    |        |           |       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |IP         |       |        |Tracerou|           |       |        =
|
>    |Traceroute |       |        |te      |           |       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |BFD        |BFD    |BFD     |        |           |       |        =
|
>    |           |Control|Echo    |        |           |       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |MPLS OAM   |       |"Ping"  |"Tracero|           |       |        =
|
>    |(LSP Ping) |       |mode    |ute"    |           |       |        =
|
>    |           |       |        |mode    |           |       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |MPLS-TP    |CC     |CV/pro- |Route   |-Alarm     |-LM    =
|-Diagnos|
>    |OAM        |       |active  |Tracing | Reporting |-DM    | tic =
Tes|
>    |           |       |or on-  |        |-Client    |       | t      =
|
>    |           |       |demand  |        | Failure   |       |-Lock   =
|
>    |           |       |        |        | Indication|       |        =
|
>    |           |       |        |        |-Remote    |       |        =
|
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 26]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    |           |       |        |        | Defect    |       |        =
|
>    |           |       |        |        | Indication|       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |PWE3 OAM   |BFD    |-BFD    |LSP-Ping|           |       |        =
|
>    |           |       |-ICMP   |        |           |       |        =
|
>    |           |       | Ping   |        |           |       |        =
|
>    |           |       |-LSP-   |        |           |       |        =
|
>    |           |       | Ping   |        |           |       |        =
|
>    + --------- + ----- + ------ + ------ + --------- + ----- + ------ =
+
>    |OWAMP and  |       |        |        |           |-Delay |        =
|
>    |TWAMP      |       |        |        |           | measur|        =
|
>    |           |       |        |        |           | ement |        =
|
>    |           |       |        |        |           |-Packet|        =
|
>    |           |       |        |        |           | loss  |        =
|
>    |           |       |        |        |           | measur|        =
|
>    |           |       |        |        |           | ement |        =
|
>    =
+-----------+-------+--------+--------+-----------+-------+--------+
>                      Table 3 Summary of OAM Functions
>=20
> 4. Security Considerations
>=20
>    This memo presents an overview of existing OAM mechanisms, and
>    proposes no new OAM mechanisms. Therefore, this document introduces
>    no security considerations. However, the OAM mechanism reviewed in
>    this document can and do present security issues. The reader is
>    encouraged to review the Security Considerations section of each
>    document reference by this memo.
>=20
> 5. IANA Considerations
>=20
>    There are no new IANA considerations implied by this document.
>=20
> 6. Acknowledgments
>=20
>    The authors gratefully acknowledge Sasha Vainshtein, Carlos
>    Pignataro, David Harrington, Dan Romascanu, Ron Bonica and other
>    members of the OPSAWG mailing list for their helpful comments.
>=20
>    This document was prepared using 2-Word-v2.0.template.dot.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 27]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
> 7. References
>=20
> 7.1. Normative References
>=20
>    [LSP-Ping]    Kompella, K., Swallow, G., "Detecting Multi-Protocol
>                  Label Switched (MPLS) Data Plane Failures", RFC 4379,
>                  February 2006.
>=20
>    [MPLS-OAM]    Nadeau, T., Morrow, M., Swallow, G., Allan, D.,
>                  Matsushima, S., "Operations and Management (OAM)
>                  Requirements for Multi-Protocol Label Switched (MPLS)
>                  Networks", RFC 4377, February 2006.
>=20
>    [MPLS-OAM-FW] Allan, D., Nadeau, T., "A Framework for =
Multi-Protocol
>                  Label Switching (MPLS) Operations and Management
>                  (OAM)", RFC 4378, February 2006.
>=20
>    [OAM-Label]   Ohta, H., "Assignment of the 'OAM Alert Label' for
>                  Multiprotocol Label Switching Architecture (MPLS)
>                  Operation and Maintenance (OAM) Functions", RFC 3429,
>                  November 2002.
>=20
>    [MPLS-TP-OAM] Vigoureux, M., Ward, D., Betts, M., "Requirements for
>                  OAM in MPLS Transport Networks", RFC 5860, May 2010.
>=20
>    [G-ACh]       Bocci, M., Vigoureux, M., Bryant, S., "MPLS Generic
>                  Associated Channel", RFC 5586, June 2009.
>=20
>    [VCCV]        Nadeau, T., Pignataro, C., "Pseudowire Virtual =
Circuit
>                  Connectivity Verification (VCCV): A Control Channel
>                  for Pseudowires", RFC 5085, December 2007.
>=20
>    [PW-ACH]      Bryant, S., Swallow, G., Martini, L., McPherson, D.,
>                  "Pseudowire Emulation Edge-to-Edge (PWE3) Control =
Word
>                  for Use over an MPLS PSN", RFC 4385, February 2006.
>=20
>    [ICMPv4]      Postel, J., "Internet Control Message Protocol", STD =
5,
>                  RFC 792, September 1981.
>=20
>    [ICMPv6]      Conta, A., Deering, S., and M. Gupta, "Internet =
Control
>                  Message Protocol (ICMPv6) for the Internet Protocol
>                  Version 6 (IPv6) Specification", RFC 4443, March =
2006.
>=20
>    [MPLS-P2MP]   Yasukawa, S., Farrel, A., King, D., Nadeau, T.,
>                  "Operations and Management (OAM) Requirements for
>                  Point-to-Multipoint MPLS Networks", RFC 4687,
>                  September 2006.
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 28]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    [ICMP-Ext]    Bonica, R., Gan, D., Tappan, D., Pignataro, C., "ICMP
>                  Extensions for Multiprotocol Label Switching", RFC
>                  4950, August 2007.
>=20
>    [ICMP-MP]     Bonica, R., Gan, D., Tappan, D., Pignataro, C.,
>                  "Extended ICMP to Support Multi-Part Messages", RFC
>                  4884, April 2007.
>=20
>    [ICMP-Int]    Atlas, A., Bonica, R., Pignataro, C., Shen, N., =
Rivers,
>                  JR., "Extending ICMP for Interface and Next-Hop
>                  Identification", RFC 5837, April 2010.
>=20
>    [TCPIP-Tools] Kessler, G., Shepard, S., "A Primer On Internet and
>                  TCP/IP Tools and Utilities", RFC 2151, June 1997.
>=20
>    [NetTools]    Stine, R., "FYI on a Network Management Tool Catalog:
>                  Tools for Monitoring and Debugging TCP/IP Internets
>                  and Interconnected Devices", RFC 1147, April 1990.
>=20
>    [IPPM-FW]     Paxson, V., Almes, G., Mahdavi, J., and Mathis, M.,
>                  "Framework for IP Performance Metrics", RFC 2330, May
>                  1998.
>=20
>    [IPPM-Con]    Mahdavi, J., Paxson, V., "IPPM Metrics for Measuring
>                  Connectivity", RFC 2678, September 1999.
>=20
>    [IPPM-1DM]    Almes, G., Kalidindi, S., Zekauskas, M., "A One-way
>                  Delay Metric for IPPM", RFC 2679, September 1999.
>=20
>    [IPPM-1LM]    Almes, G., Kalidindi, S., Zekauskas, M., "A One-way
>                  Packet Loss Metric for IPPM", RFC 2680, September
>                  1999.
>=20
>    [IPPM-2DM]    Almes, G., Kalidindi, S., Zekauskas, M., "A =
Round-trip
>                  Delay Metric for IPPM", RFC 2681, September 1999.
>=20
>    [OWAMP]       Shalunov, S., Teitelbaum, B., Karp, A., Boote, J., =
and
>                  Zekauskas, M., "A One-way Active Measurement Protocol
>                  (OWAMP)", RFC 4656, September 2006.
>=20
>    [TWAMP]       Hedayat, K., Krzanowski, R., Morton, A., Yum, K., and
>                  Babiarz, J., "A Two-Way Active Measurement Protocol
>                  (TWAMP)", RFC 5357, October 2008.
>=20
>    [BFD]         Katz, D., Ward, D., "Bidirectional Forwarding =
Detection
>                  (BFD)", RFC 5880, June 2010.
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 29]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    [BFD-IP]      Katz, D., Ward, D., "Bidirectional Forwarding =
Detection
>                  (BFD) for IPv4 and IPv6 (Single Hop)", RFC 5881, June
>                  2010.
>=20
>    [BFD-Gen]     Katz, D., Ward, D., "Generic Application of
>                  Bidirectional Forwarding Detection (BFD)", RFC 5882,
>                  June 2010.
>=20
>    [BFD-Multi]   Katz, D., Ward, D., "Bidirectional Forwarding =
Detection
>                  (BFD) for Multihop Paths", RFC 5883, June 2010.
>=20
>    [BFD-LSP]     Aggarwal, R., Kompella, K., Nadeau, T., and Swallow,
>                  G., "Bidirectional Forwarding Detection (BFD) for =
MPLS
>                  Label Switched Paths (LSPs)", RFC 5884, June 2010.
>=20
>    [BFD-VCCV]    Nadeau, T., Pignataro, C., "Bidirectional Forwarding
>                  Detection (BFD) for the Pseudowire Virtual Circuit
>                  Connectivity Verification (VCCV)", RFC 5885, June
>                  2010.
>=20
>    [TP-OAM-FW]   Busi, I., Allan, D., "Operations, Administration and
>                  Maintenance Framework for MPLS-based Transport
>                  Networks ", RFC 6371, September 2011.
>=20
>    [TP-CC-CV]    Allan, D., Swallow, G., Drake, J., "Proactive
>                  Connectivity Verification, Continuity Check and =
Remote
>                  Defect indication for MPLS Transport Profile", RFC
>                  6428, November 2011.
>=20
>    [OnDemand-CV] Gray, E., Bahadur, N., Boutros, S., Aggarwal, R. =
"MPLS
>                  On-Demand Connectivity Verification and Route
>                  Tracing", RFC 6426, November 2011.
>=20
>    [MPLS-LM-DM]  Frost, D., Bryant, S., "Packet Loss and Delay
>                  Measurement for MPLS Networks", RFC 6374, September
>                  2011.
>=20
>    [TP-LM-DM]    Frost, D., Bryant, S., "A Packet Loss and Delay
>                  Measurement Profile for MPLS-Based Transport
>                  Networks", RFC 6375, September 2011.
>=20
>    [TP-Fault]    Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, =
S.,
>                  "MPLS Fault Management Operations, Administration, =
and
>                  Maintenance (OAM)", RFC 6427, November 2011.
>=20
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 30]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    [Lock-Loop]   Boutros, S., Sivabalan, S., Aggarwal, R., Vigoureux,
>                  M., Dai, X., "MPLS Transport Profile Lock Instruct =
and
>                  Loopback Functions", RFC 6435, November 2011.
>=20
>    [ITU-T-CT]    Betts, M., "Allocation of a Generic Associated =
Channel
>                  Type for ITU-T MPLS Transport Profile Operation,
>                  Maintenance, and Administration (MPLS-TP OAM)", RFC
>                  6671, November 2012.
>=20
>    [PW-Map]      M. Aissaoui, P. Busschbach, L. Martini, M. Morrow, T.
>                  Nadeau, "Pseudowire (PW) Operations, Administration,
>                  and Maintenance (OAM) Message Mapping", RFC 6310, =
July
>                  2011.
>=20
>    [PW-G-ACh]    Li, H., Martini, L., He, J., Huang, F., "Using the
>                  Generic Associated Channel Label for Pseudowire in =
the
>                  MPLS Transport Profile (MPLS-TP)", RFC 6423, November
>                  2011.
>=20
> 7.2. Informative References
>=20
>    [OAM-Def]     Andersson, L., Van Helvoort, H., Bonica, R., =
Romascanu,
>                  D., Mansfield, S., "Guidelines for the use of the OAM
>                  acronym in the IETF ", RFC 6291, June 2011.
>=20
>    [OAM-Analys]  Sprecher, N., Fang, L., "An Overview of the OAM Tool
>                  Set for  MPLS based Transport Networks", RFC 6669,
>                  July 2012.
>=20
>    [TP-Term]     Van Helvoort, H., Andersson, L., Sprecher, N., "A
>                  Thesaurus for the Terminology used in Multiprotocol
>                  Label Switching Transport Profile (MPLS-TP)
>                  drafts/RFCs and ITU-T's Transport Network
>                  Recommendations", work-in-progress, draft-ietf-mpls-
>                  tp-rosetta-stone, July 2012.
>=20
>    [IEEE802.1ag] IEEE 802.1Q, "IEEE Standard for Local and =
metropolitan
>                  area networks - Media Access Control (MAC) Bridges =
and
>                  Virtual Bridged Local Area Networks", October 2012.
>=20
>    [ITU-T-Y1731] ITU-T Recommendation G.8013/Y.1731, "OAM Functions =
and
>                  Mechanisms for Ethernet-based Networks", July 2011.
>=20
>    [ITU-T-Y1711] ITU-T Recommendation Y.1711, "Operation & Maintenance
>                  mechanism for MPLS networks", February 2004.
>=20
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 31]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    [IEEE802.3ah] IEEE 802.3, "IEEE Standard for Information technology =
-
>                  Local and metropolitan area networks - Carrier sense
>                  multiple access with collision detection (CSMA/CD)
>                  access method and physical layer specifications",
>                  clause 57, December 2008.
>=20
>    [ITU-T-G.806] ITU-T Recommendation G.806, "Characteristics of
>                  transport equipment - Description methodology and
>                  generic functionality", January 2009.
>=20
>    [ITU-G8113.2] ITU-T Recommendation G.8113.2/Y.1372.2, "Operations,
>                  administration and maintenance mechanisms for MPLS-TP
>                  networks using the tools defined for MPLS", November
>                  2012.
>=20
>    [ITU-G8113.1] ITU-T Recommendation G.8113.1/Y.1372.1, "Operations,
>                  Administration and Maintenance mechanism for MPLS-TP
>                  in Packet Transport Network (PTN)", November 2012.
>=20
>=20
>=20
> Authors' Addresses
>=20
>    Tal Mizrahi
>    Marvell
>    6 Hamada St.
>    Yokneam, 20692
>    Israel
>=20
>    Email: talmi@marvell.com
>=20
>=20
>    Nurit Sprecher
>    Nokia Siemens Networks
>    3 Hanagar St. Neve Ne'eman B
>    Hod Hasharon,   45241
>    Israel
>=20
>    Email: nurit.sprecher@nsn.com
>=20
>=20
>    Elisa Bellagamba
>    Ericsson
>    6 Farogatan St.
>    Stockholm,   164 40
>    Sweden
>=20
>=20
>=20
> Mizrahi, et al.         Expires July 9, 2013                 [Page 32]
> Internet-Draft       Overview of OAM Mechanisms           January 2013
>=20
>=20
>    Phone: +46 761440785
>    Email: elisa.bellagamba@ericsson.com
>=20
>=20
>    Yaacov Weingarten
>    34 Hagefen St.
>    Karnei Shomron,   4485500
>    Israel
>=20
>    Email: wyaacov@gmail.com
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>> draft-ietf-opsawg-oam-overview authors,
>>=20
>> Here is my feedback on this document.
>>=20
>> 1.
>> Is this document in line with =
http://tools.ietf.org/html/draft-ietf-trill-oam-req-04?=20
>> * For example, the following definitions could be reused.
>>    Fault: The term Fault refers to an inability to perform a required
>>    action, e.g., an unsuccessful attempt to deliver a packet.
>>=20
>>    Defect: The term Defect refers to an interruption in the normal
>>    operation, such that over a period of time no packets are =
delivered
>>    successfully.
>>=20
>>    Failure: The term Failure refers to the termination of the =
required
>>    function over a longer period of time. Persistence of a defect for =
a
>>    period of time is interpreted as a failure.
>>=20
>> * For example, on the basic abstract=20
>> Abstract
>>=20
>>    Operations, Administration, and Maintenance (OAM) is a general =
term
>>    that refers to a toolset that can be used for fault detection and
>>    isolation, and for performance measurement. OAM mechanisms have =
been
>>    defined for various layers in the protocol stack, and are used =
with a
>>    variety of protocols.
>>=20
>> Abstract (draft-ietf-trill-oam-req-04)
>>=20
>>    OAM (Operations, Administration and Maintenance) is a general term
>>    used to identify functions and toolsets to troubleshoot and =
monitor
>>    networks. This document presents, OAM Requirements applicable to
>>    TRILL.=20
>>=20
>> So, as an example: does OAM include function?=20
>> I advice to review draft-ietf-trill-oam-req-04
>>=20
>> 2.=20
>> draft-ietf-trill-oam is not mentioned, while the abstract mentions:
>>    This document presents an overview of the OAM mechanisms that have
>>    been defined and are currently being defined by the IETF.
>> Search for OAM in the current draft names =
(https://datatracker.ietf.org/), and you will find many references.
>> Ok, I see later on:=09
>>    This document focuses on IETF
>>    documents that have been published as RFCs, while other ongoing =
OAM-
>>    related work is outside the scope.
>> Ok, fine then: we don't need a reference to all the drafts.=20
>> However, draft-ietf-trill-oam is closed to be a RFC, and should be =
mentioned.
>>=20
>>=20
>> 3.
>> Section 1
>>    The term OAM in this document refers to Operations, Administration
>>    and Maintenance [OAM-Def], focusing on the forwarding plane of =
OAM.
>> What does it mean "focusing on the forwarding plane of OAM"?
>> Do you take a subset of the definition for this document?
>> Btw, I don't see a definition in the terminology section.
>> In section 2.2.3
>>    A Maintenance Point (MP) is a functional entity that is defined at =
a
>>    node in the network, and either initiates or reacts to OAM =
messages.
>> Which plane is MP?
>>=20
>> 4.
>> Section 1, Introduction
>> "Hence, management aspects are outside the scope of this document."
>> I don't understand which management aspects we speak about here.
>> 5.
>> Clarifying question regarding 1.2
>> If speak about OWAMP or TWAMP 'synthetic traffic), is that data =
plane, control plane, or management plane?
>> Note that I found later on in the draft:
>>    OWAMP and TWAMP use two separate protocols: a Control plane =
protocol,
>>    and a Test plane protocol.
>> Interestingly enough, after reading the document, I reviewed =
http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/, =
and saw the same feedback from Stewart Bryant:
>> Provide a clear view of OAM functionality and its relationship
>> to various =93planes=94 of networking (data plane, control plane,
>> management plane). In particular, the importance of
>> fate-sharing of OAM and user traffic flows in packet networks
>> should be explained.
>> 6.
>> I see a multiplication of "plane" terms in the IETF document, and in =
this document in particular.
>> I could find: forwarding plane, management plane, control plane, data =
plane, user plane, and test plane.
>> Way too many.
>> Please be consistent
>> 7.
>>    Table 1 summarizes the IETF OAM related RFCs discussed in this
>>    document.
>>=20
>>    Table 2 summarizes the OAM standards mentioned in this document.=20=

>>=20
>> You need to change the Table 2 description. Do you want to say =
something along the lines of:
>>    Table 2 summarizes the OAM standards specified by other Standard =
Development Organization=20
>>    (SDO) than the IETF, along with IETF references where applicable.
>>=20
>>=20
>> 8.
>> Section 2.2.1
>>    For a formal definition of each term, refer to the references at =
the end of
>>    this document.
>> Without a reference to a specific RFC, this is the type of statement =
which is not useful: you have 5 pages of references.
>> You position this document as "An Overview of Operations, =
Administration, and Maintenance (OAM) Mechanisms", but you tell the =
reader: "if you want to know about the terms,
>> just read first all references!"
>>=20
>> 9.
>> You specify some terms and some OAM categories,=20
>>    2.2.2. OAM Maintenance Entities .......................... 13
>>          2.2.3. OAM Maintenance Points ............................ =
14
>>          2.2.4. Proactive and On-demand activation ................ =
15
>>          2.2.5. Connectivity Verification and Continuity Checks ... =
15
>>          2.2.6. Failures .......................................... =
15
>> ... but you don't use them in the section 3
>>=20
>> Just one example with section 3.2.2
>> -
>>    o Demand mode: in this mode, BFD control packets are sent =
on-demand.
>>       Upon need, a system initiates a series of BFD control packets =
to
>>       verify the liveness of the session
>> Instead of liveness, you have defined Connectivity Verification and =
Continuity Checks in section 2.2.5
>> - OLD:
>>    Each of the end-points of the monitored path maintains its own
>>    session identification
>> NEW:
>>    Each of the MEP maintains its own session identification
>> OR NEW (actually I don't know)
>>    Each of the MP maintains its own session identification
>> - OLD
>> 	A BFD echo packet is sent to a peer system
>> Peer system =3D MEP, MP, or something else?
>> - etc...=20
>>=20
>> 10.=20
>> This document is composed of a list of OAM content and references, =
but I'm really missing the document "scope and target audience".
>> When we did RFC 6632, which is the companion document, we had =
http://tools.ietf.org/html/rfc6632#section-1.1
>> =20
>>    The target audience of the document is, on the one hand, IETF =
working
>>    groups, which aim to select appropriate standard management =
protocols
>>    and data models to address their needs concerning network =
management.
>>    On the other hand, the document can be used as an overview and
>>    guideline by non-IETF Standards Development Organizations (SDOs)
>>    planning to use IETF management technologies and data models for =
the
>>    realization of management applications.  The document can also be
>>    used to initiate a discussion between the bodies with the goal to
>>    gather new requirements and to detect possible gaps.  Finally, =
this
>>    document is directed to all interested parties that seek to get an
>>    overview of the current set of the IETF network management =
protocols
>>    such as network administrators or newcomers to the IETF.
>>=20
>> You should have something similar.
>>=20
>>=20
>> 11.
>> Section 3.6.1, put the paragraph 2 at the end of the section. The =
"alternative" in the following sentence would then make sense
>>    Alternative protocols for performance measurement are defined, for
>>    example, in MPLS-TP OAM ([MPLS-LM-DM], [TP-LM-DM]), and in =
Ethernet
>>    OAM [ITU-T-Y1731].
>>=20
>>=20
>> My conclusions: this document still needs some work
>>=20
>> Regards, Benoit
>> =20
>>> The IESG has received a request from the Operations and Management =
Area
>>> Working Group WG (opsawg) to consider the following document:
>>> - 'An Overview of Operations, Administration, and Maintenance (OAM)
>>>    Mechanisms'
>>>   <draft-ietf-opsawg-oam-overview-08.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-01-25. Exceptionally, comments =
may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>>    Operations, Administration, and Maintenance (OAM) is a general =
term
>>>    that refers to a toolset that can be used for fault detection and
>>>    isolation, and for performance measurement. OAM mechanisms have =
been
>>>    defined for various layers in the protocol stack, and are used =
with a
>>>    variety of protocols.
>>>=20
>>>    This document presents an overview of the OAM mechanisms that =
have
>>>    been defined and are currently being defined by the IETF.
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/
>>>=20
>>> IESG discussion can be tracked via
>>> =
http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballot/
>>>=20
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>>=20
>>>=20
>>>=20
>>=20
>=20


--Apple-Mail=_37D55104-A690-4711-87D5-FDCA45807A2C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	</span>Reviewing the current version of =
the draft (12), many of the comments below are still not =
addressed.<div><br></div><div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre">	=
</span>--Tom</div><div><br></div><div><br><div><div><br></div><blockquote =
type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <div class=3D"moz-cite-prefix">Here is Tom Nadeau's feedback,
      forwarded with permission:<br>
      <br>
      Regards, Benoit<br>
      <br>
      =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
      <br>
      <div>Some general comments:</div>
      <div><br>
      </div>
      <ol>
        <li>I did not find any discussion around use of configuration
          within OAM mechanisms. This is clearly something that is
          happening in groups like PWE3 and CCAMP. The motivation for
          this should be explained and documented to at least guide
          these efforts.</li>
      </ol>
      <div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span>2.
        There is no real discussion around the security aspects of these
        tools. Should there be?</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span>3.
        While the document provides a nice taxonomy of various OAM
        tools, it does not really discuss the techniques for using them.
        I do not expect anything in detail, but it is not obvious that
        many of these tools can be orchestrated to form a "toolset" that
        can be used to do multi-layer OAM functions for services such as
        carrier Ethernet over VPLS over MPLS, for example.</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span>4.
        It might be useful to at least mention in the performance
        metrics section, a discussion around the accuracy of these tools
        and how it depends on scale, implementation and network
        configurations.</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>My detailed comments inline starting with TOM:</div>
      <div><br>
      </div>
      <div><span class=3D"Apple-tab-span" =
style=3D"white-space:pre"></span>--Tom</div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF"><br>
            <div>Expires: July 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Nokia
              Siemens Networks</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;E. Bellagamba</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; Ericsson</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;Y. Weingarten</div>
            <div><br>
            </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;January 9, 2013</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; An Overview of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; Operations, Administration, =
and Maintenance
              (OAM) Mechanisms</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;
              &nbsp;draft-ietf-opsawg-oam-overview-08.txt</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Abstract</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Operations, Administration, and =
Maintenance (OAM) is
              a general term</div>
          </div>
        </blockquote>
      </span><span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div>&nbsp; &nbsp;that refers to a toolset that can be used =
for fault
              detection and</div>
            <div>&nbsp; &nbsp;isolation, and for performance =
measurement. OAM
              mechanisms have been</div>
            <div>&nbsp; &nbsp;defined for various layers in the protocol =
stack,
              and are used with a</div>
            <div>&nbsp; &nbsp;variety of protocols.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document presents an overview of the =
OAM
              mechanisms that have</div>
            <div>&nbsp; &nbsp;been defined and are currently being =
defined by the
              IETF.</div>
            <div><br>
            </div>
            <div>Status of this Memo</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This Internet-Draft is submitted to IETF =
in full
              conformance with the</div>
            <div>&nbsp; &nbsp;provisions of BCP 78 and BCP 79.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Internet-Drafts are working documents of =
the
              Internet Engineering</div>
            <div>&nbsp; &nbsp;Task Force (IETF), its areas, and its =
working
              groups. &nbsp;Note that</div>
            <div>&nbsp; &nbsp;other groups may also distribute working =
documents
              as Internet-</div>
            <div>&nbsp; &nbsp;Drafts.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Internet-Drafts are draft documents valid =
for a
              maximum of six months</div>
            <div>&nbsp; &nbsp;and may be updated, replaced, or obsoleted =
by other
              documents at any</div>
            <div>&nbsp; &nbsp;time. &nbsp;It is inappropriate to use =
Internet-Drafts as
              reference</div>
            <div>&nbsp; &nbsp;material or to cite them other than as =
"work in
              progress."</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The list of current Internet-Drafts can be =
accessed
              at</div>
            <div>&nbsp; &nbsp;<a class=3D"moz-txt-link-freetext" =
href=3D"http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ie=
tf/1id-abstracts.txt</a>.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The list of Internet-Draft Shadow =
Directories can be
              accessed at</div>
            <div>&nbsp; &nbsp;<a class=3D"moz-txt-link-freetext" =
href=3D"http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</=
a>.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This Internet-Draft will expire on July 9, =
2013.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 1]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Copyright Notice</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Copyright (c) 2013 IETF Trust and the =
persons
              identified as the</div>
            <div>&nbsp; &nbsp;document authors. All rights =
reserved.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document is subject to BCP 78 and the =
IETF
              Trust's Legal</div>
            <div>&nbsp; &nbsp;Provisions Relating to IETF =
Documents</div>
            <div>&nbsp; &nbsp;(<a class=3D"moz-txt-link-freetext" =
href=3D"http://trustee.ietf.org/license-info">http://trustee.ietf.org/lice=
nse-info</a>) in effect on
              the date of</div>
            <div>&nbsp; &nbsp;publication of this document. Please =
review these
              documents</div>
            <div>&nbsp; &nbsp;carefully, as they describe your rights =
and
              restrictions with respect</div>
            <div>&nbsp; &nbsp;to this document. Code Components =
extracted from
              this document must</div>
            <div>&nbsp; &nbsp;include Simplified BSD License text as =
described in
              Section 4.e of</div>
            <div>&nbsp; &nbsp;the Trust Legal Provisions and are =
provided without
              warranty as</div>
            <div>&nbsp; &nbsp;described in the Simplified BSD =
License.</div>
            <div><br>
            </div>
            <div>Table of Contents</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;1. Introduction
              ................................................. 3</div>
            <div>&nbsp; &nbsp; &nbsp; 1.1. The Building Blocks of OAM
              .............................. 3</div>
            <div>&nbsp; &nbsp; &nbsp; 1.2. Forwarding Plane vs. =
Management Plane
              ................... 4</div>
            <div>&nbsp; &nbsp; &nbsp; 1.3. The OAM toolsets
              ........................................ 4</div>
            <div>&nbsp; &nbsp; &nbsp; 1.4. IETF OAM Documents
              ...................................... 6</div>
            <div>&nbsp; &nbsp; &nbsp; 1.5. Non-IETF OAM Documents
              ................................. 10</div>
            <div>&nbsp; &nbsp;2. Basic Terminology
              ........................................... 12</div>
            <div>&nbsp; &nbsp; &nbsp; 2.1. Abbreviations
              .......................................... 12</div>
            <div>&nbsp; &nbsp; &nbsp; 2.2. Terminology used in OAM =
Standards
              ...................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.1. General Terms
              ..................................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.2. OAM =
Maintenance Entities
              .......................... 13</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.3. OAM =
Maintenance Points
              ............................ 14</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.4. Proactive and =
On-demand activation
              ................ 15</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.5. Connectivity =
Verification and
              Continuity Checks ... 15</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;2.2.6. Failures
              .......................................... 15</div>
            <div>&nbsp; &nbsp;3. OAM Tools
              ................................................... =
16</div>
            <div>&nbsp; &nbsp; &nbsp; 3.1. IP Ping and Traceroute
              ................................. 16</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.1.1. Ping
              .............................................. 16</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.1.2.
              Traceroute......................................... =
16</div>
            <div>&nbsp; &nbsp; &nbsp; 3.2. Bidirectional Forwarding =
Detection (BFD)
              ............... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.1. Overview
              .......................................... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.2. BFD Control
              ....................................... 17</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.2.3. BFD Echo
              .......................................... 18</div>
            <div>&nbsp; &nbsp; &nbsp; 3.3. MPLS OAM
              ............................................... 18</div>
            <div>&nbsp; &nbsp; &nbsp; 3.4. MPLS-TP OAM
              ............................................ 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.1. Overview
              .......................................... 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.2. Generic =
Associated Channel
              ........................ 19</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.4.3. MPLS-TP OAM =
Toolset
              ............................... 20</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.1. =
Continuity Check and Connectivity
              Verification 20</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 2]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.2. =
Route Tracing
              ................................ 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.3. Lock =
Instruct
              ................................ 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.4. Lock =
Reporting
              ............................... 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.5. =
Alarm Reporting
              .............................. 21</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.6. =
Remote Defect Indication
              ..................... 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.7. =
Client Failure Indication
              .................... 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.8. =
Packet Loss Measurement (LM)
              ................. 22</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.4.3.9. =
Packet Delay Measurement (DM)
              ................ 22</div>
            <div>&nbsp; &nbsp; &nbsp; 3.5. PWE3 OAM
              ............................................... 23</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.5.1. PWE3 OAM using =
Virtual Circuit
              Connectivity Verification</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;(VCCV)
              ................................................... =
23</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.5.2. PWE3 OAM using =
G-ACh
              .............................. 24</div>
            <div>&nbsp; &nbsp; &nbsp; 3.6. OWAMP and
              TWAMP......................................... 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.1. Overview
              .......................................... 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.2. Control and =
Test Protocols
              ........................ 24</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.3. OWAMP
              ............................................. 25</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;3.6.4. TWAMP
              ............................................. 26</div>
            <div>&nbsp; &nbsp; &nbsp; 3.7. Summary of OAM Functions
              ............................... 26</div>
            <div>&nbsp; &nbsp;4. Security Considerations
              ..................................... 27</div>
            <div>&nbsp; &nbsp;5. IANA Considerations
              ......................................... 27</div>
            <div>&nbsp; &nbsp;6. Acknowledgments
              ............................................. 27</div>
            <div>&nbsp; &nbsp;7. References
              .................................................. =
28</div>
            <div>&nbsp; &nbsp; &nbsp; 7.1. Normative References
              ................................... 28</div>
            <div>&nbsp; &nbsp; &nbsp; 7.2. Informative References
              ................................. 31</div>
            <div><br>
            </div>
            <div>1. Introduction</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM is a general term that refers to a =
toolset for
              detecting,</div>
            <div>&nbsp; &nbsp;isolating and reporting connection =
failures and
              performance</div>
            <div>&nbsp; &nbsp;degradation.</div>
          </div>
        </blockquote>
      </span><span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document summarizes the OAM tools and
              mechanisms defined in the</div>
            <div>&nbsp; &nbsp;IETF.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The term OAM in this document refers to =
Operations,
              Administration</div>
            <div>&nbsp; &nbsp;and Maintenance [OAM-Def], focusing on the
              forwarding plane of OAM.</div>
            <div>&nbsp; &nbsp;Hence, management aspects are outside the =
scope of
              this document.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: This is a curious sentence to me since to me, OAM is
        management, or a subset of it. &nbsp; Also, if you look at the
        referenced documents, there are many indirect references to
        MIBs, Netconf, etc=85 making this sentence further confusing. It
        might be helpful to explain more clearly that the authors here
        intended to not cover those things explicitly rather than
        grouping them arbitrarily under the definition of "management
        aspects" &nbsp;Further, to clarify, it might be useful to expand =
on
        what "forwarding plane" is here just to be clear. &nbsp; That =
is, is
        this "in band" or "out-of band" or both? Some of the tools
        referred to here also are part of the control AND data =
planes.&nbsp;</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div>1.1. The Building Blocks of OAM</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;An OAM protocol is run in the context of a
              Maintenance Domain,</div>
            <div>&nbsp; &nbsp;consisting of two or more nodes that run =
the OAM
              protocol, referred</div>
            <div>&nbsp; &nbsp;to as Maintenance Points (MP).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This subsection provides a brief summary =
of the
              common tools used by</div>
            <div>&nbsp; &nbsp;OAM protocols. An OAM protocol typically =
supports
              one or more of the</div>
            <div>&nbsp; &nbsp;tools described below.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 3]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Continuity Checking (CC):</div>
            <div>&nbsp; &nbsp; &nbsp; Used for verifying the liveness of =
a connection
              between two MPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Connectivity Verification (CV):</div>
            <div>&nbsp; &nbsp; &nbsp; Allows an MP to check whether it =
is connected to
              a peer MP, and to</div>
            <div>&nbsp; &nbsp; &nbsp; verify that messages from the peer =
MP are
              received through the</div>
            <div>&nbsp; &nbsp; &nbsp; expected path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Path Discovery / Fault =
Localization:</div>
            <div>&nbsp; &nbsp; &nbsp; An MP uses this mechanism to trace =
the route to a
              peer MP, i.e.,</div>
            <div>&nbsp; &nbsp; &nbsp; to identify the nodes along the =
path to the peer
              MP. When a</div>
            <div>&nbsp; &nbsp; &nbsp; connection fails, this mechanism =
also allows the
              MP to detect the</div>
            <div>&nbsp; &nbsp; &nbsp; location of the failure.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: The definition calls this "path discovery" but then
        talks about tracing routes. A better way of describing this in
        the paragraph would be that there I a use of path tracing in
        order to discover (or re-discover) paths that have been changed,
        created or destroyed. &nbsp;</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Performance Monitoring:</div>
            <div>&nbsp; &nbsp; &nbsp; Consists of 3 main functions</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Loss Measurement (LM) - =
monitors the packet
              loss rate of a</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; connection.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Delay Measurement (DM) - =
monitors the delay
              and delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; variation between =
MPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; o Throughput measurement - =
monitors the
              throughput of a</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; connection.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Along with the discussion above around path
        trace/discovery, it is imperative that paths be discovered (one
        way or another) in order to successfully d performance
        monitoring on those paths.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div>1.2. Forwarding Plane vs. Management Plane</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;While the OAM tools may, and quite often =
do, work in
              conjunction with</div>
            <div>&nbsp; &nbsp;a control-plane or management plane, they =
are
              usually defined to be</div>
            <div>&nbsp; &nbsp;independent of the control-plane. =
&nbsp;The OAM tools
              communicate with the</div>
            <div>&nbsp; &nbsp;management plane to raise alarms, and =
often the
              on-demand tools may</div>
            <div>&nbsp; &nbsp;be activated by the management, e.g. to =
locate and
              localize problems.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The considerations of the control-plane =
maintenance
              tools or the</div>
            <div>&nbsp; &nbsp;functionality of the management-plane are =
out of
              scope for this</div>
            <div>&nbsp; &nbsp;document, which will concentrate on =
presenting the
              forwarding-plane</div>
            <div>&nbsp; &nbsp;tools that are used for OAM.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: What about the data plane? For example, the GACH OAM
        type is such an example. VCCV also operates within the data
        plane after its configuration capabilities have been signaled.
        &nbsp;It should also be mentioned that it is imperative that =
when
        required, OAM tools are capable of testing the actual data plane
        in as much accuracy as possible, but that they all should note
        how accurate. &nbsp; Not all OAM tools are created equal.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div>1.3. The OAM toolsets</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This memo provides an overview of the =
different sets
              of OAM</div>
            <div>&nbsp; &nbsp;mechanisms defined by the IETF. It is =
intended for
              those with little</div>
            <div>&nbsp; &nbsp;or no familiarity with the described =
mechanisms. The
              set of OAM</div>
            <div>&nbsp; &nbsp;mechanisms described in this memo are =
applicable to
              IP unicast, MPLS,</div>
            <div>&nbsp; &nbsp;pseudowires, and MPLS for the transport =
environment
              (MPLS-TP). While</div>
            <div>&nbsp; &nbsp;OAM mechanisms that are applicable to =
other
              technologies exist, they</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 4]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;are beyond the scope of this memo. This =
document
              focuses on IETF</div>
            <div>&nbsp; &nbsp;documents that have been published as =
RFCs, while
              other ongoing OAM-</div>
            <div>&nbsp; &nbsp;related work is outside the scope.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IETF has defined OAM protocols and =
mechanisms in
              several</div>
            <div>&nbsp; &nbsp;different fronts:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o IP Ping and Traceroute:</div>
            <div>&nbsp; &nbsp; &nbsp; Ping is a very simple and common =
application for
              failure diagnosis</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: I am not sure the term "common" is necessary.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div>&nbsp; &nbsp; &nbsp; that uses ICMP Echo requests, as =
defined in
              [ICMPv4], and</div>
            <div>&nbsp; &nbsp; &nbsp; [ICMPv6].</div>
            <div>&nbsp; &nbsp; &nbsp; Traceroute ([TCPIP-Tools], =
[NetTools]) is an
              application that</div>
            <div>&nbsp; &nbsp; &nbsp; allows users to trace the path =
between an IP
              source and an IP</div>
            <div>&nbsp; &nbsp; &nbsp; destination, i.e., to identify the =
nodes along
              the path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o BFD:</div>
            <div>&nbsp; &nbsp; &nbsp; Bidirectional Forwarding Detection =
(BFD) is
              defined in [BFD] as a</div>
            <div>&nbsp; &nbsp; &nbsp; framework for a lightweight =
generic OAM
              mechanism. &nbsp;The intention</div>
            <div>&nbsp; &nbsp; &nbsp; is to define a base mechanism that =
can be used
              with various</div>
            <div>&nbsp; &nbsp; &nbsp; encapsulation types, network =
environments, and in
              various medium</div>
            <div>&nbsp; &nbsp; &nbsp; types.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS LSP Ping, as defined in =
[MPLS-OAM],
              [MPLS-OAM-FW] and [LSP-</div>
            <div>&nbsp; &nbsp; &nbsp; Ping], is an OAM mechanism for =
point to point
              MPLS LSPs. It</div>
            <div>&nbsp; &nbsp; &nbsp; includes two main functions: Ping =
and Traceroute.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS-TP OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS-TP OAM is defined in a set of =
RFCs. The OAM
              requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS Transport Profile (MPLS-TP) =
are defined in
              [MPLS-TP-OAM].</div>
            <div>&nbsp; &nbsp; &nbsp; Each of the tools in the OAM =
toolset is defined
              in its own RFC, as</div>
            <div>&nbsp; &nbsp; &nbsp; specified in Section 1.4.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o PWE3 OAM:</div>
            <div>&nbsp; &nbsp; &nbsp; The PWE3 OAM architecture defines =
control
              channels that support</div>
            <div>&nbsp; &nbsp; &nbsp; the use of existing IETF OAM tools =
to be used for
              a pseudowire</div>
            <div>&nbsp; &nbsp; &nbsp; (PW). &nbsp;The control channels =
that are defined in
              [VCCV] and [PW-G-</div>
            <div>&nbsp; &nbsp; &nbsp; ACH] may be used in conjunction =
with ICMP Ping,
              LSP Ping, and BFD</div>
            <div>&nbsp; &nbsp; &nbsp; to perform CC and CV =
functionality. &nbsp;In addition
              the channels</div>
            <div>&nbsp; &nbsp; &nbsp; support use of any of the MPLS-TP =
based OAM tools
              for completing</div>
            <div>&nbsp; &nbsp; &nbsp; their respective OAM functionality =
for a PW.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OWAMP and TWAMP:</div>
            <div>&nbsp; &nbsp; &nbsp; The One Way Active Measurement =
Protocol (OWAMP)
              and the Two Way</div>
            <div>&nbsp; &nbsp; &nbsp; Active Measurement Protocols =
(TWAMP) are two
              protocols defined in</div>
            <div>&nbsp; &nbsp; &nbsp; the IP Performance Metrics (IPPM) =
working group
              in the IETF. These</div>
            <div>&nbsp; &nbsp; &nbsp; protocols allow delay and packet =
loss measurement
              in IP networks.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 5]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document summarizes the OAM =
mechanisms defined
              by the IETF. We</div>
            <div>&nbsp; &nbsp;first present a comparison of the =
terminology used
              in various OAM</div>
            <div>&nbsp; &nbsp;standards, and then summarize the OAM =
functions that
              each OAM</div>
            <div>&nbsp; &nbsp;standard provides.</div>
            <div><br>
            </div>
            <div>1.4. IETF OAM Documents</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 1 summarizes the IETF OAM related =
RFCs
              discussed in this</div>
            <div>&nbsp; &nbsp;document.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The table includes a "Type" column, =
specifying the
              nature of each of</div>
            <div>&nbsp; &nbsp;the listed documents:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Tool: documents that define an OAM tool =
or
              mechanism.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Prof.: documents that define a profile =
or a
              variant for an OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tool that is defined in other =
documents.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Inf.: documents that define an =
infrastructure that
              is used by OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tools.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Misc.: other OAM related documents, =
e.g., OAM
              requirement and</div>
            <div>&nbsp; &nbsp; &nbsp; framework documents.</div>
            <div><br>
            </div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Type | RFC &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|IP Ping and| Internet Control Message =
Protocol &nbsp;
              &nbsp;|Tool | RFC 792 &nbsp;|</div>
            <div>&nbsp; &nbsp;|Traceroute | [ICMPv4] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Internet Control Message Protocol &nbsp;
              &nbsp;|Tool | RFC 4443 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
(ICMPv6) for the Internet Protocol &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Version 6 (IPv6) Specification &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[ICMPv6] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Primer On Internet and TCP/IP &nbsp; &nbsp;
              &nbsp;|Tool | RFC 2151 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Tools and Utilities [TCPIP-Tools] &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | FYI =
on a Network Management Tool &nbsp; &nbsp;
              |Tool | RFC 1147 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Catalog: Tools for Monitoring and &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Debugging TCP/IP Internets and &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Interconnected Devices [NetTools] &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Extended ICMP to Support Multi-Part
              &nbsp;|Tool | RFC 4884 |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 6]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Messages [ICMP-MP] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
ICMP Extensions for Multiprotocol &nbsp;
              &nbsp;|Tool | RFC 4950 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Label Switching [ICMP-Ext] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Extending ICMP for Interface and &nbsp; &nbsp;
              |Tool | RFC 5837 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Next-Hop Identification [ICMP-Int] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|BFD &nbsp; &nbsp; &nbsp; &nbsp;| =
Bidirectional Forwarding Detection &nbsp;
              |Tool | RFC 5880 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[BFD] &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>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5881 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
(BFD) for IPv4 and IPv6 (Single Hop) |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[BFD-IP] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Generic Application of Bidirectional
              |Misc.| RFC 5882 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Forwarding Detection [BFD-Gen] &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5883 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
(BFD) for Multihop Paths [BFD-Multi] |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5884 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for =
MPLS Label Switched Paths (LSPs) |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[BFD-LSP] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5885 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for =
the Pseudowire Virtual Circuit &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Connectivity Verification (VCCV) &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[BFD-VCCV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | Operations and =
Management (OAM) &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 4377 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Requirements for Multi-Protocol Label|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Switched (MPLS) Networks [MPLS-OAM] &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Framework for Multi-Protocol &nbsp; &nbsp; &nbsp;
              |Misc.| RFC 4378 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Label Switching (MPLS) Operations &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | and =
Management (OAM) [MPLS-OAM-FW] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Detecting Multi-Protocol Label &nbsp; &nbsp; &nbsp;
              |Tool | RFC 4379 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Switched (MPLS) Data Plane Failures &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[LSP-Ping] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 7]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Operations and Management (OAM) &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 4687 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Requirements for Point-to-Multipoint |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS Networks [MPLS-P2MP] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|MPLS-TP &nbsp; &nbsp;| Requirements for =
OAM in MPLS-TP &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 5860 |</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| =
[MPLS-TP-OAM] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS Generic Associated Channel &nbsp; &nbsp;
              &nbsp;|Inf. | RFC 5586 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[G-ACh] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS-TP OAM Framework &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 6371 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[TP-OAM-FW] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Proactive Connectivity Verification,
              |Tool | RFC 6428 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Continuity Check, and Remote Defect &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Indication for the MPLS Transport &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Profile [TP-CC-CV] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS On-Demand Connectivity &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Tool | RFC 6426 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Verification and Route Tracing &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[OnDemand-CV] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS Fault Management Operations, &nbsp;
              &nbsp;|Tool | RFC 6427 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Administration, and Maintenance (OAM)|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[TP-Fault] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS Transport Profile Lock Instruct
              |Tool | RFC 6435 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | and =
Loopback Functions [Lock-Loop] &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Packet Loss and Delay Measurement
              for|Tool | RFC 6374 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS Networks [MPLS-LM-DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Packet Loss and Delay Measurement
              &nbsp;|Prof.| RFC 6375 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Profile for MPLS-Based Transport &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Networks [TP-LM-DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|PWE3 OAM &nbsp; | Pseudowire Virtual =
Circuit &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |Inf. | RFC 5085 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Connectivity Verification (VCCV): &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Control Channel for Pseudowires &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[VCCV] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 8]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Bidirectional Forwarding Detection &nbsp;
              |Prof.| RFC 5885 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for =
the Pseudowire Virtual Circuit &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Connectivity Verification (VCCV) &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[BFD-VCCV] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Using the Generic Associated Channel
              |Inf. | RFC 6423 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Label for Pseudowire in the MPLS &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Transport Profile (MPLS-TP) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[PW-G-ACh] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Pseudowire (PW) Operations, &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 6310 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Administration, and Maintenance (OAM)|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Message Mapping [PW-Map] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp;|OWAMP and &nbsp;| A One-way Active =
Measurement
              Protocol|Tool | RFC 4656 |</div>
            <div>&nbsp; &nbsp;|TWAMP &nbsp; &nbsp; &nbsp;| [OWAMP] =
&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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Two-Way Active Measurement
              Protocol|Tool | RFC 5357 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[TWAMP] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Framework for IP Performance Metrics
              |Misc.| RFC 2330 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[IPPM-FW] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
IPPM Metrics for Measuring &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |Misc.| RFC 2678 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Connectivity [IPPM-Con] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;|
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
One-way Delay Metric for IPPM &nbsp; &nbsp;
              &nbsp;|Misc.| RFC 2679 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[IPPM-1DM] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
One-way Packet Loss Metric for
              IPPM|Misc.| RFC 2680 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[IPPM-1LM] &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;
              =
+--------------------------------------+-----+----------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | A =
Round-trip Delay Metric for IPPM &nbsp;
              |Misc.| RFC 2681 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[IPPM-2DM] &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+-----+----------=
+</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Table 1 Summary of IETF OAM Related
              RFCs</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; &nbsp;[Page 9]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>1.5. Non-IETF OAM Documents</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In addition to the OAM mechanisms defined =
by the
              IETF, the IEEE and</div>
            <div>&nbsp; &nbsp;ITU-T have also defined various OAM =
mechanisms that
              focus on</div>
            <div>&nbsp; &nbsp;Ethernet, and various other transport =
network
              environments. These</div>
            <div>&nbsp; &nbsp;various mechanisms, defined by the three =
standard
              organizations, are</div>
            <div>&nbsp; &nbsp;often tightly coupled, and have had a =
mutual effect
              on each other.</div>
            <div>&nbsp; &nbsp;The ITU-T and IETF have both defined OAM =
mechanisms
              for MPLS LSPs,</div>
            <div>&nbsp; &nbsp;[ITU-T-Y1711] and [LSP-Ping]. The =
following OAM
              standards by the IEEE</div>
            <div>&nbsp; &nbsp;and ITU-T are to some extent linked to =
IETF OAM
              mechanisms listed</div>
            <div>&nbsp; &nbsp;above and are mentioned here only as =
reference
              material:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OAM mechanisms for Ethernet based =
networks have
              been defined by</div>
            <div>&nbsp; &nbsp; &nbsp; both the ITU-T in [ITU-T-Y1731], =
and by the IEEE
              in [IEEE802.1ag].</div>
            <div>&nbsp; &nbsp; &nbsp; The IEEE 802.3 standard defines =
OAM for one-hop
              Ethernet links</div>
            <div>&nbsp; &nbsp; &nbsp; [IEEE802.3ah].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o The ITU-T has defined OAM for MPLS LSPs =
in
              [ITU-T-Y1711], and</div>
            <div>&nbsp; &nbsp; &nbsp; MPLS-TP OAM in [ITU-G8113.1] and =
[ITU-G8113.2].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 2 summarizes the OAM standards =
mentioned in
              this document. This</div>
            <div>&nbsp; &nbsp;document focuses on IETF OAM standards, =
but these
              non-IETF standards</div>
            <div>&nbsp; &nbsp;are referenced where relevant.</div>
            <div><br>
            </div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp;|Standard/Draft |</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| Operation =
&amp; Maintenance mechanism
              &nbsp; &nbsp;| ITU-T Y.1711 &nbsp;|</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | for MPLS networks =
[ITU-T-Y1711] &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Assignment of the 'OAM Alert Label' &nbsp;|
              RFC 3429 &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | for =
Multiprotocol Label Switching &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Architecture (MPLS) Operation and &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Maintenance (OAM) Functions &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[OAM-Label] &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; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;Note: although this is an IETF &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;document, it is listed as one of the|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;non-IETF OAM standards, since it &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;was defined as a complementary part |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;of ITU-T Y.1711. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| Operations, =
administration and &nbsp; &nbsp; &nbsp;
              |ITU-T G.8113.2 |</div>
            <div>&nbsp; &nbsp;|MPLS-TP OAM| Maintenance mechanisms for =
MPLS-TP &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 10]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
networks using the tools defined for |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
MPLS [ITU-G8113.2] &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; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;Note: this document describes the &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;OAM toolset defined by the IETF for |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;MPLS-TP, whereas ITU-T G.8113.1 &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;describes the OAM toolset defined &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;by the ITU-T. &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;
              =
+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Operations, Administration and &nbsp; &nbsp; &nbsp;
              |ITU-T G.8113.1 |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Maintenance mechanism for MPLS-TP in |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Packet Transport Network (PTN) &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              =
+--------------------------------------+---------------+</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Allocation of a Generic Associated &nbsp; |
              RFC 6671 &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Channel Type for ITU-T MPLS Transport|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Profile Operation, Maintenance, and &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
Administration (MPLS-TP OAM) &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
[ITU-T-CT] &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; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;Note: although this is an IETF &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;document, it is listed as one of the|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;non-IETF OAM standards, since it &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;was defined as a complementary part |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;of ITU-T G.8113.1. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;|ITU-T &nbsp; &nbsp; &nbsp;| OAM Functions =
and Mechanisms for &nbsp; &nbsp;
              |[ITU-T-Y1731] &nbsp;|</div>
            <div>&nbsp; &nbsp;|Ethernet &nbsp; | Ethernet-based Networks =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|OAM &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>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;|IEEE &nbsp; &nbsp; &nbsp; | Connectivity =
Fault Management &nbsp; &nbsp; &nbsp; &nbsp;|
              IEEE 802.1ag &nbsp;|</div>
            <div>&nbsp; &nbsp;|CFM &nbsp; &nbsp; &nbsp; &nbsp;| =
[IEEE802.1ag] &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; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;Note: CFM was originally published &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;as IEEE 802.1ag, but is now &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;incorporated in the 802.1Q standard.|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp;|IEEE &nbsp; &nbsp; &nbsp; | Media Access =
Control Parameters, &nbsp; &nbsp; |
              IEEE 802.3ah &nbsp;|</div>
            <div>&nbsp; &nbsp;|802.3 &nbsp; &nbsp; &nbsp;| Physical =
Layers, and Management &nbsp; &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|link level | Parameters for Subscriber =
Access &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| Networks =
[IEEE802.3ah] &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; |</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 11]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;Note: link level OAM was originally |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;defined in IEEE 802.3ah, and is now |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp;incorporated in the 802.3 standard. |
              &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp;
              =
&nbsp;+-----------+--------------------------------------+---------------+=
</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Table 2 Non-IETF OAM =
Standards Mentioned in
              this Document</div>
            <div><br>
            </div>
            <div>2. Basic Terminology</div>
            <div><br>
            </div>
            <div>2.1. Abbreviations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ACH &nbsp; &nbsp;Associated Channel =
Header</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;AIS &nbsp; &nbsp;Alarm Indication =
Signal</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD &nbsp; &nbsp;Bidirectional Forwarding =
Detection</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;CC &nbsp; &nbsp; Continuity Check</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;CV &nbsp; &nbsp; Connectivity =
Verification</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;DM &nbsp; &nbsp; Delay Measurement</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;FEC &nbsp; &nbsp;Forwarding Equivalence =
Class</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;GAL &nbsp; &nbsp;Generic Associated =
Label</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ICMP &nbsp; Internet Control Message =
Protocol</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LDP &nbsp; &nbsp;Label Distribution =
Protocol</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LM &nbsp; &nbsp; Loss Measurement</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP &nbsp; &nbsp;Label Switched Path</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;ME &nbsp; &nbsp; Maintenance Entity</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MEG &nbsp; &nbsp;Maintenance Entity =
Group</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MEP &nbsp; &nbsp;MEG End Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MIP &nbsp; &nbsp;MEG Intermediate =
Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MP &nbsp; &nbsp; Maintenance Point</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS &nbsp; Multiprotocol Label =
Switching</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 12]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP MPLS Transport Profile</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MTU &nbsp; &nbsp;Maximum Transmission =
Unit</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM &nbsp; &nbsp;Operations, =
Administration, and Maintenance</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;PW &nbsp; &nbsp; Pseudowire</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;PWE3 &nbsp; Pseudowire Emulation =
Edge-to-Edge</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;RDI &nbsp; &nbsp;Remote Defect =
Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TTL &nbsp; &nbsp;Time To Live</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV &nbsp; Virtual Circuit Connectivity =
Verification</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div><br>
      </div>
      <div>TOM: Why is this section not at the top of this document, as
        is customary for RFCs? &nbsp;</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div>2.2. Terminology used in OAM Standards</div>
            <div><br>
            </div>
            <div>2.2.1. General Terms</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A wide variety of terms is used in various =
OAM
              standards. Each of the</div>
            <div>&nbsp; &nbsp;OAM standards listed in the reference =
section
              includes a section that</div>
            <div>&nbsp; &nbsp;defines terms relevant to that tool. A =
thesaurus of
              terminology for</div>
            <div>&nbsp; &nbsp;MPLS-TP terms is presented in [TP-Term], =
and
              provides a good summary</div>
            <div>&nbsp; &nbsp;of some of the OAM related =
terminology.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This section presents a comparison of the =
terms used
              in various OAM</div>
            <div>&nbsp; &nbsp;standards, without fully quoting the =
definition of
              each term. For a</div>
            <div>&nbsp; &nbsp;formal definition of each term, refer to =
the
              references at the end of</div>
            <div>&nbsp; &nbsp;this document.</div>
            <div><br>
            </div>
            <div>2.2.2. OAM Maintenance Entities</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OAM tools are designed to monitor and =
manage a
              Maintenance Entity</div>
            <div>&nbsp; &nbsp;(ME). &nbsp;An ME, as defined in =
[TP-OAM-FW], defines a
              relationship</div>
            <div>&nbsp; &nbsp;between two points of a transport path to =
which
              maintenance and</div>
            <div>&nbsp; &nbsp;monitoring operations apply.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The following related terms are also =
quoted from
              [TP-OAM-FW]:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MEP: The two points that define a =
maintenance
              entity.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MEG: The collection of one or more MEs =
that
              belongs to the same</div>
            <div>&nbsp; &nbsp; &nbsp; transport path and that are =
maintained and
              monitored as a group</div>
            <div>&nbsp; &nbsp; &nbsp; are known as a Maintenance Entity =
Group (MEG).</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 13]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MIP: In between MEPs, there are zero or =
more
              intermediate points,</div>
            <div>&nbsp; &nbsp; &nbsp; called Maintenance Entity Group =
Intermediate
              Points (MIPs).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A pair of MEPs engaged in an ME are =
connected by a
              communication</div>
            <div>&nbsp; &nbsp;link, which may be one of several types of
              connection, e.g. a single</div>
            <div>&nbsp; &nbsp;physical connection, a set of physical =
connections,
              or a virtual link</div>
            <div>&nbsp; &nbsp;such as an MPLS LSP.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The term Maintenance Entity (ME) is used =
in ITU-T
              Recommendations</div>
            <div>&nbsp; &nbsp;(e.g. [ITU-T-Y1731]), as well as in the =
MPLS-TP
              terminology ([TP-OAM-</div>
            <div>&nbsp; &nbsp;FW]). Various terms are used to refer to =
an ME. For
              example, BFD does</div>
            <div>&nbsp; &nbsp;not explicitly use a term that is =
equivalent to ME,
              but rather uses</div>
            <div>&nbsp; &nbsp;the term "session", referring to the =
relationship
              between two nodes</div>
            <div>&nbsp; &nbsp;using a BFD protocol. The MPLS LSP Ping =
([LSP-Ping])
              terminology</div>
            <div>&nbsp; &nbsp;simply uses the term "LSP" in this =
context.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP has defined the terms ME and =
Maintenance
              Entity Group (MEG)</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW], similar to the terms =
defined by
              ITU-T. &nbsp;A MEG allows</div>
            <div>&nbsp; &nbsp;the monitoring of a compound set of MEs, =
for example
              when monitoring</div>
            <div>&nbsp; &nbsp;a p2mp MEG that is considered to be the =
set of MEs
              between the root</div>
            <div>&nbsp; &nbsp;and each individual destination MEP.</div>
            <div><br>
            </div>
            <div>2.2.3. OAM Maintenance Points</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A Maintenance Point (MP) is a functional =
entity that
              is defined at a</div>
            <div>&nbsp; &nbsp;node in the network, and either initiates =
or reacts
              to OAM messages.</div>
            <div>&nbsp; &nbsp;A Maintenance End Point (MEP) is one of =
the end
              points of an ME, and</div>
            <div>&nbsp; &nbsp;can initiate OAM messages and respond to =
them. A
              Maintenance</div>
            <div>&nbsp; &nbsp;Intermediate Point (MIP) is an =
intermediate point
              between two MEPs,</div>
            <div>&nbsp; &nbsp;that does not generally initiate OAM =
frames (one
              exception to this is</div>
            <div>&nbsp; &nbsp;the use of AIS notifications), but is able =
to
              respond to OAM frames</div>
            <div>&nbsp; &nbsp;that are destined to it. A MIP in MPLS-TP =
identifies
              OAM packets</div>
            <div>&nbsp; &nbsp;destined to it by the value of the TTL =
field in the
              OAM packet. The</div>
            <div>&nbsp; &nbsp;term Maintenance Point is a general term =
for MEPs
              and MIPs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The 802.1ag defines a finer distinction =
between Up
              MPs and Down MPs.</div>
            <div>&nbsp; &nbsp;An MP is a bridge interface, that is =
monitored by an
              OAM protocol</div>
            <div>&nbsp; &nbsp;either in the direction facing the =
network, or in
              the direction</div>
            <div>&nbsp; &nbsp;facing the bridge. A Down MP is an MP that =
receives
              OAM packets from,</div>
            <div>&nbsp; &nbsp;and transmits them to the direction of the =
network.
              An Up MP receives</div>
            <div>&nbsp; &nbsp;OAM packets from, and transmits them to =
the
              direction of the bridging</div>
            <div>&nbsp; &nbsp;entity.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;MPLS-TP ([TP-OAM-FW]) uses a similar =
distinction on
              the placement of</div>
            <div>&nbsp; &nbsp;the MP - either at the ingress, egress, or
              forwarding function of the</div>
            <div>&nbsp; &nbsp;node (Down / Up MPs). &nbsp;This placement =
is important
              for localization</div>
            <div>&nbsp; &nbsp;of a connection failure.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 14]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>2.2.4. Proactive and On-demand activation</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The different OAM tools may be used in one =
of two
              basic types of</div>
            <div>&nbsp; &nbsp;activation:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Proactive activation - indicates that =
the tool is
              activated on a</div>
            <div>&nbsp; &nbsp; &nbsp; continual basis periodically, =
where messages are
              sent between the</div>
            <div>&nbsp; &nbsp; &nbsp; two MEPs, and errors are detected =
when a certain
              number of</div>
            <div>&nbsp; &nbsp; &nbsp; expected messages are not =
received.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o On-demand activation - indicates that =
the tool is
              activated</div>
            <div>&nbsp; &nbsp; &nbsp; "manually" to detect a specific =
anomaly. &nbsp;In this
              activation a</div>
            <div>&nbsp; &nbsp; &nbsp; small number of OAM messages are =
sent by a MEP
              and the reply</div>
            <div>&nbsp; &nbsp; &nbsp; message is received.</div>
            <div><br>
            </div>
            <div>2.2.5. Connectivity Verification and Continuity =
Checks</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Two distinct classes of failure management =
functions
              are used in OAM</div>
            <div>&nbsp; &nbsp;protocols, connectivity verification and =
continuity
              checks. The</div>
            <div>&nbsp; &nbsp;distinction between these terms is defined =
in
              [MPLS-TP-OAM], and is</div>
            <div>&nbsp; &nbsp;used similarly in this document.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Continuity checks are used to verify the =
liveness of
              a connection or</div>
            <div>&nbsp; &nbsp;a path between two MPs, and are typically =
sent
              proactively, though</div>
            <div>&nbsp; &nbsp;they can be invoked on-demand as =
well.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A connectivity verification function =
allows an MP to
              check whether it</div>
            <div>&nbsp; &nbsp;is connected to a peer MP or not. This =
function also
              allows the MP to</div>
            <div>&nbsp; &nbsp;verify that messages from the peer MP are =
received
              through the</div>
            <div>&nbsp; &nbsp;correct path, thereby verifying not only =
that the
              two MPs are</div>
            <div>&nbsp; &nbsp;connected, but also that they are =
connected through
              the expected</div>
            <div>&nbsp; &nbsp;path. This allows detection of unexpected =
topology
              changes. A</div>
            <div>&nbsp; &nbsp;connectivity verification (CV) protocol =
typically
              uses a CV message,</div>
            <div>&nbsp; &nbsp;followed by a CV reply that is sent back =
to the
              originator. A CV</div>
            <div>&nbsp; &nbsp;function can be applied proactively or =
on-demand.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Connectivity verification and continuity =
checks are
              considered</div>
            <div>&nbsp; &nbsp;complementary mechanisms, and are often =
used in
              conjunction with each</div>
            <div>&nbsp; &nbsp;other.</div>
            <div><br>
            </div>
            <div>2.2.6. Failures</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The terms Failure, Fault, and Defect are =
used
              interchangeably in the</div>
            <div>&nbsp; &nbsp;standards, referring to a malfunction that =
can be
              detected by a</div>
            <div>&nbsp; &nbsp;connectivity or a continuity check. In =
some
              standards, such as</div>
            <div>&nbsp; &nbsp;[IEEE802.1ag], there is no distinction =
between these
              terms, while in</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 15]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;other standards each of these terms refers =
to a
              different type of</div>
            <div>&nbsp; &nbsp;malfunction.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The terminology used in IETF MPLS-TP OAM =
takes after
              the ITU-T, which</div>
            <div>&nbsp; &nbsp;distinguishes between these terms in =
[ITU-T-G.806];
              The term Fault</div>
            <div>&nbsp; &nbsp;refers to an inability to perform a =
required action,
              e.g., an</div>
            <div>&nbsp; &nbsp;unsuccessful attempt to deliver a packet. =
The term
              Defect refers to</div>
            <div>&nbsp; &nbsp;an interruption in the normal operation, =
such as a
              consecutive period</div>
            <div>&nbsp; &nbsp;of time where no packets are delivered =
successfully.
              The term Failure</div>
            <div>&nbsp; &nbsp;refers to the termination of the required =
function.
              While a Defect</div>
            <div>&nbsp; &nbsp;typically refers to a limited period of =
time, a
              failure refers to a</div>
            <div>&nbsp; &nbsp;long period of time.</div>
            <div><br>
            </div>
            <div>3. OAM Tools</div>
            <div><br>
            </div>
            <div>3.1. IP Ping and Traceroute</div>
            <div><br>
            </div>
            <div>3.1.1. Ping</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Ping is a common network diagnosis =
application for
              IP networks that</div>
            <div>&nbsp; &nbsp;uses ICMP. The ICMP Echo request/reply =
exchange is a
              connectivity</div>
            <div>&nbsp; &nbsp;verification function for the Internet =
Protocol. The
              originator</div>
            <div>&nbsp; &nbsp;transmits an ICMP Echo request packet, and =
the
              receiver replies with</div>
            <div>&nbsp; &nbsp;an Echo reply. ICMP ping is defined in two =
variants,
              [ICMPv4] is used</div>
            <div>&nbsp; &nbsp;for IPv4, and [ICMPv6] is used for =
IPv6.</div>
            <div><br>
            </div>
            <div>3.1.2. Traceroute</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Traceroute ([TCPIP-Tools], [NetTools]) is =
an
              application that allows</div>
            <div>&nbsp; &nbsp;users to discover the path between an IP =
source and
              an IP</div>
            <div>&nbsp; &nbsp;destination. Traceroute sends a sequence =
of UDP
              packets to UDP port</div>
            <div>&nbsp; &nbsp;33434 at the destination. By default, =
Traceroute
              begins by sending</div>
            <div>&nbsp; &nbsp;three packets (the number of packets is =
configurable
              in most</div>
            <div>&nbsp; &nbsp;Traceroute implementations), each with an =
IP
              Time-To-Live (TTL) value</div>
            <div>&nbsp; &nbsp;of one to the destination. These packets =
expire as
              soon as they reach</div>
            <div>&nbsp; &nbsp;the first router in the path. That router =
responds
              by sending three</div>
            <div>&nbsp; &nbsp;ICMP Time Exceeded Messages to the =
Traceroute
              application. Traceroute</div>
            <div>&nbsp; &nbsp;now sends another three UDP packets, each =
with the
              TTL value of 2.</div>
            <div>&nbsp; &nbsp;These messages cause the second router to =
return
              ICMP messages. This</div>
            <div>&nbsp; &nbsp;process continues, with ever increasing =
values for
              the TTL field,</div>
            <div>&nbsp; &nbsp;until the packets actually reach the =
destination.
              Because no</div>
            <div>&nbsp; &nbsp;application listens to port 33434 at the
              destination, the destination</div>
            <div>&nbsp; &nbsp;returns ICMP Destination Unreachable =
Messages
              indicating an</div>
            <div>&nbsp; &nbsp;unreachable port. This event indicates to =
the
              Traceroute application</div>
            <div>&nbsp; &nbsp;that it is finished. &nbsp;The Traceroute =
program
              displays the round-trip</div>
            <div>&nbsp; &nbsp;delay associated with each of the =
attempts.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 16]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Note that IP routing may be asymmetric. =
While
              Traceroute reveals the</div>
            <div>&nbsp; &nbsp;path between a source and destination, it =
may not
              reveal the reverse</div>
            <div>&nbsp; &nbsp;path.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A few ICMP extensions ([ICMP-Ext], =
[ICMP-MP],
              [ICMP-Int]) have been</div>
            <div>&nbsp; &nbsp;defined in the context of Traceroute. =
These
              extensions augment the</div>
            <div>&nbsp; &nbsp;ICMP Destination Unreachable message, and =
can be
              used by Traceroute</div>
            <div>&nbsp; &nbsp;applications.</div>
            <div><br>
            </div>
            <div>3.2. Bidirectional Forwarding Detection (BFD)</div>
            <div><br>
            </div>
            <div>3.2.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;While multiple OAM mechanisms have been =
defined for
              various protocols</div>
            <div>&nbsp; &nbsp;in the protocol stack, Bidirectional =
Forwarding
              Detection [BFD],</div>
            <div>&nbsp; &nbsp;defined by the IETF BFD working group, is =
a generic
              OAM mechanism</div>
            <div>&nbsp; &nbsp;that can be deployed over various =
encapsulating
              protocols, and in</div>
            <div>&nbsp; &nbsp;various medium types. The IETF has defined =
variants
              of the protocol</div>
            <div>&nbsp; &nbsp;for IP ([BFD-IP], [BFD-Multi]), for MPLS =
LSPs
              [BFD-LSP], and for PWE3</div>
            <div>&nbsp; &nbsp;[BFD-VCCV]. The usage of BFD in MPLS-TP is =
defined
              in [MPLS-TP-CC-</div>
            <div>&nbsp; &nbsp;CV].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD includes two main OAM functions, using =
two types
              of BFD packets:</div>
            <div>&nbsp; &nbsp;BFD Control packets, and BFD Echo =
packets.</div>
            <div><br>
            </div>
            <div>3.2.2. BFD Control</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;BFD supports a bidirectional continuity =
check, using
              BFD control</div>
            <div>&nbsp; &nbsp;packets, that are exchanged within a BFD =
session.
              BFD sessions</div>
            <div>&nbsp; &nbsp;operate in one of two modes:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Asynchronous mode (i.e. proactive): in =
this mode
              BFD control</div>
            <div>&nbsp; &nbsp; &nbsp; packets are sent periodically. =
When the receiver
              detects that no</div>
            <div>&nbsp; &nbsp; &nbsp; BFD control packet have been =
received during a
              predetermined</div>
            <div>&nbsp; &nbsp; &nbsp; period of time, a failure is =
detected.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Demand mode: in this mode, BFD control =
packets are
              sent on-demand.</div>
            <div>&nbsp; &nbsp; &nbsp; Upon need, a system initiates a =
series of BFD
              control packets to</div>
            <div>&nbsp; &nbsp; &nbsp; verify the liveness of the =
session. BFD control
              packets are sent</div>
            <div>&nbsp; &nbsp; &nbsp; independently in each =
direction.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Each of the end-points of the monitored =
path
              maintains its own</div>
            <div>&nbsp; &nbsp;session identification, called a =
Discriminator, both
              of which are</div>
            <div>&nbsp; &nbsp;included in the BFD Control Packets that =
are
              exchanged between the</div>
            <div>&nbsp; &nbsp;end-points. &nbsp;At the time of session =
establishment,
              the Discriminators</div>
            <div>&nbsp; &nbsp;are exchanged between the two-end points. =
&nbsp;In
              addition, the</div>
            <div>&nbsp; &nbsp;transmission (and reception) rate is =
negotiated
              between the two end-</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 17]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;points, based on information included in =
the control
              packets. &nbsp;These</div>
            <div>&nbsp; &nbsp;transmission rates may be renegotiated =
during the
              session.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;During normal operation of the session, =
i.e. no
              failures are</div>
            <div>&nbsp; &nbsp;detected, the BFD session is in the Up =
state. &nbsp;If no
              BFD Control</div>
            <div>&nbsp; &nbsp;packets are received during a fixed period =
of time,
              called the</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Fixed, pre-configured or negotiated period of time
        (i.e.: BFD interval)</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div>&nbsp; &nbsp;Detection Time, the session is declared to =
be Down.
              The detection</div>
            <div>&nbsp; &nbsp;time is a function of the negotiated =
transmission
              time, and a</div>
            <div>&nbsp; &nbsp;parameter called Detect Mult. Detect Mult =
determines
              the number of</div>
            <div>&nbsp; &nbsp;missing BFD Control packets that cause the =
session
              to be declared as</div>
            <div>&nbsp; &nbsp;Down. This parameter is included in the =
BFD Control
              packet.</div>
            <div><br>
            </div>
            <div>3.2.3. BFD Echo</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;A BFD echo packet is sent to a peer =
system, and is
              looped back to the</div>
            <div>&nbsp; &nbsp;originator. The echo function can be used
              proactively, or on-demand.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The BFD echo function has been defined in =
BFD for
              IPv4 and IPv6</div>
            <div>&nbsp; &nbsp;([BFD-IP]), but is not used in BFD for =
MPLS LSPs,
              PWs, or in BFD for</div>
            <div>&nbsp; &nbsp;MPLS-TP.</div>
            <div><br>
            </div>
            <div>3.3. MPLS OAM</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IETF MPLS working group has defined =
OAM for MPLS
              LSPs. The</div>
            <div>&nbsp; &nbsp;requirements and framework of this effort =
are
              defined in [MPLS-OAM-</div>
            <div>&nbsp; &nbsp;FW] and [MPLS-OAM], respectively. The =
corresponding
              OAM mechanism</div>
            <div>&nbsp; &nbsp;defined, in this context, is LSP Ping =
[LSP-Ping].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping is based on ICMP Ping and just =
like its
              predecessor may be</div>
            <div>&nbsp; &nbsp;used in one of two modes:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o "Ping" mode: In this mode LSP ping is =
used for
              end-to-end</div>
            <div>&nbsp; &nbsp; &nbsp; connectivity verification between =
two LERs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o "Traceroute" mode: This mode is used for
              hop-by-hop fault</div>
            <div>&nbsp; &nbsp; &nbsp; isolation.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping extends the basic ICMP Ping =
operation (of
              data-plane</div>
            <div>&nbsp; &nbsp;connectivity verification) with =
functionality to
              verify data-plane</div>
            <div>&nbsp; &nbsp;vs. control-plane consistency for a =
Forwarding
              Equivalence Class</div>
            <div>&nbsp; &nbsp;(FEC) and also Maximum Transmission Unit =
(MTU)
              problems. The</div>
            <div>&nbsp; &nbsp;traceroute functionality may be used to =
isolate and
              localize the MPLS</div>
            <div>&nbsp; &nbsp;faults, using the Time-to-live (TTL) =
indicator to
              incrementally</div>
            <div>&nbsp; &nbsp;identify the sub-path of the LSP that is
              successfully traversed</div>
            <div>&nbsp; &nbsp;before the faulty link or node.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 18]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;It should be noted that LSP Ping supports =
unique
              identification of</div>
            <div>&nbsp; &nbsp;the LSP within an addressing domain. The
              identification is checked</div>
            <div>&nbsp; &nbsp;using the full FEC identification. LSP =
Ping is
              easily extensible to</div>
            <div>&nbsp; &nbsp;include additional information needed to =
support new
              functionality,</div>
            <div>&nbsp; &nbsp;by use of Type-Length-Value (TLV) =
constructs. The
              usage of TLVs is</div>
            <div>&nbsp; &nbsp;typically not easy to perform in hardware, =
and is
              thus typically</div>
            <div>&nbsp; &nbsp;handled by the control plane.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;LSP Ping supports both asynchronous, as =
well as,
              on-demand</div>
            <div>&nbsp; &nbsp;activation.</div>
            <div><br>
            </div>
            <div>3.4. MPLS-TP OAM</div>
            <div><br>
            </div>
            <div>3.4.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The MPLS working group is currently =
working on
              defining the OAM</div>
            <div>&nbsp; &nbsp;toolset that fulfills the requirements for =
MPLS-TP
              OAM. The full set</div>
            <div>&nbsp; &nbsp;of requirements for MPLS-TP OAM are =
defined in
              [MPLS-TP-OAM], and</div>
            <div>&nbsp; &nbsp;include both general requirements for the =
behavior
              of the OAM</div>
            <div>&nbsp; &nbsp;mechanisms and a set of operations that =
should be
              supported by the</div>
            <div>&nbsp; &nbsp;OAM toolset. &nbsp;The set of mechanisms =
required are
              further elaborated</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW], which describes the =
general
              architecture of the OAM</div>
            <div>&nbsp; &nbsp;system as well as giving overviews of the
              functionality of the OAM</div>
            <div>&nbsp; &nbsp;toolset.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Some of the basic requirements for the OAM =
toolset
              for MPLS-TP are:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o MPLS-TP OAM must be able to support both =
an IP
              based and non-IP</div>
            <div>&nbsp; &nbsp; &nbsp; based environment. If the network =
is IP based,
              i.e. IP routing and</div>
            <div>&nbsp; &nbsp; &nbsp; forwarding are available, then the =
MPLS-TP OAM
              toolset should rely</div>
            <div>&nbsp; &nbsp; &nbsp; on the IP routing and forwarding =
capabilities. On
              the other hand,</div>
            <div>&nbsp; &nbsp; &nbsp; in environments where IP =
functionality is not
              available, the OAM</div>
            <div>&nbsp; &nbsp; &nbsp; tools must still be able to =
operate without
              dependence on IP</div>
            <div>&nbsp; &nbsp; &nbsp; forwarding and routing.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o OAM packets and the user traffic are =
required to
              be congruent</div>
            <div>&nbsp; &nbsp; &nbsp; (i.e. OAM packets are transmitted =
in-band) and
              there is a need to</div>
            <div>&nbsp; &nbsp; &nbsp; differentiate OAM packets from =
user-plane ones.
              Inherent in this</div>
            <div>&nbsp; &nbsp; &nbsp; requirement is the principle that =
MPLS-TP OAM be
              independent of</div>
            <div>&nbsp; &nbsp; &nbsp; any existing control-plane, =
although it should
              not preclude use of</div>
            <div>&nbsp; &nbsp; &nbsp; the control-plane =
functionality.</div>
            <div><br>
            </div>
            <div>3.4.2. Generic Associated Channel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In order to address the requirement for =
in-band
              transmission of MPLS-</div>
            <div>&nbsp; &nbsp;TP OAM traffic, MPLS-TP uses a Generic =
Associated
              Channel (G-ACh),</div>
            <div>&nbsp; &nbsp;defined in [G-ACh] for LSP-based OAM =
traffic. This
              mechanism is based</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 19]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;on the same concepts as the PWE3 ACH and =
VCCV
              mechanisms. &nbsp;However,</div>
            <div>&nbsp; &nbsp;to address the needs of LSPs as =
differentiated from
              PW, the following</div>
            <div>&nbsp; &nbsp;concepts were defined for [G-ACh]:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o An Associated Channel Header (ACH), that =
uses a
              format similar to</div>
            <div>&nbsp; &nbsp; &nbsp; the PW Control Word, is a 4-byte =
header that is
              prepended to OAM</div>
            <div>&nbsp; &nbsp; &nbsp; packets.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o A Generic Associated Label (GAL). The =
GAL is a
              reserved MPLS label</div>
            <div>&nbsp; &nbsp; &nbsp; value (13) that indicates that the =
packet is an
              ACH packet and the</div>
            <div>&nbsp; &nbsp; &nbsp; payload follows immediately after =
the label
              stack.</div>
            <div><br>
            </div>
            <div>3.4.3. MPLS-TP OAM Toolset</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;To address the functionality that is =
required of the
              OAM toolset, the</div>
            <div>&nbsp; &nbsp;MPLS WG conducted an analysis of the =
existing IETF
              and ITU-T OAM</div>
            <div>&nbsp; &nbsp;mechanisms and their ability to fulfill =
the required
              functionality.</div>
            <div>&nbsp; &nbsp;The conclusions of this analysis are =
documented in
              [OAM-Analys]. The</div>
            <div>&nbsp; &nbsp;MPLS working group currently plans to use =
a mixture
              of OAM mechanisms</div>
            <div>&nbsp; &nbsp;that are based on various existing =
standards, and
              adapt them to the</div>
            <div>&nbsp; &nbsp;requirements of [MPLS-TP-OAM]. Some of the =
main
              building blocks of</div>
            <div>&nbsp; &nbsp;this solution are based on:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Bidirectional Forwarding Detection =
([BFD],
              [BFD-LSP]) for</div>
            <div>&nbsp; &nbsp; &nbsp; proactive continuity check and =
connectivity
              verification.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o LSP Ping as defined in [LSP-Ping] for =
on-demand
              connectivity</div>
            <div>&nbsp; &nbsp; &nbsp; verification.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o New protocol packets, using G-ACH, to =
address
              different</div>
            <div>&nbsp; &nbsp; &nbsp; functionality.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Performance measurement protocols that =
are based
              on the</div>
            <div>&nbsp; &nbsp; &nbsp; functionality that is described in =
[ITU-T-Y1731].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The following sub-sections describe the =
OAM tools
              defined for MPLS-TP</div>
            <div>&nbsp; &nbsp;as described in [TP-OAM-FW].</div>
            <div><br>
            </div>
            <div>3.4.3.1. Continuity Check and Connectivity =
Verification</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Continuity Check and Connectivity =
Verification are
              presented in</div>
            <div>&nbsp; &nbsp;Section 2.2.5. of this document. &nbsp;As =
presented
              there, these tools may</div>
            <div>&nbsp; &nbsp;be used either proactively or on-demand. =
&nbsp;When using
              these tools</div>
            <div>&nbsp; &nbsp;proactively, they are generally used in =
tandem.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;For MPLS-TP there are two distinct tools, =
the
              proactive tool is</div>
            <div>&nbsp; &nbsp;defined in [TP-CC-CV] while the on-demand =
tool is
              defined in</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 20]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OnDemand-CV].Proactively [MPLS-TP-OAM] =
states that
              the function</div>
            <div>&nbsp; &nbsp;should allow the MEPs to monitor the =
liveness and
              connectivity of a</div>
            <div>&nbsp; &nbsp;transport path. In on-demand mode, this =
function
              should support</div>
            <div>&nbsp; &nbsp;monitoring between the MEPs and, in =
addition,
              between a MEP and MIP.</div>
            <div>&nbsp; &nbsp;[TP-OAM-FW] highlights, &nbsp;when =
performing
              Connectivity Verification,</div>
            <div>&nbsp; &nbsp;the need for the CC-V messages to include =
unique
              identification of</div>
            <div>&nbsp; &nbsp;the MEG that is being monitored and the =
MEP that
              originated the</div>
            <div>&nbsp; &nbsp;message.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The proactive tool [TP-CC-CV] is based on =
extensions
              to BFD (see</div>
            <div>&nbsp; &nbsp;Section 3.2. ) with the additional =
limitation that
              the transmission</div>
            <div>&nbsp; &nbsp;and receiving rates are based on =
configuration by
              the operator. &nbsp;The</div>
            <div>&nbsp; &nbsp;on-demand tool [OnDemand-CV] is an =
adaptation of LSP
              Ping (see</div>
            <div>&nbsp; &nbsp;Section 3.3. ) for the required behavior =
of MPLS-TP.</div>
            <div><br>
            </div>
            <div>3.4.3.2. Route Tracing</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-TP-OAM] defines that there is a need =
for
              functionality that</div>
            <div>&nbsp; &nbsp;would allow a path end-point to identify =
the
              intermediate and end-</div>
            <div>&nbsp; &nbsp;points of the path. This function would be =
used in
              on-demand mode.</div>
            <div>&nbsp; &nbsp;Normally, this path will be used for =
bidirectional
              PW, LSP, and</div>
            <div>&nbsp; &nbsp;sections, however, unidirectional paths =
may be
              supported only if a</div>
            <div>&nbsp; &nbsp;return path exists. &nbsp;The tool for =
this is based on
              the LSP Ping (see</div>
            <div>&nbsp; &nbsp;Section 3.3. ) functionality and is =
described in
              [OnDemand-CV].</div>
            <div><br>
            </div>
            <div>3.4.3.3. Lock Instruct</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The Lock Instruct function [Lock-Loop] is =
used to
              notify a transport</div>
            <div>&nbsp; &nbsp;path end-point of an administrative need =
to disable
              the transport</div>
            <div>&nbsp; &nbsp;path. &nbsp;This functionality will =
generally be used in
              conjunction with</div>
            <div>&nbsp; &nbsp;some intrusive OAM function, e.g. =
Performance
              measurement, Diagnostic</div>
            <div>&nbsp; &nbsp;testing, to minimize the side-effect on =
user data
              traffic.</div>
            <div><br>
            </div>
            <div>3.4.3.4. Lock Reporting</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Lock Reporting is a function used by an =
end-point of
              a path to report</div>
            <div>&nbsp; &nbsp;to its far-end end-point that a lock =
condition has
              been affected on</div>
            <div>&nbsp; &nbsp;the path.</div>
            <div><br>
            </div>
            <div>3.4.3.5. Alarm Reporting</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Alarm Reporting is a function used by an
              intermediate point of a</div>
            <div>&nbsp; &nbsp;path, that becomes aware of a fault on the =
path, to
              report to the</div>
            <div>&nbsp; &nbsp;end-points of the path. [TP-OAM-FW] states =
that this
              may occur as a</div>
            <div>&nbsp; &nbsp;result of a defect condition discovered at =
a server
              sub-layer. This</div>
            <div>&nbsp; &nbsp;generates an Alarm Indication Signal (AIS) =
that
              continues until the</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 21]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;fault is cleared. The consequent action of =
this
              function is detailed</div>
            <div>&nbsp; &nbsp;in [TP-OAM-FW].</div>
            <div><br>
            </div>
            <div>3.4.3.6. Remote Defect Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Remote Defect Indication (RDI) is used =
proactively
              by a path end-</div>
            <div>&nbsp; &nbsp;point to report to its peer end-point that =
a defect
              is detected on a</div>
            <div>&nbsp; &nbsp;bidirectional connection between them. =
[MPLS-TP-OAM]
              points out that</div>
            <div>&nbsp; &nbsp;this function may be applied to a =
unidirectional LSP
              only if there a</div>
            <div>&nbsp; &nbsp;return path exists. &nbsp;[TP-OAM-FW] =
points out that
              this function is</div>
            <div>&nbsp; &nbsp;associated with the proactive CC-V =
function.</div>
            <div><br>
            </div>
            <div>3.4.3.7. Client Failure Indication</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Client Failure Indication (CFI) is defined =
in
              [MPLS-TP-OAM] to allow</div>
            <div>&nbsp; &nbsp;the propagation information from one edge =
of the
              network to the</div>
            <div>&nbsp; &nbsp;other. The information concerns a defect =
to a
              client, in the case</div>
            <div>&nbsp; &nbsp;that the client does not support alarm =
notification.</div>
            <div><br>
            </div>
            <div>3.4.3.8. Packet Loss Measurement (LM)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Packet Loss Measurement is a function used =
to verify
              the quality of</div>
            <div>&nbsp; &nbsp;the service. This function indicates the =
ratio of
              packets that are</div>
            <div>&nbsp; &nbsp;not delivered out of all packets that are
              transmitted by the path</div>
            <div>&nbsp; &nbsp;source.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;There are two possible ways of determining =
this
              measurement:</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Using OAM packets, it is possible to =
compute the
              statistics based</div>
            <div>&nbsp; &nbsp; &nbsp; on a series of OAM packets. This, =
however, has
              the disadvantage of</div>
            <div>&nbsp; &nbsp; &nbsp; being artificial, and may not be =
representative
              since part of the</div>
            <div>&nbsp; &nbsp; &nbsp; packet loss may be dependent upon =
packet sizes.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Not just packet sizes. Things like implementation (as I
        mentioned above with the comment about the accuracy or
        truthfulness of the data plane processing of OAM packets).
        &nbsp;Doing very accurate RTT as a simple example, with just IP
        Pings, is a tricky thing to make work. &nbsp;Also, it is =
important to
        mention that the scale in terms of number of packets, number of
        tests, etc=85 can and will impact these parameters too.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Sending delimiting messages for the =
start and end
              of a measurement</div>
            <div>&nbsp; &nbsp; &nbsp; period during which the source and =
sink of the
              path count the</div>
            <div>&nbsp; &nbsp; &nbsp; packets transmitted and received. =
After the end
              delimiter, the</div>
            <div>&nbsp; &nbsp; &nbsp; ratio would be calculated by the =
path OAM entity.</div>
            <div><br>
            </div>
            <div>3.4.3.9. Packet Delay Measurement (DM)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Packet Delay Measurement is a function =
that is used
              to measure one-</div>
            <div>&nbsp; &nbsp;way or two-way delay of a packet =
transmission
              between a pair of the</div>
            <div>&nbsp; &nbsp;end-points of a path (PW, LSP, or =
Section). Where:</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 22]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o One-way packet delay is the time elapsed =
from the
              start of</div>
            <div>&nbsp; &nbsp; &nbsp; transmission of the first bit of =
the packet by a
              source node until</div>
            <div>&nbsp; &nbsp; &nbsp; the reception of the last bit of =
that packet by
              the destination</div>
            <div>&nbsp; &nbsp; &nbsp; node.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;o Two-way packet delay is the time elapsed =
from the
              start of</div>
            <div>&nbsp; &nbsp; &nbsp; transmission of the first bit of =
the packet by a
              source node until</div>
            <div>&nbsp; &nbsp; &nbsp; the reception of the last bit of =
the loop-backed
              packet by the</div>
            <div>&nbsp; &nbsp; &nbsp; same source node, when the =
loopback is performed
              at the packet's</div>
            <div>&nbsp; &nbsp; &nbsp; destination node.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Similarly to the packet loss measurement =
this could
              be performed in</div>
            <div>&nbsp; &nbsp;either of the two ways outlined =
above.</div>
            <div><br>
            </div>
            <div>3.5. PWE3 OAM</div>
            <div><br>
            </div>
            <div>3.5.1. PWE3 OAM using Virtual Circuit Connectivity
              Verification (VCCV)</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV, as defined in [VCCV], provides a =
means for
              end-to-end fault</div>
            <div>&nbsp; &nbsp;detection and diagnostics tools to be =
extended for
              PWs (regardless of</div>
            <div>&nbsp; &nbsp;the underlying tunneling technology). The =
VCCV
              switching function</div>
            <div>&nbsp; &nbsp;provides a control channel associated with =
each PW
              (based on the PW</div>
            <div>&nbsp; &nbsp;Associated Channel Header (ACH) which is =
defined in
              [PW-ACH]), and</div>
            <div>&nbsp; &nbsp;allows transmitting the OAM packets =
in-band with PW
              data (using CC</div>
            <div>&nbsp; &nbsp;Type 1: In-band VCCV).</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV currently supports the following OAM
              mechanisms: ICMP Ping, LSP</div>
            <div>&nbsp; &nbsp;Ping, and BFD. ICMP and LSP Ping are IP =
encapsulated
              before being</div>
            <div>&nbsp; &nbsp;sent over the PW ACH. BFD for VCCV =
[BFD-VCCV]
              supports two modes of</div>
            <div>&nbsp; &nbsp;encapsulation - either IP/UDP encapsulated =
(with
              IP/UDP header) or</div>
            <div>&nbsp; &nbsp;PW-ACH encapsulated (with no IP/UDP =
header) and
              provides support to</div>
            <div>&nbsp; &nbsp;signal the AC status. The use of the VCCV =
control
              channel provides</div>
            <div>&nbsp; &nbsp;the context, based on the MPLS-PW label, =
required to
              bind and</div>
            <div>&nbsp; &nbsp;bootstrap the BFD session to a particular =
pseudo
              wire (FEC),</div>
            <div>&nbsp; &nbsp;eliminating the need to exchange =
Discriminator
              values.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV consists of two components: (1) =
signaled
              component to</div>
            <div>&nbsp; &nbsp;communicate VCCV capabilities as part of =
VC label,
              and (2) switching</div>
            <div>&nbsp; &nbsp;component to cause the PW payload to be =
treated as a
              control packet.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;VCCV is not directly dependent upon the =
presence of
              a control plane.</div>
            <div>&nbsp; &nbsp;The VCCV capability negotiation may be =
performed as
              part of the PW</div>
            <div>&nbsp; &nbsp;signaling when LDP is used. In case of =
manual
              configuration of the</div>
            <div>&nbsp; &nbsp;PW, it is the responsibility of the =
operator to set
              consistent</div>
            <div>&nbsp; &nbsp;options at both ends.</div>
          </div>
        </blockquote>
      </span>
      <div><br>
      </div>
      <div>TOM: Might be helpful to note that the static mode was
        created specifically to handle the MPLS-TP cases where no
        control plane was a requirement. However, new use cases such as
        pure mobile backhaul, etc=85 find this functionality useful =
too.</div>
      <div><br>
      </div>
      <span id=3D"OLK_SRC_BODY_SECTION">
        <blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" =
style=3D"BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
          0 0 5;">
          <div text=3D"#000000" bgcolor=3D"#FFFFFF">
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 23]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>3.5.2. PWE3 OAM using G-ACh</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;As mentioned above, VCCV enables OAM for =
PWs by
              using a control</div>
            <div>&nbsp; &nbsp;channel for OAM packets. When PWs are used =
in
              MPLS-TP networks,</div>
            <div>&nbsp; &nbsp;rather than the control channels defined =
in VCCV,
              the G-ACh can be</div>
            <div>&nbsp; &nbsp;used as an alternative control channel. =
The usage of
              the G-ACh for</div>
            <div>&nbsp; &nbsp;PWs is defined in [PW-G-ACh].</div>
            <div><br>
            </div>
            <div>3.6. OWAMP and TWAMP</div>
            <div><br>
            </div>
            <div>3.6.1. Overview</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IPPM working group in the IETF defines =
common
              criteria and</div>
            <div>&nbsp; &nbsp;metrics for measuring performance of IP =
traffic
              ([IPPM-FW]). Some of</div>
            <div>&nbsp; &nbsp;the key RFCs published by this working =
group have
              defined metrics for</div>
            <div>&nbsp; &nbsp;measuring connectivity [IPPM-Con], delay
              ([IPPM-1DM], [IPPM-2DM]),</div>
            <div>&nbsp; &nbsp;and packet loss [IPPM-1LM].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Alternative protocols for performance =
measurement
              are defined, for</div>
            <div>&nbsp; &nbsp;example, in MPLS-TP OAM ([MPLS-LM-DM], =
[TP-LM-DM]),
              and in Ethernet</div>
            <div>&nbsp; &nbsp;OAM [ITU-T-Y1731].</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The IPPM working group has defined not =
only metrics
              for performance</div>
            <div>&nbsp; &nbsp;measurement, but also protocols that =
define how the
              measurement is</div>
            <div>&nbsp; &nbsp;carried out. The One-way Active =
Measurement Protocol
              [OWAMP] and the</div>
            <div>&nbsp; &nbsp;Two-Way Active Measurement Protocol =
[TWAMP] define a
              method and</div>
            <div>&nbsp; &nbsp;protocol for measuring delay and packet =
loss in IP
              networks.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP [OWAMP] enables measurement of =
one-way
              characteristics of IP</div>
            <div>&nbsp; &nbsp;networks, such as one-way packet loss and =
one-way
              delay. &nbsp;For its</div>
            <div>&nbsp; &nbsp;proper operation OWAMP requires accurate =
time of day
              setting at its</div>
            <div>&nbsp; &nbsp;end points.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TWAMP [TWAMP] is a similar protocol that =
enables
              measurement of two-</div>
            <div>&nbsp; &nbsp;way (round trip) characteristics. =
&nbsp;TWAMP does not
              require accurate</div>
            <div>&nbsp; &nbsp;time of day, and, furthermore, allows the =
use of a
              simple session</div>
            <div>&nbsp; &nbsp;reflector, making it an attractive =
alternative to
              OWAMP.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP use two separate =
protocols: a
              Control plane protocol,</div>
            <div>&nbsp; &nbsp;and a Test plane protocol.</div>
            <div><br>
            </div>
            <div>3.6.2. Control and Test Protocols</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP control protocols run over =
TCP,
              while the test</div>
            <div>&nbsp; &nbsp;protocols run over UDP. &nbsp;The purpose =
of the control
              protocols is to</div>
            <div>&nbsp; &nbsp;initiate, start, and stop test sessions, =
and for
              OWAMP to fetch</div>
            <div>&nbsp; &nbsp;results. &nbsp;The test protocols =
introduce test packets
              (which contain</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 24]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;sequence numbers and timestamps) along the =
IP path
              under test</div>
            <div>&nbsp; &nbsp;according to a schedule, and record =
statistics of
              packet arrival.</div>
            <div>&nbsp; &nbsp;Multiple sessions may be simultaneously =
defined,
              each with a session</div>
            <div>&nbsp; &nbsp;identifier, and defining the number of =
packets to be
              sent, the amount</div>
            <div>&nbsp; &nbsp;of padding to be added (and thus the =
packet size),
              the start time,</div>
            <div>&nbsp; &nbsp;and the send schedule (which can be either =
a
              constant time between</div>
            <div>&nbsp; &nbsp;test packets or exponentially distributed
              pseudo-random). Statistics</div>
            <div>&nbsp; &nbsp;recorded conform to the relevant IPPM =
RFCs.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP and TWAMP test traffic is designed =
with
              security in mind. &nbsp;Test</div>
            <div>&nbsp; &nbsp;packets are hard to detect because they =
are simply
              UDP streams</div>
            <div>&nbsp; &nbsp;between negotiated port numbers, with =
potentially
              nothing static in</div>
            <div>&nbsp; &nbsp;the packets. &nbsp;OWAMP and TWAMP also =
include optional
              authentication</div>
            <div>&nbsp; &nbsp;and encryption for both control and test =
packets.</div>
            <div><br>
            </div>
            <div>3.6.3. OWAMP</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;OWAMP defines the following logical roles:
              Session-Sender, Session-</div>
            <div>&nbsp; &nbsp;Receiver, Server, Control-Client, and =
Fetch-Client.
              &nbsp;The Session-</div>
            <div>&nbsp; &nbsp;Sender originates test traffic that is =
received by
              the Session-</div>
            <div>&nbsp; &nbsp;Receiver. &nbsp;The Server configures and =
manages the
              session, as well as</div>
            <div>&nbsp; &nbsp;returning the results. &nbsp;The =
Control-Client initiates
              requests for</div>
            <div>&nbsp; &nbsp;test sessions, triggers their start, and =
may trigger
              their</div>
            <div>&nbsp; &nbsp;termination. &nbsp;The Fetch-Client =
requests the results
              of a completed</div>
            <div>&nbsp; &nbsp;session. &nbsp;Multiple roles may be =
combined in a single
              host - for</div>
            <div>&nbsp; &nbsp;example, one host may play the roles of
              Control-Client, Fetch-Client,</div>
            <div>&nbsp; &nbsp;and Session-Sender, and a second playing =
the roles
              of Server and</div>
            <div>&nbsp; &nbsp;Session-Receiver.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In a typical OWAMP session the =
Control-Client
              establishes a TCP</div>
            <div>&nbsp; &nbsp;connection to port 861 of the Server, =
which responds
              with a server</div>
            <div>&nbsp; &nbsp;greeting message indicating supported
              security/integrity modes. The</div>
            <div>&nbsp; &nbsp;Control-Client responds with the chosen
              communications mode and the</div>
            <div>&nbsp; &nbsp;Server accepts the modes. &nbsp;The =
Control-Client then
              requests and fully</div>
            <div>&nbsp; &nbsp;describes a test session to which the =
Server
              responds with its</div>
            <div>&nbsp; &nbsp;acceptance and supporting information. =
&nbsp;More than
              one test session</div>
            <div>&nbsp; &nbsp;may be requested with additional messages. =
&nbsp;The
              Control-Client then</div>
            <div>&nbsp; &nbsp;starts a test session and the Server =
acknowledges.
              &nbsp;The Session-</div>
            <div>&nbsp; &nbsp;Sender then sends test packets with =
pseudorandom
              padding to the</div>
            <div>&nbsp; &nbsp;Session-Receiver until the session is =
complete or
              until the Control-</div>
            <div>&nbsp; &nbsp;client stops the session. &nbsp;Once =
finished, the
              Fetch-Client sends a</div>
            <div>&nbsp; &nbsp;fetch request to the server, which =
responds with an
              acknowledgement</div>
            <div>&nbsp; &nbsp;and immediately thereafter the result =
data.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 25]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>3.6.4. TWAMP</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;TWAMP defines the following logical roles:
              session-sender, session-</div>
            <div>&nbsp; &nbsp;reflector, server, and control-client. =
&nbsp;These are
              similar to the</div>
            <div>&nbsp; &nbsp;OWAMP roles, except that the =
Session-Reflector does
              not collect any</div>
            <div>&nbsp; &nbsp;packet information, and there is no need =
for a
              Fetch-Client.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;In a typical TWAMP session the =
Control-Client
              establishes a TCP</div>
            <div>&nbsp; &nbsp;connection to port 862 of the Server, and =
mode is
              negotiated as in</div>
            <div>&nbsp; &nbsp;OWAMP. &nbsp;The Control-Client then =
requests sessions
              and starts them.</div>
            <div>&nbsp; &nbsp;The Session-Sender sends test packets with
              pseudorandom padding to</div>
            <div>&nbsp; &nbsp;the Session-Reflector which returns them =
with
              insertion of</div>
            <div>&nbsp; &nbsp;timestamps.</div>
            <div><br>
            </div>
            <div>3.7. Summary of OAM Functions</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Table 3 summarizes the OAM functions that =
are
              supported in each of</div>
            <div>&nbsp; &nbsp;the categories that were analyzed in this =
section.</div>
            <div><br>
            </div>
            <div>&nbsp;
              =
&nbsp;+-----------+-------+--------+--------+-----------+-------+--------+=
</div>
            <div>&nbsp; &nbsp;| Standard &nbsp;|Continu|Connecti|Path =
&nbsp; &nbsp;|Defect &nbsp; &nbsp;
              |Perform|Other &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |ity =
&nbsp; &nbsp;|vity &nbsp;
              &nbsp;|Discover|Indications|ance &nbsp; |Function|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
|Check &nbsp;|Verifica|y &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;
              |Monitor|s &nbsp; &nbsp; &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; |tion &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              |ing &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+-------+--------+--------+-----------+-------+--------+=
</div>
            <div>&nbsp; &nbsp;|IP Ping &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; |Echo &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|IP &nbsp; &nbsp; &nbsp; &nbsp; | &nbsp; =
&nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|Tracerou| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|Traceroute | &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp;|te &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|BFD &nbsp; &nbsp; &nbsp; &nbsp;|BFD =
&nbsp; &nbsp;|BFD &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; =
|Control|Echo &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|MPLS OAM &nbsp; | &nbsp; &nbsp; &nbsp; =
|"Ping" &nbsp;|"Tracero| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|(LSP Ping) | &nbsp; &nbsp; &nbsp; |mode =
&nbsp; &nbsp;|ute" &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;|mode &nbsp; &nbsp;| =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|MPLS-TP &nbsp; &nbsp;|CC &nbsp; &nbsp; =
|CV/pro- |Route &nbsp; |-Alarm &nbsp; &nbsp;
              |-LM &nbsp; &nbsp;|-Diagnos|</div>
            <div>&nbsp; &nbsp;|OAM &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp; &nbsp; |active &nbsp;|Tracing | Reporting
              |-DM &nbsp; &nbsp;| tic Tes|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; |or on- &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;|-Client =
&nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; | t &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; |demand &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| =
Failure &nbsp; |
              &nbsp; &nbsp; &nbsp; |-Lock &nbsp; |</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;| Indication|
              &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;|-Remote &nbsp; &nbsp;|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 26]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; =
&nbsp;| Defect &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;| Indication|
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|PWE3 OAM &nbsp; |BFD &nbsp; &nbsp;|-BFD =
&nbsp; &nbsp;|LSP-Ping| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; |-ICMP &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; | Ping &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; |-LSP- &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; | Ping &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; |
              &nbsp; &nbsp; &nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;+ --------- + ----- + ------ + ------ + =
--------- +
              ----- + ------ +</div>
            <div>&nbsp; &nbsp;|OWAMP and &nbsp;| &nbsp; &nbsp; &nbsp; | =
&nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;
              |-Delay | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp; &nbsp;|TWAMP &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; =
&nbsp; | &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp; &nbsp; &nbsp;| =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
              measur| &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; |
              ement | &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;
              |-Packet| &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; |
              loss &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; |
              measur| &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; |
              ement | &nbsp; &nbsp; &nbsp; &nbsp;|</div>
            <div>&nbsp;
              =
&nbsp;+-----------+-------+--------+--------+-----------+-------+--------+=
</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;Table 3 Summary of OAM Functions</div>
            <div><br>
            </div>
            <div>4. Security Considerations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This memo presents an overview of existing =
OAM
              mechanisms, and</div>
            <div>&nbsp; &nbsp;proposes no new OAM mechanisms. Therefore, =
this
              document introduces</div>
            <div>&nbsp; &nbsp;no security considerations. However, the =
OAM
              mechanism reviewed in</div>
            <div>&nbsp; &nbsp;this document can and do present security =
issues.
              The reader is</div>
            <div>&nbsp; &nbsp;encouraged to review the Security =
Considerations
              section of each</div>
            <div>&nbsp; &nbsp;document reference by this memo.</div>
            <div><br>
            </div>
            <div>5. IANA Considerations</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;There are no new IANA considerations =
implied by this
              document.</div>
            <div><br>
            </div>
            <div>6. Acknowledgments</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;The authors gratefully acknowledge Sasha =
Vainshtein,
              Carlos</div>
            <div>&nbsp; &nbsp;Pignataro, David Harrington, Dan =
Romascanu, Ron
              Bonica and other</div>
            <div>&nbsp; &nbsp;members of the OPSAWG mailing list for =
their helpful
              comments.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;This document was prepared using
              2-Word-v2.0.template.dot.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 27]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>7. References</div>
            <div><br>
            </div>
            <div>7.1. Normative References</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[LSP-Ping] &nbsp; &nbsp;Kompella, K., =
Swallow, G., "Detecting
              Multi-Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Label Switched (MPLS) Data Plane
              Failures", RFC 4379,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-OAM] &nbsp; &nbsp;Nadeau, T., =
Morrow, M., Swallow, G.,
              Allan, D.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Matsushima, S., "Operations and
              Management (OAM)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Requirements for Multi-Protocol Label
              Switched (MPLS)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Networks", RFC 4377, February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-OAM-FW] Allan, D., Nadeau, T., "A =
Framework
              for Multi-Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Label Switching (MPLS) Operations and
              Management</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(OAM)", RFC 4378, February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Label] &nbsp; Ohta, H., "Assignment =
of the 'OAM
              Alert Label' for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Multiprotocol Label Switching
              Architecture (MPLS)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Operation and Maintenance (OAM)
              Functions", RFC 3429,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;November 2002.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-TP-OAM] Vigoureux, M., Ward, D., =
Betts, M.,
              "Requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;OAM in MPLS Transport Networks", RFC
              5860, May 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[G-ACh] &nbsp; &nbsp; &nbsp; Bocci, M., =
Vigoureux, M., Bryant, S.,
              "MPLS Generic</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Associated Channel", RFC 5586, June
              2009.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[VCCV] &nbsp; &nbsp; &nbsp; &nbsp;Nadeau, =
T., Pignataro, C., "Pseudowire
              Virtual Circuit</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Connectivity Verification (VCCV): A
              Control Channel</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;for Pseudowires", RFC 5085, December
              2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-ACH] &nbsp; &nbsp; &nbsp;Bryant, S., =
Swallow, G., Martini, L.,
              McPherson, D.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"Pseudowire Emulation Edge-to-Edge
              (PWE3) Control Word</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;for Use over an MPLS PSN", RFC 4385,
              February 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMPv4] &nbsp; &nbsp; &nbsp;Postel, J., =
"Internet Control Message
              Protocol", STD 5,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;RFC 792, September 1981.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMPv6] &nbsp; &nbsp; &nbsp;Conta, A., =
Deering, S., and M. Gupta,
              "Internet Control</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Message Protocol (ICMPv6) for the
              Internet Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Version 6 (IPv6) Specification", RFC
              4443, March 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-P2MP] &nbsp; Yasukawa, S., Farrel, =
A., King, D.,
              Nadeau, T.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"Operations and Management (OAM)
              Requirements for</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Point-to-Multipoint MPLS Networks",
              RFC 4687,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;September 2006.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 28]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-Ext] &nbsp; &nbsp;Bonica, R., Gan, =
D., Tappan, D.,
              Pignataro, C., "ICMP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Extensions for Multiprotocol Label
              Switching", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;4950, August 2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-MP] &nbsp; &nbsp; Bonica, R., Gan, =
D., Tappan, D.,
              Pignataro, C.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"Extended ICMP to Support Multi-Part
              Messages", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;4884, April 2007.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ICMP-Int] &nbsp; &nbsp;Atlas, A., Bonica, =
R., Pignataro, C.,
              Shen, N., Rivers,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;JR., "Extending ICMP for Interface and
              Next-Hop</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Identification", RFC 5837, April 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TCPIP-Tools] Kessler, G., Shepard, S., "A =
Primer On
              Internet and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;TCP/IP Tools and Utilities", RFC 2151,
              June 1997.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[NetTools] &nbsp; &nbsp;Stine, R., "FYI on =
a Network
              Management Tool Catalog:</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Tools for Monitoring and Debugging
              TCP/IP Internets</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;and Interconnected Devices", RFC 1147,
              April 1990.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-FW] &nbsp; &nbsp; Paxson, V., Almes, =
G., Mahdavi, J.,
              and Mathis, M.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"Framework for IP Performance
              Metrics", RFC 2330, May</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;1998.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-Con] &nbsp; &nbsp;Mahdavi, J., =
Paxson, V., "IPPM Metrics
              for Measuring</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Connectivity", RFC 2678, September
              1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-1DM] &nbsp; &nbsp;Almes, G., =
Kalidindi, S., Zekauskas,
              M., "A One-way</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Delay Metric for IPPM", RFC 2679,
              September 1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-1LM] &nbsp; &nbsp;Almes, G., =
Kalidindi, S., Zekauskas,
              M., "A One-way</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Packet Loss Metric for IPPM", RFC
              2680, September</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IPPM-2DM] &nbsp; &nbsp;Almes, G., =
Kalidindi, S., Zekauskas,
              M., "A Round-trip</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Delay Metric for IPPM", RFC 2681,
              September 1999.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OWAMP] &nbsp; &nbsp; &nbsp; Shalunov, S., =
Teitelbaum, B., Karp,
              A., Boote, J., and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Zekauskas, M., "A One-way Active
              Measurement Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(OWAMP)", RFC 4656, September 2006.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TWAMP] &nbsp; &nbsp; &nbsp; Hedayat, K., =
Krzanowski, R., Morton,
              A., Yum, K., and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Babiarz, J., "A Two-Way Active
              Measurement Protocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(TWAMP)", RFC 5357, October 2008.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD] &nbsp; &nbsp; &nbsp; &nbsp; Katz, =
D., Ward, D., "Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(BFD)", RFC 5880, June 2010.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 29]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-IP] &nbsp; &nbsp; &nbsp;Katz, D., =
Ward, D., "Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(BFD) for IPv4 and IPv6 (Single Hop)",
              RFC 5881, June</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-Gen] &nbsp; &nbsp; Katz, D., Ward, =
D., "Generic
              Application of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Bidirectional Forwarding Detection
              (BFD)", RFC 5882,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-Multi] &nbsp; Katz, D., Ward, D., =
"Bidirectional
              Forwarding Detection</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;(BFD) for Multihop Paths", RFC 5883,
              June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-LSP] &nbsp; &nbsp; Aggarwal, R., =
Kompella, K., Nadeau,
              T., and Swallow,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;G., "Bidirectional Forwarding
              Detection (BFD) for MPLS</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Label Switched Paths (LSPs)", RFC
              5884, June 2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[BFD-VCCV] &nbsp; &nbsp;Nadeau, T., =
Pignataro, C.,
              "Bidirectional Forwarding</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Detection (BFD) for the Pseudowire
              Virtual Circuit</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Connectivity Verification (VCCV)", RFC
              5885, June</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2010.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-OAM-FW] &nbsp; Busi, I., Allan, D., =
"Operations,
              Administration and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Maintenance Framework for MPLS-based
              Transport</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Networks ", RFC 6371, September 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-CC-CV] &nbsp; &nbsp;Allan, D., =
Swallow, G., Drake, J.,
              "Proactive</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Connectivity Verification, Continuity
              Check and Remote</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Defect indication for MPLS Transport
              Profile", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;6428, November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OnDemand-CV] Gray, E., Bahadur, N., =
Boutros, S.,
              Aggarwal, R. "MPLS</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;On-Demand Connectivity Verification
              and Route</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Tracing", RFC 6426, November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[MPLS-LM-DM] &nbsp;Frost, D., Bryant, S., =
"Packet Loss
              and Delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Measurement for MPLS Networks", RFC
              6374, September</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-LM-DM] &nbsp; &nbsp;Frost, D., Bryant, =
S., "A Packet Loss
              and Delay</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Measurement Profile for MPLS-Based
              Transport</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Networks", RFC 6375, September 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-Fault] &nbsp; &nbsp;Swallow, G., =
Fulignoli, A., Vigoureux,
              M., Boutros, S.,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;"MPLS Fault Management Operations,
              Administration, and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Maintenance (OAM)", RFC 6427, November
              2011.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 30]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[Lock-Loop] &nbsp; Boutros, S., Sivabalan, =
S., Aggarwal,
              R., Vigoureux,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;M., Dai, X., "MPLS Transport Profile
              Lock Instruct and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Loopback Functions", RFC 6435,
              November 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-CT] &nbsp; &nbsp;Betts, M., =
"Allocation of a Generic
              Associated Channel</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Type for ITU-T MPLS Transport Profile
              Operation,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Maintenance, and Administration
              (MPLS-TP OAM)", RFC</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;6671, November 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-Map] &nbsp; &nbsp; &nbsp;M. Aissaoui, =
P. Busschbach, L.
              Martini, M. Morrow, T.</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Nadeau, "Pseudowire (PW) Operations,
              Administration,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;and Maintenance (OAM) Message
              Mapping", RFC 6310, July</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[PW-G-ACh] &nbsp; &nbsp;Li, H., Martini, =
L., He, J., Huang,
              F., "Using the</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Generic Associated Channel Label for
              Pseudowire in the</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;MPLS Transport Profile (MPLS-TP)", RFC
              6423, November</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2011.</div>
            <div><br>
            </div>
            <div>7.2. Informative References</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Def] &nbsp; &nbsp; Andersson, L., Van =
Helvoort, H.,
              Bonica, R., Romascanu,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;D., Mansfield, S., "Guidelines for the
              use of the OAM</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;acronym in the IETF ", RFC 6291, June
              2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[OAM-Analys] &nbsp;Sprecher, N., Fang, L., =
"An Overview
              of the OAM Tool</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Set for &nbsp;MPLS based Transport
              Networks", RFC 6669,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;July 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[TP-Term] &nbsp; &nbsp; Van Helvoort, H., =
Andersson, L.,
              Sprecher, N., "A</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Thesaurus for the Terminology used in
              Multiprotocol</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Label Switching Transport Profile
              (MPLS-TP)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;drafts/RFCs and ITU-T's Transport
              Network</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Recommendations", work-in-progress,
              draft-ietf-mpls-</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;tp-rosetta-stone, July 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IEEE802.1ag] IEEE 802.1Q, "IEEE Standard =
for Local
              and metropolitan</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;area networks - Media Access Control
              (MAC) Bridges and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Virtual Bridged Local Area Networks",
              October 2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-Y1731] ITU-T Recommendation =
G.8013/Y.1731,
              "OAM Functions and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Mechanisms for Ethernet-based
              Networks", July 2011.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-Y1711] ITU-T Recommendation Y.1711,
              "Operation &amp; Maintenance</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;mechanism for MPLS networks", February
              2004.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 31]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[IEEE802.3ah] IEEE 802.3, "IEEE Standard =
for
              Information technology -</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Local and metropolitan area networks -
              Carrier sense</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;multiple access with collision
              detection (CSMA/CD)</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;access method and physical layer
              specifications",</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;clause 57, December 2008.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-T-G.806] ITU-T Recommendation G.806,
              "Characteristics of</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;transport equipment - Description
              methodology and</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;generic functionality", January 2009.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-G8113.2] ITU-T Recommendation
              G.8113.2/Y.1372.2, "Operations,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;administration and maintenance
              mechanisms for MPLS-TP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;networks using the tools defined for
              MPLS", November</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;2012.</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;[ITU-G8113.1] ITU-T Recommendation
              G.8113.1/Y.1372.1, "Operations,</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;Administration and Maintenance
              mechanism for MPLS-TP</div>
            <div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;in Packet Transport Network (PTN)",
              November 2012.</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Authors' Addresses</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Tal Mizrahi</div>
            <div>&nbsp; &nbsp;Marvell</div>
            <div>&nbsp; &nbsp;6 Hamada St.</div>
            <div>&nbsp; &nbsp;Yokneam, 20692</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class=3D"moz-txt-link-abbreviated"=
 href=3D"mailto:talmi@marvell.com">talmi@marvell.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Nurit Sprecher</div>
            <div>&nbsp; &nbsp;Nokia Siemens Networks</div>
            <div>&nbsp; &nbsp;3 Hanagar St. Neve Ne'eman B</div>
            <div>&nbsp; &nbsp;Hod Hasharon, &nbsp; 45241</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class=3D"moz-txt-link-abbreviated"=
 href=3D"mailto:nurit.sprecher@nsn.com">nurit.sprecher@nsn.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Elisa Bellagamba</div>
            <div>&nbsp; &nbsp;Ericsson</div>
            <div>&nbsp; &nbsp;6 Farogatan St.</div>
            <div>&nbsp; &nbsp;Stockholm, &nbsp; 164 40</div>
            <div>&nbsp; &nbsp;Sweden</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>Mizrahi, et al. &nbsp; &nbsp; &nbsp; &nbsp; Expires =
July 9, 2013 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; &nbsp; &nbsp; [Page 32]</div>
            <div>Internet-Draft &nbsp; &nbsp; &nbsp; Overview of OAM =
Mechanisms &nbsp; &nbsp; &nbsp; &nbsp;
              &nbsp; January 2013</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Phone: +46 761440785</div>
            <div>&nbsp; &nbsp;Email: <a class=3D"moz-txt-link-abbreviated"=
 =
href=3D"mailto:elisa.bellagamba@ericsson.com">elisa.bellagamba@ericsson.co=
m</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Yaacov Weingarten</div>
            <div>&nbsp; &nbsp;34 Hagefen St.</div>
            <div>&nbsp; &nbsp;Karnei Shomron, &nbsp; 4485500</div>
            <div>&nbsp; &nbsp;Israel</div>
            <div><br>
            </div>
            <div>&nbsp; &nbsp;Email: <a class=3D"moz-txt-link-abbreviated"=
 href=3D"mailto:wyaacov@gmail.com">wyaacov@gmail.com</a></div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
            </div>
          </div>
        </blockquote>
      </span><br>
    </div>
    <blockquote cite=3D"mid:50F437BF.8040005@cisco.com" type=3D"cite">
      <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
      <div class=3D"moz-cite-prefix">draft-ietf-opsawg-oam-overview
        authors,<br>
        <br>
        Here is my feedback on this document.<br>
        <br>
        1.<br>
        Is this document in line with <a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"http://tools.ietf.org/html/draft-ietf-trill-oam-req-04">http://too=
ls.ietf.org/html/draft-ietf-trill-oam-req-04</a>?
        <br>
        * For example, the following definitions could be reused.<br>
        <pre class=3D"newpage">   Fault: The term Fault refers to an =
inability to perform a required
   action, e.g., an unsuccessful attempt to deliver a packet.

   Defect: The term Defect refers to an interruption in the normal
   operation, such that over a period of time no packets are delivered
   successfully.

   Failure: The term Failure refers to the termination of the required
   function over a longer period of time. Persistence of a defect for a
   period of time is interpreted as a failure.

* For example, on the basic abstract=20
Abstract

   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

Abstract (draft-ietf-trill-oam-req-04)

   OAM (Operations, Administration and Maintenance) is a general term
   used to identify functions and toolsets to troubleshoot and monitor
   networks. This document presents, OAM Requirements applicable to
   TRILL.=20

So, as an example: does OAM include function?=20
I advice to review draft-ietf-trill-oam-req-04

2.=20
draft-ietf-trill-oam is not mentioned, while the abstract mentions:
   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.
Search for OAM in the current draft names (<a moz-do-not-send=3D"true" =
class=3D"moz-txt-link-freetext" =
href=3D"https://datatracker.ietf.org/">https://datatracker.ietf.org/</a>),=
 and you will find many references.
Ok, I see later on:=09
   This document focuses on IETF
   documents that have been published as RFCs, while other ongoing OAM-
   related work is outside the scope.
Ok, fine then: we don't need a reference to all the drafts.=20
However, draft-ietf-trill-oam is closed to be a RFC, and should be =
mentioned.


3.
Section 1
   The term OAM in this document refers to Operations, Administration
   and Maintenance [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-O=
AM-Def" title=3D"&quot;Guidelines for the use of the OAM acronym in the =
IETF &quot;">OAM-Def</a>], focusing on the forwarding plane of OAM.
What does it mean "focusing on the forwarding plane of OAM"?
Do you take a subset of the definition for this document?
Btw, I don't see a definition in the terminology section.
In section 2.2.3
   A Maintenance Point (MP) is a functional entity that is defined at a
   node in the network, and either initiates or reacts to OAM messages.
Which plane is MP?

4.
Section 1, Introduction
"Hence, management aspects are outside the scope of this document."
I don't understand which management aspects we speak about here.
</pre>
        5.<br>
        Clarifying question regarding 1.2<br>
        If speak about OWAMP or TWAMP 'synthetic traffic), is that data
        plane, control plane, or management plane?<br>
        Note that I found later on in the draft:<br>
        <pre class=3D"newpage">   OWAMP and TWAMP use two separate =
protocols: a Control plane protocol,
   and a Test plane protocol.</pre>
        Interestingly enough, after reading the document, I reviewed <a =
moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/bal=
lot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballo=
t/</a>,
        and saw the same feedback from Stewart Bryant:<br>
        <blockquote>
          <pre>Provide a clear view of OAM functionality and its =
relationship
to various =93planes=94 of networking (data plane, control plane,
management plane). In particular, the importance of
fate-sharing of OAM and user traffic flows in packet networks
should be explained.</pre>
        </blockquote>
        6.<br>
        <pre class=3D"newpage">I see a multiplication of "plane" terms =
in the IETF document, and in this document in particular.
I could find: forwarding plane, management plane, control plane, data =
plane, user plane, and test plane.
Way too many.
Please be consistent
</pre>
        7.<br>
        <pre class=3D"newpage">   Table 1 summarizes the IETF OAM =
related RFCs discussed in this
   document.

   Table 2 summarizes the OAM standards mentioned in this document.=20

You need to change the Table 2 description. Do you want to say something =
along the lines of:
   Table 2 summarizes the OAM standards specified by other Standard =
Development Organization=20
   (SDO) than the IETF, along with IETF references where applicable.


8.
Section 2.2.1
   For a formal definition of each term, refer to the references at the =
end of
   this document.
Without a reference to a specific RFC, this is the type of statement =
which is not useful: you have 5 pages of references.
You position this document as "An Overview of<span class=3D"h1"></span> =
Operations, Administration, and Maintenance (OAM) Mechanisms<span =
class=3D"h1"></span>", but you tell the reader: "if you want to know =
about the terms,
just read first all references!"

9.
You specify some terms and some OAM categories,=20
   <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.2">2.2.2</a>. OAM Maintenance Entities .......................... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
13">13</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.3">2.2.3</a>. OAM Maintenance Points ............................ =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
14">14</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.4">2.2.4</a>. Proactive and On-demand activation ................ =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.5">2.2.5</a>. Connectivity Verification and Continuity Checks ... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
         <a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#secti=
on-2.2.6">2.2.6</a>. Failures .......................................... =
<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#page-=
15">15</a>
... but you don't use them in the section 3

Just <u>one </u>example with section 3.2.2
-
   o Demand mode: in this mode, BFD control packets are sent on-demand.
      Upon need, a system initiates a series of BFD control packets to
      verify the liveness of the session
Instead of liveness, you have defined Connectivity Verification and =
Continuity Checks<span class=3D"h4"></span> in section 2.2.5
- OLD:
   Each of the end-points of the monitored path maintains its own
   session identification
NEW:
   Each of the MEP maintains its own session identification
OR NEW (actually I don't know)
   Each of the MP maintains its own session identification
- OLD
	A BFD echo packet is sent to a peer system
Peer system =3D MEP, MP, or something else?
- etc...=20

10.=20
This document is composed of a list of OAM content and references, but =
I'm really missing the document "scope and target audience".
When we did RFC 6632, which is the companion document, we had <a =
moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://tools.ietf.org/html/rfc6632#section-1.1">http://tools.ietf.=
org/html/rfc6632#section-1.1</a>
&nbsp;
   The target audience of the document is, on the one hand, IETF working
   groups, which aim to select appropriate standard management protocols
   and data models to address their needs concerning network management.
   On the other hand, the document can be used as an overview and
   guideline by non-IETF Standards Development Organizations (SDOs)
   planning to use IETF management technologies and data models for the
   realization of management applications.  The document can also be
   used to initiate a discussion between the bodies with the goal to
   gather new requirements and to detect possible gaps.  Finally, this
   document is directed to all interested parties that seek to get an
   overview of the current set of the IETF network management protocols
   such as network administrators or newcomers to the IETF.

You should have something similar.


11.
Section 3.6.1, put the paragraph 2 at the end of the section. The =
"alternative" in the following sentence would then make sense
   Alternative protocols for performance measurement are defined, for
   example, in MPLS-TP OAM ([<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-M=
PLS-LM-DM" title=3D"&quot;Packet Loss and Delay Measurement for MPLS =
Networks&quot;">MPLS-LM-DM</a>], [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-T=
P-LM-DM" title=3D"&quot;A Packet Loss and Delay Measurement Profile for =
MPLS-Based Transport Networks&quot;">TP-LM-DM</a>]), and in Ethernet
   OAM [<a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-08#ref-I=
TU-T-Y1731" title=3D"&quot;OAM Functions and Mechanisms for =
Ethernet-based Networks&quot;">ITU-T-Y1731</a>].


My conclusions: this document still needs some work

Regards, Benoit
&nbsp;
</pre>
      </div>
      <blockquote =
cite=3D"mid:20130111193616.19158.16205.idtracker@ietfa.amsl.com" =
type=3D"cite">
        <pre wrap=3D"">The IESG has received a request from the =
Operations and Management Area
Working Group WG (opsawg) to consider the following document:
- 'An Overview of Operations, Administration, and Maintenance (OAM)
   Mechanisms'
  &lt;draft-ietf-opsawg-oam-overview-08.txt&gt; 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
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by =
2013-01-25. Exceptionally, comments may be
sent to <a moz-do-not-send=3D"true" class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, =
please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Operations, Administration, and Maintenance (OAM) is a general term
   that refers to a toolset that can be used for fault detection and
   isolation, and for performance measurement. OAM mechanisms have been
   defined for various layers in the protocol stack, and are used with a
   variety of protocols.

   This document presents an overview of the OAM mechanisms that have
   been defined and are currently being defined by the IETF.




The file can be obtained via
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/">h=
ttp://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/</a>

IESG discussion can be tracked via
<a moz-do-not-send=3D"true" class=3D"moz-txt-link-freetext" =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/bal=
lot/">http://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/ballo=
t/</a>


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



</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </div>

</blockquote></div><br></div></body></html>=

--Apple-Mail=_37D55104-A690-4711-87D5-FDCA45807A2C--

--Apple-Mail=_6B2B593D-96C5-4FE4-AD09-6076CE6AEF7A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJS3UDHAAoJEPcO+I7eiUJZr1wP/isACdDIAyERf+o4mDqjf1vP
udmoX7qa+RGpKPmB2UtmQVka36EJxOmU7Kvc/8hDpw3M+VYpJ3I/Y2008xbWdFbm
cSmggU4TaVufE/b6BvUll+cKL0z+RPsDR4YS1iVV9FMBF+FXREwPTsSqhZrvFzAP
s5sQ3S4ZRgkaM0EnjdmuZdicnVXHn/+q0BTeUqsiPG5gRDKoW4MMUHhC9SjNU8VD
hDKSamIrz29KTVBOFuGcpbTjqaZ4xLpCnfvX+AkMmMjclKyeku8fcxKafnBalPJb
RIuu0CoZEwEIWP7X0VJgcCXlkY/47VHWBIk9Ks/ZyW0EmjNH1Ze+6HZF35eurJaY
tR0cIkjyb9qeIvIwNQLM5ooFQX0XWupdUVNO5F+6XDy7g0tPH3GPBygmmf8p3Fwj
ZW9GpnOAzw5SKrgwoDEWomlbT/kKYta/3lrGv2MGwP0UhZ7QC22lz+zH77pVWqTW
2DhCJ1CgfRZ2BYUA+N2/V/8M1HFbn/I9MP9t94+y8Kuw45BEpkm6dhDrACOd4Q/L
j7fPwIGJLI9YlJlaWz+leQN2XQ4NQ216UpkK+42voKcPrxUPnWrV1m3gD6Si8LRR
OM/FPg2f8MyvyFdAKGLm4oCMTs0F0bN+z0niZe5un0xjzA6+KnRxYtfhdMeKDBo5
7snjH3V2QiGhe5/237/j
=ApCx
-----END PGP SIGNATURE-----

--Apple-Mail=_6B2B593D-96C5-4FE4-AD09-6076CE6AEF7A--

From david.black@emc.com  Mon Jan 20 09:28:00 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D46AD1A01B2; Mon, 20 Jan 2014 09:28:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJfcwtG2YSN4; Mon, 20 Jan 2014 09:27:57 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 73EA61A01A2; Mon, 20 Jan 2014 09:27:57 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0KHPgUZ032284 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jan 2014 12:25:45 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s0KHPgUZ032284
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390238746; bh=RT/4T7uY/z4f6y23zmetvQNNNGE=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=SmTvDHLET61jTrFQ8/uI2oOJnpXmf0fGcQat+JhguuD9mf8wAVFX1z+Lzf6XTaJsT PLaCyYmlMtTT/PbalgUJwq2KTjXChROpjjW47gY/Fh90innGucbJ1iqB901UMoI0wI cK+DqvbAAuq9V2nyII61o+JD19Y63CT1DFE1Ff70=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s0KHPgUZ032284
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor); Mon, 20 Jan 2014 09:25:32 -0800
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0KHPTsH019845 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 20 Jan 2014 12:25:31 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Mon, 20 Jan 2014 12:25:28 -0500
From: "Black, David" <david.black@emc.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Date: Mon, 20 Jan 2014 12:25:28 -0500
Subject: RE: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Topic: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Index: Ac8Vj+sUxkixdvZlQDyGimrIKN8dNQAD35l5ABkZW3A=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F04796A@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F047824@MX15A.corp.emc.com> <3568aff546054a748d73d029c110c97b@AM3PR03MB532.eurprd03.prod.outlook.com>
In-Reply-To: <3568aff546054a748d73d029c110c97b@AM3PR03MB532.eurprd03.prod.outlook.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-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Cc: "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "Black, David" <david.black@emc.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 17:28:01 -0000

Alex,

> In the case of GRE-in-UDP the text goes into more detail, but, IMHO and F=
WIW,
> these details are not sufficient. AFAIK , the GRE encapsulators in most c=
ases
> follows RFC 2784 and not RFC 1701. The reduced GRE header adopted RFC 278=
4
> does not leave any place for meaningful "flow invariant fields" (unless y=
ou
> count the protocol type as such).  This means that the head-end of the UD=
P
> tunnel has to look beyond the IP and GRE headers of the packet to be
> encapsulated for these fields - and this is something that, to the best o=
f my
> understanding, GRE tries to prevent.

My understanding of the intent of the GRE in UDP draft is that the encapsul=
ator
really has to look beyond the GRE header to set the UDP source port in orde=
r to
get load balancing.  E.g., for MPLS/GRE/UDP, the ECMP hash for MPLS would b=
e
the basis for setting the UDP source port in a fashion analogous to Eric's =
message.
This requires encapsulators that can do that, and do analogous things for o=
ther
protocol stacks above GRE (e.g., those that do not use MPLS).

Thanks,
--David

> -----Original Message-----
> From: Alexander Vainshtein [mailto:Alexander.Vainshtein@ecitele.com]
> Sent: Monday, January 20, 2014 12:45 AM
> To: Black, David; stbryant@cisco.com
> Cc: mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; Randy Bush; lisp@ietf.o=
rg
> Subject: RE: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] O=
T
> (was Re: draft-ietf-mpls-in-udp)
>=20
> David,
> Lots of thanks for a detailed response.
>=20
> My original question dealt with the MPLS-in-UDP draft, where the relevant=
 text
> was quite brief:
>=20
> <quote>
>             Source Port of UDP
>=20
>                 This field contains a 16-bit entropy value that is
>                 generated by the ingress PE router. What algorithm is
>                 actually used by the ingress PE router to generate an
>                 entropy value is outside the scope of this doc. In the
>                 case where the flow does not need entropy, this field
>                 SHOULD be set to a randomly selected constant value to
>                 avoid packet reordering.
> <end quote>
>=20
> The answer given by Eric Rosen in http://www.ietf.org/mail-
> archive/web/mpls/current/msg11277.html (use the hash of the label stack o=
f the
> packet to be encapsulated ) resolves, IMO, this issue because the head-en=
d of
> the UDP tunnel (the encapsulator) looks at the label stack of the packet =
to be
> encapsulated in any case. Of course other methods are not precluded, but =
there
> is at least one method that is both reasonably simple and meaningful,
> especially because it is possible to add entropy to the label stack (RFC
> 6790).
>=20
> In the case of GRE-in-UDP the text goes into more detail, but, IMHO and F=
WIW,
> these details are not sufficient. AFAIK , the GRE encapsulators in most c=
ases
> follows RFC 2784 and not RFC 1701. The reduced GRE header adopted RFC 278=
4
> does not leave any place for meaningful "flow invariant fields" (unless y=
ou
> count the prtotocol type as such).  This means that the head-end of the U=
DP
> tunnel has to look beyond the IP and GRE headers of the packet to be
> encapsulated for these fields - and this is something that, to the best o=
f my
> understanding, GRE tries to prevent.
>=20
> My 2c,
>      Sasha
> ________________________________________
> From: Black, David <david.black@emc.com>
> Sent: Monday, January 20, 2014 5:30 AM
> To: Alexander Vainshtein; stbryant@cisco.com
> Cc: mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; Randy Bush; lisp@ietf.o=
rg;
> Black, David
> Subject: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (w=
as
> Re: draft-ietf-mpls-in-udp)
>=20
> Sasha,
>=20
> > But I would like to understand whether this protocol can really result =
in
> > reasonable distribution of traffic. "Reasonable" means that (a) there i=
s
> > sufficient entropy and (b) that the order in specific micro-flows is
> > preserved. The draft skips this issue (unless you consider a recommenda=
tion
> to
> > use a fixed  randomly selected source port value if the tunnel does not=
 need
> > ECMP a valid answer) .
>=20
> Well, there's a bit more in the draft than just a "randomly selected" val=
ue,
> as the ability to use ECMP on these tunnels is rather important (text quo=
ted
> is from Section 3 in the draft):
>=20
>    The ingress device SHOULD set
>    the UDP source port based on flow invariant fields from the payload
>    header, otherwise it should be set to a randomly selected constant
>    value, e.g. zero, to avoid packet flow reordering.  How a tunnel
>    ingress generates entropy from the payload is outside the scope of
>    this document.
>=20
> I suppose that more discussion and examples of "flow invariant fields"
> would be useful, although an attempt at a comprehensive listing would be
> pointless, IMHO.  An important situation is one where the tunnel ingress
> "knows" (because the network operator actually does know) what the protoc=
ol
> stack(s) is/are for the encapsulated traffic (e.g., HTTP/TCP/IP/GRE/IP) a=
nd
> hence can find the flow-invariant fields that it wants to use for that
> (those) specific stack(s).
>=20
> With good selection of flow-invariant fields wrt traffic mix, good
> distribution is possible.
>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Alexander
> Vainshtein
> > Sent: Wednesday, January 15, 2014 6:54 AM
> > To: stbryant@cisco.com
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org;
> Randy
> > Bush; jnc@mit.edu; lisp@ietf.org
> > Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: =
gre-
> in-
> > udp draft (was: RE: Milestones changed for tsvwg WG))
> >
> > Stewart, and all,
> > I fully agree that UDP checksums is not a real-life issue with the prot=
ocol
> in
> > question. They could probably help to check corrupted packets if corrup=
tion
> > happens when a packet passes thru a router (i.e. when the ingress data =
link
> > FCS has already been terminated and the egress data link FCS has not be=
en
> > generated yet). But this is hopefully rare - and since MPLS does not ca=
re
> > about it, why should the MPLS encapsulator care?
> >
> > I also do not think that congestion control is a serious issue for this
> > protocol, not in the least because the primary purpose of this protocol=
 is
> > ECMP.
> >
> > But I would like to understand whether this protocol can really result =
in
> > reasonable distribution of traffic. "Reasonable" means that (a) there i=
s
> > sufficient entropy and (b) that the order in specific micro-flows is
> > preserved. The draft skips this issue (unless you consider a recommenda=
tion
> to
> > use a fixed  randomly selected source port value if the tunnel does not=
 need
> > ECMP a valid answer) .
> >
> > Any ideas as to how reasonable distribution of traffic  can be achieved=
 with
> > this protocol?
> >
> > Regards,
> >        Sasha
> > Email: Alexander.Vainshtein@ecitele.com
> > Mobile: 054-9266302
> >
> > > -----Original Message-----
> > > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Stewart Bryant
> > > Sent: Wednesday, January 15, 2014 1:31 PM
> > > To: Randy Bush
> > > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org=
;
> > > wes@mti-systems.com; tsvwg@ietf.org; jnc@mit.edu
> > > Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE=
:
> gre-
> > in-
> > > udp draft (was: RE: Milestones changed for tsvwg WG))
> > >
> > > On 15/01/2014 11:08, Randy Bush wrote:
> > > > [ you insist on cc:ing me, so you get to endure my opinions ]
> > > >
> > > >> it seems that there are no valid statistics for the current Intern=
et
> > > >> to sustain your case.
> > > > as we discussed privately, there seem to be no real measurements to
> > > > sustain any case.  this is all conjecturbation.
> > > >
> > > > what i do not understand is why, given the lack of solid evidence t=
hat
> > > > we are in a safe space, you and others are not willing to spend a f=
ew
> > > > euro cents to have a reasonable level of assurance at this layer.
> > > >
> > > > randy
> > > Randy,
> > >
> > > It is not a few cents, it is likely the re-engineering of a lot of
> silicon.
> > >
> > > The reason that UDP is of interest is that the on path silicon knows =
how
> to
> > > process it, for example it knows how to to ECMP it.
> > >
> > > The reason that the UDP c/s is a problem for a tunneler is that it ne=
eds
> to
> > > have access to the whole pkt to calculate the c/s, but as you know th=
e
> > silicon
> > > optimised that access away a long time ago.
> > >
> > > The alternative would be UDP-lite, but the ability of on path silicon=
 to
> > process
> > > that as competently and as completely as it processes UDP is by no me=
ans
> > > clear.
> > >
> > > - Stewart
> > >
> > >
> > > _______________________________________________
> > > mpls mailing list
> > > mpls@ietf.org
> > > https://www.ietf.org/mailman/listinfo/mpls
>=20


From barryleiba.mailing.lists@gmail.com  Mon Jan 20 10:28:15 2014
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC2C91A022B; Mon, 20 Jan 2014 10:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.621
X-Spam-Level: 
X-Spam-Status: No, score=0.621 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6OnLuNHhjvDR; Mon, 20 Jan 2014 10:28:13 -0800 (PST)
Received: from mail-ve0-x230.google.com (mail-ve0-x230.google.com [IPv6:2607:f8b0:400c:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4321A021A; Mon, 20 Jan 2014 10:28:13 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id oz11so1853929veb.7 for <multiple recipients>; Mon, 20 Jan 2014 10:28:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=mRLrudKQP5g5HsORdCzgikX9aU3aYyDvZRqMJgKc2fA=; b=B/QP2nNhybuwtKPBIEAG9825T4DSw/iYPkRM40YqgNNL7odTLUu2gMUdmSUtRMxMBM tNHIBvUe+NafVz1V67Df4e8BJy3+LGAPBnAiRzGN5kJcdflRLOQ4UbpcNkmmIT+ZT1HS /9rbvbSTY+7lU2dqvbMy/HN4+71IkVM8gpgOrVOpibXpsSMkmn6pmYuigKRoK9urcNne stxW6QEyIDggtE2WddT6oQffXOsu0d3lcD4Fq5bZp+MePQQyIDtqdD2Q2PfEF3Oai5Ph SQou9wkxuXDPi8A+3JKE7X/ID9lgSECQSKFmlvuQB62CGsBYg4jb6AkDxb2wfcE/hiG6 sKdA==
MIME-Version: 1.0
X-Received: by 10.220.98.204 with SMTP id r12mr36810vcn.48.1390242492832; Mon, 20 Jan 2014 10:28:12 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.170.71 with HTTP; Mon, 20 Jan 2014 10:28:12 -0800 (PST)
In-Reply-To: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
References: <CAJxDCqUXWiMexON+ya-2mA2hF4gMK0D+8iY_kvvPEzLeF0BNig@mail.gmail.com>
Date: Mon, 20 Jan 2014 13:28:12 -0500
X-Google-Sender-Auth: 0NsZUnFmVfkAuJWCU5BC5l_Nxsc
Message-ID: <CAC4RtVDFVYcOqa_H6n8ys2FV+92P0yZLdB4He7_h3h_nB3OM8Q@mail.gmail.com>
Subject: Re: Last Call <draft-daboo-icalendar-rscale> (Non-Gregorian Recurrence Rules in iCalendar) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Gregory Yakushev <yakushev@google.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Calsify <calsify@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 18:28:15 -0000

I need to point out that the subject message (below) is NOT an
official IETF Last Call message, though the subject makes it look like
one.  It is a last call by the authors for comments, before they move
their document into the formal IETF process (most likely, getting an
AD to sponsor the document).

That said, as Grisha says: your comments are welcome.  It's always
better to get them in earlier.  Assuming that the authors pursue this
as a Standards Track document, a proper IETF Last Call will eventually
appear.

Barry, Applications AD

On Tue, Jan 14, 2014 at 4:29 AM, Gregory Yakushev <yakushev@google.com> wrote:
> This is last call for
> http://tools.ietf.org/html/draft-daboo-icalendar-rscale . The draft was
> extensively discussed at CalConnect (http://calconnect.org/), previous IETF
> discussion is on calsify@ietf.org .
>
> The draft functionality is currently fully implemented in Google Calendar.
> You can try it out using proprietary Google Calendar API:
> 1. Follow this link: http://goo.gl/tKTUQZ
> 2. Click on Oauth2.0 trigger in the upper right corner to authenticate
> 3. Enter your Google Calendar e-mail into calendarId field
> 4. Click Execute, you should get 200 OK
> 5. Now your non-Gregorian recurring event is visible in UI, embedded
> calendar, and any client that doesn't do recurrence expansion by itself
>
> Your comments are welcome,
> Grisha

From l.wood@surrey.ac.uk  Mon Jan 20 15:13:02 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061A01A0272; Mon, 20 Jan 2014 15:13:02 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ONO69m9g_X7; Mon, 20 Jan 2014 15:12:58 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id 551E41A022B; Mon, 20 Jan 2014 15:12:57 -0800 (PST)
Received: from [85.158.136.51:2109] by server-17.bemta-5.messagelabs.com id 31/E9-19152-87DADD25; Mon, 20 Jan 2014 23:12:56 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-49.messagelabs.com!1390259575!25528403!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1613 invoked from network); 20 Jan 2014 23:12:55 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-14.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 20 Jan 2014 23:12:55 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 20 Jan 2014 23:12:54 +0000
From: <l.wood@surrey.ac.uk>
To: <curtis@ipv6.occnc.com>
Date: Mon, 20 Jan 2014 23:11:05 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8WM2X1RbWDYR4VRMe+b3I1p2VF1gAAX75U
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346D6@EXMB01CMS.surrey.ac.uk>
References: Your message of "Fri, 17 Jan 2014 23:00:33 +0000." <290E20B455C66743BE178C5C84F1240847E63346D1@EXMB01CMS.surrey.ac.uk>, <201401202247.s0KMllSl047284@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401202247.s0KMllSl047284@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 23:13:02 -0000

> Router vendors focus on real needs identified by customers.  If this
> were to become something customers were bugging them about, then
> they'll do it.

And pollution of ports for other traffic, like congestion, is something
experienced by people who are not customers - the rest of the net.

Which is why this draft does not address the possibility of missent traffic=
,
and does not address congestion. Not a tunnel customer problem,
therefore not a vendor problem.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Curtis Villamizar [curtis@ipv6.occnc.com]
Sent: 20 January 2014 22:47
To: Wood L  Dr (Electronic Eng)
Cc: curtis@ipv6.occnc.com; stbryant@cisco.com; lars@netapp.com; joelja@bogu=
s.com; mpls@ietf.org; ietf@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

We are continuing to stray off topic, but...

Router vendors focus on real needs identified by customers.  If this
were to become something customers were bugging them about, then
they'll do it.  OTOH, most hardware in the field today can only track
one 32 bit FCS, given that only one L2 header would need this.  The
ability to run on existing hardware is important.

Perhaps you missed this:

> When a critical mass of routers hash on this new protocol number and
> port space we'll let you know and the MPLS WG can obsolete MPLS over
> UDP and replace it with MPLS over this new protocol.

Providers and router vendors are also aware that most routers look
only for protocol numbers 6 and 17 for load balancing on port
numbers.  So if the motivation of MPLS over UDP is an interim solution
to get ECMP, then not using UDP is not an option.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346D1@EXMB01CMS.surrey.ac.=
uk>
l.wood@surrey.ac.uk writes:
>
> Yes, it would be unreasonable for the router vendors themselves to design
> something with a trailing checksum and pseudo-header check that would mee=
t
> their forwarding needs while ensuring reliability.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 17 January 2014 18:05
> To: Wood L  Dr (Electronic Eng)
> Cc: stbryant@cisco.com; lars@netapp.com; joelja@bogus.com; mpls@ietf.org;=
 ietf@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting MPLS in UDP) to Proposed Standard
>
> In message <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.a=
c.uk>
> l.wood@surrey.ac.uk writes:
>
> > There's an opportunity to define a simple generic IPv6 encapsulating
> > mechanism a la UDP, but with a payload checksum of varying coverage
> > (header only, partial payload, full payload) and with the (stronger
> > than UDP) checksum placed at the end of the packet.
> >
> > Lloyd Wood
> > http://about.me/lloydwood
>
>
> Go for it!
>
> When a critical mass of routers hash on this new protocol number and
> port space we'll let you know and the MPLS WG can obsolete MPLS over
> UDP and replace it with MPLS over this new protocol.
>
> Thanks for offering to write this.
>
> Curtis
>
>
> > ________________________________________
> > From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryan=
t@cisco.com]
> > Sent: 16 January 2014 17:35
> > To: Eggert, Lars; Joel Jaeggli
> > Cc: mpls@ietf.org; IETF discussion list
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsu=
lating MPLS in UDP) to Proposed Standard
> >
> > On 16/01/2014 17:19, Eggert, Lars wrote:
> > > Hi,
> > >
> > > On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> > >> These tunnels are stateless
> > > yep. (But they don't have to be.)
> > Ah, they do if they are to scale. State at speed is really hard. The so=
rt
> > of systems we are talking about do things like pipeline counters
> > and it is loooooots of packets later before the counter is actually
> > incremented.
> > >>   The endpoints not the encapsulators have visibility into the
> > >> end-to-end loss latency properties of the path.
> > > Yep. But when you tunnel some L2 in UDP, apps that were limited to L2=
 domains - where not reacting to congestion may be OK - can now go over the=
 wider Internet, where this is not OK.
> > >
> > > I'd be great if those apps would change. But in the meantime, it's th=
e duty of the encapsulator - who enables this traffic to break out of an L2=
 domain and go over the wider net - to make sure the traffic it emits confo=
rms to our BCPs.
> > >
> > >>   the encapsulator is an intermediate hop, similar to any other rout=
er
> > >> in the path.
> > > It's not. For the rest of the network, that encapsulator is indisting=
uishable from any other app that sends UDP traffic.
> > >
> > > UDP is a transport-layer protocol, and we have practices how it is to=
 be used on the net. If you want to use it for encapsulation, you bind your=
self to these BCPs.
> > >
> > > Look at it the other way: if transport area folks would want to send =
MPLS packets into the network in some problematic way, I'm sure the routing=
 and ops folks would not be amused.
> > The root cause of the problem here is that UDP, has bifurcated into
> > a general purpose encapsulation.
> >
> > Stewart=

From lars@netapp.com  Tue Jan 21 05:22:53 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39F1F1A00EC; Tue, 21 Jan 2014 05:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.937
X-Spam-Level: 
X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TZ34nwMaV9-w; Tue, 21 Jan 2014 05:22:51 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 88C0F1A00CF; Tue, 21 Jan 2014 05:22:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,696,1384329600";  d="asc'?scan'208";a="97226067"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx11-out.netapp.com with ESMTP; 21 Jan 2014 05:22:51 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Tue, 21 Jan 2014 05:22:51 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPE6hVZzPPQlRcgk6ua2U45NfiYJqPto2A
Date: Tue, 21 Jan 2014 13:22:50 +0000
Message-ID: <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
References: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_43F78036-C5EC-458C-9F4D-22B8DDF299CC"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 13:22:53 -0000

--Apple-Mail=_43F78036-C5EC-458C-9F4D-22B8DDF299CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> You have made your assertions about your desire to uphold the purity
> of any new UDP applications and adhere to the BCP you wrote.
>=20
> You appear to be very nearly alone in this argument and certainly no
> one that works with MPLS is siding with you.

the reason we wrote the RFC when I was TSV AD was that we were seeing a =
whole bunch of questionable uses of UDP over the eyars and we were =
having the same arguments over and over. That's why we decided to write =
down the practices we expect users of UDP to follow. This is yet another =
such questionable use.

(Also, I don't appreciate you turning this into a personal argument.)

> In the end we can put anything we want in the RFC *but* IETF has never
> truly had the final word on what vendors and operators do in provider
> networks.

Aka the "take my toys and go home" argument. Heard it many times.

> In this case, regardless of what changes are made to the draft,
> implementations will offer at least the option for non-RFC behavior by
> using zero checksums and not using any congestion control.  And
> providers will make use of it, perhaps exclusively.

And there's nothing wrong with that - the BCP even says that one SHOULD =
NOT use congestion control for some deployment cases.

But for others, one SHOULD. For those, a mechanism needs to be =
available, i.e., it needs to be specified and implemented.

> The document might as well reflect reality, despite reality not
> conforming to your notions of architectural purity.

I'm sorry, but we have certain architectural principles in the Internet =
that we have IETF consensus on. At least since RFC2914, that includes =
the need to have congestion control in place.

There are always special deployment scenarios where these principles do =
not apply, and we typically explain in applicability statements when out =
specifications can only be safely used under certain conditions. I don't =
see any such statement in draft-ietf-mpls-in-udp, which to me means it's =
targeted at general Internet-wide use.

> The best course of action is to put a SHOULD in regarding checksums
> and put a SHOULD in regarding congestion avoidance.  Even the BCP does
> not go any further than to say a tunneling protocol SHOULD use
> congestion control and there were reasons that the word MUST was not
> acceptable in the BCP.

The SHOULD for congestion control needs to actually describe a mechanism =
that can be used when needed. It can't be a blanket "you SHOULD use =
something but we don't tell you what it is"-statement.

> If we are still arguing over two instances of SHOULD vs MUST we have
> wasted a lot of bandwidth on those two words.

It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs =
to be specified what is to be done. In the case of checksums, that's =
obvious (calculate it and check it); in the case of congestion control, =
some actual mechanism needs to be described (e.g., a circuit breaker).

> IMHO The only remaining question is whether the document can go =
forward
> with the definition of congestion control for MPLS over UDP left out
> of scope and for another document if a need arises.

In my opinion, it cannot.

> If this is not acceptable to you (I doubt it is) please indicate what
> you would like to see in the document and since this is IETF last call
> where consensus matters and no one individual has veto power, we'll
> have to see if there is consensus behind your proposed changes.

I would like the document to specify at the very least a circuit breaker =
mechanism, that stops the tunneled traffic if severe packet loss is =
detected along the path.

And this isn't about an "individual veto". This is about a document that =
is at the moment in violation of IETF consensus at least as far back as =
RFC2914.

Lars

--Apple-Mail=_43F78036-C5EC-458C-9F4D-22B8DDF299CC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUt50qdZcnpRveo1xAQK2uQP/ZqatIuOb8OeFnQecASThxV/kogHB2Q8h
qojxxjDxE7YLzI82TnOt0GF04I9ns4eZ8vd+wvz9ZLrEWlASpR4Ws7DmmBCs6GdX
y/g1rNsN5bE7J53EWM84baxWdE7EeKTliax8NDNd1YKoElcHrmJdU+QqmASEUCjB
nOwB1XSpTbc=
=LDDc
-----END PGP SIGNATURE-----

--Apple-Mail=_43F78036-C5EC-458C-9F4D-22B8DDF299CC--

From jari.arkko@piuha.net  Tue Jan 21 07:50:55 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4620F1A019F; Tue, 21 Jan 2014 07:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t0gjyZIyck5w; Tue, 21 Jan 2014 07:50:54 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CBC091A018D; Tue, 21 Jan 2014 07:50:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 64E692CEB1; Tue, 21 Jan 2014 17:50:53 +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 JYeLQJPySbMX; Tue, 21 Jan 2014 17:50:52 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D8B4E2CC48; Tue, 21 Jan 2014 17:50:52 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
Date: Tue, 21 Jan 2014 17:50:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
References: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
To: curtis@ipv6.occnc.com, Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1510)
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, "gen-art@ietf.org Gen-ART" <gen-art@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:50:55 -0000

Many thanks for your (once again) detailed review, Peter! And thank you =
Curtis for making the fixes. One comment below:

>> Make all references to the expansion of ECMP read "Equal-Cost =
Multipath" for
>> consistency with RFC 2991.
>=20
> ECMP is expanded on first use in compliance with RFC Editor quidelines
> for abbreviations.  ECMP is also expanded on first use within each
> section where it is used with the exception of one place where ECMP is
> contained in a verbatim excerpt in a quote from RFC6374.

I thought Peter was referring to the fact that your draft has some =
variation on the way the term is expanded, even outside verbatim =
examples:

> % grep -i 'equal' draft-ietf-mpls-multipath-use-03.txt
> draft-ietf-mpls-multipath-use-03.txt:94:   than parallel links =
includes Equal Cost MultiPath (ECMP) as applied
> draft-ietf-mpls-multipath-use-03.txt:148:   Equal Cost Multipath =
(ECMP)
> draft-ietf-mpls-multipath-use-03.txt:149:       Equal Cost Multipath =
(ECMP) is a specific form of multipath in
> draft-ietf-mpls-multipath-use-03.txt:229:       Equal-Cost Multi-Path =
(ECMP) load-balancing MUST NOT be performed
> draft-ietf-mpls-multipath-use-03.txt:288:   following paragraph in =
"Section 2.9.4 Equal Cost Multipath" gives the
> =85
> % grep -i "equal" rfc2991.txt
> rfc2991.txt:   allow "Equal-Cost Multipath" (ECMP) routing.  Some =
router
> =85

I think you could align other instances than those relating to verbatim =
text from RFC 5960 or 6374.

Anyway, minor things. I have balloted no-objection for this draft for =
the Thursday's IESG telechat. Thanks for your hard work, all.

Jari


From Alexander.Vainshtein@ecitele.com  Sun Jan 19 21:44:43 2014
Return-Path: <Alexander.Vainshtein@ecitele.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 902D11A0034; Sun, 19 Jan 2014 21:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2pOvGj5Jhxfy; Sun, 19 Jan 2014 21:44:40 -0800 (PST)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0080.outbound.protection.outlook.com [213.199.154.80]) by ietfa.amsl.com (Postfix) with ESMTP id 91DF11A0023; Sun, 19 Jan 2014 21:44:36 -0800 (PST)
Received: from AM3PR03MB532.eurprd03.prod.outlook.com (10.242.109.156) by AM3PR03MB531.eurprd03.prod.outlook.com (10.242.109.155) with Microsoft SMTP Server (TLS) id 15.0.851.11; Mon, 20 Jan 2014 05:44:34 +0000
Received: from AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) by AM3PR03MB532.eurprd03.prod.outlook.com ([10.242.109.156]) with mapi id 15.00.0851.011; Mon, 20 Jan 2014 05:44:34 +0000
From: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
To: "Black, David" <david.black@emc.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Topic: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp)
Thread-Index: Ac8Vj+sUxkixdvZlQDyGimrIKN8dNQAD35l5
Date: Mon, 20 Jan 2014 05:44:33 +0000
Message-ID: <3568aff546054a748d73d029c110c97b@AM3PR03MB532.eurprd03.prod.outlook.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F047824@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F047824@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [109.66.126.123]
x-forefront-prvs: 00979FCB3A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(13464003)(51704005)(252514010)(24454002)(189002)(199002)(164054003)(479174003)(377454003)(81686001)(31966008)(87936001)(74876001)(74706001)(90146001)(80022001)(4396001)(47446002)(15202345003)(76576001)(87266001)(83072002)(85852003)(81542001)(74316001)(86362001)(74366001)(93516002)(81342001)(74502001)(51856001)(56816005)(47976001)(69226001)(74662001)(15975445006)(65816001)(66066001)(85306002)(2656002)(19580395003)(83322001)(19580405001)(47736001)(80976001)(92566001)(53806001)(54356001)(79102001)(46102001)(50986001)(76786001)(49866001)(54316002)(76796001)(56776001)(33646001)(93136001)(59766001)(76482001)(63696002)(77982001)(81816001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR03MB531; H:AM3PR03MB532.eurprd03.prod.outlook.com; CLIP:109.66.126.123; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: ecitele.com
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:55:08 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Jan 2014 05:44:43 -0000

David,=0A=
Lots of thanks for a detailed response.=0A=
=0A=
My original question dealt with the MPLS-in-UDP draft, where the relevant t=
ext was quite brief:=0A=
=0A=
<quote>=0A=
            Source Port of UDP =0A=
=0A=
                This field contains a 16-bit entropy value that is =0A=
                generated by the ingress PE router. What algorithm is =0A=
                actually used by the ingress PE router to generate an =0A=
                entropy value is outside the scope of this doc. In the =0A=
                case where the flow does not need entropy, this field =0A=
                SHOULD be set to a randomly selected constant value to =0A=
                avoid packet reordering.    =0A=
<end quote>=0A=
=0A=
The answer given by Eric Rosen in http://www.ietf.org/mail-archive/web/mpls=
/current/msg11277.html (use the hash of the label stack of the packet to be=
 encapsulated ) resolves, IMO, this issue because the head-end of the UDP t=
unnel (the encapsulator) looks at the label stack of the packet to be encap=
sulated in any case. Of course other methods are not precluded, but there i=
s at least one method that is both reasonably simple and meaningful, especi=
ally because it is possible to add entropy to the label stack (RFC 6790).=
=0A=
=0A=
In the case of GRE-in-UDP the text goes into more detail, but, IMHO and FWI=
W, these details are not sufficient. AFAIK , the GRE encapsulators in most =
cases follows RFC 2784 and not RFC 1701. The reduced GRE header adopted RFC=
 2784 does not leave any place for meaningful "flow invariant fields" (unle=
ss you count the prtotocol type as such).  This means that the head-end of =
the UDP tunnel has to look beyond the IP and GRE headers of the packet to b=
e encapsulated for these fields - and this is something that, to the best o=
f my understanding, GRE tries to prevent.=0A=
=0A=
My 2c,=0A=
     Sasha=0A=
________________________________________=0A=
From: Black, David <david.black@emc.com>=0A=
Sent: Monday, January 20, 2014 5:30 AM=0A=
To: Alexander Vainshtein; stbryant@cisco.com=0A=
Cc: mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; Randy Bush; lisp@ietf.org=
; Black, David=0A=
Subject: GRE in UDP - traffic distribution ( was RE: [tsvwg] [mpls] OT (was=
 Re: draft-ietf-mpls-in-udp)=0A=
=0A=
Sasha,=0A=
=0A=
> But I would like to understand whether this protocol can really result in=
=0A=
> reasonable distribution of traffic. "Reasonable" means that (a) there is=
=0A=
> sufficient entropy and (b) that the order in specific micro-flows is=0A=
> preserved. The draft skips this issue (unless you consider a recommendati=
on to=0A=
> use a fixed  randomly selected source port value if the tunnel does not n=
eed=0A=
> ECMP a valid answer) .=0A=
=0A=
Well, there's a bit more in the draft than just a "randomly selected" value=
,=0A=
as the ability to use ECMP on these tunnels is rather important (text quote=
d=0A=
is from Section 3 in the draft):=0A=
=0A=
   The ingress device SHOULD set=0A=
   the UDP source port based on flow invariant fields from the payload=0A=
   header, otherwise it should be set to a randomly selected constant=0A=
   value, e.g. zero, to avoid packet flow reordering.  How a tunnel=0A=
   ingress generates entropy from the payload is outside the scope of=0A=
   this document.=0A=
=0A=
I suppose that more discussion and examples of "flow invariant fields"=0A=
would be useful, although an attempt at a comprehensive listing would be=0A=
pointless, IMHO.  An important situation is one where the tunnel ingress=0A=
"knows" (because the network operator actually does know) what the protocol=
=0A=
stack(s) is/are for the encapsulated traffic (e.g., HTTP/TCP/IP/GRE/IP) and=
=0A=
hence can find the flow-invariant fields that it wants to use for that=0A=
(those) specific stack(s).=0A=
=0A=
With good selection of flow-invariant fields wrt traffic mix, good=0A=
distribution is possible.=0A=
=0A=
Thanks,=0A=
--David=0A=
=0A=
> -----Original Message-----=0A=
> From: tsvwg [mailto:tsvwg-bounces@ietf.org] On Behalf Of Alexander Vainsh=
tein=0A=
> Sent: Wednesday, January 15, 2014 6:54 AM=0A=
> To: stbryant@cisco.com=0A=
> Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; ietf@ietf.org; tsvwg@ietf.org; R=
andy=0A=
> Bush; jnc@mit.edu; lisp@ietf.org=0A=
> Subject: Re: [tsvwg] [mpls] OT (was Re: draft-ietf-mpls-in-udp was RE: gr=
e-in-=0A=
> udp draft (was: RE: Milestones changed for tsvwg WG))=0A=
>=0A=
> Stewart, and all,=0A=
> I fully agree that UDP checksums is not a real-life issue with the protoc=
ol in=0A=
> question. They could probably help to check corrupted packets if corrupti=
on=0A=
> happens when a packet passes thru a router (i.e. when the ingress data li=
nk=0A=
> FCS has already been terminated and the egress data link FCS has not been=
=0A=
> generated yet). But this is hopefully rare - and since MPLS does not care=
=0A=
> about it, why should the MPLS encapsulator care?=0A=
>=0A=
> I also do not think that congestion control is a serious issue for this=
=0A=
> protocol, not in the least because the primary purpose of this protocol i=
s=0A=
> ECMP.=0A=
>=0A=
> But I would like to understand whether this protocol can really result in=
=0A=
> reasonable distribution of traffic. "Reasonable" means that (a) there is=
=0A=
> sufficient entropy and (b) that the order in specific micro-flows is=0A=
> preserved. The draft skips this issue (unless you consider a recommendati=
on to=0A=
> use a fixed  randomly selected source port value if the tunnel does not n=
eed=0A=
> ECMP a valid answer) .=0A=
>=0A=
> Any ideas as to how reasonable distribution of traffic  can be achieved w=
ith=0A=
> this protocol?=0A=
>=0A=
> Regards,=0A=
>        Sasha=0A=
> Email: Alexander.Vainshtein@ecitele.com=0A=
> Mobile: 054-9266302=0A=
>=0A=
> > -----Original Message-----=0A=
> > From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Stewart Bryant=
=0A=
> > Sent: Wednesday, January 15, 2014 1:31 PM=0A=
> > To: Randy Bush=0A=
> > Cc: gorry@erg.abdn.ac.uk; mpls@ietf.org; lisp@ietf.org; ietf@ietf.org;=
=0A=
> > wes@mti-systems.com; tsvwg@ietf.org; jnc@mit.edu=0A=
> > Subject: Re: [mpls] [tsvwg] OT (was Re: draft-ietf-mpls-in-udp was RE: =
gre-=0A=
> in-=0A=
> > udp draft (was: RE: Milestones changed for tsvwg WG))=0A=
> >=0A=
> > On 15/01/2014 11:08, Randy Bush wrote:=0A=
> > > [ you insist on cc:ing me, so you get to endure my opinions ]=0A=
> > >=0A=
> > >> it seems that there are no valid statistics for the current Internet=
=0A=
> > >> to sustain your case.=0A=
> > > as we discussed privately, there seem to be no real measurements to=
=0A=
> > > sustain any case.  this is all conjecturbation.=0A=
> > >=0A=
> > > what i do not understand is why, given the lack of solid evidence tha=
t=0A=
> > > we are in a safe space, you and others are not willing to spend a few=
=0A=
> > > euro cents to have a reasonable level of assurance at this layer.=0A=
> > >=0A=
> > > randy=0A=
> > Randy,=0A=
> >=0A=
> > It is not a few cents, it is likely the re-engineering of a lot of sili=
con.=0A=
> >=0A=
> > The reason that UDP is of interest is that the on path silicon knows ho=
w to=0A=
> > process it, for example it knows how to to ECMP it.=0A=
> >=0A=
> > The reason that the UDP c/s is a problem for a tunneler is that it need=
s to=0A=
> > have access to the whole pkt to calculate the c/s, but as you know the=
=0A=
> silicon=0A=
> > optimised that access away a long time ago.=0A=
> >=0A=
> > The alternative would be UDP-lite, but the ability of on path silicon t=
o=0A=
> process=0A=
> > that as competently and as completely as it processes UDP is by no mean=
s=0A=
> > clear.=0A=
> >=0A=
> > - Stewart=0A=
> >=0A=
> >=0A=
> > _______________________________________________=0A=
> > mpls mailing list=0A=
> > mpls@ietf.org=0A=
> > https://www.ietf.org/mailman/listinfo/mpls=0A=
=0A=

From jari.arkko@ericsson.com  Tue Jan 21 07:25:13 2014
Return-Path: <jari.arkko@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D15C1A0150 for <ietf@ietfa.amsl.com>; Tue, 21 Jan 2014 07:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BvjKvIws7Ub for <ietf@ietfa.amsl.com>; Tue, 21 Jan 2014 07:25:11 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id D3D731A0174 for <ietf@ietf.org>; Tue, 21 Jan 2014 07:25:10 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-63-52de9155eeea
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 03.33.23809.5519ED25; Tue, 21 Jan 2014 16:25:09 +0100 (CET)
Received: from ESESSMB307.ericsson.se ([169.254.7.171]) by ESESSHC017.ericsson.se ([153.88.183.69]) with mapi id 14.02.0387.000; Tue, 21 Jan 2014 16:25:09 +0100
From: Jari Arkko <jari.arkko@ericsson.com>
To: "<adrian@olddog.co.uk>" <adrian@olddog.co.uk>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Thread-Topic: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Thread-Index: AQHPFrz3GJfyCgvGzE2WLrs2tsmjEA==
Date: Tue, 21 Jan 2014 15:25:08 +0000
Message-ID: <8D0FB4E1-92B6-45F9-8213-3934F8FBF019@ericsson.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk>
In-Reply-To: <07d701cf1547$782166f0$686434d0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/signed; boundary="Apple-Mail=_DCA90775-2403-4EF0-879C-1B6EC215DDC6"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRmVeSWpSXmKPExsUyM+JvjW7oxHtBBq0dNhY/em4wW1zsvshq 8WzjfBYHZo8lS34yeazYvJLR48vlz2wBzFFcNimpOZllqUX6dglcGfvPP2csWG1W8fzxS8YG xh3GXYycHBICJhKtHZ9YIWwxiQv31rN1MXJxCAkcYpS423ydHcJZwijx5vplJpAqNgEtiY3L FwBVcXCICBhKHHgWAFLDLDCNUeLcxqUsIDXCAqUSGw/dZgexRQTKJCZfW8MGYetJtF7/zAxi swioSnxe1w9WwytgL7Hp4XWwuJBAgUTHpf9gNqeAtcTbto9g1zECXff91BqwG5gFxCVuPZnP BHG1iMTDi6fZIGxRiZeP/0F9oySx9vB2FojjpjBKzPzxkgVimaDEyZlPWCYwis5CMmsWsrpZ SOogirQlli18zTwL6GlmAR2JyQsZIcKmEq+PfoSyrSVm/DrIBmErSkzpfsi+gJFjFSN7bmJm Tnq50SZGYAwe3PJbdQfjnXMihxilOViUxHk/vHUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp 1cC4ZGVe7tXlCxgKn6e8d9hZMtEp7o2vfsYikzOJsa3pqTN9pZz5pHr2d686UpIVpf60RDXc x5770c8dCkHbbrxiu/DU/Hww8xIus41dRr+jbJY/NJctFru84/Oee/O0BBv6gl+FuQQVsW88 orYz1O+fwr8iXY9DRvYKVQ3xp15svnoua52k8HwlluKMREMt5qLiRACWfwxijwIAAA==
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:55:21 -0800
Cc: "<draft-housley-number-registries.all@tools.ietf.org>" <draft-housley-number-registries.all@tools.ietf.org>, "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 15:25:13 -0000

--Apple-Mail=_DCA90775-2403-4EF0-879C-1B6EC215DDC6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> Section 2.1 says...
>=20
>   Reservations of special-purpose AS Numbers are made through Internet
>   Standards actions.
>=20
> Section 2.2 says...
>=20
>   Reservation of special-purpose IPv4 addresses are made through
>   Internet Standards actions.
>=20
> Section 2.3 says...
>=20
>   Reservation of special-purpose IPv6 addresses are made through
>   Internet Standards actions.
>=20
> Section 3 says...
>=20
>   "IETF Review" as defined in [RFC5226] is required to reserve =
special-
>   purpose AS numbers, IPv4 addresses, or IPv6 addresses.
>=20
> 1. 2.1, 2.2, and 2.3 should have a reference to 5226
> 2. Section 3 contradicts 2.1, 2.2, and 2.3.
> 3. Why is Section 3 present since there are no instructions for IANA?

FWIW, I agree with these comments, and they deserve to be fixed. Thanks =
for your review.

Jari



--Apple-Mail=_DCA90775-2403-4EF0-879C-1B6EC215DDC6
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINaDCCBEUw
ggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVs
aWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4X
DTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv
1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqT
u3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMc
CYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUb
Az2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB
/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRh
cC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2
MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNV
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb
8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXI
v6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzY
FSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67
OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3k
MXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OY
CMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAw
OjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDgg
VjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVy
YSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5D
uVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe
1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF4
6H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjgh
XYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGj
ggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7ga
YqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0F
BgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7Bgcq
hXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20w
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vv
bi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkww
DgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUE
kUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDC
fkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6b
KuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHn
tP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPd
OI5GtDYPMIIEqjCCA5KgAwIBAgIQTyXs3vXto5joAjtwrbnc3jANBgkqhkiG9w0BAQUFADA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxMB4X
DTEzMDMwNDEzMjUyMVoXDTE2MDMwNDEzMjUxOVowYjERMA8GA1UECgwIRXJpY3Nzb24xEzARBgNV
BAMMCkphcmkgQXJra28xEDAOBgNVBAUTB2xtZmphYXIxJjAkBgkqhkiG9w0BCQEWF2phcmkuYXJr
a29AZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhwriyJIY5Bbz
yZrfnFAjWFLMNc6O6Z6dw5HqexTVyrUymDobuwcFtGl3n+yc6tYcvzM85LJMotJlOJH4NHEqClEc
iMw+gFvN17PXxM2aAPuv1ZUL1wSdQ9dS94zxQEQuh4Myyfy+eqvrEBkzZaDPu4Evz6xsmCYPYSZP
t4Bo6zbwQqkRvSQUO659ytmlyiPOiWN6wxEpwwO43LEw12xFrVSOQw3AG8ULW/xHbQvInuyWQdBC
ug/1n6IJETsMWSrLFnk888IjABXKkmq42EG6RQ0BWLw8lAQwTju7rsDF9HrcTYBcu9z2u/d4cSgH
P9SkRncRm68xrt7bD2RhPf3rkQIDAQABo4IBgzCCAX8wgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3
aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vRXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZx
bGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29tL2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFs
JTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2Uw
IgYDVR0RBBswGYEXamFyaS5hcmtrb0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEw
MTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0O
BBYEFLk/k+8oySkNxYm0GyPaFaKSRQufMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCb
MA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEAECF65IiGH7GS+EEHre+itv2wv0OQ
Z68DWR6G9IqMkBgb8dj6JcfFsu+9p8ID1e1L/0ybeTwz1t4IPhuOuWBPohj5irYiCBJkIokUr09B
rWPyxfBrSoZ+uXVWfmZSdp15pWlEnHhuGuJkZ2a0MKrj+OEM9qfQR5Cvdlmx5PvsIhFkAFcZWldI
xBwHsEeSoGJbVvvNImiY6M27u6rhuR8HanXVdcW4B8gK489LutxKhyhT9QDFUhmyWk2qYCUJgwM/
w44sLz8tv95jDbJxAR/aOwdwF3fQgj8VB5Xwvdn6B0PhfEcd3Ju4yUz6HE6ELZWG4ruE2haUCOn4
8WStKZ/RPDGCApMwggKPAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQTyXs3vXto5joAjtwrbnc3jAJBgUrDgMCGgUAoIIBGzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAxMjExNTI1MDhaMCMG
CSqGSIb3DQEJBDEWBBRBr+MgSFxvxf5CZcACYWR9tNMHUDBcBgkrBgEEAYI3EAQxTzBNMDkxETAP
BgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l
7N717aOY6AI7cK253N4wXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l7N717aOY6AI7cK253N4wDQYJ
KoZIhvcNAQEBBQAEggEAUny3y2gapdMiQHJSx0BRk4jj/chtDFEW0NlF/WjWesiG7fO4CFnVLQRt
EbHAn/PCPml9mI8AJuOU2DoDD8HXD05xCAPFQy97Hwfx1BW8PfbTtkGtex4FDXlF7LLZ+7YluN4d
XMeRjTYqgvywGYqY51LFMbfavc+Rzsfjs0xPOv6uQne2Fo9inwQkC4FpMZPPkAB1di4lkaDO/cR2
5eK/9DjI2njFIcxgpob0DZ4iIROaLiKqx7o8zoGLxn+Kx0PyUrTXLk728+tLT9ST6U+uWiKoOP0L
Tpa399z2kdWwmNSr6+u7tXImeksSJTSs9csftTgDx0ZUxdHmSDaFsY8IPQAAAAAAAA==

--Apple-Mail=_DCA90775-2403-4EF0-879C-1B6EC215DDC6--

From curtis@ipv6.occnc.com  Fri Jan 17 09:20:12 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53E701AE155; Fri, 17 Jan 2014 09:20:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.94
X-Spam-Level: 
X-Spam-Status: No, score=-1.94 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OOEX1DlxWCOm; Fri, 17 Jan 2014 09:20:10 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 148EA1AE0DB; Fri, 17 Jan 2014 09:20:09 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0HHJqHY062965; Fri, 17 Jan 2014 12:19:52 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
To: "Eggert, Lars" <lars@netapp.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Thu, 16 Jan 2014 17:19:50 +0000." <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
Date: Fri, 17 Jan 2014 12:19:52 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 17 Jan 2014 17:20:12 -0000

Lars,

We seem to be in an endless loop here.

You have made your assertions about your desire to uphold the purity
of any new UDP applications and adhere to the BCP you wrote.

You appear to be very nearly alone in this argument and certainly no
one that works with MPLS is siding with you.

In the end we can put anything we want in the RFC *but* IETF has never
truly had the final word on what vendors and operators do in provider
networks.

In this case, regardless of what changes are made to the draft,
implementations will offer at least the option for non-RFC behavior by
using zero checksums and not using any congestion control.  And
providers will make use of it, perhaps exclusively.

The document might as well reflect reality, despite reality not
conforming to your notions of architectural purity.

The best course of action is to put a SHOULD in regarding checksums
and put a SHOULD in regarding congestion avoidance.  Even the BCP does
not go any further than to say a tunneling protocol SHOULD use
congestion control and there were reasons that the word MUST was not
acceptable in the BCP.

If we are still arguing over two instances of SHOULD vs MUST we have
wasted a lot of bandwidth on those two words.

IMHO The only remaining question is whether the document can go forward
with the definition of congestion control for MPLS over UDP left out
of scope and for another document if a need arises.

If this is not acceptable to you (I doubt it is) please indicate what
you would like to see in the document and since this is IETF last call
where consensus matters and no one individual has veto power, we'll
have to see if there is consensus behind your proposed changes.

Curtis


In message <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com>
"Eggert, Lars" writes:
 
> Hi,
>  
> On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> > These tunnels are stateless
>  
> yep. (But they don't have to be.)
>  
> >  The endpoints not the encapsulators have visibility into the
> > end-to-end loss latency properties of the path.
>  
> Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 =
> domains - where not reacting to congestion may be OK - can now go over =
> the wider Internet, where this is not OK.
>  
> I'd be great if those apps would change. But in the meantime, it's the =
> duty of the encapsulator - who enables this traffic to break out of an =
> L2 domain and go over the wider net - to make sure the traffic it emits =
> conforms to our BCPs.
>  
> >  the encapsulator is an intermediate hop, similar to any other router
> > in the path.
>  
> It's not. For the rest of the network, that encapsulator is =
> indistinguishable from any other app that sends UDP traffic.
>  
> UDP is a transport-layer protocol, and we have practices how it is to be =
> used on the net. If you want to use it for encapsulation, you bind =
> yourself to these BCPs.
>  
> Look at it the other way: if transport area folks would want to send =
> MPLS packets into the network in some problematic way, I'm sure the =
> routing and ops folks would not be amused.
>  
> Lars

From curtis@ipv6.occnc.com  Fri Jan 17 10:02:56 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E209D1AC421; Fri, 17 Jan 2014 10:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id etx0bFqg6eoS; Fri, 17 Jan 2014 10:02:54 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id A0C331A16F0; Fri, 17 Jan 2014 10:02:54 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0HI2cI6063577; Fri, 17 Jan 2014 13:02:38 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401171802.s0HI2cI6063577@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Fri, 17 Jan 2014 01:19:41 +0000." <290E20B455C66743BE178C5C84F1240847E63346CE@EXMB01CMS.surrey.ac.uk>
Date: Fri, 17 Jan 2014 13:02:37 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: ietf@ietf.org, mpls@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 17 Jan 2014 18:02:57 -0000

Lloyd,

If we really want to get silly we can claim that a UDP control block
or socket state on a UDP listen is state and therefore UDP is not a
stateless protocol.

But we don't want to get silly.  Do we?  Or are we long past that
point?

Curtis

PS - type "man setsocopt" on a BSD system to see a list of state, most
of which applies to any socket including UDP sockets.


In message <290E20B455C66743BE178C5C84F1240847E63346CE@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> Surely you mean minimised state?
>  
> The tunnels have to know where the other tunnel endpoint is -
> state. This is distinct from having a congestion-aware state machine
> that e.g. TCP includes...
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: mpls [mpls-bounces@ietf.org] On Behalf Of Ross Callon [rcallon@juniper.net]
> Sent: 16 January 2014 22:32
> To: Eggert, Lars
> Cc: EXT - joelja@bogus.com; mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> >> These tunnels are stateless
> >
> > yep. (But they don't have to be.)
>  
> The tunnels strictly speaking do not have to be stateless. However, if you want routers to actually implement them, and you want to scale in both forwarding speed and number of tunnels, then yes they do have to be stateless.
>  
> Ross
> (speaking only as an individual contributor)
>  
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Eggert, Lars
> Sent: Thursday, January 16, 2014 12:20 PM
> To: EXT - joelja@bogus.com
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> Hi,
>  
> On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> > These tunnels are stateless
>  
> yep. (But they don't have to be.)
>  
> >  The endpoints not the encapsulators have visibility into the
> > end-to-end loss latency properties of the path.
>  
> Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domains - where not reacting to congestion may be OK - can now go over the wider Internet, where this is not OK.
>  
> I'd be great if those apps would change. But in the meantime, it's the duty of the encapsulator - who enables this traffic to break out of an L2 domain and go over the wider net - to make sure the traffic it emits conforms to our BCPs.
>  
> >  the encapsulator is an intermediate hop, similar to any other router
> > in the path.
>  
> It's not. For the rest of the network, that encapsulator is indistinguishable from any other app that sends UDP traffic.
>  
> UDP is a transport-layer protocol, and we have practices how it is to be used on the net. If you want to use it for encapsulation, you bind yourself to these BCPs.
>  
> Look at it the other way: if transport area folks would want to send MPLS packets into the network in some problematic way, I'm sure the routing and ops folks would not be amused.
>  
> Lars

From curtis@ipv6.occnc.com  Fri Jan 17 10:06:08 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CC1B1AC421; Fri, 17 Jan 2014 10:06:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bf9pvr_JNmjs; Fri, 17 Jan 2014 10:06:06 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 576021A16F0; Fri, 17 Jan 2014 10:06:06 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0HI5kUC063603; Fri, 17 Jan 2014 13:05:46 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401171805.s0HI5kUC063603@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Fri, 17 Jan 2014 03:03:05 +0000." <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.uk>
Date: Fri, 17 Jan 2014 13:05:46 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: mpls@ietf.org, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 17 Jan 2014 18:06:08 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> There's an opportunity to define a simple generic IPv6 encapsulating
> mechanism a la UDP, but with a payload checksum of varying coverage
> (header only, partial payload, full payload) and with the (stronger
> than UDP) checksum placed at the end of the packet.
>  
> Lloyd Wood
> http://about.me/lloydwood


Go for it!

When a critical mass of routers hash on this new protocol number and
port space we'll let you know and the MPLS WG can obsolete MPLS over
UDP and replace it with MPLS over this new protocol.

Thanks for offering to write this.

Curtis


> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@cisco.com]
> Sent: 16 January 2014 17:35
> To: Eggert, Lars; Joel Jaeggli
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> On 16/01/2014 17:19, Eggert, Lars wrote:
> > Hi,
> >
> > On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> >> These tunnels are stateless
> > yep. (But they don't have to be.)
> Ah, they do if they are to scale. State at speed is really hard. The sort
> of systems we are talking about do things like pipeline counters
> and it is loooooots of packets later before the counter is actually
> incremented.
> >>   The endpoints not the encapsulators have visibility into the
> >> end-to-end loss latency properties of the path.
> > Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domains - where not reacting to congestion may be OK - can now go over the wider Internet, where this is not OK.
> >
> > I'd be great if those apps would change. But in the meantime, it's the duty of the encapsulator - who enables this traffic to break out of an L2 domain and go over the wider net - to make sure the traffic it emits conforms to our BCPs.
> >
> >>   the encapsulator is an intermediate hop, similar to any other router
> >> in the path.
> > It's not. For the rest of the network, that encapsulator is indistinguishable from any other app that sends UDP traffic.
> >
> > UDP is a transport-layer protocol, and we have practices how it is to be used on the net. If you want to use it for encapsulation, you bind yourself to these BCPs.
> >
> > Look at it the other way: if transport area folks would want to send MPLS packets into the network in some problematic way, I'm sure the routing and ops folks would not be amused.
> The root cause of the problem here is that UDP, has bifurcated into
> a general purpose encapsulation.
>  
> Stewart
>  
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls

From curtis@ipv6.occnc.com  Fri Jan 17 10:16:28 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF7A1A1F64; Fri, 17 Jan 2014 10:16:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59XwkD_sYlYW; Fri, 17 Jan 2014 10:16:26 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 8D37F1A1F4A; Fri, 17 Jan 2014 10:16:26 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0HIGBJa063724; Fri, 17 Jan 2014 13:16:12 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401171816.s0HIGBJa063724@maildrop2.v6ds.occnc.com>
To: joel jaeggli <joelja@bogus.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Thu, 16 Jan 2014 23:38:12 -0800." <52D8DDE4.4020508@bogus.com>
Date: Fri, 17 Jan 2014 13:16:11 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 17 Jan 2014 18:16:28 -0000

In message <52D8DDE4.4020508@bogus.com>
joel jaeggli writes:
 
> On 1/16/14, 9:19 AM, Eggert, Lars wrote:
> > Hi,
> > 
> > On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> >> These tunnels are stateless
> > 
> > yep. (But they don't have to be.)
>  
> They do in-fact have to be stateless with respect to the contents. They
> will no doubt be created in a same distributed forwarding  engines that
> currently do IP-MPLS encapsulation and L2-MPLS encapsulation. likewise
> their decapsulation will occur in such devices.
>  
> > Look at it the other way: if transport area folks would want to send
> > MPLS packets into the network in some problematic way, I'm sure the
> > routing and ops folks would not be amused.

They would never notice since MPLS packets are only passed around
internally and in some cases among peer providers.  If you did try to
do that and succeeded in getting even one packet through there are
some security holes to worry about.  Point is that you can't get MPLS
packets into provider networks unless something is very seriously
wrong and the already persistant attackers would have a picnic.

> Today congestion occurs on MPLS networks. intermediate hops that are
> congested have no choice but to drop packets.

And nothing bad happens because providers that allow any congestion to
occur by provisioning so that it can happen (usually occasionally or
very rarely) carry two kinds of traffic in that network.  One is IP in
MPLS or IP native.  The other is high margin VPN services and emulated
legacy L2 services that are given a different TC value.  What the
providers want to happen on light congestion happens.  Slight drop
gets IP (mostly TCP still to this date) to reduce load.  The high
paying VPN and emulated legacy L2 services are completely unaffected
(as the provider wants given they are paying a lot for that).

So I'm agreeing with you (Joel).

> > Lars

Curtis

From curtis@ipv6.occnc.com  Fri Jan 17 12:28:35 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 771411AC3FA; Fri, 17 Jan 2014 12:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEyVjjnDGtlV; Fri, 17 Jan 2014 12:28:33 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7021A802D; Fri, 17 Jan 2014 12:28:32 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0HKSJP6065706; Fri, 17 Jan 2014 15:28:19 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401172028.s0HKSJP6065706@maildrop2.v6ds.occnc.com>
To: Saku Ytti <saku@ytti.fi>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] [tsvwg] [lisp] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG)
In-reply-to: Your message of "Fri, 17 Jan 2014 18:33:07 +0200." <20140117163307.GA4577@pob.ytti.fi>
Date: Fri, 17 Jan 2014 15:28:19 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: mpls@ietf.org, lisp@ietf.org, tsvwg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 17 Jan 2014 20:28:35 -0000

In message <20140117163307.GA4577@pob.ytti.fi>
Saku Ytti writes:
 
> On (2014-01-13 14:11 -0500), Curtis Villamizar wrote:
>  
> > One of the reasons that IPv6 (rfc2460) dropped the header checksum
> > that was in IPv4 is that with link layers all doing FCS it served no
> > purpose.  For the same reason TCP and UDP checksums server no purpose.
>  
> One datapoint from today. Peering router has 4xLACP to core and in one of
> these LACP members it is sometimes mangling packets during send and FCS is
> being calculated for this mangled data.
> All egress PE boxes start logging errors (maybe 1 error per 30min), because
> they check IP checksum, which is now incorrect.
>  
> Router is latest generation service provider router from major vendor running
> recent software and affected router is logging no errors.  Can't imagine
> when, if ever, would this issue have been found without IP checksums.
>  
> -- 
>   ++ytti
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


This sounds like a router acting as a host for the given packet.  The
forwarding data paths in routers are usually protected.  If the router
was forwarding and mangled packets, that speak well for the router
vendor since the major vendors claim to protect their data paths from
this sort of thing.  Less so for the path from the route processor.

If this was originated at the router it would also be caught if AH was
enabled.  Were these unauthenticated control plane packets?

You've made a good anecdotal case for keeping TCP and UDP checksums.

Curtis

From curtis@ipv6.occnc.com  Mon Jan 20 14:48:09 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 876FD1A0272 for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 14:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4N23puI14DUa for <ietf@ietfa.amsl.com>; Mon, 20 Jan 2014 14:48:08 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id BAD9B1A026F for <ietf@ietf.org>; Mon, 20 Jan 2014 14:48:07 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0KMllSl047284; Mon, 20 Jan 2014 17:47:47 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401202247.s0KMllSl047284@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Fri, 17 Jan 2014 23:00:33 +0000." <290E20B455C66743BE178C5C84F1240847E63346D1@EXMB01CMS.surrey.ac.uk>
Date: Mon, 20 Jan 2014 17:47:47 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: mpls@ietf.org, ietf@ietf.org, curtis@ipv6.occnc.com, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 20 Jan 2014 22:48:09 -0000

We are continuing to stray off topic, but...

Router vendors focus on real needs identified by customers.  If this
were to become something customers were bugging them about, then
they'll do it.  OTOH, most hardware in the field today can only track
one 32 bit FCS, given that only one L2 header would need this.  The
ability to run on existing hardware is important.

Perhaps you missed this:

> When a critical mass of routers hash on this new protocol number and
> port space we'll let you know and the MPLS WG can obsolete MPLS over
> UDP and replace it with MPLS over this new protocol.

Providers and router vendors are also aware that most routers look
only for protocol numbers 6 and 17 for load balancing on port
numbers.  So if the motivation of MPLS over UDP is an interim solution
to get ECMP, then not using UDP is not an option.

Curtis


In message <290E20B455C66743BE178C5C84F1240847E63346D1@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
> 
> Yes, it would be unreasonable for the router vendors themselves to design
> something with a trailing checksum and pseudo-header check that would meet
> their forwarding needs while ensuring reliability.
>  
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Curtis Villamizar [curtis@ipv6.occnc.com]
> Sent: 17 January 2014 18:05
> To: Wood L  Dr (Electronic Eng)
> Cc: stbryant@cisco.com; lars@netapp.com; joelja@bogus.com; mpls@ietf.org; ietf@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> In message <290E20B455C66743BE178C5C84F1240847E63346CF@EXMB01CMS.surrey.ac.uk>
> l.wood@surrey.ac.uk writes:
>  
> > There's an opportunity to define a simple generic IPv6 encapsulating
> > mechanism a la UDP, but with a payload checksum of varying coverage
> > (header only, partial payload, full payload) and with the (stronger
> > than UDP) checksum placed at the end of the packet.
> >
> > Lloyd Wood
> > http://about.me/lloydwood
>  
>  
> Go for it!
>  
> When a critical mass of routers hash on this new protocol number and
> port space we'll let you know and the MPLS WG can obsolete MPLS over
> UDP and replace it with MPLS over this new protocol.
>  
> Thanks for offering to write this.
>  
> Curtis
>  
>  
> > ________________________________________
> > From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@cisco.com]
> > Sent: 16 January 2014 17:35
> > To: Eggert, Lars; Joel Jaeggli
> > Cc: mpls@ietf.org; IETF discussion list
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
> >
> > On 16/01/2014 17:19, Eggert, Lars wrote:
> > > Hi,
> > >
> > > On 2014-1-16, at 18:06, joel jaeggli <joelja@bogus.com> wrote:
> > >> These tunnels are stateless
> > > yep. (But they don't have to be.)
> > Ah, they do if they are to scale. State at speed is really hard. The sort
> > of systems we are talking about do things like pipeline counters
> > and it is loooooots of packets later before the counter is actually
> > incremented.
> > >>   The endpoints not the encapsulators have visibility into the
> > >> end-to-end loss latency properties of the path.
> > > Yep. But when you tunnel some L2 in UDP, apps that were limited to L2 domains - where not reacting to congestion may be OK - can now go over the wider Internet, where this is not OK.
> > >
> > > I'd be great if those apps would change. But in the meantime, it's the duty of the encapsulator - who enables this traffic to break out of an L2 domain and go over the wider net - to make sure the traffic it emits conforms to our BCPs.
> > >
> > >>   the encapsulator is an intermediate hop, similar to any other router
> > >> in the path.
> > > It's not. For the rest of the network, that encapsulator is indistinguishable from any other app that sends UDP traffic.
> > >
> > > UDP is a transport-layer protocol, and we have practices how it is to be used on the net. If you want to use it for encapsulation, you bind yourself to these BCPs.
> > >
> > > Look at it the other way: if transport area folks would want to send MPLS packets into the network in some problematic way, I'm sure the routing and ops folks would not be amused.
> > The root cause of the problem here is that UDP, has bifurcated into
> > a general purpose encapsulation.
> >
> > Stewart

From curtis@ipv6.occnc.com  Mon Jan 20 21:17:35 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A199D1A0036; Mon, 20 Jan 2014 21:17:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.137
X-Spam-Level: 
X-Spam-Status: No, score=-0.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_LIST=2.3, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qj_ujqFTuoYX; Mon, 20 Jan 2014 21:17:33 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id CE4C11A002F; Mon, 20 Jan 2014 21:17:32 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0L5HKkg051900; Tue, 21 Jan 2014 00:17:20 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401210517.s0L5HKkg051900@maildrop2.v6ds.occnc.com>
To: "Peter Yee" <peter@akayla.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: Gen-ART LC review of draft-ietf-mpls-multipath-use-03
In-reply-to: Your message of "Fri, 17 Jan 2014 23:21:28 -0800." <02d101cf141d$ea1a8f50$be4fadf0$@akayla.com>
Date: Tue, 21 Jan 2014 00:17:20 -0500
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:56:09 -0800
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 21 Jan 2014 05:17:35 -0000

In message <02d101cf141d$ea1a8f50$be4fadf0$@akayla.com>
"Peter Yee" writes:
> 
> 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-mpls-multipath-use-03
> Reviewer: Peter Yee
> Review Date: January-16-2014
> IETF LC End Date: January-17-2014
> IESG Telechat date: January-23-2014
>  
> Summary: This draft is basically ready for publication as an Informational
> RFC, but has nits that should be fixed before publication. [Ready with
> nits.]
>  
> This document discusses multipath MPLS operations and describes the means of
> supporting MPLS as a server layer for MPLS-TP and vice versa.  It lists
> requirements and implications for these operations.
>  
>  
> Nits:
>  
> General nits:
>  
> Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
> consistency with RFC 2991.

ECMP is expanded on first use in compliance with RFC Editor quidelines
for abbreviations.  ECMP is also expanded on first use within each
section where it is used with the exception of one place where ECMP is
contained in a verbatim excerpt in a quote from RFC6374.

> In the usage RFCxxxx, use a space between RFC and xxxx except when used as a
> reference, e.g., [RFCxxxx].

Nine instances were found and fixed, including two instancees of
"pre-RFC6790" changed to "pre- RFC 6790".  I don't think that one
looks right as "pre-RFC 6790".

> There are many unexplained acronyms without definition or reference.  Unless
> these are abundantly clear to most readers, expand them on first usage and
> provide a reference pointer where feasible.

The following acronyms were found and checked for expansion on first
use:

  Listed in RFC Editor guidelines on acronyms as well known:

    BGP GMPLS IANA IEEE IP IS-IS ITU-T MPLS OSPF

  Used only in verbatim quoted text (expanded in one use)

    E-LSP L-LSP

  Already expanded on first use

    ECMP EL ELI FA GAL ILM LACP LAG LFA LM LSP LSR PHB PSC RSVP-TE

  Changed to be expanded on first use

    IPFRR MPLS-TP OAM TC

Many of the acronyms are explained in the referenced documents.  The
intended audience should be familiar with this set of acronyms.

Almost all of these acronyms are in the RFC Editor list with only a
few exceptions.  The RFC Editor may want to add the following:

  Traffic CLass (TC) and cite RFC 5462 (Multiprotocol Label Switching
  (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class"
  Field),

  Loss Measurement (LM) and and Delay Measurement (DM) and cite RFC
  6374 (Packet Loss and Delay Measurement for MPLS Networks).  The
  abbreviations LM and DM are also used in other OAM documents from
  other SDO (with the same expansion).

  Entropy Label Indicator (ELI) and Entropy Label (EL) and cite RFC
  6790 (The Use of Entropy Labels in MPLS Forwarding).

This document cites the above three RFCs and expands each of these
acronyms on first use (except DM which is not used).

> Specific nits:
>  
> Page 1, Abstract, 2nd paragraph, 1st sentence: change "MPLS Entropy label"
> to "the MPLS Entropy Label".

In this instance the phrase "MPLS Entropy Labels" is the name of the
technique and the short name of RFC 6790 (plural in the RFC 6790 short
name).  The abstract cannot contain citations but I can put "RFC 6790"
in parens.

I suggest s/Using MPLS Entropy label/Using MPLS Entropy Labels (RFC 6790)/
and if there are no objections will make that change.

> Page 2, Section 1, 1st paragraph,  1st sentence: delete the comma after
> "traffic".

OK.

> Page 2, Section 1, 1st paragraph, last sentence: change "load split" to
> "load splitting".

OK.

> Page 2, Section 1, 2nd paragraph, last sentence: hyphenate "fate sharing".

OK

> Page 3, Section 1, 1st paragraph, 1st sentence: hyphenate "equal cost".

I do not think equal cost needs to be hyphenated.  In the technique
Equal-Cost Multipath (ECMP) the choice to hyphenate was made for
historic reasons, but for example in the RFC Editor list of acroyms
"Unequal Loss Protection (ULP)" does not hyphenate "unequal loss".

No ambiguity is created in the instances where hyphenation is not used
and equal cost is consistently not hyphenated in this document.

> Page 3, definition of "Loop Free Alternate Paths (LFA)": hyphenate "Loop
> Free".

OK.

> Page 3, definition of "Loop Free Alternate Paths (LFA), 1st sentence: change
> the terminating period to a colon.

OK.

> Page 4, Section 3.1, 1st paragraph, 1st sentence: change "date" to "data".

OK.

> Page 4, Section 3.1, 1st paragraph, 2nd sentence: change the terminating
> period to a colon.

OK.

> Page 5, 1st full paragraph, 1st sentence: insert "Section 3.1.1" between
> "[RFC5960]" and "paragraph 3".  Capitalize "paragraph".

OK.

> Page 5, 1st full paragraph, 3rd sentence: same as previous instructions.

OK.

> Page 5, 2nd paragraph, 2nd sentence: change ' "Section 1 Introduction"' to '
> Section 1 ("Introduction")'.

OK.

> Page 6, 1st paragraph, 3rd sentence: change ' "Section 2.9.4 Equal Cost
> Multipath") to ' Section 2.9.4 ("Equal Cost Multipath")'.

OK.

> Page 6, Section 3.2, 1st paragraph, 1st sentence: hyphenate "MPLS-TP
> conformant" and delete the comma after "multipath".

In existing RFCs, including some that are quite recent, a spec acronym
followed by the word conformant is both hyphenated and not hyphenated.

I prefer not to hyphenate because the acronym itself is already
hyphentated and no ambiguity is created either way.

> Page 7, 2nd paragraph, 2nd sentence: change "A" to "An".

OK.  In future reviews please include the noun that follows.

> Page 7, 2nd paragraph, 5th and 6th sentences: change all occurrences of
> "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 7, 3rd paragraph, 2nd sentence: change "LSP" to "LSPs".

OK.

> Page 7, 4th paragraph, 2nd sentence: change "LSR" to "LSRs".

OK.

> Page 7, 5th paragraph: change all occurrences of "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 7, 5th paragraph last sentence: change "co-existance" to "coexistence".

OK.

> Page 8, 1st partial paragraph, 2nd full sentence: change all occurrences of
> "LSP" to "LPSs" and change "LSR" to "LSRs".

I added the "s" where "LSP" or "LSR" should have been plural in that
paragraph.

> Page 8, 2nd full paragraph: change all occurrences of "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 8, 4th paragraph, 1st sentence: change "LSP" to "LSPs".

I added the "s" where "LSP" should have been plural in that paragraph.

> Page 8, 4th paragraph, 2nd sentence: is there a quantitative definition for
> "very infrequent" that can be substituted or explained?

Any time load balancing occurs there is a chance of reordering and TCP
generally backs off (sans SACK support) when such an event occurs as
it would back off if a single packet was dropped.  The frequency of
load balancing has to be kept low to avoid this, but how low is the
topic of debate and will certainly vary among services with different
expectations (for example financial transactions vs plain old
Internet).

For the purpose of the discussion here the phrase "except during very
infrequent transitions due to load balancing" acknowledges that load
balance causes some imperfection, but does not try to quantify it.

> Page 8, 4th paragraph, 3rd sentence: change "presense" to "presence".
> Insert "a" before "GAL".

OK.

> Page 9, 1st partial paragraph: delete "label" following "EL" in two
> locations.

OK.

> Page 9, Section 4, 1st paragraph, 1st sentence: change first "LSP" to
> "LSPs".  Change "a MPLS-TP" to "an MPLS-TP" unless MPLS is pronounced liked
> "mipples" or something similar and not just spelled out.

OK.

> Page 9, Section 4, 2nd paragraph: replace all occurrences of "LSP" with
> "LSPs".

OK.

> Page 9, Section 4, 2nd paragraph, 2nd sentence: insert "the" between "in"
> and "number".

OK.

> Page 9, Section 4, 2nd paragraph, 3rd sentence: change "ILM" to "ILMs".

OK.

> Page 9, Section 4, 3rd paragraph, 1st sentence: change "Server Layer" to
> "server layer" for consistency of usage.  Insert "of" between "use" and
> "MPLS-TP".  Change "LSP" to "LSPs".

OK.

> Page 9, Section 4, 3rd paragraph, 4th sentence: change "LSP" to "LSPs".

OK.

> Page 9, Section 4, 3rd paragraph, 5th sentence: change "LSP" to "LSPs".
> Change "capacity" to "capacities".  Insert "generally" before "not integer"
> unless it is always the case that the capacity is not a multiple of 10 Gb/s.

OK.

> Page 9, Section 4, 4th paragraph, 1st sentence: change "Server Layer" to
> "server layer".

OK.

> Page 10, Section 6, 2nd paragraph, 2nd sentence: hyphenate "high end" and
> append a comma after that.  Hyphenate "packet processing".

OK.

> Page 10, Section 6, 3rd paragraph, last sentence: same as previous
> instructions.

OK.

> Page 10, Section 8, 1st sentence: insert "a" between "of" and "framework".

OK.

> I'm not particularly knowledgeable about MPLS, so I'm unable to express much
> about the correctness of the operational points made in the document.
>  
> 		-Peter Yee

OK.  But you certainly did read this thoroughly and pick out a lot of
nits.  Thanks for doing so.

Curtis

From saku@ytti.fi  Fri Jan 17 08:33:29 2014
Return-Path: <saku@ytti.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B8C1AE12E for <ietf@ietfa.amsl.com>; Fri, 17 Jan 2014 08:33:29 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toWV8ZddOY9R for <ietf@ietfa.amsl.com>; Fri, 17 Jan 2014 08:33:28 -0800 (PST)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1A61AE14E for <ietf@ietf.org>; Fri, 17 Jan 2014 08:33:25 -0800 (PST)
Received: by mail-bk0-f44.google.com with SMTP id ej10so1717289bkb.17 for <ietf@ietf.org>; Fri, 17 Jan 2014 08:33:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=fOExXz/vu7Y2EmPTN7KeV7eiMgKQomSy+C+1ovhn/KA=; b=ef4ePdaie/nt3LMD01OAnBeQ0aAJDzH02TDwdY8nfMoZxvbcYXs2HQ4jA0FOrDeRKS s2YdBJRU7dm4O2Rgm70mLiEO4BWaLpzGNsJ+uZEDmhBtFjQ2wNqB2u1Gdli4EU4fjrgr yVbOT+HU5tNGvsVmcMsHWFDtsVnIieqKBlml/UA4rlavObVKDJyujLgl9LKewhYvuWmx C1euNoKfgEzagpZpdbXXjSI8aVlEmSESQJfe/fHryVxweBtZwaCb43cShgNS7y3pEOTg Ild8wGQAfiTTXC2JhVP20Ij9L0ae3cwLkeOU4ydjYvqOhW1eT2rsFVunXI6+zk4gbzl3 CA0w==
X-Gm-Message-State: ALoCoQlkvh0em8urjjTQPutnhkWFKCTW1x2QG6HU/w9quv2H6oWgsSIwAVNZDZSY/D51yNJqnZ49
X-Received: by 10.205.67.199 with SMTP id xv7mr15190bkb.149.1389976391762; Fri, 17 Jan 2014 08:33:11 -0800 (PST)
Received: from pob.ytti.fi (up.ip.fi. [2001:6e8:288::d]) by mx.google.com with ESMTPSA id d5sm10022809bkc.9.2014.01.17.08.33.09 for <multiple recipients> (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 17 Jan 2014 08:33:10 -0800 (PST)
Date: Fri, 17 Jan 2014 18:33:07 +0200
From: Saku Ytti <saku@ytti.fi>
To: tsvwg@ietf.org, mpls@ietf.org, ietf@ietf.org, lisp@ietf.org
Subject: Re: [tsvwg] [mpls] [lisp] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG)
Message-ID: <20140117163307.GA4577@pob.ytti.fi>
References: <290E20B455C66743BE178C5C84F1240847E63346BF@EXMB01CMS.surrey.ac.uk> <201401131911.s0DJBC1o079251@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201401131911.s0DJBC1o079251@maildrop2.v6ds.occnc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 21 Jan 2014 07:58:47 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 16:33:29 -0000

On (2014-01-13 14:11 -0500), Curtis Villamizar wrote:

> One of the reasons that IPv6 (rfc2460) dropped the header checksum
> that was in IPv4 is that with link layers all doing FCS it served no
> purpose.  For the same reason TCP and UDP checksums server no purpose.

One datapoint from today. Peering router has 4xLACP to core and in one of
these LACP members it is sometimes mangling packets during send and FCS is
being calculated for this mangled data.
All egress PE boxes start logging errors (maybe 1 error per 30min), because
they check IP checksum, which is now incorrect.

Router is latest generation service provider router from major vendor running
recent software and affected router is logging no errors.  Can't imagine when,
if ever, would this issue have been found without IP checksums.

-- 
  ++ytti

From saku@ytti.fi  Fri Jan 17 14:33:04 2014
Return-Path: <saku@ytti.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BB151ACAD7 for <ietf@ietfa.amsl.com>; Fri, 17 Jan 2014 14:33: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=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uRHtqaG1KPBL for <ietf@ietfa.amsl.com>; Fri, 17 Jan 2014 14:33:03 -0800 (PST)
Received: from mail-bk0-f45.google.com (mail-bk0-f45.google.com [209.85.214.45]) by ietfa.amsl.com (Postfix) with ESMTP id B8C061ACCEB for <ietf@ietf.org>; Fri, 17 Jan 2014 14:33:00 -0800 (PST)
Received: by mail-bk0-f45.google.com with SMTP id v16so1847713bkz.18 for <ietf@ietf.org>; Fri, 17 Jan 2014 14:32:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=ghRO5DRJKlNVgt4RvXMoNoXDkyNXVZev0O5yIWKwBnU=; b=RqSU66amcfNqckh0MNZ9DMO8iAxdaXcqMKlkLuFZ6XXHOUiE0hgsd9uUOGY+yECD2h u+wlYZym85wzag6ovCQsdOoCjgkVCc//ZMWaQr8kW3IZzUaUdtK/J/RbzqW3ppUNLF1e i2dqbJzFYSAq5CeLmHqxUy9PxD45KC+jvrrIZnt6H9jwkCeAlO4AR7p/SrV8exuQEESc 5qroqwZmHOsMLtfh1VPVBKwKRuIcF3oCWta6e17UbP7QM9k4vmEm4Ubtsakv39rHCJ25 gbwYHKKpMe6E0Ix9XEyDGIfFaOozr0KTnkN48mOwS0N61cxOHrBKZrj6/R9fVSd2Gfer Vsyw==
X-Gm-Message-State: ALoCoQn6vGsXe3t+u8gSvCC0pSovNRat4o0dqJIR1/lm+UTOKDUwpkavGPUGhJFnAb9hUtrWyLmM
X-Received: by 10.205.10.66 with SMTP id oz2mr21880bkb.142.1389997966847; Fri, 17 Jan 2014 14:32:46 -0800 (PST)
Received: from pob.ytti.fi (up.ip.fi. [2001:6e8:288::d]) by mx.google.com with ESMTPSA id d5sm10751384bkc.9.2014.01.17.14.32.45 for <multiple recipients> (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Fri, 17 Jan 2014 14:32:45 -0800 (PST)
Date: Sat, 18 Jan 2014 00:32:43 +0200
From: Saku Ytti <saku@ytti.fi>
To: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] [tsvwg] [lisp] draft-ietf-mpls-in-udp was RE: gre-in-udp draft (was: RE: Milestones changed for tsvwg WG)
Message-ID: <20140117223243.GA21841@pob.ytti.fi>
References: <20140117163307.GA4577@pob.ytti.fi> <201401172028.s0HKSJP6065706@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201401172028.s0HKSJP6065706@maildrop2.v6ds.occnc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Tue, 21 Jan 2014 08:01:11 -0800
Cc: mpls@ietf.org, lisp@ietf.org, tsvwg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jan 2014 22:33:04 -0000

On (2014-01-17 15:28 -0500), Curtis Villamizar wrote:

> This sounds like a router acting as a host for the given packet.  The
> forwarding data paths in routers are usually protected.  If the router

This was transit packets ingressing as IP packet, egressing as MPLS packet.
Consequently the peer router needed to touch TTL and checksum. Then generate
new L2 frame.
MPLS core obviously need not to worry about packet being broken, as frame is
fine.

> was forwarding and mangled packets, that speak well for the router
> vendor since the major vendors claim to protect their data paths from

Are such claims realistic or practical? I think it sounds like snakeoil when
someone claims such absolutes.

> this sort of thing.  Less so for the path from the route processor.

This was forwarding plane.

> You've made a good anecdotal case for keeping TCP and UDP checksums.

This would actually require IP checksum specifically, otherwise we would have
probably never found it. If each egress PE suffers from it maybe once 30min,
each customer suffers from it less than once a month, even if everyone would
catch it and open trouble ticket, we couldn't correlate the cases to any
single peering router, without having historic routing data for each egress
PE.

Disclaimer, I'm not for or against checksum/FCS in any particular layer, I've
not thought about the matter deeply. It was just extremely timely thing in
real-life network I wanted to share.

-- 
  ++ytti

From adrian@olddog.co.uk  Tue Jan 21 09:32:19 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB5F1A01B4; Tue, 21 Jan 2014 09:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9S2-qAToyY0; Tue, 21 Jan 2014 09:32:17 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id ED4581A011D; Tue, 21 Jan 2014 09:32:16 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0LHWD5f012989; Tue, 21 Jan 2014 17:32:13 GMT
Received: from 950129200 (14.21.90.92.rev.sfr.net [92.90.21.14]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0LHWBCd012983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 21 Jan 2014 17:32:12 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20140121123220.22080.99260.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121123220.22080.99260.idtracker@ietfa.amsl.com>
Subject: RE: Last Call: <draft-ietf-manet-olsrv2-rmpr-optimization-00.txt> (Routing MPR Optimization for the Optimized Link State Routing Protocol version 2 (OLSRv2)) to Proposed Standard
Date: Tue, 21 Jan 2014 17:32:13 -0000
Message-ID: <0b2201cf16ce$b9f1a850$2dd4f8f0$@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: AQHG3hSrZrEvJ4Ju2PHbphkRO7whdpqf3/UA
Content-Language: en-gb
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-rmpr-optimization.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 17:32:19 -0000

A few minor last call comments coming from my AD review.
The authors have already discussed these and know what to fix at the end of last
call.

Adrian

===

I think MPR could usefully be expanded in the document title, in the
Abstract, and on first use in the body.  Then you won't need to expand 
it in Section 3.

---

It seems odd that Section 4 has a bullet numbered "1." but no other
numbered bullets.

---

I think Section 4 uses the notation of 18.2 of [OLSRv2] not 18.3. At 
least, that is where d1() etc. are defined for revision -19 of that 
document.


From akatlas@gmail.com  Tue Jan 21 12:20:04 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A15001A0166; Tue, 21 Jan 2014 12:20:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_ABOUTYOU=0.5, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NiTZSpujKlzJ; Tue, 21 Jan 2014 12:20:02 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 134111A0125; Tue, 21 Jan 2014 12:20:01 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id ar20so5604565iec.6 for <multiple recipients>; Tue, 21 Jan 2014 12:20:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q9npFE35PfGotROmpBpR21Umf76VJaEmtFP5VBTEmzc=; b=ZuYGVDBL8IecI+uY33+AbSVGErHdrLkJgoQCkOqA/imun2MYPeB4m0SdNSxnPJCfID rS6k47J45wBoWsMsbyhbYxUp4UhLpF8taUHfrXToSAAihTlnJBNT9yqQ5RCVDjjBaHx/ +GqhdknSz+DaiMsFqY24gTcqndtLko/qpGvNz4A5Cws/YrgJPAmJlMg7qtMElp47YlrO jdvrGLjiT10EmHdol1Lr4vWK3Xqib6Nn5eS/eKL/mnIHCumUhv4pSGdFwiC3Z04KaYCd BLdb+K0Ew3Hjsvx/OuUyhP1bUKOnIxeRaK0cPXc25L5MT2YazR08NJVl/qwzIuh6nWAH bJDA==
MIME-Version: 1.0
X-Received: by 10.50.79.198 with SMTP id l6mr19754960igx.23.1390335601836; Tue, 21 Jan 2014 12:20:01 -0800 (PST)
Received: by 10.64.72.132 with HTTP; Tue, 21 Jan 2014 12:20:01 -0800 (PST)
In-Reply-To: <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
References: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com> <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
Date: Tue, 21 Jan 2014 15:20:01 -0500
Message-ID: <CAG4d1rfbvFe06dwAj7GJ5UrpzeWzTJWW1mBiZwF-g5+o2CHppg@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
From: Alia Atlas <akatlas@gmail.com>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary=089e013a1102aa89de04f080bbd2
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 20:20:04 -0000

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

Apologies for top-posting, but what struck me as very useful that Lars said
is:

"There are always special deployment scenarios where these principles do
not apply, and we typically explain in applicability statements when out
specifications can only be safely used under certain conditions. I don't
see any such statement in draft-ietf-mpls-in-udp, which to me means it's
targeted at general Internet-wide use."

Why don't we add an applicability statement?  That seems easier than trying
to define the appropriate congestion control mechanism which is highly
likely to interact badly with the congestion control applied to the
encapsulated traffic?

Alia

Alia


On Tue, Jan 21, 2014 at 8:22 AM, Eggert, Lars <lars@netapp.com> wrote:

> Hi,
>
> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> > You have made your assertions about your desire to uphold the purity
> > of any new UDP applications and adhere to the BCP you wrote.
> >
> > You appear to be very nearly alone in this argument and certainly no
> > one that works with MPLS is siding with you.
>
> the reason we wrote the RFC when I was TSV AD was that we were seeing a
> whole bunch of questionable uses of UDP over the eyars and we were having
> the same arguments over and over. That's why we decided to write down the
> practices we expect users of UDP to follow. This is yet another such
> questionable use.
>
> (Also, I don't appreciate you turning this into a personal argument.)
>
> > In the end we can put anything we want in the RFC *but* IETF has never
> > truly had the final word on what vendors and operators do in provider
> > networks.
>
> Aka the "take my toys and go home" argument. Heard it many times.
>
> > In this case, regardless of what changes are made to the draft,
> > implementations will offer at least the option for non-RFC behavior by
> > using zero checksums and not using any congestion control.  And
> > providers will make use of it, perhaps exclusively.
>
> And there's nothing wrong with that - the BCP even says that one SHOULD
> NOT use congestion control for some deployment cases.
>
> But for others, one SHOULD. For those, a mechanism needs to be available,
> i.e., it needs to be specified and implemented.
>
> > The document might as well reflect reality, despite reality not
> > conforming to your notions of architectural purity.
>
> I'm sorry, but we have certain architectural principles in the Internet
> that we have IETF consensus on. At least since RFC2914, that includes the
> need to have congestion control in place.
>
> There are always special deployment scenarios where these principles do
> not apply, and we typically explain in applicability statements when out
> specifications can only be safely used under certain conditions. I don't
> see any such statement in draft-ietf-mpls-in-udp, which to me means it's
> targeted at general Internet-wide use.
>
> > The best course of action is to put a SHOULD in regarding checksums
> > and put a SHOULD in regarding congestion avoidance.  Even the BCP does
> > not go any further than to say a tunneling protocol SHOULD use
> > congestion control and there were reasons that the word MUST was not
> > acceptable in the BCP.
>
> The SHOULD for congestion control needs to actually describe a mechanism
> that can be used when needed. It can't be a blanket "you SHOULD use
> something but we don't tell you what it is"-statement.
>
> > If we are still arguing over two instances of SHOULD vs MUST we have
> > wasted a lot of bandwidth on those two words.
>
> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs to
> be specified what is to be done. In the case of checksums, that's obvious
> (calculate it and check it); in the case of congestion control, some actual
> mechanism needs to be described (e.g., a circuit breaker).
>
> > IMHO The only remaining question is whether the document can go forward
> > with the definition of congestion control for MPLS over UDP left out
> > of scope and for another document if a need arises.
>
> In my opinion, it cannot.
>
> > If this is not acceptable to you (I doubt it is) please indicate what
> > you would like to see in the document and since this is IETF last call
> > where consensus matters and no one individual has veto power, we'll
> > have to see if there is consensus behind your proposed changes.
>
> I would like the document to specify at the very least a circuit breaker
> mechanism, that stops the tunneled traffic if severe packet loss is
> detected along the path.
>
> And this isn't about an "individual veto". This is about a document that
> is at the moment in violation of IETF consensus at least as far back as
> RFC2914.
>
> Lars
>

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

<div dir=3D"ltr">Apologies for top-posting, but what struck me as very usef=
ul that Lars said is:<div><br></div><div>&quot;<span style=3D"font-family:a=
rial,sans-serif;font-size:13px">There are always special deployment scenari=
os where these principles do not apply, and we typically explain in applica=
bility statements when out specifications can only be safely used under cer=
tain conditions. I don&#39;t see any such statement in draft-ietf-mpls-in-u=
dp, which to me means it&#39;s targeted at general Internet-wide use.&quot;=
</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">Why=
 don&#39;t we add an applicability statement? =A0That seems easier than try=
ing to define the appropriate congestion control mechanism which is highly =
likely to interact badly with the congestion control applied to the encapsu=
lated traffic?</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">Ali=
a</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13=
px"><br>
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:13p=
x">Alia</span></div></div><div class=3D"gmail_extra"><br><br><div class=3D"=
gmail_quote">On Tue, Jan 21, 2014 at 8:22 AM, Eggert, Lars <span dir=3D"ltr=
">&lt;<a href=3D"mailto:lars@netapp.com" target=3D"_blank">lars@netapp.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">Hi,<br>
<br>
On 2014-1-17, at 18:19, Curtis Villamizar &lt;<a href=3D"mailto:curtis@ipv6=
.occnc.com">curtis@ipv6.occnc.com</a>&gt; wrote:<br>
&gt; You have made your assertions about your desire to uphold the purity<b=
r>
&gt; of any new UDP applications and adhere to the BCP you wrote.<br>
&gt;<br>
&gt; You appear to be very nearly alone in this argument and certainly no<b=
r>
&gt; one that works with MPLS is siding with you.<br>
<br>
the reason we wrote the RFC when I was TSV AD was that we were seeing a who=
le bunch of questionable uses of UDP over the eyars and we were having the =
same arguments over and over. That&#39;s why we decided to write down the p=
ractices we expect users of UDP to follow. This is yet another such questio=
nable use.<br>

<br>
(Also, I don&#39;t appreciate you turning this into a personal argument.)<b=
r>
<br>
&gt; In the end we can put anything we want in the RFC *but* IETF has never=
<br>
&gt; truly had the final word on what vendors and operators do in provider<=
br>
&gt; networks.<br>
<br>
Aka the &quot;take my toys and go home&quot; argument. Heard it many times.=
<br>
<br>
&gt; In this case, regardless of what changes are made to the draft,<br>
&gt; implementations will offer at least the option for non-RFC behavior by=
<br>
&gt; using zero checksums and not using any congestion control. =A0And<br>
&gt; providers will make use of it, perhaps exclusively.<br>
<br>
And there&#39;s nothing wrong with that - the BCP even says that one SHOULD=
 NOT use congestion control for some deployment cases.<br>
<br>
But for others, one SHOULD. For those, a mechanism needs to be available, i=
.e., it needs to be specified and implemented.<br>
<br>
&gt; The document might as well reflect reality, despite reality not<br>
&gt; conforming to your notions of architectural purity.<br>
<br>
I&#39;m sorry, but we have certain architectural principles in the Internet=
 that we have IETF consensus on. At least since RFC2914, that includes the =
need to have congestion control in place.<br>
<br>
There are always special deployment scenarios where these principles do not=
 apply, and we typically explain in applicability statements when out speci=
fications can only be safely used under certain conditions. I don&#39;t see=
 any such statement in draft-ietf-mpls-in-udp, which to me means it&#39;s t=
argeted at general Internet-wide use.<br>

<br>
&gt; The best course of action is to put a SHOULD in regarding checksums<br=
>
&gt; and put a SHOULD in regarding congestion avoidance. =A0Even the BCP do=
es<br>
&gt; not go any further than to say a tunneling protocol SHOULD use<br>
&gt; congestion control and there were reasons that the word MUST was not<b=
r>
&gt; acceptable in the BCP.<br>
<br>
The SHOULD for congestion control needs to actually describe a mechanism th=
at can be used when needed. It can&#39;t be a blanket &quot;you SHOULD use =
something but we don&#39;t tell you what it is&quot;-statement.<br>
<br>
&gt; If we are still arguing over two instances of SHOULD vs MUST we have<b=
r>
&gt; wasted a lot of bandwidth on those two words.<br>
<br>
It&#39;s not SHOULD vs. MUST. It&#39;s two SHOULDs, but in both cases it ne=
eds to be specified what is to be done. In the case of checksums, that&#39;=
s obvious (calculate it and check it); in the case of congestion control, s=
ome actual mechanism needs to be described (e.g., a circuit breaker).<br>

<br>
&gt; IMHO The only remaining question is whether the document can go forwar=
d<br>
&gt; with the definition of congestion control for MPLS over UDP left out<b=
r>
&gt; of scope and for another document if a need arises.<br>
<br>
In my opinion, it cannot.<br>
<br>
&gt; If this is not acceptable to you (I doubt it is) please indicate what<=
br>
&gt; you would like to see in the document and since this is IETF last call=
<br>
&gt; where consensus matters and no one individual has veto power, we&#39;l=
l<br>
&gt; have to see if there is consensus behind your proposed changes.<br>
<br>
I would like the document to specify at the very least a circuit breaker me=
chanism, that stops the tunneled traffic if severe packet loss is detected =
along the path.<br>
<br>
And this isn&#39;t about an &quot;individual veto&quot;. This is about a do=
cument that is at the moment in violation of IETF consensus at least as far=
 back as RFC2914.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Lars<br>
</font></span></blockquote></div><br></div>

--089e013a1102aa89de04f080bbd2--

From hartmans@mit.edu  Tue Jan 21 13:38:44 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 954981A0393; Tue, 21 Jan 2014 13:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IvEI1sLEYw4J; Tue, 21 Jan 2014 13:38:43 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D79A81A0381; Tue, 21 Jan 2014 13:38:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8DD492064F; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCpIgOxvohNk; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Tue, 21 Jan 2014 16:35:55 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8561E8351F; Tue, 21 Jan 2014 16:38:41 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie>
Date: Tue, 21 Jan 2014 16:38:41 -0500
In-Reply-To: <52DC1F71.80102@cs.tcd.ie> (Stephen Farrell's message of "Sun, 19 Jan 2014 18:54:41 +0000")
Message-ID: <tsl8uu9dnha.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, gen-art <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 21:38:44 -0000

I think that consideration of perpass at the architectural  level, being
prepared to justify decisions, and seeking adequate review of those
decision early enough to make changes if we're wrong are critical to
this document.
strongly object to publication of this document without that.

I value integrity and honesty very highly and am feel sick when I think
about claiming to the world that we're going to address perpass
mitigations without being willing to commit to ourselves  to do the
architectural work.
You cannot simply  take a protocol and mitigate these sorts of issues.
Many of our existing technologies leak a lot of information to
attackers.
One of the most important decisions when we start work on new protocols
in terms of perpass mitigation will be what building blocks we use.

If we're not willing to commit to having those discussions up front,
reviewing them and when questions arise during that review , I don't
think we're being truthful or acting with integrity if we claim that
we're mittigating perpass threats.

I'd much rather us be honest that we're not willing to do what it takes
to deal with perpass threats than to claim to try and mitigate them with
a solution that I think will be unsuccessful.

I do understand being concerned and worried that an AD would block
something late in the process because of bad architecture.
If the architecture was appropriately reviewed, I think that's the right
wrong approach.  I'd support language making that more clear.
If the architecture was inadequately reviewed, I strongly feel  that
should be handled like any process problem.  Some process problems are
blocking; some cases of inadequate review of an architecture also should
be blocking.
Yes, some of that is subjective and needs to be argued by the IESG and
community if there is conflict.

From scott.brim@gmail.com  Tue Jan 21 14:26:32 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8171A0232; Tue, 21 Jan 2014 14:26:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id plQnuMDA9cO2; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADA51A01F6; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id j17so4045199oag.28 for <multiple recipients>; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zfsiA/cLT0pbUGnMFWF+nruSdueijanTYy6qxbiYRB0=; b=ZIHwbAxdSRmEa1rpGjLZcdPIbOvsHSo582GeevTrEqw9+/loONcMovijfmA4oLMDXm 4qYy7tf21ik2G78wXqSGbxFa0jPELH1TJubti/iyCPS/01r5/U0wMBMMZbuHbQ1NeBv/ 1JiPCNRt710iRl5XuJWbnjrsu2y2bkBsewWPIXre6oC3vivReU8GfwdNDJnAw/P6Chhf nZGAfa7/QhfmaY3hbk1HCA83nBOf3CJz46gQX5lBeD3mRl7ZEFCmJBwChNEJZl29LV0Q AT0biXG0O8p3k2azq07PhPzDzW4JkMFwis9f2x7UyqVCBvhhSSzL+R7cqvAuXQPUSsdb QLZQ==
MIME-Version: 1.0
X-Received: by 10.60.63.102 with SMTP id f6mr3020461oes.76.1390343190212; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 14:26:30 -0800 (PST)
In-Reply-To: <tsl8uu9dnha.fsf@mit.edu>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu>
Date: Tue, 21 Jan 2014 17:26:30 -0500
Message-ID: <CAPv4CP-d2BNzG6Ww+sCFWcXGZgYi59bqqenksgaDqSggqRhmyg@mail.gmail.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
From: Scott Brim <scott.brim@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: multipart/alternative; boundary=001a11c25532f7f7e904f0827f51
Cc: IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, gen-art <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Jan 2014 22:26:32 -0000

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

Sam: I believe that all you ask is still there.  We will consider PM at
architecture time, and anyone can contribute. We'll take it seriously.
What's missing is the requirement to demonstrate that you have covered all
the issues, to an unknown level.  Essentially this is how we work already.

Scott

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

<p dir=3D"ltr">Sam: I believe that all you ask is still there.=A0 We will c=
onsider PM at architecture time, and anyone can contribute. We&#39;ll take =
it seriously.=A0 What&#39;s missing is the requirement to demonstrate that =
you have covered all the issues, to an unknown level.=A0 Essentially this i=
s how we work already. </p>

<p dir=3D"ltr">Scott </p>

--001a11c25532f7f7e904f0827f51--

From dhc@dcrocker.net  Tue Jan 21 14:56:09 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A911D1A0263; Tue, 21 Jan 2014 14:56:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EJimi9DLK9Dy; Tue, 21 Jan 2014 14:56:08 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB231A01D7; Tue, 21 Jan 2014 14:56:08 -0800 (PST)
Received: from [192.168.1.6] (cpe-76-93-140-82.san.res.rr.com [76.93.140.82]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s0LMtvt3006178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 14:56:00 -0800
Message-ID: <52DEFAEE.3000900@dcrocker.net>
Date: Tue, 21 Jan 2014 14:55:42 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu>
In-Reply-To: <tsl8uu9dnha.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.66]); Tue, 21 Jan 2014 14:56:01 -0800 (PST)
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Jan 2014 22:56:09 -0000

On 1/21/2014 1:38 PM, Sam Hartman wrote:
> I think that consideration of perpass at the architectural  level, being
> prepared to justify decisions, and seeking adequate review of those
> decision
...
> I value integrity and honesty very highly and am feel sick when I think
> about claiming to the world that we're going to address perpass
> mitigations without being willing to commit to ourselves  to do the
> architectural work.


Sam,

Consider the level of activity on this topic that is already happening 
in the IETF, as well as the nature of this initial document.  I'll 
suggest that that's the most important demonstration of organizational 
commitment.

The document in question marks that commitment, but it needs to be 
careful not to mark it beyond our current capabilities.

In particular please point me/us to established consensus documents that 
define the problem space, the solution space and the architectural 
choices appropriate to this topic.  I'm not aware of any, but perhaps I 
missed them.

Absent established documents on this topic, "justifying" is only 
reasonable in terms of demonstrating thoughtfulness, not demonstrating 
that the choices are "correct".  Yet a term like "justify" encourages 
this latter expectations.   the view that we have far more community 
clue about this topic than we currently have.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From david.black@emc.com  Tue Jan 21 16:02:48 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7BB81A0260; Tue, 21 Jan 2014 16:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.536
X-Spam-Level: 
X-Spam-Status: No, score=-4.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hd7k7sLMCekh; Tue, 21 Jan 2014 16:02:44 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6911A0225; Tue, 21 Jan 2014 16:02:43 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0M02fZN012270 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 19:02:42 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0M02fZN012270
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390348963; bh=xzCObmqSS8B84Tukb1D8ud+K38U=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=QBb4PRc37bQuK1QBOFetFFlDVKVJkFLBL6Q1SPOdkewpuQy2L6kWxPlRTC65YfsF9 wqyYwC6+d+n4vWQPisOXrJJbGdyWWu+1Ml6jhQrmQLtYJDYZW1SZM9VeryntROcPIB T8d6VRPjPj2Kaz1EKry1ZAjWlmDu1vhcETrUa2kM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0M02fZN012270
Received: from mailusrhubprd53.lss.emc.com (mailusrhubprd53.lss.emc.com [10.106.48.18]) by maildlpprd04.lss.emc.com (RSA Interceptor); Tue, 21 Jan 2014 16:02:36 -0800
Received: from mxhub03.corp.emc.com (mxhub03.corp.emc.com [10.254.141.105]) by mailusrhubprd53.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0M02YPi002932 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 19:02:35 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub03.corp.emc.com ([10.254.141.105]) with mapi; Tue, 21 Jan 2014 19:02:34 -0500
From: "Black, David" <david.black@emc.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Date: Tue, 21 Jan 2014 19:02:33 -0500
Subject: RE: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Topic: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Index: Ac8W3kd3cn8I8nSsRQ6C7ksWTmbcMwAHK7fQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F047CC2@MX15A.corp.emc.com>
References: Your message of "Sun, 19 Jan 2014 21:05:17 -0500." <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com> <201401211923.s0LJNRPm064842@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401211923.s0LJNRPm064842@maildrop2.v6ds.occnc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd53.lss.emc.com
X-RSA-Classifications: DLM_1, public, GIS Solicitation
Cc: "draft-ietf-mpls-multipath-use.all@tools.ietf.org" <draft-ietf-mpls-multipath-use.all@tools.ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 00:02:49 -0000

Curtis,

> Thanks for the review and for pointing out lack of clarity due to
> underlying assumptions about the use of RFC 4206 (and perhaps use of
> RFC 4201 as well for large MPLS LSP over MPLS-TP).
>
> Sometimes it is too easy to forget that not all readers are going to
> be as steeped in MPLS "as deployed today" details as a relatively
> small number of long time MPLS participants are.
>
> Adding a few paragraphs to the introduction and a few concluding
> paragraphs may significantly improve clarity for people who have not
> been following MPLS closely for a decade or more without requiring
> them to read the references and figure out usage details themselves.
>
> Please let me know how you feel about the suggested additions to the
> document.

Most of them look good - details below.  Many thanks for the prompt and
comprehensive response.  I have a few more suggestions in what follows
- anything that I don't comment on below is fine with me.

-- Introduction

> There is an underlying assumption in the draft that the reader
> understands that MPLS-in-MPLS exists today, most commonly but not
> exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> means to advertise forward adjacencies (FA) where MPLS-in-MPLS at some
> level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> to make use of the management plane, using CLI or NETCONF or the MPLS
> cross connect MIB to program a multiple label MPLS push operation.
>
> If a very experienced reviewer could miss that, then the introduction
> could be improved by better stating assumptions.  It is also the case
> that many participants in MPLS, particularly those primarily
> interested in MPLS-TP, began participation long after RFC 4206 was
> written and would benefit by better stated assumptions in the intro.
>
> I suggest that the following paragraphs be added to the introduction.

The suggested new paragraphs will definitely improve the introduction.

-- [A] Summary text in Introduction appears to be wrong.

> > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > exception appears to concern the reverse, and Section 4 on carrying MPL=
S
> > over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> > Was the exception intended to be for an MPLS-TP LSP that exceeds the
> > capacity of any single component link?

[... snip ...]

> To answer your question directly: the exception is a very large MPLS
> LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> this is occurring.

It looks like  my confusion stemmed from the original text only
discussing only what won't work and referencing a section that
concerns a different encapsulation order than the one that causes
the problem.  Including the "MAY NOT" -> "SHOULD NOT" change, I suggest:

OLD
   When an MPLS LSP
   exceeds the capacity of any single component link it MAY be carried
   by a network using multipath techniques, but MAY NOT be carried by a
   single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
   imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
   fate sharing constraints and MPLS-TP LM OAM packet ordering
   constraints (see Section 3.1).
NEW
   When an MPLS LSP
   exceeds the capacity of any single component link it MAY be carried
   by a network using multipath techniques, but SHOULD NOT be carried by a
   single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
   imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
   fate sharing constraints and MPLS-TP LM OAM packet ordering
   constraints (see Section 3.1).  Instead, multiple MPLS-TP LSPs SHOULD
   be used to carry a large MPLS LSP (see Section 4).

-- [B] Section 3.2 needs a summary.

The proposed summary looks good, and helps with [C], but the phrase
"access and edge" needs qualification in the following sentence:

   However access and edge is the least likely to support
   RFC 6790 in the near term.

"access and edge" what? e.g., areas of the network? LSRs?

-- [C] Entropy label "sandwich" seems peculiar and at least needs an explan=
ation.

> The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> paragraph.
>
>    Alternately, the need for requirement MP#1 can be eliminated if
>    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
>    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
>    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
>    in a deployment support Entropy Label, which may render it
>    impractical in many deployments.
>
> Please not the "Alternately" at the beginning and "impractical in many
> deployments" at the end.
>
> The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> above that but assumes knowledge of RFC 6790.  I think the following
> change within this paragraph would clear things up:

That change is helpful, but my "sandwich" concern was actually raised
by text two paragraphs further down:

   MPLS-TP LSPs can be carried as client LSPs within an MPLS server LSP
   if an Entropy Label Indicator (ELI) and Entropy Label (EL) is pushed
   below the server layer LSP label(s) in the label stack, just above
   the MPLS-TP LSP label entry [RFC6790].

Read after the "Alternately" paragraph, this text appeared to suggest
a "sandwich" that would have an ELI/EL pair both above and below the
MPLS-TP label.  That was clearly not intended, so I suggest inserting
"When Entropy Label Indicators (ELIs) and Entropy Labels (ELs) are not
applied by MPLS-TP ingresses," before the start of the first sentence
above, so that the result is:

   When Entropy Label Indicator (ELIs) and Entropy Labels (ELs) are
   not applied by MPLS-TP ingresses, MPLS-TP LSPs can be carried as
   client LSPs within an MPLS server LSP if an ELI and EL are pushed
   below the server layer LSP label(s) in the label stack, just above
   the MPLS-TP LSP label entry [RFC6790].

-- [D] Discussion of multipath impacts on MPLS OAM

> > Section 3.2 discusses OAM, and contains this important
> > requirement for OAM traffic:
> >
> >    An Entropy Label must be used to insure that all of the
> >    MPLS-TP payload and OAM traffic are carried on the same component,
> >    except during very infrequent transitions due to load balancing.
> >
> > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > Section 4; that should be added.
>
> There is no impact on MPLS OAM traffic.  There are three cases to
> consider.
>
>   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
>      one link.  MPLS OAM is unaffected and need not use multipath
>      support in LSP Ping.
>
>   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
>      LSP is carried over one link thanks to the fixed EL value.
>      MPLS-TP OAM is unaffected.
>
>   3.  Where MPLS is carried over MPLS (an existing case) or over
>       multiple MPLS-TP, the multipath support in LSP Ping (as
>       imperfect as it may already be) is used and LSP Ping (RFC 4379)
>       operation is unaffected.
>
> If needed something can be added to state the above (maybe with less
> informal wording).  What is obvious to some people may not be obvious
> to everyone.  Briefly stating the almost obvious is usually not a bad
> thing.

Points 1-3 are useful explanation as complement to the Entropy label
requirement to correctly handle OAM traffic for the other encapsulation.

I like your suggestion to add this text as part of a new concluding
Section 5, and the rest of the proposed conclusion section text looks
good.

Thanks,
--David

> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]
> Sent: Tuesday, January 21, 2014 2:23 PM
> To: Black, David
> Cc: ops-dir@ietf.org; ietf@ietf.org; draft-ietf-mpls-multipath-
> use.all@tools.ietf.org
> Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
>
>
> In message <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com=
>
> "Black, David" writes:
> >
> > I have reviewed this document as part of the operations directorate's
> > ongoing effort to review all IETF documents being processed by the
> > IESG.  These comments were written primarily for the benefit of the
> > operations area directors.  Document editors and WG chairs should treat
> > these comments just like any other last call comments.
> >
> > Summary:
> > This draft is on the right track but has open issues, described in the
> review.
> >
> > I apologize for this review showing up a couple of days after the end o=
f
> > IETF Last Call.
> >
> > This draft discusses considerations for what are effectively MPLS-in-MP=
LS
> > tunnels for multipathing - an LSP carries another LSP, with the inner
> > (client) LSPs being distributed across multiple outer (server) LSPs tha=
t
> > use different paths.  This draft is motivated by considerations specifi=
c
> > to MPLS-TP that complicate multipathing when one of the two MPLS instan=
ces
> > is MPLS-TP.
>
> Skipping to the discussion quite a ways down, there seems to be some
> confusion about what is being proposed here.  While MPLS-in-MPLS is
> being used, no new form of MPLS-in-MPLS is being proposed.
>
> There is an underlying assumption in the draft that the reader
> understands that MPLS-in-MPLS exists today, most commonly but not
> exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> means to advertise forward adjacencies (FA) where MPLS-in-MPLS at some
> level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> to make use of the management plane, using CLI or NETCONF or the MPLS
> cross connect MIB to program a multiple label MPLS push operation.
>
> If a very experienced reviewer could miss that, then the introduction
> could be improved by better stating assumptions.  It is also the case
> that many participants in MPLS, particularly those primarily
> interested in MPLS-TP, began participation long after RFC 4206 was
> written and would benefit by better stated assumptions in the intro.
>
> I suggest that the following paragraphs be added to the introduction.
>
>    MPLS LSPs today are able to function as a server layer and carry
>    client MPLS LSPs.  When control plane signaling is used, forwarding
>    adjacency (FA) advertisements are used to inform the set of LSR of
>    Packet Switching Capable (PSC) LSP within the MPLS topology
>    [RFC4206].  Client MPLS LSP at a higher layer (lower PSC number)
>    may signal their intention to use PSC LSP as hops in the RSVP-TE
>    Explicit Route Object (ERO).  LSR with no explicit support for RFC
>    4206 see the PSC LSP as ordinary links and therefore use them.
>
>    An MPLS LSP that has been set up using RSVP-TE appears to its
>    ingress LSR as a viable IP next hop to a distant LSR.  If LDP is
>    used and bidirectional RSVP-TE LSP connectivity is available, then
>    LDP signaling can be set up among the RSVP-TE LSP endpoints and LDP
>    can make use of the RSVP-TE LSP as an LDP hop.  This is another
>    form of existing MPLS-in-MPLS use.
>
>    MPLS LSPs may also make use of hierarchy that is configured through
>    the management plane rather than signaled using RSVP-TE.
>
>    These existing forms of MPLS-in-MPLS may traverse multipath hops
>    such as Ethernet LAG [IEEE802.1AX] or MPLS Link Bundling [RFC4201].
>    MPLS-TP brings with it a new set of requirements not considered in
>    past deployments of the various forms of MPLS-in-MPLS where
>    multipath was in use.  This document merely discusses use of
>    existing forwarding and protocol mechanisms that can support the
>    case where either the client layer LSPs or the server layer LSPs
>    are MPLS-TP and where multipath is used.
>
> If there are no objections I will add these paragraphs.
>
> Now on to the specific comments.
>
> > I consider the following to be open issues that need attention (each
> > letter is used to tag the issue in the text that follows - [B] occurs
> > multiple times, as there are multiple aspect to that issue):
> >
> > [A] Summary text in Introduction appears to be wrong.
> > [B] Section 3.2 needs a summary.
> > [C] Entropy label "sandwich" seems peculiar and at least needs an expla=
nation.
> > [D] Discussion of multipath impacts on MPLS OAM should be added to Sect=
ion
> 4.
> >
> > --- Comments on draft text
> >
> > [A] Section 1 (Introduction) 2nd paragraph:
> >
> >    RFC 5654 requirement 33 requires the capability to carry a client
> >    MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC5654].
> >    This is possible in all cases with one exception.  When an MPLS LSP
> >    exceeds the capacity of any single component link it MAY be carried
> >    by a network using multipath techniques, but MAY NOT be carried by a
> >    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
> >    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
> >    fate sharing constraints and MPLS-TP LM OAM packet ordering
> >    constraints (see Section 3.1).
> >
> > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > exception appears to concern the reverse, and Section 4 on carrying MPL=
S
> > over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> > Was the exception intended to be for an MPLS-TP LSP that exceeds the
> > capacity of any single component link?
>
> There is no problem today with MPLS LSP carried by MPLS-TP LSP except
> the existing case where MPLS LSP capacity is too big.  For example, a
> 500 Gb/s LSP is possible today carried over N x 100 Gb/s or N x 10
> Gb/s multipath links but could not be carried over a single MPLS-TP
> LSP which would be limited to a single 100 Gb/s or 10 Gb/s link.  So
> the exception is where the MPLS LSP is too big to fit in any possible
> single MPLS-TP LSP.
>
> To answer your question directly: the exception is a very large MPLS
> LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> this is occurring.
>
> > Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's equival=
ent
> > to "MAY OR MAY NOT").  I think "cannot" was intended here, but "MUST NO=
T"
> > is another possibility.
>
> Good point.  I suggest we replace the MAY NOT with SHOULD NOT.  Many
> people would insist that it should be MUST NOT, but in reality
> networks SHOULD NOT be congested but sometimes they are.
>
> > [B] Section 3.2 contains a lot of useful details, but it could really u=
se
> > a summary at the end on the options and recommendations for meeting the
> > four requirements (this summary could be a new Section 3.3).  It's a bi=
t
> > difficult to discern what's going on, as I had to read this section mor=
e
> > than once in order to discern the following:
>
> OK.  A Summary paragraph can be added.  See below.  Perhaps conclusion
> section can be added.  See far below.
>
> > [C] In Section 3.2, use of an MPLS entropy label to meet requirement MP=
#1
> > requires that it be "below the MPLS-TP label" whereas, to meet requirem=
ent
> > MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LSP la=
bel".
> > This combination appears to suggest "sandwiching" the MPLS-TP label bet=
ween
> > two entropy labels that effectively carry the same information (albeit,
> > applied and removed at different places in the network) - was that inte=
nded?
> > This is important, as there seems to be no reasonable alternative
> > to the entropy label for meeting requirement MP#2, and the draft's
> > alternative to the entropy label for meeting requirement MP#1 is "some =
form
> > of configuration" - the entropy label would seem to be preferred to tha=
t
> > based on my reading of this draft and the comment in RFC 5706 section 2=
.2
> > that "Anything that can be configured can be misconfigured."
>
> The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> paragraph.
>
>    Alternately, the need for requirement MP#1 can be eliminated if
>    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
>    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
>    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
>    in a deployment support Entropy Label, which may render it
>    impractical in many deployments.
>
> Please not the "Alternately" at the beginning and "impractical in many
> deployments" at the end.
>
> The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> above that but assumes knowledge of RFC 6790.  I think the following
> change within this paragraph would clear things up:
>
>  OLD
>
>    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
>    and Entropy Label (EL) are added to the label stack [RFC6790].  For
>    those client LSP that are MPLS-TP LSP, a single EL value must be
>    chosen.  For those client LSP that are MPLS LSP, per packet entropy
>    below the top label must, for practical reasons, be used to
>    determine the entropy label value.
>
>  NEW
>
>    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
>    and Entropy Label (EL) are added to the label stack by the midpoint
>    LSR for the client MPLS-TP LSP, at the ingress of the MPLS LSP
>    [RFC6790].  For those client LSP that are MPLS-TP LSP, a single EL
>    value must be chosen.  For those client LSP that are MPLS LSP, per
>    packet entropy below the top label must, for practical reasons, be
>    used to determine the entropy label value.  The resulting label
>    stack contains the server MPLS LSP label, ELI, EL and the client
>    LSP label.
>
> The above rewording is simply more explicit about the label stack
> order and which LSR puts the ELI and EL in the label stack.
>
> > [B] A summary of requirements for implementation and deployment at the =
end
> > of Section 3.2 would have made this much more obvious.  That should be
> > provided in addition to addressing the above question about duplicate u=
se
> > of the MPLS entropy label.
>
> The following summary can be added to the end of Section 3.2:
>
>    Two methods of adding an Entropy Label are described above.  The
>    MPLS-TP ingress must have a means to determine which links can
>    support MPLS-TP in selecting a path (MP#4).  Administrative
>    attributes can satisfy that requirement.  If the MPLS-TP LSR is
>    capable of adding ELI/EL to the label stack, this method is
>    preferred.  However access and edge is the least likely to support
>    RFC 6790 in the near term.  For portions of the topology where an
>    MPLS-TP is carried within a server layer MPLS LSP the ingress of
>    the server layer MPLS LSP can add ELI/EL using a fixed EL value per
>    client LSP, except those known not to require MPLS-TP treatment.
>    There are numerous ways to determine which client LSP are MPLS-TP
>    LSP and which are not.  While this determination is out of scope
>    and will vary among deployments, configuration or the presence of
>    specific attribute affinities in RSVP-TE signaling are among the
>    likely means to do so.
>
> If there are no objections I will add the above paragraph.
>
> > --- Relevant Q&A based on RFC 5706 Appendix A
> >
> > I'm omitting management concerns, as both MPLS and MPLS-TP have extensi=
ve
> > management infrastructure, and this draft's notion of stacking LSPs so
> > that one instance of MPLS (or MPLS-TP) can be a server to (i.e., carry)
> > another is not novel to this draft.
> >
> > A.1.1.  Has deployment been discussed?
> >
> > [B] Yes, although Section 3.2 is weak on deployment requirements (some =
of
> > which are implementation requirements) and could use a summary.
>
> The use of RFC 4206 is assumed throughout the discussion of signaling
> in section 3.2.  This assumption is made more clear by suggested
> additions to the introduction.
>
> > A.1.2.  Has installation and initial setup been discussed?
> >
> > No, although because this draft reuses existing functionality in differ=
ent
> > configurations, this really reduces to the A.1.9 configuration question
> > below.  In practice, quite a bit of operator knowledge and insight is
> > required to get initial setup right, e.g., as traffic engineering LSPs =
to
> > avoid congestion problems (needed to meet requirement MP#3) requires
> > significant knowledge of network structure and expected traffic flows.
> > This should be obvious to anyone who works w/MPLS, but it's probably
> > worth stating for completeness.
>
> FA advertisements defined in RFC 4206 make it possible for ingress to
> signal viable paths.  Either the use of Ethernet Link Aggregation or
> MPLS Link bundling using the all-ones component link (RFC 4201) allows
> the total capacity of a multipath to be advertised.  Meeting the
> requirement to balance traffic over the component links in a multipath
> (MP#3) is then a local matter and requires no further signaling
> extensions.
>
> > A.1.6.  Have suggestions for verifying correct operation been discussed=
?
> >
> > Yes and no.  Section 3.2 discusses OAM, and contains this important
> > requirement for OAM traffic:
> >
> >    An Entropy Label must be used to insure that all of the
> >    MPLS-TP payload and OAM traffic are carried on the same component,
> >    except during very infrequent transitions due to load balancing.
> >
> > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > Section 4; that should be added.
>
> There is no impact on MPLS OAM traffic.  There are three cases to
> consider.
>
>   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
>      one link.  MPLS OAM is unaffected and need not use multipath
>      support in LSP Ping.
>
>   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
>      LSP is carried over one link thanks to the fixed EL value.
>      MPLS-TP OAM is unaffected.
>
>   3.  Where MPLS is carried over MPLS (an existing case) or over
>       multiple MPLS-TP, the multipath support in LSP Ping (as
>       imperfect as it may already be) is used and LSP Ping (RFC 4379)
>       operation is unaffected.
>
> If needed something can be added to state the above (maybe with less
> informal wording).  What is obvious to some people may not be obvious
> to everyone.  Briefly stating the almost obvious is usually not a bad
> thing.  Please tell me if a small subsection on "Imopact on MPLS and
> MPLS-TP OAM" is needed.
>
> Note that the limitations of LSP Ping are currently being discussed in
> the MPLS WG in the context of extensions to LSP Ping to better support
> Entropy Label.  A few limitations not related to EL may get fixed in
> the process.
>
> > A.1.9.  Is configuration discussed?
> >
> > [B] Not much. Configuration is required to meet requirements MP#3 and M=
P#4,
> > and is one of the options for MP#1.  A summary of what has to be config=
ured
> > as part of the summary at the end of Section 3.2 would be a good idea.
>
> Perhaps a worked example appendix could be added but I don't think
> this is common and may not be necessary with some of the
> clarifications suggested so far.
>
> > A.2.* [skipped, see above]
> >
> > A.3 Documentation
> >
> > There's quite a bit of operational material contained in this draft; a
> > separate section on operations and management considerations would not
> > be appropriate.
> >
> > There is a useful implementation status section which appears to imply
> > that MPLS-TP over MPLS is not currently deployable due to absence of
> > entropy label support, and because deployed MPLS equipment does not
> > generally support multipathing.  Nonetheless, data center experience
> > indicates significant value and widespread use of multipathing based
> > on link aggregation and ECMP; corresponding benefits can be expected
> > for use of multipathing in the Internet beyond data centers.
>
> If you would like I can add a conclusion section as Section 5 with
> these paragraphs:
>
>    MPLS equipment deployed in the core currently supports multipath.
>    For large service providers, core LSR must support some form of
>    multipath to be deployable.  Deployed MPLS access and edge
>    equipment is often oblivious to the use of multipath in the core.
>    It is expected that at least first generation MPLS-TP equipment
>    will be oblivious to the use of multipath in the core.  This first
>    generation MPLS-TP equipment is deployable in a core using
>    multipath, with no adverse impact to RSVP-TE signaling, if the edge
>    equipment can support administrative attributes (RFC 3209) and the
>    core equipment can support ELI/EL and put a per-LSP fixed EL value
>    on any LSP that indicates a particular attribute affinity or can
>    identify client MPLS-TP LSP through some other means.
>
>    There are no issues carrying MPLS over MPLS-TP, except when the
>    MPLS LSP is too big to be carried by a single MPLS-TP LSP.  Most
>    MPLS core equipment and some edge equipment can configure an MPLS
>    Link Bundle [RFC4201] over multiple component links where the
>    component links are themselves MPLS LSP.  This existing capability
>    can be used to carry large MPLS LSP and overcome the limited
>    capacity of any single server layer MPLS-TP LSP.
>
> If this conclusion section is added, then the three bullets above
> regarding impact on OAM can be put there.  The three bullets can be
> added as follows:
>
>    MPLS OAM and MPLS-TP OAM are unaffected in the following cases
>    proposed in this document:
>
>      1. Where MPLS is carried over a single MPLS-TP all traffic flows
>         on one link.  MPLS OAM is unaffected and need not use
>         multipath support in LSP Ping.
>
>      2. Where MPLS-TP is carried over MPLS, all traffic for that
>         MPLS-TP LSP is carried over one link thanks to the fixed EL
>         value.  MPLS-TP OAM is unaffected.
>
>      3.  Where MPLS is carried over MPLS (an existing case) or over
>          multiple MPLS-TP, the multipath support in LSP Ping is used
>          and LSP Ping (RFC 4379) operation is unaffected.
>
> I think adding the above as a conclusion section as Section 5 would
> improve clarity and therefore is worth doing.
>
> > --- Editorial comments/nits:
> >
> > - Section 3.1, after RFC 5960 quotes:
> >
> >    [RFC5960] paragraph 3 requires that packets within a specific ordere=
d
> >
> > Insert "Section 3.1.1.", before "paragraph 3" and likewise for "paragra=
ph 6"
> > later in the same paragraph in the draft.
>
> GenArt review caught this.  Done.
>
> > - Section 3.2, requirement MP#3:
> >
> >    MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not be
> >
> > "insure" -> "ensure" or "assure".  Surely this draft does not envision
> > operators taking out insurance policies on MPLS TP LSP behavior ;-).
>
> Good catch.  I think "ensure" is the right word.
>
> > - Section 3.2, last paragraph on p.8:
> >
> >    An MPLS-TP LSP may not traverse multipath links on the path where
> >    MPLS-TP forwarding requirements cannot be met.
> >
> > "may not" is meaningless - I believe "MUST NOT" was intended here.
>
> I suggested SHOULD NOT above.
>
> > - Section 4, middle of 3rd para:
> >
> > Editorial suggestions for clarity:
> >
> > OLD
> >             For those LSP that are larger than component link
> >     capacity, their capacity are not integer multiples of convenient
> >     capacity increments such as 10Gb/s.
> > NEW
> >             For those LSPs that are larger than a component link
> >    capacity, the LSP capacities need not be (and often are not)
> >    integer multiples of convenient capacity increments such as 10Gb/s.
>
> Good suggestion.  GenArt review suggested adding "generally" making
> the statement read "their capacity are generally not integer
> multiples".  Your suggested rewording may be more clear.
>
> Also "10Gb/s" should be "10 Gb/s".
>
> > In particular, "are not" seems wrong, as the "integer multiples"
> > case is possible, so I changed "are not" to "need not be (and often
> > are not)" in the suggested new text.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
>
> Thanks for the review and for pointing out lack of clarity due to
> underlying assumptions about the use of RFC 4206 (and perhaps use of
> RFC 4201 as well for large MPLS LSP over MPLS-TP).
>
> Sometimes it is too easy to forget that not all readers are going to
> be as steeped in MPLS "as deployed today" details as a relatively
> small number of long time MPLS participants are.
>
> Adding a few paragraphs to the introduction and a few concluding
> paragraphs may significantly improve clarity for people who have not
> been following MPLS closely for a decade or more without requiring
> them to read the references and figure out usage details themselves.
>
> Please let me know how you feel about the suggested additions to the
> document.
>
> Curtis


From touch@isi.edu  Tue Jan 21 17:05:26 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7021A0266; Tue, 21 Jan 2014 17:05:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yFUgIdWtgmu1; Tue, 21 Jan 2014 17:05:25 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id ECEDA1A024F; Tue, 21 Jan 2014 17:05:24 -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 s0M14Inb000306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 17:04:18 -0800 (PST)
Message-ID: <52DF1911.8040806@isi.edu>
Date: Tue, 21 Jan 2014 17:04:17 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <CACKN6JGNAm6KWLohzqaM58jy94wYqmtjJTh4Y8Cx2dcRRqJ_xQ@mail.gmail.com> <CAPv4CP_YiOnKNBgh5Qg2AaLwOGfm6j3FidNQD347+QQhv5MfkA@mail.gmail.com> <52D05C75.3050505@joelhalpern.com> <CAPv4CP_33OU-s+8xt9t5voAtiXMS3pw2+67w9=FxpS2cAOmDeg@mail.gmail.com> <AAA47C6B-C06B-4C95-9D7E-4A7BAA40E480@netapp.com>
In-Reply-To: <AAA47C6B-C06B-4C95-9D7E-4A7BAA40E480@netapp.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: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:05:26 -0000

+1

Edward Crabbe is right - the encapsulated protocols ought to take care 
of congestion control when using UDP.

When they do NOT - e.g., when using MPLS to transfer traffic that either 
isn't IP or is IP but isn't congestion controlled, then some other 
mechanism needs to be employed.

It's not enough to assume "someone else, somewhere else" will handle this.

I agree with Lars - this needs to be part of the encapsulation protocol, 
because it's not enforced by MPLS, and not provided by UDP.

Joe

On 1/10/2014 10:23 PM, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-10, at 22:32, Scott Brim <scott.brim@gmail.com> wrote:
>> OK good point - so we invoke the end-to-end argument on MPLS's behalf.
>
> look at it the other way. From the viewpoint of the rest of the net, you are an application using UDP. Such applications need to follow a set of principles we have IETF consensus on (RFC5405).
>
> By encapsulating MPLS in UDP, you are changing the game. That traffic can now appear on any Internet path, and not just inside provisioned networks. Because of that, you need a mechanism to detect if you are causing congestion, and a mechanism to react to it.
>
> And it *is* a requirement on the encapsulator, because from the perspective of the rest of the net, that is the application that generates the UDP traffic.
>
> Lars
>

From touch@isi.edu  Tue Jan 21 17:08:43 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2061B1A02DE; Tue, 21 Jan 2014 17:08:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ycx--PJrQ9dC; Tue, 21 Jan 2014 17:08:37 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 8B2FA1A0266; Tue, 21 Jan 2014 17:08:33 -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 s0M17vXb001507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 17:07:57 -0800 (PST)
Message-ID: <52DF19ED.8010200@isi.edu>
Date: Tue, 21 Jan 2014 17:07:57 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "Eggert, Lars" <lars@netapp.com>,  Stewart Bryant <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com>
In-Reply-To: <52D5568F.2070600@joelhalpern.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:08:43 -0000

On 1/14/2014 7:23 AM, Joel M. Halpern wrote:
> Isn't that basically the problem of the inner traffic sender, not the
> problem of the tunnel that is carrying the traffic?
> Asking tunnel's to solve the problem of applications with undesirable
> behavior seems backwards.

By that argument, apps using TCP shouldn't expect the transport to 
control congestion. They ought to control it at the app layer.

Tunneled MPLS, when encapsulated inside UDP, *is* the "application". UDP 
expects the app to deal with congestion, so it's entirely reasonable for 
UDP to expect the tunneling system to do this.

Joe

>
> Yours,
> Joel
>
> On 1/14/14 10:20 AM, Eggert, Lars wrote:
>> On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
>>> Yes, the inner (real) transport header is the only meaningful place
>>> to apply congestion avoidance.
>>
>> But what if the inner traffic isn't congestion controlled?
>>
>> Lars
>>

From touch@isi.edu  Tue Jan 21 17:11:50 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2C911A033F; Tue, 21 Jan 2014 17:11:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WN6-MZQ7ovip; Tue, 21 Jan 2014 17:11:44 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id BFF271A01BC; Tue, 21 Jan 2014 17:11:44 -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 s0M1BW8I002184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 17:11:32 -0800 (PST)
Message-ID: <52DF1AC4.7080007@isi.edu>
Date: Tue, 21 Jan 2014 17:11:32 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ross Callon <rcallon@juniper.net>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com>
In-Reply-To: <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:11:51 -0000

On 1/16/2014 2:32 PM, Ross Callon wrote:
>>> These tunnels are stateless
>>
>> yep. (But they don't have to be.)
>
> The tunnels strictly speaking do not have to be stateless. However, if you want routers to actually implement them, and you want to scale in both forwarding speed and number of tunnels, then yes they do have to be stateless.

There's clearly a problem though:

	- tunnels must be stateless to be efficiently implemented

	- transport layer tunnels must have congestion control

Saying that the only way we can make tunnels cheap is to make them break 
the Internet isn't a good solution.

Maybe it's time to expect something that's inherently costly to end up 
being expensive?

Joe

From touch@isi.edu  Tue Jan 21 17:13:49 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAA3E1A0381; Tue, 21 Jan 2014 17:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8E3I-ViLnAaJ; Tue, 21 Jan 2014 17:13:48 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 35C781A037F; Tue, 21 Jan 2014 17:13:48 -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 s0M1Cace002661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 17:12:36 -0800 (PST)
Message-ID: <52DF1B04.70802@isi.edu>
Date: Tue, 21 Jan 2014 17:12:36 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Xuxiaohu <xuxiaohu@huawei.com>
Subject: Re: Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE082443DD@NKGEML512-MBS.china.huawei.com> <B4EBCDAD-CD64-41F9-9D5B-D7FE903AC195@netapp.com>
In-Reply-To: <B4EBCDAD-CD64-41F9-9D5B-D7FE903AC195@netapp.com>
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:13:50 -0000

+1

I don't even care if the safety breaker is a little late, e.g., a few
hundreds of packets (as might be needed for efficient implementation).

Joe

On 1/13/2014 1:42 AM, Eggert, Lars wrote:
> Hi,
> 
> On 2014-1-13, at 10:16, Xuxiaohu <xuxiaohu@huawei.com> wrote:
>> No conflict at all. What I meant is: for those clients of MPLS which are not TCP-friendly (case 2&3 as described in Section 3.1.3 of RFC5405), they should never be transported over the unprovisioned path (e.g., the Internet). Insteads, they should only be transported over a provisioned path in a restricted networking environment. As a result, there is no need for the congestion control mechanism for them.
> 
> I agree, but I think we need a safety mechanism when such traffic does end up on the general Internet (because operators may not read the RFC, or there may be configuration errors, etc.)
> 
> Even when running inside a provisioned domain, you probably want some sort of safety net, like a circuit breaker that detects if your tunnel is experiencing/causing severe congestion, and shut it down.
> 
> Lars
> 

From touch@isi.edu  Tue Jan 21 17:15:22 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F611A0284; Tue, 21 Jan 2014 17:15:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.235
X-Spam-Level: 
X-Spam-Status: No, score=-4.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QVcYqZn5PMbU; Tue, 21 Jan 2014 17:15:18 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7D9161A0285; Tue, 21 Jan 2014 17:15:18 -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 s0M1EjNh003052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 21 Jan 2014 17:14:45 -0800 (PST)
Message-ID: <52DF1B85.4020302@isi.edu>
Date: Tue, 21 Jan 2014 17:14:45 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com> <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
In-Reply-To: <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:15:23 -0000

+1 on all points.

I suspect if more people in transport had the time to track this 
protracted discussion, you'd get the same from them too.

Joe

On 1/21/2014 5:22 AM, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
>> You have made your assertions about your desire to uphold the purity
>> of any new UDP applications and adhere to the BCP you wrote.
>>
>> You appear to be very nearly alone in this argument and certainly no
>> one that works with MPLS is siding with you.
>
> the reason we wrote the RFC when I was TSV AD was that we were seeing a whole bunch of questionable uses of UDP over the eyars and we were having the same arguments over and over. That's why we decided to write down the practices we expect users of UDP to follow. This is yet another such questionable use.
>
> (Also, I don't appreciate you turning this into a personal argument.)
>
>> In the end we can put anything we want in the RFC *but* IETF has never
>> truly had the final word on what vendors and operators do in provider
>> networks.
>
> Aka the "take my toys and go home" argument. Heard it many times.
>
>> In this case, regardless of what changes are made to the draft,
>> implementations will offer at least the option for non-RFC behavior by
>> using zero checksums and not using any congestion control.  And
>> providers will make use of it, perhaps exclusively.
>
> And there's nothing wrong with that - the BCP even says that one SHOULD NOT use congestion control for some deployment cases.
>
> But for others, one SHOULD. For those, a mechanism needs to be available, i.e., it needs to be specified and implemented.
>
>> The document might as well reflect reality, despite reality not
>> conforming to your notions of architectural purity.
>
> I'm sorry, but we have certain architectural principles in the Internet that we have IETF consensus on. At least since RFC2914, that includes the need to have congestion control in place.
>
> There are always special deployment scenarios where these principles do not apply, and we typically explain in applicability statements when out specifications can only be safely used under certain conditions. I don't see any such statement in draft-ietf-mpls-in-udp, which to me means it's targeted at general Internet-wide use.
>
>> The best course of action is to put a SHOULD in regarding checksums
>> and put a SHOULD in regarding congestion avoidance.  Even the BCP does
>> not go any further than to say a tunneling protocol SHOULD use
>> congestion control and there were reasons that the word MUST was not
>> acceptable in the BCP.
>
> The SHOULD for congestion control needs to actually describe a mechanism that can be used when needed. It can't be a blanket "you SHOULD use something but we don't tell you what it is"-statement.
>
>> If we are still arguing over two instances of SHOULD vs MUST we have
>> wasted a lot of bandwidth on those two words.
>
> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs to be specified what is to be done. In the case of checksums, that's obvious (calculate it and check it); in the case of congestion control, some actual mechanism needs to be described (e.g., a circuit breaker).
>
>> IMHO The only remaining question is whether the document can go forward
>> with the definition of congestion control for MPLS over UDP left out
>> of scope and for another document if a need arises.
>
> In my opinion, it cannot.
>
>> If this is not acceptable to you (I doubt it is) please indicate what
>> you would like to see in the document and since this is IETF last call
>> where consensus matters and no one individual has veto power, we'll
>> have to see if there is consensus behind your proposed changes.
>
> I would like the document to specify at the very least a circuit breaker mechanism, that stops the tunneled traffic if severe packet loss is detected along the path.
>
> And this isn't about an "individual veto". This is about a document that is at the moment in violation of IETF consensus at least as far back as RFC2914.
>
> Lars
>

From david.black@emc.com  Tue Jan 21 18:23:48 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2EB1A01B8; Tue, 21 Jan 2014 18:23:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.536
X-Spam-Level: 
X-Spam-Status: No, score=-4.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ATFgNqCmJFA7; Tue, 21 Jan 2014 18:23:41 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 22CEC1A0125; Tue, 21 Jan 2014 18:23:40 -0800 (PST)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0M2Ncds032745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Jan 2014 21:23:39 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s0M2Ncds032745
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390357420; bh=ld3otB+/Wd6WJb0sEUuHywKA8jQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=mEcYXLPNH7bppdTK2PMEScDXz8amLb07RwsOPYjb0Ji1z3JnBfbe5wJO/obbkIvci 3MQ77Zd31vqQxsPCciT/zE7nQ0cPALzA9SXp5BPVNsp9pUfIzg5TQRGFhlDD/NKBbh IzKGfxzuAT/QxpGucmyqSKgm/Zb4Dw61LwIF593A=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s0M2Ncds032745
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 21 Jan 2014 18:23:28 -0800
Received: from mxhub40.corp.emc.com (mxhub40.corp.emc.com [128.222.70.107]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0M2NQDq020051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 21 Jan 2014 21:23:26 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub40.corp.emc.com ([128.222.70.107]) with mapi; Tue, 21 Jan 2014 21:23:25 -0500
From: "Black, David" <david.black@emc.com>
To: "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
Date: Tue, 21 Jan 2014 21:23:24 -0500
Subject: RE: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Topic: OPS-Dir review of draft-ietf-mpls-multipath-use-03
Thread-Index: Ac8XDmOoKOxRb7+CTPGOpjJL/hjbZAAChjHA
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F047CFB@MX15A.corp.emc.com>
References: Your message of "Tue, 21 Jan 2014 19:02:33 -0500." <8D3D17ACE214DC429325B2B98F3AE712026F047CC2@MX15A.corp.emc.com> <201401220107.s0M17lAq069282@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401220107.s0M17lAq069282@maildrop2.v6ds.occnc.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-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: public
Cc: "draft-ietf-mpls-multipath-use.all@tools.ietf.org" <draft-ietf-mpls-multipath-use.all@tools.ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 02:23:48 -0000

> I think we are in agreement and I will edit the document to reflect
> your comments shortly.  I think Adrian is AD on this and Loa the
> shepard, so I'll wait for a go-ahead from either of them before
> submiting the edits.

Yes, we're in agreement, and indeed, "sandwich" is a term I coined in my
review - it seemed descriptive of an MPLS-TP label in a stack between
two ELI/EL pairs.

Thanks,
--David

> -----Original Message-----
> From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]
> Sent: Tuesday, January 21, 2014 8:08 PM
> To: Black, David
> Cc: curtis@ipv6.occnc.com; ops-dir@ietf.org; ietf@ietf.org; draft-ietf-mp=
ls-
> multipath-use.all@tools.ietf.org
> Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
>
>
> In message <8D3D17ACE214DC429325B2B98F3AE712026F047CC2@MX15A.corp.emc.com=
>
> "Black, David" writes:
> >
> > Curtis,
> >
> > > Thanks for the review and for pointing out lack of clarity due to
> > > underlying assumptions about the use of RFC 4206 (and perhaps use of
> > > RFC 4201 as well for large MPLS LSP over MPLS-TP).
> > >
> > > Sometimes it is too easy to forget that not all readers are going to
> > > be as steeped in MPLS "as deployed today" details as a relatively
> > > small number of long time MPLS participants are.
> > >
> > > Adding a few paragraphs to the introduction and a few concluding
> > > paragraphs may significantly improve clarity for people who have not
> > > been following MPLS closely for a decade or more without requiring
> > > them to read the references and figure out usage details themselves.
> > >
> > > Please let me know how you feel about the suggested additions to the
> > > document.
> >
> > Most of them look good - details below.  Many thanks for the prompt and
> > comprehensive response.  I have a few more suggestions in what follows
> > - anything that I don't comment on below is fine with me.
>
> Thank you for the quick turnaround on this as well.
>
> > -- Introduction
> >
> > > There is an underlying assumption in the draft that the reader
> > > understands that MPLS-in-MPLS exists today, most commonly but not
> > > exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> > > means to advertise forward adjacencies (FA) where MPLS-in-MPLS at som=
e
> > > level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> > > to make use of the management plane, using CLI or NETCONF or the MPLS
> > > cross connect MIB to program a multiple label MPLS push operation.
> > >
> > > If a very experienced reviewer could miss that, then the introduction
> > > could be improved by better stating assumptions.  It is also the case
> > > that many participants in MPLS, particularly those primarily
> > > interested in MPLS-TP, began participation long after RFC 4206 was
> > > written and would benefit by better stated assumptions in the intro.
> > >
> > > I suggest that the following paragraphs be added to the introduction.
> >
> > The suggested new paragraphs will definitely improve the introduction.
> >
> > -- [A] Summary text in Introduction appears to be wrong.
> >
> > > > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > > > exception appears to concern the reverse, and Section 4 on carrying=
 MPLS
> > > > over MPLS-TP allows for MPLS LSPs that exceed component link capaci=
ty.
> > > > Was the exception intended to be for an MPLS-TP LSP that exceeds th=
e
> > > > capacity of any single component link?
> >
> > [... snip ...]
> >
> > > To answer your question directly: the exception is a very large MPLS
> > > LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> > > multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> > > this is occurring.
> >
> > It looks like  my confusion stemmed from the original text only
> > discussing only what won't work and referencing a section that
> > concerns a different encapsulation order than the one that causes
> > the problem.  Including the "MAY NOT" -> "SHOULD NOT" change, I suggest=
:
> >
> > OLD
> >    When an MPLS LSP
> >    exceeds the capacity of any single component link it MAY be carried
> >    by a network using multipath techniques, but MAY NOT be carried by a
> >    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
> >    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
> >    fate sharing constraints and MPLS-TP LM OAM packet ordering
> >    constraints (see Section 3.1).
> > NEW
> >    When an MPLS LSP
> >    exceeds the capacity of any single component link it MAY be carried
> >    by a network using multipath techniques, but SHOULD NOT be carried b=
y a
> >    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
> >    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
> >    fate sharing constraints and MPLS-TP LM OAM packet ordering
> >    constraints (see Section 3.1).  Instead, multiple MPLS-TP LSPs SHOUL=
D
> >    be used to carry a large MPLS LSP (see Section 4).
>
> OK.  Good addition.
>
> > -- [B] Section 3.2 needs a summary.
> >
> > The proposed summary looks good, and helps with [C], but the phrase
> > "access and edge" needs qualification in the following sentence:
> >
> >    However access and edge is the least likely to support
> >    RFC 6790 in the near term.
> >
> > "access and edge" what? e.g., areas of the network? LSRs?
>
> Oh.  Good point.
>
> Core, edge, aggregation, and access are terms commonly used for the
> tiers in provider networks.  Core is central, high traffic.  Access is
> furthest out with lower traffic (think of subscriber connections for
> consumer Internet).
>
> Perhaps I can just change the sentence to:
>
>   However equipment furthest from a provider's network core is the
>   least likely to support RFC 6790 in the near term.
>
> I think we all know "core" at this point so furthest from core might
> be easier to understand.
>
> > -- [C] Entropy label "sandwich" seems peculiar and at least needs an
> >  explanation.
>
> That was your term.  I didn't propose adding Entropy label "sandwich"
> to the text.  I think this is just an excerpt from your prior email as
> a marker in following up on it.  Please correct me if I am wrong.
>
> > > The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> > > paragraph.
> > >
> > >    Alternately, the need for requirement MP#1 can be eliminated if
> > >    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
> > >    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
> > >    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
> > >    in a deployment support Entropy Label, which may render it
> > >    impractical in many deployments.
> > >
> > > Please not the "Alternately" at the beginning and "impractical in man=
y
> > > deployments" at the end.
>
> That should have said "Please note".
>
> > > The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> > > above that but assumes knowledge of RFC 6790.  I think the following
> > > change within this paragraph would clear things up:
> >
> > That change is helpful, but my "sandwich" concern was actually raised
> > by text two paragraphs further down:
> >
> >    MPLS-TP LSPs can be carried as client LSPs within an MPLS server LSP
> >    if an Entropy Label Indicator (ELI) and Entropy Label (EL) is pushed
> >    below the server layer LSP label(s) in the label stack, just above
> >    the MPLS-TP LSP label entry [RFC6790].
> >
> > Read after the "Alternately" paragraph, this text appeared to suggest
> > a "sandwich" that would have an ELI/EL pair both above and below the
> > MPLS-TP label.  That was clearly not intended, so I suggest inserting
> > "When Entropy Label Indicators (ELIs) and Entropy Labels (ELs) are not
> > applied by MPLS-TP ingresses," before the start of the first sentence
> > above, so that the result is:
> >
> >    When Entropy Label Indicator (ELIs) and Entropy Labels (ELs) are
> >    not applied by MPLS-TP ingresses, MPLS-TP LSPs can be carried as
> >    client LSPs within an MPLS server LSP if an ELI and EL are pushed
> >    below the server layer LSP label(s) in the label stack, just above
> >    the MPLS-TP LSP label entry [RFC6790].
>
> OK.  I will make that replacement.
>
> > -- [D] Discussion of multipath impacts on MPLS OAM
> >
> > > > Section 3.2 discusses OAM, and contains this important
> > > > requirement for OAM traffic:
> > > >
> > > >    An Entropy Label must be used to insure that all of the
> > > >    MPLS-TP payload and OAM traffic are carried on the same componen=
t,
> > > >    except during very infrequent transitions due to load balancing.
> > > >
> > > > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > > > Section 4; that should be added.
> > >
> > > There is no impact on MPLS OAM traffic.  There are three cases to
> > > consider.
> > >
> > >   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
> > >      one link.  MPLS OAM is unaffected and need not use multipath
> > >      support in LSP Ping.
> > >
> > >   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
> > >      LSP is carried over one link thanks to the fixed EL value.
> > >      MPLS-TP OAM is unaffected.
> > >
> > >   3.  Where MPLS is carried over MPLS (an existing case) or over
> > >       multiple MPLS-TP, the multipath support in LSP Ping (as
> > >       imperfect as it may already be) is used and LSP Ping (RFC 4379)
> > >       operation is unaffected.
> > >
> > > If needed something can be added to state the above (maybe with less
> > > informal wording).  What is obvious to some people may not be obvious
> > > to everyone.  Briefly stating the almost obvious is usually not a bad
> > > thing.
> >
> > Points 1-3 are useful explanation as complement to the Entropy label
> > requirement to correctly handle OAM traffic for the other encapsulation=
.
> >
> > I like your suggestion to add this text as part of a new concluding
> > Section 5, and the rest of the proposed conclusion section text looks
> > good.
> >
> > Thanks,
> > --David
>
> Thanks again.
>
> I think we are in agreement and I will edit the document to reflect
> your comments shortly.  I think Adrian is AD on this and Loa the
> shepard, so I'll wait for a go-ahead from either of them before
> submiting the edits.
>
> Curtis
>
>
> > > -----Original Message-----
> > > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]
> > > Sent: Tuesday, January 21, 2014 2:23 PM
> > > To: Black, David
> > > Cc: ops-dir@ietf.org; ietf@ietf.org; draft-ietf-mpls-multipath-
> > > use.all@tools.ietf.org
> > > Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
> > >
> > >
> > > In message <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc=
.com>
> > > "Black, David" writes:
> > > >
> > > > I have reviewed this document as part of the operations directorate=
's
> > > > ongoing effort to review all IETF documents being processed by the
> > > > IESG.  These comments were written primarily for the benefit of the
> > > > operations area directors.  Document editors and WG chairs should t=
reat
> > > > these comments just like any other last call comments.
> > > >
> > > > Summary:
> > > > This draft is on the right track but has open issues, described in =
the
> > > review.
> > > >
> > > > I apologize for this review showing up a couple of days after the e=
nd of
> > > > IETF Last Call.
> > > >
> > > > This draft discusses considerations for what are effectively MPLS-i=
n-
> MPLS
> > > > tunnels for multipathing - an LSP carries another LSP, with the inn=
er
> > > > (client) LSPs being distributed across multiple outer (server) LSPs=
 that
> > > > use different paths.  This draft is motivated by considerations spe=
cific
> > > > to MPLS-TP that complicate multipathing when one of the two MPLS
> instances
> > > > is MPLS-TP.
> > >
> > > Skipping to the discussion quite a ways down, there seems to be some
> > > confusion about what is being proposed here.  While MPLS-in-MPLS is
> > > being used, no new form of MPLS-in-MPLS is being proposed.
> > >
> > > There is an underlying assumption in the draft that the reader
> > > understands that MPLS-in-MPLS exists today, most commonly but not
> > > exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> > > means to advertise forward adjacencies (FA) where MPLS-in-MPLS at som=
e
> > > level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> > > to make use of the management plane, using CLI or NETCONF or the MPLS
> > > cross connect MIB to program a multiple label MPLS push operation.
> > >
> > > If a very experienced reviewer could miss that, then the introduction
> > > could be improved by better stating assumptions.  It is also the case
> > > that many participants in MPLS, particularly those primarily
> > > interested in MPLS-TP, began participation long after RFC 4206 was
> > > written and would benefit by better stated assumptions in the intro.
> > >
> > > I suggest that the following paragraphs be added to the introduction.
> > >
> > >    MPLS LSPs today are able to function as a server layer and carry
> > >    client MPLS LSPs.  When control plane signaling is used, forwardin=
g
> > >    adjacency (FA) advertisements are used to inform the set of LSR of
> > >    Packet Switching Capable (PSC) LSP within the MPLS topology
> > >    [RFC4206].  Client MPLS LSP at a higher layer (lower PSC number)
> > >    may signal their intention to use PSC LSP as hops in the RSVP-TE
> > >    Explicit Route Object (ERO).  LSR with no explicit support for RFC
> > >    4206 see the PSC LSP as ordinary links and therefore use them.
> > >
> > >    An MPLS LSP that has been set up using RSVP-TE appears to its
> > >    ingress LSR as a viable IP next hop to a distant LSR.  If LDP is
> > >    used and bidirectional RSVP-TE LSP connectivity is available, then
> > >    LDP signaling can be set up among the RSVP-TE LSP endpoints and LD=
P
> > >    can make use of the RSVP-TE LSP as an LDP hop.  This is another
> > >    form of existing MPLS-in-MPLS use.
> > >
> > >    MPLS LSPs may also make use of hierarchy that is configured throug=
h
> > >    the management plane rather than signaled using RSVP-TE.
> > >
> > >    These existing forms of MPLS-in-MPLS may traverse multipath hops
> > >    such as Ethernet LAG [IEEE802.1AX] or MPLS Link Bundling [RFC4201]=
.
> > >    MPLS-TP brings with it a new set of requirements not considered in
> > >    past deployments of the various forms of MPLS-in-MPLS where
> > >    multipath was in use.  This document merely discusses use of
> > >    existing forwarding and protocol mechanisms that can support the
> > >    case where either the client layer LSPs or the server layer LSPs
> > >    are MPLS-TP and where multipath is used.
> > >
> > > If there are no objections I will add these paragraphs.
> > >
> > > Now on to the specific comments.
> > >
> > > > I consider the following to be open issues that need attention (eac=
h
> > > > letter is used to tag the issue in the text that follows - [B] occu=
rs
> > > > multiple times, as there are multiple aspect to that issue):
> > > >
> > > > [A] Summary text in Introduction appears to be wrong.
> > > > [B] Section 3.2 needs a summary.
> > > > [C] Entropy label "sandwich" seems peculiar and at least needs an
> explanation.
> > > > [D] Discussion of multipath impacts on MPLS OAM should be added to
> Section
> > > 4.
> > > >
> > > > --- Comments on draft text
> > > >
> > > > [A] Section 1 (Introduction) 2nd paragraph:
> > > >
> > > >    RFC 5654 requirement 33 requires the capability to carry a clien=
t
> > > >    MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC56=
54].
> > > >    This is possible in all cases with one exception.  When an MPLS =
LSP
> > > >    exceeds the capacity of any single component link it MAY be carr=
ied
> > > >    by a network using multipath techniques, but MAY NOT be carried =
by a
> > > >    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitati=
on
> > > >    imposed by MPLS-TP Operations, Administration, and Maintenance (=
OAM)
> > > >    fate sharing constraints and MPLS-TP LM OAM packet ordering
> > > >    constraints (see Section 3.1).
> > > >
> > > > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > > > exception appears to concern the reverse, and Section 4 on carrying=
 MPLS
> > > > over MPLS-TP allows for MPLS LSPs that exceed component link capaci=
ty.
> > > > Was the exception intended to be for an MPLS-TP LSP that exceeds th=
e
> > > > capacity of any single component link?
> > >
> > > There is no problem today with MPLS LSP carried by MPLS-TP LSP except
> > > the existing case where MPLS LSP capacity is too big.  For example, a
> > > 500 Gb/s LSP is possible today carried over N x 100 Gb/s or N x 10
> > > Gb/s multipath links but could not be carried over a single MPLS-TP
> > > LSP which would be limited to a single 100 Gb/s or 10 Gb/s link.  So
> > > the exception is where the MPLS LSP is too big to fit in any possible
> > > single MPLS-TP LSP.
> > >
> > > To answer your question directly: the exception is a very large MPLS
> > > LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> > > multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> > > this is occurring.
> > >
> > > > Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's
> equivalent
> > > > to "MAY OR MAY NOT").  I think "cannot" was intended here, but "MUS=
T
> NOT"
> > > > is another possibility.
> > >
> > > Good point.  I suggest we replace the MAY NOT with SHOULD NOT.  Many
> > > people would insist that it should be MUST NOT, but in reality
> > > networks SHOULD NOT be congested but sometimes they are.
> > >
> > > > [B] Section 3.2 contains a lot of useful details, but it could real=
ly
> use
> > > > a summary at the end on the options and recommendations for meeting=
 the
> > > > four requirements (this summary could be a new Section 3.3).  It's =
a bit
> > > > difficult to discern what's going on, as I had to read this section=
 more
> > > > than once in order to discern the following:
> > >
> > > OK.  A Summary paragraph can be added.  See below.  Perhaps conclusio=
n
> > > section can be added.  See far below.
> > >
> > > > [C] In Section 3.2, use of an MPLS entropy label to meet requiremen=
t
> MP#1
> > > > requires that it be "below the MPLS-TP label" whereas, to meet
> requirement
> > > > MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LS=
P
> label".
> > > > This combination appears to suggest "sandwiching" the MPLS-TP label
> between
> > > > two entropy labels that effectively carry the same information (alb=
eit,
> > > > applied and removed at different places in the network) - was that
> intended?
> > > > This is important, as there seems to be no reasonable alternative
> > > > to the entropy label for meeting requirement MP#2, and the draft's
> > > > alternative to the entropy label for meeting requirement MP#1 is "s=
ome
> form
> > > > of configuration" - the entropy label would seem to be preferred to=
 that
> > > > based on my reading of this draft and the comment in RFC 5706 secti=
on
> 2.2
> > > > that "Anything that can be configured can be misconfigured."
> > >
> > > The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> > > paragraph.
> > >
> > >    Alternately, the need for requirement MP#1 can be eliminated if
> > >    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
> > >    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
> > >    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
> > >    in a deployment support Entropy Label, which may render it
> > >    impractical in many deployments.
> > >
> > > Please not the "Alternately" at the beginning and "impractical in man=
y
> > > deployments" at the end.
> > >
> > > The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> > > above that but assumes knowledge of RFC 6790.  I think the following
> > > change within this paragraph would clear things up:
> > >
> > >  OLD
> > >
> > >    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
> > >    and Entropy Label (EL) are added to the label stack [RFC6790].  Fo=
r
> > >    those client LSP that are MPLS-TP LSP, a single EL value must be
> > >    chosen.  For those client LSP that are MPLS LSP, per packet entrop=
y
> > >    below the top label must, for practical reasons, be used to
> > >    determine the entropy label value.
> > >
> > >  NEW
> > >
> > >    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
> > >    and Entropy Label (EL) are added to the label stack by the midpoin=
t
> > >    LSR for the client MPLS-TP LSP, at the ingress of the MPLS LSP
> > >    [RFC6790].  For those client LSP that are MPLS-TP LSP, a single EL
> > >    value must be chosen.  For those client LSP that are MPLS LSP, per
> > >    packet entropy below the top label must, for practical reasons, be
> > >    used to determine the entropy label value.  The resulting label
> > >    stack contains the server MPLS LSP label, ELI, EL and the client
> > >    LSP label.
> > >
> > > The above rewording is simply more explicit about the label stack
> > > order and which LSR puts the ELI and EL in the label stack.
> > >
> > > > [B] A summary of requirements for implementation and deployment at =
the
> end
> > > > of Section 3.2 would have made this much more obvious.  That should=
 be
> > > > provided in addition to addressing the above question about duplica=
te
> use
> > > > of the MPLS entropy label.
> > >
> > > The following summary can be added to the end of Section 3.2:
> > >
> > >    Two methods of adding an Entropy Label are described above.  The
> > >    MPLS-TP ingress must have a means to determine which links can
> > >    support MPLS-TP in selecting a path (MP#4).  Administrative
> > >    attributes can satisfy that requirement.  If the MPLS-TP LSR is
> > >    capable of adding ELI/EL to the label stack, this method is
> > >    preferred.  However access and edge is the least likely to support
> > >    RFC 6790 in the near term.  For portions of the topology where an
> > >    MPLS-TP is carried within a server layer MPLS LSP the ingress of
> > >    the server layer MPLS LSP can add ELI/EL using a fixed EL value pe=
r
> > >    client LSP, except those known not to require MPLS-TP treatment.
> > >    There are numerous ways to determine which client LSP are MPLS-TP
> > >    LSP and which are not.  While this determination is out of scope
> > >    and will vary among deployments, configuration or the presence of
> > >    specific attribute affinities in RSVP-TE signaling are among the
> > >    likely means to do so.
> > >
> > > If there are no objections I will add the above paragraph.
> > >
> > > > --- Relevant Q&A based on RFC 5706 Appendix A
> > > >
> > > > I'm omitting management concerns, as both MPLS and MPLS-TP have
> extensive
> > > > management infrastructure, and this draft's notion of stacking LSPs=
 so
> > > > that one instance of MPLS (or MPLS-TP) can be a server to (i.e., ca=
rry)
> > > > another is not novel to this draft.
> > > >
> > > > A.1.1.  Has deployment been discussed?
> > > >
> > > > [B] Yes, although Section 3.2 is weak on deployment requirements (s=
ome
> of
> > > > which are implementation requirements) and could use a summary.
> > >
> > > The use of RFC 4206 is assumed throughout the discussion of signaling
> > > in section 3.2.  This assumption is made more clear by suggested
> > > additions to the introduction.
> > >
> > > > A.1.2.  Has installation and initial setup been discussed?
> > > >
> > > > No, although because this draft reuses existing functionality in
> different
> > > > configurations, this really reduces to the A.1.9 configuration ques=
tion
> > > > below.  In practice, quite a bit of operator knowledge and insight =
is
> > > > required to get initial setup right, e.g., as traffic engineering L=
SPs
> to
> > > > avoid congestion problems (needed to meet requirement MP#3) require=
s
> > > > significant knowledge of network structure and expected traffic flo=
ws.
> > > > This should be obvious to anyone who works w/MPLS, but it's probabl=
y
> > > > worth stating for completeness.
> > >
> > > FA advertisements defined in RFC 4206 make it possible for ingress to
> > > signal viable paths.  Either the use of Ethernet Link Aggregation or
> > > MPLS Link bundling using the all-ones component link (RFC 4201) allow=
s
> > > the total capacity of a multipath to be advertised.  Meeting the
> > > requirement to balance traffic over the component links in a multipat=
h
> > > (MP#3) is then a local matter and requires no further signaling
> > > extensions.
> > >
> > > > A.1.6.  Have suggestions for verifying correct operation been discu=
ssed?
> > > >
> > > > Yes and no.  Section 3.2 discusses OAM, and contains this important
> > > > requirement for OAM traffic:
> > > >
> > > >    An Entropy Label must be used to insure that all of the
> > > >    MPLS-TP payload and OAM traffic are carried on the same componen=
t,
> > > >    except during very infrequent transitions due to load balancing.
> > > >
> > > > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > > > Section 4; that should be added.
> > >
> > > There is no impact on MPLS OAM traffic.  There are three cases to
> > > consider.
> > >
> > >   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
> > >      one link.  MPLS OAM is unaffected and need not use multipath
> > >      support in LSP Ping.
> > >
> > >   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
> > >      LSP is carried over one link thanks to the fixed EL value.
> > >      MPLS-TP OAM is unaffected.
> > >
> > >   3.  Where MPLS is carried over MPLS (an existing case) or over
> > >       multiple MPLS-TP, the multipath support in LSP Ping (as
> > >       imperfect as it may already be) is used and LSP Ping (RFC 4379)
> > >       operation is unaffected.
> > >
> > > If needed something can be added to state the above (maybe with less
> > > informal wording).  What is obvious to some people may not be obvious
> > > to everyone.  Briefly stating the almost obvious is usually not a bad
> > > thing.  Please tell me if a small subsection on "Imopact on MPLS and
> > > MPLS-TP OAM" is needed.
> > >
> > > Note that the limitations of LSP Ping are currently being discussed i=
n
> > > the MPLS WG in the context of extensions to LSP Ping to better suppor=
t
> > > Entropy Label.  A few limitations not related to EL may get fixed in
> > > the process.
> > >
> > > > A.1.9.  Is configuration discussed?
> > > >
> > > > [B] Not much. Configuration is required to meet requirements MP#3 a=
nd
> MP#4,
> > > > and is one of the options for MP#1.  A summary of what has to be
> configured
> > > > as part of the summary at the end of Section 3.2 would be a good id=
ea.
> > >
> > > Perhaps a worked example appendix could be added but I don't think
> > > this is common and may not be necessary with some of the
> > > clarifications suggested so far.
> > >
> > > > A.2.* [skipped, see above]
> > > >
> > > > A.3 Documentation
> > > >
> > > > There's quite a bit of operational material contained in this draft=
; a
> > > > separate section on operations and management considerations would =
not
> > > > be appropriate.
> > > >
> > > > There is a useful implementation status section which appears to im=
ply
> > > > that MPLS-TP over MPLS is not currently deployable due to absence o=
f
> > > > entropy label support, and because deployed MPLS equipment does not
> > > > generally support multipathing.  Nonetheless, data center experienc=
e
> > > > indicates significant value and widespread use of multipathing base=
d
> > > > on link aggregation and ECMP; corresponding benefits can be expecte=
d
> > > > for use of multipathing in the Internet beyond data centers.
> > >
> > > If you would like I can add a conclusion section as Section 5 with
> > > these paragraphs:
> > >
> > >    MPLS equipment deployed in the core currently supports multipath.
> > >    For large service providers, core LSR must support some form of
> > >    multipath to be deployable.  Deployed MPLS access and edge
> > >    equipment is often oblivious to the use of multipath in the core.
> > >    It is expected that at least first generation MPLS-TP equipment
> > >    will be oblivious to the use of multipath in the core.  This first
> > >    generation MPLS-TP equipment is deployable in a core using
> > >    multipath, with no adverse impact to RSVP-TE signaling, if the edg=
e
> > >    equipment can support administrative attributes (RFC 3209) and the
> > >    core equipment can support ELI/EL and put a per-LSP fixed EL value
> > >    on any LSP that indicates a particular attribute affinity or can
> > >    identify client MPLS-TP LSP through some other means.
> > >
> > >    There are no issues carrying MPLS over MPLS-TP, except when the
> > >    MPLS LSP is too big to be carried by a single MPLS-TP LSP.  Most
> > >    MPLS core equipment and some edge equipment can configure an MPLS
> > >    Link Bundle [RFC4201] over multiple component links where the
> > >    component links are themselves MPLS LSP.  This existing capability
> > >    can be used to carry large MPLS LSP and overcome the limited
> > >    capacity of any single server layer MPLS-TP LSP.
> > >
> > > If this conclusion section is added, then the three bullets above
> > > regarding impact on OAM can be put there.  The three bullets can be
> > > added as follows:
> > >
> > >    MPLS OAM and MPLS-TP OAM are unaffected in the following cases
> > >    proposed in this document:
> > >
> > >      1. Where MPLS is carried over a single MPLS-TP all traffic flows
> > >         on one link.  MPLS OAM is unaffected and need not use
> > >         multipath support in LSP Ping.
> > >
> > >      2. Where MPLS-TP is carried over MPLS, all traffic for that
> > >         MPLS-TP LSP is carried over one link thanks to the fixed EL
> > >         value.  MPLS-TP OAM is unaffected.
> > >
> > >      3.  Where MPLS is carried over MPLS (an existing case) or over
> > >          multiple MPLS-TP, the multipath support in LSP Ping is used
> > >          and LSP Ping (RFC 4379) operation is unaffected.
> > >
> > > I think adding the above as a conclusion section as Section 5 would
> > > improve clarity and therefore is worth doing.
> > >
> > > > --- Editorial comments/nits:
> > > >
> > > > - Section 3.1, after RFC 5960 quotes:
> > > >
> > > >    [RFC5960] paragraph 3 requires that packets within a specific or=
dered
> > > >
> > > > Insert "Section 3.1.1.", before "paragraph 3" and likewise for
> "paragraph 6"
> > > > later in the same paragraph in the draft.
> > >
> > > GenArt review caught this.  Done.
> > >
> > > > - Section 3.2, requirement MP#3:
> > > >
> > > >    MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not=
 be
> > > >
> > > > "insure" -> "ensure" or "assure".  Surely this draft does not envis=
ion
> > > > operators taking out insurance policies on MPLS TP LSP behavior ;-)=
.
> > >
> > > Good catch.  I think "ensure" is the right word.
> > >
> > > > - Section 3.2, last paragraph on p.8:
> > > >
> > > >    An MPLS-TP LSP may not traverse multipath links on the path wher=
e
> > > >    MPLS-TP forwarding requirements cannot be met.
> > > >
> > > > "may not" is meaningless - I believe "MUST NOT" was intended here.
> > >
> > > I suggested SHOULD NOT above.
> > >
> > > > - Section 4, middle of 3rd para:
> > > >
> > > > Editorial suggestions for clarity:
> > > >
> > > > OLD
> > > >             For those LSP that are larger than component link
> > > >     capacity, their capacity are not integer multiples of convenien=
t
> > > >     capacity increments such as 10Gb/s.
> > > > NEW
> > > >             For those LSPs that are larger than a component link
> > > >    capacity, the LSP capacities need not be (and often are not)
> > > >    integer multiples of convenient capacity increments such as 10Gb=
/s.
> > >
> > > Good suggestion.  GenArt review suggested adding "generally" making
> > > the statement read "their capacity are generally not integer
> > > multiples".  Your suggested rewording may be more clear.
> > >
> > > Also "10Gb/s" should be "10 Gb/s".
> > >
> > > > In particular, "are not" seems wrong, as the "integer multiples"
> > > > case is possible, so I changed "are not" to "need not be (and often
> > > > are not)" in the suggested new text.
> > > >
> > > > Thanks,
> > > > --David
> > > > ----------------------------------------------------
> > > > David L. Black, Distinguished Engineer
> > > > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > > > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > > > david.black@emc.com        Mobile: +1 (978) 394-7754
> > > > ----------------------------------------------------
> > >
> > > Thanks for the review and for pointing out lack of clarity due to
> > > underlying assumptions about the use of RFC 4206 (and perhaps use of
> > > RFC 4201 as well for large MPLS LSP over MPLS-TP).
> > >
> > > Sometimes it is too easy to forget that not all readers are going to
> > > be as steeped in MPLS "as deployed today" details as a relatively
> > > small number of long time MPLS participants are.
> > >
> > > Adding a few paragraphs to the introduction and a few concluding
> > > paragraphs may significantly improve clarity for people who have not
> > > been following MPLS closely for a decade or more without requiring
> > > them to read the references and figure out usage details themselves.
> > >
> > > Please let me know how you feel about the suggested additions to the
> > > document.
> > >
> > > Curtis
>


From rcallon@juniper.net  Tue Jan 21 18:40:12 2014
Return-Path: <rcallon@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2859A1A025F; Tue, 21 Jan 2014 18:40:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n8sAdxCtsrrY; Tue, 21 Jan 2014 18:40:09 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe002.messaging.microsoft.com [213.199.154.205]) by ietfa.amsl.com (Postfix) with ESMTP id 3746A1A0152; Tue, 21 Jan 2014 18:40:09 -0800 (PST)
Received: from mail52-am1-R.bigfish.com (10.3.201.239) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.22; Wed, 22 Jan 2014 02:40:08 +0000
Received: from mail52-am1 (localhost [127.0.0.1])	by mail52-am1-R.bigfish.com (Postfix) with ESMTP id 3774AE0144; Wed, 22 Jan 2014 02:40:08 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z579ehzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1de098h1033IL1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach9a9j1155h)
Received-SPF: pass (mail52-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rcallon@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(13464003)(24454002)(377454003)(51704005)(479174003)(19580405001)(86362001)(83322001)(51856001)(50986001)(33646001)(74876001)(66066001)(2656002)(74706001)(4396001)(80022001)(47736001)(47976001)(83072002)(65816001)(49866001)(46102001)(54356001)(53806001)(19580395003)(74316001)(81686001)(92566001)(93136001)(90146001)(2171001)(93516002)(74366001)(80976001)(76482001)(87936001)(74662001)(56816005)(85852003)(74502001)(85306002)(47446002)(81342001)(81542001)(81816001)(79102001)(63696002)(87266001)(31966008)(76576001)(59766001)(77982001)(54316002)(56776001)(76796001)(76786001)(69226001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB635; H:CO2PR05MB636.namprd05.prod.outlook.com; CLIP:66.129.241.13; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail52-am1 (localhost.localdomain [127.0.0.1]) by mail52-am1 (MessageSwitch) id 139035840584948_19187; Wed, 22 Jan 2014 02:40:05 +0000 (UTC)
Received: from AM1EHSMHS017.bigfish.com (unknown [10.3.201.248])	by mail52-am1.bigfish.com (Postfix) with ESMTP id 106AA46004C;	Wed, 22 Jan 2014 02:40:05 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS017.bigfish.com (10.3.207.155) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 22 Jan 2014 02:40:04 +0000
Received: from CO2PR05MB635.namprd05.prod.outlook.com (10.141.199.22) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.395.1; Wed, 22 Jan 2014 02:40:02 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) by CO2PR05MB635.namprd05.prod.outlook.com (10.141.199.22) with Microsoft SMTP Server (TLS) id 15.0.851.11; Wed, 22 Jan 2014 02:40:00 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) by CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) with mapi id 15.00.0851.011; Wed, 22 Jan 2014 02:40:00 +0000
From: Ross Callon <rcallon@juniper.net>
To: Joe Touch <touch@isi.edu>, "Eggert, Lars" <lars@netapp.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPB81jtn8uxkZO2EiBZeT7DEf4ppp6pziAgAK2KYCAAFQ7gIAAckaAgAAJRICAAAZDAIAD31WAgABWkACAAHXPgIAAN0wAgAEJtoCAACSWAIAAC2+AgAAH1ACAABCvgIAAAQmAgAABlACAAz/IAIAAA6wAgABUpZCACArNAIAAFXLw
Date: Wed, 22 Jan 2014 02:40:00 +0000
Message-ID: <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com> <52DF1AC4.7080007@isi.edu>
In-Reply-To: <52DF1AC4.7080007@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.13]
x-forefront-prvs: 00997889E7
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 02:40:12 -0000

If the upper layers (the thing that runs over the tunnel) involves applicat=
ions over TCP over IP, or if it is otherwise responding to congestion in th=
e same way that we expect anything running over IP to respond to congestion=
, then we don't want the tunnel to also independently try to respond to con=
gestion (two independent cooks cooking the same meal does not necessarily l=
ead to success).=20

If the upper layer does not respond to congestion, then perhaps it shouldn'=
t be running over the open Internet (with or without a tunnel), unless the =
*total* bandwidth that could be used is inherently quite low. On the other =
hand, it might want to run within a data center or internally to a service =
provider network with appropriate provisioning.=20

Ross

-----Original Message-----
From: Joe Touch [mailto:touch@isi.edu]=20
Sent: Tuesday, January 21, 2014 8:12 PM
To: Ross Callon; Eggert, Lars
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard



On 1/16/2014 2:32 PM, Ross Callon wrote:
>>> These tunnels are stateless
>>
>> yep. (But they don't have to be.)
>
> The tunnels strictly speaking do not have to be stateless. However, if yo=
u want routers to actually implement them, and you want to scale in both fo=
rwarding speed and number of tunnels, then yes they do have to be stateless=
.

There's clearly a problem though:

	- tunnels must be stateless to be efficiently implemented

	- transport layer tunnels must have congestion control

Saying that the only way we can make tunnels cheap is to make them break=20
the Internet isn't a good solution.

Maybe it's time to expect something that's inherently costly to end up=20
being expensive?

Joe




From scott.brim@gmail.com  Tue Jan 21 19:51:03 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 520501A01C8; Tue, 21 Jan 2014 19:51:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6alxzttj4Fru; Tue, 21 Jan 2014 19:51:01 -0800 (PST)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id C10EE1A018E; Tue, 21 Jan 2014 19:51:01 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id j17so4325404oag.14 for <multiple recipients>; Tue, 21 Jan 2014 19:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=1Y157LQ/7jrE6Mfvy16cUTetDh9KfSGvX1/rbqvqyAg=; b=hFtvXo3fWctR2MrIx3VFkGfPrhpwNH0lrE71ZdKt7EfvhV1vwHz37hx3Owq+UsDMrZ 60+zSoPwIm3K0AZ+ESY6taDN0T0R/FRAgVzmKLGuPQH8GgwAShOA5cGVowS+lvT+eKTJ KSKfQMLZX3LOZliJlaVLjzEU+4PEbg0mWV0rrz7rcB/SF7ajLSggQjhaSgKvCUDw/7GA Xkciy3df25XaL2ciVBz5MdMu8jhODoTOrZ9hAP+MvRu9cUGBnDqUf+FofWDluXrOlmBO HyyqmgAOdyULIXHzw+NVkHlKV5rr44yF+EDJUMPvGwLoNo29HExMYMBnQNpD4T7dGSfJ i0FA==
X-Received: by 10.60.98.40 with SMTP id ef8mr24179552oeb.13.1390362661415; Tue, 21 Jan 2014 19:51:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 19:50:40 -0800 (PST)
In-Reply-To: <52DF19ED.8010200@isi.edu>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <52DF19ED.8010200@isi.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 21 Jan 2014 22:50:40 -0500
Message-ID: <CAPv4CP_OQ57_tHzVB+7cQ=QpMPyD9Q9zLJW0MrGDioiCADF9Rg@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 03:51:03 -0000

On Tue, Jan 21, 2014 at 8:07 PM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 1/14/2014 7:23 AM, Joel M. Halpern wrote:
>>
>> Isn't that basically the problem of the inner traffic sender, not the
>> problem of the tunnel that is carrying the traffic?
>> Asking tunnel's to solve the problem of applications with undesirable
>> behavior seems backwards.
>
>
> By that argument, apps using TCP shouldn't expect the transport to control
> congestion. They ought to control it at the app layer.
>
> Tunneled MPLS, when encapsulated inside UDP, *is* the "application". UDP
> expects the app to deal with congestion, so it's entirely reasonable for UDP
> to expect the tunneling system to do this.

Joe, I believe you are confusing a protocol with an architectural
function. It's a UDP encapsulation, but that encapsulation has nothing
to do with transport, and what runs over it is not an "application".
It may be a client layer (with the encapsulation a service layer), but
that's a relative relationship, not an absolution one about stack
position.  This instance of UDP is way below transport, is just in
fact a bit of lubrication for the packet, and considered
_functionally_ has nothing to do with congestion control. The only
reason for using UDP encapsulation is to get through middleboxes. If
something else worked better for that, they would use it.

From scott.brim@gmail.com  Tue Jan 21 20:03:43 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8099E1A028A; Tue, 21 Jan 2014 20:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cxa1YYN7yUEU; Tue, 21 Jan 2014 20:03:42 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id D09771A0270; Tue, 21 Jan 2014 20:03:41 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id vb8so9930383obc.3 for <multiple recipients>; Tue, 21 Jan 2014 20:03:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=YX9WgGK60iZ/lSVVH8SYOGDDc9XjbDqHnWBilhfrS08=; b=K2GTIot584G79iLero+oE3MBKjnAwYwtWiFEKDFIY8xza16Wyccs72pEoJj/tjzLDD pznh52HZKn+yU9PGk27SDoYAVyW89s7QuLWi/8OsqBdS6dFMeE2G6l7ykK3HId3B3VRe Np7bKE8EE7FVOrDJtpyflvbRVPnVZT4lxSOq4unzw/1uC/Q5hlXFjYjdf0gpgHonqlBz dj9gW0HC2hIOY/YQIxY7xHb4vEX1hpwc9Cp012ZKTxTDs+wq7WAmrNbOe+ZMn//xPfd0 ucOwGcyNZXEjZRV+NIoRhrR20Lyd1hnkdvrwL+DROYsEWxHkf3fyFEkDvDqd3r/bYtUj svAw==
X-Received: by 10.60.51.6 with SMTP id g6mr24290928oeo.5.1390363421476; Tue, 21 Jan 2014 20:03:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 21 Jan 2014 20:03:21 -0800 (PST)
In-Reply-To: <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.com>
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com> <52DF1AC4.7080007@isi.edu> <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 21 Jan 2014 23:03:21 -0500
Message-ID: <CAPv4CP9UJxf+w6yOwVq9=nDmig=br4x1qD3_sJpz+WpHaDd+Kw@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Ross Callon <rcallon@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 04:03:43 -0000

On Tue, Jan 21, 2014 at 9:40 PM, Ross Callon <rcallon@juniper.net> wrote:
> If the upper layers (the thing that runs over the tunnel) involves applic=
ations over TCP over IP, or if it is otherwise responding to congestion in =
the same way that we expect anything running over IP to respond to congesti=
on, then we don't want the tunnel to also independently try to respond to c=
ongestion (two independent cooks cooking the same meal does not necessarily=
 lead to success).
>
> If the upper layer does not respond to congestion, then perhaps it should=
n't be running over the open Internet (with or without a tunnel), unless th=
e *total* bandwidth that could be used is inherently quite low. On the othe=
r hand, it might want to run within a data center or internally to a servic=
e provider network with appropriate provisioning.

To paraphrase: if this problem exists in the new encapsulation, then
it exists already.

Lars is right, this does allow traffic that was formerly run over
provisioned paths in well-managed networks to possibly be part of
general Internet traffic. It would be good if there were a way to be
_sure_ there was e2e congestion control. But there is no signaling
between this low-layer UDP encapsulation and anything above it that
might already be reacting to congestion. There is no reasonably easy
way for it to know what it is carrying. Yes there is a way to do
congestion control at the bottom layer, but doing so could destroy
performance if one (or more) layer(s) is already doing it up above. We
have experience with that.

I can't remember who said it, but an applicability statement might
satisfy everyone, especially since it's been said (Curtis?) that this
just isn't going to be used in situations where congestion will be a
problem.

Alternatively, a paragraph laying out the problem and saying if this
is used in a way that could impact ordinary traffic, a mechanism must
be defined.

Scott

From garbakora@gmail.com  Tue Jan 21 23:32:36 2014
Return-Path: <garbakora@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA261A034E; Tue, 21 Jan 2014 23:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I59tbaAx9rFk; Tue, 21 Jan 2014 23:32:35 -0800 (PST)
Received: from mail-qa0-x243.google.com (mail-qa0-x243.google.com [IPv6:2607:f8b0:400d:c00::243]) by ietfa.amsl.com (Postfix) with ESMTP id C1F9C1A005A; Tue, 21 Jan 2014 23:32:34 -0800 (PST)
Received: by mail-qa0-f67.google.com with SMTP id j5so7749qaq.6 for <multiple recipients>; Tue, 21 Jan 2014 23:32:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=rlGNooE69Cee68SAMhzp1j5WpfQVsWhSeW2C87Bylgo=; b=WJj3InmpeaZUcQ3qMKOAd24ZGyL8beTC1tIWJiSzz7JgobfBTfQ8RVizN3W8LLdooH +Edu9ltGvDSvlNjswf2C0HhvcpcT0N3y149MvL98tzdCHCZWCKXefHzX1Fb3OoX/wgGZ xL5T3uLZvv8kc0fF4W44kZv4WnRzD3GN2NYj14WM9+xV+l2E3+26JYOJr1kMLPNmxqAU 66F52m7tfDiC5pv7/0OFAHezsssIdH7neDonA/aoZPESv4tNb8tHy3ajKnyMSaLE8GTC SHFJfzV8KOzu7XCrb0207+sieZOtCRlbZ5BZipXibkv02JgKbF2CjT1p6Lj8/BIhvaSc hgYw==
MIME-Version: 1.0
X-Received: by 10.224.2.194 with SMTP id 2mr64141qak.44.1390375954211; Tue, 21 Jan 2014 23:32:34 -0800 (PST)
Received: by 10.96.31.9 with HTTP; Tue, 21 Jan 2014 23:32:34 -0800 (PST)
Date: Wed, 22 Jan 2014 08:32:34 +0100
Message-ID: <CA+bJALp_wp=6o7TE6UBsCz9wFr-hHM2Tns34_R3A=MifEfXF5w@mail.gmail.com>
Subject: Remove me please
From: GARBA KORA TAMSIRD BELLO <garbakora@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: manet@ietf.org, draft-ietf-manet-olsrv2-rmpr-optimization.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 07:32:36 -0000

Hello

I do not want receive no more msg from this mailing liste , please remove me




Thanks for sharing long work


2014/1/21, Adrian Farrel <adrian@olddog.co.uk>:
> A few minor last call comments coming from my AD review.
> The authors have already discussed these and know what to fix at the end of
> last
> call.
>
> Adrian
>
> ===
>
> I think MPR could usefully be expanded in the document title, in the
> Abstract, and on first use in the body.  Then you won't need to expand
> it in Section 3.
>
> ---
>
> It seems odd that Section 4 has a bullet numbered "1." but no other
> numbered bullets.
>
> ---
>
> I think Section 4 uses the notation of 18.2 of [OLSRv2] not 18.3. At
> least, that is where d1() etc. are defined for revision -19 of that
> document.
>
>

From spencerdawkins.ietf@gmail.com  Wed Jan 22 06:48:12 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFDE71A0113; Wed, 22 Jan 2014 06:48:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57E7xIgE6j7u; Wed, 22 Jan 2014 06:48:11 -0800 (PST)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id A94ED1A014B; Wed, 22 Jan 2014 06:48:10 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so529625oag.30 for <multiple recipients>; Wed, 22 Jan 2014 06:48:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=cSOPjB8N1Xa9jg5gO0+Pl1i9QqB3QlrEXfOCpxkD8q4=; b=iUAoblElrl8dMmEVwYfMu9/FZs2tzddvvfdns1uCvURIFZdOKA+4uD0ptXqocl3rDl iNuRDekWYe9MiJRKXOAJ/9mpwlYiPY+rHJBA6KVcSg/aqYi+HAvIOqwEo7drIOtVaElc dcP0ISNMnq3ooSkzBBh0uAkRUIuNuyScTOGzuBmBdNm5dzxLyFd9bPO1Ztc9Rc+UF3BW C32zN4PfrEjOkXpBK4MR8lv6veLVU9BcJzso9zMlpeKnO9MGF3m5yNncmCtvJsvPUFOR jxVKHpPWxBFZYg0ALKOkDTUNGYB9uUY2sm3Bs/qe77c2Dd5fYKLwlGK32sC5NKdPnM69 9KVw==
X-Received: by 10.182.22.33 with SMTP id a1mr1620189obf.60.1390402090123; Wed, 22 Jan 2014 06:48:10 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id oo13sm39900310oeb.0.2014.01.22.06.48.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 06:48:09 -0800 (PST)
Message-ID: <52DFDA26.2070103@gmail.com>
Date: Wed, 22 Jan 2014 08:48:06 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, Ross Callon <rcallon@juniper.net>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com> <52DF1AC4.7080007@isi.edu> <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.com> <CAPv4CP9UJxf+w6yOwVq9=nDmig=br4x1qD3_sJpz+WpHaDd+Kw@mail.gmail.com>
In-Reply-To: <CAPv4CP9UJxf+w6yOwVq9=nDmig=br4x1qD3_sJpz+WpHaDd+Kw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 14:48:13 -0000

For what it's worth ...

On 01/21/2014 10:03 PM, Scott Brim wrote:
> On Tue, Jan 21, 2014 at 9:40 PM, Ross Callon <rcallon@juniper.net> wrote:
>> If the upper layers (the thing that runs over the tunnel) involves applications over TCP over IP, or if it is otherwise responding to congestion in the same way that we expect anything running over IP to respond to congestion, then we don't want the tunnel to also independently try to respond to congestion (two independent cooks cooking the same meal does not necessarily lead to success).
>>
>> If the upper layer does not respond to congestion, then perhaps it shouldn't be running over the open Internet (with or without a tunnel), unless the *total* bandwidth that could be used is inherently quite low. On the other hand, it might want to run within a data center or internally to a service provider network with appropriate provisioning.
> To paraphrase: if this problem exists in the new encapsulation, then
> it exists already.
>
> Lars is right, this does allow traffic that was formerly run over
> provisioned paths in well-managed networks to possibly be part of
> general Internet traffic. It would be good if there were a way to be
> _sure_ there was e2e congestion control. But there is no signaling
> between this low-layer UDP encapsulation and anything above it that
> might already be reacting to congestion. There is no reasonably easy
> way for it to know what it is carrying. Yes there is a way to do
> congestion control at the bottom layer, but doing so could destroy
> performance if one (or more) layer(s) is already doing it up above. We
> have experience with that.
>
> I can't remember who said it, but an applicability statement might
> satisfy everyone, especially since it's been said (Curtis?) that this
> just isn't going to be used in situations where congestion will be a
> problem.

Alia Atlas made this suggestion.

Speaking as an AD who has been following this conversation with some 
interest ... that's gotta help.

> Alternatively, a paragraph laying out the problem and saying if this
> is used in a way that could impact ordinary traffic, a mechanism must
> be defined.

I would read such a paragraph with some interest ...

Spencer

From touch@isi.edu  Wed Jan 22 07:20:26 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C21761A010C; Wed, 22 Jan 2014 07:20:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pynengn7gPRw; Wed, 22 Jan 2014 07:20:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id EDC1D1A0111; Wed, 22 Jan 2014 07:20:11 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0MFIXkP025761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 07:18:42 -0800 (PST)
Message-ID: <52DFE14C.5010802@isi.edu>
Date: Wed, 22 Jan 2014 07:18:36 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ross Callon <rcallon@juniper.net>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com> <52DF1AC4.7080007@isi.edu> <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlo! ok.com>
In-Reply-To: <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:20:27 -0000

On 1/21/2014 6:40 PM, Ross Callon wrote:
> If the upper layers (the thing that runs over the tunnel) involves
> applications over TCP over IP, or if it is otherwise responding to
> congestion in the same way that we expect anything running over IP to
> respond to congestion, then we don't want the tunnel to also
> independently try to respond to congestion (two independent cooks
> cooking the same meal does not necessarily lead to success).

That's true, but is an issue only if the tunnel congestion control is 
dynamic over the same or shorter timescales than the 
congestion-controlled traffic being tunneled.

> If the upper layer does not respond to congestion, then perhaps it
> shouldn't be running over the open Internet (with or without a tunnel),
> unless the *total* bandwidth that could be used is inherently quite low.

Sure, but who would enforce that? If you're using MPLS, the only entity 
in a position to know (whether the traffic is congestion controlled or 
not) is the tunnel encapsulator.

> On the other hand, it might want to run within a data center or
> internally to a service provider network with appropriate provisioning.

All bets are always off for private networks; they need not comply with 
any Internet standards or expectations, even when they leverage Internet 
header formats and protocols.

But that's not a strict constraint of the proposed approach here.

Joe


> Ross
>
> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, January 21, 2014 8:12 PM
> To: Ross Callon; Eggert, Lars
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>
>
>
> On 1/16/2014 2:32 PM, Ross Callon wrote:
>>>> These tunnels are stateless
>>>
>>> yep. (But they don't have to be.)
>>
>> The tunnels strictly speaking do not have to be stateless. However, if you want routers to actually implement them, and you want to scale in both forwarding speed and number of tunnels, then yes they do have to be stateless.
>
> There's clearly a problem though:
>
> 	- tunnels must be stateless to be efficiently implemented
>
> 	- transport layer tunnels must have congestion control
>
> Saying that the only way we can make tunnels cheap is to make them break
> the Internet isn't a good solution.
>
> Maybe it's time to expect something that's inherently costly to end up
> being expensive?
>
> Joe
>
>
>

From touch@isi.edu  Wed Jan 22 07:34:39 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDBDD1A0102; Wed, 22 Jan 2014 07:34:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uo7-mb0gFZvx; Wed, 22 Jan 2014 07:34:38 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 278241A00E4; Wed, 22 Jan 2014 07:34:38 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0MFXQj1028544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 07:33:35 -0800 (PST)
Message-ID: <52DFE4C9.8080403@isi.edu>
Date: Wed, 22 Jan 2014 07:33:29 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <5933BB7D-2D2D-4145-A0B2-E92C8DA25844@netapp.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE08242A8E@NKGEML512-MBS.china.huawei.com> <43B89809-F517-4BE2-BE1B-748A4B78FC7F@netapp.com> <52D01383.2080509@joelhalpern.com> <8DCFAFEE-2B06-4334-A5D7-7698D8D3081A@netapp.com> <CAPv4CP-iwoHEiV=xtNAd7qT4r8OYvfE1ZjnKE=wWY5VVcQ3x8w@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <52DF19ED.8010200@isi.edu> <CAPv4CP_OQ57_tHzVB+7cQ=QpMPyD9Q9zLJW0MrGDioiCADF9Rg@mail.gm! ail.com>
In-Reply-To: <CAPv4CP_OQ57_tHzVB+7cQ=QpMPyD9Q9zLJW0MrGDioiCADF9Rg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:34:39 -0000

On 1/21/2014 7:50 PM, Scott Brim wrote:
> On Tue, Jan 21, 2014 at 8:07 PM, Joe Touch <touch@isi.edu> wrote:
>>
>> On 1/14/2014 7:23 AM, Joel M. Halpern wrote:
>>>
>>> Isn't that basically the problem of the inner traffic sender, not the
>>> problem of the tunnel that is carrying the traffic?
>>> Asking tunnel's to solve the problem of applications with undesirable
>>> behavior seems backwards.
>>
>> By that argument, apps using TCP shouldn't expect the transport to control
>> congestion. They ought to control it at the app layer.
>>
>> Tunneled MPLS, when encapsulated inside UDP, *is* the "application". UDP
>> expects the app to deal with congestion, so it's entirely reasonable for UDP
>> to expect the tunneling system to do this.
>
> Joe, I believe you are confusing a protocol with an architectural
> function.

http://www.isi.edu/rna ought to clear that misconception up.

> It's a UDP encapsulation, but that encapsulation has nothing
> to do with transport, and what runs over it is not an "application".

That would be correct if the 8-byte UDP header were interpreted anywhere 
*except* the current Internet as the demuxing layer above IP. But that 
semantics is exactly what this document seeks - to use that UDP 
information for load balancing, e.g.

Consider this from the Internet's viewpoint; UDP traffic is traversing 
it, sourced by the tunnel ingress, and travels through the Internet with 
the congestion control expectations outlined in RFC5405.

To the Internet, this UDP header is a transport layer, and the tunnel 
ingress is the application.

Yes, if you were just using these bytes somewhere else, interpreted by 
some other mechanism (or not), they'd be just bytes of encapsulation. 
But in the Internet, the roles are determined by RFC768, RFC1122, and 
RFC5405.

> It may be a client layer (with the encapsulation a service layer), but
> that's a relative relationship, not an absolution one about stack
> position.

In an arbitrary environment, without knowledge of any of the other 
protocol layers, yes (that's the principle behind RNA, above).

When instantiated inside the Internet, when you take a physical signal, 
interpret it as a link layer packet, examine the next 20-40 bytes as the 
IP header, and the next 8 as UDP, then that UDP header *is* the 
transport layer for that network (the Internet), and the application 
layer *is* whatever generated the contents of that packet (the 
encapsulator).

 > This instance of UDP is way below transport, is just in
> fact a bit of lubrication for the packet, and considered

That's true from the perspective of the MPLS packet and its origin 
network, but not from the perspective of the network the UDP 
encapsulated result traverses.

> _functionally_ has nothing to do with congestion control.

Oh, sure - UDP has nothing to do with congestion control. But that's 
exactly why the transport area generated RFC5405's section 3.1.3 - 
requiring that the application (the party that generates the UDP 
packets) includes congestion control (directly, or by transitive closure 
of the source of the source of the source... that generated the original 
highest layer of packet, which eventually became encapsulated in UDP).

 > The only
> reason for using UDP encapsulation is to get through middleboxes. If
> something else worked better for that, they would use it.

According to the doc, this is also for load distribution. That aside, 
however, it'd be nice if there were a layer that just "got through 
middleboxes" and had no other properties.

UDP isn't that layer. Nor is TCP.

TCP comes with its own baggage (including reactive congestion control) 
of a heavyweight mechanism that isn't desired for most high-speed tunnels.

UDP comes with RFC5405. That requires some sort of congestion reaction. 
No need to be on the same timescale as TCP - it could be much slower, or 
could simply be (as Lars suggested) a throttle-limit (circuit breaker).

Joe

From touch@isi.edu  Wed Jan 22 07:37:53 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6A71A00E4; Wed, 22 Jan 2014 07:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hwx41X7SzANq; Wed, 22 Jan 2014 07:37:52 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 672BE1A00CF; Wed, 22 Jan 2014 07:37:52 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0MFbGJJ029275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 07:37:25 -0800 (PST)
Message-ID: <52DFE5AC.9020008@isi.edu>
Date: Wed, 22 Jan 2014 07:37:16 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, Ross Callon <rcallon@juniper.net>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140102151419.4692.48031.idtracker@ietfa.amsl.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0824427A@NKGEML512-MBS.china.huawei.com> <A1F82D9D-F9D0-46C1-B666-0C13DB79A845@netapp.com> <52D40B91.8040101@joelhalpern.com> <CAPv4CP9R-6Dv9O_H8Ox_-uLWMSzqpx7Gn97TF8jceFkVKPLWTw@mail.gmail.com> <52D518D9.7010703@cisco.com> <CAPv4CP-eNJuOKv4vWxGkiUPUTMkYyqY4cbTmj8M4sn+jXzmCkw@mail.gmail.com> <CAPv4CP-DnNdSoVEFTg9N53xP=yOd6pNe97WxmXJeGHBPKC2h6w@mail.gmail.com> <52D547B2.1060302@cisco.com> <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com> <52D5568F.2070600@joelhalpern.com> <3D9BA53E-F0F7-4B8B-8433-4DFE6852AF87@netapp.com> <52D811A2.9070606@bogus.com> <7865A4F7-F142-43FA-9E6B-94912F1BDC3A@netapp.com> <491c4cdfce7e4d688f8c054553901f39@CO2PR05MB636.namprd05.prod.outlook.com> <52DF1AC4.7080007@isi.edu> <c3c178b033114a4eba7c226293f451c1@CO2PR05MB636.namprd05.prod.outlook.com> <CAPv4CP9UJxf+w6yOwVq9=nDmig=br4x1qD3_sJpz+WpHaDd+Kw@mail.gmail.com>
In-Reply-To: <CAPv4CP9UJxf+w6yOwVq9=nDmig=br4x1qD3_sJpz+WpHaDd+Kw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:37:54 -0000

On 1/21/2014 8:03 PM, Scott Brim wrote:
> Lars is right, this does allow traffic that was formerly run over
> provisioned paths in well-managed networks to possibly be part of
> general Internet traffic. It would be good if there were a way to be
> _sure_  there was e2e congestion control. But there is no signaling
> between this low-layer UDP encapsulation and anything above it that
> might already be reacting to congestion. There is no reasonably easy
> way for it to know what it is carrying. Yes there is a way to do
> congestion control at the bottom layer, but doing so could destroy
> performance if one (or more) layer(s) is already doing it up above. We
> have experience with that.

Lars isn't suggesting congestion control on the same timescale as TCP, 
which is where the problem would be.

Long-timescale control OR something as simple as a throttle-cap would be 
sufficient.

> I can't remember who said it, but an applicability statement might
> satisfy everyone, especially since it's been said (Curtis?) that this
> just isn't going to be used in situations where congestion will be a
> problem.

If we accepted that premise, we wouldn't need any congestion control. 
Nobody openly claims to want to generate congestion.

Congestion control is required to protect the rest of us from cases 
where that claim turns out to be false (typically because the protocol 
designers/use case authors turned out to be wrong).

> Alternatively, a paragraph laying out the problem and saying if this
> is used in a way that could impact ordinary traffic, a mechanism must
> be defined.

The problem is very clearly already stated in RFC5405. I can't see how 
this mechanism would ever be used if not for ordinary traffic.

So yes, a mechanism must be defined IMO too.

Joe

From touch@isi.edu  Wed Jan 22 07:47:16 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3F91A0159; Wed, 22 Jan 2014 07:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.235
X-Spam-Level: 
X-Spam-Status: No, score=-4.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id alGmuZx7SSph; Wed, 22 Jan 2014 07:47:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id E75B11A0154; Wed, 22 Jan 2014 07:47:15 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0MFkUn6001040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 07:46:39 -0800 (PST)
Message-ID: <52DFE7D8.9090400@isi.edu>
Date: Wed, 22 Jan 2014 07:46:32 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:47:16 -0000

On 1/17/2014 9:19 AM, Curtis Villamizar wrote:
> Lars,
>
> We seem to be in an endless loop here.
>
> You have made your assertions about your desire to uphold the purity
> of any new UDP applications and adhere to the BCP you wrote.

The BCP that the transport area as a whole recommends, in conjunction 
with the IETF as a whole.

> You appear to be very nearly alone in this argument...

The IETF is a very large DDOS attack on people's time. It's very easy 
for faulty ideas to pop up and not be challenged - easy because there 
are a lot of people (companies) with vested (financial) interest in 
promoting their particular approaches, and only a few people who care to 
spend the time playing "whack a mole" to defend the Internet against 
these approaches (by either pulling them back into compliance with 
agreed principles, such as BCPs, or shooting down ideas altogether).

So if your room is full of your own choir singing so loud for your own 
sake that you can't hear the objections of the few who are providing 
feedback from outside the room, that shouldn't be surprising. But that 
neither means the choir is in tune nor that there aren't many outside 
the room (or who don't attend meetings) who aren't trying to tell you 
otherwise.

FWIW.

:-)

Joe

From touch@isi.edu  Wed Jan 22 07:51:55 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 490141A0167; Wed, 22 Jan 2014 07:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ky4hNptpXHK1; Wed, 22 Jan 2014 07:51:54 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3112C1A0160; Wed, 22 Jan 2014 07:51:54 -0800 (PST)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id s0MFpAXI001943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 22 Jan 2014 07:51:19 -0800 (PST)
Message-ID: <52DFE8F1.7070304@isi.edu>
Date: Wed, 22 Jan 2014 07:51:13 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401150040.s0F0eZXj005169@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401150040.s0F0eZXj005169@maildrop2.v6ds.occnc.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:51:55 -0000

On 1/14/2014 4:40 PM, Curtis Villamizar wrote:
> In message <DB6CF60F-FFBA-47DA-9FD6-7288CCB260A6@netapp.com>
> "Eggert, Lars" writes:
>
>> On 2014-1-14, at 15:20, Stewart Bryant <stbryant@cisco.com> wrote:
>>> Yes, the inner (real) transport header is the only meaningful place
>>> to apply congestion avoidance.
>>
>> But what if the inner traffic isn't congestion controlled?
>>
>> Lars
>
>
> Lars,
>
> The exact same thing will happen in all of the following cases:
>
>    NON-congestion controlled application --over--
>    UDP --over-- IP --over-- L2
>
>    NON-congestion controlled application --over--
>    UDP --over-- IP --over-- MPLS --over-- L2
>
>    NON-congestion controlled application --over--
>    UDP --over-- IP --over-- MPLS --over-- UDP --over-- IP --over-- L2
>
> The non-congestion controlled application is what needs fixing.

In all three cases, RFC5405 expects that traffic inside UDP is 
congestion controlled. That can happen when the source application does 
so, but when that isn't known, it needs to happen at whatever layer puts 
the packet inside the UDP header that the Internet ends up seeing.

> It would be wrong to try to put congestion control at every layer
> underneath the non-congestion controlled application

Yes, but it's not wrong to require some sort of congestion control at 
any layer that generates a UDP packet inside the Internet or any other 
Internet-protocol-based network that has the same RFC5405 expectations.

Joe


From curtis@ipv6.occnc.com  Tue Jan 21 11:23:35 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AED131A01D2; Tue, 21 Jan 2014 11:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.437
X-Spam-Level: 
X-Spam-Status: No, score=-4.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ln7sROzeoa-V; Tue, 21 Jan 2014 11:23:32 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id B4DA91A01C3; Tue, 21 Jan 2014 11:23:31 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0LJNRPm064842; Tue, 21 Jan 2014 14:23:27 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401211923.s0LJNRPm064842@maildrop2.v6ds.occnc.com>
To: "Black, David" <david.black@emc.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
In-reply-to: Your message of "Sun, 19 Jan 2014 21:05:17 -0500." <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
Date: Tue, 21 Jan 2014 14:23:27 -0500
X-Mailman-Approved-At: Wed, 22 Jan 2014 08:10:34 -0800
Cc: "draft-ietf-mpls-multipath-use.all@tools.ietf.org" <draft-ietf-mpls-multipath-use.all@tools.ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 21 Jan 2014 19:23:35 -0000

In message <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
"Black, David" writes:
> 
> I have reviewed this document as part of the operations directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> operations area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>  
> Summary:
> This draft is on the right track but has open issues, described in the review.
>  
> I apologize for this review showing up a couple of days after the end of
> IETF Last Call.
>  
> This draft discusses considerations for what are effectively MPLS-in-MPLS
> tunnels for multipathing - an LSP carries another LSP, with the inner
> (client) LSPs being distributed across multiple outer (server) LSPs that
> use different paths.  This draft is motivated by considerations specific
> to MPLS-TP that complicate multipathing when one of the two MPLS instances
> is MPLS-TP.

Skipping to the discussion quite a ways down, there seems to be some
confusion about what is being proposed here.  While MPLS-in-MPLS is
being used, no new form of MPLS-in-MPLS is being proposed.

There is an underlying assumption in the draft that the reader
understands that MPLS-in-MPLS exists today, most commonly but not
exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
means to advertise forward adjacencies (FA) where MPLS-in-MPLS at some
level of Packet Switch Capable (PSC) hierarchy.  It is also possible
to make use of the management plane, using CLI or NETCONF or the MPLS
cross connect MIB to program a multiple label MPLS push operation.

If a very experienced reviewer could miss that, then the introduction
could be improved by better stating assumptions.  It is also the case
that many participants in MPLS, particularly those primarily
interested in MPLS-TP, began participation long after RFC 4206 was
written and would benefit by better stated assumptions in the intro.

I suggest that the following paragraphs be added to the introduction.

   MPLS LSPs today are able to function as a server layer and carry
   client MPLS LSPs.  When control plane signaling is used, forwarding
   adjacency (FA) advertisements are used to inform the set of LSR of
   Packet Switching Capable (PSC) LSP within the MPLS topology
   [RFC4206].  Client MPLS LSP at a higher layer (lower PSC number)
   may signal their intention to use PSC LSP as hops in the RSVP-TE
   Explicit Route Object (ERO).  LSR with no explicit support for RFC
   4206 see the PSC LSP as ordinary links and therefore use them.

   An MPLS LSP that has been set up using RSVP-TE appears to its
   ingress LSR as a viable IP next hop to a distant LSR.  If LDP is
   used and bidirectional RSVP-TE LSP connectivity is available, then
   LDP signaling can be set up among the RSVP-TE LSP endpoints and LDP
   can make use of the RSVP-TE LSP as an LDP hop.  This is another
   form of existing MPLS-in-MPLS use.

   MPLS LSPs may also make use of hierarchy that is configured through
   the management plane rather than signaled using RSVP-TE.

   These existing forms of MPLS-in-MPLS may traverse multipath hops
   such as Ethernet LAG [IEEE802.1AX] or MPLS Link Bundling [RFC4201].
   MPLS-TP brings with it a new set of requirements not considered in
   past deployments of the various forms of MPLS-in-MPLS where
   multipath was in use.  This document merely discusses use of
   existing forwarding and protocol mechanisms that can support the
   case where either the client layer LSPs or the server layer LSPs
   are MPLS-TP and where multipath is used.

If there are no objections I will add these paragraphs.

Now on to the specific comments.

> I consider the following to be open issues that need attention (each
> letter is used to tag the issue in the text that follows - [B] occurs
> multiple times, as there are multiple aspect to that issue):
>  
> [A] Summary text in Introduction appears to be wrong.
> [B] Section 3.2 needs a summary.
> [C] Entropy label "sandwich" seems peculiar and at least needs an explanation.
> [D] Discussion of multipath impacts on MPLS OAM should be added to Section 4.
>  
> --- Comments on draft text
>  
> [A] Section 1 (Introduction) 2nd paragraph:
>  
>    RFC 5654 requirement 33 requires the capability to carry a client
>    MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC5654].
>    This is possible in all cases with one exception.  When an MPLS LSP
>    exceeds the capacity of any single component link it MAY be carried
>    by a network using multipath techniques, but MAY NOT be carried by a
>    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
>    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
>    fate sharing constraints and MPLS-TP LM OAM packet ordering
>    constraints (see Section 3.1).
>  
> Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> exception appears to concern the reverse, and Section 4 on carrying MPLS
> over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> Was the exception intended to be for an MPLS-TP LSP that exceeds the
> capacity of any single component link?

There is no problem today with MPLS LSP carried by MPLS-TP LSP except
the existing case where MPLS LSP capacity is too big.  For example, a
500 Gb/s LSP is possible today carried over N x 100 Gb/s or N x 10
Gb/s multipath links but could not be carried over a single MPLS-TP
LSP which would be limited to a single 100 Gb/s or 10 Gb/s link.  So
the exception is where the MPLS LSP is too big to fit in any possible
single MPLS-TP LSP.

To answer your question directly: the exception is a very large MPLS
LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
this is occurring.

> Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's equivalent
> to "MAY OR MAY NOT").  I think "cannot" was intended her, but "MUST NOT"
> is another possibility.

Good point.  I suggest we replace the MAY NOT with SHOULD NOT.  Many
people would insist that it should be MUST NOT, but in reality
networks SHOULD NOT be congested but sometimes they are.

> [B] Section 3.2 contains a lot of useful details, but it could really use
> a summary at the end on the options and recommendations for meeting the
> four requirements (this summary could be a new Section 3.3).  It's a bit
> difficult to discern what's going on, as I had to read this section more
> than once in order to discern the following:

OK.  A Summary paragraph can be added.  See below.  Perhaps conclusion
section can be added.  See far below.

> [C] In Section 3.2, use of an MPLS entropy label to meet requirement MP#1
> requires that it be "below the MPLS-TP label" whereas, to meet requirement
> MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LSP label".
> This combination appears to suggest "sandwiching" the MPLS-TP label between
> two entropy labels that effectively carry the same information (albeit,
> applied and removed at different places in the network) - was that intended?
> This is important, as there seems to be no reasonable alternative
> to the entropy label for meeting requirement MP#2, and the draft's
> alternative to the entropy label for meeting requirement MP#1 is "some form
> of configuration" - the entropy label would seem to be preferred to that
> based on my reading of this draft and the comment in RFC 5706 section 2.2
> that "Anything that can be configured can be misconfigured."

The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
paragraph.

   Alternately, the need for requirement MP#1 can be eliminated if
   every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
   Entropy Label Indicator (ELI) and Entropy Label (EL) below the
   MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
   in a deployment support Entropy Label, which may render it
   impractical in many deployments.

Please not the "Alternately" at the beginning and "impractical in many
deployments" at the end.

The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
above that but assumes knowledge of RFC 6790.  I think the following
change within this paragraph would clear things up:

 OLD

   MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
   and Entropy Label (EL) are added to the label stack [RFC6790].  For
   those client LSP that are MPLS-TP LSP, a single EL value must be
   chosen.  For those client LSP that are MPLS LSP, per packet entropy
   below the top label must, for practical reasons, be used to
   determine the entropy label value.

 NEW

   MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
   and Entropy Label (EL) are added to the label stack by the midpoint
   LSR for the client MPLS-TP LSP, at the ingress of the MPLS LSP
   [RFC6790].  For those client LSP that are MPLS-TP LSP, a single EL
   value must be chosen.  For those client LSP that are MPLS LSP, per
   packet entropy below the top label must, for practical reasons, be
   used to determine the entropy label value.  The resulting label
   stack contains the server MPLS LSP label, ELI, EL and the client
   LSP label.

The above rewording is simply more explicit about the label stack
order and which LSR puts the ELI and EL in the label stack.

> [B] A summary of requirements for implementation and deployment at the end
> of Section 3.2 would have made this much more obvious.  That should be
> provided in addition to addressing the above question about duplicate use
> of the MPLS entropy label.

The following summary can be added to the end of Section 3.2:

   Two methods of adding an Entropy Label are described above.  The
   MPLS-TP ingress must have a means to determine which links can
   support MPLS-TP in selecting a path (MP#4).  Administrative
   attributes can satisfy that requirement.  If the MPLS-TP LSR is
   capable of adding ELI/EL to the label stack, this method is
   preferred.  However access and edge is the least likely to support
   RFC 6790 in the near term.  For portions of the topology where an
   MPLS-TP is carried within a server layer MPLS LSP the ingress of
   the server layer MPLS LSP can add ELI/EL using a fixed EL value per
   client LSP, except those known not to require MPLS-TP treatment.
   There are numerous ways to determine which client LSP are MPLS-TP
   LSP and which are not.  While this determination is out of scope
   and will vary among deployments, configuration or the presence of
   specific attribute affinities in RSVP-TE signaling are among the
   likely means to do so.

If there are no objections I will add the above paragraph.

> --- Relevant Q&A based on RFC 5706 Appendix A
>  
> I'm omitting management concerns, as both MPLS and MPLS-TP have extensive
> management infrastructure, and this draft's notion of stacking LSPs so
> that one instance of MPLS (or MPLS-TP) can be a server to (i.e., carry)
> another is not novel to this draft.
>  
> A.1.1.  Has deployment been discussed?
>  
> [B] Yes, although Section 3.2 is weak on deployment requirements (some of
> which are implementation requirements) and could use a summary.

The use of RFC 4206 is assumed throughout the discussion of signaling
in section 3.2.  This assumption is made more clear by suggested
additions to the introduction.

> A.1.2.  Has installation and initial setup been discussed?
>  
> No, although because this draft reuses existing functionality in different
> configurations, this really reduces to the A.1.9 configuration question
> below.  In practice, quite a bit of operator knowledge and insight is
> required to get initial setup right, e.g., as traffic engineering LSPs to
> avoid congestion problems (needed to meet requirement MP#3) requires
> significant knowledge of network structure and expected traffic flows.
> This should be obvious to anyone who works w/MPLS, but it's probably
> worth stating for completeness.

FA advertisements defined in RFC 4206 make it possible for ingress to
signal viable paths.  Either the use of Ethernet Link Aggregation or
MPLS Link bundling using the all-ones component link (RFC 4201) allows
the total capacity of a multipath to be advertised.  Meeting the
requirement to balance traffic over the component links in a multipath
(MP#3) is then a local matter and requires no further signaling
extensions.

> A.1.6.  Have suggestions for verifying correct operation been discussed?
>  
> Yes and no.  Section 3.2 discusses OAM, and contains this important
> requirement for OAM traffic:
>  
>    An Entropy Label must be used to insure that all of the
>    MPLS-TP payload and OAM traffic are carried on the same component,
>    except during very infrequent transitions due to load balancing.
>  
> [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> Section 4; that should be added.

There is no impact on MPLS OAM traffic.  There are three cases to
consider.

  1. Where MPLS is carried over a single MPLS-TP all traffic flows on
     one link.  MPLS OAM is unaffected and need not use multipath
     support in LSP Ping.

  2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
     LSP is carried over one link thanks to the fixed EL value.
     MPLS-TP OAM is unaffected.

  3.  Where MPLS is carried over MPLS (an existing case) or over
      multiple MPLS-TP, the multipath support in LSP Ping (as
      imperfect as it may already be) is used and LSP Ping (RFC 4379)
      operation is unaffected.

If needed something can be added to state the above (maybe with less
informal wording).  What is obvious to some people may not be obvious
to everyone.  Briefly stating the almost obvious is usually not a bad
thing.  Please tell me if a small subsection on "Imopact on MPLS and
MPLS-TP OAM" is needed.

Note that the limitations of LSP Ping are currently being discussed in
the MPLS WG in the context of extensions to LSP Ping to better support
Entropy Label.  A few limitations not related to EL may get fixed in
the process.

> A.1.9.  Is configuration discussed?
>  
> [B] Not much. Configuration is required to meet requirements MP#3 and MP#4,
> and is one of the options for MP#1.  A summary of what has to be configured
> as part of the summary at the end of Section 3.2 would be a good idea.

Perhaps a worked example appendix could be added but I don't think
this is common and may not be necessary with some of the
clarifications suggested so far.

> A.2.* [skipped, see above]
>  
> A.3 Documentation
>  
> There's quite a bit of operational material contained in this draft; a
> separate section on operations and management considerations would not
> be appropriate.
>  
> There is a useful implementation status section which appears to imply
> that MPLS-TP over MPLS is not currently deployable due to absence of
> entropy label support, and because deployed MPLS equipment does not
> generally support multipathing.  Nonetheless, data center experience
> indicates significant value and widespread use of multipathing based
> on link aggregation and ECMP; corresponding benefits can be expected
> for use of multipathing in the Internet beyond data centers.

If you would like I can add a conclusion section as Section 5 with
these paragraphs:

   MPLS equipment deployed in the core currently supports multipath.
   For large service providers, core LSR must support some form of
   multipath to be deployable.  Deployed MPLS access and edge
   equipment is often oblivious to the use of multipath in the core.
   It is expected that at least first generation MPLS-TP equipment
   will be oblivious to the use of multipath in the core.  This first
   generation MPLS-TP equipment is deployable in a core using
   multipath, with no adverse impact to RSVP-TE signaling, if the edge
   equipment can support administrative attributes (RFC 3209) and the
   core equipment can support ELI/EL and put a per-LSP fixed EL value
   on any LSP that indicates a particular attribute affinity or can
   identify client MPLS-TP LSP through some other means.

   There are no issues carrying MPLS over MPLS-TP, except when the
   MPLS LSP is too big to be carried by a single MPLS-TP LSP.  Most
   MPLS core equipment and some edge equipment can configure an MPLS
   Link Bundle [RFC4201] over multiple component links where the
   component links are themselves MPLS LSP.  This existing capability
   can be used to carry large MPLS LSP and overcome the limited
   capacity of any single server layer MPLS-TP LSP.

If this conclusion section is added, then the three bullets above
regarding impact on OAM can be put there.  The three bullets can be
added as follows:

   MPLS OAM and MPLS-TP OAM are unaffected in the following cases
   proposed in this document:

     1. Where MPLS is carried over a single MPLS-TP all traffic flows
        on one link.  MPLS OAM is unaffected and need not use
        multipath support in LSP Ping.

     2. Where MPLS-TP is carried over MPLS, all traffic for that
        MPLS-TP LSP is carried over one link thanks to the fixed EL
        value.  MPLS-TP OAM is unaffected.

     3.  Where MPLS is carried over MPLS (an existing case) or over
         multiple MPLS-TP, the multipath support in LSP Ping is used
         and LSP Ping (RFC 4379) operation is unaffected.

I think adding the above as a conclusion section as Section 5 would
improve clarity and therefore is worth doing.

> --- Editorial comments/nits:
>  
> - Section 3.1, after RFC 5960 quotes:
>  
>    [RFC5960] paragraph 3 requires that packets within a specific ordered
>  
> Insert "Section 3.1.1., before "paragraph 3" and likewise for "paragraph 6"
> later in the same paragraph in the draft.

GenArt review caught this.  Done.

> - Section 3.2, requirement MP#3:
>  
>    MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not be
>  
> "insure" -> "ensure" or "assure".  Surely this draft does not envision
> operators taking out insurance policies on MPLS TP LSP behavior ;-).

Good catch.  I think "ensure" is the right word.

> - Section 3.2, last paragraph on p.8:
>  
>    An MPLS-TP LSP may not traverse multipath links on the path where
>    MPLS-TP forwarding requirements cannot be met.
>  
> "may not" is meaningless - I believe "MUST NOT" was intended here.

I suggested SHOULD NOT above.

> - Section 4, middle of 3rd para:
>  
> Editorial suggestions for clarity:
>  
> OLD
>             For those LSP that are larger than component link
>     capacity, their capacity are not integer multiples of convenient
>     capacity increments such as 10Gb/s.
> NEW
>             For those LSPs that are larger than a component link
>    capacity, the LSP capacities need not be (and often are not)
>    integer multiples of convenient capacity increments such as 10Gb/s.

Good suggestion.  GenArt review suggested adding "generally" making
the statement read "their capacity are generally not integer
multiples".  Your suggested rewording may be more clear.

Also "10Gb/s" should be "10 Gb/s".

> In particular, "are not" seems wrong, as the "integer multiples"
> case is possible, so I changed "are not" to "need not be (and often
> are not)" in the suggested new text.
>  
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------

Thanks for the review and for pointing out lack of clarity due to
underlying assumptions about the use of RFC 4206 (and perhaps use of
RFC 4201 as well for large MPLS LSP over MPLS-TP).

Sometimes it is too easy to forget that not all readers are going to
be as steeped in MPLS "as deployed today" details as a relatively
small number of long time MPLS participants are.

Adding a few paragraphs to the introduction and a few concluding
paragraphs may significantly improve clarity for people who have not
been following MPLS closely for a decade or more without requiring
them to read the references and figure out usage details themselves.

Please let me know how you feel about the suggested additions to the
document.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 21 12:58:55 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67B321A0358; Tue, 21 Jan 2014 12:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.937
X-Spam-Level: 
X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MdACCtiEuEiR; Tue, 21 Jan 2014 12:58:53 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 871EE1A02DC; Tue, 21 Jan 2014 12:58:40 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0LKwcu2066223; Tue, 21 Jan 2014 15:58:39 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401212058.s0LKwcu2066223@maildrop2.v6ds.occnc.com>
To: "Eggert, Lars" <lars@netapp.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Tue, 21 Jan 2014 13:22:50 +0000." <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
Date: Tue, 21 Jan 2014 15:58:38 -0500
X-Mailman-Approved-At: Wed, 22 Jan 2014 08:10:33 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 21 Jan 2014 20:58:55 -0000

Lars,

The IETF consensus in RFC5405 was to put a SHOULD in regarding use of
congestion control in tunneling protocols.

RFC2119 states:

  3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there
     may exist valid reasons in particular circumstances to ignore a
     particular item, but the full implications must be understood and
     carefully weighed before choosing a different course.

We have discussed the reasons why congestion control is in general a
good thing.  We have also discussed why there may be valid reasons to
not include congestion control in MPLS over UDP.

The question is not whether there is already IETF consensus on
congestion control in UDP in general.  There is consensus and that
consensus was to use the word "SHOULD".

The question we now face is whether MPLS in UDP needs to up the prior
consensus to a MUST or can keep it as SHOULD.  I see one or maybe two
people vigorously arguing to upgrade this to a MUST and otherwise
consensus to keep this as SHOULD.  Further I see no objection except
the same one or maybe two people to making the congestion control the
topic of a later work if a need for it arises.  Consensus does not
require unanimous agreeement.

If we are trying to gauge consensus, maybe both you and I should sit
back and let other people weigh in.

Curtis


In message <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
"Eggert, Lars" writes:
> 
> Hi,
>  
> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> > You have made your assertions about your desire to uphold the purity
> > of any new UDP applications and adhere to the BCP you wrote.
> >=20
> > You appear to be very nearly alone in this argument and certainly no
> > one that works with MPLS is siding with you.
>  
> the reason we wrote the RFC when I was TSV AD was that we were seeing a =
> whole bunch of questionable uses of UDP over the eyars and we were =
> having the same arguments over and over. That's why we decided to write =
> down the practices we expect users of UDP to follow. This is yet another =
> such questionable use.
>  
> (Also, I don't appreciate you turning this into a personal argument.)

Nothing personal intended.  

The important point is the sentence "You appear to be very nearly
alone in this argument and certainly no one that works with MPLS is
siding with you." was intended to point out that there is no consensus
behind your argument regardless of how vigorously you make that
argument.

> > In the end we can put anything we want in the RFC *but* IETF has never
> > truly had the final word on what vendors and operators do in provider
> > networks.
>  
> Aka the "take my toys and go home" argument. Heard it many times.

It has been successful many times in the past.  It turns into the "its
deployed so get over it" argument after a few years.

> > In this case, regardless of what changes are made to the draft,
> > implementations will offer at least the option for non-RFC behavior by
> > using zero checksums and not using any congestion control.  And
> > providers will make use of it, perhaps exclusively.
>  
> And there's nothing wrong with that - the BCP even says that one SHOULD =
> NOT use congestion control for some deployment cases.
>  
> But for others, one SHOULD. For those, a mechanism needs to be =
> available, i.e., it needs to be specified and implemented.
>  
> > The document might as well reflect reality, despite reality not
> > conforming to your notions of architectural purity.
>  
> I'm sorry, but we have certain architectural principles in the Internet =
> that we have IETF consensus on. At least since RFC2914, that includes =
> the need to have congestion control in place.
>  
> There are always special deployment scenarios where these principles do =
> not apply, and we typically explain in applicability statements when out =
> specifications can only be safely used under certain conditions. I don't =
> see any such statement in draft-ietf-mpls-in-udp, which to me means it's =
> targeted at general Internet-wide use.
>  
> > The best course of action is to put a SHOULD in regarding checksums
> > and put a SHOULD in regarding congestion avoidance.  Even the BCP does
> > not go any further than to say a tunneling protocol SHOULD use
> > congestion control and there were reasons that the word MUST was not
> > acceptable in the BCP.
>  
> The SHOULD for congestion control needs to actually describe a mechanism =
> that can be used when needed. It can't be a blanket "you SHOULD use =
> something but we don't tell you what it is"-statement.
>  
> > If we are still arguing over two instances of SHOULD vs MUST we have
> > wasted a lot of bandwidth on those two words.
>  
> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs =
> to be specified what is to be done. In the case of checksums, that's =
> obvious (calculate it and check it); in the case of congestion control, =
> some actual mechanism needs to be described (e.g., a circuit breaker).
>  
> > IMHO The only remaining question is whether the document can go =
> forward
> > with the definition of congestion control for MPLS over UDP left out
> > of scope and for another document if a need arises.
>  
> In my opinion, it cannot.
>  
> > If this is not acceptable to you (I doubt it is) please indicate what
> > you would like to see in the document and since this is IETF last call
> > where consensus matters and no one individual has veto power, we'll
> > have to see if there is consensus behind your proposed changes.
>  
> I would like the document to specify at the very least a circuit breaker =
> mechanism, that stops the tunneled traffic if severe packet loss is =
> detected along the path.
>  
> And this isn't about an "individual veto". This is about a document that =
> is at the moment in violation of IETF consensus at least as far back as =
> RFC2914.
>  
> Lars

From curtis@ipv6.occnc.com  Tue Jan 21 14:06:58 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC721A0225; Tue, 21 Jan 2014 14:06:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7DDumnr8LSh; Tue, 21 Jan 2014 14:06:54 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 05C211A01D3; Tue, 21 Jan 2014 14:06:51 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0LM6l4b067118; Tue, 21 Jan 2014 17:06:47 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401212206.s0LM6l4b067118@maildrop2.v6ds.occnc.com>
To: Jari Arkko <jari.arkko@piuha.net>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-mpls-multipath-use-03
In-reply-to: Your message of "Tue, 21 Jan 2014 17:50:52 +0200." <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
Date: Tue, 21 Jan 2014 17:06:47 -0500
X-Mailman-Approved-At: Wed, 22 Jan 2014 08:10:33 -0800
Cc: draft-ietf-mpls-multipath-use.all@tools.ietf.org, "gen-art@ietf.org Gen-ART" <gen-art@ietf.org>, ietf@ietf.org, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 21 Jan 2014 22:06:59 -0000

In message <E736F946-88D0-4262-B2DD-C62FC461A885@piuha.net>
Jari Arkko writes:
>  
> Many thanks for your (once again) detailed review, Peter! And thank
> you Curtis for making the fixes. One comment below:
>  
> >> Make all references to the expansion of ECMP read "Equal-Cost Multipath" for
> >> consistency with RFC 2991.
> > 
> > ECMP is expanded on first use in compliance with RFC Editor quidelines
> > for abbreviations.  ECMP is also expanded on first use within each
> > section where it is used with the exception of one place where ECMP is
> > contained in a verbatim excerpt in a quote from RFC6374.
>  
> I thought Peter was referring to the fact that your draft has some variation on the way the term is expanded, even outside verbatim examples:
>  
> > % grep -i 'equal' draft-ietf-mpls-multipath-use-03.txt
> > draft-ietf-mpls-multipath-use-03.txt:94:   than parallel links includes Equal Cost MultiPath (ECMP) as applied
> > draft-ietf-mpls-multipath-use-03.txt:148:   Equal Cost Multipath (ECMP)
> > draft-ietf-mpls-multipath-use-03.txt:149:       Equal Cost Multipath (ECMP) is a specific form of multipath in
> > draft-ietf-mpls-multipath-use-03.txt:229:       Equal-Cost Multi-Path (ECMP) load-balancing MUST NOT be performed
> > draft-ietf-mpls-multipath-use-03.txt:288:   following paragraph in "Section 2.9.4 Equal Cost Multipath" gives the
> > 
> > % grep -i "equal" rfc2991.txt
> > rfc2991.txt:   allow "Equal-Cost Multipath" (ECMP) routing.  Some router
> > 
>  
> I think you could align other instances than those relating to
> verbatim text from RFC 5960 or 6374.
>  
> Anyway, minor things. I have balloted no-objection for this draft for
> the Thursday's IESG telechat. Thanks for your hard work, all.
>  
> Jari


Jari,

Thanks for the no-objection.

There doesn't seem to be much consistency on ECMP expansion.

Checking abstracts in rfc-index:

RFC2992 (same authors as RFC2991) uses:

  Equal-Cost Multi-Path        - in the title
  Equal-cost multi-path (ECMP) - in the abstract

RFC4928 uses:

  Equal Cost Multipath (ECMP)

RFC5640 uses:

  equal cost multiple paths (ECMPs)

RFC6391 uses:

  Equal Cost Multiple Paths (ECMPs)

RFC6754 in the title uses:

  Equal-Cost Multipath (ECMP)

You'll get a few more combinations of hyphenation and capitalization
if you try:

  grep -i 'equal[- ]cost' rfc????.txt | grep ECMP

The total count for space vs hyphen (up to rfc7052) are:

  grep -i 'equal cost multi' rfc????.txt | grep ECMP | wc -l
      47
  grep -i 'equal-cost multi' rfc????.txt | grep ECMP | wc -l
      26

  grep -i 'equal cost multi' rfc????.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      34
  grep -i 'equal-cost multi' rfc????.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      18

The hyphen form is used less often recently (May 2008 - Oct 2013).

  grep -i 'equal cost multi' rfc[567]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      27
  grep -i 'equal-cost multi' rfc[567]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      10

  grep -i 'equal cost multi' rfc[67]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
      15
  grep -i 'equal-cost multi' rfc[67]???.txt | grep ECMP \
    | sed 's/:.*//' | uniq | wc -l
       8

I prefer the RFC4928 flavor of this acronym and the above greps show
that it is more widely used in the RFC series.

Curtis

From curtis@ipv6.occnc.com  Tue Jan 21 17:07:59 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FAD1A026D; Tue, 21 Jan 2014 17:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.437
X-Spam-Level: 
X-Spam-Status: No, score=-4.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AE7qLRAMVuBL; Tue, 21 Jan 2014 17:07:53 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 940241A024F; Tue, 21 Jan 2014 17:07:52 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0M17lAq069282; Tue, 21 Jan 2014 20:07:47 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401220107.s0M17lAq069282@maildrop2.v6ds.occnc.com>
To: "Black, David" <david.black@emc.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
In-reply-to: Your message of "Tue, 21 Jan 2014 19:02:33 -0500." <8D3D17ACE214DC429325B2B98F3AE712026F047CC2@MX15A.corp.emc.com>
Date: Tue, 21 Jan 2014 20:07:47 -0500
X-Mailman-Approved-At: Wed, 22 Jan 2014 08:10:33 -0800
Cc: "draft-ietf-mpls-multipath-use.all@tools.ietf.org" <draft-ietf-mpls-multipath-use.all@tools.ietf.org>, "ops-dir@ietf.org" <ops-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 01:07:59 -0000

In message <8D3D17ACE214DC429325B2B98F3AE712026F047CC2@MX15A.corp.emc.com>
"Black, David" writes:
> 
> Curtis,
>  
> > Thanks for the review and for pointing out lack of clarity due to
> > underlying assumptions about the use of RFC 4206 (and perhaps use of
> > RFC 4201 as well for large MPLS LSP over MPLS-TP).
> >
> > Sometimes it is too easy to forget that not all readers are going to
> > be as steeped in MPLS "as deployed today" details as a relatively
> > small number of long time MPLS participants are.
> >
> > Adding a few paragraphs to the introduction and a few concluding
> > paragraphs may significantly improve clarity for people who have not
> > been following MPLS closely for a decade or more without requiring
> > them to read the references and figure out usage details themselves.
> >
> > Please let me know how you feel about the suggested additions to the
> > document.
>  
> Most of them look good - details below.  Many thanks for the prompt and
> comprehensive response.  I have a few more suggestions in what follows
> - anything that I don't comment on below is fine with me.

Thank you for the quick turnaround on this as well.

> -- Introduction
>  
> > There is an underlying assumption in the draft that the reader
> > understands that MPLS-in-MPLS exists today, most commonly but not
> > exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> > means to advertise forward adjacencies (FA) where MPLS-in-MPLS at some
> > level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> > to make use of the management plane, using CLI or NETCONF or the MPLS
> > cross connect MIB to program a multiple label MPLS push operation.
> >
> > If a very experienced reviewer could miss that, then the introduction
> > could be improved by better stating assumptions.  It is also the case
> > that many participants in MPLS, particularly those primarily
> > interested in MPLS-TP, began participation long after RFC 4206 was
> > written and would benefit by better stated assumptions in the intro.
> >
> > I suggest that the following paragraphs be added to the introduction.
>  
> The suggested new paragraphs will definitely improve the introduction.
>  
> -- [A] Summary text in Introduction appears to be wrong.
>  
> > > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > > exception appears to concern the reverse, and Section 4 on carrying MPLS
> > > over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> > > Was the exception intended to be for an MPLS-TP LSP that exceeds the
> > > capacity of any single component link?
>  
> [... snip ...]
>  
> > To answer your question directly: the exception is a very large MPLS
> > LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> > multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> > this is occurring.
>  
> It looks like  my confusion stemmed from the original text only
> discussing only what won't work and referencing a section that
> concerns a different encapsulation order than the one that causes
> the problem.  Including the "MAY NOT" -> "SHOULD NOT" change, I suggest:
>  
> OLD
>    When an MPLS LSP
>    exceeds the capacity of any single component link it MAY be carried
>    by a network using multipath techniques, but MAY NOT be carried by a
>    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
>    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
>    fate sharing constraints and MPLS-TP LM OAM packet ordering
>    constraints (see Section 3.1).
> NEW
>    When an MPLS LSP
>    exceeds the capacity of any single component link it MAY be carried
>    by a network using multipath techniques, but SHOULD NOT be carried by a
>    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
>    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
>    fate sharing constraints and MPLS-TP LM OAM packet ordering
>    constraints (see Section 3.1).  Instead, multiple MPLS-TP LSPs SHOULD
>    be used to carry a large MPLS LSP (see Section 4).

OK.  Good addition.

> -- [B] Section 3.2 needs a summary.
>  
> The proposed summary looks good, and helps with [C], but the phrase
> "access and edge" needs qualification in the following sentence:
>  
>    However access and edge is the least likely to support
>    RFC 6790 in the near term.
>  
> "access and edge" what? e.g., areas of the network? LSRs?

Oh.  Good point.

Core, edge, aggregation, and access are terms commonly used for the
tiers in provider networks.  Core is central, high traffic.  Access is
furthest out with lower traffic (think of subscriber connections for
consumer Internet).

Perhaps I can just change the sentence to:

  However equipment furthest from a provider's network core is the
  least likely to support RFC 6790 in the near term.

I think we all know "core" at this point so furthest from core might
be easier to understand.

> -- [C] Entropy label "sandwich" seems peculiar and at least needs an
>  explanation. 

That was your term.  I didn't propose adding Entropy label "sandwich"
to the text.  I think this is just an excerpt from your prior email as
a marker in following up on it.  Please correct me if I am wrong.

> > The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> > paragraph.
> >
> >    Alternately, the need for requirement MP#1 can be eliminated if
> >    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
> >    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
> >    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
> >    in a deployment support Entropy Label, which may render it
> >    impractical in many deployments.
> >
> > Please not the "Alternately" at the beginning and "impractical in many
> > deployments" at the end.

That should have said "Please note".

> > The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> > above that but assumes knowledge of RFC 6790.  I think the following
> > change within this paragraph would clear things up:
>  
> That change is helpful, but my "sandwich" concern was actually raised
> by text two paragraphs further down:
>  
>    MPLS-TP LSPs can be carried as client LSPs within an MPLS server LSP
>    if an Entropy Label Indicator (ELI) and Entropy Label (EL) is pushed
>    below the server layer LSP label(s) in the label stack, just above
>    the MPLS-TP LSP label entry [RFC6790].
>  
> Read after the "Alternately" paragraph, this text appeared to suggest
> a "sandwich" that would have an ELI/EL pair both above and below the
> MPLS-TP label.  That was clearly not intended, so I suggest inserting
> "When Entropy Label Indicators (ELIs) and Entropy Labels (ELs) are not
> applied by MPLS-TP ingresses," before the start of the first sentence
> above, so that the result is:
> 
>    When Entropy Label Indicator (ELIs) and Entropy Labels (ELs) are
>    not applied by MPLS-TP ingresses, MPLS-TP LSPs can be carried as
>    client LSPs within an MPLS server LSP if an ELI and EL are pushed
>    below the server layer LSP label(s) in the label stack, just above
>    the MPLS-TP LSP label entry [RFC6790].

OK.  I will make that replacement.

> -- [D] Discussion of multipath impacts on MPLS OAM
>  
> > > Section 3.2 discusses OAM, and contains this important
> > > requirement for OAM traffic:
> > >
> > >    An Entropy Label must be used to insure that all of the
> > >    MPLS-TP payload and OAM traffic are carried on the same component,
> > >    except during very infrequent transitions due to load balancing.
> > >
> > > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > > Section 4; that should be added.
> >
> > There is no impact on MPLS OAM traffic.  There are three cases to
> > consider.
> >
> >   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
> >      one link.  MPLS OAM is unaffected and need not use multipath
> >      support in LSP Ping.
> >
> >   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
> >      LSP is carried over one link thanks to the fixed EL value.
> >      MPLS-TP OAM is unaffected.
> >
> >   3.  Where MPLS is carried over MPLS (an existing case) or over
> >       multiple MPLS-TP, the multipath support in LSP Ping (as
> >       imperfect as it may already be) is used and LSP Ping (RFC 4379)
> >       operation is unaffected.
> >
> > If needed something can be added to state the above (maybe with less
> > informal wording).  What is obvious to some people may not be obvious
> > to everyone.  Briefly stating the almost obvious is usually not a bad
> > thing.
>  
> Points 1-3 are useful explanation as complement to the Entropy label
> requirement to correctly handle OAM traffic for the other encapsulation.
>  
> I like your suggestion to add this text as part of a new concluding
> Section 5, and the rest of the proposed conclusion section text looks
> good.
>  
> Thanks,
> --David

Thanks again.

I think we are in agreement and I will edit the document to reflect
your comments shortly.  I think Adrian is AD on this and Loa the
shepard, so I'll wait for a go-ahead from either of them before
submiting the edits.

Curtis


> > -----Original Message-----
> > From: Curtis Villamizar [mailto:curtis@ipv6.occnc.com]
> > Sent: Tuesday, January 21, 2014 2:23 PM
> > To: Black, David
> > Cc: ops-dir@ietf.org; ietf@ietf.org; draft-ietf-mpls-multipath-
> > use.all@tools.ietf.org
> > Subject: Re: OPS-Dir review of draft-ietf-mpls-multipath-use-03
> >
> >
> > In message <8D3D17ACE214DC429325B2B98F3AE712026F047819@MX15A.corp.emc.com>
> > "Black, David" writes:
> > >
> > > I have reviewed this document as part of the operations directorate's
> > > ongoing effort to review all IETF documents being processed by the
> > > IESG.  These comments were written primarily for the benefit of the
> > > operations area directors.  Document editors and WG chairs should treat
> > > these comments just like any other last call comments.
> > >
> > > Summary:
> > > This draft is on the right track but has open issues, described in the
> > review.
> > >
> > > I apologize for this review showing up a couple of days after the end of
> > > IETF Last Call.
> > >
> > > This draft discusses considerations for what are effectively MPLS-in-MPLS
> > > tunnels for multipathing - an LSP carries another LSP, with the inner
> > > (client) LSPs being distributed across multiple outer (server) LSPs that
> > > use different paths.  This draft is motivated by considerations specific
> > > to MPLS-TP that complicate multipathing when one of the two MPLS instances
> > > is MPLS-TP.
> >
> > Skipping to the discussion quite a ways down, there seems to be some
> > confusion about what is being proposed here.  While MPLS-in-MPLS is
> > being used, no new form of MPLS-in-MPLS is being proposed.
> >
> > There is an underlying assumption in the draft that the reader
> > understands that MPLS-in-MPLS exists today, most commonly but not
> > exclusively in the form of RFC 4206 hierarchy.  RFC 4206 provides a
> > means to advertise forward adjacencies (FA) where MPLS-in-MPLS at some
> > level of Packet Switch Capable (PSC) hierarchy.  It is also possible
> > to make use of the management plane, using CLI or NETCONF or the MPLS
> > cross connect MIB to program a multiple label MPLS push operation.
> >
> > If a very experienced reviewer could miss that, then the introduction
> > could be improved by better stating assumptions.  It is also the case
> > that many participants in MPLS, particularly those primarily
> > interested in MPLS-TP, began participation long after RFC 4206 was
> > written and would benefit by better stated assumptions in the intro.
> >
> > I suggest that the following paragraphs be added to the introduction.
> >
> >    MPLS LSPs today are able to function as a server layer and carry
> >    client MPLS LSPs.  When control plane signaling is used, forwarding
> >    adjacency (FA) advertisements are used to inform the set of LSR of
> >    Packet Switching Capable (PSC) LSP within the MPLS topology
> >    [RFC4206].  Client MPLS LSP at a higher layer (lower PSC number)
> >    may signal their intention to use PSC LSP as hops in the RSVP-TE
> >    Explicit Route Object (ERO).  LSR with no explicit support for RFC
> >    4206 see the PSC LSP as ordinary links and therefore use them.
> >
> >    An MPLS LSP that has been set up using RSVP-TE appears to its
> >    ingress LSR as a viable IP next hop to a distant LSR.  If LDP is
> >    used and bidirectional RSVP-TE LSP connectivity is available, then
> >    LDP signaling can be set up among the RSVP-TE LSP endpoints and LDP
> >    can make use of the RSVP-TE LSP as an LDP hop.  This is another
> >    form of existing MPLS-in-MPLS use.
> >
> >    MPLS LSPs may also make use of hierarchy that is configured through
> >    the management plane rather than signaled using RSVP-TE.
> >
> >    These existing forms of MPLS-in-MPLS may traverse multipath hops
> >    such as Ethernet LAG [IEEE802.1AX] or MPLS Link Bundling [RFC4201].
> >    MPLS-TP brings with it a new set of requirements not considered in
> >    past deployments of the various forms of MPLS-in-MPLS where
> >    multipath was in use.  This document merely discusses use of
> >    existing forwarding and protocol mechanisms that can support the
> >    case where either the client layer LSPs or the server layer LSPs
> >    are MPLS-TP and where multipath is used.
> >
> > If there are no objections I will add these paragraphs.
> >
> > Now on to the specific comments.
> >
> > > I consider the following to be open issues that need attention (each
> > > letter is used to tag the issue in the text that follows - [B] occurs
> > > multiple times, as there are multiple aspect to that issue):
> > >
> > > [A] Summary text in Introduction appears to be wrong.
> > > [B] Section 3.2 needs a summary.
> > > [C] Entropy label "sandwich" seems peculiar and at least needs an explanation.
> > > [D] Discussion of multipath impacts on MPLS OAM should be added to Section
> > 4.
> > >
> > > --- Comments on draft text
> > >
> > > [A] Section 1 (Introduction) 2nd paragraph:
> > >
> > >    RFC 5654 requirement 33 requires the capability to carry a client
> > >    MPLS-TP or MPLS layer over a server MPLS-TP or MPLS layer [RFC5654].
> > >    This is possible in all cases with one exception.  When an MPLS LSP
> > >    exceeds the capacity of any single component link it MAY be carried
> > >    by a network using multipath techniques, but MAY NOT be carried by a
> > >    single MPLS-TP LSP due to the inherent MPLS-TP capacity limitation
> > >    imposed by MPLS-TP Operations, Administration, and Maintenance (OAM)
> > >    fate sharing constraints and MPLS-TP LM OAM packet ordering
> > >    constraints (see Section 3.1).
> > >
> > > Section 3.1 concerns carrying MPLS-TP over MPLS, whereas the above
> > > exception appears to concern the reverse, and Section 4 on carrying MPLS
> > > over MPLS-TP allows for MPLS LSPs that exceed component link capacity.
> > > Was the exception intended to be for an MPLS-TP LSP that exceeds the
> > > capacity of any single component link?
> >
> > There is no problem today with MPLS LSP carried by MPLS-TP LSP except
> > the existing case where MPLS LSP capacity is too big.  For example, a
> > 500 Gb/s LSP is possible today carried over N x 100 Gb/s or N x 10
> > Gb/s multipath links but could not be carried over a single MPLS-TP
> > LSP which would be limited to a single 100 Gb/s or 10 Gb/s link.  So
> > the exception is where the MPLS LSP is too big to fit in any possible
> > single MPLS-TP LSP.
> >
> > To answer your question directly: the exception is a very large MPLS
> > LSP can't be carried by a single MPLS-TP LSP.  The solution is to use
> > multiple MPLS-TP LSP.  The MPLS-TP LSR need not be not "aware" that
> > this is occurring.
> >
> > > Also, "MAY NOT" is not an RFC 2119 term (for good reason - it's equivalent
> > > to "MAY OR MAY NOT").  I think "cannot" was intended here, but "MUST NOT"
> > > is another possibility.
> >
> > Good point.  I suggest we replace the MAY NOT with SHOULD NOT.  Many
> > people would insist that it should be MUST NOT, but in reality
> > networks SHOULD NOT be congested but sometimes they are.
> >
> > > [B] Section 3.2 contains a lot of useful details, but it could really use
> > > a summary at the end on the options and recommendations for meeting the
> > > four requirements (this summary could be a new Section 3.3).  It's a bit
> > > difficult to discern what's going on, as I had to read this section more
> > > than once in order to discern the following:
> >
> > OK.  A Summary paragraph can be added.  See below.  Perhaps conclusion
> > section can be added.  See far below.
> >
> > > [C] In Section 3.2, use of an MPLS entropy label to meet requirement MP#1
> > > requires that it be "below the MPLS-TP label" whereas, to meet requirement
> > > MP#2, the MPLS entropy label needs to be "just above the MPLS-TP LSP label".
> > > This combination appears to suggest "sandwiching" the MPLS-TP label between
> > > two entropy labels that effectively carry the same information (albeit,
> > > applied and removed at different places in the network) - was that intended?
> > > This is important, as there seems to be no reasonable alternative
> > > to the entropy label for meeting requirement MP#2, and the draft's
> > > alternative to the entropy label for meeting requirement MP#1 is "some form
> > > of configuration" - the entropy label would seem to be preferred to that
> > > based on my reading of this draft and the comment in RFC 5706 section 2.2
> > > that "Anything that can be configured can be misconfigured."
> >
> > The "MPLS MPLS-TP ELI EL" sandwich is suggested in the following
> > paragraph.
> >
> >    Alternately, the need for requirement MP#1 can be eliminated if
> >    every MPLS-TP LSP created by an MPLS-TP ingress makes use of an
> >    Entropy Label Indicator (ELI) and Entropy Label (EL) below the
> >    MPLS-TP label [RFC6790].  This would require that all MPLS-TP LSR
> >    in a deployment support Entropy Label, which may render it
> >    impractical in many deployments.
> >
> > Please not the "Alternately" at the beginning and "impractical in many
> > deployments" at the end.
> >
> > The other sandwich "MPLS ELI EL MPLS-TP" is described two paragraphs
> > above that but assumes knowledge of RFC 6790.  I think the following
> > change within this paragraph would clear things up:
> >
> >  OLD
> >
> >    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
> >    and Entropy Label (EL) are added to the label stack [RFC6790].  For
> >    those client LSP that are MPLS-TP LSP, a single EL value must be
> >    chosen.  For those client LSP that are MPLS LSP, per packet entropy
> >    below the top label must, for practical reasons, be used to
> >    determine the entropy label value.
> >
> >  NEW
> >
> >    MPLS server layer LSP ingress LSR an Entropy Label Indicator (ELI)
> >    and Entropy Label (EL) are added to the label stack by the midpoint
> >    LSR for the client MPLS-TP LSP, at the ingress of the MPLS LSP
> >    [RFC6790].  For those client LSP that are MPLS-TP LSP, a single EL
> >    value must be chosen.  For those client LSP that are MPLS LSP, per
> >    packet entropy below the top label must, for practical reasons, be
> >    used to determine the entropy label value.  The resulting label
> >    stack contains the server MPLS LSP label, ELI, EL and the client
> >    LSP label.
> >
> > The above rewording is simply more explicit about the label stack
> > order and which LSR puts the ELI and EL in the label stack.
> >
> > > [B] A summary of requirements for implementation and deployment at the end
> > > of Section 3.2 would have made this much more obvious.  That should be
> > > provided in addition to addressing the above question about duplicate use
> > > of the MPLS entropy label.
> >
> > The following summary can be added to the end of Section 3.2:
> >
> >    Two methods of adding an Entropy Label are described above.  The
> >    MPLS-TP ingress must have a means to determine which links can
> >    support MPLS-TP in selecting a path (MP#4).  Administrative
> >    attributes can satisfy that requirement.  If the MPLS-TP LSR is
> >    capable of adding ELI/EL to the label stack, this method is
> >    preferred.  However access and edge is the least likely to support
> >    RFC 6790 in the near term.  For portions of the topology where an
> >    MPLS-TP is carried within a server layer MPLS LSP the ingress of
> >    the server layer MPLS LSP can add ELI/EL using a fixed EL value per
> >    client LSP, except those known not to require MPLS-TP treatment.
> >    There are numerous ways to determine which client LSP are MPLS-TP
> >    LSP and which are not.  While this determination is out of scope
> >    and will vary among deployments, configuration or the presence of
> >    specific attribute affinities in RSVP-TE signaling are among the
> >    likely means to do so.
> >
> > If there are no objections I will add the above paragraph.
> >
> > > --- Relevant Q&A based on RFC 5706 Appendix A
> > >
> > > I'm omitting management concerns, as both MPLS and MPLS-TP have extensive
> > > management infrastructure, and this draft's notion of stacking LSPs so
> > > that one instance of MPLS (or MPLS-TP) can be a server to (i.e., carry)
> > > another is not novel to this draft.
> > >
> > > A.1.1.  Has deployment been discussed?
> > >
> > > [B] Yes, although Section 3.2 is weak on deployment requirements (some of
> > > which are implementation requirements) and could use a summary.
> >
> > The use of RFC 4206 is assumed throughout the discussion of signaling
> > in section 3.2.  This assumption is made more clear by suggested
> > additions to the introduction.
> >
> > > A.1.2.  Has installation and initial setup been discussed?
> > >
> > > No, although because this draft reuses existing functionality in different
> > > configurations, this really reduces to the A.1.9 configuration question
> > > below.  In practice, quite a bit of operator knowledge and insight is
> > > required to get initial setup right, e.g., as traffic engineering LSPs to
> > > avoid congestion problems (needed to meet requirement MP#3) requires
> > > significant knowledge of network structure and expected traffic flows.
> > > This should be obvious to anyone who works w/MPLS, but it's probably
> > > worth stating for completeness.
> >
> > FA advertisements defined in RFC 4206 make it possible for ingress to
> > signal viable paths.  Either the use of Ethernet Link Aggregation or
> > MPLS Link bundling using the all-ones component link (RFC 4201) allows
> > the total capacity of a multipath to be advertised.  Meeting the
> > requirement to balance traffic over the component links in a multipath
> > (MP#3) is then a local matter and requires no further signaling
> > extensions.
> >
> > > A.1.6.  Have suggestions for verifying correct operation been discussed?
> > >
> > > Yes and no.  Section 3.2 discusses OAM, and contains this important
> > > requirement for OAM traffic:
> > >
> > >    An Entropy Label must be used to insure that all of the
> > >    MPLS-TP payload and OAM traffic are carried on the same component,
> > >    except during very infrequent transitions due to load balancing.
> > >
> > > [D] OTOH, there is no discussion of OAM traffic for the MPLS LSP in
> > > Section 4; that should be added.
> >
> > There is no impact on MPLS OAM traffic.  There are three cases to
> > consider.
> >
> >   1. Where MPLS is carried over a single MPLS-TP all traffic flows on
> >      one link.  MPLS OAM is unaffected and need not use multipath
> >      support in LSP Ping.
> >
> >   2. Where MPLS-TP is carried over MPLS, all traffic for that MPLS-TP
> >      LSP is carried over one link thanks to the fixed EL value.
> >      MPLS-TP OAM is unaffected.
> >
> >   3.  Where MPLS is carried over MPLS (an existing case) or over
> >       multiple MPLS-TP, the multipath support in LSP Ping (as
> >       imperfect as it may already be) is used and LSP Ping (RFC 4379)
> >       operation is unaffected.
> >
> > If needed something can be added to state the above (maybe with less
> > informal wording).  What is obvious to some people may not be obvious
> > to everyone.  Briefly stating the almost obvious is usually not a bad
> > thing.  Please tell me if a small subsection on "Imopact on MPLS and
> > MPLS-TP OAM" is needed.
> >
> > Note that the limitations of LSP Ping are currently being discussed in
> > the MPLS WG in the context of extensions to LSP Ping to better support
> > Entropy Label.  A few limitations not related to EL may get fixed in
> > the process.
> >
> > > A.1.9.  Is configuration discussed?
> > >
> > > [B] Not much. Configuration is required to meet requirements MP#3 and MP#4,
> > > and is one of the options for MP#1.  A summary of what has to be configured
> > > as part of the summary at the end of Section 3.2 would be a good idea.
> >
> > Perhaps a worked example appendix could be added but I don't think
> > this is common and may not be necessary with some of the
> > clarifications suggested so far.
> >
> > > A.2.* [skipped, see above]
> > >
> > > A.3 Documentation
> > >
> > > There's quite a bit of operational material contained in this draft; a
> > > separate section on operations and management considerations would not
> > > be appropriate.
> > >
> > > There is a useful implementation status section which appears to imply
> > > that MPLS-TP over MPLS is not currently deployable due to absence of
> > > entropy label support, and because deployed MPLS equipment does not
> > > generally support multipathing.  Nonetheless, data center experience
> > > indicates significant value and widespread use of multipathing based
> > > on link aggregation and ECMP; corresponding benefits can be expected
> > > for use of multipathing in the Internet beyond data centers.
> >
> > If you would like I can add a conclusion section as Section 5 with
> > these paragraphs:
> >
> >    MPLS equipment deployed in the core currently supports multipath.
> >    For large service providers, core LSR must support some form of
> >    multipath to be deployable.  Deployed MPLS access and edge
> >    equipment is often oblivious to the use of multipath in the core.
> >    It is expected that at least first generation MPLS-TP equipment
> >    will be oblivious to the use of multipath in the core.  This first
> >    generation MPLS-TP equipment is deployable in a core using
> >    multipath, with no adverse impact to RSVP-TE signaling, if the edge
> >    equipment can support administrative attributes (RFC 3209) and the
> >    core equipment can support ELI/EL and put a per-LSP fixed EL value
> >    on any LSP that indicates a particular attribute affinity or can
> >    identify client MPLS-TP LSP through some other means.
> >
> >    There are no issues carrying MPLS over MPLS-TP, except when the
> >    MPLS LSP is too big to be carried by a single MPLS-TP LSP.  Most
> >    MPLS core equipment and some edge equipment can configure an MPLS
> >    Link Bundle [RFC4201] over multiple component links where the
> >    component links are themselves MPLS LSP.  This existing capability
> >    can be used to carry large MPLS LSP and overcome the limited
> >    capacity of any single server layer MPLS-TP LSP.
> >
> > If this conclusion section is added, then the three bullets above
> > regarding impact on OAM can be put there.  The three bullets can be
> > added as follows:
> >
> >    MPLS OAM and MPLS-TP OAM are unaffected in the following cases
> >    proposed in this document:
> >
> >      1. Where MPLS is carried over a single MPLS-TP all traffic flows
> >         on one link.  MPLS OAM is unaffected and need not use
> >         multipath support in LSP Ping.
> >
> >      2. Where MPLS-TP is carried over MPLS, all traffic for that
> >         MPLS-TP LSP is carried over one link thanks to the fixed EL
> >         value.  MPLS-TP OAM is unaffected.
> >
> >      3.  Where MPLS is carried over MPLS (an existing case) or over
> >          multiple MPLS-TP, the multipath support in LSP Ping is used
> >          and LSP Ping (RFC 4379) operation is unaffected.
> >
> > I think adding the above as a conclusion section as Section 5 would
> > improve clarity and therefore is worth doing.
> >
> > > --- Editorial comments/nits:
> > >
> > > - Section 3.1, after RFC 5960 quotes:
> > >
> > >    [RFC5960] paragraph 3 requires that packets within a specific ordered
> > >
> > > Insert "Section 3.1.1.", before "paragraph 3" and likewise for "paragraph 6"
> > > later in the same paragraph in the draft.
> >
> > GenArt review caught this.  Done.
> >
> > > - Section 3.2, requirement MP#3:
> > >
> > >    MP#3  It SHOULD be possible to insure that MPLS-TP LSPs will not be
> > >
> > > "insure" -> "ensure" or "assure".  Surely this draft does not envision
> > > operators taking out insurance policies on MPLS TP LSP behavior ;-).
> >
> > Good catch.  I think "ensure" is the right word.
> >
> > > - Section 3.2, last paragraph on p.8:
> > >
> > >    An MPLS-TP LSP may not traverse multipath links on the path where
> > >    MPLS-TP forwarding requirements cannot be met.
> > >
> > > "may not" is meaningless - I believe "MUST NOT" was intended here.
> >
> > I suggested SHOULD NOT above.
> >
> > > - Section 4, middle of 3rd para:
> > >
> > > Editorial suggestions for clarity:
> > >
> > > OLD
> > >             For those LSP that are larger than component link
> > >     capacity, their capacity are not integer multiples of convenient
> > >     capacity increments such as 10Gb/s.
> > > NEW
> > >             For those LSPs that are larger than a component link
> > >    capacity, the LSP capacities need not be (and often are not)
> > >    integer multiples of convenient capacity increments such as 10Gb/s.
> >
> > Good suggestion.  GenArt review suggested adding "generally" making
> > the statement read "their capacity are generally not integer
> > multiples".  Your suggested rewording may be more clear.
> >
> > Also "10Gb/s" should be "10 Gb/s".
> >
> > > In particular, "are not" seems wrong, as the "integer multiples"
> > > case is possible, so I changed "are not" to "need not be (and often
> > > are not)" in the suggested new text.
> > >
> > > Thanks,
> > > --David
> > > ----------------------------------------------------
> > > David L. Black, Distinguished Engineer
> > > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > > david.black@emc.com        Mobile: +1 (978) 394-7754
> > > ----------------------------------------------------
> >
> > Thanks for the review and for pointing out lack of clarity due to
> > underlying assumptions about the use of RFC 4206 (and perhaps use of
> > RFC 4201 as well for large MPLS LSP over MPLS-TP).
> >
> > Sometimes it is too easy to forget that not all readers are going to
> > be as steeped in MPLS "as deployed today" details as a relatively
> > small number of long time MPLS participants are.
> >
> > Adding a few paragraphs to the introduction and a few concluding
> > paragraphs may significantly improve clarity for people who have not
> > been following MPLS closely for a decade or more without requiring
> > them to read the references and figure out usage details themselves.
> >
> > Please let me know how you feel about the suggested additions to the
> > document.
> >
> > Curtis


From mls.ietf@gmail.com  Wed Jan 22 07:57:01 2014
Return-Path: <mls.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 849181A02D9; Wed, 22 Jan 2014 07:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_ABOUTYOU=0.5, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKGeZ9jXTq0I; Wed, 22 Jan 2014 07:56:57 -0800 (PST)
Received: from mail-ea0-x235.google.com (mail-ea0-x235.google.com [IPv6:2a00:1450:4013:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 007501A02D5; Wed, 22 Jan 2014 07:56:56 -0800 (PST)
Received: by mail-ea0-f181.google.com with SMTP id m10so4761860eaj.12 for <multiple recipients>; Wed, 22 Jan 2014 07:56:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=dIghn2bh5Hftkq+R9GKQ8MqqfVq/aLsaUGxIeJ1ZJNU=; b=bE2sqOcCYq50JjzCEkFz8sCUcozWZobu52d2VzL1YucMiwU6+sE0Q3upts8al57aYw a+6Bc2AFRE7nqKC9jVW7ztYd4QplJoAwKzo35h3Q5HdtzP5E1QF46AgcDqxkUsLK8UtT 3H3lG9lQvnMgYE/xaIG9YILSDCq2JarrpsjsR/ZwGyMbsJEewUReBx3SDZJduCJJOywL ihbvUCEXBQU1q4XNT+LnVBK/D9oh6DzNTwG3Z4UUWy/8VrGA/XtXK2KaEct8a0X6lU+T f5HfN/h/1pcTj1fbG0ODgIZyJ6vBAFpk5A0ReK3bgNUgVRH8EPkz9Sle4PVFx/fMxqag KrMg==
X-Received: by 10.15.36.65 with SMTP id h41mr2306940eev.0.1390406215900; Wed, 22 Jan 2014 07:56:55 -0800 (PST)
Received: from [192.168.178.53] (port-92-202-18-73.dynamic.qsc.de. [92.202.18.73]) by mx.google.com with ESMTPSA id d43sm28517526eeo.12.2014.01.22.07.56.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jan 2014 07:56:54 -0800 (PST)
Message-ID: <52DFEA45.6040701@gmail.com>
Date: Wed, 22 Jan 2014 16:56:53 +0100
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401171719.s0HHJqHY062965@maildrop2.v6ds.occnc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 22 Jan 2014 08:16:15 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 15:57:01 -0000

Hi Curtis,

I want to make an important observation below:

On 01/17/2014 06:19 PM, Curtis Villamizar wrote:
> Lars,
>
> We seem to be in an endless loop here.
>
> You have made your assertions about your desire to uphold the purity
> of any new UDP applications and adhere to the BCP you wrote.
>
> You appear to be very nearly alone in this argument and certainly no
> one that works with MPLS is siding with you.

Lars is not alone but took the time and energy to comment on the draft.

Lars' arguments are just right and need to be addressed.

Regards,

   Martin

Transport Area Director


From jnc@mercury.lcs.mit.edu  Wed Jan 22 09:29:33 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93B61A011B; Wed, 22 Jan 2014 09:29:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctB-qpFkctrB; Wed, 22 Jan 2014 09:29:31 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 17D701A0119; Wed, 22 Jan 2014 09:29:30 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 3D31A18C13B; Wed, 22 Jan 2014 12:29:30 -0500 (EST)
To: ietf@ietf.org, mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Message-Id: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu>
Date: Wed, 22 Jan 2014 12:29:30 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 17:29:33 -0000

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

    > I would like the document to specify at the very least a circuit
    > breaker mechanism, that stops the tunneled traffic if severe packet
    > loss is detected along the path.

I think people are looking at this from the wrong perspective, focusing in on
UDP and what its specs say, and not on the larger engineering picture.

Envision the following 4 (or more) scenarios for one Border Tunneling Routing
(BTR), BTR A, to send packets to another BTR, BTR B, on the path from ultimate
source S (somewhere before BTR A) to destination D (somewhere after BTR B).

- Plain IP
- Some existing encapsulation like GRE
- A new, custom encapsulation
- Encapsulation using UDP

What you seem to be claiming is that in case 4 we need to have congestion
detection and response at the intermediate forwarding node BTR A - but it
would not be required in cases 1-3? This makes no sense.

Even better, suppose that BTR A implements _both_ one of the first three,
_and_ UDP encapsulation. If its response to UDP congestion on the path to BTR
B is to.... switch to a _different_ encapsulation for traffic to that
intermediate forwarding node, one for which it's not required to detect and
respond to congestion, did that really help?

Similarly, if people doing tunnels ditched UDP in favor of some other
encapsulation (assuming they could find something that would get through as
many filters as UDP does, would have the same load-spreading properties that
UDP does, etc, etc - or maybe not, if that's the price they have to pay for
being free of the grief they are getting because they are using UDP) - would
that do anything at all for any potential congestion from their traffic? No,
it would still be there, obviously.


Look, the current architectural model of the Internet for dealing with
congestion is that the _application endpoints_ have to notice it, and slow
down. Intermediate forwarding nodes don't have any particular responsibility
other than to drop packets if they have too many.

You are quite right that if we take some application that doesn't detect and
respond to congestion (perhaps because it was written for a local environment,
and some bright spark is tunnelling that L2 protocol over the Internet), that
can cause problems - but that's because we are violating the Internet's
architectural assumption on how/who/where congestion control is done.

I don't have any particularly brilliant suggestions on how to respond to
situations in which applications don't detect and respond to congestion.
Architecturally, if we are to keep to the existing congestion control scheme
(endpoints are responsible), the responsibilty has to go back to the ultimate
source of the traffic somehow...

But saying that _intermediate forwarding nodes_ have to detect down-stream
congestion, and respond, represents a fundamental change to the Internet's
architecture for congestion control.

	Noel

From lars@netapp.com  Wed Jan 22 09:55:32 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB8031A0188; Wed, 22 Jan 2014 09:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7BtcWX0YP8-6; Wed, 22 Jan 2014 09:55:31 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id A8D2E1A0199; Wed, 22 Jan 2014 09:55:24 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,701,1384329600";  d="asc'?scan'208";a="97521704"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 22 Jan 2014 09:55:24 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Wed, 22 Jan 2014 09:55:24 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPF5eBFyKjVtdEy02x6qUpK40JLJqRjSoA
Date: Wed, 22 Jan 2014 17:55:23 +0000
Message-ID: <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu>
In-Reply-To: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.118]
Content-Type: multipart/signed; boundary="Apple-Mail=_8A1F21FB-58D7-4707-982F-B65299EABE49"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 17:55:32 -0000

--Apple-Mail=_8A1F21FB-58D7-4707-982F-B65299EABE49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2014-1-22, at 18:29, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
> Envision the following 4 (or more) scenarios for one Border Tunneling =
Routing
> (BTR), BTR A, to send packets to another BTR, BTR B, on the path from =
ultimate
> source S (somewhere before BTR A) to destination D (somewhere after =
BTR B).
>=20
> - Plain IP
> - Some existing encapsulation like GRE
> - A new, custom encapsulation
> - Encapsulation using UDP
>=20
> What you seem to be claiming is that in case 4 we need to have =
congestion
> detection and response at the intermediate forwarding node BTR A - but =
it
> would not be required in cases 1-3? This makes no sense.

I'm not saying that. I'm saying that for every tunnel that can extend =
the reach of not-congestion-controlled traffic, e.g., some L2 traffic, =
over the wider Internet, we have a potential problem.

For plain IP as well as encapsulations that use IP protocol numbers that =
are different than UDP, TCP and I guess ICMP, that danger is somewhat =
mitigated, because such traffic typically dies at the next NAT or =
firewall (unless that has been specifically provisioned, which is then =
also OK). So there can be harm, but it will be limited to some segment =
of the network, hopefully the segment that the entity who performed the =
encapsulation manages.

UDP and TCP traverse most NATs and firewalls, if the directionality of =
the flow establishment is as expected by the middlebox ("inside" to =
"outside"). That means that UDP-encapsulated L2 traffic has a much wider =
reach - an Internet-wide reach. That's the fundamental difference to the =
other cases.

> Even better, suppose that BTR A implements _both_ one of the first =
three,
> _and_ UDP encapsulation. If its response to UDP congestion on the path =
to BTR
> B is to.... switch to a _different_ encapsulation for traffic to that
> intermediate forwarding node, one for which it's not required to =
detect and
> respond to congestion, did that really help?

It won't solve the problem, but these other encapsulations have more =
limited reach, and as such the potential for damage is lessened.

> Similarly, if people doing tunnels ditched UDP in favor of some other
> encapsulation (assuming they could find something that would get =
through as
> many filters as UDP does, would have the same load-spreading =
properties that
> UDP does, etc, etc - or maybe not, if that's the price they have to =
pay for
> being free of the grief they are getting because they are using UDP) - =
would
> that do anything at all for any potential congestion from their =
traffic? No,
> it would still be there, obviously.

Depends on the reach of that encapsulation. If it requires manual =
configuration of middleboxes to make it traverse (like GRE would), that =
danger is lessened. If it traversed such middleboxes by default, as UDP =
does, it has the same issues.

> Look, the current architectural model of the Internet for dealing with
> congestion is that the _application endpoints_ have to notice it, and =
slow
> down. Intermediate forwarding nodes don't have any particular =
responsibility
> other than to drop packets if they have too many.

Right. =46rom the viewpoint of the Internet, the *encapsulator* is that =
application endpoint. That's what the whole concept of a tunnel is =
about.

> You are quite right that if we take some application that doesn't =
detect and
> respond to congestion (perhaps because it was written for a local =
environment,
> and some bright spark is tunnelling that L2 protocol over the =
Internet), that
> can cause problems - but that's because we are violating the =
Internet's
> architectural assumption on how/who/where congestion control is done.

Exactly.=20

> I don't have any particularly brilliant suggestions on how to respond =
to
> situations in which applications don't detect and respond to =
congestion.
> Architecturally, if we are to keep to the existing congestion control =
scheme
> (endpoints are responsible), the responsibilty has to go back to the =
ultimate
> source of the traffic somehow...

No, it doesn't. That responsibility lies with the entity that injects =
that packet into the Internet, which is the encapsulator. For the rest =
of the Internet, the encapsulator is the sending application of the UDP =
traffic. Without the encapsulator, that traffic would not exist on the =
Internet.

> But saying that _intermediate forwarding nodes_ have to detect =
down-stream
> congestion, and respond, represents a fundamental change to the =
Internet's
> architecture for congestion control.

And here's the fallacy: UDP encapsulators are forwarding nodes *only* =
from the viewpoint of the final endpoints. =46rom the viewpoint of the =
rest of the Internet, they are traffic *sources*, not *forwarders*.=20

Lars

--Apple-Mail=_8A1F21FB-58D7-4707-982F-B65299EABE49
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuAGCtZcnpRveo1xAQKpqQQAsy2+qTUBiH1uxeE2Z5H2CcqVCmKNEMxf
snsKO+JwL36uQE+GpMUk59FWmQwI8qpOwx5cONDddNfGWcKVdIVRt4IxwNs5XA4/
67oPhuPTMMAHysRw5YgK0wTWitMZQ0iuuogcL2u2x/S3i1VxLIHj5dtP/4+gvedt
QbCu9sKKu6Y=
=EvAi
-----END PGP SIGNATURE-----

--Apple-Mail=_8A1F21FB-58D7-4707-982F-B65299EABE49--

From jnc@mercury.lcs.mit.edu  Wed Jan 22 10:33:20 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 208111A0174; Wed, 22 Jan 2014 10:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id en5IS1-ZKUOD; Wed, 22 Jan 2014 10:33:17 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 139781A018B; Wed, 22 Jan 2014 10:32:37 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 0FE0918C144; Wed, 22 Jan 2014 13:32:37 -0500 (EST)
To: ietf@ietf.org, mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Message-Id: <20140122183237.0FE0918C144@mercury.lcs.mit.edu>
Date: Wed, 22 Jan 2014 13:32:37 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 18:33:20 -0000

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

    > that danger is somewhat mitigated, because such traffic typically dies
    > at the next NAT or firewall (unless that has been specifically
    > provisioned, which is then also OK).

But such packets/protocols are usually not "provisioned" (i.e. specific
resources set aside to carry them). Generally, they are merely "allowed" - and
one then still has the potential of congestion at that device.

    > Depends on the reach of that encapsulation. .. If it traversed such
    > middleboxes by default, as UDP does, it has the same issues.

Exactly. The problem is not specific to UDP. So why is the discussion
(seemingly) trying to solve it in a UDP-specific way?

I repeat: even if people were _not_ using UDP encapsulations, the exact same
problem (of potential congestion caused by non-congestion-compliant
applications) would still exist. Switching to a different encapsulation method
is not going to get rid of _any_ potential congestion - not one packet's
worth.

So can we just drop all mention of UDP, since it's irrelevant to the _real_
problem?

    >> But saying that _intermediate forwarding nodes_ have to detect
    >> down-stream congestion, and respond, represents a fundamental change
    >> to the Internet's architecture for congestion control.

    > And here's the fallacy: UDP encapsulators are forwarding nodes *only*
    > from the viewpoint of the final endpoints. From the viewpoint of the
    > rest of the Internet, they are traffic *sources*, not *forwarders*.

I present two boxes. In one, a packet comes in, and after some manipulation of
headers, the packet goes out. In the other, a packet comes in, and after some
header changes, the packet goes out. You're trying to tell me that,
architecturally, one _is_ an intermediate forwarding node (which doesn't have
to detect downsteam congestion, and respond), and the other is not (and so
does have to)?

And I repeat: mandating that nodes which are forwarding nodes have to detect,
and respond to, downsteam congestion caused by non-congestion-compliant
traffic flowing _through_ them is a fundamental change to the Internet's
existing framework for congestion control.

Not that I'm opposed to such a change (it might make sense, I'd have to go
away and think about it), but if we're going to make such an architectural
change, i) we should do so explicitly, and ii) such a requirement should fall
on _all_ packet forwarding nodes - including regular routers, since they could
equally possibly be given non-congestion-compliant traffic to forward.

	Noel

From hartmans@mit.edu  Wed Jan 22 15:02:13 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAEA1A0253 for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 15:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dG-JsNmZDuCn for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 15:02: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 1B73F1A0242 for <ietf@ietf.org>; Wed, 22 Jan 2014 15:02:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 9E58520647; Wed, 22 Jan 2014 17:59:20 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBIQASwEoOwY; Wed, 22 Jan 2014 17:59:19 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed, 22 Jan 2014 17:59:19 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 71BA9836D4; Wed, 22 Jan 2014 18:02:08 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Jari Arkko <jari.arkko@ericsson.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com>
Date: Wed, 22 Jan 2014 18:02:08 -0500
In-Reply-To: <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> (Jari Arkko's message of "Wed, 22 Jan 2014 22:48:41 +0000")
Message-ID: <tslvbxb62of.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Sam Hartman <hartmans-ietf@mit.edu>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 23:02:13 -0000

>>>>> "Jari" == Jari Arkko <jari.arkko@ericsson.com> writes:

    Jari> Sam, FWIW my view is pretty much what Dave and Scott noted. I
    Jari> don't think the change weakens the draft's message: We'll take
    Jari> the issue seriously.

I disagree for the following reasons.
When we remove text saying that WGs need to be able to justify  their
decisions, we're saying that we do not have consensus on that statement.

If we do not have agreement that WGs should be able to justify their
choices with regard to perpass mitigation, then I think that we are not
actually  going to do what is necessary to approach the issue.

Here are concrete examples of what I expect to be able to do:

* I should be able to ask NVO3 to explain why they chose an architecture
  that either does or does not support encryption of data plane traffic
  while reviewing that architecture.

* If we were doing DDS/NAPTR work today I should be able to ask whether
  confidentiality is a requirement and if so why DNS is an appropriate
  substrate.

* If the working group I chair (kitten) were to actually work on an
  administration protocol to manifest our information model for
  Kerberos, I should be able to ask about privacy implications of that
  protocol and whether Kerberos is an appropriate substrate.

To me, by removing text that WGs need to be able to justify these sorts
of decisions we're saying that we don't have consensus that such
questions would need to be justified during a review.

If you think those are reasonable, then I'd strongly prefer to spend the
time to figure out what we actually mean.  Come up with text that makes
it sure that such questions are reasonable while ruling out the things
people are worried about.

If we do not think  that WGs should be required to justify these
positions, then I strongly object to a claim that we have chosen to
mitigate perpass attacks because I believe that claim is meaningless
without actually being able to get WGs to justify these decisions while
doing architectural review.

From lear@cisco.com  Wed Jan 22 23:30:01 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 362501A0220 for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 23:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvLySoJvphxF for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 23:29:58 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7446D1A0135 for <ietf@ietf.org>; Wed, 22 Jan 2014 23:29:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3099; q=dns/txt; s=iport; t=1390462198; x=1391671798; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=F7KrugpZU/hY0Hnh24y6dHR5avUDDqEQKs4e5yI3IuQ=; b=mU5QEQlXb+xDWnXQU6zJbNniBKIPXP12zeJf+/Wc1jlEHuFMPeX/yuk8 wsiZyfRx862aWTdHgBGVU6ngaK5UGeIsBybxsDhLvNzin13pztBqc8TyB /wCBuyyt3mFNKq/eUoGNLOfqcJlmwLmB57XUnvDVuPbtnFXTWwSu3yhXm U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFADjE4FKQ/khM/2dsb2JhbABbDoJ+hAy4dIENFnSCJgEBBCNVARALBB0WCwICCQMCAQIBRQYBDAEHAQGIAahknCEXjnwHgm+BSQSYIpIYgm5AOw
X-IronPort-AV: E=Sophos;i="4.95,704,1384300800"; d="scan'208,217";a="4051943"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 23 Jan 2014 07:29:57 +0000
Received: from dhcp-wlsn01-vlan250-10-147-28-17.cisco.com (dhcp-wlsn01-vlan250-10-147-28-17.cisco.com [10.147.28.17]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0N7TuI3024055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Jan 2014 07:29:56 GMT
Message-ID: <52E0C4F4.3090706@cisco.com>
Date: Thu, 23 Jan 2014 08:29:56 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>, Jari Arkko <jari.arkko@ericsson.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu>
In-Reply-To: <tslvbxb62of.fsf@mit.edu>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------040301060702050506010109"
Cc: IETF discussion list <ietf@ietf.org>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 07:30:01 -0000

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


On 1/23/14, 12:02 AM, Sam Hartman wrote:

> * If we were doing DDS/NAPTR work today I should be able to ask whether
>   confidentiality is a requirement and if so why DNS is an appropriate
>   substrate.

And herein lies the problem.  It would depend on the record's
application, and how information was released that couldn't otherwise be
relatively easily gleaned.  Would you find that a sufficient answer? 
And what if you didn't?  Who should decide?  Nothing stops you from
asking the question now, by the way,  and we're already saying that
people should ask these sorts of questions and give serious
consideration to the matter.

And the example points to another problem.  We neither have a common
view of what the threat is or how best to mitigate it.  Therefore, *at
this moment in time*, how can we go any further without (a) possibly
addressing the wrong threat, and (b) causing inefficient or
inappropriate architectural changes?

My previous sentence more than implies, by the way, that this situation
is subject to change based on how we further our understanding of the
issue.  The draft also states that.

Eliot

--------------040301060702050506010109
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 1/23/14, 12:02 AM, Sam Hartman
      wrote:
    </div>
    <br>
    <blockquote cite="mid:tslvbxb62of.fsf@mit.edu" type="cite">
      <pre wrap="">
* If we were doing DDS/NAPTR work today I should be able to ask whether
  confidentiality is a requirement and if so why DNS is an appropriate
  substrate.</pre>
    </blockquote>
    <br>
    And herein lies the problem.Â  It would depend on the record's
    application, and how information was released that couldn't
    otherwise be relatively easily gleaned.Â  Would you find that a
    sufficient answer?Â  And what if you didn't?Â  Who should decide?Â 
    Nothing stops you from asking the question now, by the way,Â  and
    we're already saying that people should ask these sorts of questions
    and give serious consideration to the matter.<br>
    <br>
    And the example points to another problem.Â  We neither have a common
    view of what the threat is or how best to mitigate it.Â  Therefore, <b>at
      this moment in time</b>, how can we go any further without (a)
    possibly addressing the wrong threat, and (b) causing inefficient or
    inappropriate architectural changes?<br>
    <br>
    My previous sentence more than implies, by the way, that this
    situation is subject to change based on how we further our
    understanding of the issue.Â  The draft also states that.<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------040301060702050506010109--

From lars@netapp.com  Thu Jan 23 02:37:10 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD0F1A03A9; Thu, 23 Jan 2014 02:37:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPsch87rsW8E; Thu, 23 Jan 2014 02:37:07 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id D803D1A03D5; Thu, 23 Jan 2014 02:37:07 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,705,1384329600";  d="asc'?scan'208";a="97660183"
Received: from vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) by mx11-out.netapp.com with ESMTP; 23 Jan 2014 02:37:07 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht02-prd.hq.netapp.com ([10.106.76.240]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 02:37:07 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPF6BSFyKjVtdEy02x6qUpK40JLJqSpPgA
Date: Thu, 23 Jan 2014 10:37:06 +0000
Message-ID: <0DCB269E-D53D-4BF5-8D1A-42445ABBBB1E@netapp.com>
References: <20140122183237.0FE0918C144@mercury.lcs.mit.edu>
In-Reply-To: <20140122183237.0FE0918C144@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_D267C342-22A5-4375-B74A-7185400A74A7"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 10:37:10 -0000

--Apple-Mail=_D267C342-22A5-4375-B74A-7185400A74A7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2014-1-22, at 19:32, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>> From: "Eggert, Lars" <lars@netapp.com>
>=20
>> Depends on the reach of that encapsulation. .. If it traversed such
>> middleboxes by default, as UDP does, it has the same issues.
>=20
> Exactly. The problem is not specific to UDP. So why is the discussion
> (seemingly) trying to solve it in a UDP-specific way?

you conveniently cut the part of my original message where I tried to =
explain that the difference is in *reach* of the traffic.

> I repeat: even if people were _not_ using UDP encapsulations, the =
exact same
> problem (of potential congestion caused by non-congestion-compliant
> applications) would still exist. Switching to a different =
encapsulation method
> is not going to get rid of _any_ potential congestion - not one =
packet's
> worth.

The severity of the problem depends on the reach of the traffic. =
Encapsulating something inside some "obscure" IP protocol number limits =
the reach. Encapsulating in UDP does not.

> So can we just drop all mention of UDP, since it's irrelevant to the =
_real_
> problem?

But it isn't.

>>> But saying that _intermediate forwarding nodes_ have to detect
>>> down-stream congestion, and respond, represents a fundamental change
>>> to the Internet's architecture for congestion control.
>=20
>> And here's the fallacy: UDP encapsulators are forwarding nodes *only*
>> from the viewpoint of the final endpoints. =46rom the viewpoint of =
the
>> rest of the Internet, they are traffic *sources*, not *forwarders*.
>=20
> I present two boxes. In one, a packet comes in, and after some =
manipulation of
> headers, the packet goes out. In the other, a packet comes in, and =
after some
> header changes, the packet goes out. You're trying to tell me that,
> architecturally, one _is_ an intermediate forwarding node (which =
doesn't have
> to detect downsteam congestion, and respond), and the other is not =
(and so
> does have to)?

You have oversimplified the scenario.=20

In one case, an L2 packet comes in, and goes out as an L2 packet that is =
limited in reach to the L2 topology, or as an L3 packet with an obscure =
IP protocol number that will make it die at the next middlebox (in the =
case of MPLS in IP).

In the other case, an L2 packet comes in and it comes out as an L4 UDP =
packet that can now go anywhere on the Internet.

Surely you see the difference?

> And I repeat: mandating that nodes which are forwarding nodes have to =
detect,
> and respond to, downsteam congestion caused by =
non-congestion-compliant
> traffic flowing _through_ them is a fundamental change to the =
Internet's
> existing framework for congestion control.

Since we're repeating ourselves, I'll again say that encapsulators are =
not forwarding nodes from the viewpoint of the network they tunnel over. =
They are traffic sources.

> Not that I'm opposed to such a change (it might make sense, I'd have =
to go
> away and think about it), but if we're going to make such an =
architectural
> change, i) we should do so explicitly, and ii) such a requirement =
should fall
> on _all_ packet forwarding nodes - including regular routers, since =
they could
> equally possibly be given non-congestion-compliant traffic to forward.

Lars

--Apple-Mail=_D267C342-22A5-4375-B74A-7185400A74A7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuDw0dZcnpRveo1xAQJbVgP8D3cTNl5SZRKcD5Xlny3NJbVsqgataqkI
GfQt0OyysOwHZQrLbkzSRYAzedQldpa6IwamTC2bAnukEnuVv1BX7CFZSfTEwahy
vdfDw0fi4iac2TeOZpDfm6KJ235a4Bw82ZBew2iFEHn4heI7m+oZdyoZBzhgZ5l8
8bMCste8GnQ=
=Ggw/
-----END PGP SIGNATURE-----

--Apple-Mail=_D267C342-22A5-4375-B74A-7185400A74A7--

From jnc@mercury.lcs.mit.edu  Thu Jan 23 06:49:20 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3BFA1A00FC; Thu, 23 Jan 2014 06:49:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qsawzw_UJ7lF; Thu, 23 Jan 2014 06:49:18 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E316E1A00E2; Thu, 23 Jan 2014 06:49:17 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id AF62D18C151; Thu, 23 Jan 2014 09:49:16 -0500 (EST)
To: ietf@ietf.org, mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Message-Id: <20140123144916.AF62D18C151@mercury.lcs.mit.edu>
Date: Thu, 23 Jan 2014 09:49:16 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 14:49:20 -0000

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

    >>> Depends on the reach of that encapsulation. .. If it traversed such
    >>> middleboxes by default, as UDP does, it has the same issues.

    >> Exactly. The problem is not specific to UDP.

    > you conveniently cut the part of my original message where I tried to
    > explain that the difference is in *reach* of the traffic.

Say what? Does not "Depends on the reach of that encapsulation. .. If it
traversed such middleboxes by default" (which I did include) make exactly
that point?

But that's not important. Moving on...


    > encapsulators are not forwarding nodes from the viewpoint of the
    > network they tunnel over. They are traffic sources.

You might just as well say that 'from the viewpoint of the rest of the
Internet, a NAT box is a traffic source'. I mean, as far as the rest of the
Internet can tell, it just sits there, and emits packets, right?

After all, i) the packets it emits are quite different from the packets it
receives, and ii) (to make your pet point) the original packets (which
usually have RFC-1918 source addresses) would not make it far through the
Internet without the header changes the NAT box makes. 

But I don't hear you clamouring to have NAT boxes detect, and respond to,
down-stream congestion.


Look at it from the point of view of the box. Something(s) is sending it
packets, which it is supposed to forward. Basically, it can do one of three
(really, two) things with the packet:

- Forward it
- Drop it
- Queue it (but this eventually has to turn into 1 or 2, above)

How is that any different between i) a plain old router, and ii) one of these
boxes that you insist is a "traffic *source[]*, not [a] *forwarder[]*"?


You want to separate out a very specific class of intermediate forwarding
nodes, selected on a fairly arbitrary basis (the particular kind of header
they emit), and impose requirements on them that are not imposed on any other
intermediate forwarding nodes - and change the Internet's basic schemea of
congestion control in the process.

Why restrict that change to this particular kind of intermediate forwarding
device?

	Noel

From hartmans@mit.edu  Thu Jan 23 08:06:35 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 394511A002F for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 08:06:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DEID3LREN1lw for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 08:06:32 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4F0581A002A for <ietf@ietf.org>; Thu, 23 Jan 2014 08:06:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 488E820647; Thu, 23 Jan 2014 11:03:40 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdUiCd8Cas5I; Thu, 23 Jan 2014 11:03:39 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 23 Jan 2014 11:03:39 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 314F1819E5; Thu, 23 Jan 2014 11:06:30 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Eliot Lear <lear@cisco.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu> <52E0C4F4.3090706@cisco.com>
Date: Thu, 23 Jan 2014 11:06:30 -0500
In-Reply-To: <52E0C4F4.3090706@cisco.com> (Eliot Lear's message of "Thu, 23 Jan 2014 08:29:56 +0100")
Message-ID: <tslwqhqznqx.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, Jari Arkko <jari.arkko@ericsson.com>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 16:06:35 -0000

>>>>> "Eliot" == Eliot Lear <lear@cisco.com> writes:

    Eliot>    On 1/23/14, 12:02 AM, Sam Hartman wrote:
    Eliot> * If we were doing DDS/NAPTR work today I should be able to
    Eliot> ask whether confidentiality is a requirement and if so why
    Eliot> DNS is an appropriate substrate.

    Eliot>    And herein lies the problem.  It would depend on the
    Eliot> record's application, and how information was released that
    Eliot> couldn't otherwise be relatively easily gleaned.  Would you
    Eliot> find that a sufficient answer?  And what if you didn't?  Who
    Eliot> should decide?  

I find it a sufficient answer; I'm not actually sure I agree with it but
it's definitely the kind of answer I'm looking for.
Whether I agree with the answer doesn't matter for a hypothetical.

Who decides?
Our standard process applies for figuring out whether we as a community
have decided something--the IETF rough consensus process.
The specific details of that process are kind of complex, but I think we
both agree to a fairly strong approximation what that process is.  We
probably disagree on details about corner cases that don't come up
often.


From jari.arkko@ericsson.com  Wed Jan 22 14:48:46 2014
Return-Path: <jari.arkko@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6A1C1A04D3 for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 14:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XG2W_3tGvJZV for <ietf@ietfa.amsl.com>; Wed, 22 Jan 2014 14:48:45 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id D5F181A02DC for <ietf@ietf.org>; Wed, 22 Jan 2014 14:48:44 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-60-52e04acb826f
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 33.F4.10875.BCA40E25; Wed, 22 Jan 2014 23:48:43 +0100 (CET)
Received: from ESESSMB307.ericsson.se ([169.254.7.171]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0387.000; Wed, 22 Jan 2014 23:48:42 +0100
From: Jari Arkko <jari.arkko@ericsson.com>
To: "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, Scott Brim <scott.brim@gmail.com>, Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Topic: Gen-Art telechat review of draft-farrell-perpass-attack-04
Thread-Index: AQHPF8QYhZ89fpHxYEaxPXxqNJZteQ==
Date: Wed, 22 Jan 2014 22:48:41 +0000
Message-ID: <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net>
In-Reply-To: <52DEFAEE.3000900@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/signed; boundary="Apple-Mail=_AAF0C73C-7843-4821-BD81-C7505FA1FB95"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplkeLIzCtJLcpLzFFi42KZGfG3Rve014Mgg5nLRSx+f/rAZnGlOdBi ztfVbBbPNs5nsXi34zCbA6vHpZ0n2Tx2zrrL7rFkyU8mj6YzR5k9vlz+zBbAGsVlk5Kak1mW WqRvl8CV8frmL/aCzwYVB7cvYWxgnKnfxcjJISFgIjHl3HRmCFtM4sK99WxdjFwcQgKHGCXO HW1ghnCWMEps+tPHBFLFJqAlsXH5AqAqDg4RgVqJBTc8QWqYBSYySjw9co8RpEZYwF3iz7Ol rBA1HhJffoWDhEUE9CQmfHkKtoxFQFVi3Z31YCW8AvYSsyaDhYUEfjJKPP/kBhLmFNCRaH3m CRJmBDrt+6k1YAcwC4hL3HoynwniZBGJhxdPs0HYohIvH/9jhbCVJBqXPGGFuGwKo8THFw9Y QBK8AoISJ2c+YZnAKDoLyaxZyOpmIamDKNKWWLbwNTOErSfxsukdO4RtKvH66EdGCNtaYsav g2wQtqLElO6H7AsYOVYxsucmZuaklxtuYgRG6cEtv3V3MJ46J3KIUZqDRUmc98Nb5yAhgfTE ktTs1NSC1KL4otKc1OJDjEwcnFINjEZLo209w8I/qJgZJNZzr/1eaadaM7tZLD4qNJnh1F2+ DxGlrh2R8tut2Pfxt734HLe86UX8tvbps9+zNxo/qM9QCj76ryDboHqZ7UqtPxGmyzU8X8xc YhrE5X58Xdz1b48mNB/h3LZYTmmdj1m4Upqn8u75D2Kn+inMefsm3/ypnarojzm+SizFGYmG WsxFxYkASPgLvaACAAA=
X-Mailman-Approved-At: Thu, 23 Jan 2014 08:26:01 -0800
Cc: IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jan 2014 22:48:47 -0000

--Apple-Mail=_AAF0C73C-7843-4821-BD81-C7505FA1FB95
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Sam,

FWIW my view is pretty much what Dave and Scott noted. I don't think the =
change weakens the draft's message: We'll take the issue seriously.

Jari


--Apple-Mail=_AAF0C73C-7843-4821-BD81-C7505FA1FB95
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINaDCCBEUw
ggMtoAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVs
aWFTb25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4X
DTA2MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv
1rLnfub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqT
u3TT39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMc
CYXRlobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUb
Az2oFRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB
/wQIMAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8v
cmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRh
cC50cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2
MSxvPVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNV
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb
8I+4GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXI
v6tPjhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzY
FSzz6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67
OzIKXrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3k
MXuiNuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OY
CMZ9lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAw
OjEZMBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDgg
VjMwHhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVy
YSBHcm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqG
SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5D
uVdWPMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe
1X7/jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF4
6H1ibp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjgh
XYpw/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGj
ggFiMIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7ga
YqGoIxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0F
BgEwMDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7Bgcq
hXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20w
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vv
bi9yZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkww
DgYDVR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUE
kUm25PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDC
fkDJSgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6b
KuTPBH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHn
tP+npjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPd
OI5GtDYPMIIEqjCCA5KgAwIBAgIQTyXs3vXto5joAjtwrbnc3jANBgkqhkiG9w0BAQUFADA5MREw
DwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQTAxMB4X
DTEzMDMwNDEzMjUyMVoXDTE2MDMwNDEzMjUxOVowYjERMA8GA1UECgwIRXJpY3Nzb24xEzARBgNV
BAMMCkphcmkgQXJra28xEDAOBgNVBAUTB2xtZmphYXIxJjAkBgkqhkiG9w0BCQEWF2phcmkuYXJr
a29AZXJpY3Nzb24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhwriyJIY5Bbz
yZrfnFAjWFLMNc6O6Z6dw5HqexTVyrUymDobuwcFtGl3n+yc6tYcvzM85LJMotJlOJH4NHEqClEc
iMw+gFvN17PXxM2aAPuv1ZUL1wSdQ9dS94zxQEQuh4Myyfy+eqvrEBkzZaDPu4Evz6xsmCYPYSZP
t4Bo6zbwQqkRvSQUO659ytmlyiPOiWN6wxEpwwO43LEw12xFrVSOQw3AG8ULW/xHbQvInuyWQdBC
ug/1n6IJETsMWSrLFnk888IjABXKkmq42EG6RQ0BWLw8lAQwTju7rsDF9HrcTYBcu9z2u/d4cSgH
P9SkRncRm68xrt7bD2RhPf3rkQIDAQABo4IBgzCCAX8wgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3
aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vRXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZx
bGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29tL2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFs
JTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmljYXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2Uw
IgYDVR0RBBswGYEXamFyaS5hcmtrb0Blcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEw
MTAvBggrBgEFBQcCARYjaHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0O
BBYEFLk/k+8oySkNxYm0GyPaFaKSRQufMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCb
MA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQUFAAOCAQEAECF65IiGH7GS+EEHre+itv2wv0OQ
Z68DWR6G9IqMkBgb8dj6JcfFsu+9p8ID1e1L/0ybeTwz1t4IPhuOuWBPohj5irYiCBJkIokUr09B
rWPyxfBrSoZ+uXVWfmZSdp15pWlEnHhuGuJkZ2a0MKrj+OEM9qfQR5Cvdlmx5PvsIhFkAFcZWldI
xBwHsEeSoGJbVvvNImiY6M27u6rhuR8HanXVdcW4B8gK489LutxKhyhT9QDFUhmyWk2qYCUJgwM/
w44sLz8tv95jDbJxAR/aOwdwF3fQgj8VB5Xwvdn6B0PhfEcd3Ju4yUz6HE6ELZWG4ruE2haUCOn4
8WStKZ/RPDGCApMwggKPAgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNz
c29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQTyXs3vXto5joAjtwrbnc3jAJBgUrDgMCGgUAoIIBGzAY
BgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAxMjIyMjQ4NDBaMCMG
CSqGSIb3DQEJBDEWBBReFv5ZTNNolITD6rT2GMj8LktB6zBcBgkrBgEEAYI3EAQxTzBNMDkxETAP
BgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l
7N717aOY6AI7cK253N4wXgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQw
IgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEE8l7N717aOY6AI7cK253N4wDQYJ
KoZIhvcNAQEBBQAEggEADPGhsV+0ezNmAVa1HOyHQIfVHx4SBhGcR4lw7uqb8W6LEuFEutoHNMkd
u4MZK86eyjhzrhzFRoYiZ4UZ550d+4+q8W7dzfm0dOdNZuhxo7vnFXT8VzIb28rZVM0hG+HnhHDN
iIwbwV1oqX3YEaxkrq4zBJLKnCD0cEXdsA5cVmf3HndRXiLoV6LDpRW5+s5jiNPC7jddcptkPAny
xLnYj8UPfjZg57R58o6XLuaHw7LlOdTZIILeHBpiBfH1ndGmJZwElvv4ulnciWPDZO5A0fZ8qACf
+HkOiIJgrY4PhF4nw5mrFtOHl6JpccNA/vxfRxLTrVO/wfETkdbcQPQL0wAAAAAAAA==

--Apple-Mail=_AAF0C73C-7843-4821-BD81-C7505FA1FB95--

From fluffy@cisco.com  Thu Jan 23 09:25:28 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAEA11A0097; Thu, 23 Jan 2014 09:25:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2AsioC8Awrcm; Thu, 23 Jan 2014 09:25:22 -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 898531A008E; Thu, 23 Jan 2014 09:25:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4744; q=dns/txt; s=iport; t=1390497922; x=1391707522; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=PyVmN5+k3lP+L1rXDge0tNjsPJ7uWr2n3N/v1Mk8mhU=; b=TNy55b0FsOrAzuKdNBt4PbAF3U0VdwswyBATy/V+429x0Hnmx4aY2/nJ Ueh5UnBarq5X3MexXnP7rWSue+l7PzIn/ONgYiB2hMhc0XbLlgb4PBhqw EFqgG9q5ZC2adsn8ouaO0YmcY3WQI+8/RF/DXyWEoAC5qb67GK9c81NXs U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgsFAHFP4VKtJXG//2dsb2JhbABYA4MMOFa7e4ETFnSCJQEBAQMBeQULAgEIEgYuMhcOAgQBDQUJh3QIDcYIF40PgR0hIxACBRGDE4EUBJgjgTKQZoMtgio
X-IronPort-AV: E=Sophos;i="4.95,706,1384300800"; d="scan'208";a="299340950"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-4.cisco.com with ESMTP; 23 Jan 2014 17:25:21 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0NHPLIu006171 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 17:25:21 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 11:25:20 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Russ Housley <housley@vigilsec.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGFpx6U6AfiunqkWV7evY6wlIJZqS9A2A
Date: Thu, 23 Jan 2014 17:25:20 +0000
Message-ID: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com>
In-Reply-To: <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <89BD4672CA5554479439815A68F00696@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:25:28 -0000

This new note well is a real problem for me and  I can not register without=
 clicking "I agree" to it. It is not consistent with the BCPs. The problem =
is the line that says

	=95 If you are aware that any contribution (something written, said, or di=
scussed in any IETF context) is covered by patents or patent applications, =
you must disclose that fact.

I do not agree to that - I can=92t given my NDA with my employer does not a=
llow me to disclose confidential information. Yes, I realize there is some =
weasel words near the top that say "Exceptions may apply." but that does no=
t help me. When you are testifying in court on patents, credibility is incr=
edibly important. You can not have the lawyers on the other side saying tha=
t you clicked yes I agree to the line above but you did not actually do wha=
t that lines says. You may think this does to matter but the exact topic of=
 how Cisco employees deal with IPR at the IETF is a topic that I have testi=
fied on in an East Texas court so this really does happen and really does h=
appen to me. It may happen to you next and you will be much happier if you =
say what you mean and mean what you say. This new note well fails that test=
.=20

I realize some people would like to change the IETF policy to be that you d=
o have to do what that line says but I do not think that is a change the IE=
SG can make without IETF updating the BCP or at least having IETF consensus=
 on the change. I would respectfully ask the IESG to change this line to so=
mething that is still brief but that people can agree with it. Simply addin=
g something like "or not contribute to the discussion on that contribution"=
 would probably solve this problem for me.=20

Thank you,=20

Cullen

I will note that above line is not consistent with Cisco employment contrac=
ts and if we can not resolve this I will be asking Cisco legal to inform Ci=
sco employees they can not agree with this without violating their employme=
nt agreement.=20



On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:

> It seems that the shorter one is now being used on the IETF web site:
> http://www.ietf.org/about/note-well.html
>=20
>=20
> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>=20
>> Personally, I've never seen significant value in this shorter note well =
and while others have been using this new text for the past few meetings, I=
've stuck to the old.   Now that this is considered the recommended note we=
ll for chairs to use, I guess I'll use it.  But, I personally think accurac=
y should trump brevity.  I think the "must" in that bullet  ought to at lea=
st be a should and that adding an "otherwise, one should not contribute to =
or participate in any related IETF activities." would add more value.  =20
>>=20
>> Mary.
>>=20
>>=20
>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>> you are correct - we (Barry, the IESG & me) discussed this before the IE=
SG approved this text - they felt that
>> being brief was more important than being fully accurate (or at least th=
at is the way I expressed it)
>>=20
>> Scott
>>=20
>> Scott O Bradner
>> Senior Technology Consultant
>>=20
>> Harvard University Information Technology
>> Innovation & Architecture
>> (P) +1 (617) 495 3864
>> 8 Story St, room 5014
>> Cambridge, MA 02138
>>=20
>>=20
>>=20
>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:
>>=20
>> >
>> >
>> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wr=
ote:
>> >
>> >> The IESG has made final edits to the updated Note Well statement, and
>> >> it has been officially updated:
>> >> http://www.ietf.org/about/note-well.html
>> >>
>> >> I have just uploaded the final versions of the Note Well meeting
>> >> slides, attached to the bottom of the WG Chairs wiki:
>> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>> >>
>> >> Please use this new version now, and please remember that as you
>> >> prepare slides for the London meeting.
>> >>
>> >> Barry
>> >
>> >
>> > The new note well says
>> >
>> >       =95 If you are aware that any contribution (something written, s=
aid, or discussed in any IETF context) is covered by patents or patent appl=
ications, you must disclose that fact.
>> >
>> > Is that true?  Or is it missing something along the lines of section y=
 of BCP 79 such as
>> >
>> >   or must not contribute to or participate in IETF activities with
>> >   respect to technologies that he or she reasonably and personally
>> >   knows to be Covered by IPR which he or she will not disclose.
>> >
>> > Thanks, Cullen
>=20


From mstjohns@comcast.net  Thu Jan 23 09:51:02 2014
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F651A016F for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 09:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.038
X-Spam-Level: 
X-Spam-Status: No, score=-2.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xLKtAgmjjzp for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 09:50:57 -0800 (PST)
Received: from qmta14.emeryville.ca.mail.comcast.net (qmta14.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:44:76:96:27:212]) by ietfa.amsl.com (Postfix) with ESMTP id 91F031A0177 for <ietf@ietf.org>; Thu, 23 Jan 2014 09:50:52 -0800 (PST)
Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta14.emeryville.ca.mail.comcast.net with comcast id HUvR1n0020vp7WLAEVqssz; Thu, 23 Jan 2014 17:50:52 +0000
Received: from Mike-T530ssd.comcast.net ([76.14.1.153]) by omta05.emeryville.ca.mail.comcast.net with comcast id HVpv1n00S3J4Au48RVq14J; Thu, 23 Jan 2014 17:50:46 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 23 Jan 2014 12:49:59 -0500
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Russ Housley <housley@vigilsec.com>,Jari Arkko <jari.arkko@piuha.net>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1390499452; bh=WeedSkUFXQu0ApZ+mrRzs8GiwXgttB/3A0MHE/Vmc8I=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=IEFidyulBDorp5RxoWIpBjDCMoKOnt4Gins8WvJesFOb00lNd96jLau+ukPjvkLm0 +nW12Ca8+JRvod/1ZvHefumSNx0Zjv78pA2r8uNwxWA5ZE3VjrMJZRI79Hd96ZRi0t wnTW9KZRerONnxSA9UiLOMN46Q8G9OAoB19s1CglkvYNVbtykNaOzAC298vICxBJhX qPnuY9p5kCtKvo/egeZ81rjAggejHCCk/ozA9CxUNLrjzqYUnS6u9sIzbzAK7SzVk1 J/tH3TZV/ZMmTUGW27IFIgkqgl+D8Jkzp6VmzDbOS4FxuVgwWn5rHQMy7XubY9464y e/QQoQzmvP2bQ==
Cc: IESG IESG <iesg@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:51:02 -0000

Is the issue the difference between "any contribution YOU MAKE" and "any=
 contribution"?  E.g. if you happen to hear someone discussing something you=
 think is covered by patent, you can't say anything, but conversely, if YOU=
 are making a contribution that's covered by patent then the NDA doesn't=
 apply (because you have approval to make the contribution and disclosure).

Mike


At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:

>This new note well is a real problem for me and  I can not register without=
 clicking "I agree" to it. It is not consistent with the BCPs. The problem=
 is the line that says
>
>        =95 If you are aware that any contribution (something written,=
 said, or discussed in any IETF context) is covered by patents or patent=
 applications, you must disclose that fact.
>
>I do not agree to that - I can=92t given my NDA with my employer does not=
 allow me to disclose confidential information. Yes, I realize there is some=
 weasel words near the top that say "Exceptions may apply." but that does=
 not help me. When you are testifying in court on patents, credibility is=
 incredibly important. You can not have the lawyers on the other side saying=
 that you clicked yes I agree to the line above but you did not actually do=
 what that lines says. You may think this does to matter but the exact topic=
 of how Cisco employees deal with IPR at the IETF is a topic that I have=
 testified on in an East Texas court so this really does happen and really=
 does happen to me. It may happen to you next and you will be much happier=
 if you say what you mean and mean what you say. This new note well fails=
 that test.=20
>
>I realize some people would like to change the IETF policy to be that you=
 do have to do what that line says but I do not think that is a change the=
 IESG can make without IETF updating the BCP or at least having IETF=
 consensus on the change. I would respectfully ask the IESG to change this=
 line to something that is still brief but that people can agree with it.=
 Simply adding something like "or not contribute to the discussion on that=
 contribution" would probably solve this problem for me.=20
>
>Thank you,=20
>
>Cullen
>
>I will note that above line is not consistent with Cisco employment=
 contracts and if we can not resolve this I will be asking Cisco legal to=
 inform Cisco employees they can not agree with this without violating their=
 employment agreement.=20
>
>
>
>On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>=20
>>=20
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>=20
>>> Personally, I've never seen significant value in this shorter note well=
 and while others have been using this new text for the past few meetings,=
 I've stuck to the old.   Now that this is considered the recommended note=
 well for chairs to use, I guess I'll use it.  But, I personally think=
 accuracy should trump brevity.  I think the "must" in that bullet  ought to=
 at least be a should and that adding an "otherwise, one should not=
 contribute to or participate in any related IETF activities." would add=
 more value.  =20
>>>=20
>>> Mary.
>>>=20
>>>=20
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>> you are correct - we (Barry, the IESG & me) discussed this before the=
 IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least=
 that is the way I expressed it)
>>>=20
>>> Scott
>>>=20
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>=20
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>=20
>>>=20
>>>=20
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com>=
 wrote:
>>>=20
>>> >
>>> >
>>> > On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org>=
 wrote:
>>> >
>>> >> The IESG has made final edits to the updated Note Well statement, and
>>> >> it has been officially updated:
>>> >> http://www.ietf.org/about/note-well.html
>>> >>
>>> >> I have just uploaded the final versions of the Note Well meeting
>>> >> slides, attached to the bottom of the WG Chairs wiki:
>>> >> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>> >>
>>> >> Please use this new version now, and please remember that as you
>>> >> prepare slides for the London meeting.
>>> >>
>>> >> Barry
>>> >
>>> >
>>> > The new note well says
>>> >
>>> >       =95 If you are aware that any contribution (something written,=
 said, or discussed in any IETF context) is covered by patents or patent=
 applications, you must disclose that fact.
>>> >
>>> > Is that true?  Or is it missing something along the lines of section y=
 of BCP 79 such as
>>> >
>>> >   or must not contribute to or participate in IETF activities with
>>> >   respect to technologies that he or she reasonably and personally
>>> >   knows to be Covered by IPR which he or she will not disclose.
>>> >
>>> > Thanks, Cullen
>>=20



From sob@harvard.edu  Thu Jan 23 09:58:27 2014
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BA271A01A1; Thu, 23 Jan 2014 09:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KtkdGqoyV1db; Thu, 23 Jan 2014 09:58:19 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id 72E121A0189; Thu, 23 Jan 2014 09:58:13 -0800 (PST)
Received: from ENTWEDGE0000003.university.harvard.edu (entwedge0000003.university.harvard.edu [10.35.202.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 9EF76E8EEF; Thu, 23 Jan 2014 12:58:12 -0500 (EST)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by entwedge0000003.university.harvard.edu (10.35.202.50) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 23 Jan 2014 12:58:01 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.03.0146.000; Thu, 23 Jan 2014 12:58:12 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Mike StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGGAibruxKTnnVUu65PwElpA1yg==
Date: Thu, 23 Jan 2014 17:58:12 +0000
Message-ID: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu>
In-Reply-To: <20140123175052.CC016E8F3D@ackroyd.harvard.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.103.229.199]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3EE725A95AB8144AB3E380EC9DB859D7@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 17:58:27 -0000

the actual rules are
	1/ if you know of any of your IPR in a contribution you make, you must dis=
close
	2/ if you know of any of your IPR in any contribution from someone else an=
d you are participating in discussions
	    that involve that contribution, then you must disclose
	3/ if you know of any of your IPR in any contribution from someone else an=
d you are not participating in discussions
	    that involve that contribution, then you are requested to disclose

see - its not that hard to say this briefly

Scott

On Jan 23, 2014, at 12:49 PM, Michael StJohns <mstjohns@comcast.net> wrote:

> Is the issue the difference between "any contribution YOU MAKE" and "any =
contribution"?  E.g. if you happen to hear someone discussing something you=
 think is covered by patent, you can't say anything, but conversely, if YOU=
 are making a contribution that's covered by patent then the NDA doesn't ap=
ply (because you have approval to make the contribution and disclosure).
>=20
> Mike
>=20
>=20
> At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:
>=20
>> This new note well is a real problem for me and  I can not register with=
out clicking "I agree" to it. It is not consistent with the BCPs. The probl=
em is the line that says
>>=20
>>       . If you are aware that any contribution (something written, said,=
 or discussed in any IETF context) is covered by patents or patent applicat=
ions, you must disclose that fact.
>>=20
>> I do not agree to that - I can't given my NDA with my employer does not =
allow me to disclose confidential information. Yes, I realize there is some=
 weasel words near the top that say "Exceptions may apply." but that does n=
ot help me. When you are testifying in court on patents, credibility is inc=
redibly important. You can not have the lawyers on the other side saying th=
at you clicked yes I agree to the line above but you did not actually do wh=
at that lines says. You may think this does to matter but the exact topic o=
f how Cisco employees deal with IPR at the IETF is a topic that I have test=
ified on in an East Texas court so this really does happen and really does =
happen to me. It may happen to you next and you will be much happier if you=
 say what you mean and mean what you say. This new note well fails that tes=
t.=20
>>=20
>> I realize some people would like to change the IETF policy to be that yo=
u do have to do what that line says but I do not think that is a change the=
 IESG can make without IETF updating the BCP or at least having IETF consen=
sus on the change. I would respectfully ask the IESG to change this line to=
 something that is still brief but that people can agree with it. Simply ad=
ding something like "or not contribute to the discussion on that contributi=
on" would probably solve this problem for me.=20
>>=20
>> Thank you,=20
>>=20
>> Cullen
>>=20
>> I will note that above line is not consistent with Cisco employment cont=
racts and if we can not resolve this I will be asking Cisco legal to inform=
 Cisco employees they can not agree with this without violating their emplo=
yment agreement.=20
>>=20
>>=20
>>=20
>> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>>=20
>>> It seems that the shorter one is now being used on the IETF web site:
>>> http://www.ietf.org/about/note-well.html
>>>=20
>>>=20
>>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>>=20
>>>> Personally, I've never seen significant value in this shorter note wel=
l and while others have been using this new text for the past few meetings,=
 I've stuck to the old.   Now that this is considered the recommended note =
well for chairs to use, I guess I'll use it.  But, I personally think accur=
acy should trump brevity.  I think the "must" in that bullet  ought to at l=
east be a should and that adding an "otherwise, one should not contribute t=
o or participate in any related IETF activities." would add more value.  =20
>>>>=20
>>>> Mary.
>>>>=20
>>>>=20
>>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote=
:
>>>> you are correct - we (Barry, the IESG & me) discussed this before the =
IESG approved this text - they felt that
>>>> being brief was more important than being fully accurate (or at least =
that is the way I expressed it)
>>>>=20
>>>> Scott
>>>>=20
>>>> Scott O Bradner
>>>> Senior Technology Consultant
>>>>=20
>>>> Harvard University Information Technology
>>>> Innovation & Architecture
>>>> (P) +1 (617) 495 3864
>>>> 8 Story St, room 5014
>>>> Cambridge, MA 02138
>>>>=20
>>>>=20
>>>>=20
>>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com=
> wrote:
>>>>=20
>>>>>=20
>>>>>=20
>>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> w=
rote:
>>>>>=20
>>>>>> The IESG has made final edits to the updated Note Well statement, an=
d
>>>>>> it has been officially updated:
>>>>>> http://www.ietf.org/about/note-well.html
>>>>>>=20
>>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>>=20
>>>>>> Please use this new version now, and please remember that as you
>>>>>> prepare slides for the London meeting.
>>>>>>=20
>>>>>> Barry
>>>>>=20
>>>>>=20
>>>>> The new note well says
>>>>>=20
>>>>>      . If you are aware that any contribution (something written, sai=
d, or discussed in any IETF context) is covered by patents or patent applic=
ations, you must disclose that fact.
>>>>>=20
>>>>> Is that true?  Or is it missing something along the lines of section =
y of BCP 79 such as
>>>>>=20
>>>>>  or must not contribute to or participate in IETF activities with
>>>>>  respect to technologies that he or she reasonably and personally
>>>>>  knows to be Covered by IPR which he or she will not disclose.
>>>>>=20
>>>>> Thanks, Cullen
>>>=20
>=20
>=20


From presnick@qti.qualcomm.com  Thu Jan 23 10:02:47 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2914A1A00DF; Thu, 23 Jan 2014 10:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYCreSvAdGGi; Thu, 23 Jan 2014 10:02:43 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3EC1A0052; Thu, 23 Jan 2014 10:02:37 -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=1390500156; x=1422036156; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mjlox8GK7GbC8nh/TP6foRKgkMuRFOZitdGRBDHnEmg=; b=ggFvQnJwumrAlFBmGPgNhHCh0wb+w9raZ1YTvrx0luVuJlCWzoMGGHgK g0ahMxWY1qDARIJ5HOC2G1n5Lnf1kPlxVJKSOSOon8IYrlOVDpgONn0OS V/2oquE496YJNA2f7RwydGamgQEw9xVJfT9Oq4zqU5MmRap2kXppp/MHb 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58459355"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth01.qualcomm.com with ESMTP; 23 Jan 2014 10:02:36 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="26198272"
Received: from nasanexhc02.na.qualcomm.com ([172.30.48.24]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:02:35 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC02.na.qualcomm.com (172.30.48.24) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:02:35 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:02:34 -0800
Message-ID: <52E15937.8010600@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:02:31 -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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:02:47 -0000

On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register without clicking "I agree" to it.

You are not asked to click "I agree" to any statement. You are asked to 
"Acknowledge" that you read it. And the statement says right at the top:

"This summary is only meant to point you in the right direction, and 
does not contain all the details. Exceptions may apply."

So by participating, there are things that you are agreeing to that are 
not on this page, and there are exceptions to things on this page that 
you don't have to agree to do.

The only thing that this page does is make you "Acknowledge" that you've 
got homework to do about rules for your participation.

pr

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


From fluffy@cisco.com  Thu Jan 23 10:07:13 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984781A0012; Thu, 23 Jan 2014 10:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2AWDFTAL-Qv; Thu, 23 Jan 2014 10:07:09 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id D62251A000A; Thu, 23 Jan 2014 10:07:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1175; q=dns/txt; s=iport; t=1390500429; x=1391710029; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=eDoZbefKl4CVsrsxiAvuUhu82cpqQ9W+8dxONZ4Nd7k=; b=UQEhTDfehJ7QCG2iFGQDQSzQ6AR5C1hsEfA7truXZV47pdxUOzKy8HXz JGzZCw7u+fBUdGK8CLHVhTyt91byGx+OA47uEgMV+GRpE/A+n0d4P0IBQ dBaILKyxNfexLMsNdy7IJ2mKpTcBFcDUwxplJ904Mhk/T1+HzXGRfvg0l M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAGxZ4VKtJXG8/2dsb2JhbABYAxaCdjhWu3uBExZ0giUBAQEDAXkFCwIBCA4KLjIlAgQOBYd9CA3FeheOTSMQBxGDE4EUBIkQjxOSGIMtgio
X-IronPort-AV: E=Sophos;i="4.95,707,1384300800"; d="scan'208";a="299296652"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jan 2014 18:07:08 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0NI77nG005078 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 18:07:07 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 12:07:07 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGGVI6U6AfiunqkWV7evY6wlIJZqS/6QA
Date: Thu, 23 Jan 2014 18:07:07 +0000
Message-ID: <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com>
In-Reply-To: <52E15937.8010600@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <46FFC73E42D86C4FAF1A35DA54BCA737@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IESG IESG <iesg@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:07:13 -0000

Pete,  what do you think "Acknowledge" means on a from like this? ( I will =
note it does not say "I Acknowledge I read this but may not agree with it" =
)



On Jan 23, 2014, at 11:02 AM, Pete Resnick <presnick@qti.qualcomm.com> wrot=
e:

> On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
>> This new note well is a real problem for me and  I can not register with=
out clicking "I agree" to it.
>=20
> You are not asked to click "I agree" to any statement. You are asked to "=
Acknowledge" that you read it. And the statement says right at the top:
>=20
> "This summary is only meant to point you in the right direction, and does=
 not contain all the details. Exceptions may apply."
>=20
> So by participating, there are things that you are agreeing to that are n=
ot on this page, and there are exceptions to things on this page that you d=
on't have to agree to do.
>=20
> The only thing that this page does is make you "Acknowledge" that you've =
got homework to do about rules for your participation.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From presnick@qti.qualcomm.com  Thu Jan 23 10:09:46 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 829A21A000A; Thu, 23 Jan 2014 10:09:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T1j8jkFwnM84; Thu, 23 Jan 2014 10:09:42 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8101A0028; Thu, 23 Jan 2014 10:09:42 -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=1390500581; x=1422036581; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VQN4XO27kBoVTraJjoWJdXaBdupIUOHprzlMsgaKMfc=; b=k/YRRDUsgqGjgMn9ZA84nv21tSoUWYkrOAFpRdsB9/wdbgfcFaRw6yyH mRCus0dLKU8T+NbO0oBGxlNCdrRCCHYgnlVKyNvx34PImtJIeZeYajuau QDItBGm1ZGFEVJgnxEe0VeU3RmkrpipqXD3V/EWz5wL4TZeB66guAapns Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58557099"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by sabertooth02.qualcomm.com with ESMTP; 23 Jan 2014 10:09:41 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="672416311"
Received: from nasanexhc14.na.qualcomm.com ([172.30.48.23]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:09:41 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc14.na.qualcomm.com (172.30.48.23) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:09:40 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:09:40 -0800
Message-ID: <52E15AE2.7030508@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:09:38 -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: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:09:46 -0000

On 1/23/14 11:58 AM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
>    

No, that's not true. If you know of any of your own IPR *that is 
necessarily infringed* by implementing your contribution, you must 
disclose. And what it means to be "necessarily infringed" has some 
details to it, and it might not be even implementation that causes the 
problem. And that's why it says at the top of the current document that 
there are exceptions.

> see - its not that hard to say this briefly

Really, it is quite hard to state the rules briefly such that it doesn't 
include *more* than you are required to do. Your statement did not.

pr

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


From scott.brim@gmail.com  Thu Jan 23 10:15:23 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90CE31A0024; Thu, 23 Jan 2014 10:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PvWM3OnW3WWq; Thu, 23 Jan 2014 10:15:22 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 03FAC1A000A; Thu, 23 Jan 2014 10:15:21 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so2590222qac.22 for <multiple recipients>; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IcFDFJL49BTRHZgRsH6pttCFnNOr+fve3gno97eirtw=; b=J9InLZrp3wB7f2kKZOKrI0d1IWSIzliHNP88vN44/UnSPMouWdw6dSWLJ53e5oz5Xq YH3oDk4L0EWdHN4OfVVb+CnPUNKuaTJVDkki5jipGz7QvPVwQSUXXN5KH1PHb8NepTYm 3ifjHWDR3+5H5bnN0yTSCmSS9HN4TSzNUEd9hKHXj3Yc2sFgypdBXaxpEvO++9dGOvEu GJoP6xJzLj2uPHs1MK5CXKrUXKoCBfKOw/5NKu8fQ93C1GZ/YtK+IXZHGOOxUYWhIFnH qyrasT86GinknndL1Dq0tyPTO5Dmn7ZCiI4Hpm/bfgHdlGcBMCTz1VwEynBEMzXne72r eK6A==
MIME-Version: 1.0
X-Received: by 10.224.5.69 with SMTP id 5mr13887903qau.11.1390500920885; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 23 Jan 2014 10:15:20 -0800 (PST)
In-Reply-To: <52E15AE2.7030508@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 13:15:20 -0500
Message-ID: <CAPv4CP-K+zfMV--pamd27SaPgZ2=Tg4UVeNuyn8oN+apsp3znw@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Scott Brim <scott.brim@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=001a11c2c28e730a1c04f0a73932
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, "Bradner, Scott" <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:15:23 -0000

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

Also, instant disclosure is not expected. I remember in the discussions it
was decided that a reasonable amount of time could be allowed for
consultation with lawyers, decisions about who would say what, etc.

--001a11c2c28e730a1c04f0a73932
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr">Also, instant disclosure is not expected. I remember in the discussions it was decided that a reasonable amount of time could be allowed for consultation with lawyers, decisions about who would say what, etc. </p>


--001a11c2c28e730a1c04f0a73932--

From presnick@qti.qualcomm.com  Thu Jan 23 10:25:56 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B2F41A00DE; Thu, 23 Jan 2014 10:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level: 
X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xiwLMdy1rF_3; Thu, 23 Jan 2014 10:25:51 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id C204C1A004A; Thu, 23 Jan 2014 10:25:51 -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=1390501551; x=1422037551; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=VIj2Pea93ajbO2VE5FPbT/v6TrSRxH0Tth/car5HwJI=; b=cZ3Y94KIBkRI2/2qna9LyIxQdpc1wGucZjp4V2DnHBjb6e85le6usiRt 0vzAG72TgZKofrDqUC0Jwe68t+FLi03hzWRCW9VEMRPCYeMY3dy2MWP54 UNr0aGmmTDFbRHVJgfOtf+kDn0irvnFSYeF1oXKvgR+PJCqN5RTut0+YP I=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="10035369"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 23 Jan 2014 10:25:49 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="618367016"
Received: from nasanexhc01.na.qualcomm.com ([172.30.48.25]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 10:25:49 -0800
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC01.na.qualcomm.com (172.30.48.25) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:25:48 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 10:25:48 -0800
Message-ID: <52E15EAA.8060301@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 12:25:46 -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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
In-Reply-To: <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, IESG IESG <iesg@ietf.org>, Scott Bradner <sob@harvard.edu>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:25:56 -0000

On 1/23/14 12:07 PM, Cullen Jennings (fluffy) wrote:
> Pete,  what do you think "Acknowledge" means on a from like this? ( I will note it does not say "I Acknowledge I read this but may not agree with it" )
>    

You are acknowledging that there are rules (not fully specified here) 
that you have to go read and abide by if you show up and participate at 
the meeting. When you show up and participate at the meeting, you are 
agreeing to a bunch of things that are not on this page.

Are you saying that you don't agree that there are exceptions to what's 
on this page?

pr

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


From ned+ietf@mauve.mrochek.com  Thu Jan 23 10:27:33 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4A61A01EC for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 10:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ERzhlmWMAm9H for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 10:27:31 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 64F3A1A01F7 for <ietf@ietf.org>; Thu, 23 Jan 2014 10:27:13 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3HNC8W334003JH7@mauve.mrochek.com> for ietf@ietf.org; Thu, 23 Jan 2014 10:22:11 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=Windows-1252
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P2SI6PLQJK0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 23 Jan 2014 10:22:06 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P3HNC7BYKK0000AS@mauve.mrochek.com>
Date: Thu, 23 Jan 2014 09:41:59 -0800 (PST)
Subject: Re: Problem with new Note Well
In-reply-to: "Your message dated Thu, 23 Jan 2014 17:25:20 +0000" <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 18:27:33 -0000

> This new note well is a real problem for me and  I can not register without
> clicking "I agree" to it. It is not consistent with the BCPs. The problem is
> the line that says

>     If you are aware that any contribution (something written, said, or
>     discussed in any IETF context) is covered by patents or patent applications,
>     you must disclose that fact.

> I do not agree to that - I can’t given my NDA with my employer does not allow
> me to disclose confidential information. Yes, I realize there is some weasel
> words near the top that say "Exceptions may apply." but that does not help me.

It's actually much worse than that. This wording would require that not only do
I disclose not only past and present employer/sponsor/personal IPR, but also
IPR third parties have asserted that I happen to be aware of as a result of,
say, a patent dispute. In constrast, the relevant BCPs are clear that while
I'm encouraged to disclose third party IPR I'm aware of, I'm not required to.

The resulting glut of disclosures created by following such a rule would in
turn create serious problems of its own. A lot of people, myself included,
operate under restricitons as to what sort of information about IPR we're
supposed to see. This could easily cross the line.

> When you are testifying in court on patents, credibility is incredibly
> important. You can not have the lawyers on the other side saying that you
> clicked yes I agree to the line above but you did not actually do what that
> lines says. You may think this does to matter but the exact topic of how Cisco
> employees deal with IPR at the IETF is a topic that I have testified on in an
> East Texas court so this really does happen and really does happen to me. It
> may happen to you next and you will be much happier if you say what you mean
> and mean what you say. This new note well fails that test.

The issue of how Oracle employees deal with IPR at the IETF hasn't come up for
me - at least not yet. But this is highly problematic for me in other ways,
as noted above.

> I realize some people would like to change the IETF policy to be that you do
> have to do what that line says but I do not think that is a change the IESG can
> make without IETF updating the BCP or at least having IETF consensus on the
> change.

I realize that a some people think they would like to make such a change, but
having spent a fair bit of time on patent matters, IMO this is a case of "be
careful what you wish for".

> I would respectfully ask the IESG to change this line to something that
> is still brief but that people can agree with it. Simply adding something like
> "or not contribute to the discussion on that contribution" would probably solve
> this problem for me.

Not sufficient for me. This also needs to be changed so that the
employee/sponsor restrictions set forth in sections 6.1.1 and 6.1.2 and most
especially 6.1.3 of BCP 79 are included.

> I will note that above line is not consistent with Cisco employment contracts
> and if we can not resolve this I will be asking Cisco legal to inform Cisco
> employees they can not agree with this without violating their employment
> agreement.

I haven't checked Oracle's contract, but the same may be true here as well, and
if so I will have no choice but to do something similar.

				Ned

From sob@harvard.edu  Thu Jan 23 11:56:52 2014
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8575C1A004E; Thu, 23 Jan 2014 11:56:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj9UXrjN9Z6R; Thu, 23 Jan 2014 11:56:50 -0800 (PST)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id B17B01A001D; Thu, 23 Jan 2014 11:56:50 -0800 (PST)
Received: from ENTWEDGE0000004.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 65843E939C; Thu, 23 Jan 2014 14:56:47 -0500 (EST)
Received: from ENTWHUBT0000000.university.harvard.edu (10.32.8.201) by entwedge0000004.university.harvard.edu (10.35.202.51) with Microsoft SMTP Server (TLS) id 14.3.146.0; Thu, 23 Jan 2014 14:56:35 -0500
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.46]) by ENTWHUBT0000000.university.harvard.edu ([10.32.8.201]) with mapi id 14.03.0146.000; Thu, 23 Jan 2014 14:56:47 -0500
From: "Bradner, Scott" <sob@harvard.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well 
Thread-Topic: Problem with new Note Well 
Thread-Index: AQHPGHU+CFZ0F6AtJEKMoMTuYGDa1Q==
Date: Thu, 23 Jan 2014 19:56:46 +0000
Message-ID: <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com>
In-Reply-To: <52E15AE2.7030508@qti.qualcomm.com>
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="Windows-1252"
Content-ID: <EB04A132A483394FA54E23C9D9A08C7C@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 19:56:52 -0000

while, in the end, this is true (the "necessarily infringed=94 requirement)=
 I do not think it is a good thing
to obsess about at the disclose-so-the-working-group-can-evaluate-the-techn=
ology stage since it is impossible
to know if any particular IPR will wind up in this catagory until a RFC is =
finished - which would negate=20
the whole reason for the disclosure

 maybe we should make that clear (disclose if you suspect that IPR relates =
not =93is necessarily infringed=94)
in the 3979 update - this is what the rule used to be and the language Pete=
 is focussing on
was added and, apparently, has an undesired side effect

Scott

On Jan 23, 2014, at 1:09 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>> the actual rules are
>> 	1/ if you know of any of your IPR in a contribution you make, you must =
disclose
>>  =20
>=20
> No, that's not true. If you know of any of your own IPR *that is necessar=
ily infringed* by implementing your contribution, you must disclose. And wh=
at it means to be "necessarily infringed" has some details to it, and it mi=
ght not be even implementation that causes the problem. And that's why it s=
ays at the top of the current document that there are exceptions.
>=20
>> see - its not that hard to say this briefly
>=20
> Really, it is quite hard to state the rules briefly such that it doesn't =
include *more* than you are required to do. Your statement did not.
>=20
> pr
>=20
> --=20
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>=20


From john-ietf@jck.com  Thu Jan 23 12:43:34 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 032791A0197 for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 12:43:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DRoNVvbxWe2q for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 12:43:31 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id F077D1A00C5 for <ietf@ietf.org>; Thu, 23 Jan 2014 12:43: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 1W6R7P-0003L2-TD; Thu, 23 Jan 2014 15:43:19 -0500
Date: Thu, 23 Jan 2014 15:43:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, Jari Arkko <jari.arkko@ericsson.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
Message-ID: <98477509D05291683DB2CAC5@JcK-HP8200.jck.com>
In-Reply-To: <tslvbxb62of.fsf@mit.edu>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 20:43:34 -0000

--On Wednesday, January 22, 2014 18:02 -0500 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

>...
> If you think those are reasonable, then I'd strongly prefer to
> spend the time to figure out what we actually mean.  Come up
> with text that makes it sure that such questions are
> reasonable while ruling out the things people are worried
> about.
> 
> If we do not think  that WGs should be required to justify
> these positions, then I strongly object to a claim that we
> have chosen to mitigate perpass attacks because I believe that
> claim is meaningless without actually being able to get WGs to
> justify these decisions while doing architectural review.

IMO, this lies nearly at the core of one of my fundamental
issues with the draft.  If we are looking to make a broad
statement of intent that is not actually actionable, then the
statement linked from the IETF home page as "Leading Engineers
Agree to Upgrade Standards to Improve Internet Privacy..." is
probably sufficient.   If someone wanted to republish that as an
Informational RFC, I'd hope that would not be controversial (if
it were, we have much deeper problems with this "perpass-attack"
draft).

On the other hand, if there is a real commitment to action, then
WGs have to be accountable for design decisions that do (or do
not) support the goal and be ready to explain their decisions,
even privacy-protecting ones that impose or increase costs to
performance, operations, or elsewhere.  And I would expect (not
merely fear) ADs to push back strongly on a WG that was
unwilling or unable to do that and expect Nomcoms to hold ADs
accountable if they did not enforce the intent of the rules.

It is not clear to me that the community is really willing to
make that commitment.  Fortunately, I'm lucky enough to not have
to make that call.  

But it seems to me that this document, especially with some of
the recently-proposed changes, is trying to simultaneously be 

	-- a general statement of principles that sounds good,
	encourages people to do good deeds wrt privacy and
	surveillance issues but doesn't represent a real,
	actionable, commitment by the IETF     and
	
	-- something far more substantial that actually changes
	the way we do things wrt this particular area.

I don't think it can be both.  And, if it is the latter, then
ADs who holding up a document with a DISCUSS or who try to force
a WG to more clearly justify its decisions are not being abusive
-- they are doing the job that the community has demanded of
them.   And that, IMO, is what is different from the various
notes that have said, more or less, "we don't need to worry
about ADs holding up documents and abusing the system because of
this draft because there are ample opportunities for abuse
already".  The concern is the AD who will say "just doing my job
and that document explicitly tells me that the community said
that was my job -- it isn't a judgment call whether or not it
is".    That is ok if it is what the community wants, but we
need to be careful what we wish for.

    john




From presnick@qti.qualcomm.com  Thu Jan 23 12:56:15 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE021A01B3; Thu, 23 Jan 2014 12:56:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3-Mxf6YeCU8; Thu, 23 Jan 2014 12:56:14 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 0B95B1A0161; Thu, 23 Jan 2014 12:56:13 -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=1390510573; x=1422046573; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oByWaso0T/b65bQQh3DHhEEyJIfaRK6176tfe7Sd0nk=; b=svWhhvE+AEe5wPvqjdSUKu7IRwgaB3yZhGChScxeJBRqR3Qml9evUZQt zYhrSqP0Tnp9ewdc5naNxvNV5bx/mFIYqeFNACyrKi6fNVtWfRkkALQLb glIIyuVi75ak/ZzoRbcpWtSect50Dz76LbgNDKv2jYfJ7zafNW76wfnUY w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="58466922"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 23 Jan 2014 12:56:12 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7327"; a="26081114"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Jan 2014 12:56:12 -0800
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 23 Jan 2014 12:50:12 -0800
Message-ID: <52E18081.1010709@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 14:50:09 -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: "Bradner, Scott" <sob@harvard.edu>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com> <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
In-Reply-To: <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 20:56:16 -0000

On 1/23/14 1:56 PM, Bradner, Scott wrote:
> while, in the end, this is true (the "necessarily infringed” requirement) I do not think it is a good thing to obsess about at the disclose-so-the-working-group-can-evaluate-the-technology stage since it is impossible to know if any particular IPR will wind up in this catagory until a RFC is finished - which would negate the whole reason for the disclosure
>    

I generally agree with that, though I think this gets to why I think 
having the "Note Well" state a plain-English, imprecise, overbroad 
summary is the right thing to do: The Note Well text should say, "You 
have to disclose IPR you know about. Not always, but maybe more than you 
think. If you're worried about specifically what, when, who, and how, 
you need to go read these other documents, and once you start 
participating, you've agreed to the specifics of what's in those 
documents. Got it?" Part of the reason that some of us pushed to change 
the current Note Well text was because people were *underdisclosing* 
what they were absolutely required to disclose by the BCP.

I'm really concerned about the amateur lawyering. If you're worried 
about this, go consult an attorney. The IESG consulted with Jorge about 
what's up there now, and though he preferred some additional escape 
clauses, he found the current text acceptable. If a bunch of corporate 
attorneys come out of the woodwork and say that they can't let their 
employees hit the "Acknowledge" button on the registration page, we'll 
revisit the issue I'm sure. But my guess is that you'll find that the 
exception language on the page now is sufficient to make them happy.

> maybe we should make that clear (disclose if you suspect that IPR relates not “is necessarily infringed”) in the 3979 update - this is what the rule used to be and the language Pete is focussing on was added and, apparently, has an undesired side effect
>    

I think you'll find that such a change is likely to (a) produce an 
unmanageable number of disclosures (because "you suspect that IPR 
relates" is a pretty low bar) and (b) that such a rule will cause 
heartburn among a bunch of folks. I'm not saying it's the wrong 
direction, but it's not obvious that it's the right direction either.

pr

> On Jan 23, 2014, at 1:09 PM, Pete Resnick<presnick@qti.qualcomm.com>  wrote:
>
>    
>> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>>      
>>> the actual rules are
>>> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
>>>
>>>        
>> No, that's not true. If you know of any of your own IPR *that is necessarily infringed* by implementing your contribution, you must disclose. And what it means to be "necessarily infringed" has some details to it, and it might not be even implementation that causes the problem. And that's why it says at the top of the current document that there are exceptions.
>>
>>      
>>> see - its not that hard to say this briefly
>>>        
>> Really, it is quite hard to state the rules briefly such that it doesn't include *more* than you are required to do. Your statement did not.
>>
>> pr

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


From hartmans@mit.edu  Thu Jan 23 13:13:10 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207041A008E for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6a-sjoa8dmO for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:13:08 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 9F9271A0012 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:13:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 13B4A205EA; Thu, 23 Jan 2014 16:10:16 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2C2LSKfX1-De; Thu, 23 Jan 2014 16:10:14 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 23 Jan 2014 16:10:14 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2F2E083DFC; Thu, 23 Jan 2014 16:13:05 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu> <98477509D05291683DB2CAC5@JcK-HP8200.jck.com>
Date: Thu, 23 Jan 2014 16:13:05 -0500
In-Reply-To: <98477509D05291683DB2CAC5@JcK-HP8200.jck.com> (John C. Klensin's message of "Thu, 23 Jan 2014 15:43:14 -0500")
Message-ID: <tslbnz2xuzi.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, Jari Arkko <jari.arkko@ericsson.com>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:13:10 -0000

>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:


    John> On the other hand, if there is a real commitment to action,
    John> then WGs have to be accountable for design decisions that do
    John> (or do not) support the goal and be ready to explain their
    John> decisions, even privacy-protecting ones that impose or
    John> increase costs to performance, operations, or elsewhere.  And
    John> I would expect (not merely fear) ADs to push back strongly on
    John> a WG that was unwilling or unable to do that and expect
    John> Nomcoms to hold ADs accountable if they did not enforce the
    John> intent of the rules.

Strongly agreed.
And if we don't have a community commitment to do that can we please be
honest with the world and tell everyone that when we look at the cost of
this issue it was something our community did not choose to pay?

    John> It is not clear to me that the community is really willing to
    John> make that commitment.  Fortunately, I'm lucky enough to not
    John> have to make that call.
I hope we are willing to make that commitment.

Note however that I do not want ADs pushing back at the end of the
process (unless WGs clearly failed to get adequate review of their
architectures up front.)

End-of-process security work is rarely all that productive.
You spend weeks or months fighting for little gain and for everyone
involved walking away with a sence of frustration and a diminished sense
of joy in the engineering challenges we face.

I want ADs to be pushing back in the early architecture phases.
Comments on early architecture drafts, and WG-decision-level appeals
filed early in the process are probably better tools for pushing back
on WGs that are not adequately considering privacy than late-stage
discuss positions requiring architectural change.

And as Eliot points out, the question of what balance in tradeoffs is
appropriate will evolve over time.  At the beginning if a WG does a good
job of considering something and you just don't like how they balanced
the issues, your only option is to start a broader discussion.  That's
how it should it be.  If community norms emerge, then there are tools
for applying those.

From touch@isi.edu  Thu Jan 23 13:16:16 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 288431A00C9; Thu, 23 Jan 2014 13:16:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ygOVmu-YtQFw; Thu, 23 Jan 2014 13:16:12 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC0C1A00B6; Thu, 23 Jan 2014 13:16:12 -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 s0NLFD9m002532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 13:15:14 -0800 (PST)
Message-ID: <52E18661.4060000@isi.edu>
Date: Thu, 23 Jan 2014 13:15:13 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com>
In-Reply-To: <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:16:16 -0000

On 1/22/2014 9:55 AM, Eggert, Lars wrote:
> Hi,
>
> On 2014-1-22, at 18:29, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>> Envision the following 4 (or more) scenarios for one Border Tunneling Routing
>> (BTR), BTR A, to send packets to another BTR, BTR B, on the path from ultimate
>> source S (somewhere before BTR A) to destination D (somewhere after BTR B).
>>
>> - Plain IP
>> - Some existing encapsulation like GRE
>> - A new, custom encapsulation
>> - Encapsulation using UDP
>>
>> What you seem to be claiming is that in case 4 we need to have congestion
>> detection and response at the intermediate forwarding node BTR A - but it
>> would not be required in cases 1-3? This makes no sense.

FWIW, the whole point of using UDP is to leverage the Internet's ability 
to interpret the tunneled traffic as application data - to manage it 
according to port-based flow interpretation.

There's a cost associated with that privilege - the cost of needing to 
react to congestion. That doesn't require 1-RTT, TCP-friendly dynamic 
congestion control; it does mean *reacting* to congestion in some way, 
over some timescale more than just ignoring things.

This should be expected of any tunneling system that encapsulates 
non-reactive flows - regardless of technology.

Joe

From touch@isi.edu  Thu Jan 23 13:20:49 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6866D1A0140; Thu, 23 Jan 2014 13:20:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2FiViWBbdTb; Thu, 23 Jan 2014 13:20:48 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 054481A013B; Thu, 23 Jan 2014 13:20:48 -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 s0NLK3mm003430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 13:20:04 -0800 (PST)
Message-ID: <52E18783.4020905@isi.edu>
Date: Thu, 23 Jan 2014 13:20:03 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122183237.0FE0918C144@mercury.lcs.mit.edu> <0DCB269E-D53D-4BF5-8D1A-42445ABBBB1E@netapp.com>
In-Reply-To: <0DCB269E-D53D-4BF5-8D1A-42445ABBBB1E@netapp.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:20:49 -0000

On 1/23/2014 2:37 AM, Eggert, Lars wrote:
> Since we're repeating ourselves, I'll again say that encapsulators are not forwarding nodes from the viewpoint of the network they tunnel over. They are traffic sources.

+1

Just as NATs act like sources to the networks they traverse (NATs being 
a kind of tunnel that replaces encapsulation with translation).

In both cases, they ought to behave just like any other source on that 
network.

Joe

From touch@isi.edu  Thu Jan 23 13:22:47 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAD3A1A01FD; Thu, 23 Jan 2014 13:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.235
X-Spam-Level: 
X-Spam-Status: No, score=-4.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjEYka13vFQA; Thu, 23 Jan 2014 13:22:45 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 23D0F1A007C; Thu, 23 Jan 2014 13:22:45 -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 s0NLMOTR003983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 13:22:24 -0800 (PST)
Message-ID: <52E18810.1010701@isi.edu>
Date: Thu, 23 Jan 2014 13:22:24 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, "Eggert, Lars" <lars@netapp.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401212058.s0LKwcu2066223@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401212058.s0LKwcu2066223@maildrop2.v6ds.occnc.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:22:47 -0000

Curtis,

If you're going with this argument (SHOULD vs MUST), then you need to 
explain exactly *why* you're not doing what's recommended. "SHOULD" 
isn't carte blanche to claim an exception.

And the need to avoid layered congestion control is a good justification 
for not layering TCP-friendly on top of TCP-friendly, but not for 
avoiding circuit breaker-style congestion controls/limits.

Joe

On 1/21/2014 12:58 PM, Curtis Villamizar wrote:
> Lars,
>
> The IETF consensus in RFC5405 was to put a SHOULD in regarding use of
> congestion control in tunneling protocols.
>
> RFC2119 states:
>
>    3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there
>       may exist valid reasons in particular circumstances to ignore a
>       particular item, but the full implications must be understood and
>       carefully weighed before choosing a different course.
>
> We have discussed the reasons why congestion control is in general a
> good thing.  We have also discussed why there may be valid reasons to
> not include congestion control in MPLS over UDP.
>
> The question is not whether there is already IETF consensus on
> congestion control in UDP in general.  There is consensus and that
> consensus was to use the word "SHOULD".
>
> The question we now face is whether MPLS in UDP needs to up the prior
> consensus to a MUST or can keep it as SHOULD.  I see one or maybe two
> people vigorously arguing to upgrade this to a MUST and otherwise
> consensus to keep this as SHOULD.  Further I see no objection except
> the same one or maybe two people to making the congestion control the
> topic of a later work if a need for it arises.  Consensus does not
> require unanimous agreeement.
>
> If we are trying to gauge consensus, maybe both you and I should sit
> back and let other people weigh in.
>
> Curtis
>
>
> In message <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
> "Eggert, Lars" writes:
>>
>> Hi,
>>
>> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
>>> You have made your assertions about your desire to uphold the purity
>>> of any new UDP applications and adhere to the BCP you wrote.
>>> =20
>>> You appear to be very nearly alone in this argument and certainly no
>>> one that works with MPLS is siding with you.
>>
>> the reason we wrote the RFC when I was TSV AD was that we were seeing a =
>> whole bunch of questionable uses of UDP over the eyars and we were =
>> having the same arguments over and over. That's why we decided to write =
>> down the practices we expect users of UDP to follow. This is yet another =
>> such questionable use.
>>
>> (Also, I don't appreciate you turning this into a personal argument.)
>
> Nothing personal intended.
>
> The important point is the sentence "You appear to be very nearly
> alone in this argument and certainly no one that works with MPLS is
> siding with you." was intended to point out that there is no consensus
> behind your argument regardless of how vigorously you make that
> argument.
>
>>> In the end we can put anything we want in the RFC *but* IETF has never
>>> truly had the final word on what vendors and operators do in provider
>>> networks.
>>
>> Aka the "take my toys and go home" argument. Heard it many times.
>
> It has been successful many times in the past.  It turns into the "its
> deployed so get over it" argument after a few years.
>
>>> In this case, regardless of what changes are made to the draft,
>>> implementations will offer at least the option for non-RFC behavior by
>>> using zero checksums and not using any congestion control.  And
>>> providers will make use of it, perhaps exclusively.
>>
>> And there's nothing wrong with that - the BCP even says that one SHOULD =
>> NOT use congestion control for some deployment cases.
>>
>> But for others, one SHOULD. For those, a mechanism needs to be =
>> available, i.e., it needs to be specified and implemented.
>>
>>> The document might as well reflect reality, despite reality not
>>> conforming to your notions of architectural purity.
>>
>> I'm sorry, but we have certain architectural principles in the Internet =
>> that we have IETF consensus on. At least since RFC2914, that includes =
>> the need to have congestion control in place.
>>
>> There are always special deployment scenarios where these principles do =
>> not apply, and we typically explain in applicability statements when out =
>> specifications can only be safely used under certain conditions. I don't =
>> see any such statement in draft-ietf-mpls-in-udp, which to me means it's =
>> targeted at general Internet-wide use.
>>
>>> The best course of action is to put a SHOULD in regarding checksums
>>> and put a SHOULD in regarding congestion avoidance.  Even the BCP does
>>> not go any further than to say a tunneling protocol SHOULD use
>>> congestion control and there were reasons that the word MUST was not
>>> acceptable in the BCP.
>>
>> The SHOULD for congestion control needs to actually describe a mechanism =
>> that can be used when needed. It can't be a blanket "you SHOULD use =
>> something but we don't tell you what it is"-statement.
>>
>>> If we are still arguing over two instances of SHOULD vs MUST we have
>>> wasted a lot of bandwidth on those two words.
>>
>> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs =
>> to be specified what is to be done. In the case of checksums, that's =
>> obvious (calculate it and check it); in the case of congestion control, =
>> some actual mechanism needs to be described (e.g., a circuit breaker).
>>
>>> IMHO The only remaining question is whether the document can go =
>> forward
>>> with the definition of congestion control for MPLS over UDP left out
>>> of scope and for another document if a need arises.
>>
>> In my opinion, it cannot.
>>
>>> If this is not acceptable to you (I doubt it is) please indicate what
>>> you would like to see in the document and since this is IETF last call
>>> where consensus matters and no one individual has veto power, we'll
>>> have to see if there is consensus behind your proposed changes.
>>
>> I would like the document to specify at the very least a circuit breaker =
>> mechanism, that stops the tunneled traffic if severe packet loss is =
>> detected along the path.
>>
>> And this isn't about an "individual veto". This is about a document that =
>> is at the moment in violation of IETF consensus at least as far back as =
>> RFC2914.
>>
>> Lars

From scott.brim@gmail.com  Thu Jan 23 13:24:14 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0285B1A0269 for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y6-AjtNWNanA for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:24:12 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8F3431A0197 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:24:12 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i7so2774447oag.8 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:24:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZYRQCqt2vuIviY/AqU9r0CVRlllMJsjrqZxeF8h7jPE=; b=y6X8CkAcwsDjAbz+s5gofw0T5QhM8f5Bgr5XvzS6lI28R3h0Gy4ruHO9jtBJ7aZxaE lPvUGjfvWsgUN20KQef8m9R1/5MLwqEl3WGaKqeeACFvX0lFYbekdxvehY8nhVo/mm1+ 125jFMrXjF9IjzhkNYP6yhTWD4uGq/SWbwNHMJTNTZMW5TVE+7KA0PJB72TzTSD8hTZM QqZ+Uk+kQX5TwaQLhcMbAHt7pvxxKurQZfXAhGOyT1PfzgKh/sm2DuChMp+E1dv2TRm/ jmgoYbERT12hs3N12gYyTVG63UhfOLAvRPih4hgtnvT/9bc3P0DhMeEi9VvdYRe51JUO 4Z0w==
X-Received: by 10.182.153.226 with SMTP id vj2mr9046716obb.26.1390512251593; Thu, 23 Jan 2014 13:24:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 23 Jan 2014 13:23:51 -0800 (PST)
In-Reply-To: <tslbnz2xuzi.fsf@mit.edu>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu> <98477509D05291683DB2CAC5@JcK-HP8200.jck.com> <tslbnz2xuzi.fsf@mit.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 23 Jan 2014 16:23:51 -0500
Message-ID: <CAPv4CP9eD3RdTfqkW_QMhomfbqEjn82PQz0ompkynGMrNxJFPw@mail.gmail.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>, Jari Arkko <jari.arkko@ericsson.com>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:24:14 -0000

On Thu, Jan 23, 2014 at 4:13 PM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:
>
>     John> On the other hand, if there is a real commitment to action,
>     John> then WGs have to be accountable for design decisions that do
>     John> (or do not) support the goal and be ready to explain their
>     John> decisions, even privacy-protecting ones that impose or
>     John> increase costs to performance, operations, or elsewhere.  And
>     John> I would expect (not merely fear) ADs to push back strongly on
>     John> a WG that was unwilling or unable to do that and expect
>     John> Nomcoms to hold ADs accountable if they did not enforce the
>     John> intent of the rules.
>
> Strongly agreed.
> And if we don't have a community commitment to do that can we please be
> honest with the world and tell everyone that when we look at the cost of
> this issue it was something our community did not choose to pay?

Being ready to explain decisions (or positions) is fine. The problem
was the word "justify". When do we know that a decision is justified?
Who decides? That's an undefined metric. WG decisions are explained,
and critiqued, all the time, by everyone.

Personally I hope we don't develop too "mature" a concept of what
we're including in pervasive monitoring, because we need to be open to
new ideas all the time. Therefore I hope we never develop criteria by
which a PM consideration could be "justified".

> Note however that I do not want ADs pushing back at the end of the
> process (unless WGs clearly failed to get adequate review of their
> architectures up front.)

(Aside: That's circular -- unless the critique is based on new ideas
that emerged between WG last call and a telechat, then by definition a
late critique of an architectural issue means it failed to get
adequate review at the proper time.)

> I want ADs to be pushing back in the early architecture phases.
> Comments on early architecture drafts, and WG-decision-level appeals
> filed early in the process are probably better tools for pushing back
> on WGs that are not adequately considering privacy than late-stage
> discuss positions requiring architectural change.

Yes, and we encourage that with the paragraph as it is, without "justified".

> And as Eliot points out, the question of what balance in tradeoffs is
> appropriate will evolve over time.  At the beginning if a WG does a good
> job of considering something and you just don't like how they balanced
> the issues, your only option is to start a broader discussion.  That's
> how it should it be.  If community norms emerge, then there are tools
> for applying those.

Yes.

Do we have agreement?

Scott

From hartmans@mit.edu  Thu Jan 23 13:32:17 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40E981A012B for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:32:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ueyLYaSwzu8I for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:32:16 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFA31A00C9 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:32:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 8B8D8205EA; Thu, 23 Jan 2014 16:29:23 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhmkVlQ5CHuY; Thu, 23 Jan 2014 16:29:23 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Thu, 23 Jan 2014 16:29:23 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E1A2083DFC; Thu, 23 Jan 2014 16:32:13 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie> <tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu> <98477509D05291683DB2CAC5@JcK-HP8200.jck.com> <tslbnz2xuzi.fsf@mit.edu> <CAPv4CP9eD3RdTfqkW_QMhomfbqEjn82PQz0ompkynGMrNxJFPw@mail.gmail.com>
Date: Thu, 23 Jan 2014 16:32:13 -0500
In-Reply-To: <CAPv4CP9eD3RdTfqkW_QMhomfbqEjn82PQz0ompkynGMrNxJFPw@mail.gmail.com> (Scott Brim's message of "Thu, 23 Jan 2014 16:23:51 -0500")
Message-ID: <tsly526wfj6.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, Jari Arkko <jari.arkko@ericsson.com>, draft-farrell-perpass-attack.all@tools.ietf.org, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, John C Klensin <john-ietf@jck.com>, Sam Hartman <hartmans-ietf@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:32:17 -0000

>>>>> "Scott" == Scott Brim <scott.brim@gmail.com> writes:

    Scott> Being ready to explain decisions (or positions) is fine. The
    Scott> problem was the word "justify". When do we know that a
    Scott> decision is justified?  Who decides? That's an undefined
    Scott> metric. WG decisions are explained, and critiqued, all the
    Scott> time, by everyone.

I view justify and explain as synonyms in the text I proposed.
If people are OK with explain but not justify, I would support
publication of the document with that substitution.

I realize I may be in the rough regardless; I'm just stating my position
in case it is useful to those making a consensus call.

my problem is that by removing justify and not replacing it with
something like explain, then I see that as an active failure to get
consensus that a WG should have to (explain|justify--remember I don't
see a difference) the perpass implications of its architecture.
Without community agreement in favor of that, I think we have no
meaningful commitment to perpass mittigation.

From touch@isi.edu  Thu Jan 23 13:39:25 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBF421A0140; Thu, 23 Jan 2014 13:39:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzEqwJrABF4R; Thu, 23 Jan 2014 13:39:23 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id E57821A00C9; Thu, 23 Jan 2014 13:39:23 -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 s0NLcwbP007223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 13:38:58 -0800 (PST)
Message-ID: <52E18BF1.1040004@isi.edu>
Date: Thu, 23 Jan 2014 13:38:57 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Edward Crabbe <edc@google.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>
In-Reply-To: <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:39:26 -0000

On 1/23/2014 1:27 PM, Edward Crabbe wrote:
> Part of the point of using UDP is to make use of lowest common
> denominator forwarding hardware in introducing entropy to protocols that
> lack it ( this is particularly true of the GRE in UDP use case also
> under discussion elsewhere).
>
> The tunnel is not the source of the traffic.  The _source of the
> traffic_ is the source of the traffic.

To the Internet, the tunnel encapusulator is the source of traffic. 
Tracing the data back further than that is a mirage at best - and 
irrelevant.

The tunnel head-end is responsible for the tunnel walking, talking, and 
quaking like a duck (host). When the tunnel head-end knows something 
about the ultimate origin of the traffic - whether real, imagined, or 
from Asgard - then it has done it's duty (e.g., that it's already 
congestion controlled).

But that head end is responsible, regardless of what it knows or 
doesn't. And when it doesn't know, the only way to be responsible is to 
put in its own reactivity.

> The originating application
> who's traffic is being tunneled should be responsible for congestion
> control, or lack there of.

Perhaps it should be, but that's an agreement between whomever 
implements/deploys the tunnel headend and whomever provides the 
originating traffic to them. The problem is that this isn't true for the 
typical use case for this kind of encapsulation.

I.e., if we were talking about MPLS traffic that already was reactive, 
we wouldn't be claiming the need for additional encapsulator mechanism. 
It's precisely because nothing is known about the MPLS traffic that the 
encapsulator needs to act.

 > Are we advocating a return to intermediate
> congestion control (I like X.25 as much as the next guy, but...).  This
> is a very stark change of direction.
>
> I think mandating congestion control  is not technically sound from
> either a theoretical (violation of end to end principle, stacking of
> congestion control algorithms leading to complex and potentially
> suboptimal results) or economic perspective (as a very large backbone,
> we've been doing just fine without intermediate congestion management
> thank you very much, and I have 0 desire to pay for a cost prohibitive,
> unnecessary feature in silicon.)

Write that up, and we'll see how it turns out in the IETF. However, 
right now, the IETF BCPs do require reactive congestion management of 
transport streams.

If you don't want/like that, then either don't use transport 
encapsulation, or change the BCPs.

> I get Lars comments regarding reach, to some limited extent.
>   Ultimately, the implication seems to be that the protocols riding the
> L2 network will have no form of congestion control and are fundamentally
> different than protocols that would reside on a typical wan.  I have
> some serious doubts about this, although I'm sure this is the case in
> some specialized environments.  At any rate, it seems to me that a stern
> warning regarding edge filtering on interdomain boundaries will be
> sufficient.

My concern may be slightly different that his. My concern is that you 
want the benefits of a UDP header, but don't like the responsibilities 
that come along with it.

Joe


From ted.ietf@gmail.com  Thu Jan 23 13:48:17 2014
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CBA81A0384; Thu, 23 Jan 2014 13:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2r8n21OQq4pU; Thu, 23 Jan 2014 13:48:14 -0800 (PST)
Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 90D241A0380; Thu, 23 Jan 2014 13:48:14 -0800 (PST)
Received: by mail-ie0-f182.google.com with SMTP id lx4so1946832iec.13 for <multiple recipients>; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0jPnA73ijg2L2TDlU5j13UgZLJblLZp/4g+ki8rvJSU=; b=FjpDpCCtniYnHzUehm+vuiCGpeelpzerBbVIdKQQGrEfTU9lf6YLlCTJAyHa4LNmB3 fGj1KN8hiS4xvvDesrxmUfJCOoGnhxyQZ2icnAbmTQvUbEaoy6NNATgKKrFQes2nQZTE Xlu/h0u928EH28ixVQx99JkzyU+iZ1OdeaM6OijrDcbIl/5A7rqHXWgLZzRPbyB8aVyt NkwvFp/anreO2tVkKouAbQHufAUVsc7uMooDRL7Pjai7dDKEU4r2MWUt6AtZVLKPBOLS 0tLswQ6sg4IPjU9zABBa1247e1DTQpAAAY1s1/FPfPrcEhptKLMZZnPoGWtTegLeynPa 8gVQ==
MIME-Version: 1.0
X-Received: by 10.50.60.99 with SMTP id g3mr1443626igr.13.1390513693577; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
Received: by 10.43.65.14 with HTTP; Thu, 23 Jan 2014 13:48:13 -0800 (PST)
In-Reply-To: <52E18081.1010709@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E15AE2.7030508@qti.qualcomm.com> <E3E4E04A-B342-4FDC-89EC-5FC8F7CEAAF0@harvard.edu> <52E18081.1010709@qti.qualcomm.com>
Date: Thu, 23 Jan 2014 13:48:13 -0800
Message-ID: <CA+9kkMAdBnwGEVf86F8wiX1R3h81cADuv7RS-L3a1ttML-bP_g@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Ted Hardie <ted.ietf@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=047d7b10cf25c2d82404f0aa3228
Cc: IETF WG Chairs <wgchairs@ietf.org>, "Bradner, Scott" <sob@harvard.edu>, Jorge Contreras <contreraslegal@att.net>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:48:17 -0000

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

On Thu, Jan 23, 2014 at 12:50 PM, Pete Resnick <presnick@qti.qualcomm.com>w=
rote:

> On 1/23/14 1:56 PM, Bradner, Scott wrote:
>
>> while, in the end, this is true (the "necessarily infringed=94 requireme=
nt)
>> I do not think it is a good thing to obsess about at the
>> disclose-so-the-working-group-can-evaluate-the-technology stage since it
>> is impossible to know if any particular IPR will wind up in this catagor=
y
>> until a RFC is finished - which would negate the whole reason for the
>> disclosure
>>
>>
>
> I generally agree with that, though I think this gets to why I think
> having the "Note Well" state a plain-English, imprecise, overbroad summar=
y
> is the right thing to do: The Note Well text should say, "You have to
> disclose IPR you know about. Not always, but maybe more than you think. I=
f
> you're worried about specifically what, when, who, and how, you need to g=
o
> read these other documents, and once you start participating, you've agre=
ed
> to the specifics of what's in those documents. Got it?" Part of the reaso=
n
> that some of us pushed to change the current Note Well text was because
> people were *underdisclosing* what they were absolutely required to
> disclose by the BCP.
>
> I'm really concerned about the amateur lawyering. If you're worried about
> this, go consult an attorney. The IESG consulted with Jorge about what's =
up
> there now, and though he preferred some additional escape clauses, he fou=
nd
> the current text acceptable. If a bunch of corporate attorneys come out o=
f
> the woodwork and say that they can't let their employees hit the
> "Acknowledge" button on the registration page, we'll revisit the issue I'=
m
> sure. But my guess is that you'll find that the exception language on the
> page now is sufficient to make them happy.
>
> I had a quick chat with our legal folks.  They understood that the intent
of the new Note Well language was to give a heads up that there are rules
which are presented elsewhere.  They did feel, however, that the second
bullet captured that
spirit
less well than the first.  Perhaps language that said something like "You
are aware that there are patent disclosure requirements" would do that
slightly better.


regards,

Ted





>
>  maybe we should make that clear (disclose if you suspect that IPR relate=
s
>> not =93is necessarily infringed=94) in the 3979 update - this is what th=
e rule
>> used to be and the language Pete is focussing on was added and, apparent=
ly,
>> has an undesired side effect
>>
>>
>
> I think you'll find that such a change is likely to (a) produce an
> unmanageable number of disclosures (because "you suspect that IPR relates=
"
> is a pretty low bar) and (b) that such a rule will cause heartburn among =
a
> bunch of folks. I'm not saying it's the wrong direction, but it's not
> obvious that it's the right direction either.
>
> pr
>
>
>  On Jan 23, 2014, at 1:09 PM, Pete Resnick<presnick@qti.qualcomm.com>
>>  wrote:
>>
>>
>>
>>> On 1/23/14 11:58 AM, Bradner, Scott wrote:
>>>
>>>
>>>> the actual rules are
>>>>         1/ if you know of any of your IPR in a contribution you make,
>>>> you must disclose
>>>>
>>>>
>>>>
>>> No, that's not true. If you know of any of your own IPR *that is
>>> necessarily infringed* by implementing your contribution, you must
>>> disclose. And what it means to be "necessarily infringed" has some deta=
ils
>>> to it, and it might not be even implementation that causes the problem.=
 And
>>> that's why it says at the top of the current document that there are
>>> exceptions.
>>>
>>>
>>>
>>>> see - its not that hard to say this briefly
>>>>
>>>>
>>> Really, it is quite hard to state the rules briefly such that it doesn'=
t
>>> include *more* than you are required to do. Your statement did not.
>>>
>>> pr
>>>
>>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Thu, Jan 23, 2014 at 12:50 P=
M, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualco=
mm.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrote:<b=
r><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 1/23=
/14 1:56 PM, Bradner, Scott wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
while, in the end, this is true (the &quot;necessarily infringed=94 require=
ment) I do not think it is a good thing to obsess about at the disclose-so-=
the-working-group-<u></u>can-evaluate-the-technology stage since it is impo=
ssible to know if any particular IPR will wind up in this catagory until a =
RFC is finished - which would negate the whole reason for the disclosure<br=
>

=A0 =A0<br>
</blockquote>
<br></div>
I generally agree with that, though I think this gets to why I think having=
 the &quot;Note Well&quot; state a plain-English, imprecise, overbroad summ=
ary is the right thing to do: The Note Well text should say, &quot;You have=
 to disclose IPR you know about. Not always, but maybe more than you think.=
 If you&#39;re worried about specifically what, when, who, and how, you nee=
d to go read these other documents, and once you start participating, you&#=
39;ve agreed to the specifics of what&#39;s in those documents. Got it?&quo=
t; Part of the reason that some of us pushed to change the current Note Wel=
l text was because people were *underdisclosing* what they were absolutely =
required to disclose by the BCP.<br>

<br>
I&#39;m really concerned about the amateur lawyering. If you&#39;re worried=
 about this, go consult an attorney. The IESG consulted with Jorge about wh=
at&#39;s up there now, and though he preferred some additional escape claus=
es, he found the current text acceptable. If a bunch of corporate attorneys=
 come out of the woodwork and say that they can&#39;t let their employees h=
it the &quot;Acknowledge&quot; button on the registration page, we&#39;ll r=
evisit the issue I&#39;m sure. But my guess is that you&#39;ll find that th=
e exception language on the page now is sufficient to make them happy.<div =
class=3D"im">
<br></div></blockquote><div><span style=3D"color:rgb(34,34,34);font-family:=
arial,sans-serif;font-size:12.8px;font-style:normal;font-variant:normal;fon=
t-weight:normal;letter-spacing:normal;line-height:normal;text-align:left;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backg=
round-color:rgb(255,255,255);display:inline!important;float:none">I had a q=
uick chat with our legal folks. =A0They understood that the intent of the n=
ew Note Well language was to give a heads up that there are rules which are=
 presented elsewhere. =A0They did feel, however, that the second bullet cap=
tured that=A0<div class=3D"gmail_default" style=3D"font-family:georgia,seri=
f;display:inline">
spirit</div> less well than the first. =A0Perhaps language that said someth=
ing like &quot;You are aware that there are patent disclosure requirements&=
quot; would do that slightly better.</span><br><br><br><div class=3D"gmail_=
default" style=3D"font-family:georgia,serif">
regards,<br><br>Ted</div><br><br><br>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex"><div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
maybe we should make that clear (disclose if you suspect that IPR relates n=
ot =93is necessarily infringed=94) in the 3979 update - this is what the ru=
le used to be and the language Pete is focussing on was added and, apparent=
ly, has an undesired side effect<br>

=A0 =A0<br>
</blockquote>
<br></div>
I think you&#39;ll find that such a change is likely to (a) produce an unma=
nageable number of disclosures (because &quot;you suspect that IPR relates&=
quot; is a pretty low bar) and (b) that such a rule will cause heartburn am=
ong a bunch of folks. I&#39;m not saying it&#39;s the wrong direction, but =
it&#39;s not obvious that it&#39;s the right direction either.<span class=
=3D""><font color=3D"#888888"><br>

<br>
pr</font></span><div class=3D""><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
On Jan 23, 2014, at 1:09 PM, Pete Resnick&lt;<a href=3D"mailto:presnick@qti=
.qualcomm.com" target=3D"_blank">presnick@qti.qualcomm.<u></u>com</a>&gt; =
=A0wrote:<br>
<br>
=A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
On 1/23/14 11:58 AM, Bradner, Scott wrote:<br>
=A0 =A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
the actual rules are<br>
=A0 =A0 =A0 =A0 1/ if you know of any of your IPR in a contribution you mak=
e, you must disclose<br>
<br>
=A0 =A0 =A0 =A0<br>
</blockquote>
No, that&#39;s not true. If you know of any of your own IPR *that is necess=
arily infringed* by implementing your contribution, you must disclose. And =
what it means to be &quot;necessarily infringed&quot; has some details to i=
t, and it might not be even implementation that causes the problem. And tha=
t&#39;s why it says at the top of the current document that there are excep=
tions.<br>

<br>
=A0 =A0 =A0<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
see - its not that hard to say this briefly<br>
=A0 =A0 =A0 =A0<br>
</blockquote>
Really, it is quite hard to state the rules briefly such that it doesn&#39;=
t include *more* than you are required to do. Your statement did not.<br>
<br>
pr<br>
</blockquote></blockquote>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--047d7b10cf25c2d82404f0aa3228--

From l.wood@surrey.ac.uk  Thu Jan 23 14:08:48 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F891A00AA; Thu, 23 Jan 2014 14:08:48 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nX8fG-v5Wz7s; Thu, 23 Jan 2014 14:08:47 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id 37EC71A0091; Thu, 23 Jan 2014 14:08:46 -0800 (PST)
Received: from [85.158.136.51:43593] by server-17.bemta-5.messagelabs.com id 65/FB-19152-CE291E25; Thu, 23 Jan 2014 22:08:44 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-49.messagelabs.com!1390514924!18829655!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26082 invoked from network); 23 Jan 2014 22:08:44 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-4.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 23 Jan 2014 22:08:44 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 23 Jan 2014 22:08:43 +0000
From: <l.wood@surrey.ac.uk>
To: <presnick@qti.qualcomm.com>, <fluffy@cisco.com>
Date: Thu, 23 Jan 2014 22:08:12 +0000
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: Ac8YZWs8U98barEPT3q+jCOoIA73CAAIjBFM
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346E5@EXMB01CMS.surrey.ac.uk>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>, <52E15937.8010600@qti.qualcomm.com>
In-Reply-To: <52E15937.8010600@qti.qualcomm.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: iesg@ietf.org, wgchairs@ietf.org, mary.ietf.barnes@gmail.com, ietf@ietf.org, sob@harvard.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:08:48 -0000

Pete,

is that your qualified legal opinion in the appropriate jurisdiction?

thanks,

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Pete Resnick [presnick@qti.=
qualcomm.com]
Sent: 23 January 2014 18:02
To: Cullen Jennings (fluffy)
Cc: IETF WG Chairs; ietf@ietf.org Mailing List; Scott Bradner; IESG IESG; M=
ary Barnes
Subject: Re: Problem with new Note Well

On 1/23/14 11:25 AM, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register witho=
ut clicking "I agree" to it.

You are not asked to click "I agree" to any statement. You are asked to
"Acknowledge" that you read it. And the statement says right at the top:

"This summary is only meant to point you in the right direction, and
does not contain all the details. Exceptions may apply."

So by participating, there are things that you are agreeing to that are
not on this page, and there are exceptions to things on this page that
you don't have to agree to do.

The only thing that this page does is make you "Acknowledge" that you've
got homework to do about rules for your participation.

pr

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


From fluffy@cisco.com  Thu Jan 23 14:30:28 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 749BD1A035C; Thu, 23 Jan 2014 14:30:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S3uPF6wX4CFy; Thu, 23 Jan 2014 14:30:24 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id E1E951A023D; Thu, 23 Jan 2014 14:30:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1284; q=dns/txt; s=iport; t=1390516223; x=1391725823; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=BQ6Wn+QTo3jfS3CYV/2fFkEaUZbmJ816z/BUf5IbU0o=; b=RlxKfYJbHjZ9mpG0ScusRvK0bVx+EFbfhkHr9NdM4DNICIu10E6gFMCL S6q+2BPDBwXoI/WjKtOKTdx1/YguCuzfian2nzqcDujEkCA7PmoFt3umb YtjCCornDQF0a7FcG7biBy4X7RGUTDvahcbP7H2P0FnT1x1eGm2GvZCwa w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFACqX4VKtJV2b/2dsb2JhbABagwyBDrw3gRUWdIIlAQEBAwF5BQsCAQgOCi4yJQIEDgWHfQjHHheOTTMHgySBFAEDiRCPE5IYgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,709,1384300800"; d="scan'208";a="15116727"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-6.cisco.com with ESMTP; 23 Jan 2014 22:30:18 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0NMUI1Y026540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 22:30:18 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 16:30:18 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGIqxCJjiC+6Mn0KbkcizeejIsw==
Date: Thu, 23 Jan 2014 22:30:17 +0000
Message-ID: <057D93E6-9311-44AA-A7B0-685FBB850D5F@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <18480766-BA47-445B-8C75-5DD261F94A76@cisco.com> <52E15EAA.8060301@qti.qualcomm.com>
In-Reply-To: <52E15EAA.8060301@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <C0286DA5CB82B94DBC3E3F7992761733@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, IESG IESG <iesg@ietf.org>, Scott Bradner <sob@harvard.edu>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:30:28 -0000

On Jan 23, 2014, at 11:25 AM, Pete Resnick <presnick@qti.qualcomm.com> wrot=
e:

> On 1/23/14 12:07 PM, Cullen Jennings (fluffy) wrote:
>> Pete,  what do you think "Acknowledge" means on a from like this? ( I wi=
ll note it does not say "I Acknowledge I read this but may not agree with i=
t" )
>>  =20
>=20
> You are acknowledging that there are rules (not fully specified here) tha=
t you have to go read and abide by if you show up and participate at the me=
eting. When you show up and participate at the meeting, you are agreeing to=
 a bunch of things that are not on this page.
>=20
> Are you saying that you don't agree that there are exceptions to what's o=
n this page?
>=20

Pete, I am saying that this page is likely to be used to undermine the cred=
ibility of IETF participants in patent trials. That is a bad thing.=20

We both agree the BCPs do NOT say=20

    If you are aware that any contribution (something written, said, or dis=
cussed in any IETF context) is covered by patents or patent applications, y=
ou must disclose that fact.

So I do not think it is OK for the IESG to be making me click "Acknowledge"=
 to a page that contains the above sentence. I have no problem with acknowl=
edging I am bound by the rules BCP 79.=20











From worley@shell01.TheWorld.com  Thu Jan 23 14:45:16 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 532AE1A0474 for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 14:45:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BNHODf54xRia for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 14:45:14 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 548371A0462 for <ietf@ietf.org>; Thu, 23 Jan 2014 14:45:14 -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 s0NMj79x030817; Thu, 23 Jan 2014 17:45:09 -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 s0NMj6CJ3448760; Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0NMj6uH3447931; Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Date: Thu, 23 Jan 2014 17:45:06 -0500 (EST)
Message-Id: <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Pete Resnick <presnick@qti.qualcomm.com>
In-reply-to: <52E15937.8010600@qti.qualcomm.com> (presnick@qti.qualcomm.com)
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com>
Cc: fluffy@cisco.com, wgchairs@ietf.org, ietf@ietf.org, sob@harvard.edu, iesg@ietf.org, mary.ietf.barnes@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:45:16 -0000

> From: Pete Resnick <presnick@qti.qualcomm.com>
> 
> You are not asked to click "I agree" to any statement. You are asked
> to "Acknowledge" that you read it. And the statement says right at
> the top:
> 
> "This summary is only meant to point you in the right direction, and 
> does not contain all the details. Exceptions may apply."

> From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
> 
> "If you are aware that any contribution (something written, said, or
> discussed in any IETF context) is covered by patents or patent
> applications, you must disclose that fact."

Surely we can write a better statement than what Cullen quotes.  To
begin with, it contains the word "must".  And while the statment is
amplified with "does not contain all the details", can we not provide
a proper pointer to the details?

Not being fully informed about this subject, it seems to me that it
would be far better to say:

    "By participating in an IETF discussion, you agree that if you are
    aware that any contribution (something written, said, or discussed
    in any IETF context) to that discussion is covered by patents or
    patent applications, you may be required to disclose that fact.
    The specific requirements are described in BCP 79."

Dale

From fluffy@cisco.com  Thu Jan 23 14:50:40 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A420F1A0403; Thu, 23 Jan 2014 14:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fbmSC2rKxRf6; Thu, 23 Jan 2014 14:50:37 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id C5BA31A007C; Thu, 23 Jan 2014 14:50:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1467; q=dns/txt; s=iport; t=1390517437; x=1391727037; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=+KUxHza109fhyW0j1DNTqxTElZWmUUKlsPcbx8uhwmQ=; b=T86SHDRgcZAUc9MePpWk/MPN8rQxMpns8NziGHSM4h/7Jjn0y6tU00EL wxReI/SM/l0frVZCyrYIDUekmPdDjNNdg0FL6HfSiP50HtQ7MetHs96lY aC/MB/c6PlYtHnnc+DOT5nRRWt5EYQ7AWmdZ6ibtxavKzFsi+LH1Z5faR E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAGqc4VKtJXHB/2dsb2JhbABagwyBDrw3gRYWdIIlAQEBAwF5EAIBCBUxMiUCBA4Fh30IxyAXjwAHgySBFAEDmCOSGIMtgio
X-IronPort-AV: E=Sophos;i="4.95,709,1384300800"; d="scan'208";a="299370729"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 23 Jan 2014 22:50:36 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0NMoZHP030051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 23 Jan 2014 22:50:35 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Thu, 23 Jan 2014 16:50:35 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGIzTSIiTtRgEUkSf0hEoiuKs/ZqTToUA
Date: Thu, 23 Jan 2014 22:50:34 +0000
Message-ID: <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
In-Reply-To: <201401232245.s0NMj6uH3447931@shell01.TheWorld.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C1720E7E6D65294FACE2516DB48D3BCA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 22:50:40 -0000

On Jan 23, 2014, at 3:45 PM, Dale R. Worley <worley@ariadne.com> wrote:

>> From: Pete Resnick <presnick@qti.qualcomm.com>
>>=20
>> You are not asked to click "I agree" to any statement. You are asked
>> to "Acknowledge" that you read it. And the statement says right at
>> the top:
>>=20
>> "This summary is only meant to point you in the right direction, and=20
>> does not contain all the details. Exceptions may apply."
>=20
>> From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
>>=20
>> "If you are aware that any contribution (something written, said, or
>> discussed in any IETF context) is covered by patents or patent
>> applications, you must disclose that fact."
>=20
> Surely we can write a better statement than what Cullen quotes.  To
> begin with, it contains the word "must".  And while the statment is
> amplified with "does not contain all the details", can we not provide
> a proper pointer to the details?
>=20
> Not being fully informed about this subject, it seems to me that it
> would be far better to say:
>=20
>    "By participating in an IETF discussion, you agree that if you are
>    aware that any contribution (something written, said, or discussed
>    in any IETF context) to that discussion is covered by patents or
>    patent applications, you may be required to disclose that fact.
>    The specific requirements are described in BCP 79."
>=20
> Dale

I=92d be fine with Dale=92s proposal.=20


From touch@isi.edu  Thu Jan 23 15:57:26 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49BF71A03E6; Thu, 23 Jan 2014 15:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dUbHBaI_hRIN; Thu, 23 Jan 2014 15:57:23 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id A34F41A01D3; Thu, 23 Jan 2014 15:57:23 -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 s0NNukiX004611 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 15:56:46 -0800 (PST)
Message-ID: <52E1AC3E.2040204@isi.edu>
Date: Thu, 23 Jan 2014 15:56:46 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Edward Crabbe <edc@google.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com>
In-Reply-To: <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 23:57:26 -0000

On 1/23/2014 3:32 PM, Edward Crabbe wrote:
> Joe, thanks for your response. Comments inline:
>
>
>     On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>
>         Part of the point of using UDP is to make use of lowest common
>         denominator forwarding hardware in introducing entropy to
>         protocols that
>         lack it ( this is particularly true of the GRE in UDP use case also
>         under discussion elsewhere).
>
>         The tunnel is not the source of the traffic.  The _source of the
>         traffic_ is the source of the traffic.
>
>
>     To the Internet, the tunnel encapusulator is the source of traffic.
>     Tracing the data back further than that is a mirage at best - and
>     irrelevant.
>
>
> The 'internet' cares about characteristics of reactivity to congestion.
>   This is guaranteed by the /source of the traffic/ independent of any
> intermediate node.

Are you prepared to make that a requirement of this document, i.e., that 
the only MPLS traffic that can be UDP encapsulated is known to react to 
congestion?

How exactly can you know that?

>     The tunnel head-end is responsible for the tunnel walking, talking,
>     and quaking like a duck (host). When the tunnel head-end knows
>     something about the ultimate origin of the traffic - whether real,
>     imagined, or from Asgard - then it has done it's duty (e.g., that
>     it's already congestion controlled).
>
>     But that head end is responsible, regardless of what it knows or
>     doesn't. And when it doesn't know, the only way to be responsible is
>     to put in its own reactivity.
>
> This is not fact; it's actually precisely the principle  we're currently
> arguing about.  ;)

Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.

We can continue to debate it, but until it's been *changed* by a 
revision, it remains BCP.

> I would posit:
>
> The tunnel doesn't have to know anything about congestion or performance
> characteristics because the originating application must.

That works only if you know that fact about the originating application. 
However, there are plenty of applications whose traffic goes over MPLS 
that isn't congestion reactive or bandwidth-limited.

 > See GRE,
> MPLS, many other tunnel types,

This isn't an issue for all tunnels until they enter the Internet...

> including several existing within the
> IETF that make use of an outer UDP header.

Which are all already supposed to follow the recommendations of RFC5405. 
To the extent that they don't, they don't agree with that BCP.

I'm not saying such things never can or will exist, but I don't think 
the IETF should be self-contradictory. We already agreed as a group on 
such BCPs and other standards, and new standards-track docs need to 
follow them.

>         The originating application
>         who's traffic is being tunneled should be responsible for congestion
>         control, or lack there of.
>
>     Perhaps it should be, but that's an agreement between whomever
>     implements/deploys the tunnel headend and whomever provides the
>     originating traffic to them. The problem is that this isn't true for
>     the typical use case for this kind of encapsulation.
>
> How so?  As mentioned before, this is the same case as standard GRE/MPLS
> etc.

It's putting MPLS inside UDP. That's a different case, and the reason 
RFC5405 applies.

>     I.e., if we were talking about MPLS traffic that already was
>     reactive, we wouldn't be claiming the need for additional
>     encapsulator mechanism. It's precisely because nothing is known
>     about the MPLS traffic that the encapsulator needs to act.
>
> The MPLS traffic doesn't have to be reactive, it's the applications
> being encapsulated / traversing a particular tunnel that are responsible
> for and aware of path and congestion charateristics.  Because the MPLS
> head end knows nothing about the /end to end application 'session'/
> characteristics it /shouldn't/ have anything to do with congestion
> management.

OK, so what you're saying is that "traffic using this encapsulation MUST 
be known to be congestion reactive". Put that in the doc and we'll 
debate whether we believe it.

But right now you're basically saying that because you think it's 
someone else's problem (the originating application), it isn't yours. 
The difficulty with that logic is that you (the tunnel headend) is 
responsible to ensure that this is true - either by *knowing* that the 
originating traffic is congestion reactive, or by putting in its own 
mechanism to ensure that this happens if the originating application isn't.

>      > Are we advocating a return to intermediate
>
>         congestion control (I like X.25 as much as the next guy,
>         but...).  This
>         is a very stark change of direction.
>
>         I think mandating congestion control  is not technically sound from
>         either a theoretical (violation of end to end principle, stacking of
>         congestion control algorithms leading to complex and potentially
>         suboptimal results) or economic perspective (as a very large
>         backbone,
>         we've been doing just fine without intermediate congestion
>         management
>         thank you very much, and I have 0 desire to pay for a cost
>         prohibitive,
>         unnecessary feature in silicon.)
>
>     Write that up, and we'll see how it turns out in the IETF. However,
>     right now, the IETF BCPs do require reactive congestion management
>     of transport streams.
>
> Which part?  The end-to-end principle, or the aversion to congestion
> control stacking?  These have been implicit in all tunneling protocols
> produced by the IETF for the modern internet.

Sure, and that's reflected in RFC5405 already. However, please, PLEASE 
appreciate that NOBODY here is asking you to put in "congestion control 
stacking"; that happens when you run two dynamic, reactive control 
algorithms using the same timescale on top of each other.

Equally well-known in CC circles is that you CAN - and often *should* - 
stack different kinds of mechanisms at different layers with different 
timescales. E.g., that's why we have an AQM WG - because even when all 
the traffic is TCP, that's not quite enough inside the network. That's 
also why Lars was suggesting something coarse on a longer timescale - a 
circuit breaker - rather than AIMD on a RTT basis.

Keep in mind as well that the E2E argument says that you can't get an 
E2E service by composing the equivalent HBH one; it also says that HBH 
mechanisms can be required for efficiency. That's what we're talking 
about here - the efficiency impact of congestion, not the overall 
correctness of E2E control.

>     If you don't want/like that, then either don't use transport
>     encapsulation, or change the BCPs.
>
> These BCPs are defined for an originating /application/.

Yes, and I don't understand why you (and others) keep thinking it 
matters that there are layers of things behind the tunnel head end. It 
doesn't - unless you KNOW what those layers are, and can ensure that 
they behave as you expect.

> In this case
> the UDP header is simply a shim header applied to existing application
> traffic.

It's not "simply a shim" - if that's the case, use IP and we're done. No 
need for congestion control.

The reason congestion issues arise is because you're inserting a header 
****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.

If you put in a UDP-like header that nobody in the Internet would 
interpret, this wouldn't be an issue.

But you simply cannot expect the Internet to treat you like 
"application" traffic if you won't enforce acting like that traffic too.

> The tunnel head does not introduce traffic independent of the
> originating application.

The Internet ****neither knows nor cares****.

To the Internet, the head-end is the source. Whatever data the head end 
puts inside the UDP packets *is application data* to the rest of the 
Internet.

Again, if you are saying that you know so much about the originating 
source that you know you don't need additional mechanism at the headend, 
say so - but then live by that requirement.

If *any* MPLS traffic could show up at the headend, then it becomes the 
headend's responsibility to do something.

---

Consider the following case:

	- video shows up inside the OS, destined for the network

	- software X bundles that video and sends it to go out

	- software Y puts that data into UDP packets to go
	to the Internet

So what's the "application" here? To the Internet, it's software Y -- 
the thing that puts the 'application' data into UDP packets. The 
previous steps are irrelevant - just as irrelevant as the singer your 
video camera is filming, as irrelevant as the sun that created the light 
that is reflected off the singer to your camera.

If software Y knows so much about the steps that lead to its input data 
that it knows it's congestion reactive, nothing more need be done.

If NOT (and that's the relevant corollary here), then it becomes 
software Y's responsibility to put in some reactivity.

Joe

From akatlas@gmail.com  Thu Jan 23 16:07:31 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 046B21A0493; Thu, 23 Jan 2014 16:07:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yysSrxnD2GRb; Thu, 23 Jan 2014 16:07:26 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 96C7E1A0491; Thu, 23 Jan 2014 16:07:26 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id tp5so2007145ieb.7 for <multiple recipients>; Thu, 23 Jan 2014 16:07:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VwcuizKnEIN/7aOhj2d1R6wjOLeSik0tNx9fgGVzRUY=; b=s4kWvHuNFb4/27LtN1RwsV9VR8tGernHUVYEcff9+Z+usUElLw2hkv7KK02ycbQhW/ mH1qB4Zd5HdHY4J9jI3Zr9uh7+2XAATtM/Cf3/+Y/NwpPMRJOv8inBjbQWv1TQRQvM1L GBkj6efPOg27UY2OvaOWhFdVZCijWNEG5n2cQA8vBiS8S6XvWGgcKLeY+iXzvKyyL70d kwFt6D99mDu+qkxGiDA8hmXm4liJKTU+6IwGSoegogEfZJcuTZqZRqPGk7okiwNn4NJf pbf6s3t1+hZK5+4u8BSAyxqK5H0XiLG1mfm45A5kQfhIj6wjTQqrTtcnuiC59WcHvfzc hVvQ==
MIME-Version: 1.0
X-Received: by 10.43.163.3 with SMTP id mm3mr11845icc.63.1390522045559; Thu, 23 Jan 2014 16:07:25 -0800 (PST)
Received: by 10.64.72.132 with HTTP; Thu, 23 Jan 2014 16:07:25 -0800 (PST)
In-Reply-To: <52E1AC3E.2040204@isi.edu>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com> <52E1AC3E.2040204@isi.edu>
Date: Thu, 23 Jan 2014 19:07:25 -0500
Message-ID: <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
From: Alia Atlas <akatlas@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=001a11c2fafe93fadf04f0ac2478
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 00:07:31 -0000

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

I don't want to get in the way of vehement discussion, but I thought we
were on the verge of finding an actual solution...

IMHO, that was a combination of an applicability statement, using SHOULD
for congestion control and checksum, and defining a longer-term OAM-based
approach (as Stewart Bryant suggested) to be able to verify that packet
corruption or excessive drops aren't happening.

Does that sound like an acceptable set?

Alia


On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 1/23/2014 3:32 PM, Edward Crabbe wrote:
>
>> Joe, thanks for your response. Comments inline:
>>
>>
>>     On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>>
>>         Part of the point of using UDP is to make use of lowest common
>>         denominator forwarding hardware in introducing entropy to
>>         protocols that
>>         lack it ( this is particularly true of the GRE in UDP use case
>> also
>>         under discussion elsewhere).
>>
>>         The tunnel is not the source of the traffic.  The _source of the
>>         traffic_ is the source of the traffic.
>>
>>
>>     To the Internet, the tunnel encapusulator is the source of traffic.
>>     Tracing the data back further than that is a mirage at best - and
>>     irrelevant.
>>
>>
>> The 'internet' cares about characteristics of reactivity to congestion.
>>   This is guaranteed by the /source of the traffic/ independent of any
>> intermediate node.
>>
>
> Are you prepared to make that a requirement of this document, i.e., that
> the only MPLS traffic that can be UDP encapsulated is known to react to
> congestion?
>
> How exactly can you know that?
>
>
>      The tunnel head-end is responsible for the tunnel walking, talking,
>>     and quaking like a duck (host). When the tunnel head-end knows
>>     something about the ultimate origin of the traffic - whether real,
>>     imagined, or from Asgard - then it has done it's duty (e.g., that
>>     it's already congestion controlled).
>>
>>     But that head end is responsible, regardless of what it knows or
>>     doesn't. And when it doesn't know, the only way to be responsible is
>>     to put in its own reactivity.
>>
>> This is not fact; it's actually precisely the principle  we're currently
>> arguing about.  ;)
>>
>
> Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
>
> We can continue to debate it, but until it's been *changed* by a revision,
> it remains BCP.
>
>
>  I would posit:
>>
>> The tunnel doesn't have to know anything about congestion or performance
>> characteristics because the originating application must.
>>
>
> That works only if you know that fact about the originating application.
> However, there are plenty of applications whose traffic goes over MPLS that
> isn't congestion reactive or bandwidth-limited.
>
>
> > See GRE,
>
>> MPLS, many other tunnel types,
>>
>
> This isn't an issue for all tunnels until they enter the Internet...
>
>
>  including several existing within the
>> IETF that make use of an outer UDP header.
>>
>
> Which are all already supposed to follow the recommendations of RFC5405.
> To the extent that they don't, they don't agree with that BCP.
>
> I'm not saying such things never can or will exist, but I don't think the
> IETF should be self-contradictory. We already agreed as a group on such
> BCPs and other standards, and new standards-track docs need to follow them.
>
>
>          The originating application
>>         who's traffic is being tunneled should be responsible for
>> congestion
>>         control, or lack there of.
>>
>>     Perhaps it should be, but that's an agreement between whomever
>>     implements/deploys the tunnel headend and whomever provides the
>>     originating traffic to them. The problem is that this isn't true for
>>     the typical use case for this kind of encapsulation.
>>
>> How so?  As mentioned before, this is the same case as standard GRE/MPLS
>> etc.
>>
>
> It's putting MPLS inside UDP. That's a different case, and the reason
> RFC5405 applies.
>
>
>      I.e., if we were talking about MPLS traffic that already was
>>     reactive, we wouldn't be claiming the need for additional
>>     encapsulator mechanism. It's precisely because nothing is known
>>     about the MPLS traffic that the encapsulator needs to act.
>>
>> The MPLS traffic doesn't have to be reactive, it's the applications
>> being encapsulated / traversing a particular tunnel that are responsible
>> for and aware of path and congestion charateristics.  Because the MPLS
>> head end knows nothing about the /end to end application 'session'/
>> characteristics it /shouldn't/ have anything to do with congestion
>> management.
>>
>
> OK, so what you're saying is that "traffic using this encapsulation MUST
> be known to be congestion reactive". Put that in the doc and we'll debate
> whether we believe it.
>
> But right now you're basically saying that because you think it's someone
> else's problem (the originating application), it isn't yours. The
> difficulty with that logic is that you (the tunnel headend) is responsible
> to ensure that this is true - either by *knowing* that the originating
> traffic is congestion reactive, or by putting in its own mechanism to
> ensure that this happens if the originating application isn't.
>
>
>       > Are we advocating a return to intermediate
>>
>>         congestion control (I like X.25 as much as the next guy,
>>         but...).  This
>>         is a very stark change of direction.
>>
>>         I think mandating congestion control  is not technically sound
>> from
>>         either a theoretical (violation of end to end principle, stacking
>> of
>>         congestion control algorithms leading to complex and potentially
>>         suboptimal results) or economic perspective (as a very large
>>         backbone,
>>         we've been doing just fine without intermediate congestion
>>         management
>>         thank you very much, and I have 0 desire to pay for a cost
>>         prohibitive,
>>         unnecessary feature in silicon.)
>>
>>     Write that up, and we'll see how it turns out in the IETF. However,
>>     right now, the IETF BCPs do require reactive congestion management
>>     of transport streams.
>>
>> Which part?  The end-to-end principle, or the aversion to congestion
>> control stacking?  These have been implicit in all tunneling protocols
>> produced by the IETF for the modern internet.
>>
>
> Sure, and that's reflected in RFC5405 already. However, please, PLEASE
> appreciate that NOBODY here is asking you to put in "congestion control
> stacking"; that happens when you run two dynamic, reactive control
> algorithms using the same timescale on top of each other.
>
> Equally well-known in CC circles is that you CAN - and often *should* -
> stack different kinds of mechanisms at different layers with different
> timescales. E.g., that's why we have an AQM WG - because even when all the
> traffic is TCP, that's not quite enough inside the network. That's also why
> Lars was suggesting something coarse on a longer timescale - a circuit
> breaker - rather than AIMD on a RTT basis.
>
> Keep in mind as well that the E2E argument says that you can't get an E2E
> service by composing the equivalent HBH one; it also says that HBH
> mechanisms can be required for efficiency. That's what we're talking about
> here - the efficiency impact of congestion, not the overall correctness of
> E2E control.
>
>
>      If you don't want/like that, then either don't use transport
>>     encapsulation, or change the BCPs.
>>
>> These BCPs are defined for an originating /application/.
>>
>
> Yes, and I don't understand why you (and others) keep thinking it matters
> that there are layers of things behind the tunnel head end. It doesn't -
> unless you KNOW what those layers are, and can ensure that they behave as
> you expect.
>
>
>  In this case
>> the UDP header is simply a shim header applied to existing application
>> traffic.
>>
>
> It's not "simply a shim" - if that's the case, use IP and we're done. No
> need for congestion control.
>
> The reason congestion issues arise is because you're inserting a header
> ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.
>
> If you put in a UDP-like header that nobody in the Internet would
> interpret, this wouldn't be an issue.
>
> But you simply cannot expect the Internet to treat you like "application"
> traffic if you won't enforce acting like that traffic too.
>
>
>  The tunnel head does not introduce traffic independent of the
>> originating application.
>>
>
> The Internet ****neither knows nor cares****.
>
> To the Internet, the head-end is the source. Whatever data the head end
> puts inside the UDP packets *is application data* to the rest of the
> Internet.
>
> Again, if you are saying that you know so much about the originating
> source that you know you don't need additional mechanism at the headend,
> say so - but then live by that requirement.
>
> If *any* MPLS traffic could show up at the headend, then it becomes the
> headend's responsibility to do something.
>
> ---
>
> Consider the following case:
>
>         - video shows up inside the OS, destined for the network
>
>         - software X bundles that video and sends it to go out
>
>         - software Y puts that data into UDP packets to go
>         to the Internet
>
> So what's the "application" here? To the Internet, it's software Y -- the
> thing that puts the 'application' data into UDP packets. The previous steps
> are irrelevant - just as irrelevant as the singer your video camera is
> filming, as irrelevant as the sun that created the light that is reflected
> off the singer to your camera.
>
> If software Y knows so much about the steps that lead to its input data
> that it knows it's congestion reactive, nothing more need be done.
>
> If NOT (and that's the relevant corollary here), then it becomes software
> Y's responsibility to put in some reactivity.
>
> Joe
>

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

<div dir=3D"ltr">I don&#39;t want to get in the way of vehement discussion,=
 but I thought we were on the verge of finding an actual solution...<div><b=
r></div><div>IMHO, that was a combination of an applicability statement, us=
ing SHOULD for congestion control and checksum, and defining a longer-term =
OAM-based approach (as Stewart Bryant suggested) to be able to verify that =
packet corruption or excessive drops aren&#39;t happening.</div>
<div><br></div><div>Does that sound like an acceptable set?</div><div><br><=
/div><div>Alia</div></div><div class=3D"gmail_extra"><br><br><div class=3D"=
gmail_quote">On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <span dir=3D"ltr">&=
lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</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>
<br>
On 1/23/2014 3:32 PM, Edward Crabbe wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Joe, thanks for your response. Comments inline:<br>
<br>
<br>
=A0 =A0 On 1/23/2014 1:27 PM, Edward Crabbe wrote:<br>
<br>
=A0 =A0 =A0 =A0 Part of the point of using UDP is to make use of lowest com=
mon<br>
=A0 =A0 =A0 =A0 denominator forwarding hardware in introducing entropy to<b=
r>
=A0 =A0 =A0 =A0 protocols that<br>
=A0 =A0 =A0 =A0 lack it ( this is particularly true of the GRE in UDP use c=
ase also<br>
=A0 =A0 =A0 =A0 under discussion elsewhere).<br>
<br>
=A0 =A0 =A0 =A0 The tunnel is not the source of the traffic. =A0The _source=
 of the<br>
=A0 =A0 =A0 =A0 traffic_ is the source of the traffic.<br>
<br>
<br>
=A0 =A0 To the Internet, the tunnel encapusulator is the source of traffic.=
<br>
=A0 =A0 Tracing the data back further than that is a mirage at best - and<b=
r>
=A0 =A0 irrelevant.<br>
<br>
<br>
The &#39;internet&#39; cares about characteristics of reactivity to congest=
ion.<br>
=A0 This is guaranteed by the /source of the traffic/ independent of any<br=
>
intermediate node.<br>
</blockquote>
<br></div>
Are you prepared to make that a requirement of this document, i.e., that th=
e only MPLS traffic that can be UDP encapsulated is known to react to conge=
stion?<br>
<br>
How exactly can you know that?<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">
=A0 =A0 The tunnel head-end is responsible for the tunnel walking, talking,=
<br>
=A0 =A0 and quaking like a duck (host). When the tunnel head-end knows<br>
=A0 =A0 something about the ultimate origin of the traffic - whether real,<=
br>
=A0 =A0 imagined, or from Asgard - then it has done it&#39;s duty (e.g., th=
at<br>
=A0 =A0 it&#39;s already congestion controlled).<br>
<br>
=A0 =A0 But that head end is responsible, regardless of what it knows or<br=
>
=A0 =A0 doesn&#39;t. And when it doesn&#39;t know, the only way to be respo=
nsible is<br>
=A0 =A0 to put in its own reactivity.<br>
<br>
This is not fact; it&#39;s actually precisely the principle =A0we&#39;re cu=
rrently<br>
arguing about. =A0;)<br>
</blockquote>
<br></div>
Actually, it&#39;s a paraphrasing of Section 3.1.3 of RFC5405.<br>
<br>
We can continue to debate it, but until it&#39;s been *changed* by a revisi=
on, it remains BCP.<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">
I would posit:<br>
<br>
The tunnel doesn&#39;t have to know anything about congestion or performanc=
e<br>
characteristics because the originating application must.<br>
</blockquote>
<br></div>
That works only if you know that fact about the originating application. Ho=
wever, there are plenty of applications whose traffic goes over MPLS that i=
sn&#39;t congestion reactive or bandwidth-limited.<div class=3D"im"><br>

<br>
&gt; See GRE,<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
MPLS, many other tunnel types,<br>
</blockquote>
<br></div>
This isn&#39;t an issue for all tunnels until they enter the Internet...<di=
v 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">
including several existing within the<br>
IETF that make use of an outer UDP header.<br>
</blockquote>
<br></div>
Which are all already supposed to follow the recommendations of RFC5405. To=
 the extent that they don&#39;t, they don&#39;t agree with that BCP.<br>
<br>
I&#39;m not saying such things never can or will exist, but I don&#39;t thi=
nk the IETF should be self-contradictory. We already agreed as a group on s=
uch BCPs and other standards, and new standards-track docs need to follow t=
hem.<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">
=A0 =A0 =A0 =A0 The originating application<br>
=A0 =A0 =A0 =A0 who&#39;s traffic is being tunneled should be responsible f=
or congestion<br>
=A0 =A0 =A0 =A0 control, or lack there of.<br>
<br>
=A0 =A0 Perhaps it should be, but that&#39;s an agreement between whomever<=
br>
=A0 =A0 implements/deploys the tunnel headend and whomever provides the<br>
=A0 =A0 originating traffic to them. The problem is that this isn&#39;t tru=
e for<br>
=A0 =A0 the typical use case for this kind of encapsulation.<br>
<br>
How so? =A0As mentioned before, this is the same case as standard GRE/MPLS<=
br>
etc.<br>
</blockquote>
<br></div>
It&#39;s putting MPLS inside UDP. That&#39;s a different case, and the reas=
on RFC5405 applies.<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">
=A0 =A0 I.e., if we were talking about MPLS traffic that already was<br>
=A0 =A0 reactive, we wouldn&#39;t be claiming the need for additional<br>
=A0 =A0 encapsulator mechanism. It&#39;s precisely because nothing is known=
<br>
=A0 =A0 about the MPLS traffic that the encapsulator needs to act.<br>
<br>
The MPLS traffic doesn&#39;t have to be reactive, it&#39;s the applications=
<br>
being encapsulated / traversing a particular tunnel that are responsible<br=
>
for and aware of path and congestion charateristics. =A0Because the MPLS<br=
>
head end knows nothing about the /end to end application &#39;session&#39;/=
<br>
characteristics it /shouldn&#39;t/ have anything to do with congestion<br>
management.<br>
</blockquote>
<br></div>
OK, so what you&#39;re saying is that &quot;traffic using this encapsulatio=
n MUST be known to be congestion reactive&quot;. Put that in the doc and we=
&#39;ll debate whether we believe it.<br>
<br>
But right now you&#39;re basically saying that because you think it&#39;s s=
omeone else&#39;s problem (the originating application), it isn&#39;t yours=
. The difficulty with that logic is that you (the tunnel headend) is respon=
sible to ensure that this is true - either by *knowing* that the originatin=
g traffic is congestion reactive, or by putting in its own mechanism to ens=
ure that this happens if the originating application isn&#39;t.<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">
=A0 =A0 =A0&gt; Are we advocating a return to intermediate<br>
<br>
=A0 =A0 =A0 =A0 congestion control (I like X.25 as much as the next guy,<br=
>
=A0 =A0 =A0 =A0 but...). =A0This<br>
=A0 =A0 =A0 =A0 is a very stark change of direction.<br>
<br>
=A0 =A0 =A0 =A0 I think mandating congestion control =A0is not technically =
sound from<br>
=A0 =A0 =A0 =A0 either a theoretical (violation of end to end principle, st=
acking of<br>
=A0 =A0 =A0 =A0 congestion control algorithms leading to complex and potent=
ially<br>
=A0 =A0 =A0 =A0 suboptimal results) or economic perspective (as a very larg=
e<br>
=A0 =A0 =A0 =A0 backbone,<br>
=A0 =A0 =A0 =A0 we&#39;ve been doing just fine without intermediate congest=
ion<br>
=A0 =A0 =A0 =A0 management<br>
=A0 =A0 =A0 =A0 thank you very much, and I have 0 desire to pay for a cost<=
br>
=A0 =A0 =A0 =A0 prohibitive,<br>
=A0 =A0 =A0 =A0 unnecessary feature in silicon.)<br>
<br>
=A0 =A0 Write that up, and we&#39;ll see how it turns out in the IETF. Howe=
ver,<br>
=A0 =A0 right now, the IETF BCPs do require reactive congestion management<=
br>
=A0 =A0 of transport streams.<br>
<br>
Which part? =A0The end-to-end principle, or the aversion to congestion<br>
control stacking? =A0These have been implicit in all tunneling protocols<br=
>
produced by the IETF for the modern internet.<br>
</blockquote>
<br></div>
Sure, and that&#39;s reflected in RFC5405 already. However, please, PLEASE =
appreciate that NOBODY here is asking you to put in &quot;congestion contro=
l stacking&quot;; that happens when you run two dynamic, reactive control a=
lgorithms using the same timescale on top of each other.<br>

<br>
Equally well-known in CC circles is that you CAN - and often *should* - sta=
ck different kinds of mechanisms at different layers with different timesca=
les. E.g., that&#39;s why we have an AQM WG - because even when all the tra=
ffic is TCP, that&#39;s not quite enough inside the network. That&#39;s als=
o why Lars was suggesting something coarse on a longer timescale - a circui=
t breaker - rather than AIMD on a RTT basis.<br>

<br>
Keep in mind as well that the E2E argument says that you can&#39;t get an E=
2E service by composing the equivalent HBH one; it also says that HBH mecha=
nisms can be required for efficiency. That&#39;s what we&#39;re talking abo=
ut here - the efficiency impact of congestion, not the overall correctness =
of E2E control.<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">
=A0 =A0 If you don&#39;t want/like that, then either don&#39;t use transpor=
t<br>
=A0 =A0 encapsulation, or change the BCPs.<br>
<br>
These BCPs are defined for an originating /application/.<br>
</blockquote>
<br></div>
Yes, and I don&#39;t understand why you (and others) keep thinking it matte=
rs that there are layers of things behind the tunnel head end. It doesn&#39=
;t - unless you KNOW what those layers are, and can ensure that they behave=
 as you expect.<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 this case<br>
the UDP header is simply a shim header applied to existing application<br>
traffic.<br>
</blockquote>
<br></div>
It&#39;s not &quot;simply a shim&quot; - if that&#39;s the case, use IP and=
 we&#39;re done. No need for congestion control.<br>
<br>
The reason congestion issues arise is because you&#39;re inserting a header=
 ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.<br=
>
<br>
If you put in a UDP-like header that nobody in the Internet would interpret=
, this wouldn&#39;t be an issue.<br>
<br>
But you simply cannot expect the Internet to treat you like &quot;applicati=
on&quot; traffic if you won&#39;t enforce acting like that traffic too.<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">
The tunnel head does not introduce traffic independent of the<br>
originating application.<br>
</blockquote>
<br></div>
The Internet ****neither knows nor cares****.<br>
<br>
To the Internet, the head-end is the source. Whatever data the head end put=
s inside the UDP packets *is application data* to the rest of the Internet.=
<br>
<br>
Again, if you are saying that you know so much about the originating source=
 that you know you don&#39;t need additional mechanism at the headend, say =
so - but then live by that requirement.<br>
<br>
If *any* MPLS traffic could show up at the headend, then it becomes the hea=
dend&#39;s responsibility to do something.<br>
<br>
---<br>
<br>
Consider the following case:<br>
<br>
=A0 =A0 =A0 =A0 - video shows up inside the OS, destined for the network<br=
>
<br>
=A0 =A0 =A0 =A0 - software X bundles that video and sends it to go out<br>
<br>
=A0 =A0 =A0 =A0 - software Y puts that data into UDP packets to go<br>
=A0 =A0 =A0 =A0 to the Internet<br>
<br>
So what&#39;s the &quot;application&quot; here? To the Internet, it&#39;s s=
oftware Y -- the thing that puts the &#39;application&#39; data into UDP pa=
ckets. The previous steps are irrelevant - just as irrelevant as the singer=
 your video camera is filming, as irrelevant as the sun that created the li=
ght that is reflected off the singer to your camera.<br>

<br>
If software Y knows so much about the steps that lead to its input data tha=
t it knows it&#39;s congestion reactive, nothing more need be done.<br>
<br>
If NOT (and that&#39;s the relevant corollary here), then it becomes softwa=
re Y&#39;s responsibility to put in some reactivity.<span class=3D"HOEnZb">=
<font color=3D"#888888"><br>
<br>
Joe<br>
</font></span></blockquote></div><br></div>

--001a11c2fafe93fadf04f0ac2478--

From touch@isi.edu  Thu Jan 23 16:11:12 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E686F1A01A0; Thu, 23 Jan 2014 16:11:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBHE9UvscKsG; Thu, 23 Jan 2014 16:11:08 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 550791A00AA; Thu, 23 Jan 2014 16:11:08 -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 s0O0AM3o006909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 23 Jan 2014 16:10:22 -0800 (PST)
Message-ID: <52E1AF6E.1000108@isi.edu>
Date: Thu, 23 Jan 2014 16:10:22 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu>	<64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com>	<52E18661.4060000@isi.edu>	<CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>	<52E18BF1.1040004@isi.edu>	<CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com>	<52E1AC3E.2040204@isi.edu> <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
In-Reply-To: <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 00:11:13 -0000

Hi, Alia,

On 1/23/2014 4:07 PM, Alia Atlas wrote:
> I don't want to get in the way of vehement discussion, but I thought we
> were on the verge of finding an actual solution...
>
> IMHO, that was a combination of an applicability statement, using SHOULD
> for congestion control and checksum, and defining a longer-term
> OAM-based approach (as Stewart Bryant suggested) to be able to verify
> that packet corruption or excessive drops aren't happening.
>
> Does that sound like an acceptable set?

It answers my concerns (I was concerned about the checksum issue too, 
though it seems to have petered out). I wasn't tracking whether there 
were other issues that this doesn't address that were raised, though.

Joe

> Alia
>
>
> On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>
>
>     On 1/23/2014 3:32 PM, Edward Crabbe wrote:
>
>         Joe, thanks for your response. Comments inline:
>
>
>              On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>
>                  Part of the point of using UDP is to make use of lowest
>         common
>                  denominator forwarding hardware in introducing entropy to
>                  protocols that
>                  lack it ( this is particularly true of the GRE in UDP
>         use case also
>                  under discussion elsewhere).
>
>                  The tunnel is not the source of the traffic.  The
>         _source of the
>                  traffic_ is the source of the traffic.
>
>
>              To the Internet, the tunnel encapusulator is the source of
>         traffic.
>              Tracing the data back further than that is a mirage at best
>         - and
>              irrelevant.
>
>
>         The 'internet' cares about characteristics of reactivity to
>         congestion.
>            This is guaranteed by the /source of the traffic/ independent
>         of any
>         intermediate node.
>
>
>     Are you prepared to make that a requirement of this document, i.e.,
>     that the only MPLS traffic that can be UDP encapsulated is known to
>     react to congestion?
>
>     How exactly can you know that?
>
>
>              The tunnel head-end is responsible for the tunnel walking,
>         talking,
>              and quaking like a duck (host). When the tunnel head-end knows
>              something about the ultimate origin of the traffic -
>         whether real,
>              imagined, or from Asgard - then it has done it's duty
>         (e.g., that
>              it's already congestion controlled).
>
>              But that head end is responsible, regardless of what it
>         knows or
>              doesn't. And when it doesn't know, the only way to be
>         responsible is
>              to put in its own reactivity.
>
>         This is not fact; it's actually precisely the principle  we're
>         currently
>         arguing about.  ;)
>
>
>     Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
>
>     We can continue to debate it, but until it's been *changed* by a
>     revision, it remains BCP.
>
>
>         I would posit:
>
>         The tunnel doesn't have to know anything about congestion or
>         performance
>         characteristics because the originating application must.
>
>
>     That works only if you know that fact about the originating
>     application. However, there are plenty of applications whose traffic
>     goes over MPLS that isn't congestion reactive or bandwidth-limited.
>
>
>      > See GRE,
>
>         MPLS, many other tunnel types,
>
>
>     This isn't an issue for all tunnels until they enter the Internet...
>
>
>         including several existing within the
>         IETF that make use of an outer UDP header.
>
>
>     Which are all already supposed to follow the recommendations of
>     RFC5405. To the extent that they don't, they don't agree with that BCP.
>
>     I'm not saying such things never can or will exist, but I don't
>     think the IETF should be self-contradictory. We already agreed as a
>     group on such BCPs and other standards, and new standards-track docs
>     need to follow them.
>
>
>                  The originating application
>                  who's traffic is being tunneled should be responsible
>         for congestion
>                  control, or lack there of.
>
>              Perhaps it should be, but that's an agreement between whomever
>              implements/deploys the tunnel headend and whomever provides the
>              originating traffic to them. The problem is that this isn't
>         true for
>              the typical use case for this kind of encapsulation.
>
>         How so?  As mentioned before, this is the same case as standard
>         GRE/MPLS
>         etc.
>
>
>     It's putting MPLS inside UDP. That's a different case, and the
>     reason RFC5405 applies.
>
>
>              I.e., if we were talking about MPLS traffic that already was
>              reactive, we wouldn't be claiming the need for additional
>              encapsulator mechanism. It's precisely because nothing is known
>              about the MPLS traffic that the encapsulator needs to act.
>
>         The MPLS traffic doesn't have to be reactive, it's the applications
>         being encapsulated / traversing a particular tunnel that are
>         responsible
>         for and aware of path and congestion charateristics.  Because
>         the MPLS
>         head end knows nothing about the /end to end application 'session'/
>         characteristics it /shouldn't/ have anything to do with congestion
>         management.
>
>
>     OK, so what you're saying is that "traffic using this encapsulation
>     MUST be known to be congestion reactive". Put that in the doc and
>     we'll debate whether we believe it.
>
>     But right now you're basically saying that because you think it's
>     someone else's problem (the originating application), it isn't
>     yours. The difficulty with that logic is that you (the tunnel
>     headend) is responsible to ensure that this is true - either by
>     *knowing* that the originating traffic is congestion reactive, or by
>     putting in its own mechanism to ensure that this happens if the
>     originating application isn't.
>
>
>               > Are we advocating a return to intermediate
>
>                  congestion control (I like X.25 as much as the next guy,
>                  but...).  This
>                  is a very stark change of direction.
>
>                  I think mandating congestion control  is not
>         technically sound from
>                  either a theoretical (violation of end to end
>         principle, stacking of
>                  congestion control algorithms leading to complex and
>         potentially
>                  suboptimal results) or economic perspective (as a very
>         large
>                  backbone,
>                  we've been doing just fine without intermediate congestion
>                  management
>                  thank you very much, and I have 0 desire to pay for a cost
>                  prohibitive,
>                  unnecessary feature in silicon.)
>
>              Write that up, and we'll see how it turns out in the IETF.
>         However,
>              right now, the IETF BCPs do require reactive congestion
>         management
>              of transport streams.
>
>         Which part?  The end-to-end principle, or the aversion to congestion
>         control stacking?  These have been implicit in all tunneling
>         protocols
>         produced by the IETF for the modern internet.
>
>
>     Sure, and that's reflected in RFC5405 already. However, please,
>     PLEASE appreciate that NOBODY here is asking you to put in
>     "congestion control stacking"; that happens when you run two
>     dynamic, reactive control algorithms using the same timescale on top
>     of each other.
>
>     Equally well-known in CC circles is that you CAN - and often
>     *should* - stack different kinds of mechanisms at different layers
>     with different timescales. E.g., that's why we have an AQM WG -
>     because even when all the traffic is TCP, that's not quite enough
>     inside the network. That's also why Lars was suggesting something
>     coarse on a longer timescale - a circuit breaker - rather than AIMD
>     on a RTT basis.
>
>     Keep in mind as well that the E2E argument says that you can't get
>     an E2E service by composing the equivalent HBH one; it also says
>     that HBH mechanisms can be required for efficiency. That's what
>     we're talking about here - the efficiency impact of congestion, not
>     the overall correctness of E2E control.
>
>
>              If you don't want/like that, then either don't use transport
>              encapsulation, or change the BCPs.
>
>         These BCPs are defined for an originating /application/.
>
>
>     Yes, and I don't understand why you (and others) keep thinking it
>     matters that there are layers of things behind the tunnel head end.
>     It doesn't - unless you KNOW what those layers are, and can ensure
>     that they behave as you expect.
>
>
>         In this case
>         the UDP header is simply a shim header applied to existing
>         application
>         traffic.
>
>
>     It's not "simply a shim" - if that's the case, use IP and we're
>     done. No need for congestion control.
>
>     The reason congestion issues arise is because you're inserting a
>     header ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO
>     REACT TO****.
>
>     If you put in a UDP-like header that nobody in the Internet would
>     interpret, this wouldn't be an issue.
>
>     But you simply cannot expect the Internet to treat you like
>     "application" traffic if you won't enforce acting like that traffic too.
>
>
>         The tunnel head does not introduce traffic independent of the
>         originating application.
>
>
>     The Internet ****neither knows nor cares****.
>
>     To the Internet, the head-end is the source. Whatever data the head
>     end puts inside the UDP packets *is application data* to the rest of
>     the Internet.
>
>     Again, if you are saying that you know so much about the originating
>     source that you know you don't need additional mechanism at the
>     headend, say so - but then live by that requirement.
>
>     If *any* MPLS traffic could show up at the headend, then it becomes
>     the headend's responsibility to do something.
>
>     ---
>
>     Consider the following case:
>
>              - video shows up inside the OS, destined for the network
>
>              - software X bundles that video and sends it to go out
>
>              - software Y puts that data into UDP packets to go
>              to the Internet
>
>     So what's the "application" here? To the Internet, it's software Y
>     -- the thing that puts the 'application' data into UDP packets. The
>     previous steps are irrelevant - just as irrelevant as the singer
>     your video camera is filming, as irrelevant as the sun that created
>     the light that is reflected off the singer to your camera.
>
>     If software Y knows so much about the steps that lead to its input
>     data that it knows it's congestion reactive, nothing more need be done.
>
>     If NOT (and that's the relevant corollary here), then it becomes
>     software Y's responsibility to put in some reactivity.
>
>     Joe
>
>

From akatlas@gmail.com  Thu Jan 23 16:22:18 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F4B1A01D3; Thu, 23 Jan 2014 16:22:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m7ro5TIPVu4m; Thu, 23 Jan 2014 16:22:15 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2725A1A034B; Thu, 23 Jan 2014 16:22:15 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id tp5so2090609ieb.35 for <multiple recipients>; Thu, 23 Jan 2014 16:22:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rvOrBZR4e7WAEY2PHiW87cbKpP9iWrgkYKW6V4SEptU=; b=ziLIscQNwneUbehpL2DqVfP+jLhgsiCAhjTE+TzXDJCO29NZhhQe+apfGvseMcx7h8 98iSSO1yEew3BZ3MmM7dZsAPb7FSncEoLafJxsE40F6368x7e4UtB/xKpWk8hIhHkTCv nDRdlbHABLC/EbooIrT6w3Pg9dt5Du7MKPF40JKQqbRGqYR4eUpzBtEgjcm1Aqxgw8fF n4viAlQs6aBBEOZDzE+qv+9C9KarrDgVssUd8IyaCVi7+MEbEmG+juXWNTzGa8n2DVjP NY1JKgENEGMOD/cfZLutvtUNl/YMF6TYldsEkUse6u8QDsxNQVAs5vdS1QPz3VRfecFZ gm9g==
MIME-Version: 1.0
X-Received: by 10.50.43.134 with SMTP id w6mr2063144igl.20.1390522934092; Thu, 23 Jan 2014 16:22:14 -0800 (PST)
Received: by 10.64.72.132 with HTTP; Thu, 23 Jan 2014 16:22:13 -0800 (PST)
In-Reply-To: <CACKN6JEA--9zXgLSWfMHpJD3svQ-JeMPBq2sazPifbujSpwn7g@mail.gmail.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com> <52E1AC3E.2040204@isi.edu> <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com> <CACKN6JEA--9zXgLSWfMHpJD3svQ-JeMPBq2sazPifbujSpwn7g@mail.gmail.com>
Date: Thu, 23 Jan 2014 19:22:13 -0500
Message-ID: <CAG4d1rf7Nefwo2Kiej2dQF7LLqw-_n+zH4u=aWtQEK+W+8KX-A@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
From: Alia Atlas <akatlas@gmail.com>
To: Edward Crabbe <edc@google.com>
Content-Type: multipart/alternative; boundary=089e01184b0c89e95004f0ac59ce
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 00:22:18 -0000

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

On Thu, Jan 23, 2014 at 7:08 PM, Edward Crabbe <edc@google.com> wrote:

> I think there also needs to be a network boundary statement with
> recommendations for filtering and usage in terms of intra vs interdomain
> protocol usage.
>

Agreed - I think that's part of describing how the applicability statement
can be enforced by a service provider.

Alia


>
>
> On Thu, Jan 23, 2014 at 4:07 PM, Alia Atlas <akatlas@gmail.com> wrote:
>
>> I don't want to get in the way of vehement discussion, but I thought we
>> were on the verge of finding an actual solution...
>>
>> IMHO, that was a combination of an applicability statement, using SHOULD
>> for congestion control and checksum, and defining a longer-term OAM-based
>> approach (as Stewart Bryant suggested) to be able to verify that packet
>> corruption or excessive drops aren't happening.
>>
>> Does that sound like an acceptable set?
>>
>> Alia
>>
>>
>> On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu> wrote:
>>
>>>
>>>
>>> On 1/23/2014 3:32 PM, Edward Crabbe wrote:
>>>
>>>> Joe, thanks for your response. Comments inline:
>>>>
>>>>
>>>>     On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>>>>
>>>>         Part of the point of using UDP is to make use of lowest common
>>>>         denominator forwarding hardware in introducing entropy to
>>>>         protocols that
>>>>         lack it ( this is particularly true of the GRE in UDP use case
>>>> also
>>>>         under discussion elsewhere).
>>>>
>>>>         The tunnel is not the source of the traffic.  The _source of the
>>>>         traffic_ is the source of the traffic.
>>>>
>>>>
>>>>     To the Internet, the tunnel encapusulator is the source of traffic.
>>>>     Tracing the data back further than that is a mirage at best - and
>>>>     irrelevant.
>>>>
>>>>
>>>> The 'internet' cares about characteristics of reactivity to congestion.
>>>>   This is guaranteed by the /source of the traffic/ independent of any
>>>> intermediate node.
>>>>
>>>
>>> Are you prepared to make that a requirement of this document, i.e., that
>>> the only MPLS traffic that can be UDP encapsulated is known to react to
>>> congestion?
>>>
>>> How exactly can you know that?
>>>
>>>
>>>      The tunnel head-end is responsible for the tunnel walking, talking,
>>>>     and quaking like a duck (host). When the tunnel head-end knows
>>>>     something about the ultimate origin of the traffic - whether real,
>>>>     imagined, or from Asgard - then it has done it's duty (e.g., that
>>>>     it's already congestion controlled).
>>>>
>>>>     But that head end is responsible, regardless of what it knows or
>>>>     doesn't. And when it doesn't know, the only way to be responsible is
>>>>     to put in its own reactivity.
>>>>
>>>> This is not fact; it's actually precisely the principle  we're currently
>>>> arguing about.  ;)
>>>>
>>>
>>> Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
>>>
>>> We can continue to debate it, but until it's been *changed* by a
>>> revision, it remains BCP.
>>>
>>>
>>>  I would posit:
>>>>
>>>> The tunnel doesn't have to know anything about congestion or performance
>>>> characteristics because the originating application must.
>>>>
>>>
>>> That works only if you know that fact about the originating application.
>>> However, there are plenty of applications whose traffic goes over MPLS that
>>> isn't congestion reactive or bandwidth-limited.
>>>
>>>
>>> > See GRE,
>>>
>>>> MPLS, many other tunnel types,
>>>>
>>>
>>> This isn't an issue for all tunnels until they enter the Internet...
>>>
>>>
>>>  including several existing within the
>>>> IETF that make use of an outer UDP header.
>>>>
>>>
>>> Which are all already supposed to follow the recommendations of RFC5405.
>>> To the extent that they don't, they don't agree with that BCP.
>>>
>>> I'm not saying such things never can or will exist, but I don't think
>>> the IETF should be self-contradictory. We already agreed as a group on such
>>> BCPs and other standards, and new standards-track docs need to follow them.
>>>
>>>
>>>          The originating application
>>>>         who's traffic is being tunneled should be responsible for
>>>> congestion
>>>>         control, or lack there of.
>>>>
>>>>     Perhaps it should be, but that's an agreement between whomever
>>>>     implements/deploys the tunnel headend and whomever provides the
>>>>     originating traffic to them. The problem is that this isn't true for
>>>>     the typical use case for this kind of encapsulation.
>>>>
>>>> How so?  As mentioned before, this is the same case as standard GRE/MPLS
>>>> etc.
>>>>
>>>
>>> It's putting MPLS inside UDP. That's a different case, and the reason
>>> RFC5405 applies.
>>>
>>>
>>>      I.e., if we were talking about MPLS traffic that already was
>>>>     reactive, we wouldn't be claiming the need for additional
>>>>     encapsulator mechanism. It's precisely because nothing is known
>>>>     about the MPLS traffic that the encapsulator needs to act.
>>>>
>>>> The MPLS traffic doesn't have to be reactive, it's the applications
>>>> being encapsulated / traversing a particular tunnel that are responsible
>>>> for and aware of path and congestion charateristics.  Because the MPLS
>>>> head end knows nothing about the /end to end application 'session'/
>>>> characteristics it /shouldn't/ have anything to do with congestion
>>>> management.
>>>>
>>>
>>> OK, so what you're saying is that "traffic using this encapsulation MUST
>>> be known to be congestion reactive". Put that in the doc and we'll debate
>>> whether we believe it.
>>>
>>> But right now you're basically saying that because you think it's
>>> someone else's problem (the originating application), it isn't yours. The
>>> difficulty with that logic is that you (the tunnel headend) is responsible
>>> to ensure that this is true - either by *knowing* that the originating
>>> traffic is congestion reactive, or by putting in its own mechanism to
>>> ensure that this happens if the originating application isn't.
>>>
>>>
>>>       > Are we advocating a return to intermediate
>>>>
>>>>         congestion control (I like X.25 as much as the next guy,
>>>>         but...).  This
>>>>         is a very stark change of direction.
>>>>
>>>>         I think mandating congestion control  is not technically sound
>>>> from
>>>>         either a theoretical (violation of end to end principle,
>>>> stacking of
>>>>         congestion control algorithms leading to complex and potentially
>>>>         suboptimal results) or economic perspective (as a very large
>>>>         backbone,
>>>>         we've been doing just fine without intermediate congestion
>>>>         management
>>>>         thank you very much, and I have 0 desire to pay for a cost
>>>>         prohibitive,
>>>>         unnecessary feature in silicon.)
>>>>
>>>>     Write that up, and we'll see how it turns out in the IETF. However,
>>>>     right now, the IETF BCPs do require reactive congestion management
>>>>     of transport streams.
>>>>
>>>> Which part?  The end-to-end principle, or the aversion to congestion
>>>> control stacking?  These have been implicit in all tunneling protocols
>>>> produced by the IETF for the modern internet.
>>>>
>>>
>>> Sure, and that's reflected in RFC5405 already. However, please, PLEASE
>>> appreciate that NOBODY here is asking you to put in "congestion control
>>> stacking"; that happens when you run two dynamic, reactive control
>>> algorithms using the same timescale on top of each other.
>>>
>>> Equally well-known in CC circles is that you CAN - and often *should* -
>>> stack different kinds of mechanisms at different layers with different
>>> timescales. E.g., that's why we have an AQM WG - because even when all the
>>> traffic is TCP, that's not quite enough inside the network. That's also why
>>> Lars was suggesting something coarse on a longer timescale - a circuit
>>> breaker - rather than AIMD on a RTT basis.
>>>
>>> Keep in mind as well that the E2E argument says that you can't get an
>>> E2E service by composing the equivalent HBH one; it also says that HBH
>>> mechanisms can be required for efficiency. That's what we're talking about
>>> here - the efficiency impact of congestion, not the overall correctness of
>>> E2E control.
>>>
>>>
>>>      If you don't want/like that, then either don't use transport
>>>>     encapsulation, or change the BCPs.
>>>>
>>>> These BCPs are defined for an originating /application/.
>>>>
>>>
>>> Yes, and I don't understand why you (and others) keep thinking it
>>> matters that there are layers of things behind the tunnel head end. It
>>> doesn't - unless you KNOW what those layers are, and can ensure that they
>>> behave as you expect.
>>>
>>>
>>>  In this case
>>>> the UDP header is simply a shim header applied to existing application
>>>> traffic.
>>>>
>>>
>>> It's not "simply a shim" - if that's the case, use IP and we're done. No
>>> need for congestion control.
>>>
>>> The reason congestion issues arise is because you're inserting a header
>>> ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.
>>>
>>> If you put in a UDP-like header that nobody in the Internet would
>>> interpret, this wouldn't be an issue.
>>>
>>> But you simply cannot expect the Internet to treat you like
>>> "application" traffic if you won't enforce acting like that traffic too.
>>>
>>>
>>>  The tunnel head does not introduce traffic independent of the
>>>> originating application.
>>>>
>>>
>>> The Internet ****neither knows nor cares****.
>>>
>>> To the Internet, the head-end is the source. Whatever data the head end
>>> puts inside the UDP packets *is application data* to the rest of the
>>> Internet.
>>>
>>> Again, if you are saying that you know so much about the originating
>>> source that you know you don't need additional mechanism at the headend,
>>> say so - but then live by that requirement.
>>>
>>> If *any* MPLS traffic could show up at the headend, then it becomes the
>>> headend's responsibility to do something.
>>>
>>> ---
>>>
>>> Consider the following case:
>>>
>>>         - video shows up inside the OS, destined for the network
>>>
>>>         - software X bundles that video and sends it to go out
>>>
>>>         - software Y puts that data into UDP packets to go
>>>         to the Internet
>>>
>>> So what's the "application" here? To the Internet, it's software Y --
>>> the thing that puts the 'application' data into UDP packets. The previous
>>> steps are irrelevant - just as irrelevant as the singer your video camera
>>> is filming, as irrelevant as the sun that created the light that is
>>> reflected off the singer to your camera.
>>>
>>> If software Y knows so much about the steps that lead to its input data
>>> that it knows it's congestion reactive, nothing more need be done.
>>>
>>> If NOT (and that's the relevant corollary here), then it becomes
>>> software Y's responsibility to put in some reactivity.
>>>
>>> Joe
>>>
>>
>>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Thu, Jan 23, 2014 at 7:08 PM, Edward Crabbe <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:edc@google.com" target=3D"_blank">edc@google.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 dir=3D"ltr">I think there also needs to=
 be a network boundary statement with recommendations for filtering and usa=
ge in terms of intra vs interdomain protocol usage.=A0</div>
</blockquote><div><br></div><div>Agreed - I think that&#39;s part of descri=
bing how the applicability statement can be enforced by a service provider.=
</div><div><br></div><div>Alia</div><div>=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">

On Thu, Jan 23, 2014 at 4:07 PM, Alia Atlas <span dir=3D"ltr">&lt;<a href=
=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">


<div dir=3D"ltr">I don&#39;t want to get in the way of vehement discussion,=
 but I thought we were on the verge of finding an actual solution...<div><b=
r></div><div>IMHO, that was a combination of an applicability statement, us=
ing SHOULD for congestion control and checksum, and defining a longer-term =
OAM-based approach (as Stewart Bryant suggested) to be able to verify that =
packet corruption or excessive drops aren&#39;t happening.</div>



<div><br></div><div>Does that sound like an acceptable set?</div><span><fon=
t color=3D"#888888"><div><br></div><div>Alia</div></font></span></div><div>=
<div><div class=3D"gmail_extra"><br>

<br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <=
span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">tou=
ch@isi.edu</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><br>
<br>
On 1/23/2014 3:32 PM, Edward Crabbe wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Joe, thanks for your response. Comments inline:<br>
<br>
<br>
=A0 =A0 On 1/23/2014 1:27 PM, Edward Crabbe wrote:<br>
<br>
=A0 =A0 =A0 =A0 Part of the point of using UDP is to make use of lowest com=
mon<br>
=A0 =A0 =A0 =A0 denominator forwarding hardware in introducing entropy to<b=
r>
=A0 =A0 =A0 =A0 protocols that<br>
=A0 =A0 =A0 =A0 lack it ( this is particularly true of the GRE in UDP use c=
ase also<br>
=A0 =A0 =A0 =A0 under discussion elsewhere).<br>
<br>
=A0 =A0 =A0 =A0 The tunnel is not the source of the traffic. =A0The _source=
 of the<br>
=A0 =A0 =A0 =A0 traffic_ is the source of the traffic.<br>
<br>
<br>
=A0 =A0 To the Internet, the tunnel encapusulator is the source of traffic.=
<br>
=A0 =A0 Tracing the data back further than that is a mirage at best - and<b=
r>
=A0 =A0 irrelevant.<br>
<br>
<br>
The &#39;internet&#39; cares about characteristics of reactivity to congest=
ion.<br>
=A0 This is guaranteed by the /source of the traffic/ independent of any<br=
>
intermediate node.<br>
</blockquote>
<br></div>
Are you prepared to make that a requirement of this document, i.e., that th=
e only MPLS traffic that can be UDP encapsulated is known to react to conge=
stion?<br>
<br>
How exactly can you know that?<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 The tunnel head-end is responsible for the tunnel walking, talking,=
<br>
=A0 =A0 and quaking like a duck (host). When the tunnel head-end knows<br>
=A0 =A0 something about the ultimate origin of the traffic - whether real,<=
br>
=A0 =A0 imagined, or from Asgard - then it has done it&#39;s duty (e.g., th=
at<br>
=A0 =A0 it&#39;s already congestion controlled).<br>
<br>
=A0 =A0 But that head end is responsible, regardless of what it knows or<br=
>
=A0 =A0 doesn&#39;t. And when it doesn&#39;t know, the only way to be respo=
nsible is<br>
=A0 =A0 to put in its own reactivity.<br>
<br>
This is not fact; it&#39;s actually precisely the principle =A0we&#39;re cu=
rrently<br>
arguing about. =A0;)<br>
</blockquote>
<br></div>
Actually, it&#39;s a paraphrasing of Section 3.1.3 of RFC5405.<br>
<br>
We can continue to debate it, but until it&#39;s been *changed* by a revisi=
on, it remains BCP.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I would posit:<br>
<br>
The tunnel doesn&#39;t have to know anything about congestion or performanc=
e<br>
characteristics because the originating application must.<br>
</blockquote>
<br></div>
That works only if you know that fact about the originating application. Ho=
wever, there are plenty of applications whose traffic goes over MPLS that i=
sn&#39;t congestion reactive or bandwidth-limited.<div><br>

<br>
&gt; See GRE,<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
MPLS, many other tunnel types,<br>
</blockquote>
<br></div>
This isn&#39;t an issue for all tunnels until they enter the Internet...<di=
v><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
including several existing within the<br>
IETF that make use of an outer UDP header.<br>
</blockquote>
<br></div>
Which are all already supposed to follow the recommendations of RFC5405. To=
 the extent that they don&#39;t, they don&#39;t agree with that BCP.<br>
<br>
I&#39;m not saying such things never can or will exist, but I don&#39;t thi=
nk the IETF should be self-contradictory. We already agreed as a group on s=
uch BCPs and other standards, and new standards-track docs need to follow t=
hem.<div>



<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 The originating application<br>
=A0 =A0 =A0 =A0 who&#39;s traffic is being tunneled should be responsible f=
or congestion<br>
=A0 =A0 =A0 =A0 control, or lack there of.<br>
<br>
=A0 =A0 Perhaps it should be, but that&#39;s an agreement between whomever<=
br>
=A0 =A0 implements/deploys the tunnel headend and whomever provides the<br>
=A0 =A0 originating traffic to them. The problem is that this isn&#39;t tru=
e for<br>
=A0 =A0 the typical use case for this kind of encapsulation.<br>
<br>
How so? =A0As mentioned before, this is the same case as standard GRE/MPLS<=
br>
etc.<br>
</blockquote>
<br></div>
It&#39;s putting MPLS inside UDP. That&#39;s a different case, and the reas=
on RFC5405 applies.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 I.e., if we were talking about MPLS traffic that already was<br>
=A0 =A0 reactive, we wouldn&#39;t be claiming the need for additional<br>
=A0 =A0 encapsulator mechanism. It&#39;s precisely because nothing is known=
<br>
=A0 =A0 about the MPLS traffic that the encapsulator needs to act.<br>
<br>
The MPLS traffic doesn&#39;t have to be reactive, it&#39;s the applications=
<br>
being encapsulated / traversing a particular tunnel that are responsible<br=
>
for and aware of path and congestion charateristics. =A0Because the MPLS<br=
>
head end knows nothing about the /end to end application &#39;session&#39;/=
<br>
characteristics it /shouldn&#39;t/ have anything to do with congestion<br>
management.<br>
</blockquote>
<br></div>
OK, so what you&#39;re saying is that &quot;traffic using this encapsulatio=
n MUST be known to be congestion reactive&quot;. Put that in the doc and we=
&#39;ll debate whether we believe it.<br>
<br>
But right now you&#39;re basically saying that because you think it&#39;s s=
omeone else&#39;s problem (the originating application), it isn&#39;t yours=
. The difficulty with that logic is that you (the tunnel headend) is respon=
sible to ensure that this is true - either by *knowing* that the originatin=
g traffic is congestion reactive, or by putting in its own mechanism to ens=
ure that this happens if the originating application isn&#39;t.<div>



<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0&gt; Are we advocating a return to intermediate<br>
<br>
=A0 =A0 =A0 =A0 congestion control (I like X.25 as much as the next guy,<br=
>
=A0 =A0 =A0 =A0 but...). =A0This<br>
=A0 =A0 =A0 =A0 is a very stark change of direction.<br>
<br>
=A0 =A0 =A0 =A0 I think mandating congestion control =A0is not technically =
sound from<br>
=A0 =A0 =A0 =A0 either a theoretical (violation of end to end principle, st=
acking of<br>
=A0 =A0 =A0 =A0 congestion control algorithms leading to complex and potent=
ially<br>
=A0 =A0 =A0 =A0 suboptimal results) or economic perspective (as a very larg=
e<br>
=A0 =A0 =A0 =A0 backbone,<br>
=A0 =A0 =A0 =A0 we&#39;ve been doing just fine without intermediate congest=
ion<br>
=A0 =A0 =A0 =A0 management<br>
=A0 =A0 =A0 =A0 thank you very much, and I have 0 desire to pay for a cost<=
br>
=A0 =A0 =A0 =A0 prohibitive,<br>
=A0 =A0 =A0 =A0 unnecessary feature in silicon.)<br>
<br>
=A0 =A0 Write that up, and we&#39;ll see how it turns out in the IETF. Howe=
ver,<br>
=A0 =A0 right now, the IETF BCPs do require reactive congestion management<=
br>
=A0 =A0 of transport streams.<br>
<br>
Which part? =A0The end-to-end principle, or the aversion to congestion<br>
control stacking? =A0These have been implicit in all tunneling protocols<br=
>
produced by the IETF for the modern internet.<br>
</blockquote>
<br></div>
Sure, and that&#39;s reflected in RFC5405 already. However, please, PLEASE =
appreciate that NOBODY here is asking you to put in &quot;congestion contro=
l stacking&quot;; that happens when you run two dynamic, reactive control a=
lgorithms using the same timescale on top of each other.<br>




<br>
Equally well-known in CC circles is that you CAN - and often *should* - sta=
ck different kinds of mechanisms at different layers with different timesca=
les. E.g., that&#39;s why we have an AQM WG - because even when all the tra=
ffic is TCP, that&#39;s not quite enough inside the network. That&#39;s als=
o why Lars was suggesting something coarse on a longer timescale - a circui=
t breaker - rather than AIMD on a RTT basis.<br>




<br>
Keep in mind as well that the E2E argument says that you can&#39;t get an E=
2E service by composing the equivalent HBH one; it also says that HBH mecha=
nisms can be required for efficiency. That&#39;s what we&#39;re talking abo=
ut here - the efficiency impact of congestion, not the overall correctness =
of E2E control.<div>



<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 If you don&#39;t want/like that, then either don&#39;t use transpor=
t<br>
=A0 =A0 encapsulation, or change the BCPs.<br>
<br>
These BCPs are defined for an originating /application/.<br>
</blockquote>
<br></div>
Yes, and I don&#39;t understand why you (and others) keep thinking it matte=
rs that there are layers of things behind the tunnel head end. It doesn&#39=
;t - unless you KNOW what those layers are, and can ensure that they behave=
 as you expect.<div>



<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In this case<br>
the UDP header is simply a shim header applied to existing application<br>
traffic.<br>
</blockquote>
<br></div>
It&#39;s not &quot;simply a shim&quot; - if that&#39;s the case, use IP and=
 we&#39;re done. No need for congestion control.<br>
<br>
The reason congestion issues arise is because you&#39;re inserting a header=
 ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.<br=
>
<br>
If you put in a UDP-like header that nobody in the Internet would interpret=
, this wouldn&#39;t be an issue.<br>
<br>
But you simply cannot expect the Internet to treat you like &quot;applicati=
on&quot; traffic if you won&#39;t enforce acting like that traffic too.<div=
><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The tunnel head does not introduce traffic independent of the<br>
originating application.<br>
</blockquote>
<br></div>
The Internet ****neither knows nor cares****.<br>
<br>
To the Internet, the head-end is the source. Whatever data the head end put=
s inside the UDP packets *is application data* to the rest of the Internet.=
<br>
<br>
Again, if you are saying that you know so much about the originating source=
 that you know you don&#39;t need additional mechanism at the headend, say =
so - but then live by that requirement.<br>
<br>
If *any* MPLS traffic could show up at the headend, then it becomes the hea=
dend&#39;s responsibility to do something.<br>
<br>
---<br>
<br>
Consider the following case:<br>
<br>
=A0 =A0 =A0 =A0 - video shows up inside the OS, destined for the network<br=
>
<br>
=A0 =A0 =A0 =A0 - software X bundles that video and sends it to go out<br>
<br>
=A0 =A0 =A0 =A0 - software Y puts that data into UDP packets to go<br>
=A0 =A0 =A0 =A0 to the Internet<br>
<br>
So what&#39;s the &quot;application&quot; here? To the Internet, it&#39;s s=
oftware Y -- the thing that puts the &#39;application&#39; data into UDP pa=
ckets. The previous steps are irrelevant - just as irrelevant as the singer=
 your video camera is filming, as irrelevant as the sun that created the li=
ght that is reflected off the singer to your camera.<br>




<br>
If software Y knows so much about the steps that lead to its input data tha=
t it knows it&#39;s congestion reactive, nothing more need be done.<br>
<br>
If NOT (and that&#39;s the relevant corollary here), then it becomes softwa=
re Y&#39;s responsibility to put in some reactivity.<span><font color=3D"#8=
88888"><br>
<br>
Joe<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>

--089e01184b0c89e95004f0ac59ce--

From l.wood@surrey.ac.uk  Thu Jan 23 16:35:41 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64CF81A04B1; Thu, 23 Jan 2014 16:35:41 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoskbpwVuOtF; Thu, 23 Jan 2014 16:35:36 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.153]) by ietfa.amsl.com (Postfix) with ESMTP id D3F221A04AD; Thu, 23 Jan 2014 16:35:35 -0800 (PST)
Received: from [85.158.136.51:13375] by server-17.bemta-5.messagelabs.com id 87/38-19152-655B1E25; Fri, 24 Jan 2014 00:35:34 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-49.messagelabs.com!1390523733!18630929!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5644 invoked from network); 24 Jan 2014 00:35:33 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-16.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 24 Jan 2014 00:35:33 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 24 Jan 2014 00:35:32 +0000
From: <l.wood@surrey.ac.uk>
To: <touch@isi.edu>, <akatlas@gmail.com>
Date: Fri, 24 Jan 2014 00:33:49 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8YmNyQleJV1FEDSgabe3hbCgDd0wAAxaYP
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346E6@EXMB01CMS.surrey.ac.uk>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com>	<52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com> <52E1AC3E.2040204@isi.edu> <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>, <52E1AF6E.1000108@isi.edu>
In-Reply-To: <52E1AF6E.1000108@isi.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, edc@google.com, jnc@mercury.lcs.mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 00:35:41 -0000

I wouldn't say the checksum issue has petered out - I've provided replaceme=
nt paragraphs of text to Xiaohu which will hopefully resolve it.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Joe Touch [touch@isi.edu]
Sent: 24 January 2014 00:10
To: Alia Atlas
Cc: mpls@ietf.org; Edward Crabbe; Noel Chiappa; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Hi, Alia,

On 1/23/2014 4:07 PM, Alia Atlas wrote:
> I don't want to get in the way of vehement discussion, but I thought we
> were on the verge of finding an actual solution...
>
> IMHO, that was a combination of an applicability statement, using SHOULD
> for congestion control and checksum, and defining a longer-term
> OAM-based approach (as Stewart Bryant suggested) to be able to verify
> that packet corruption or excessive drops aren't happening.
>
> Does that sound like an acceptable set?

It answers my concerns (I was concerned about the checksum issue too,
though it seems to have petered out). I wasn't tracking whether there
were other issues that this doesn't address that were raised, though.

Joe

> Alia
>
>
> On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>
>
>     On 1/23/2014 3:32 PM, Edward Crabbe wrote:
>
>         Joe, thanks for your response. Comments inline:
>
>
>              On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>
>                  Part of the point of using UDP is to make use of lowest
>         common
>                  denominator forwarding hardware in introducing entropy t=
o
>                  protocols that
>                  lack it ( this is particularly true of the GRE in UDP
>         use case also
>                  under discussion elsewhere).
>
>                  The tunnel is not the source of the traffic.  The
>         _source of the
>                  traffic_ is the source of the traffic.
>
>
>              To the Internet, the tunnel encapusulator is the source of
>         traffic.
>              Tracing the data back further than that is a mirage at best
>         - and
>              irrelevant.
>
>
>         The 'internet' cares about characteristics of reactivity to
>         congestion.
>            This is guaranteed by the /source of the traffic/ independent
>         of any
>         intermediate node.
>
>
>     Are you prepared to make that a requirement of this document, i.e.,
>     that the only MPLS traffic that can be UDP encapsulated is known to
>     react to congestion?
>
>     How exactly can you know that?
>
>
>              The tunnel head-end is responsible for the tunnel walking,
>         talking,
>              and quaking like a duck (host). When the tunnel head-end kno=
ws
>              something about the ultimate origin of the traffic -
>         whether real,
>              imagined, or from Asgard - then it has done it's duty
>         (e.g., that
>              it's already congestion controlled).
>
>              But that head end is responsible, regardless of what it
>         knows or
>              doesn't. And when it doesn't know, the only way to be
>         responsible is
>              to put in its own reactivity.
>
>         This is not fact; it's actually precisely the principle  we're
>         currently
>         arguing about.  ;)
>
>
>     Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
>
>     We can continue to debate it, but until it's been *changed* by a
>     revision, it remains BCP.
>
>
>         I would posit:
>
>         The tunnel doesn't have to know anything about congestion or
>         performance
>         characteristics because the originating application must.
>
>
>     That works only if you know that fact about the originating
>     application. However, there are plenty of applications whose traffic
>     goes over MPLS that isn't congestion reactive or bandwidth-limited.
>
>
>      > See GRE,
>
>         MPLS, many other tunnel types,
>
>
>     This isn't an issue for all tunnels until they enter the Internet...
>
>
>         including several existing within the
>         IETF that make use of an outer UDP header.
>
>
>     Which are all already supposed to follow the recommendations of
>     RFC5405. To the extent that they don't, they don't agree with that BC=
P.
>
>     I'm not saying such things never can or will exist, but I don't
>     think the IETF should be self-contradictory. We already agreed as a
>     group on such BCPs and other standards, and new standards-track docs
>     need to follow them.
>
>
>                  The originating application
>                  who's traffic is being tunneled should be responsible
>         for congestion
>                  control, or lack there of.
>
>              Perhaps it should be, but that's an agreement between whomev=
er
>              implements/deploys the tunnel headend and whomever provides =
the
>              originating traffic to them. The problem is that this isn't
>         true for
>              the typical use case for this kind of encapsulation.
>
>         How so?  As mentioned before, this is the same case as standard
>         GRE/MPLS
>         etc.
>
>
>     It's putting MPLS inside UDP. That's a different case, and the
>     reason RFC5405 applies.
>
>
>              I.e., if we were talking about MPLS traffic that already was
>              reactive, we wouldn't be claiming the need for additional
>              encapsulator mechanism. It's precisely because nothing is kn=
own
>              about the MPLS traffic that the encapsulator needs to act.
>
>         The MPLS traffic doesn't have to be reactive, it's the applicatio=
ns
>         being encapsulated / traversing a particular tunnel that are
>         responsible
>         for and aware of path and congestion charateristics.  Because
>         the MPLS
>         head end knows nothing about the /end to end application 'session=
'/
>         characteristics it /shouldn't/ have anything to do with congestio=
n
>         management.
>
>
>     OK, so what you're saying is that "traffic using this encapsulation
>     MUST be known to be congestion reactive". Put that in the doc and
>     we'll debate whether we believe it.
>
>     But right now you're basically saying that because you think it's
>     someone else's problem (the originating application), it isn't
>     yours. The difficulty with that logic is that you (the tunnel
>     headend) is responsible to ensure that this is true - either by
>     *knowing* that the originating traffic is congestion reactive, or by
>     putting in its own mechanism to ensure that this happens if the
>     originating application isn't.
>
>
>               > Are we advocating a return to intermediate
>
>                  congestion control (I like X.25 as much as the next guy,
>                  but...).  This
>                  is a very stark change of direction.
>
>                  I think mandating congestion control  is not
>         technically sound from
>                  either a theoretical (violation of end to end
>         principle, stacking of
>                  congestion control algorithms leading to complex and
>         potentially
>                  suboptimal results) or economic perspective (as a very
>         large
>                  backbone,
>                  we've been doing just fine without intermediate congesti=
on
>                  management
>                  thank you very much, and I have 0 desire to pay for a co=
st
>                  prohibitive,
>                  unnecessary feature in silicon.)
>
>              Write that up, and we'll see how it turns out in the IETF.
>         However,
>              right now, the IETF BCPs do require reactive congestion
>         management
>              of transport streams.
>
>         Which part?  The end-to-end principle, or the aversion to congest=
ion
>         control stacking?  These have been implicit in all tunneling
>         protocols
>         produced by the IETF for the modern internet.
>
>
>     Sure, and that's reflected in RFC5405 already. However, please,
>     PLEASE appreciate that NOBODY here is asking you to put in
>     "congestion control stacking"; that happens when you run two
>     dynamic, reactive control algorithms using the same timescale on top
>     of each other.
>
>     Equally well-known in CC circles is that you CAN - and often
>     *should* - stack different kinds of mechanisms at different layers
>     with different timescales. E.g., that's why we have an AQM WG -
>     because even when all the traffic is TCP, that's not quite enough
>     inside the network. That's also why Lars was suggesting something
>     coarse on a longer timescale - a circuit breaker - rather than AIMD
>     on a RTT basis.
>
>     Keep in mind as well that the E2E argument says that you can't get
>     an E2E service by composing the equivalent HBH one; it also says
>     that HBH mechanisms can be required for efficiency. That's what
>     we're talking about here - the efficiency impact of congestion, not
>     the overall correctness of E2E control.
>
>
>              If you don't want/like that, then either don't use transport
>              encapsulation, or change the BCPs.
>
>         These BCPs are defined for an originating /application/.
>
>
>     Yes, and I don't understand why you (and others) keep thinking it
>     matters that there are layers of things behind the tunnel head end.
>     It doesn't - unless you KNOW what those layers are, and can ensure
>     that they behave as you expect.
>
>
>         In this case
>         the UDP header is simply a shim header applied to existing
>         application
>         traffic.
>
>
>     It's not "simply a shim" - if that's the case, use IP and we're
>     done. No need for congestion control.
>
>     The reason congestion issues arise is because you're inserting a
>     header ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO
>     REACT TO****.
>
>     If you put in a UDP-like header that nobody in the Internet would
>     interpret, this wouldn't be an issue.
>
>     But you simply cannot expect the Internet to treat you like
>     "application" traffic if you won't enforce acting like that traffic t=
oo.
>
>
>         The tunnel head does not introduce traffic independent of the
>         originating application.
>
>
>     The Internet ****neither knows nor cares****.
>
>     To the Internet, the head-end is the source. Whatever data the head
>     end puts inside the UDP packets *is application data* to the rest of
>     the Internet.
>
>     Again, if you are saying that you know so much about the originating
>     source that you know you don't need additional mechanism at the
>     headend, say so - but then live by that requirement.
>
>     If *any* MPLS traffic could show up at the headend, then it becomes
>     the headend's responsibility to do something.
>
>     ---
>
>     Consider the following case:
>
>              - video shows up inside the OS, destined for the network
>
>              - software X bundles that video and sends it to go out
>
>              - software Y puts that data into UDP packets to go
>              to the Internet
>
>     So what's the "application" here? To the Internet, it's software Y
>     -- the thing that puts the 'application' data into UDP packets. The
>     previous steps are irrelevant - just as irrelevant as the singer
>     your video camera is filming, as irrelevant as the sun that created
>     the light that is reflected off the singer to your camera.
>
>     If software Y knows so much about the steps that lead to its input
>     data that it knows it's congestion reactive, nothing more need be don=
e.
>
>     If NOT (and that's the relevant corollary here), then it becomes
>     software Y's responsibility to put in some reactivity.
>
>     Joe
>
>

From jmh@joelhalpern.com  Thu Jan 23 18:31:51 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 879D91A01BE; Thu, 23 Jan 2014 18:31:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUa0nL06So02; Thu, 23 Jan 2014 18:31:49 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id 80E311A0195; Thu, 23 Jan 2014 18:31:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id C83A84415B9; Thu, 23 Jan 2014 18:31:48 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (24-104-115-2-ip-static.hfc.comcastbusiness.net [24.104.115.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 5DBC31C05A5; Thu, 23 Jan 2014 18:31:48 -0800 (PST)
Message-ID: <52E1D093.8040603@joelhalpern.com>
Date: Thu, 23 Jan 2014 21:31:47 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, Edward Crabbe <edc@google.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu>
In-Reply-To: <52E18BF1.1040004@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 02:31:51 -0000

Joe, while your argument is internally consistent, it is not consistent 
with history.  We have not demanded that tunnel entries behave fully 
like source hosts for any of the other myriad kinds of tunnels we have 
done over the years.

If we take your logic as stated, then the usage of IPSec over UDP would 
be required to apply congestion control unless it knew that all the 
content traffic was TCP.  Is that really your intent?

Yours,
Joel

On 1/23/14 4:38 PM, Joe Touch wrote:
>
>
> On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>> Part of the point of using UDP is to make use of lowest common
>> denominator forwarding hardware in introducing entropy to protocols that
>> lack it ( this is particularly true of the GRE in UDP use case also
>> under discussion elsewhere).
>>
>> The tunnel is not the source of the traffic.  The _source of the
>> traffic_ is the source of the traffic.
>
> To the Internet, the tunnel encapusulator is the source of traffic.
> Tracing the data back further than that is a mirage at best - and
> irrelevant.
>
> The tunnel head-end is responsible for the tunnel walking, talking, and
> quaking like a duck (host). When the tunnel head-end knows something
> about the ultimate origin of the traffic - whether real, imagined, or
> from Asgard - then it has done it's duty (e.g., that it's already
> congestion controlled).
>
> But that head end is responsible, regardless of what it knows or
> doesn't. And when it doesn't know, the only way to be responsible is to
> put in its own reactivity.
>
>> The originating application
>> who's traffic is being tunneled should be responsible for congestion
>> control, or lack there of.
>
> Perhaps it should be, but that's an agreement between whomever
> implements/deploys the tunnel headend and whomever provides the
> originating traffic to them. The problem is that this isn't true for the
> typical use case for this kind of encapsulation.
>
> I.e., if we were talking about MPLS traffic that already was reactive,
> we wouldn't be claiming the need for additional encapsulator mechanism.
> It's precisely because nothing is known about the MPLS traffic that the
> encapsulator needs to act.
>
>  > Are we advocating a return to intermediate
>> congestion control (I like X.25 as much as the next guy, but...).  This
>> is a very stark change of direction.
>>
>> I think mandating congestion control  is not technically sound from
>> either a theoretical (violation of end to end principle, stacking of
>> congestion control algorithms leading to complex and potentially
>> suboptimal results) or economic perspective (as a very large backbone,
>> we've been doing just fine without intermediate congestion management
>> thank you very much, and I have 0 desire to pay for a cost prohibitive,
>> unnecessary feature in silicon.)
>
> Write that up, and we'll see how it turns out in the IETF. However,
> right now, the IETF BCPs do require reactive congestion management of
> transport streams.
>
> If you don't want/like that, then either don't use transport
> encapsulation, or change the BCPs.
>
>> I get Lars comments regarding reach, to some limited extent.
>>   Ultimately, the implication seems to be that the protocols riding the
>> L2 network will have no form of congestion control and are fundamentally
>> different than protocols that would reside on a typical wan.  I have
>> some serious doubts about this, although I'm sure this is the case in
>> some specialized environments.  At any rate, it seems to me that a stern
>> warning regarding edge filtering on interdomain boundaries will be
>> sufficient.
>
> My concern may be slightly different that his. My concern is that you
> want the benefits of a UDP header, but don't like the responsibilities
> that come along with it.
>
> Joe
>
>

From execd@iab.org  Thu Jan 23 19:32:37 2014
Return-Path: <execd@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 793B81A0014; Thu, 23 Jan 2014 19:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aPnHoR0ZpYw; Thu, 23 Jan 2014 19:32:34 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B20601A00D0; Thu, 23 Jan 2014 19:32:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IAB Executive Director <execd@iab.org>
To: trevp@trevp.net
Subject: IAB Comments Regarding the IRTF CFRG chair
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140124033234.5680.60052.idtracker@ietfa.amsl.com>
Date: Thu, 23 Jan 2014 19:32:34 -0800
Cc: iab@iab.org, cfrg@irtf.org, ietf@ietf.org, ietf-announce@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 03:32:40 -0000

The IAB thanks Trevor Perrin for his request for our review of the decision
made by the chair of the IRTF regarding Kevin Igoe as co-chair for the
CFRG.  We have taken Trevor Perrin's concerns and others' quite seriously,
as we do the functioning of the IRTF and the CFRG.  We have also taken
into account the comments that we have received from the community.

Sections 2  and 4 of RFC 2014 specify that changes to research groups
are to be sent to us by the chair of the IRTF.  The IAB has concluded
that the chair of the IRTF has, in accordance with RFC 2014,
properly and diligently exercised his responsibilities by investigating
the matter, taking community input, and providing a timely response
that addresses the points that were raised by Trevor Perrin and others.
In doing so, he has decided not to forward to us for consideration any
changes to the CFRG at this time.

While it is certainly true that positions of individuals are often aligned =

with those of their employers, RFC 2014 states: =E2=80=9CParticipation is b=
y =

individual contributors, rather than by representatives of organizations.=
=E2=80=9D  =

We expect individuals to participate in the IRTF in their own capacity
to further the research goals of the IRTF and the Internet community.  =

In doing so, we must all remember that as individuals we will all make =

mistakes from time to time.  The best way for anyone to allay their =

concerns about the direction and decisions of a group is to contribute
their own ideas and actively review ideas of others, engaging in discussion=
s =

so that everyone's understanding can be improved.

We count on the chair of the IRTF to continually monitor the CFRG and all R=
Gs
to see that they function properly as specified by their charters.  Should =
he
find that this is not the case with the CFRG in the future, he may at that =
time
initiate changes in consultation with the RG and IRSG as specified in Secti=
on 4
of RFC 2014.  We understand the CFRG is engaging in discussions on how to
evolve itself and its procedures over time.  The RG may wish to more clearly
specify the manner by which decisions are made and represented. We =

encourage all interested parties to participate in those discussions, and w=
e look forward to any changes the chair of the IRTF would bring to us as a =
result.

Please note that Russ Housley recused himself from this matter.

On behalf of the IAB,
Mary Barnes
IAB Executive Director

From gdaley@au.logicalis.com  Thu Jan 23 19:38:50 2014
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED461A012A; Thu, 23 Jan 2014 19:38:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.442
X-Spam-Level: 
X-Spam-Status: No, score=-1.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kSGdqo_qWe88; Thu, 23 Jan 2014 19:38:48 -0800 (PST)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id 4D0721A0117; Thu, 23 Jan 2014 19:38:48 -0800 (PST)
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([203.8.7.161]) by smtp2.au.logicalis.com with ESMTP; 24 Jan 2014 14:38:47 +1100
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([fe80::68b7:8880:fefb:f742%12]) with mapi id 14.02.0347.000; Fri, 24 Jan 2014 14:38:45 +1100
From: Greg Daley <gdaley@au.logicalis.com>
To: "'Joel M. Halpern'" <jmh@joelhalpern.com>, Joe Touch <touch@isi.edu>, Edward Crabbe <edc@google.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPF5eBZzPPQlRcgk6ua2U45NfiYJqQTqiAgAHKKoCAAL8zyf//mUCAgAC+CKA=
Date: Fri, 24 Jan 2014 03:38:44 +0000
Message-ID: <72381AF1F18BAE4F890A0813768D992817FD35E1@sdcexchms.au.logicalis.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <52E1D093.8040603@joelhalpern.com>
In-Reply-To: <52E1D093.8040603@joelhalpern.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.196.183]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 03:38:50 -0000

Hi Joel,=20

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern
> Sent: Friday, 24 January 2014 1:32 PM
> To: Joe Touch; Edward Crabbe
> Cc: mpls@ietf.org; Noel Chiappa; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> Joe, while your argument is internally consistent, it is not consistent w=
ith
> history.  We have not demanded that tunnel entries behave fully like sour=
ce
> hosts for any of the other myriad kinds of tunnels we have done over the =
years.


Actually, many of the tunnel protocols on the standards track have been eit=
her for upper-layer IP or Transport protocols or require congestion mitigat=
ion:


RFC 4448 for EoMPLS, and 5994 for Ethernet pseudowires over MPLS each ask t=
hat tunnelled protocols support congestion mechanisms,
RFC5085 and 5586:  VCCV and BFD with VCCV define congestion considerations =
for pseudowire tunnels.
RFC 4719 updated by RFC 5641: Ethernet pseudowires over L2TP (a UDP encapsu=
lated protocol)  permit packet loss indications to take down the active cir=
cuit.=20
RFC 4454: ATM over L2TPv3 indicates that inelastic flows are stopped when c=
ongestion occurs.

They (ATM over L2TPv3 and Ethernet PW over L2TPv3) also require usage over =
a traffic engineered network.

RFC 4817 MPLS over L2TPv3 requires non-IP upper layer protocols not to exce=
ed the offered load of a typical TCP application on the same path.


For those protocols which have IP, UDP, TCP, SCCP or DCCP this is just pass=
ing the buck to the upper layer protocol (which is OK, so long as the appli=
cation protocol in UDP has congestion measures). For environments where thi=
s cannot be relied upon, additional protocol specification and applicabilit=
y statements have previously been applied.

> If we take your logic as stated, then the usage of IPSec over UDP would b=
e
> required to apply congestion control unless it knew that all the content =
traffic
> was TCP.  Is that really your intent?

Actually, one of the compelling use cases for running MPLS over UDP (or L2T=
Pv3) would be to encapsulate the traffic in ESP in order to combat passive =
snooping.

For ESP I believe the implicit assumption (via the Traffic Selectors in IKE=
) was that the upper layer protocol is IP or in transport mode another prot=
ocol such as TCP, UDP etc.

Sincerely,=20

Greg Daley
gdaley@au.logicalis.com


From narten@us.ibm.com  Thu Jan 23 21:53:09 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88641A00FB for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 21:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.637
X-Spam-Level: 
X-Spam-Status: No, score=-4.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, TO_IN_SUBJ=2.799] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s1iSVrfxk9xy for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 21:53:08 -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 0CDEE1A00F1 for <ietf@ietf.org>; Thu, 23 Jan 2014 21:53:07 -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>; Fri, 24 Jan 2014 00:53:06 -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;  Fri, 24 Jan 2014 00:53:04 -0500
Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 0B4906E8040 for <ietf@ietf.org>; Fri, 24 Jan 2014 00:53:00 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22036.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0O5r4BC2425132 for <ietf@ietf.org>; Fri, 24 Jan 2014 05:53:04 GMT
Received: from d01av01.pok.ibm.com (localhost [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0O5r3cY024721 for <ietf@ietf.org>; Fri, 24 Jan 2014 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0O5r3II024715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 24 Jan 2014 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s0O5r26e031038 for <ietf@ietf.org>; Fri, 24 Jan 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s0O5r2dg030990 for ietf@ietf.org; Fri, 24 Jan 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201401240553.s0O5r2dg030990@rotala.raleigh.ibm.com>
Date: Fri, 24 Jan 2014 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-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14012405-7182-0000-0000-000009A58C94
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 05:53:10 -0000

Total of 80 messages in the last 7 days.
 
script run at: Fri Jan 24 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  1.25% |    1 | 27.79% |   299338 | tnadeau@lucidvision.com
 13.75% |   11 | 12.90% |   139008 | curtis@ipv6.occnc.com
 12.50% |   10 |  6.80% |    73222 | touch@isi.edu
  6.25% |    5 | 10.87% |   117074 | david.black@emc.com
  6.25% |    5 |  4.73% |    50909 | lear@cisco.com
  6.25% |    5 |  4.33% |    46686 | l.wood@surrey.ac.uk
  6.25% |    5 |  3.51% |    37839 | scott.brim@gmail.com
  6.25% |    5 |  2.87% |    30901 | jari.arkko@piuha.net
  3.75% |    3 |  2.73% |    29459 | lars@netapp.com
  3.75% |    3 |  2.37% |    25499 | adrian@olddog.co.uk
  3.75% |    3 |  1.88% |    20245 | jnc@mercury.lcs.mit.edu
  3.75% |    3 |  1.84% |    19829 | dhc@dcrocker.net
  2.50% |    2 |  1.39% |    14950 | joelja@bogus.com
  2.50% |    2 |  1.36% |    14698 | hartmans-ietf@mit.edu
  2.50% |    2 |  1.27% |    13702 | saku@ytti.fi
  1.25% |    1 |  1.54% |    16548 | akatlas@gmail.com
  1.25% |    1 |  1.38% |    14871 | huitema@microsoft.com
  1.25% |    1 |  1.25% |    13505 | alexander.vainshtein@ecitele.com
  1.25% |    1 |  1.21% |    13040 | jari.arkko@ericsson.com
  1.25% |    1 |  1.01% |    10835 | rcallon@juniper.net
  1.25% |    1 |  0.87% |     9418 | peter@akayla.com
  1.25% |    1 |  0.82% |     8866 | narten@us.ibm.com
  1.25% |    1 |  0.82% |     8811 | spencerdawkins.ietf@gmail.com
  1.25% |    1 |  0.79% |     8520 | stephen.farrell@cs.tcd.ie
  1.25% |    1 |  0.79% |     8508 | stbryant@cisco.com
  1.25% |    1 |  0.63% |     6777 | barryleiba@computer.org
  1.25% |    1 |  0.61% |     6575 | mls.ietf@gmail.com
  1.25% |    1 |  0.61% |     6567 | j.schoenwaelder@jacobs-university.de
  1.25% |    1 |  0.54% |     5790 | garbakora@gmail.com
  1.25% |    1 |  0.49% |     5246 | kent@bbn.com
--------+------+--------+----------+------------------------
100.00% |   80 |100.00% |  1077236 | Total


From peter@akayla.com  Fri Jan 24 00:04:18 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4F01A01C6; Fri, 24 Jan 2014 00:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O6uHfc4Cgfih; Fri, 24 Jan 2014 00:04:16 -0800 (PST)
Received: from p3plsmtpa08-03.prod.phx3.secureserver.net (p3plsmtpa08-03.prod.phx3.secureserver.net [173.201.193.104]) by ietfa.amsl.com (Postfix) with ESMTP id A9F261A01DE; Fri, 24 Jan 2014 00:04:14 -0800 (PST)
Received: from [172.20.7.225] ([69.63.220.2]) by p3plsmtpa08-03.prod.phx3.secureserver.net with  id Hk471n00B03iA9901k48So; Fri, 24 Jan 2014 01:04:13 -0700
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Fri, 24 Jan 2014 00:04:07 -0800
Subject: Gen-ART LC review of draft-ietf-netmod-ip-cfg-12
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-netmod-ip-cfg.all@tools.ietf.org>
Message-ID: <CF075E77.8F72%peter@akayla.com>
Thread-Topic: Gen-ART LC review of draft-ietf-netmod-ip-cfg-12
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: Gen-art <gen-art-bounces@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 08:04:18 -0000

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

Document: draft-ietf-netmod-ip-cfg-12
Reviewer: Peter Yee
Review Date: Jan-23-2014
IETF LC End Date: Jan-23-2014
IESG Telechat date: TBD

Summary: This draft is ready for publication as a Standards Track
RFC. [Ready]

The abstract says it pretty well: This document defines a YANG data model
for management of IP implementations.

Major issues: None

Minor issues: None

Nits: None

All of the issues from my -09 review have been addressed in the
-12 version.

		-Peter Yee




From lars@netapp.com  Fri Jan 24 00:20:12 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F03AA1A01DD; Fri, 24 Jan 2014 00:20:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.437
X-Spam-Level: 
X-Spam-Status: No, score=-7.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hCTva3_iPb8E; Fri, 24 Jan 2014 00:20:04 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5321A0199; Fri, 24 Jan 2014 00:20:04 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,711,1384329600";  d="asc'?scan'208";a="138801597"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 24 Jan 2014 00:17:45 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Fri, 24 Jan 2014 00:17:45 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPDLRewts4Z03OwUmpMDWCPAmms5qTIZaAgAALSwCAAApkgP//yPPdgACHiACAAJ5zgA==
Date: Fri, 24 Jan 2014 08:17:44 +0000
Message-ID: <E871E20C-EC8D-41AA-A556-103246C90EA0@netapp.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E15937.8010600@qti.qualcomm.com> <201401232245.s0NMj6uH3447931@shell01.TheWorld.com> <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
In-Reply-To: <97F802E5-6E15-4BDF-A0D1-EF299DCBBAC4@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 08:20:12 -0000

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I will (again) point at the IPR text for the I*R*TF, that we changed =
last year in an attempt to be more descriptive: http://irtf.org/ipr

I believe it captures Cullen's (and my) concern, and is still quite =
short.

Lars


The IRTF follows the IETF Intellectual Property Rights (IPR) disclosure =
rules. This is a summary of these rules as they relate to IRTF research =
group discussions, mailing lists and Internet Drafts:

	=95 If you include your own or your employer=92s IPR in a =
contribution to an IRTF research group, then you must file an IPR =
disclosure with the IETF.

	=95 If you recognize your own or your employer=92s IPR in =
someone else=92s contribution and you are participating in the =
discussions in the research group relating to that contribution, then =
you must file an IPR disclosure with the IETF. Even if you are not =
participating in the discussion, the IRTF still requests that you file =
an IPR disclosure with the IETF.

	=95 Finally, the IRTF requests that you file an IPR disclosure =
with the IETF if you recognize IPR owned by others in any IRTF =
contribution.

The IRTF expects that you file IPR disclosures in a timely manner, i.e., =
in a period measured in days or weeks, not months. The IRTF prefers that =
the most liberal licensing terms possible are available for IRTF Stream =
documents, see RFC 5743. You may file an IPR disclosure =
here:http://www.ietf.org/ipr/file-disclosure

See RFC 3979 (BCP 79) for definitions of =93IPR=94 and =93contribution=94 =
and for the detailed rules (substituting =93IRTF=94 for =93IETF=94).

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuIhpdZcnpRveo1xAQKHvwP/eryEnXj0oB/sIi9jg8uHnlWmQ26m/fof
aUGheeQBfW3lKPnZ3Xizy3Xc2lXA+q7NGxans7QejaDP9S1z5jW5MnbtLVdoMItA
hnvn3IhLTC9DvqsyA8wWgFFfojvftF5r3buewu0SywBrYy5vf/gh47zBy/iQXo3N
Vvn+2szIyQE=
=9o2c
-----END PGP SIGNATURE-----

--Apple-Mail=_FB351A87-10AF-45F2-BB6D-11EC879479D4--

From john-ietf@jck.com  Fri Jan 24 02:36:00 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1809C1A022A for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 02:36:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W3N3LIhkWVBz for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 02:35:53 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C6A661A0265 for <ietf@ietf.org>; Fri, 24 Jan 2014 02:35:53 -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 1W6e6t-0004mP-Tg; Fri, 24 Jan 2014 05:35:39 -0500
Date: Fri, 24 Jan 2014 05:35:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Gen-Art telechat review of draft-farrell-perpass-attack-04
Message-ID: <7C687DF341F83C7D1C645DF9@JcK-HP8200.jck.com>
In-Reply-To: <tslbnz2xuzi.fsf@mit.edu>
References: <CAPv4CP9OdZSnwoNWPYNRrASjtAdMsxGwBs_pEtZToc=ciR6iRg@mail.gmail.com> <744231EC-0272-486C-994E-B4F1F54862ED@piuha.net> <52DB8D0E.8000708@cisco.com> <52DC1F71.80102@cs.tcd.ie>	<tsl8uu9dnha.fsf@mit.edu> <52DEFAEE.3000900@dcrocker.net> <6543394D-151C-4E1C-8BCC-5D9AAF56E584@ericsson.com> <tslvbxb62of.fsf@mit.edu> <98477509D05291683DB2CAC5@JcK-HP8200.jck.com> <tslbnz2xuzi.fsf@mit.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF discussion list <ietf@ietf.org>, "dcrocker@bbiw.net Crocker" <dcrocker@bbiw.net>, Jari Arkko <jari.arkko@ericsson.com>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 10:36:00 -0000

--On Thursday, January 23, 2014 16:13 -0500 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

>>>>>> "John" == John C Klensin <john-ietf@jck.com> writes:
> 
> 
>     John> On the other hand, if there is a real commitment to
> action,     John> then WGs have to be accountable for design
> decisions that do     John> (or do not) support the goal and
> be ready to explain their     John> decisions, even
> privacy-protecting ones that impose or     John> increase
> costs to performance, operations, or elsewhere.  And     John>
> I would expect (not merely fear) ADs to push back strongly on
>     John> a WG that was unwilling or unable to do that and
> expect     John> Nomcoms to hold ADs accountable if they did
> not enforce the     John> intent of the rules.
> 
> Strongly agreed.
> And if we don't have a community commitment to do that can we
> please be honest with the world and tell everyone that when we
> look at the cost of this issue it was something our community
> did not choose to pay?

Sam, 

I think we are in agreement but, to clarify one possible issue
about choosing to pay: my ongoing fear is that, no matter what
disclaimers are made during this discussion or in the document
itself, sooner or later someone will make, and get traction for,
the claim that, since we have a BCP that says "pervasive
monitoring/surveillance is bad and needs to be repelled" and no
BCP that says "performance is important", privacy is inherently
more important in protocol design.   I have no problem requiring
that a WG explain and justify choices that are not as
monitoring-resistant as is possible, but, were the community not
able to consider and accept such explanations (when they are
reasonable), I think we would be in big trouble.

FWIW, I slightly prefer "justify" to "explain" but, like you,
can live with "explain" if others have a strong preference in
that direction.

best,
   john


From hsantos@isdg.net  Fri Jan 24 05:48:24 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C6B11A0459 for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 05:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYF3WYI1gaPw for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 05:48:22 -0800 (PST)
Received: from winserver.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BB9BA1A0469 for <ietf@ietf.org>; Fri, 24 Jan 2014 05:45:48 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6403; t=1390571141; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=qYp0RrovwTjeNpdU3Se+dj+LItI=; b=KhHsDSS8pn11GLyAB3xm dHk6VE1xJsZ21mvt7dhva7D4viHwiRPFE0y1py4SN2hKz0K/lz1GHZv1jWUmGouv /TEk5PmIJNBTw6odIgOQYS0BDtxeTmYkj0HGWz5naKaal9mbI8bAvKj6Qc/xC2pp 2kswiqaE14eSmTfvPd3+OEQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 24 Jan 2014 08:45:41 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4148601066.13414.980; Fri, 24 Jan 2014 08:45:40 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6403; t=1390570557; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ztVMOo+ bsC+7TSDq1ceMEpt+cgdprxDMxvkSJRl2wR4=; b=rp0JSUFCjM65Jwq4yLzYt46 ZgE1Z0ciSVbCr2N4R6rdO65GJXX4WSLRw+7o6/UwwOdEEs6HtDtq1MfRJGjNt7Vo ATDB/2KgZq84Wmw7Ge+sXy3cs3Wl7SXvGvEVIav6nb5hk8CCG6ks7z4iWkNW2AN1 qNzyqVzZ02N8HLAwSuE4=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 24 Jan 2014 08:35:57 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3594903036.9.6860; Fri, 24 Jan 2014 08:35:56 -0500
Message-ID: <52E26E81.2000000@isdg.net>
Date: Fri, 24 Jan 2014 08:45:37 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 13:48:24 -0000

I'm not quite following the concern. First, I am little surprise that 
this would be anything new in a patent case with lawyers asking 
questions, seeking facts related to prior art discovery. Second, I 
don't see how you (speaking in general, but mostly top IETF Key cogs 
and industry market leaders) can escape any awareness. Ignorance is 
difficult to claim, however, it can lead to a claim of negligence, and 
IMO, this is more the case today. I am more surprise that the employer 
is not enforcing their NDA more, especially in regards with IETF 
participation which is really wide now with international, and 
countries involved with laws are not consistent with the US.  But I 
suppose your corporation would be in an unique position here given its 
long history and presence within the IETF and industry. This is 
something you should be talking with your corporate chief council. 
Despite whatever the Note Well says, despite the non-binding "I Agree" 
click or statement present or not, it is pretty difficult today to 
escape awareness.  Of course, there are many fine lines here, but that 
is even the more reason your corporate legal guys should be advising 
you -- first.

BTW, I think the first item on the note well page, can be argued as 
the "agreement":

    * By participating with the IETF, you agree to follow IETF 
processes and policies.

It then gets down to defining what is meant by "participating" and 
defining what is meant by "follow."

Does it include the lurkers?  Does it include readers, reviewers, but 
not actually implementators?  etc, and all other similar related 
questions about this.

Its difficult to escape awareness if you are involved in the IETF.


--
HLS

On 1/23/2014 12:25 PM, Cullen Jennings (fluffy) wrote:
>
> This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says
>
> 	ï¿½ If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>
> I do not agree to that - I canï¿½t given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test.
>
> I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me.
>
> Thank you,
>
> Cullen
>
> I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement.
>
>
>
> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>
>>
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>
>>> Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.
>>>
>>> Mary.
>>>
>>>
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>> you are correct - we (Barry, the IESG & me) discussed this before the IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least that is the way I expressed it)
>>>
>>> Scott
>>>
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>
>>>
>>>
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>>>
>>>>
>>>>
>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote:
>>>>
>>>>> The IESG has made final edits to the updated Note Well statement, and
>>>>> it has been officially updated:
>>>>> http://www.ietf.org/about/note-well.html
>>>>>
>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>
>>>>> Please use this new version now, and please remember that as you
>>>>> prepare slides for the London meeting.
>>>>>
>>>>> Barry
>>>>
>>>>
>>>> The new note well says
>>>>
>>>>        ï¿½ If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>>
>>>> Is that true?  Or is it missing something along the lines of section y of BCP 79 such as
>>>>
>>>>    or must not contribute to or participate in IETF activities with
>>>>    respect to technologies that he or she reasonably and personally
>>>>    knows to be Covered by IPR which he or she will not disclose.
>>>>
>>>> Thanks, Cullen
>>
>
>
>

-- 
HLS



From jdrake@juniper.net  Fri Jan 24 07:01:14 2014
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E461A011E; Fri, 24 Jan 2014 07:01:14 -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=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2xlTVp2sVK1; Fri, 24 Jan 2014 07:01:11 -0800 (PST)
Received: from am1outboundpool.messaging.microsoft.com (am1ehsobe003.messaging.microsoft.com [213.199.154.206]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2311A00BE; Fri, 24 Jan 2014 07:01:10 -0800 (PST)
Received: from mail35-am1-R.bigfish.com (10.3.201.253) by AM1EHSOBE026.bigfish.com (10.3.207.148) with Microsoft SMTP Server id 14.1.225.22; Fri, 24 Jan 2014 15:01:08 +0000
Received: from mail35-am1 (localhost [127.0.0.1])	by mail35-am1-R.bigfish.com (Postfix) with ESMTP id 92406480495; Fri, 24 Jan 2014 15:01:08 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT003.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -33
X-BigFish: VPS-33(z579ehzbb2dI98dI9371I3071M936eIc85fh11f6Nzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1de097h186068hz2fh109h2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h20f0h2216h22d0h2336h2461h2487h24ach24d7h9a9j1155h)
Received-SPF: pass (mail35-am1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT003.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(979002)(124014002)(479174003)(377454003)(24454002)(377424004)(189002)(199002)(45984002)(4396001)(79102001)(83322001)(47446002)(65816001)(81342001)(2171001)(74502001)(2656002)(33646001)(63696002)(92566001)(81686001)(74876001)(74662001)(80022001)(59766001)(50986001)(77982001)(87266001)(85306002)(81542001)(66066001)(47976001)(74366001)(47736001)(80976001)(87936001)(19580395003)(49866001)(81816001)(31966008)(19580405001)(76786001)(15202345003)(76796001)(93516002)(83072002)(86362001)(85852003)(19300405004)(74316001)(15975445006)(19609705001)(93136001)(90146001)(56816005)(16236675002)(46102001)(51856001)(76576001)(69226001)(56776001)(54356001)(54316002)(76482001)(53806001)(74706001)(94316002)(24736002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB564; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.239.14; FPR:; InfoNoRecordsMX:1; A:1; LANG:en; 
Received: from mail35-am1 (localhost.localdomain [127.0.0.1]) by mail35-am1 (MessageSwitch) id 1390575665842961_4215; Fri, 24 Jan 2014 15:01:05 +0000 (UTC)
Received: from AM1EHSMHS010.bigfish.com (unknown [10.3.201.253])	by mail35-am1.bigfish.com (Postfix) with ESMTP id C8495E0075;	Fri, 24 Jan 2014 15:01:05 +0000 (UTC)
Received: from BL2PRD0510HT003.namprd05.prod.outlook.com (157.56.240.101) by AM1EHSMHS010.bigfish.com (10.3.207.110) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 24 Jan 2014 15:01:05 +0000
Received: from BLUPR05MB564.namprd05.prod.outlook.com (10.141.202.150) by BL2PRD0510HT003.namprd05.prod.outlook.com (10.255.100.38) with Microsoft SMTP Server (TLS) id 14.16.395.1; Fri, 24 Jan 2014 15:01:03 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB564.namprd05.prod.outlook.com (10.141.202.150) with Microsoft SMTP Server (TLS) id 15.0.859.15; Fri, 24 Jan 2014 15:01:02 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0859.013; Fri, 24 Jan 2014 15:01:02 +0000
From: John E Drake <jdrake@juniper.net>
To: Edward Crabbe <edc@google.com>, Joe Touch <touch@isi.edu>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPF5eBadQG/CmveUie5TOX7n7WJpqRBw+AgAHKKoCAAANeAIABJGlQ
Date: Fri, 24 Jan 2014 15:01:01 +0000
Message-ID: <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>
In-Reply-To: <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.239.14]
x-forefront-prvs: 01018CB5B3
Content-Type: multipart/alternative; boundary="_000_e807421cc9fb4d98a46dce129aa39c82BLUPR05MB562namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:01:15 -0000

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

Ed,

I completely agree with your email, below.  As an aside, the L2 packets tha=
t Lars is worried about are transported over a pseudo-wire using MPLS, so t=
he logical place to place congestion awareness is in the pseudo-wire endpoi=
nts.  I remember that this was in the PWE3's charter some time ago.

Yours Irrespectively,

John

From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Edward Crabbe
Sent: Thursday, January 23, 2014 1:27 PM
To: Joe Touch
Cc: mpls@ietf.org; Eggert, Lars; Noel Chiappa; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Part of the point of using UDP is to make use of lowest common denominator =
forwarding hardware in introducing entropy to protocols that lack it ( this=
 is particularly true of the GRE in UDP use case also under discussion else=
where).

The tunnel is not the source of the traffic.  The _source of the traffic_ i=
s the source of the traffic.  The originating application who's traffic is =
being tunneled should be responsible for congestion control, or lack there =
of.  Are we advocating a return to intermediate congestion control (I like =
X.25 as much as the next guy, but...).  This is a very stark change of dire=
ction.

I think mandating congestion control  is not technically sound from either =
a theoretical (violation of end to end principle, stacking of congestion co=
ntrol algorithms leading to complex and potentially suboptimal results) or =
economic perspective (as a very large backbone, we've been doing just fine =
without intermediate congestion management thank you very much, and I have =
0 desire to pay for a cost prohibitive, unnecessary feature in silicon.)

I get Lars comments regarding reach, to some limited extent.  Ultimately, t=
he implication seems to be that the protocols riding the L2 network will ha=
ve no form of congestion control and are fundamentally different than proto=
cols that would reside on a typical wan.  I have some serious doubts about =
this, although I'm sure this is the case in some specialized environments. =
 At any rate, it seems to me that a stern warning regarding edge filtering =
on interdomain boundaries will be sufficient.

On Thu, Jan 23, 2014 at 1:15 PM, Joe Touch <touch@isi.edu<mailto:touch@isi.=
edu>> wrote:


On 1/22/2014 9:55 AM, Eggert, Lars wrote:
Hi,

On 2014-1-22, at 18:29, Noel Chiappa <jnc@mercury.lcs.mit.edu<mailto:jnc@me=
rcury.lcs.mit.edu>> wrote:
Envision the following 4 (or more) scenarios for one Border Tunneling Routi=
ng
(BTR), BTR A, to send packets to another BTR, BTR B, on the path from ultim=
ate
source S (somewhere before BTR A) to destination D (somewhere after BTR B).

- Plain IP
- Some existing encapsulation like GRE
- A new, custom encapsulation
- Encapsulation using UDP

What you seem to be claiming is that in case 4 we need to have congestion
detection and response at the intermediate forwarding node BTR A - but it
would not be required in cases 1-3? This makes no sense.

FWIW, the whole point of using UDP is to leverage the Internet's ability to=
 interpret the tunneled traffic as application data - to manage it accordin=
g to port-based flow interpretation.

There's a cost associated with that privilege - the cost of needing to reac=
t to congestion. That doesn't require 1-RTT, TCP-friendly dynamic congestio=
n control; it does mean *reacting* to congestion in some way, over some tim=
escale more than just ignoring things.

This should be expected of any tunneling system that encapsulates non-react=
ive flows - regardless of technology.

Joe

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


--_000_e807421cc9fb4d98a46dce129aa39c82BLUPR05MB562namprd05pro_
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=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ed,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I completely agree with y=
our email, below.&nbsp; As an aside, the L2 packets that Lars is worried ab=
out are transported over a pseudo-wire using MPLS, so the logical
 place to place congestion awareness is in the pseudo-wire endpoints.&nbsp;=
 I remember that this was in the PWE3&#8217;s charter some time ago.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours Irrespectively,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> mpls [=
mailto:mpls-bounces@ietf.org]
<b>On Behalf Of </b>Edward Crabbe<br>
<b>Sent:</b> Thursday, January 23, 2014 1:27 PM<br>
<b>To:</b> Joe Touch<br>
<b>Cc:</b> mpls@ietf.org; Eggert, Lars; Noel Chiappa; IETF discussion list<=
br>
<b>Subject:</b> Re: [mpls] Last Call: &lt;draft-ietf-mpls-in-udp-04.txt&gt;=
 (Encapsulating MPLS in UDP) to Proposed Standard<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Part of the point of using UDP is to make use of low=
est common denominator forwarding hardware in introducing entropy to protoc=
ols that lack it ( this is particularly true of the GRE in UDP use case als=
o under discussion elsewhere).&nbsp;<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The tunnel is not the source of the traffic. &nbsp;T=
he _source of the traffic_ is the source of the traffic. &nbsp;The originat=
ing application who's traffic is being tunneled should be responsible for c=
ongestion control, or lack there of. &nbsp;Are we
 advocating a return to intermediate congestion control (I like X.25 as muc=
h as the next guy, but...). &nbsp;This is a very stark change of direction.=
 &nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I think mandating congestion control &nbsp;is not te=
chnically sound from either a theoretical (violation of end to end principl=
e, stacking of congestion control algorithms leading to complex and potenti=
ally suboptimal results) or economic perspective
 (as a very large backbone, we've been doing just fine without intermediate=
 congestion management thank you very much, and I have 0 desire to pay for =
a cost prohibitive, unnecessary feature in silicon.)<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I get Lars comments regarding reach, to some limited=
 extent. &nbsp;Ultimately, the implication seems to be that the protocols r=
iding the L2 network will have no form of congestion control and are fundam=
entally different than protocols that would
 reside on a typical wan. &nbsp;I have some serious doubts about this, alth=
ough I'm sure this is the case in some specialized environments. &nbsp;At a=
ny rate, it seems to me that a stern warning regarding edge filtering on in=
terdomain boundaries will be sufficient. &nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On Thu, Jan 23, 2014 at 1:15 PM, Joe Touch &lt;<a hr=
ef=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt; wrote:<=
o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal"><br>
<br>
On 1/22/2014 9:55 AM, Eggert, Lars wrote:<o:p></o:p></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">Hi,<br>
<br>
On 2014-1-22, at 18:29, Noel Chiappa &lt;<a href=3D"mailto:jnc@mercury.lcs.=
mit.edu" target=3D"_blank">jnc@mercury.lcs.mit.edu</a>&gt; wrote:<o:p></o:p=
></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal">Envision the following 4 (or more) scenarios for one=
 Border Tunneling Routing<br>
(BTR), BTR A, to send packets to another BTR, BTR B, on the path from ultim=
ate<br>
source S (somewhere before BTR A) to destination D (somewhere after BTR B).=
<br>
<br>
- Plain IP<br>
- Some existing encapsulation like GRE<br>
- A new, custom encapsulation<br>
- Encapsulation using UDP<br>
<br>
What you seem to be claiming is that in case 4 we need to have congestion<b=
r>
detection and response at the intermediate forwarding node BTR A - but it<b=
r>
would not be required in cases 1-3? This makes no sense.<o:p></o:p></p>
</blockquote>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">FWIW, the whole point of using UDP is to leverage th=
e Internet's ability to interpret the tunneled traffic as application data =
- to manage it according to port-based flow interpretation.<br>
<br>
There's a cost associated with that privilege - the cost of needing to reac=
t to congestion. That doesn't require 1-RTT, TCP-friendly dynamic congestio=
n control; it does mean *reacting* to congestion in some way, over some tim=
escale more than just ignoring things.<br>
<br>
This should be expected of any tunneling system that encapsulates non-react=
ive flows - regardless of technology.<span style=3D"color:#888888"><br>
<br>
<span class=3D"hoenzb">Joe</span></span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><br>
_______________________________________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/mpls</a><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</body>
</html>

--_000_e807421cc9fb4d98a46dce129aa39c82BLUPR05MB562namprd05pro_--

From scott.brim@gmail.com  Fri Jan 24 07:47:25 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D702E1A001E; Fri, 24 Jan 2014 07:47:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9rnNVEzP44L; Fri, 24 Jan 2014 07:47:24 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 416091A0021; Fri, 24 Jan 2014 07:47:24 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id wn1so3802458obc.9 for <multiple recipients>; Fri, 24 Jan 2014 07:47:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=qzq02ldwbLGHF7RdIB2Z2MxN5PPTXEtwQ5xp1pk0oQI=; b=fhq8nQpVU0/pq7HEao/1Y28bykdX4UEarLJNYYB2UwvSU4poHaUmOcQs9wAje79g5f 31rGUq9PfdRj8TwmmvyAvc3DKUA7ULvOador2z7Cl8eGkSwifYSf1qkPIkGFnH78d0tg DKylKfj57yVI5Ooisvhnms7vhGFcJrOIvxm7FacEMsD6iCeOBYOfuwk/OipoGGcNhami tccTrcozdVFJKHCfOvdhuytFvUWDrkSTDwfHvgAwH4+9FbO0fzgW8GE3p/JIuA4jnxmI EiLHTBmIhuRMSVyB9ArXmJKwSBbUbTttwGN8zBczyMabrP8ovsgltoUDx9jO7AqgWnAJ 0Htg==
X-Received: by 10.60.69.38 with SMTP id b6mr3342840oeu.27.1390578442952; Fri, 24 Jan 2014 07:47:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 24 Jan 2014 07:47:01 -0800 (PST)
In-Reply-To: <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 24 Jan 2014 10:47:01 -0500
Message-ID: <CAPv4CP_xP+VxgaAj7aogwFDQzt3cTeTmzfWY1qayuQ3teiaa3w@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: John E Drake <jdrake@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Edward Crabbe <edc@google.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 15:47:26 -0000

-05 version is out.

From curtis@ipv6.occnc.com  Thu Jan 23 19:21:02 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24A241A012A; Thu, 23 Jan 2014 19:21:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.937
X-Spam-Level: 
X-Spam-Status: No, score=-1.937 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mIB3PqSSyeRi; Thu, 23 Jan 2014 19:20:58 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id D0A1B1A018F; Thu, 23 Jan 2014 19:20:57 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0O3KsR9013700; Thu, 23 Jan 2014 22:20:54 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com>
To: Joe Touch <touch@isi.edu>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Thu, 23 Jan 2014 13:22:24 -0800." <52E18810.1010701@isi.edu>
Date: Thu, 23 Jan 2014 22:20:54 -0500
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:01:20 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 24 Jan 2014 03:21:02 -0000

In message <52E18810.1010701@isi.edu>
Joe Touch writes:
 
> Curtis,
>  
> If you're going with this argument (SHOULD vs MUST), then you need to 
> explain exactly *why* you're not doing what's recommended. "SHOULD" 
> isn't carte blanche to claim an exception.
>  
> And the need to avoid layered congestion control is a good justification 
> for not layering TCP-friendly on top of TCP-friendly, but not for 
> avoiding circuit breaker-style congestion controls/limits.
>  
> Joe


Joe,

I agree with you that the word SHOULD is not an automatic pass and
quoted from RFC 2119 because I think that on this thread the criteria
"valid reasons in particular circumstances" and "implications
... carefully weighed" have both been met.

Perhaps you joined the discussion a little late.

Please allow me to recap.  There are two issues under discussion, UDP
checksums and congestion control.

All parties seem to be OK with limiting the use of MPLS over UDP to
service providers only within their own infrastructure only, except
among cooperating service providers with explicit agreement
(consenting adults).

Within that context, some service providers find that parts of their
infrastructure either doesn't support MPLS at all or doesn't support a
usable variation of multipath for MPLS but does support IP ECMP (as I
understand it, this is primarily in the fringes, access and less so
edge - but someone who knows for sure please correct me if not).

This eliminates the "expands the reach of MPLS argument".

First UDP checksums:

  The UDP checksum is at the beginning of the payload.  Please see
  http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
  This makes filling in a new UDP checksum infeasible on most high end
  hardware.

  Within all of that context, all of the links have at least 32 bit
  FCS (either Ethernet framing or SONET or OTN) and some has much
  better such as the FEC found in OTN.  This makes undetected
  corruption by any of the links extremely unlikely.

  Corruption internal to the router the only potential impact.  There
  is good reason to think that this is extremely rare.

  Infeasibility of doing UDP checksums in some instances (not just
  performance concerns) is sufficient to make use of UDP checksums a
  SHOULD.

On to congestion control:

  Some MPLS payloads such as IP over MPLS have congestion control.
  While it can't be assured that all IP traffic makes use of
  congestion control, the problem is in the UDP services carried over
  MPLS regardless of whether MPLS over UDP is used.

  The only other type of traffic carried by MPLS in any volume (not
  counting ISIS control traffic carried as CLNP over MPLS, for
  example) is PW.

    PW in turn supports Ethernet, FR, ATM, TDM, and maybe a few
    others.  The vast majority of payload in Ethernet, FR, ATM, is IP
    so were are back to the prior bullet.  It PW packlet carrying
    Ethernet, FR, or ATM are dropped the congestion response is
    virtually identical to IP because the payload is IP.

    The other PW case is TDM.  TDM serves two purposes in SP networks.
    A small number of legacy customers circuits, generally T1 or T3
    use it.  These are 1.5 and 45 Mb/s services on 1 Gb/s and 10 Gb/s
    links.  Hardly a source of congestion, plus they pay a lot more
    and therefore are priority traffic.  Another is 3G mobile
    backhaul.  Again this is T1 or T3, but maybe as much as small
    multiples of T3.  Still very low capacity.

  TCP-like congestion control in a tunnel is very bad for any TCP
  carried within the tunnel.  The vast majority on MPLS traffic is IP
  and therefore is TCP.

  Regardless of the weak argument in favor of it given the operational
  reality, the authors have conceded to state that "MPLS over UDP
  SHOULD have congestion control" in the document.

  Because in the scenario it is intended to be deploy congestion
  control is very unlikely to prove to be needed, defining the exact
  form of congestion control is deferred to a later document which
  will be written only if needed.

That said, I have in the past argued that the "circuit breaker" form
of congestion control would be one of the worst things we could
possibly do.  It would be terrible for TCP and most anything else.
See http://www.ietf.org/mail-archive/web/mpls/current/msg11262.html
The right place to put any circuit breaker would be TDM over PW, but
given the capacities involved, that is not really needed either.

In the past I've said:

  The technical sticky point is knowing that the congestion is
  occuring.  Perhaps a LM like packet on another UDP port could be
  exchanged with the same caveats about inaccuracy if implemented in
  software and inaccuracy if reordering occurs, and a recommendation
  can be made to do something to introduce drop if congestion is
  indicated by this method.  How to introduce drop should be an
  implementation detail, a form of AQM or leaky bucket being possible
  choices, but entirely a local matter.

MPLS LM OAM would be a good choice for detection of congestion (as
evidenced by loss).  A leaky bucket (aka shaper) likely with AQM seems
like a reasonable choice.  This could be put into another document if
a need ever truly arises for congestion control in MPLS and it could
be applied to MPLS over anything (though it could prove impractical
for MPLS over avian carrier).

Curtis


> On 1/21/2014 12:58 PM, Curtis Villamizar wrote:
> > Lars,
> >
> > The IETF consensus in RFC5405 was to put a SHOULD in regarding use of
> > congestion control in tunneling protocols.
> >
> > RFC2119 states:
> >
> >    3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there
> >       may exist valid reasons in particular circumstances to ignore a
> >       particular item, but the full implications must be understood and
> >       carefully weighed before choosing a different course.
> >
> > We have discussed the reasons why congestion control is in general a
> > good thing.  We have also discussed why there may be valid reasons to
> > not include congestion control in MPLS over UDP.
> >
> > The question is not whether there is already IETF consensus on
> > congestion control in UDP in general.  There is consensus and that
> > consensus was to use the word "SHOULD".
> >
> > The question we now face is whether MPLS in UDP needs to up the prior
> > consensus to a MUST or can keep it as SHOULD.  I see one or maybe two
> > people vigorously arguing to upgrade this to a MUST and otherwise
> > consensus to keep this as SHOULD.  Further I see no objection except
> > the same one or maybe two people to making the congestion control the
> > topic of a later work if a need for it arises.  Consensus does not
> > require unanimous agreeement.
> >
> > If we are trying to gauge consensus, maybe both you and I should sit
> > back and let other people weigh in.
> >
> > Curtis
> >
> >
> > In message <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
> > "Eggert, Lars" writes:
> >>
> >> Hi,
> >>
> >> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> >>> You have made your assertions about your desire to uphold the purity
> >>> of any new UDP applications and adhere to the BCP you wrote.
> >>> =20
> >>> You appear to be very nearly alone in this argument and certainly no
> >>> one that works with MPLS is siding with you.
> >>
> >> the reason we wrote the RFC when I was TSV AD was that we were seeing a =
> >> whole bunch of questionable uses of UDP over the eyars and we were =
> >> having the same arguments over and over. That's why we decided to write =
> >> down the practices we expect users of UDP to follow. This is yet another =
> >> such questionable use.
> >>
> >> (Also, I don't appreciate you turning this into a personal argument.)
> >
> > Nothing personal intended.
> >
> > The important point is the sentence "You appear to be very nearly
> > alone in this argument and certainly no one that works with MPLS is
> > siding with you." was intended to point out that there is no consensus
> > behind your argument regardless of how vigorously you make that
> > argument.
> >
> >>> In the end we can put anything we want in the RFC *but* IETF has never
> >>> truly had the final word on what vendors and operators do in provider
> >>> networks.
> >>
> >> Aka the "take my toys and go home" argument. Heard it many times.
> >
> > It has been successful many times in the past.  It turns into the "its
> > deployed so get over it" argument after a few years.
> >
> >>> In this case, regardless of what changes are made to the draft,
> >>> implementations will offer at least the option for non-RFC behavior by
> >>> using zero checksums and not using any congestion control.  And
> >>> providers will make use of it, perhaps exclusively.
> >>
> >> And there's nothing wrong with that - the BCP even says that one SHOULD =
> >> NOT use congestion control for some deployment cases.
> >>
> >> But for others, one SHOULD. For those, a mechanism needs to be =
> >> available, i.e., it needs to be specified and implemented.
> >>
> >>> The document might as well reflect reality, despite reality not
> >>> conforming to your notions of architectural purity.
> >>
> >> I'm sorry, but we have certain architectural principles in the Internet =
> >> that we have IETF consensus on. At least since RFC2914, that includes =
> >> the need to have congestion control in place.
> >>
> >> There are always special deployment scenarios where these principles do =
> >> not apply, and we typically explain in applicability statements when out =
> >> specifications can only be safely used under certain conditions. I don't =
> >> see any such statement in draft-ietf-mpls-in-udp, which to me means it's =
> >> targeted at general Internet-wide use.
> >>
> >>> The best course of action is to put a SHOULD in regarding checksums
> >>> and put a SHOULD in regarding congestion avoidance.  Even the BCP does
> >>> not go any further than to say a tunneling protocol SHOULD use
> >>> congestion control and there were reasons that the word MUST was not
> >>> acceptable in the BCP.
> >>
> >> The SHOULD for congestion control needs to actually describe a mechanism =
> >> that can be used when needed. It can't be a blanket "you SHOULD use =
> >> something but we don't tell you what it is"-statement.
> >>
> >>> If we are still arguing over two instances of SHOULD vs MUST we have
> >>> wasted a lot of bandwidth on those two words.
> >>
> >> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs =
> >> to be specified what is to be done. In the case of checksums, that's =
> >> obvious (calculate it and check it); in the case of congestion control, =
> >> some actual mechanism needs to be described (e.g., a circuit breaker).
> >>
> >>> IMHO The only remaining question is whether the document can go =
> >> forward
> >>> with the definition of congestion control for MPLS over UDP left out
> >>> of scope and for another document if a need arises.
> >>
> >> In my opinion, it cannot.
> >>
> >>> If this is not acceptable to you (I doubt it is) please indicate what
> >>> you would like to see in the document and since this is IETF last call
> >>> where consensus matters and no one individual has veto power, we'll
> >>> have to see if there is consensus behind your proposed changes.
> >>
> >> I would like the document to specify at the very least a circuit breaker =
> >> mechanism, that stops the tunneled traffic if severe packet loss is =
> >> detected along the path.
> >>
> >> And this isn't about an "individual veto". This is about a document that =
> >> is at the moment in violation of IETF consensus at least as far back as =
> >> RFC2914.
> >>
> >> Lars

From curtis@ipv6.occnc.com  Thu Jan 23 20:05:17 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6D31A045D; Thu, 23 Jan 2014 20:05:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29x39oZsyOWd; Thu, 23 Jan 2014 20:05:14 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 68BE21A03D6; Thu, 23 Jan 2014 20:05:14 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0O45AEB014301; Thu, 23 Jan 2014 23:05:11 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401240405.s0O45AEB014301@maildrop2.v6ds.occnc.com>
To: Alia Atlas <akatlas@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Thu, 23 Jan 2014 19:07:25 -0500." <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
Date: Thu, 23 Jan 2014 23:05:10 -0500
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:01:20 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 24 Jan 2014 04:05:17 -0000

+1

Alia - Nice concise summary.  Thanks.

Curtis


In message <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
Alia Atlas writes:
> 
> I don't want to get in the way of vehement discussion, but I thought
> we were on the verge of finding an actual solution...
>  
> IMHO, that was a combination of an applicability statement, using
> SHOULD for congestion control and checksum, and defining a longer-term
> OAM-based approach (as Stewart Bryant suggested) to be able to verify
> that packet corruption or excessive drops aren't happening.
>  
> Does that sound like an acceptable set?
>  
> Alia
>  
>  
> On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu> wrote:
>  
> >
> >
> > On 1/23/2014 3:32 PM, Edward Crabbe wrote:
> >
> >> Joe, thanks for your response. Comments inline:
> >>
> >>
> >>     On 1/23/2014 1:27 PM, Edward Crabbe wrote:
> >>
> >>         Part of the point of using UDP is to make use of lowest common
> >>         denominator forwarding hardware in introducing entropy to
> >>         protocols that
> >>         lack it ( this is particularly true of the GRE in UDP use case
> >> also
> >>         under discussion elsewhere).
> >>
> >>         The tunnel is not the source of the traffic.  The _source of the
> >>         traffic_ is the source of the traffic.
> >>
> >>
> >>     To the Internet, the tunnel encapusulator is the source of traffic.
> >>     Tracing the data back further than that is a mirage at best - and
> >>     irrelevant.
> >>
> >>
> >> The 'internet' cares about characteristics of reactivity to congestion.
> >>   This is guaranteed by the /source of the traffic/ independent of any
> >> intermediate node.
> >>
> >
> > Are you prepared to make that a requirement of this document, i.e., that
> > the only MPLS traffic that can be UDP encapsulated is known to react to
> > congestion?
> >
> > How exactly can you know that?
> >
> >
> >      The tunnel head-end is responsible for the tunnel walking, talking,
> >>     and quaking like a duck (host). When the tunnel head-end knows
> >>     something about the ultimate origin of the traffic - whether real,
> >>     imagined, or from Asgard - then it has done it's duty (e.g., that
> >>     it's already congestion controlled).
> >>
> >>     But that head end is responsible, regardless of what it knows or
> >>     doesn't. And when it doesn't know, the only way to be responsible is
> >>     to put in its own reactivity.
> >>
> >> This is not fact; it's actually precisely the principle  we're currently
> >> arguing about.  ;)
> >>
> >
> > Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
> >
> > We can continue to debate it, but until it's been *changed* by a revision,
> > it remains BCP.
> >
> >
> >  I would posit:
> >>
> >> The tunnel doesn't have to know anything about congestion or performance
> >> characteristics because the originating application must.
> >>
> >
> > That works only if you know that fact about the originating application.
> > However, there are plenty of applications whose traffic goes over MPLS that
> > isn't congestion reactive or bandwidth-limited.
> >
> >
> > > See GRE,
> >
> >> MPLS, many other tunnel types,
> >>
> >
> > This isn't an issue for all tunnels until they enter the Internet...
> >
> >
> >  including several existing within the
> >> IETF that make use of an outer UDP header.
> >>
> >
> > Which are all already supposed to follow the recommendations of RFC5405.
> > To the extent that they don't, they don't agree with that BCP.
> >
> > I'm not saying such things never can or will exist, but I don't think the
> > IETF should be self-contradictory. We already agreed as a group on such
> > BCPs and other standards, and new standards-track docs need to follow them.
> >
> >
> >          The originating application
> >>         who's traffic is being tunneled should be responsible for
> >> congestion
> >>         control, or lack there of.
> >>
> >>     Perhaps it should be, but that's an agreement between whomever
> >>     implements/deploys the tunnel headend and whomever provides the
> >>     originating traffic to them. The problem is that this isn't true for
> >>     the typical use case for this kind of encapsulation.
> >>
> >> How so?  As mentioned before, this is the same case as standard GRE/MPLS
> >> etc.
> >>
> >
> > It's putting MPLS inside UDP. That's a different case, and the reason
> > RFC5405 applies.
> >
> >
> >      I.e., if we were talking about MPLS traffic that already was
> >>     reactive, we wouldn't be claiming the need for additional
> >>     encapsulator mechanism. It's precisely because nothing is known
> >>     about the MPLS traffic that the encapsulator needs to act.
> >>
> >> The MPLS traffic doesn't have to be reactive, it's the applications
> >> being encapsulated / traversing a particular tunnel that are responsible
> >> for and aware of path and congestion charateristics.  Because the MPLS
> >> head end knows nothing about the /end to end application 'session'/
> >> characteristics it /shouldn't/ have anything to do with congestion
> >> management.
> >>
> >
> > OK, so what you're saying is that "traffic using this encapsulation MUST
> > be known to be congestion reactive". Put that in the doc and we'll debate
> > whether we believe it.
> >
> > But right now you're basically saying that because you think it's someone
> > else's problem (the originating application), it isn't yours. The
> > difficulty with that logic is that you (the tunnel headend) is responsible
> > to ensure that this is true - either by *knowing* that the originating
> > traffic is congestion reactive, or by putting in its own mechanism to
> > ensure that this happens if the originating application isn't.
> >
> >
> >       > Are we advocating a return to intermediate
> >>
> >>         congestion control (I like X.25 as much as the next guy,
> >>         but...).  This
> >>         is a very stark change of direction.
> >>
> >>         I think mandating congestion control  is not technically sound
> >> from
> >>         either a theoretical (violation of end to end principle, stacking
> >> of
> >>         congestion control algorithms leading to complex and potentially
> >>         suboptimal results) or economic perspective (as a very large
> >>         backbone,
> >>         we've been doing just fine without intermediate congestion
> >>         management
> >>         thank you very much, and I have 0 desire to pay for a cost
> >>         prohibitive,
> >>         unnecessary feature in silicon.)
> >>
> >>     Write that up, and we'll see how it turns out in the IETF. However,
> >>     right now, the IETF BCPs do require reactive congestion management
> >>     of transport streams.
> >>
> >> Which part?  The end-to-end principle, or the aversion to congestion
> >> control stacking?  These have been implicit in all tunneling protocols
> >> produced by the IETF for the modern internet.
> >>
> >
> > Sure, and that's reflected in RFC5405 already. However, please, PLEASE
> > appreciate that NOBODY here is asking you to put in "congestion control
> > stacking"; that happens when you run two dynamic, reactive control
> > algorithms using the same timescale on top of each other.
> >
> > Equally well-known in CC circles is that you CAN - and often *should* -
> > stack different kinds of mechanisms at different layers with different
> > timescales. E.g., that's why we have an AQM WG - because even when all the
> > traffic is TCP, that's not quite enough inside the network. That's also why
> > Lars was suggesting something coarse on a longer timescale - a circuit
> > breaker - rather than AIMD on a RTT basis.
> >
> > Keep in mind as well that the E2E argument says that you can't get an E2E
> > service by composing the equivalent HBH one; it also says that HBH
> > mechanisms can be required for efficiency. That's what we're talking about
> > here - the efficiency impact of congestion, not the overall correctness of
> > E2E control.
> >
> >
> >      If you don't want/like that, then either don't use transport
> >>     encapsulation, or change the BCPs.
> >>
> >> These BCPs are defined for an originating /application/.
> >>
> >
> > Yes, and I don't understand why you (and others) keep thinking it matters
> > that there are layers of things behind the tunnel head end. It doesn't -
> > unless you KNOW what those layers are, and can ensure that they behave as
> > you expect.
> >
> >
> >  In this case
> >> the UDP header is simply a shim header applied to existing application
> >> traffic.
> >>
> >
> > It's not "simply a shim" - if that's the case, use IP and we're done. No
> > need for congestion control.
> >
> > The reason congestion issues arise is because you're inserting a header
> > ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.
> >
> > If you put in a UDP-like header that nobody in the Internet would
> > interpret, this wouldn't be an issue.
> >
> > But you simply cannot expect the Internet to treat you like "application"
> > traffic if you won't enforce acting like that traffic too.
> >
> >
> >  The tunnel head does not introduce traffic independent of the
> >> originating application.
> >>
> >
> > The Internet ****neither knows nor cares****.
> >
> > To the Internet, the head-end is the source. Whatever data the head end
> > puts inside the UDP packets *is application data* to the rest of the
> > Internet.
> >
> > Again, if you are saying that you know so much about the originating
> > source that you know you don't need additional mechanism at the headend,
> > say so - but then live by that requirement.
> >
> > If *any* MPLS traffic could show up at the headend, then it becomes the
> > headend's responsibility to do something.
> >
> > ---
> >
> > Consider the following case:
> >
> >         - video shows up inside the OS, destined for the network
> >
> >         - software X bundles that video and sends it to go out
> >
> >         - software Y puts that data into UDP packets to go
> >         to the Internet
> >
> > So what's the "application" here? To the Internet, it's software Y -- the
> > thing that puts the 'application' data into UDP packets. The previous steps
> > are irrelevant - just as irrelevant as the singer your video camera is
> > filming, as irrelevant as the sun that created the light that is reflected
> > off the singer to your camera.
> >
> > If software Y knows so much about the steps that lead to its input data
> > that it knows it's congestion reactive, nothing more need be done.
> >
> > If NOT (and that's the relevant corollary here), then it becomes software
> > Y's responsibility to put in some reactivity.
> >
> > Joe

From edc@google.com  Thu Jan 23 13:28:01 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A041A02D7 for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:28:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vnKt08EXEFGs for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 13:27:58 -0800 (PST)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 778411A00D0 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:27:58 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id z12so2127448wgg.18 for <ietf@ietf.org>; Thu, 23 Jan 2014 13:27:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ySeAoBVOKxEcgFiTTL0qa++Og2YCAQ8uttU9Q+IcfdM=; b=J1b2cLlQjYq8fwTDYZrqGp/CcvKir+doLGZvqvP9pkIBDmtIWkk1CQxexuMNMx894H w3KYraGbHrlRAcnvpdFxp9ZqMRXVqhfbSVH6W+5wK7aiNvXPKqdI/Iyh4OdYlQWZTfsW ZiAOXbdiA6poWXDB4vBfP72t/msjq40m7kZzlQo/wlLp867My8zUrVsGFLbjMm6LJ5f6 mOHUa10xpLIQlCPQ2JlyH0pfvAvyL12PinBD0zldsu3+t36eQI+l/VBIA54wpFHUSO09 5Q6ytVeOqZj8K/qucCmgVvRN7kImiGIWeDObxfauR5Dj2V8tFprO09Otj9iUnQP8KEnD tvEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ySeAoBVOKxEcgFiTTL0qa++Og2YCAQ8uttU9Q+IcfdM=; b=Os+5RS7j1WjiaOi8UUf3OsMBYZ9pQnNEHdrvIdQKfCvI/Mcr5Kqa0PoqrzrxfSy9m3 iyfJ4JocEYPkXvzTitlnFdnl0oQXDVqIqbLe3LXqxxytRK/120KSu3TRXPRtIJjFZDe4 BDBNKLvjUVzzOJlE7DmaYM07Ek6tK/+XtDlDxya7dg2uV2FRAizVWE6kW5/Ehhpk4yFy UNCXgWeHT7hnpt1FmHEeHnWEPZkZDDHrJs5musC+pYR8TFarxXrvUTBQSce844IYjSyN aAH5gCXC3K2h/RQs6i96KJZtlvSJOpv1fWY8CoMOQFU5KlLaZ1JRfaqsEi4zFXOmfit0 sPJg==
X-Gm-Message-State: ALoCoQmwtZ1p1u0QE+tsKouWahogMwXX4709ll6TS+lUHL/hjXOBARvCGzzKd/Lk80v/dJ7MCAhjlELmZtvim5Awn+vx/7pePkQA7F6s1+0Bc8LALmYs204von+IDEOxDKjAA5U9aPRUqT18yQbcjQ0M2HpF7dK/P7AaCeFe1n9x15ERfyZGzK492UHow+YqvD/BO9WWxi5v
X-Received: by 10.180.9.74 with SMTP id x10mr567884wia.52.1390512476895; Thu, 23 Jan 2014 13:27:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Thu, 23 Jan 2014 13:27:16 -0800 (PST)
In-Reply-To: <52E18661.4060000@isi.edu>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu>
From: Edward Crabbe <edc@google.com>
Date: Thu, 23 Jan 2014 13:27:16 -0800
Message-ID: <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=001a11c245fa3de08904f0a9eac1
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:01:46 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 21:28:01 -0000

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

Part of the point of using UDP is to make use of lowest common denominator
forwarding hardware in introducing entropy to protocols that lack it ( this
is particularly true of the GRE in UDP use case also under discussion
elsewhere).

The tunnel is not the source of the traffic.  The _source of the traffic_
is the source of the traffic.  The originating application who's traffic is
being tunneled should be responsible for congestion control, or lack there
of.  Are we advocating a return to intermediate congestion control (I like
X.25 as much as the next guy, but...).  This is a very stark change of
direction.

I think mandating congestion control  is not technically sound from either
a theoretical (violation of end to end principle, stacking of congestion
control algorithms leading to complex and potentially suboptimal results)
or economic perspective (as a very large backbone, we've been doing just
fine without intermediate congestion management thank you very much, and I
have 0 desire to pay for a cost prohibitive, unnecessary feature in
silicon.)

I get Lars comments regarding reach, to some limited extent.  Ultimately,
the implication seems to be that the protocols riding the L2 network will
have no form of congestion control and are fundamentally different than
protocols that would reside on a typical wan.  I have some serious doubts
about this, although I'm sure this is the case in some specialized
environments.  At any rate, it seems to me that a stern warning regarding
edge filtering on interdomain boundaries will be sufficient.


On Thu, Jan 23, 2014 at 1:15 PM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 1/22/2014 9:55 AM, Eggert, Lars wrote:
>
>> Hi,
>>
>> On 2014-1-22, at 18:29, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>>
>>> Envision the following 4 (or more) scenarios for one Border Tunneling
>>> Routing
>>> (BTR), BTR A, to send packets to another BTR, BTR B, on the path from
>>> ultimate
>>> source S (somewhere before BTR A) to destination D (somewhere after BTR
>>> B).
>>>
>>> - Plain IP
>>> - Some existing encapsulation like GRE
>>> - A new, custom encapsulation
>>> - Encapsulation using UDP
>>>
>>> What you seem to be claiming is that in case 4 we need to have congestion
>>> detection and response at the intermediate forwarding node BTR A - but it
>>> would not be required in cases 1-3? This makes no sense.
>>>
>>
> FWIW, the whole point of using UDP is to leverage the Internet's ability
> to interpret the tunneled traffic as application data - to manage it
> according to port-based flow interpretation.
>
> There's a cost associated with that privilege - the cost of needing to
> react to congestion. That doesn't require 1-RTT, TCP-friendly dynamic
> congestion control; it does mean *reacting* to congestion in some way, over
> some timescale more than just ignoring things.
>
> This should be expected of any tunneling system that encapsulates
> non-reactive flows - regardless of technology.
>
> Joe
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

<div dir=3D"ltr">Part of the point of using UDP is to make use of lowest co=
mmon denominator forwarding hardware in introducing entropy to protocols th=
at lack it ( this is particularly true of the GRE in UDP use case also unde=
r discussion elsewhere).=A0<div>

<br></div><div>The tunnel is not the source of the traffic. =A0The _source =
of the traffic_ is the source of the traffic. =A0The originating applicatio=
n who&#39;s traffic is being tunneled should be responsible for congestion =
control, or lack there of. =A0Are we advocating a return to intermediate co=
ngestion control (I like X.25 as much as the next guy, but...). =A0This is =
a very stark change of direction. =A0</div>

<div><br></div><div>I think mandating congestion control =A0is not technica=
lly sound from either a theoretical (violation of end to end principle, sta=
cking of congestion control algorithms leading to complex and potentially s=
uboptimal results) or economic perspective (as a very large backbone, we&#3=
9;ve been doing just fine without intermediate congestion management thank =
you very much, and I have 0 desire to pay for a cost prohibitive, unnecessa=
ry feature in silicon.)</div>

<div><br></div><div>I get Lars comments regarding reach, to some limited ex=
tent. =A0Ultimately, the implication seems to be that the protocols riding =
the L2 network will have no form of congestion control and are fundamentall=
y different than protocols that would reside on a typical wan. =A0I have so=
me serious doubts about this, although I&#39;m sure this is the case in som=
e specialized environments. =A0At any rate, it seems to me that a stern war=
ning regarding edge filtering on interdomain boundaries will be sufficient.=
 =A0</div>

</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Jan 23, 2014 at 1:15 PM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto=
:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">

<div class=3D"im"><br>
<br>
On 1/22/2014 9:55 AM, Eggert, Lars wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi,<br>
<br>
On 2014-1-22, at 18:29, Noel Chiappa &lt;<a href=3D"mailto:jnc@mercury.lcs.=
mit.edu" target=3D"_blank">jnc@mercury.lcs.mit.edu</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Envision the following 4 (or more) scenarios for one Border Tunneling Routi=
ng<br>
(BTR), BTR A, to send packets to another BTR, BTR B, on the path from ultim=
ate<br>
source S (somewhere before BTR A) to destination D (somewhere after BTR B).=
<br>
<br>
- Plain IP<br>
- Some existing encapsulation like GRE<br>
- A new, custom encapsulation<br>
- Encapsulation using UDP<br>
<br>
What you seem to be claiming is that in case 4 we need to have congestion<b=
r>
detection and response at the intermediate forwarding node BTR A - but it<b=
r>
would not be required in cases 1-3? This makes no sense.<br>
</blockquote></blockquote>
<br></div>
FWIW, the whole point of using UDP is to leverage the Internet&#39;s abilit=
y to interpret the tunneled traffic as application data - to manage it acco=
rding to port-based flow interpretation.<br>
<br>
There&#39;s a cost associated with that privilege - the cost of needing to =
react to congestion. That doesn&#39;t require 1-RTT, TCP-friendly dynamic c=
ongestion control; it does mean *reacting* to congestion in some way, over =
some timescale more than just ignoring things.<br>


<br>
This should be expected of any tunneling system that encapsulates non-react=
ive flows - regardless of technology.<span class=3D"HOEnZb"><font color=3D"=
#888888"><br>
<br>
Joe</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
______________________________<u></u>_________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/mpls</a><br>
</div></div></blockquote></div><br></div>

--001a11c245fa3de08904f0a9eac1--

From edc@google.com  Thu Jan 23 15:32:47 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C2F1A0240 for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 15:32:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBiTMUxawzJR for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 15:32:45 -0800 (PST)
Received: from mail-wg0-x22a.google.com (mail-wg0-x22a.google.com [IPv6:2a00:1450:400c:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D33C31A01FE for <ietf@ietf.org>; Thu, 23 Jan 2014 15:32:44 -0800 (PST)
Received: by mail-wg0-f42.google.com with SMTP id l18so1241100wgh.1 for <ietf@ietf.org>; Thu, 23 Jan 2014 15:32:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7iEPFVrQDwc4acl4MKrckex2YxOTgnXyGxXhsmkODEQ=; b=pa4QVk5Pp8ZlhFoWQXHGnwqGLthIavXIhgaje1DZP6CfrvptzWZ0FBOObDcw2CSvYh 42X5wDsMF/g+DgouVPFQjo+cgiGOPXdblQW2u3T0tWBROs9iu/gwjNeO4lNKW8uSk7R4 v3d3P/1P2JqGpub17yNupT8ZI8ACteDPh1qd6c5BdgBFey2o4qckPEQ/ZbtqaO+8hT45 wfPhZDae7rmGUJJAPvzoNV/RFL874ozDwgwOjB8/AHQoShTWaBgmZvrQy0ViPupp05u+ dVUZwrxZ6F1WVNvWq+YjHpbFW+Ge7YmVikO9qZMgWLm1Yop12FnrcdLC0Qv5QrGqrADX 94MQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7iEPFVrQDwc4acl4MKrckex2YxOTgnXyGxXhsmkODEQ=; b=GF+jWAFQtxTO6SLRef3xTqNtSkefLzJapXEG9J6qFVUVJpglbUAZEfjAJ33tkocqHA hamLa1BhpJWddM4dbMrKOlS1dpWrugJ8RdbY5W6X8Tkv1XyRtb3EMn8AZ2hiGFzd+poE 1fzEUXZlHxNzLDH7Skkm9oMphlHhcDtkNvvG0OD78hrPesnlu4ty+gv1om05xLpzeAEB OGnSxlyRHSAU1AJEIqacBzOSrYDRJYyxNfBq+HnQ/1IRmpm/buBlrA+iCeRwSiZXst/m eVX+YDfYPW334uVQgnjGbLow0pMTndTcAMx46lyk21RJMnmr2VySC9wYs7HPjk/b2oL4 hGJg==
X-Gm-Message-State: ALoCoQnGLVVus+KavHRUD3XbWg+LgolC78+/Zq1p07Hrj1KYB+JwcyhO/WGzg8Qt5C1lDmqEiSiczPVa2F0/nv+w4tQWNuAmmwQ1ZnxXZ5vUs3OK8x1HVov+BNkgjhY5seTryLXXgK4SsLOV15VfpKdQP3XCwNjUAdRWHKzB/VR61SXix85UKZX8e/qBcU/KmiTYtrKLCqUy
X-Received: by 10.195.13.17 with SMTP id eu17mr8614706wjd.24.1390519963327; Thu, 23 Jan 2014 15:32:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Thu, 23 Jan 2014 15:32:03 -0800 (PST)
In-Reply-To: <52E18BF1.1040004@isi.edu>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu>
From: Edward Crabbe <edc@google.com>
Date: Thu, 23 Jan 2014 15:32:03 -0800
Message-ID: <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=047d7bd91a7a77b4c304f0aba8c7
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:01:44 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2014 23:32:47 -0000

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

Joe, thanks for your response. Comments inline:


> On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>
>> Part of the point of using UDP is to make use of lowest common
>> denominator forwarding hardware in introducing entropy to protocols that
>> lack it ( this is particularly true of the GRE in UDP use case also
>> under discussion elsewhere).
>>
>> The tunnel is not the source of the traffic.  The _source of the
>> traffic_ is the source of the traffic.
>>
>
> To the Internet, the tunnel encapusulator is the source of traffic.
> Tracing the data back further than that is a mirage at best - and
> irrelevant.
>

The 'internet' cares about characteristics of reactivity to congestion.
 This is guaranteed by the /source of the traffic/ independent of any
intermediate node.


>
> The tunnel head-end is responsible for the tunnel walking, talking, and
> quaking like a duck (host). When the tunnel head-end knows something about
> the ultimate origin of the traffic - whether real, imagined, or from Asgard
> - then it has done it's duty (e.g., that it's already congestion
> controlled).
>
> But that head end is responsible, regardless of what it knows or doesn't.
> And when it doesn't know, the only way to be responsible is to put in its
> own reactivity.


This is not fact; it's actually precisely the principle  we're currently
arguing about.  ;)

I would posit:

The tunnel doesn't have to know anything about congestion or performance
characteristics because the originating application must.  See GRE, MPLS,
many other tunnel types, including several existing within the IETF that
make use of an outer UDP header.


>
>
>  The originating application
>> who's traffic is being tunneled should be responsible for congestion
>> control, or lack there of.
>>
>
> Perhaps it should be, but that's an agreement between whomever
> implements/deploys the tunnel headend and whomever provides the originating
> traffic to them. The problem is that this isn't true for the typical use
> case for this kind of encapsulation.
>

How so?  As mentioned before, this is the same case as standard GRE/MPLS
etc.


>
> I.e., if we were talking about MPLS traffic that already was reactive, we
> wouldn't be claiming the need for additional encapsulator mechanism. It's
> precisely because nothing is known about the MPLS traffic that the
> encapsulator needs to act.


The MPLS traffic doesn't have to be reactive, it's the applications being
encapsulated / traversing a particular tunnel that are responsible for and
aware of path and congestion charateristics.  Because the MPLS head end
knows nothing about the /end to end application 'session'/ characteristics
it /shouldn't/ have anything to do with congestion management.


>
> > Are we advocating a return to intermediate
>
>> congestion control (I like X.25 as much as the next guy, but...).  This
>> is a very stark change of direction.
>>
>> I think mandating congestion control  is not technically sound from
>> either a theoretical (violation of end to end principle, stacking of
>> congestion control algorithms leading to complex and potentially
>> suboptimal results) or economic perspective (as a very large backbone,
>> we've been doing just fine without intermediate congestion management
>> thank you very much, and I have 0 desire to pay for a cost prohibitive,
>> unnecessary feature in silicon.)
>>
>
> Write that up, and we'll see how it turns out in the IETF. However, right
> now, the IETF BCPs do require reactive congestion management of transport
> streams.
>

Which part?  The end-to-end principle, or the aversion to congestion
control stacking?  These have been implicit in all tunneling protocols
produced by the IETF for the modern internet.


> If you don't want/like that, then either don't use transport
> encapsulation, or change the BCPs.



These BCPs are defined for an originating /application/.  In this case the
UDP header is simply a shim header applied to existing application traffic.
 The tunnel head does not introduce traffic independent of the originating
application.


>
>
>  I get Lars comments regarding reach, to some limited extent.
>>   Ultimately, the implication seems to be that the protocols riding the
>> L2 network will have no form of congestion control and are fundamentally
>> different than protocols that would reside on a typical wan.  I have
>> some serious doubts about this, although I'm sure this is the case in
>> some specialized environments.  At any rate, it seems to me that a stern
>> warning regarding edge filtering on interdomain boundaries will be
>> sufficient.
>>
>
> My concern may be slightly different that his. My concern is that you want
> the benefits of a UDP header, but don't like the responsibilities that come
> along with it.
>
> Joe
>
>

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

<div dir=3D"ltr">Joe, thanks for your response. Comments inline:<div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div>

<br>
On 1/23/2014 1:27 PM, Edward Crabbe wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Part of the point of using UDP is to make use of lowest common<br>
denominator forwarding hardware in introducing entropy to protocols that<br=
>
lack it ( this is particularly true of the GRE in UDP use case also<br>
under discussion elsewhere).<br>
<br>
The tunnel is not the source of the traffic. =A0The _source of the<br>
traffic_ is the source of the traffic.<br>
</blockquote>
<br></div>
To the Internet, the tunnel encapusulator is the source of traffic. Tracing=
 the data back further than that is a mirage at best - and irrelevant.<br><=
/blockquote><div><br></div><div>The &#39;internet&#39; cares about characte=
ristics of reactivity to congestion. =A0This is guaranteed by the /source o=
f the traffic/ independent of any intermediate node.=A0</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
The tunnel head-end is responsible for the tunnel walking, talking, and qua=
king like a duck (host). When the tunnel head-end knows something about the=
 ultimate origin of the traffic - whether real, imagined, or from Asgard - =
then it has done it&#39;s duty (e.g., that it&#39;s already congestion cont=
rolled).<br>



<br>
But that head end is responsible, regardless of what it knows or doesn&#39;=
t. And when it doesn&#39;t know, the only way to be responsible is to put i=
n its own reactivity.</blockquote><div><br></div><div>This is not fact; it&=
#39;s actually precisely the principle =A0we&#39;re currently arguing about=
. =A0;)</div>

<div><br></div><div>I would posit:</div><div><br></div><div>The tunnel does=
n&#39;t have to know anything about congestion or performance characteristi=
cs because the originating application must. =A0See GRE, MPLS, many other t=
unnel types, including several existing within the IETF that make use of an=
 outer UDP header.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The originating application<br>
who&#39;s traffic is being tunneled should be responsible for congestion<br=
>
control, or lack there of.<br>
</blockquote>
<br></div>
Perhaps it should be, but that&#39;s an agreement between whomever implemen=
ts/deploys the tunnel headend and whomever provides the originating traffic=
 to them. The problem is that this isn&#39;t true for the typical use case =
for this kind of encapsulation.<br>

</blockquote><div><br></div><div>How so? =A0As mentioned before, this is th=
e same case as standard GRE/MPLS etc. =A0</div><div>=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">



<br>
I.e., if we were talking about MPLS traffic that already was reactive, we w=
ouldn&#39;t be claiming the need for additional encapsulator mechanism. It&=
#39;s precisely because nothing is known about the MPLS traffic that the en=
capsulator needs to act.</blockquote>

<div><br></div><div>The MPLS traffic doesn&#39;t have to be reactive, it&#3=
9;s the applications being encapsulated / traversing a particular tunnel th=
at are responsible for and aware of path and congestion charateristics. =A0=
Because the MPLS head end knows nothing about the /end to end application &=
#39;session&#39;/ characteristics it /shouldn&#39;t/ have anything to do wi=
th congestion management. =A0</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
&gt; Are we advocating a return to intermediate<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
congestion control (I like X.25 as much as the next guy, but...). =A0This<b=
r>
is a very stark change of direction.<br>
<br>
I think mandating congestion control =A0is not technically sound from<br>
either a theoretical (violation of end to end principle, stacking of<br>
congestion control algorithms leading to complex and potentially<br>
suboptimal results) or economic perspective (as a very large backbone,<br>
we&#39;ve been doing just fine without intermediate congestion management<b=
r>
thank you very much, and I have 0 desire to pay for a cost prohibitive,<br>
unnecessary feature in silicon.)<br>
</blockquote>
<br></div>
Write that up, and we&#39;ll see how it turns out in the IETF. However, rig=
ht now, the IETF BCPs do require reactive congestion management of transpor=
t streams.<br></blockquote><div><br></div><div>Which part? =A0The end-to-en=
d principle, or the aversion to congestion control stacking? =A0These have =
been implicit in all tunneling protocols produced by the IETF for the moder=
n internet.=A0</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
If you don&#39;t want/like that, then either don&#39;t use transport encaps=
ulation, or change the BCPs.</blockquote><div><br></div><div><br></div><div=
>These BCPs are defined for an originating /application/. =A0In this case t=
he UDP header is simply a shim header applied to existing application traff=
ic. =A0The tunnel head does not introduce traffic independent of the origin=
ating application. =A0</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I get Lars comments regarding reach, to some limited extent.<br>
=A0 Ultimately, the implication seems to be that the protocols riding the<b=
r>
L2 network will have no form of congestion control and are fundamentally<br=
>
different than protocols that would reside on a typical wan. =A0I have<br>
some serious doubts about this, although I&#39;m sure this is the case in<b=
r>
some specialized environments. =A0At any rate, it seems to me that a stern<=
br>
warning regarding edge filtering on interdomain boundaries will be<br>
sufficient.<br>
</blockquote>
<br></div>
My concern may be slightly different that his. My concern is that you want =
the benefits of a UDP header, but don&#39;t like the responsibilities that =
come along with it.<span><font color=3D"#888888"><br>
<br>
Joe<br>
<br>
</font></span></blockquote></div><br></div></div>

--047d7bd91a7a77b4c304f0aba8c7--

From edc@google.com  Thu Jan 23 16:09:09 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B14221A049A for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 16:09:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdsK35yLNmWt for <ietf@ietfa.amsl.com>; Thu, 23 Jan 2014 16:09:06 -0800 (PST)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id E19881A048F for <ietf@ietf.org>; Thu, 23 Jan 2014 16:09:05 -0800 (PST)
Received: by mail-we0-f177.google.com with SMTP id x55so1967692wes.22 for <ietf@ietf.org>; Thu, 23 Jan 2014 16:09:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jI6V2xlZ2oaxIW6hKnc+9sUSJ1S3GLJ13RLK+iDfNV8=; b=SmZm1kJL16ST0la54OuW/vEj1c2y15+A/letuk2MUsAUXEFJqwsBG/8KvAZk6mMkbw pbbR7MvNIwImZ8ZOt7OjKMvxzcMWq9VTOLk8mEVJ0AqJsrux+l/7nlMaAUSSOvAuZnPx RcCSGfuOIIl/O35xQXTC79ZRvbEeJtSG0VYGRleqSn1V7zvfghGp1uSbpubmEVOFTf8j fYSfLKtXjJTU2+RfgXI4cDu8cQqf0WHDdBlc8+uEsrLWA9UxyKr81/yuFCyDVUApCbgy 4MSp/MCHjkwDd5H6K5hyNT8YI/BdMjHG2oghNSkSPPW6wzi5eysGmk5wrYzdKHhHDHEW sR+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=jI6V2xlZ2oaxIW6hKnc+9sUSJ1S3GLJ13RLK+iDfNV8=; b=AaWXh6edtl7UlFKWIiH3/wLC3E7JYRWzzAISZ9s11UsMnH1lXTIGfJbWQTqVj927um 2t7tlQA99yjpdBhpQWvcdbsy+Pa272BSQOY2I+KF3SWTMry4gEq9RdTYzzyzYdzwBLBG 0CbNqeaE5X6NMnOcAwANE6wnuDDv6/MwdzZ3BhtPlFJB2XpH1z3TB6ZJAbapBNF6Q/W5 cBpnZ4HCsleEnXCXZCyHPKBIGMa8y1P1EqFv2nBLSVO91CcApKmkQHe0CnA+f2RdLBYn Z2TOwVve/jxpzlMebufA+wfQWb5NJEoX8z7dBAJAD/IdJgDoutd3wsAmTKxaJ+T5RuEY tMmQ==
X-Gm-Message-State: ALoCoQmJWwAJThHpYlShpfK5Y0VS3ZfNz/WIBKRq/2REp/371I7Ov96lhLH4TuV/ZapgcgtN3QALhJOUTsBvBWdq9ys9ihCbn7jNAq9CPBk6yf+gm8f2KrdWMfpo0cw2Ju3mAWupuBjTp/15E76sjm9jGWFyGMBP7Iztn8BrgxRSChPvTJtlsoeOFrtSm84+8WZa6dlSSKUF
X-Received: by 10.180.93.169 with SMTP id cv9mr1093140wib.3.1390522144277; Thu, 23 Jan 2014 16:09:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Thu, 23 Jan 2014 16:08:24 -0800 (PST)
In-Reply-To: <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com> <52E1AC3E.2040204@isi.edu> <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
From: Edward Crabbe <edc@google.com>
Date: Thu, 23 Jan 2014 16:08:24 -0800
Message-ID: <CACKN6JEA--9zXgLSWfMHpJD3svQ-JeMPBq2sazPifbujSpwn7g@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c7fc0769e9404f0ac2aea
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:01:40 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 00:09:09 -0000

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

I think there also needs to be a network boundary statement with
recommendations for filtering and usage in terms of intra vs interdomain
protocol usage.


On Thu, Jan 23, 2014 at 4:07 PM, Alia Atlas <akatlas@gmail.com> wrote:

> I don't want to get in the way of vehement discussion, but I thought we
> were on the verge of finding an actual solution...
>
> IMHO, that was a combination of an applicability statement, using SHOULD
> for congestion control and checksum, and defining a longer-term OAM-based
> approach (as Stewart Bryant suggested) to be able to verify that packet
> corruption or excessive drops aren't happening.
>
> Does that sound like an acceptable set?
>
> Alia
>
>
> On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <touch@isi.edu> wrote:
>
>>
>>
>> On 1/23/2014 3:32 PM, Edward Crabbe wrote:
>>
>>> Joe, thanks for your response. Comments inline:
>>>
>>>
>>>     On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>>>
>>>         Part of the point of using UDP is to make use of lowest common
>>>         denominator forwarding hardware in introducing entropy to
>>>         protocols that
>>>         lack it ( this is particularly true of the GRE in UDP use case
>>> also
>>>         under discussion elsewhere).
>>>
>>>         The tunnel is not the source of the traffic.  The _source of the
>>>         traffic_ is the source of the traffic.
>>>
>>>
>>>     To the Internet, the tunnel encapusulator is the source of traffic.
>>>     Tracing the data back further than that is a mirage at best - and
>>>     irrelevant.
>>>
>>>
>>> The 'internet' cares about characteristics of reactivity to congestion.
>>>   This is guaranteed by the /source of the traffic/ independent of any
>>> intermediate node.
>>>
>>
>> Are you prepared to make that a requirement of this document, i.e., that
>> the only MPLS traffic that can be UDP encapsulated is known to react to
>> congestion?
>>
>> How exactly can you know that?
>>
>>
>>      The tunnel head-end is responsible for the tunnel walking, talking,
>>>     and quaking like a duck (host). When the tunnel head-end knows
>>>     something about the ultimate origin of the traffic - whether real,
>>>     imagined, or from Asgard - then it has done it's duty (e.g., that
>>>     it's already congestion controlled).
>>>
>>>     But that head end is responsible, regardless of what it knows or
>>>     doesn't. And when it doesn't know, the only way to be responsible is
>>>     to put in its own reactivity.
>>>
>>> This is not fact; it's actually precisely the principle  we're currently
>>> arguing about.  ;)
>>>
>>
>> Actually, it's a paraphrasing of Section 3.1.3 of RFC5405.
>>
>> We can continue to debate it, but until it's been *changed* by a
>> revision, it remains BCP.
>>
>>
>>  I would posit:
>>>
>>> The tunnel doesn't have to know anything about congestion or performance
>>> characteristics because the originating application must.
>>>
>>
>> That works only if you know that fact about the originating application.
>> However, there are plenty of applications whose traffic goes over MPLS that
>> isn't congestion reactive or bandwidth-limited.
>>
>>
>> > See GRE,
>>
>>> MPLS, many other tunnel types,
>>>
>>
>> This isn't an issue for all tunnels until they enter the Internet...
>>
>>
>>  including several existing within the
>>> IETF that make use of an outer UDP header.
>>>
>>
>> Which are all already supposed to follow the recommendations of RFC5405.
>> To the extent that they don't, they don't agree with that BCP.
>>
>> I'm not saying such things never can or will exist, but I don't think the
>> IETF should be self-contradictory. We already agreed as a group on such
>> BCPs and other standards, and new standards-track docs need to follow them.
>>
>>
>>          The originating application
>>>         who's traffic is being tunneled should be responsible for
>>> congestion
>>>         control, or lack there of.
>>>
>>>     Perhaps it should be, but that's an agreement between whomever
>>>     implements/deploys the tunnel headend and whomever provides the
>>>     originating traffic to them. The problem is that this isn't true for
>>>     the typical use case for this kind of encapsulation.
>>>
>>> How so?  As mentioned before, this is the same case as standard GRE/MPLS
>>> etc.
>>>
>>
>> It's putting MPLS inside UDP. That's a different case, and the reason
>> RFC5405 applies.
>>
>>
>>      I.e., if we were talking about MPLS traffic that already was
>>>     reactive, we wouldn't be claiming the need for additional
>>>     encapsulator mechanism. It's precisely because nothing is known
>>>     about the MPLS traffic that the encapsulator needs to act.
>>>
>>> The MPLS traffic doesn't have to be reactive, it's the applications
>>> being encapsulated / traversing a particular tunnel that are responsible
>>> for and aware of path and congestion charateristics.  Because the MPLS
>>> head end knows nothing about the /end to end application 'session'/
>>> characteristics it /shouldn't/ have anything to do with congestion
>>> management.
>>>
>>
>> OK, so what you're saying is that "traffic using this encapsulation MUST
>> be known to be congestion reactive". Put that in the doc and we'll debate
>> whether we believe it.
>>
>> But right now you're basically saying that because you think it's someone
>> else's problem (the originating application), it isn't yours. The
>> difficulty with that logic is that you (the tunnel headend) is responsible
>> to ensure that this is true - either by *knowing* that the originating
>> traffic is congestion reactive, or by putting in its own mechanism to
>> ensure that this happens if the originating application isn't.
>>
>>
>>       > Are we advocating a return to intermediate
>>>
>>>         congestion control (I like X.25 as much as the next guy,
>>>         but...).  This
>>>         is a very stark change of direction.
>>>
>>>         I think mandating congestion control  is not technically sound
>>> from
>>>         either a theoretical (violation of end to end principle,
>>> stacking of
>>>         congestion control algorithms leading to complex and potentially
>>>         suboptimal results) or economic perspective (as a very large
>>>         backbone,
>>>         we've been doing just fine without intermediate congestion
>>>         management
>>>         thank you very much, and I have 0 desire to pay for a cost
>>>         prohibitive,
>>>         unnecessary feature in silicon.)
>>>
>>>     Write that up, and we'll see how it turns out in the IETF. However,
>>>     right now, the IETF BCPs do require reactive congestion management
>>>     of transport streams.
>>>
>>> Which part?  The end-to-end principle, or the aversion to congestion
>>> control stacking?  These have been implicit in all tunneling protocols
>>> produced by the IETF for the modern internet.
>>>
>>
>> Sure, and that's reflected in RFC5405 already. However, please, PLEASE
>> appreciate that NOBODY here is asking you to put in "congestion control
>> stacking"; that happens when you run two dynamic, reactive control
>> algorithms using the same timescale on top of each other.
>>
>> Equally well-known in CC circles is that you CAN - and often *should* -
>> stack different kinds of mechanisms at different layers with different
>> timescales. E.g., that's why we have an AQM WG - because even when all the
>> traffic is TCP, that's not quite enough inside the network. That's also why
>> Lars was suggesting something coarse on a longer timescale - a circuit
>> breaker - rather than AIMD on a RTT basis.
>>
>> Keep in mind as well that the E2E argument says that you can't get an E2E
>> service by composing the equivalent HBH one; it also says that HBH
>> mechanisms can be required for efficiency. That's what we're talking about
>> here - the efficiency impact of congestion, not the overall correctness of
>> E2E control.
>>
>>
>>      If you don't want/like that, then either don't use transport
>>>     encapsulation, or change the BCPs.
>>>
>>> These BCPs are defined for an originating /application/.
>>>
>>
>> Yes, and I don't understand why you (and others) keep thinking it matters
>> that there are layers of things behind the tunnel head end. It doesn't -
>> unless you KNOW what those layers are, and can ensure that they behave as
>> you expect.
>>
>>
>>  In this case
>>> the UDP header is simply a shim header applied to existing application
>>> traffic.
>>>
>>
>> It's not "simply a shim" - if that's the case, use IP and we're done. No
>> need for congestion control.
>>
>> The reason congestion issues arise is because you're inserting a header
>> ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.
>>
>> If you put in a UDP-like header that nobody in the Internet would
>> interpret, this wouldn't be an issue.
>>
>> But you simply cannot expect the Internet to treat you like "application"
>> traffic if you won't enforce acting like that traffic too.
>>
>>
>>  The tunnel head does not introduce traffic independent of the
>>> originating application.
>>>
>>
>> The Internet ****neither knows nor cares****.
>>
>> To the Internet, the head-end is the source. Whatever data the head end
>> puts inside the UDP packets *is application data* to the rest of the
>> Internet.
>>
>> Again, if you are saying that you know so much about the originating
>> source that you know you don't need additional mechanism at the headend,
>> say so - but then live by that requirement.
>>
>> If *any* MPLS traffic could show up at the headend, then it becomes the
>> headend's responsibility to do something.
>>
>> ---
>>
>> Consider the following case:
>>
>>         - video shows up inside the OS, destined for the network
>>
>>         - software X bundles that video and sends it to go out
>>
>>         - software Y puts that data into UDP packets to go
>>         to the Internet
>>
>> So what's the "application" here? To the Internet, it's software Y -- the
>> thing that puts the 'application' data into UDP packets. The previous steps
>> are irrelevant - just as irrelevant as the singer your video camera is
>> filming, as irrelevant as the sun that created the light that is reflected
>> off the singer to your camera.
>>
>> If software Y knows so much about the steps that lead to its input data
>> that it knows it's congestion reactive, nothing more need be done.
>>
>> If NOT (and that's the relevant corollary here), then it becomes software
>> Y's responsibility to put in some reactivity.
>>
>> Joe
>>
>
>

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

<div dir=3D"ltr">I think there also needs to be a network boundary statemen=
t with recommendations for filtering and usage in terms of intra vs interdo=
main protocol usage.=A0</div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">

On Thu, Jan 23, 2014 at 4:07 PM, Alia Atlas <span dir=3D"ltr">&lt;<a href=
=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">

<div dir=3D"ltr">I don&#39;t want to get in the way of vehement discussion,=
 but I thought we were on the verge of finding an actual solution...<div><b=
r></div><div>IMHO, that was a combination of an applicability statement, us=
ing SHOULD for congestion control and checksum, and defining a longer-term =
OAM-based approach (as Stewart Bryant suggested) to be able to verify that =
packet corruption or excessive drops aren&#39;t happening.</div>


<div><br></div><div>Does that sound like an acceptable set?</div><span clas=
s=3D"HOEnZb"><font color=3D"#888888"><div><br></div><div>Alia</div></font><=
/span></div><div class=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_ext=
ra"><br>

<br><div class=3D"gmail_quote">On Thu, Jan 23, 2014 at 6:56 PM, Joe Touch <=
span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D"_blank">tou=
ch@isi.edu</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><br>
<br>
On 1/23/2014 3:32 PM, Edward Crabbe wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Joe, thanks for your response. Comments inline:<br>
<br>
<br>
=A0 =A0 On 1/23/2014 1:27 PM, Edward Crabbe wrote:<br>
<br>
=A0 =A0 =A0 =A0 Part of the point of using UDP is to make use of lowest com=
mon<br>
=A0 =A0 =A0 =A0 denominator forwarding hardware in introducing entropy to<b=
r>
=A0 =A0 =A0 =A0 protocols that<br>
=A0 =A0 =A0 =A0 lack it ( this is particularly true of the GRE in UDP use c=
ase also<br>
=A0 =A0 =A0 =A0 under discussion elsewhere).<br>
<br>
=A0 =A0 =A0 =A0 The tunnel is not the source of the traffic. =A0The _source=
 of the<br>
=A0 =A0 =A0 =A0 traffic_ is the source of the traffic.<br>
<br>
<br>
=A0 =A0 To the Internet, the tunnel encapusulator is the source of traffic.=
<br>
=A0 =A0 Tracing the data back further than that is a mirage at best - and<b=
r>
=A0 =A0 irrelevant.<br>
<br>
<br>
The &#39;internet&#39; cares about characteristics of reactivity to congest=
ion.<br>
=A0 This is guaranteed by the /source of the traffic/ independent of any<br=
>
intermediate node.<br>
</blockquote>
<br></div>
Are you prepared to make that a requirement of this document, i.e., that th=
e only MPLS traffic that can be UDP encapsulated is known to react to conge=
stion?<br>
<br>
How exactly can you know that?<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 The tunnel head-end is responsible for the tunnel walking, talking,=
<br>
=A0 =A0 and quaking like a duck (host). When the tunnel head-end knows<br>
=A0 =A0 something about the ultimate origin of the traffic - whether real,<=
br>
=A0 =A0 imagined, or from Asgard - then it has done it&#39;s duty (e.g., th=
at<br>
=A0 =A0 it&#39;s already congestion controlled).<br>
<br>
=A0 =A0 But that head end is responsible, regardless of what it knows or<br=
>
=A0 =A0 doesn&#39;t. And when it doesn&#39;t know, the only way to be respo=
nsible is<br>
=A0 =A0 to put in its own reactivity.<br>
<br>
This is not fact; it&#39;s actually precisely the principle =A0we&#39;re cu=
rrently<br>
arguing about. =A0;)<br>
</blockquote>
<br></div>
Actually, it&#39;s a paraphrasing of Section 3.1.3 of RFC5405.<br>
<br>
We can continue to debate it, but until it&#39;s been *changed* by a revisi=
on, it remains BCP.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I would posit:<br>
<br>
The tunnel doesn&#39;t have to know anything about congestion or performanc=
e<br>
characteristics because the originating application must.<br>
</blockquote>
<br></div>
That works only if you know that fact about the originating application. Ho=
wever, there are plenty of applications whose traffic goes over MPLS that i=
sn&#39;t congestion reactive or bandwidth-limited.<div><br>

<br>
&gt; See GRE,<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
MPLS, many other tunnel types,<br>
</blockquote>
<br></div>
This isn&#39;t an issue for all tunnels until they enter the Internet...<di=
v><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
including several existing within the<br>
IETF that make use of an outer UDP header.<br>
</blockquote>
<br></div>
Which are all already supposed to follow the recommendations of RFC5405. To=
 the extent that they don&#39;t, they don&#39;t agree with that BCP.<br>
<br>
I&#39;m not saying such things never can or will exist, but I don&#39;t thi=
nk the IETF should be self-contradictory. We already agreed as a group on s=
uch BCPs and other standards, and new standards-track docs need to follow t=
hem.<div>


<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0 The originating application<br>
=A0 =A0 =A0 =A0 who&#39;s traffic is being tunneled should be responsible f=
or congestion<br>
=A0 =A0 =A0 =A0 control, or lack there of.<br>
<br>
=A0 =A0 Perhaps it should be, but that&#39;s an agreement between whomever<=
br>
=A0 =A0 implements/deploys the tunnel headend and whomever provides the<br>
=A0 =A0 originating traffic to them. The problem is that this isn&#39;t tru=
e for<br>
=A0 =A0 the typical use case for this kind of encapsulation.<br>
<br>
How so? =A0As mentioned before, this is the same case as standard GRE/MPLS<=
br>
etc.<br>
</blockquote>
<br></div>
It&#39;s putting MPLS inside UDP. That&#39;s a different case, and the reas=
on RFC5405 applies.<div><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 I.e., if we were talking about MPLS traffic that already was<br>
=A0 =A0 reactive, we wouldn&#39;t be claiming the need for additional<br>
=A0 =A0 encapsulator mechanism. It&#39;s precisely because nothing is known=
<br>
=A0 =A0 about the MPLS traffic that the encapsulator needs to act.<br>
<br>
The MPLS traffic doesn&#39;t have to be reactive, it&#39;s the applications=
<br>
being encapsulated / traversing a particular tunnel that are responsible<br=
>
for and aware of path and congestion charateristics. =A0Because the MPLS<br=
>
head end knows nothing about the /end to end application &#39;session&#39;/=
<br>
characteristics it /shouldn&#39;t/ have anything to do with congestion<br>
management.<br>
</blockquote>
<br></div>
OK, so what you&#39;re saying is that &quot;traffic using this encapsulatio=
n MUST be known to be congestion reactive&quot;. Put that in the doc and we=
&#39;ll debate whether we believe it.<br>
<br>
But right now you&#39;re basically saying that because you think it&#39;s s=
omeone else&#39;s problem (the originating application), it isn&#39;t yours=
. The difficulty with that logic is that you (the tunnel headend) is respon=
sible to ensure that this is true - either by *knowing* that the originatin=
g traffic is congestion reactive, or by putting in its own mechanism to ens=
ure that this happens if the originating application isn&#39;t.<div>


<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0&gt; Are we advocating a return to intermediate<br>
<br>
=A0 =A0 =A0 =A0 congestion control (I like X.25 as much as the next guy,<br=
>
=A0 =A0 =A0 =A0 but...). =A0This<br>
=A0 =A0 =A0 =A0 is a very stark change of direction.<br>
<br>
=A0 =A0 =A0 =A0 I think mandating congestion control =A0is not technically =
sound from<br>
=A0 =A0 =A0 =A0 either a theoretical (violation of end to end principle, st=
acking of<br>
=A0 =A0 =A0 =A0 congestion control algorithms leading to complex and potent=
ially<br>
=A0 =A0 =A0 =A0 suboptimal results) or economic perspective (as a very larg=
e<br>
=A0 =A0 =A0 =A0 backbone,<br>
=A0 =A0 =A0 =A0 we&#39;ve been doing just fine without intermediate congest=
ion<br>
=A0 =A0 =A0 =A0 management<br>
=A0 =A0 =A0 =A0 thank you very much, and I have 0 desire to pay for a cost<=
br>
=A0 =A0 =A0 =A0 prohibitive,<br>
=A0 =A0 =A0 =A0 unnecessary feature in silicon.)<br>
<br>
=A0 =A0 Write that up, and we&#39;ll see how it turns out in the IETF. Howe=
ver,<br>
=A0 =A0 right now, the IETF BCPs do require reactive congestion management<=
br>
=A0 =A0 of transport streams.<br>
<br>
Which part? =A0The end-to-end principle, or the aversion to congestion<br>
control stacking? =A0These have been implicit in all tunneling protocols<br=
>
produced by the IETF for the modern internet.<br>
</blockquote>
<br></div>
Sure, and that&#39;s reflected in RFC5405 already. However, please, PLEASE =
appreciate that NOBODY here is asking you to put in &quot;congestion contro=
l stacking&quot;; that happens when you run two dynamic, reactive control a=
lgorithms using the same timescale on top of each other.<br>



<br>
Equally well-known in CC circles is that you CAN - and often *should* - sta=
ck different kinds of mechanisms at different layers with different timesca=
les. E.g., that&#39;s why we have an AQM WG - because even when all the tra=
ffic is TCP, that&#39;s not quite enough inside the network. That&#39;s als=
o why Lars was suggesting something coarse on a longer timescale - a circui=
t breaker - rather than AIMD on a RTT basis.<br>



<br>
Keep in mind as well that the E2E argument says that you can&#39;t get an E=
2E service by composing the equivalent HBH one; it also says that HBH mecha=
nisms can be required for efficiency. That&#39;s what we&#39;re talking abo=
ut here - the efficiency impact of congestion, not the overall correctness =
of E2E control.<div>


<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 If you don&#39;t want/like that, then either don&#39;t use transpor=
t<br>
=A0 =A0 encapsulation, or change the BCPs.<br>
<br>
These BCPs are defined for an originating /application/.<br>
</blockquote>
<br></div>
Yes, and I don&#39;t understand why you (and others) keep thinking it matte=
rs that there are layers of things behind the tunnel head end. It doesn&#39=
;t - unless you KNOW what those layers are, and can ensure that they behave=
 as you expect.<div>


<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In this case<br>
the UDP header is simply a shim header applied to existing application<br>
traffic.<br>
</blockquote>
<br></div>
It&#39;s not &quot;simply a shim&quot; - if that&#39;s the case, use IP and=
 we&#39;re done. No need for congestion control.<br>
<br>
The reason congestion issues arise is because you&#39;re inserting a header=
 ****THAT YOU EXPECT PARTS OF THE INTERNET YOU TRAVERSE TO REACT TO****.<br=
>
<br>
If you put in a UDP-like header that nobody in the Internet would interpret=
, this wouldn&#39;t be an issue.<br>
<br>
But you simply cannot expect the Internet to treat you like &quot;applicati=
on&quot; traffic if you won&#39;t enforce acting like that traffic too.<div=
><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The tunnel head does not introduce traffic independent of the<br>
originating application.<br>
</blockquote>
<br></div>
The Internet ****neither knows nor cares****.<br>
<br>
To the Internet, the head-end is the source. Whatever data the head end put=
s inside the UDP packets *is application data* to the rest of the Internet.=
<br>
<br>
Again, if you are saying that you know so much about the originating source=
 that you know you don&#39;t need additional mechanism at the headend, say =
so - but then live by that requirement.<br>
<br>
If *any* MPLS traffic could show up at the headend, then it becomes the hea=
dend&#39;s responsibility to do something.<br>
<br>
---<br>
<br>
Consider the following case:<br>
<br>
=A0 =A0 =A0 =A0 - video shows up inside the OS, destined for the network<br=
>
<br>
=A0 =A0 =A0 =A0 - software X bundles that video and sends it to go out<br>
<br>
=A0 =A0 =A0 =A0 - software Y puts that data into UDP packets to go<br>
=A0 =A0 =A0 =A0 to the Internet<br>
<br>
So what&#39;s the &quot;application&quot; here? To the Internet, it&#39;s s=
oftware Y -- the thing that puts the &#39;application&#39; data into UDP pa=
ckets. The previous steps are irrelevant - just as irrelevant as the singer=
 your video camera is filming, as irrelevant as the sun that created the li=
ght that is reflected off the singer to your camera.<br>



<br>
If software Y knows so much about the steps that lead to its input data tha=
t it knows it&#39;s congestion reactive, nothing more need be done.<br>
<br>
If NOT (and that&#39;s the relevant corollary here), then it becomes softwa=
re Y&#39;s responsibility to put in some reactivity.<span><font color=3D"#8=
88888"><br>
<br>
Joe<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--f46d043c7fc0769e9404f0ac2aea--

From tom.taylor.stds@gmail.com  Fri Jan 24 03:43:06 2014
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8171A02BA; Fri, 24 Jan 2014 03:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hX5zss1eSBuE; Fri, 24 Jan 2014 03:43:05 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 9C9E51A02B8; Fri, 24 Jan 2014 03:43:04 -0800 (PST)
Received: by mail-ig0-f172.google.com with SMTP id k19so2310217igc.5 for <multiple recipients>; Fri, 24 Jan 2014 03:43:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=zsOpZiK7mukcXr3NGnkXrUrPoTHHYxs6TNYhP7Zsf9g=; b=s4zGC6erGq/hNFbxT5NKOssShTI+nZxg3bRXc10fdcxySn21NyexcgEFVEp+7xzPGR 4ZwFTgUCGgayDsE/UVGAgaWp8oet9vhJ67/T5+eiYwA/MiJ7jYuKizU+zZeZWc1fUHkk IoZfsAEmyij4aYPdC2G91CnYHT6xDHHnydIbX5IaIWdkFsBZbvE9YsQBeYBqVj0QoeSI 3lVR8C9pN0ZdvB2xmuyyDXjhPVzSuPWlUIAgMvf0IqbaRgk7R+eZd+s4gOYppgM1C1WQ bWV3oROhkNlnX4BaOu3mQ1erEPDygniiT/b574Sy63iWaXLsCzzZuvyxeBS2U4S0dOxn RDzA==
X-Received: by 10.43.19.66 with SMTP id qj2mr10191883icb.31.1390563783443; Fri, 24 Jan 2014 03:43:03 -0800 (PST)
Received: from [192.168.1.69] ([64.56.225.169]) by mx.google.com with ESMTPSA id f15sm7917128igd.3.2014.01.24.03.43.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 03:43:02 -0800 (PST)
Message-ID: <52E251C2.7060009@gmail.com>
Date: Fri, 24 Jan 2014 06:42:58 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>, Pete Resnick <presnick@qualcomm.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 24 Jan 2014 08:05:43 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 11:43:06 -0000

Couldn't sleep last night as often happens because of the medication I'm 
on. So how about this medication-inspired effort, starting with Scott's 
summation:

"BCP79 provides authoritative rules regarding your obligations to 
disclose IPR when participating in the activities of the IETF, and 
should be referred to when the issue arises. The following summary is 
not totally accurate but provides a brief reminder.

General rule: if you make a contribution to IETF discussion, and you 
know or have reason to believe (without making a search) that you or 
your employer or sponsor owns IPR that has a high probability of being 
infringed by implementations based on that contribution, you or your 
employer must disclose that IPR in timely fashion.

Secondly, if you know or have reason to believe (without making a 
search) that implementations of the content of an IETF discussion in 
which you have not yet participated have a high probability of 
infringing on IPR owned by you or your employer then you must either
  -- not participate in the discussion, or
  -- participate and disclose in accordance with the general rule.

Finally, if you are aware of third party IPR in a contribution to the 
IETF, you are encouraged to send an email message to ietf-ipr@ietf.org 
as soon as reasonable disclosing that information."

On 23/01/2014 12:58 PM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
> 	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
> 	    that involve that contribution, then you must disclose
> 	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
> 	    that involve that contribution, then you are requested to disclose
>
> see - its not that hard to say this briefly
>
> Scott
>
...

From fluffy@cisco.com  Fri Jan 24 08:31:43 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27C301A0023; Fri, 24 Jan 2014 08:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWWvQMyeDZT5; Fri, 24 Jan 2014 08:31:41 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id DBAEF1A0010; Fri, 24 Jan 2014 08:31:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2439; q=dns/txt; s=iport; t=1390581100; x=1391790700; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=rN4LpuVoSbVP6WJxFtEb2G9V3JZwKDLui4qaxJhqmiY=; b=LtmV1riqWUE74H23TziWseRKvmaiLEXAXLC8kCsO8d7oVDa8JloHV/pH btrA7lBN1xUifskdTW1KLOUfyhpratNgJnTG/o37XGjdbDDvEBe+WNmd5 PloLZE2gB+MFruWn5YzwxCF5c5P0k2WN+tA6a+a38aGxO395e1DuLEjtP Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah8FAKGU4lKtJXHB/2dsb2JhbABZAYMMgQ6ISLNtgQwWdIIlAQEBAwF5BQsCAQgOChkBARMhERQRAgQOBYdxAwkIwlkNhVYXjHaBNBEBHTMHIwQBgnyBFASJEI0rgWyMXYVBgy2BcTk
X-IronPort-AV: E=Sophos;i="4.95,713,1384300800"; d="scan'208";a="15299105"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-6.cisco.com with ESMTP; 24 Jan 2014 16:31:39 +0000
Received: from xhc-aln-x08.cisco.com (xhc-aln-x08.cisco.com [173.36.12.82]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0OGVd8r028626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Jan 2014 16:31:39 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-aln-x08.cisco.com ([173.36.12.82]) with mapi id 14.03.0123.003; Fri, 24 Jan 2014 10:31:39 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGSHBHRiLKTI0hE2ZsfFwjVVpSg==
Date: Fri, 24 Jan 2014 16:31:38 +0000
Message-ID: <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com>
In-Reply-To: <52E251C2.7060009@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <490E46E22E7D7341816AF343C73C01B1@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, Tom Taylor <tom.taylor.stds@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 16:31:43 -0000

Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP. =20

Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?



On Jan 24, 2014, at 4:42 AM, Tom Taylor <tom.taylor.stds@gmail.com> wrote:

> Couldn't sleep last night as often happens because of the medication I'm =
on. So how about this medication-inspired effort, starting with Scott's sum=
mation:
>=20
> "BCP79 provides authoritative rules regarding your obligations to disclos=
e IPR when participating in the activities of the IETF, and should be refer=
red to when the issue arises. The following summary is not totally accurate=
 but provides a brief reminder.
>=20
> General rule: if you make a contribution to IETF discussion, and you know=
 or have reason to believe (without making a search) that you or your emplo=
yer or sponsor owns IPR that has a high probability of being infringed by i=
mplementations based on that contribution, you or your employer must disclo=
se that IPR in timely fashion.
>=20
> Secondly, if you know or have reason to believe (without making a search)=
 that implementations of the content of an IETF discussion in which you hav=
e not yet participated have a high probability of infringing on IPR owned b=
y you or your employer then you must either
> -- not participate in the discussion, or
> -- participate and disclose in accordance with the general rule.
>=20
> Finally, if you are aware of third party IPR in a contribution to the IET=
F, you are encouraged to send an email message to ietf-ipr@ietf.org as soon=
 as reasonable disclosing that information."
>=20
> On 23/01/2014 12:58 PM, Bradner, Scott wrote:
>> the actual rules are
>> 	1/ if you know of any of your IPR in a contribution you make, you must =
disclose
>> 	2/ if you know of any of your IPR in any contribution from someone else=
 and you are participating in discussions
>> 	    that involve that contribution, then you must disclose
>> 	3/ if you know of any of your IPR in any contribution from someone else=
 and you are not participating in discussions
>> 	    that involve that contribution, then you are requested to disclose
>>=20
>> see - its not that hard to say this briefly
>>=20
>> Scott
>>=20
> ...


From stbryant@cisco.com  Fri Jan 24 10:04:59 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 732261A0040; Fri, 24 Jan 2014 10:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3r0WeC_ELcZh; Fri, 24 Jan 2014 10:04:57 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 691091A003B; Fri, 24 Jan 2014 10:04:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5743; q=dns/txt; s=iport; t=1390586695; x=1391796295; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=38Pz967vdvkDhMGfnp2j9WEtHzW/xJWBdxFgrAvQajI=; b=FkWN2GAhM1dmD6cX5qS9xQiCIy1OO2kbZBPALYkb/r+W5y2wGaGh157G h+hBiHB4DuGPKoyK5xqpyQJZT+LJIRY8IZxclF0kI42AFUBnLqJJc2+1/ z4J60+JjWLXjcESemShIr9oYGBtMBS5iRvLCrnFsI8Fd86e59G8Unnzxb s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiAFAAmr4lKQ/khM/2dsb2JhbABaDoI6RDi9C4ENFnSCJQEBAQQtSwEQCxgJFgQLCQMCAQIBRQYBDAEHAQGIAQ3INxMEjioRAVAHhDgEmCeSHoFvfz+BcQ
X-IronPort-AV: E=Sophos;i="4.95,714,1384300800"; d="scan'208,217";a="3473128"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 24 Jan 2014 18:04:54 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0OI4r35000313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Jan 2014 18:04:53 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0OI4one006108; Fri, 24 Jan 2014 18:04:51 GMT
Message-ID: <52E2AB42.8060206@cisco.com>
Date: Fri, 24 Jan 2014 18:04:50 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>, Edward Crabbe <edc@google.com>, Joe Touch <touch@isi.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
In-Reply-To: <e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------060005050208040809040604"
Cc: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 18:04:59 -0000

This is a multi-part message in MIME format.
--------------060005050208040809040604
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 24/01/2014 15:01, John E Drake wrote:
>
> Ed,
>
> I completely agree with your email, below.  As an aside, the L2 
> packets that Lars is worried about are transported over a pseudo-wire 
> using MPLS, so the logical place to place congestion awareness is in 
> the pseudo-wire endpoints.  I remember that this was in the PWE3's 
> charter some time ago.
>
> Yours Irrespectively,
>
> John
>
The charter says:

Whilst a service provider may traffic engineer their network
in such a way that PW traffic will not cause significant
congestion, a PW deployed by an end-user may cause
congestion of the underlying PSN. Suitable congestion
avoidance mechanisms are therefore needed to protect the
Internet from the unconstrained deployment of PWs. Congestion
avoidance may be more difficult with P2MP pseudowires than
P2P pseudowires. The WG will consider both cases.

https://datatracker.ietf.org/doc/draft-stein-pwe3-congcons/
has expired, but if you are interested in working on the subject
I am sure the authors would be delighted to talk to you.

Stewart

--------------060005050208040809040604
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 24/01/2014 15:01, John E Drake
      wrote:<br>
    </div>
    <blockquote
cite="mid:e807421cc9fb4d98a46dce129aa39c82@BLUPR05MB562.namprd05.prod.outlook.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@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="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ed,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">I
            completely agree with your email, below.&nbsp; As an aside, the
            L2 packets that Lars is worried about are transported over a
            pseudo-wire using MPLS, so the logical place to place
            congestion awareness is in the pseudo-wire endpoints.&nbsp; I
            remember that this was in the PWE3&#8217;s charter some time ago.
            <o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours
            Irrespectively,<o:p></o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p>
      </div>
    </blockquote>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    The charter says:<br>
    <br>
    Whilst a service provider may traffic engineer their network<br>
    in such a way that PW traffic will not cause significant<br>
    congestion, a PW deployed by an end-user may cause<br>
    congestion of the underlying PSN. Suitable congestion<br>
    avoidance mechanisms are therefore needed to protect the<br>
    Internet from the unconstrained deployment of PWs. Congestion <br>
    avoidance may be more difficult with P2MP pseudowires than<br>
    P2P pseudowires. The WG will consider both cases.<br>
    <br>
    <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-stein-pwe3-congcons/">https://datatracker.ietf.org/doc/draft-stein-pwe3-congcons/</a> <br>
    has expired, but if you are interested in working on the subject<br>
    I am sure the authors would be delighted to talk to you.<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------060005050208040809040604--

From touch@isi.edu  Fri Jan 24 10:51:26 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7EC1A00F4; Fri, 24 Jan 2014 10:51:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1HpRDKyP-F1j; Fri, 24 Jan 2014 10:51:24 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id F31231A00F7; Fri, 24 Jan 2014 10:51:22 -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 s0OIoSFs019424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Jan 2014 10:50:31 -0800 (PST)
Message-ID: <52E2B5F4.8050008@isi.edu>
Date: Fri, 24 Jan 2014 10:50:28 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Edward Crabbe <edc@google.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <52E1D093.8040603@joelhalpern.com>
In-Reply-To: <52E1D093.8040603@joelhalpern.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: "mpls@ietf.org" <mpls@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 18:51:26 -0000

On 1/23/2014 6:31 PM, Joel M. Halpern wrote:
> Joe, while your argument is internally consistent, it is not consistent
> with history.

That's also why we're not exchanging email over X.25. We learn and move on.

However, the fact that tunnel heads ought to act like hosts is an issue 
I've been raising in the IETF for over 15 years, and was the primary 
reason why I argued for transport mode support in routers for tunneling 
(see RFC 3884).

> We have not demanded that tunnel entries behave fully
> like source hosts for any of the other myriad kinds of tunnels we have
> done over the years.

That has been a continual mistake, one that a group was formed in 2005 
to address, which resulted in an INTAREA document on this:

http://tools.ietf.org/html/draft-touch-intarea-tunnels-01

That doc has been fallow for a while largely because the problem and its 
complexity hasn't been fully appreciated. We're hoping to correct that 
and revive it, FWIW.

> If we take your logic as stated, then the usage of IPSec over UDP would
> be required to apply congestion control unless it knew that all the
> content traffic was TCP.  Is that really your intent?

Yes, and that's already what RFC 5405 says. The fact that IPsec-UDP 
encap doesn't address this is because RFC 3948 predates RFC 5405.

This document (mpls-in-udp) does not, however.

Joe

> Yours,
> Joel
>
> On 1/23/14 4:38 PM, Joe Touch wrote:
>>
>>
>> On 1/23/2014 1:27 PM, Edward Crabbe wrote:
>>> Part of the point of using UDP is to make use of lowest common
>>> denominator forwarding hardware in introducing entropy to protocols that
>>> lack it ( this is particularly true of the GRE in UDP use case also
>>> under discussion elsewhere).
>>>
>>> The tunnel is not the source of the traffic.  The _source of the
>>> traffic_ is the source of the traffic.
>>
>> To the Internet, the tunnel encapusulator is the source of traffic.
>> Tracing the data back further than that is a mirage at best - and
>> irrelevant.
>>
>> The tunnel head-end is responsible for the tunnel walking, talking, and
>> quaking like a duck (host). When the tunnel head-end knows something
>> about the ultimate origin of the traffic - whether real, imagined, or
>> from Asgard - then it has done it's duty (e.g., that it's already
>> congestion controlled).
>>
>> But that head end is responsible, regardless of what it knows or
>> doesn't. And when it doesn't know, the only way to be responsible is to
>> put in its own reactivity.
>>
>>> The originating application
>>> who's traffic is being tunneled should be responsible for congestion
>>> control, or lack there of.
>>
>> Perhaps it should be, but that's an agreement between whomever
>> implements/deploys the tunnel headend and whomever provides the
>> originating traffic to them. The problem is that this isn't true for the
>> typical use case for this kind of encapsulation.
>>
>> I.e., if we were talking about MPLS traffic that already was reactive,
>> we wouldn't be claiming the need for additional encapsulator mechanism.
>> It's precisely because nothing is known about the MPLS traffic that the
>> encapsulator needs to act.
>>
>>  > Are we advocating a return to intermediate
>>> congestion control (I like X.25 as much as the next guy, but...).  This
>>> is a very stark change of direction.
>>>
>>> I think mandating congestion control  is not technically sound from
>>> either a theoretical (violation of end to end principle, stacking of
>>> congestion control algorithms leading to complex and potentially
>>> suboptimal results) or economic perspective (as a very large backbone,
>>> we've been doing just fine without intermediate congestion management
>>> thank you very much, and I have 0 desire to pay for a cost prohibitive,
>>> unnecessary feature in silicon.)
>>
>> Write that up, and we'll see how it turns out in the IETF. However,
>> right now, the IETF BCPs do require reactive congestion management of
>> transport streams.
>>
>> If you don't want/like that, then either don't use transport
>> encapsulation, or change the BCPs.
>>
>>> I get Lars comments regarding reach, to some limited extent.
>>>   Ultimately, the implication seems to be that the protocols riding the
>>> L2 network will have no form of congestion control and are fundamentally
>>> different than protocols that would reside on a typical wan.  I have
>>> some serious doubts about this, although I'm sure this is the case in
>>> some specialized environments.  At any rate, it seems to me that a stern
>>> warning regarding edge filtering on interdomain boundaries will be
>>> sufficient.
>>
>> My concern may be slightly different that his. My concern is that you
>> want the benefits of a UDP header, but don't like the responsibilities
>> that come along with it.
>>
>> Joe
>>
>>

From derhoermi@gmx.net  Fri Jan 24 11:07:25 2014
Return-Path: <derhoermi@gmx.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7341A014F for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 11:07:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YeMegGTcjG8e for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 11:07:23 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 26E141A00F4 for <ietf@ietf.org>; Fri, 24 Jan 2014 11:07:22 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.13.92]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MPUFR-1WBQne3I3d-004mmK for <ietf@ietf.org>; Fri, 24 Jan 2014 20:07:20 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Date: Fri, 24 Jan 2014 20:07:24 +0100
Message-ID: <tde5e99k0mdgumopticvk79tg6ghu1drfv@hive.bjoern.hoehrmann.de>
References: <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
In-Reply-To: <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.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-Provags-ID: V03:K0:afFmRJXqghgn6N7j17fITmuRLBAJSrp2b4R/fyUE5PpZxGXn0MM HsU289ua4YdiPsrsfdrsYrQeuDv/ASLvuGMsiibOPU2RMHNeRDhec3tF5l58Vry6Aku0wKA ipbNbsYFEdKopProlRtaq8IG9u9L1FzjgUbgdFT04t0hx1Nq1nptYhnL694OnwGpxivttRh mNftIzX+aBq/NFnuHlWHg==
Cc: Pete Resnick <presnick@qualcomm.com>, Tom Taylor <tom.taylor.stds@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 19:07:25 -0000

* Cullen Jennings (fluffy) wrote:
>Pete, I really think it is that putting a sentences in it that is 
>clearly false is just wrong and I can not understand why you are arguing 
>for that?

(Me too.)
-- 
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 touch@isi.edu  Fri Jan 24 11:16:36 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D5B51A017C; Fri, 24 Jan 2014 11:16:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.235
X-Spam-Level: 
X-Spam-Status: No, score=-4.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_ABOUTYOU=0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0sSaa6_DS5SQ; Fri, 24 Jan 2014 11:16:30 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id F1CB51A0175; Fri, 24 Jan 2014 11:16:13 -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 s0OJFCsn023069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 24 Jan 2014 11:15:13 -0800 (PST)
Message-ID: <52E2BBC0.2030203@isi.edu>
Date: Fri, 24 Jan 2014 11:15:12 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 19:16:36 -0000

On 1/23/2014 7:20 PM, Curtis Villamizar wrote:
...
> Joe,
>
> I agree with you that the word SHOULD is not an automatic pass and
> quoted from RFC 2119 because I think that on this thread the criteria
> "valid reasons in particular circumstances" and "implications
> ... carefully weighed" have both been met.
>
> Perhaps you joined the discussion a little late.
>
> Please allow me to recap.  There are two issues under discussion, UDP
> checksums and congestion control.
>
> All parties seem to be OK with limiting the use of MPLS over UDP to
> service providers only within their own infrastructure only, except
> among cooperating service providers with explicit agreement
> (consenting adults).
>
> Within that context, some service providers find that parts of their
> infrastructure either doesn't support MPLS at all or doesn't support a
> usable variation of multipath for MPLS but does support IP ECMP (as I
> understand it, this is primarily in the fringes, access and less so
> edge - but someone who knows for sure please correct me if not).
>
> This eliminates the "expands the reach of MPLS argument".
>
> First UDP checksums:
>
>    The UDP checksum is at the beginning of the payload.  Please see
>    http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>    This makes filling in a new UDP checksum infeasible on most high end
>    hardware.

That argument would make sense if most hardware wasn't store-and-forward 
on a per-packet basis.

>    Within all of that context, all of the links have at least 32 bit
>    FCS (either Ethernet framing or SONET or OTN) and some has much
>    better such as the FEC found in OTN.  This makes undetected
>    corruption by any of the links extremely unlikely.
>
>    Corruption internal to the router the only potential impact.  There
>    is good reason to think that this is extremely rare.

I don't buy the argument that per-hop checksums replace the need for 
end-to-end checksums; that's part of why more modern tunneling systems 
(e.g., SEAL) include their own head-to-tail checksum. So while I agree 
that UDP checksums may not be strong enough here, that might be an 
argument for a better tunneling mechanism than raw MPLS in IP, rather 
than ditching UDP checksums.

>    Infeasibility of doing UDP checksums in some instances (not just
>    performance concerns) is sufficient to make use of UDP checksums a
>    SHOULD.

Your argument hinges on feasibility, but that doesn't hold water (esp. 
given I've designed hardware that does Internet checksums - including 
some recent all-optical designs).

> On to congestion control:
>
>    Some MPLS payloads such as IP over MPLS have congestion control.
>    While it can't be assured that all IP traffic makes use of
>    congestion control, the problem is in the UDP services carried over
>    MPLS regardless of whether MPLS over UDP is used.

That is the key problem. As you point out below, other traffic is 
somewhat 'noise' on the overall equation.

>    The only other type of traffic carried by MPLS in any volume (not
>    counting ISIS control traffic carried as CLNP over MPLS, for
>    example) is PW.
>
>      PW in turn supports Ethernet, FR, ATM, TDM, and maybe a few
>      others.  The vast majority of payload in Ethernet, FR, ATM, is IP
>      so were are back to the prior bullet.  It PW packlet carrying
>      Ethernet, FR, or ATM are dropped the congestion response is
>      virtually identical to IP because the payload is IP.
>
>      The other PW case is TDM.  TDM serves two purposes in SP networks.
>      A small number of legacy customers circuits, generally T1 or T3
>      use it.  These are 1.5 and 45 Mb/s services on 1 Gb/s and 10 Gb/s
>      links.  Hardly a source of congestion, plus they pay a lot more
>      and therefore are priority traffic.  Another is 3G mobile
>      backhaul.  Again this is T1 or T3, but maybe as much as small
>      multiples of T3.  Still very low capacity.

You can't know whether the PW cases you expect will change over time, or 
are accurate as per above. I would not be surprised if someone started 
(or is already) using PW to connect datacenters to exchange bulk data 
using non-CC protocols.

>    TCP-like congestion control in a tunnel is very bad for any TCP
>    carried within the tunnel.  The vast majority on MPLS traffic is IP
>    and therefore is TCP.

Yes, and that's why nobody is asking for that.

>    Regardless of the weak argument in favor of it given the operational
>    reality, the authors have conceded to state that "MPLS over UDP
>    SHOULD have congestion control" in the document.

OK (that matches RFC 5405).

>    Because in the scenario it is intended to be deploy congestion
>    control is very unlikely to prove to be needed,

That's pure speculation, and more importantly undermines the SHOULD 
you've just conceded.

> defining the exact
>    form of congestion control is deferred to a later document which
>    will be written only if needed.

That document is needed now, exactly because of the SHOULD. You can't 
make a SHOULD recommendation without backing it up with the detail 
needed to implement it.

Other wise, it's a MAY, or (more to the point), a (nonexistent) MIGHT 
SOMEDAY.

> That said, I have in the past argued that the "circuit breaker" form
> of congestion control would be one of the worst things we could
> possibly do.  It would be terrible for TCP and most anything else.

Maybe, but if so, then you need the head-end to employ that breaker only 
on non-CC traffic.

> See http://www.ietf.org/mail-archive/web/mpls/current/msg11262.html
> The right place to put any circuit breaker would be TDM over PW, but
> given the capacities involved, that is not really needed either.
>
> In the past I've said:
>
>    The technical sticky point is knowing that the congestion is
>    occuring.  Perhaps a LM like packet on another UDP port could be
>    exchanged with the same caveats about inaccuracy if implemented in
>    software and inaccuracy if reordering occurs, and a recommendation
>    can be made to do something to introduce drop if congestion is
>    indicated by this method.  How to introduce drop should be an
>    implementation detail, a form of AQM or leaky bucket being possible
>    choices, but entirely a local matter.
>
> MPLS LM OAM would be a good choice for detection of congestion (as
> evidenced by loss).  A leaky bucket (aka shaper) likely with AQM seems
> like a reasonable choice.  This could be put into another document if
> a need ever truly arises for congestion control in MPLS and it could
> be applied to MPLS over anything (though it could prove impractical
> for MPLS over avian carrier).

See above. MIGHT SOMEDAY isn't a reasonable solution to a problem for 
which the need for a solution is already conceded.

Joe

>
> Curtis
>
>
>> On 1/21/2014 12:58 PM, Curtis Villamizar wrote:
>>> Lars,
>>>
>>> The IETF consensus in RFC5405 was to put a SHOULD in regarding use of
>>> congestion control in tunneling protocols.
>>>
>>> RFC2119 states:
>>>
>>>     3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there
>>>        may exist valid reasons in particular circumstances to ignore a
>>>        particular item, but the full implications must be understood and
>>>        carefully weighed before choosing a different course.
>>>
>>> We have discussed the reasons why congestion control is in general a
>>> good thing.  We have also discussed why there may be valid reasons to
>>> not include congestion control in MPLS over UDP.
>>>
>>> The question is not whether there is already IETF consensus on
>>> congestion control in UDP in general.  There is consensus and that
>>> consensus was to use the word "SHOULD".
>>>
>>> The question we now face is whether MPLS in UDP needs to up the prior
>>> consensus to a MUST or can keep it as SHOULD.  I see one or maybe two
>>> people vigorously arguing to upgrade this to a MUST and otherwise
>>> consensus to keep this as SHOULD.  Further I see no objection except
>>> the same one or maybe two people to making the congestion control the
>>> topic of a later work if a need for it arises.  Consensus does not
>>> require unanimous agreeement.
>>>
>>> If we are trying to gauge consensus, maybe both you and I should sit
>>> back and let other people weigh in.
>>>
>>> Curtis
>>>
>>>
>>> In message <B36BA2A8-0C28-4B88-87BD-51A6F964F893@netapp.com>
>>> "Eggert, Lars" writes:
>>>>
>>>> Hi,
>>>>
>>>> On 2014-1-17, at 18:19, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
>>>>> You have made your assertions about your desire to uphold the purity
>>>>> of any new UDP applications and adhere to the BCP you wrote.
>>>>> =20
>>>>> You appear to be very nearly alone in this argument and certainly no
>>>>> one that works with MPLS is siding with you.
>>>>
>>>> the reason we wrote the RFC when I was TSV AD was that we were seeing a =
>>>> whole bunch of questionable uses of UDP over the eyars and we were =
>>>> having the same arguments over and over. That's why we decided to write =
>>>> down the practices we expect users of UDP to follow. This is yet another =
>>>> such questionable use.
>>>>
>>>> (Also, I don't appreciate you turning this into a personal argument.)
>>>
>>> Nothing personal intended.
>>>
>>> The important point is the sentence "You appear to be very nearly
>>> alone in this argument and certainly no one that works with MPLS is
>>> siding with you." was intended to point out that there is no consensus
>>> behind your argument regardless of how vigorously you make that
>>> argument.
>>>
>>>>> In the end we can put anything we want in the RFC *but* IETF has never
>>>>> truly had the final word on what vendors and operators do in provider
>>>>> networks.
>>>>
>>>> Aka the "take my toys and go home" argument. Heard it many times.
>>>
>>> It has been successful many times in the past.  It turns into the "its
>>> deployed so get over it" argument after a few years.
>>>
>>>>> In this case, regardless of what changes are made to the draft,
>>>>> implementations will offer at least the option for non-RFC behavior by
>>>>> using zero checksums and not using any congestion control.  And
>>>>> providers will make use of it, perhaps exclusively.
>>>>
>>>> And there's nothing wrong with that - the BCP even says that one SHOULD =
>>>> NOT use congestion control for some deployment cases.
>>>>
>>>> But for others, one SHOULD. For those, a mechanism needs to be =
>>>> available, i.e., it needs to be specified and implemented.
>>>>
>>>>> The document might as well reflect reality, despite reality not
>>>>> conforming to your notions of architectural purity.
>>>>
>>>> I'm sorry, but we have certain architectural principles in the Internet =
>>>> that we have IETF consensus on. At least since RFC2914, that includes =
>>>> the need to have congestion control in place.
>>>>
>>>> There are always special deployment scenarios where these principles do =
>>>> not apply, and we typically explain in applicability statements when out =
>>>> specifications can only be safely used under certain conditions. I don't =
>>>> see any such statement in draft-ietf-mpls-in-udp, which to me means it's =
>>>> targeted at general Internet-wide use.
>>>>
>>>>> The best course of action is to put a SHOULD in regarding checksums
>>>>> and put a SHOULD in regarding congestion avoidance.  Even the BCP does
>>>>> not go any further than to say a tunneling protocol SHOULD use
>>>>> congestion control and there were reasons that the word MUST was not
>>>>> acceptable in the BCP.
>>>>
>>>> The SHOULD for congestion control needs to actually describe a mechanism =
>>>> that can be used when needed. It can't be a blanket "you SHOULD use =
>>>> something but we don't tell you what it is"-statement.
>>>>
>>>>> If we are still arguing over two instances of SHOULD vs MUST we have
>>>>> wasted a lot of bandwidth on those two words.
>>>>
>>>> It's not SHOULD vs. MUST. It's two SHOULDs, but in both cases it needs =
>>>> to be specified what is to be done. In the case of checksums, that's =
>>>> obvious (calculate it and check it); in the case of congestion control, =
>>>> some actual mechanism needs to be described (e.g., a circuit breaker).
>>>>
>>>>> IMHO The only remaining question is whether the document can go =
>>>> forward
>>>>> with the definition of congestion control for MPLS over UDP left out
>>>>> of scope and for another document if a need arises.
>>>>
>>>> In my opinion, it cannot.
>>>>
>>>>> If this is not acceptable to you (I doubt it is) please indicate what
>>>>> you would like to see in the document and since this is IETF last call
>>>>> where consensus matters and no one individual has veto power, we'll
>>>>> have to see if there is consensus behind your proposed changes.
>>>>
>>>> I would like the document to specify at the very least a circuit breaker =
>>>> mechanism, that stops the tunneled traffic if severe packet loss is =
>>>> detected along the path.
>>>>
>>>> And this isn't about an "individual veto". This is about a document that =
>>>> is at the moment in violation of IETF consensus at least as far back as =
>>>> RFC2914.
>>>>
>>>> Lars

From presnick@qti.qualcomm.com  Fri Jan 24 12:24:24 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2A61A018E; Fri, 24 Jan 2014 12:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9Erk9040MQH; Fri, 24 Jan 2014 12:24:22 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id D6AE21A012D; Fri, 24 Jan 2014 12:24:22 -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=1390595062; x=1422131062; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=hFBkb9K6s9FXn4fZtGRtBDcQe2NkD4zqae/IRozthjw=; b=cfAePG9dXSbJATOAA4iGdT/vfLMIDGLQCO/Ev07XxTAf/4fpZoBTXWSf y08hl7J5WKBEuIvj6D0H9EdZo+8DmPJ7qW4qSoltkPYugyMV67xM1AZOi d8nN0/P89Ya2MSpxjl68B+P41nP00Ejx/jiA5IzrBdZLkM/9AMIg42QR5 o=;
X-IronPort-AV: E=McAfee;i="5400,1158,7328"; a="58608756"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 24 Jan 2014 12:24:22 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7328"; a="26130709"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Jan 2014 12:24:21 -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.3.158.1; Fri, 24 Jan 2014 12:24:20 -0800
Message-ID: <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 14:24:18 -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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
In-Reply-To: <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF WG Chairs <wgchairs@ietf.org>, Tom Taylor <tom.taylor.stds@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:24:24 -0000

On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
> Both Tom and Lars text would work for me. There seem to be so many ways to write it such that it is still brief but captures the key elements of the BCP.
>
> Pete, I really think it is that putting a sentences in it that is clearly false is just wrong and I can not understand why you are arguing for that?
>    

So here's the key for me (and maybe this means we have a separate Note 
Well for the room from the one on the web site):

In the room, I want something short enough that the chairs might 
actually be inclined to read out loud. It should have the three basic 
messages:

- By participating here, you've agreed to our rules.
- You can be recorded.
- You have to disclose your IPR.
Details on the above specified elsewhere. Go read if you're worried 
about it.

I want those statements extended as little as possible to keep it so 
that the chair might be willing to say it.

And (and this is probably the one where we might still disagree) if it's 
going to be inaccurate, and it will *have* to be inaccurate just by 
nature of being a summary, I want it to be inaccurate such that it 
includes *more* things to disclose than you are actually required to, 
not less. I don't want the excuse for not disclosing to be "I didn't 
understand all of the detail in BCP 79, but the Note Well sure didn't 
say that I had to disclose anything like *that*." If there's going to be 
an inaccuracy in the statement, I want it to be that BCP 79 says to 
disclose *less* than the summarized warning we give folks in the room.

Both Tom's and Lars's summaries are fine, but they're not reasonable 
things to read in the room.

We wrestled with this for a while. I'm open to suggestions. But the 
above are really my design criteria, at least for the one we put on a 
slide for the room.

pr

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


From hallam@gmail.com  Fri Jan 24 12:33:23 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04EC1A01C5 for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 12:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U7WfzJy9jMQf for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 12:33:20 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 329191A01B9 for <ietf@ietf.org>; Fri, 24 Jan 2014 12:33:20 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id p9so2871932lbv.20 for <ietf@ietf.org>; Fri, 24 Jan 2014 12:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=RNIEY0JQgipRWKnPwlf2Hk0ARrs93mlO71oWZ2/N65I=; b=VGfzKHxUm0S/ArqKtZ8Lv/cjTKyfdlUpv2+mZ+ai9iUopMUt8PnxLqSo1XyuILEks6 hDEM7H+jEcGO2LxpRIwqLVk7QsYcXGry9MtqCALPBai//axGOO98UjjV9zNzbc3vYrWg 8Gdp+heh/EtZNTIpt09EKiem7W6FE6u4W5haIYSzJxjk6on3j3MVe4U8dRdOB6qP0mm7 cFDGWT9DLYPMOOEWsfmOB1nVKtTbbIQIWyUjQi6zXkHweYijSzL6viWOnH1eKpfXi0uR c16a/5AeeDyhhRHN1DyUZpnKGmX4b1ZUkS/EtdiMVf81i6yFQt4dV4jUmtOhJkU9U2hb vI3Q==
MIME-Version: 1.0
X-Received: by 10.112.157.234 with SMTP id wp10mr1225980lbb.50.1390595598212;  Fri, 24 Jan 2014 12:33:18 -0800 (PST)
Received: by 10.112.37.172 with HTTP; Fri, 24 Jan 2014 12:33:18 -0800 (PST)
In-Reply-To: <CAMm+Lwh0JaVtNH6Xs9gMJNHUhRLvBbgzPoCNgwin79O3m7vYwA@mail.gmail.com>
References: <20140124175305.23709.87470.idtracker@ietfa.amsl.com> <CAMm+Lwh0JaVtNH6Xs9gMJNHUhRLvBbgzPoCNgwin79O3m7vYwA@mail.gmail.com>
Date: Fri, 24 Jan 2014 15:33:18 -0500
Message-ID: <CAMm+Lwj71Ah4rR49gWJiBvDQ_A_dJq+-Ms+UCpqJJPipWwvrSA@mail.gmail.com>
Subject: Re: [therightkey] WG Review: Public Notary Transparency (trans)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c26b12a861eb04f0bd4484
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:33:23 -0000

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

I support the creation of this WG.

I also prefer 'Transparent Public Notary'

Putting the adjective after the noun suggests that the emphasis is on
making notaries transparent rather than a new notary protocol that is
transparent.


On Fri, Jan 24, 2014 at 3:12 PM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> I support the creation of this WG.
>
> I also prefer 'Transparent Public Notary'
>
> Putting the adjective after the noun suggests that the emphasis is on
> making notaries transparent rather than a new notary protocol that is
> transparent.
>
>
>
> On Fri, Jan 24, 2014 at 12:53 PM, The IESG <iesg-secretary@ietf.org>wrote:
>
>> A new IETF working group has been proposed in the Security Area. The IESG
>> has not made any determination yet. The following draft charter was
>> submitted, and is provided for informational purposes only. Please send
>> your comments to the IESG mailing list (iesg at ietf.org) by 2014-02-03.
>>
>> Public Notary Transparency  (trans)
>> ------------------------------------------------
>> Current Status: Proposed WG
>>
>> Assigned Area Director:
>>   Stephen Farrell <stephen.farrell@cs.tcd.ie>
>>
>> Mailing list
>>   Address: therightkey@ietf.org
>>   To Subscribe: https://www.ietf.org/mailman/listinfo/therightkey
>>   Archive: http://www.ietf.org/mail-archive/web/therightkey/
>>
>> Charter:
>>
>> Mitigating web site certificate mis-issuance is the initial problem of
>> interest for this working group. Certificate Transparency (CT,
>> RFC6962) allows such mis-issuance to be detected in interesting and
>> useful cases, for example by an auditor acting for the web site, or
>> one acting to check general CA behaviour. The working group will
>> produce a standards-track version of the experimental RFC 6962
>> for HTTP over TLS, reflecting implementation and deployment
>> experience since that specification was completed.
>>
>> Many Internet protocols for example, SMTPS, IPsec, DNSSEC,
>> OpenPGP and HTTPS, require  a mapping between some kind of
>> identifier and some kind of public key. These protocols rely
>> on either ad-hoc mappings, (as in a web of trust), or on authorities
>> (such as CAs) that attest to the mappings. History shows that neither
>> of these mechanisms is entirely satisfactory.  Ad-hoc mappings are
>> difficult to discover and maintain, and authorities make mistakes or
>> are subverted.
>>
>> Cryptographically verifiable logs can help to ameliorate these
>> problems by making it possible to discover errors quickly, so that
>> other mechanisms can be applied to rectify them. A cryptographically
>> verifiable log is an append-only log of hashes of more-or-less anything
>> that  is structured in such a way as to provide efficiently-accessible,
>> cryptographically-supported evidence of correct log behaviour. For
>> example, RFC 6962 says: "The append-only property of each log is
>> technically achieved using Merkle Trees, which can be used to show
>> that any particular version of the log is a superset of any particular
>> previous version. Likewise, Merkle Trees avoid the need to blindly
>> trust logs: if a log attempts to show different things to different
>> people, this can be efficiently detected by comparing tree roots and
>> consistency proofs. Similarly, other misbehaviors of any log (e.g.,
>> issuing signed timestamps for certificates they then don't log) can be
>> efficiently detected and proved to the world at large."
>>
>> These logs can potentially also assist with other interesting
>> problems, such as how to assure end users that software they are
>> running is, indeed, the software they intend to run.
>>
>> While the privacy issues related to use of RFC6962 for public
>> web sites are minimal, the working group will consider privacy
>> as it might impact on uses of CT e.g. within enterprises or
>> for other uses of logs.
>>
>> Work items:
>>
>> - Publish an update to RFC 6962 as a standards-track mechanism to
>> apply verifiable logs to HTTP over TLS.  As DANE (RFC6698) provides an
>> alternative keying infrastructure to that used in the current web PKI,
>> the working group should consider appropriate client behavior in the
>> presence of both DANE-based keying and current web PKI when
>> standardising CT.
>>
>> - Discuss mechanisms and techniques that allow cryptographically
>> verifiable logs to be deployed to improve the security of protocols
>> other than HTTP over TLS, for example SMTP/TLS or software
>> distribution. Where such mechanisms appear sufficiently useful,
>> the WG will re-charter to add relevant new work items.  Should
>> no such items be chartered the WG will close when documents
>> associated with the first work item are complete.
>>
>>
>>
>> Milestones:
>>
>> TBD
>> _______________________________________________
>> therightkey mailing list
>> therightkey@ietf.org
>> https://www.ietf.org/mailman/listinfo/therightkey
>>
>
>
>
> --
> Website: http://hallambaker.com/
>



-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><span style=3D"font-family:arial,sans-serif;font-size:16px=
">I support the creation of this WG.</span><div style=3D"font-family:arial,=
sans-serif;font-size:16px"><br></div><div style=3D"font-family:arial,sans-s=
erif;font-size:16px">
I also prefer=A0&#39;Transparent Public Notary&#39;</div><div style=3D"font=
-family:arial,sans-serif;font-size:16px"><br></div><div style=3D"font-famil=
y:arial,sans-serif;font-size:16px">Putting the adjective after the noun sug=
gests that the emphasis is on making notaries transparent rather than a new=
 notary protocol that is transparent.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri,=
 Jan 24, 2014 at 3:12 PM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:hallam@gmail.com" target=3D"_blank">hallam@gmail.com</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">I support the creation of t=
his WG.<div><br></div><div>I also prefer=A0<span style=3D"font-family:arial=
,sans-serif;font-size:16px">&#39;Transparent Public Notary&#39;</span></div=
>
<div><span style=3D"font-family:arial,sans-serif;font-size:16px"><br>
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:16p=
x">Putting the adjective after the noun suggests that the emphasis is on ma=
king notaries transparent rather than a new notary protocol that is transpa=
rent.</span></div>

<div><span style=3D"font-family:arial,sans-serif;font-size:16px"><br></span=
></div></div><div class=3D"gmail_extra"><div><div class=3D"h5"><br><br><div=
 class=3D"gmail_quote">On Fri, Jan 24, 2014 at 12:53 PM, The IESG <span dir=
=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">i=
esg-secretary@ietf.org</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">A new IETF working group has been proposed i=
n the Security Area. The IESG<br>
has not made any determination yet. The following draft charter was<br>
submitted, and is provided for informational purposes only. Please send<br>
your comments to the IESG mailing list (iesg at <a href=3D"http://ietf.org"=
 target=3D"_blank">ietf.org</a>) by 2014-02-03.<br>
<br>
Public Notary Transparency =A0(trans)<br>
------------------------------------------------<br>
Current Status: Proposed WG<br>
<br>
Assigned Area Director:<br>
=A0 Stephen Farrell &lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=
=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;<br>
<br>
Mailing list<br>
=A0 Address: <a href=3D"mailto:therightkey@ietf.org" target=3D"_blank">ther=
ightkey@ietf.org</a><br>
=A0 To Subscribe: <a href=3D"https://www.ietf.org/mailman/listinfo/theright=
key" target=3D"_blank">https://www.ietf.org/mailman/listinfo/therightkey</a=
><br>
=A0 Archive: <a href=3D"http://www.ietf.org/mail-archive/web/therightkey/" =
target=3D"_blank">http://www.ietf.org/mail-archive/web/therightkey/</a><br>
<br>
Charter:<br>
<br>
Mitigating web site certificate mis-issuance is the initial problem of<br>
interest for this working group. Certificate Transparency (CT,<br>
RFC6962) allows such mis-issuance to be detected in interesting and<br>
useful cases, for example by an auditor acting for the web site, or<br>
one acting to check general CA behaviour. The working group will<br>
produce a standards-track version of the experimental RFC 6962<br>
for HTTP over TLS, reflecting implementation and deployment<br>
experience since that specification was completed.<br>
<br>
Many Internet protocols for example, SMTPS, IPsec, DNSSEC,<br>
OpenPGP and HTTPS, require =A0a mapping between some kind of<br>
identifier and some kind of public key. These protocols rely<br>
on either ad-hoc mappings, (as in a web of trust), or on authorities<br>
(such as CAs) that attest to the mappings. History shows that neither<br>
of these mechanisms is entirely satisfactory. =A0Ad-hoc mappings are<br>
difficult to discover and maintain, and authorities make mistakes or<br>
are subverted.<br>
<br>
Cryptographically verifiable logs can help to ameliorate these<br>
problems by making it possible to discover errors quickly, so that<br>
other mechanisms can be applied to rectify them. A cryptographically<br>
verifiable log is an append-only log of hashes of more-or-less anything<br>
that =A0is structured in such a way as to provide efficiently-accessible,<b=
r>
cryptographically-supported evidence of correct log behaviour. For<br>
example, RFC 6962 says: &quot;The append-only property of each log is<br>
technically achieved using Merkle Trees, which can be used to show<br>
that any particular version of the log is a superset of any particular<br>
previous version. Likewise, Merkle Trees avoid the need to blindly<br>
trust logs: if a log attempts to show different things to different<br>
people, this can be efficiently detected by comparing tree roots and<br>
consistency proofs. Similarly, other misbehaviors of any log (e.g.,<br>
issuing signed timestamps for certificates they then don&#39;t log) can be<=
br>
efficiently detected and proved to the world at large.&quot;<br>
<br>
These logs can potentially also assist with other interesting<br>
problems, such as how to assure end users that software they are<br>
running is, indeed, the software they intend to run.<br>
<br>
While the privacy issues related to use of RFC6962 for public<br>
web sites are minimal, the working group will consider privacy<br>
as it might impact on uses of CT e.g. within enterprises or<br>
for other uses of logs.<br>
<br>
Work items:<br>
<br>
- Publish an update to RFC 6962 as a standards-track mechanism to<br>
apply verifiable logs to HTTP over TLS. =A0As DANE (RFC6698) provides an<br=
>
alternative keying infrastructure to that used in the current web PKI,<br>
the working group should consider appropriate client behavior in the<br>
presence of both DANE-based keying and current web PKI when<br>
standardising CT.<br>
<br>
- Discuss mechanisms and techniques that allow cryptographically<br>
verifiable logs to be deployed to improve the security of protocols<br>
other than HTTP over TLS, for example SMTP/TLS or software<br>
distribution. Where such mechanisms appear sufficiently useful,<br>
the WG will re-charter to add relevant new work items. =A0Should<br>
no such items be chartered the WG will close when documents<br>
associated with the first work item are complete.<br>
<br>
<br>
<br>
Milestones:<br>
<br>
TBD<br>
_______________________________________________<br>
therightkey mailing list<br>
<a href=3D"mailto:therightkey@ietf.org" target=3D"_blank">therightkey@ietf.=
org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/therightkey" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/therightkey</a><br>
</blockquote></div><br><br clear=3D"all"><div><br></div></div></div><span c=
lass=3D"HOEnZb"><font color=3D"#888888">-- <br>Website: <a href=3D"http://h=
allambaker.com/" target=3D"_blank">http://hallambaker.com/</a><br>
</font></span></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--001a11c26b12a861eb04f0bd4484--

From rlb@ipv.sx  Fri Jan 24 12:38:02 2014
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62DE1A01EB for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 12:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCJOTj8vEnvz for <ietf@ietfa.amsl.com>; Fri, 24 Jan 2014 12:38:00 -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 07CB11A01E6 for <ietf@ietf.org>; Fri, 24 Jan 2014 12:37:59 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id uy5so4162790obc.33 for <ietf@ietf.org>; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=NMIx45lNMifRSAjmzAWQYxXMbVUUcIaaLN6P9hxDWqQ=; b=E2fAB2WXLisg4xZGekzmc5HE+DDnPsyTrXfFjfXElemThlc+dvV5CcCitePBGIznsg oEnzj+h1CPlT8xV0OwBlHayfSvgjNLS8Ul3bnKr/Wt/22SIQ6DwHBAUBHFAvFVNOBZyV 4YUUW1a35FI9ry8SsH5eXp0YtCLDnQZ0pNpo/9QCfZKdHlwyRlL2NXbEUoAl/CgaTm1L AZNv8xA2j0idOiN0oTQ+/j6bGPIMYhp6ksAmHaDhusoGxq74+ZJrDmrk+gliNaYQXJjY FNcC/8if3Ox16EU8/sRcfQyZyEUfl5pypMktJchnM05zY2yu7tQHdJm1ohPAw6tocn7I 68aw==
X-Gm-Message-State: ALoCoQk8FA0Af+97wp4BUtLtEU4oc+KkaVW/Pff27geS0q4IquqLlQFg1ys3WIaq1rKpdgRUDHav
MIME-Version: 1.0
X-Received: by 10.60.84.199 with SMTP id b7mr3028681oez.55.1390595878574; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
Received: by 10.60.54.65 with HTTP; Fri, 24 Jan 2014 12:37:58 -0800 (PST)
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 21:37:58 +0100
Message-ID: <CAL02cgSeyk0SYGwe-hHbOOe4Y-KJqo9Yd-2wpHQvjrO=jnAxZQ@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Richard Barnes <rlb@ipv.sx>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=089e0102dc825e714704f0bd55ca
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:38:03 -0000

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

On Fri, Jan 24, 2014 at 9:24 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>
>> Both Tom and Lars text would work for me. There seem to be so many ways
>> to write it such that it is still brief but captures the key elements of
>> the BCP.
>>
>> Pete, I really think it is that putting a sentences in it that is clearly
>> false is just wrong and I can not understand why you are arguing for that?
>>
>>
>
> So here's the key for me (and maybe this means we have a separate Note
> Well for the room from the one on the web site):
>
> In the room, I want something short enough that the chairs might actually
> be inclined to read out loud. It should have the three basic messages:
>
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.
>

It seems like this last part is what Cullen and others are catching on,
since it misses an essential caveat.  You *don't* have to disclose IPR on
things you where don't participate in the discussion.



> Details on the above specified elsewhere. Go read if you're worried about
> it.
>
> I want those statements extended as little as possible to keep it so that
> the chair might be willing to say it.
>

All Cullen proposed changing was the following:
OLD: "If you are aware that any contribution (something written, said, or
discussed in any IETF context) is covered by patents or patent
applications, you must disclose that fact."
NEW:  "If you are aware that any contribution (something written, said, or
discussed in any IETF context) is covered by patents or patent
applications, you must disclose that fact, or not contribute to the
discussion on that contribution"

Nine more words is really too long?

--Richard



>
> And (and this is probably the one where we might still disagree) if it's
> going to be inaccurate, and it will *have* to be inaccurate just by nature
> of being a summary, I want it to be inaccurate such that it includes *more*
> things to disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand all of the
> detail in BCP 79, but the Note Well sure didn't say that I had to disclose
> anything like *that*." If there's going to be an inaccuracy in the
> statement, I want it to be that BCP 79 says to disclose *less* than the
> summarized warning we give folks in the room.
>
> Both Tom's and Lars's summaries are fine, but they're not reasonable
> things to read in the room.
>
> We wrestled with this for a while. I'm open to suggestions. But the above
> are really my design criteria, at least for the one we put on a slide for
> the room.
>
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Jan 24, 2014 at 9:24 PM, Pete Resnick <span dir=3D"ltr">&lt=
;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">presnick@qt=
i.qualcomm.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"im">On 1/24=
/14 10:31 AM, Cullen Jennings (fluffy) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP.<br>
<br>
Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?<b=
r>
=A0 =A0<br>
</blockquote>
<br></div>
So here&#39;s the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):<br>
<br>
In the room, I want something short enough that the chairs might actually b=
e inclined to read out loud. It should have the three basic messages:<br>
<br>
- By participating here, you&#39;ve agreed to our rules.<br>
- You can be recorded.<br>
- You have to disclose your IPR.<br></blockquote><div><br></div><div>It see=
ms like this last part is what Cullen and others are catching on, since it =
misses an essential caveat.=A0 You *don&#39;t* have to disclose IPR on thin=
gs you where don&#39;t participate in the discussion.=A0 <br>
</div><div><br>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Details on the above specified elsewhere. Go read if you&#39;re worried abo=
ut it.<br>
<br>
I want those statements extended as little as possible to keep it so that t=
he chair might be willing to say it.<br></blockquote><div><br></div><div>Al=
l Cullen proposed changing was the following:<br>OLD: &quot;If you are awar=
e that any contribution (something written, said, or=20
discussed in any IETF context) is covered by patents or patent=20
applications, you must disclose that fact.&quot;<br>NEW:=A0 &quot;If you ar=
e aware that any contribution (something written, said, or=20
discussed in any IETF context) is covered by patents or patent=20
applications, you must disclose that fact, or not contribute to the discuss=
ion on that contribution&quot;=A0 <br><br>Nine more words is really too lon=
g?=A0 <br><br></div><div>--Richard<br></div><div><br>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">

<br>
And (and this is probably the one where we might still disagree) if it&#39;=
s going to be inaccurate, and it will *have* to be inaccurate just by natur=
e of being a summary, I want it to be inaccurate such that it includes *mor=
e* things to disclose than you are actually required to, not less. I don&#3=
9;t want the excuse for not disclosing to be &quot;I didn&#39;t understand =
all of the detail in BCP 79, but the Note Well sure didn&#39;t say that I h=
ad to disclose anything like *that*.&quot; If there&#39;s going to be an in=
accuracy in the statement, I want it to be that BCP 79 says to disclose *le=
ss* than the summarized warning we give folks in the room.<br>

<br>
Both Tom&#39;s and Lars&#39;s summaries are fine, but they&#39;re not reaso=
nable things to read in the room.<br>
<br>
We wrestled with this for a while. I&#39;m open to suggestions. But the abo=
ve are really my design criteria, at least for the one we put on a slide fo=
r the room.<div class=3D""><div class=3D"h5"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</div></div></blockquote></div><br></div></div>

--089e0102dc825e714704f0bd55ca--

From paul.hoffman@vpnc.org  Fri Jan 24 12:56:48 2014
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8811A0099; Fri, 24 Jan 2014 12:56:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUTSi3-xuFhx; Fri, 24 Jan 2014 12:56:47 -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 2B8C71A0090; Fri, 24 Jan 2014 12:56:47 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s0OKaXY8031132 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 24 Jan 2014 13:36:34 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Problem with new Note Well
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 12:56:42 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF96DC31-A2B8-400D-913F-C66A278DA2B6@vpnc.org>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 20:56:48 -0000

On Jan 24, 2014, at 12:24 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> So here's the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):
>=20
> In the room, I want something short enough that the chairs might =
actually be inclined to read out loud.

So, you want IPR theater. Lovely.

Everyone in the room has already seen the full Note Well at least twice: =
once upon registering, and once on the agenda. If your actual mission is =
to get people to read what they have already seen, then the in-room =
message should simply be:

You already received the IPR rules at least twice. If you haven't read =
them,
do so right now on on the little schedule or at =
<http://www.ietf.org/ipr/policy.html>.

That statement lets the WG get to the real purpose of the face-to-face =
meeting, and does not badly summarize the actual rules.

--Paul Hoffman=

From spencerdawkins.ietf@gmail.com  Fri Jan 24 14:13:24 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2791A0185; Fri, 24 Jan 2014 14:13:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NoZXp5tSIVnW; Fri, 24 Jan 2014 14:13:23 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id ECBEE1A001A; Fri, 24 Jan 2014 14:13:22 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id wn1so4245279obc.34 for <multiple recipients>; Fri, 24 Jan 2014 14:13:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=z+TI4U3m5PbgLUPDpL/eYcK4iOGTB3v4XB1gJEuieKo=; b=HIxJDJjo4gbVE8mpZTjnEwcmMkKcuUCXx4jzGilUX3djfps1N4vAsCVlqyRWPTDdCo tb5vhL6F4wkYDWDI1lQnhDoXhUjJYOjM6bIkJjTgiZiaj3ksTPkaMLwh1CxU+t1S9pI9 3yuFSyltkV/Co8DpRGLR1H4aC3cfcOyju0xSPDYCC/d/v4tRG9rSc1XTpx37ghWl5/ki 3RDKS1DpIieoyYAt5Lf53+zab+BBLIsp4QfRFLSfKIJK+zWlcCF3hcz262zxngFcxzhc 4swEqS146c4w/nTk4QLZ/PvFVQ/gblSmxJOzwrESYTcYsGD4OBqRo0WpCIDU6my7sAW1 yA2Q==
X-Received: by 10.182.22.18 with SMTP id z18mr13814867obe.42.1390601600648; Fri, 24 Jan 2014 14:13:20 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id ii8sm3847353obb.11.2014.01.24.14.13.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 14:13:19 -0800 (PST)
Message-ID: <52E2E57D.70403@gmail.com>
Date: Fri, 24 Jan 2014 16:13:17 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, Joe Touch <touch@isi.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140122172930.3D31A18C13B@mercury.lcs.mit.edu> <64A7AA55-795A-40FA-8008-5FCE3B8E2C44@netapp.com> <52E18661.4060000@isi.edu> <CACKN6JFzaGkiCzJgcd0BEHeWi5x0ReemJOv4ASuXAnz36RA-fg@mail.gmail.com> <52E18BF1.1040004@isi.edu> <CACKN6JEA6=vJM94gdhc8iBJV52eTg1X-f7fyBiouJMGz+HOqsw@mail.gmail.com> <52E1AC3E.2040204@isi.edu> <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
In-Reply-To: <CAG4d1rf+wAJuD2GvYfm14bOoEvbhqq0azN5fOq35aPJDUvg=gw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 22:13:24 -0000

On 01/23/2014 06:07 PM, Alia Atlas wrote:
> I don't want to get in the way of vehement discussion, but I thought 
> we were on the verge of finding an actual solution...
>
> IMHO, that was a combination of an applicability statement, using 
> SHOULD for congestion control and checksum, and defining a longer-term 
> OAM-based approach (as Stewart Bryant suggested) to be able to verify 
> that packet corruption or excessive drops aren't happening.
>
> Does that sound like an acceptable set?

Alia, I certainly hope so (speaking as an individual), and I appreciate 
you conjuring up the specter of an applicability statement (speaking as 
TSV AD).

I expect to find that helpful.

Spencer

From john-ietf@jck.com  Fri Jan 24 19:04:18 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D31E1A0445; Fri, 24 Jan 2014 19:04:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.135
X-Spam-Level: 
X-Spam-Status: No, score=-5.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rZlVuB2sBoU0; Fri, 24 Jan 2014 19:04:17 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E993A1A047A; Fri, 24 Jan 2014 19:04:16 -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 1W6tXU-00064X-Au; Fri, 24 Jan 2014 22:04:08 -0500
Date: Fri, 24 Jan 2014 22:04:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Message-ID: <3F2BCC58F9BDF9731C6E7A8C@JcK-HP8200.jck.com>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, Tom Taylor <tom.taylor.stds@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 03:04:18 -0000

--On Friday, January 24, 2014 14:24 -0600 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

>...
> And (and this is probably the one where we might still
> disagree) if it's going to be inaccurate, and it will *have*
> to be inaccurate just by nature of being a summary, I want it
> to be inaccurate such that it includes *more* things to
> disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand
> all of the detail in BCP 79, but the Note Well sure didn't say
> that I had to disclose anything like *that*." If there's going
> to be an inaccuracy in the statement, I want it to be that BCP
> 79 says to disclose *less* than the summarized warning we give
> folks in the room.
>...
> We wrestled with this for a while. I'm open to suggestions.
> But the above are really my design criteria, at least for the
> one we put on a slide for the room.

Pete,

If the announcement appears to require more than what is
actually required, you will divide the part of the audience that
pays any attention at all [1] into three categories:

(1) Those who will be scared off by it, or who will discuss it
with their corporate lawyers who will be scared off.  Perhaps
that will be because they will be concerned that the superset
notice is what they were actually told and for which they might
be held accountable, perhaps they conclude that, in the event of
confusion, conservatism is best.  Perhaps something else, but
the net effect is likely to be as much to reduce IETF
participation by those who are concerned as it would be to get
more disclosures.

(2) Those who will say "Well, the announcement distorts the
meaning of BCP 79, so there must be loopholes they are trying to
hide.  Let's go find them."

(3) Those who will go reread BCP 79, and do exactly what it says
regardless of your exaggerations.

Remembering that our goal should be to enable and encourage as
much participation as possible consistent with getting the
disclosures we actually need, I don't see most of those options
as desirable.

    john

[1] Some of us have a talent for tuning out boilerplate.  As a
sometime WG chair, if I have any choice at all, I won't spend
time trying to read things that I'm pretty sure that those who
will listen have already seen and those who won't, won't (I
think that puts my position in alignment with Paul Hoffman's).
As an individual, as soon as the WG Chair says something that
implies "I have this obligatory statement to read that you have
heard before", I'm likely to decide it is an invitation to open
a tunnel to my mailbox (or equivalent).  If that describes a
significant set of patterns, then anything you do to alter the
in-meeting version is a waste of time.
 


From brian.e.carpenter@gmail.com  Fri Jan 24 19:41:34 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E03C1A0211; Fri, 24 Jan 2014 19:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TvA64UflrJbc; Fri, 24 Jan 2014 19:41:31 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id BAD7D1A01C9; Fri, 24 Jan 2014 19:41:31 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id bj1so3951948pad.25 for <multiple recipients>; Fri, 24 Jan 2014 19:41:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=dHJGTfgw4tnjafBq4m6H+ABEXaiaYplioxAooq2O+r8=; b=0Q0/BJDyR6eLzYKXhH2HcVxpd4JjZBibz0t54+X6NPceIqTyN60WZnfDwiVpq6veHv QUcPavQDTnJskfAH5BYgFFRCDdLRerfMgfZaWuifdu22i16ckvR3DcbMOZschBpMhncA AIRjGAcn4ApeZj9voOeXAQ/MRlawlQXoY0ukW4eaShRjQP1TD5o5BprBkj6DIQFFSdfz bSuhtilNDapapkrrDt4/eP+0ubkQAfNyKGwawUaU15+k/QxbjN8AqfCnw1zlILMDw+SK +lYq5+4cmBXAUzY00JtHSQVQ7gLPP3TWv4tuXU9clr8OqmeBGHNczSBgwaRqVUgWn9GP 9/0w==
X-Received: by 10.68.230.137 with SMTP id sy9mr17768010pbc.126.1390621290492;  Fri, 24 Jan 2014 19:41:30 -0800 (PST)
Received: from [192.168.178.23] (218.194.69.111.dynamic.snap.net.nz. [111.69.194.218]) by mx.google.com with ESMTPSA id ns7sm8152367pbc.32.2014.01.24.19.41.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Jan 2014 19:41:29 -0800 (PST)
Message-ID: <52E3326E.3080007@gmail.com>
Date: Sat, 25 Jan 2014 16:41:34 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
In-Reply-To: <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 03:41:34 -0000

It's quite obvious from reading this thread that the IAOC needs
to revert to the previous Note Well text right now, until the
wording issue is resolved.

It is apparent to me though that the BCP *requires* disclosure
as a condition of participation, regardless of employment agreements,
and always has done. That's why there has always been tolerance extended
to allow corporate IPR departments to have time to prepare and make
disclosures at lawyerly speed. Nothing new here except the more brutal
wording.

Regards
   Brian

On 24/01/2014 06:25, Cullen Jennings (fluffy) wrote:
> This new note well is a real problem for me and  I can not register wit=
hout clicking "I agree" to it. It is not consistent with the BCPs. The pr=
oblem is the line that says
>=20
> 	=E2=80=A2 If you are aware that any contribution (something written, s=
aid, or discussed in any IETF context) is covered by patents or patent ap=
plications, you must disclose that fact.
>=20
> I do not agree to that - I can=E2=80=99t given my NDA with my employer =
does not allow me to disclose confidential information. Yes, I realize th=
ere is some weasel words near the top that say "Exceptions may apply." bu=
t that does not help me. When you are testifying in court on patents, cre=
dibility is incredibly important. You can not have the lawyers on the oth=
er side saying that you clicked yes I agree to the line above but you did=
 not actually do what that lines says. You may think this does to matter =
but the exact topic of how Cisco employees deal with IPR at the IETF is a=
 topic that I have testified on in an East Texas court so this really doe=
s happen and really does happen to me. It may happen to you next and you =
will be much happier if you say what you mean and mean what you say. This=
 new note well fails that test.=20
>=20
> I realize some people would like to change the IETF policy to be that y=
ou do have to do what that line says but I do not think that is a change =
the IESG can make without IETF updating the BCP or at least having IETF c=
onsensus on the change. I would respectfully ask the IESG to change this =
line to something that is still brief but that people can agree with it. =
Simply adding something like "or not contribute to the discussion on that=
 contribution" would probably solve this problem for me.=20
>=20
> Thank you,=20
>=20
> Cullen
>=20
> I will note that above line is not consistent with Cisco employment con=
tracts and if we can not resolve this I will be asking Cisco legal to inf=
orm Cisco employees they can not agree with this without violating their =
employment agreement.=20
>=20
>=20
>=20
> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:=

>=20
>> It seems that the shorter one is now being used on the IETF web site:
>> http://www.ietf.org/about/note-well.html
>>
>>
>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>
>>> Personally, I've never seen significant value in this shorter note we=
ll and while others have been using this new text for the past few meetin=
gs, I've stuck to the old.   Now that this is considered the recommended =
note well for chairs to use, I guess I'll use it.  But, I personally thin=
k accuracy should trump brevity.  I think the "must" in that bullet  ough=
t to at least be a should and that adding an "otherwise, one should not c=
ontribute to or participate in any related IETF activities." would add mo=
re value.  =20
>>>
>>> Mary.
>>>
>>>
>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrot=
e:
>>> you are correct - we (Barry, the IESG & me) discussed this before the=
 IESG approved this text - they felt that
>>> being brief was more important than being fully accurate (or at least=
 that is the way I expressed it)
>>>
>>> Scott
>>>
>>> Scott O Bradner
>>> Senior Technology Consultant
>>>
>>> Harvard University Information Technology
>>> Innovation & Architecture
>>> (P) +1 (617) 495 3864
>>> 8 Story St, room 5014
>>> Cambridge, MA 02138
>>>
>>>
>>>
>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.co=
m> wrote:
>>>
>>>>
>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> =
wrote:
>>>>
>>>>> The IESG has made final edits to the updated Note Well statement, a=
nd
>>>>> it has been officially updated:
>>>>> http://www.ietf.org/about/note-well.html
>>>>>
>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>
>>>>> Please use this new version now, and please remember that as you
>>>>> prepare slides for the London meeting.
>>>>>
>>>>> Barry
>>>>
>>>> The new note well says
>>>>
>>>>       =E2=80=A2 If you are aware that any contribution (something wr=
itten, said, or discussed in any IETF context) is covered by patents or p=
atent applications, you must disclose that fact.
>>>>
>>>> Is that true?  Or is it missing something along the lines of section=
 y of BCP 79 such as
>>>>
>>>>   or must not contribute to or participate in IETF activities with
>>>>   respect to technologies that he or she reasonably and personally
>>>>   knows to be Covered by IPR which he or she will not disclose.
>>>>
>>>> Thanks, Cullen
>=20
>=20


From john-ietf@jck.com  Sat Jan 25 05:19:38 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F53D1A02EE; Sat, 25 Jan 2014 05:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ErVvyD58Z99m; Sat, 25 Jan 2014 05:19:36 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8281A02EA; Sat, 25 Jan 2014 05:19:36 -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 1W7391-000789-Qc; Sat, 25 Jan 2014 08:19:31 -0500
Date: Sat, 25 Jan 2014 08:19:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
Message-ID: <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
In-Reply-To: <52E3326E.3080007@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@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: IESG IESG <iesg@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 13:19:38 -0000

--On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> It's quite obvious from reading this thread that the IAOC needs
> to revert to the previous Note Well text right now, until the
> wording issue is resolved.
> 
> It is apparent to me though that the BCP *requires* disclosure
> as a condition of participation, regardless of employment
> agreements, and always has done. That's why there has always
> been tolerance extended to allow corporate IPR departments to
> have time to prepare and make disclosures at lawyerly speed.
> Nothing new here except the more brutal wording.

Agreed.  Noting that the likely effect of "regardless of
employment agreements" if there really is a conflict in a
particular company-participant relations is "don't participate
in that" under the BCP and "don't attend" if the wording is more
brutal, we should have a lot of incentive to clean the language
up... and go back to the tested language until a cleaned-up
version is ready.

    john



From fluffy@cisco.com  Sat Jan 25 06:21:48 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21B3A1A02D3; Sat, 25 Jan 2014 06:21:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxn-yYoxuyCT; Sat, 25 Jan 2014 06:21:46 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id E2BEB1A02C2; Sat, 25 Jan 2014 06:21:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3704; q=dns/txt; s=iport; t=1390659704; x=1391869304; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=IagNhy1J0UeNQKRbGiy9P3kCxco+DqUM0GeNPLaAC4M=; b=gQ+7QPeGxvJBx20apJaGvsQa1d+/r9eDOdMEqx51wIS+Va4JyKr4H5ad 5ZbhdQF7PBuwPIIMzVJVeI09Q77QChra1g8lFlFDMZdBHq+ZyDeZqNr6p w+eRoabObcOkVLSv9UgbWk0MLclOJwaBvJfQYMjI57rdceYgoMC3+9gZ5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FABjH41KtJV2d/2dsb2JhbABXAxaCdjhWvEmBBhZ0giUBAQEDAXkFCwIBCA4KLjIlAgQOBYd9CA3IcReOWiMQBxGDE4EUBJgnkh6DLYIq
X-IronPort-AV: E=Sophos;i="4.95,719,1384300800"; d="scan'208";a="15497084"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP; 25 Jan 2014 14:21:42 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s0PELgkm010550 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 25 Jan 2014 14:21:42 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Sat, 25 Jan 2014 08:21:42 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGUJBoZGQwbDO+0qJCUaQbh9tI5qV45iA
Date: Sat, 25 Jan 2014 14:21:41 +0000
Message-ID: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <800C0B52F6818E47B570431EAAD9677E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IESG IESG <iesg@ietf.org>, IETF WG Chairs <wgchairs@ietf.org>, Tom Taylor <tom.taylor.stds@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 14:21:48 -0000

Pete, inline =85


On Jan 24, 2014, at 1:24 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote=
:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>> Both Tom and Lars text would work for me. There seem to be so many ways =
to write it such that it is still brief but captures the key elements of th=
e BCP.
>>=20
>> Pete, I really think it is that putting a sentences in it that is clearl=
y false is just wrong and I can not understand why you are arguing for that=
?
>>  =20
>=20
> So here's the key for me (and maybe this means we have a separate Note We=
ll for the room from the one on the web site):
>=20
> In the room, I want something short enough that the chairs might actually=
 be inclined to read out loud. It should have the three basic messages:

I certainly don=92t plan to read it out in meetings I chair as I do not see=
 any way that it will actually improve the situation at IETF but none the l=
ess I still basically agree with your design goals (include keeping it rela=
tively short).=20

>=20
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.

It=92s this above point that I don=92t believe is true. I think the point y=
ou need to make is, I think what you need to say is=20

      "You have to disclose your IPR, or not participate in the discussion"

I do want to point out that if you truly wanted this short the total slides=
 would say=20

      "This meeting may be recorded. To be in this meeting you must agree t=
o the rules in BCP 79. "


> Details on the above specified elsewhere. Go read if you're worried about=
 it.
>=20
> I want those statements extended as little as possible to keep it so that=
 the chair might be willing to say it.
>=20
> And (and this is probably the one where we might still disagree) if it's =
going to be inaccurate, and it will *have* to be inaccurate just by nature =
of being a summary, I want it to be inaccurate such that it includes *more*=
 things to disclose than you are actually required to, not less. I don't wa=
nt the excuse for not disclosing to be "I didn't understand all of the deta=
il in BCP 79, but the Note Well sure didn't say that I had to disclose anyt=
hing like *that*." If there's going to be an inaccuracy in the statement, I=
 want it to be that BCP 79 says to disclose *less* than the summarized warn=
ing we give folks in the room.

The core issue here is that you are making the summary be a sentence which =
is not wrong and which people can not and will not comply with. At that poi=
nt you toss the whole thing into questions. People who need to testify in c=
ourt on patents will have their credibility undermined by having agreed to =
this and then not doing it. You need to come up with a summary is not wrong=
 even if it is not be complete.

I would also like to point out we are not talking about just what goes up o=
n the front of the room but also what I must click agree to when I register=
.=20

>=20
> Both Tom's and Lars's summaries are fine, but they're not reasonable thin=
gs to read in the room.
>=20
> We wrestled with this for a while. I'm open to suggestions. But the above=
 are really my design criteria, at least for the one we put on a slide for =
the room.

Good to hear, I am very hopeful that someone will come up with a suggestion=
 that is not wrong, and at the same time does not increase the total length=
 of the Note Well by more than lets say 20%. Would that work for you ?


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


From john-ietf@jck.com  Sat Jan 25 06:46:13 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEBE1A037D; Sat, 25 Jan 2014 06:46:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Az-SbAeTZnyo; Sat, 25 Jan 2014 06:46:11 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B70771A026C; Sat, 25 Jan 2014 06:46:11 -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 1W74Uq-0007ED-HI; Sat, 25 Jan 2014 09:46:08 -0500
Date: Sat, 25 Jan 2014 09:46:03 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Message-ID: <9393741FAF54D30498339914@JcK-HP8200.jck.com>
In-Reply-To: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, Scott Bradner <sob@harvard.edu>, Tom Taylor <tom.taylor.stds@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 14:46:13 -0000

--On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
(fluffy)" <fluffy@cisco.com> wrote:

>...
>> - By participating here, you've agreed to our rules.
>> - You can be recorded.
>> - You have to disclose your IPR.
> 
> It's this above point that I don't believe is true. I
> think the point you need to make is, I think what you need to
> say is 
> 
>       "You have to disclose your IPR, or not participate in
> the discussion"

And, of course, this drags us into the precise definition of
"participate", an axle around which we've gotten wrapped several
times.  In particular, 

> I do want to point out that if you truly wanted this short the
> total slides would say 
> 
>       "This meeting may be recorded. To be in this meeting you
> must agree to the rules in BCP 79. "

but "to be in this meeting" means that sitting in the room
during a WG session constitutes "participation".  I like that
definition, but we've been around it several times and my
recollection is that I was in the minority.  If "participate"
for IPR purposes has any resemblance to "making a Contribution",
e.g., opening your mouth, then the above statement is as false
as some of those to which you object.

>...
> The core issue here is that you are making the summary be a
> sentence which is not wrong and which people can not and will
> not comply with. At that point you toss the whole thing into
> questions. People who need to testify in court on patents will
> have their credibility undermined by having agreed to this and
> then not doing it. You need to come up with a summary is not
> wrong even if it is not be complete.

Yep.  See earlier comments by Brian and myself, but this
credibility effect is equally important.

Perhaps the appropriate short statement might be more like:

	"If you are in this room two minutes from now or
	thereafter, you are deemed to have read, understood, and
	agreed to BCP 79.  If you have not read and understood
	it, please leave until after you do."
	
I hope that is a joke, but it is short, says nothing false, and
doesn't get entangled with terms like "participate".

>...

   john



From fluffy@cisco.com  Sat Jan 25 06:51:01 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5A81A0377; Sat, 25 Jan 2014 06:51:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AA1TnvY54-vk; Sat, 25 Jan 2014 06:50:59 -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 8C9A61A026C; Sat, 25 Jan 2014 06:50:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2716; q=dns/txt; s=iport; t=1390661458; x=1391871058; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=TMBI58sb5EgpPFfyO9g0JAdogc3fsHfJzgwogQ6SHbY=; b=YO4WTDyZ/Xg41IzPGfhop1ihSjPehqyzYjcmkUYKUXfpd0F7kGAA1pw4 nGbyQq6+rfJtboZgTbWhg77UjQ4xxaaTDEgMGkUhgKtI7bJ+fqpMyoauU eijHEQAKqNj8SWRKbwpGoHTp/Nb0EA7phVWAHlMk09NQS0SutguZqA+23 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FAOTO41KtJXG+/2dsb2JhbABagwyBDrxJgQYWdIIlAQEBBHkQAgEIGC4yJQIEDgWIBckDF45aMweDJIEUAQOYJ5Iegy2CKg
X-IronPort-AV: E=Sophos;i="4.95,719,1384300800"; d="scan'208";a="299753196"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-4.cisco.com with ESMTP; 25 Jan 2014 14:50:58 +0000
Received: from xhc-rcd-x10.cisco.com (xhc-rcd-x10.cisco.com [173.37.183.84]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0PEov5d027388 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 25 Jan 2014 14:50:57 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x10.cisco.com ([173.37.183.84]) with mapi id 14.03.0123.003; Sat, 25 Jan 2014 08:50:57 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPGUJBoZGQwbDO+0qJCUaQbh9tI5qVhdvZgABl6QA=
Date: Sat, 25 Jan 2014 14:50:56 +0000
Message-ID: <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com>
In-Reply-To: <9393741FAF54D30498339914@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <936585A394D32647BEDD31B18F77C491@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Tom Taylor <tom.taylor.stds@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 14:51:01 -0000

John,

Point taken and I understand how hard it is to get the right words. I=92m n=
ot trying to propose exact words as I=92m hoping that someone else can come=
 up with something that meets Pete=92s goals of relatively short and my goa=
ls of not looking like an idiot in some court room.=20

Cullen


On Jan 25, 2014, at 7:46 AM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
> (fluffy)" <fluffy@cisco.com> wrote:
>=20
>> ...
>>> - By participating here, you've agreed to our rules.
>>> - You can be recorded.
>>> - You have to disclose your IPR.
>>=20
>> It's this above point that I don't believe is true. I
>> think the point you need to make is, I think what you need to
>> say is=20
>>=20
>>      "You have to disclose your IPR, or not participate in
>> the discussion"
>=20
> And, of course, this drags us into the precise definition of
> "participate", an axle around which we've gotten wrapped several
> times.  In particular,=20
>=20
>> I do want to point out that if you truly wanted this short the
>> total slides would say=20
>>=20
>>      "This meeting may be recorded. To be in this meeting you
>> must agree to the rules in BCP 79. "
>=20
> but "to be in this meeting" means that sitting in the room
> during a WG session constitutes "participation".  I like that
> definition, but we've been around it several times and my
> recollection is that I was in the minority.  If "participate"
> for IPR purposes has any resemblance to "making a Contribution",
> e.g., opening your mouth, then the above statement is as false
> as some of those to which you object.
>=20
>> ...
>> The core issue here is that you are making the summary be a
>> sentence which is not wrong and which people can not and will
>> not comply with. At that point you toss the whole thing into
>> questions. People who need to testify in court on patents will
>> have their credibility undermined by having agreed to this and
>> then not doing it. You need to come up with a summary is not
>> wrong even if it is not be complete.
>=20
> Yep.  See earlier comments by Brian and myself, but this
> credibility effect is equally important.
>=20
> Perhaps the appropriate short statement might be more like:
>=20
> 	"If you are in this room two minutes from now or
> 	thereafter, you are deemed to have read, understood, and
> 	agreed to BCP 79.  If you have not read and understood
> 	it, please leave until after you do."
> =09
> I hope that is a joke, but it is short, says nothing false, and
> doesn't get entangled with terms like "participate".
>=20
>> ...
>=20
>   john
>=20
>=20


From housley@vigilsec.com  Sat Jan 25 07:15:21 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B831A00CA for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 07:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XU5LSX4LaGhd for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 07:15:19 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id E29851A00F2 for <ietf@ietf.org>; Sat, 25 Jan 2014 07:15:18 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 4622A9A42B7; Sat, 25 Jan 2014 10:15:07 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id tKuuG-s6uG0R; Sat, 25 Jan 2014 10:14:46 -0500 (EST)
Received: from [192.168.2.106] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 2B3D49A42BB; Sat, 25 Jan 2014 10:14:46 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20131216185842.0c8a6dc8@resistor.net>
Date: Sat, 25 Jan 2014 09:48:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCCB9F8F-32CE-45A5-9ED5-1491254331EB@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <6.2.5.6.2.20131216185842.0c8a6dc8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 15:15:21 -0000

SM:

> At 14:34 16-12-2013, Russ Housley wrote:
>> This document tells which registries have policy set by the RIRs.  =
The special-purpose values are exceptions, and that is why they are =
named in this document.
>=20
> [snip]
>=20
>> Again, these are saying that exceptions require IETF Review, but =
otherwise the policy for these registries is handled by the RIRs.
>=20
> Thanks for the reply.  I read draft-housley-number-registries-02 =
again.  The "which registries have policy set ..." would be the =
following text:
>=20
>  "The allocation and registration functions for all non-reserved
>   globally unique unicast IPv4/IPv6 unicast addresses are handled by =
the
>   Internet Numbers Registry System in accordance with policies
>   developed by the Regional Internet Registries (RIRs)."
>=20
> The special-propose values are already discussed in RFC 6890.  Section =
2.2 of that RFC mentions that:
>=20
>  'IANA will update the aforementioned registries as requested in the
>   "IANA Considerations" section of a document that has passed IETF
>   Review [RFC5226].'
>=20
> My reading of the above is that it says that exceptions require IETF =
Review.  I read Section 3 of RFC 7020:
>=20
>  "In addition, ICANN performs the IANA services related to the IP
>   address space and AS numbers according to global number resource
>   policies that have been developed by the community and formalized
>   under a Memorandum of Understanding between ICANN and the Regional
>   Internet Registries [ASOMOU] and documented in [ICANNv4], [ICANNv6],
>   and [ICANNASN]."
>=20
> That text covers the policy angle.
>=20
> The Introduction section of the draft mentions "IANA registries".  The =
quoted paragraph of the reply mentioned that the "document tells which =
registries have policy ...".  It is difficult to understand what the =
draft is about.
>=20
> Regards,
> -sm=20

Thanks for your comments.  I have changed section 1 and section 2 to =
address them.  Here is the updated text:

1.  Introduction

   In accordance with the IETF-IANA Memorandum of Understanding
   [RFC2860], RFC 7020 [RFC7020] provides information about the Internet
   Numbers Registry System and how it is used in the distribution of
   autonomous system (AS) numbers and globally unique unicast Internet
   Protocol (IP) address space.

   This companion document identifies the IANA registries that are part
   of the Internet Numbers Registry System at this time.

2.  Internet Numbers Registries

   Three IANA registries are associated with the Internet Numbers
   Registry System: AS Numbers, unicast IPv4 Addresses, and unicast IPv6
   Addresses.  However, in each case, there are special-purpose values,
   and those special-purpose values are outside the Internet Numbers
   Registry System.

Russ



From housley@vigilsec.com  Sat Jan 25 08:23:19 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 112E31A0390 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LXasU7I6tYmr for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:17 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 899C51A03D6 for <ietf@ietf.org>; Sat, 25 Jan 2014 08:23:15 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 211419A42BD; Sat, 25 Jan 2014 11:23:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id cHV5Ro7ZXygR; Sat, 25 Jan 2014 11:22:43 -0500 (EST)
Received: from [192.168.2.106] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 41B729A42BA; Sat, 25 Jan 2014 11:22:43 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <201401062137.s06Lb6jG017519@cichlid.raleigh.ibm.com>
Date: Sat, 25 Jan 2014 11:06:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E3BDEEF-40E9-400D-B920-DEE7F8273935@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <201401062137.s06Lb6jG017519@cichlid.raleigh.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1085)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 16:23:19 -0000

Thomas:

> Overall, this document looks good. But a couple of suggestions.
>=20
> As a general comment, I think the document should include a reference
> wherever it states what a policy is (as defined elswhere).
>=20
>>   Reservations of special-purpose AS Numbers are made through =
Internet
>>   Standards actions.
>=20
> Citation of where that policy is defined?

I have updated the document; it will be posted as -03.  It now uses =
"IETF Review" throughout.
=20
> But then later, the document says::
>=20
>> 3.  IANA Considerations
>>=20
>>   "IETF Review" as defined in [RFC5226] is required to reserve =
special-
>>   purpose AS numbers, IPv4 addresses, or IPv6 addresses.  Reserved AS
>>   numbers, IPv4 addresses, or IPv6 addresses may be designated to
>>   support testing, IETF experimental activities, or other special =
uses
>>   (e.g., anycast).  These reservations are recorded in the relevant
>=20
> which contradicts the previous statement.
>=20
> Also, would be good to cite all the individual RFCs when restating
> what the policy is for each registries listed above.

I have reworked this as suggested by David Conrad.  It now points to the =
existing IANA registry, which already requires "IETF Review" for =
additions.

>>   Reservation of special-purpose IPv4 addresses are made through
>>   Internet Standards actions.  Reserved IPv4 unicast addresses are
>>   registered in the Special Purpose IP address registries [RFC6890].
>=20
> Citation for first sentence?

I have reworked this as suggested by David Conrad.  It now points to the =
existing IANA registry, which already requires "IETF Review" for =
additions.

>>   The vast bulk of the IPv6 address space (approximately 7/8ths of =
the
>>   whole address space) is reserved by the IETF, with the expectation
>=20
> For first sentence, cite where that reservation/delegation was made
> (i.e., RFC 3513).

Okay.

Russ


From housley@vigilsec.com  Sat Jan 25 08:23:19 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7651A03D5 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SAcobjU5PJ56 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:17 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id CB7BB1A03D9 for <ietf@ietf.org>; Sat, 25 Jan 2014 08:23:15 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 65D569A42BA; Sat, 25 Jan 2014 11:23:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id Ev1OCIeqZ1h9; Sat, 25 Jan 2014 11:22:42 -0500 (EST)
Received: from [192.168.2.106] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id D9B619A42B7; Sat, 25 Jan 2014 11:22:42 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org>
Date: Sat, 25 Jan 2014 10:58:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF378B80-A687-4014-8DAE-0A71E8154716@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Pgp-Agent: GPGMail 1.4.1
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 16:23:20 -0000

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

David:

> Overall: =20
>=20
> I'm a bit uncomfortable with specifying the contents of registries =
within RFCs these days as they can become out of date even before =
they're published.  For example, it's likely there's going to be a =
reservation of IPv6 space for LISP EID prefixes in the near future but =
(I suspect) after your draft is published as an RFC.  Perhaps it would =
make more sense to reference IANA registries instead of listing the =
contents of what would be in those registries in the draft text, e.g., =
pointing to =
http://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-speci=
al-registry.xml for IPv4 and =
http://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-speci=
al-registry.xhtml for IPv6 (and creating a special purpose registry for =
AS numbers)?

I think this is a good idea.  It required a fairly significant update to =
the document.  I did it in version -03.

> I find it curious that when talking about top-level domains, the =
criteria (according to RFC 6761) for reservation is "Standards Action" =
or "IESG Approval" but when talking about reserving Internet Number =
resources, the criteria is "IETF Review".  Any idea why there is a =
discrepancy?

These three IANA registries require IETF Review.  In fact, that is =
already documented at the two URLs that you provide above.

> Specific comments:
>=20
> Section 2.1, second paragraph:
>=20
>   The allocation and registration functions for all non-reserved AS
>   numbers are handled by the Internet Numbers Registry System in
>   accordance with policies developed by the Regional Internet
>   Registries (RIRs).
>=20
> I might suggest:
>=20
> "The allocation and registration functions for all non-reserved AS =
numbers are currently handled by the Internet Numbers Registry System in =
accordance with policies developed via the Regional Internet Registries' =
(RIRs) public policy development processes."

Okay.  I added "public policy development processes" to the end of the =
sentence.

> Section 2.2, first paragraph:
>=20
>   The allocation and registration functions for all non-reserved
>   globally unique unicast IPv4 unicast addresses are handled by the
>   Internet Numbers Registry System in accordance with policies
>   developed by the Regional Internet Registries (RIRs).
>=20
> Similar to the previous suggestion (dropping a redundant 'unicast'):
>=20
> "The allocation and registration functions for all non-reserved =
globally unique unicast IPv4 addresses are currently handled by the =
Internet Numbers Registry System in accordance with policies developed =
via the RIRs' public policy development processes."

Okay. I dropped the duplicate "unicast."  I added "public policy =
development processes" to the end of the sentence.

> Section 2.3, second paragraph:
>=20
>   The allocation and registration functions for all non-reserved
>   globally unique unicast IPv6 unicast addresses are handled by the
>   Internet Numbers Registry System in accordance with policies
>   developed by the Regional Internet Registries (RIRs).
>=20
> Similar to the previous suggestion (also dropping a redundant =
'unicast'):
>=20
> "The allocation and registration functions for all non-reserved =
globally unique unicast IPv6 addresses are currently handled by the =
Internet Numbers Registry System in accordance with policies developed =
via the RIRs' public policy development processes."

Okay. I dropped the duplicate "unicast."  I added "public policy =
development processes" to the end of the sentence.

> Section 3:
>=20
> The parenthetical "(e.g., anycast)" may be a bit confusing/ambiguous.  =
What most people today think of anycast (i.e., "shared unicast") don't =
generally need to be treated specially by the Internet Numbers Registry =
System or the IETF.  I'd recommend just dropping the parenthetical.

This section is completely replaced with the establishment of the =
special-purpose AS number registry.

> Section 4:
>=20
> While the statement there is truthful, perhaps should there be some =
mention of the potential implications of reserved space in the context =
of trying to identify sources of badness that are using reserved =
addresses or ASes?  E.g., perhaps recommending that care should be taken =
by operators to ensure that traffic sourced and/or destined to reserved =
addresses/ASNs is appropriate?

How about:

Network operators should take care that special-purpose numbers and
addresses are used on the public Internet in a manner that is consistent
with their reserved purpose.

Russ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlLj3y8ACgkQiuTu0PWcEcs+nACgiuaf753yizBeTJlXMUxLuw98
f3gAn2/A/rVLdg+Hic5fbGzSeLcNtXxW
=3DdmaF
-----END PGP SIGNATURE-----

From housley@vigilsec.com  Sat Jan 25 08:23:21 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C82C11A03CA for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PCDTxbRq7zod for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:23:19 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id E0B941A03DC for <ietf@ietf.org>; Sat, 25 Jan 2014 08:23:15 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 769239A42B7; Sat, 25 Jan 2014 11:23:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id 4ic1vrvaYfdX; Sat, 25 Jan 2014 11:22:43 -0500 (EST)
Received: from [192.168.2.106] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 76DDC9A42BB; Sat, 25 Jan 2014 11:22:43 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=windows-1252
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <F0D5C88C-3391-4539-AB36-C45FECC71A10@sobco.com>
Date: Sat, 25 Jan 2014 11:21:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2E5837DE-982C-4300-90D1-CA4AC6864416@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <F0D5C88C-3391-4539-AB36-C45FECC71A10@sobco.com>
To: Scott O Bradner <sob@sobco.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 16:23:22 -0000

Scott:

Others have made a similar suggestion.  I think it might be better to =
point to the IANA registry, instead of the RFC that created the =
registry.  In addition, this document can create a registry for =
special-purpose AS numbers.

Russ



On Dec 16, 2013, at 2:09 PM, Scott O Bradner wrote:

> I=92m not sure it is helpful to have the special use IPv4 address in =
more than one RFC
>=20
> i.e., why not just point to RFC 6890 rather than reproduce it?
>=20
> and if there is a reason to make a new one then this doc should =
unambiguously obsolete RFC 6890
>=20
> Scott
>=20
> On Dec 16, 2013, at 12:55 PM, The IESG <iesg-secretary@ietf.org> =
wrote:
>=20
>>=20
>> The IESG has received a request from an individual submitter to =
consider
>> the following document:
>> - 'Internet Numbers Registries'
>> <draft-housley-number-registries-02.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 2014-01-22. Exceptionally, comments =
may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>  RFC 7020 provides information about the Internet Numbers Registry
>>  System and how it is used in the distribution of autonomous system
>>  (AS) numbers and globally unique unicast Internet Protocol (IP)
>>  address space.
>>=20
>>  This companion document identifies the IANA registries that are part
>>  of the Internet Numbers Registry System at this time.
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-housley-number-registries/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-housley-number-registries/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>=20


From housley@vigilsec.com  Sat Jan 25 08:39:37 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 070071A03BF for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbLEIAKLBTq8 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 08:39:35 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id CF3741A034E for <ietf@ietf.org>; Sat, 25 Jan 2014 08:39:35 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 6071E9A42BB; Sat, 25 Jan 2014 11:39:24 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id hCYoS47+-rqI; Sat, 25 Jan 2014 11:39:03 -0500 (EST)
Received: from [192.168.2.106] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 883FD9A42B7; Sat, 25 Jan 2014 11:39:03 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <07d701cf1547$782166f0$686434d0$@olddog.co.uk>
Date: Sat, 25 Jan 2014 11:38:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk>
To: <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1085)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 16:39:37 -0000

Adrian:

> Section 2.1 says...
>=20
>   Reservations of special-purpose AS Numbers are made through Internet
>   Standards actions.
>=20
> Section 2.2 says...
>=20
>   Reservation of special-purpose IPv4 addresses are made through
>   Internet Standards actions.
>=20
> Section 2.3 says...
>=20
>   Reservation of special-purpose IPv6 addresses are made through
>   Internet Standards actions.
>=20
> Section 3 says...
>=20
>   "IETF Review" as defined in [RFC5226] is required to reserve =
special-
>   purpose AS numbers, IPv4 addresses, or IPv6 addresses.
>=20

I will post -03 soon.  It uses "IETF Review" throughout.

> 1. 2.1, 2.2, and 2.3 should have a reference to 5226

Fixed.

> 2. Section 3 contradicts 2.1, 2.2, and 2.3.

Fixed.

> 3. Why is Section 3 present since there are no instructions for IANA?

Based on the suggestion from David Conrad, Section 3 now asks IANA to =
establish a registry for special-purpose AS numbers.

Russ


From sm@resistor.net  Sat Jan 25 09:06:21 2014
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B981A002A for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 09:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Udj7PK-BdDK4 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 09:06:19 -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 786791A0027 for <ietf@ietf.org>; Sat, 25 Jan 2014 09:06:19 -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 s0PH67rn009642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 25 Jan 2014 09:06:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1390669577; bh=ZPB/MfyhNeXvZssJaGwFCwFuDhJpQgdeOjgXb6e0fq8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jngxyinCyrvlitV2HKIzxZfb88paLC0IqERWD5tliBF6zuN8PnIGJL5AoaLmV6c6y INwl6ma4hn0RT2BkAGCX4Y2cpDwo16y2/v5qWsbqC0EDQzzv8+rYXLngSywVRlOdxk +yqQ8qRUDLSWZS3B3L8+GWYT1rdTJ490qk21g6sI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1390669577; i=@resistor.net; bh=ZPB/MfyhNeXvZssJaGwFCwFuDhJpQgdeOjgXb6e0fq8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vR5CqFp9sObXmNhSg8moVLK1PBVezT5uJV7q4fOYBU2hGGCPgDbsX+u2b5gSkv4P2 kS1sbFmAOmdYmChnBieRYnhlYABwBFH7RGIekLKKgqGLMJUn1iTG5IOS/mZcOZckRZ yrkp0Sx388+QKvNee7qTTqNNpQ2C9dws1d+omqk0=
Message-Id: <6.2.5.6.2.20140125073037.0acdb198@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Jan 2014 07:33:24 -0800
To: Russ Housley <housley@vigilsec.com>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
In-Reply-To: <BCCB9F8F-32CE-45A5-9ED5-1491254331EB@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <6.2.5.6.2.20131216185842.0c8a6dc8@resistor.net> <BCCB9F8F-32CE-45A5-9ED5-1491254331EB@vigilsec.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 17:06:21 -0000

Hi Russ,
At 06:48 25-01-2014, Russ Housley wrote:
>Thanks for your comments.  I have changed section 1 and section 2 to 
>address them.  Here is the updated text:
>
>1.  Introduction
>
>    In accordance with the IETF-IANA Memorandum of Understanding
>    [RFC2860], RFC 7020 [RFC7020] provides information about the Internet
>    Numbers Registry System and how it is used in the distribution of
>    autonomous system (AS) numbers and globally unique unicast Internet
>    Protocol (IP) address space.
>
>    This companion document identifies the IANA registries that are part
>    of the Internet Numbers Registry System at this time.
>
>2.  Internet Numbers Registries
>
>    Three IANA registries are associated with the Internet Numbers
>    Registry System: AS Numbers, unicast IPv4 Addresses, and unicast IPv6
>    Addresses.  However, in each case, there are special-purpose values,
>    and those special-purpose values are outside the Internet Numbers
>    Registry System.

Thanks for addressing the comments.  I am okay with the above.

Regards,
-sm 


From suzworldwide@gmail.com  Sat Jan 25 11:15:35 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5731A0028; Sat, 25 Jan 2014 11:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XRLU_7Z9UB2Y; Sat, 25 Jan 2014 11:15:34 -0800 (PST)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id C5B131A003C; Sat, 25 Jan 2014 11:15:33 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id i13so5496048qae.13 for <multiple recipients>; Sat, 25 Jan 2014 11:15:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bDUIwPr4w/WEZfUoBGTcpE+LT275dKeAeL9bUb7yK34=; b=gqu0AncOwpwQNJU2zTPRgzAZefS/hlp6my/CyXccoLywvJOwjLktMdkEuHy5VXGe7y u2Noqi/YBRsqvPguBTGvmrVLMzAPaV6/9+r08GWxsiezJ06J0ahPv6ncn8eKfihksGNz r+qaU+XTPa0kjlzV3pvTQejuqLBNC5ItVmKmxY3WsLxabNdaDidbMOTc4ebZ5BazKE15 LsFdBSziDI838ik0kDwjpiioeztZpUA59hrQ7ouFvSyXo6Ym0p0vl6IoT5zS8jok0RIb YKgP+d6yGG3wFXp9fWv+1E7i0uQYfUSY9f6xZvV5EOSYHL/FZ405Kb17Yc6AEorwoczC ChXQ==
X-Received: by 10.224.16.72 with SMTP id n8mr30975013qaa.76.1390677332156; Sat, 25 Jan 2014 11:15:32 -0800 (PST)
Received: from [10.0.0.5] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id i38sm4036446qge.1.2014.01.25.11.15.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 11:15:31 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
Date: Sat, 25 Jan 2014 14:15:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com> <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com>
To: IETF WG Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 19:15:35 -0000

Colleagues,

As a long-time IETF'er and new WG chair, I want a) something I can say =
in the room as part of the opening to a meeting, if only to support =
Cullen's non-idiocy requirement; b) something that will make sense to =
those with the ability/inclination to pay attention to boilerplate; and =
c) something not wrong, for which Pete's requirements sound reasonable =
to me.

It also sounds like Richard's suggested change meets the requirements, =
including the one that encourages us to err on the side of disclosure or =
non-participation.

If we can't agree on that, I'd prefer to revert to the old wording while =
we hash this out, but I really hope more hashing isn't needed.


best,
Suzanne

On Jan 25, 2014, at 9:50 AM, Cullen Jennings (fluffy) <fluffy@cisco.com> =
wrote:

>=20
> John,
>=20
> Point taken and I understand how hard it is to get the right words. =
I=92m not trying to propose exact words as I=92m hoping that someone =
else can come up with something that meets Pete=92s goals of relatively =
short and my goals of not looking like an idiot in some court room.=20
>=20
> Cullen
>=20
>=20
> On Jan 25, 2014, at 7:46 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
>>=20
>>=20
>> --On Saturday, January 25, 2014 14:21 +0000 "Cullen Jennings
>> (fluffy)" <fluffy@cisco.com> wrote:
>>=20
>>> ...
>>>> - By participating here, you've agreed to our rules.
>>>> - You can be recorded.
>>>> - You have to disclose your IPR.
>>>=20
>>> It's this above point that I don't believe is true. I
>>> think the point you need to make is, I think what you need to
>>> say is=20
>>>=20
>>>     "You have to disclose your IPR, or not participate in
>>> the discussion"
>>=20
>> And, of course, this drags us into the precise definition of
>> "participate", an axle around which we've gotten wrapped several
>> times.  In particular,=20
>>=20
>>> I do want to point out that if you truly wanted this short the
>>> total slides would say=20
>>>=20
>>>     "This meeting may be recorded. To be in this meeting you
>>> must agree to the rules in BCP 79. "
>>=20
>> but "to be in this meeting" means that sitting in the room
>> during a WG session constitutes "participation".  I like that
>> definition, but we've been around it several times and my
>> recollection is that I was in the minority.  If "participate"
>> for IPR purposes has any resemblance to "making a Contribution",
>> e.g., opening your mouth, then the above statement is as false
>> as some of those to which you object.
>>=20
>>> ...
>>> The core issue here is that you are making the summary be a
>>> sentence which is not wrong and which people can not and will
>>> not comply with. At that point you toss the whole thing into
>>> questions. People who need to testify in court on patents will
>>> have their credibility undermined by having agreed to this and
>>> then not doing it. You need to come up with a summary is not
>>> wrong even if it is not be complete.
>>=20
>> Yep.  See earlier comments by Brian and myself, but this
>> credibility effect is equally important.
>>=20
>> Perhaps the appropriate short statement might be more like:
>>=20
>> 	"If you are in this room two minutes from now or
>> 	thereafter, you are deemed to have read, understood, and
>> 	agreed to BCP 79.  If you have not read and understood
>> 	it, please leave until after you do."
>> =09
>> I hope that is a joke, but it is short, says nothing false, and
>> doesn't get entangled with terms like "participate".
>>=20
>>> ...
>>=20
>>  john
>>=20
>>=20
>=20


From scott.brim@gmail.com  Sat Jan 25 11:25:44 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB4ED1A002F; Sat, 25 Jan 2014 11:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W-NwtcsVAJAh; Sat, 25 Jan 2014 11:25:44 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id CE8EF1A0028; Sat, 25 Jan 2014 11:25:43 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so5251621oah.31 for <multiple recipients>; Sat, 25 Jan 2014 11:25:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jCSTZYhUafSIeAyvC0oDr0L0+eP3/ZPtBvbmQW0uQPQ=; b=L6LeqWht1ZJh/GG8UCZucMvkVi8HUXmd/OLP6flz1GmsaxOSZ4tXulSkbS1yOZVxAc nr3x4J6PgzMHqeBv2XsoNwZPSXcphLgXGhDVO4CuCxw/Rm/NcAkXokzgMlclnG3jC92n I8LlOr8X7NIs60AgLBCtbeA37Tv9oRJXuGJIPjokwGwXNyWTIt/J3/cRNUhQDJjIDgwr iEugs5E/eixx5VhCiI86nzZrijhCOEY7YIZLbrrPBKVW9/wbWfiEtMGIMEXxj503IN9G aAi00gR03Rw/suQYbH0M6zXozYyFpLQ9CggTGzGGIvnBsWDplRB8FQdm8EdoxGG5QgYd XZ5g==
MIME-Version: 1.0
X-Received: by 10.182.16.33 with SMTP id c1mr17500362obd.4.1390677942212; Sat, 25 Jan 2014 11:25:42 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 25 Jan 2014 11:25:41 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Sat, 25 Jan 2014 11:25:41 -0800 (PST)
In-Reply-To: <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com> <9393741FAF54D30498339914@JcK-HP8200.jck.com> <D8D0971F-57F9-405A-B25D-61F9C88B84EE@cisco.com> <B627AAAB-5F7B-4230-AB9E-99838C0BC63E@gmail.com>
Date: Sat, 25 Jan 2014 14:25:41 -0500
Message-ID: <CAPv4CP9ecuVsNJXo1k0ALAhs8cJQK5ihirAo7aPaqLik4pwLyg@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Scott Brim <scott.brim@gmail.com>
To: Suzanne Woolf <suzworldwide@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04479f93be1e9304f0d070e7
Cc: John C Klensin <john-ietf@jck.com>, wgchairs@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jan 2014 19:25:45 -0000

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

On Jan 25, 2014 2:16 PM, "Suzanne Woolf" <suzworldwide@gmail.com> wrote:
> As a long-time IETF'er and new WG chair, I want a) something I can say in
the room as part of the opening ...

What I did last time I chaired was put up the Note Well and tell everyone
it was important and they should read it; pass out blue sheets; when I came
back, ask if anyone had not read it. I didn't have to turn anyone off by
reading something to them, but I did get to call their attention to it
twice.

Scott

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

<p dir=3D"ltr"><br>
On Jan 25, 2014 2:16 PM, &quot;Suzanne Woolf&quot; &lt;<a href=3D"mailto:su=
zworldwide@gmail.com">suzworldwide@gmail.com</a>&gt; wrote:<br>
&gt; As a long-time IETF&#39;er and new WG chair, I want a) something I can=
 say in the room as part of the opening ...</p>
<p dir=3D"ltr">What I did last time I chaired was put up the Note Well and =
tell everyone it was important and they should read it; pass out blue sheet=
s; when I came back, ask if anyone had not read it. I didn&#39;t have to tu=
rn anyone off by reading something to them, but I did get to call their att=
ention to it twice. </p>

<p dir=3D"ltr">Scott</p>

--f46d04479f93be1e9304f0d070e7--

From adrian@olddog.co.uk  Sat Jan 25 12:14:20 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3C81A0027 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:14:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.13
X-Spam-Level: 
X-Spam-Status: No, score=-1.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wj7pcspki5xV for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:14:19 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id E47EA1A0033 for <ietf@ietf.org>; Sat, 25 Jan 2014 12:14:18 -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 s0PKEFjK007726; Sat, 25 Jan 2014 20:14:15 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0PKECSv007711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 25 Jan 2014 20:14:13 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Russ Housley'" <housley@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com>
In-Reply-To: <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com>
Subject: RE: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Date: Sat, 25 Jan 2014 20:14:11 -0000
Message-ID: <028c01cf1a0a$048899d0$0d99cd70$@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: AQGQWqUAg1FoaRx5MrXXqxtkR3Q4dgFkwopqAbQIw/Sa+pgrUA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Jan 2014 20:14:20 -0000

Hi Russ,

Thanks for this. The -03 revision just posted addresses my comments.

Adrian

> -----Original Message-----
> From: Russ Housley [mailto:housley@vigilsec.com]
> Sent: 25 January 2014 16:39
> To: adrian@olddog.co.uk
> Cc: IETF
> Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet
> Numbers Registries) to Informational RFC
> 
> Adrian:
> 
> > Section 2.1 says...
> >
> >   Reservations of special-purpose AS Numbers are made through Internet
> >   Standards actions.
> >
> > Section 2.2 says...
> >
> >   Reservation of special-purpose IPv4 addresses are made through
> >   Internet Standards actions.
> >
> > Section 2.3 says...
> >
> >   Reservation of special-purpose IPv6 addresses are made through
> >   Internet Standards actions.
> >
> > Section 3 says...
> >
> >   "IETF Review" as defined in [RFC5226] is required to reserve special-
> >   purpose AS numbers, IPv4 addresses, or IPv6 addresses.
> >
> 
> I will post -03 soon.  It uses "IETF Review" throughout.
> 
> > 1. 2.1, 2.2, and 2.3 should have a reference to 5226
> 
> Fixed.
> 
> > 2. Section 3 contradicts 2.1, 2.2, and 2.3.
> 
> Fixed.
> 
> > 3. Why is Section 3 present since there are no instructions for IANA?
> 
> Based on the suggestion from David Conrad, Section 3 now asks IANA to
establish
> a registry for special-purpose AS numbers.
> 
> Russ


From adrian@olddog.co.uk  Sat Jan 25 12:24:30 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 790631A003C for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:24:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.13
X-Spam-Level: 
X-Spam-Status: No, score=-1.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bNq5loExDaqt for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:24:29 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id ADA7E1A0027 for <ietf@ietf.org>; Sat, 25 Jan 2014 12:24:28 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0PKOQLI013578 for <ietf@ietf.org>; Sat, 25 Jan 2014 20:24:26 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0PKOOAI013556 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sat, 25 Jan 2014 20:24:25 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Date: Sat, 25 Jan 2014 20:24:23 -0000
Message-ID: <029b01cf1a0b$707d5c60$51781520$@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: AQFerF+1MVKpbR9CNhjCMYsURGW24pt2vUnw
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 25 Jan 2014 20:24:30 -0000

Hi,

I have a process question on this last call which is not clear from the last
call text.

Are we being asked to consider whether publication of this document is useful,
or are we being asked for IETF consensus on the *content* of the document?

It seems from the document that the content is descriptive of something
implemented by a single vendor. I applaud putting that information into the
public domain, but I don't understand the meaning of IETF consensus with respect
to this document.

Thanks,
Adrian

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 21 January 2014 12:33
> To: IETF-Announce
> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
> Information Elements reused in IPFIX) to Informational RFC
> 
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Cisco Specific Information Elements reused in IPFIX'
>   <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document describes some additional Information Elements of Cisco
>    Systems, Inc. that are not listed in RFC3954.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.



From ron.even.tlv@gmail.com  Sun Jan 26 00:16:30 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE0271A010D; Sun, 26 Jan 2014 00:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AzA0I3lxGfXy; Sun, 26 Jan 2014 00:16:28 -0800 (PST)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 8F8CF1A010C; Sun, 26 Jan 2014 00:16:27 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id d17so1681733eek.36 for <multiple recipients>; Sun, 26 Jan 2014 00:16:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=O8aXxEzj547gHhS2QvvNZQL63A7ZKrMn44kQsRc1wXY=; b=xrrASH8WzplIeptgwit7mNgTmh3W2FuQcpNSYB8sOgpU2XXyesHrdQDR/3InivtcK5 +KXXJJgTQG/TlW9x6Wmvz4+xtNGnKIqPgT2KYE4U4gZbNd3gxoeS8IPMLW36DFaMwv52 YGkqxcZHPVq4etHBbiTtk7T+Jjg5FYsI9rzKwZwj10JBXTjCLwMGslWT3LYAVr34Ffjj u9I1PwWpUsd4DZV6qWlWLfvtrrPm5qgqu1ejNwQnFLMN/6TmgIu9RgLZrTxOmkAZHUwj bvhLp6aqDDsUYOXa6gtV1yVH+UFaE8htGnEdaROEgZ+vaPgTXPrd8Pa35KcblVyieeuL Rj8Q==
X-Received: by 10.14.9.70 with SMTP id 46mr109460ees.102.1390724185298; Sun, 26 Jan 2014 00:16:25 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id z49sm26153432eeo.10.2014.01.26.00.16.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 26 Jan 2014 00:16:24 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-pcp-description-option.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-pcp-description-option-03
Date: Sun, 26 Jan 2014 10:12:38 +0200
Message-ID: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_02DC_01CF1A7F.267563F0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/Q==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jan 2014 08:16:31 -0000

This is a multipart message in MIME format.

------=_NextPart_000_02DC_01CF1A7F.267563F0
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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

 

1.       I am not sure what the use of the "description" option is. I can
see how to create one but as for usage the only text I can see is "Querying
the PCP server to get the description text of an existing mapping is out of
scope." I think that the document should provide information about the
purpose of this option.

 

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options 

 


------=_NextPart_000_02DC_01CF1A7F.267563F0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><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:&n=
bsp; </span><span style=3D'font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;1-26<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: 2014&#8211;2-4<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is almost ready for publication as a standard track =
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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>I am not =
sure what the use of the &#8220;description&#8221; option is. I can see =
how to create one but as for usage the only text I can see is =
&#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Querying =
the PCP server to get the description text of an existing mapping is out =
of scope.&#8221; I think that the document should provide information =
about the purpose of this option.</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=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:l1 level1 lfo2'>The =
IANA section should provide enough information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_02DC_01CF1A7F.267563F0--


From ned+ietf@mauve.mrochek.com  Sun Jan 26 15:13:53 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674141A015C for <ietf@ietfa.amsl.com>; Sun, 26 Jan 2014 15:13:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wROdXVMQDQIV for <ietf@ietfa.amsl.com>; Sun, 26 Jan 2014 15:13:51 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id C8DFC1A015B for <ietf@ietf.org>; Sun, 26 Jan 2014 15:13:51 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3M48I2WOW003GG2@mauve.mrochek.com> for ietf@ietf.org; Sun, 26 Jan 2014 15:08:44 -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 <01P2SI6PLQJK0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 26 Jan 2014 15:08:36 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P3M48DZNS80000AS@mauve.mrochek.com>
Date: Sun, 26 Jan 2014 14:45:47 -0800 (PST)
Subject: Re: Problem with new Note Well
In-reply-to: "Your message dated Sat, 25 Jan 2014 08:19:26 -0500" <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jan 2014 23:13:53 -0000

> --On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:

> > It's quite obvious from reading this thread that the IAOC needs
> > to revert to the previous Note Well text right now, until the
> > wording issue is resolved.
> >
> > It is apparent to me though that the BCP *requires* disclosure
> > as a condition of participation, regardless of employment
> > agreements, and always has done. That's why there has always
> > been tolerance extended to allow corporate IPR departments to
> > have time to prepare and make disclosures at lawyerly speed.
> > Nothing new here except the more brutal wording.

Nonsense. The BCP is careful to make it clear that you're obliged to
dislose your IPR when you're contributing.

The Note Well grossly misprepresents the BCP by talking about any contribution
and any IPR without qualification. This is incorrect in two ways: It conflates
contributions in general with someone acting in the role of a contributor, and
it fails to distingish between "your" IPR and third party IPR. 

The wording is not brutal, or as others have claimed, overly broad. It's sloppy
and wrong.

And I'm far more worried about 3rd party IPR here. BCP 79 section 6.1.3 makes
disclosure of that a MAY. (The exact word used is "encouraged".) This languages
makes it a MUST. Would we tolerate a MUST where a MAY is needed in any other
context, even with an "exceptions may apply" disclaimer attached? I think not.

> Agreed.  Noting that the likely effect of "regardless of
> employment agreements" if there really is a conflict in a
> particular company-participant relations is "don't participate
> in that" under the BCP and "don't attend" if the wording is more
> brutal, we should have a lot of incentive to clean the language
> up... and go back to the tested language until a cleaned-up
> version is ready.

Mandating disclosure of 3rd party IPR drags in a whole lot more than employment
contracts.

				Ned

From john-ietf@jck.com  Sun Jan 26 15:24:51 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9EE91A0169; Sun, 26 Jan 2014 15:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0kICEHxdElsE; Sun, 26 Jan 2014 15:24:50 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 36ADE1A0092; Sun, 26 Jan 2014 15:24:50 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W7Z4B-000AkQ-6r; Sun, 26 Jan 2014 18:24:39 -0500
X-Vipre-Scanned: 0536E268002C310536E3B5-TDI
Date: Sun, 26 Jan 2014 18:24:37 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
Message-ID: <9244D7CE10A93EC07BBD46C6@[192.168.1.128]>
In-Reply-To: <01P3M48DZNS80000AS@mauve.mrochek.com>
References: <01P3M48DZNS80000AS@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jan 2014 23:24:52 -0000

--On Sunday, 26 January, 2014 14:45 -0800 Ned Freed
<ned.freed@mrochek.com> wrote:

>...
>> Agreed.  Noting that the likely effect of "regardless of
>> employment agreements" if there really is a conflict in a
>> particular company-participant relations is "don't participate
>> in that" under the BCP and "don't attend" if the wording is
>> more brutal, we should have a lot of incentive to clean the
>> language up... and go back to the tested language until a
>> cleaned-up version is ready.
> 
> Mandating disclosure of 3rd party IPR drags in a whole lot
> more than employment contracts.

Of course.  And some of what gets dragged in is, or may be, more
important than the employment contracts.  I was just responding
to Brian's specific point and trying to suggest that "regardless
of employment agreements" was really not something one could say
if an open, broadly representative, IETF was part of one's
target.

I agree about "sloppy and wrong" too.

best,
   john





From david.black@emc.com  Sun Jan 26 18:07:12 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 806981A0177; Sun, 26 Jan 2014 18:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYbdt8fMIrWX; Sun, 26 Jan 2014 18:07:10 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id DC25E1A017F; Sun, 26 Jan 2014 18:07:09 -0800 (PST)
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0R272eN009869 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jan 2014 21:07:04 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0R272eN009869
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390788424; bh=NTNbS+noRA1hBvvbiBuOg2FrqTY=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=rY2IROtckpBIBAobnn1MktvIui+paBtFv70Frg6GtgN14Y+ikpSrasrkCvH8Y9/EU fME+qFSf4485+KN9dVCGs2sT+jLcTU6Kld4rv5z+nmiDsMy7h3wOX1OYTLoocBuzTU v2ylUXkxXwLIuhBCeXwq3QeeB6a6vCJ8to6Kwtjg=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0R272eN009869
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd52.lss.emc.com (RSA Interceptor); Sun, 26 Jan 2014 21:06:56 -0500
Received: from mxhub12.corp.emc.com (mxhub12.corp.emc.com [10.254.92.107]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0R26tat031811 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 26 Jan 2014 21:06:56 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub12.corp.emc.com ([10.254.92.107]) with mapi; Sun, 26 Jan 2014 21:06:54 -0500
From: "Black, David" <david.black@emc.com>
To: "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>,  "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Sun, 26 Jan 2014 21:06:53 -0500
Subject: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bBHAYj1adCBYhQu2KINJ+hxA0mA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public, Resumes
Cc: "Black, David" <david.black@emc.com>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 02:07:12 -0000

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

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

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

Document: draft-ietf-qresync-rfc5162bis-09
Reviewer: David L. Black
Review Date: January 26, 2014
IETF LC End Date: January 27, 2014

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

This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
(IMAP Quick Mailbox Resynchronization) into a single document and makes
a few minor updates.  It also updates the command line length
recommendation in RFC 2683 to support the longer command lines that
can occur with these extensions.

As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
they look reasonable.  I found one minor issue that should be relatively
easy to address.

Minor Issues:

The command line length change in Section 4 applies to all IMAP commands,
and hence affects old servers, including those that don't implement either
of the extensions in this draft. That raises a backwards compatibility
concern - what happens when a new client sends a > 1000 character command
line to an old server that isn't expecting more than 1000 characters?

One possibility would be to apply the larger length recommendation only
after the client determines that the server supports at least one of
these extensions.

Nits/editorial comments:

The update to RFC 2683 would be easier to find from the table of contents
if the title of Section 4 were changed to "Long Command Lines (Update to
RFC 2683)".

idnits 2.13.01 got confused by the command line examples, and flagged a
downref:

  ** Downref: Normative reference to an Informational RFC: RFC 2683

That downref appears to be ok and intended, as noted in the shepherd's
writeup.

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


From brian.e.carpenter@gmail.com  Sun Jan 26 20:53:02 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87631A01A2; Sun, 26 Jan 2014 20:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGgCnZXUx450; Sun, 26 Jan 2014 20:53:01 -0800 (PST)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F22D21A0185; Sun, 26 Jan 2014 20:53:00 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id w10so5225519pde.6 for <multiple recipients>; Sun, 26 Jan 2014 20:52:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=aLWwR9IVxGi4lfaRwL7E8JDVajiOIvjC/utSUvyvB54=; b=osssolj4t+hKyTHXV2DJOxhBR6pmA0LQhMKGIBDC7hmtKAPOKeRLmGdChsj7fIsI2p AU/tBsT55eESOXPDSOGfs2yimIa8r4pAqIuGzc3ZqOF2oZKF+a/7MqHrX5kUqtRw66vX 69TNH8Ft3W3E9jsxk3Q6+HOKheRWSontVWClMDoC3dUD9oqI6lFVuzz50ppJN0AmEDYp iulm3fOoG/kKaz3p1px3vBvI9FVYUFZDJcEVoPgs7eFWXpqgaEiTxP9OH5ZgVhG+/oDy Y1uRs70YtdYnti+wqy17CvQiUIUfkA3SrOE8bokaUGBHgdwmk4eP9FgXoeF3x8qJEQxL 4ZJw==
X-Received: by 10.68.195.4 with SMTP id ia4mr1015652pbc.142.1390798378991; Sun, 26 Jan 2014 20:52:58 -0800 (PST)
Received: from [192.168.178.23] (100.199.69.111.dynamic.snap.net.nz. [111.69.199.100]) by mx.google.com with ESMTPSA id iu7sm27511270pbc.45.2014.01.26.20.52.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Jan 2014 20:52:58 -0800 (PST)
Message-ID: <52E5E624.4080003@gmail.com>
Date: Mon, 27 Jan 2014 17:52:52 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com>
In-Reply-To: <01P3M48DZNS80000AS@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Scott Bradner <sob@harvard.edu>, IESG IESG <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, Mary Barnes <mary.ietf.barnes@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 04:53:02 -0000

On 27/01/2014 11:45, Ned Freed wrote:
>> --On Saturday, January 25, 2014 16:41 +1300 Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
> 
>>> It's quite obvious from reading this thread that the IAOC needs
>>> to revert to the previous Note Well text right now, until the
>>> wording issue is resolved.
>>>
>>> It is apparent to me though that the BCP *requires* disclosure
>>> as a condition of participation, regardless of employment
>>> agreements, and always has done. That's why there has always
>>> been tolerance extended to allow corporate IPR departments to
>>> have time to prepare and make disclosures at lawyerly speed.
>>> Nothing new here except the more brutal wording.
> 
> Nonsense. The BCP is careful to make it clear that you're obliged to
> dislose your IPR when you're contributing.

Yes. I should have written "as a condition of contribution". Sorry.

Anyway - same conclusion, we should use the old wording until
the new wording has been corrected.

    Brian

> 
> The Note Well grossly misprepresents the BCP by talking about any contribution
> and any IPR without qualification. This is incorrect in two ways: It conflates
> contributions in general with someone acting in the role of a contributor, and
> it fails to distingish between "your" IPR and third party IPR. 
> 
> The wording is not brutal, or as others have claimed, overly broad. It's sloppy
> and wrong.
> 
> And I'm far more worried about 3rd party IPR here. BCP 79 section 6.1.3 makes
> disclosure of that a MAY. (The exact word used is "encouraged".) This languages
> makes it a MUST. Would we tolerate a MUST where a MAY is needed in any other
> context, even with an "exceptions may apply" disclaimer attached? I think not.
> 
>> Agreed.  Noting that the likely effect of "regardless of
>> employment agreements" if there really is a conflict in a
>> particular company-participant relations is "don't participate
>> in that" under the BCP and "don't attend" if the wording is more
>> brutal, we should have a lot of incentive to clean the language
>> up... and go back to the tested language until a cleaned-up
>> version is ready.
> 
> Mandating disclosure of 3rd party IPR drags in a whole lot more than employment
> contracts.
> 
> 				Ned
> 

From drc@virtualized.org  Sun Jan 26 23:08:38 2014
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4CF11A01D0 for <ietf@ietfa.amsl.com>; Sun, 26 Jan 2014 23:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dykhPcUVO0WR for <ietf@ietfa.amsl.com>; Sun, 26 Jan 2014 23:08:36 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 7906E1A01CF for <ietf@ietf.org>; Sun, 26 Jan 2014 23:08:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 34FDF84B43; Mon, 27 Jan 2014 02:08:33 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 87643-06; Mon, 27 Jan 2014 02:08:32 -0500 (EST)
Received: from [10.0.1.3] (c-67-169-100-133.hsd1.ca.comcast.net [67.169.100.133]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 14ACA84B42; Mon, 27 Jan 2014 02:08:31 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_116B9FE7-3E1C-44E3-B6B0-864F661EB36B"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <BF378B80-A687-4014-8DAE-0A71E8154716@vigilsec.com>
Date: Sun, 26 Jan 2014 23:08:29 -0800
Message-Id: <F0B0C22E-08CA-4503-ACFB-5F588FE7A322@virtualized.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <6.2.5.6.2.20131216121747.0cc284d8@resistor.net> <36FB4FC7-0E97-4BE1-BFFE-394DF406DB3D@vigilsec.com> <BF91FE26-DAD6-4565-A7EB-2A1E3714A862@virtualized.org> <BF378B80-A687-4014-8DAE-0A71E8154716@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.1827)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 07:08:39 -0000

--Apple-Mail=_116B9FE7-3E1C-44E3-B6B0-864F661EB36B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Russ,

On Jan 25, 2014, at 7:58 AM, Russ Housley <housley@vigilsec.com> wrote:
>> Perhaps it would make more sense to reference IANA registries instead =
of listing the contents of what would be in those registries in the =
draft text
> I think this is a good idea.  It required a fairly significant update =
to the document.  I did it in version -03.

Works for me.

>> I find it curious that when talking about top-level domains, the =
criteria (according to RFC 6761) for reservation is "Standards Action" =
or "IESG Approval" but when talking about reserving Internet Number =
resources, the criteria is "IETF Review".  Any idea why there is a =
discrepancy?
> These three IANA registries require IETF Review.  In fact, that is =
already documented at the two URLs that you provide above.

Right. The thing I found curious was that special numbers get "IETF =
Review" whereas special names get "Standards Action" or "IESG Approval". =
 This isn't really a comment on your draft per se, just confusion about =
the discrepancy in treatment between these identifiers.

>> "The allocation and registration functions for all non-reserved AS =
numbers are currently handled by the Internet Numbers Registry System in =
accordance with policies developed via the Regional Internet Registries' =
(RIRs) public policy development processes."
> Okay.  I added "public policy development processes" to the end of the =
sentence.

As Geoff identified, the bit I was more focused on was the "currently", =
however this is a nit I can probably avoid picking.

> How about:
>=20
> Network operators should take care that special-purpose numbers and
> addresses are used on the public Internet in a manner that is =
consistent
> with their reserved purpose.

Works for me.

Thanks!

Regards,
-drc


--Apple-Mail=_116B9FE7-3E1C-44E3-B6B0-864F661EB36B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJS5gXtAAoJENV6ebf0/4rXVOwIAJzYa1U1QTFu8TLnRCxCH7YD
t5VExTQhzKj8m2eICwKI6mNpIPyqGCxUvAFYW94qHtvHZ6sSIw1oDUxZbUKyFayR
GO65AM7R3s+oGHgHIGCxg4WSND01p7jupVf9tHva1iKFsxexalF14bYSHD0nGu4t
C/IloWfJI8XxSXMTDJJGAotXlhQ4YF6CYQlo49QD1sF3yXL55NIetqH5ZIbohUDV
Y6vXQW0GywEkYGx8BhPJ0/AJnfnpVqsc/Vwn2RLrCoaD/rVRWY2dxfg3wVND4gdx
vfAvStKVLVRvPOGdOzrQMvFnAcESMvOMG6lJ0L5A2Jaw6lVztoD2q9FtsJcJ0Ok=
=I1ho
-----END PGP SIGNATURE-----

--Apple-Mail=_116B9FE7-3E1C-44E3-B6B0-864F661EB36B--

From mohamed.boucadair@orange.com  Mon Jan 27 00:31:15 2014
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB1061A002E; Mon, 27 Jan 2014 00:31:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.548
X-Spam-Level: 
X-Spam-Status: No, score=-0.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNLgauZmPdZH; Mon, 27 Jan 2014 00:31:12 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias245.francetelecom.com [80.12.204.245]) by ietfa.amsl.com (Postfix) with ESMTP id F023E1A0111; Mon, 27 Jan 2014 00:31:11 -0800 (PST)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda09.si.francetelecom.fr (ESMTP service) with ESMTP id 0CD34C04F7; Mon, 27 Jan 2014 09:31:09 +0100 (CET)
Received: from PUEXCH71.nanterre.francetelecom.fr (unknown [10.101.44.33]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id DA2DEC804B; Mon, 27 Jan 2014 09:31:08 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH71.nanterre.francetelecom.fr ([10.101.44.33]) with mapi; Mon, 27 Jan 2014 09:31:08 +0100
From: <mohamed.boucadair@orange.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Date: Mon, 27 Jan 2014 09:31:06 +0100
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/QAyx66A
Message-ID: <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
In-Reply-To: <02db01cf1a6e$62eb8280$28c28780$@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 08:31:16 -0000
X-List-Received-Date: Mon, 27 Jan 2014 08:31:16 -0000

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

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the "description" option is. I can s=
ee how to create one but as for usage the only text I can see is "Querying =
the PCP server to get the description text of an existing mapping is out of=
 scope." I think that the document should provide information about the pur=
pose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text "   This option can be used by a u=
ser (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

"


Nits/editorial comments:

 1.  The IANA section should provide enough information to fill the registr=
y http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.


--_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"Texte brut Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#1F497D;}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1837839053;
	mso-list-template-ids:1556752032;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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;line-height:115%;font-family:"Courier New";color:#1F497D'>D=
ear Roni,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-siz=
e:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'>Thank yo=
u for the review. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'=
>Please see inline.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#1F49=
7D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;line-height:115%;font-family:"Courier New";color:#1F497D'>Med<o:=
p></o:p></span></p><div style=3D'border:none;border-left:solid blue 1.5pt;p=
adding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:solid #=
B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D'margi=
n-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><span lang=3DFR s=
tyle=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</span=
></b><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Tahoma","sans-s=
erif"'> Roni Even [mailto:ron.even.tlv@gmail.com] <br><b>Envoy=E9&nbsp;:</b=
> dimanche 26 janvier 2014 09:13<br><b>=C0&nbsp;:</b> draft-ietf-pcp-descri=
ption-option.all@tools.ietf.org<br><b>Cc&nbsp;:</b> ietf@ietf.org; gen-art@=
ietf.org<br><b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-descrip=
tion-option-03<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span =
lang=3DFR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><a name=3D"OLE_L=
INK2"></a><a name=3D"OLE_LINK1"></a>I am the assigned Gen-ART reviewer for =
this draft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D=
"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank"=
>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p=
></p><p class=3DMsoNormal>Please resolve these comments along with any othe=
r 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"'>Docume=
nt:&nbsp; </span><span style=3D'font-family:"Courier New"'>draft-ietf-pcp-d=
escription-option-03<o:p></o:p></span></p><p class=3DMsoPlainText><span sty=
le=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: Roni E=
ven<o:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:1=
1.0pt;font-family:"Calibri","sans-serif"'>Review Date:2014&#8211;1-26<o:p><=
/o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;fon=
t-family:"Calibri","sans-serif"'>IETF LC End Date: 2014&#8211;2-4<o:p></o:p=
></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fa=
mily:"Calibri","sans-serif"'>IESG Telechat date: <o:p></o:p></span></p><p c=
lass=3DMsoPlainText><span style=3D'font-size:11.0pt;font-family:"Calibri","=
sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoPlainText><span styl=
e=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: This dra=
ft is almost ready for publication as a standard track RFC.<o:p></o:p></spa=
n></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>&n=
bsp;</o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0p=
t;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 st=
yle=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor issues:<o=
:p></o:p></span></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt=
;font-family:"Calibri","sans-serif"'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoPlainText style=3D'margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0=
 level1 lfo2'><![if !supportLists]><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif"'><span style=3D'mso-list:Ignore'>1.<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </sp=
an></span></span><![endif]><span style=3D'font-size:11.0pt;font-family:"Cal=
ibri","sans-serif"'>I am not sure what the use of the &#8220;description&#8=
221; option is. I can see how to create one but as for usage the only text =
I can see is &#8220;Querying the PCP server to get the description text of =
an existing mapping is out of scope.&#8221; I think that the document shoul=
d provide information about the purpose of this option.<o:p></o:p></span></=
p><pre><b><i><span style=3D'color:#1F497D'>[Med] The main usage is for a us=
er to associate a textual description with a mapping. This is captured by t=
his text &#8220;</span></i></b>=A0=A0 This option can be used by a user (or=
 an application) to indicate a<o:p></o:p></pre><p class=3DMsoNormal style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'>=A0=A0 description associat=
ed with a given mapping such as &quot;FTP server&quot;, &quot;My<o:p></o:p>=
</span></p><p class=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0=
001pt;line-height:normal'><span style=3D'font-size:10.0pt;font-family:"Cour=
ier New"'>=A0=A0 remote access to my CP router&quot;, &quot;Camera&quot;, &=
quot;Network attached storage<o:p></o:p></span></p><p class=3DMsoNormal sty=
le=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span sty=
le=3D'font-size:10.0pt;font-family:"Courier New"'>=A0=A0 serve&quot;, etc.<=
o:p></o:p></span></p><p class=3DMsoPlainText><b><i><span style=3D'font-size=
:10.0pt;font-family:"Courier New";color:#1F497D'>&#8221;<o:p></o:p></span><=
/i></b></p><p class=3DMsoPlainText><span style=3D'font-size:11.0pt;font-fam=
ily:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p cl=
ass=3DMsoNormal>Nits/editorial comments:<o:p></o:p></p><ol style=3D'margin-=
top:0cm' start=3D1 type=3D1><li class=3DMsoNormal style=3D'mso-list:l1 leve=
l1 lfo5'>The IANA section should provide enough information to fill the reg=
istry <a href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-paramet=
ers.xml#options">http://www.iana.org/assignments/pcp-parameters/pcp-paramet=
ers.xml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span s=
tyle=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#=
1F497D'>[Med] Required information as per RFC6887 is provided in <a href=3D=
"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2"=
>http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2<=
/a>. </span></i></b><span style=3D'font-size:10.0pt;line-height:115%;font-f=
amily:"Courier New";color:#1F497D'><o:p></o:p></span></p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36F4736082CPUEXCB1Bnante_--

From lars@netapp.com  Mon Jan 27 01:20:09 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 908EC1A0169 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 01:20:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Q_NOrziZnRL for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 01:20:08 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 31AA81A0163 for <ietf@ietf.org>; Mon, 27 Jan 2014 01:20:08 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,728,1384329600";  d="asc'?scan'208";a="98290286"
Received: from vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) by mx11-out.netapp.com with ESMTP; 27 Jan 2014 01:20:06 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.03.0123.003; Mon, 27 Jan 2014 01:20:06 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Topic: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Index: AQHPFqUWbHitS8PQ2U61HYhCH0Ib05qWb7CAgAJrBQA=
Date: Mon, 27 Jan 2014 09:20:04 +0000
Message-ID: <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk>
In-Reply-To: <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_28E1AA3C-B390-4A7A-A280-DAAE716D3708"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:20:09 -0000

--Apple-Mail=_28E1AA3C-B390-4A7A-A280-DAAE716D3708
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2014-1-25, at 21:24, Adrian Farrel <adrian@olddog.co.uk> wrote:
> It seems from the document that the content is descriptive of =
something
> implemented by a single vendor. I applaud putting that information =
into the
> public domain, but I don't understand the meaning of IETF consensus =
with respect
> to this document.

+1

The Independent RFC Stream would seem more appropriate.

Lars

--Apple-Mail=_28E1AA3C-B390-4A7A-A280-DAAE716D3708
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuYkvNZcnpRveo1xAQJHZQQAhZDlmgrgW+TfhvXIkOpHQ3rP7XHcXkty
IUk6yGTesO7Lt1LS3Hhtim684ok51Caxqzmj4EWm6EbwF9FfSvM8yx+1WyYSOFYJ
zWMGVqyOW/ywPJpnD1ei2HYLNlqJ3xqomNuGuZFxBwlns7N8AyOgCF+/Ks+m7s81
fGlDIXbCvIM=
=9fCu
-----END PGP SIGNATURE-----

--Apple-Mail=_28E1AA3C-B390-4A7A-A280-DAAE716D3708--

From ron.even.tlv@gmail.com  Mon Jan 27 01:35:04 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C1A1A011C; Mon, 27 Jan 2014 01:35:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHW3abtXXyK3; Mon, 27 Jan 2014 01:35:01 -0800 (PST)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ED5FD1A0117; Mon, 27 Jan 2014 01:35:00 -0800 (PST)
Received: by mail-ea0-f170.google.com with SMTP id k10so2158064eaj.15 for <multiple recipients>; Mon, 27 Jan 2014 01:34:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:thread-index:content-language; bh=+S8C2s6/5BP+rxt5uSY2LO/pOQpHBE7+wBsaMf6Dvb4=; b=MGGEpDsocD/kKDZg8xNqzj+U7OndgZ5O8Oe4Y/VvNDhMouODwJ14dNECCVVzGLvjZf sc+meBMwjCAXkkC/MZsttdauerUtxplw9KCQpt+/1sNcNW8uIZ/EzO1qsgKBzkuRup28 cRDzHyxqKn81zLtiuFGf27K730pW5FvLRY9VPXO+l/ZBq5ZlgVHnF9cu8uX4nj9ZhSh8 g4PwHwSeUwssPjZQ0C1jlSOT8dWBpgVB6HXm3JwDM0lxA7ErQBt+MBns+KNlZF8TjDv1 Bb0zne/Ba/hxmlxIzEy5D++Ci/PVqprdMixognvBWpd95MBP3aGOi62F79jkGTHIxR33 jOdA==
X-Received: by 10.14.95.2 with SMTP id o2mr20122125eef.69.1390815298175; Mon, 27 Jan 2014 01:34:58 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id o13sm40083434eex.19.2014.01.27.01.34.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 01:34:57 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Date: Mon, 27 Jan 2014 11:31:08 +0200
Message-ID: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_033E_01CF1B53.48D64070"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDmy6g4DA=
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:35:05 -0000

This is a multipart message in MIME format.

------=_NextPart_000_033E_01CF1B53.48D64070
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Med,=20

Inline

Roni

=20

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

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

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

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_033E_01CF1B53.48D64070
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:2105032897;
	mso-list-template-ids:-1035336528;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =
<br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> Roni Even; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I =
am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Reviewer: Roni =
Even<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Review =
Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IESG Telechat date: =
<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Summary: This draft is =
almost ready for publication as a standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>I am not sure what the =
use of the &#8220;description&#8221; option is. I can see how to create =
one but as for usage the only text I can see is &#8220;Querying the PCP =
server to get the description text of an existing mapping is out of =
scope.&#8221; I think that the document should provide information about =
the purpose of this option.<o:p></o:p></p><pre><b><i><span =
style=3D'color:#1F497D'>[Med] The main usage is for a user to associate =
a textual description with a mapping. This is captured by this text =
&#8220;</span></i></b>&nbsp;&nbsp; This option can be used by a user (or =
an application) to indicate a<o:p></o:p></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
description associated with a given mapping such as &quot;FTP =
server&quot;, &quot;My<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network =
attached storage<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
serve&quot;, etc.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'><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:l1 level1 lfo5'>The IANA section should provide enough =
information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. <o:p></o:p></span></i></b></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_033E_01CF1B53.48D64070--


From mohamed.boucadair@orange.com  Mon Jan 27 01:55:16 2014
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BE71A0184; Mon, 27 Jan 2014 01:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.548
X-Spam-Level: 
X-Spam-Status: No, score=-1.548 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gskwMuUXJ2KZ; Mon, 27 Jan 2014 01:55:13 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id D13381A011C; Mon, 27 Jan 2014 01:55:12 -0800 (PST)
Received: from omfeda08.si.francetelecom.fr (unknown [xx.xx.xx.201]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id EF4432AC68D; Mon, 27 Jan 2014 10:55:09 +0100 (CET)
Received: from PUEXCH81.nanterre.francetelecom.fr (unknown [10.101.44.34]) by omfeda08.si.francetelecom.fr (ESMTP service) with ESMTP id CE590384078; Mon, 27 Jan 2014 10:55:09 +0100 (CET)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.9]) by PUEXCH81.nanterre.francetelecom.fr ([10.101.44.34]) with mapi; Mon, 27 Jan 2014 10:55:09 +0100
From: <mohamed.boucadair@orange.com>
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Date: Mon, 27 Jan 2014 10:55:07 +0100
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDmy6g4DCAAAX/8A==
Message-ID: <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
In-Reply-To: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2013.11.19.63615
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:55:16 -0000

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

Re-,
The description is used by the entity managing the PCP server. The document=
 does not elaborate on such usage as this is deployment-specific: e.g.,  (1=
) it can be used as  helper to clean the mapping table, (2) in some deploym=
ents that make use of a portal to instruct pcp mappings, this option can be=
 used to store a subscriber-identifier, etc. We can add some text if you th=
ink this is useful to be mentioned in the document.
For the second point, I updated Section 5 with a pointer to Section 2. Than=
ks.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : lundi 27 janvier 2014 10:31
=C0 : BOUCADAIR Mohamed IMT/OLN; draft-ietf-pcp-description-option.all@tool=
s.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Hi Med,
Inline
Roni

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:=
draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:draft-iet=
f-pcp-description-option.all@tools.ietf.org>
Cc : ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@i=
etf.org>
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014-1-26

IETF LC End Date: 2014-2-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the "description" option is. I can s=
ee how to create one but as for usage the only text I can see is "Querying =
the PCP server to get the description text of an existing mapping is out of=
 scope." I think that the document should provide information about the pur=
pose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text "   This option can be used by a u=
ser (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

"

[Roni Even] This is motivation but it is not clear why the user does it if =
no one can see it or does anything with it. It is kept on the server but no=
t used by anyone?


Nits/editorial comments:

 1.  The IANA section should provide enough information to fill the registr=
y http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.
[Roni Even] So section 5 should point to the definition is section 2



--_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-1"><meta name=3DGenerator content=3D"Micr=
osoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	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:"Texte brut Car";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML Car";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Texte de bulles Car";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PrformatHTMLCar
	{mso-style-name:"Pr=E9format=E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr=E9format=E9 HTML";
	font-family:"Courier New";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
p.HTMLPreformatted, li.HTMLPreformatted, div.HTMLPreformatted
	{mso-style-name:"HTML Preformatted";
	mso-style-link:"HTML Preformatted Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.PlainText, li.PlainText, div.PlainText
	{mso-style-name:"Plain Text";
	mso-style-link:"Plain Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.BalloonText, li.BalloonText, div.BalloonText
	{mso-style-name:"Balloon Text";
	mso-style-link:"Balloon Text Char";
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:10.0pt;
	margin-left:0cm;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#993366;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@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:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1954749651;
	mso-list-template-ids:412145204;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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;line-height:115%;font-family:"Courier New";color:#993366'>R=
e-,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0=
pt;line-height:115%;font-family:"Courier New";color:#993366'>The descriptio=
n is used by the entity managing the PCP server. The document does not elab=
orate on such usage as this is deployment-specific: e.g., =A0(1) it can be =
used as =A0helper to clean the mapping table, (2) in some deployments that =
make use of a portal to instruct pcp mappings, this option can be used to s=
tore a subscriber-identifier, etc. We can add some text if you think this i=
s useful to be mentioned in the document.<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Cour=
ier New";color:#993366'>For the second point, I updated Section 5 with a po=
inter to Section 2. Thanks.<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color=
:#993366'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:10.0pt;line-height:115%;font-family:"Courier New";color:#993366'>=
Med<o:p></o:p></span></p><div style=3D'border:none;border-left:solid blue 1=
.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none;border-top:s=
olid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal style=3D=
'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><b><span style=
=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</span></b=
><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni E=
ven [mailto:ron.even.tlv@gmail.com] <br><b>Envoy=E9&nbsp;:</b> lundi 27 jan=
vier 2014 10:31<br><b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; draft-ietf-=
pcp-description-option.all@tools.ietf.org<br><b>Cc&nbsp;:</b> ietf@ietf.org=
; gen-art@ietf.org<br><b>Objet&nbsp;:</b> RE: Gen-ART LC review of draft-ie=
tf-pcp-description-option-03<o:p></o:p></span></p></div></div><p class=3DMs=
oNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span style=3D'color:#1F4=
97D'>Hi Med, <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'colo=
r:#1F497D'>Inline<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
color:#1F497D'>Roni<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;bo=
rder-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'bo=
rder:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p clas=
s=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:=
normal'><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif=
"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif"'> <a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucada=
ir@orange.com</a> [<a href=3D"mailto:mohamed.boucadair@orange.com">mailto:m=
ohamed.boucadair@orange.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM=
<br><b>To:</b> Roni Even; <a href=3D"mailto:draft-ietf-pcp-description-opti=
on.all@tools.ietf.org">draft-ietf-pcp-description-option.all@tools.ietf.org=
</a><br><b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a h=
ref=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> RE:=
 Gen-ART LC review of draft-ietf-pcp-description-option-03<o:p></o:p></span=
></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNo=
rmal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";co=
lor:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Courie=
r New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p class=3DMs=
oNormal><span style=3D'font-size:10.0pt;line-height:115%;font-family:"Couri=
er New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";co=
lor:#1F497D'>Med<o:p></o:p></span></p><div style=3D'border:none;border-left=
:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style=3D'border:none=
;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNo=
rmal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><=
b><span lang=3DFR style=3D'font-size:10.0pt;font-family:"Tahoma","sans-seri=
f"'>De&nbsp;:</span></b><span lang=3DFR style=3D'font-size:10.0pt;font-fami=
ly:"Tahoma","sans-serif"'> Roni Even [<a href=3D"mailto:ron.even.tlv@gmail.=
com">mailto:ron.even.tlv@gmail.com</a>] <br><b>Envoy=E9&nbsp;:</b> dimanche=
 26 janvier 2014 09:13<br><b>=C0&nbsp;:</b> <a href=3D"mailto:draft-ietf-pc=
p-description-option.all@tools.ietf.org">draft-ietf-pcp-description-option.=
all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> <a href=3D"mailto:ietf@ietf.org"=
>ietf@ietf.org</a>; <a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a=
><br><b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-description-op=
tion-03<o:p></o:p></span></p></div></div><p class=3DMsoNormal><span lang=3D=
FR><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><a name=3D"OLE_LINK2"><=
/a><a name=3D"OLE_LINK1"></a>I am the assigned Gen-ART reviewer for this dr=
aft. For background on Gen-ART, please see the FAQ at &lt;<a href=3D"http:/=
/wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" target=3D"_blank">http:/=
/wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p><p=
 class=3DMsoNormal>Please resolve these comments along with any other Last =
Call comments you may receive.<o:p></o:p></p><p class=3DMsoPlainText style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Document:&nbsp; <span style=3D=
'font-size:10.5pt;line-height:115%;font-family:"Courier New"'>draft-ietf-pc=
p-description-option-03<o:p></o:p></span></p><p class=3DMsoPlainText style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Reviewer: Roni Even<o:p></o:p>=
</p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001p=
t'>Review Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText style=
=3D'margin-bottom:0cm;margin-bottom:.0001pt'>IETF LC End Date: 2014&#8211;2=
-4<o:p></o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-=
bottom:.0001pt'>IESG Telechat date: <o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p c=
lass=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Summa=
ry: This draft is almost ready for publication as a standard track RFC.<o:p=
></o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom=
:.0001pt'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText style=3D'margin-bott=
om:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0cm;margin-bottom:.0001pt'>Major issues:<o:p></o:p><=
/p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt=
'><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;m=
argin-bottom:.0001pt'>Minor issues:<o:p></o:p></p><p class=3DMsoPlainText s=
tyle=3D'margin-bottom:0cm;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoPlainText style=3D'mso-margin-top-alt:0cm;margin-right:0cm;margin-=
bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt;text-indent:-18.0pt;mso=
-list:l0 level1 lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>=
1.<span style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; </span></span><![endif]>I am not sure what the use of the &#8220;d=
escription&#8221; option is. I can see how to create one but as for usage t=
he only text I can see is &#8220;Querying the PCP server to get the descrip=
tion text of an existing mapping is out of scope.&#8221; I think that the d=
ocument should provide information about the purpose of this option.<o:p></=
o:p></p><pre style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New";color:=
#1F497D'>[Med] The main usage is for a user to associate a textual descript=
ion with a mapping. This is captured by this text &#8220;</span></i></b><sp=
an style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier New"'>&n=
bsp;&nbsp; This option can be used by a user (or an application) to indicat=
e a<o:p></o:p></span></pre><p class=3DMsoNormal style=3D'margin-bottom:0cm;=
margin-bottom:.0001pt;line-height:normal'><span style=3D'font-size:10.0pt;f=
ont-family:"Courier New"'>&nbsp;&nbsp; description associated with a given =
mapping such as &quot;FTP server&quot;, &quot;My<o:p></o:p></span></p><p cl=
ass=3DMsoNormal style=3D'margin-bottom:0cm;margin-bottom:.0001pt;line-heigh=
t:normal'><span style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;=
&nbsp; remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Netwo=
rk attached storage<o:p></o:p></span></p><p class=3DMsoNormal style=3D'marg=
in-bottom:0cm;margin-bottom:.0001pt;line-height:normal'><span style=3D'font=
-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; serve&quot;, etc.<o:p>=
</o:p></span></p><p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-=
bottom:.0001pt'><b><i><span style=3D'font-size:10.0pt;line-height:115%;font=
-family:"Courier New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><=
p class=3DMsoPlainText style=3D'margin-bottom:0cm;margin-bottom:.0001pt'><b=
><i><span style=3D'color:#1F497D'>[Roni Even] </span></i></b><span style=3D=
'color:#1F497D'>This is motivation but it is not clear why the user does it=
 if no one can see it or does anything with it. It is kept on the server bu=
t not used by anyone?<o:p></o:p></span></p><p class=3DMsoPlainText style=3D=
'margin-bottom:0cm;margin-bottom:.0001pt'><span style=3D'color:#1F497D'><o:=
p>&nbsp;</o:p></span></p><p class=3DMsoNormal>Nits/editorial comments:<o:p>=
</o:p></p><ol style=3D'margin-top:0cm' start=3D1 type=3D1><li class=3DMsoNo=
rmal style=3D'mso-list:l1 level1 lfo5'>The IANA section should provide enou=
gh information to fill the registry <a href=3D"http://www.iana.org/assignme=
nts/pcp-parameters/pcp-parameters.xml#options">http://www.iana.org/assignme=
nts/pcp-parameters/pcp-parameters.xml#options</a> <o:p></o:p></li></ol><p c=
lass=3DMsoNormal><b><i><span style=3D'font-size:10.0pt;line-height:115%;fon=
t-family:"Courier New";color:#1F497D'>[Med] Required information as per RFC=
6887 is provided in <a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-de=
scription-option-03#section-2">http://tools.ietf.org/html/draft-ietf-pcp-de=
scription-option-03#section-2</a>. <o:p></o:p></span></i></b></p><p class=
=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] </span></i></b=
><span style=3D'color:#1F497D'>So section 5 should point to the definition =
is section 2<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color=
:#1F497D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p></div></div></div></div></body></html>=

--_000_94C682931C08B048B7A8645303FDC9F36F473608DFPUEXCB1Bnante_--

From ron.even.tlv@gmail.com  Mon Jan 27 02:05:55 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AFFF1A01DE; Mon, 27 Jan 2014 02:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LrNmtDIo6_W8; Mon, 27 Jan 2014 02:05:52 -0800 (PST)
Received: from mail-ee0-x230.google.com (mail-ee0-x230.google.com [IPv6:2a00:1450:4013:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2E4AA1A01D2; Mon, 27 Jan 2014 02:05:52 -0800 (PST)
Received: by mail-ee0-f48.google.com with SMTP id t10so2127223eei.7 for <multiple recipients>; Mon, 27 Jan 2014 02:05:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:thread-index:content-language; bh=dIl1Z/B8WMVRLn4+g0iy9AJ4MpetQpHGIls3eP54Tg4=; b=K+KZPoX3b4K/PgzZozsDlBrWDT4wjbz1z2QF9/3CQ/jdM4uVafwMvNPI/4GHa4+xwz HXj/0iJL6esLIALbi8kJ8z6+4JL+QH9JbfXu5XHqcIKrXUMSyWr6ZUrnBDLKqBlZKuoj DqE4zkHq5YbQYHwXDKjAzIcsctbglEltRj8vgphyW6qVWssz8JPG7mhWUuatWEh7nWXw mEsrrxCiv7yuMD+GHCFGvCmKE6mZs9YbMHUj1uDh+UjcFqdLVlQVLE21wFnCuNnzJe1O xAJCJrmQ6MjJI9uXOlzVlPmpkFlRrj5be4vbxAOOA1I7FM1E53tA8eIR+X2vThsOQvBs Q9mg==
X-Received: by 10.14.211.131 with SMTP id w3mr17084233eeo.7.1390817149571; Mon, 27 Jan 2014 02:05:49 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id o13sm40402995eex.19.2014.01.27.02.05.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 02:05:49 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Reinaldo Penno \(repenno\)'" <repenno@cisco.com>, <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com>
In-Reply-To: <CF0B68F0.8395%repenno@cisco.com>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Date: Mon, 27 Jan 2014 12:02:01 +0200
Message-ID: <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0354_01CF1B57.98D67550"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQCBFcQxKd1jXqufJNTVIZgvX5PLAp00YNqg
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 10:05:55 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0354_01CF1B57.98D67550
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

This should be stated and I assume that it is not for standardization =
but
not clear why the entity operating the PCP server needs it, is it =
described
in another document.

I am curious why querying the PCP server is =93out of scope=94 and not =
is =93for
further work=94.

Roni

=20

From: Reinaldo Penno (repenno) [mailto:repenno@cisco.com]=20
Sent: 27 January, 2014 11:39 AM
To: Roni Even; mohamed.boucadair@orange.com;
draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Hi,

=20

The idea is that it can be seen by the entity operating the PCP Server.=20

=20

Thanks,

=20

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, January 27, 2014 at 1:31 AM
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>,
"draft-ietf-pcp-description-option.all@tools.ietf.org"
<draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" =
<gen-art@ietf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Resent-From: <draft-alias-bounces@tools.ietf.org>
Resent-To: <dthaler@microsoft.com>, <dwing@cisco.com>,
"mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, Cisco
Employee <repenno@cisco.com>, <ted.lemon@nominum.com>
Resent-Date: Monday, January 27, 2014 at 1:35 AM

=20

Hi Med,=20

Inline

Roni

=20

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

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

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

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_0354_01CF1B57.98D67550
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1"><meta name=3DGenerator content=3D"Microsoft Word =
14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.EmailStyle27
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle28
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle30
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1808356015;
	mso-list-template-ids:-1385152000;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>This should be stated =
and I assume that it is not for standardization but not clear why the =
entity operating the PCP server needs it, is it described in another =
document.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>I am curious why querying the PCP server is =
&#8220;out of scope&#8221; and not is &#8220;for further =
work&#8221;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Reinaldo Penno (repenno) [mailto:repenno@cisco.com] <br><b>Sent:</b> 27 =
January, 2014 11:39 AM<br><b>To:</b> Roni Even; =
mohamed.boucadair@orange.com; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> Re: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Hi,<o:p></o:p></s=
pan></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>The idea is that =
it can be seen by the entity operating the PCP =
Server.&nbsp;<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'>Thanks,<o:p></o:p=
></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span =
style=3D'color:black'>From: </span></b><span style=3D'color:black'>Roni =
Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, January 27, 2014 at 1:31 AM<br><b>To: </b>&quot;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&quot; &lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&gt;, &quot;<a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a>&gt;<br><b>Cc: =
</b>&quot;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; =
&lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<br><b>Resent-From: </b>&lt;<a =
href=3D"mailto:draft-alias-bounces@tools.ietf.org">draft-alias-bounces@to=
ols.ietf.org</a>&gt;<br><b>Resent-To: </b>&lt;<a =
href=3D"mailto:dthaler@microsoft.com">dthaler@microsoft.com</a>&gt;, =
&lt;<a href=3D"mailto:dwing@cisco.com">dwing@cisco.com</a>&gt;, &quot;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&quot; &lt;<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a>&gt;, Cisco Employee &lt;<a =
href=3D"mailto:repenno@cisco.com">repenno@cisco.com</a>&gt;, &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt;<br><b=
>Resent-Date: </b>Monday, January 27, 2014 at 1:35 =
AM<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;color:black'><o:p>&nbsp;</o:p>=
</span></p></div><div><div><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med, </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
From:</span></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 <a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a> [<a =
href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.boucadair@ora=
nge.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> =
Roni Even; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc:</b> <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. </span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med</span><span =
style=3D'color:black'><o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
De&nbsp;:</span></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:black'>=
 Roni Even [<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR =
style=3D'color:black'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><a =
name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a><span =
style=3D'color:black'>I am the assigned Gen-ART reviewer for this draft. =
For background on Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Document:&nbsp; </span><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New";color:black'>draft-ietf-pcp-description-option-03</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Reviewer: Roni Even<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Review =
Date:2014&#8211;1-26<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>IESG Telechat date: <o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Summary: This draft is almost ready for =
publication as a standard track RFC.<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Major issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>Minor issues:<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'color:black'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:black'>I am not sure what the use of the =
&#8220;description&#8221; option is. I can see how to create one but as =
for usage the only text I can see is &#8220;Querying the PCP server to =
get the description text of an existing mapping is out of scope.&#8221; =
I think that the document should provide information about the purpose =
of this option.<o:p></o:p></span></p><pre><b><i><span =
style=3D'color:#1F497D'>[Med] The main usage is for a user to associate =
a textual description with a mapping. This is captured by this text =
&#8220;</span></i></b><span style=3D'color:black'>&nbsp;&nbsp; This =
option can be used by a user (or an application) to indicate =
a<o:p></o:p></span></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; description associated with a given =
mapping such as &quot;FTP server&quot;, &quot;My</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; remote access to my CP router&quot;, =
&quot;Camera&quot;, &quot;Network attached storage</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'>&nbsp;&nbsp; serve&quot;, etc.</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;</span></i></b><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>Nits/editorial comments:<o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:black;mso-list:l1 level1 lfo5'>The IANA section should =
provide enough information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. </span></i></b><span =
style=3D'color:black'><o:p></o:p></span></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>&nbsp;</span><span =
style=3D'color:black'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:black'>&nbsp;<o:p></o:p></span></p></div></div></div></div=
></div></div></body></html>
------=_NextPart_000_0354_01CF1B57.98D67550--


From ron.even.tlv@gmail.com  Mon Jan 27 03:34:22 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 427031A01E8; Mon, 27 Jan 2014 03:34:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZC22RVCiZgjA; Mon, 27 Jan 2014 03:34:18 -0800 (PST)
Received: from mail-ee0-x233.google.com (mail-ee0-x233.google.com [IPv6:2a00:1450:4013:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 8D5831A01E4; Mon, 27 Jan 2014 03:34:17 -0800 (PST)
Received: by mail-ee0-f51.google.com with SMTP id b57so2199343eek.38 for <multiple recipients>; Mon, 27 Jan 2014 03:34:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:thread-index:content-language; bh=pHb8s3pVsDXVxNNIHuXFf9iYCvfCD+jjspbwRHMZrNE=; b=WeLp9V62jEOKqmn0gKjcMGdjcqkwopiZjyAFRWqygdcu4AKJLhDW3rWOjHro3tqOWW 9kJlD13+OoRZufKwgFfBFUkFfwIeUXPRNaDhwzix4j8vHrmZPsvl/PHi85hG93S/dMEn RUcPbGuPAvpBm4oxwVZZIIGRZ9ievC/fyryZTMfQWsGQgYPEOKs3QnwaFt4K/sUI0i9Y ygYt1KHdjV7Ji2hstgmaXFtKwWlpW6mFDSBGpRlDVZgoj56X5Sj3STbsKV09puDUHbs5 ZTBe+dl53tcJAd5HHnGZ/yWzVeF6ZxTxYbfhvx1YWw2taS8u5H2Xu4FioTokmAjq0ryl ITVQ==
X-Received: by 10.14.6.129 with SMTP id 1mr274364een.99.1390822454872; Mon, 27 Jan 2014 03:34:14 -0800 (PST)
Received: from RoniE ([109.66.49.55]) by mx.google.com with ESMTPSA id 46sm41351623ees.4.2014.01.27.03.34.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 27 Jan 2014 03:34:13 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mohamed.boucadair@orange.com>, <draft-ietf-pcp-description-option.all@tools.ietf.org>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
In-Reply-To: <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Date: Mon, 27 Jan 2014 13:30:24 +0200
Message-ID: <036401cf1b53$2ec6cdd0$8c546970$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0365_01CF1B63.F2517290"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQF6/p6mIwEjavahOcoGuw0nlckk9wI8szcDAx3Ucj0Btw/0U5sIHEGg
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 11:34:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0365_01CF1B63.F2517290
Content-Type: text/plain;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Med,

I think some text will be useful

Roni

=20

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: 27 January, 2014 11:55 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Re-,

The description is used by the entity managing the PCP server. The =
document
does not elaborate on such usage as this is deployment-specific: e.g.,  =
(1)
it can be used as  helper to clean the mapping table, (2) in some
deployments that make use of a portal to instruct pcp mappings, this =
option
can be used to store a subscriber-identifier, etc. We can add some text =
if
you think this is useful to be mentioned in the document.

For the second point, I updated Section 5 with a pointer to Section 2.
Thanks.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : lundi 27 janvier 2014 10:31
=C0 : BOUCADAIR Mohamed IMT/OLN;
draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Hi Med,=20

Inline

Roni

=20

From: mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =

Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

Dear Roni,

Thank you for the review.=20

Please see inline.

Cheers,

Med

De : Roni Even [mailto:ron.even.tlv@gmail.com]=20
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org
Cc : ietf@ietf.org; gen-art@ietf.org
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

=20

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

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

Document:  draft-ietf-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:=20

=20

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

=20

=20

Major issues:

=20

Minor issues:

=20

1.       I am not sure what the use of the =93description=94 option is. =
I can
see how to create one but as for usage the only text I can see is =
=93Querying
the PCP server to get the description text of an existing mapping is out =
of
scope.=94 I think that the document should provide information about the
purpose of this option.

[Med] The main usage is for a user to associate a textual description =
with a
mapping. This is captured by this text =93   This option can be used by =
a user
(or an application) to indicate a

   description associated with a given mapping such as "FTP server", "My

   remote access to my CP router", "Camera", "Network attached storage

   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it =
if
no one can see it or does anything with it. It is kept on the server but =
not
used by anyone?

=20

Nits/editorial comments:

1.	The IANA section should provide enough information to fill the
registry
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options=
=20

[Med] Required information as per RFC6887 is provided in
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2=
.=20

[Roni Even] So section 5 should point to the definition is section 2

=20

=20


------=_NextPart_000_0365_01CF1B63.F2517290
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<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 name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	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";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
p.Textedebulles, li.Textedebulles, div.Textedebulles
	{mso-style-name:"Texte de bulles";
	mso-style-link:"Texte de bulles Car";
	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";}
span.TextedebullesCar
	{mso-style-name:"Texte de bulles Car";
	mso-style-priority:99;
	mso-style-link:"Texte de bulles";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle30
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
span.EmailStyle31
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle32
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#993366;}
span.EmailStyle33
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:1517378766;
	mso-list-template-ids:1165285046;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I think some text will =
be useful<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
mohamed.boucadair@orange.com [mailto:mohamed.boucadair@orange.com] =
<br><b>Sent:</b> 27 January, 2014 11:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-pcp-description-option.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org<br><b>Subject:</b> RE: Gen-ART LC review =
of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Re-,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>The description is used by the entity managing the =
PCP server. The document does not elaborate on such usage as this is =
deployment-specific: e.g., &nbsp;(1) it can be used as &nbsp;helper to =
clean the mapping table, (2) in some deployments that make use of a =
portal to instruct pcp mappings, this option can be used to store a =
subscriber-identifier, etc. We can add some text if you think this is =
useful to be mentioned in the document.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>For the second point, I updated Section 5 with a =
pointer to Section 2. Thanks.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#993366'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> lundi 27 janvier 2014 =
10:31<br><b>=C0&nbsp;:</b> BOUCADAIR Mohamed IMT/OLN; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Hi Med, <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Inline<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
<a =
href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com=
</a> [<a =
href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.boucadair@ora=
nge.com</a>] <br><b>Sent:</b> 27 January, 2014 10:31 AM<br><b>To:</b> =
Roni Even; <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc:</b> <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Subject:</b> =
RE: Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Dear Roni,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Thank you for the review. <o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Please see inline.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>Med<o:p></o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><b><=
span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>De&nbsp;:</s=
pan></b><span lang=3DFR =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Roni Even =
[<a =
href=3D"mailto:ron.even.tlv@gmail.com">mailto:ron.even.tlv@gmail.com</a>]=
 <br><b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 =
09:13<br><b>=C0&nbsp;:</b> <a =
href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org">draf=
t-ietf-pcp-description-option.all@tools.ietf.org</a><br><b>Cc&nbsp;:</b> =
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a><br><b>Objet&nbsp;:<=
/b> Gen-ART LC review of =
draft-ietf-pcp-description-option-03<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><span lang=3DFR><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>I =
am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Document:&nbsp; <span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Courier =
New"'>draft-ietf-pcp-description-option-03<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Reviewer: Roni =
Even<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Review =
Date:2014&#8211;1-26<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IETF LC End Date: =
2014&#8211;2-4<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>IESG Telechat date: =
<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Summary: This draft is =
almost ready for publication as a standard track RFC.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Major =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'>Minor =
issues:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><o:p>&nbsp;</o:p></p><p=
 class=3DMsoPlainText =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;text-indent:-.25in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]><span dir=3DLTR></span>I am not sure what the =
use of the &#8220;description&#8221; option is. I can see how to create =
one but as for usage the only text I can see is &#8220;Querying the PCP =
server to get the description text of an existing mapping is out of =
scope.&#8221; I think that the document should provide information about =
the purpose of this option.<o:p></o:p></p><pre =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] The main usage is for a user to associate a =
textual description with a mapping. This is captured by this text =
&#8220;</span></i></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New"'>&nbsp;&nbsp; This option can be used by a user (or an application) =
to indicate a<o:p></o:p></span></pre><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
description associated with a given mapping such as &quot;FTP =
server&quot;, &quot;My<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
remote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network =
attached storage<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><spa=
n style=3D'font-size:10.0pt;font-family:"Courier New"'>&nbsp;&nbsp; =
serve&quot;, etc.<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>&#8221;<o:p></o:p></span></i></b></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><b><i><span =
style=3D'color:#1F497D'>[Roni Even] </span></i></b><span =
style=3D'color:#1F497D'>This is motivation but it is not clear why the =
user does it if no one can see it or does anything with it. It is kept =
on the server but not used by anyone?<o:p></o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-bottom:0in;margin-bottom:.0001pt'><span =
style=3D'color:#1F497D'><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:l1 level1 lfo5'>The IANA section should provide enough =
information to fill the registry <a =
href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml=
#options">http://www.iana.org/assignments/pcp-parameters/pcp-parameters.x=
ml#options</a> <o:p></o:p></li></ol><p class=3DMsoNormal><b><i><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Courier =
New";color:#1F497D'>[Med] Required information as per RFC6887 is =
provided in <a =
href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#s=
ection-2">http://tools.ietf.org/html/draft-ietf-pcp-description-option-03=
#section-2</a>. <o:p></o:p></span></i></b></p><p =
class=3DMsoNormal><b><i><span style=3D'color:#1F497D'>[Roni Even] =
</span></i></b><span style=3D'color:#1F497D'>So section 5 should point =
to the definition is section 2<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></div></div></bo=
dy></html>
------=_NextPart_000_0365_01CF1B63.F2517290--


From lear@cisco.com  Mon Jan 27 05:20:58 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F15B1A020E; Mon, 27 Jan 2014 05:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfVPqbDkO5jQ; Mon, 27 Jan 2014 05:20:57 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 782CE1A020A; Mon, 27 Jan 2014 05:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3184; q=dns/txt; s=iport; t=1390828855; x=1392038455; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=z0yW11rgQCG4ugwACOvVUpM4Ma+Riefv+tmp1OKfZRo=; b=PVYiBNlNngqbMRMUmJnaSAGOVmsBFtP8p4hWO7dy9PsTj80DgG7H5gWi j8S7DD6dKfvRtKNbdTlowtqPPo3LQ61lbY9uJ0nbTQ55qAFIcTJTqMADu VGyGW/vcHA/+CP5r0USkjrHAZU4NoDEz13t/yZpV0g+nnJiUu2Q97yJTX A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai8FAJdc5lKQ/khM/2dsb2JhbABZgww4g1O5WIENFnSCJQEBAQMBI1UBEAsUBAICBRYLAgIJAwIBAgErGgYBDAEHAQGHeQgNq1KcWheBKYtxgSBTB4JvgUkBA5gngTKQbIMuO4E1
X-IronPort-AV: E=Sophos;i="4.95,729,1384300800";  d="scan'208";a="3576971"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 27 Jan 2014 13:20:53 +0000
Received: from mctiny.local ([10.61.174.53]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0RDKqKK031965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 13:20:53 GMT
Message-ID: <52E65878.9030906@cisco.com>
Date: Mon, 27 Jan 2014 14:00:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>, "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Subject: Re: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 13:20:58 -0000

Hi Dave,

First, thank you for your review.  I personally appreciate to the time
you put in to all of your reviews.

On 1/27/14, 3:06 AM, Black, David wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-qresync-rfc5162bis-09
> Reviewer: David L. Black
> Review Date: January 26, 2014
> IETF LC End Date: January 27, 2014
>
> Summary:
> This draft is basically ready for publication, but has minor issues that
> should be fixed before publication.
>
> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
> (IMAP Quick Mailbox Resynchronization) into a single document and makes
> a few minor updates.  It also updates the command line length
> recommendation in RFC 2683 to support the longer command lines that
> can occur with these extensions.
>
> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
> they look reasonable.  I found one minor issue that should be relatively
> easy to address.
>
> Minor Issues:
>
> The command line length change in Section 4 applies to all IMAP commands,
> and hence affects old servers, including those that don't implement either
> of the extensions in this draft. That raises a backwards compatibility
> concern - what happens when a new client sends a > 1000 character command
> line to an old server that isn't expecting more than 1000 characters?

As the draft indicates, this is problematic for the two extensions in
question. We have discussed this limitation in the working group, and
nobody seems to be concerned.  That's due to two factors, I think:
first, RFC 2683 is not normative (informational).  I am unaware of any
strict line length limitation in RFC 3501, for instance.  Instead, there
is a requirement for strict syntax parsing.  If the client blows it in
any way, the server SHOULD return an error with a BAD response.

This having been said, while the working group has discussed this
matter, it would be good to hear any additional voices of concern, in
the interests of interoperability.

This takes us to your next point:

>
> One possibility would be to apply the larger length recommendation only
> after the client determines that the server supports at least one of
> these extensions.
>
> Nits/editorial comments:
>
> The update to RFC 2683 would be easier to find from the table of contents
> if the title of Section 4 were changed to "Long Command Lines (Update to
> RFC 2683)".
>
> idnits 2.13.01 got confused by the command line examples, and flagged a
> downref:
>
>   ** Downref: Normative reference to an Informational RFC: RFC 2683
>
> That downref appears to be ok and intended, as noted in the shepherd's
> writeup.

This will be addressed in a forthcoming update.  Barry has "educated" us
that really this is NOT an update to RFC2683, where the advice given in
that document is superceded by a specific option.  As such, this error
will evaporate.



From lars@netapp.com  Mon Jan 27 06:10:51 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66E091A023A for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 06:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.437
X-Spam-Level: 
X-Spam-Status: No, score=-7.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-JMD_-l4P34 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 06:10:49 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1201A022F for <ietf@ietf.org>; Mon, 27 Jan 2014 06:10:49 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,729,1384329600";  d="asc'?scan'208";a="139300107"
Received: from vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) by mx12-out.netapp.com with ESMTP; 27 Jan 2014 06:10:47 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht06-prd.hq.netapp.com ([10.106.77.104]) with mapi id 14.03.0123.003; Mon, 27 Jan 2014 06:10:47 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Topic: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Index: AQHPFqUWbHitS8PQ2U61HYhCH0Ib05qWb7CAgAJrBQCAAE0SgIAABC6A
Date: Mon, 27 Jan 2014 14:10:45 +0000
Message-ID: <24557711-DEB4-4E8B-8751-9FC9ECF9F844@netapp.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com>
In-Reply-To: <m3ppnda5r0.wl%narten@us.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_2DE8216F-7775-4B7E-8A77-C2BC797BA3AB"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:10:51 -0000

--Apple-Mail=_2DE8216F-7775-4B7E-8A77-C2BC797BA3AB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Yeah, we've been inconsistent. And I'm not saying we should block the =
document from being published on the IETF stream. But maybe the IESG =
wants to put a note on it or something.

Lars

On 2014-1-27, at 14:55, Thomas Narten <narten@us.ibm.com> wrote:

> At Mon, 27 Jan 2014 09:20:04 +0000,
> Eggert, Lars wrote:
>>=20
>> [1  <text/plain; us-ascii (quoted-printable)>]
>> On 2014-1-25, at 21:24, Adrian Farrel <adrian@olddog.co.uk> wrote:
>>> It seems from the document that the content is descriptive of =
something
>>> implemented by a single vendor. I applaud putting that information =
into the
>>> public domain, but I don't understand the meaning of IETF consensus =
with respect
>>> to this document.
>>=20
>> +1
>>=20
>> The Independent RFC Stream would seem more appropriate.
>=20
> Well, if you run a document through the RFC Stream publication
> process, it doesn't get the same level/type of review as does running
> it through the IETF. At least in theory.
>=20
> So if one wanted to get IETF folk to review it, running it through
> IETF consensus (or something) doesn't seem unreasonable.
>=20
> I don't know that we actually have an exact category for these kinds
> of documents. Indeed, the categories we have are rather course, and
> one can identify plenty of past documents that one might argue could
> have/should have been published in a different stream than it
> was. E.g., looking backwards for "cisco" documents published as RFCs:
>=20
>> A new Request for Comments is now available in online RFC libraries.
>>        RFC 6812
>>=20
>>        Title:      Cisco Service-Level Assurance Protocol=20
>>        Status:     Informational
>>        Stream:     Independent
>>        Date:       January 2013
>>        I-D Tag:    draft-cisco-sla-protocol-04.txt
>=20
> It was published in the RFC editor stream.
>=20
> On the other hand:
>=20
>>        RFC 6759
>>        Title:      Cisco Systems Export of Application=20
>>                    Information in IP Flow Information Export=20
>>                    (IPFIX)=20
>>        Status:     Informational
>>        Stream:     IETF
>>        Date:       November 2012
>>        I-D Tag:    =
draft-claise-export-application-info-in-ipfix-10.txt
>=20
> It was published via the IETF stream.
>=20
> Thomas
>=20


--Apple-Mail=_2DE8216F-7775-4B7E-8A77-C2BC797BA3AB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----

iQCVAwUBUuZo5dZcnpRveo1xAQLzrAP/RCIRYvn1Omcs+c6S6GSzPrTzXmJLU43P
Yl5q7lMQUphThcw8YYklberCHXkQIV2/6emHD4m7jd5irracFDH9XLtA9Hf9BIxQ
d9fPnxverHPYlyHn4Jw5+J1Xai34YqX76oPccqY8mVk8/Czl2CUqsavpD8mcTI3z
8n4EiDeoobA=
=U5ff
-----END PGP SIGNATURE-----

--Apple-Mail=_2DE8216F-7775-4B7E-8A77-C2BC797BA3AB--

From david.black@emc.com  Mon Jan 27 06:21:04 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FDF1A0231; Mon, 27 Jan 2014 06:21:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4k4CV4Q1QIzT; Mon, 27 Jan 2014 06:21:02 -0800 (PST)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id D4A081A0214; Mon, 27 Jan 2014 06:21:01 -0800 (PST)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0REKLUO005722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 09:20:24 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0REKLUO005722
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390832424; bh=2TDDdpW2GAOoDonVpmg7CzXjIek=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=CDhHkLolIvVEg8Kcj/wWVR+cv+5cmANArOcKK6i9IszzUwSTv3Qnh+TcGKcpKM80Z uVyJzzkBzaHwzp5SQ2GsMVI9FamanA170cziXAtFXPOJc9FsldCMC4VAuu2WfXkE2D kw4nR0ylR6eUm3OXLcP2REdli60Ft8d0r27H92EI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s0REKLUO005722
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd53.lss.emc.com (RSA Interceptor); Mon, 27 Jan 2014 09:20:13 -0500
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0REKCKA001772 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 09:20:12 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Mon, 27 Jan 2014 09:19:47 -0500
From: "Black, David" <david.black@emc.com>
To: Eliot Lear <lear@cisco.com>, "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 27 Jan 2014 09:20:10 -0500
Subject: RE: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bYuepHQKAPJ5wQ42zaOAlQX1aAAAB1PLg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>
In-Reply-To: <52E65878.9030906@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Cc: "Black, David" <david.black@emc.com>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:21:05 -0000

SGkgRWxpb3QsDQoNClJlZ2FyZGluZyBsaW5lIGxlbmd0aDoNCg0KPiBBcyB0aGUgZHJhZnQgaW5k
aWNhdGVzLCB0aGlzIGlzIHByb2JsZW1hdGljIGZvciB0aGUgdHdvIGV4dGVuc2lvbnMgaW4NCj4g
cXVlc3Rpb24uIFdlIGhhdmUgZGlzY3Vzc2VkIHRoaXMgbGltaXRhdGlvbiBpbiB0aGUgd29ya2lu
ZyBncm91cCwgYW5kDQo+IG5vYm9keSBzZWVtcyB0byBiZSBjb25jZXJuZWQuICBUaGF0J3MgZHVl
IHRvIHR3byBmYWN0b3JzLCBJIHRoaW5rOg0KPiBmaXJzdCwgUkZDIDI2ODMgaXMgbm90IG5vcm1h
dGl2ZSAoaW5mb3JtYXRpb25hbCkuICBJIGFtIHVuYXdhcmUgb2YgYW55DQo+IHN0cmljdCBsaW5l
IGxlbmd0aCBsaW1pdGF0aW9uIGluIFJGQyAzNTAxLCBmb3IgaW5zdGFuY2UuICBJbnN0ZWFkLCB0
aGVyZQ0KPiBpcyBhIHJlcXVpcmVtZW50IGZvciBzdHJpY3Qgc3ludGF4IHBhcnNpbmcuICBJZiB0
aGUgY2xpZW50IGJsb3dzIGl0IGluDQo+IGFueSB3YXksIHRoZSBzZXJ2ZXIgU0hPVUxEIHJldHVy
biBhbiBlcnJvciB3aXRoIGEgQkFEIHJlc3BvbnNlLg0KDQpUaGUgbGF0dGVyIHR3byBzZW50ZW5j
ZXMgd291bGQgYmUgZ29vZCB0byBhZGQgdG8gdGhlIGRyYWZ0IGluIHNvbWUgZm9ybS4NCg0KTXkg
cHJpbWFyeSBjb25jZXJuIGlzIHdoYXQgaGFwcGVucyBpZiB0aGUgY2xpZW50IHNlbmRzIGEgcmF0
aGVyIGxvbmcNCmxpbmUgdG8gYSBzZXJ2ZXIgdGhhdCBpc24ndCBwcmVwYXJlZCB0byBjb3BlLCBh
bmQgdGhlIGxhdHRlciBzZW50ZW5jZQ0Kd291bGQgYWRkcmVzcyBpdC4gIFRoYXQgY291bGQgYmUg
YWNjb21wYW5pZWQgYnkgc29tZSBzb3J0IG9mIHN0YXRlbWVudA0KdGhhdCBzZXJ2ZXJzIHRoYXQg
aW1wbGVtZW50IHRoaXMgZXh0ZW5zaW9uIG5lZWQgdG8gYmUgcHJlcGFyZWQgdG8gY29wZQ0Kd2l0
aCBsb25nZXIgbGluZXMuDQoNCkknbGwgbGVhdmUgdGhlIGRvd25yZWYgYXMgYSBwcm9jZXNzIGNv
bmNlcm4gZm9yIHlvdSAoV0cgY2hhaXIpIGFuZCBCYXJyeSAoQUQpDQp0byB3b3JrIG91dC4NCg0K
VGhhbmtzLA0KLS1EYXZpZA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206
IEVsaW90IExlYXIgW21haWx0bzpsZWFyQGNpc2NvLmNvbV0NCj4gU2VudDogTW9uZGF5LCBKYW51
YXJ5IDI3LCAyMDE0IDg6MDEgQU0NCj4gVG86IEJsYWNrLCBEYXZpZDsgQWxleGV5IE1lbG5pa292
IChhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29tKTsNCj4gZGNyaWRsYW5kQGFyY29kZS5jb207IEdl
bmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAoZ2VuLWFydEBpZXRmLm9yZykNCj4gQ2M6IEJhcnJ5IExl
aWJhIChiYXJyeWxlaWJhQGNvbXB1dGVyLm9yZyk7IGlldGZAaWV0Zi5vcmc7IGltYXBleHRAaWV0
Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbi1BUlQgcmV2aWV3IG9mIGRyYWZ0LWlldGYtcXJlc3lu
Yy1yZmM1MTYyYmlzLTA5DQo+IA0KPiBIaSBEYXZlLA0KPiANCj4gRmlyc3QsIHRoYW5rIHlvdSBm
b3IgeW91ciByZXZpZXcuICBJIHBlcnNvbmFsbHkgYXBwcmVjaWF0ZSB0byB0aGUgdGltZQ0KPiB5
b3UgcHV0IGluIHRvIGFsbCBvZiB5b3VyIHJldmlld3MuDQo+IA0KPiBPbiAxLzI3LzE0LCAzOjA2
IEFNLCBCbGFjaywgRGF2aWQgd3JvdGU6DQo+ID4gSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCBy
ZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gRm9yIGJhY2tncm91bmQgb24NCj4gPiBHZW4tQVJULCBw
bGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPg0KPiA+IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9y
Zy9hcmVhL2dlbi90cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCj4gPg0KPiA+IFBsZWFzZSByZXNvbHZl
IHRoZXNlIGNvbW1lbnRzIGFsb25nIHdpdGggYW55IG90aGVyIExhc3QgQ2FsbCBjb21tZW50cw0K
PiA+IHlvdSBtYXkgcmVjZWl2ZS4NCj4gPg0KPiA+IERvY3VtZW50OiBkcmFmdC1pZXRmLXFyZXN5
bmMtcmZjNTE2MmJpcy0wOQ0KPiA+IFJldmlld2VyOiBEYXZpZCBMLiBCbGFjaw0KPiA+IFJldmll
dyBEYXRlOiBKYW51YXJ5IDI2LCAyMDE0DQo+ID4gSUVURiBMQyBFbmQgRGF0ZTogSmFudWFyeSAy
NywgMjAxNA0KPiA+DQo+ID4gU3VtbWFyeToNCj4gPiBUaGlzIGRyYWZ0IGlzIGJhc2ljYWxseSBy
ZWFkeSBmb3IgcHVibGljYXRpb24sIGJ1dCBoYXMgbWlub3IgaXNzdWVzIHRoYXQNCj4gPiBzaG91
bGQgYmUgZml4ZWQgYmVmb3JlIHB1YmxpY2F0aW9uLg0KPiA+DQo+ID4gVGhpcyBkcmFmdCBjb25z
b2xpZGF0ZXMgUkZDIDQ1NTEgKElNQVAgQ29uZGl0aW9uYWwgU1RPUkUpIGFuZCBSRkMgNTE2Mg0K
PiA+IChJTUFQIFF1aWNrIE1haWxib3ggUmVzeW5jaHJvbml6YXRpb24pIGludG8gYSBzaW5nbGUg
ZG9jdW1lbnQgYW5kIG1ha2VzDQo+ID4gYSBmZXcgbWlub3IgdXBkYXRlcy4gIEl0IGFsc28gdXBk
YXRlcyB0aGUgY29tbWFuZCBsaW5lIGxlbmd0aA0KPiA+IHJlY29tbWVuZGF0aW9uIGluIFJGQyAy
NjgzIHRvIHN1cHBvcnQgdGhlIGxvbmdlciBjb21tYW5kIGxpbmVzIHRoYXQNCj4gPiBjYW4gb2Nj
dXIgd2l0aCB0aGVzZSBleHRlbnNpb25zLg0KPiA+DQo+ID4gQXMgdGhpcyBpcyBhbiB1cGRhdGUs
IEkgY2hlY2tlZCB0aGUgZGlmZnMgYWdhaW5zdCBSRkMgNDU1MSBhbmQgUkZDIDUxNjI7DQo+ID4g
dGhleSBsb29rIHJlYXNvbmFibGUuICBJIGZvdW5kIG9uZSBtaW5vciBpc3N1ZSB0aGF0IHNob3Vs
ZCBiZSByZWxhdGl2ZWx5DQo+ID4gZWFzeSB0byBhZGRyZXNzLg0KPiA+DQo+ID4gTWlub3IgSXNz
dWVzOg0KPiA+DQo+ID4gVGhlIGNvbW1hbmQgbGluZSBsZW5ndGggY2hhbmdlIGluIFNlY3Rpb24g
NCBhcHBsaWVzIHRvIGFsbCBJTUFQIGNvbW1hbmRzLA0KPiA+IGFuZCBoZW5jZSBhZmZlY3RzIG9s
ZCBzZXJ2ZXJzLCBpbmNsdWRpbmcgdGhvc2UgdGhhdCBkb24ndCBpbXBsZW1lbnQgZWl0aGVyDQo+
ID4gb2YgdGhlIGV4dGVuc2lvbnMgaW4gdGhpcyBkcmFmdC4gVGhhdCByYWlzZXMgYSBiYWNrd2Fy
ZHMgY29tcGF0aWJpbGl0eQ0KPiA+IGNvbmNlcm4gLSB3aGF0IGhhcHBlbnMgd2hlbiBhIG5ldyBj
bGllbnQgc2VuZHMgYSA+IDEwMDAgY2hhcmFjdGVyIGNvbW1hbmQNCj4gPiBsaW5lIHRvIGFuIG9s
ZCBzZXJ2ZXIgdGhhdCBpc24ndCBleHBlY3RpbmcgbW9yZSB0aGFuIDEwMDAgY2hhcmFjdGVycz8N
Cj4gDQo+IEFzIHRoZSBkcmFmdCBpbmRpY2F0ZXMsIHRoaXMgaXMgcHJvYmxlbWF0aWMgZm9yIHRo
ZSB0d28gZXh0ZW5zaW9ucyBpbg0KPiBxdWVzdGlvbi4gV2UgaGF2ZSBkaXNjdXNzZWQgdGhpcyBs
aW1pdGF0aW9uIGluIHRoZSB3b3JraW5nIGdyb3VwLCBhbmQNCj4gbm9ib2R5IHNlZW1zIHRvIGJl
IGNvbmNlcm5lZC4gIFRoYXQncyBkdWUgdG8gdHdvIGZhY3RvcnMsIEkgdGhpbms6DQo+IGZpcnN0
LCBSRkMgMjY4MyBpcyBub3Qgbm9ybWF0aXZlIChpbmZvcm1hdGlvbmFsKS4gIEkgYW0gdW5hd2Fy
ZSBvZiBhbnkNCj4gc3RyaWN0IGxpbmUgbGVuZ3RoIGxpbWl0YXRpb24gaW4gUkZDIDM1MDEsIGZv
ciBpbnN0YW5jZS4gIEluc3RlYWQsIHRoZXJlDQo+IGlzIGEgcmVxdWlyZW1lbnQgZm9yIHN0cmlj
dCBzeW50YXggcGFyc2luZy4gIElmIHRoZSBjbGllbnQgYmxvd3MgaXQgaW4NCj4gYW55IHdheSwg
dGhlIHNlcnZlciBTSE9VTEQgcmV0dXJuIGFuIGVycm9yIHdpdGggYSBCQUQgcmVzcG9uc2UuDQo+
IA0KPiBUaGlzIGhhdmluZyBiZWVuIHNhaWQsIHdoaWxlIHRoZSB3b3JraW5nIGdyb3VwIGhhcyBk
aXNjdXNzZWQgdGhpcw0KPiBtYXR0ZXIsIGl0IHdvdWxkIGJlIGdvb2QgdG8gaGVhciBhbnkgYWRk
aXRpb25hbCB2b2ljZXMgb2YgY29uY2VybiwgaW4NCj4gdGhlIGludGVyZXN0cyBvZiBpbnRlcm9w
ZXJhYmlsaXR5Lg0KPiANCj4gVGhpcyB0YWtlcyB1cyB0byB5b3VyIG5leHQgcG9pbnQ6DQo+IA0K
PiA+DQo+ID4gT25lIHBvc3NpYmlsaXR5IHdvdWxkIGJlIHRvIGFwcGx5IHRoZSBsYXJnZXIgbGVu
Z3RoIHJlY29tbWVuZGF0aW9uIG9ubHkNCj4gPiBhZnRlciB0aGUgY2xpZW50IGRldGVybWluZXMg
dGhhdCB0aGUgc2VydmVyIHN1cHBvcnRzIGF0IGxlYXN0IG9uZSBvZg0KPiA+IHRoZXNlIGV4dGVu
c2lvbnMuDQo+ID4NCj4gPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gPg0KPiA+IFRoZSB1
cGRhdGUgdG8gUkZDIDI2ODMgd291bGQgYmUgZWFzaWVyIHRvIGZpbmQgZnJvbSB0aGUgdGFibGUg
b2YgY29udGVudHMNCj4gPiBpZiB0aGUgdGl0bGUgb2YgU2VjdGlvbiA0IHdlcmUgY2hhbmdlZCB0
byAiTG9uZyBDb21tYW5kIExpbmVzIChVcGRhdGUgdG8NCj4gPiBSRkMgMjY4MykiLg0KPiA+DQo+
ID4gaWRuaXRzIDIuMTMuMDEgZ290IGNvbmZ1c2VkIGJ5IHRoZSBjb21tYW5kIGxpbmUgZXhhbXBs
ZXMsIGFuZCBmbGFnZ2VkIGENCj4gPiBkb3ducmVmOg0KPiA+DQo+ID4gICAqKiBEb3ducmVmOiBO
b3JtYXRpdmUgcmVmZXJlbmNlIHRvIGFuIEluZm9ybWF0aW9uYWwgUkZDOiBSRkMgMjY4Mw0KPiA+
DQo+ID4gVGhhdCBkb3ducmVmIGFwcGVhcnMgdG8gYmUgb2sgYW5kIGludGVuZGVkLCBhcyBub3Rl
ZCBpbiB0aGUgc2hlcGhlcmQncw0KPiA+IHdyaXRldXAuDQo+IA0KPiBUaGlzIHdpbGwgYmUgYWRk
cmVzc2VkIGluIGEgZm9ydGhjb21pbmcgdXBkYXRlLiAgQmFycnkgaGFzICJlZHVjYXRlZCIgdXMN
Cj4gdGhhdCByZWFsbHkgdGhpcyBpcyBOT1QgYW4gdXBkYXRlIHRvIFJGQzI2ODMsIHdoZXJlIHRo
ZSBhZHZpY2UgZ2l2ZW4gaW4NCj4gdGhhdCBkb2N1bWVudCBpcyBzdXBlcmNlZGVkIGJ5IGEgc3Bl
Y2lmaWMgb3B0aW9uLiAgQXMgc3VjaCwgdGhpcyBlcnJvcg0KPiB3aWxsIGV2YXBvcmF0ZS4NCj4g
DQo+IA0KDQo=

From curtis@ipv6.occnc.com  Sat Jan 25 12:47:53 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 385151A0067 for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UQRph97MjfgL for <ietf@ietfa.amsl.com>; Sat, 25 Jan 2014 12:47:51 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 87A8F1A0045 for <ietf@ietf.org>; Sat, 25 Jan 2014 12:47:51 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0PKlmgS048899; Sat, 25 Jan 2014 15:47:49 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
To: Greg Daley <gdaley@au.logicalis.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Fri, 24 Jan 2014 03:38:44 +0000." <72381AF1F18BAE4F890A0813768D992817FD35E1@sdcexchms.au.logicalis.com>
Date: Sat, 25 Jan 2014 15:47:48 -0500
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:21:44 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, IETF discussion list <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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: Sat, 25 Jan 2014 20:47:53 -0000

In message <72381AF1F18BAE4F890A0813768D992817FD35E1@sdcexchms.au.logicalis.com>
Greg Daley writes:
 
> Hi Joel, 
>  
> > -----Original Message-----
> > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Joel M. Halpern
> > Sent: Friday, 24 January 2014 1:32 PM
> > To: Joe Touch; Edward Crabbe
> > Cc: mpls@ietf.org; Noel Chiappa; IETF discussion list
> > Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating
> > MPLS in UDP) to Proposed Standard
> > 
> > Joe, while your argument is internally consistent, it is not consistent with
> > history.  We have not demanded that tunnel entries behave fully like source
> > hosts for any of the other myriad kinds of tunnels we have done over the years.
>  
>  
> Actually, many of the tunnel protocols on the standards track have
> been either for upper-layer IP or Transport protocols or require
> congestion mitigation:
>  
>    RFC 4448 for EoMPLS, and 5994 for Ethernet pseudowires over MPLS
>    each ask that tunnelled protocols support congestion mechanisms,
>    RFC5085 and 5586: VCCV and BFD with VCCV define congestion
>    considerations for pseudowire tunnels.  RFC 4719 updated by RFC
>    5641: Ethernet pseudowires over L2TP (a UDP encapsulated protocol)
>    permit packet loss indications to take down the active circuit.
>    RFC 4454: ATM over L2TPv3 indicates that inelastic flows are
>    stopped when congestion occurs.
>  
> They (ATM over L2TPv3 and Ethernet PW over L2TPv3) also require usage
> over a traffic engineered network.
>  
> RFC 4817 MPLS over L2TPv3 requires non-IP upper layer protocols not to
> exceed the offered load of a typical TCP application on the same path.
>  
> For those protocols which have IP, UDP, TCP, SCCP or DCCP this is just
> passing the buck to the upper layer protocol (which is OK, so long as
> the application protocol in UDP has congestion measures). For
> environments where this cannot be relied upon, additional protocol
> specification and applicability statements have previously been
> applied.
>  
> > If we take your logic as stated, then the usage of IPSec over UDP would be
> > required to apply congestion control unless it knew that all the
> > content traffic was TCP.  Is that really your intent?
>  
> Actually, one of the compelling use cases for running MPLS over UDP
> (or L2TPv3) would be to encapsulate the traffic in ESP in order to
> combat passive snooping.
>  
> For ESP I believe the implicit assumption (via the Traffic Selectors
> in IKE) was that the upper layer protocol is IP or in transport mode
> another protocol such as TCP, UDP etc.
>  
> Sincerely, 
>  
> Greg Daley
> gdaley@au.logicalis.com


Reality check time.

To get the PW over MPLS drafts past the TSV AD there is a SHOULD
regarding congestion control.

AFAIK: No service providers ask for it.  No one implements it.  If
they did implement it no one would deploy it.

PW over MPLS is generally carrying relatively low volumes of high
priority traffic.  The TC bits (MPLS flavor of Diffserv DSCP) are used
to enforce the higher priority.  If congestion occurs other traffic on
that infrastructure (typically plain old Internet) sees loss.  That is
intended.  This is the reality of how PW over MPLS is deployed.

Anyone who knows of implementation or deployment of congestion control
for PW over MPLS can correct me.

I don't know about the "over GRE" or "over L2TP" tunneling.

Curtis

From geoff.mulligan@nist.gov  Sat Jan 25 08:52:01 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F5D71A0025; Sat, 25 Jan 2014 08:52:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bBbQ-ooDPmDH; Sat, 25 Jan 2014 08:51:57 -0800 (PST)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id B8FE11A001D; Sat, 25 Jan 2014 08:51:56 -0800 (PST)
Received: from [192.168.224.46] (unknown [209.117.47.254]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id C527623744; Sat, 25 Jan 2014 09:51:52 -0700 (MST)
Message-ID: <52E3EBA9.4050005@nist.gov>
Date: Sat, 25 Jan 2014 09:51:53 -0700
From: Geoff Mulligan <geoff.mulligan@nist.gov>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Bradner, Scott" <sob@harvard.edu>,  Mike StJohns <mstjohns@comcast.net>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
In-Reply-To: <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu>
Content-Type: multipart/alternative; boundary="------------090104000507010602050804"
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:22:00 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, Mary Barnes <mary.ietf.barnes@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 14:24:50 -0000

This is a multi-part message in MIME format.
--------------090104000507010602050804
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Scott,
   Maybe this is a potential rat-hole - I don't know - but what if:
     -  I'm working as a consultant and attending the IETF representing 
myself
     -  I know of IPR in someone else's contribution
     -  I'm participating in the discussion
     -  I'm under an NDA with that company that covers their IPR

    Geoff

*Presidential Innovation Fellow | Executive Office of the President | 
301.975.6283*

On 01/23/2014 10:58 AM, Bradner, Scott wrote:
> the actual rules are
> 	1/ if you know of any of your IPR in a contribution you make, you must disclose
> 	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
> 	    that involve that contribution, then you must disclose
> 	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
> 	    that involve that contribution, then you are requested to disclose
>
> see - its not that hard to say this briefly
>
> Scott
>
> On Jan 23, 2014, at 12:49 PM, Michael StJohns <mstjohns@comcast.net> wrote:
>
>> Is the issue the difference between "any contribution YOU MAKE" and "any contribution"?  E.g. if you happen to hear someone discussing something you think is covered by patent, you can't say anything, but conversely, if YOU are making a contribution that's covered by patent then the NDA doesn't apply (because you have approval to make the contribution and disclosure).
>>
>> Mike
>>
>>
>> At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:
>>
>>> This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says
>>>
>>>        . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>
>>> I do not agree to that - I can't given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test.
>>>
>>> I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me.
>>>
>>> Thank you,
>>>
>>> Cullen
>>>
>>> I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement.
>>>
>>>
>>>
>>> On Jan 23, 2014, at 9:44 AM, Russ Housley <housley@vigilsec.com> wrote:
>>>
>>>> It seems that the shorter one is now being used on the IETF web site:
>>>> http://www.ietf.org/about/note-well.html
>>>>
>>>>
>>>> On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:
>>>>
>>>>> Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.
>>>>>
>>>>> Mary.
>>>>>
>>>>>
>>>>> On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <sob@harvard.edu> wrote:
>>>>> you are correct - we (Barry, the IESG & me) discussed this before the IESG approved this text - they felt that
>>>>> being brief was more important than being fully accurate (or at least that is the way I expressed it)
>>>>>
>>>>> Scott
>>>>>
>>>>> Scott O Bradner
>>>>> Senior Technology Consultant
>>>>>
>>>>> Harvard University Information Technology
>>>>> Innovation & Architecture
>>>>> (P) +1 (617) 495 3864
>>>>> 8 Story St, room 5014
>>>>> Cambridge, MA 02138
>>>>>
>>>>>
>>>>>
>>>>> On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
>>>>>
>>>>>>
>>>>>> On Dec 16, 2013, at 12:56 PM, Barry Leiba <barryleiba@computer.org> wrote:
>>>>>>
>>>>>>> The IESG has made final edits to the updated Note Well statement, and
>>>>>>> it has been officially updated:
>>>>>>> http://www.ietf.org/about/note-well.html
>>>>>>>
>>>>>>> I have just uploaded the final versions of the Note Well meeting
>>>>>>> slides, attached to the bottom of the WG Chairs wiki:
>>>>>>> http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart
>>>>>>>
>>>>>>> Please use this new version now, and please remember that as you
>>>>>>> prepare slides for the London meeting.
>>>>>>>
>>>>>>> Barry
>>>>>>
>>>>>> The new note well says
>>>>>>
>>>>>>       . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.
>>>>>>
>>>>>> Is that true?  Or is it missing something along the lines of section y of BCP 79 such as
>>>>>>
>>>>>>   or must not contribute to or participate in IETF activities with
>>>>>>   respect to technologies that he or she reasonably and personally
>>>>>>   knows to be Covered by IPR which he or she will not disclose.
>>>>>>
>>>>>> Thanks, Cullen
>>


--------------090104000507010602050804
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Scott,<br>
    &nbsp; Maybe this is a potential rat-hole - I don't know - but what if:<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm working as a consultant and attending the IETF
    representing myself<br>
    &nbsp; &nbsp; -&nbsp; I know of IPR in someone else's contribution<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm participating in the discussion<br>
    &nbsp;&nbsp;&nbsp; -&nbsp; I'm under an NDA with that company that covers their IPR<br>
    <br>
    &nbsp;&nbsp; Geoff<br>
    <br>
    <small><b><font face="serif">Presidential Innovation Fellow |
          Executive Office of the President | 301.975.6283</font></b></small><br>
    <br>
    <div class="moz-cite-prefix">On 01/23/2014 10:58 AM, Bradner, Scott
      wrote:<br>
    </div>
    <blockquote
      cite="mid:77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu"
      type="cite">
      <pre wrap="">the actual rules are
	1/ if you know of any of your IPR in a contribution you make, you must disclose
	2/ if you know of any of your IPR in any contribution from someone else and you are participating in discussions
	    that involve that contribution, then you must disclose
	3/ if you know of any of your IPR in any contribution from someone else and you are not participating in discussions
	    that involve that contribution, then you are requested to disclose

see - its not that hard to say this briefly

Scott

On Jan 23, 2014, at 12:49 PM, Michael StJohns <a class="moz-txt-link-rfc2396E" href="mailto:mstjohns@comcast.net">&lt;mstjohns@comcast.net&gt;</a> wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">Is the issue the difference between "any contribution YOU MAKE" and "any contribution"?  E.g. if you happen to hear someone discussing something you think is covered by patent, you can't say anything, but conversely, if YOU are making a contribution that's covered by patent then the NDA doesn't apply (because you have approval to make the contribution and disclosure).

Mike


At 12:25 PM 1/23/2014, Cullen Jennings (fluffy) wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">This new note well is a real problem for me and  I can not register without clicking "I agree" to it. It is not consistent with the BCPs. The problem is the line that says

      . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.

I do not agree to that - I can't given my NDA with my employer does not allow me to disclose confidential information. Yes, I realize there is some weasel words near the top that say "Exceptions may apply." but that does not help me. When you are testifying in court on patents, credibility is incredibly important. You can not have the lawyers on the other side saying that you clicked yes I agree to the line above but you did not actually do what that lines says. You may think this does to matter but the exact topic of how Cisco employees deal with IPR at the IETF is a topic that I have testified on in an East Texas court so this really does happen and really does happen to me. It may happen to you next and you will be much happier if you say what you mean and mean what you say. This new note well fails that test. 

I realize some people would like to change the IETF policy to be that you do have to do what that line says but I do not think that is a change the IESG can make without IETF updating the BCP or at least having IETF consensus on the change. I would respectfully ask the IESG to change this line to something that is still brief but that people can agree with it. Simply adding something like "or not contribute to the discussion on that contribution" would probably solve this problem for me. 

Thank you, 

Cullen

I will note that above line is not consistent with Cisco employment contracts and if we can not resolve this I will be asking Cisco legal to inform Cisco employees they can not agree with this without violating their employment agreement. 



On Jan 23, 2014, at 9:44 AM, Russ Housley <a class="moz-txt-link-rfc2396E" href="mailto:housley@vigilsec.com">&lt;housley@vigilsec.com&gt;</a> wrote:

</pre>
          <blockquote type="cite">
            <pre wrap="">It seems that the shorter one is now being used on the IETF web site:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/about/note-well.html">http://www.ietf.org/about/note-well.html</a>


On Jan 8, 2014, at 3:57 PM, Mary Barnes wrote:

</pre>
            <blockquote type="cite">
              <pre wrap="">Personally, I've never seen significant value in this shorter note well and while others have been using this new text for the past few meetings, I've stuck to the old.   Now that this is considered the recommended note well for chairs to use, I guess I'll use it.  But, I personally think accuracy should trump brevity.  I think the "must" in that bullet  ought to at least be a should and that adding an "otherwise, one should not contribute to or participate in any related IETF activities." would add more value.   

Mary.


On Wed, Jan 8, 2014 at 1:17 PM, Bradner, Scott <a class="moz-txt-link-rfc2396E" href="mailto:sob@harvard.edu">&lt;sob@harvard.edu&gt;</a> wrote:
you are correct - we (Barry, the IESG &amp; me) discussed this before the IESG approved this text - they felt that
being brief was more important than being fully accurate (or at least that is the way I expressed it)

Scott

Scott O Bradner
Senior Technology Consultant

Harvard University Information Technology
Innovation &amp; Architecture
(P) +1 (617) 495 3864
8 Story St, room 5014
Cambridge, MA 02138



On Jan 8, 2014, at 2:13 PM, Cullen Jennings (fluffy) <a class="moz-txt-link-rfc2396E" href="mailto:fluffy@cisco.com">&lt;fluffy@cisco.com&gt;</a> wrote:

</pre>
              <blockquote type="cite">
                <pre wrap="">

On Dec 16, 2013, at 12:56 PM, Barry Leiba <a class="moz-txt-link-rfc2396E" href="mailto:barryleiba@computer.org">&lt;barryleiba@computer.org&gt;</a> wrote:

</pre>
                <blockquote type="cite">
                  <pre wrap="">The IESG has made final edits to the updated Note Well statement, and
it has been officially updated:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/about/note-well.html">http://www.ietf.org/about/note-well.html</a>

I have just uploaded the final versions of the Note Well meeting
slides, attached to the bottom of the WG Chairs wiki:
<a class="moz-txt-link-freetext" href="http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart">http://wiki.tools.ietf.org/group/wgchairs/wiki/WikiStart</a>

Please use this new version now, and please remember that as you
prepare slides for the London meeting.

Barry
</pre>
                </blockquote>
                <pre wrap="">

The new note well says

     . If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or patent applications, you must disclose that fact.

Is that true?  Or is it missing something along the lines of section y of BCP 79 such as

 or must not contribute to or participate in IETF activities with
 respect to technologies that he or she reasonably and personally
 knows to be Covered by IPR which he or she will not disclose.

Thanks, Cullen
</pre>
              </blockquote>
            </blockquote>
            <pre wrap="">
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">

</pre>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090104000507010602050804--

From mary.ietf.barnes@gmail.com  Fri Jan 24 13:03:57 2014
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB0211A01CC; Fri, 24 Jan 2014 13:03:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o8B-UlpczmVm; Fri, 24 Jan 2014 13:03:55 -0800 (PST)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DF42C1A011B; Fri, 24 Jan 2014 13:03:54 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id tp5so3345627ieb.5 for <multiple recipients>; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3YkDX4zhn1nYaoiS36WrwwgcRPtcfDDMk1/8IsENrMc=; b=FpZRjOdX97hLa+c7X7PTIMFPW0QweBUuDXNRXD5kg0h+0+65ZupmWnAfL+gfcxI4gg fUuVpPvl+LHB2t7I14gv6nl1r4M1Zart0UrDeFhfGjknB04UlASxy9jqnvBpuWHiKh8N rB2rI332CEjy0LxsXEr1eqM40ygFwhFNxhI5kz1GLhLloR5QGp594dySuCihmG3z/kbw 3c98NFWRdnGbUBzy/zoIdRK+hs08l2Ra6lCGfh513tk+k7eOaocCr27M979l0HQNLSN4 vAz/1g7X9+2eyViqNLfLMiNM16TwGnKkMyurbfpXuhvx8s9ecMQsW7pkXIRV4t86gWVh 7m6w==
MIME-Version: 1.0
X-Received: by 10.43.103.67 with SMTP id dh3mr2852899icc.60.1390597433633; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
Received: by 10.43.58.137 with HTTP; Fri, 24 Jan 2014 13:03:53 -0800 (PST)
In-Reply-To: <52E2CBF2.7070807@qti.qualcomm.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com>
Date: Fri, 24 Jan 2014 15:03:53 -0600
Message-ID: <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=bcaec517201f0eb23b04f0bdb293
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:23:07 -0800
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jan 2014 21:03:58 -0000
X-List-Received-Date: Fri, 24 Jan 2014 21:03:58 -0000

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

On Fri, Jan 24, 2014 at 2:24 PM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 1/24/14 10:31 AM, Cullen Jennings (fluffy) wrote:
>
>> Both Tom and Lars text would work for me. There seem to be so many ways
>> to write it such that it is still brief but captures the key elements of
>> the BCP.
>>
>> Pete, I really think it is that putting a sentences in it that is clearly
>> false is just wrong and I can not understand why you are arguing for that?
>>
>>
>
> So here's the key for me (and maybe this means we have a separate Note
> Well for the room from the one on the web site):
>
> In the room, I want something short enough that the chairs might actually
> be inclined to read out loud. It should have the three basic messages:
>
> - By participating here, you've agreed to our rules.
> - You can be recorded.
> - You have to disclose your IPR.
> Details on the above specified elsewhere. Go read if you're worried about
> it.
>

[MB] As a chair, I would not be reading the statement out loud. As far as
I'm concerned, my responsibility as a chair is to make sure everyone in the
room is aware of the IETF IPR rules - it's not up to me to summarize them
for the group.  And, saying go read the details "if you're worried" isn't
sufficient.  Everyone should have read the documents in detail and make
sure that anyone that has a say on how they disclose and deal with IPR in
IETF (i.e., corporate lawyers) are aware of IETF policy.  [/MB]

>
> I want those statements extended as little as possible to keep it so that
> the chair might be willing to say it.
>
> And (and this is probably the one where we might still disagree) if it's
> going to be inaccurate, and it will *have* to be inaccurate just by nature
> of being a summary, I want it to be inaccurate such that it includes *more*
> things to disclose than you are actually required to, not less. I don't
> want the excuse for not disclosing to be "I didn't understand all of the
> detail in BCP 79, but the Note Well sure didn't say that I had to disclose
> anything like *that*." If there's going to be an inaccuracy in the
> statement, I want it to be that BCP 79 says to disclose *less* than the
> summarized warning we give folks in the room.
>
> Both Tom's and Lars's summaries are fine, but they're not reasonable
> things to read in the room.
>
[MB] I don't at all think that's too much text to read aloud should someone
think they should do that.  We have lots of slides presented in WGs that
have just as much information and (sadly) sometimes those are just read out
versus someone just hitting on the key points. [/MB]

>
> We wrestled with this for a while. I'm open to suggestions. But the above
> are really my design criteria, at least for the one we put on a slide for
> the room.
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra">On Fri, Jan 24, 2014 at 2:24 PM=
, Pete Resnick <span dir=3D"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcom=
m.com" target=3D"_blank">presnick@qti.qualcomm.com</a>&gt;</span> wrote:<br=
><div class=3D"gmail_quote">
<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 1/24/14 10:31 AM, Culle=
n Jennings (fluffy) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Both Tom and Lars text would work for me. There seem to be so many ways to =
write it such that it is still brief but captures the key elements of the B=
CP.<br>
<br>
Pete, I really think it is that putting a sentences in it that is clearly f=
alse is just wrong and I can not understand why you are arguing for that?<b=
r>
=A0 =A0<br>
</blockquote>
<br></div>
So here&#39;s the key for me (and maybe this means we have a separate Note =
Well for the room from the one on the web site):<br>
<br>
In the room, I want something short enough that the chairs might actually b=
e inclined to read out loud. It should have the three basic messages:<br>
<br>
- By participating here, you&#39;ve agreed to our rules.<br>
- You can be recorded.<br>
- You have to disclose your IPR.<br>
Details on the above specified elsewhere. Go read if you&#39;re worried abo=
ut it.<br></blockquote><div><br></div><div>[MB] As a chair, I would not be =
reading the statement out loud. As far as I&#39;m concerned, my responsibil=
ity as a chair is to make sure everyone in the room is aware of the IETF IP=
R rules - it&#39;s not up to me to summarize them for the group. =A0And, sa=
ying go read the details &quot;if you&#39;re worried&quot; isn&#39;t suffic=
ient. =A0Everyone should have read the documents in detail and make sure th=
at anyone that has a say on how they disclose and deal with IPR in IETF (i.=
e., corporate lawyers) are aware of IETF policy. =A0[/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I want those statements extended as little as possible to keep it so that t=
he chair might be willing to say it.<br>
<br>
And (and this is probably the one where we might still disagree) if it&#39;=
s going to be inaccurate, and it will *have* to be inaccurate just by natur=
e of being a summary, I want it to be inaccurate such that it includes *mor=
e* things to disclose than you are actually required to, not less. I don&#3=
9;t want the excuse for not disclosing to be &quot;I didn&#39;t understand =
all of the detail in BCP 79, but the Note Well sure didn&#39;t say that I h=
ad to disclose anything like *that*.&quot; If there&#39;s going to be an in=
accuracy in the statement, I want it to be that BCP 79 says to disclose *le=
ss* than the summarized warning we give folks in the room.<br>

<br>
Both Tom&#39;s and Lars&#39;s summaries are fine, but they&#39;re not reaso=
nable things to read in the room.<br></blockquote><div>[MB] I don&#39;t at =
all think that&#39;s too much text to read aloud should someone think they =
should do that. =A0We have lots of slides presented in WGs that have just a=
s much information and (sadly) sometimes those are just read out versus som=
eone just hitting on the key points. [/MB]=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
We wrestled with this for a while. I&#39;m open to suggestions. But the abo=
ve are really my design criteria, at least for the one we put on a slide fo=
r the room.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
pr<br>
<br>
-- <br>
Pete Resnick&lt;<a href=3D"http://www.qualcomm.com/~presnick/" target=3D"_b=
lank">http://www.qualcomm.<u></u>com/~presnick/</a>&gt;<br>
Qualcomm Technologies, Inc. - <a href=3D"tel:%2B1%20%28858%29651-4478" valu=
e=3D"+18586514478" target=3D"_blank">+1 (858)651-4478</a><br>
<br>
</font></span></blockquote></div><br></div></div>

--bcaec517201f0eb23b04f0bdb293--

From narten@us.ibm.com  Mon Jan 27 05:55:57 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CC21A022E for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 05:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-uZdUw1ANkd for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 05:55:56 -0800 (PST)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id A0A8C1A0200 for <ietf@ietf.org>; Mon, 27 Jan 2014 05:55:56 -0800 (PST)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Mon, 27 Jan 2014 06:55:54 -0700
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Mon, 27 Jan 2014 06:55:52 -0700
Received: from b01cxnp22034.gho.pok.ibm.com (b01cxnp22034.gho.pok.ibm.com [9.57.198.24]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 0833B38C8027 for <ietf@ietf.org>; Mon, 27 Jan 2014 08:55:52 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0RDtpZJ55574672 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:55:52 GMT
Received: from d01av01.pok.ibm.com (localhost [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0RDtpQj021393 for <ietf@ietf.org>; Mon, 27 Jan 2014 08:55:51 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-76-156-52.mts.ibm.com [9.76.156.52]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0RDtoxK021360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 08:55:51 -0500
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s0RDtlLD031655; Mon, 27 Jan 2014 08:55:47 -0500
Date: Mon, 27 Jan 2014 08:55:47 -0500
Message-ID: <m3ppnda5r0.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
In-Reply-To: <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14012713-9332-0000-0000-000002E47A67
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:23:50 -0800
Cc: Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 13:55:58 -0000

At Mon, 27 Jan 2014 09:20:04 +0000,
Eggert, Lars wrote:
> 
> [1  <text/plain; us-ascii (quoted-printable)>]
> On 2014-1-25, at 21:24, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > It seems from the document that the content is descriptive of something
> > implemented by a single vendor. I applaud putting that information into the
> > public domain, but I don't understand the meaning of IETF consensus with respect
> > to this document.
> 
> +1
> 
> The Independent RFC Stream would seem more appropriate.

Well, if you run a document through the RFC Stream publication
process, it doesn't get the same level/type of review as does running
it through the IETF. At least in theory.

So if one wanted to get IETF folk to review it, running it through
IETF consensus (or something) doesn't seem unreasonable.

I don't know that we actually have an exact category for these kinds
of documents. Indeed, the categories we have are rather course, and
one can identify plenty of past documents that one might argue could
have/should have been published in a different stream than it
was. E.g., looking backwards for "cisco" documents published as RFCs:

> A new Request for Comments is now available in online RFC libraries.
>         RFC 6812
> 
>         Title:      Cisco Service-Level Assurance Protocol 
>         Status:     Informational
>         Stream:     Independent
>         Date:       January 2013
>         I-D Tag:    draft-cisco-sla-protocol-04.txt

It was published in the RFC editor stream.

On the other hand:

>         RFC 6759
>         Title:      Cisco Systems Export of Application 
>                     Information in IP Flow Information Export 
>                     (IPFIX) 
>         Status:     Informational
>         Stream:     IETF
>         Date:       November 2012
>         I-D Tag:    draft-claise-export-application-info-in-ipfix-10.txt

It was published via the IETF stream.

Thomas


From repenno@cisco.com  Mon Jan 27 01:38:51 2014
Return-Path: <repenno@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932C91A011C; Mon, 27 Jan 2014 01:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VV0_slMA765A; Mon, 27 Jan 2014 01:38:49 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) by ietfa.amsl.com (Postfix) with ESMTP id B64441A0117; Mon, 27 Jan 2014 01:38:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23400; q=dns/txt; s=iport; t=1390815527; x=1392025127; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=/PDkheEyah9yV21wccpxSltr10EWTKycXqUxebM/oVM=; b=ckcklDLGlDCWokqRwx/yAx9Cz1jk2eUwI532ccUbQffRA2FPThNCl8Pz Us77TfjggPL+9S1y2jx8LLyZaCtYVYboKvpxroIqRQqiiJcX0JJt6VYN8 QC48NA4P7NC9dyCEf9xPITWODoOsirFgHYn3EIwMboJL8U5asJDExqA8T w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkAHABwo5lKtJV2b/2dsb2JhbABZgkhEOFa0AIhTgQoWdIIlAQEBBC1MEgEIDgMDAQEBIQcoERQJCAEBBAENBQmHaAMRDcI8DYVWF4x3I4EqOBEGAYQ4BIVYkGOBbIEyiyuFQYMtgWlB
X-IronPort-AV: E=Sophos;i="4.95,728,1384300800"; d="scan'208,217";a="15747634"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-5.cisco.com with ESMTP; 27 Jan 2014 09:38:46 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0R9cjRb019913 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 09:38:46 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.37]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0123.003; Mon, 27 Jan 2014 03:38:45 -0600
From: "Reinaldo Penno (repenno)" <repenno@cisco.com>
To: Roni Even <ron.even.tlv@gmail.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "draft-ietf-pcp-description-option.all@tools.ietf.org" <draft-ietf-pcp-description-option.all@tools.ietf.org>
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Topic: Gen-ART LC review of draft-ietf-pcp-description-option-03
Thread-Index: Ac8ablfn3UbFfKwfSEyn6Pcjjhog/QAyx66AAA7VfwD//3wCgA==
Date: Mon, 27 Jan 2014 09:38:44 +0000
Message-ID: <CF0B68F0.8395%repenno@cisco.com>
In-Reply-To: <033d01cf1b42$854c10e0$8fe432a0$@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
x-originating-ip: [10.21.91.128]
Content-Type: multipart/alternative; boundary="_000_CF0B68F08395repennociscocom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 27 Jan 2014 07:23:56 -0800
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 09:38:51 -0000

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

Hi,

The idea is that it can be seen by the entity operating the PCP Server.

Thanks,

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Monday, January 27, 2014 at 1:31 AM
To: "mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>" <mo=
hamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>>, "draft-ie=
tf-pcp-description-option.all@tools.ietf.org<mailto:draft-ietf-pcp-descript=
ion-option.all@tools.ietf.org>" <draft-ietf-pcp-description-option.all@tool=
s.ietf.org<mailto:draft-ietf-pcp-description-option.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: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03
Resent-From: <draft-alias-bounces@tools.ietf.org<mailto:draft-alias-bounces=
@tools.ietf.org>>
Resent-To: <dthaler@microsoft.com<mailto:dthaler@microsoft.com>>, <dwing@ci=
sco.com<mailto:dwing@cisco.com>>, "mohamed.boucadair@orange.com<mailto:moha=
med.boucadair@orange.com>" <mohamed.boucadair@orange.com<mailto:mohamed.bou=
cadair@orange.com>>, Cisco Employee <repenno@cisco.com<mailto:repenno@cisco=
.com>>, <ted.lemon@nominum.com<mailto:ted.lemon@nominum.com>>
Resent-Date: Monday, January 27, 2014 at 1:35 AM

Hi Med,
Inline
Roni

From: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com> [ma=
ilto:mohamed.boucadair@orange.com]
Sent: 27 January, 2014 10:31 AM
To: Roni Even; draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:=
draft-ietf-pcp-description-option.all@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@ie=
tf.org>
Subject: RE: Gen-ART LC review of draft-ietf-pcp-description-option-03

Dear Roni,
Thank you for the review.
Please see inline.
Cheers,
Med
De : Roni Even [mailto:ron.even.tlv@gmail.com]
Envoy=E9 : dimanche 26 janvier 2014 09:13
=C0 : draft-ietf-pcp-description-option.all@tools.ietf.org<mailto:draft-iet=
f-pcp-description-option.all@tools.ietf.org>
Cc : ietf@ietf.org<mailto:ietf@ietf.org>; gen-art@ietf.org<mailto:gen-art@i=
etf.org>
Objet : Gen-ART LC review of draft-ietf-pcp-description-option-03

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-pcp-description-option-03

Reviewer: Roni Even

Review Date:2014=961-26

IETF LC End Date: 2014=962-4

IESG Telechat date:



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





Major issues:



Minor issues:



1.       I am not sure what the use of the =93description=94 option is. I c=
an see how to create one but as for usage the only text I can see is =93Que=
rying the PCP server to get the description text of an existing mapping is =
out of scope.=94 I think that the document should provide information about=
 the purpose of this option.

[Med] The main usage is for a user to associate a textual description with =
a mapping. This is captured by this text =93   This option can be used by a=
 user (or an application) to indicate a
   description associated with a given mapping such as "FTP server", "My
   remote access to my CP router", "Camera", "Network attached storage
   serve", etc.

=94

[Roni Even] This is motivation but it is not clear why the user does it if =
no one can see it or does anything with it. It is kept on the server but no=
t used by anyone?


Nits/editorial comments:

  1.  The IANA section should provide enough information to fill the regist=
ry http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#option=
s
[Med] Required information as per RFC6887 is provided in http://tools.ietf.=
org/html/draft-ietf-pcp-description-option-03#section-2.
[Roni Even] So section 5 should point to the definition is section 2



--_000_CF0B68F08395repennociscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A71178D9E1B5CB489BEA10CF0E9BAC95@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>Hi,</div>
<div><br>
</div>
<div>The idea is that it can be seen by the entity operating the PCP Server=
.&nbsp;</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>Roni Even &lt;<a href=3D"mail=
to:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Monday, January 27, 2014 at 1=
:31 AM<br>
<span style=3D"font-weight:bold">To: </span>&quot;<a href=3D"mailto:mohamed=
.boucadair@orange.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=
=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&g=
t;, &quot;<a href=3D"mailto:draft-ietf-pcp-description-option.all@tools.iet=
f.org">draft-ietf-pcp-description-option.all@tools.ietf.org</a>&quot;
 &lt;<a href=3D"mailto:draft-ietf-pcp-description-option.all@tools.ietf.org=
">draft-ietf-pcp-description-option.all@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:ietf@ie=
tf.org">ietf@ietf.org</a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@i=
etf.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>RE: Gen-ART LC review of d=
raft-ietf-pcp-description-option-03<br>
<span style=3D"font-weight:bold">Resent-From: </span>&lt;<a href=3D"mailto:=
draft-alias-bounces@tools.ietf.org">draft-alias-bounces@tools.ietf.org</a>&=
gt;<br>
<span style=3D"font-weight:bold">Resent-To: </span>&lt;<a href=3D"mailto:dt=
haler@microsoft.com">dthaler@microsoft.com</a>&gt;, &lt;<a href=3D"mailto:d=
wing@cisco.com">dwing@cisco.com</a>&gt;, &quot;<a href=3D"mailto:mohamed.bo=
ucadair@orange.com">mohamed.boucadair@orange.com</a>&quot; &lt;<a href=3D"m=
ailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.com</a>&gt;,
 Cisco Employee &lt;<a href=3D"mailto:repenno@cisco.com">repenno@cisco.com<=
/a>&gt;, &lt;<a href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com=
</a>&gt;<br>
<span style=3D"font-weight:bold">Resent-Date: </span>Monday, January 27, 20=
14 at 1:35 AM<br>
</div>
<div><br>
</div>
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns: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 Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* 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-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
p.Textebrut, li.Textebrut, div.Textebrut
	{mso-style-name:"Texte brut";
	mso-style-link:"Texte brut Car";
	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";}
span.TextebrutCar
	{mso-style-name:"Texte brut Car";
	mso-style-priority:99;
	mso-style-link:"Texte brut";
	font-family:Consolas;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle24
	{mso-style-type:personal;
	font-family:"Courier New";
	color:#1F497D;}
p.PrformatHTML, li.PrformatHTML, div.PrformatHTML
	{mso-style-name:"Pr\00E9format\00E9 HTML";
	mso-style-link:"Pr\00E9format\00E9 HTML Car";
	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";}
span.PrformatHTMLCar
	{mso-style-name:"Pr\00E9format\00E9 HTML Car";
	mso-style-priority:99;
	mso-style-link:"Pr\00E9format\00E9 HTML";
	font-family:"Courier New";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle29
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:354504229;
	mso-list-type:hybrid;
	mso-list-template-ids:1129510024 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;}
@list l1
	{mso-list-id:458913598;
	mso-list-type:hybrid;
	mso-list-template-ids:-1849926478 67698703 67698713 67698715 67698703 6769=
8713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l2
	{mso-list-id:2105032897;
	mso-list-template-ids:-1035336528;}
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"><span style=3D"color:#1F497D">Hi Med, <o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Inline<o:p></o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Roni<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;">From:<=
/span></b><span style=3D"font-size: 10pt; font-family: Tahoma, sans-serif;"=
>
<a href=3D"mailto:mohamed.boucadair@orange.com">mohamed.boucadair@orange.co=
m</a> [<a href=3D"mailto:mohamed.boucadair@orange.com">mailto:mohamed.bouca=
dair@orange.com</a>]
<br>
<b>Sent:</b> 27 January, 2014 10:31 AM<br>
<b>To:</b> Roni Even; <a href=3D"mailto:draft-ietf-pcp-description-option.a=
ll@tools.ietf.org">
draft-ietf-pcp-description-option.all@tools.ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"m=
ailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Subject:</b> RE: Gen-ART LC review of draft-ietf-pcp-description-option-=
03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Dear Roni,<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Thank you for the revi=
ew.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Please see inline.<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Cheers,<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size: 10pt; line-height: 115%; f=
ont-family: 'Courier New'; color: rgb(31, 73, 125);">Med<o:p></o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<b><span lang=3D"FR" style=3D"font-size: 10pt; font-family: Tahoma, sans-se=
rif;">De&nbsp;:</span></b><span lang=3D"FR" style=3D"font-size: 10pt; font-=
family: Tahoma, sans-serif;"> Roni Even [<a href=3D"mailto:ron.even.tlv@gma=
il.com">mailto:ron.even.tlv@gmail.com</a>]
<br>
<b>Envoy=E9&nbsp;:</b> dimanche 26 janvier 2014 09:13<br>
<b>=C0&nbsp;:</b> <a href=3D"mailto:draft-ietf-pcp-description-option.all@t=
ools.ietf.org">
draft-ietf-pcp-description-option.all@tools.ietf.org</a><br>
<b>Cc&nbsp;:</b> <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a hre=
f=3D"mailto:gen-art@ietf.org">
gen-art@ietf.org</a><br>
<b>Objet&nbsp;:</b> Gen-ART LC review of draft-ietf-pcp-description-option-=
03<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><span lang=3D"FR"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><a name=3D"OLE_LINK2"></a><a name=3D"OLE_LINK1"></a>=
I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen=
/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal">Please resolve these comments along with any other L=
ast Call comments you may receive.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Document:&nbsp;
<span style=3D"font-size: 10.5pt; line-height: 115%; font-family: 'Courier =
New';">draft-ietf-pcp-description-option-03<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Reviewer: Roni Even<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Review Date:2014=961-26<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>IETF LC End Date: 2014=962-4<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>IESG Telechat date:
<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Summary: This draft is almost ready for publication as a standard track RF=
C.<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Major issues:<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
>Minor issues:<o:p></o:p></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText" style=3D"mso-margin-top-alt:0in;margin-right:0in;=
margin-bottom:0in;margin-left:.5in;margin-bottom:.0001pt;text-indent:-.25in=
;mso-list:l0 level1 lfo2">
<!--[if !supportLists]--><span style=3D"mso-list:Ignore">1.<span style=3D"f=
ont-style: normal; font-variant: normal; font-weight: normal; font-size: 7p=
t; line-height: normal; font-family: 'Times New Roman';">&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;
</span></span><!--[endif]--><span dir=3D"LTR"></span>I am not sure what the=
 use of the =93description=94 option is. I can see how to create one but as=
 for usage the only text I can see is =93Querying the PCP server to get the=
 description text of an existing mapping
 is out of scope.=94 I think that the document should provide information a=
bout the purpose of this option.<o:p></o:p></p>
<pre><b><i><span style=3D"color:#1F497D">[Med] The main usage is for a user=
 to associate a textual description with a mapping. This is captured by thi=
s text =93</span></i></b>&nbsp;&nbsp; This option can be used by a user (or=
 an application) to indicate a<o:p></o:p></pre>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; d=
escription associated with a given mapping such as &quot;FTP server&quot;, =
&quot;My<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; r=
emote access to my CP router&quot;, &quot;Camera&quot;, &quot;Network attac=
hed storage<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:0in;margin-bottom:.0001pt;lin=
e-height:normal">
<span style=3D"font-size: 10pt; font-family: 'Courier New';">&nbsp;&nbsp; s=
erve&quot;, etc.<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><b><i><span style=3D"font-size: 10pt; line-height: 115%; font-family: 'Cou=
rier New'; color: rgb(31, 73, 125);">=94<o:p></o:p></span></i></b></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><b><i><span style=3D"color:#1F497D">[Roni Even]
</span></i></b><span style=3D"color:#1F497D">This is motivation but it is n=
ot clear why the user does it if no one can see it or does anything with it=
. It is kept on the server but not used by anyone?<o:p></o:p></span></p>
<p class=3D"MsoPlainText" style=3D"margin-bottom:0in;margin-bottom:.0001pt"=
><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal">Nits/editorial comments:<o:p></o:p></p>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo5">The IANA section =
should provide enough information to fill the registry
<a href=3D"http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xm=
l#options">
http://www.iana.org/assignments/pcp-parameters/pcp-parameters.xml#options</=
a> <o:p>
</o:p></li></ol>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size: 10pt; line-height: 1=
15%; font-family: 'Courier New'; color: rgb(31, 73, 125);">[Med] Required i=
nformation as per RFC6887 is provided in
<a href=3D"http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#=
section-2">
http://tools.ietf.org/html/draft-ietf-pcp-description-option-03#section-2</=
a>. <o:p>
</o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"color:#1F497D">[Roni Even] </sp=
an></i></b><span style=3D"color:#1F497D">So section 5 should point to the d=
efinition is section 2<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>

--_000_CF0B68F08395repennociscocom_--

From john-ietf@jck.com  Mon Jan 27 07:46:03 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2D81A0228; Mon, 27 Jan 2014 07:46:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQKc8X5igdCb; Mon, 27 Jan 2014 07:46:01 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id CB2F61A021B; Mon, 27 Jan 2014 07:45:57 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W7oNk-000D0z-9p; Mon, 27 Jan 2014 10:45:52 -0500
X-Vipre-Scanned: 08B93933002C3108B93A80-TDI
Date: Mon, 27 Jan 2014 10:45:51 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Problem with new Note Well
Message-ID: <2B1C52E87C5B3A5C2D68E3E1@[192.168.1.128]>
In-Reply-To: <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <CAHBDyN5dm+=najR5LVGDyxrcpAyivx+hEnF0Zzhzzik6wmO_gw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 15:46:03 -0000

--On Friday, 24 January, 2014 15:03 -0600 Mary Barnes
<mary.ietf.barnes@gmail.com> wrote:

>...
> [MB] As a chair, I would not be reading the statement out
> loud. As far as I'm concerned, my responsibility as a chair is
> to make sure everyone in the room is aware of the IETF IPR
> rules - it's not up to me to summarize them for the group.

For both this new statement and its predecessors, it seems to me
that we have to recognize the limitations of what we are trying
to do and think about and balance policy plans accordingly.   If
your "responsibility as a chair is to make sure everyone in the
room is aware..." then you need to repeat the announcement every
time someone walks into the room who wasn't there when you made
your check, showed your slides, or did your reading.  Unless we
are going to take to locking doors so that no one can enter a WG
meeting after the "Note Well" announcement is made, such
repetition would be disruptive and absurd.  

Similarly, if one were really inclined to "make sure", the right
way to do it would be to ask at the beginning of the session for
everyone who was familiar with the IPR policies to put up their
hands, ask everyone else to leave, and then take pictures of
everyone who was left for later correlation with the blue
sheets.  But that is almost equally absurd and the community has
been fairly clear about its distaste for pictures that can be
correlated with names.

Given our registration procedures, we could take the possession
of a badge as evidence that someone had been adequately exposed
to the Note Well (if not actually to the BCP) and arrange to
check for badges at meeting room doors.  But we've decided, IMO,
for good reason, to not do that either.


> And, saying go read the details "if you're worried" isn't
> sufficient.  Everyone should have read the documents in detail
> and make sure that anyone that has a say on how they disclose
> and deal with IPR in IETF (i.e., corporate lawyers) are aware
> of IETF policy.  [/MB]

Yes.  But "the documents" there are BCP 79 (and probably BCP 78
and various Trust policies) and not some summary.  And, no
matter how much it might make those who are IPR-fascinated
happy, as a WG participant and sometime chair, I don't want
people spending time in WG meetings trying to decipher BCP79 and
its implications (or bringing their lawyers with them to do so)
any more than I want them buried in email -- I want them paying
attention to the meeting, else why are they present.  

For someone (and their organizations if relevant) who is
adequately familiar with BCP 79 before walking into the WG
meeting, further announcements, regardless of their precise
content, are a waste of time except maybe as a small reminder.
For anyone who isn't, the announcements are useless unless we
are just trying to tell them that they might be in big trouble
if they stay in the room.

best,
   john

 





From simon.perreault@viagenie.ca  Mon Jan 27 07:46:04 2014
Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46F1A1A0228 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 07:46:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.436
X-Spam-Level: 
X-Spam-Status: No, score=-2.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihB6oh-Dretb for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 07:46:02 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id CDA911A0235 for <ietf@ietf.org>; Mon, 27 Jan 2014 07:45:58 -0800 (PST)
Received: from porto.nomis80.org (ringo.viagenie.ca [IPv6:2620:0:230:c000:3e97:eff:fe0b:dd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 85554403CA for <ietf@ietf.org>; Mon, 27 Jan 2014 10:45:56 -0500 (EST)
Message-ID: <52E67F34.1050404@viagenie.ca>
Date: Mon, 27 Jan 2014 10:45:56 -0500
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com> <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
In-Reply-To: <035301cf1b46$d54ba980$7fe2fc80$@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 15:46:04 -0000

Le 2014-01-27 05:02, Roni Even a écrit :
> This should be stated and I assume that it is not for standardization
> but not clear why the entity operating the PCP server needs it, is it
> described in another document.
>
> I am curious why querying the PCP server is “out of scope” and not is
> “for further work”.

Example use case: you have several hosts in your home that do PCP 
automatically. For example, you start up Transmission, a BitTorrent 
client, and that automatically fires a PCP request to create a mapping. 
Transmission could set a description such as "Transmission BitTorrent 
client running on Roni Even's MacBook Pro". This is useful when you 
access your home router's administration web interface and see the list 
of mappings created with PCP. You can immediately understand what it is 
that is opening holes in your firewall/NAT.

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

From rdroms.ietf@gmail.com  Mon Jan 27 07:58:27 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE5681A02B3; Mon, 27 Jan 2014 07:58:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QBsWDFYo5GeJ; Mon, 27 Jan 2014 07:58:26 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1EFBD1A027C; Mon, 27 Jan 2014 07:58:26 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so7379470qac.22 for <multiple recipients>; Mon, 27 Jan 2014 07:58:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L3MAeMhzScFfm4/v5q/RgAlbRPh5GGW8EJbvSfBJzuc=; b=HARCeHxEQa+RbKRVts3wJ/1C7OoUQaWfDQNgDm56N1e+AFNbadknfp7psIod+FyZBW bS2TB/39ZVhDmF2ePHwGE432WSq72xeEzncrzM8YB36po1RN93AmzmDLERLRfkLxyUwG rXiq2wKYcpFdoc3OHsHbkLKlnMx4m3j2Dck+S/EFzJcr2Kl/KarP03ZYOh3sQneRi/lu WUQ8dzCdl6E8js2GEeji1+xRMOjCKogzgTPYg1Gf1efRYmrpT+4t3dpz/35ZV8U2c0hw CefqNGcfud95P727vZk5SjXd/UN1zQA0fDeqUAssdXgan/xWKWBLmrhU/39RUeSDSv+Z orVQ==
X-Received: by 10.140.46.119 with SMTP id j110mr41723062qga.32.1390838303786;  Mon, 27 Jan 2014 07:58:23 -0800 (PST)
Received: from [161.44.68.171] ([161.44.68.171]) by mx.google.com with ESMTPSA id 72sm8722607qgv.19.2014.01.27.07.58.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Jan 2014 07:58:22 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
Date: Mon, 27 Jan 2014 10:58:20 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C62FB50-C8E8-4CEA-BD42-B64076883379@gmail.com>
References: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1510)
Cc: roll@ietf.org, "roll-ads@tools.ietf.org" <roll-ads@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 15:58:28 -0000

I've reviewed draft-ietf-roll-trickle-mcast-06.txt.  The issues I raised =
during the WG last call have been addressed and, in my opinion, the =
document is now ready for publication.

- Ralph


On Jan 24, 2014, at 3:16 PM 1/24/14, The IESG <iesg-secretary@ietf.org> =
wrote:

> The IESG has received a request from the Routing Over Low power and =
Lossy
> networks WG (roll) to consider the following document:
> - 'Multicast Protocol for Low power and Lossy Networks (MPL)'
>  <draft-ietf-roll-trickle-mcast-06.txt> as Proposed Standard
>=20
> This is a second last call, the first one having been abandoned to =
send
> the document back to the working group. But the latest revision =
addresses
> comments that were received during the first last call.
>=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 2014-02-07. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>   This document specifies the Multicast Protocol for Low power and
>   Lossy Networks (MPL) that provides IPv6 multicast forwarding in
>   constrained networks.  MPL avoids the need to construct or maintain
>   any multicast forwarding topology, disseminating messages to all MPL
>   Forwarders in an MPL Domain.  MPL uses the Trickle algorithm to
>   manage message transmissions for both control and data-plane
>   messages.  Different Trickle parameter configurations allow MPL to
>   trade between dissemination latency and transmission efficiency.
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ballot/
>=20
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   http://datatracker.ietf.org/ipr/1858/
>=20
>=20
>=20


From jari.arkko@piuha.net  Mon Jan 27 08:02:15 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13B4C1A0297; Mon, 27 Jan 2014 08:02:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ekyPX4cf7-LX; Mon, 27 Jan 2014 08:02:13 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 5ADA61A0231; Mon, 27 Jan 2014 08:02:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D56202CCBE; Mon, 27 Jan 2014 18:02:10 +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 I6CU8y0JMJ6C; Mon, 27 Jan 2014 18:02:10 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 62CFC2CC5D; Mon, 27 Jan 2014 18:02:10 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Third party disclosures and NDAs (Re: Problem with new Note Well )
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E3EBA9.4050005@nist.gov>
Date: Mon, 27 Jan 2014 18:02:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>
To: Geoff Mulligan <geoff.mulligan@nist.gov>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:02:15 -0000

Starting a separate thread, because this is not related to the original =
complaint about inaccurate new note well text.

>   Maybe this is a potential rat-hole - I don't know - but what if:
>     -  I'm working as a consultant and attending the IETF representing =
myself
>     -  I know of IPR in someone else's contribution
>     -  I'm participating in the discussion
>     -  I'm under an NDA with that company that covers their IPR

That is a rat-^H^H^H^Hhard problem. Something has to give. You can't =
simultaneously follow two incompatible sets of rules. If you end up in =
that situation and can't convince parties to disclose, maybe =
"participating in the discussion" has to give. Of course this is a =
specific example of things that can happen in people's lives in other =
ways, too. Two consulting contracts that have incompatible requirements. =
Board position and a job that creates a conflict interest for you to be =
in the board. And so on.

Jari


From scott.brim@gmail.com  Mon Jan 27 08:07:04 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5982E1A029C; Mon, 27 Jan 2014 08:07:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AubJ-WyhqhLk; Mon, 27 Jan 2014 08:07:03 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 01DBC1A0255; Mon, 27 Jan 2014 08:07:02 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so6689502obc.11 for <multiple recipients>; Mon, 27 Jan 2014 08:07:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=S/l1ErEhC7iExKjtlMhPgmbw03D93KhGidOWBeFzf4A=; b=OYwtIBPzEteL/WaLq0A5ke7unyqYa2kmyqaBgRgxROR4NyYLZ3/urpOQjqUpqvLrUS rgl2XcXZBhPW4qxuimDdrxFWNX/Je1eu85ZdATwoBP/yz9MnbIEBt/I1jradsoSCFM/R op6n6+y8hPV6u5fJZ14ETujF1TiRTKUy1sYnXC6j9VFSGPqYJEb6VK6IA3BZJzSu4I4/ khHVzo6sLm0rbmy5+V3nye1lEusRCE1Dzud8vNep3pTl6+o6uUFAZx8wkFTHt54SiXxA HwLnekNw6O5MdgXutrupkcQOernlWnCJIxnBZ1Fcmkdqbr0uxa36F+k5zyPPiXe/XEG1 QZuw==
X-Received: by 10.182.148.106 with SMTP id tr10mr617384obb.65.1390838820642; Mon, 27 Jan 2014 08:07:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 27 Jan 2014 08:06:40 -0800 (PST)
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 Jan 2014 11:06:40 -0500
Message-ID: <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Geoff Mulligan <geoff.mulligan@nist.gov>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:07:04 -0000

On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> Starting a separate thread, because this is not related to the original c=
omplaint about inaccurate new note well text.
>
>>   Maybe this is a potential rat-hole - I don't know - but what if:
>>     -  I'm working as a consultant and attending the IETF representing m=
yself
>>     -  I know of IPR in someone else's contribution
>>     -  I'm participating in the discussion
>>     -  I'm under an NDA with that company that covers their IPR
>
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simu=
ltaneously follow two incompatible sets of rules. If you end up in that sit=
uation and can't convince parties to disclose, maybe "participating in the =
discussion" has to give. Of course this is a specific example of things tha=
t can happen in people's lives in other ways, too. Two consulting contracts=
 that have incompatible requirements. Board position and a job that creates=
 a conflict interest for you to be in the board. And so on.
>
> Jari

Right. IMHO if you haven't anticipated this situation you would do
best to shut up until you talk to your lawyers. However, thankfully,
you have learned that you need to anticipate the problem and you can
talk to them before the problem arises.

Scott

From hallam@gmail.com  Mon Jan 27 08:12:42 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 078CE1A0242; Mon, 27 Jan 2014 08:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pUxH57PAJB1P; Mon, 27 Jan 2014 08:12:39 -0800 (PST)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id 425271A0231; Mon, 27 Jan 2014 08:12:39 -0800 (PST)
Received: by mail-lb0-f182.google.com with SMTP id w7so4699692lbi.27 for <multiple recipients>; Mon, 27 Jan 2014 08:12:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Ii/ajS5A5SGtzVnZV8vN7T/VUx7HtNL9YBWfKVr5FrM=; b=c9D2TTqk+p/6W77E2nTeJBio2l7cEJyxTJbouD6lUCwlK743gtvru49pnlZGvtfOsI Ha+1DhAvMW47ZGszlO8HnGKneDWrgMePv3JR4fbVFzEC1B90fhldLmf9nncAvvgb954O jesqxaq9shsvzhzEna9PGY5b8RTyrXDqw7xKysd/uzfcLTtw3e57GrL1Ju8QKcEh2wcy XtPiwfVAm5t+KmyX5zcbYV8nJO2APKnTSgWhZKDfz0wACEvvgZ0ONN5z+5eklybciehs QVmjNDCHBKd13E9mZHqCrJZaGpWDI8vrw3x5mCYZaKd2GU6w3PRN9jWXXYKjtBfaczOU xY1A==
MIME-Version: 1.0
X-Received: by 10.153.0.33 with SMTP id av1mr12750303lad.14.1390839155701; Mon, 27 Jan 2014 08:12:35 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 27 Jan 2014 08:12:35 -0800 (PST)
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
Date: Mon, 27 Jan 2014 11:12:35 -0500
Message-ID: <CAMm+LwgArQzBO+fs=k=oc31s9ShCnYJF-B25WHw4rYUGCiQ57w@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a11381264d0beb604f0f5f95a
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, Geoff Mulligan <geoff.mulligan@nist.gov>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:12:42 -0000

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

On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> Starting a separate thread, because this is not related to the original
> complaint about inaccurate new note well text.
>
> >   Maybe this is a potential rat-hole - I don't know - but what if:
> >     -  I'm working as a consultant and attending the IETF representing
> myself
> >     -  I know of IPR in someone else's contribution
> >     -  I'm participating in the discussion
> >     -  I'm under an NDA with that company that covers their IPR
>
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't
> simultaneously follow two incompatible sets of rules. If you end up in that
> situation and can't convince parties to disclose, maybe "participating in
> the discussion" has to give. Of course this is a specific example of things
> that can happen in people's lives in other ways, too. Two consulting
> contracts that have incompatible requirements. Board position and a job
> that creates a conflict interest for you to be in the board. And so on.
>
> Jari
>
>
And it is not just IPR, it is IPR claims that are covered.

I know a lot of IPR claims that are utter hogwash. But if I am working with
a company that is defending itself against a lawsuit asserting that claim,
their lawyers usually don't want that to be public knowledge until they
tell the plaintiff.

The IETF IPR rules were crafted to address one particular IPR problem that
doesn't really exist any more because the courts have effectively
eliminated any incentive. Anyone who goes to a standards body with the
objective of covertly ensuring that the standard necessarily infringes is
risking getting their patent invalidated at the very least.

The IPR problems we have at the moment are an industry wide patent war that
has broken out between groups of companies with very broad portfolios of
claims which come from significant investments in R&D and a large number of
non-practicing entities, some of which have attempted claims that are so
ridiculous the lawyers behind them are facing civil lawsuits from the FTC.


-- 
Website: http://hallambaker.com/

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <span dir=3D"ltr">&lt;=
<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari.arkko@piuha.=
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">Starting a separate thread, because this is =
not related to the original complaint about inaccurate new note well text.<=
br>

<br>
&gt; =A0 Maybe this is a potential rat-hole - I don&#39;t know - but what i=
f:<br>
&gt; =A0 =A0 - =A0I&#39;m working as a consultant and attending the IETF re=
presenting myself<br>
&gt; =A0 =A0 - =A0I know of IPR in someone else&#39;s contribution<br>
&gt; =A0 =A0 - =A0I&#39;m participating in the discussion<br>
&gt; =A0 =A0 - =A0I&#39;m under an NDA with that company that covers their =
IPR<br>
<br>
That is a rat-^H^H^H^Hhard problem. Something has to give. You can&#39;t si=
multaneously follow two incompatible sets of rules. If you end up in that s=
ituation and can&#39;t convince parties to disclose, maybe &quot;participat=
ing in the discussion&quot; has to give. Of course this is a specific examp=
le of things that can happen in people&#39;s lives in other ways, too. Two =
consulting contracts that have incompatible requirements. Board position an=
d a job that creates a conflict interest for you to be in the board. And so=
 on.<br>

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br>And it is not just IPR, it is IPR clai=
ms that are covered.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">I know a lot of IPR claims that are utter hogwash. But if =
I am working with a company that is defending itself against a lawsuit asse=
rting that claim, their lawyers usually don&#39;t want that to be public kn=
owledge until they tell the plaintiff.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The IETF IP=
R rules were crafted to address one particular IPR problem that doesn&#39;t=
 really exist any more because the courts have effectively eliminated any i=
ncentive. Anyone who goes to a standards body with the objective of covertl=
y ensuring that the standard necessarily infringes is risking getting their=
 patent invalidated at the very least.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The IPR pro=
blems we have at the moment are an industry wide patent war that has broken=
 out between groups of companies with very broad portfolios of claims which=
 come from significant investments in R&amp;D and a large number of non-pra=
cticing entities, some of which have attempted claims that are so ridiculou=
s the lawyers behind them are facing civil lawsuits from the FTC.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><br></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>
</div></div>

--001a11381264d0beb604f0f5f95a--

From jari.arkko@piuha.net  Mon Jan 27 08:17:26 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5283B1A02E8; Mon, 27 Jan 2014 08:17:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qCyDXtBA5IXn; Mon, 27 Jan 2014 08:17:25 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C90FF1A025D; Mon, 27 Jan 2014 08:17:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4EFBB2CCBE; Mon, 27 Jan 2014 18:17:22 +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 oVvaTZl1HdlB; Mon, 27 Jan 2014 18:17: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 BB37C2CC5D; Mon, 27 Jan 2014 18:17:20 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well 
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <52E5E624.4080003@gmail.com>
Date: Mon, 27 Jan 2014 18:17:20 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:17:26 -0000

All - it is clear that you have a concern about the new note well text. =
The problem has been well articulated; personally, I'd be happy with =
some of the edits suggested. However, it is probably better if we do the =
word-smithing separately and come back with a proposal. I have asked the =
IESG to consider the situation and the need for a new version of the =
note well and/or reverting to the old version.

Thanks for the feedback, as always!

Jari


From stbryant@cisco.com  Mon Jan 27 08:40:58 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B911A0276; Mon, 27 Jan 2014 08:40:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUYC7CJ9KC9D; Mon, 27 Jan 2014 08:40:56 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id C017E1A029C; Mon, 27 Jan 2014 08:40:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=822; q=dns/txt; s=iport; t=1390840854; x=1392050454; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iaxdndm+s+9xAew4nIrH3Gjx/fIspLkrns2aB9rsCwM=; b=Hpug268PCSHkRhvtUcpntgjdTLXFk18GSvKLCfh88PMtvRi8DhV3YCHA DxKmvlRkLlsQoGdjV2dgZ90TtHo3r3STD1dXNMICmstmf4BWy6H5JEqYN jKM9psrBv3cSNHW3pBfk4g1syqnwbvuSrZXQd16X+3/FF5f6n4/ScUr2L E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAPyK5lKQ/khR/2dsb2JhbABZDoJ+OL0vgRUWdIIlAQEBBDhAARALGAkWBAsJAwIBAgFFBgEMAQcBAQWHfA3HEReOPAEBTweEOAEDmCeSHoFvfz+BcQ
X-IronPort-AV: E=Sophos;i="4.95,729,1384300800";  d="scan'208";a="4256365"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 27 Jan 2014 16:40:53 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0RGeq4x018651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 16:40:52 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0RGeou7025359; Mon, 27 Jan 2014 16:40:51 GMT
Message-ID: <52E68C12.2050308@cisco.com>
Date: Mon, 27 Jan 2014 16:40:50 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, curtis@ipv6.occnc.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu>
In-Reply-To: <52E2BBC0.2030203@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:40:58 -0000

On 24/01/2014 19:15, Joe Touch wrote:
>
>> This eliminates the "expands the reach of MPLS argument".
>>
>> First UDP checksums:
>>
>>    The UDP checksum is at the beginning of the payload.  Please see
>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>    This makes filling in a new UDP checksum infeasible on most high end
>>    hardware.
>
> That argument would make sense if most hardware wasn't 
> store-and-forward on a per-packet basis.
They may be store and forward, but most of the high end designs
use multiple grades of memory putting the packet in "slow memory"
and providing a snapshot of the header in "fast memory" to the
forwarder. Thus although the whole packet is in the system, it
it is not accessible to the engine that would need to calculate the
c/s.

Stewart

From touch@isi.edu  Mon Jan 27 08:49:49 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D37611A035C; Mon, 27 Jan 2014 08:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QEZEbwtpVby; Mon, 27 Jan 2014 08:49:48 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6F61A0250; Mon, 27 Jan 2014 08:49:48 -0800 (PST)
Received: from [192.168.1.97] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s0RGmZJH003804 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 27 Jan 2014 08:48:39 -0800 (PST)
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com>
In-Reply-To: <52E68C12.2050308@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
X-Mailer: iPhone Mail (11B554a)
From: Joe Touch <touch@isi.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Date: Mon, 27 Jan 2014 08:48:35 -0800
To: "stbryant@cisco.com" <stbryant@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 16:49:50 -0000

Those same mechanisms have provided hardware checksum support for a very lon=
g time.=20

Joe

> On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>=20
>> On 24/01/2014 19:15, Joe Touch wrote:
>>=20
>>> This eliminates the "expands the reach of MPLS argument".
>>>=20
>>> First UDP checksums:
>>>=20
>>>   The UDP checksum is at the beginning of the payload.  Please see
>>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>>   This makes filling in a new UDP checksum infeasible on most high end
>>>   hardware.
>>=20
>> That argument would make sense if most hardware wasn't store-and-forward o=
n a per-packet basis.
> They may be store and forward, but most of the high end designs
> use multiple grades of memory putting the packet in "slow memory"
> and providing a snapshot of the header in "fast memory" to the
> forwarder. Thus although the whole packet is in the system, it
> it is not accessible to the engine that would need to calculate the
> c/s.
>=20
> Stewart

From stbryant@cisco.com  Mon Jan 27 09:16:25 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBCB21A02CF; Mon, 27 Jan 2014 09:16:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQ6KE1u2kuej; Mon, 27 Jan 2014 09:16:23 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6581A024C; Mon, 27 Jan 2014 09:16:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1314; q=dns/txt; s=iport; t=1390842981; x=1392052581; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=AmzRjME8C6wrg13eGk7lsXy7FVA02Is8vaR249QsW0Y=; b=bX8bEa3bxD1wrMP1CkKAq9b7UnBWu6+6OWtQ25MXglUiTqAA5lGOiGxr LiZlO8OgeiWLg4iGo1MLYxxZGg1dZtfcJRXjO3NnaubQSWGaviEfdf/zK Q8+Ftv3A0+yj9DF/YwQVlaelBe5CL5IDSgmU964Zu0T0cnq9LQ7AQuH01 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsgSAOWT5lKQ/khM/2dsb2JhbABaDoFkAgGBFzi9L4EWFnSCJQEBAQQ4QAEQCxgJFgQLCQMCAQIBRQYNAQUCAQEFh3wNxxQXjjwBAU8HhDgBA5gnkh6Bb38/gXE
X-IronPort-AV: E=Sophos;i="4.95,730,1384300800";  d="scan'208";a="3589030"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 27 Jan 2014 17:16:20 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0RHGKMJ006581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 17:16:20 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0RHGIAV027530; Mon, 27 Jan 2014 17:16:19 GMT
Message-ID: <52E69462.9030703@cisco.com>
Date: Mon, 27 Jan 2014 17:16:18 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
In-Reply-To: <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:16:26 -0000

Sorry, are you talking the same h/w that does IP c/s?

That h/w can only see the IP header.

S


On 27/01/2014 16:48, Joe Touch wrote:
> Those same mechanisms have provided hardware checksum support for a very long time.
>
> Joe
>
>> On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>>
>>> On 24/01/2014 19:15, Joe Touch wrote:
>>>
>>>> This eliminates the "expands the reach of MPLS argument".
>>>>
>>>> First UDP checksums:
>>>>
>>>>    The UDP checksum is at the beginning of the payload.  Please see
>>>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>>>    This makes filling in a new UDP checksum infeasible on most high end
>>>>    hardware.
>>> That argument would make sense if most hardware wasn't store-and-forward on a per-packet basis.
>> They may be store and forward, but most of the high end designs
>> use multiple grades of memory putting the packet in "slow memory"
>> and providing a snapshot of the header in "fast memory" to the
>> forwarder. Thus although the whole packet is in the system, it
>> it is not accessible to the engine that would need to calculate the
>> c/s.
>>
>> Stewart
> .
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From presnick@qti.qualcomm.com  Mon Jan 27 09:16:44 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 202FE1A038C; Mon, 27 Jan 2014 09:16:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bwGgQjtAVq0h; Mon, 27 Jan 2014 09:16:42 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id ED6641A0372; Mon, 27 Jan 2014 09:16:41 -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=1390843000; x=1422379000; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mhJMSTSoyvCkA8tVzxb+1utFXq/wEqwg/F8YxDBgkAE=; b=T7S5kqern91whxrA2JO1yS8oXeRj73USAVAKe0AKQKrV5R2K8tSmJ1dl 7lfKWlMn5w2N3dZSdyvSszecNWMf1o1QQstCRUZ086xpMoyBmiNPSSA7x 2KQtXoyXmEddlcShHyMqzK98ReyX/L4k35pLExRICdD7vm4twzFarLvU9 s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7330"; a="58688827"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth02.qualcomm.com with ESMTP; 27 Jan 2014 09:16:39 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7330"; a="620168779"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Jan 2014 09:16:39 -0800
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Jan 2014 09:16:38 -0800
Message-ID: <52E69475.6020403@qti.qualcomm.com>
Date: Mon, 27 Jan 2014 11:16:37 -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: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E251C2.7060009@gmail.com> <3F350057-8BF4-4A41-BC6D-3141AE419765@cisco.com> <52E2CBF2.7070807@qti.qualcomm.com> <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
In-Reply-To: <29860DAF-ABE7-4EAD-B79B-5537D661B89B@cisco.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [172.30.39.5]
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, Scott Bradner <sob@harvard.edu>, Tom Taylor <tom.taylor.stds@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:16:44 -0000

Re-reading, apparently I was in a particularly foul mood last week. My 
apologies for the amount of foulness that leaked through.

Closing the loop:

On 1/25/14 8:21 AM, Cullen Jennings (fluffy) wrote:
> It’s this above point that I don’t believe is true. I think the point you need to make is, I think what you need to say is
>
>        "You have to disclose your IPR, or not participate in the discussion"
>    

For in the room, I'd be fine with that. If all you want to do is add "or 
not participate in the discussion" to the end of what's there now, cool 
with me.

I am completely ambivalent about what goes on the registration page or 
elsewhere on the web site. I am fine with that text being different than 
what is used in the room as the reminder. I would like something that is 
more of a "plain language" version.

> I do want to point out that if you truly wanted this short the total slides would say
>
>        "This meeting may be recorded. To be in this meeting you must agree to the rules in BCP 79. "
>    

Well, that's the problem with the original text. All it says is "you 
have to abide by BCP 79" and doesn't mention "IPR" at all. Nobody 
reading it could be expected to know that there are IPR rules in the 
IETF from only reading that. For practical purposes, I think that's 
next-to-useless.

Anyway, it sounds like Jari is asking for a regroup. A fine plan.

pr

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


From dhc@dcrocker.net  Mon Jan 27 09:21:38 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD021A0246; Mon, 27 Jan 2014 09:21:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NgDGyVEe4wMY; Mon, 27 Jan 2014 09:21:35 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7E19E1A0141; Mon, 27 Jan 2014 09:21:35 -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 s0RHLBVx020732 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 09:21:15 -0800
Message-ID: <52E69572.7000903@dcrocker.net>
Date: Mon, 27 Jan 2014 09:20:50 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Subject: Re: Problem with new Note Well
X-Priority: 2 (High)
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
In-Reply-To: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.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.66]); Mon, 27 Jan 2014 09:21:15 -0800 (PST)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jan 2014 17:21:38 -0000

On 1/27/2014 8:17 AM, Jari Arkko wrote:
> All - it is clear that you have a concern about the new note well text. The problem has been well articulated;


Jari, et al,


There are a number of different problems, and only some of them have 
been articulated.  Worse, the problems include the IPR rules themselves, 
not just the Note Well:

      0.  We have had IPR rules and a Note Well for many years and have 
revised both a number of times.  Normally, work we do that has been 
around that long warrants being called "mature", which means that it 
works well and is well understood.  The latest discussion demonstrates 
that that model does not apply to the IETF's IPR handling.  In fact, the 
exchange looks more like the disparities we see early in a working group 
effort, not what normally takes place after many years.

      1. The participants in the discussion are extremely experienced 
with the IETF and with this topic.  Yet they demonstrated a strong 
/lack/ of rough consensus about what the /current/ IPR rules mean.

      2.  The current rules are too complex for use by average 
engineers.  Engineers are not attorneys, nevermind IPR attorneys.  IPR 
is considered by attorneys to be an esoteric and difficult specialty. 
The IETF's IPR rules need to be simple and simply stated, if we expect 
average engineers to understand them.

      3.  The current IPR rules appear to impose an unreasonable demand 
on IETF participants, such as conflicting with employment arrangements. 
(And if the demand is reasonable, then what is noteworthy is that 
someone who has read this latest IETF discussion has developed the 
impression that it isn't.  See point 6.)

      4.  The current Note Well is too complex and apparently erroneous. 
  (And if it is not erroneous, then what is noteworthy is that a serious 
attempt to review the thread has resulted in someone coming to the 
conclusion that the Note Well is erroneous.  See point 6.)

      5.  Expecting an average IETF engineer to consult 4 different 
BCPs, in order to understand what is required of them is not reasonable. 
  Nor is all each document relevant.  So, in effect, the references are 
overly broad, as well as too complicated. (See point 6.)

      6.  Having a range of experienced, diligent IETF participants 
demonstrate substantive disagreement about the meaning of our current 
IPR rules undermines whatever utility the rules might have.  It sets up 
a litigation argument that the participant did not understand the rules, 
citing this thread as demonstrating that others also don't.


The remedies we need are not just with the Note Well.  We need to fix 
the IPR rules too.


      0.  We need to establish clear and compelling community rough 
consensus about the meaning of our IPR rules and the utility of our Note 
Well.  We are currently /very/ far from being able to do that.

      1.  We need a consensus statement that describes our 'model' of an 
IETF particpant, in terms of what is reasonable for them to know and 
what is reasonable for them to be responsible for and what is reasonable 
for them to do, especially within the real time performance constraints 
of a working group meeting. The premise of that model needs to be 
extreme simplicity and clarity.  Any rules we assert need to be vetted 
against that model.  Our current arrangement requires an average 
engineer to be more knowledgeable and more diligent than is reasonable. 
  (By 'diligent' I'm not referring to intent; I'm referring to classic 
human factors usability limits.)

      2.  One of the distinctions in the latest discussion is between 
having the Note Well attempt to summarize what the IPR rules are, versus 
having it merely declare that we have IPR rules and point the reader to 
them.  For summary instruments, like a Note Well, the latter approach 
makes far more sense.

      3.  We need all of the IPR rules for IETF participation to be in a 
single, simple, clear document that is easily understandable by an 
average engineer. (See point 1.)


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Mon Jan 27 09:35:05 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D1A1A025D; Mon, 27 Jan 2014 09:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id es6uSZuhSOnA; Mon, 27 Jan 2014 09:35:03 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 896B71A015A; Mon, 27 Jan 2014 09:35:03 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so6797373obb.35 for <multiple recipients>; Mon, 27 Jan 2014 09:35:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=p/DRpa9aJElSth7LdkQmyoEyinOqO3bcLuV+etgGaeA=; b=B7CKHl6z7x/eI4CjFDJnBN8pKx8lgF8CJP/j+VFweZC9bymGVlyi6E5wkbAxH7TkLf ksk38C8JZW5rCE/8rV2dPlUBNmCA2mjV4rJtwDs1+76fJKwCn0l4bFphPI+ZcpIaNBtn QEjiakUBcuQWNpzr0RWyGN0wUhUO2+t9c+WQ21HTLi8fqet63A30BlkrOui753OKeJ+u 87AJ44YLLJoXr3hZadQQemQma3evDMs/qMn9KzR/d2xD/5kq9GnL2vQeOL5piqTlVkT8 Mal0TNW2mfYumnKD2nFjk+um+HytNvMPYdlgdtxnK2OWUHEvIhNLnNxBYfupQFeqz02K OAtQ==
X-Received: by 10.182.247.68 with SMTP id yc4mr926787obc.67.1390844101240; Mon, 27 Jan 2014 09:35:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Mon, 27 Jan 2014 09:34:41 -0800 (PST)
In-Reply-To: <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com> <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Mon, 27 Jan 2014 12:34:41 -0500
Message-ID: <CAPv4CP_QU=SSpQxAiw9_VWZ5O1ZG4fiKVScOi7yUNNDX5_GB9Q@mail.gmail.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:35:05 -0000

On Mon, Jan 27, 2014 at 12:03 PM, Mulligan, Geoff
<geoff.mulligan@nist.gov> wrote:
> I do want to be clear - I am not currently facing this situation and I ha=
ven't yet faced this situation, but I fear that as a consultant (in the fut=
ure when this current job ends) I may face this.  I want to understand my o=
ptions as I would like to continue my participation and affiliation with th=
e IETF.

Geoff, IMHO (and I have done this): when you start a consulting gig
that involves speaking up in SDOs, set up time to review the SDO IPR
policies with your management and lawyers, and get a baseline for how
they want you to handle gray area situations.

From alexey.melnikov@isode.com  Mon Jan 27 09:41:44 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75BFC1A0290; Mon, 27 Jan 2014 09:41:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcNTaKPShegQ; Mon, 27 Jan 2014 09:41:41 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id C21331A0251; Mon, 27 Jan 2014 09:41:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390844497; d=isode.com; s=selector; i=@isode.com; bh=C18uM+P5IrqBZjvicy6HsYMmV/FIf/YMEFq48laZPNU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=gKHDuaWsygTzN5F1hpI/js9w5Bf4oEarrulJGwZKfYx4gyajH7B8OrhX9AQRGAQdXWPuY1 iL3aivay/zUhf/AYd6W78Aj8agaGuIoCFueBz0PtkPQoS7WFyFYkcJqWKnp048UySeQWCa +xn1rZoB2yoRy6U/Fac/FmT+bkFbOYc=;
Received: from [192.168.0.4] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UuaaUAAIPyYq@waldorf.isode.com>; Mon, 27 Jan 2014 17:41:37 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <52E69A54.9030104@isode.com>
Date: Mon, 27 Jan 2014 17:41:40 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
To: Eliot Lear <lear@cisco.com>
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>
In-Reply-To: <52E65878.9030906@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:41:44 -0000

Hi Eliot,
Mostly agreeing with you, but some corrections below:

On 27/01/2014 13:00, Eliot Lear wrote:
> Hi Dave,
>
> First, thank you for your review.  I personally appreciate to the time
> you put in to all of your reviews.
>
> On 1/27/14, 3:06 AM, Black, David wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>>
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>> Document: draft-ietf-qresync-rfc5162bis-09
>> Reviewer: David L. Black
>> Review Date: January 26, 2014
>> IETF LC End Date: January 27, 2014
>>
>> Summary:
>> This draft is basically ready for publication, but has minor issues that
>> should be fixed before publication.
>>
>> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
>> (IMAP Quick Mailbox Resynchronization) into a single document and makes
>> a few minor updates.  It also updates the command line length
>> recommendation in RFC 2683 to support the longer command lines that
>> can occur with these extensions.
>>
>> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
>> they look reasonable.  I found one minor issue that should be relatively
>> easy to address.
>>
>> Minor Issues:
>>
>> The command line length change in Section 4 applies to all IMAP commands,
>> and hence affects old servers, including those that don't implement either
>> of the extensions in this draft. That raises a backwards compatibility
>> concern - what happens when a new client sends a > 1000 character command
>> line to an old server that isn't expecting more than 1000 characters?
> As the draft indicates, this is problematic for the two extensions in
> question. We have discussed this limitation in the working group, and
> nobody seems to be concerned.  That's due to two factors, I think:
> first, RFC 2683 is not normative (informational).
I don't think this actually matters, but the rest of your argument is 
still valid.
> I am unaware of any
> strict line length limitation in RFC 3501, for instance.  Instead, there
> is a requirement for strict syntax parsing.  If the client blows it in
> any way, the server SHOULD return an error with a BAD response.
That is very true. This is what happens now.
> This having been said, while the working group has discussed this
> matter, it would be good to hear any additional voices of concern, in
> the interests of interoperability.
Agreed.
> This takes us to your next point:
>
>> One possibility would be to apply the larger length recommendation only
>> after the client determines that the server supports at least one of
>> these extensions.
>>
>> Nits/editorial comments:
>>
>> The update to RFC 2683 would be easier to find from the table of contents
>> if the title of Section 4 were changed to "Long Command Lines (Update to
>> RFC 2683)".
>>
>> idnits 2.13.01 got confused by the command line examples, and flagged a
>> downref:
>>
>>    ** Downref: Normative reference to an Informational RFC: RFC 2683
>>
>> That downref appears to be ok and intended, as noted in the shepherd's
>> writeup.
> This will be addressed in a forthcoming update.  Barry has "educated" us
> that really this is NOT an update to RFC2683, where the advice given in
> that document is superceded by a specific option.  As such, this error
> will evaporate.
Actually, I think I convinced Barry that it is updating RFC 2683.

Best Regards,
Alexey


From touch@isi.edu  Mon Jan 27 10:01:20 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C8DD1A001E; Mon, 27 Jan 2014 10:01:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rWy0CR_VzjB3; Mon, 27 Jan 2014 10:01:17 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id AC1D41A0256; Mon, 27 Jan 2014 10:01:17 -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 s0RI0olq024489 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 10:00:53 -0800 (PST)
Message-ID: <52E69ED3.1060005@isi.edu>
Date: Mon, 27 Jan 2014 10:00:51 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E69462.9030703@cisco.com>
In-Reply-To: <52E69462.9030703@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 18:01:20 -0000

On 1/27/2014 9:16 AM, Stewart Bryant wrote:
>
> Sorry, are you talking the same h/w that does IP c/s?

It's been trivial to implement this for TCP checksums for a long time. 
18 years ago I showed how to do it for what was then $40 at 1Gbps (RFC 
1936).

They're done in hardware in many network interface cards on end systems, 
and it's been necessary for routers that use TCP tunnels as well.

Splitting headers from packet body for high-throughput routing has been 
known and done for a long time too (e.g., S. Walton, A. Hutton, and J. 
Touch, “High-Speed Data Paths in Host-Based Routers,” IEEE Computer, 
Nov. 1998, pp. 46-52.); during body transfer, the contents can easily be 
summed, and that sum can be combined with the header sum easily too.

Joe

> That h/w can only see the IP header.
>
> S
>
>
> On 27/01/2014 16:48, Joe Touch wrote:
>> Those same mechanisms have provided hardware checksum support for a
>> very long time.
>>
>> Joe
>>
>>> On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>>>
>>>> On 24/01/2014 19:15, Joe Touch wrote:
>>>>
>>>>> This eliminates the "expands the reach of MPLS argument".
>>>>>
>>>>> First UDP checksums:
>>>>>
>>>>>    The UDP checksum is at the beginning of the payload.  Please see
>>>>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>>>>    This makes filling in a new UDP checksum infeasible on most high
>>>>> end
>>>>>    hardware.
>>>> That argument would make sense if most hardware wasn't
>>>> store-and-forward on a per-packet basis.
>>> They may be store and forward, but most of the high end designs
>>> use multiple grades of memory putting the packet in "slow memory"
>>> and providing a snapshot of the header in "fast memory" to the
>>> forwarder. Thus although the whole packet is in the system, it
>>> it is not accessible to the engine that would need to calculate the
>>> c/s.
>>>
>>> Stewart
>> .
>>
>
>

From joelja@bogus.com  Mon Jan 27 10:49:01 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E05131A0276; Mon, 27 Jan 2014 10:49:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UpBZmwrp5IkO; Mon, 27 Jan 2014 10:49:00 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 775C81A0264; Mon, 27 Jan 2014 10:49:00 -0800 (PST)
Received: from 02351a-maguilar.corp.zynga.com ([199.48.105.4]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0RImiKS042439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 27 Jan 2014 18:48:44 GMT (envelope-from joelja@bogus.com)
Message-ID: <52E6AA0B.1050600@bogus.com>
Date: Mon, 27 Jan 2014 10:48:43 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
In-Reply-To: <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OriKbApKhGlWr638DuclAaA0Sme6Slsso"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Mon, 27 Jan 2014 18:48:45 +0000 (UTC)
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 18:49:02 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--OriKbApKhGlWr638DuclAaA0Sme6Slsso
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 1/27/14, 8:48 AM, Joe Touch wrote:
> Those same mechanisms have provided hardware checksum support for a ver=
y long time.=20


The new header and the payload are actually in different parts of the
forwarding complex until they hit the output queue, you can't checksum
data you don't have.

> Joe
>=20
>> On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote=
:
>>
>>> On 24/01/2014 19:15, Joe Touch wrote:
>>>
>>>> This eliminates the "expands the reach of MPLS argument".
>>>>
>>>> First UDP checksums:
>>>>
>>>>   The UDP checksum is at the beginning of the payload.  Please see
>>>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>>>   This makes filling in a new UDP checksum infeasible on most high e=
nd
>>>>   hardware.
>>>
>>> That argument would make sense if most hardware wasn't store-and-forw=
ard on a per-packet basis.
>> They may be store and forward, but most of the high end designs
>> use multiple grades of memory putting the packet in "slow memory"
>> and providing a snapshot of the header in "fast memory" to the
>> forwarder. Thus although the whole packet is in the system, it
>> it is not accessible to the engine that would need to calculate the
>> c/s.
>>
>> Stewart
>=20



--OriKbApKhGlWr638DuclAaA0Sme6Slsso
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLmqgwACgkQ8AA1q7Z/VrJ0zACeJrp+2AtldVjwugnNSUZYioX3
sX0An3nU4rW8YFZ58lK3lkrH/mGl7oX2
=6qzZ
-----END PGP SIGNATURE-----

--OriKbApKhGlWr638DuclAaA0Sme6Slsso--

From touch@isi.edu  Mon Jan 27 10:53:54 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FD461A02A4; Mon, 27 Jan 2014 10:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r85c620Ak3Vp; Mon, 27 Jan 2014 10:53:53 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF461A0239; Mon, 27 Jan 2014 10:53:53 -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 s0RIr9lx006196 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 10:53:09 -0800 (PST)
Message-ID: <52E6AB15.2080907@isi.edu>
Date: Mon, 27 Jan 2014 10:53:09 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com>
In-Reply-To: <52E6AA0B.1050600@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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 18:53:54 -0000

On 1/27/2014 10:48 AM, joel jaeggli wrote:
> On 1/27/14, 8:48 AM, Joe Touch wrote:
>> Those same mechanisms have provided hardware checksum support for a very long time.
>
> The new header and the payload are actually in different parts of the
> forwarding complex until they hit the output queue, you can't checksum
> data you don't have.

You can (and some do) the checksum component parts when things go into 
memory; the partial sums can be added as the parts are combined in the 
output queue.

I appreciate that we're all taking about what might be done, but the 
reality is that there are many 'transparent TCP proxies' that have to do 
this, so there's clearly a solution, and it clearly runs fast enough.

Joe

From jmh@joelhalpern.com  Mon Jan 27 11:19:10 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02DD1A034B; Mon, 27 Jan 2014 11:19:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sYqcEwHlF2be; Mon, 27 Jan 2014 11:19:09 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 27A8B1A0264; Mon, 27 Jan 2014 11:19:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 096EF102BF0; Mon, 27 Jan 2014 11:19:07 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-128.clppva.east.verizon.net [70.106.135.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 087C3102B42; Mon, 27 Jan 2014 11:19:05 -0800 (PST)
Message-ID: <52E6B128.8060306@joelhalpern.com>
Date: Mon, 27 Jan 2014 14:19:04 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, joel jaeggli <joelja@bogus.com>,  "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu>
In-Reply-To: <52E6AB15.2080907@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:19:11 -0000

Yes Joe, routers could ahve been built to do those calcualtions at that 
performance scale.
There are however two major problems:

1) That is not how routers are built.
2) The target performance scale is rather higher.

So could someone build an ASIC to do what you want?  Probably.  Is there 
any reason in the world to expect operators to pay the significant extra 
cost for such?  Not that I can see.
And even if we could and they would, that is not the world into which we 
are deploying these tunnels.

Yours,
Joel

On 1/27/14 1:53 PM, Joe Touch wrote:
>
>
> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>> Those same mechanisms have provided hardware checksum support for a
>>> very long time.
>>
>> The new header and the payload are actually in different parts of the
>> forwarding complex until they hit the output queue, you can't checksum
>> data you don't have.
>
> You can (and some do) the checksum component parts when things go into
> memory; the partial sums can be added as the parts are combined in the
> output queue.
>
> I appreciate that we're all taking about what might be done, but the
> reality is that there are many 'transparent TCP proxies' that have to do
> this, so there's clearly a solution, and it clearly runs fast enough.
>
> Joe
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

From keith.drage@alcatel-lucent.com  Mon Jan 27 11:25:00 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE7B21A0341; Mon, 27 Jan 2014 11:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NUKnR4Hxa6QZ; Mon, 27 Jan 2014 11:24:58 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8F61A033D; Mon, 27 Jan 2014 11:24:57 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0RJOrch013849 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 27 Jan 2014 13:24:54 -0600 (CST)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0RJOqYh016110 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 20:24:52 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Mon, 27 Jan 2014 20:24:52 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7pgAAnw3A=
Date: Mon, 27 Jan 2014 19:24:51 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B123A69@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>,<CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
In-Reply-To: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:25:01 -0000

An you clarify whether you consider your use case as trying to meet the req=
uirements of 6.1.2 or the requirements of 6.1.3 of RFC 3979.

Regards

Keith=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Mulligan, Geoff
> Sent: 27 January 2014 17:01
> To: Jari Arkko
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: RE: Third party disclosures and NDAs (Re: Problem=20
> with new Note Well )
>=20
> So because I know of IPR that someone else has and is not=20
> disclosing and because I cannot legally disclose it - I can't=20
> continue to participate in the discussion doesn't seem right.=20
>  I'm not the holder of the IPR that isn't being disclosed,=20
> but I'm penalized.
>=20
> Geoff
>=20
>=20
> Geoff Mulligan | Presidential Innovation Fellow | Cyber=20
> Physical Systems | 301.975.6283
>=20
> ________________________________________
> From: Jari Arkko <jari.arkko@piuha.net>
> Sent: Monday, January 27, 2014 11:02 AM
> To: Mulligan, Geoff
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: Third party disclosures and NDAs (Re: Problem with=20
> new Note Well )
>=20
> Starting a separate thread, because this is not related to=20
> the original complaint about inaccurate new note well text.
>=20
> >   Maybe this is a potential rat-hole - I don't know - but what if:
> >     -  I'm working as a consultant and attending the IETF=20
> representing myself
> >     -  I know of IPR in someone else's contribution
> >     -  I'm participating in the discussion
> >     -  I'm under an NDA with that company that covers their IPR
>=20
> That is a rat-^H^H^H^Hhard problem. Something has to give.=20
> You can't simultaneously follow two incompatible sets of=20
> rules. If you end up in that situation and can't convince=20
> parties to disclose, maybe "participating in the discussion"=20
> has to give. Of course this is a specific example of things=20
> that can happen in people's lives in other ways, too. Two=20
> consulting contracts that have incompatible requirements.=20
> Board position and a job that creates a conflict interest for=20
> you to be in the board. And so on.
>=20
> Jari
>=20
> =

From touch@isi.edu  Mon Jan 27 11:25:07 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A2E1A03C6; Mon, 27 Jan 2014 11:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PKG8HIMZy2Wj; Mon, 27 Jan 2014 11:25:04 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 445B71A03AD; Mon, 27 Jan 2014 11:25:04 -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 s0RJOYXQ011992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 11:24:34 -0800 (PST)
Message-ID: <52E6B272.4030703@isi.edu>
Date: Mon, 27 Jan 2014 11:24:34 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Joel M. Halpern" <jmh@joelhalpern.com>, joel jaeggli <joelja@bogus.com>,  "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com>
In-Reply-To: <52E6B128.8060306@joelhalpern.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:25:07 -0000

On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
> Yes Joe, routers could ahve been built to do those calcualtions at that
> performance scale.
> There are however two major problems:
>
> 1) That is not how routers are built.
> 2) The target performance scale is rather higher.
>
> So could someone build an ASIC to do what you want?

Has. It's already part of nearly every DMA ASIC in a network interface 
already.

 > Probably.  Is there
> any reason in the world to expect operators to pay the significant extra
> cost for such?Not that I can see.

We're talking about a ring of full adders, the specs for which are given 
in an RFC that's 18 years old, and that is already implemented in nearly 
every host interface, including 10Gps NICs.

And we're talking about "routers", many variants of which operate at 
very high speeds and transparently proxy TCP already. So this is a 
solved problem.

> And even if we could and they would, that is not the world into which we
> are deploying these tunnels.

We're back to "that's not what they do now", at least in some devices.

Well, they don't use MPLS in UDP (since no spec exists), so clearly if 
they're limited to doing what they already do, this is an exercise in 
futility.

Joe

>
> Yours,
> Joel
>
> On 1/27/14 1:53 PM, Joe Touch wrote:
>>
>>
>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>> Those same mechanisms have provided hardware checksum support for a
>>>> very long time.
>>>
>>> The new header and the payload are actually in different parts of the
>>> forwarding complex until they hit the output queue, you can't checksum
>>> data you don't have.
>>
>> You can (and some do) the checksum component parts when things go into
>> memory; the partial sums can be added as the parts are combined in the
>> output queue.
>>
>> I appreciate that we're all taking about what might be done, but the
>> reality is that there are many 'transparent TCP proxies' that have to do
>> this, so there's clearly a solution, and it clearly runs fast enough.
>>
>> Joe
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>

From john@jlc.net  Mon Jan 27 11:34:42 2014
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1082E1A02DF; Mon, 27 Jan 2014 11:34:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lH5V_5D_fG2U; Mon, 27 Jan 2014 11:34:39 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A10541A007C; Mon, 27 Jan 2014 11:34:39 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 6100FC94A9; Mon, 27 Jan 2014 14:34:35 -0500 (EST)
Date: Mon, 27 Jan 2014 14:34:35 -0500
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: Problem with new Note Well
Message-ID: <20140127193435.GC87271@verdi>
References: <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52E69572.7000903@dcrocker.net>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:34:42 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> 
> There are a number of different problems, and only some of them have 
> been articulated.  Worse, the problems include the IPR rules themselves, 
> not just the Note Well:
> 
> 0. We have had IPR rules and a Note Well for many years and have 
>    revised both a number of times.

   I'd bet 90% of folks who read the Note Well aren't even aware that
BCP 79 is a concatenation of RFC 3979 and RFC 4879.

   :^(

   It is a sad fact that having read BCP 79 eight years ago isn't "enough".

>  Normally, work we do that has been around that long warrants being
> called "mature", which means that it works well and is well understood.

   Delusions _are_ functional! ;^)

> The latest discussion demonstrates that that model does not apply to
> the IETF's IPR handling...

> 1. The participants in the discussion are extremely experienced 
>    with the IETF and with this topic.  Yet they demonstrated a strong 
>    /lack/ of rough consensus about what the /current/ IPR rules mean.

   +1

> 2. The current rules are too complex for use by average engineers.
>    Engineers are not attorneys, nevermind IPR attorneys...

   Folks are pretty much forced to "click-through" any legalese today.
We are only deluding ourselves to think it "means" anything.

> 3. The current IPR rules appear to impose an unreasonable demand 
>    on IETF participants, such as conflicting with employment
>    arrangements...

   By the time the average attendee hears the Note Well read in a
meeting, the employer has already agreed to pay for airfare and hotel.
Do we really expect that he who pays the piper doesn't call the tune?

> 4. The current Note Well is too complex and apparently erroneous... 

   I am sympathetic to Pete's desire to impress on hearers that there
_are_ rules about disclosing IPR. But we shouldn't go so far as to
exclude Cisco employees.

> 5. Expecting an average IETF engineer to consult 4 different BCPs,
>    in order to understand what is required of them is not reasonable. 
>    Nor is all [of] each document relevant...

   It's actually worse, since BCPs can change... :^(

> 6. Having a range of experienced, diligent IETF participants 
>    demonstrate substantive disagreement about the meaning of our
>    current IPR rules undermines whatever utility the rules might
>    have...

   I wouldn't go quite that far... lawyers _love_ disagreements about
what a document "means." We can't avoid this! :^(

   But IMHO, the Note Well read at the beginning of meetings shouldn't
attempt to summarize the rules: merely "BCP 79 as of January 2014"
seems sufficient.

   (Which is not to say that a more extensive "Note Well" during the
registration process wouldn't be appropriate...)

--
John Leslie <john@jlc.net>

From barryleiba@gmail.com  Mon Jan 27 12:59:52 2014
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA5C1A0034; Mon, 27 Jan 2014 12:59:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4U925Qkk0Oky; Mon, 27 Jan 2014 12:59:51 -0800 (PST)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 191571A00F6; Mon, 27 Jan 2014 12:59:50 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id ii20so8098601qab.32 for <multiple recipients>; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OSrFbNu2l6O1KqgTDGi2hu1gj+san85JxbwA4k43bAA=; b=R4kN6jlLnj9/n3B29XDtftV99XoQIoVkvHlXkn30YbVX9k9bvkTVFO5tZbgWXicjmT 3fm3LB5ipbXZNVS4U0Qr5KZc0Pj5xBGz6zBUW2qITlOGtbJNNVzzBh+2cCyuxv9Sc14P aNNXvPZkRRL/k57Hwl5GmkuC7kBNnm8g0rp5J90QNXkBMZjtmcSl+g0wcG0jrNfCpJkC 4xUpBBtWiBZeQqsqzCtRHvE9I/znW7MekpRRZ2cqWOXwKv1HppmaQurEKnGajcq/2fG5 VzSj3hUTdahbnIvvQnTMJ8p8eYJVIV9PfpzEg7NDbt01KjodbPsYJVJnON/5FkTcxfWL e/FA==
MIME-Version: 1.0
X-Received: by 10.229.196.197 with SMTP id eh5mr46178465qcb.3.1390856388591; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Mon, 27 Jan 2014 12:59:48 -0800 (PST)
In-Reply-To: <52E69A54.9030104@isode.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com>
Date: Mon, 27 Jan 2014 15:59:48 -0500
X-Google-Sender-Auth: 1G53Zb6aqJxTFsRRiXicjYq710k
Message-ID: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 20:59:52 -0000

> Actually, I think I convinced Barry that it is updating RFC 2683.

Yes: because the new line-length-limit recommendation is meant to
apply whether or not condstore or qresync are in play, this "updates"
remains (it's the others that used to be there that we scrubbed).

I think David's right that some version of what Eliot said:

> there
> is a requirement for strict syntax parsing.  If the client blows it in
> any way, the server SHOULD return an error with a BAD response.

...should be added to the section about the line-length limit.  A
sentence or two should do nicely.

Barry

From lear@cisco.com  Mon Jan 27 13:23:40 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9B61A0235; Mon, 27 Jan 2014 13:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i6C1ijOmn1e7; Mon, 27 Jan 2014 13:23:39 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 968821A0146; Mon, 27 Jan 2014 13:23:38 -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=1390857817; x=1392067417; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mGexWQU6ryTrAoAhd2Rl73rE0NOxP6a31fYtzTO6uYE=; b=BkeyN9i5tWhiJQQV+4NQJhsnufLOiXJ0VlpQiJCdArNNLrrTZVGKJwLo AHZmHBqCcHV67fAUogv1U4MFGweFQ4yyvBBdAXOaeC0wn7IEdCJKpS+Yx KroUjos38zAvabk/eva/0IILAHmHO9OKwCtdiBY0Aa63SCLGokBRJjPAw U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcFAInN5lKQ/khM/2dsb2JhbABagwyEC7legRwWdIIlAQEBBCNVARALGAICBRYLAgIJAwIBAgErGgYBDAEHAQGIAaoBnQAXgSmNDVcHgm+BSQEDmCeSHoMtPIEt
X-IronPort-AV: E=Sophos;i="4.95,731,1384300800";  d="scan'208";a="3597002"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 27 Jan 2014 21:23:34 +0000
Received: from mctiny.local ([10.61.192.127]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0RLNX5f004819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 21:23:33 GMT
Message-ID: <52E6CE54.7020104@cisco.com>
Date: Mon, 27 Jan 2014 21:23:32 +0000
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com>	<52E65878.9030906@cisco.com>	<52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
In-Reply-To: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Black, David" <david.black@emc.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "imapext@ietf.org" <imapext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:23:40 -0000

Hi Barry, Dave, and Alexey,

On 1/27/14, 8:59 PM, Barry Leiba wrote:
>> Actually, I think I convinced Barry that it is updating RFC 2683.
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
>
> I think David's right that some version of what Eliot said:
>
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.
>
>

I don't see a problem, but for context I was really just borrowing from
RFC 3501, which already states that SHOULD (Section 2.2 if memory
serves).  Stating it again won't hurt.

Eliot

From dave@cridland.net  Mon Jan 27 13:26:07 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F1D1A0146 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:26:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rs6J7HdlgYlC for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:26:06 -0800 (PST)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 97F2B1A0366 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:26:06 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id n16so7365886oag.19 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:26:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=N7jwDBVDrmNguCLWnep1Rk8QFpjKRB8rdlqV1l6chMw=; b=dtzq4Na2/zm8H4s7ZbZALoPHJUiQUvSRsDBVAaPa4uFGXvxXP5InWn8bpMGlyK8jzD 2KLwh8/LIDoJv0HxbsKIOtDxOYvxgLDRRknVR8BaFmstVwHhmixW+bqPQkMa9VahpVL6 pZyq0WhluEBlHCghXFinsQQDN6Xj/EucvaGZ8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=N7jwDBVDrmNguCLWnep1Rk8QFpjKRB8rdlqV1l6chMw=; b=Hq3r8wiVJhEp+ZfTDjYGxt6KSD4CKEGMQK00Qo/gt9PRpuoBU0C/UCYHC8I8lhMIMT 9CGFDskv659upWxhu5zU4CIcB6wQnN+nFOHrULsuclogjJh6K+M/8/GswMSGpO1wO0xb BCSdXO+iqXtFoxTQzBIsqR91nCHSp8cvIsNmNLDxoTEeoz9KSL8ig/vjDzhylVVT4zHl J5TwhUX9lDJwW1YSUYqwu77vLojJA9ljWJ3tIRUxdn9R+haduQR15PcEo/tQgyF4Wyav tuMmrjn8wl9tLr0N21V1sfiTJaYPCHOfXCgCPRcjuW8JHpV4KqSRtVtcY5OyUCWjFT4s +7IA==
X-Gm-Message-State: ALoCoQmPhrLhuG1yVDZuRAI3HaM8pZsHIjXuELLKb5GsTbS83IR6TlaDjJgiMmPG8JxVCXJlCBZD
MIME-Version: 1.0
X-Received: by 10.182.84.132 with SMTP id z4mr2378405oby.49.1390857964060; Mon, 27 Jan 2014 13:26:04 -0800 (PST)
Received: by 10.60.55.138 with HTTP; Mon, 27 Jan 2014 13:26:03 -0800 (PST)
In-Reply-To: <52E6CE54.7020104@cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <52E6CE54.7020104@cisco.com>
Date: Mon, 27 Jan 2014 21:26:03 +0000
Message-ID: <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.gmail.com>
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
From: Dave Cridland <dave@cridland.net>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary=089e0111c09ae1d54804f0fa5a09
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:26:08 -0000

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

I assume you mean it should include a pointer to that SHOULD, not restate
it as such?


On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <lear@cisco.com> wrote:

> Hi Barry, Dave, and Alexey,
>
> On 1/27/14, 8:59 PM, Barry Leiba wrote:
> >> Actually, I think I convinced Barry that it is updating RFC 2683.
> > Yes: because the new line-length-limit recommendation is meant to
> > apply whether or not condstore or qresync are in play, this "updates"
> > remains (it's the others that used to be there that we scrubbed).
> >
> > I think David's right that some version of what Eliot said:
> >
> >> there
> >> is a requirement for strict syntax parsing.  If the client blows it in
> >> any way, the server SHOULD return an error with a BAD response.
> > ...should be added to the section about the line-length limit.  A
> > sentence or two should do nicely.
> >
> >
>
> I don't see a problem, but for context I was really just borrowing from
> RFC 3501, which already states that SHOULD (Section 2.2 if memory
> serves).  Stating it again won't hurt.
>
> Eliot
>

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

<div dir=3D"ltr">I assume you mean it should include a pointer to that SHOU=
LD, not restate it as such?</div><div class=3D"gmail_extra"><br><br><div cl=
ass=3D"gmail_quote">On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <span dir=
=3D"ltr">&lt;<a href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco=
.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">Hi Barry, Dave, and Alexey,<br>
<div><div class=3D"h5"><br>
On 1/27/14, 8:59 PM, Barry Leiba wrote:<br>
&gt;&gt; Actually, I think I convinced Barry that it is updating RFC 2683.<=
br>
&gt; Yes: because the new line-length-limit recommendation is meant to<br>
&gt; apply whether or not condstore or qresync are in play, this &quot;upda=
tes&quot;<br>
&gt; remains (it&#39;s the others that used to be there that we scrubbed).<=
br>
&gt;<br>
&gt; I think David&#39;s right that some version of what Eliot said:<br>
&gt;<br>
&gt;&gt; there<br>
&gt;&gt; is a requirement for strict syntax parsing. =A0If the client blows=
 it in<br>
&gt;&gt; any way, the server SHOULD return an error with a BAD response.<br=
>
&gt; ...should be added to the section about the line-length limit. =A0A<br=
>
&gt; sentence or two should do nicely.<br>
&gt;<br>
&gt;<br>
<br>
</div></div>I don&#39;t see a problem, but for context I was really just bo=
rrowing from<br>
RFC 3501, which already states that SHOULD (Section 2.2 if memory<br>
serves). =A0Stating it again won&#39;t hurt.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Eliot<br>
</font></span></blockquote></div><br></div>

--089e0111c09ae1d54804f0fa5a09--

From david.black@emc.com  Mon Jan 27 13:43:00 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEAC1A022F; Mon, 27 Jan 2014 13:43:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cUom4Om3wqrC; Mon, 27 Jan 2014 13:42:57 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E50401A0068; Mon, 27 Jan 2014 13:42:56 -0800 (PST)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0RLgnYi017670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Jan 2014 16:42:50 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0RLgnYi017670
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1390858971; bh=12zzdRDW9QV+c/0eAaX8QEfLPao=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=rY7rrAiEtHpMhmjmUoDQE/lcEGS3l/lRujCo9sxiRRsswCJvRxuhhB/5PM5OdaKqy Ir57vKU+ImrVfJf0UGSkLX35AYZwZT13iGxxNZXPrDV/KDbrxwcJAGAjJef+Sp6eeL e9TVd++9aXXHS1Nxcko3d/TAK7+OcIvQ1MPLFR44=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s0RLgnYi017670
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd01.lss.emc.com (RSA Interceptor); Mon, 27 Jan 2014 16:42:29 -0500
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0RLgSnm028782 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 27 Jan 2014 16:42:28 -0500
Received: from mx15a.corp.emc.com ([169.254.1.107]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Mon, 27 Jan 2014 16:42:27 -0500
From: "Black, David" <david.black@emc.com>
To: Dave Cridland <dave@cridland.net>, Eliot Lear <lear@cisco.com>
Date: Mon, 27 Jan 2014 16:42:27 -0500
Subject: RE: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Topic: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
Thread-Index: Ac8bpmqQhOX2b95ATuq5+uw+4lVz3AAAG3bw
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712026F1623A4@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com>	<52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <52E6CE54.7020104@cisco.com> <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.gmail.com>
In-Reply-To: <CAKHUCzy8-YuH7sESMA_oZRnX_s38pUDqeDB78qP=0QOYbhruPg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:43:00 -0000

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

I don't quite see the details in RFC 3501.  I think what's going on is that=
:

A server implementation that uses a shorter command line length limit than
this recommendation could clip a longer client command line at the server's
line length limit.  This SHOULD result in a syntax error (e.g., due to the
server not finding a CRLF at the end of the clipped command line) that
causes the server to return a BAD response, as specified in RFC 3501.

Thanks,
--David

From: Dave Cridland [mailto:dave@cridland.net]
Sent: Monday, January 27, 2014 4:26 PM
To: Eliot Lear
Cc: Barry Leiba; Alexey Melnikov; General Area Review Team (gen-art@ietf.or=
g); Black, David; dcridland@arcode.com; imapext@ietf.org; ietf@ietf.org
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09

I assume you mean it should include a pointer to that SHOULD, not restate i=
t as such?

On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear <lear@cisco.com<mailto:lear@cis=
co.com>> wrote:
Hi Barry, Dave, and Alexey,

On 1/27/14, 8:59 PM, Barry Leiba wrote:
>> Actually, I think I convinced Barry that it is updating RFC 2683.
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
>
> I think David's right that some version of what Eliot said:
>
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.
>
>
I don't see a problem, but for context I was really just borrowing from
RFC 3501, which already states that SHOULD (Section 2.2 if memory
serves).  Stating it again won't hurt.

Eliot


--_000_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_
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 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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;}
span.hoenzb
	{mso-style-name:hoenzb;}
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-family:"Calibri","sans-serif";}
@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'>I don&#8217;t quite =
see the details in RFC 3501.&nbsp; I think what&#8217;s going on is that:<o=
:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;fo=
nt-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New";colo=
r:black'>A server implementation that uses a shorter command line length li=
mit than<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:10.0pt;font-family:"Courier New";color:black'>this recommendation could cl=
ip a longer client command line at the server&#8217;s<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew";color:black'>line length limit.&nbsp; This SHOULD result in a syntax er=
ror (e.g., due to the<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New";color:black'>server not find=
ing a CRLF at the end of the clipped command line) that<o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier=
 New";color:black'>causes the server to return a BAD response, as specified=
 in RFC 3501.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:10.0pt;font-family:"Courier New";color:black'><o:p>&nbsp;</o:p></span=
></p><div><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
"Courier New";color:black'>Thanks,<br>--David</span><span style=3D'font-siz=
e:11.0pt;font-family:"Courier New";color:black'><o:p></o:p></span></p></div=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New";color:black'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;bor=
der-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'bor=
der:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=
=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-=
serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'> Dave Cridland [mailto:dave@cridland.net] <br><b>Sent:</b> =
Monday, January 27, 2014 4:26 PM<br><b>To:</b> Eliot Lear<br><b>Cc:</b> Bar=
ry Leiba; Alexey Melnikov; General Area Review Team (gen-art@ietf.org); Bla=
ck, David; dcridland@arcode.com; imapext@ietf.org; ietf@ietf.org<br><b>Subj=
ect:</b> Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09<o=
:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><=
div><p class=3DMsoNormal>I assume you mean it should include a pointer to t=
hat SHOULD, not restate it as such?<o:p></o:p></p></div><div><p class=3DMso=
Normal style=3D'margin-bottom:12.0pt'><o:p>&nbsp;</o:p></p><div><p class=3D=
MsoNormal>On Mon, Jan 27, 2014 at 9:23 PM, Eliot Lear &lt;<a href=3D"mailto=
:lear@cisco.com" target=3D"_blank">lear@cisco.com</a>&gt; wrote:<o:p></o:p>=
</p><p class=3DMsoNormal>Hi Barry, Dave, and Alexey,<o:p></o:p></p><div><di=
v><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>On 1/27/14, 8:59 =
PM, Barry Leiba wrote:<br>&gt;&gt; Actually, I think I convinced Barry that=
 it is updating RFC 2683.<br>&gt; Yes: because the new line-length-limit re=
commendation is meant to<br>&gt; apply whether or not condstore or qresync =
are in play, this &quot;updates&quot;<br>&gt; remains (it's the others that=
 used to be there that we scrubbed).<br>&gt;<br>&gt; I think David's right =
that some version of what Eliot said:<br>&gt;<br>&gt;&gt; there<br>&gt;&gt;=
 is a requirement for strict syntax parsing. &nbsp;If the client blows it i=
n<br>&gt;&gt; any way, the server SHOULD return an error with a BAD respons=
e.<br>&gt; ...should be added to the section about the line-length limit. &=
nbsp;A<br>&gt; sentence or two should do nicely.<br>&gt;<br>&gt;<o:p></o:p>=
</p></div></div><p class=3DMsoNormal>I don't see a problem, but for context=
 I was really just borrowing from<br>RFC 3501, which already states that SH=
OULD (Section 2.2 if memory<br>serves). &nbsp;Stating it again won't hurt.<=
br><span style=3D'color:#888888'><br><span class=3Dhoenzb>Eliot</span></spa=
n><o:p></o:p></p></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></di=
v></div></body></html>=

--_000_8D3D17ACE214DC429325B2B98F3AE712026F1623A4MX15Acorpemcc_--

From wesley.george@twcable.com  Mon Jan 27 13:50:20 2014
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD5A1A03B1 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.1
X-Spam-Level: *
X-Spam-Status: No, score=1.1 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hcTszsqPmY-D for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:50:18 -0800 (PST)
Received: from cdcipgw02.twcable.com (cdcipgw02.twcable.com [165.237.91.111]) by ietfa.amsl.com (Postfix) with ESMTP id A29C31A03C7 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:50:17 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.95,731,1384318800"; d="scan'208";a="59151411"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdcipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 27 Jan 2014 16:49:35 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Mon, 27 Jan 2014 16:50:09 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Dave Crocker <dhc@dcrocker.net>,  Jari Arkko <jari.arkko@piuha.net>
Importance: high
X-Priority: 1
Date: Mon, 27 Jan 2014 16:50:07 -0500
Subject: finding the union of multiple documents (was Re: Problem with new Note Well)
Thread-Topic: finding the union of multiple documents (was Re: Problem with new Note Well)
Thread-Index: Ac8bqb8Xw0OX8qEST1qSoEnpSckMOw==
Message-ID: <CF0C3BA9.B2AC%wesley.george@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
acceptlanguage: en-US
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:50:21 -0000

DQpPbiAxLzI3LzE0LCAxMjoyMCBQTSwgIkRhdmUgQ3JvY2tlciIgPGRoY0BkY3JvY2tlci5uZXQ+
IHdyb3RlOg0KPg0KPiAgICAgIDUuICBFeHBlY3RpbmcgYW4gYXZlcmFnZSBJRVRGIGVuZ2luZWVy
IHRvIGNvbnN1bHQgNCBkaWZmZXJlbnQNCj5CQ1BzLCBpbiBvcmRlciB0byB1bmRlcnN0YW5kIHdo
YXQgaXMgcmVxdWlyZWQgb2YgdGhlbSBpcyBub3QgcmVhc29uYWJsZS4NCj4gIE5vciBpcyBhbGwg
ZWFjaCBkb2N1bWVudCByZWxldmFudC4gIFNvLCBpbiBlZmZlY3QsIHRoZSByZWZlcmVuY2VzIGFy
ZQ0KPm92ZXJseSBicm9hZCwgYXMgd2VsbCBhcyB0b28gY29tcGxpY2F0ZWQuIChTZWUgcG9pbnQg
Ni4pDQo+DQo+PHNuaXA+DQo+ICAgICAgMy4gIFdlIG5lZWQgYWxsIG9mIHRoZSBJUFIgcnVsZXMg
Zm9yIElFVEYgcGFydGljaXBhdGlvbiB0byBiZSBpbiBhDQo+c2luZ2xlLCBzaW1wbGUsIGNsZWFy
IGRvY3VtZW50IHRoYXQgaXMgZWFzaWx5IHVuZGVyc3RhbmRhYmxlIGJ5IGFuDQo+YXZlcmFnZSBl
bmdpbmVlci4gKFNlZSBwb2ludCAxLikNCg0KV2h5IHNob3VsZCBJRVRGIGVuZ2luZWVycyBnZXQg
c3BlY2lhbCB0cmVhdG1lbnQgb3ZlciBhbnlvbmUgdHJ5aW5nIHRvDQppbXBsZW1lbnQgYW4gSUVU
RiBzdGFuZGFyZD8gVGhpcyBpcyBhIG11Y2ggbGFyZ2VyIHByb2JsZW0gdGhhdCBleGlzdHMgZm9y
DQptYW55IG9mIElFVEbigJlzIGRvY3VtZW50cyB0aGF0IGhhdmUgYmVlbiBwYXJ0aWFsbHkgdXBk
YXRlZCBieSBzdWJzZXF1ZW50DQpkb2N1bWVudHMgcmF0aGVyIHRoYW4gY29tcGxldGVseSByZXBs
YWNlZC9vYnNvbGV0ZWQgYnkgYSBCSVMgdmVyc2lvbi4NClRyeWluZyB0byBmb2xsb3cgdGhlIHVw
ZGF0ZXMvcmVwbGFjZXMgY2hhaW4gb24gc29tZSBzZXRzIG9mIGRvY3VtZW50cyB0bw0KZmlndXJl
IG91dCB3aGF0IHlvdeKAmXJlIGFjdHVhbGx5IHN1cHBvc2VkIHRvIGltcGxlbWVudCBjYW4gYmUg
cXVpdGUNCmZydXN0cmF0aW5nLiBXb3VsZG7igJl0IGl0IGJlIG5pY2UgdG8gaGF2ZSBhIG1vZHVs
YXIgZG9jdW1lbnQgbWFuYWdlbWVudA0Kc3lzdGVtIHRoYXQgd2FzIGNhcGFibGUgb2YgdXNpbmcg
bWV0YWRhdGEgdG8gdGFrZSBhbiBvcmlnaW5hbCBkb2N1bWVudCwNCnRoZSBpZGVudGlmaWVkIHNl
dCBvZiBjaGFuZ2VzIGZyb20gb25lIG9yIG1vcmUgc3Vic2VxdWVudCDigJx1cGRhdGluZ+KAnQ0K
ZG9jdW1lbnRzLCBhbmQgc3ludGhlc2l6aW5nIGEgbmV3IGRvY3VtZW50IHRoYXQgaGFzIGFsbCBv
ZiB0aGUgaW5mbyBpbiBvbmUNCnBsYWNlPw0KU2VlbXMgYSB3b3J0aHdoaWxlIHByb2JsZW0gdG8g
dHJ5IHRvIHNvbHZlLCBlc3BlY2lhbGx5IGFzIHRoZSBzZXJpZXMgYWdlcy4NCkkgYmV0IHdlIGNv
dWxkIGRvIGl0IGV2ZW4gaWYgd2UgaGFkIHRvIGtlZXAgdGhlIGV4aXN0aW5nIExQUi1mcmllbmRs
eQ0KYWxsLXRleHQgZm9ybWF0LiA7LSkNCg0KV2VzIEdlb3JnZQ0KDQpBbnl0aGluZyBiZWxvdyB0
aGlzIGxpbmUgaGFzIGJlZW4gYWRkZWQgYnkgbXkgY29tcGFueeKAmXMgbWFpbCBzZXJ2ZXIsIEkN
CmhhdmUgbm8gY29udHJvbCBvdmVyIGl0Lg0KLS0tLS0tLS0tLS0NCg0KDQpUaGlzIEUtbWFpbCBh
bmQgYW55IG9mIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBUaW1lIFdhcm5lciBDYWJsZSBw
cm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hpY2ggaXMgcHJpdmlsZWdlZCwgY29uZmlkZW50aWFs
LCBvciBzdWJqZWN0IHRvIGNvcHlyaWdodCBiZWxvbmdpbmcgdG8gVGltZSBXYXJuZXIgQ2FibGUu
IFRoaXMgRS1tYWlsIGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBvZiB0aGUgaW5kaXZp
ZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggaXQgaXMgYWRkcmVzc2VkLiBJZiB5b3UgYXJlIG5vdCB0
aGUgaW50ZW5kZWQgcmVjaXBpZW50IG9mIHRoaXMgRS1tYWlsLCB5b3UgYXJlIGhlcmVieSBub3Rp
ZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIGNvcHlpbmcsIG9yIGFj
dGlvbiB0YWtlbiBpbiByZWxhdGlvbiB0byB0aGUgY29udGVudHMgb2YgYW5kIGF0dGFjaG1lbnRz
IHRvIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1
bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3Rp
ZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmln
aW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBwcmludG91dC4NCg==

From farmer@umn.edu  Mon Jan 27 13:57:15 2014
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 716801A0274 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QEJOx6OfSNEo for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 13:57:13 -0800 (PST)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.135.88]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7EA1A0235 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:57:08 -0800 (PST)
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Mon, 27 Jan 2014 15:57:02 -0600 (CST)
X-Umn-Remote-Mta: [N] mail-ie0-f181.google.com [209.85.223.181] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ie0-f181.google.com with SMTP id to1so1647870ieb.40 for <ietf@ietf.org>; Mon, 27 Jan 2014 13:57:01 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=sqw3vQb+05YZvX7fe6BJ2cv5eU7074TbzVEOcpWoIro=; b=jCp+E8gEDHrLo+YCpcQYnaX3YlFi8bLv85A31eHu3PXQgIo7yzSxO0m844U9mjiz7k VbjYizcdc3AbQyQ51Auhj+HERAYkA6f2DAE87EydyhiZcE6YmmjXVgnDqBOFQ2680Zk5 WArB8VyWuPJvDs426vzp8eT0E5LueMgSCKU2AycDjREQBGpFycNNbOjPxczpL/e4JxGl OsHhUBjmgcTIaryHIX9mFjYum6XdJkAAE8sGmiYuFzoqxIu0Q2UBks0IcOY6ma+fNR6k qsmeARGpmVaWzWdHzkH/TMo7G3CxyTjo6zocfqGzsaRsTuh/fyPyIAxwz7MQQs/Y1Hat V08Q==
X-Gm-Message-State: ALoCoQncqjt2KgyI/py1fP/GtkiufZmY5G6+9oNLnuZdnwJQ9NZ6ci5lXa9YIa9jnDMFxQ5+MO6aFwEZ02VKhSNDZwlbGdlqx8Ccl4/wJiRyBQ6GP110bLe0AtIz6k0NTzcwA7I9HRCD
X-Received: by 10.50.43.199 with SMTP id y7mr19713032igl.43.1390859821496; Mon, 27 Jan 2014 13:57:01 -0800 (PST)
X-Received: by 10.50.43.199 with SMTP id y7mr19713014igl.43.1390859821255; Mon, 27 Jan 2014 13:57:01 -0800 (PST)
Received: from x-160-94-7-119.uofm-secure.wireless.umn.edu (x-160-94-7-119.uofm-secure.wireless.umn.edu. [160.94.7.119]) by mx.google.com with ESMTPSA id d18sm48983249igz.0.2014.01.27.13.56.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 27 Jan 2014 13:56:58 -0800 (PST)
Message-ID: <52E6D628.80103@umn.edu>
Date: Mon, 27 Jan 2014 15:56:56 -0600
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, 'Russ Housley' <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk>
In-Reply-To: <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 'IETF' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 21:57:15 -0000

On 1/25/14, 14:14 , Adrian Farrel wrote:
> Hi Russ,
>
> Thanks for this. The -03 revision just posted addresses my comments.
>
> Adrian

Russ,

I also like the -03 revision, its has generally moved everything in the 
right direction.  But I have a few comments on it.

1. The part about RFC2860 in Section 1 seems like an incomplete thought, 
at the very least it seems awkward to me.  I'm really not sure what you 
are intending to say.  But, I agree RFC2860 is relevant to the 
discussion.  I'm just not sure you have nailed what to say about it.

2. I really like the idea of creating a "Special-Purpose AS Number 
Registry".  However, it may be a better idea to spin-off the creation of 
a "Special-Purpose AS Number Registry" into a separate draft.  I'm 
concerned that trying to do two important things in the same document 
will fail to achieve one or both of the important things.  For instance 
the simple section 3 you have currently worries me.  I'd really think 
RFC6890 is the template to use for creating a "Special-Purpose AS Number 
Registry", more below.

If you spin-off the creation of a "Special-Purpose AS Number Registry", 
the following items are for that draft.

3. There is a draft in WG Last Call in the IDR that documents the 
reservations of ASNs 65535 and 4294967295, the "Last ASNs".
http://tools.ietf.org/html/draft-ietf-idr-last-as-reservation-01

4. As I said, I like the idea of creating a "Special-Purpose AS Number 
Registry", but it should have certain information recoded about each AS 
number range.  This information should be similar to the format 
described in Section 2.2.1 of RFC6890 for the "Special-Purpose IP 
Address Registries" for IPv4 and IPv6, that you reference elsewhere in 
the draft.

First, there should be general information describing each of the 
special-purpose ASN ranges, essentially the first half of the columns 
specified in Section 2.2.1 of RFC6890;

  o AS Number Range - An AS number or range of AS numbers that has been
    registered for a special purpose.

  o Name - A descriptive name for the special-purpose AS number range.

  o RFC - The RFC through which the special-purpose AS number range was
    requested.

  o Allocation Date - The date upon which the special-purpose AS number
    range was allocated.

  o Termination Date - The date upon which the allocation is to be
    terminated.  This field is applicable for limited-use allocations
    only.

Then, information specific to how the special-purpose ASNs are to be 
used.  There may be others as well, I but I think these are the minimum.

  o Local - A boolean value indicating whether an AS number from the
    allocated special-purpose AS Number range is valid when used as the
    value of the "My Autonomous System" field of a BGP OPEN message, or
    equivalently in the Capability Value of the "support for four-octet
    AS number capability".

  o Global - A boolean value indicating whether an ASN from the allocated
    special-purpose ASN range is valid in the AS_PATH or AS4_PATH
    attributes when advertised to the global Internet.

  o Reserved-by-Protocol - A boolean value indicating whether the
    special-purpose address block is reserved by BGP, itself.  This
    value is "TRUE" if the RFC that created the special-purpose ASN
    range requires all compliant implementations to behave in a special
    way when this ASN is used.

I believe this is the table for these last three items

    ASN Range              Local    Global   Reserved-by-Protocol
    ---------------------  -------  -------  --------------------
    0                      FALSE    FALSE    TRUE
    23456                  TRUE[1]  TRUE[1]  TRUE
    64496-64511            FALSE    FALSE    FALSE
    64512-65534            TRUE     FALSE    FALSE
    65535                  FALSE    FALSE    FALSE
    65536-65551            FALSE    FALSE    FALSE
    4200000000-4294967294  TRUE     FALSE    FALSE
    4294967295             FALSE    FALSE    FALSE

    [1] Only valid in a BGP OPEN message or AS_PATH, not valid within a
    four-octet AS number capability negotiation or AS4_PATH.


Thanks.

-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================

From dhc@dcrocker.net  Mon Jan 27 14:04:58 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E85031A0093 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 14:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ayKVW70W3jES for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 14:04:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 480831A0068 for <ietf@ietf.org>; Mon, 27 Jan 2014 14:04:57 -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 s0RM4pKr017449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 14:04:54 -0800
Message-ID: <52E6D7EE.60706@dcrocker.net>
Date: Mon, 27 Jan 2014 14:04:30 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: finding the union of multiple documents (was Re: Problem with new Note Well)
References: <CF0C3BA9.B2AC%wesley.george@twcable.com>
In-Reply-To: <CF0C3BA9.B2AC%wesley.george@twcable.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 Jan 2014 14:04:55 -0800 (PST)
Cc: RFC Interest <rfc-interest@rfc-editor.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 27 Jan 2014 22:04:59 -0000

On 1/27/2014 1:50 PM, George, Wes wrote:
> Why should IETF engineers get special treatment over anyone trying to
> implement an IETF standard? This is a much larger problem that exists for
> many of IETFâ€™s documents that have been partially updated by subsequent
> documents rather than completely replaced/obsoleted by a BIS version.


I'll encourage avoiding this bit of scope-creep.  As with most such 
cases, it's not that the point is not valid.  It's valid.  And pursuing 
simplification is a worth goal.

But it's also a much, much larger task.

In addition, application of IETF IPR requirements by participants, in 
real-time, is an entirely different behavioral demand, from what a 
programmer needs to do in the much more casual pace of working "offline".

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From gdaley@au.logicalis.com  Mon Jan 27 14:18:16 2014
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85AA91A0366; Mon, 27 Jan 2014 14:18:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.442
X-Spam-Level: 
X-Spam-Status: No, score=-1.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9C45GdneVQvu; Mon, 27 Jan 2014 14:18:14 -0800 (PST)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id 77AFB1A0093; Mon, 27 Jan 2014 14:18:13 -0800 (PST)
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([203.8.7.161]) by smtp2.au.logicalis.com with ESMTP; 28 Jan 2014 09:18:10 +1100
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([fe80::68b7:8880:fefb:f742%12]) with mapi id 14.02.0347.000; Tue, 28 Jan 2014 09:18:09 +1100
From: Greg Daley <gdaley@au.logicalis.com>
To: "'curtis@ipv6.occnc.com'" <curtis@ipv6.occnc.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPGg60ZzPPQlRcgk6ua2U45NfiYJqZJKag
Date: Mon, 27 Jan 2014 22:18:08 +0000
Message-ID: <72381AF1F18BAE4F890A0813768D992817FD63D0@sdcexchms.au.logicalis.com>
References: Your message of "Fri, 24 Jan 2014 03:38:44 +0000." <72381AF1F18BAE4F890A0813768D992817FD35E1@sdcexchms.au.logicalis.com> <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.196.186]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "mpls@ietf.org" <mpls@ietf.org>, Edward Crabbe <edc@google.com>, IETF discussion list <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 22:18:17 -0000

Hi Curtis,=20

> -----Original Message-----
[my post chopped]
>=20
>=20
> Reality check time.
>=20
> To get the PW over MPLS drafts past the TSV AD there is a SHOULD regardin=
g
> congestion control.
>=20
> AFAIK: No service providers ask for it.  No one implements it.  If they d=
id
> implement it no one would deploy it.
>=20
> PW over MPLS is generally carrying relatively low volumes of high priorit=
y
> traffic.  The TC bits (MPLS flavor of Diffserv DSCP) are used to enforce =
the
> higher priority.  If congestion occurs other traffic on that infrastructu=
re
> (typically plain old Internet) sees loss.  That is intended.  This is the=
 reality of
> how PW over MPLS is deployed.
>=20
> Anyone who knows of implementation or deployment of congestion control fo=
r
> PW over MPLS can correct me.
>=20
> I don't know about the "over GRE" or "over L2TP" tunneling.

Essentially, my point is that with traditional carriage environments there =
is an underlying medium which it may be possible to traffic engineer.
The value of a SHOULD is that it isn't necessary to there is a valid reason=
 not to follow it (i.e. you control the medium and/or the ingress traffic f=
lows and the traffic remains private).  The onus remains on the implementer=
 and deployer not to mess up the Internet.

I think that similar guidance may be applicable in this case (as in GRE and=
 L2TP encapsulations), where the next label switch could be across paths sh=
ared with other Internet traffic that has congestion avoidance, mitigation =
or control.

Sincerely,=20

Greg Daley

From l.wood@surrey.ac.uk  Mon Jan 27 15:18:25 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A842B1A03F5; Mon, 27 Jan 2014 15:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HRYjlQSwBXdA; Mon, 27 Jan 2014 15:18:23 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.138]) by ietfa.amsl.com (Postfix) with ESMTP id 440351A03F4; Mon, 27 Jan 2014 15:18:23 -0800 (PST)
Received: from [195.245.231.67:50896] by server-2.bemta-5.messagelabs.com id F8/1A-29392-C39E6E25; Mon, 27 Jan 2014 23:18:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-82.messagelabs.com!1390864700!16172229!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 27996 invoked from network); 27 Jan 2014 23:18:20 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-15.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 27 Jan 2014 23:18:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 27 Jan 2014 23:18:19 +0000
From: <l.wood@surrey.ac.uk>
To: <touch@isi.edu>, <stbryant@cisco.com>
Date: Mon, 27 Jan 2014 23:17:24 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8bf94zJtt9BjXcSyehmYkUhwCIgwANhGc2
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346F6@EXMB01CMS.surrey.ac.uk>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com>,<98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
In-Reply-To: <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 23:18:25 -0000

...and UDP Lite just covering the L3 and L4 headers, but not the full paylo=
ad a la UDP,
 is still possible when the full payload is not visible.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Joe Touch [touch@isi.edu]
Sent: 27 January 2014 16:48
To: stbryant@cisco.com
Cc: mpls@ietf.org; IETF discussion list; curtis@ipv6.occnc.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Those same mechanisms have provided hardware checksum support for a very lo=
ng time.

Joe

> On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>
>> On 24/01/2014 19:15, Joe Touch wrote:
>>
>>> This eliminates the "expands the reach of MPLS argument".
>>>
>>> First UDP checksums:
>>>
>>>   The UDP checksum is at the beginning of the payload.  Please see
>>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
>>>   This makes filling in a new UDP checksum infeasible on most high end
>>>   hardware.
>>
>> That argument would make sense if most hardware wasn't store-and-forward=
 on a per-packet basis.
> They may be store and forward, but most of the high end designs
> use multiple grades of memory putting the packet in "slow memory"
> and providing a snapshot of the header in "fast memory" to the
> forwarder. Thus although the whole packet is in the system, it
> it is not accessible to the engine that would need to calculate the
> c/s.
>
> Stewart

From l.wood@surrey.ac.uk  Mon Jan 27 15:20:44 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D06821A0403; Mon, 27 Jan 2014 15:20:44 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qpFspQ5__ypV; Mon, 27 Jan 2014 15:20:42 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id 21CD11A03E5; Mon, 27 Jan 2014 15:20:41 -0800 (PST)
Received: from [85.158.137.99:12055] by server-12.bemta-3.messagelabs.com id E7/CE-20055-6C9E6E25; Mon, 27 Jan 2014 23:20:38 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-217.messagelabs.com!1390864837!20311613!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20075 invoked from network); 27 Jan 2014 23:20:38 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-15.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 27 Jan 2014 23:20:38 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 27 Jan 2014 23:20:37 +0000
From: <l.wood@surrey.ac.uk>
To: <touch@isi.edu>, <jmh@joelhalpern.com>, <joelja@bogus.com>, <stbryant@cisco.com>
Date: Mon, 27 Jan 2014 23:18:56 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8blZc5hdQm73++Ro+O4zq8V8TTqQAII9Om
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346F7@EXMB01CMS.surrey.ac.uk>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com>,<52E6B272.4030703@isi.edu>
In-Reply-To: <52E6B272.4030703@isi.edu>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: mpls@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 23:20:44 -0000

"ASICs can't do IPv6 in hardware! IPv6 can only be done with slow
software forwarding! We're stuck with v4!"

I think we've been here before.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: mpls [mpls-bounces@ietf.org] On Behalf Of Joe Touch [touch@isi.edu]
Sent: 27 January 2014 19:24
To: Joel M. Halpern; joel jaeggli; stbryant@cisco.com
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
> Yes Joe, routers could ahve been built to do those calcualtions at that
> performance scale.
> There are however two major problems:
>
> 1) That is not how routers are built.
> 2) The target performance scale is rather higher.
>
> So could someone build an ASIC to do what you want?

Has. It's already part of nearly every DMA ASIC in a network interface
already.

 > Probably.  Is there
> any reason in the world to expect operators to pay the significant extra
> cost for such?Not that I can see.

We're talking about a ring of full adders, the specs for which are given
in an RFC that's 18 years old, and that is already implemented in nearly
every host interface, including 10Gps NICs.

And we're talking about "routers", many variants of which operate at
very high speeds and transparently proxy TCP already. So this is a
solved problem.

> And even if we could and they would, that is not the world into which we
> are deploying these tunnels.

We're back to "that's not what they do now", at least in some devices.

Well, they don't use MPLS in UDP (since no spec exists), so clearly if
they're limited to doing what they already do, this is an exercise in
futility.

Joe

>
> Yours,
> Joel
>
> On 1/27/14 1:53 PM, Joe Touch wrote:
>>
>>
>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>> Those same mechanisms have provided hardware checksum support for a
>>>> very long time.
>>>
>>> The new header and the payload are actually in different parts of the
>>> forwarding complex until they hit the output queue, you can't checksum
>>> data you don't have.
>>
>> You can (and some do) the checksum component parts when things go into
>> memory; the partial sums can be added as the parts are combined in the
>> output queue.
>>
>> I appreciate that we're all taking about what might be done, but the
>> reality is that there are many 'transparent TCP proxies' that have to do
>> this, so there's clearly a solution, and it clearly runs fast enough.
>>
>> Joe
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From bclaise@cisco.com  Mon Jan 27 16:14:52 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451D61A015B for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZdtNq3ine0He for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:14:50 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id CF9AF1A008F for <ietf@ietf.org>; Mon, 27 Jan 2014 16:14:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2731; q=dns/txt; s=iport; t=1390868087; x=1392077687; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=z2q2l2w+ePb8Ncf0l0040HiIUslLI7zcWNkNpv364xQ=; b=mMcyRrCuXD6PTJOxNWiGC3X7znPjNhRJaTQFf/v+JuEscga30+rNCmff z3F8a/0oSdv0Jv2E9K+CgzkrOxugg8JRMD7IPWEBXyTDXggACJ21BuZoV hfHo5v322yNNtwvc+8i+P4dfeA0nhDio1ISyQ15awdmTUIHSnnpdR/gf2 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAIv15lKQ/khN/2dsb2JhbABagww4vTSBGxZ0giUBAQEDATg2CgYHBAsRBAEBChYEBAcJAwIBAgE0CQgHDAYCAQGHeQgNxwUXjxQGhDIBA5gngTKFFYQWh0GBb4E/Ow
X-IronPort-AV: E=Sophos;i="4.95,732,1384300800";  d="scan'208";a="3602030"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-2.cisco.com with ESMTP; 28 Jan 2014 00:14:46 +0000
Received: from [10.61.214.84] ([10.61.214.84]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s0S0Ekgr008356; Tue, 28 Jan 2014 00:14:46 GMT
Message-ID: <52E6F676.9020104@cisco.com>
Date: Tue, 28 Jan 2014 01:14:46 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, ietf@ietf.org
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk>
In-Reply-To: <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 00:14:52 -0000

Adrian,

Not an answer to the process question, but some background information 
on this draft.
This draft, which is now 3 years old, has been evolving with the IPFIX 
standardization.
For example, looking at 
http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt, 
you can see the interaction with the IPFIX WG document 
ietf-ipfix-data-link-layer-monitoring: now that
ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the 
draft has been simplified, and some IPFIX Information Elements in the 
range 1-127 became deprecated.
This explains why the draft has been presented and reviewed multiple 
times in the IPFIX WG, and also why it would benefit from a wider review 
than the independent stream.

Regards, Benoit (as draft author)


> Hi,
>
> I have a process question on this last call which is not clear from the last
> call text.
>
> Are we being asked to consider whether publication of this document is useful,
> or are we being asked for IETF consensus on the *content* of the document?
>
> It seems from the document that the content is descriptive of something
> implemented by a single vendor. I applaud putting that information into the
> public domain, but I don't understand the meaning of IETF consensus with respect
> to this document.
>
> Thanks,
> Adrian
>
>> -----Original Message-----
>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
>> IESG
>> Sent: 21 January 2014 12:33
>> To: IETF-Announce
>> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
>> Information Elements reused in IPFIX) to Informational RFC
>>
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'Cisco Specific Information Elements reused in IPFIX'
>>    <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>     This document describes some additional Information Elements of Cisco
>>     Systems, Inc. that are not listed in RFC3954.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>
> .
>


From presnick@qti.qualcomm.com  Mon Jan 27 16:56:13 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3E3A1A00B7 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YADTkpP6khMg for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:56:11 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6A3101A008F for <ietf@ietf.org>; Mon, 27 Jan 2014 16:56:11 -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=1390870569; x=1422406569; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Kp207zVpXFG7RWD702OJJ9xso1u6kXcMMNeAszsK3/c=; b=RBj75bkj+NhaYXLAkZ3v/FogLFmp/DM7T1Eu6XF30ISiVnZLiP39cwnJ QPzogiXJFkNobBMrL1NF3oCATH9EvxijqoT/fqBqGm3x/6hnntfQac8mC mTzypZ7i94lIg9ziyL02QA0RTpKqM7p1hU8NVvV1au1LgY+Y/gXrUnkKR 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,7331"; a="58611801"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth01.qualcomm.com with ESMTP; 27 Jan 2014 16:56:09 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7331"; a="26217861"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Jan 2014 16:56:08 -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.3.158.1; Mon, 27 Jan 2014 16:56:07 -0800
Message-ID: <52E70025.6060707@qti.qualcomm.com>
Date: Mon, 27 Jan 2014 18:56:05 -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: Thomas Narten <narten@us.ibm.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com>
In-Reply-To: <m3ppnda5r0.wl%narten@us.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 00:56:13 -0000

On 1/27/14 7:55 AM, Thomas Narten wrote:
>> The Independent RFC Stream would seem more appropriate.
>>      
> Well, if you run a document through the RFC Stream publication
> process, it doesn't get the same level/type of review as does running
> it through the IETF. At least in theory.
>    

If it were running through a WG and the WG wanted to publish it, I'd be 
much more likely to believe that it was getting a better level/type of 
review than running it through the ISE. But just getting a Last Call as 
an AD-sponsored document? I have my doubts.

And though Lars is right that we've been darn inconsistent about it, 
2026 does say that we're not supposed to be doing that:

http://tools.ietf.org/html/rfc2026#section-4.2.3

The ISE can always send a message to the IETF list saying, "I'd like the 
IETF to have a look at this document and send comments." I think it is 
almost identically as effective as sending out an IETF Last Call for an 
AD-sponsored Informational document.

I can imagine times where an AD-sponsored Informational document is 
useful, but I'm guessing there are far less than the number of times we 
do it.

pr

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


From stephen.farrell@cs.tcd.ie  Mon Jan 27 17:18:17 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8E081A008F for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Km8-fGG7kGmg for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:18:15 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC971A00A7 for <ietf@ietf.org>; Mon, 27 Jan 2014 17:18:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3DA15BE24; Tue, 28 Jan 2014 01:18:12 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOx4RiT750lx; Tue, 28 Jan 2014 01:18:10 +0000 (GMT)
Received: from [10.87.48.8] (unknown [86.46.27.32]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id A3D5DBE20; Tue, 28 Jan 2014 01:18:10 +0000 (GMT)
Message-ID: <52E70548.3090703@cs.tcd.ie>
Date: Tue, 28 Jan 2014 01:18:00 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>,  Thomas Narten <narten@us.ibm.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com> <52E70025.6060707@qti.qualcomm.com>
In-Reply-To: <52E70025.6060707@qti.qualcomm.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 01:18:18 -0000

Pete,

On 01/28/2014 12:56 AM, Pete Resnick wrote:
> On 1/27/14 7:55 AM, Thomas Narten wrote:
>>> The Independent RFC Stream would seem more appropriate.
>>>      
>> Well, if you run a document through the RFC Stream publication
>> process, it doesn't get the same level/type of review as does running
>> it through the IETF. At least in theory.
>>    
> 
> If it were running through a WG and the WG wanted to publish it, I'd be
> much more likely to believe that it was getting a better level/type of
> review than running it through the ISE. But just getting a Last Call as
> an AD-sponsored document? I have my doubts.
> 
> And though Lars is right that we've been darn inconsistent about it,
> 2026 does say that we're not supposed to be doing that:
> 
> http://tools.ietf.org/html/rfc2026#section-4.2.3

Which also says:

  "In order to differentiate these Internet-Drafts
   they will be labeled or grouped in the I-D directory so they are
   easily recognizable."

Pretty modern eh;-) And hightly likely to be meaningful
to readers.

More relevant though, the same section implies correctly
that it'd be a bad plan to let people easily "circumvent
the Internet Standards Process" and I would argue that
doing an IETF LC is a fine way for that be tested. About
as good as the ISE asking the IESG probably on balance
though the trade offs differ.

I suspect we'll be better off just not getting bothered
until such time as someone takes on the always-gargantuan
task of updating this bit of 2026.

> The ISE can always send a message to the IETF list saying, "I'd like the
> IETF to have a look at this document and send comments." I think it is
> almost identically as effective as sending out an IETF Last Call for an
> AD-sponsored Informational document.
> 
> I can imagine times where an AD-sponsored Informational document is
> useful, but I'm guessing there are far less than the number of times we
> do it.

I'm not at all clear why its useful to be bothered about
that. Can you explain how we all win?

I've no idea what's in draft-yourtchenko, but I do not
have any general problem with something that could be sent
to the ISE being handled in this way. And nor should any
of us I reckon, unless we prefer pointless process over
getting-stuff-done, in the absence of a particular issue
with the draft.

S.


> 
> pr
> 

From presnick@qti.qualcomm.com  Mon Jan 27 17:30:52 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DACF1A0345 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:30:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level: 
X-Spam-Status: No, score=-4.836 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHagq2ayISO8 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:30:50 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 886C81A00A7 for <ietf@ietf.org>; Mon, 27 Jan 2014 17:30:50 -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=1390872648; x=1422408648; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xXigV/OaCRGtl6QuiqN4hcMIDwXJhVHBXvT70MDnYpc=; b=dIVxHQ3+QPMU+beFcSd8myIJlX1LR36awVw8SDGT4IPPxmEOpuHSUyQD 2arBVCfphhtyYqE/pt8nDfrypZGs58kySVP7bFMtVgdQs+Y90RCeUcJZZ /L3xI1AY49aUASBlRImj3jm228IIeH8kMe/+8hHEzM7RaTizqI7jWHkQO A=;
X-IronPort-AV: E=McAfee;i="5400,1158,7331"; a="10769644"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 27 Jan 2014 17:30:48 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7331"; a="674607800"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 27 Jan 2014 17:30:47 -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.3.158.1; Mon, 27 Jan 2014 17:30:47 -0800
Message-ID: <52E70845.1030806@qti.qualcomm.com>
Date: Mon, 27 Jan 2014 19:30:45 -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: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com> <52E70025.6060707@qti.qualcomm.com> <52E70548.3090703@cs.tcd.ie>
In-Reply-To: <52E70548.3090703@cs.tcd.ie>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: Thomas Narten <narten@us.ibm.com>, Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 01:30:52 -0000

On 1/27/14 7:18 PM, Stephen Farrell wrote:
>> I can imagine times where an AD-sponsored Informational document is
>> useful, but I'm guessing there are far less than the number of times we
>> do it.
>>      
> I'm not at all clear why its useful to be bothered about
> that. Can you explain how we all win?
>    

Somehow I feel responsible to actually review AD-sponsored documents, 
both for content as well as for IETF consensus. It wastes my time as an 
AD. I suppose I could get over that and simply review them for end-runs.

I suppose there's also the bigger question of why other ADs are wasting 
their time sponsoring, reviewing, and doing all of the process nonsense 
associated with publishing a draft that not even a WG is interested 
enough to do all of that with. I guess that's mostly that AD's problem, 
but it's time wasted that could be better spent. (As you are fond of 
saying, ADs will always fill there time, no matter what they really have 
to do. I say let them fill it with other things.)

And then of course is the "stake in the heart" of any semblance of our 
document categories meaning anything. ("Sometimes, Informational means 
there is IETF consensus that this is a good piece of information; 
sometimes not.") But I suppose that spilled milk is under the dam or 
over the bridge and we might as well lie in it.

> ...I do not
> have any general problem with something that could be sent
> to the ISE being handled in this way. And nor should any
> of us I reckon, unless we prefer pointless process over
> getting-stuff-done...
>    

That's exactly my point. Seems pointless to waste time on the process 
for this document when we could dump it over the wall and let the ISE 
deal with it. Unless there's some reason it's important for the IETF to 
waste time on it.

pr

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


From stephen.farrell@cs.tcd.ie  Mon Jan 27 17:43:32 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C102E1A03DD for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FJVv4TrtEyBx for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 17:43:31 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9E76F1A03DB for <ietf@ietf.org>; Mon, 27 Jan 2014 17:43:30 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 77B7EBE1C; Tue, 28 Jan 2014 01:43:26 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lEdl35WDqm+7; Tue, 28 Jan 2014 01:43:25 +0000 (GMT)
Received: from [10.87.48.8] (unknown [86.46.27.32]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 50196BDE3; Tue, 28 Jan 2014 01:43:25 +0000 (GMT)
Message-ID: <52E70B32.2000607@cs.tcd.ie>
Date: Tue, 28 Jan 2014 01:43:14 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com> <52E70025.6060707@qti.qualcomm.com> <52E70548.3090703@cs.tcd.ie> <52E70845.1030806@qti.qualcomm.com>
In-Reply-To: <52E70845.1030806@qti.qualcomm.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Thomas Narten <narten@us.ibm.com>, Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 01:43:33 -0000

On 01/28/2014 01:30 AM, Pete Resnick wrote:
> 
> And then of course is the "stake in the heart" of any semblance of our
> document categories meaning anything. ("Sometimes, Informational means
> there is IETF consensus that this is a good piece of information;
> sometimes not.") But I suppose that spilled milk is under the dam or
> over the bridge and we might as well lie in it.

The semblance of that semblance has long left the building
I reckon.

>> ...I do not
>> have any general problem with something that could be sent
>> to the ISE being handled in this way. And nor should any
>> of us I reckon, unless we prefer pointless process over
>> getting-stuff-done...
>>    
> 
> That's exactly my point. Seems pointless to waste time on the process
> for this document when we could dump it over the wall and let the ISE
> deal with it. Unless there's some reason it's important for the IETF to
> waste time on it.

Ah sorry, the waste-of-time I meant was caring about the
process here, i.e. what you're doing:-)

I do agree ADs ought use their judgement as to what to
sponsor. But that's enough of a rule for my taste.

S.

From dhc@dcrocker.net  Mon Jan 27 18:18:57 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 633991A00A7 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 18:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15DTCaL7LN2o for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 18:18:56 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 152551A008F for <ietf@ietf.org>; Mon, 27 Jan 2014 18:18:56 -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 s0S2IhWX023929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 18:18:46 -0800
Message-ID: <52E71365.7070504@dcrocker.net>
Date: Mon, 27 Jan 2014 18:18:13 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com> <52E70025.6060707@qti.qualcomm.com> <52E70548.3090703@cs.tcd.ie> <52E70845.1030806@qti.qualcomm.com>
In-Reply-To: <52E70845.1030806@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 27 Jan 2014 18:18:51 -0800 (PST)
Cc: Thomas Narten <narten@us.ibm.com>, Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Jan 2014 02:18:57 -0000

On 1/27/2014 5:30 PM, Pete Resnick wrote:
> I suppose there's also the bigger question of why other ADs are wasting
> their time sponsoring, reviewing, and doing all of the process nonsense
> associated with publishing a draft that not even a WG is interested
> enough to do all of that with.


1. Not all documents require the work of a working group.  If there is 
believed to be no actual work to do on a document, then keeping it out 
of a wg isn't about lack of interest but lack of... work to do.

2. All that reviewing is called quality assurance.  I always thought 
that our open review processes had more to do with quality than with a 
status label.

Has the model changed and the standards label is all that matters these 
days?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From joelja@bogus.com  Mon Jan 27 22:50:34 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABF0A1A0235 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 22:50:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id asuIQjG_ieBh for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 22:50:33 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id D5FD11A022F for <ietf@ietf.org>; Mon, 27 Jan 2014 22:50:32 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s0S6oRW0047843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 28 Jan 2014 06:50:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <52E7532D.7040209@bogus.com>
Date: Mon, 27 Jan 2014 22:50:21 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: Benoit Claise <bclaise@cisco.com>, adrian@olddog.co.uk, ietf@ietf.org
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com>
In-Reply-To: <52E6F676.9020104@cisco.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hh79jFB7XoHV72Fpd2HRh8pHTPor4bLru"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Tue, 28 Jan 2014 06:50:28 +0000 (UTC)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 06:50:34 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--hh79jFB7XoHV72Fpd2HRh8pHTPor4bLru
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 1/27/14, 4:14 PM, Benoit Claise wrote:

>> Hi,
>>
>> I have a process question on this last call which is not clear from
>> the last
>> call text.
>>
>> Are we being asked to consider whether publication of this document is=

>> useful,
>> or are we being asked for IETF consensus on the *content* of the
>> document?

I'd actually like the communities input that there is not something
catastrophically wrong to sending the document on it's merry way that
I've missed.

>> It seems from the document that the content is descriptive of somethin=
g
>> implemented by a single vendor. I applaud putting that information
>> into the
>> public domain, but I don't understand the meaning of IETF consensus
>> with respect
>> to this document.

It seems highly likely that others have both implemented parsing of
these IEs and may well do so in the future for IEs which are not
depreciated. The fact that these are vendor specific doesn't preclude
there being interoperability concerns given that they are by their
nature exported. Much of Netflow and IPFIX has at one time been vendor
specific.

I don't think there much point is asking a working group to hold the pen
on this given that existing usage of existing values isn't likely to chan=
ge.

>>
>> Thanks,
>> Adrian
>>
>>> -----Original Message-----
>>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf=

>>> Of The
>>> IESG
>>> Sent: 21 January 2014 12:33
>>> To: IETF-Announce
>>> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Speci=
fic
>>> Information Elements reused in IPFIX) to Informational RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to consi=
der
>>> the following document:
>>> - 'Cisco Specific Information Elements reused in IPFIX'
>>>    <draft-yourtchenko-cisco-ies-09.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 th=
e
>>> ietf@ietf.org mailing lists by 2014-02-18. Exceptionally, comments
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>     This document describes some additional Information Elements of
>>> Cisco
>>>     Systems, Inc. that are not listed in RFC3954.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>
>> .
>>
>=20



--hh79jFB7XoHV72Fpd2HRh8pHTPor4bLru
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLnUy4ACgkQ8AA1q7Z/VrJi7gCfcGtYvFWmlG7GDQZad3Mws2tY
t1cAn2TCAaeyVhI3nfAJbiiWRLhaDuWc
=9vTy
-----END PGP SIGNATURE-----

--hh79jFB7XoHV72Fpd2HRh8pHTPor4bLru--

From ned+ietf@mauve.mrochek.com  Mon Jan 27 22:52:09 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B67C81A022F for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 22:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aQ1AoY9WZ-r6 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 22:52:08 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 711D11A0235 for <ietf@ietf.org>; Mon, 27 Jan 2014 22:52:08 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3NYJ3Z6IO0039PF@mauve.mrochek.com> for ietf@ietf.org; Mon, 27 Jan 2014 22:47:02 -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 <01P3NP4TEOIO0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 27 Jan 2014 22:46:55 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P3NYJ02QBM0000AS@mauve.mrochek.com>
Date: Mon, 27 Jan 2014 22:36:56 -0800 (PST)
Subject: Re: Problem with new Note Well
In-reply-to: "Your message dated Mon, 27 Jan 2014 14:34:35 -0500" <20140127193435.GC87271@verdi>
References: <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <20140127193435.GC87271@verdi>
To: John Leslie <john@jlc.net>
Cc: iesg@ietf.org, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 06:52:09 -0000

> Dave Crocker <dhc@dcrocker.net> wrote:
> >
> > There are a number of different problems, and only some of them have
> > been articulated.  Worse, the problems include the IPR rules themselves,
> > not just the Note Well:
> >
> > 0. We have had IPR rules and a Note Well for many years and have
> >    revised both a number of times.

>    I'd bet 90% of folks who read the Note Well aren't even aware that
> BCP 79 is a concatenation of RFC 3979 and RFC 4879.

I didn't know that those were the specific RFCs involved. But I didn't have to.
I clicked on the link the last time the Note Well came up, up popped the text
of both RFCs and I read it.

>    It is a sad fact that having read BCP 79 eight years ago isn't "enough".

That's highly debatable. All RFC 4879 does is clarify one sentence in RFC 3979
having to do with the handling of third party disclosures by the Executive
Director. It doesn't affect the responsibilities of participants at all.

A cogent argument can be made that we should work towards consolidating 
and simplifying the IPR documents. This isn't it.

				Ned

From dhc@dcrocker.net  Mon Jan 27 23:26:45 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02EC61A01C9; Mon, 27 Jan 2014 23:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id imo48dr5Kg22; Mon, 27 Jan 2014 23:26:43 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 728831A0161; Mon, 27 Jan 2014 23:26:43 -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 s0S7Qa3a026977 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Jan 2014 23:26:39 -0800
Message-ID: <52E75B96.1000100@dcrocker.net>
Date: Mon, 27 Jan 2014 23:26:14 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>, John Leslie <john@jlc.net>
Subject: Re: Problem with new Note Well
References: <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <20140127193435.GC87271@verdi> <01P3NYJ02QBM0000AS@mauve.mrochek.com>
In-Reply-To: <01P3NYJ02QBM0000AS@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.66]); Mon, 27 Jan 2014 23:26:40 -0800 (PST)
Cc: iesg@ietf.org, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 28 Jan 2014 07:26:45 -0000

On 1/27/2014 10:36 PM, Ned Freed wrote:
>> >    It is a sad fact that having read BCP 79 eight years ago isn't "enough".
> That's highly debatable. All RFC 4879 does is clarify one sentence in RFC 3979
> having to do with the handling of third party disclosures by the Executive
> Director. It doesn't affect the responsibilities of participants at all.
>
> A cogent argument can be made that we should work towards consolidating
> and simplifying the IPR documents. This isn't it.


http://www.ietf.org/about/note-well.html contains pointers to multiple 
documents.  (I thought I saw 4 docs, but apparently it's 3.)

      "All IETF Contributions are subject to the rules of RFC 5378 and 
RFC 3979 (updated by RFC 4879)."

It does not matter how much or how little of each document is relevant. 
  The citations are generic, establishing a burden on the reader to 
consult all 3 documents and then try to figure out what parts of them apply.

The burden created by the presence of multiple, generic citations -- not 
the burden of the "relevant" text contained in any of those documents, 
once the readers figures out what's relevant -- is what I am calling 
inappropriate.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Mon Jan 27 23:41:00 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91CB81A02A1 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 23:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lk2JT3VJStb4 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 23:40:58 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A111D1A0276 for <ietf@ietf.org>; Mon, 27 Jan 2014 23:40:58 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W83Hq-000IXG-Lj; Tue, 28 Jan 2014 02:40:46 -0500
X-Vipre-Scanned: 01BE5C3F002C3101BE5D8C-TDI
Date: Tue, 28 Jan 2014 02:40:45 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Message-ID: <4529BD9437AD627F59CA3DB4@[192.168.1.128]>
In-Reply-To: <52E70B32.2000607@cs.tcd.ie>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <891684D8-96CE-44FF-B8DC-E3A4EA5938E8@netapp.com> <m3ppnda5r0.wl%narten@us.ibm.com> <52E70025.6060707@qti.qualcomm.com> <52E70548.3090703@cs.tcd.ie> <52E70845.1030806@qti.qualcomm.com> <52E70B32.2000607@cs.tcd.ie>
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: Thomas Narten <narten@us.ibm.com>, Adrian Farrel <adrian@olddog.co.uk>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 07:41:00 -0000

--On Tuesday, 28 January, 2014 01:43 +0000 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

> On 01/28/2014 01:30 AM, Pete Resnick wrote:
>> 
>> And then of course is the "stake in the heart" of any
>> semblance of our document categories meaning anything.
>> ("Sometimes, Informational means there is IETF consensus that
>> this is a good piece of information; sometimes not.") But I
>> suppose that spilled milk is under the dam or over the bridge
>> and we might as well lie in it.
> 
> The semblance of that semblance has long left the building
> I reckon.

Hmm. The community went to a lot of effort not long ago,
partially IIR at the urging of the then-IESG and IAB, to
identify RFCs by stream and to allow the streams to include
specific statements about review and consensus in the Status
section.  I wouldn't try to refute a claim that few people pay
attention to those labels and that text, but it is there and it
is supposed to be functional.  

Again IIR, we did not get rid of AD-sponsored at the time for
two reasons: 

(1) Many people felt that there were a few reasons for using
that process.  Most of them involved documents that had been
considered in and abandoned by a WG (including when a WG had
been closed with some documents still in progress).  If an AD
felt that they should continue to be processed in the IETF where
the context existed, that seemed to be more sensible than
starting over with the ISE and less context.  That principle
seems to me to apply whether the document is Standards Track,
inherently Informational, or published as a record of an
alternative that was considered and not chosen.  Others involved
suggestions for minor process patches or equivalent, where
AD-sponsorship of a document developed in the community seems
like a better option than the more recent pattern of
AD-initiated, AD-written (even with co-authors), and
AD-sponsored that, given professional courtesy within the IESG,
appears to be a recipe for abuse (even if actual abuses were
rare).

(2) The IESG didn't like the idea of giving up one of its
prerogatives.  Since they had to approve the relevant document
and changes, pushing to take it away from them seemed futile.


>>> ...I do not
>>> have any general problem with something that could be sent
>>> to the ISE being handled in this way. And nor should any
>>> of us I reckon, unless we prefer pointless process over
>>> getting-stuff-done...    
>> 
>> That's exactly my point. Seems pointless to waste time on the
>> process for this document when we could dump it over the wall
>> and let the ISE deal with it. Unless there's some reason it's
>> important for the IETF to waste time on it.

> Ah sorry, the waste-of-time I meant was caring about the
> process here, i.e. what you're doing:-)
> 
> I do agree ADs ought use their judgement as to what to
> sponsor. But that's enough of a rule for my taste.

I agree in the sense that I don't think that trying to write
fine distinctions into rules would help in this case.  And, to
repeat an argument from another thread that seems far more
applicable here, ADs who are inclined to abuse the system will
always find a way.

On the other hand, members of the community who believe that
particular ADs are not exercising good judgment in this area,
e.g., prioritizing their time and the community's on
AD-sponsored documents over getting the IETF's critical path
work done, should communicate their concerns to the Nomcom
which, I hope, is able to listen to new issues up to the day
that they deliver their reports about selections.   There is a
long history that, once a topic like this turns up and is
discussed, ADs who are reappointed consider their reappointment
as evidence of community approval for whatever they have been
doing, so comments to the Nomcom (this year and next) are now a
lot more important than they were a week ago.

Just IMO, of course.
    john





From jari.arkko@piuha.net  Mon Jan 27 23:44:07 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA9EB1A02A1; Mon, 27 Jan 2014 23:44:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a20CEbrs_sgS; Mon, 27 Jan 2014 23:44:07 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DFCBF1A0276; Mon, 27 Jan 2014 23:44:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2CF112CC61; Tue, 28 Jan 2014 09:44:04 +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 nVLtCgRKNEDU; Tue, 28 Jan 2014 09:44:03 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id A4DC72CC5D; Tue, 28 Jan 2014 09:44:03 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Problem with new Note Well 
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
Date: Tue, 28 Jan 2014 09:44:03 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <31F38883-AA9F-420F-877F-394C283A779F@piuha.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
X-Mailer: Apple Mail (2.1510)
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 07:44:08 -0000

For your information, as a temporary measure we have pulled back the =
change and the web site (registration etc) should now display the old =
note well text.

Jari


From alexey.melnikov@isode.com  Tue Jan 28 00:34:20 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2F431A019D; Tue, 28 Jan 2014 00:34:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tYwZcJ-XB8Ia; Tue, 28 Jan 2014 00:34:18 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id A1EEE1A003E; Tue, 28 Jan 2014 00:34:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1390898054; d=isode.com; s=selector; i=@isode.com; bh=lxpmDPU4z6yjKvLWu+4P5DeogEHrcYgaIXv+kitVDkQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=tJul53O7nj7jkfwO9ZwldU9iBYLe6DgI7Z3TSBVrEoVLvW6saEqqBFrjq5YIyaeH3r9n7v nITmf0AG2pYlcZlq4An73aZEHR2SBPzeIhE6F67NeQ3XAwplODskcolhB8913L/z1Yjm7M lAEsWRc9TTTxmNgRTzIGHMrKfRVep3s=;
Received: from [192.168.0.12] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <UudrhQAIPzmg@waldorf.isode.com>; Tue, 28 Jan 2014 08:34:14 +0000
X-SMTP-Protocol-Errors: PIPELINING
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPad Mail (11B511)
In-Reply-To: <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
Date: Tue, 28 Jan 2014 08:37:07 +0000
Message-Id: <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 08:34:20 -0000

On 27 Jan 2014, at 20:59, Barry Leiba <barryleiba@computer.org> wrote:

>> Actually, I think I convinced Barry that it is updating RFC 2683.
> 
> Yes: because the new line-length-limit recommendation is meant to
> apply whether or not condstore or qresync are in play, this "updates"
> remains (it's the others that used to be there that we scrubbed).
> 
> I think David's right that some version of what Eliot said:
> 
>> there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> 
> ...should be added to the section about the line-length limit.  A
> sentence or two should do nicely.

Yes, I agree.


From bclaise@cisco.com  Tue Jan 28 01:46:50 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D77621A02D9 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 01:46:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nhfEhVpjPfIr for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 01:46:47 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 997321A0233 for <ietf@ietf.org>; Tue, 28 Jan 2014 01:46:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11151; q=dns/txt; s=iport; t=1390902404; x=1392112004; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=4v9W20xs9GW3oQhU35L4umDKMZMPiruWPvHkipciIt4=; b=DZyfeDxeElajx7Zf0s/hRa8FDf9FGtyrVvqCRhovivr5hgyZDTUZ7wIy vShCSrn4rTGk8a6pRx8hI2xSVH8/DqDNk/h2TaattCUXNzjQNEmfH99sj CbBNv+DgjQgoEwkPUsOUgyBl8MKh6dzy7WabRn3Drq/m8y9eFB9t7FWqD M=;
X-IronPort-AV: E=Sophos;i="4.95,735,1384300800"; d="scan'208,217";a="3620024"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 28 Jan 2014 09:46:42 +0000
Received: from [10.61.90.206] (ams3-vpn-dhcp6863.cisco.com [10.61.90.206]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0S9kfvr010479; Tue, 28 Jan 2014 09:46:41 GMT
Message-ID: <52E77C81.8020803@cisco.com>
Date: Tue, 28 Jan 2014 10:46:41 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, ietf@ietf.org, Andrew Yourtchenko <ayourtch@cisco.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com>
In-Reply-To: <52E6F676.9020104@cisco.com>
Content-Type: multipart/alternative; boundary="------------090702060303090502090908"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 09:46:51 -0000

This is a multi-part message in MIME format.
--------------090702060303090502090908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Let me reply to myself: I forgot an important point, which might be 
useful if people start discussing AD sponsoring of this document, 
without actually having read it.

Let me stress the first sentence of the Introduction section.

    The section 4 of [RFC7012] defines the IPFIX Information Elements in
    the range of 1-127 to be compatible with the NetFlow version 9
    fields, as specified in the "Cisco Systems NetFlow Services Export
    Version 9" [RFC3954].

So this draft is clearly linked to the work in IPFIX RFC 7012 (IPFIX 
information model) and must follow the RFC 7013 rules (Guidelines for 
Authors and Reviewers of IPFIX Information Elements), therefore would 
benefit from more reviews.

It's probably not too clear from the abstract, and should be improved.

OLD:

    This document describes some additional Information Elements of Cisco
    Systems, Inc. that are not listed in RFC3954

NEW:
    This document describes some additional IPFIX Information Elements in
    the range of 1-127, which is the range compatible with field types used
    by NetFlow version 9 inRFC3954  <http://tools.ietf.org/html/rfc3954>, as specified in the IPFIX Information Model
    RFC 7012.
  
Regards, Benoit (an as author)


> Adrian,
>
> Not an answer to the process question, but some background information 
> on this draft.
> This draft, which is now 3 years old, has been evolving with the IPFIX 
> standardization.
> For example, looking at 
> http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt, 
> you can see the interaction with the IPFIX WG document 
> ietf-ipfix-data-link-layer-monitoring: now that
> ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the 
> draft has been simplified, and some IPFIX Information Elements in the 
> range 1-127 became deprecated.
> This explains why the draft has been presented and reviewed multiple 
> times in the IPFIX WG, and also why it would benefit from a wider 
> review than the independent stream.
>
> Regards, Benoit (as draft author)
>
>
>> Hi,
>>
>> I have a process question on this last call which is not clear from 
>> the last
>> call text.
>>
>> Are we being asked to consider whether publication of this document 
>> is useful,
>> or are we being asked for IETF consensus on the *content* of the 
>> document?
>>
>> It seems from the document that the content is descriptive of something
>> implemented by a single vendor. I applaud putting that information 
>> into the
>> public domain, but I don't understand the meaning of IETF consensus 
>> with respect
>> to this document.
>>
>> Thanks,
>> Adrian
>>
>>> -----Original Message-----
>>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On 
>>> Behalf Of The
>>> IESG
>>> Sent: 21 January 2014 12:33
>>> To: IETF-Announce
>>> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco 
>>> Specific
>>> Information Elements reused in IPFIX) to Informational RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to 
>>> consider
>>> the following document:
>>> - 'Cisco Specific Information Elements reused in IPFIX'
>>>    <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments 
>>> may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>     This document describes some additional Information Elements of 
>>> Cisco
>>>     Systems, Inc. that are not listed in RFC3954.
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>
>> .
>>
>
> .
>


--------------090702060303090502090908
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Let me reply to myself: I forgot an
      important point, which might be useful if people start discussing
      AD sponsoring of this document, without actually having read it.<br>
      <br>
      Let me stress the first sentence of the Introduction section.<br>
      <pre>   The section 4 of [RFC7012] defines the IPFIX Information Elements in
   the range of 1-127 to be compatible with the NetFlow version 9
   fields, as specified in the "Cisco Systems NetFlow Services Export
   Version 9" [RFC3954]. </pre>
      So this draft is clearly linked to the work in IPFIX RFC 7012
      (IPFIX information model) and must follow the RFC 7013 rules
      (Guidelines for Authors and Reviewers of IPFIX Information
      Elements), therefore would benefit from more reviews.<br>
      <br>
      It's probably not too clear from the abstract, and should be
      improved.<br>
      <br>
      OLD:<br>
      <pre>   This document describes some additional Information Elements of Cisco
   Systems, Inc. that are not listed in RFC3954

NEW:
   This document describes some additional IPFIX Information Elements in 
   the range of 1-127, which is the range compatible with field types used 
   by NetFlow version 9 in <a href="http://tools.ietf.org/html/rfc3954" title="&quot;Cisco Systems NetFlow Services Export Version 9&quot;">RFC3954</a>, as specified in the IPFIX Information Model
   RFC 7012.
&nbsp;
Regards, Benoit (an as author)
</pre>
      <br>
    </div>
    <blockquote cite="mid:52E6F676.9020104@cisco.com" type="cite">Adrian,
      <br>
      <br>
      Not an answer to the process question, but some background
      information on this draft.
      <br>
      This draft, which is now 3 years old, has been evolving with the
      IPFIX standardization.
      <br>
      For example, looking at
      <a class="moz-txt-link-freetext" href="http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt">http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt</a>,
      you can see the interaction with the IPFIX WG document
      ietf-ipfix-data-link-layer-monitoring: now that
      <br>
      ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue,
      the draft has been simplified, and some IPFIX Information Elements
      in the range 1-127 became deprecated.
      <br>
      This explains why the draft has been presented and reviewed
      multiple times in the IPFIX WG, and also why it would benefit from
      a wider review than the independent stream.
      <br>
      <br>
      Regards, Benoit (as draft author)
      <br>
      <br>
      <br>
      <blockquote type="cite">Hi,
        <br>
        <br>
        I have a process question on this last call which is not clear
        from the last
        <br>
        call text.
        <br>
        <br>
        Are we being asked to consider whether publication of this
        document is useful,
        <br>
        or are we being asked for IETF consensus on the *content* of the
        document?
        <br>
        <br>
        It seems from the document that the content is descriptive of
        something
        <br>
        implemented by a single vendor. I applaud putting that
        information into the
        <br>
        public domain, but I don't understand the meaning of IETF
        consensus with respect
        <br>
        to this document.
        <br>
        <br>
        Thanks,
        <br>
        Adrian
        <br>
        <br>
        <blockquote type="cite">-----Original Message-----
          <br>
          From: IETF-Announce [<a class="moz-txt-link-freetext" href="mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounces@ietf.org</a>] On
          Behalf Of The
          <br>
          IESG
          <br>
          Sent: 21 January 2014 12:33
          <br>
          To: IETF-Announce
          <br>
          Subject: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt;
          (Cisco Specific
          <br>
          Information Elements reused in IPFIX) to Informational RFC
          <br>
          <br>
          <br>
          The IESG has received a request from an individual submitter
          to consider
          <br>
          the following document:
          <br>
          - 'Cisco Specific Information Elements reused in IPFIX'
          <br>
          &nbsp;&nbsp; &lt;draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally,
          comments may be
          <br>
          sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain
          the
          <br>
          beginning of the Subject line to allow automated sorting.
          <br>
          <br>
          Abstract
          <br>
          <br>
          <br>
          &nbsp;&nbsp;&nbsp; This document describes some additional Information
          Elements of Cisco
          <br>
          &nbsp;&nbsp;&nbsp; Systems, Inc. that are not listed in RFC3954.
          <br>
          <br>
          <br>
          <br>
          <br>
          The file can be obtained via
          <br>
          <a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/">http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/</a>
          <br>
          <br>
          IESG discussion can be tracked via
          <br>
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/">http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/</a>
          <br>
          <br>
          <br>
          No IPR declarations have been submitted directly on this I-D.
          <br>
        </blockquote>
        <br>
        .
        <br>
        <br>
      </blockquote>
      <br>
      .
      <br>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------090702060303090502090908--

From adrian@olddog.co.uk  Tue Jan 28 03:17:25 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF881A0348 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 03:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.217
X-Spam-Level: 
X-Spam-Status: No, score=0.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AqSoLd7IxAzx for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 03:17:23 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7D37D1A01D2 for <ietf@ietf.org>; Tue, 28 Jan 2014 03:17:23 -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 s0SBHHEb012395; Tue, 28 Jan 2014 11:17:17 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SBHCdP012373 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jan 2014 11:17:15 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Benoit Claise'" <bclaise@cisco.com>, <ietf@ietf.org>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com>
In-Reply-To: <52E6F676.9020104@cisco.com>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Date: Tue, 28 Jan 2014 11:17:10 -0000
Message-ID: <033501cf1c1a$80089fd0$8019df70$@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: AQFerF+1MVKpbR9CNhjCMYsURGW24gGF8EmEAuvAeambV0zN8A==
Content-Language: en-gb
X-TM-AS-MML: No
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 11:17:25 -0000

Thanks Benoit,

And I am not much concerned with the process here as with the meaning of the
IETF last call.

Reading the document, I don't understand what would happen if I found something
that I thought should be different. It looks to me that this is a record of what
has been implemented and deployed. That is fine and good, but I don't see what
my review is supposed to give as input.

It seems to me that either this is an IETF document describing some IPFIX
widgets (drop all the Cisco stuff, get the WG to agree they want the feature,
and let the IETF do a proper review probably as Standards Track) or it is a
record of what Cisco did (continue to publish it, but don't ask for review of
the content).

Joel points out that it is valuable to check that the publication of this
document doesn't break anything else. I think that is a fine answer to my
question and would ask that, in future, when the scope or intent of a last call
is limited, that limit be explicitly called out in the last call so that no-one
waste review effort. I also think that when the RFC is published it should not
use boilerplate that says the document is a product of the IETF if the IETF did
not have the opportunity to edit the technical content. It would be better to
say that the IETF had consensus to publish the document but that it is not a
product of the IETF.

Cheers,
Adrian

> -----Original Message-----
> From: Benoit Claise [mailto:bclaise@cisco.com]
> Sent: 28 January 2014 00:15
> To: adrian@olddog.co.uk; ietf@ietf.org
> Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
> Information Elements reused in IPFIX) to Informational RFC
> 
> Adrian,
> 
> Not an answer to the process question, but some background information
> on this draft.
> This draft, which is now 3 years old, has been evolving with the IPFIX
> standardization.
> For example, looking at
> http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt,
> you can see the interaction with the IPFIX WG document
> ietf-ipfix-data-link-layer-monitoring: now that
> ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the
> draft has been simplified, and some IPFIX Information Elements in the
> range 1-127 became deprecated.
> This explains why the draft has been presented and reviewed multiple
> times in the IPFIX WG, and also why it would benefit from a wider review
> than the independent stream.
> 
> Regards, Benoit (as draft author)
> 
> 
> > Hi,
> >
> > I have a process question on this last call which is not clear from the last
> > call text.
> >
> > Are we being asked to consider whether publication of this document is
useful,
> > or are we being asked for IETF consensus on the *content* of the document?
> >
> > It seems from the document that the content is descriptive of something
> > implemented by a single vendor. I applaud putting that information into the
> > public domain, but I don't understand the meaning of IETF consensus with
> respect
> > to this document.
> >
> > Thanks,
> > Adrian
> >
> >> -----Original Message-----
> >> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
> The
> >> IESG
> >> Sent: 21 January 2014 12:33
> >> To: IETF-Announce
> >> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
> >> Information Elements reused in IPFIX) to Informational RFC
> >>
> >>
> >> The IESG has received a request from an individual submitter to consider
> >> the following document:
> >> - 'Cisco Specific Information Elements reused in IPFIX'
> >>    <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be
> >> sent to iesg@ietf.org instead. In either case, please retain the
> >> beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>
> >>     This document describes some additional Information Elements of Cisco
> >>     Systems, Inc. that are not listed in RFC3954.
> >>
> >>
> >>
> >>
> >> The file can be obtained via
> >> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
> >>
> >> IESG discussion can be tracked via
> >> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >
> > .
> >


From spencerdawkins.ietf@gmail.com  Tue Jan 28 04:58:18 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F071A039F for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 04:58:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c-nfymQ-_Snj for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 04:58:15 -0800 (PST)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 662C41A01EB for <ietf@ietf.org>; Tue, 28 Jan 2014 04:58:15 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id c11so293562lbj.3 for <ietf@ietf.org>; Tue, 28 Jan 2014 04:58:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5ffCyOuL2tTjzjYrpzQUsp3/ea32Ks9+Gh3eo7/cvvk=; b=l3AmjsUEF/kV4txSAAkBRBA3vxHMBSzDDJjjF4r4YJ/54K2I4Cd9/vIRjKVkfofhrb DV09sx27S0Zk2uUYNGmohbBe5cDe93C9dM6m+5HWndWiGX9ttq4mkkFc8U8kRYrfxv8/ qg8iajNO6pRX0nRCavTFBtOKaxHBtuPMiEh8wxZ3P2HfDeRHHYoXJ0vdh8IbGuoLztar CUT6qWFsgTVGx05ru9g+k/lC+3ZRq9yQvCxld6YOaAYgQDgXl9vl00Gxix6MR9afwifT qAyLmcNWI06ZLnaTaVOACqSVu2OVDA378BAxWJ46EBYfte+4ECS3Eqbz7Q56FrRqCrus zGZw==
MIME-Version: 1.0
X-Received: by 10.152.164.166 with SMTP id yr6mr913099lab.1.1390913892022; Tue, 28 Jan 2014 04:58:12 -0800 (PST)
Received: by 10.152.46.50 with HTTP; Tue, 28 Jan 2014 04:58:11 -0800 (PST)
In-Reply-To: <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
Date: Tue, 28 Jan 2014 06:58:11 -0600
Message-ID: <CAKKJt-e5CyrNfjtvySAKx_tnQWMZEg5buXU1H2Tech5g_Ay+Qw@mail.gmail.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=001a11349a02728b8904f1076027
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 12:58:18 -0000

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

Adrian,

Nicely said.

If we can give reviewers a clue about what we hope they are looking for,
we're more likely to get the results we hope for.

And being accurate about the review we asked for in the final document seems
helpful.

Spencer

On Tuesday, January 28, 2014, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Thanks Benoit,
>
> And I am not much concerned with the process here as with the meaning of
> the
> IETF last call.
>
> Reading the document, I don't understand what would happen if I found
> something
> that I thought should be different. It looks to me that this is a record
> of what
> has been implemented and deployed. That is fine and good, but I don't see
> what
> my review is supposed to give as input.
>
> It seems to me that either this is an IETF document describing some IPFIX
> widgets (drop all the Cisco stuff, get the WG to agree they want the
> feature,
> and let the IETF do a proper review probably as Standards Track) or it is a
> record of what Cisco did (continue to publish it, but don't ask for review
> of
> the content).
>
> Joel points out that it is valuable to check that the publication of this
> document doesn't break anything else. I think that is a fine answer to my
> question and would ask that, in future, when the scope or intent of a last
> call
> is limited, that limit be explicitly called out in the last call so that
> no-one
> waste review effort. I also think that when the RFC is published it should
> not
> use boilerplate that says the document is a product of the IETF if the
> IETF did
> not have the opportunity to edit the technical content. It would be better
> to
> say that the IETF had consensus to publish the document but that it is not
> a
> product of the IETF.
>
> Cheers,
> Adrian
>
> > -----Original Message-----
> > From: Benoit Claise [mailto:bclaise@cisco.com <javascript:;>]
> > Sent: 28 January 2014 00:15
> > To: adrian@olddog.co.uk <javascript:;>; ietf@ietf.org <javascript:;>
> > Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco
> Specific
> > Information Elements reused in IPFIX) to Informational RFC
> >
> > Adrian,
> >
> > Not an answer to the process question, but some background information
> > on this draft.
> > This draft, which is now 3 years old, has been evolving with the IPFIX
> > standardization.
> > For example, looking at
> > http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt,
> > you can see the interaction with the IPFIX WG document
> > ietf-ipfix-data-link-layer-monitoring: now that
> > ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the
> > draft has been simplified, and some IPFIX Information Elements in the
> > range 1-127 became deprecated.
> > This explains why the draft has been presented and reviewed multiple
> > times in the IPFIX WG, and also why it would benefit from a wider review
> > than the independent stream.
> >
> > Regards, Benoit (as draft author)
> >
> >
> > > Hi,
> > >
> > > I have a process question on this last call which is not clear from
> the last
> > > call text.
> > >
> > > Are we being asked to consider whether publication of this document is
> useful,
> > > or are we being asked for IETF consensus on the *content* of the
> document?
> > >
> > > It seems from the document that the content is descriptive of something
> > > implemented by a single vendor. I applaud putting that information
> into the
> > > public domain, but I don't understand the meaning of IETF consensus
> with
> > respect
> > > to this document.
> > >
> > > Thanks,
> > > Adrian
> > >
> > >> -----Original Message-----
> > >> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org<javascript:;>]
> On Behalf Of
> > The
> > >> IESG
> > >> Sent: 21 January 2014 12:33
> > >> To: IETF-Announce
> > >> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco
> Specific
> > >> Information Elements reused in IPFIX) to Informational RFC
> > >>
> > >>
> > >> The IESG has received a request from an individual submitter to
> consider
> > >> the following document:
> > >> - 'Cisco Specific Information Elements reused in IPFIX'
> > >>    <draft-yourtchenko-cisco-ies-09.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 <javascript:;> mailing lists by 2014-02-18.
> Exceptionally, comments may be
> > >> sent to iesg@ietf.org <javascript:;> instead. In either case, please
> retain the
> > >> beginning of the Subject line to allow automated sorting.
> > >>
> > >> Abstract
> > >>
> > >>
> > >>     This document describes some additional Information Elements of
> Cisco
> > >>     Systems, Inc. that are not listed in RFC3954.
> > >>
> > >>
> > >>
> > >>
> > >> The file can be obtained via
> > >> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
> > >>
> > >> IESG discussion can be tracked via
> > >> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> > >>
> > >>
> > >> No IPR declarations have been submitted directly on this I-D.
> > >
> > > .
> > >
>
>

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

Adrian,=A0<div><br></div><div>Nicely said.</div><div><br></div><div>If we c=
an give reviewers a clue about what we hope they are looking for, we&#39;re=
 more likely to get the results we hope for.</div><div><br></div><div>And b=
eing accurate about the review we asked for in the final document=A0<span><=
/span>seems helpful.</div>
<div><br></div><div>Spencer<br><br>On Tuesday, January 28, 2014, Adrian Far=
rel &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
Thanks Benoit,<br>
<br>
And I am not much concerned with the process here as with the meaning of th=
e<br>
IETF last call.<br>
<br>
Reading the document, I don&#39;t understand what would happen if I found s=
omething<br>
that I thought should be different. It looks to me that this is a record of=
 what<br>
has been implemented and deployed. That is fine and good, but I don&#39;t s=
ee what<br>
my review is supposed to give as input.<br>
<br>
It seems to me that either this is an IETF document describing some IPFIX<b=
r>
widgets (drop all the Cisco stuff, get the WG to agree they want the featur=
e,<br>
and let the IETF do a proper review probably as Standards Track) or it is a=
<br>
record of what Cisco did (continue to publish it, but don&#39;t ask for rev=
iew of<br>
the content).<br>
<br>
Joel points out that it is valuable to check that the publication of this<b=
r>
document doesn&#39;t break anything else. I think that is a fine answer to =
my<br>
question and would ask that, in future, when the scope or intent of a last =
call<br>
is limited, that limit be explicitly called out in the last call so that no=
-one<br>
waste review effort. I also think that when the RFC is published it should =
not<br>
use boilerplate that says the document is a product of the IETF if the IETF=
 did<br>
not have the opportunity to edit the technical content. It would be better =
to<br>
say that the IETF had consensus to publish the document but that it is not =
a<br>
product of the IETF.<br>
<br>
Cheers,<br>
Adrian<br>
<br>
&gt; -----Original Message-----<br>
&gt; From: Benoit Claise [mailto:<a href=3D"javascript:;" onclick=3D"_e(eve=
nt, &#39;cvml&#39;, &#39;bclaise@cisco.com&#39;)">bclaise@cisco.com</a>]<br=
>
&gt; Sent: 28 January 2014 00:15<br>
&gt; To: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39=
;adrian@olddog.co.uk&#39;)">adrian@olddog.co.uk</a>; <a href=3D"javascript:=
;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;ietf@ietf.org&#39;)">ietf@ietf=
.org</a><br>

&gt; Subject: Re: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Ci=
sco Specific<br>
&gt; Information Elements reused in IPFIX) to Informational RFC<br>
&gt;<br>
&gt; Adrian,<br>
&gt;<br>
&gt; Not an answer to the process question, but some background information=
<br>
&gt; on this draft.<br>
&gt; This draft, which is now 3 years old, has been evolving with the IPFIX=
<br>
&gt; standardization.<br>
&gt; For example, looking at<br>
&gt; <a href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisc=
o-ies-09.txt" target=3D"_blank">http://tools.ietf.org/rfcdiff?url2=3Ddraft-=
yourtchenko-cisco-ies-09.txt</a>,<br>
&gt; you can see the interaction with the IPFIX WG document<br>
&gt; ietf-ipfix-data-link-layer-monitoring: now that<br>
&gt; ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the<=
br>
&gt; draft has been simplified, and some IPFIX Information Elements in the<=
br>
&gt; range 1-127 became deprecated.<br>
&gt; This explains why the draft has been presented and reviewed multiple<b=
r>
&gt; times in the IPFIX WG, and also why it would benefit from a wider revi=
ew<br>
&gt; than the independent stream.<br>
&gt;<br>
&gt; Regards, Benoit (as draft author)<br>
&gt;<br>
&gt;<br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; I have a process question on this last call which is not clear fr=
om the last<br>
&gt; &gt; call text.<br>
&gt; &gt;<br>
&gt; &gt; Are we being asked to consider whether publication of this docume=
nt is<br>
useful,<br>
&gt; &gt; or are we being asked for IETF consensus on the *content* of the =
document?<br>
&gt; &gt;<br>
&gt; &gt; It seems from the document that the content is descriptive of som=
ething<br>
&gt; &gt; implemented by a single vendor. I applaud putting that informatio=
n into the<br>
&gt; &gt; public domain, but I don&#39;t understand the meaning of IETF con=
sensus with<br>
&gt; respect<br>
&gt; &gt; to this document.<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt; Adrian<br>
&gt; &gt;<br>
&gt; &gt;&gt; -----Original Message-----<br>
&gt; &gt;&gt; From: IETF-Announce [mailto:<a href=3D"javascript:;" onclick=
=3D"_e(event, &#39;cvml&#39;, &#39;ietf-announce-bounces@ietf.org&#39;)">ie=
tf-announce-bounces@ietf.org</a>] On Behalf Of<br>
&gt; The<br>
&gt; &gt;&gt; IESG<br>
&gt; &gt;&gt; Sent: 21 January 2014 12:33<br>
&gt; &gt;&gt; To: IETF-Announce<br>
&gt; &gt;&gt; Subject: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt=
; (Cisco Specific<br>
&gt; &gt;&gt; Information Elements reused in IPFIX) to Informational RFC<br=
>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The IESG has received a request from an individual submitter =
to consider<br>
&gt; &gt;&gt; the following document:<br>
&gt; &gt;&gt; - &#39;Cisco Specific Information Elements reused in IPFIX&#3=
9;<br>
&gt; &gt;&gt; =A0 =A0&lt;draft-yourtchenko-cisco-ies-09.txt&gt; as Informat=
ional RFC<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The IESG plans to make a decision in the next few weeks, and =
solicits<br>
&gt; &gt;&gt; final comments on this action. Please send substantive commen=
ts to the<br>
&gt; &gt;&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;,=
 &#39;ietf@ietf.org&#39;)">ietf@ietf.org</a> mailing lists by 2014-02-18. E=
xceptionally, comments may be<br>
&gt; &gt;&gt; sent to <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cv=
ml&#39;, &#39;iesg@ietf.org&#39;)">iesg@ietf.org</a> instead. In either cas=
e, please retain the<br>
&gt; &gt;&gt; beginning of the Subject line to allow automated sorting.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Abstract<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 This document describes some additional Information E=
lements of Cisco<br>
&gt; &gt;&gt; =A0 =A0 Systems, Inc. that are not listed in RFC3954.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The file can be obtained via<br>
&gt; &gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-=
cisco-ies/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-yourtch=
enko-cisco-ies/</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; IESG discussion can be tracked via<br>
&gt; &gt;&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-=
cisco-ies/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-=
yourtchenko-cisco-ies/ballot/</a><br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; No IPR declarations have been submitted directly on this I-D.=
<br>
&gt; &gt;<br>
&gt; &gt; .<br>
&gt; &gt;<br>
<br>
</blockquote></div>

--001a11349a02728b8904f1076027--

From john-ietf@jck.com  Tue Jan 28 06:11:10 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9D0C1A0416 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 06:11:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vR2oJzDga_Lx for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 06:11:07 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 835041A03FE for <ietf@ietf.org>; Tue, 28 Jan 2014 06:11:07 -0800 (PST)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W89NS-000Jdt-7b; Tue, 28 Jan 2014 09:10:58 -0500
X-Vipre-Scanned: 03239894002C31032399E1-TDI
Date: Tue, 28 Jan 2014 09:10:57 -0500
From: John C Klensin <john-ietf@jck.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, adrian@olddog.co.uk
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Message-ID: <487CEC5B5E391C4726DD6AC5@[192.168.1.128]>
In-Reply-To: <CAKKJt-e5CyrNfjtvySAKx_tnQWMZEg5buXU1H2Tech5g_Ay+Qw@mail.gmail.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk> <CAKKJt-e5CyrNfjtvySAKx_tnQWMZEg5buXU1H2Tech5g_Ay+Qw@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, rfc-ise@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 14:11:10 -0000

--On Tuesday, 28 January, 2014 06:58 -0600 Spencer Dawkins at
IETF <spencerdawkins.ietf@gmail.com> wrote:

>...
> If we can give reviewers a clue about what we hope they are
> looking for, we're more likely to get the results we hope for.

Of course, one of the long-time characteristics of the
Independent Submission system is the ability to get
tightly-focused reviews from people with relevant experience.

Is there any chance that, rather than continuing this discussion
on the IETF list to the point of general exhaustion, the IESG
and ISE (and maybe some RSAG members) could sit down in London
and produce some general guidelines about how to allocate such
categories as...

(1) Corporate or similar specs, proposed to be documented in the
RFC Series for the information of the community.

(2) Documents considered in a WG that fail to get traction or
that are overtaken by events but that don't get strong
opposition within the WG.

(3) Documents considered by a WG that don't get approval, either
because the WG finds series defects or because it selected a
different path or set of alternatives.

(4) Documents clearly appropriate for IETF work but for which no
existing WG is available and appropriate and for which there is
little enough controversy that setting up a WG is not worth the
trouble.

(5) Documents that are not relevant to the Internet going
forward but for which publication appears to have significant
historical value.

(6) Documents that may be important or useful for the network
but that do not directly relate to the sorts of work the IETF is
doing (or has the institutional competence to do).

(7) Documents that affect IETF process but for which there is no
consensus for forming a WG or processing in other ways.

(8) Documents whose purpose is to create an IANA registration
under "specification required" provisions of some existing
protocol.

There is probably a longer list, and some of those categories
overlap.   I'd be opposed to firm rules because, as we usually
discover about such things, there are always edge cases and
judgment calls.  But, if agreement could be reached on some
general guidelines and maybe even presented in a plenary to
inform the community and get comments, it would probably be a
big help to all concerned.

   john



From fluffy@cisco.com  Tue Jan 28 06:40:48 2014
Return-Path: <fluffy@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 069941A0420 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 06:40:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ag-zWuYSeUzC for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 06:40:46 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 8935D1A0418 for <ietf@ietf.org>; Tue, 28 Jan 2014 06:40:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=387; q=dns/txt; s=iport; t=1390920044; x=1392129644; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=fA0WZ4dMLDxq0QnHtkNiZGCTL3tpN+OdTJV8xIxI+sM=; b=PoFgpQM2FfiCzxDesLgh1e7yCxi5F+MA55/1TDWcgf/Q1srM9LYTHmAL 9Gi7WbbIGQnSxnfqU0BT6XLkMod2OPHqwcK8pe/NfHn96Zi8ZqE84oWVw iYDtG/YsuNAWwdBUGw6StjImXiYTLNEzvKs2gEPSIvlja98a6Wao9Ardt o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAIrA51KtJXHA/2dsb2JhbABagwyBDrxYgQ8WdIIlAQEBAwE6PwULAgEINhAyJQIEDgWHfQjJaxeOTDMHgySBFAEDmCiSH4MtgWgkHg
X-IronPort-AV: E=Sophos;i="4.95,736,1384300800"; d="scan'208";a="300227353"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-3.cisco.com with ESMTP; 28 Jan 2014 14:40:43 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s0SEeh4T012501 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 28 Jan 2014 14:40:43 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.76]) by xhc-rcd-x04.cisco.com ([::1]) with mapi id 14.03.0123.003; Tue, 28 Jan 2014 08:40:43 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Problem with new Note Well 
Thread-Topic: Problem with new Note Well 
Thread-Index: AQHPG3tHOdcS5a/no0eQRXpC/QFQ0JqaJwyAgAB0ZwA=
Date: Tue, 28 Jan 2014 14:40:42 +0000
Message-ID: <4DB1E54E-371F-47EE-90E7-F0D09D874921@cisco.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <31F38883-AA9F-420F-877F-394C283A779F@piuha.net>
In-Reply-To: <31F38883-AA9F-420F-877F-394C283A779F@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4ADA924EF51B4D41B6DFC6778D1BEF42@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 14:40:48 -0000

On Jan 28, 2014, at 12:44 AM, Jari Arkko <jari.arkko@piuha.net> wrote:

> For your information, as a temporary measure we have pulled back the chan=
ge and the web site (registration etc) should now display the old note well=
 text.
>=20
> Jari
>=20

Thank you - I just registered. And I appreciate the IESG deciding to go bac=
k and have a second look at the Note Well.=20



From curtis@ipv6.occnc.com  Mon Jan 27 17:00:58 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70E9E1A037E; Mon, 27 Jan 2014 17:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a5mtqxYZ2gB0; Mon, 27 Jan 2014 17:00:56 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 8E8391A0377; Mon, 27 Jan 2014 17:00:56 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0S10jhO097154; Mon, 27 Jan 2014 20:00:45 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401280100.s0S10jhO097154@maildrop2.v6ds.occnc.com>
To: Joe Touch <touch@isi.edu>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 27 Jan 2014 10:53:09 -0800." <52E6AB15.2080907@isi.edu>
Date: Mon, 27 Jan 2014 20:00:45 -0500
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:00 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, "curtis@ipv6.occnc.com" <curtis@ipv6.occnc.com>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 28 Jan 2014 01:00:58 -0000

In message <52E6AB15.2080907@isi.edu>
Joe Touch writes:
 
> On 1/27/2014 10:48 AM, joel jaeggli wrote:
> > On 1/27/14, 8:48 AM, Joe Touch wrote:
> >> Those same mechanisms have provided hardware checksum support for a very long time.
> >
> > The new header and the payload are actually in different parts of the
> > forwarding complex until they hit the output queue, you can't checksum
> > data you don't have.
>  
> You can (and some do) the checksum component parts when things go into
> memory; the partial sums can be added as the parts are combined in the
> output queue.
>  
> I appreciate that we're all taking about what might be done, but the
> reality is that there are many 'transparent TCP proxies' that have to
> do this, so there's clearly a solution, and it clearly runs fast
> enough.
>  
> Joe


Joe,

Chips that did 4 x 10 Gb/s are old stuff now but in their day they
pushed silicon limites.  Chips now do N x 100 Gb/s.  Stewart is
describing how these chips (both the prior generation and current) are
architected and you are going back to some idea that there is a common
memory where this all resides and its just a matter of looking at it.
This is not software on a general purpose processor.

If a queue forms, the headers are in SRAM and the body of the packet
is off chip in DRAM.  There isn't enough memory bandwidth to pull the
packet back until its time to send it out.  At that point the header
and body are joined but the header processing has been completed long
ago.

If there is not much of a queue the packet may go into SRAM cache for
the buffer DRAM and go right out of that SRAM.

If there is no queue at all cut-through can happen.  The header gets
transmitted before the entire packet arrives at the input of the
chip.  (And if FCS fails a runt with bad FCS goes out).

At the very least this can't work if cut-through is used to reduce
latency.  When the two are joined, about the only processing is in the
MAC, its mostly loading a shift register and serializing but it also
does the FCS and sticks that *at the end*.  The MAC is quite
inflexible as it is mostly silicon gates designed to do some minimal
processing for a layer-2 such as Ethernet or GFP/OTN.

Think for a moment what N x 100 Gb/s means.  For small packets 150
Mpps per interface with Ethernet overhead (large overhead).  That is
20 clock cycles per packet for a 3 GHz clock rate.  Divide that by N.
This has to be done in specialized hardware and if you also think
about the memory bandwidth needed, you need very wide and very fast
DRAM and get one write when the packet arrives and one read before it
leaves and even then have to play tricks in the SRAM cache like
concatonating short packets going out the same queue.

BTW - "transparent TCP proxies" don't need to look at the payload for
the purpose of updating a checksum.  Whenever a header modification is
made you only need to know the old checksum, the old information and
the new information replacing it.  That is why IP checksum
modification can be done quickly.  Typically only TTL changes.  These
are also running at least a decimal order of magnitude or two slower.

Curtis

From curtis@ipv6.occnc.com  Mon Jan 27 17:29:24 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E7F1A0345; Mon, 27 Jan 2014 17:29:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BMkI_-i-Yuax; Mon, 27 Jan 2014 17:29:21 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC941A00A7; Mon, 27 Jan 2014 17:29:21 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0S1TGY5099912; Mon, 27 Jan 2014 20:29:16 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401280129.s0S1TGY5099912@maildrop2.v6ds.occnc.com>
To: Joe Touch <touch@isi.edu>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 27 Jan 2014 11:24:34 -0800." <52E6B272.4030703@isi.edu>
Date: Mon, 27 Jan 2014 20:29:16 -0500
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:01 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 28 Jan 2014 01:29:24 -0000

In message <52E6B272.4030703@isi.edu>
Joe Touch writes:
 
> On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
> > Yes Joe, routers could ahve been built to do those calcualtions at that
> > performance scale.
> > There are however two major problems:
> >
> > 1) That is not how routers are built.
> > 2) The target performance scale is rather higher.
> >
> > So could someone build an ASIC to do what you want?
>  
> Has. It's already part of nearly every DMA ASIC in a network interface
> already.

There is no DMA ASIC in these designs.  There is no shared memory to
DMA from.  A router is not a specialized PC.

At any one point in time the best DMA ASICs run at a fraction of the
speed of forwarding ASICs of that same era.  Some forwarding ASICs
through parallelism or pipelining (or both) can forward a packet in
under ten clock ticks of the ASIC.  [The best forwarding chips today
are technically not ASICs but custom silicon though they are still
often called forwarding ASICs.]

BTW - the PCIe FCS is at the end of the transmission not the front so
the DMA ASIC doesn't have to read memory twice, the first time to
compute a checksum to put at the front.

>  > Probably.  Is there
> > any reason in the world to expect operators to pay the significant extra
> > cost for such?Not that I can see.
>  
> We're talking about a ring of full adders, the specs for which are
> given in an RFC that's 18 years old, and that is already implemented
> in nearly every host interface, including 10Gps NICs.
>  
> And we're talking about "routers", many variants of which operate at
> very high speeds and transparently proxy TCP already. So this is a
> solved problem.

See prior email.  They don't need to look at the payload to modify IP
or TCP headers and then update the checksum.

> > And even if we could and they would, that is not the world into which we
> > are deploying these tunnels.
>  
> We're back to "that's not what they do now", at least in some devices.
>  
> Well, they don't use MPLS in UDP (since no spec exists), so clearly if
> they're limited to doing what they already do, this is an exercise in
> futility.
>  
> Joe

You seem to be missing the point that MPLS over UDP is not considered
a good solution going forward on which to base the design of new
hardware, but rather an interim solution to accomodate old hardware
that doesn't load split MPLS traffic.

In any case, two passes, one to compute a checksum and put it on the
front, would increase latency.  If anything UDP-Heavy with an FCS at
the end would be used, even though two FCS is considered bad form.

Curtis


> > Yours,
> > Joel
> >
> > On 1/27/14 1:53 PM, Joe Touch wrote:
> >>
> >>
> >> On 1/27/2014 10:48 AM, joel jaeggli wrote:
> >>> On 1/27/14, 8:48 AM, Joe Touch wrote:
> >>>> Those same mechanisms have provided hardware checksum support for a
> >>>> very long time.
> >>>
> >>> The new header and the payload are actually in different parts of the
> >>> forwarding complex until they hit the output queue, you can't checksum
> >>> data you don't have.
> >>
> >> You can (and some do) the checksum component parts when things go into
> >> memory; the partial sums can be added as the parts are combined in the
> >> output queue.
> >>
> >> I appreciate that we're all taking about what might be done, but the
> >> reality is that there are many 'transparent TCP proxies' that have to do
> >> this, so there's clearly a solution, and it clearly runs fast enough.
> >>
> >> Joe

From curtis@ipv6.occnc.com  Mon Jan 27 17:56:28 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1631A00BE; Mon, 27 Jan 2014 17:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8M7-DlnmQ_Z5; Mon, 27 Jan 2014 17:56:26 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 60D351A008F; Mon, 27 Jan 2014 17:56:26 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0S1uKJA000384; Mon, 27 Jan 2014 20:56:20 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401280156.s0S1uKJA000384@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 27 Jan 2014 23:17:24 +0000." <290E20B455C66743BE178C5C84F1240847E63346F6@EXMB01CMS.surrey.ac.uk>
Date: Mon, 27 Jan 2014 20:56:20 -0500
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:01 -0800
Cc: mpls@ietf.org, stbryant@cisco.com, ietf@ietf.org, curtis@ipv6.occnc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 28 Jan 2014 01:56:28 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346F6@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
 
> ...and UDP Lite just covering the L3 and L4 headers, but not the full
>  payload a la UDP, is still possible when the full payload is not
>  visible.
>  
> Lloyd Wood
> http://about.me/lloydwood


... but doesn't solve the problem of ECMP using old routers so
UDP-Lite is a non-starter.

Curtis


> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Joe Touch [touch@isi.edu]
> Sent: 27 January 2014 16:48
> To: stbryant@cisco.com
> Cc: mpls@ietf.org; IETF discussion list; curtis@ipv6.occnc.com
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> Those same mechanisms have provided hardware checksum support for a very long time.
>  
> Joe
>  
> > On Jan 27, 2014, at 8:40 AM, Stewart Bryant <stbryant@cisco.com> wrote:
> >
> >> On 24/01/2014 19:15, Joe Touch wrote:
> >>
> >>> This eliminates the "expands the reach of MPLS argument".
> >>>
> >>> First UDP checksums:
> >>>
> >>>   The UDP checksum is at the beginning of the payload.  Please see
> >>> http://www.ietf.org/mail-archive/web/mpls/current/msg11279.html
> >>>   This makes filling in a new UDP checksum infeasible on most high end
> >>>   hardware.
> >>
> >> That argument would make sense if most hardware wasn't store-and-forward on a per-packet basis.
> > They may be store and forward, but most of the high end designs
> > use multiple grades of memory putting the packet in "slow memory"
> > and providing a snapshot of the header in "fast memory" to the
> > forwarder. Thus although the whole packet is in the system, it
> > it is not accessible to the engine that would need to calculate the
> > c/s.
> >
> > Stewart


From curtis@ipv6.occnc.com  Mon Jan 27 18:23:51 2014
Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7620C1A03C9 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 18:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nV3iIlNUz8XS for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 18:23:48 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 557711A008F for <ietf@ietf.org>; Mon, 27 Jan 2014 18:23:48 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0S2NgVH000747; Mon, 27 Jan 2014 21:23:42 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401280223.s0S2NgVH000747@maildrop2.v6ds.occnc.com>
To: l.wood@surrey.ac.uk
From: Curtis Villamizar <curtis@ipv6.occnc.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
In-reply-to: Your message of "Mon, 27 Jan 2014 23:18:56 +0000." <290E20B455C66743BE178C5C84F1240847E63346F7@EXMB01CMS.surrey.ac.uk>
Date: Mon, 27 Jan 2014 21:23:42 -0500
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:01 -0800
Cc: mpls@ietf.org, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.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, 28 Jan 2014 02:23:51 -0000

In message <290E20B455C66743BE178C5C84F1240847E63346F7@EXMB01CMS.surrey.ac.uk>
l.wood@surrey.ac.uk writes:
> 
> "ASICs can't do IPv6 in hardware! IPv6 can only be done with slow
> software forwarding! We're stuck with v4!"
>  
> I think we've been here before.
>  
> Lloyd Wood
> http://about.me/lloydwood


At what point does this discussion no longer have any relevance at all
to draft-ietf-mpls-in-udp?

The draft is going to say SHOULD wrt UDP checksums.  If you have an
issue with the wording of the draft, please comment on the draft.

Curtis


> ________________________________________
> From: mpls [mpls-bounces@ietf.org] On Behalf Of Joe Touch [touch@isi.edu]
> Sent: 27 January 2014 19:24
> To: Joel M. Halpern; joel jaeggli; stbryant@cisco.com
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>  
> On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
> > Yes Joe, routers could ahve been built to do those calcualtions at that
> > performance scale.
> > There are however two major problems:
> >
> > 1) That is not how routers are built.
> > 2) The target performance scale is rather higher.
> >
> > So could someone build an ASIC to do what you want?
>  
> Has. It's already part of nearly every DMA ASIC in a network interface
> already.
>  
>  > Probably.  Is there
> > any reason in the world to expect operators to pay the significant extra
> > cost for such?Not that I can see.
>  
> We're talking about a ring of full adders, the specs for which are given
> in an RFC that's 18 years old, and that is already implemented in nearly
> every host interface, including 10Gps NICs.
>  
> And we're talking about "routers", many variants of which operate at
> very high speeds and transparently proxy TCP already. So this is a
> solved problem.
>  
> > And even if we could and they would, that is not the world into which we
> > are deploying these tunnels.
>  
> We're back to "that's not what they do now", at least in some devices.
>  
> Well, they don't use MPLS in UDP (since no spec exists), so clearly if
> they're limited to doing what they already do, this is an exercise in
> futility.
>  
> Joe
>  
> >
> > Yours,
> > Joel
> >
> > On 1/27/14 1:53 PM, Joe Touch wrote:
> >>
> >>
> >> On 1/27/2014 10:48 AM, joel jaeggli wrote:
> >>> On 1/27/14, 8:48 AM, Joe Touch wrote:
> >>>> Those same mechanisms have provided hardware checksum support for a
> >>>> very long time.
> >>>
> >>> The new header and the payload are actually in different parts of the
> >>> forwarding complex until they hit the output queue, you can't checksum
> >>> data you don't have.
> >>
> >> You can (and some do) the checksum component parts when things go into
> >> memory; the partial sums can be added as the parts are combined in the
> >> output queue.
> >>
> >> I appreciate that we're all taking about what might be done, but the
> >> reality is that there are many 'transparent TCP proxies' that have to do
> >> this, so there's clearly a solution, and it clearly runs fast enough.
> >>
> >> Joe

From edc@google.com  Mon Jan 27 16:26:38 2014
Return-Path: <edc@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 215851A0264 for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level: 
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rl3hhBfN7ffs for <ietf@ietfa.amsl.com>; Mon, 27 Jan 2014 16:26:35 -0800 (PST)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0B1BF1A008F for <ietf@ietf.org>; Mon, 27 Jan 2014 16:26:34 -0800 (PST)
Received: by mail-wg0-f45.google.com with SMTP id n12so6644669wgh.12 for <ietf@ietf.org>; Mon, 27 Jan 2014 16:26:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IOHvugfO/57La6Ot5vPqMuy1EOm7psOq5pGD5jVMrz8=; b=EFspGDVbZpSMlCKBvFKvfUPmCIZZgKOdMt/T+/i3dw+BrP4M93uGVETf+QQuEyyV3C fZfhg1tdHyGcH0FlQwmAIsyLBQJOYQQhVJfklvldqp4tqvM4/4mw5NXmn5xOxTU/tOHl q8+ovqWxPy/r1+0IkfkjKsuzcx+fzI58hopa74t4CAFRfNjivlKLT17LB4rnIYO/9pSP B1XEtnjolZ+Nw0pIreZDndoXLh563f8WCcgLfHQ9hKt8mhHJ+rn4Q9OQerLJfz6K7r17 8YXftZtvcvEFHoB7bp+r0ygLoFEDvMtv4HZUR/to0BjBbbhp42hw5wHD/EDt5yazr3M3 AP5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=IOHvugfO/57La6Ot5vPqMuy1EOm7psOq5pGD5jVMrz8=; b=nIBDkhqoUhMos2hGN5uyv5CN+VBj8RLcv6EcyVwpHZSdCsEDSDFaLs30HvMYLxTg/+ K8P0FAxReIa1ATpHGzI0XG7hmtgSWM8BVy6HLTr1z0fs1wLqeQB+7/AxEcI8QU0kphla md5xFqroDx/qLryGPZcDsRn1CN2tatqefCtXxW93kEs1hWFctw9LPAorvaPNv+aWkdc8 i/bhEpCM90RwePmS/eqTRuqQAm7T2nv6sAm7trzWFzy5FqLoB265AoEsuaZ5SOSiK+Xt zWwwT72IyD4zXQEnwBvpBrHG6SgRCn8APHRa8axLF8XJA5SJyi0JsoDJlW8u/MBu+gnW HmSw==
X-Gm-Message-State: ALoCoQlaFDlGCO1c/5/OfISRkFbUnfKVEidBqBP92mpWP4HSRxsfHdJJ/UQ8u8AGI1rZ7xlA+OipAD5OdKaoGaVniouGvB3zJYS0KnhNP+/AE0TbPyz3R4AGWXUwfeaDd2iBaOmekjqGjJoheDWFMz3vw50JlNlfdkyEyM2/iVPzXZauyJLT0VyIZVmWqS52/YSmiPeD4dK5
X-Received: by 10.180.165.174 with SMTP id yz14mr9953139wib.34.1390868792119;  Mon, 27 Jan 2014 16:26:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.23.3 with HTTP; Mon, 27 Jan 2014 16:25:51 -0800 (PST)
In-Reply-To: <52E6B272.4030703@isi.edu>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <52E6B272.4030703@isi.edu>
From: Edward Crabbe <edc@google.com>
Date: Mon, 27 Jan 2014 16:25:51 -0800
Message-ID: <CACKN6JF9DMNTftj8TwrYDW1ASFQbO2ronX2LDj6eYDa4bjTLdA@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=90e6ba30982448c77504f0fce00f
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:39 -0800
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 00:26:38 -0000

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

I assume we're talking about the chksum issue here.  If this is the case,
please go fix IPv6 by adding a hop by hop checksum extension header and
getting it implemented by vendors.  ^_^

If by 'this' we mean stateful congestion control of multiple terabits of
tunnel traffic, then it is *most certainly* not a solved problem, and
definitely not something I'm interested in paying for.

cheers,
   -ed


On Mon, Jan 27, 2014 at 11:24 AM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
>
>> Yes Joe, routers could ahve been built to do those calcualtions at that
>> performance scale.
>> There are however two major problems:
>>
>> 1) That is not how routers are built.
>> 2) The target performance scale is rather higher.
>>
>> So could someone build an ASIC to do what you want?
>>
>
> Has. It's already part of nearly every DMA ASIC in a network interface
> already.
>
>
> > Probably.  Is there
>
>> any reason in the world to expect operators to pay the significant extra
>> cost for such?Not that I can see.
>>
>
> We're talking about a ring of full adders, the specs for which are given
> in an RFC that's 18 years old, and that is already implemented in nearly
> every host interface, including 10Gps NICs.
>
> And we're talking about "routers", many variants of which operate at very
> high speeds and transparently proxy TCP already. So this is a solved
> problem.
>
>
>  And even if we could and they would, that is not the world into which we
>> are deploying these tunnels.
>>
>
> We're back to "that's not what they do now", at least in some devices.
>
> Well, they don't use MPLS in UDP (since no spec exists), so clearly if
> they're limited to doing what they already do, this is an exercise in
> futility.
>
> Joe
>
>
>
>> Yours,
>> Joel
>>
>> On 1/27/14 1:53 PM, Joe Touch wrote:
>>
>>>
>>>
>>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>>
>>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>>
>>>>> Those same mechanisms have provided hardware checksum support for a
>>>>> very long time.
>>>>>
>>>>
>>>> The new header and the payload are actually in different parts of the
>>>> forwarding complex until they hit the output queue, you can't checksum
>>>> data you don't have.
>>>>
>>>
>>> You can (and some do) the checksum component parts when things go into
>>> memory; the partial sums can be added as the parts are combined in the
>>> output queue.
>>>
>>> I appreciate that we're all taking about what might be done, but the
>>> reality is that there are many 'transparent TCP proxies' that have to do
>>> this, so there's clearly a solution, and it clearly runs fast enough.
>>>
>>> Joe
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>>
>>>  _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>

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

<div dir=3D"ltr">I assume we&#39;re talking about the chksum issue here. =
=A0If this is the case, please go fix IPv6 by adding a hop by hop checksum =
extension header and getting it implemented by vendors. =A0^_^<div><br></di=
v><div>

If by &#39;this&#39; we mean stateful congestion control of multiple terabi=
ts of tunnel traffic, then it is *most certainly* not a solved problem, and=
 definitely not something I&#39;m interested in paying for. =A0</div><div>

<br></div><div>cheers,</div><div>=A0 =A0-ed</div></div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Mon, Jan 27, 2014 at 11:24 AM,=
 Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.edu" target=3D=
"_blank">touch@isi.edu</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>
<br>
On 1/27/2014 11:19 AM, Joel M. Halpern wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yes Joe, routers could ahve been built to do those calcualtions at that<br>
performance scale.<br>
There are however two major problems:<br>
<br>
1) That is not how routers are built.<br>
2) The target performance scale is rather higher.<br>
<br>
So could someone build an ASIC to do what you want?<br>
</blockquote>
<br></div>
Has. It&#39;s already part of nearly every DMA ASIC in a network interface =
already.<div class=3D"im"><br>
<br>
&gt; Probably. =A0Is there<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
any reason in the world to expect operators to pay the significant extra<br=
>
cost for such?Not that I can see.<br>
</blockquote>
<br></div>
We&#39;re talking about a ring of full adders, the specs for which are give=
n in an RFC that&#39;s 18 years old, and that is already implemented in nea=
rly every host interface, including 10Gps NICs.<br>
<br>
And we&#39;re talking about &quot;routers&quot;, many variants of which ope=
rate at very high speeds and transparently proxy TCP already. So this is a =
solved problem.<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">
And even if we could and they would, that is not the world into which we<br=
>
are deploying these tunnels.<br>
</blockquote>
<br></div>
We&#39;re back to &quot;that&#39;s not what they do now&quot;, at least in =
some devices.<br>
<br>
Well, they don&#39;t use MPLS in UDP (since no spec exists), so clearly if =
they&#39;re limited to doing what they already do, this is an exercise in f=
utility.<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Joe</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Yours,<br>
Joel<br>
<br>
On 1/27/14 1:53 PM, Joe Touch 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 1/27/2014 10:48 AM, joel jaeggli wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 1/27/14, 8:48 AM, Joe Touch wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Those same mechanisms have provided hardware checksum support for a<br>
very long time.<br>
</blockquote>
<br>
The new header and the payload are actually in different parts of the<br>
forwarding complex until they hit the output queue, you can&#39;t checksum<=
br>
data you don&#39;t have.<br>
</blockquote>
<br>
You can (and some do) the checksum component parts when things go into<br>
memory; the partial sums can be added as the parts are combined in the<br>
output queue.<br>
<br>
I appreciate that we&#39;re all taking about what might be done, but the<br=
>
reality is that there are many &#39;transparent TCP proxies&#39; that have =
to do<br>
this, so there&#39;s clearly a solution, and it clearly runs fast enough.<b=
r>
<br>
Joe<br>
______________________________<u></u>_________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/mpls</a><br>
<br>
</blockquote></blockquote>
______________________________<u></u>_________________<br>
mpls mailing list<br>
<a href=3D"mailto:mpls@ietf.org" target=3D"_blank">mpls@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mpls" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/mpls</a><br>
</div></div></blockquote></div><br></div>

--90e6ba30982448c77504f0fce00f--

From geoff.mulligan@nist.gov  Mon Jan 27 09:01:02 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B07E1A0353; Mon, 27 Jan 2014 09:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WJUGh93uLETU; Mon, 27 Jan 2014 09:01:00 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id 37E461A0345; Mon, 27 Jan 2014 09:01:00 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB053.namprd09.prod.outlook.com (10.255.211.146) with Microsoft SMTP Server (TLS) id 15.0.859.15; Mon, 27 Jan 2014 17:00:56 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) with mapi id 15.00.0859.020; Mon, 27 Jan 2014 17:00:56 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7p
Date: Mon, 27 Jan 2014 17:00:55 +0000
Message-ID: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>,<CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
In-Reply-To: <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(377454003)(54356001)(76482001)(53806001)(74662001)(74502001)(47446002)(87266001)(31966008)(46102001)(2656002)(51856001)(93516002)(50986001)(47976001)(85306002)(81686001)(76576001)(87936001)(76786001)(76796001)(69226001)(81816001)(77096001)(4396001)(47736001)(33646001)(49866001)(83322001)(19580405001)(56816005)(81342001)(19580395003)(93136001)(65816001)(74706001)(80022001)(92566001)(74316001)(81542001)(80976001)(90146001)(86362001)(54316002)(56776001)(85852003)(83072002)(59766001)(77982001)(74876001)(63696002)(79102001)(74366001)(66066001)(94316002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB053; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; MLV:nspm; InfoNoRecordsMX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:24:01 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:01:02 -0000

So because I know of IPR that someone else has and is not disclosing and be=
cause I cannot legally disclose it - I can't continue to participate in the=
 discussion doesn't seem right.  I'm not the holder of the IPR that isn't b=
eing disclosed, but I'm penalized.=0A=
=0A=
Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Cyber Physical Systems | =
301.975.6283=0A=
=0A=
________________________________________=0A=
From: Jari Arkko <jari.arkko@piuha.net>=0A=
Sent: Monday, January 27, 2014 11:02 AM=0A=
To: Mulligan, Geoff=0A=
Cc: IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: Third party disclosures and NDAs (Re: Problem with new Note Well )=
=0A=
=0A=
Starting a separate thread, because this is not related to the original com=
plaint about inaccurate new note well text.=0A=
=0A=
>   Maybe this is a potential rat-hole - I don't know - but what if:=0A=
>     -  I'm working as a consultant and attending the IETF representing my=
self=0A=
>     -  I know of IPR in someone else's contribution=0A=
>     -  I'm participating in the discussion=0A=
>     -  I'm under an NDA with that company that covers their IPR=0A=
=0A=
That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simult=
aneously follow two incompatible sets of rules. If you end up in that situa=
tion and can't convince parties to disclose, maybe "participating in the di=
scussion" has to give. Of course this is a specific example of things that =
can happen in people's lives in other ways, too. Two consulting contracts t=
hat have incompatible requirements. Board position and a job that creates a=
 conflict interest for you to be in the board. And so on.=0A=
=0A=
Jari=0A=
=0A=

From geoff.mulligan@nist.gov  Mon Jan 27 09:04:03 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB59B1A0378; Mon, 27 Jan 2014 09:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u7E1z1GQHznQ; Mon, 27 Jan 2014 09:04:01 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0188.outbound.protection.outlook.com [207.46.163.188]) by ietfa.amsl.com (Postfix) with ESMTP id 587121A0363; Mon, 27 Jan 2014 09:04:01 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB055.namprd09.prod.outlook.com (10.255.211.152) with Microsoft SMTP Server (TLS) id 15.0.859.15; Mon, 27 Jan 2014 17:03:58 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.155]) with mapi id 15.00.0859.020; Mon, 27 Jan 2014 17:03:58 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Scott Brim <scott.brim@gmail.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYvJQAgAAPTFk=
Date: Mon, 27 Jan 2014 17:03:57 +0000
Message-ID: <b416b4c6ea2248d393f90fe0860d4165@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net>, <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
In-Reply-To: <CAPv4CP8dGLrPfsq_Jrz7mFk2eCuxs58gQ1xGqR-BeT=ZFoWhmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 0104247462
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(51704005)(199002)(189002)(24454002)(79102001)(59766001)(77982001)(46102001)(80976001)(81542001)(4396001)(74316001)(81342001)(56776001)(83322001)(19580405001)(53806001)(47976001)(47736001)(49866001)(50986001)(19580395003)(54316002)(85852003)(83072002)(74876001)(81686001)(2656002)(81816001)(94316002)(90146001)(56816005)(87936001)(74706001)(87266001)(92566001)(80022001)(47446002)(85306002)(74366001)(66066001)(65816001)(31966008)(74662001)(74502001)(86362001)(93516002)(33646001)(63696002)(77096001)(54356001)(76482001)(51856001)(76796001)(76786001)(69226001)(76576001)(93136001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB055; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; MLV:nspm; InfoNoRecordsA:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:23:59 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 17:04:04 -0000

I do want to be clear - I am not currently facing this situation and I have=
n't yet faced this situation, but I fear that as a consultant (in the futur=
e when this current job ends) I may face this.  I want to understand my opt=
ions as I would like to continue my participation and affiliation with the =
IETF.=0A=
=0A=
   Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Cyber Physical Systems | =
301.975.6283=0A=
    =0A=
________________________________________=0A=
From: Scott Brim <scott.brim@gmail.com>=0A=
Sent: Monday, January 27, 2014 11:06 AM=0A=
To: Jari Arkko=0A=
Cc: Mulligan, Geoff; IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note We=
ll )=0A=
=0A=
On Mon, Jan 27, 2014 at 11:02 AM, Jari Arkko <jari.arkko@piuha.net> wrote:=
=0A=
> Starting a separate thread, because this is not related to the original c=
omplaint about inaccurate new note well text.=0A=
>=0A=
>>   Maybe this is a potential rat-hole - I don't know - but what if:=0A=
>>     -  I'm working as a consultant and attending the IETF representing m=
yself=0A=
>>     -  I know of IPR in someone else's contribution=0A=
>>     -  I'm participating in the discussion=0A=
>>     -  I'm under an NDA with that company that covers their IPR=0A=
>=0A=
> That is a rat-^H^H^H^Hhard problem. Something has to give. You can't simu=
ltaneously follow two incompatible sets of rules. If you end up in that sit=
uation and can't convince parties to disclose, maybe "participating in the =
discussion" has to give. Of course this is a specific example of things tha=
t can happen in people's lives in other ways, too. Two consulting contracts=
 that have incompatible requirements. Board position and a job that creates=
 a conflict interest for you to be in the board. And so on.=0A=
>=0A=
> Jari=0A=
=0A=
Right. IMHO if you haven't anticipated this situation you would do=0A=
best to shut up until you talk to your lawyers. However, thankfully,=0A=
you have learned that you need to anticipate the problem and you can=0A=
talk to them before the problem arises.=0A=
=0A=
Scott=0A=

From mark.tinka@seacom.mu  Mon Jan 27 11:30:23 2014
Return-Path: <mark.tinka@seacom.mu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 619821A007C; Mon, 27 Jan 2014 11:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.589
X-Spam-Level: 
X-Spam-Status: No, score=-1.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_MISMATCH_COM=0.311] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yZ3l3WXINhEd; Mon, 27 Jan 2014 11:30:21 -0800 (PST)
Received: from the-host.seacom.mu (ge-0.ln-01-mba.ke.seacomnet.com [41.87.100.230]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC111A001E; Mon, 27 Jan 2014 11:30:20 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=the-host.localnet) by the-host.seacom.mu with esmtp (Exim 4.80.1) (envelope-from <mark.tinka@seacom.mu>) id 1W7rsc-0008LP-8h; Mon, 27 Jan 2014 21:29:58 +0200
From: Mark Tinka <mark.tinka@seacom.mu>
Organization: SEACOM
To: mpls@ietf.org, curtis@ipv6.occnc.com
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Date: Mon, 27 Jan 2014 21:29:54 +0200
User-Agent: KMail/1.13.6 (Linux/2.6.37.6-24-desktop; KDE/4.6.0; i686; ; )
References: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
In-Reply-To: <201401252047.s0PKlmgS048899@maildrop2.v6ds.occnc.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1477944.eXu6q19VvR"; protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201401272129.55230.mark.tinka@seacom.mu>
X-Mailman-Approved-At: Tue, 28 Jan 2014 08:24:19 -0800
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mark.tinka@seacom.mu
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jan 2014 19:30:23 -0000

--nextPart1477944.eXu6q19VvR
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

On Saturday, January 25, 2014 10:47:48 PM Curtis Villamizar=20
wrote:

> Reality check time.
>=20
> To get the PW over MPLS drafts past the TSV AD there is a
> SHOULD regarding congestion control.
>=20
> AFAIK: No service providers ask for it.  No one
> implements it.  If they did implement it no one would
> deploy it.
>=20
> PW over MPLS is generally carrying relatively low volumes
> of high priority traffic.  The TC bits (MPLS flavor of
> Diffserv DSCP) are used to enforce the higher priority.=20
> If congestion occurs other traffic on that
> infrastructure (typically plain old Internet) sees loss.
>  That is intended.  This is the reality of how PW over
> MPLS is deployed.
>=20
> Anyone who knows of implementation or deployment of
> congestion control for PW over MPLS can correct me.

And this is what I mentioned several weeks ago. As=20
operators, we police traffic on ingress and egress (some=20
operators shape on egress, but the result is the same), and=20
this is how we control admission to the network.

I have never used intrinsic congestion mechanisms in=20
protocols (outside of lab fun-time when I'm really bored),=20
and don't know anyone that has either. Of course, the risk=20
is that router/switch vendors have all sorts of=20
implementation as regards policing/shaping; but I can say=20
that in the past 7x years or so (and especially in the past=20
year for switches), this is reasonably mature, and no vendor=20
worth their salt is shipping product that can't police or=20
shape properly.

Just one point to make, not all traffic being carried over=20
MPLS is "high priority". Some of it really isn't, and is=20
treated on a best-effort basis. But, this is all specific to=20
operators and their customers. General traffic admission=20
rules still apply all the same.

Personally, if there was congestion mechanisms proposed as=20
part of the MPLS-in-UDP spec., I would never run them as an=20
operator. I'd rely on policing at the edge, as usual.

Cheers,

Mark.

--nextPart1477944.eXu6q19VvR
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQIcBAABAgAGBQJS5rOzAAoJEGcZuYTeKm+GQfkP/2V/hyPrib+UGVANMxoYiXSh
XHEzlRDf34NLcNZO8C3xqysiL7pb3HJR6a3HMPXwfHu0oDFoUwTQJ/PcSRWLyfrH
MXiQIwsZMLczNo1472uVuybibevLVNCQf5wu3HMHVKSXLfb1ABLN11/VibINJiZO
qKeEHu5YW048nZuaYekLDwHehye8whaM3ABdIvZ/mrEATbnIaOZ4ghEfs2lMl4Qb
1aD6DjLN1C/giozplbljqiyspk/T0oXeC9J/7M1u6m6u82cNeG3elrjKl013ABOy
DlypgIW0dedK9mPzOkfURhhgN98/HIVpukWS07OOAdyA15f4uuRV5KkokKk+V4pY
zvMtDI5S8aE85G5GLTrEGxSjGxAY6EgG3HjTbqrKrLlk2Ba/fZWMC04A65MgKiaO
LMACgUl+Omab91UnSW74PPUGNV3LBEzrg2VVdTYLqyfprm6NvHSu/K+9rNWvDCKM
FWH3kqFKIh76q2tC11jF1g8hof+9G6o2oLtINhLhGIL6PrxyxwU3WGZqCx1g1EbH
MY6KX9u5/qNxbQoubmd5cxCb1/HrqT3ehOS3bEsVwwnW1YAzv+kRQ8Ri7sv26KCB
u2bTbQTaX6pmy5Yd3ea/TbEkZjKrHP+TscdvVL+aAOsu35pF7+CFjo+JvCzoNOov
p4ojTcfKlzo2d4KO0PVZ
=JywG
-----END PGP SIGNATURE-----

--nextPart1477944.eXu6q19VvR--

From touch@isi.edu  Tue Jan 28 08:41:57 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D19A1A02EA; Tue, 28 Jan 2014 08:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GWO1aLhAmlxH; Tue, 28 Jan 2014 08:41:55 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0A61A02D5; Tue, 28 Jan 2014 08:41:55 -0800 (PST)
Received: from [192.168.1.91] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s0SGecLE029899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 28 Jan 2014 08:40:41 -0800 (PST)
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=iso-8859-1
From: Joe Touch <touch@isi.edu>
In-Reply-To: <CACKN6JF9DMNTftj8TwrYDW1ASFQbO2ronX2LDj6eYDa4bjTLdA@mail.gmail.com>
Date: Tue, 28 Jan 2014 08:40:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB36D802-970E-4C49-A006-B90DD522D9FD@isi.edu>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <52E6B272.4030703@isi.edu> <CACKN6JF9DMNTftj8TwrYDW1ASFQbO2ronX2LDj6eYDa4bjTLdA@mail.gmail.com>
To: Edward Crabbe <edc@google.com>
X-Mailer: Apple Mail (2.1827)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:41:57 -0000

On Jan 27, 2014, at 4:25 PM, Edward Crabbe <edc@google.com> wrote:

> I assume we're talking about the chksum issue here.  If this is the =
case, please go fix IPv6 by adding a hop by hop checksum extension =
header and getting it implemented by vendors.  ^_^

Please don't use UDP as a network layer.

See how easy that works?

> If by 'this' we mean stateful congestion control of multiple terabits =
of tunnel traffic, then it is *most certainly* not a solved problem, and =
definitely not something I'm interested in paying for. =20

Oh, nobody wants to pay for anything, including (and especially) =
following standards. Fortunately, the IETF isn't an extension of an =
industrial company's marketing department (or isn't yet, I should say).

Joe


>=20
> cheers,
>    -ed
>=20
>=20
> On Mon, Jan 27, 2014 at 11:24 AM, Joe Touch <touch@isi.edu> wrote:
>=20
>=20
> On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
> Yes Joe, routers could ahve been built to do those calcualtions at =
that
> performance scale.
> There are however two major problems:
>=20
> 1) That is not how routers are built.
> 2) The target performance scale is rather higher.
>=20
> So could someone build an ASIC to do what you want?
>=20
> Has. It's already part of nearly every DMA ASIC in a network interface =
already.
>=20
>=20
> > Probably.  Is there
> any reason in the world to expect operators to pay the significant =
extra
> cost for such?Not that I can see.
>=20
> We're talking about a ring of full adders, the specs for which are =
given in an RFC that's 18 years old, and that is already implemented in =
nearly every host interface, including 10Gps NICs.
>=20
> And we're talking about "routers", many variants of which operate at =
very high speeds and transparently proxy TCP already. So this is a =
solved problem.
>=20
>=20
> And even if we could and they would, that is not the world into which =
we
> are deploying these tunnels.
>=20
> We're back to "that's not what they do now", at least in some devices.
>=20
> Well, they don't use MPLS in UDP (since no spec exists), so clearly if =
they're limited to doing what they already do, this is an exercise in =
futility.
>=20
> Joe
>=20
>=20
>=20
> Yours,
> Joel
>=20
> On 1/27/14 1:53 PM, Joe Touch wrote:
>=20
>=20
> On 1/27/2014 10:48 AM, joel jaeggli wrote:
> On 1/27/14, 8:48 AM, Joe Touch wrote:
> Those same mechanisms have provided hardware checksum support for a
> very long time.
>=20
> The new header and the payload are actually in different parts of the
> forwarding complex until they hit the output queue, you can't checksum
> data you don't have.
>=20
> You can (and some do) the checksum component parts when things go into
> memory; the partial sums can be added as the parts are combined in the
> output queue.
>=20
> I appreciate that we're all taking about what might be done, but the
> reality is that there are many 'transparent TCP proxies' that have to =
do
> this, so there's clearly a solution, and it clearly runs fast enough.
>=20
> Joe
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>=20


From touch@isi.edu  Tue Jan 28 08:50:54 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708C51A017D; Tue, 28 Jan 2014 08:50:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rP67viUTlQW; Tue, 28 Jan 2014 08:50:53 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 185851A0146; Tue, 28 Jan 2014 08:50:53 -0800 (PST)
Received: from [192.168.1.91] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s0SGo3c5002940 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 28 Jan 2014 08:50:07 -0800 (PST)
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <201401280100.s0S10jhO097154@maildrop2.v6ds.occnc.com>
Date: Tue, 28 Jan 2014 08:49:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <16B434AA-C151-490D-98C2-DE052F464640@isi.edu>
References: <201401280100.s0S10jhO097154@maildrop2.v6ds.occnc.com>
To: curtis@ipv6.occnc.com
X-Mailer: Apple Mail (2.1827)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:50:54 -0000

On Jan 27, 2014, at 5:00 PM, Curtis Villamizar <curtis@ipv6.occnc.com> =
wrote:

>=20
> In message <52E6AB15.2080907@isi.edu>
> Joe Touch writes:
>=20
>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>> Those same mechanisms have provided hardware checksum support for a =
very long time.
>>>=20
>>> The new header and the payload are actually in different parts of =
the
>>> forwarding complex until they hit the output queue, you can't =
checksum
>>> data you don't have.
>>=20
>> You can (and some do) the checksum component parts when things go =
into
>> memory; the partial sums can be added as the parts are combined in =
the
>> output queue.
>>=20
>> I appreciate that we're all taking about what might be done, but the
>> reality is that there are many 'transparent TCP proxies' that have to
>> do this, so there's clearly a solution, and it clearly runs fast
>> enough.
>>=20
>> Joe
>=20
>=20
> Joe,
>=20
> Chips that did 4 x 10 Gb/s are old stuff now but in their day they
> pushed silicon limites.  Chips now do N x 100 Gb/s.

Yes, and it's 18 years later.=20

> Stewart is
> describing how these chips (both the prior generation and current) are
> architected and you are going back to some idea that there is a common
> memory where this all resides and its just a matter of looking at it.
> This is not software on a general purpose processor.

I never said software; I said that the checksum can be computed as the =
data moves (which is how we did it in 1996).

> If a queue forms, the headers are in SRAM and the body of the packet
> is off chip in DRAM.  There isn't enough memory bandwidth to pull the
> packet back until its time to send it out.  At that point the header
> and body are joined but the header processing has been completed long
> ago.

At some point the two come back together, at which point the partial =
sums of the header and body can be combined and inserted in the header.

...
> If there is no queue at all cut-through can happen.  The header gets
> transmitted before the entire packet arrives at the input of the
> chip.  (And if FCS fails a runt with bad FCS goes out).
>=20
> At the very least this can't work if cut-through is used to reduce
> latency.

Latency is a complex function of the bandwidth, propagation, coding, and =
processing delays, and there are very rare cases where cut-through =
reductions would impact E2E latency.=20

In those cases, there are other good reasons not to use UDP =
encapsulation.

> When the two are joined, about the only processing is in the
> MAC, its mostly loading a shift register and serializing but it also
> does the FCS and sticks that *at the end*.  The MAC is quite
> inflexible as it is mostly silicon gates designed to do some minimal
> processing for a layer-2 such as Ethernet or GFP/OTN.
>=20
> Think for a moment what N x 100 Gb/s means.  For small packets 150
> Mpps per interface with Ethernet overhead (large overhead).  That is
> 20 clock cycles per packet for a 3 GHz clock rate.  Divide that by N.
> This has to be done in specialized hardware

The hardware required is trivial, and easy to include in the same =
transfer mechanism used to move data (as it already has been for many =
years in network interfaces).

> BTW - "transparent TCP proxies" don't need to look at the payload for
> the purpose of updating a checksum.

That depends on whether the segments boundaries are preserved.

Joe=

From touch@isi.edu  Tue Jan 28 08:57:35 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 443961A0146; Tue, 28 Jan 2014 08:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRrmpIDEjhc4; Tue, 28 Jan 2014 08:57:34 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 00FE91A0240; Tue, 28 Jan 2014 08:57:33 -0800 (PST)
Received: from [192.168.1.91] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s0SGv15Q005298 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 28 Jan 2014 08:57:05 -0800 (PST)
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Content-Type: text/plain; charset=us-ascii
From: Joe Touch <touch@isi.edu>
In-Reply-To: <201401280129.s0S1TGY5099912@maildrop2.v6ds.occnc.com>
Date: Tue, 28 Jan 2014 08:57:00 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E4D36AF-2CB4-431C-BE01-8560BC46B0A3@isi.edu>
References: <201401280129.s0S1TGY5099912@maildrop2.v6ds.occnc.com>
To: curtis@ipv6.occnc.com
X-Mailer: Apple Mail (2.1827)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 16:57:35 -0000

On Jan 27, 2014, at 5:29 PM, Curtis Villamizar <curtis@ipv6.occnc.com> =
wrote:

>=20
> In message <52E6B272.4030703@isi.edu>
> Joe Touch writes:
>=20
>> On 1/27/2014 11:19 AM, Joel M. Halpern wrote:
>>> Yes Joe, routers could ahve been built to do those calcualtions at =
that
>>> performance scale.
>>> There are however two major problems:
>>>=20
>>> 1) That is not how routers are built.
>>> 2) The target performance scale is rather higher.
>>>=20
>>> So could someone build an ASIC to do what you want?
>>=20
>> Has. It's already part of nearly every DMA ASIC in a network =
interface
>> already.
>=20
> There is no DMA ASIC in these designs.  There is no shared memory to
> DMA from.  A router is not a specialized PC.

Agreed; the point was that it isn't an ASIC, but a very small function =
that can be included in any data transfer mechanism.

> BTW - the PCIe FCS is at the end of the transmission not the front so
> the DMA ASIC doesn't have to read memory twice, the first time to
> compute a checksum to put at the front.

Right, and until you modify UDP to have a trailer checksum, or use a =
different encapsulation that has one (e.g., via an IPv6 option), then =
you need to deal with the fact that the UDP checksum would require a =
store-and-forward delay.

IMO, if you don't like that, then use another encapsulation.

>>> Probably.  Is there
>>> any reason in the world to expect operators to pay the significant =
extra
>>> cost for such?Not that I can see.
>>=20
>> We're talking about a ring of full adders, the specs for which are
>> given in an RFC that's 18 years old, and that is already implemented
>> in nearly every host interface, including 10Gps NICs.
>>=20
>> And we're talking about "routers", many variants of which operate at
>> very high speeds and transparently proxy TCP already. So this is a
>> solved problem.
>=20
> See prior email.  They don't need to look at the payload to modify IP
> or TCP headers and then update the checksum.
>=20
>>> And even if we could and they would, that is not the world into =
which we
>>> are deploying these tunnels.
>>=20
>> We're back to "that's not what they do now", at least in some =
devices.
>>=20
>> Well, they don't use MPLS in UDP (since no spec exists), so clearly =
if
>> they're limited to doing what they already do, this is an exercise in
>> futility.
>>=20
>> Joe
>=20
> You seem to be missing the point that MPLS over UDP is not considered
> a good solution going forward on which to base the design of new
> hardware, but rather an interim solution to accomodate old hardware
> that doesn't load split MPLS traffic.

We live with interim solutions for decades.

I'd be OK with something that says that the UDP checksum SHOULD be used, =
but that legacy deployments MAY ignore it.

That solves what happens in the short term, but doesn't saddle us all =
with a poor solution if/when it persists.

> In any case, two passes, one to compute a checksum and put it on the
> front, would increase latency.

Again, latency is a complex issue, and store-and-forward delays inside =
routers is irrelevant for all but specialty deployments (stock trading =
esp.), and in those cases the use of additional encapsulation should be =
avoided anyway.

Joe

>  If anything UDP-Heavy with an FCS at
> the end would be used, even though two FCS is considered bad form.
>=20
> Curtis
>=20
>=20
>>> Yours,
>>> Joel
>>>=20
>>> On 1/27/14 1:53 PM, Joe Touch wrote:
>>>>=20
>>>>=20
>>>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>>>> Those same mechanisms have provided hardware checksum support for =
a
>>>>>> very long time.
>>>>>=20
>>>>> The new header and the payload are actually in different parts of =
the
>>>>> forwarding complex until they hit the output queue, you can't =
checksum
>>>>> data you don't have.
>>>>=20
>>>> You can (and some do) the checksum component parts when things go =
into
>>>> memory; the partial sums can be added as the parts are combined in =
the
>>>> output queue.
>>>>=20
>>>> I appreciate that we're all taking about what might be done, but =
the
>>>> reality is that there are many 'transparent TCP proxies' that have =
to do
>>>> this, so there's clearly a solution, and it clearly runs fast =
enough.
>>>>=20
>>>> Joe


From spencerdawkins.ietf@gmail.com  Tue Jan 28 09:00:50 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0AFC1A03B7 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 09:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n9wUrcVTNsRb for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 09:00:49 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 922401A029D for <ietf@ietf.org>; Tue, 28 Jan 2014 09:00:49 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i7so710756oag.36 for <ietf@ietf.org>; Tue, 28 Jan 2014 09:00:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=98b8cjMJhk7N89T4VnhX9qAK/e6NwncO+YLmdYjLxQ0=; b=AtVEiXEf+zqLT6qPugafVNaGOsXG7mzSbdmqO/sgOvyJWIRp5slAWNIdDGaZR6FNd/ hWk7JQqZXo/T/ykup2NupeEHL/PaaSBQrXuwVu1CYglXFdfVMf5YPpT5CEdyZmWN8yk9 HgfkJ0x/sY4ku8w8VOoggwgK6fh+LpdYQ/ADXN6NPDL6t2EvVtBTJo/0Xxif+iaousk1 jkcteipLJeVkYwV4kOwwhFvcU8AQxFLKGQkhmp7udMfIAGtbDBllRiPeHntCCxAOSP/S qBAUn4T4uFPGoPdt4juMqzVI+En2gu5kLUepS2CxlhJMb4AtW3Ab2CwjKkYJHjdqkgXC S/UQ==
X-Received: by 10.182.223.114 with SMTP id qt18mr1048403obc.61.1390928446930;  Tue, 28 Jan 2014 09:00:46 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id qe2sm26713579obc.1.2014.01.28.09.00.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 09:00:45 -0800 (PST)
Message-ID: <52E7E23B.9090205@gmail.com>
Date: Tue, 28 Jan 2014 11:00:43 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, adrian@olddog.co.uk
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk> <CAKKJt-e5CyrNfjtvySAKx_tnQWMZEg5buXU1H2Tech5g_Ay+Qw@mail.gmail.com> <487CEC5B5E391C4726DD6AC5@[192.168.1.128]>
In-Reply-To: <487CEC5B5E391C4726DD6AC5@[192.168.1.128]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, rfc-ise@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 17:00:51 -0000

On 01/28/2014 08:10 AM, John C Klensin wrote:
>
> --On Tuesday, 28 January, 2014 06:58 -0600 Spencer Dawkins at
> IETF <spencerdawkins.ietf@gmail.com> wrote:
>
>> ...
>> If we can give reviewers a clue about what we hope they are
>> looking for, we're more likely to get the results we hope for.
> Of course, one of the long-time characteristics of the
> Independent Submission system is the ability to get
> tightly-focused reviews from people with relevant experience.
>
> Is there any chance that, rather than continuing this discussion
> on the IETF list to the point of general exhaustion, the IESG
> and ISE (and maybe some RSAG members) could sit down in London
> and produce some general guidelines about how to allocate such
> categories as...

This is a very helpful suggestion.

Spencer

> (1) Corporate or similar specs, proposed to be documented in the
> RFC Series for the information of the community.
>
> (2) Documents considered in a WG that fail to get traction or
> that are overtaken by events but that don't get strong
> opposition within the WG.
>
> (3) Documents considered by a WG that don't get approval, either
> because the WG finds series defects or because it selected a
> different path or set of alternatives.
>
> (4) Documents clearly appropriate for IETF work but for which no
> existing WG is available and appropriate and for which there is
> little enough controversy that setting up a WG is not worth the
> trouble.
>
> (5) Documents that are not relevant to the Internet going
> forward but for which publication appears to have significant
> historical value.
>
> (6) Documents that may be important or useful for the network
> but that do not directly relate to the sorts of work the IETF is
> doing (or has the institutional competence to do).
>
> (7) Documents that affect IETF process but for which there is no
> consensus for forming a WG or processing in other ways.
>
> (8) Documents whose purpose is to create an IANA registration
> under "specification required" provisions of some existing
> protocol.
>
> There is probably a longer list, and some of those categories
> overlap.   I'd be opposed to firm rules because, as we usually
> discover about such things, there are always edge cases and
> judgment calls.  But, if agreement could be reached on some
> general guidelines and maybe even presented in a plenary to
> inform the community and get comments, it would probably be a
> big help to all concerned.
>
>     john
>
>


From chair@ietf.org  Tue Jan 28 09:21:40 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 415B01A0243; Tue, 28 Jan 2014 09:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cO8ueB-R-KsZ; Tue, 28 Jan 2014 09:21:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B52B41A0187; Tue, 28 Jan 2014 09:21:38 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Invitation to Participate in Mentoring Program
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140128172138.28200.99163.idtracker@ietfa.amsl.com>
Date: Tue, 28 Jan 2014 09:21:38 -0800
Cc: 89-1st-timers@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 17:21:40 -0000

All,

At IETF 89 we will once again offer the IETF Mentoring Program. The goal
of the IETF Mentoring Program is to match IETF participants who may be new
or otherwise in need of guidance with experienced IETF mentors. As a
mentoring participant, your mentor will personally introduce you to the
IETF community, help you find your way around the IETF & the meeting,
explain things, and introduce you to other attendees you might like to
meet. Basically, your mentor will be your personal buddy during the
meeting week, and possibly afterwards.

Unlike in the past, at IETF 89 we will accept requests for mentors from
anyone who wants one, regardless of how many meetings they have attended
previously. We cannot guarantee that every request will be honored, but we
will do our best.

If you wish to participate in the IETF Mentoring Program, you can follow
the sign-up procedures described in the program FAQ:

https://www.ietf.org/resources/mentoring-program.html

After you follow the sign-up procedure, we will introduce you to your
mentor by email prior to IETF 89, and invite you to meet up in person at
the IETF Meet & Greet event on Sunday afternoon in London. From there on,
you and your mentor decide on when and where to meet during the rest of
the week and afterwards.

You are of course free to withdraw from the program at any time and for
any reason, no questions asked, should a need arise. But I sincerely
believe the IETF Mentoring Program will be a great way for new
participants to get introduced to the IETF by an experienced participant
with matching interest.

Regards,
Jari Arkko
IETF Chair

From worley@shell01.TheWorld.com  Tue Jan 28 10:16:10 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAC7E1A026A for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 10:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5RueNULqk6g for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 10:16:09 -0800 (PST)
Received: from TheWorld.com (pcls5.std.com [192.74.137.145]) by ietfa.amsl.com (Postfix) with ESMTP id D2DB91A0230 for <ietf@ietf.org>; Tue, 28 Jan 2014 10:16:08 -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 s0SIF9E1021120; Tue, 28 Jan 2014 13:15: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 s0SICWxR3772471; Tue, 28 Jan 2014 13:12:32 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s0SICTXk3778564; Tue, 28 Jan 2014 13:12:29 -0500 (EST)
Date: Tue, 28 Jan 2014 13:12:29 -0500 (EST)
Message-Id: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
In-reply-to: <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> (geoff.mulligan@nist.gov)
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:16:11 -0000

> From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> 
> So because I know of IPR that someone else has and is not disclosing
> and because I cannot legally disclose it - I can't continue to
> participate in the discussion doesn't seem right.  I'm not the
> holder of the IPR that isn't being disclosed, but I'm penalized.

That is the rule (it seems).  It's hard on you, but the IETF seems to
hold to the principle "You can't participate if you know of
undisclosed IPR claims", presumably so the participant can't secretly
steer the solution to include or exclude the IPR.  It's a choice of
who gets inconvenienced, you or the IETF?

Indeed, if the IETF didn't have this rule, a company with undisclosed
IPR could hire consultants, put them under NDA, and have them advocate
at the IETF to include the IPR in standards.

Dale

From housley@vigilsec.com  Tue Jan 28 10:42:11 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91BE1A037F; Tue, 28 Jan 2014 10:42:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rKMEs1xcf3wV; Tue, 28 Jan 2014 10:42:08 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 346971A0374; Tue, 28 Jan 2014 10:42:08 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 2B4939A42BD; Tue, 28 Jan 2014 13:41:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id ubQrKM8ets0n; Tue, 28 Jan 2014 13:41:32 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DAD0C9A429F; Tue, 28 Jan 2014 13:41:32 -0500 (EST)
Subject: Appointments for ICANN Technical Liaison Group
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6E69571E-3BF4-4255-9D9C-ECC80CFA4B1A@iab.org>
Date: Tue, 28 Jan 2014 13:41:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA197A34-7053-43CA-B0A6-19D264769910@vigilsec.com>
References: <CE9467A6.1087%karine.perset@icann.org>	<EB54A1CD-5BDE-4FBE-930B-2B3103C32C81@shinkuro.com>	<D9112687-832E-4B3A-9C7C-BD722041A4C7@vigilsec.com>	<1FC796F8-5A1B-4930-BBF0-0C251A7B5355@shinkuro.com>	<6A1627AB-D488-4496-B091-D8CEE928902B@vigilsec.com> <29e4fce546af4ecab5c758d24d4e60ca@BY2PR03MB269.namprd03.prod.outlook.com> <527003E3.8020505@cisco.com> <9F7F6E84-3ECC-4129-B105-136153D30E3C@vigilsec.com> <5270065E.7010305@cisco.com> <9524AFE7-1DEB-488E-B9B5-A79C0F7DA13D@vigilsec.com> <5270117B.5050809@cisco.com> <CB78FE0E-184B-4FB5-AA8B-48D2FFA7549D@vigilsec.com> <52701441.2050601@cisco.com> <7E10A87A-4A1E-44A4-9785-8A7353AAE117@vigilsec.com> <5788665A-DED5-4FE5-9A3D-9AD53A472877@iab.org> <2ECBAB99-9FE4-42C9-BF73-229B6E2C54F6@viagenie.ca> <6E69571E-3BF4-4255-9D9C-ECC80CFA4B1A@iab.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:42:11 -0000

Dear Colleagues,

The IAB has selected Warren Kumari to serve a two-tear term on the ICANN =
TLG and selected Daniel Migault a one-tear term.  Thanks for your =
willingness to serve the community in this capacity.

The IAB thanks all of the candidates.  This was a difficult decision =
with so many strong candidates.

On behalf of the IAB,
Russ Housley
IAB Chair



> Dear Colleagues,
>=20
> The IAB recently requested nominations to the ICANN Technical
> Liaison Group (TLG).  We have a number of candidates, and we
> are soliciting comment from the community on these candidates.
>=20
> The following candidates have put their names forward:
>=20
>  Marc Blanchet <marc.blanchet@viagenie.ca>
>  David Conrad <drc@virtualized.org>
>  Alex Deacon <Alex_Deacon@mpaa.org>
>  Geoff Huston <gih902@gmail.com>
>  Stephen Kent <kent@bbn.com>
>  Peter Koch <pk@denic.de>
>  Warren Kumari <warren@kumari.net>
>  John Levine <johnl@taugh.com>
>  Daniel Migault <mglt.biz@gmail.com>
>  Hassan Zaheer <hassanZaheer@gmail.com>
>=20
> Please send your remarks in confidence about any or all candidates to
> iab-chair@iab.org and execd@iab.org.  We thank you in advance for
> your help.
>=20
> Best regards,
> Russ Housley
> IAB Chair
>=20
>=20
>=20
>> Dear Colleagues,
>>=20
>> The IAB (on behalf of the IETF) has been asked to supply two =
technical
>> experts to ICANN Technical Liaison Group (TLG).  The ICANN Bylaws
>> (Article XI-A, Section 2, Paragraph 6) asks the IETF, ITU-T, ETSI, =
and
>> W3C to each provide two technical experts.  The technical experts are
>> expected to be "familiar with the technical standards issues that are
>> relevant to ICANN's activities." These eight experts are expected to =
be
>> "available as necessary to determine, through an exchange of e-mail
>> messages, where to direct a technical question from ICANN when ICANN
>> does not ask a specific TLG organization directly.
>>=20
>> The ICANN bylaws can be found at
>> http://www.icann.org/en/about/governance/bylaws.
>>=20
>> The IAB is asking the community for volunteers to serve on the ICANN =
TLG.
>> If you are interested, please send a short e-mail to iab-chair at =
iab.org
>> with a copy to execd at iab.org with your motivation and information
>> concerning your familiarity with the IETF and ICANN as well as the =
other
>> standards organizations represented on the TLG.  The deadline for
>> volunteering is 17 Nov 2013.
>>=20
>> The IAB will select from the available candidates, taking into =
account
>> the familiarity with ICANN and the IETF, their roles, and the IETF
>> protocols.  While familiarity with ETSI, ITU-T, and W3C is also
>> desirable, it is not required.  The selected candidates will serve on
>> the ICANN TLG on personal title; however, the IAB will be looking for
>> candidates who have an understanding of the interests of the =
technical
>> community.
>>=20
>> The IAB will select one person for a one year term and select one =
person
>> for a two year term.
>>=20
>> The ICANN TLG is expected to meet in person at or around the three =
ICANN
>> meetings held each year.
>>=20
>> NOTE: ICANN does cover travel and hotel costs for a pre-determined =
number
>> of days at each of the ICANN meetings.
>>=20
>> If you are willing to be considered or would like to nominate someone
>> else for one of the TLG positions, please send an email to iab-chair =
at
>> iab.org and execd at iab.org by 17 Nov 2013.
>>=20
>> On behalf of the IAB,
>> Russ Housley
>> IAB Chair
>>=20
>=20


From ned+ietf@mauve.mrochek.com  Tue Jan 28 10:50:41 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A80D1A0263 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 10:50:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROwrqdAOMEyi for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 10:50:40 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2B40F1A035F for <ietf@ietf.org>; Tue, 28 Jan 2014 10:50:40 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3ONM07NOG003QK5@mauve.mrochek.com> for ietf@ietf.org; Tue, 28 Jan 2014 10:45:35 -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 <01P3NP4TEOIO0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 28 Jan 2014 10:45:28 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Date: Tue, 28 Jan 2014 10:31:36 -0800 (PST)
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-reply-to: "Your message dated Mon, 27 Jan 2014 17:00:55 +0000" <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
To: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 18:50:41 -0000

> So because I know of IPR that someone else has and is not disclosing and
> because I cannot legally disclose it - I can't continue to participate in the
> discussion doesn't seem right.  I'm not the holder of the IPR that isn't being
> disclosed, but I'm penalized.

As I have pointed out several times now, that's incorrect. Section 6.1.3 of
BCP 79 discusses "IPR of Others", and says:

   If a person has information about IPR that may Cover IETF
   Contributions, but the participant is not required to disclose
   because they do not meet the criteria in Section 6.6 (e.g., the IPR
   is owned by some other company), such person is encouraged to notify
   the IETF by sending an email message to ietf-ipr@ietf.org.  Such a
   notice should be sent as soon as reasonably possible after the person
   realizes the connection.

And the referenced section 6.6 says:

   6.6.  When is a Disclosure Required?

   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with
   respect to IPR that is owned directly or indirectly, by the
   individual or his/her employer or sponsor (if any) or that such
   persons otherwise have the right to license or assert.

Encouraged != required.

The wrinkle here - and why I think you're getting some odd answers to your
questions - is that you're not being clear about what role the "someone else"
you're talking about has in the IETF. If the "someone else" is not
participating in the IETF, then there's no problem, other than possibly your
own conscience.

If the "someone else" is participating while meeting the disclosure
requirements, then once again there's no problem since the disclosure has
already been done and there's no need for you to repeat it.

But if they are participating and not disclosing, then there's a big problem,
and in that case it may indeed suck to be you. My advice in such cases would be
to consult an attorney with substantive expertise in IP law as to what your
obligations are.

I do expect such cases to be quite rare though.


				Ned

From dwm@xpasc.com  Tue Jan 28 11:01:38 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 459651A03B7; Tue, 28 Jan 2014 11:01:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.23
X-Spam-Level: *
X-Spam-Status: No, score=1.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jv8rLtoWK_ZT; Tue, 28 Jan 2014 11:01:37 -0800 (PST)
Received: from c2w3p-2.abacamail.com (unknown [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 465671A0159; Tue, 28 Jan 2014 11:01:37 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 9C8A340876; Tue, 28 Jan 2014 19:01:25 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s0SJ1ORw005387; Tue, 28 Jan 2014 11:01:24 -0800
Date: Tue, 28 Jan 2014 11:01:24 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-Reply-To: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
Message-ID: <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: wgchairs@ietf.org, ietf@ietf.org, "Mulligan, Geoff" <geoff.mulligan@nist.gov>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 19:01:38 -0000

On Tue, 28 Jan 2014, Dale R. Worley wrote:

> > From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> >
> > So because I know of IPR that someone else has and is not disclosing
> > and because I cannot legally disclose it - I can't continue to
> > participate in the discussion doesn't seem right.  I'm not the
> > holder of the IPR that isn't being disclosed, but I'm penalized.
>
> That is the rule (it seems).  It's hard on you, but the IETF seems to
> hold to the principle "You can't participate if you know of
> undisclosed IPR claims", presumably so the participant can't secretly
> steer the solution to include or exclude the IPR.  It's a choice of
> who gets inconvenienced, you or the IETF?
>
> Indeed, if the IETF didn't have this rule, a company with undisclosed
> IPR could hire consultants, put them under NDA, and have them advocate
> at the IETF to include the IPR in standards.

Um ... if you are currently working for the IPR owner as a consultant,
it isn't 3rd party IPR ... if one is being paid to advocate related
to IPR, it is not the case Geoff outlined.

From adrian@olddog.co.uk  Tue Jan 28 11:03:55 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 616FC1A03B7; Tue, 28 Jan 2014 11:03:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3xsr3ya14PDR; Tue, 28 Jan 2014 11:03:54 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 012971A0159; Tue, 28 Jan 2014 11:03:53 -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 s0SJ3og3007547; Tue, 28 Jan 2014 19:03:50 GMT
Received: from 950129200 (13.17.90.92.rev.sfr.net [92.90.17.13]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SJ3l2h007519 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jan 2014 19:03:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Ned Freed'" <ned.freed@mrochek.com>, "'Mulligan, Geoff'" <geoff.mulligan@nist.gov>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <01P3ONLTEKWA0000AS@mauve.mrochek.com>
In-Reply-To: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Date: Tue, 28 Jan 2014 19:03:45 -0000
Message-ID: <047901cf1c5b$ad1c7a00$07556e00$@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: AQJJCP7mxrFZ7FpkefVpkZtALbnGxwHO9euCAaaLxDsCUoT0BwN3skPlAiUGdNAB1IqIxAMvTub5AZSy7CABe0denQHbXiYvAj5/8f+Y6g/AoA==
Content-Language: en-gb
X-TM-AS-MML: No
Cc: 'IETF WG Chairs' <wgchairs@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 19:03:55 -0000

Ned's reading agrees with mine.

It must suck to be under contract or NDA to someone who is participating in the
IETF and wilfully ignoring the IETF's IPR rules.

The first step may be to check with them direct that they are wilfully ignoring
those rules - it is possible that they have missed something and will thank you
for pointing it out. Both the company concerned and the participating individual
may be glad to hear from you.

Why might they thank you? Because if the company later tries to enforce a
license on their patent and it comes out that they sent people to participate
against the IETF's rules, then it is possible that a court might take a dim view
of their claim. Because if the IETF later discovers that the individual has
participated against the IETF's rules then the IETF might read and apply RFC
6701.

Cheers,
Adrian

PS It is not unheard of for a third party (such as an AD) to discover (through
whatever means) the existence of IPR that might be relevant and file a 3rd-party
notice accordingly.

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Ned Freed
> Sent: 28 January 2014 18:32
> To: Mulligan, Geoff
> Cc: IETF WG Chairs; ietf@ietf.org Mailing List
> Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well
)
> 
> > So because I know of IPR that someone else has and is not disclosing and
> > because I cannot legally disclose it - I can't continue to participate in
the
> > discussion doesn't seem right.  I'm not the holder of the IPR that isn't
being
> > disclosed, but I'm penalized.
> 
> As I have pointed out several times now, that's incorrect. 


From chair@ietf.org  Tue Jan 28 12:02:44 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1BA1A043C; Tue, 28 Jan 2014 12:02:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y8PVW4czDvio; Tue, 28 Jan 2014 12:02:43 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 428711A041F; Tue, 28 Jan 2014 12:02:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id D39DCA6150; Tue, 28 Jan 2014 12:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4_WIZcZFKQi3; Tue, 28 Jan 2014 12:01:57 -0800 (PST)
Received: from [10.30.0.105] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id ED1F29FB34; Tue, 28 Jan 2014 12:01:56 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Data Privacy Day
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 28 Jan 2014 22:02:37 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E3BAE90-6E18-4D67-A5E5-1F9BC17F3D01@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "alissa.cooper@gmail.com" <alissa.cooper@gmail.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 20:02:44 -0000

Today is International Data Privacy Day, and I asked Alissa Cooper to =
say a few words about how we are working on privacy topics at the IETF. =
You can read her thoughts here:

http://www.ietf.org/blog/2014/01/celebrating-data-privacy-day/

Jari Arkko
IETF Chair


From spencerdawkins.ietf@gmail.com  Tue Jan 28 12:14:43 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D80D1A039E for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 12:14:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZ15gttbw8ah for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 12:14:39 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6EFEA1A0266 for <ietf@ietf.org>; Tue, 28 Jan 2014 12:14:39 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id vb8so970697obc.32 for <ietf@ietf.org>; Tue, 28 Jan 2014 12:14:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=MAzXAJrnuYEnvImfCBmURmc07YvU0wMK/P+oxXECN/E=; b=zZCCqiIwGbIgujXmzo/7IjpnWWvuzbP/ht9dmsIZ1UF/TC0MH2FiQqQTZenzHXOn6P teAdoxQV0zP9R5j0IW4jMxZv/DWneVBy3NU1fRrAgj0S8qc6BUcgjVwJdWqsi3bjuxGr jsjmwIuetydMHlnpgz6Jheri7YX056ZO5gkrvobtmvriZxjJ7yVOHa0rKIY8mDkwrs66 e3n/la7WGjQDp24dHviUjei5TR4ag/e1IVQ/GogvZR1cUbT2+sOP74cPZZl2XAi99l+/ Oiy4mofYTJ0ySeeyIjK0131EqCk3s4iCrWflUKudc6SjjbkcsR7u8x2wB5iBM2E23pu6 3x+w==
X-Received: by 10.182.146.104 with SMTP id tb8mr1822163obb.54.1390940076792; Tue, 28 Jan 2014 12:14:36 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id n5sm98600706oer.5.2014.01.28.12.14.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 12:14:35 -0800 (PST)
Message-ID: <52E80FA9.5020704@gmail.com>
Date: Tue, 28 Jan 2014 14:14:33 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: When is an idea a good idea?
Content-Type: multipart/alternative; boundary="------------040909010703050008010902"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 20:14:43 -0000

This is a multi-part message in MIME format.
--------------040909010703050008010902
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Disclaimer - I'm one of the ADs who will be balloting your documents 
until at least March 2015, but I'm only one of 15 ADs, and haven't 
talked about this with the rest of the IESG.

The past week has brought me yet another example of an idea that could 
be a good idea, but not under every possible set of conditions, being 
evaluated as if we had to decide whether it was a good idea in all 
cases, or a bad idea. This might sound familiar to you, but if it does, 
let's not talk about that specific case.

The longer (and more painfully) we talk during Last Call, the more 
details we unearth that help me to understand what document 
authors/working groups are thinking, and that's good, but if it was less 
painful, that would be even better.

http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability 
Statements, as distinct from Technical Specifications, and says (among 
other things):

    An Applicability Statement specifies how, and under what
    circumstances, one or more TSs may be applied to support a particular
    Internet capability.

...

    An AS may describe particular methods of using a TS in a restricted
    "domain of applicability", such as Internet routers, terminal
    servers, Internet systems that interface to Ethernets, or datagram-
    based database servers.


Speaking only for myself, I don't expect Proposed Standards to be 
perfect, and to work perfectly in every situation, but if a 
specification doesn't describe any limits on applicability, I'm going to 
be evaluating it as if it will be used on the open Internet (that's what 
the "I" in "IETF" stands for).

If a draft says it's only intended to be used within an IP subnet, I'd 
evaluate it differently. I might ask that the authors/working group 
consider what the TTL should be set to, so that what starts out within 
an IP subnet stays within an IP subnet, but (to use one actual example) 
we wouldn't be arguing about whether it's OK to send 32K max-length 
packets over an arbitrary Internet path at line rate without getting any 
feedback about path capacity - there are probably paths where that would 
work, and there are definitely paths where it would not.

If a draft says it's only intended to be used on provisioned, managed 
internetwork links subject to SLA monitoring, I'd evaluate it differently.

If a draft says "this is a hack, intended for use on old hardware that 
can't do $X", I'd evaluate it differently.

There are other limited-use scenarios that would make me evaluate a 
draft differently.

None of this is a guaranteed pass, but it would help me a lot. It would 
likely help other reviewers, too.

So, if you don't intend for your draft to be used on the global 
Internet, please say so! As per 
http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to 
put an Applicability Statement in a different draft; just a section that 
says (another actual example) "this has been tested using these 
parameters on a lightly-loaded LAN, and it works there", that is more 
helpful than a tug of war(*) about whether something is a good idea or a 
bad idea in all situations, in front of a live studio audience.

Thanks to Alia Atlas for nudging me to think about this more.

Spencer

p.s. If you have feedback about what I'm thinking, I'd love for you to 
share it, whether on this list, privately to me, to the 2015 Nomcom, or 
to other Nomcom-eligible IETF participants when you're asking them to to 
sign the recall petition ;-)

(*) http://en.wikipedia.org/wiki/Tug_of_war

--------------040909010703050008010902
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Disclaimer - I'm one of the ADs who will be balloting your documents
    until at least March 2015, but I'm only one of 15 ADs, and haven't
    talked about this with the rest of the IESG.<br>
    <br>
    The past week has brought me yet another example of an idea that
    could be a good idea, but not under every possible set of
    conditions, being evaluated as if we had to decide whether it was a
    good idea in all cases, or a bad idea. This might sound familiar to
    you, but if it does, let's not talk about that specific case.<br>
    <br>
    The longer (and more painfully) we talk during Last Call, the more
    details we unearth that help me to understand what document
    authors/working groups are thinking, and that's good, but if it was
    less painful, that would be even better.<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="http://tools.ietf.org/html/rfc2026#section-3.2">http://tools.ietf.org/html/rfc2026#section-3.2</a>
    describes Applicability Statements, as distinct from Technical
    Specifications, and says (among other things):<br>
    <br>
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">   An Applicability Statement specifies how, and under what
   circumstances, one or more TSs may be applied to support a particular
   Internet capability. 

...

<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">   An AS may describe particular methods of using a TS in a restricted
   "domain of applicability", such as Internet routers, terminal
   servers, Internet systems that interface to Ethernets, or datagram-
   based database servers.
<pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"></pre></pre>
    <br>
    Speaking only for myself, I don't expect Proposed Standards to be
    perfect, and to work perfectly in every situation, but if a
    specification doesn't describe any limits on applicability, I'm
    going to be evaluating it as if it will be used on the open Internet
    (that's what the "I" in "IETF" stands for).<br>
    <br>
    If a draft says it's only intended to be used within an IP subnet,
    I'd evaluate it differently. I might ask that the authors/working
    group consider what the TTL should be set to, so that what starts
    out within an IP subnet stays within an IP subnet, but (to use one
    actual example) we wouldn't be arguing about whether it's OK to send
    32K max-length packets over an arbitrary Internet path at line rate
    without getting any feedback about path capacity - there are
    probably paths where that would work, and there are definitely paths
    where it would not.<br>
    <br>
    If a draft says it's only intended to be used on provisioned,
    managed internetwork links subject to SLA monitoring, I'd evaluate
    it differently.<br>
    <br>
    If a draft says "this is a hack, intended for use on old hardware
    that can't do $X", I'd evaluate it differently.<br>
    <br>
    There are other limited-use scenarios that would make me evaluate a
    draft differently.<br>
    <br>
    None of this is a guaranteed pass, but it would help me a lot. It
    would likely help other reviewers, too.<br>
    <br>
    So, if you don't intend for your draft to be used on the global
    Internet, please say so! As per
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="http://tools.ietf.org/html/rfc2026#section-3.3">http://tools.ietf.org/html/rfc2026#section-3.3</a>,
    it's not necessary to put an Applicability Statement in a different
    draft; just a section that says (another actual example) "this has
    been tested using these parameters on a lightly-loaded LAN, and it
    works there", that is more helpful than a tug of war(*) about
    whether something is a good idea or a bad idea in all situations, in
    front of a live studio audience.<br>
    <br>
    Thanks to Alia Atlas for nudging me to think about this more.<br>
    <br>
    Spencer<br>
    <br>
    p.s. If you have feedback about what I'm thinking, I'd love for you
    to share it, whether on this list, privately to me, to the 2015
    Nomcom, or to other Nomcom-eligible IETF participants when you're
    asking them to to sign the recall petition ;-)<br>
    <br>
    (*)
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a href="http://en.wikipedia.org/wiki/Tug_of_war">http://en.wikipedia.org/wiki/Tug_of_war</a><br>
  </body>
</html>

--------------040909010703050008010902--

From wood@isoc.org  Tue Jan 28 12:24:57 2014
Return-Path: <wood@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0291A03DB for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 12:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pN20l-UEVM_R for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 12:24:55 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0189.outbound.protection.outlook.com [207.46.163.189]) by ietfa.amsl.com (Postfix) with ESMTP id 653201A039E for <ietf@ietf.org>; Tue, 28 Jan 2014 12:24:55 -0800 (PST)
Received: from [10.8.25.1] (65.222.231.2) by BY2PR06MB026.namprd06.prod.outlook.com (10.242.45.12) with Microsoft SMTP Server (TLS) id 15.0.868.8; Tue, 28 Jan 2014 20:24:50 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Data Privacy Day
From: Greg Wood <wood@isoc.org>
In-Reply-To: <3E3BAE90-6E18-4D67-A5E5-1F9BC17F3D01@ietf.org>
Date: Tue, 28 Jan 2014 15:24:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <7EC48091-06A1-4743-A8C7-75AED5EC0D7F@isoc.org>
References: <3E3BAE90-6E18-4D67-A5E5-1F9BC17F3D01@ietf.org>
To: <ietf@ietf.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [65.222.231.2]
X-ClientProxiedBy: DM2PR08CA015.namprd08.prod.outlook.com (10.141.241.45) To BY2PR06MB026.namprd06.prod.outlook.com (10.242.45.12)
X-Forefront-PRVS: 0105DAA385
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(407274004)(164054003)(24454002)(199002)(189002)(51704005)(377454003)(495834002)(66066001)(76482001)(47976001)(47736001)(50226001)(65816001)(62966002)(81816001)(49866001)(50986001)(81686001)(80022001)(54316002)(53806001)(42186004)(51856001)(4396001)(33656001)(46102001)(56776001)(81542001)(79102001)(57306001)(50466002)(69226001)(93916002)(77982001)(59766001)(15975445006)(74706001)(23726002)(82746002)(81342001)(47776003)(63696002)(74502001)(74662001)(31966008)(74876001)(76786001)(86362001)(76796001)(87286001)(87266001)(93516002)(47446002)(74366001)(89996001)(56816005)(90146001)(77156001)(94316002)(77096001)(19580395003)(36756003)(19580405001)(92566001)(83716003)(83072002)(80976001)(93136001)(85306002)(85852003)(92726001)(15202345003)(15974865002)(46406003)(83322001)(88136002)(87976001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB026; H:[10.8.25.1]; CLIP:65.222.231.2; FPR:FADAC534.BB0B55FB.32D1BD6B.5CF481C1.201D4; InfoNoRecordsA:1; MX:1; LANG:en;
X-OriginatorOrg: isoc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 20:24:57 -0000

Jari,

This is a great post. Will push out via channels shortly.

I would like to chart out something like an editorial calendar for the =
blog and other efforts, in particular because these will start leading =
into and setting up potential media and policymaker conversations before =
and during the STRING workshop and IETF meeting.

Does your schedule permit a 30 min conversation this week?  I can put =
together a proposed agenda.=20

Thanks,
-Greg

On Jan 28, 2014, at 3:02 PM, IETF Chair <chair@ietf.org> wrote:

> Today is International Data Privacy Day, and I asked Alissa Cooper to =
say a few words about how we are working on privacy topics at the IETF. =
You can read her thoughts here:
>=20
> http://www.ietf.org/blog/2014/01/celebrating-data-privacy-day/
>=20
> Jari Arkko
> IETF Chair
>=20

--
Greg Wood
Internet Society

www.internetsociety.org
office: +1-703-439-2145
mobile: +1-703-625-3917


From adrian@olddog.co.uk  Tue Jan 28 13:01:16 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168921A038E for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.218
X-Spam-Level: 
X-Spam-Status: No, score=0.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PVY9JTiDLe7F for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:01:13 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 1A22F1A034E for <ietf@ietf.org>; Tue, 28 Jan 2014 13:01:12 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SL17CQ004764; Tue, 28 Jan 2014 21:01:07 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s0SL0rCn004706 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jan 2014 21:01:04 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Benoit Claise'" <bclaise@cisco.com>, <ietf@ietf.org>, "'Andrew Yourtchenko'" <ayourtch@cisco.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <52E77C81.8020803@cisco.com>
In-Reply-To: <52E77C81.8020803@cisco.com>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Date: Tue, 28 Jan 2014 21:00:51 -0000
Message-ID: <050801cf1c6c$0e7fdca0$2b7f95e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0509_01CF1C6C.0E870890"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFerF+1MVKpbR9CNhjCMYsURGW24gGF8EmEAuvAeakCKvVZ35tGmDiA
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 21:01:16 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0509_01CF1C6C.0E870890
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Thanks Benoit, that is an important point and is really helpful.
 
So, do I read you right if I say that this document records some NetFlow v9
features and codepoints that were accidentally missed when RFC 3954 was written.
 
Or are these later modifications to NetFlow v9 (let's call it v9.x) that use the
same code point range but were not actually part of v9?
 
The question might arise as to whether this document is supposed to update 3954.
 
Thanks,
Adrian
 
From: Benoit Claise [mailto:bclaise@cisco.com] 
Sent: 28 January 2014 09:47
To: adrian@olddog.co.uk; ietf@ietf.org; Andrew Yourtchenko
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
Information Elements reused in IPFIX) to Informational RFC
 
Let me reply to myself: I forgot an important point, which might be useful if
people start discussing AD sponsoring of this document, without actually having
read it.

Let me stress the first sentence of the Introduction section.
   The section 4 of [RFC7012] defines the IPFIX Information Elements in
   the range of 1-127 to be compatible with the NetFlow version 9
   fields, as specified in the "Cisco Systems NetFlow Services Export
   Version 9" [RFC3954]. 
So this draft is clearly linked to the work in IPFIX RFC 7012 (IPFIX information
model) and must follow the RFC 7013 rules (Guidelines for Authors and Reviewers
of IPFIX Information Elements), therefore would benefit from more reviews.

It's probably not too clear from the abstract, and should be improved.

OLD:
   This document describes some additional Information Elements of Cisco
   Systems, Inc. that are not listed in RFC3954
 
NEW:
   This document describes some additional IPFIX Information Elements in 
   the range of 1-127, which is the range compatible with field types used 
   by NetFlow version 9 in RFC3954 <http://tools.ietf.org/html/rfc3954> , as
specified in the IPFIX Information Model
   RFC 7012.
 
Regards, Benoit (an as author)
 
Adrian, 

Not an answer to the process question, but some background information on this
draft. 
This draft, which is now 3 years old, has been evolving with the IPFIX
standardization. 
For example, looking at
http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt, you can
see the interaction with the IPFIX WG document
ietf-ipfix-data-link-layer-monitoring: now that 
ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the draft has
been simplified, and some IPFIX Information Elements in the range 1-127 became
deprecated. 
This explains why the draft has been presented and reviewed multiple times in
the IPFIX WG, and also why it would benefit from a wider review than the
independent stream. 

Regards, Benoit (as draft author) 




Hi, 

I have a process question on this last call which is not clear from the last 
call text. 

Are we being asked to consider whether publication of this document is useful, 
or are we being asked for IETF consensus on the *content* of the document? 

It seems from the document that the content is descriptive of something 
implemented by a single vendor. I applaud putting that information into the 
public domain, but I don't understand the meaning of IETF consensus with respect

to this document. 

Thanks, 
Adrian 



-----Original Message----- 
From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The 
IESG 
Sent: 21 January 2014 12:33 
To: IETF-Announce 
Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific 
Information Elements reused in IPFIX) to Informational RFC 


The IESG has received a request from an individual submitter to consider 
the following document: 
- 'Cisco Specific Information Elements reused in IPFIX' 
   <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be 
sent to iesg@ietf.org instead. In either case, please retain the 
beginning of the Subject line to allow automated sorting. 

Abstract 


    This document describes some additional Information Elements of Cisco 
    Systems, Inc. that are not listed in RFC3954. 




The file can be obtained via 
http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ 

IESG discussion can be tracked via 
http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/ 


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

. 

. 
 

------=_NextPart_000_0509_01CF1C6C.0E870890
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CF1C6B.86D15D60"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536870145 1073786111 1 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-520092929 1073806591 9 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
pre
	{mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:Calibri;
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	mso-ascii-font-family:Consolas;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Consolas;
	mso-bidi-font-family:Consolas;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-size:10.0pt;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman","serif";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite =
lang=3DEN-GB link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:36.0pt'><div class=3DWordSection1><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Thanks Benoit, that is an =
important point and is really helpful.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>So, do I read you right if I =
say that this document records some NetFlow v9 features and codepoints =
that were accidentally missed when RFC 3954 was =
written.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Or are these later =
modifications to NetFlow v9 (let's call it v9.x) that use the same code =
point range but were not actually part of v9?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>The question might arise as to =
whether this document is supposed to update =
3954.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";color:windowtext;mso-ansi-language:EN-US'>From:</span></b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";color:windowtext;mso-ansi-language:EN-US'> =
Benoit Claise [mailto:bclaise@cisco.com] <br><b>Sent:</b> 28 January =
2014 09:47<br><b>To:</b> adrian@olddog.co.uk; ietf@ietf.org; Andrew =
Yourtchenko<br><b>Subject:</b> Re: Last Call: =
&lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco Specific Information =
Elements reused in IPFIX) to Informational =
RFC<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>Let me reply to =
myself: I forgot an important point, which might be useful if people =
start discussing AD sponsoring of this document, without actually having =
read it.<br><br>Let me stress the first sentence of the Introduction =
section.<o:p></o:p></span></p><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>The section 4 of =
[RFC7012] defines the IPFIX Information Elements =
in<o:p></o:p></pre><pre><span style=3D'mso-spacerun:yes'>&nbsp;&nbsp; =
</span>the range of 1-127 to be compatible with the NetFlow version =
9<o:p></o:p></pre><pre><span style=3D'mso-spacerun:yes'>&nbsp;&nbsp; =
</span>fields, as specified in the &quot;Cisco Systems NetFlow Services =
Export<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>Version 9&quot; =
[RFC3954]. <o:p></o:p></pre><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New Roman"'>So this draft is =
clearly linked to the work in IPFIX RFC 7012 (IPFIX information model) =
and must follow the RFC 7013 rules (Guidelines for Authors and Reviewers =
of IPFIX Information Elements), therefore would benefit from more =
reviews.<br><br>It's probably not too clear from the abstract, and =
should be improved.<br><br>OLD:<o:p></o:p></span></p><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>This document describes =
some additional Information Elements of Cisco<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>Systems, Inc. that are =
not listed in =
RFC3954<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>NEW:<o:p></o:p><=
/pre><pre><span style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>This =
document describes some additional IPFIX Information Elements in =
<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp;</span>the range of 1-127, =
which is the range compatible with field types used =
<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp;&nbsp;</span>by NetFlow version 9 =
in <a href=3D"http://tools.ietf.org/html/rfc3954" title=3D"&quot;Cisco =
Systems NetFlow Services Export Version 9&quot;">RFC3954</a>, as =
specified in the IPFIX Information Model<o:p></o:p></pre><pre><span =
style=3D'mso-spacerun:yes'>&nbsp;&nbsp; </span>RFC =
7012.<o:p></o:p></pre><pre>&nbsp;<o:p></o:p></pre><pre>Regards, Benoit =
(an as author)<o:p></o:p></pre><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><p =
class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Adrian, <br><br>Not an answer to the process question, but some =
background information on this draft. <br>This draft, which is now 3 =
years old, has been evolving with the IPFIX standardization. <br>For =
example, looking at <a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisco-ies-=
09.txt">http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisco-ies-=
09.txt</a>, you can see the interaction with the IPFIX WG document =
ietf-ipfix-data-link-layer-monitoring: now that =
<br>ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, =
the draft has been simplified, and some IPFIX Information Elements in =
the range 1-127 became deprecated. <br>This explains why the draft has =
been presented and reviewed multiple times in the IPFIX WG, and also why =
it would benefit from a wider review than the independent stream. =
<br><br>Regards, Benoit (as draft author) <br><br><br =
style=3D'mso-special-character:line-break'><![if =
!supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'><![endif]><o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>Hi, <br><br>I have a process question on this last call which is =
not clear from the last <br>call text. <br><br>Are we being asked to =
consider whether publication of this document is useful, <br>or are we =
being asked for IETF consensus on the *content* of the document? =
<br><br>It seems from the document that the content is descriptive of =
something <br>implemented by a single vendor. I applaud putting that =
information into the <br>public domain, but I don't understand the =
meaning of IETF consensus with respect <br>to this document. =
<br><br>Thanks, <br>Adrian <br><br =
style=3D'mso-special-character:line-break'><![if =
!supportLineBreakNewLine]><br =
style=3D'mso-special-character:line-break'><![endif]><o:p></o:p></span></=
p><p class=3DMsoNormal><span style=3D'mso-fareast-font-family:"Times New =
Roman"'>-----Original Message----- <br>From: IETF-Announce [<a =
href=3D"mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounc=
es@ietf.org</a>] On Behalf Of The <br>IESG <br>Sent: 21 January 2014 =
12:33 <br>To: IETF-Announce <br>Subject: Last Call: =
&lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco Specific =
<br>Information Elements reused in IPFIX) to Informational RFC =
<br><br><br>The IESG has received a request from an individual submitter =
to consider <br>the following document: <br>- 'Cisco Specific =
Information Elements reused in IPFIX' <br>&nbsp;&nbsp; =
&lt;draft-yourtchenko-cisco-ies-09.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 href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> =
mailing lists by 2014-02-18. Exceptionally, comments may be <br>sent to =
<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either =
case, please retain the <br>beginning of the Subject line to allow =
automated sorting. <br><br>Abstract <br><br><br>&nbsp;&nbsp;&nbsp; This =
document describes some additional Information Elements of Cisco =
<br>&nbsp;&nbsp;&nbsp; Systems, Inc. that are not listed in RFC3954. =
<br><br><br><br><br>The file can be obtained via <br><a =
href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/">htt=
p://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/</a> =
<br><br>IESG discussion can be tracked via <br><a =
href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballo=
t/">http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/</=
a> <br><br><br>No IPR declarations have been submitted directly on this =
I-D. <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'mso-fareast-font-family:"Times New Roman"'><br>. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><span =
style=3D'mso-fareast-font-family:"Times New Roman"'><br>. =
<o:p></o:p></span></p></blockquote><p class=3DMsoNormal><span =
style=3D'mso-fareast-font-family:"Times New =
Roman"'><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_000_0509_01CF1C6C.0E870890--


From trammell@tik.ee.ethz.ch  Tue Jan 28 13:42:56 2014
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AA21A018F for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.734
X-Spam-Level: 
X-Spam-Status: No, score=-4.734 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3BygXRMBNXCb for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:42:52 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id 5958E1A0056 for <ietf@ietf.org>; Tue, 28 Jan 2014 13:42:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id A0853D9303; Tue, 28 Jan 2014 22:42:48 +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 AqloAbH29mFR; Tue, 28 Jan 2014 22:42:48 +0100 (MET)
Received: from [10.0.27.100] (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 B6832D9302; Tue, 28 Jan 2014 22:42:47 +0100 (MET)
Content-Type: multipart/signed; boundary="Apple-Mail=_C42187CD-88CA-4B27-B466-433DECC1ADAB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
From: Brian Trammell <trammell@tik.ee.ethz.ch>
In-Reply-To: <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
Date: Tue, 28 Jan 2014 22:42:46 +0100
Message-Id: <5FDB6DFC-DEC9-4066-A9AF-C6FDFCFC7C2E@tik.ee.ethz.ch>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1827)
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 21:42:56 -0000

--Apple-Mail=_C42187CD-88CA-4B27-B466-433DECC1ADAB
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_F76E93B8-A7A9-43F5-857F-29192819B3EB"


--Apple-Mail=_F76E93B8-A7A9-43F5-857F-29192819B3EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

hi Adrian, all,

answering as an IPFIX geek and RFC 7013 IE-Doctors reviewer, inline=85

On 28 Jan 2014, at 12:17, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Thanks Benoit,
>=20
> And I am not much concerned with the process here as with the meaning =
of the
> IETF last call.
>=20
> Reading the document, I don't understand what would happen if I found =
something
> that I thought should be different. It looks to me that this is a =
record of what
> has been implemented and deployed. That is fine and good, but I don't =
see what
> my review is supposed to give as input.
>=20
> It seems to me that either this is an IETF document describing some =
IPFIX
> widgets (drop all the Cisco stuff, get the WG to agree they want the =
feature,
> and let the IETF do a proper review probably as Standards Track) or it =
is a
> record of what Cisco did (continue to publish it, but don't ask for =
review of
> the content).

My understanding is it=92s the latter: for these, we basically have to =
presume that the _content_ of the Information Element descriptions =
correctly describes the behavior in NetFlow Version 9, and cannot change =
the descriptions to improve them for general use, because this is =
essentially the opening of an (older) internal spec. Indeed, note that =
11 of the 18 of the Information Elements are being added to the registry =
as deprecated already, as they have been replaced by improved =
Information Elements within the context of further development of IPFIX.

> Joel points out that it is valuable to check that the publication of =
this
> document doesn't break anything else.

That's one utility of wider review here. Another is to ensure that there =
are no obvious errors: either inconsistencies in the descriptions =
(though none of the descriptions make reference to external sources that =
the community could check) or in the various fields of the registry =
(abstract data type and semantics; these will also be checked in the =
IE-Doctors review).

And on this question:=20

> The question might arise as to whether this document is supposed to =
update 3954.

In general, when documents only change the IPFIX Information Element =
registry, we consider that separate from changes to the protocol. =
Documents proposing new Information Elements don't update RFC 5102; =
Indeed, RFC 7012, which obsoletes 5102, even removed all the Information =
Element definitions to make it very clear to implementors that the IANA =
registry was now the normative reference for them.

Of course, 3954 is a bit of an oddity in that it contains both protocol =
and information model, but at the same time, 3954 only exists in an IETF =
context as part of the candidate evaluation for IPFIX protocols. So =
since we don't really expect anyone to implement it (indeed, we'd much =
rather they implement IPFIX), I don't see how having this document =
referenced from 3954 would improve interoperability of flow measurement: =
the Information Elements will be added to the registry, which is where =
we want everyone to look.

Best regards,

Brian

>> -----Original Message-----
>> From: Benoit Claise [mailto:bclaise@cisco.com]
>> Sent: 28 January 2014 00:15
>> To: adrian@olddog.co.uk; ietf@ietf.org
>> Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco =
Specific
>> Information Elements reused in IPFIX) to Informational RFC
>>=20
>> Adrian,
>>=20
>> Not an answer to the process question, but some background =
information
>> on this draft.
>> This draft, which is now 3 years old, has been evolving with the =
IPFIX
>> standardization.
>> For example, looking at
>> =
http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisco-ies-09.txt,
>> you can see the interaction with the IPFIX WG document
>> ietf-ipfix-data-link-layer-monitoring: now that
>> ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the
>> draft has been simplified, and some IPFIX Information Elements in the
>> range 1-127 became deprecated.
>> This explains why the draft has been presented and reviewed multiple
>> times in the IPFIX WG, and also why it would benefit from a wider =
review
>> than the independent stream.
>>=20
>> Regards, Benoit (as draft author)
>>=20
>>=20
>>> Hi,
>>>=20
>>> I have a process question on this last call which is not clear from =
the last
>>> call text.
>>>=20
>>> Are we being asked to consider whether publication of this document =
is
> useful,
>>> or are we being asked for IETF consensus on the *content* of the =
document?
>>>=20
>>> It seems from the document that the content is descriptive of =
something
>>> implemented by a single vendor. I applaud putting that information =
into the
>>> public domain, but I don't understand the meaning of IETF consensus =
with
>> respect
>>> to this document.
>>>=20
>>> Thanks,
>>> Adrian
>>>=20
>>>> -----Original Message-----
>>>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On =
Behalf Of
>> The
>>>> IESG
>>>> Sent: 21 January 2014 12:33
>>>> To: IETF-Announce
>>>> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco =
Specific
>>>> Information Elements reused in IPFIX) to Informational RFC
>>>>=20
>>>>=20
>>>> The IESG has received a request from an individual submitter to =
consider
>>>> the following document:
>>>> - 'Cisco Specific Information Elements reused in IPFIX'
>>>>   <draft-yourtchenko-cisco-ies-09.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 2014-02-18. 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 describes some additional Information Elements of =
Cisco
>>>>    Systems, Inc. that are not listed in RFC3954.
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>>>>=20
>>>>=20
>>>> No IPR declarations have been submitted directly on this I-D.
>>>=20
>>> .
>>>=20


--Apple-Mail=_F76E93B8-A7A9-43F5-857F-29192819B3EB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">hi =
Adrian, all,<div><br></div><div>answering as an IPFIX geek and RFC 7013 =
IE-Doctors reviewer, inline=85</div><div><br><div><div>On 28 Jan 2014, =
at 12:17, Adrian Farrel &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Thanks Benoit,<br><br>And I am not much concerned with the =
process here as with the meaning of the<br>IETF last =
call.<br><br>Reading the document, I don't understand what would happen =
if I found something<br>that I thought should be different. It looks to =
me that this is a record of what<br>has been implemented and deployed. =
That is fine and good, but I don't see what<br>my review is supposed to =
give as input.<br><br>It seems to me that either this is an IETF =
document describing some IPFIX<br>widgets (drop all the Cisco stuff, get =
the WG to agree they want the feature,<br>and let the IETF do a proper =
review probably as Standards Track) or it is a<br>record of what Cisco =
did (continue to publish it, but don't ask for review of<br>the =
content).<br></blockquote><div><br></div><div>My understanding is it=92s =
the latter: for these, we basically have to presume that the _content_ =
of the Information Element descriptions correctly describes the behavior =
in NetFlow Version 9, and cannot change the descriptions to improve them =
for general use, because this is essentially the opening of an (older) =
internal spec. Indeed, note that 11 of the 18 of the Information =
Elements are being added to the registry as deprecated already, as they =
have been replaced by improved Information Elements within the context =
of further development of IPFIX.</div><div><br></div><blockquote =
type=3D"cite">Joel points out that it is valuable to check that the =
publication of this<br>document doesn't break anything =
else.</blockquote><div><br></div><div>That's one utility of wider review =
here. Another is to ensure that there are no obvious errors: either =
inconsistencies in the descriptions (though none of the descriptions =
make reference to external sources that the community could check) or in =
the various fields of the registry (abstract data type and semantics; =
these will also be checked in the IE-Doctors =
review).</div><div><br></div><div>And on this =
question:&nbsp;</div><div><span style=3D"background-color: rgb(255, 255, =
255); color: rgb(31, 73, 125); font-family: Calibri, sans-serif; =
font-size: 15px;"><br></span></div><div><blockquote type=3D"cite"><span =
style=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; =
font-size: 15px; background-color: rgb(255, 255, 255);">The question =
might arise as to whether this document is supposed to update =
3954.</span></blockquote><br></div><div>In general, when documents only =
change the IPFIX Information Element registry, we consider that separate =
from changes to the protocol. Documents proposing new Information =
Elements don't update RFC 5102; Indeed, RFC 7012, which obsoletes 5102, =
even removed all the Information Element definitions to make it very =
clear to implementors that the IANA registry was now the normative =
reference for them.</div><div><br></div><div>Of course, 3954 is a bit of =
an oddity in that it contains both protocol and information model, but =
at the same time, 3954 only exists in an IETF context as part of the =
candidate evaluation for IPFIX protocols. So since we don't really =
expect anyone to implement it (indeed, we'd much rather they implement =
IPFIX), I don't see how having this document referenced from 3954 would =
improve interoperability of flow measurement: the Information Elements =
will be added to the registry, which is where we want everyone to =
look.</div><div><br></div><div>Best =
regards,</div><div><br></div><div>Brian</div><div><br></div><blockquote =
type=3D"cite"><blockquote type=3D"cite">-----Original =
Message-----<br>From: Benoit Claise [<a =
href=3D"mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]<br>Sent: =
28 January 2014 00:15<br>To: <a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>; <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>Subject: Re: Last =
Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco =
Specific<br>Information Elements reused in IPFIX) to Informational =
RFC<br><br>Adrian,<br><br>Not an answer to the process question, but =
some background information<br>on this draft.<br>This draft, which is =
now 3 years old, has been evolving with the =
IPFIX<br>standardization.<br>For example, looking at<br><a =
href=3D"http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisco-ies-0=
9.txt">http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-cisco-ies-09=
.txt</a>,<br>you can see the interaction with the IPFIX WG =
document<br>ietf-ipfix-data-link-layer-monitoring: now =
that<br>ietf-ipfix-data-link-layer-monitoring is in the RFC editor =
queue, the<br>draft has been simplified, and some IPFIX Information =
Elements in the<br>range 1-127 became deprecated.<br>This explains why =
the draft has been presented and reviewed multiple<br>times in the IPFIX =
WG, and also why it would benefit from a wider review<br>than the =
independent stream.<br><br>Regards, Benoit (as draft =
author)<br><br><br><blockquote type=3D"cite">Hi,<br><br>I have a process =
question on this last call which is not clear from the last<br>call =
text.<br><br>Are we being asked to consider whether publication of this =
document is<br></blockquote></blockquote>useful,<br><blockquote =
type=3D"cite"><blockquote type=3D"cite">or are we being asked for IETF =
consensus on the *content* of the document?<br><br>It seems from the =
document that the content is descriptive of something<br>implemented by =
a single vendor. I applaud putting that information into the<br>public =
domain, but I don't understand the meaning of IETF consensus =
with<br></blockquote>respect<br><blockquote type=3D"cite">to this =
document.<br><br>Thanks,<br>Adrian<br><br><blockquote =
type=3D"cite">-----Original Message-----<br>From: IETF-Announce [<a =
href=3D"mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounce=
s@ietf.org</a>] On Behalf =
Of<br></blockquote></blockquote>The<br><blockquote =
type=3D"cite"><blockquote type=3D"cite">IESG<br>Sent: 21 January 2014 =
12:33<br>To: IETF-Announce<br>Subject: Last Call: =
&lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco =
Specific<br>Information Elements reused in IPFIX) to Informational =
RFC<br><br><br>The IESG has received a request from an individual =
submitter to consider<br>the following document:<br>- 'Cisco Specific =
Information Elements reused in IPFIX'<br> =
&nbsp;&nbsp;&lt;draft-yourtchenko-cisco-ies-09.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 href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> =
mailing lists by 2014-02-18. Exceptionally, comments may be<br>sent to =
<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either =
case, please retain the<br>beginning of the Subject line to allow =
automated sorting.<br><br>Abstract<br><br><br> &nbsp;&nbsp;&nbsp;This =
document describes some additional Information Elements of Cisco<br> =
&nbsp;&nbsp;&nbsp;Systems, Inc. that are not listed in =
RFC3954.<br><br><br><br><br>The file can be obtained via<br><a =
href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/">http=
://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/</a><br><br>IESG =
discussion can be tracked =
via<br>http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/=
<br><br><br>No IPR declarations have been submitted directly on this =
I-D.<br></blockquote><br>.<br><br></blockquote></blockquote></blockquote><=
/div><br></div></body></html>=

--Apple-Mail=_F76E93B8-A7A9-43F5-857F-29192819B3EB--

--Apple-Mail=_C42187CD-88CA-4B27-B466-433DECC1ADAB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJS6CRWAAoJENt3nsOmbNJcPz0IAK0YYFhg2S+sPDTlKp1S9PMf
omrksS80DtRz0GC06SC4ahRYeq0YE9YX79Na71de3B+hfjigD+Sm7CkvhjgO54DP
8oj1NnvcH9EETkSwiYneP8bTdFxf36LZOAuw3FNcoCaA0Ql6hz3sdagAyrqgySst
NGO4ZKn+Q327u3nYaqXMaOnGJb0eFJIN8P7CqCmPOvEAiRPNliQaVzjTjFBEvdbz
L/lpMl3fPWJRXPs5HUhR0ow04/EN9m3cC2cLB611qJBqZBWfLxcP4Rc8IaY7DQxq
oFZfHKVhAkXX2vT7CvsHv34f0KzQeE+PseVeUyfTIcwFX64NDD6EqmQppim0af8=
=UHnB
-----END PGP SIGNATURE-----

--Apple-Mail=_C42187CD-88CA-4B27-B466-433DECC1ADAB--

From hsantos@isdg.net  Tue Jan 28 13:52:51 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 117FF1A028F for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ypr-LkBpsLim for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 13:52:47 -0800 (PST)
Received: from mail.santronics.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF3A1A00F6 for <ietf@ietf.org>; Tue, 28 Jan 2014 13:52:47 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5505; t=1390945955; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=4yZHX2yzIv8Z9crOsjGs1PI9IqM=; b=lpIYahvUOBjvMQEzUBUE 6t1+LmEsEsmE+jUCu4ixsGrSYCYnSdVPRmFgC10cDgsEMbjfMZoc8DbIodI9qtuQ 1ReGI++FFTK3jLJreFr+hZVNA4/NtTJKoT/FOaVXSeNfDbcKRoy0/7nZHsqoZkS9 9j9DXUJk9NVu2gDd0oyGwDw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 28 Jan 2014 16:52:35 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 228443753.2349.5116; Tue, 28 Jan 2014 16:52:34 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5505; t=1390945367; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=S7blt3w vC5TSEl8MWu9vl6pu/Hv0NFcKUXUGDFLxFG0=; b=WG5VHckXt21R01Vp0WaoQQ7 Dml7P+a1kyaB3fte3H3evk0cg1psZxzD/lW+0PttpZMM32e82wHxlx4w9u13IRbo IWlKznsEf0R3MRakjN3PUpxAbSMaHv2NY0sq4QreJ7TSnU+2g98LbrZVXfz3tZIO vewZ6d+vhp1sD2unh4ng=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 28 Jan 2014 16:42:47 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3969713942.9.7196; Tue, 28 Jan 2014 16:42:47 -0500
Message-ID: <52E826A3.3040605@isdg.net>
Date: Tue, 28 Jan 2014 16:52:35 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
References: <52E80FA9.5020704@gmail.com>
In-Reply-To: <52E80FA9.5020704@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 21:52:51 -0000

I think the IETF needs a new status for document submissions. 
Something more advanced than experimental and informational but less 
than a Proposed Standard (PS) perhaps called Proposed Method (PM).  A 
PM will need towards an IM (Internet Method).

When something is written as a "standard" there tends to be a higher 
bar to do something different. It provides a sense of final closure 
and resolution and this is where many debates, conflict of interest, 
are based, where IETF Appeals are more probable.  Who cares if a 
proposal is informational or experiment?  Not really strong enough and 
too risky for adoption. A "standard" has a higher bar to reach but 
also to change as well.

I believe a PM will help with the acceptance of proposals that may fit 
in this in between category where it may not be considered a standard 
material, yet, it offers some level of technology that is beyond being 
informational or experimental, i.e. a segment of the market place is 
using it, technology leader wishes to document a proprietary method as 
an open and public domain method.

I believe a PM may also help alleviate the "good vs bad" debates, 
allow for greater adoption explorations.   It tells the industry that 
we found something useful, already used in practice, try it yourself, 
but its still not something the IETF to be the "standard" method.

Anyway, the PM idea seems to come back more and more as you see more 
of these "half-baked" proposed standards when they seems to be more 
experimental or informational in nature.   You have good ideas out 
there that do need to be documented.  But you don't need to make them 
Proposed Standards which has a tremendously high bar and higher source 
for major debates, especially when there are conflicts.

--
HLS

On 1/28/2014 3:14 PM, Spencer Dawkins wrote:
> Disclaimer - I'm one of the ADs who will be balloting your documents
> until at least March 2015, but I'm only one of 15 ADs, and haven't
> talked about this with the rest of the IESG.
>
> The past week has brought me yet another example of an idea that could
> be a good idea, but not under every possible set of conditions, being
> evaluated as if we had to decide whether it was a good idea in all
> cases, or a bad idea. This might sound familiar to you, but if it
> does, let's not talk about that specific case.
>
> The longer (and more painfully) we talk during Last Call, the more
> details we unearth that help me to understand what document
> authors/working groups are thinking, and that's good, but if it was
> less painful, that would be even better.
>
> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
> Statements, as distinct from Technical Specifications, and says (among
> other things):
>
>     An Applicability Statement specifies how, and under what
>     circumstances, one or more TSs may be applied to support a particular
>     Internet capability.
>
> ...
>
>     An AS may describe particular methods of using a TS in a restricted
>     "domain of applicability", such as Internet routers, terminal
>     servers, Internet systems that interface to Ethernets, or datagram-
>     based database servers.
>
>
> Speaking only for myself, I don't expect Proposed Standards to be
> perfect, and to work perfectly in every situation, but if a
> specification doesn't describe any limits on applicability, I'm going
> to be evaluating it as if it will be used on the open Internet (that's
> what the "I" in "IETF" stands for).
>
> If a draft says it's only intended to be used within an IP subnet, I'd
> evaluate it differently. I might ask that the authors/working group
> consider what the TTL should be set to, so that what starts out within
> an IP subnet stays within an IP subnet, but (to use one actual
> example) we wouldn't be arguing about whether it's OK to send 32K
> max-length packets over an arbitrary Internet path at line rate
> without getting any feedback about path capacity - there are probably
> paths where that would work, and there are definitely paths where it
> would not.
>
> If a draft says it's only intended to be used on provisioned, managed
> internetwork links subject to SLA monitoring, I'd evaluate it differently.
>
> If a draft says "this is a hack, intended for use on old hardware that
> can't do $X", I'd evaluate it differently.
>
> There are other limited-use scenarios that would make me evaluate a
> draft differently.
>
> None of this is a guaranteed pass, but it would help me a lot. It
> would likely help other reviewers, too.
>
> So, if you don't intend for your draft to be used on the global
> Internet, please say so! As per
> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
> put an Applicability Statement in a different draft; just a section
> that says (another actual example) "this has been tested using these
> parameters on a lightly-loaded LAN, and it works there", that is more
> helpful than a tug of war(*) about whether something is a good idea or
> a bad idea in all situations, in front of a live studio audience.
>
> Thanks to Alia Atlas for nudging me to think about this more.
>
> Spencer
>
> p.s. If you have feedback about what I'm thinking, I'd love for you to
> share it, whether on this list, privately to me, to the 2015 Nomcom,
> or to other Nomcom-eligible IETF participants when you're asking them
> to to sign the recall petition ;-)
>
> (*) http://en.wikipedia.org/wiki/Tug_of_war





From spencerdawkins.ietf@gmail.com  Tue Jan 28 14:34:32 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BBA91A03A6 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 14:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vo4zgt0Xqgnt for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 14:34:29 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id C55DF1A03C4 for <ietf@ietf.org>; Tue, 28 Jan 2014 14:34:29 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id uy5so1135127obc.19 for <ietf@ietf.org>; Tue, 28 Jan 2014 14:34:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=kNzoHQ5M4j0dAsdEaaddG/617BVYmECERPcPYHqaI0A=; b=m9mqi9WXQ71c/ZclPt4NpPzchp/+lEHg59KAlWY+ug6YJ5792t0eUvtUF3aGa/yJ4Q pZgmQdA8HDoSQ5kU/PgR3IjOLyzgD2m/isycVP+Yr5Sb7daXkzHcS/2Rp9YGT+2Vo0O5 5YXoyygKyayv2+D6UHh7RsfX57f2IYcOnxwcZKz5EiPNje517lbu8pL1IGnTPGsaHOBC hMPNHuSWswOfCkixAiUsU7u8r7LWTdiuqUF6/Gxz96pE+Ikr506WnbVwHoqIp5YrzyEj QPs1YM1jhXRhiy0LzoM4eZNTBLBkF9e1vxWFIBMeBUYoe41kFrmZoxiqmZs3mGfTvjnN 1xWw==
X-Received: by 10.60.246.164 with SMTP id xx4mr3085603oec.25.1390948467094; Tue, 28 Jan 2014 14:34:27 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id su13sm537651oeb.1.2014.01.28.14.34.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 14:34:26 -0800 (PST)
Message-ID: <52E8306F.3020403@gmail.com>
Date: Tue, 28 Jan 2014 16:34:23 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net>
In-Reply-To: <52E826A3.3040605@isdg.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 22:34:32 -0000

Just to be clear, I'm certainly not opposed to exploring this question, 
but I do think it's orthogonal to my post ("how do we review 
specifications that might not be applicable everywhere?" as opposed to 
"how do we get some deployment experience before deciding something is a 
proposed standard?").

So definitely, thanks for changing the subject line, and perhaps you 
could knock out an Internet-Draft proposing Proposed Methods?

Spencer

On 01/28/2014 03:52 PM, Hector Santos wrote:
> I think the IETF needs a new status for document submissions. 
> Something more advanced than experimental and informational but less 
> than a Proposed Standard (PS) perhaps called Proposed Method (PM).  A 
> PM will need towards an IM (Internet Method).
>
> When something is written as a "standard" there tends to be a higher 
> bar to do something different. It provides a sense of final closure 
> and resolution and this is where many debates, conflict of interest, 
> are based, where IETF Appeals are more probable.  Who cares if a 
> proposal is informational or experiment?  Not really strong enough and 
> too risky for adoption. A "standard" has a higher bar to reach but 
> also to change as well.
>
> I believe a PM will help with the acceptance of proposals that may fit 
> in this in between category where it may not be considered a standard 
> material, yet, it offers some level of technology that is beyond being 
> informational or experimental, i.e. a segment of the market place is 
> using it, technology leader wishes to document a proprietary method as 
> an open and public domain method.
>
> I believe a PM may also help alleviate the "good vs bad" debates, 
> allow for greater adoption explorations.   It tells the industry that 
> we found something useful, already used in practice, try it yourself, 
> but its still not something the IETF to be the "standard" method.
>
> Anyway, the PM idea seems to come back more and more as you see more 
> of these "half-baked" proposed standards when they seems to be more 
> experimental or informational in nature.   You have good ideas out 
> there that do need to be documented.  But you don't need to make them 
> Proposed Standards which has a tremendously high bar and higher source 
> for major debates, especially when there are conflicts.
>
> -- 
> HLS
>
> On 1/28/2014 3:14 PM, Spencer Dawkins wrote:
>> Disclaimer - I'm one of the ADs who will be balloting your documents
>> until at least March 2015, but I'm only one of 15 ADs, and haven't
>> talked about this with the rest of the IESG.
>>
>> The past week has brought me yet another example of an idea that could
>> be a good idea, but not under every possible set of conditions, being
>> evaluated as if we had to decide whether it was a good idea in all
>> cases, or a bad idea. This might sound familiar to you, but if it
>> does, let's not talk about that specific case.
>>
>> The longer (and more painfully) we talk during Last Call, the more
>> details we unearth that help me to understand what document
>> authors/working groups are thinking, and that's good, but if it was
>> less painful, that would be even better.
>>
>> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
>> Statements, as distinct from Technical Specifications, and says (among
>> other things):
>>
>>     An Applicability Statement specifies how, and under what
>>     circumstances, one or more TSs may be applied to support a 
>> particular
>>     Internet capability.
>>
>> ...
>>
>>     An AS may describe particular methods of using a TS in a restricted
>>     "domain of applicability", such as Internet routers, terminal
>>     servers, Internet systems that interface to Ethernets, or datagram-
>>     based database servers.
>>
>>
>> Speaking only for myself, I don't expect Proposed Standards to be
>> perfect, and to work perfectly in every situation, but if a
>> specification doesn't describe any limits on applicability, I'm going
>> to be evaluating it as if it will be used on the open Internet (that's
>> what the "I" in "IETF" stands for).
>>
>> If a draft says it's only intended to be used within an IP subnet, I'd
>> evaluate it differently. I might ask that the authors/working group
>> consider what the TTL should be set to, so that what starts out within
>> an IP subnet stays within an IP subnet, but (to use one actual
>> example) we wouldn't be arguing about whether it's OK to send 32K
>> max-length packets over an arbitrary Internet path at line rate
>> without getting any feedback about path capacity - there are probably
>> paths where that would work, and there are definitely paths where it
>> would not.
>>
>> If a draft says it's only intended to be used on provisioned, managed
>> internetwork links subject to SLA monitoring, I'd evaluate it 
>> differently.
>>
>> If a draft says "this is a hack, intended for use on old hardware that
>> can't do $X", I'd evaluate it differently.
>>
>> There are other limited-use scenarios that would make me evaluate a
>> draft differently.
>>
>> None of this is a guaranteed pass, but it would help me a lot. It
>> would likely help other reviewers, too.
>>
>> So, if you don't intend for your draft to be used on the global
>> Internet, please say so! As per
>> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
>> put an Applicability Statement in a different draft; just a section
>> that says (another actual example) "this has been tested using these
>> parameters on a lightly-loaded LAN, and it works there", that is more
>> helpful than a tug of war(*) about whether something is a good idea or
>> a bad idea in all situations, in front of a live studio audience.
>>
>> Thanks to Alia Atlas for nudging me to think about this more.
>>
>> Spencer
>>
>> p.s. If you have feedback about what I'm thinking, I'd love for you to
>> share it, whether on this list, privately to me, to the 2015 Nomcom,
>> or to other Nomcom-eligible IETF participants when you're asking them
>> to to sign the recall petition ;-)
>>
>> (*) http://en.wikipedia.org/wiki/Tug_of_war
>
>
>
>


From brian.e.carpenter@gmail.com  Tue Jan 28 15:11:40 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BC31A029E for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 15:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYbWRnpzJNK7 for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 15:11:36 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id C18EB1A0270 for <ietf@ietf.org>; Tue, 28 Jan 2014 15:11:36 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id p10so944347pdj.31 for <ietf@ietf.org>; Tue, 28 Jan 2014 15:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=0Gz6VQrU7xSBqShvhFDMKUzyzr7ZmzUeyTCqjCknrR0=; b=xWwNa6c1IOwc/DSdCak7rhe66Soe90MAYFZ2wa3iWeHfCtYPwAkO5UXoRSv4o4tL79 07iyI2N3gFTm8hyjY/seBE32uqtZIlcuQUFDSetzocWxnx2bVb1hi3H7y0vZFK9jR7iM RiICqomV+qfOfIegdjiABigmCtuRezuRsEsLLCOLsqdU0+19WmjyFqFIEMEposv97uFy ehuHP/PDHcznriifgt1ZUo4YPifHu7bv36LTYxlGjWxYG6+95BODgK8xzySt5iAr5w2r 4TXUck5t9Qnf51/+mpl1HK3tm27xdbPI94a5g9dFfdj55yJcEoIJJ0jkRT4xgihNV/Z2 Ab1w==
X-Received: by 10.66.159.132 with SMTP id xc4mr4277418pab.27.1390950694242; Tue, 28 Jan 2014 15:11:34 -0800 (PST)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id om6sm403751pbc.43.2014.01.28.15.11.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 28 Jan 2014 15:11:33 -0800 (PST)
Message-ID: <52E83926.1060909@gmail.com>
Date: Wed, 29 Jan 2014 12:11:34 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com>
In-Reply-To: <52E80FA9.5020704@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jan 2014 23:11:40 -0000

Hi Spencer,

I think there's a bit more to be said, though.

The goal is to make the Internet work better, not to make
private networks work better. Actually RFC 3935 defines
the IETF's scope as: "protocols and practices for which
secure and scalable implementations are expected to have
wide deployment and interoperation on the Internet, or to
form part of the infrastructure of the Internet."

So if there are two ways of doing something, one of which
works globally and one of which only works locally, the choice
is a no-brainer. If a local-only solution comes up to the IESG,
I think the first question is "Why isn't there a globally
applicable solution to this problem?". Then the second question
is "Why is this on the standards track, rather than being an
informational document for the record?". And the third question
is "Why is this better as an IETF document rather than an
Independent Submission?".

There may be perfectly good answers to those questions, but
IMHO they need to be asked.

Regards
   Brian

On 29/01/2014 09:14, Spencer Dawkins wrote:
> Disclaimer - I'm one of the ADs who will be balloting your documents
> until at least March 2015, but I'm only one of 15 ADs, and haven't
> talked about this with the rest of the IESG.
> 
> The past week has brought me yet another example of an idea that could
> be a good idea, but not under every possible set of conditions, being
> evaluated as if we had to decide whether it was a good idea in all
> cases, or a bad idea. This might sound familiar to you, but if it does,
> let's not talk about that specific case.
> 
> The longer (and more painfully) we talk during Last Call, the more
> details we unearth that help me to understand what document
> authors/working groups are thinking, and that's good, but if it was less
> painful, that would be even better.
> 
> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
> Statements, as distinct from Technical Specifications, and says (among
> other things):
> 
>    An Applicability Statement specifies how, and under what
>    circumstances, one or more TSs may be applied to support a particular
>    Internet capability.
> 
> ...
> 
>    An AS may describe particular methods of using a TS in a restricted
>    "domain of applicability", such as Internet routers, terminal
>    servers, Internet systems that interface to Ethernets, or datagram-
>    based database servers.
> 
> 
> Speaking only for myself, I don't expect Proposed Standards to be
> perfect, and to work perfectly in every situation, but if a
> specification doesn't describe any limits on applicability, I'm going to
> be evaluating it as if it will be used on the open Internet (that's what
> the "I" in "IETF" stands for).
> 
> If a draft says it's only intended to be used within an IP subnet, I'd
> evaluate it differently. I might ask that the authors/working group
> consider what the TTL should be set to, so that what starts out within
> an IP subnet stays within an IP subnet, but (to use one actual example)
> we wouldn't be arguing about whether it's OK to send 32K max-length
> packets over an arbitrary Internet path at line rate without getting any
> feedback about path capacity - there are probably paths where that would
> work, and there are definitely paths where it would not.
> 
> If a draft says it's only intended to be used on provisioned, managed
> internetwork links subject to SLA monitoring, I'd evaluate it differently.
> 
> If a draft says "this is a hack, intended for use on old hardware that
> can't do $X", I'd evaluate it differently.
> 
> There are other limited-use scenarios that would make me evaluate a
> draft differently.
> 
> None of this is a guaranteed pass, but it would help me a lot. It would
> likely help other reviewers, too.
> 
> So, if you don't intend for your draft to be used on the global
> Internet, please say so! As per
> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
> put an Applicability Statement in a different draft; just a section that
> says (another actual example) "this has been tested using these
> parameters on a lightly-loaded LAN, and it works there", that is more
> helpful than a tug of war(*) about whether something is a good idea or a
> bad idea in all situations, in front of a live studio audience.
> 
> Thanks to Alia Atlas for nudging me to think about this more.
> 
> Spencer
> 
> p.s. If you have feedback about what I'm thinking, I'd love for you to
> share it, whether on this list, privately to me, to the 2015 Nomcom, or
> to other Nomcom-eligible IETF participants when you're asking them to to
> sign the recall petition ;-)
> 
> (*) http://en.wikipedia.org/wiki/Tug_of_war
> 

From ned+ietf@mauve.mrochek.com  Tue Jan 28 16:02:35 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B57A1A028F for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 16:02:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPeGwwMagD3Q for <ietf@ietfa.amsl.com>; Tue, 28 Jan 2014 16:02:33 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id BC9391A03CA for <ietf@ietf.org>; Tue, 28 Jan 2014 16:02:33 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P3OYIKUQNK003OBB@mauve.mrochek.com> for ietf@ietf.org; Tue, 28 Jan 2014 15:57:25 -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 <01P3NP4TEOIO0000AS@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 28 Jan 2014 15:57:18 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P3OYII11RI0000AS@mauve.mrochek.com>
Date: Tue, 28 Jan 2014 15:51:17 -0800 (PST)
Subject: Re: Third party disclosures and NDAs (Re: Problem with new Note Well )
In-reply-to: "Your message dated Tue, 28 Jan 2014 11:01:24 -0800 (PST)" <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <alpine.LRH.2.01.1401281053460.5198@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
Cc: wgchairs@ietf.org, ietf@ietf.org, "Mulligan, Geoff" <geoff.mulligan@nist.gov>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 00:02:35 -0000

> On Tue, 28 Jan 2014, Dale R. Worley wrote:

> > > From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
> > >
> > > So because I know of IPR that someone else has and is not disclosing
> > > and because I cannot legally disclose it - I can't continue to
> > > participate in the discussion doesn't seem right.  I'm not the
> > > holder of the IPR that isn't being disclosed, but I'm penalized.
> >
> > That is the rule (it seems).  It's hard on you, but the IETF seems to
> > hold to the principle "You can't participate if you know of
> > undisclosed IPR claims", presumably so the participant can't secretly
> > steer the solution to include or exclude the IPR.  It's a choice of
> > who gets inconvenienced, you or the IETF?
> >
> > Indeed, if the IETF didn't have this rule, a company with undisclosed
> > IPR could hire consultants, put them under NDA, and have them advocate
> > at the IETF to include the IPR in standards.

> Um ... if you are currently working for the IPR owner as a consultant,
> it isn't 3rd party IPR ... if one is being paid to advocate related
> to IPR, it is not the case Geoff outlined.

Quite right.

There's also the case of where you're consulting for two entities, one of which
has IP they won't let you disclose and the other wants you to do IETF work in
an area touched on by that IP.

But here both the involvement in the IETF as well as this being an IP matter
are really just red herrings. This is a conflict of interest between the two
entities you're consulting for, nothing more and nothing less. And once again
it sucks to be you, but handling such conflicts of interest is decidedly out of
scope.

There are certainly other variations, leading to the general observation that
the more interests you're involved with and/or representing, the more
constrained you're going to be. That's ineluctable.

				Ned

From chair@ietf.org  Tue Jan 28 16:56:26 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3881A1A0378; Tue, 28 Jan 2014 16:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IP3cFkKx9QU5; Tue, 28 Jan 2014 16:56:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 190F61A0290; Tue, 28 Jan 2014 16:56:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Chair <chair@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Request for IETF Mentoring Program Volunteers
X-Test-IDTracker: no
X-IETF-IDTracker: 4.90.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140129005624.6209.33988.idtracker@ietfa.amsl.com>
Date: Tue, 28 Jan 2014 16:56:24 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 00:56:26 -0000

Hi all,

In London we will once again be running the IETF Mentoring Program. We
will be pairing IETF participants who are new or otherwise in need of
guidance with existing IETF participants. Unlike at previous meetings,
anyone will be able to sign up for a mentor regardless of how many
meetings they have attended. The goal is to provide a resource for
participants that can assist them with integrating into the IETF
community.  Mentors and newcomers will be paired prior to IETF 89.

We're seeking IETF participants to volunteer to be mentors. As a mentor,
we would ask that you be willing to assist your mentoring participant
before, during, and (hopefully) after IETF 89.  The actual level of
interaction will be driven by an agreement between the mentor and the
mentoring participant. Additionally, we would need a brief description of
your areas of expertise, technical interests, and conversational languages.

 A description of the Mentor Program (including a FAQ describing
how to volunteer to be a mentor) is available:

http://www.ietf.org/resources/mentoring-program.html.

 Anyone interested in being a mentor who has not previously signed up
should follow the sign-up instructions contained in the above URL. If you
have previously signed up as a mentor, you do not need to sign up and you
should have received an email requesting that you confirm whether you will
be available to mentor in London.

Please consider volunteering. The more volunteers we have, the stronger
the program will be!

Regards,
IETF Chair

From Chris.Dearlove@baesystems.com  Wed Jan 29 02:29:18 2014
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21A6B1A04D9 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 02:29:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.435
X-Spam-Level: 
X-Spam-Status: No, score=-7.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XK-qVJGnBCbL for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 02:29:10 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id E034E1A04D6 for <ietf@ietf.org>; Wed, 29 Jan 2014 02:29:05 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,741,1384300800"; d="scan'208";a="344995098"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 29 Jan 2014 10:29:02 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-IronPort-AV: E=Sophos;i="4.95,741,1384300800"; d="scan'208";a="44150426"
Received: from glkxh0003v.greenlnk.net ([10.109.2.34]) by baemasodc005.greenlnk.net with ESMTP; 29 Jan 2014 10:29:02 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.106]) by GLKXH0003V.GREENLNK.net ([10.109.2.34]) with mapi id 14.03.0174.001; Wed, 29 Jan 2014 10:29:02 +0000
To: Hector Santos <hsantos@isdg.net>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: RE: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
Thread-Topic: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
Thread-Index: AQHPHHNORtIQDqqAq0OXjp8Di0/XRZqbfamQ
Date: Wed, 29 Jan 2014 10:29:02 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40245F28@GLKXM0002V.GREENLNK.net>
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net>
In-Reply-To: <52E826A3.3040605@isdg.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 10:29:18 -0000

SSdtIG5vdCBzdXJlIG1vcmUgY2F0ZWdvcmllcyBpcyB3aGF0IHdlIHdhbnQuDQoNCkkgaGF2ZSBv
YnNlcnZlZCBhbGwgb2YgdGhlIGZvbGxvd2luZyAobm90IGF0IHRoZSBzYW1lIHRpbWUsIHRob3Vn
aCBzb21lIHdlcmUpIGZyb20gcGVvcGxlIG5vdCBmYW1pbGlhciB3aXRoIHRoZSBJRVRGIGFuZCBS
RkNzLCBhbHRob3VnaCBpbnZlc3RlZCBpbiBvciB1c2luZyBSRkNzOg0KLSBBc3N1bWluZyB0aGF0
IGFsbCBSRkNzIGFyZSBzdGFuZGFyZHMuDQotIEFzc3VtaW5nIHRoYXQgb25seSBTdGFuZGFyZHMg
bWF0dGVyLCB0aGF0IFByb3Bvc2VkIFN0YW5kYXJkcyBhbmQgRHJhZnQgc3RhbmRhcmRzIGFyZW4n
dCBpbXBvcnRhbnQuDQotIEFzc3VtaW5nIHRoYXQgRHJhZnQgU3RhbmRhcmQgaXMgYSBjYXRlZ29y
eSBiZWxvdyBQcm9wb3NlZCBTdGFuZGFyZC4NCi0gUmVjb2duaXNpbmcgdGhhdCB0aGVyZSBhcmUg
c3RhbmRhcmRzIGFuZCBub3Qtc3RhbmRhcmRzLCBidXQgbm90IGRpc3Rpbmd1aXNoaW5nIGluIGFu
eSB3YXkgYmV0d2VlbiBTdGFuZGFyZCwgRHJhZnQgU3RhbmRhcmQgYW5kIFByb3Bvc2VkIFN0YW5k
YXJkIChjYWxsaW5nIGFsbCBvZiB0aGVtIFN0YW5kYXJkcykuDQotIEp1c3QgcGxhaW4gY29uZnVz
ZWQuDQoNCihBbmQgdGhlIGNvbmNlcHQgb2YgQkNQIGlzIHByb2JhYmx5IGNvbXBsZXRlbHkgdW5r
bm93biB0byBhbnlvbmUgdGhpbmtpbmcgYW55IG9mIHRoZSBhYm92ZS4pDQoNCkFub3RoZXIgY2F0
ZWdvcnkgaXNuJ3QgZ29pbmcgdG8gaGVscCBoZXJlLg0KDQotLSANCkNocmlzdG9waGVyIERlYXJs
b3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVuZ2luZWVyLCBDb21tdW5pY2F0aW9ucyBHcm91cA0KQ29t
bXVuaWNhdGlvbnMsIE5ldHdvcmtzIGFuZCBJbWFnZSBBbmFseXNpcyBDYXBhYmlsaXR5DQpCQUUg
U3lzdGVtcyBBZHZhbmNlZCBUZWNobm9sb2d5IENlbnRyZQ0KV2VzdCBIYW5uaW5nZmllbGQgUm9h
ZCwgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBDTTIgOEhOLCBVSw0KVGVsOiArNDQgMTI0NSAy
NDIxOTTCoHwgIEZheDogKzQ0IDEyNDUgMjQyMTI0DQpjaHJpcy5kZWFybG92ZUBiYWVzeXN0ZW1z
LmNvbSB8IGh0dHA6Ly93d3cuYmFlc3lzdGVtcy5jb20NCg0KQkFFIFN5c3RlbXMgKE9wZXJhdGlv
bnMpIExpbWl0ZWQNClJlZ2lzdGVyZWQgT2ZmaWNlOiBXYXJ3aWNrIEhvdXNlLCBQTyBCb3ggODcs
IEZhcm5ib3JvdWdoIEFlcm9zcGFjZSBDZW50cmUsIEZhcm5ib3JvdWdoLCBIYW50cywgR1UxNCA2
WVUsIFVLDQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcyBObzogMTk5NjY4Nw0KDQotLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogaWV0ZiBbbWFpbHRvOmlldGYtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIEhlY3RvciBTYW50b3MNClNlbnQ6IDI4IEphbnVhcnkgMjAx
NCAyMTo1Mw0KVG86IFNwZW5jZXIgRGF3a2lucw0KQ2M6IElFVEYgZGlzY3Vzc2lvbiBsaXN0DQpT
dWJqZWN0OiBNYWtlIGl0IGEgUHJvcG9zZWQgTWV0aG9kIHJhdGhlciB0aGFuIFByb3Bvc2VkIFN0
YW5kYXJkIFtSZTogV2hlbiBpcyBhbiBpZGVhIGEgZ29vZCBpZGVhP10NCg0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSEgV0FSTklORyAhIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gVGhpcyBtZXNzYWdl
IG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlzYXRpb24sIGVpdGhlciBmcm9tIGFu
IGV4dGVybmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUgaW50ZXJuZXQuDQpDb25zaWRlciBjYXJlZnVs
bHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0YWNo
bWVudHMgb3IgcmVwbHkuDQpGb2xsb3cgdGhlICdSZXBvcnQgU3VzcGljaW91cyBFbWFpbHMnIGxp
bmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9uIHJlcG9ydGluZyBzdXNwaWNpb3Vz
IGVtYWlsIG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KSSB0aGluayB0aGUgSUVURiBuZWVkcyBhIG5ldyBzdGF0dXMg
Zm9yIGRvY3VtZW50IHN1Ym1pc3Npb25zLiANClNvbWV0aGluZyBtb3JlIGFkdmFuY2VkIHRoYW4g
ZXhwZXJpbWVudGFsIGFuZCBpbmZvcm1hdGlvbmFsIGJ1dCBsZXNzIHRoYW4gYSBQcm9wb3NlZCBT
dGFuZGFyZCAoUFMpIHBlcmhhcHMgY2FsbGVkIFByb3Bvc2VkIE1ldGhvZCAoUE0pLiAgQSBQTSB3
aWxsIG5lZWQgdG93YXJkcyBhbiBJTSAoSW50ZXJuZXQgTWV0aG9kKS4NCg0KV2hlbiBzb21ldGhp
bmcgaXMgd3JpdHRlbiBhcyBhICJzdGFuZGFyZCIgdGhlcmUgdGVuZHMgdG8gYmUgYSBoaWdoZXIg
YmFyIHRvIGRvIHNvbWV0aGluZyBkaWZmZXJlbnQuIEl0IHByb3ZpZGVzIGEgc2Vuc2Ugb2YgZmlu
YWwgY2xvc3VyZSBhbmQgcmVzb2x1dGlvbiBhbmQgdGhpcyBpcyB3aGVyZSBtYW55IGRlYmF0ZXMs
IGNvbmZsaWN0IG9mIGludGVyZXN0LCBhcmUgYmFzZWQsIHdoZXJlIElFVEYgQXBwZWFscyBhcmUg
bW9yZSBwcm9iYWJsZS4gIFdobyBjYXJlcyBpZiBhIHByb3Bvc2FsIGlzIGluZm9ybWF0aW9uYWwg
b3IgZXhwZXJpbWVudD8gIE5vdCByZWFsbHkgc3Ryb25nIGVub3VnaCBhbmQgdG9vIHJpc2t5IGZv
ciBhZG9wdGlvbi4gQSAic3RhbmRhcmQiIGhhcyBhIGhpZ2hlciBiYXIgdG8gcmVhY2ggYnV0IGFs
c28gdG8gY2hhbmdlIGFzIHdlbGwuDQoNCkkgYmVsaWV2ZSBhIFBNIHdpbGwgaGVscCB3aXRoIHRo
ZSBhY2NlcHRhbmNlIG9mIHByb3Bvc2FscyB0aGF0IG1heSBmaXQgaW4gdGhpcyBpbiBiZXR3ZWVu
IGNhdGVnb3J5IHdoZXJlIGl0IG1heSBub3QgYmUgY29uc2lkZXJlZCBhIHN0YW5kYXJkIG1hdGVy
aWFsLCB5ZXQsIGl0IG9mZmVycyBzb21lIGxldmVsIG9mIHRlY2hub2xvZ3kgdGhhdCBpcyBiZXlv
bmQgYmVpbmcgaW5mb3JtYXRpb25hbCBvciBleHBlcmltZW50YWwsIGkuZS4gYSBzZWdtZW50IG9m
IHRoZSBtYXJrZXQgcGxhY2UgaXMgdXNpbmcgaXQsIHRlY2hub2xvZ3kgbGVhZGVyIHdpc2hlcyB0
byBkb2N1bWVudCBhIHByb3ByaWV0YXJ5IG1ldGhvZCBhcyBhbiBvcGVuIGFuZCBwdWJsaWMgZG9t
YWluIG1ldGhvZC4NCg0KSSBiZWxpZXZlIGEgUE0gbWF5IGFsc28gaGVscCBhbGxldmlhdGUgdGhl
ICJnb29kIHZzIGJhZCIgZGViYXRlcywgDQphbGxvdyBmb3IgZ3JlYXRlciBhZG9wdGlvbiBleHBs
b3JhdGlvbnMuICAgSXQgdGVsbHMgdGhlIGluZHVzdHJ5IHRoYXQgDQp3ZSBmb3VuZCBzb21ldGhp
bmcgdXNlZnVsLCBhbHJlYWR5IHVzZWQgaW4gcHJhY3RpY2UsIHRyeSBpdCB5b3Vyc2VsZiwgYnV0
IGl0cyBzdGlsbCBub3Qgc29tZXRoaW5nIHRoZSBJRVRGIHRvIGJlIHRoZSAic3RhbmRhcmQiIG1l
dGhvZC4NCg0KQW55d2F5LCB0aGUgUE0gaWRlYSBzZWVtcyB0byBjb21lIGJhY2sgbW9yZSBhbmQg
bW9yZSBhcyB5b3Ugc2VlIG1vcmUgb2YgdGhlc2UgImhhbGYtYmFrZWQiIHByb3Bvc2VkIHN0YW5k
YXJkcyB3aGVuIHRoZXkgc2VlbXMgdG8gYmUgbW9yZSANCmV4cGVyaW1lbnRhbCBvciBpbmZvcm1h
dGlvbmFsIGluIG5hdHVyZS4gICBZb3UgaGF2ZSBnb29kIGlkZWFzIG91dCANCnRoZXJlIHRoYXQg
ZG8gbmVlZCB0byBiZSBkb2N1bWVudGVkLiAgQnV0IHlvdSBkb24ndCBuZWVkIHRvIG1ha2UgdGhl
bSBQcm9wb3NlZCBTdGFuZGFyZHMgd2hpY2ggaGFzIGEgdHJlbWVuZG91c2x5IGhpZ2ggYmFyIGFu
ZCBoaWdoZXIgc291cmNlIGZvciBtYWpvciBkZWJhdGVzLCBlc3BlY2lhbGx5IHdoZW4gdGhlcmUg
YXJlIGNvbmZsaWN0cy4NCg0KLS0NCkhMUw0KDQpPbiAxLzI4LzIwMTQgMzoxNCBQTSwgU3BlbmNl
ciBEYXdraW5zIHdyb3RlOg0KPiBEaXNjbGFpbWVyIC0gSSdtIG9uZSBvZiB0aGUgQURzIHdobyB3
aWxsIGJlIGJhbGxvdGluZyB5b3VyIGRvY3VtZW50cw0KPiB1bnRpbCBhdCBsZWFzdCBNYXJjaCAy
MDE1LCBidXQgSSdtIG9ubHkgb25lIG9mIDE1IEFEcywgYW5kIGhhdmVuJ3QNCj4gdGFsa2VkIGFi
b3V0IHRoaXMgd2l0aCB0aGUgcmVzdCBvZiB0aGUgSUVTRy4NCj4NCj4gVGhlIHBhc3Qgd2VlayBo
YXMgYnJvdWdodCBtZSB5ZXQgYW5vdGhlciBleGFtcGxlIG9mIGFuIGlkZWEgdGhhdCBjb3VsZA0K
PiBiZSBhIGdvb2QgaWRlYSwgYnV0IG5vdCB1bmRlciBldmVyeSBwb3NzaWJsZSBzZXQgb2YgY29u
ZGl0aW9ucywgYmVpbmcNCj4gZXZhbHVhdGVkIGFzIGlmIHdlIGhhZCB0byBkZWNpZGUgd2hldGhl
ciBpdCB3YXMgYSBnb29kIGlkZWEgaW4gYWxsDQo+IGNhc2VzLCBvciBhIGJhZCBpZGVhLiBUaGlz
IG1pZ2h0IHNvdW5kIGZhbWlsaWFyIHRvIHlvdSwgYnV0IGlmIGl0DQo+IGRvZXMsIGxldCdzIG5v
dCB0YWxrIGFib3V0IHRoYXQgc3BlY2lmaWMgY2FzZS4NCj4NCj4gVGhlIGxvbmdlciAoYW5kIG1v
cmUgcGFpbmZ1bGx5KSB3ZSB0YWxrIGR1cmluZyBMYXN0IENhbGwsIHRoZSBtb3JlDQo+IGRldGFp
bHMgd2UgdW5lYXJ0aCB0aGF0IGhlbHAgbWUgdG8gdW5kZXJzdGFuZCB3aGF0IGRvY3VtZW50DQo+
IGF1dGhvcnMvd29ya2luZyBncm91cHMgYXJlIHRoaW5raW5nLCBhbmQgdGhhdCdzIGdvb2QsIGJ1
dCBpZiBpdCB3YXMNCj4gbGVzcyBwYWluZnVsLCB0aGF0IHdvdWxkIGJlIGV2ZW4gYmV0dGVyLg0K
Pg0KPiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMyMDI2I3NlY3Rpb24tMy4yIGRlc2Ny
aWJlcyBBcHBsaWNhYmlsaXR5DQo+IFN0YXRlbWVudHMsIGFzIGRpc3RpbmN0IGZyb20gVGVjaG5p
Y2FsIFNwZWNpZmljYXRpb25zLCBhbmQgc2F5cyAoYW1vbmcNCj4gb3RoZXIgdGhpbmdzKToNCj4N
Cj4gICAgIEFuIEFwcGxpY2FiaWxpdHkgU3RhdGVtZW50IHNwZWNpZmllcyBob3csIGFuZCB1bmRl
ciB3aGF0DQo+ICAgICBjaXJjdW1zdGFuY2VzLCBvbmUgb3IgbW9yZSBUU3MgbWF5IGJlIGFwcGxp
ZWQgdG8gc3VwcG9ydCBhIHBhcnRpY3VsYXINCj4gICAgIEludGVybmV0IGNhcGFiaWxpdHkuDQo+
DQo+IC4uLg0KPg0KPiAgICAgQW4gQVMgbWF5IGRlc2NyaWJlIHBhcnRpY3VsYXIgbWV0aG9kcyBv
ZiB1c2luZyBhIFRTIGluIGEgcmVzdHJpY3RlZA0KPiAgICAgImRvbWFpbiBvZiBhcHBsaWNhYmls
aXR5Iiwgc3VjaCBhcyBJbnRlcm5ldCByb3V0ZXJzLCB0ZXJtaW5hbA0KPiAgICAgc2VydmVycywg
SW50ZXJuZXQgc3lzdGVtcyB0aGF0IGludGVyZmFjZSB0byBFdGhlcm5ldHMsIG9yIGRhdGFncmFt
LQ0KPiAgICAgYmFzZWQgZGF0YWJhc2Ugc2VydmVycy4NCj4NCj4NCj4gU3BlYWtpbmcgb25seSBm
b3IgbXlzZWxmLCBJIGRvbid0IGV4cGVjdCBQcm9wb3NlZCBTdGFuZGFyZHMgdG8gYmUNCj4gcGVy
ZmVjdCwgYW5kIHRvIHdvcmsgcGVyZmVjdGx5IGluIGV2ZXJ5IHNpdHVhdGlvbiwgYnV0IGlmIGEN
Cj4gc3BlY2lmaWNhdGlvbiBkb2Vzbid0IGRlc2NyaWJlIGFueSBsaW1pdHMgb24gYXBwbGljYWJp
bGl0eSwgSSdtIGdvaW5nDQo+IHRvIGJlIGV2YWx1YXRpbmcgaXQgYXMgaWYgaXQgd2lsbCBiZSB1
c2VkIG9uIHRoZSBvcGVuIEludGVybmV0ICh0aGF0J3MNCj4gd2hhdCB0aGUgIkkiIGluICJJRVRG
IiBzdGFuZHMgZm9yKS4NCj4NCj4gSWYgYSBkcmFmdCBzYXlzIGl0J3Mgb25seSBpbnRlbmRlZCB0
byBiZSB1c2VkIHdpdGhpbiBhbiBJUCBzdWJuZXQsIEknZA0KPiBldmFsdWF0ZSBpdCBkaWZmZXJl
bnRseS4gSSBtaWdodCBhc2sgdGhhdCB0aGUgYXV0aG9ycy93b3JraW5nIGdyb3VwDQo+IGNvbnNp
ZGVyIHdoYXQgdGhlIFRUTCBzaG91bGQgYmUgc2V0IHRvLCBzbyB0aGF0IHdoYXQgc3RhcnRzIG91
dCB3aXRoaW4NCj4gYW4gSVAgc3VibmV0IHN0YXlzIHdpdGhpbiBhbiBJUCBzdWJuZXQsIGJ1dCAo
dG8gdXNlIG9uZSBhY3R1YWwNCj4gZXhhbXBsZSkgd2Ugd291bGRuJ3QgYmUgYXJndWluZyBhYm91
dCB3aGV0aGVyIGl0J3MgT0sgdG8gc2VuZCAzMksNCj4gbWF4LWxlbmd0aCBwYWNrZXRzIG92ZXIg
YW4gYXJiaXRyYXJ5IEludGVybmV0IHBhdGggYXQgbGluZSByYXRlDQo+IHdpdGhvdXQgZ2V0dGlu
ZyBhbnkgZmVlZGJhY2sgYWJvdXQgcGF0aCBjYXBhY2l0eSAtIHRoZXJlIGFyZSBwcm9iYWJseQ0K
PiBwYXRocyB3aGVyZSB0aGF0IHdvdWxkIHdvcmssIGFuZCB0aGVyZSBhcmUgZGVmaW5pdGVseSBw
YXRocyB3aGVyZSBpdA0KPiB3b3VsZCBub3QuDQo+DQo+IElmIGEgZHJhZnQgc2F5cyBpdCdzIG9u
bHkgaW50ZW5kZWQgdG8gYmUgdXNlZCBvbiBwcm92aXNpb25lZCwgbWFuYWdlZA0KPiBpbnRlcm5l
dHdvcmsgbGlua3Mgc3ViamVjdCB0byBTTEEgbW9uaXRvcmluZywgSSdkIGV2YWx1YXRlIGl0IGRp
ZmZlcmVudGx5Lg0KPg0KPiBJZiBhIGRyYWZ0IHNheXMgInRoaXMgaXMgYSBoYWNrLCBpbnRlbmRl
ZCBmb3IgdXNlIG9uIG9sZCBoYXJkd2FyZSB0aGF0DQo+IGNhbid0IGRvICRYIiwgSSdkIGV2YWx1
YXRlIGl0IGRpZmZlcmVudGx5Lg0KPg0KPiBUaGVyZSBhcmUgb3RoZXIgbGltaXRlZC11c2Ugc2Nl
bmFyaW9zIHRoYXQgd291bGQgbWFrZSBtZSBldmFsdWF0ZSBhDQo+IGRyYWZ0IGRpZmZlcmVudGx5
Lg0KPg0KPiBOb25lIG9mIHRoaXMgaXMgYSBndWFyYW50ZWVkIHBhc3MsIGJ1dCBpdCB3b3VsZCBo
ZWxwIG1lIGEgbG90LiBJdA0KPiB3b3VsZCBsaWtlbHkgaGVscCBvdGhlciByZXZpZXdlcnMsIHRv
by4NCj4NCj4gU28sIGlmIHlvdSBkb24ndCBpbnRlbmQgZm9yIHlvdXIgZHJhZnQgdG8gYmUgdXNl
ZCBvbiB0aGUgZ2xvYmFsDQo+IEludGVybmV0LCBwbGVhc2Ugc2F5IHNvISBBcyBwZXINCj4gaHR0
cDovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMjAyNiNzZWN0aW9uLTMuMywgaXQncyBub3QgbmVj
ZXNzYXJ5IHRvDQo+IHB1dCBhbiBBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCBpbiBhIGRpZmZlcmVu
dCBkcmFmdDsganVzdCBhIHNlY3Rpb24NCj4gdGhhdCBzYXlzIChhbm90aGVyIGFjdHVhbCBleGFt
cGxlKSAidGhpcyBoYXMgYmVlbiB0ZXN0ZWQgdXNpbmcgdGhlc2UNCj4gcGFyYW1ldGVycyBvbiBh
IGxpZ2h0bHktbG9hZGVkIExBTiwgYW5kIGl0IHdvcmtzIHRoZXJlIiwgdGhhdCBpcyBtb3JlDQo+
IGhlbHBmdWwgdGhhbiBhIHR1ZyBvZiB3YXIoKikgYWJvdXQgd2hldGhlciBzb21ldGhpbmcgaXMg
YSBnb29kIGlkZWEgb3INCj4gYSBiYWQgaWRlYSBpbiBhbGwgc2l0dWF0aW9ucywgaW4gZnJvbnQg
b2YgYSBsaXZlIHN0dWRpbyBhdWRpZW5jZS4NCj4NCj4gVGhhbmtzIHRvIEFsaWEgQXRsYXMgZm9y
IG51ZGdpbmcgbWUgdG8gdGhpbmsgYWJvdXQgdGhpcyBtb3JlLg0KPg0KPiBTcGVuY2VyDQo+DQo+
IHAucy4gSWYgeW91IGhhdmUgZmVlZGJhY2sgYWJvdXQgd2hhdCBJJ20gdGhpbmtpbmcsIEknZCBs
b3ZlIGZvciB5b3UgdG8NCj4gc2hhcmUgaXQsIHdoZXRoZXIgb24gdGhpcyBsaXN0LCBwcml2YXRl
bHkgdG8gbWUsIHRvIHRoZSAyMDE1IE5vbWNvbSwNCj4gb3IgdG8gb3RoZXIgTm9tY29tLWVsaWdp
YmxlIElFVEYgcGFydGljaXBhbnRzIHdoZW4geW91J3JlIGFza2luZyB0aGVtDQo+IHRvIHRvIHNp
Z24gdGhlIHJlY2FsbCBwZXRpdGlvbiA7LSkNCj4NCj4gKCopIGh0dHA6Ly9lbi53aWtpcGVkaWEu
b3JnL3dpa2kvVHVnX29mX3dhcg0KDQoNCg0KDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgpUaGlzIGVtYWlsIGFuZCBh
bnkgYXR0YWNobWVudHMgYXJlIGNvbmZpZGVudGlhbCB0byB0aGUgaW50ZW5kZWQKcmVjaXBpZW50
IGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQK
cmVjaXBpZW50IHBsZWFzZSBkZWxldGUgaXQgZnJvbSB5b3VyIHN5c3RlbSBhbmQgbm90aWZ5IHRo
ZSBzZW5kZXIuCllvdSBzaG91bGQgbm90IGNvcHkgaXQgb3IgdXNlIGl0IGZvciBhbnkgcHVycG9z
ZSBub3IgZGlzY2xvc2Ugb3IKZGlzdHJpYnV0ZSBpdHMgY29udGVudHMgdG8gYW55IG90aGVyIHBl
cnNvbi4KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioK


From abdussalambaryun@gmail.com  Wed Jan 29 02:39:21 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8031A016A; Wed, 29 Jan 2014 02:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0B_4E0YNxDj; Wed, 29 Jan 2014 02:39:19 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id F3BE71A014C; Wed, 29 Jan 2014 02:39:18 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id x10so1553124pdj.11 for <multiple recipients>; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=H5TvdShZnT8eatK38c0OvSEsHvOwn/Q90eeBwyccKDQ=; b=KANCOR09MVGV1bn2N6s1MLKY0A/kRcQ27yKN7zzU731gs5vUBwmd/5u2TkOggxl/XI lFpZqbYDrI0FzCUXOQFIyR+W7nFm3QyA46AIFfauSG+4oqe5omCL1yu15WJrPtxTEFkP Q/RpFW1nprVb1WVhPZQxLo3XaVIv23iBejUwVAGXNVZFqw8VgpspCE5lWe3qJUT+VoRG bO7kq8jsDZDMzXQ3ctirDMtO3cTGFokIaJyG8LnTgp8LUNPqwiAdsZvSZAAlZdaNOr1e TIcTARjz3tIxW9AYay7zXb+rmL5wvczxDRjc472BRDlPMaV49XGOm/Vrs5ZzGhzp79Z7 HH0w==
MIME-Version: 1.0
X-Received: by 10.68.229.106 with SMTP id sp10mr7157438pbc.23.1390991956271; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 29 Jan 2014 02:39:16 -0800 (PST)
In-Reply-To: <52E69572.7000903@dcrocker.net>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net>
Date: Wed, 29 Jan 2014 11:39:16 +0100
Message-ID: <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
Subject: Re: Problem with new Note Well
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>, IESG IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 10:39:21 -0000

I agree with the suggestions below and that I never liked the note
well wordings. In addition, from Cullen's first message and others, it
seems like most IETF participants are not practicing or understandning
the note well. The reason may be because engineers are not good in
legal issues, so do we have a current legal advisor/position in IETF
organisation, or still IETF has no progress in legal experience, so we
will need to go back to external legal. Why IETF just leaves its
participants alone to do the legal advise but when it comes to their
works it encourages inputs? Does the note well consider all
countries/regions legal policies? Is it practical/agreeable for all
participants any where, or was it tested?

For me I don't agree with the way the note well is forced on all, it
needs more discussions between WGs and their Chairs, but no time for
it or no advisors or group discussion/meeting for legal issues (may be
only IESG decides for us so far which is never practical).

AB

On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> On 1/27/2014 8:17 AM, Jari Arkko wrote:
>> All - it is clear that you have a concern about the new note well text.
>> The problem has been well articulated;
>
>
> Jari, et al,
>
>
> There are a number of different problems, and only some of them have
> been articulated.  Worse, the problems include the IPR rules themselves,
> not just the Note Well:
>
>       0.  We have had IPR rules and a Note Well for many years and have
> revised both a number of times.  Normally, work we do that has been
> around that long warrants being called "mature", which means that it
> works well and is well understood.  The latest discussion demonstrates
> that that model does not apply to the IETF's IPR handling.  In fact, the
> exchange looks more like the disparities we see early in a working group
> effort, not what normally takes place after many years.
>
>       1. The participants in the discussion are extremely experienced
> with the IETF and with this topic.  Yet they demonstrated a strong
> /lack/ of rough consensus about what the /current/ IPR rules mean.
>
>       2.  The current rules are too complex for use by average
> engineers.  Engineers are not attorneys, nevermind IPR attorneys.  IPR
> is considered by attorneys to be an esoteric and difficult specialty.
> The IETF's IPR rules need to be simple and simply stated, if we expect
> average engineers to understand them.
>
>       3.  The current IPR rules appear to impose an unreasonable demand
> on IETF participants, such as conflicting with employment arrangements.
> (And if the demand is reasonable, then what is noteworthy is that
> someone who has read this latest IETF discussion has developed the
> impression that it isn't.  See point 6.)
>
>       4.  The current Note Well is too complex and apparently erroneous.
>   (And if it is not erroneous, then what is noteworthy is that a serious
> attempt to review the thread has resulted in someone coming to the
> conclusion that the Note Well is erroneous.  See point 6.)
>
>       5.  Expecting an average IETF engineer to consult 4 different
> BCPs, in order to understand what is required of them is not reasonable.
>   Nor is all each document relevant.  So, in effect, the references are
> overly broad, as well as too complicated. (See point 6.)
>
>       6.  Having a range of experienced, diligent IETF participants
> demonstrate substantive disagreement about the meaning of our current
> IPR rules undermines whatever utility the rules might have.  It sets up
> a litigation argument that the participant did not understand the rules,
> citing this thread as demonstrating that others also don't.
>
>
> The remedies we need are not just with the Note Well.  We need to fix
> the IPR rules too.
>
>
>       0.  We need to establish clear and compelling community rough
> consensus about the meaning of our IPR rules and the utility of our Note
> Well.  We are currently /very/ far from being able to do that.
>
>       1.  We need a consensus statement that describes our 'model' of an
> IETF particpant, in terms of what is reasonable for them to know and
> what is reasonable for them to be responsible for and what is reasonable
> for them to do, especially within the real time performance constraints
> of a working group meeting. The premise of that model needs to be
> extreme simplicity and clarity.  Any rules we assert need to be vetted
> against that model.  Our current arrangement requires an average
> engineer to be more knowledgeable and more diligent than is reasonable.
>   (By 'diligent' I'm not referring to intent; I'm referring to classic
> human factors usability limits.)
>
>       2.  One of the distinctions in the latest discussion is between
> having the Note Well attempt to summarize what the IPR rules are, versus
> having it merely declare that we have IPR rules and point the reader to
> them.  For summary instruments, like a Note Well, the latter approach
> makes far more sense.
>
>       3.  We need all of the IPR rules for IETF participation to be in a
> single, simple, clear document that is easily understandable by an
> average engineer. (See point 1.)
>
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

From abdussalambaryun@gmail.com  Wed Jan 29 02:53:09 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BEAC1A014C for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 02:53:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6GkuwQT0hg2j for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 02:53:07 -0800 (PST)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 142FE1A0188 for <ietf@ietf.org>; Wed, 29 Jan 2014 02:53:07 -0800 (PST)
Received: by mail-pd0-f177.google.com with SMTP id x10so1555799pdj.22 for <ietf@ietf.org>; Wed, 29 Jan 2014 02:53:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=EzApIFNRQhrnPkKQl01kCfRIoa+FNJyHMKRZf5Tn4jE=; b=k+LeSGM/alAmqcECH9gs2LP8Uy9B5pWtJlw56+NktwvWVhspo4PO1E6mv3Jc5OrDlq OVqWj8x3/ebSLNMqeTzr/vOk8Mg76kHuT2Tjei55lCEB0oPM3F78utV0yrC0GoAf9R98 zw7W0SzE2AGjyCP4bwrnGkhdTmh6YXfF600TNQMi5DqgyWhsEy/FP3gzuEt4uq3QTVbI h8YAQpJtDpGT6nGx3QhddlyIGKVVFjhkB1HhitPNoVsVMowrBPm7/ekVh/PhVXGviVST OI/PgX54ujSTBVX63OGCS9OMebzVTo6ACpmIbGYr0A89AQpsmoKngDen3STVzjLY5Rrz 1Fjg==
MIME-Version: 1.0
X-Received: by 10.68.12.74 with SMTP id w10mr7253678pbb.39.1390992784325; Wed, 29 Jan 2014 02:53:04 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 29 Jan 2014 02:53:04 -0800 (PST)
In-Reply-To: <52E80FA9.5020704@gmail.com>
References: <52E80FA9.5020704@gmail.com>
Date: Wed, 29 Jan 2014 11:53:04 +0100
Message-ID: <CADnDZ895be1EdhEGa1BympPY2WUU+TaFFJK0+9CpZ3a63yJ06A@mail.gmail.com>
Subject: Re: When is an idea a good idea?
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 10:53:09 -0000

Hi Spencer,

Yes, that is right. I mentioned that many time but still no much
following, this process problem affects the end users of our
protocols. IESG needs to force ADs and WGs to describe very well in
the applicabilitity section, or the use case of such draft-protocol.
How does the IESG evaluate such drafts if there are not much
explainations in the use of the examined protocol? Could we evaluate
IESG (including previous IESG) in its RFC outputs based on your
questions?, Therefore, I suggest your ideas should be presented to
IESG and IETF WGs Chairs, how they are evaluating drafts, what is
their methodology, or Is there any
methodology/idea/format/basic-questions?

Even reviewers should focus on your questions, but I don't think we
can force them as long as we are short with reviewers.

AB

On 1/28/14, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
> Disclaimer - I'm one of the ADs who will be balloting your documents
> until at least March 2015, but I'm only one of 15 ADs, and haven't
> talked about this with the rest of the IESG.
>
> The past week has brought me yet another example of an idea that could
> be a good idea, but not under every possible set of conditions, being
> evaluated as if we had to decide whether it was a good idea in all
> cases, or a bad idea. This might sound familiar to you, but if it does,
> let's not talk about that specific case.
>
> The longer (and more painfully) we talk during Last Call, the more
> details we unearth that help me to understand what document
> authors/working groups are thinking, and that's good, but if it was less
> painful, that would be even better.
>
> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
> Statements, as distinct from Technical Specifications, and says (among
> other things):
>
>     An Applicability Statement specifies how, and under what
>     circumstances, one or more TSs may be applied to support a particular
>     Internet capability.
>
> ...
>
>     An AS may describe particular methods of using a TS in a restricted
>     "domain of applicability", such as Internet routers, terminal
>     servers, Internet systems that interface to Ethernets, or datagram-
>     based database servers.
>
>
> Speaking only for myself, I don't expect Proposed Standards to be
> perfect, and to work perfectly in every situation, but if a
> specification doesn't describe any limits on applicability, I'm going to
> be evaluating it as if it will be used on the open Internet (that's what
> the "I" in "IETF" stands for).
>
> If a draft says it's only intended to be used within an IP subnet, I'd
> evaluate it differently. I might ask that the authors/working group
> consider what the TTL should be set to, so that what starts out within
> an IP subnet stays within an IP subnet, but (to use one actual example)
> we wouldn't be arguing about whether it's OK to send 32K max-length
> packets over an arbitrary Internet path at line rate without getting any
> feedback about path capacity - there are probably paths where that would
> work, and there are definitely paths where it would not.
>
> If a draft says it's only intended to be used on provisioned, managed
> internetwork links subject to SLA monitoring, I'd evaluate it differently.
>
> If a draft says "this is a hack, intended for use on old hardware that
> can't do $X", I'd evaluate it differently.
>
> There are other limited-use scenarios that would make me evaluate a
> draft differently.
>
> None of this is a guaranteed pass, but it would help me a lot. It would
> likely help other reviewers, too.
>
> So, if you don't intend for your draft to be used on the global
> Internet, please say so! As per
> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
> put an Applicability Statement in a different draft; just a section that
> says (another actual example) "this has been tested using these
> parameters on a lightly-loaded LAN, and it works there", that is more
> helpful than a tug of war(*) about whether something is a good idea or a
> bad idea in all situations, in front of a live studio audience.
>
> Thanks to Alia Atlas for nudging me to think about this more.
>
> Spencer
>
> p.s. If you have feedback about what I'm thinking, I'd love for you to
> share it, whether on this list, privately to me, to the 2015 Nomcom, or
> to other Nomcom-eligible IETF participants when you're asking them to to
> sign the recall petition ;-)
>
> (*) http://en.wikipedia.org/wiki/Tug_of_war
>

From abdussalambaryun@gmail.com  Wed Jan 29 03:05:12 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AF661A024C for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 03:05:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUj-LPda2gQz for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 03:05:10 -0800 (PST)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 29CCC1A0235 for <ietf@ietf.org>; Wed, 29 Jan 2014 03:05:10 -0800 (PST)
Received: by mail-pa0-f48.google.com with SMTP id kx10so1633000pab.7 for <ietf@ietf.org>; Wed, 29 Jan 2014 03:05:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Z+zQwlxaJKZuNdF4tU7+QrH2PLzyUDgQ9lbkWE5M3oU=; b=YqBuDxNOzOrTq0BMQwshX5Eo2dnxNmL8hWi5GczjrX6/gtdFXb11eJne7KGohx48+i jqmIkokOZCSG5baGXyhKfyBCYBNeU91cbp1KzvmJcTdmultmPke+4zxj1+FseTtTKzAE o4XTUvxC/K46QfF22OL2ZSbn2pBzbFFtVRVBc8cOence4hK6mpynSWQB0ZZuK5/4q9EW HCM92WvDQ/G1Y2w1E9eNSLhEeLQnajhoEJ3kcz8DXVmVbzps1XG1CEWnZymDgVk4WVLd 1mMWiPFZeUU14GkFtq0jjSqlX6MAGHS7SXcEw1tyvjkRiG6Cg95taHJiXUQQpSpVvg7P I5oQ==
MIME-Version: 1.0
X-Received: by 10.68.164.4 with SMTP id ym4mr7328593pbb.53.1390993507427; Wed, 29 Jan 2014 03:05:07 -0800 (PST)
Received: by 10.68.0.104 with HTTP; Wed, 29 Jan 2014 03:05:07 -0800 (PST)
In-Reply-To: <52E826A3.3040605@isdg.net>
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net>
Date: Wed, 29 Jan 2014 12:05:07 +0100
Message-ID: <CADnDZ8_shvdF3qSCc-HL=z0wZs3k-V-1CKWT0cWvpbKuQ8sXmQ@mail.gmail.com>
Subject: Re: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 11:05:12 -0000

Hi Hector,

The most importance is its use, or practice. So could it be a less
than a BCP, as a proposed practice (PIP), so we can use it as an
initial-proposal-BCP or an initial-proposal-standard. As we seen the
draft-farrell-perpass-attack-04 draft that SHOULD be an informational
or SHOULD be less than a BCP but still not in the right submission
path (because as we see there is a missing path).

The IETF needs to focus more on proposed used standards, best
practices, and real use cases. That will focus ideas and proposals in
the right directions.

AB

On 1/28/14, Hector Santos <hsantos@isdg.net> wrote:
> I think the IETF needs a new status for document submissions.
> Something more advanced than experimental and informational but less
> than a Proposed Standard (PS) perhaps called Proposed Method (PM).  A
> PM will need towards an IM (Internet Method).
>
> When something is written as a "standard" there tends to be a higher
> bar to do something different. It provides a sense of final closure
> and resolution and this is where many debates, conflict of interest,
> are based, where IETF Appeals are more probable.  Who cares if a
> proposal is informational or experiment?  Not really strong enough and
> too risky for adoption. A "standard" has a higher bar to reach but
> also to change as well.
>
> I believe a PM will help with the acceptance of proposals that may fit
> in this in between category where it may not be considered a standard
> material, yet, it offers some level of technology that is beyond being
> informational or experimental, i.e. a segment of the market place is
> using it, technology leader wishes to document a proprietary method as
> an open and public domain method.
>
> I believe a PM may also help alleviate the "good vs bad" debates,
> allow for greater adoption explorations.   It tells the industry that
> we found something useful, already used in practice, try it yourself,
> but its still not something the IETF to be the "standard" method.
>
> Anyway, the PM idea seems to come back more and more as you see more
> of these "half-baked" proposed standards when they seems to be more
> experimental or informational in nature.   You have good ideas out
> there that do need to be documented.  But you don't need to make them
> Proposed Standards which has a tremendously high bar and higher source
> for major debates, especially when there are conflicts.
>
> --
> HLS
>
> On 1/28/2014 3:14 PM, Spencer Dawkins wrote:
>> Disclaimer - I'm one of the ADs who will be balloting your documents
>> until at least March 2015, but I'm only one of 15 ADs, and haven't
>> talked about this with the rest of the IESG.
>>
>> The past week has brought me yet another example of an idea that could
>> be a good idea, but not under every possible set of conditions, being
>> evaluated as if we had to decide whether it was a good idea in all
>> cases, or a bad idea. This might sound familiar to you, but if it
>> does, let's not talk about that specific case.
>>
>> The longer (and more painfully) we talk during Last Call, the more
>> details we unearth that help me to understand what document
>> authors/working groups are thinking, and that's good, but if it was
>> less painful, that would be even better.
>>
>> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
>> Statements, as distinct from Technical Specifications, and says (among
>> other things):
>>
>>     An Applicability Statement specifies how, and under what
>>     circumstances, one or more TSs may be applied to support a particular
>>     Internet capability.
>>
>> ...
>>
>>     An AS may describe particular methods of using a TS in a restricted
>>     "domain of applicability", such as Internet routers, terminal
>>     servers, Internet systems that interface to Ethernets, or datagram-
>>     based database servers.
>>
>>
>> Speaking only for myself, I don't expect Proposed Standards to be
>> perfect, and to work perfectly in every situation, but if a
>> specification doesn't describe any limits on applicability, I'm going
>> to be evaluating it as if it will be used on the open Internet (that's
>> what the "I" in "IETF" stands for).
>>
>> If a draft says it's only intended to be used within an IP subnet, I'd
>> evaluate it differently. I might ask that the authors/working group
>> consider what the TTL should be set to, so that what starts out within
>> an IP subnet stays within an IP subnet, but (to use one actual
>> example) we wouldn't be arguing about whether it's OK to send 32K
>> max-length packets over an arbitrary Internet path at line rate
>> without getting any feedback about path capacity - there are probably
>> paths where that would work, and there are definitely paths where it
>> would not.
>>
>> If a draft says it's only intended to be used on provisioned, managed
>> internetwork links subject to SLA monitoring, I'd evaluate it
>> differently.
>>
>> If a draft says "this is a hack, intended for use on old hardware that
>> can't do $X", I'd evaluate it differently.
>>
>> There are other limited-use scenarios that would make me evaluate a
>> draft differently.
>>
>> None of this is a guaranteed pass, but it would help me a lot. It
>> would likely help other reviewers, too.
>>
>> So, if you don't intend for your draft to be used on the global
>> Internet, please say so! As per
>> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
>> put an Applicability Statement in a different draft; just a section
>> that says (another actual example) "this has been tested using these
>> parameters on a lightly-loaded LAN, and it works there", that is more
>> helpful than a tug of war(*) about whether something is a good idea or
>> a bad idea in all situations, in front of a live studio audience.
>>
>> Thanks to Alia Atlas for nudging me to think about this more.
>>
>> Spencer
>>
>> p.s. If you have feedback about what I'm thinking, I'd love for you to
>> share it, whether on this list, privately to me, to the 2015 Nomcom,
>> or to other Nomcom-eligible IETF participants when you're asking them
>> to to sign the recall petition ;-)
>>
>> (*) http://en.wikipedia.org/wiki/Tug_of_war
>
>
>
>
>

From kre@munnari.OZ.AU  Wed Jan 29 03:29:01 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD0B1A02BA; Wed, 29 Jan 2014 03:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.336
X-Spam-Level: 
X-Spam-Status: No, score=0.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZhMviMin6Ojx; Wed, 29 Jan 2014 03:29:00 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id 7E6AF1A014C; Wed, 29 Jan 2014 03:28:59 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0TBQigl009171; Wed, 29 Jan 2014 18:27:05 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0TBQ3Ue003385; Wed, 29 Jan 2014 18:26:08 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: ietf@ietf.org
Subject: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Jan 2014 18:26:03 +0700
Message-ID: <4111.1390994763@perseus.noi.kre.to>
Cc: wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 11:29:01 -0000

    Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
    From:        worley@ariadne.com (Dale R. Worley)
    Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>

  | Indeed, if the IETF didn't have this rule, a company with undisclosed
  | IPR could hire consultants, put them under NDA, and have them advocate
  | at the IETF to include the IPR in standards.

Much easier, for such nefarious company, is simply to hire (as employees, or
consultants, it makes no difference) people to "represent" the company's
interest at the IETF, and make sure that those people are unaware of any
and all IPR claims that the company may possess.

In that case, the person attending the IETF cannot possibly disclose the
IPR, as they're unaware of it, the company can't be expected to disclose
anything - companies don't attend the IETF (except as sponsors perhaps, and
I am fairly sure that no-one asks the sponsors to reveal all their IPR before
we take their money) the people all attend as individuals.

We may not like this kind of behaviour, but other than completely changing
the way the IETF is designed to operate (to actually have company's explicitly
become members, and enter into membership agreements, with only representatives
of member companies permitted to participate) which I don't think anyone wants,
there really is nothing that can be done about it.

Now this by no means guarantees that the courts won't take a dim view of
this kind of behaviour, if an attempt is later made to enforce the IPR claim,
but it won't be because of any breach of IETF rules - there hasn't been any
in this scenario.

All of these problems are brought about by yet another instance of the
IETF attempting to fix something that is simply way outside our competence
or ability to fix.  It isn't surprising - after all, the IETF is made up
(mostly) of engineers, and when an engineer sees something broken, the
natural inclination is to attempt to fix it.  But sometimes the underlying
problem is something that simply cannot be fixed by any amount of engineering.
Hidden IPR is one of those, the problem is in people's attitudes - how
willing they are to put their own interests ahead of the general community
interest.   You simply cannot engineer a fix to this, it is a social issue.

Everything beyond simply encouraging people to disclose any IPR that they're
aware of, which they are able to disclose - or if unable, to attempt to
encourage those who are able to disclose it, is beyond what is rational for
the IETF to attempt to do, and what's more, the "rules" that people spend
so much time debating (people waste so much time debating) are essentially
useless, as they have no enforcement mechanism.  What exactly is the IETF
supposed to do, if it is revealed, some time later, that some IPR was not
disclosed by a participant in some discussions that they could have
disclosed?   As I understand it, there is simply some hope that some court
will use that to invalidate the IPR claim - but nothing I've seen suggests
that the "rule" is actually necessary for that, and even if it is, as above,
it is trivial to work around.

These days the IETF is spending far too much time on issues that have nothing
to do with actually improving the protocols in use on the internet, and
should go back to doing what it can do, and simply allow the rest to be 
handled in the places designed to handle such things.   Stepping back, and
saying "I cannot fix that problem" seems like being defeated, but it isn't,
it is just accepting reality.  That is good engineering.

kre


From synp71@live.com  Wed Jan 29 04:43:06 2014
Return-Path: <synp71@live.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9C21A03F8; Wed, 29 Jan 2014 04:43:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wH_2-TAKIB8C; Wed, 29 Jan 2014 04:43:05 -0800 (PST)
Received: from blu0-omc2-s34.blu0.hotmail.com (blu0-omc2-s34.blu0.hotmail.com [65.55.111.109]) by ietfa.amsl.com (Postfix) with ESMTP id EEC051A0375; Wed, 29 Jan 2014 04:43:04 -0800 (PST)
Received: from BLU0-SMTP152 ([65.55.111.72]) by blu0-omc2-s34.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Jan 2014 04:43:02 -0800
X-TMN: [cqoIPkFlIovQgaYouUsOebbZ3/tFCxLr]
X-Originating-Email: [synp71@live.com]
Message-ID: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>
Received: from ynir-MBA.local ([194.29.32.131]) by BLU0-SMTP152.phx.gbl over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 29 Jan 2014 04:43:00 -0800
Date: Wed, 29 Jan 2014 14:42:55 +0200
From: Yoav Nir <synp71@live.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Robert Elz <kre@munnari.OZ.AU>, ietf@ietf.org
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms040406050608070901010903"
X-OriginalArrivalTime: 29 Jan 2014 12:43:00.0323 (UTC) FILETIME=[A4B6AB30:01CF1CEF]
Cc: wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 12:43:06 -0000

--------------ms040406050608070901010903
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 29/1/14 1:26 PM, Robert Elz wrote:
>      Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
>      From:        worley@ariadne.com (Dale R. Worley)
>      Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>
>
>    | Indeed, if the IETF didn't have this rule, a company with undisclo=
sed
>    | IPR could hire consultants, put them under NDA, and have them advo=
cate
>    | at the IETF to include the IPR in standards.
>
> Much easier, for such nefarious company, is simply to hire (as employee=
s, or
> consultants, it makes no difference) people to "represent" the company'=
s
> interest at the IETF, and make sure that those people are unaware of an=
y
> and all IPR claims that the company may possess.

That's not so nefarious. If those people are unaware of the IPR claims,=20
they're unable to steer the working group towards infringing technology. =

I suspect that some companies are hiring people for their "IETF=20
experience" and intentionally keeping them away from the R&D side of the =

company.

We may not like the idea of a professional IETF-er any more than people=20
used to like the idea of a professional athlete. For years professional=20
were banned from the Olympics. But I don't think such people or their=20
participation are a problem.


--------------ms040406050608070901010903
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIO4zCC
BJ0wggOFoAMCAQICEDQ96SusJzT/j8s0lPvMcFQwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4H0MIHxMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zARBgNVHSAECjAIMAYGBFUdIAAwRAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2Ny
bC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMDUGCCsGAQUFBwEB
BCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTANBgkqhkiG9w0B
AQUFAAOCAQEAAbyc42MosPMxAcLfe91ioAGdIzEPnJJzU1HqH0z61p/Eyi9nfngzD3QWuZGH
kfWKJvpkcADYHvkLBGJQh5OB1Nr1I9s0u4VWtHA0bniDNx6FHMURFZJfhxe9rGr98cLRzIlf
sXzwPlHyNfN87GCYazor4O/fs32G67Ub9VvsonyYE9cAULnRLXPeA3h04QWFMV7LmrmdlMa5
lDd1ctxE+2fo8PolHlKn2iXpR+CgxzygTrEKNvt3SJ/vl4r7tP7jlBSog7xcLT/SYHFg7sJx
ggzpiDbj2iC0o6BsqpZLuICOdcpJB/Y7FLrf3AXZn9vgsuZNoHgm5+ctbn9fxh6IFTCCBRow
ggQCoAMCAQICEG0Z6qcZT2ozIuYiMnqqcd4wDQYJKoZIhvcNAQEFBQAwga4xCzAJBgNVBAYT
AlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkxHjAcBgNVBAoTFVRo
ZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2VydHJ1c3QuY29t
MTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgRW1h
aWwwHhcNMTEwNDI4MDAwMDAwWhcNMjAwNTMwMTA0ODM4WjCBkzELMAkGA1UEBhMCR0IxGzAZ
BgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRp
b24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJKEhFtLV5jUXi+LpOFAyKNTWF9mZfEyTvefMn1V0HhMVbdClOD5J3EHxcZppLkyxPFAGpDM
J1Zifxe1cWmu5SAb5MtjXmDKokH2auGj/7jfH0htZUOMKi4rYzh337EXrMLaggLW1DJq1Gdv
IBOPXDX65VSAr9hxCh03CgJQU2yVHakQFLSZlVkSMf8JotJM3FLb3uJAAVtIaN3FSrTg7SQf
Oq9xXwfjrL8UO7AlcWg99A/WF1hGFYE8aIuLgw9teiFX5jSw2zJ+40rhpVJyZCaRTqWSD//g
sWD9Gm9oUZljjRqLpcxCm5t9ImPTqaD8zp6Q30QZ9FxbNboW86eb/8ECAwEAAaOCAUswggFH
MB8GA1UdIwQYMBaAFImCZ33EnSZwAEu0UEh83j2uBG59MB0GA1UdDgQWBBR6E04AdFvGeGNk
J8Ev4qBbvHnFezAOBgNVHQ8BAf8EBAMCAQYwEgYDVR0TAQH/BAgwBgEB/wIBADARBgNVHSAE
CjAIMAYGBFUdIAAwWAYDVR0fBFEwTzBNoEugSYZHaHR0cDovL2NybC51c2VydHJ1c3QuY29t
L1VUTi1VU0VSRmlyc3QtQ2xpZW50QXV0aGVudGljYXRpb25hbmRFbWFpbC5jcmwwdAYIKwYB
BQUHAQEEaDBmMD0GCCsGAQUFBzAChjFodHRwOi8vY3J0LnVzZXJ0cnVzdC5jb20vVVROQWRk
VHJ1c3RDbGllbnRfQ0EuY3J0MCUGCCsGAQUFBzABhhlodHRwOi8vb2NzcC51c2VydHJ1c3Qu
Y29tMA0GCSqGSIb3DQEBBQUAA4IBAQCF1r54V1VtM39EUv5C1QaoAQOAivsNsv1Kv/avQUn1
G1rF0q0bc24+6SZ85kyYwTAo38v7QjyhJT4KddbQPTmGZtGhm7VNm2+vKGwdr+XqdFqo2rHA
8XV6L566k3nK/uKRHlZ0sviN0+BDchvtj/1gOSBH+4uvOmVIPJg9pSW/ve9g4EnlFsjrP0OD
8ODuDcHTzTNfm9C9YGqzO/761Mk6PB/tm/+bSTO+Qik5g+4zaS6CnUVNqGnagBsePdIaXXxH
maWbCG0SmYbWXVcHG6cwvktJRLiQfsrReTjrtDP6oDpdJlieYVUYtCHVmdXgQ0BCML7qpeeU
0rD+83X5f27nMIIFIDCCBAigAwIBAgIRAJLy3rLPGBD9qh6TW+ZG9DowDQYJKoZIhvcNAQEF
BQAwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNV
BAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01P
RE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTMxMTE3
MDAwMDAwWhcNMTQxMTE3MjM1OTU5WjAgMR4wHAYJKoZIhvcNAQkBFg9zeW5wNzFAbGl2ZS5j
b20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCow0TXP0M95fIMY0Fsd3xpZj55
m1mkkKhUWLjVtQcd57MyVmBZNQkAmxp9PrzqdHw5eIIBn1EI9foIoynEnUSZzv6pIEXAqdYu
xBH0AdvjoPCzWb9uYrqBtbmxnLh9k9ox1pVJG4hit6WEpK+LZ7uvLj5GUWMdmzghC/+fVEZS
W8U62xlhd8Hq8ded9bfqjM4psDgqUubjcCkMIUnkD9yuXhzfzwF0wwtD66vXrUe8T4/m6XHO
iIqvvVMjzYyKrdLE7zuPyDcDjkxLCCdi2j4c44anq8Pj/yEh5JGU0XSKSfwm2m0UDHj7P/6u
B74JwiAyMtqWzdQBHVOphHKDI0ZTAgMBAAGjggHfMIIB2zAfBgNVHSMEGDAWgBR6E04AdFvG
eGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUq+f5Y55gheJJpWtJDEPf6j2uzhQwDgYDVR0PAQH/
BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUC
MBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsG
AQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEygSqBI
hkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlvbmFu
ZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0dHA6
Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJl
RW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAaBgNV
HREEEzARgQ9zeW5wNzFAbGl2ZS5jb20wDQYJKoZIhvcNAQEFBQADggEBACRvTZSZMhI7HrJr
jTpnm5FZXyYwJYVhhc643/94hv8pxAQzIY6vH+BlVwmG4Z0Dt6vWYwaUUYdGmvlH0bti8aql
JPe4fUgTxbDlTldhOYfISl3ky9+4CEPg4QvX6tOGIusOrvaIszGUIdvKHzvYM4ZapdTxyFCt
oe1RXq/17ifvIklgmuh+QcB1xNBmE3lBNj+Vy8xLvsAQlqf9ZAIcBNL2yQGCaBcr6XoR24/D
oCNCTAOCR/J2nN/okuGsEF+kvxP/BCPBnDph9coFLNOEwR4ZataT6H4vq0fwGxm5SROTDYis
SUTKc+YYKY2RllEwOxX1NZUSmISuGKrGhr2aCaUxggQcMIIEGAIBATCBqTCBkzELMAkGA1UE
BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEa
MBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0
aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAJLy3rLPGBD9qh6TW+ZG9DowCQYF
Kw4DAhoFAKCCAkcwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcN
MTQwMTI5MTI0MjU1WjAjBgkqhkiG9w0BCQQxFgQUxvQU4CBXXYr92WWw9Ehz00OzMdYwbAYJ
KoZIhvcNAQkPMV8wXTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4G
CCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCB
ugYJKwYBBAGCNxAEMYGsMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBN
YW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRl
ZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVt
YWlsIENBAhEAkvLess8YEP2qHpNb5kb0OjCBvAYLKoZIhvcNAQkQAgsxgayggakwgZMxCzAJ
BgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZv
cmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50
IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEQCS8t6yzxgQ/aoek1vmRvQ6
MA0GCSqGSIb3DQEBAQUABIIBACMUeQXYelaKtK+KN1v9fhA229xINtwSiyi8ozgyrI4/Ip5x
p3zNLW1uigyzhicp1EmpN+mIVWLHiJoJOMSC6SA9Vl02kmzPu/h9gIj1QuaQKsTjjam8CFGg
fmJmOCumI99a6nrihpX5iV9okWMunBoIE4T65wKJJocs8SbHCiokmTfOQevLwHsJG6uBIzki
3Ccis7LcMNrvqQZtLOXeiZLwpXsit7VnBNlD3/1QPanFXRPoLpDjaTEJaHvOcTlekE5IwNqn
Lm9NXRh74REF3L0+EVsBKOPXM06SsdNLt0hgdzZ1IwbWoT995IIwg1XeL0caaumeJtAVxUyX
oehGo1sAAAAAAAA=
--------------ms040406050608070901010903--

From narten@us.ibm.com  Wed Jan 29 05:12:20 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 561631A0207 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 05:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.436
X-Spam-Level: 
X-Spam-Status: No, score=-7.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X3y5O7gwyH6T for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 05:12:16 -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 23AB61A01C1 for <ietf@ietf.org>; Wed, 29 Jan 2014 05:12:15 -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>; Wed, 29 Jan 2014 06:12:12 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 29 Jan 2014 06:12:11 -0700
Received: from b03cxnp08028.gho.boulder.ibm.com (b03cxnp08028.gho.boulder.ibm.com [9.17.130.20]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 91CEF1FF003F; Wed, 29 Jan 2014 06:12:10 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp08028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0TDCAI21442112; Wed, 29 Jan 2014 14:12:10 +0100
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0TDCAro015570; Wed, 29 Jan 2014 06:12:10 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-3-183.mts.ibm.com [9.65.3.183]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0TDC98C015461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jan 2014 06:12:09 -0700
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s0TDC8TK009724; Wed, 29 Jan 2014 08:12:08 -0500
Date: Wed, 29 Jan 2014 08:12:08 -0500
Message-ID: <m3ha8n6ifr.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Robert Elz <kre@munnari.OZ.AU>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14012913-0928-0000-0000-0000060FDAC1
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 13:12:20 -0000

At Wed, 29 Jan 2014 18:26:03 +0700, Robert Elz wrote:

> Much easier, for such nefarious company, is simply to hire (as employees, or
> consultants, it makes no difference) people to "represent" the company's
> interest at the IETF, and make sure that those people are unaware of any
> and all IPR claims that the company may possess.

And doing this could even be a violation of our rules (for the IPR
holder at least), depending on the details.

RFC 3668 says:

   l. "Reasonably and personally known": means something an individual
      knows personally or, because of the job the individual holds,
      would reasonably be expected to know.  This wording is used to
      indicate that an organization cannot purposely keep an individual
      in the dark about patents or patent applications just to avoid the
      disclosure requirement.  But this requirement should not be
      interpreted as requiring the IETF Contributor or participant (or
      his or her represented organization, if any) to perform a patent
      search to find applicable IPR.

Thomas


From scott.brim@gmail.com  Wed Jan 29 05:28:34 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A2C1A0230 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 05:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9z3AQhAwOctM for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 05:28:32 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 5467E1A020D for <ietf@ietf.org>; Wed, 29 Jan 2014 05:28:32 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so1910026obb.7 for <ietf@ietf.org>; Wed, 29 Jan 2014 05:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9Pc7x7hn+3phXK7aFvluS0zY+KrprMLVZ/qoASGwurM=; b=Gc/jFKJY4C2ff2T9rF/bgCDxnIXeahAE5PNiI7xgiUoV3h6dR+yXIzNdgITqleZ23+ 8ljIc6ZoC/6votjFYNaXW790+Wm5aeWH5gR262MNhOZc2dNYIkWwtnWE5LAzomlQw2Qc /FqqbEi+xXUbTJKko22wBvoU4LzbWVvq8/Rad1Xs8S01QOWBd0VulWJUuueY+dZZ+VKF 6kvCAkBTcBTDml+Bt3pMQN0fz+4zwoQlx4UJYo4Zp/8NzcMoumgHUINJLM3/O0oUqzkU C8iCgnjRBjOhHwHKvdb5KhYpIi7DPDjhasASKWE6un7a5Gucc5eHiQmoZneXGmMB8Ifn 01Hw==
MIME-Version: 1.0
X-Received: by 10.60.56.200 with SMTP id c8mr300590oeq.80.1391002109415; Wed, 29 Jan 2014 05:28:29 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Wed, 29 Jan 2014 05:28:29 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Wed, 29 Jan 2014 05:28:29 -0800 (PST)
In-Reply-To: <52E83926.1060909@gmail.com>
References: <52E80FA9.5020704@gmail.com> <52E83926.1060909@gmail.com>
Date: Wed, 29 Jan 2014 08:28:29 -0500
Message-ID: <CAPv4CP--CC_L7Asrdf0LKCYhQA+5JtvmwVwhM2nyO0pZur58Gw@mail.gmail.com>
Subject: Re: When is an idea a good idea?
From: Scott Brim <scott.brim@gmail.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e015370949d17bf04f11beaea
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 13:28:34 -0000

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

Yes. When applicability is declared to have a narrow scope, a draft
deserves *more* attention, to ensure it really will stay scoped and not be
used globally, to ensure it wouldn't actually have global use with some
tweaking, and clearly to ensure there isn't a global approach that could
fit as well with tweaking.

Once upon a time our scope was easy, everyone who participated in the IETF
had common interests. These days we maintain ourselves on a slippery slope,
supporting scoped use cases (there are clear cases where special
application is much better) and struggling against tremendous forces trying
to fragment the Internet. We need to continue to put out extra effort to
help others keep from sliding farther down that slope than they need to.

Scott

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

<p dir=3D"ltr">Yes. When applicability is declared to have a narrow scope, =
a draft deserves *more* attention, to ensure it really will stay scoped and=
 not be used globally, to ensure it wouldn&#39;t actually have global use w=
ith some tweaking, and clearly to ensure there isn&#39;t a global approach =
that could fit as well with tweaking. </p>

<p dir=3D"ltr">Once upon a time our scope was easy, everyone who participat=
ed in the IETF had common interests. These days we maintain ourselves on a =
slippery slope, supporting scoped use cases (there are clear cases where sp=
ecial application is much better) and struggling against tremendous forces =
trying to fragment the Internet. We need to continue to put out extra effor=
t to help others keep from sliding farther down that slope than they need t=
o.</p>

<p dir=3D"ltr">Scott</p>

--089e015370949d17bf04f11beaea--

From kre@munnari.OZ.AU  Wed Jan 29 06:05:38 2014
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C6A1A0375; Wed, 29 Jan 2014 06:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.336
X-Spam-Level: 
X-Spam-Status: No, score=0.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyDxOXyV8srD; Wed, 29 Jan 2014 06:05:37 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id A74211A0371; Wed, 29 Jan 2014 06:05:36 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0TE2PeN010020; Wed, 29 Jan 2014 21:02:46 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0TE1EBL005738; Wed, 29 Jan 2014 21:01:29 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: Yoav Nir <synp71@live.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
In-Reply-To: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>
References: <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl> <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 29 Jan 2014 21:01:14 +0700
Message-ID: <8982.1391004074@perseus.noi.kre.to>
Cc: wgchairs@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 14:05:38 -0000

    Date:        Wed, 29 Jan 2014 14:42:55 +0200
    From:        Yoav Nir <synp71@live.com>
    Message-ID:  <BLU0-SMTP15291D6479F17C5A697960DB1AC0@phx.gbl>

  | If those people are unaware of the IPR claims,
  | they're unable to steer the working group towards infringing technology.

No, the people are aware of all the technology, they just have no idea
there's any patents (or other IPR) involved.  They can easily (and genuinely)
advocate some great new technology that would solve a problem, without
having the slightest idea that their company is planning on later asserting
its IPR and claiming royalties.

  | I suspect that some companies are hiring people for their "IETF
  | experience" and intentionally keeping them away from the R&D side of the
  | company.

Yes, I think you're right, this has been happening for some time now.

  | We may not like the idea of a professional IETF-er any more than people
  | used to like the idea of a professional athlete.

I don't think that's a good analogy.   There's nothing wrong in
principle with organisations having people whose job it is to interact
with all the appropriate SDOs (after all, that allows the actual R&D
people to do their jobs instead of constantly being side tracked by
nonsense like IETF IPR rules...) but for the IETF, too much of this is
not a good thing.  The problem is that if the actual developers of
whatever is relevant are in a meeting when the technology is being discussed,
they (hopefully) know what are the real issues and problems, and what are
irrelevant side issues that don't really matter.  The professional SDO
attendee tends not to be closely involved enough with the development
and reasons for it, and so will more often simply advocate their company's
way of doing things, regardless whether it is on a point where it really
matters, or one where it really doesn't.


In another reply, Thomas Narten <narten@us.ibm.com> said:

  | And doing this could even be a violation of our rules (for the IPR holder at
  | least), depending on the details.

Violation of the rules by whom?  The excerpt you quoted clearly says that
people are not required to go do patent searches to find out whether IPR
might exists, so clearly the attendees (in the situation I postulated)
are not violating any rules.

And the company has (according to IETF theory anyway) no relationship with
the IETF at all - IETF rules and procedures cannot possibly be relevant to
random outside organisations.  Note that the company does not accept the
IETF rules, or tick the box on the registration form, or however it is
done these days, and the company does not join any mailing lists etc - and
certainly is not participating in any discussions, just their unknowing
employees.

Or consider a slightly different scenario - consider a company with some
new (and just recently subject of a patent application) technology that
they'd (for obvious reasons) like to become widely used.  The company then
hires a consultant (or two, or three) to evaluate possible future uses of
the technology.  The consultants are told nothing about the patent application
(which after all, has no bearing on what they've been asked to consult about).

One (or perhaps more) of the consultants asks the company "Have you considered
submitting this to the IETF, it could solve a problem they're having ..."
to which the company replies "We know nothing about that, but we have no
objections if you think it would be useful for them".

The consultant (on his own dime) then attends an IETF meeting, and submits
this new technology to the IETF.

What rules do you think have been broken there?  What rules could possibly 
exist that would make a difference?

Perhaps you might believe that the consultant should have explicitly asked
the company if there were any patents or patent applications on this
technology?  Perhaps he/she should have, and didn't.  Or perhaps that
question was asked, and the company said no.   That might have even been
truthful at the time - it might have been that very question that inspired
the company to file its patent application.

This is all very messy, and once again, dealing with all these issues is
way beyond what network engineers should even be attempting.

Simply make it clear that knowing about IPR, and licensing terms, allows
the IETF to build better protocols that are more useful to the network as
a whole, and so disclosing IPR to the IETF is a good thing to do.  Those
companies (I suspect the majority, especially of the bigger ones) will
(and have in the past) comply, and file the relevant disclosure.  The ones
that refuse are not likely to be swayed in any way by any IETF rules, and
particularly not ones that lack even a hint of any enforcement mechanism.

kre

ps: this will be my final message on this topic.  I don't want to encourage,
or contribute to, even more IETF time wasting on non-engineering issues.


From warren@kumari.net  Wed Jan 29 06:36:06 2014
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD741A03AB for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 06:36:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2QTzGE8hK-4 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 06:36:03 -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 6B4CA1A0280 for <ietf@ietf.org>; Wed, 29 Jan 2014 06:36:03 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id m15so3729777wgh.14 for <ietf@ietf.org>; Wed, 29 Jan 2014 06:35:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WckTosF0hsKdUZnvYUtueph9fuf/0E63XJPpCNxaAOM=; b=FFyDjXLkershC5Ui8Gcrz7JKCmwPnrEaL8t1zZdOQpT6/7iyqvPaFPoFQEa2H1pjlc zPCiW3iLNdTqW2/rwYsOnl31kfo5u1zl8dcZNvMIrXq7Ge7OEfZ+j6OP7WtZLmiPCUQM OdURljlBIQRgnt9qhnHG/MnZiE/5UPhj/LbjmR2OpXdL1ZEOCynyThjlXpjeQEZ1f5kS WBI91X4foDeO2x+f+RAHuQn+E5QpdvkyGP6JsQioaq7QA0FvCeBnj74wBS9zsv94C8Kh rm9gESQn9Z196hq+HyPbsnDcpMsYzsFbcmt+noG8HDKT1k11ZSvfY8BfU8xPtgW6jnuZ j1zw==
X-Gm-Message-State: ALoCoQlYoCU+m1yIT8xY3zNgyeJqYHViOG/nOHnv7sTUoa1rq1J+WVCq+zxvQeS92mYas5FrbyYs
MIME-Version: 1.0
X-Received: by 10.180.77.74 with SMTP id q10mr5984287wiw.39.1391006159620; Wed, 29 Jan 2014 06:35:59 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Wed, 29 Jan 2014 06:35:59 -0800 (PST)
X-Originating-IP: [31.55.61.62]
In-Reply-To: <BA197A34-7053-43CA-B0A6-19D264769910@vigilsec.com>
References: <CE9467A6.1087%karine.perset@icann.org> <EB54A1CD-5BDE-4FBE-930B-2B3103C32C81@shinkuro.com> <D9112687-832E-4B3A-9C7C-BD722041A4C7@vigilsec.com> <1FC796F8-5A1B-4930-BBF0-0C251A7B5355@shinkuro.com> <6A1627AB-D488-4496-B091-D8CEE928902B@vigilsec.com> <29e4fce546af4ecab5c758d24d4e60ca@BY2PR03MB269.namprd03.prod.outlook.com> <527003E3.8020505@cisco.com> <9F7F6E84-3ECC-4129-B105-136153D30E3C@vigilsec.com> <5270065E.7010305@cisco.com> <9524AFE7-1DEB-488E-B9B5-A79C0F7DA13D@vigilsec.com> <5270117B.5050809@cisco.com> <CB78FE0E-184B-4FB5-AA8B-48D2FFA7549D@vigilsec.com> <52701441.2050601@cisco.com> <7E10A87A-4A1E-44A4-9785-8A7353AAE117@vigilsec.com> <5788665A-DED5-4FE5-9A3D-9AD53A472877@iab.org> <2ECBAB99-9FE4-42C9-BF73-229B6E2C54F6@viagenie.ca> <6E69571E-3BF4-4255-9D9C-ECC80CFA4B1A@iab.org> <BA197A34-7053-43CA-B0A6-19D264769910@vigilsec.com>
Date: Wed, 29 Jan 2014 09:35:59 -0500
Message-ID: <CAHw9_iJmNu=aCSVHns_PgOhGzG18YEGAas3+hjJm69hQdwDzew@mail.gmail.com>
Subject: Re: Appointments for ICANN Technical Liaison Group
From: Warren Kumari <warren@kumari.net>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary=f46d043bdf6a0665da04f11cdc89
Cc: IETF <ietf@ietf.org>, IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 14:36:06 -0000

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

On Tuesday, January 28, 2014, Russ Housley <housley@vigilsec.com> wrote:

> Dear Colleagues,
>
> The IAB has selected Warren Kumari to serve a two-tear term on the ICANN
> TLG and selected Daniel Migault a one-tear term.


Hopefully it will be zero-tear terms for both Daniel and myself :-p

W



>  Thanks for your willingness to serve the community in this capacity.
>
> The IAB thanks all of the candidates.  This was a difficult decision with
> so many strong candidates.
>
> On behalf of the IAB,
> Russ Housley
> IAB Chair
>
>
>
> > Dear Colleagues,
> >
> > The IAB recently requested nominations to the ICANN Technical
> > Liaison Group (TLG).  We have a number of candidates, and we
> > are soliciting comment from the community on these candidates.
> >
> > The following candidates have put their names forward:
> >
> >  Marc Blanchet <marc.blanchet@viagenie.ca <javascript:;>>
> >  David Conrad <drc@virtualized.org <javascript:;>>
> >  Alex Deacon <Alex_Deacon@mpaa.org <javascript:;>>
> >  Geoff Huston <gih902@gmail.com <javascript:;>>
> >  Stephen Kent <kent@bbn.com <javascript:;>>
> >  Peter Koch <pk@denic.de <javascript:;>>
> >  Warren Kumari <warren@kumari.net <javascript:;>>
> >  John Levine <johnl@taugh.com <javascript:;>>
> >  Daniel Migault <mglt.biz@gmail.com <javascript:;>>
> >  Hassan Zaheer <hassanZaheer@gmail.com <javascript:;>>
> >
> > Please send your remarks in confidence about any or all candidates to
> > iab-chair@iab.org <javascript:;> and execd@iab.org <javascript:;>.  We
> thank you in advance for
> > your help.
> >
> > Best regards,
> > Russ Housley
> > IAB Chair
> >
> >
> >
> >> Dear Colleagues,
> >>
> >> The IAB (on behalf of the IETF) has been asked to supply two technical
> >> experts to ICANN Technical Liaison Group (TLG).  The ICANN Bylaws
> >> (Article XI-A, Section 2, Paragraph 6) asks the IETF, ITU-T, ETSI, and
> >> W3C to each provide two technical experts.  The technical experts are
> >> expected to be "familiar with the technical standards issues that are
> >> relevant to ICANN's activities." These eight experts are expected to be
> >> "available as necessary to determine, through an exchange of e-mail
> >> messages, where to direct a technical question from ICANN when ICANN
> >> does not ask a specific TLG organization directly.
> >>
> >> The ICANN bylaws can be found at
> >> http://www.icann.org/en/about/governance/bylaws.
> >>
> >> The IAB is asking the community for volunteers to serve on the ICANN
> TLG.
> >> If you are interested, please send a short e-mail to iab-chair at
> iab.org
> >> with a copy to execd at iab.org with your motivation and information
> >> concerning your familiarity with the IETF and ICANN as well as the other
> >> standards organizations represented on the TLG.  The deadline for
> >> volunteering is 17 Nov 2013.
> >>
> >> The IAB will select from the available candidates, taking into account
> >> the familiarity with ICANN and the IETF, their roles, and the IETF
> >> protocols.  While familiarity with ETSI, ITU-T, and W3C is also
> >> desirable, it is not required.  The selected candidates will serve on
> >> the ICANN TLG on personal title; however, the IAB will be looking for
> >> candidates who have an understanding of the interests of the technical
> >> community.
> >>
> >> The IAB will select one person for a one year term and select one person
> >> for a two year term.
> >>
> >> The ICANN TLG is expected to meet in person at or around the three ICANN
> >> meetings held each year.
> >>
> >> NOTE: ICANN does cover travel and hotel costs for a pre-determined
> number
> >> of days at each of the ICANN meetings.
> >>
> >> If you are willing to be considered or would like to nominate someone
> >> else for one of the TLG positions, please send an email to iab-chair at
> >> iab.org and execd at iab.org by 17 Nov 2013.
> >>
> >> On behalf of the IAB,
> >> Russ Housley
> >> IAB Chair
> >>
> >
>
>

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

<br><br>On Tuesday, January 28, 2014, Russ Housley &lt;<a href=3D"mailto:ho=
usley@vigilsec.com">housley@vigilsec.com</a>&gt; wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
Dear Colleagues,<br>
<br>
The IAB has selected Warren Kumari to serve a two-tear term on the ICANN TL=
G and selected Daniel Migault a one-tear term.=A0</blockquote><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
</blockquote><div><br></div><div>Hopefully it will be=A0zero-tear terms for=
 both Daniel and myself :-p</div><div><br></div><div>W<span></span></div><d=
iv><br></div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
=A0Thanks for your willingness to serve the community in this capacity.<br>
<br>
The IAB thanks all of the candidates. =A0This was a difficult decision with=
 so many strong candidates.<br>
<br>
On behalf of the IAB,<br>
Russ Housley<br>
IAB Chair<br>
<br>
<br>
<br>
&gt; Dear Colleagues,<br>
&gt;<br>
&gt; The IAB recently requested nominations to the ICANN Technical<br>
&gt; Liaison Group (TLG). =A0We have a number of candidates, and we<br>
&gt; are soliciting comment from the community on these candidates.<br>
&gt;<br>
&gt; The following candidates have put their names forward:<br>
&gt;<br>
&gt; =A0Marc Blanchet &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#3=
9;cvml&#39;, &#39;marc.blanchet@viagenie.ca&#39;)">marc.blanchet@viagenie.c=
a</a>&gt;<br>
&gt; =A0David Conrad &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39=
;cvml&#39;, &#39;drc@virtualized.org&#39;)">drc@virtualized.org</a>&gt;<br>
&gt; =A0Alex Deacon &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;=
cvml&#39;, &#39;Alex_Deacon@mpaa.org&#39;)">Alex_Deacon@mpaa.org</a>&gt;<br=
>
&gt; =A0Geoff Huston &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39=
;cvml&#39;, &#39;gih902@gmail.com&#39;)">gih902@gmail.com</a>&gt;<br>
&gt; =A0Stephen Kent &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39=
;cvml&#39;, &#39;kent@bbn.com&#39;)">kent@bbn.com</a>&gt;<br>
&gt; =A0Peter Koch &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;c=
vml&#39;, &#39;pk@denic.de&#39;)">pk@denic.de</a>&gt;<br>
&gt; =A0Warren Kumari &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#3=
9;cvml&#39;, &#39;warren@kumari.net&#39;)">warren@kumari.net</a>&gt;<br>
&gt; =A0John Levine &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#39;=
cvml&#39;, &#39;johnl@taugh.com&#39;)">johnl@taugh.com</a>&gt;<br>
&gt; =A0Daniel Migault &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#=
39;cvml&#39;, &#39;mglt.biz@gmail.com&#39;)">mglt.biz@gmail.com</a>&gt;<br>
&gt; =A0Hassan Zaheer &lt;<a href=3D"javascript:;" onclick=3D"_e(event, &#3=
9;cvml&#39;, &#39;hassanZaheer@gmail.com&#39;)">hassanZaheer@gmail.com</a>&=
gt;<br>
&gt;<br>
&gt; Please send your remarks in confidence about any or all candidates to<=
br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;iab=
-chair@iab.org&#39;)">iab-chair@iab.org</a> and <a href=3D"javascript:;" on=
click=3D"_e(event, &#39;cvml&#39;, &#39;execd@iab.org&#39;)">execd@iab.org<=
/a>. =A0We thank you in advance for<br>

&gt; your help.<br>
&gt;<br>
&gt; Best regards,<br>
&gt; Russ Housley<br>
&gt; IAB Chair<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt; Dear Colleagues,<br>
&gt;&gt;<br>
&gt;&gt; The IAB (on behalf of the IETF) has been asked to supply two techn=
ical<br>
&gt;&gt; experts to ICANN Technical Liaison Group (TLG). =A0The ICANN Bylaw=
s<br>
&gt;&gt; (Article XI-A, Section 2, Paragraph 6) asks the IETF, ITU-T, ETSI,=
 and<br>
&gt;&gt; W3C to each provide two technical experts. =A0The technical expert=
s are<br>
&gt;&gt; expected to be &quot;familiar with the technical standards issues =
that are<br>
&gt;&gt; relevant to ICANN&#39;s activities.&quot; These eight experts are =
expected to be<br>
&gt;&gt; &quot;available as necessary to determine, through an exchange of =
e-mail<br>
&gt;&gt; messages, where to direct a technical question from ICANN when ICA=
NN<br>
&gt;&gt; does not ask a specific TLG organization directly.<br>
&gt;&gt;<br>
&gt;&gt; The ICANN bylaws can be found at<br>
&gt;&gt; <a href=3D"http://www.icann.org/en/about/governance/bylaws" target=
=3D"_blank">http://www.icann.org/en/about/governance/bylaws</a>.<br>
&gt;&gt;<br>
&gt;&gt; The IAB is asking the community for volunteers to serve on the ICA=
NN TLG.<br>
&gt;&gt; If you are interested, please send a short e-mail to iab-chair at =
<a href=3D"http://iab.org" target=3D"_blank">iab.org</a><br>
&gt;&gt; with a copy to execd at <a href=3D"http://iab.org" target=3D"_blan=
k">iab.org</a> with your motivation and information<br>
&gt;&gt; concerning your familiarity with the IETF and ICANN as well as the=
 other<br>
&gt;&gt; standards organizations represented on the TLG. =A0The deadline fo=
r<br>
&gt;&gt; volunteering is 17 Nov 2013.<br>
&gt;&gt;<br>
&gt;&gt; The IAB will select from the available candidates, taking into acc=
ount<br>
&gt;&gt; the familiarity with ICANN and the IETF, their roles, and the IETF=
<br>
&gt;&gt; protocols. =A0While familiarity with ETSI, ITU-T, and W3C is also<=
br>
&gt;&gt; desirable, it is not required. =A0The selected candidates will ser=
ve on<br>
&gt;&gt; the ICANN TLG on personal title; however, the IAB will be looking =
for<br>
&gt;&gt; candidates who have an understanding of the interests of the techn=
ical<br>
&gt;&gt; community.<br>
&gt;&gt;<br>
&gt;&gt; The IAB will select one person for a one year term and select one =
person<br>
&gt;&gt; for a two year term.<br>
&gt;&gt;<br>
&gt;&gt; The ICANN TLG is expected to meet in person at or around the three=
 ICANN<br>
&gt;&gt; meetings held each year.<br>
&gt;&gt;<br>
&gt;&gt; NOTE: ICANN does cover travel and hotel costs for a pre-determined=
 number<br>
&gt;&gt; of days at each of the ICANN meetings.<br>
&gt;&gt;<br>
&gt;&gt; If you are willing to be considered or would like to nominate some=
one<br>
&gt;&gt; else for one of the TLG positions, please send an email to iab-cha=
ir at<br>
&gt;&gt; <a href=3D"http://iab.org" target=3D"_blank">iab.org</a> and execd=
 at <a href=3D"http://iab.org" target=3D"_blank">iab.org</a> by 17 Nov 2013=
.<br>
&gt;&gt;<br>
&gt;&gt; On behalf of the IAB,<br>
&gt;&gt; Russ Housley<br>
&gt;&gt; IAB Chair<br>
&gt;&gt;<br>
&gt;<br>
<br>
</blockquote>

--f46d043bdf6a0665da04f11cdc89--

From keith.drage@alcatel-lucent.com  Wed Jan 29 07:31:19 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8E91A0218; Wed, 29 Jan 2014 07:31:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id drKlSdsOaFw9; Wed, 29 Jan 2014 07:31:16 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 346CF1A008E; Wed, 29 Jan 2014 07:31:15 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0TFV9v9026667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 29 Jan 2014 09:31:11 -0600 (CST)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0TFV8QC005015 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 16:31:09 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Wed, 29 Jan 2014 16:31:09 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPHPzckxdedUpOzkK4h72KmTW/JZqbxCPw
Date: Wed, 29 Jan 2014 15:31:08 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
In-Reply-To: <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, IETF WG Chairs <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 15:31:19 -0000

In regard to "all countries / regions" the disclosure requirements are not =
that different from the disclosure requirements of every SDO, all with memb=
erships from just about every country in the world.=20

I would have expected that if there was a legal problem with disclosure, th=
en it would have been spotted by now, given the level of test it has been g=
iven by all those SDOs.

The difference with IETF is with representation by individual. For the SDOs=
 the membership is by company or equivalent, and they sign up (on behalf of=
 all their employees or consultants) to the disclosure requirements when th=
ey join the SDO.

But in general the disclosure requires as defined in RFC 3979 are not that =
complex and it is entirely reasonable that all participants should be requi=
red to read it. I do not believe it requires a trained legal expert to unde=
rstand it.

And as for being left alone, if you really are an individual (alone) with "=
contributor's IPR" or "participants IPR" then you are paying any awful lot =
of legal fees to keep that IPR; why not spend some of it on your responsibi=
lities to IETF.

As for consultants, if you are paid to participate in the IETF, then you sh=
ould ensure your contract allows you to meet the requirements of the IETF. =
It might help if RFC 3979 made this point, but it should be self evident an=
yway.

Regards

Keith=20

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf=20
> Of Abdussalam Baryun
> Sent: 29 January 2014 10:39
> To: ietf
> Cc: Cullen Jennings (fluffy); IETF WG Chairs
> Subject: Re: Problem with new Note Well
>=20
> I agree with the suggestions below and that I never liked the=20
> note well wordings. In addition, from Cullen's first message=20
> and others, it seems like most IETF participants are not=20
> practicing or understandning the note well. The reason may be=20
> because engineers are not good in legal issues, so do we have=20
> a current legal advisor/position in IETF organisation, or=20
> still IETF has no progress in legal experience, so we will=20
> need to go back to external legal. Why IETF just leaves its=20
> participants alone to do the legal advise but when it comes=20
> to their works it encourages inputs? Does the note well=20
> consider all countries/regions legal policies? Is it=20
> practical/agreeable for all participants any where, or was it tested?
>=20
> For me I don't agree with the way the note well is forced on=20
> all, it needs more discussions between WGs and their Chairs,=20
> but no time for it or no advisors or group discussion/meeting=20
> for legal issues (may be only IESG decides for us so far=20
> which is never practical).
>=20
> AB
>=20
> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
> >> All - it is clear that you have a concern about the new=20
> note well text.
> >> The problem has been well articulated;
> >
> >
> > Jari, et al,
> >
> >
> > There are a number of different problems, and only some of=20
> them have=20
> > been articulated.  Worse, the problems include the IPR rules=20
> > themselves, not just the Note Well:
> >
> >       0.  We have had IPR rules and a Note Well for many years and=20
> > have revised both a number of times.  Normally, work we do that has=20
> > been around that long warrants being called "mature", which=20
> means that=20
> > it works well and is well understood.  The latest discussion=20
> > demonstrates that that model does not apply to the IETF's IPR=20
> > handling.  In fact, the exchange looks more like the disparities we=20
> > see early in a working group effort, not what normally=20
> takes place after many years.
> >
> >       1. The participants in the discussion are extremely=20
> experienced=20
> > with the IETF and with this topic.  Yet they demonstrated a strong=20
> > /lack/ of rough consensus about what the /current/ IPR rules mean.
> >
> >       2.  The current rules are too complex for use by average=20
> > engineers.  Engineers are not attorneys, nevermind IPR=20
> attorneys.  IPR=20
> > is considered by attorneys to be an esoteric and difficult=20
> specialty.
> > The IETF's IPR rules need to be simple and simply stated,=20
> if we expect=20
> > average engineers to understand them.
> >
> >       3.  The current IPR rules appear to impose an unreasonable=20
> > demand on IETF participants, such as conflicting with=20
> employment arrangements.
> > (And if the demand is reasonable, then what is noteworthy is that=20
> > someone who has read this latest IETF discussion has developed the=20
> > impression that it isn't.  See point 6.)
> >
> >       4.  The current Note Well is too complex and=20
> apparently erroneous.
> >   (And if it is not erroneous, then what is noteworthy is that a=20
> > serious attempt to review the thread has resulted in=20
> someone coming to=20
> > the conclusion that the Note Well is erroneous.  See point 6.)
> >
> >       5.  Expecting an average IETF engineer to consult 4 different=20
> > BCPs, in order to understand what is required of them is=20
> not reasonable.
> >   Nor is all each document relevant.  So, in effect, the references=20
> > are overly broad, as well as too complicated. (See point 6.)
> >
> >       6.  Having a range of experienced, diligent IETF participants=20
> > demonstrate substantive disagreement about the meaning of=20
> our current=20
> > IPR rules undermines whatever utility the rules might have.=20
>  It sets=20
> > up a litigation argument that the participant did not=20
> understand the=20
> > rules, citing this thread as demonstrating that others also don't.
> >
> >
> > The remedies we need are not just with the Note Well.  We=20
> need to fix=20
> > the IPR rules too.
> >
> >
> >       0.  We need to establish clear and compelling community rough=20
> > consensus about the meaning of our IPR rules and the utility of our=20
> > Note Well.  We are currently /very/ far from being able to do that.
> >
> >       1.  We need a consensus statement that describes our=20
> 'model' of=20
> > an IETF particpant, in terms of what is reasonable for them to know=20
> > and what is reasonable for them to be responsible for and what is=20
> > reasonable for them to do, especially within the real time=20
> performance=20
> > constraints of a working group meeting. The premise of that model=20
> > needs to be extreme simplicity and clarity.  Any rules we=20
> assert need=20
> > to be vetted against that model.  Our current arrangement=20
> requires an=20
> > average engineer to be more knowledgeable and more diligent=20
> than is reasonable.
> >   (By 'diligent' I'm not referring to intent; I'm referring=20
> to classic=20
> > human factors usability limits.)
> >
> >       2.  One of the distinctions in the latest discussion=20
> is between=20
> > having the Note Well attempt to summarize what the IPR rules are,=20
> > versus having it merely declare that we have IPR rules and=20
> point the=20
> > reader to them.  For summary instruments, like a Note Well,=20
> the latter=20
> > approach makes far more sense.
> >
> >       3.  We need all of the IPR rules for IETF=20
> participation to be in=20
> > a single, simple, clear document that is easily=20
> understandable by an=20
> > average engineer. (See point 1.)
> >
> >
> > d/
> >
> > --
> > Dave Crocker
> > Brandenburg InternetWorking
> > bbiw.net
> >
> =

From spencerdawkins.ietf@gmail.com  Wed Jan 29 07:45:56 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0E441A024E for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 07:45:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W1LepBJKcoai for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 07:45:54 -0800 (PST)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 646001A008E for <ietf@ietf.org>; Wed, 29 Jan 2014 07:45:54 -0800 (PST)
Received: by mail-oa0-f49.google.com with SMTP id i7so2187661oag.22 for <ietf@ietf.org>; Wed, 29 Jan 2014 07:45:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=D74z3NK0E822exzcdbBb0Z/55cV4oXU/+CxFIMuwarE=; b=aS/XZ4eU9s0ma//tfWVUoFWhV+2/ku1rGpVF2EkON5wkkb+bd9AHS3eAHp5MwJ54XE 9M6AKVZ+fE+uaeubIDHmWmBerrUxspoBwkFEjaXz1Xj8OIsjxnoY/TJoS9GQzWc1urQK V8NQwkhptafuhhP2s/aDlGh/BoV7K9weJcSa2FAMb1laX64LhiCUREojGB6QAY8CMOfD IxxaMdaZouOCFPrk5wb53/Q3+TTYrqYYdCHfxsAK6g4YiQQjkM04BY1iFsUpYM8L21MR fNohAOLgbl7A6KSwzL2gz/O72Y03WwN4bU1QuH3PWSnQl1MvKJR9TGRXE5DUpl4uhFG6 NSdg==
X-Received: by 10.60.116.74 with SMTP id ju10mr6744759oeb.6.1391010351411; Wed, 29 Jan 2014 07:45:51 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id qh4sm4587713obc.4.2014.01.29.07.45.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 07:45:50 -0800 (PST)
Message-ID: <52E9222C.4060601@gmail.com>
Date: Wed, 29 Jan 2014 09:45:48 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <52E83926.1060909@gmail.com>
In-Reply-To: <52E83926.1060909@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 15:45:57 -0000

I'm replying to Brian and to Scott here ...

On 01/28/2014 05:11 PM, Brian E Carpenter wrote:
> Hi Spencer,
>
> I think there's a bit more to be said, though.
>
> The goal is to make the Internet work better, not to make
> private networks work better. Actually RFC 3935 defines
> the IETF's scope as: "protocols and practices for which
> secure and scalable implementations are expected to have
> wide deployment and interoperation on the Internet, or to
> form part of the infrastructure of the Internet."
>
> So if there are two ways of doing something, one of which
> works globally and one of which only works locally, the choice
> is a no-brainer. If a local-only solution comes up to the IESG,

I couldn't agree with Brian and Scott more. I'm focusing on "comes up to 
the IESG".

My point is that the sooner someone asks "so, is this really intended 
for deployment on the global Internet?", the better. If working groups 
and authors thought about that before, or even during, WGLC time, I 
would like to think that we would have fewer cases where the question is 
asked for the first time in AD review, or in directorate reviews, or in 
IETF Last Call.

I don't think it's controversial at all that the IETF does better when 
documents don't encounter Late Surprises (tm). If the first time someone 
says "but this is only intended to be used when $whatever" is in an 
email exchange during IETF Last Call, that's a Late Surprise, and the 
chances that the best outcome will happen aren't going up at that point.

As I said in my note, this is my personal suggestion. I'm not asking for 
an Applicability Statement as a mandatory section in all IDs, precisely 
because of Brian's point that the default is "this proposal is suitable 
for deployment on the global Internet". I'm asking working groups and 
authors to consider whether that's true for their proposals, or if I 
should be reviewing with something else in mind.

And as always, I encourage people to Do The Right Thing.

Spencer

> I think the first question is "Why isn't there a globally
> applicable solution to this problem?". Then the second question
> is "Why is this on the standards track, rather than being an
> informational document for the record?". And the third question
> is "Why is this better as an IETF document rather than an
> Independent Submission?".
>
> There may be perfectly good answers to those questions, but
> IMHO they need to be asked.
>
> Regards
>     Brian
>
> On 29/01/2014 09:14, Spencer Dawkins wrote:
>> Disclaimer - I'm one of the ADs who will be balloting your documents
>> until at least March 2015, but I'm only one of 15 ADs, and haven't
>> talked about this with the rest of the IESG.
>>
>> The past week has brought me yet another example of an idea that could
>> be a good idea, but not under every possible set of conditions, being
>> evaluated as if we had to decide whether it was a good idea in all
>> cases, or a bad idea. This might sound familiar to you, but if it does,
>> let's not talk about that specific case.
>>
>> The longer (and more painfully) we talk during Last Call, the more
>> details we unearth that help me to understand what document
>> authors/working groups are thinking, and that's good, but if it was less
>> painful, that would be even better.
>>
>> http://tools.ietf.org/html/rfc2026#section-3.2 describes Applicability
>> Statements, as distinct from Technical Specifications, and says (among
>> other things):
>>
>>     An Applicability Statement specifies how, and under what
>>     circumstances, one or more TSs may be applied to support a particular
>>     Internet capability.
>>
>> ...
>>
>>     An AS may describe particular methods of using a TS in a restricted
>>     "domain of applicability", such as Internet routers, terminal
>>     servers, Internet systems that interface to Ethernets, or datagram-
>>     based database servers.
>>
>>
>> Speaking only for myself, I don't expect Proposed Standards to be
>> perfect, and to work perfectly in every situation, but if a
>> specification doesn't describe any limits on applicability, I'm going to
>> be evaluating it as if it will be used on the open Internet (that's what
>> the "I" in "IETF" stands for).
>>
>> If a draft says it's only intended to be used within an IP subnet, I'd
>> evaluate it differently. I might ask that the authors/working group
>> consider what the TTL should be set to, so that what starts out within
>> an IP subnet stays within an IP subnet, but (to use one actual example)
>> we wouldn't be arguing about whether it's OK to send 32K max-length
>> packets over an arbitrary Internet path at line rate without getting any
>> feedback about path capacity - there are probably paths where that would
>> work, and there are definitely paths where it would not.
>>
>> If a draft says it's only intended to be used on provisioned, managed
>> internetwork links subject to SLA monitoring, I'd evaluate it differently.
>>
>> If a draft says "this is a hack, intended for use on old hardware that
>> can't do $X", I'd evaluate it differently.
>>
>> There are other limited-use scenarios that would make me evaluate a
>> draft differently.
>>
>> None of this is a guaranteed pass, but it would help me a lot. It would
>> likely help other reviewers, too.
>>
>> So, if you don't intend for your draft to be used on the global
>> Internet, please say so! As per
>> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to
>> put an Applicability Statement in a different draft; just a section that
>> says (another actual example) "this has been tested using these
>> parameters on a lightly-loaded LAN, and it works there", that is more
>> helpful than a tug of war(*) about whether something is a good idea or a
>> bad idea in all situations, in front of a live studio audience.
>>
>> Thanks to Alia Atlas for nudging me to think about this more.
>>
>> Spencer
>>
>> p.s. If you have feedback about what I'm thinking, I'd love for you to
>> share it, whether on this list, privately to me, to the 2015 Nomcom, or
>> to other Nomcom-eligible IETF participants when you're asking them to to
>> sign the recall petition ;-)
>>
>> (*) http://en.wikipedia.org/wiki/Tug_of_war
>>


From dhc@dcrocker.net  Wed Jan 29 07:58:14 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C901A0280 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 07:58:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id btAtro4jZp5v for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 07:58:13 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 573761A0230 for <ietf@ietf.org>; Wed, 29 Jan 2014 07:58:13 -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 s0TFw5Il025016 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 Jan 2014 07:58:09 -0800
Message-ID: <52E924F6.3010405@dcrocker.net>
Date: Wed, 29 Jan 2014 07:57:42 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com>
In-Reply-To: <52E80FA9.5020704@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.66]); Wed, 29 Jan 2014 07:58:09 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 29 Jan 2014 15:58:14 -0000

On 1/28/2014 12:14 PM, Spencer Dawkins wrote:
> Speaking only for myself, I don't expect Proposed Standards to be
> perfect, and to work perfectly in every situation, but if a
> specification doesn't describe any limits on applicability, I'm going to
> be evaluating it as if it will be used on the open Internet (that's what
> the "I" in "IETF" stands for).
...
> So, if you don't intend for your draft to be used on the global
> Internet, please say so!


Spencer,

What an excellent bit of constructive suggestion.

However you've cast it as being for the purpose of guiding IESG 
evaluation, and I think that it really has much broader... 
applicability.  Anyone reading the document needs to know the intended 
scope of use.  For example, obviously an implementer ought to understand 
the operational limitations meant for a specification.

I take your suggestion to reduce to a simple guideline:

      The default applicability for an IETF specification is the 'open' 
Internet.  Any specification intended for more constrained use needs to 
describe the constraints.  One means of achieving this can be an 
"Applicability" section in the specification, with a description of 
intended use.

A potentially larger benefit of this consideration is that it might get 
designers to think a bit more explicitly about the use of their work.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From scott.brim@gmail.com  Wed Jan 29 08:15:55 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73ADF1A02F2 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F3HoZs3BD8MU for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:15:54 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E2B291A0230 for <ietf@ietf.org>; Wed, 29 Jan 2014 08:15:53 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id wn1so2161985obc.20 for <ietf@ietf.org>; Wed, 29 Jan 2014 08:15:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=8B/ZhppFLrHNvwEJqZvecwikquGpv7wDJp7ni+idNnE=; b=fYjp5HJs2TErU6JLHQC+9kjuaFtr48UW/0ddaWImcnU3VxRw6pKZ8827QnVc5RplvT hCR0QuvcrkP6BYxGdhXU0xNiymwqLquaBJKcpT+jiDX7YiZGN/Cnqq8TH918hqbpGDo9 FtRPGKts6MxX1O6x9dDP8sJPrm4vYxUEl3vi2lO6ox7SQQN7fkcfOaw84/kcOWSp6U7j r35cRirOeMFrzpn3+/5BpoFcA9o0mit4fBDL1bnLcHFvhQH4ftrn1/Nqg5ZDcloXxWVL 6Fb2R5KgosmNJQ2Ze2qA7dSl0nDySMbStxcf1HR6salYktijnkUjeAblJynfKm36xPZt +/HA==
X-Received: by 10.182.128.138 with SMTP id no10mr7031731obb.32.1391012150937;  Wed, 29 Jan 2014 08:15:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 29 Jan 2014 08:15:30 -0800 (PST)
In-Reply-To: <52E924F6.3010405@dcrocker.net>
References: <52E80FA9.5020704@gmail.com> <52E924F6.3010405@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 29 Jan 2014 11:15:30 -0500
Message-ID: <CAPv4CP_O5EnO7mFsqH4jMKJ3jAuQ-O_734s-z=zWmbs2Qh78bQ@mail.gmail.com>
Subject: Re: When is an idea a good idea?
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0153852e228f6304f11e415e
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:15:55 -0000

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

On Wed, Jan 29, 2014 at 10:57 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> I take your suggestion to reduce to a simple guideline:
>
>      The default applicability for an IETF specification is the 'open'
> Internet.  Any specification intended for more constrained use needs to
> describe the constraints.  One means of achieving this can be an
> "Applicability" section in the specification, with a description of
> intended use.


+1. Where would you put it?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jan 29, 2014 at 10:57 AM, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D=
"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.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"><span style=3D"color:rgb(3=
4,34,34)">I take your suggestion to reduce to a simple guideline:</span><br=
></div>


<br>
=A0 =A0 =A0The default applicability for an IETF specification is the &#39;=
open&#39; Internet. =A0Any specification intended for more constrained use =
needs to describe the constraints. =A0One means of achieving this can be an=
 &quot;Applicability&quot; section in the specification, with a description=
 of intended use.</blockquote>

<div><br></div><div>+1. Where would you put it?=A0</div></div></div></div>

--089e0153852e228f6304f11e415e--

From spencerdawkins.ietf@gmail.com  Wed Jan 29 08:16:18 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 744DA1A028A for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id saViJl8TIo22 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:16:16 -0800 (PST)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0E91A0443 for <ietf@ietf.org>; Wed, 29 Jan 2014 08:16:15 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id l6so2233055oag.7 for <ietf@ietf.org>; Wed, 29 Jan 2014 08:16:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=oKJh4Lhx0RiCQN18l+b0453BRy2MpeJ642enLhSWHnA=; b=UqRpEftqhUKXriuNBsbDLNi+6HqTDZOzNqQtbMxqPIDMKJzaYMuA8Ja04luatHKDb7 D+oVQJHxUZMdelpL5q72iwvzIijWbrZnKdTGf1Rjaidxceh4Hx+HzWXQjr/slKiETbMY LfFfflH+PzdipAjVrE4moHi2iefcVGvNz1WvDL3bAtC5IrHfEacPZx5BiEY9AOlCT6sY Q2W0+ouHfK6PAe5Cf17Ek3nw52Ua+3m02VDB7wPywd1zQvHjBSbTKx4fXvTFKcJtViJ4 tLOXVAajce1NJPxyIQojEWZCtonOEoier8gWKLZzI5uCJjskWJqx9pSVla0NVWQKIKKC I1hA==
X-Received: by 10.182.129.201 with SMTP id ny9mr7080960obb.0.1391012172547; Wed, 29 Jan 2014 08:16:12 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id z5sm4700825obg.13.2014.01.29.08.16.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 08:16:11 -0800 (PST)
Message-ID: <52E92949.1040407@gmail.com>
Date: Wed, 29 Jan 2014 10:16:09 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <52E924F6.3010405@dcrocker.net>
In-Reply-To: <52E924F6.3010405@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:16:18 -0000

On 01/29/2014 09:57 AM, Dave Crocker wrote:
> On 1/28/2014 12:14 PM, Spencer Dawkins wrote:
>> Speaking only for myself, I don't expect Proposed Standards to be
>> perfect, and to work perfectly in every situation, but if a
>> specification doesn't describe any limits on applicability, I'm going to
>> be evaluating it as if it will be used on the open Internet (that's what
>> the "I" in "IETF" stands for).
> ...
>> So, if you don't intend for your draft to be used on the global
>> Internet, please say so!
>
>
> Spencer,
>
> What an excellent bit of constructive suggestion.
>
> However you've cast it as being for the purpose of guiding IESG 
> evaluation, and I think that it really has much broader... 
> applicability.  Anyone reading the document needs to know the intended 
> scope of use.  For example, obviously an implementer ought to 
> understand the operational limitations meant for a specification.
>
> I take your suggestion to reduce to a simple guideline:
>
>      The default applicability for an IETF specification is the 'open' 
> Internet.  Any specification intended for more constrained use needs 
> to describe the constraints.  One means of achieving this can be an 
> "Applicability" section in the specification, with a description of 
> intended use.

Dave, I think that sounds about right.

Part of what I think about during IESG evaluation is the potential for 
someone to use the proposal in a way that trips over unstated 
assumptions. Seeing that a proposal includes some thoughts about 
intended uses (and why) makes me worry less. Downstream readers and 
implementers are definitely part of the food chain.

>
> A potentially larger benefit of this consideration is that it might 
> get designers to think a bit more explicitly about the use of their work.

That could be lovely ...

Spencer

From d3e3e3@gmail.com  Wed Jan 29 08:16:48 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82BE61A0427; Wed, 29 Jan 2014 08:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSAv9FihoeEn; Wed, 29 Jan 2014 08:16:46 -0800 (PST)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7C0F61A03BF; Wed, 29 Jan 2014 08:16:46 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so2275265oag.16 for <multiple recipients>; Wed, 29 Jan 2014 08:16:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5EUH2LRrrJBcDqRDHIoI5LRX5KhMmmsb3YzqRsyBQuI=; b=wlPd/h3J9Jf3V+fPkGjZQV9xdWQGUnsCLtP1ZHSYGazexifl+wIuC8f6hv3GKHKcGz GjpCBsumlyWCTgzfn9OrpqJEFEgTpDF0h5Qti7FA3WqApvI19YHqdd0rUYHTDitF0D0D YKFqhCJOTArU29wIMIiaRADe/WtfFDPzULkeibVHk2/oLTU5pS9sxC35b7eGXJdTOkJz Vb/CYoIy17JgKXLk9VBoX6H6PSzQMJYUW3YOdWeW+ILgOcsMfTvJ3xgKKFrjUnrXyzIY 741SsQOAK+VftN5em4sJCU56tuG2ZuuQEG61Q4/cwtZ1hJVUjHX5nNaFUbdgQ3i0egn6 tKaA==
X-Received: by 10.183.3.102 with SMTP id bv6mr7058660obd.18.1391012203430; Wed, 29 Jan 2014 08:16:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.33.102 with HTTP; Wed, 29 Jan 2014 08:16:23 -0800 (PST)
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 29 Jan 2014 11:16:23 -0500
Message-ID: <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
Subject: Re: Problem with new Note Well
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF WG Chairs <wgchairs@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:16:48 -0000

Hi Keith,

On Wed, Jan 29, 2014 at 10:31 AM, DRAGE, Keith (Keith)
<keith.drage@alcatel-lucent.com> wrote:
> In regard to "all countries / regions" the disclosure requirements are not that different from the disclosure requirements of every SDO, all with memberships from just about every country in the world.
>
> I would have expected that if there was a legal problem with disclosure, then it would have been spotted by now, given the level of test it has been given by all those SDOs.
>
> The difference with IETF is with representation by individual. For the SDOs the membership is by company or equivalent, and they sign up (on behalf of all their employees or consultants) to the disclosure requirements when they join the SDO.

The IETF is by no means unique in this regard. IEEE 802 and all its
working groups (802.3 (Ethernet), 802.11 (Wi-Fi), 802.15
(Bluetooth/Zigbee/etc)) all have "representation by individual".

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


> But in general the disclosure requires as defined in RFC 3979 are not that complex and it is entirely reasonable that all participants should be required to read it. I do not believe it requires a trained legal expert to understand it.
>
> And as for being left alone, if you really are an individual (alone) with "contributor's IPR" or "participants IPR" then you are paying any awful lot of legal fees to keep that IPR; why not spend some of it on your responsibilities to IETF.
>
> As for consultants, if you are paid to participate in the IETF, then you should ensure your contract allows you to meet the requirements of the IETF. It might help if RFC 3979 made this point, but it should be self evident anyway.
>
> Regards
>
> Keith
>
>> -----Original Message-----
>> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf
>> Of Abdussalam Baryun
>> Sent: 29 January 2014 10:39
>> To: ietf
>> Cc: Cullen Jennings (fluffy); IETF WG Chairs
>> Subject: Re: Problem with new Note Well
>>
>> I agree with the suggestions below and that I never liked the
>> note well wordings. In addition, from Cullen's first message
>> and others, it seems like most IETF participants are not
>> practicing or understandning the note well. The reason may be
>> because engineers are not good in legal issues, so do we have
>> a current legal advisor/position in IETF organisation, or
>> still IETF has no progress in legal experience, so we will
>> need to go back to external legal. Why IETF just leaves its
>> participants alone to do the legal advise but when it comes
>> to their works it encourages inputs? Does the note well
>> consider all countries/regions legal policies? Is it
>> practical/agreeable for all participants any where, or was it tested?
>>
>> For me I don't agree with the way the note well is forced on
>> all, it needs more discussions between WGs and their Chairs,
>> but no time for it or no advisors or group discussion/meeting
>> for legal issues (may be only IESG decides for us so far
>> which is never practical).
>>
>> AB
>>
>> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
>> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
>> >> All - it is clear that you have a concern about the new
>> note well text.
>> >> The problem has been well articulated;
>> >
>> >
>> > Jari, et al,
>> >
>> >
>> > There are a number of different problems, and only some of
>> them have
>> > been articulated.  Worse, the problems include the IPR rules
>> > themselves, not just the Note Well:
>> >
>> >       0.  We have had IPR rules and a Note Well for many years and
>> > have revised both a number of times.  Normally, work we do that has
>> > been around that long warrants being called "mature", which
>> means that
>> > it works well and is well understood.  The latest discussion
>> > demonstrates that that model does not apply to the IETF's IPR
>> > handling.  In fact, the exchange looks more like the disparities we
>> > see early in a working group effort, not what normally
>> takes place after many years.
>> >
>> >       1. The participants in the discussion are extremely
>> experienced
>> > with the IETF and with this topic.  Yet they demonstrated a strong
>> > /lack/ of rough consensus about what the /current/ IPR rules mean.
>> >
>> >       2.  The current rules are too complex for use by average
>> > engineers.  Engineers are not attorneys, nevermind IPR
>> attorneys.  IPR
>> > is considered by attorneys to be an esoteric and difficult
>> specialty.
>> > The IETF's IPR rules need to be simple and simply stated,
>> if we expect
>> > average engineers to understand them.
>> >
>> >       3.  The current IPR rules appear to impose an unreasonable
>> > demand on IETF participants, such as conflicting with
>> employment arrangements.
>> > (And if the demand is reasonable, then what is noteworthy is that
>> > someone who has read this latest IETF discussion has developed the
>> > impression that it isn't.  See point 6.)
>> >
>> >       4.  The current Note Well is too complex and
>> apparently erroneous.
>> >   (And if it is not erroneous, then what is noteworthy is that a
>> > serious attempt to review the thread has resulted in
>> someone coming to
>> > the conclusion that the Note Well is erroneous.  See point 6.)
>> >
>> >       5.  Expecting an average IETF engineer to consult 4 different
>> > BCPs, in order to understand what is required of them is
>> not reasonable.
>> >   Nor is all each document relevant.  So, in effect, the references
>> > are overly broad, as well as too complicated. (See point 6.)
>> >
>> >       6.  Having a range of experienced, diligent IETF participants
>> > demonstrate substantive disagreement about the meaning of
>> our current
>> > IPR rules undermines whatever utility the rules might have.
>>  It sets
>> > up a litigation argument that the participant did not
>> understand the
>> > rules, citing this thread as demonstrating that others also don't.
>> >
>> >
>> > The remedies we need are not just with the Note Well.  We
>> need to fix
>> > the IPR rules too.
>> >
>> >
>> >       0.  We need to establish clear and compelling community rough
>> > consensus about the meaning of our IPR rules and the utility of our
>> > Note Well.  We are currently /very/ far from being able to do that.
>> >
>> >       1.  We need a consensus statement that describes our
>> 'model' of
>> > an IETF particpant, in terms of what is reasonable for them to know
>> > and what is reasonable for them to be responsible for and what is
>> > reasonable for them to do, especially within the real time
>> performance
>> > constraints of a working group meeting. The premise of that model
>> > needs to be extreme simplicity and clarity.  Any rules we
>> assert need
>> > to be vetted against that model.  Our current arrangement
>> requires an
>> > average engineer to be more knowledgeable and more diligent
>> than is reasonable.
>> >   (By 'diligent' I'm not referring to intent; I'm referring
>> to classic
>> > human factors usability limits.)
>> >
>> >       2.  One of the distinctions in the latest discussion
>> is between
>> > having the Note Well attempt to summarize what the IPR rules are,
>> > versus having it merely declare that we have IPR rules and
>> point the
>> > reader to them.  For summary instruments, like a Note Well,
>> the latter
>> > approach makes far more sense.
>> >
>> >       3.  We need all of the IPR rules for IETF
>> participation to be in
>> > a single, simple, clear document that is easily
>> understandable by an
>> > average engineer. (See point 1.)
>> >
>> >
>> > d/
>> >
>> > --
>> > Dave Crocker
>> > Brandenburg InternetWorking
>> > bbiw.net
>> >
>>

From iab-chair@iab.org  Wed Jan 29 08:17:11 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F701A03E8; Wed, 29 Jan 2014 08:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0ZVnvjvTPnQ; Wed, 29 Jan 2014 08:17:08 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 1228C1A0471; Wed, 29 Jan 2014 08:17:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id C56D4A60D4; Wed, 29 Jan 2014 08:16:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dyvo_sRnrunz; Wed, 29 Jan 2014 08:16:11 -0800 (PST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) by c9a.amsl.com (Postfix) with ESMTPSA id 4E538A60CB; Wed, 29 Jan 2014 08:16:11 -0800 (PST)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
Date: Wed, 29 Jan 2014 11:16:56 -0500
Message-Id: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:17:12 -0000

This is a call for review of "Technical Considerations for Internet
Service Blocking and Filtering" prior to potential approval as an
IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-filtering-considerations/

The Call for Review will last until 26 February 2014.
Please send comments to iab@iab.org. 

On behalf of the IAB,
  Russ Housley
  IAB Chair


From lear@cisco.com  Wed Jan 29 08:21:46 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A0BA1A03DF; Wed, 29 Jan 2014 08:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.537
X-Spam-Level: 
X-Spam-Status: No, score=-7.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SORTED_RECIPS=2.499, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jqYNtAmpaooi; Wed, 29 Jan 2014 08:21:45 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 113E61A03D4; Wed, 29 Jan 2014 08:21:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=823; q=dns/txt; s=iport; t=1391012502; x=1392222102; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kEGMmm+BpBoFn2QsdBgGVKeeXmvbzN8Q3TYsTD72eqQ=; b=FizJD8zEYw7AEq7grfO6mlrSBeW9RHYmChdXJxycaLwo6ugaCT/JyPiD mc7nTURi38wQEWzez4JkQ/Z6cChpvLSnnWtjIHWULJHdNwAeWiSbEBUAr qil2CxB+xZ0JOueIIvISG/PD6tuZ+GVf9dhxB1z4WE78/Ip06QDavppMM o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncIAIkp6VKQ/khL/2dsb2JhbABZgwyEDLoBgQcWVh6CJQEBAQMBI1UBBQsLGgIFFgsCAgkDAgECASsaBgEMAQcBAYd5CKpCnzsXgSmMfgFXB4JvgUkBA5gokh+DLjuBLAEf
X-IronPort-AV: E=Sophos;i="4.95,742,1384300800";  d="scan'208";a="4368257"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-1.cisco.com with ESMTP; 29 Jan 2014 16:21:41 +0000
Received: from mctiny.local ([10.61.174.85]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0TGLevD012624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Jan 2014 16:21:41 GMT
Message-ID: <52E92A94.9000903@cisco.com>
Date: Wed, 29 Jan 2014 17:21:40 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [imapext] Gen-ART review of draft-ietf-qresync-rfc5162bis-09
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <52E69A54.9030104@isode.com> <CALaySJKwwZi-NumR_GiohKGb1EDSwFD0q26o-SOp5w0XJKvhrQ@mail.gmail.com> <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
In-Reply-To: <A122D59D-B356-4A92-B0C8-9E31CB938FF9@isode.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Black, David" <david.black@emc.com>, "dcridland@arcode.com" <dcridland@arcode.com>, "imapext@ietf.org" <imapext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:21:46 -0000

Alexey,

On 1/28/14, 9:37 AM, Alexey Melnikov wrote:

> I think David's right that some version of what Eliot said:
>>> there
>>> is a requirement for strict syntax parsing.  If the client blows it in
>>> any way, the server SHOULD return an error with a BAD response.
>> ...should be added to the section about the line-length limit.  A
>> sentence or two should do nicely.
> Yes, I agree.
>
>
>
Then my suggestion is to push out a new version with  some text along
these lines before the teleconference, please (tomorrow would be
ideal).  I will note that I believe this advice to be general in nature
and not limited to this capability, but we certainly can reinforce the
point here, and restate it if/when someone does an update to 3501
(probably when I have grandchildren, I would think).

Eliot

From gtw@gtwassociates.com  Wed Jan 29 09:51:53 2014
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3211A0370; Wed, 29 Jan 2014 09:51:53 -0800 (PST)
X-Quarantine-ID: <wNHj6seIxsek>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: 1.239
X-Spam-Level: *
X-Spam-Status: No, score=1.239 tagged_above=-999 required=5 tests=[BAYES_50=0.8, STOX_REPLY_TYPE=0.439] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wNHj6seIxsek; Wed, 29 Jan 2014 09:51:51 -0800 (PST)
Received: from s2.mail.rcig.net (s2.mail.rcig.net [216.87.38.202]) by ietfa.amsl.com (Postfix) with ESMTP id C8B2F1A0276; Wed, 29 Jan 2014 09:51:51 -0800 (PST)
Received: from pool-108-28-107-161.washdc.fios.verizon.net ([108.28.107.161]:62674 helo=GTWPC) by s2.mail.rcig.net with esmtpa (Exim 4.72) (envelope-from <gtw@gtwassociates.com>) id 1W8ZIh-0004Vd-H1; Wed, 29 Jan 2014 11:51:48 -0600
Message-ID: <B04A33F733FD475B99006902BBC1FE18@GTWPC>
From: "GTW" <gtw@gtwassociates.com>
To: "Robert Elz" <kre@munnari.OZ.AU>, <ietf@ietf.org>
References: <201401281812.s0SICTXk3778564@shell01.TheWorld.com> <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov>, <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com> <4111.1390994763@perseus.noi.kre.to>
In-Reply-To: <4111.1390994763@perseus.noi.kre.to>
Subject: Re: IPR disclosure rules in general (Was: various other stuff...)
Date: Wed, 29 Jan 2014 12:51:42 -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: wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 29 Jan 2014 17:51:53 -0000

I believe practical experience should play a significant role  shaping 
policies and procedures of any organization.

Much of the discussion has focused on addressing hypothetical situations ... 
and those mainly to do with disclosure obligations.

What  problems has IETF experienced due to non disclosure of IP that has 
turned out to be essential to some RFC but was not disclosed by any party 
... IETF participant, non-participant, consultant, ...anyone.   I do recall 
some sharing about "late disclosures" but I do not have any specifics.  Does 
anyone have data about our practical  experiences?  My opinion is that first 
priority should be do address whatever may be current problems.

I believe most of the current litigation has more to do with differences of 
opinion between licensees and licensors over license assurances made and 
less  to do with allegations  of non disclosure of a disclosure that should 
have been made.

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

-----Original Message----- 
From: Robert Elz
Sent: Wednesday, January 29, 2014 6:26 AM
To: ietf@ietf.org
Cc: wgchairs@ietf.org
Subject: IPR disclosure rules in general (Was: various other stuff...)

    Date:        Tue, 28 Jan 2014 13:12:29 -0500 (EST)
    From:        worley@ariadne.com (Dale R. Worley)
    Message-ID:  <201401281812.s0SICTXk3778564@shell01.TheWorld.com>

  | Indeed, if the IETF didn't have this rule, a company with undisclosed
  | IPR could hire consultants, put them under NDA, and have them advocate
  | at the IETF to include the IPR in standards.

Much easier, for such nefarious company, is simply to hire (as employees, or
consultants, it makes no difference) people to "represent" the company's
interest at the IETF, and make sure that those people are unaware of any
and all IPR claims that the company may possess.

In that case, the person attending the IETF cannot possibly disclose the
IPR, as they're unaware of it, the company can't be expected to disclose
anything - companies don't attend the IETF (except as sponsors perhaps, and
I am fairly sure that no-one asks the sponsors to reveal all their IPR 
before
we take their money) the people all attend as individuals.

We may not like this kind of behaviour, but other than completely changing
the way the IETF is designed to operate (to actually have company's 
explicitly
become members, and enter into membership agreements, with only 
representatives
of member companies permitted to participate) which I don't think anyone 
wants,
there really is nothing that can be done about it.

Now this by no means guarantees that the courts won't take a dim view of
this kind of behaviour, if an attempt is later made to enforce the IPR 
claim,
but it won't be because of any breach of IETF rules - there hasn't been any
in this scenario.

All of these problems are brought about by yet another instance of the
IETF attempting to fix something that is simply way outside our competence
or ability to fix.  It isn't surprising - after all, the IETF is made up
(mostly) of engineers, and when an engineer sees something broken, the
natural inclination is to attempt to fix it.  But sometimes the underlying
problem is something that simply cannot be fixed by any amount of 
engineering.
Hidden IPR is one of those, the problem is in people's attitudes - how
willing they are to put their own interests ahead of the general community
interest.   You simply cannot engineer a fix to this, it is a social issue.

Everything beyond simply encouraging people to disclose any IPR that they're
aware of, which they are able to disclose - or if unable, to attempt to
encourage those who are able to disclose it, is beyond what is rational for
the IETF to attempt to do, and what's more, the "rules" that people spend
so much time debating (people waste so much time debating) are essentially
useless, as they have no enforcement mechanism.  What exactly is the IETF
supposed to do, if it is revealed, some time later, that some IPR was not
disclosed by a participant in some discussions that they could have
disclosed?   As I understand it, there is simply some hope that some court
will use that to invalidate the IPR claim - but nothing I've seen suggests
that the "rule" is actually necessary for that, and even if it is, as above,
it is trivial to work around.

These days the IETF is spending far too much time on issues that have 
nothing
to do with actually improving the protocols in use on the internet, and
should go back to doing what it can do, and simply allow the rest to be
handled in the places designed to handle such things.   Stepping back, and
saying "I cannot fix that problem" seems like being defeated, but it isn't,
it is just accepting reality.  That is good engineering.

kre


From keith.drage@alcatel-lucent.com  Wed Jan 29 10:09:14 2014
Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC4B21A04D7; Wed, 29 Jan 2014 10:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jw2b6_Zo8LLs; Wed, 29 Jan 2014 10:09:10 -0800 (PST)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB0F1A036B; Wed, 29 Jan 2014 10:08:47 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s0TI8gPE014986 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Wed, 29 Jan 2014 12:08:44 -0600 (CST)
Received: from FR711WXCHHUB01.zeu.alcatel-lucent.com (fr711wxchhub01.zeu.alcatel-lucent.com [135.239.2.111]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s0TI8gOS002277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 29 Jan 2014 19:08:42 +0100
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.26]) by FR711WXCHHUB01.zeu.alcatel-lucent.com ([135.239.2.111]) with mapi id 14.02.0247.003; Wed, 29 Jan 2014 19:08:42 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: RE: Problem with new Note Well
Thread-Topic: Problem with new Note Well
Thread-Index: AQHPHPzckxdedUpOzkK4h72KmTW/JZqbxCPwgAAMB4CAAC+MEA==
Date: Wed, 29 Jan 2014 18:08:41 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B1253DF@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <52E3326E.3080007@gmail.com> <82D163D29DC1D4A7B4797E8F@JcK-HP8200.jck.com> <01P3M48DZNS80000AS@mauve.mrochek.com> <52E5E624.4080003@gmail.com> <19AAADA2-8E3B-456F-B0CE-9A27D2BB5FE9@piuha.net> <52E69572.7000903@dcrocker.net> <CADnDZ8_X-APwa6BSYF+taXw01XGCH-ffsAnneo+6HsXo4WqbHg@mail.gmail.com> <949EF20990823C4C85C18D59AA11AD8B1250B2@FR712WXCHMBA11.zeu.alcatel-lucent.com> <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
In-Reply-To: <CAF4+nEEhZRVp931ayK2LpVyEYje=3zkZ0pej5qhgoXVD+vR=Rw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF WG Chairs <wgchairs@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:09:15 -0000

Agreed. IETF is not unique in this.

The point was to try and explain why individual participants in other SDOs =
may not have realised how they were committed to similar rules, although th=
ey are generally reminded of that commitment at the start of every meeting.

Regards

Keith

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]=20
> Sent: 29 January 2014 16:16
> To: DRAGE, Keith (Keith)
> Cc: ietf; IETF WG Chairs
> Subject: Re: Problem with new Note Well
>=20
> Hi Keith,
>=20
> On Wed, Jan 29, 2014 at 10:31 AM, DRAGE, Keith (Keith)=20
> <keith.drage@alcatel-lucent.com> wrote:
> > In regard to "all countries / regions" the disclosure=20
> requirements are not that different from the disclosure=20
> requirements of every SDO, all with memberships from just=20
> about every country in the world.
> >
> > I would have expected that if there was a legal problem=20
> with disclosure, then it would have been spotted by now,=20
> given the level of test it has been given by all those SDOs.
> >
> > The difference with IETF is with representation by=20
> individual. For the SDOs the membership is by company or=20
> equivalent, and they sign up (on behalf of all their=20
> employees or consultants) to the disclosure requirements when=20
> they join the SDO.
>=20
> The IETF is by no means unique in this regard. IEEE 802 and=20
> all its working groups (802.3 (Ethernet), 802.11 (Wi-Fi), 802.15
> (Bluetooth/Zigbee/etc)) all have "representation by individual".
>=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
>=20
> > But in general the disclosure requires as defined in RFC=20
> 3979 are not that complex and it is entirely reasonable that=20
> all participants should be required to read it. I do not=20
> believe it requires a trained legal expert to understand it.
> >
> > And as for being left alone, if you really are an=20
> individual (alone) with "contributor's IPR" or "participants=20
> IPR" then you are paying any awful lot of legal fees to keep=20
> that IPR; why not spend some of it on your responsibilities to IETF.
> >
> > As for consultants, if you are paid to participate in the=20
> IETF, then you should ensure your contract allows you to meet=20
> the requirements of the IETF. It might help if RFC 3979 made=20
> this point, but it should be self evident anyway.
> >
> > Regards
> >
> > Keith
> >
> >> -----Original Message-----
> >> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of=20
> >> Abdussalam Baryun
> >> Sent: 29 January 2014 10:39
> >> To: ietf
> >> Cc: Cullen Jennings (fluffy); IETF WG Chairs
> >> Subject: Re: Problem with new Note Well
> >>
> >> I agree with the suggestions below and that I never liked the note=20
> >> well wordings. In addition, from Cullen's first message=20
> and others,=20
> >> it seems like most IETF participants are not practicing or=20
> >> understandning the note well. The reason may be because=20
> engineers are=20
> >> not good in legal issues, so do we have a current legal=20
> >> advisor/position in IETF organisation, or still IETF has=20
> no progress=20
> >> in legal experience, so we will need to go back to external legal.=20
> >> Why IETF just leaves its participants alone to do the legal advise=20
> >> but when it comes to their works it encourages inputs?=20
> Does the note=20
> >> well consider all countries/regions legal policies? Is it=20
> >> practical/agreeable for all participants any where, or was=20
> it tested?
> >>
> >> For me I don't agree with the way the note well is forced=20
> on all, it=20
> >> needs more discussions between WGs and their Chairs, but=20
> no time for=20
> >> it or no advisors or group discussion/meeting for legal=20
> issues (may=20
> >> be only IESG decides for us so far which is never practical).
> >>
> >> AB
> >>
> >> On 1/27/14, Dave Crocker <dhc@dcrocker.net> wrote:
> >> > On 1/27/2014 8:17 AM, Jari Arkko wrote:
> >> >> All - it is clear that you have a concern about the new
> >> note well text.
> >> >> The problem has been well articulated;
> >> >
> >> >
> >> > Jari, et al,
> >> >
> >> >
> >> > There are a number of different problems, and only some of
> >> them have
> >> > been articulated.  Worse, the problems include the IPR rules=20
> >> > themselves, not just the Note Well:
> >> >
> >> >       0.  We have had IPR rules and a Note Well for many=20
> years and=20
> >> > have revised both a number of times.  Normally, work we=20
> do that has=20
> >> > been around that long warrants being called "mature", which
> >> means that
> >> > it works well and is well understood.  The latest discussion=20
> >> > demonstrates that that model does not apply to the IETF's IPR=20
> >> > handling.  In fact, the exchange looks more like the=20
> disparities we=20
> >> > see early in a working group effort, not what normally
> >> takes place after many years.
> >> >
> >> >       1. The participants in the discussion are extremely
> >> experienced
> >> > with the IETF and with this topic.  Yet they=20
> demonstrated a strong=20
> >> > /lack/ of rough consensus about what the /current/ IPR=20
> rules mean.
> >> >
> >> >       2.  The current rules are too complex for use by average=20
> >> > engineers.  Engineers are not attorneys, nevermind IPR
> >> attorneys.  IPR
> >> > is considered by attorneys to be an esoteric and difficult
> >> specialty.
> >> > The IETF's IPR rules need to be simple and simply stated,
> >> if we expect
> >> > average engineers to understand them.
> >> >
> >> >       3.  The current IPR rules appear to impose an unreasonable=20
> >> > demand on IETF participants, such as conflicting with
> >> employment arrangements.
> >> > (And if the demand is reasonable, then what is=20
> noteworthy is that=20
> >> > someone who has read this latest IETF discussion has=20
> developed the=20
> >> > impression that it isn't.  See point 6.)
> >> >
> >> >       4.  The current Note Well is too complex and
> >> apparently erroneous.
> >> >   (And if it is not erroneous, then what is noteworthy is that a=20
> >> > serious attempt to review the thread has resulted in
> >> someone coming to
> >> > the conclusion that the Note Well is erroneous.  See point 6.)
> >> >
> >> >       5.  Expecting an average IETF engineer to consult=20
> 4 different=20
> >> > BCPs, in order to understand what is required of them is
> >> not reasonable.
> >> >   Nor is all each document relevant.  So, in effect, the=20
> references=20
> >> > are overly broad, as well as too complicated. (See point 6.)
> >> >
> >> >       6.  Having a range of experienced, diligent IETF=20
> participants=20
> >> > demonstrate substantive disagreement about the meaning of
> >> our current
> >> > IPR rules undermines whatever utility the rules might have.
> >>  It sets
> >> > up a litigation argument that the participant did not
> >> understand the
> >> > rules, citing this thread as demonstrating that others=20
> also don't.
> >> >
> >> >
> >> > The remedies we need are not just with the Note Well.  We
> >> need to fix
> >> > the IPR rules too.
> >> >
> >> >
> >> >       0.  We need to establish clear and compelling=20
> community rough=20
> >> > consensus about the meaning of our IPR rules and the=20
> utility of our=20
> >> > Note Well.  We are currently /very/ far from being able=20
> to do that.
> >> >
> >> >       1.  We need a consensus statement that describes our
> >> 'model' of
> >> > an IETF particpant, in terms of what is reasonable for=20
> them to know=20
> >> > and what is reasonable for them to be responsible for=20
> and what is=20
> >> > reasonable for them to do, especially within the real time
> >> performance
> >> > constraints of a working group meeting. The premise of=20
> that model=20
> >> > needs to be extreme simplicity and clarity.  Any rules we
> >> assert need
> >> > to be vetted against that model.  Our current arrangement
> >> requires an
> >> > average engineer to be more knowledgeable and more diligent
> >> than is reasonable.
> >> >   (By 'diligent' I'm not referring to intent; I'm referring
> >> to classic
> >> > human factors usability limits.)
> >> >
> >> >       2.  One of the distinctions in the latest discussion
> >> is between
> >> > having the Note Well attempt to summarize what the IPR=20
> rules are,=20
> >> > versus having it merely declare that we have IPR rules and
> >> point the
> >> > reader to them.  For summary instruments, like a Note Well,
> >> the latter
> >> > approach makes far more sense.
> >> >
> >> >       3.  We need all of the IPR rules for IETF
> >> participation to be in
> >> > a single, simple, clear document that is easily
> >> understandable by an
> >> > average engineer. (See point 1.)
> >> >
> >> >
> >> > d/
> >> >
> >> > --
> >> > Dave Crocker
> >> > Brandenburg InternetWorking
> >> > bbiw.net
> >> >
> >>
> =

From brian.e.carpenter@gmail.com  Wed Jan 29 11:46:34 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0FB1A02F2 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 11:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m15NoUyVwdAF for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 11:46:33 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 103E81A029B for <ietf@ietf.org>; Wed, 29 Jan 2014 11:46:32 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id bj1so2180222pad.39 for <ietf@ietf.org>; Wed, 29 Jan 2014 11:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=VHwGxysJEy/B6dKTOVsxR5YwCDDxlPjoIgQsEPlDj8c=; b=Nu54oYdQ0Xc9LYwCSotCFUKjqGUoOKeqQLFG/EnX0PogNgn9NDOYtK24LeHyCMFkwV Y7cFTlNI4QUs2I4Ap1SW8oq+u/Hoon3bnch/QsdLdiEbMMnCK/ge/I9cLDjPfcdLFcTv 77mei/GCU0tAtEowis63n0nUZ6GXCC0K+sRNN2YNbV/FheCqEJYuknUEsHtfwOeBl/FW BrYypp2GTDvvP7zfsjonI4Zwbm+8/sCbM8ckSpR7Wp++dO1wRvb20jkjXqM5s+oE/N8F XAEJrhoEJf0y4LIrEXILU1NZvYLwAYejdJ3ZfBxGuCJwml2MXHy2CReB6K9ogrVNab1R e2HQ==
X-Received: by 10.68.183.228 with SMTP id ep4mr9819880pbc.67.1391024790063; Wed, 29 Jan 2014 11:46:30 -0800 (PST)
Received: from [192.168.178.23] (248.196.69.111.dynamic.snap.net.nz. [111.69.196.248]) by mx.google.com with ESMTPSA id si6sm23577374pab.19.2014.01.29.11.46.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 11:46:29 -0800 (PST)
Message-ID: <52E95A98.10607@gmail.com>
Date: Thu, 30 Jan 2014 08:46:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <52E924F6.3010405@dcrocker.net> <CAPv4CP_O5EnO7mFsqH4jMKJ3jAuQ-O_734s-z=zWmbs2Qh78bQ@mail.gmail.com>
In-Reply-To: <CAPv4CP_O5EnO7mFsqH4jMKJ3jAuQ-O_734s-z=zWmbs2Qh78bQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Dave Crocker <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 19:46:34 -0000

On 30/01/2014 05:15, Scott Brim wrote:
> On Wed, Jan 29, 2014 at 10:57 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> 
>> I take your suggestion to reduce to a simple guideline:
>>
>>      The default applicability for an IETF specification is the 'open'
>> Internet.  Any specification intended for more constrained use needs to
>> describe the constraints.  One means of achieving this can be an
>> "Applicability" section in the specification, with a description of
>> intended use.
> 
> 
> +1. Where would you put it?
> 

IMHO it should have been in RFC 1958, and I'm embarassed that
we missed this point back in 1996, because it's so fundamental.
I have a tickle at the back of my brain, because I think there
is text somewhere about how solutions designed for local use
have a nasty habit of appearing on the open Internet and
causing trouble, but I can't find it.

   Brian

From chair@ietf.org  Wed Jan 29 12:45:14 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1F21A02B6; Wed, 29 Jan 2014 12:45:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JTpmi4s37NOd; Wed, 29 Jan 2014 12:45:13 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id 36EDF1A02C0; Wed, 29 Jan 2014 12:45:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 18FE2A8EC2; Wed, 29 Jan 2014 12:44:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHNIeIQn3X9L; Wed, 29 Jan 2014 12:44:23 -0800 (PST)
Received: from [IPv6:2001:14b8:400:f33:19ba:a:36b2:549d] (unknown [IPv6:2001:14b8:400:f33:19ba:a:36b2:549d]) by c9a.amsl.com (Postfix) with ESMTPSA id A2928A8EB7; Wed, 29 Jan 2014 12:44:21 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Web-based email list archive search and browsing tool ready for use
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Wed, 29 Jan 2014 22:45:04 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FAF2859A-DEE5-473F-95EB-A191065F6742@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tools-discuss@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 20:45:15 -0000

The tool realizing the requirements we developed in RFC 6778 is ready =
for your use.

You'll find the service at https://mailarchive.ietf.org/
If you choose to log in, use your datatracker credentials.

If you see issues in the messages for a list, please contact the list's =
administrators (typically the working group chairs for working group =
lists).

If you encounter other problems or have suggestions for future =
improvements, please file a report using =
http://trac.tools.ietf.org/tools/ietfdb/newticket

If you find spam in the archives, please send a request to remove it =
including a link to the message to action@ietf.org.

We are still working towards providing IMAP access to the archives. That =
is not part of the tool at this time.

The old archives will continue to receive new messages and will be =
available in their current locations until further notice.

Early testers have reported this tool to be very useful. I hope you also =
find it to be so. (And I'd like to thank the tools team, AMS, and the =
early testers for this service!)

Jari Arkko
IETF Chair


From steve@shinkuro.com  Wed Jan 29 13:00:17 2014
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9481A0372; Wed, 29 Jan 2014 13:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DSL=1.129, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yvbVUNkcqtsi; Wed, 29 Jan 2014 13:00:14 -0800 (PST)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8E51A02B6; Wed, 29 Jan 2014 13:00:14 -0800 (PST)
Received: from dummy.name; Wed, 29 Jan 2014 21:00:11 +0000
Content-Type: text/plain; charset=us-ascii
Subject: Web-based email list archive search and browsing tool ready for use
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Steve Crocker <steve@shinkuro.com>
Date: Wed, 29 Jan 2014 23:00:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5120AAC-4FDE-4B3B-83BA-42BF75F044F8@shinkuro.com>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>, tools-discuss@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tools-discuss@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 21:00:17 -0000

The tool realizing the requirements we developed in RFC 6778 is ready =
for your use.

You'll find the service at https://mailarchive.ietf.org/
If you choose to log in, use your datatracker credentials.

If you see issues in the messages for a list, please contact the list's =
administrators (typically the working group chairs for working group =
lists).

If you encounter other problems or have suggestions for future =
improvements, please file a report using =
http://trac.tools.ietf.org/tools/ietfdb/newticket

If you find spam in the archives, please send a request to remove it =
including a link to the message to action@ietf.org.

We are still working towards providing IMAP access to the archives. That =
is not part of the tool at this time.

The old archives will continue to receive new messages and will be =
available in their current locations until further notice.

Early testers have reported this tool to be very useful. I hope you also =
find it to be so. (And I'd like to thank the tools team, AMS, and the =
early testers for this service!)

Jari Arkko
IETF Chair


From brian.e.carpenter@gmail.com  Wed Jan 29 16:32:15 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 098101A041A for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 16:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLi1i7fOwOMb for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 16:32:13 -0800 (PST)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4CA1A03F8 for <ietf@ietf.org>; Wed, 29 Jan 2014 16:32:13 -0800 (PST)
Received: by mail-pd0-f180.google.com with SMTP id x10so2362730pdj.39 for <ietf@ietf.org>; Wed, 29 Jan 2014 16:32:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=08ZuD3n9cPRse9mJ2vu8GmPK8pnpHtTOWLZv2oeTpg8=; b=Xe7Lld473S6V/80yeI8GAymSdr4FI42cPDI0UU4dTtFw9CvQA21fdrolK/l6MyUoW1 cnkyryeatishWc3/LJun110IgWPZWMRO5X5bhxg4vSr4oTsJhG8Qpu7aits36fLxzvVq FBcPghjvjDyt+HVJISIIIRD1lgcLE884Iazp7j10aPr7kVnliGnMBHd9qBNZ9Xmc7CRh P417umFwyOaAfQUrW51uIuCtajIkdEUsmicgi+sUKsM7x33chq7GaJLt4pXzHu+7V4Mz ijtzGcn5CAw0Tl+SuR4cZHdrNqDwp2REJDx6hBRXIdCv9bVbQGQhGVyALVeu/vC7cRbA E6QA==
X-Received: by 10.66.220.198 with SMTP id py6mr11156485pac.21.1391041930503; Wed, 29 Jan 2014 16:32:10 -0800 (PST)
Received: from [192.168.178.23] (248.196.69.111.dynamic.snap.net.nz. [111.69.196.248]) by mx.google.com with ESMTPSA id c7sm11201075pbt.0.2014.01.29.16.32.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 29 Jan 2014 16:32:09 -0800 (PST)
Message-ID: <52E99D8D.7030508@gmail.com>
Date: Thu, 30 Jan 2014 13:32:13 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <52E924F6.3010405@dcrocker.net> <CAPv4CP_O5EnO7mFsqH4jMKJ3jAuQ-O_734s-z=zWmbs2Qh78bQ@mail.gmail.com> <52E95A98.10607@gmail.com>
In-Reply-To: <52E95A98.10607@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 00:32:15 -0000

On 30/01/2014 08:46, Brian E Carpenter wrote:
> On 30/01/2014 05:15, Scott Brim wrote:
>> On Wed, Jan 29, 2014 at 10:57 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>
>>> I take your suggestion to reduce to a simple guideline:
>>>
>>>      The default applicability for an IETF specification is the 'open'
>>> Internet.  Any specification intended for more constrained use needs to
>>> describe the constraints.  One means of achieving this can be an
>>> "Applicability" section in the specification, with a description of
>>> intended use.
>>
>> +1. Where would you put it?
>>
> 
> IMHO it should have been in RFC 1958, and I'm embarassed that
> we missed this point back in 1996, because it's so fundamental.
> I have a tickle at the back of my brain, because I think there
> is text somewhere about how solutions designed for local use
> have a nasty habit of appearing on the open Internet and
> causing trouble, but I can't find it.

grep found this in RFC 3365 (BCP 61):

   History has shown that applications that operate using the TCP/IP
   Protocol Suite wind up being used over the Internet.  This is true
   even when the original application was not envisioned to be used in a
   "wide area" Internet environment.  If an application isn't designed
   to provide security, users of the application discover that they are
   vulnerable to attack.

       Brian

From fred@cisco.com  Wed Jan 29 21:57:01 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 626E51A04CE for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 21:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -115.036
X-Spam-Level: 
X-Spam-Status: No, score=-115.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DI5ytrsEF06w for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 21:57:00 -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 17B051A041A for <ietf@ietf.org>; Wed, 29 Jan 2014 21:57:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2128; q=dns/txt; s=iport; t=1391061417; x=1392271017; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=msLDyu+o35GbGN4oroULDgQ101aXIaP8Fx6VttI24jM=; b=mcPT6H1RMoXVkXCS8zApY5YUna52vqYAU2Iv6+n/b93UV5GXVn2rfWAe W/d7Tv3jmi3tavGBEMLAPLFoDutwocTi9uuAkfZuJnFALgY1FRUmTb+oo 6hnVqUfr1G84faSWDtjiDavCdTqebluX0+tI2EyQ2pQZEAO250vbMpHKN c=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhcFAHnp6VKtJV2Z/2dsb2JhbABZgwyBD70bgQQWdIIlAQEBAwF5BQsCAQhGIRElAgQOBQ4Nh1YDCQjCOw2JHBeMaoIVB4MkgRQEkD6BMoRMgWyMXoVBgy2CKg
X-IronPort-AV: E=Sophos;i="4.95,747,1384300800";  d="asc'?scan'208";a="300612720"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 30 Jan 2014 05:56:55 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0U5usmA006621 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jan 2014 05:56:54 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.227]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Wed, 29 Jan 2014 23:56:54 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Re: When is an idea a good idea?
Thread-Topic: When is an idea a good idea?
Thread-Index: AQHPHGWfBQVxYFPGjkanxk+TTvz3ipqdK+oA
Date: Thu, 30 Jan 2014 05:56:53 +0000
Message-ID: <74C96AE6-BD0C-4618-83E2-7D9D4F9C11F8@cisco.com>
References: <52E80FA9.5020704@gmail.com>
In-Reply-To: <52E80FA9.5020704@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.221.204]
Content-Type: multipart/signed; boundary="Apple-Mail=_3EE299EB-FEBF-41B3-B989-1451C768CFF8"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 05:57:01 -0000

--Apple-Mail=_3EE299EB-FEBF-41B3-B989-1451C768CFF8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Jan 28, 2014, at 3:14 PM, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

> Speaking only for myself, I don't expect Proposed Standards to be =
perfect, and to work perfectly in every situation, but if a =
specification doesn't describe any limits on applicability, I'm going to =
be evaluating it as if it will be used on the open Internet (that's what =
the "I" in "IETF" stands for).

Speaking for myself, I expect any solution that exists to be used on the =
open Internet. This is primarily because history says "they are", but =
also because many supposedly private networks in fact operate =
environments that aren't so very different from the open Internet. My =
reference point for that second factoid-from-my-perspectve is my =
employer's network, whose network dwarfs anything we had deployed in =
1990 and probably what we had deployed in 1995, including managed =
private interconnection to (I'm told) O(200) other companies and VPN =
access from computers via VPN (such as I am typing on right now) and =
from home office networks via VPN. Every company isn't Cisco, but I =
think you may be surprised how many have similarities - I'd guess that =
Fortune 1000 enterprise networks have strong structural similarities.

If you wouldn't use a solution, or a mitigated version of a solution, on =
the open Internet, I'm not so very sure I would recommend it to my IT =
department or my customers.

--Apple-Mail=_3EE299EB-FEBF-41B3-B989-1451C768CFF8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFS6emhbjEdbHIsm0MRAj1TAJ9/iLGgISakH0Y2+l5RJCdY2umzoQCgzwwN
Fed5cgY5XPb2ivjSS9vMww0=
=db+N
-----END PGP SIGNATURE-----

--Apple-Mail=_3EE299EB-FEBF-41B3-B989-1451C768CFF8--

From lars@netapp.com  Thu Jan 30 03:40:45 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 833B31A04DB; Thu, 30 Jan 2014 03:40:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.837
X-Spam-Level: 
X-Spam-Status: No, score=-6.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHE_KPSHLcEM; Thu, 30 Jan 2014 03:40:44 -0800 (PST)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 34B731A048C; Thu, 30 Jan 2014 03:40:41 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,749,1384329600"; d="scan'208";a="68455959"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx2-out.netapp.com with ESMTP; 30 Jan 2014 03:40:33 -0800
Received: from SACEXCMBX06-PRD.hq.netapp.com ([169.254.9.60]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Thu, 30 Jan 2014 03:40:30 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "irtf-announce@irtf.org" <irtf-announce@irtf.org>, "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>, "89attendees@ietf.org" <89attendees@ietf.org>
Subject: Applied Networking Research Prize 2014 presentation	s at IETF-89
Thread-Topic: Applied Networking Research Prize 2014 presentation	s at IETF-89
Thread-Index: AQHPHbATkRNzgl7Se0qVRHH/x8WXbw==
Date: Thu, 30 Jan 2014 11:40:28 +0000
Message-ID: <908363F3-EA4E-4FA9-B98C-72E6C39F6F81@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <66DBD8E371A8A246AB7C526CCEEFD9AB@hq.netapp.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "anrp@irtf.org" <anrp@irtf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 11:40:45 -0000

Hi,

we are extremely pleased to report that for the 2014 award period
of the Applied Networking Research Prize (ANRP), 46 eligible
nominations were received. Each submission was reviewed by four
members of the selection committee according to a diverse set of
criteria, including scientific excellence and substance, timeliness,
relevance, and potential impact on the Internet.

Based on this review, six submissions were awarded an Applied
Networking Research Prize for 2014. The first two prize winners
will present their work at IETF-89 in London, UK. The ANRP awards
for IETF-89 go to:

*** Kenny Paterson *** for finding and documenting new attacks
against TLS and DTLS:

    N. J. Al Fardan and K. G. Paterson. Lucky Thirteen: Breaking
    the TLS and DTLS Record Protocols. Proc. IEEE Symposium on
    Security and Privacy, pp. 526-540, San Francisco, CA, USA,
    May 2013.

*** Keith Winstein *** for designing a transport protocol for
interactive applications that desire high throughput and low delay:

    Keith Winstein, Anirudh Sivaraman, and Hari Balakrishnan
    Stochastic Forecasts Achieve High Throughput and Low Delay
    over Cellular Networks. Proc. 10th USENIX Symposium on
    Networked Systems Design and Implementation (NSDI), Lombard,
    IL, USA, April 2013.

Kenny and Keith have been invited to present his findings in the IRTF
Open Meeting during IETF-89 in London, UK. Join them there!

The call for ANRP nominations for the 2015 awards cycle will open in the
fall of 2014. Read more about the ANRP at http://irtf.org/anrp.

Please subscribe to the IRTF-Announce mailing list in order to receive
future calls for ANRP nominations and join ISOC to stay informed of
other networking research initiatives:

http://irtf.org/mailman/listinfo/irtf-announce
http://isoc.org/join

Regards,

Lars Eggert, IRTF Chair            http://irtf.org/anrp
Mat Ford, Internet Society         http://isoc.org/research

--

2014 ANRP Selection Committee

Mark Allman, ICIR
Marcelo Bagnulo, UC3M
Lou Berger, LabN
Olivier Bonaventure, UCL Louvain
Ross Callon, Juniper
KC Claffy, CAIDA
Lars Eggert, NetApp
Stephen Farrell, Trinity College Dublin
Olivier Festor, INRIA
Mat Ford, ISOC
Lisandro Granville, UFRGS
Volker Hilt, Bell Labs
Suresh Krishnan, Ericsson
Dan Massey, Colorado State
Al Morton, AT&T Laboratories
J=F6rg Ott, Aalto University
Colin Perkins, University of Glasgow
Stefano Previdi, Cisco
J=FCrgen Sch=F6nw=E4lder, Jacobs University Bremen
Joe Touch, USC/ISI
Rolf Winter, Hochschule Augsburg
Yang Richard Yang, Yale
Lixia Zhang, UCLA=

From hsantos@isdg.net  Thu Jan 30 05:09:49 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6DB1A0193 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 05:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YRm7oGUc_xm for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 05:09:46 -0800 (PST)
Received: from ntbbs.santronics.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3A52D1A0230 for <ietf@ietf.org>; Thu, 30 Jan 2014 05:09:35 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1846; t=1391087364; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=D4JEPeVZ+LGCiLqFrxKfePdxCBY=; b=jDc4DFQJqo8u8d0Uz8bP s3TERZMDaDgfDNwLkRggbDhhGx2Iop1PaZeSNK2nN0x7onHkIPDkFOGfs87wrDI4 nTCq1JV2R59VKF47zqjrYME0OzCgOpJ8qDiyRDwuq7i29QOkXm3NTrCVFpt7UNU8 sc0h2hhAfjBfJkTslyi5K9o=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 30 Jan 2014 08:09:24 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 369850797.4268.3056; Thu, 30 Jan 2014 08:09:23 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1846; t=1391086772; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=GYBAMzy Zoxu+dVTaEzOhHjluzQEz4mV+6NITfCO6zzs=; b=lOIdewNUv2xC5FamYc9bta+ UcTxYa5+w7obk0YEyM9H8awGeYmSls47hlKAjapDTVYsZ6BoTMy/D2s3n3GQZ43m tt8Ftnny82H/88kBM4zMgLiqmLyUXoSp4vsXidEvEIWEXmQ+YeC1tTYtpYc61C2l Nx7QxaIWfGVPjkUIWHI0=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 30 Jan 2014 07:59:32 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 4111118317.9.3740; Thu, 30 Jan 2014 07:59:31 -0500
Message-ID: <52EA4F05.10003@isdg.net>
Date: Thu, 30 Jan 2014 08:09:25 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: tools-discuss@ietf.org
Subject: Re: Web-based email list archive search and browsing tool ready for use
References: <FAF2859A-DEE5-473F-95EB-A191065F6742@ietf.org>
In-Reply-To: <FAF2859A-DEE5-473F-95EB-A191065F6742@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 13:09:49 -0000

Few comments

- Cool!

- UI (user interface) breaks down with Javascript (JS) disabled.  Not 
sure if JS is an UI ergonomic requirement.  Javascript is pretty much 
required these days but nothing other IETF tools does not require it. 
  Just saying.

- Sign in? Login?  Is there a IETF membership class?  Is there a 
sign-up?  There is enough white space on the initial page to put a 
note about "Signing In" to avoid similar/future (support) questions 
from "regular IETF users."

- Add a link back to the search page from the sign in page.  Back 
button is fine though.

- I would suggest that a search result have an initial sort by 
(descending) time.


-- 
HLS



On 1/29/2014 3:45 PM, IETF Chair wrote:
> The tool realizing the requirements we developed in RFC 6778 is ready for your use.
>
> You'll find the service at https://mailarchive.ietf.org/
> If you choose to log in, use your datatracker credentials.
>
> If you see issues in the messages for a list, please contact the list's administrators (typically the working group chairs for working group lists).
>
> If you encounter other problems or have suggestions for future improvements, please file a report using http://trac.tools.ietf.org/tools/ietfdb/newticket
>
> If you find spam in the archives, please send a request to remove it including a link to the message to action@ietf.org.
>
> We are still working towards providing IMAP access to the archives. That is not part of the tool at this time.
>
> The old archives will continue to receive new messages and will be available in their current locations until further notice.
>
> Early testers have reported this tool to be very useful. I hope you also find it to be so. (And I'd like to thank the tools team, AMS, and the early testers for this service!)
>
> Jari Arkko
> IETF Chair
>
>
>



From daedulus@btconnect.com  Thu Jan 30 06:17:05 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD1B1A0362 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 06:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.008
X-Spam-Level: 
X-Spam-Status: No, score=-1.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8oiTl86H3HW for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 06:17:03 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id A399E1A037E for <ietf@ietf.org>; Thu, 30 Jan 2014 06:17:02 -0800 (PST)
Received: from mail5-ch1-R.bigfish.com (10.43.68.233) by CH1EHSOBE021.bigfish.com (10.43.70.78) with Microsoft SMTP Server id 14.1.225.22; Thu, 30 Jan 2014 14:16:59 +0000
Received: from mail5-ch1 (localhost [127.0.0.1])	by mail5-ch1-R.bigfish.com (Postfix) with ESMTP id 0BF76420053;	Thu, 30 Jan 2014 14:16:59 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Idb82hzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL17326ah8275bh8275dh1de097h186068hz2dh2a8h5a9h839h93fhd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24d7h2516h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: =?utf-8?B?U0ZWOk5TUE07U0ZTOigxMDAwOTAwMSkoNjAwOTAwMSkoMTg5MDAyKSgxOTkw?= =?utf-8?B?MDIpKDUxNzA0MDA1KSgxMzQ2NDAwMykoMjQ0NTQwMDIpKDM3NzQ1NDAwMyko?= =?utf-8?B?NDc5MTc0MDAzKSg3NDg3NjAwMSkoODUzMDYwMDIpKDc2Nzk2MDAxKSg3Njc4?= =?utf-8?B?NjAwMSkoODA5NzYwMDEpKDE1OTc1NDQ1MDA2KSg4MzMyMjAwMSkoMTk1ODA0?= =?utf-8?B?MDUwMDEpKDkzMTM2MDAxKSgzMzY0NjAwMSkoOTM1MTYwMDIpKDg2MzYyMDAx?= =?utf-8?B?KSg5NDMxNjAwMikoOTM5MTYwMDIpKDE5NTgwMzk1MDAzKSg3NzE1NjAwMSko?= =?utf-8?B?NzcwOTYwMDEpKDc5MTAyMDAxKSg1NjE5NDQwMDIpKDU5NzY2MDAxKSg4OTk5?= =?utf-8?B?NjAwMSkoOTAxNDYwMDEpKDc3OTgyMDAxKSg4MTU0MjAwMSkoMzE5NjYwMDgp?= =?utf-8?B?KDQ0NzE2MDAyKSg2MjIzNjAwMikoOTI1NjYwMDEpKDg4MTM2MDAyKSg3NDM2?= =?utf-8?B?NjAwMSkoODMwNzIwMDIpKDgxMzQyMDAxKSg4NTg1MjAwMykoNjYwNjYwMDEp?= =?utf-8?B?KDc0NTAyMDAxKSg1NjgxNjAwNSkoNDc3NzYwMDMpKDYzNjk2MDAyKSg3NDY2?= =?utf-8?B?MjAwMSkoODAwMjIwMDEpKDQ3NDQ2MDAyKSg2NTgxNjAwMSkoNjkyMjYwMDEp?= =?utf-8?B?KDc0NzA2MDAxKSgxNTIwMjM0NTAwMykoNTA0NjYwMDIpKDg3MjY2MDAxKSg4?= =?utf-8?B?NzI4NjAwMSkoODc5NzYwMDEpKDYxMjk2MDAyKSgxNDQ5NjAwMSkoNDQ3MzYw?= =?utf-8?B?MDQpKDUxODU2MDAxKSgyMzY3NjAwMikoODQzOTIwMDEpKDU0MzE2MDAyKSg2?= =?utf-8?B?Mjk2NjAwMikoOTI3MjYwMDEpKDc2NDgyMDAxKSg1MDk4NjAwMSkoNTY3NzYw?= =?utf-8?B?MDEpKDQ2MTAyMDAxKSg0OTg2NjAwMSkoOTQ5NDYwMDEpKDUwMjI2MDAxKSg1?= =?utf-8?B?MzgwNjAwMSkoNDc5NzYwMDEpKDQyMTg2MDA0KSg0Mzk2MDAxKSg0NzczNjAw?= =?utf-8?B?MSkoNzQ0MTYwMDEpKDc3MjYwMDEpO0RJUjpPVVQ7U0ZQOjExMDE7U0NMOjE7?= =?utf-8?B?U1JWUjpEQjRQUjA3TUIyNTI7SDpEQjNQUkQwNDExSFQwMDQuZXVycHJkMDQu?= =?utf-8?B?cHJvZC5vdXRsb29rLmNvbTtDTElQOjE1Ny41Ni4yNTMuNTM7RlBSOkVDN0NG?= =?utf-8?B?MjY0LkFGRkE1REQxLkJERDE1MUJGLjQ2RTZFQzUxLjIwNjc1O0luZm9Ob1Jl?= =?utf-8?Q?cordsMX:1;A:0;LANG:en;?=
Received: from mail5-ch1 (localhost.localdomain [127.0.0.1]) by mail5-ch1 (MessageSwitch) id 1391091416821261_22966; Thu, 30 Jan 2014 14:16:56 +0000 (UTC)
Received: from CH1EHSMHS015.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.251])	by mail5-ch1.bigfish.com (Postfix) with ESMTP id C40CC26004D; Thu, 30 Jan 2014 14:16:56 +0000 (UTC)
Received: from AM2PRD0710HT004.eurprd07.prod.outlook.com (157.56.249.213) by CH1EHSMHS015.bigfish.com (10.43.70.15) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 30 Jan 2014 14:16:56 +0000
Received: from DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) by AM2PRD0710HT004.eurprd07.prod.outlook.com (10.255.165.39) with Microsoft SMTP Server (TLS) id 14.16.395.1; Thu, 30 Jan 2014 14:16:43 +0000
Received: from DB3PRD0411HT004.eurprd04.prod.outlook.com (157.56.253.53) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.868.8; Thu, 30 Jan 2014 14:16:42 +0000
Message-ID: <04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
References: <52E80FA9.5020704@gmail.com> <52E83926.1060909@gmail.com> <52E9222C.4060601@gmail.com>
Subject: Re: When is an idea a good idea?
Date: Thu, 30 Jan 2014 10:03:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.253.53]
X-ClientProxiedBy: AMSPR07CA015.eurprd07.prod.outlook.com (10.242.225.173) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 0107098B6C
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 14:17:05 -0000

----- Original Message -----
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: "IETF discussion list" <ietf@ietf.org>
Sent: Wednesday, January 29, 2014 3:45 PM
> I'm replying to Brian and to Scott here ...
>
> On 01/28/2014 05:11 PM, Brian E Carpenter wrote:
> > Hi Spencer,
> >
> > I think there's a bit more to be said, though.
> >
> > The goal is to make the Internet work better, not to make
> > private networks work better. Actually RFC 3935 defines
> > the IETF's scope as: "protocols and practices for which
> > secure and scalable implementations are expected to have
> > wide deployment and interoperation on the Internet, or to
> > form part of the infrastructure of the Internet."
> >
> > So if there are two ways of doing something, one of which
> > works globally and one of which only works locally, the choice
> > is a no-brainer. If a local-only solution comes up to the IESG,
>
> I couldn't agree with Brian and Scott more. I'm focusing on "comes up
to
> the IESG".
>
> My point is that the sooner someone asks "so, is this really intended
> for deployment on the global Internet?", the better. If working groups
> and authors thought about that before, or even during, WGLC time, I
> would like to think that we would have fewer cases where the question
is
> asked for the first time in AD review, or in directorate reviews, or
in
> IETF Last Call.

Spencer

By this criterion, would MPLS ever have entered the Standards Track?

It is a protocol that works supremely well within the private network of
an ISP; extending it to work across the Internet worldwide is more of a
challenge and, from what I recall, was not contemplated at the time of
RFC3031.

Tom Petch


>
> I don't think it's controversial at all that the IETF does better when
> documents don't encounter Late Surprises (tm). If the first time
someone
> says "but this is only intended to be used when $whatever" is in an
> email exchange during IETF Last Call, that's a Late Surprise, and the
> chances that the best outcome will happen aren't going up at that
point.
>
> As I said in my note, this is my personal suggestion. I'm not asking
for
> an Applicability Statement as a mandatory section in all IDs,
precisely
> because of Brian's point that the default is "this proposal is
suitable
> for deployment on the global Internet". I'm asking working groups and
> authors to consider whether that's true for their proposals, or if I
> should be reviewing with something else in mind.
>
> And as always, I encourage people to Do The Right Thing.
>
> Spencer
>
> > I think the first question is "Why isn't there a globally
> > applicable solution to this problem?". Then the second question
> > is "Why is this on the standards track, rather than being an
> > informational document for the record?". And the third question
> > is "Why is this better as an IETF document rather than an
> > Independent Submission?".
> >
> > There may be perfectly good answers to those questions, but
> > IMHO they need to be asked.
> >
> > Regards
> >     Brian
> >
> > On 29/01/2014 09:14, Spencer Dawkins wrote:
> >> Disclaimer - I'm one of the ADs who will be balloting your
documents
> >> until at least March 2015, but I'm only one of 15 ADs, and haven't
> >> talked about this with the rest of the IESG.
> >>
> >> The past week has brought me yet another example of an idea that
could
> >> be a good idea, but not under every possible set of conditions,
being
> >> evaluated as if we had to decide whether it was a good idea in all
> >> cases, or a bad idea. This might sound familiar to you, but if it
does,
> >> let's not talk about that specific case.
> >>
> >> The longer (and more painfully) we talk during Last Call, the more
> >> details we unearth that help me to understand what document
> >> authors/working groups are thinking, and that's good, but if it was
less
> >> painful, that would be even better.
> >>
> >> http://tools.ietf.org/html/rfc2026#section-3.2 describes
Applicability
> >> Statements, as distinct from Technical Specifications, and says
(among
> >> other things):
> >>
> >>     An Applicability Statement specifies how, and under what
> >>     circumstances, one or more TSs may be applied to support a
particular
> >>     Internet capability.
> >>
> >> ...
> >>
> >>     An AS may describe particular methods of using a TS in a
restricted
> >>     "domain of applicability", such as Internet routers, terminal
> >>     servers, Internet systems that interface to Ethernets, or
datagram-
> >>     based database servers.
> >>
> >>
> >> Speaking only for myself, I don't expect Proposed Standards to be
> >> perfect, and to work perfectly in every situation, but if a
> >> specification doesn't describe any limits on applicability, I'm
going to
> >> be evaluating it as if it will be used on the open Internet (that's
what
> >> the "I" in "IETF" stands for).
> >>
> >> If a draft says it's only intended to be used within an IP subnet,
I'd
> >> evaluate it differently. I might ask that the authors/working group
> >> consider what the TTL should be set to, so that what starts out
within
> >> an IP subnet stays within an IP subnet, but (to use one actual
example)
> >> we wouldn't be arguing about whether it's OK to send 32K max-length
> >> packets over an arbitrary Internet path at line rate without
getting any
> >> feedback about path capacity - there are probably paths where that
would
> >> work, and there are definitely paths where it would not.
> >>
> >> If a draft says it's only intended to be used on provisioned,
managed
> >> internetwork links subject to SLA monitoring, I'd evaluate it
differently.
> >>
> >> If a draft says "this is a hack, intended for use on old hardware
that
> >> can't do $X", I'd evaluate it differently.
> >>
> >> There are other limited-use scenarios that would make me evaluate a
> >> draft differently.
> >>
> >> None of this is a guaranteed pass, but it would help me a lot. It
would
> >> likely help other reviewers, too.
> >>
> >> So, if you don't intend for your draft to be used on the global
> >> Internet, please say so! As per
> >> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary
to
> >> put an Applicability Statement in a different draft; just a section
that
> >> says (another actual example) "this has been tested using these
> >> parameters on a lightly-loaded LAN, and it works there", that is
more
> >> helpful than a tug of war(*) about whether something is a good idea
or a
> >> bad idea in all situations, in front of a live studio audience.
> >>
> >> Thanks to Alia Atlas for nudging me to think about this more.
> >>
> >> Spencer
> >>
> >> p.s. If you have feedback about what I'm thinking, I'd love for you
to
> >> share it, whether on this list, privately to me, to the 2015
Nomcom, or
> >> to other Nomcom-eligible IETF participants when you're asking them
to to
> >> sign the recall petition ;-)
> >>
> >> (*) http://en.wikipedia.org/wiki/Tug_of_war
> >>
>
>



From spencerdawkins.ietf@gmail.com  Thu Jan 30 07:00:04 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A581A038C for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 07:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0yYkAi7r9X8Y for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 07:00:02 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 4656D1A0385 for <ietf@ietf.org>; Thu, 30 Jan 2014 07:00:02 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so3589898obc.36 for <ietf@ietf.org>; Thu, 30 Jan 2014 06:59:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=YurkGPwGHZsYiaCC8hLiQIQ0UlHWPfuwDsmsW3SmE8I=; b=rPpzyd4sTKEgs57lJ7zdj4q794gZjVGI1DqPTw/MmZZwKEB8LLp6l/B8AiI21GsXah j3kZ2zfrAHXjnDDXRV7ajrwNBFwJHwsIhyQkzcrYmfZRWiEzBfVSmXJRREhS5M1iBy/k 9deIgj+ORWmGPg3aKDxy+5AKUsgAWgTYkmMmx5/HLsTlZ+iyR69ibf2X4hvRpj0WAol6 OMXuBT+QJow1X5rwv/iL04oVu4v6DuZHIc0LYqJQXGIX+lxMMAvSnSbXdBGkzqujBidw gjchthqMq2dhr7zjuEC0zED4eFDjFdpw0XMMG2M9bzb/B6bb/RNc6fyzMqwXoKF9CvyH irVA==
X-Received: by 10.182.2.42 with SMTP id 10mr762666obr.73.1391093998969; Thu, 30 Jan 2014 06:59:58 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id ii8sm10521797obb.11.2014.01.30.06.59.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Jan 2014 06:59:58 -0800 (PST)
Message-ID: <52EA68ED.9010806@gmail.com>
Date: Thu, 30 Jan 2014 08:59:57 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <52E83926.1060909@gmail.com> <52E9222C.4060601@gmail.com> <04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net>
In-Reply-To: <04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net>
Content-Type: multipart/alternative; boundary="------------080101010102040503050209"
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 15:00:04 -0000

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

Hi, Tom,

Keeping in mind that my ask was based on what I, personally, would find 
helpful to see in documents and not just revealed during extended Last 
Call discussions as if they were the Dance of the Seven Veils, not 
intended to express opinions about what the IESG then was doing, and 
this is slippery-sloping towards a re-litigation of a couple of decades 
of IETF work ...

( http://en.wikipedia.org/wiki/Dance_of_the_Seven_Veils)

On 01/30/2014 04:03 AM, t.p. wrote:
> Spencer
>
> By this criterion, would MPLS ever have entered the Standards Track?

Disclaimer: I'm actively chasing history on the "I stands for Internet" 
topic, so I may be smarter tomorrow, but this is what I'm looking at today.

I wasn't there (coincidentally, I was working on TSV stuff during the 
early days of tag and label switching), and folks on this list were, but 
I'm given to understand that this was discussed at the time. I've heard 
the statement "Anything that two consenting routers do over a link layer 
is their own business" attributed to Tony Li, and that makes more sense 
if it was half of a discussion, and the other half could be simplified 
to "is not".

RFC 3031 is dated 2001. The IETF mission statement, 
http://www.ietf.org/rfc/rfc3935.txt, was published after that (in 2004, 
but those ideas didn't spring from nothing in December of 2003), and it 
says things like

 >    In attempting to resolve the question of the IETF's scope, perhaps
 >    the fairest balance is struck by this formulation: "protocols and
 >    practices for which secure and scalable implementations are expected
 >    to have wide deployment and interoperation on the Internet, or to
 >    form part of the infrastructure of the Internet."

I'm assuming the last part of this paragraph is intended to cover things 
like MPLS, DHCP, and such.

Perhaps there are people on this list who would correct me if I 
misstated this.

> It is a protocol that works supremely well within the private network of
> an ISP; extending it to work across the Internet worldwide is more of a
> challenge and, from what I recall, was not contemplated at the time of
> RFC3031.

Indeed. I offer 
http://www.ietf.org/mail-archive/web/ietf/current/msg85344.html for your 
perusal. It's a thread I'm reading with some interest :p

Spencer
Spencer

--------------080101010102040503050209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi, Tom,<br>
    <br>
    Keeping in mind that my ask was based on what I, personally, would
    find helpful to see in documents and not just revealed during
    extended Last Call discussions as if they were the Dance of the
    Seven Veils, not intended to express opinions about what the IESG
    then was doing, and this is slippery-sloping towards a re-litigation
    of a couple of decades of IETF work ...<br>
    <br>
    (
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <a href="http://en.wikipedia.org/wiki/Dance_of_the_Seven_Veils">http://en.wikipedia.org/wiki/Dance_of_the_Seven_Veils</a>)<br>
    <br>
    <div class="moz-cite-prefix">On 01/30/2014 04:03 AM, t.p. wrote:<br>
    </div>
    <blockquote
      cite="mid:04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">Spencer

By this criterion, would MPLS ever have entered the Standards Track?
</pre>
    </blockquote>
    <br>
    Disclaimer: I'm actively chasing history on the "I stands for
    Internet" topic, so I may be smarter tomorrow, but this is what I'm
    looking at today.<br>
    <br>
    I wasn't there (coincidentally, I was working on TSV stuff during
    the early days of tag and label switching), and folks on this list
    were, but I'm given to understand that this was discussed at the
    time. I've heard the statement "Anything that two consenting routers
    do over a link layer is their own business" attributed to Tony Li,
    and that makes more sense if it was half of a discussion, and the
    other half could be simplified to "is not".<br>
    <br>
    RFC 3031 is dated 2001. The IETF mission statement,
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/rfc/rfc3935.txt">http://www.ietf.org/rfc/rfc3935.txt</a>, was published after that (in
    2004, but those ideas didn't spring from nothing in December of
    2003), and it says things like<br>
    <br>
    &gt;Â Â Â  In attempting to resolve the question of the IETF's scope,
    perhaps<br>
    &gt;Â Â Â  the fairest balance is struck by this formulation:
    "protocols and<br>
    &gt;Â Â Â  practices for which secure and scalable implementations are
    expected<br>
    &gt;Â Â Â  to have wide deployment and interoperation on the Internet,
    or to<br>
    &gt;Â Â Â  form part of the infrastructure of the Internet."<br>
    <br>
    I'm assuming the last part of this paragraph is intended to cover
    things like MPLS, DHCP, and such.<br>
    <br>
    Perhaps there are people on this list who would correct me if I
    misstated this.<br>
    <br>
    <blockquote type="cite">
      <pre wrap="">It is a protocol that works supremely well within the private network of
an ISP; extending it to work across the Internet worldwide is more of a
challenge and, from what I recall, was not contemplated at the time of
RFC3031.</pre>
    </blockquote>
    <br>
    Indeed. I offer
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    <a
      href="http://www.ietf.org/mail-archive/web/ietf/current/msg85344.html">http://www.ietf.org/mail-archive/web/ietf/current/msg85344.html</a>
    for your perusal. It's a thread I'm reading with some interest :p<br>
    <br>
    Spencer<br>
    Spencer<br>
  </body>
</html>

--------------080101010102040503050209--

From iab-chair@iab.org  Thu Jan 30 07:13:52 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 165DC1A041E; Thu, 30 Jan 2014 07:13:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hm08iAbLgMoe; Thu, 30 Jan 2014 07:13:49 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id BE9241A041A; Thu, 30 Jan 2014 07:13:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 212409FBB3; Thu, 30 Jan 2014 07:12:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8AxDnT6qLcMw; Thu, 30 Jan 2014 07:12:56 -0800 (PST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) by c9a.amsl.com (Postfix) with ESMTPSA id 808819FB36; Thu, 30 Jan 2014 07:12:55 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Call for nominations: IETF appointment to the ISOC Board of Trustees
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Thu, 30 Jan 2014 10:13:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2771279D-9BDD-46CE-88F5-0728F1B35CBE@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IAB <iab@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 15:13:52 -0000

The Internet Society (ISOC) provides organizational and financial =
support for the IETF. As part of the arrangements between ISOC and the =
IETF, the IETF is called upon to name 3 Trustees to its Board (BoT), =
with staggered 3 year terms. This requires that the IETF select one =
Trustee each year.=20
=20
This year, the IAB will select one person for a term ending in mid-2017.=20=

=20
A description of the IAB's process for selecting the Trustee each year =
can be found in RFC 3677, with this year's timeline as follows:=20
=20
* January 30, 2014 : Open nomination period

* February 27, 2014 : Close of the nomination period=20

* No later than April 10, 2014 : IAB selection delivered to IESG for =
confirmation

* No later than May 23, 2014 : Delivery of final confirmed selection to =
the ISOC Elections Committee for announcement with the rest of the new =
ISOC BoT slate.=20
=20
=20
Nominations=20
-----------=20
=20
Nominations (including self-nominations) should be sent to the IAB -- =
iab@iab.org.  Please include e-mail contact details with the nomination.=20=

 =20
Nomination Details=20
-----------------=20
=20
Nominees should be aware that ISOC Trustees are elected to three year =
terms with approximately one third of the Board of Trustees elected each =
year. The responsibilities of a Trustee include fiscal management of the =
Internet Society, fundraising, and participation in Board meetings plus =
conference-call meetings, as detailed by the ISOC Bylaws:
=
http://www.internetsociety.org/who-we-are/governance-and-policies/amended-=
and-restated-laws-internet-society

The desirable characteristics of a candidate that are specific to the =
IETF-selected ISOC BoT member are outlined in section 2 of RFC 3677.=20
=20
Nominees are asked to provide to the IAB:=20
=20
1. Confirmation of their willingness to be considered within this =
process.=20
=20
2. Full name and contact information.=20
=20
3. A statement confirming willingness and ability to devote an =
appropriate level of time to activities associated with the position of =
Trustee.=20
=20
4. A brief biography outlining experience and background.=20
=20
5. A statement of interests, concerns about the Internet Society, goals =
as a Trustee, and motivation to serve as a Trustee.=20
=20
6. Any further information that is relevant to the work of the IAB in =
considering your nomination.=20
=20
Time Commitment=20
---------------=20
=20
Trustees are expected to commit the time necessary to perform regular =
board and committee business. Trustees are also expected to allocate =
some time to attend and prepare for meetings.=20

=20
Care of Personal Information=20
----------------------------=20
=20
The following procedures will be used by the IAB in managing this =
process:=20
=20
- The candidate's name will be published, with all other candidate =
names, at the close of the nominations period.
=20
- Excerpts of the information provided to the IAB by the nominated =
candidate will be passed to the IESG as part of the confirmation =
process. The IESG will be requested to maintain confidentiality of the =
candidate's information.
=20
- Except as noted above, all information provided to the IAB during this =
process will be kept confidential to the IAB.=20

=20
Current IETF-Selected Trustees=20
------------------------------

The current IETF-Selected ISOC Trustees and their term of appointment =
are:=20
=20
- Bert Wijnen 2011 - 2014
- Eric Burger 2012 - 2015
- Bob Hinden 2013 - 2016=20


On behalf of the IAB,
Russ Housley
IAB Chair=

From scott.brim@gmail.com  Thu Jan 30 07:17:00 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E95BD1A0398 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 07:17:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sIk3wQ0xK5w4 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 07:16:57 -0800 (PST)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id AD64A1A038E for <ietf@ietf.org>; Thu, 30 Jan 2014 07:16:57 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id i7so3790264oag.1 for <ietf@ietf.org>; Thu, 30 Jan 2014 07:16:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rTkNMNgq5Kcb6olcWpIIukyMrPIbC6Ec/x8QjQy1JCY=; b=fQdgotdWd9/zjyaE/AaBs1SZJuW+d6Qb/6i/CZXpLnldUoZoYX+B2daar5KTKje8j0 PipbDchAY6z6+Ceh0KKWFflt7mtg6/sLdrd3BbklSN7TWH+kecxBioJZhMY0Lyuq+ft0 SSgWos1e9+4hbzc9+a7aFKw0+vfzUuydpfzDq+ql1ySwbggXEaO2HG44+xTG1jiApBu9 Sl5FdGsGaujNdVHI1nrDeNm497DbSmkJBTsNA4KsawXTNVxoLtk3y8yT1z9m1sskoTNd bF6JAqq2QnDq+7g1JiV2/3GZrBskFECZmChSoH5nrAaZqiOa4EKMfOGR8ELmpZont6W9 CyNg==
MIME-Version: 1.0
X-Received: by 10.60.50.202 with SMTP id e10mr11929224oeo.39.1391095014331; Thu, 30 Jan 2014 07:16:54 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 30 Jan 2014 07:16:54 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 30 Jan 2014 07:16:54 -0800 (PST)
In-Reply-To: <04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net>
References: <52E80FA9.5020704@gmail.com> <52E83926.1060909@gmail.com> <52E9222C.4060601@gmail.com> <04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net>
Date: Thu, 30 Jan 2014 10:16:54 -0500
Message-ID: <CAPv4CP8G9hNGZWwEHxDVnNo7AtXs6kuZmnPCh5dCaO9H_+i=Vw@mail.gmail.com>
Subject: Re: When is an idea a good idea?
From: Scott Brim <scott.brim@gmail.com>
To: "t. p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=001a11c309462d9d8404f1318c9e
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 15:17:01 -0000

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

Tom: but MPLS could be used anywhere. It isn't designed in a way that using
it would be dangerous.

Fred: but there will always be environments that would benefit from special
optimizations, such as cellular or satellite or high-performance computing.
It's reasonable for us to standardize for the special needs of those
environments too - they need interoperability and they use IP.

Scott
On Jan 30, 2014 9:17 AM, "t.p." <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
> To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> Cc: "IETF discussion list" <ietf@ietf.org>
> Sent: Wednesday, January 29, 2014 3:45 PM
> > I'm replying to Brian and to Scott here ...
> >
> > On 01/28/2014 05:11 PM, Brian E Carpenter wrote:
> > > Hi Spencer,
> > >
> > > I think there's a bit more to be said, though.
> > >
> > > The goal is to make the Internet work better, not to make
> > > private networks work better. Actually RFC 3935 defines
> > > the IETF's scope as: "protocols and practices for which
> > > secure and scalable implementations are expected to have
> > > wide deployment and interoperation on the Internet, or to
> > > form part of the infrastructure of the Internet."
> > >
> > > So if there are two ways of doing something, one of which
> > > works globally and one of which only works locally, the choice
> > > is a no-brainer. If a local-only solution comes up to the IESG,
> >
> > I couldn't agree with Brian and Scott more. I'm focusing on "comes up
> to
> > the IESG".
> >
> > My point is that the sooner someone asks "so, is this really intended
> > for deployment on the global Internet?", the better. If working groups
> > and authors thought about that before, or even during, WGLC time, I
> > would like to think that we would have fewer cases where the question
> is
> > asked for the first time in AD review, or in directorate reviews, or
> in
> > IETF Last Call.
>
> Spencer
>
> By this criterion, would MPLS ever have entered the Standards Track?
>
> It is a protocol that works supremely well within the private network of
> an ISP; extending it to work across the Internet worldwide is more of a
> challenge and, from what I recall, was not contemplated at the time of
> RFC3031.
>
> Tom Petch
>
>
> >
> > I don't think it's controversial at all that the IETF does better when
> > documents don't encounter Late Surprises (tm). If the first time
> someone
> > says "but this is only intended to be used when $whatever" is in an
> > email exchange during IETF Last Call, that's a Late Surprise, and the
> > chances that the best outcome will happen aren't going up at that
> point.
> >
> > As I said in my note, this is my personal suggestion. I'm not asking
> for
> > an Applicability Statement as a mandatory section in all IDs,
> precisely
> > because of Brian's point that the default is "this proposal is
> suitable
> > for deployment on the global Internet". I'm asking working groups and
> > authors to consider whether that's true for their proposals, or if I
> > should be reviewing with something else in mind.
> >
> > And as always, I encourage people to Do The Right Thing.
> >
> > Spencer
> >
> > > I think the first question is "Why isn't there a globally
> > > applicable solution to this problem?". Then the second question
> > > is "Why is this on the standards track, rather than being an
> > > informational document for the record?". And the third question
> > > is "Why is this better as an IETF document rather than an
> > > Independent Submission?".
> > >
> > > There may be perfectly good answers to those questions, but
> > > IMHO they need to be asked.
> > >
> > > Regards
> > >     Brian
> > >
> > > On 29/01/2014 09:14, Spencer Dawkins wrote:
> > >> Disclaimer - I'm one of the ADs who will be balloting your
> documents
> > >> until at least March 2015, but I'm only one of 15 ADs, and haven't
> > >> talked about this with the rest of the IESG.
> > >>
> > >> The past week has brought me yet another example of an idea that
> could
> > >> be a good idea, but not under every possible set of conditions,
> being
> > >> evaluated as if we had to decide whether it was a good idea in all
> > >> cases, or a bad idea. This might sound familiar to you, but if it
> does,
> > >> let's not talk about that specific case.
> > >>
> > >> The longer (and more painfully) we talk during Last Call, the more
> > >> details we unearth that help me to understand what document
> > >> authors/working groups are thinking, and that's good, but if it was
> less
> > >> painful, that would be even better.
> > >>
> > >> http://tools.ietf.org/html/rfc2026#section-3.2 describes
> Applicability
> > >> Statements, as distinct from Technical Specifications, and says
> (among
> > >> other things):
> > >>
> > >>     An Applicability Statement specifies how, and under what
> > >>     circumstances, one or more TSs may be applied to support a
> particular
> > >>     Internet capability.
> > >>
> > >> ...
> > >>
> > >>     An AS may describe particular methods of using a TS in a
> restricted
> > >>     "domain of applicability", such as Internet routers, terminal
> > >>     servers, Internet systems that interface to Ethernets, or
> datagram-
> > >>     based database servers.
> > >>
> > >>
> > >> Speaking only for myself, I don't expect Proposed Standards to be
> > >> perfect, and to work perfectly in every situation, but if a
> > >> specification doesn't describe any limits on applicability, I'm
> going to
> > >> be evaluating it as if it will be used on the open Internet (that's
> what
> > >> the "I" in "IETF" stands for).
> > >>
> > >> If a draft says it's only intended to be used within an IP subnet,
> I'd
> > >> evaluate it differently. I might ask that the authors/working group
> > >> consider what the TTL should be set to, so that what starts out
> within
> > >> an IP subnet stays within an IP subnet, but (to use one actual
> example)
> > >> we wouldn't be arguing about whether it's OK to send 32K max-length
> > >> packets over an arbitrary Internet path at line rate without
> getting any
> > >> feedback about path capacity - there are probably paths where that
> would
> > >> work, and there are definitely paths where it would not.
> > >>
> > >> If a draft says it's only intended to be used on provisioned,
> managed
> > >> internetwork links subject to SLA monitoring, I'd evaluate it
> differently.
> > >>
> > >> If a draft says "this is a hack, intended for use on old hardware
> that
> > >> can't do $X", I'd evaluate it differently.
> > >>
> > >> There are other limited-use scenarios that would make me evaluate a
> > >> draft differently.
> > >>
> > >> None of this is a guaranteed pass, but it would help me a lot. It
> would
> > >> likely help other reviewers, too.
> > >>
> > >> So, if you don't intend for your draft to be used on the global
> > >> Internet, please say so! As per
> > >> http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary
> to
> > >> put an Applicability Statement in a different draft; just a section
> that
> > >> says (another actual example) "this has been tested using these
> > >> parameters on a lightly-loaded LAN, and it works there", that is
> more
> > >> helpful than a tug of war(*) about whether something is a good idea
> or a
> > >> bad idea in all situations, in front of a live studio audience.
> > >>
> > >> Thanks to Alia Atlas for nudging me to think about this more.
> > >>
> > >> Spencer
> > >>
> > >> p.s. If you have feedback about what I'm thinking, I'd love for you
> to
> > >> share it, whether on this list, privately to me, to the 2015
> Nomcom, or
> > >> to other Nomcom-eligible IETF participants when you're asking them
> to to
> > >> sign the recall petition ;-)
> > >>
> > >> (*) http://en.wikipedia.org/wiki/Tug_of_war
> > >>
> >
> >
>
>
>

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

<p dir=3D"ltr">Tom: but MPLS could be used anywhere. It isn&#39;t designed =
in a way that using it would be dangerous. </p>
<p dir=3D"ltr">Fred: but there will always be environments that would benef=
it from special optimizations, such as cellular or satellite or high-perfor=
mance computing. It&#39;s reasonable for us to standardize for the special =
needs of those environments too - they need interoperability and they use I=
P. </p>

<p dir=3D"ltr">Scott</p>
<div class=3D"gmail_quote">On Jan 30, 2014 9:17 AM, &quot;t.p.&quot; &lt;<a=
 href=3D"mailto:daedulus@btconnect.com">daedulus@btconnect.com</a>&gt; wrot=
e:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
----- Original Message -----<br>
From: &quot;Spencer Dawkins&quot; &lt;<a href=3D"mailto:spencerdawkins.ietf=
@gmail.com">spencerdawkins.ietf@gmail.com</a>&gt;<br>
To: &quot;Brian E Carpenter&quot; &lt;<a href=3D"mailto:brian.e.carpenter@g=
mail.com">brian.e.carpenter@gmail.com</a>&gt;<br>
Cc: &quot;IETF discussion list&quot; &lt;<a href=3D"mailto:ietf@ietf.org">i=
etf@ietf.org</a>&gt;<br>
Sent: Wednesday, January 29, 2014 3:45 PM<br>
&gt; I&#39;m replying to Brian and to Scott here ...<br>
&gt;<br>
&gt; On 01/28/2014 05:11 PM, Brian E Carpenter wrote:<br>
&gt; &gt; Hi Spencer,<br>
&gt; &gt;<br>
&gt; &gt; I think there&#39;s a bit more to be said, though.<br>
&gt; &gt;<br>
&gt; &gt; The goal is to make the Internet work better, not to make<br>
&gt; &gt; private networks work better. Actually RFC 3935 defines<br>
&gt; &gt; the IETF&#39;s scope as: &quot;protocols and practices for which<=
br>
&gt; &gt; secure and scalable implementations are expected to have<br>
&gt; &gt; wide deployment and interoperation on the Internet, or to<br>
&gt; &gt; form part of the infrastructure of the Internet.&quot;<br>
&gt; &gt;<br>
&gt; &gt; So if there are two ways of doing something, one of which<br>
&gt; &gt; works globally and one of which only works locally, the choice<br=
>
&gt; &gt; is a no-brainer. If a local-only solution comes up to the IESG,<b=
r>
&gt;<br>
&gt; I couldn&#39;t agree with Brian and Scott more. I&#39;m focusing on &q=
uot;comes up<br>
to<br>
&gt; the IESG&quot;.<br>
&gt;<br>
&gt; My point is that the sooner someone asks &quot;so, is this really inte=
nded<br>
&gt; for deployment on the global Internet?&quot;, the better. If working g=
roups<br>
&gt; and authors thought about that before, or even during, WGLC time, I<br=
>
&gt; would like to think that we would have fewer cases where the question<=
br>
is<br>
&gt; asked for the first time in AD review, or in directorate reviews, or<b=
r>
in<br>
&gt; IETF Last Call.<br>
<br>
Spencer<br>
<br>
By this criterion, would MPLS ever have entered the Standards Track?<br>
<br>
It is a protocol that works supremely well within the private network of<br=
>
an ISP; extending it to work across the Internet worldwide is more of a<br>
challenge and, from what I recall, was not contemplated at the time of<br>
RFC3031.<br>
<br>
Tom Petch<br>
<br>
<br>
&gt;<br>
&gt; I don&#39;t think it&#39;s controversial at all that the IETF does bet=
ter when<br>
&gt; documents don&#39;t encounter Late Surprises (tm). If the first time<b=
r>
someone<br>
&gt; says &quot;but this is only intended to be used when $whatever&quot; i=
s in an<br>
&gt; email exchange during IETF Last Call, that&#39;s a Late Surprise, and =
the<br>
&gt; chances that the best outcome will happen aren&#39;t going up at that<=
br>
point.<br>
&gt;<br>
&gt; As I said in my note, this is my personal suggestion. I&#39;m not aski=
ng<br>
for<br>
&gt; an Applicability Statement as a mandatory section in all IDs,<br>
precisely<br>
&gt; because of Brian&#39;s point that the default is &quot;this proposal i=
s<br>
suitable<br>
&gt; for deployment on the global Internet&quot;. I&#39;m asking working gr=
oups and<br>
&gt; authors to consider whether that&#39;s true for their proposals, or if=
 I<br>
&gt; should be reviewing with something else in mind.<br>
&gt;<br>
&gt; And as always, I encourage people to Do The Right Thing.<br>
&gt;<br>
&gt; Spencer<br>
&gt;<br>
&gt; &gt; I think the first question is &quot;Why isn&#39;t there a globall=
y<br>
&gt; &gt; applicable solution to this problem?&quot;. Then the second quest=
ion<br>
&gt; &gt; is &quot;Why is this on the standards track, rather than being an=
<br>
&gt; &gt; informational document for the record?&quot;. And the third quest=
ion<br>
&gt; &gt; is &quot;Why is this better as an IETF document rather than an<br=
>
&gt; &gt; Independent Submission?&quot;.<br>
&gt; &gt;<br>
&gt; &gt; There may be perfectly good answers to those questions, but<br>
&gt; &gt; IMHO they need to be asked.<br>
&gt; &gt;<br>
&gt; &gt; Regards<br>
&gt; &gt; =A0 =A0 Brian<br>
&gt; &gt;<br>
&gt; &gt; On 29/01/2014 09:14, Spencer Dawkins wrote:<br>
&gt; &gt;&gt; Disclaimer - I&#39;m one of the ADs who will be balloting you=
r<br>
documents<br>
&gt; &gt;&gt; until at least March 2015, but I&#39;m only one of 15 ADs, an=
d haven&#39;t<br>
&gt; &gt;&gt; talked about this with the rest of the IESG.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The past week has brought me yet another example of an idea t=
hat<br>
could<br>
&gt; &gt;&gt; be a good idea, but not under every possible set of condition=
s,<br>
being<br>
&gt; &gt;&gt; evaluated as if we had to decide whether it was a good idea i=
n all<br>
&gt; &gt;&gt; cases, or a bad idea. This might sound familiar to you, but i=
f it<br>
does,<br>
&gt; &gt;&gt; let&#39;s not talk about that specific case.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; The longer (and more painfully) we talk during Last Call, the=
 more<br>
&gt; &gt;&gt; details we unearth that help me to understand what document<b=
r>
&gt; &gt;&gt; authors/working groups are thinking, and that&#39;s good, but=
 if it was<br>
less<br>
&gt; &gt;&gt; painful, that would be even better.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; <a href=3D"http://tools.ietf.org/html/rfc2026#section-3.2" ta=
rget=3D"_blank">http://tools.ietf.org/html/rfc2026#section-3.2</a> describe=
s<br>
Applicability<br>
&gt; &gt;&gt; Statements, as distinct from Technical Specifications, and sa=
ys<br>
(among<br>
&gt; &gt;&gt; other things):<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 An Applicability Statement specifies how, and under w=
hat<br>
&gt; &gt;&gt; =A0 =A0 circumstances, one or more TSs may be applied to supp=
ort a<br>
particular<br>
&gt; &gt;&gt; =A0 =A0 Internet capability.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; ...<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; =A0 =A0 An AS may describe particular methods of using a TS i=
n a<br>
restricted<br>
&gt; &gt;&gt; =A0 =A0 &quot;domain of applicability&quot;, such as Internet=
 routers, terminal<br>
&gt; &gt;&gt; =A0 =A0 servers, Internet systems that interface to Ethernets=
, or<br>
datagram-<br>
&gt; &gt;&gt; =A0 =A0 based database servers.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Speaking only for myself, I don&#39;t expect Proposed Standar=
ds to be<br>
&gt; &gt;&gt; perfect, and to work perfectly in every situation, but if a<b=
r>
&gt; &gt;&gt; specification doesn&#39;t describe any limits on applicabilit=
y, I&#39;m<br>
going to<br>
&gt; &gt;&gt; be evaluating it as if it will be used on the open Internet (=
that&#39;s<br>
what<br>
&gt; &gt;&gt; the &quot;I&quot; in &quot;IETF&quot; stands for).<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; If a draft says it&#39;s only intended to be used within an I=
P subnet,<br>
I&#39;d<br>
&gt; &gt;&gt; evaluate it differently. I might ask that the authors/working=
 group<br>
&gt; &gt;&gt; consider what the TTL should be set to, so that what starts o=
ut<br>
within<br>
&gt; &gt;&gt; an IP subnet stays within an IP subnet, but (to use one actua=
l<br>
example)<br>
&gt; &gt;&gt; we wouldn&#39;t be arguing about whether it&#39;s OK to send =
32K max-length<br>
&gt; &gt;&gt; packets over an arbitrary Internet path at line rate without<=
br>
getting any<br>
&gt; &gt;&gt; feedback about path capacity - there are probably paths where=
 that<br>
would<br>
&gt; &gt;&gt; work, and there are definitely paths where it would not.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; If a draft says it&#39;s only intended to be used on provisio=
ned,<br>
managed<br>
&gt; &gt;&gt; internetwork links subject to SLA monitoring, I&#39;d evaluat=
e it<br>
differently.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; If a draft says &quot;this is a hack, intended for use on old=
 hardware<br>
that<br>
&gt; &gt;&gt; can&#39;t do $X&quot;, I&#39;d evaluate it differently.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; There are other limited-use scenarios that would make me eval=
uate a<br>
&gt; &gt;&gt; draft differently.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; None of this is a guaranteed pass, but it would help me a lot=
. It<br>
would<br>
&gt; &gt;&gt; likely help other reviewers, too.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; So, if you don&#39;t intend for your draft to be used on the =
global<br>
&gt; &gt;&gt; Internet, please say so! As per<br>
&gt; &gt;&gt; <a href=3D"http://tools.ietf.org/html/rfc2026#section-3.3" ta=
rget=3D"_blank">http://tools.ietf.org/html/rfc2026#section-3.3</a>, it&#39;=
s not necessary<br>
to<br>
&gt; &gt;&gt; put an Applicability Statement in a different draft; just a s=
ection<br>
that<br>
&gt; &gt;&gt; says (another actual example) &quot;this has been tested usin=
g these<br>
&gt; &gt;&gt; parameters on a lightly-loaded LAN, and it works there&quot;,=
 that is<br>
more<br>
&gt; &gt;&gt; helpful than a tug of war(*) about whether something is a goo=
d idea<br>
or a<br>
&gt; &gt;&gt; bad idea in all situations, in front of a live studio audienc=
e.<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Thanks to Alia Atlas for nudging me to think about this more.=
<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Spencer<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; p.s. If you have feedback about what I&#39;m thinking, I&#39;=
d love for you<br>
to<br>
&gt; &gt;&gt; share it, whether on this list, privately to me, to the 2015<=
br>
Nomcom, or<br>
&gt; &gt;&gt; to other Nomcom-eligible IETF participants when you&#39;re as=
king them<br>
to to<br>
&gt; &gt;&gt; sign the recall petition ;-)<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; (*) <a href=3D"http://en.wikipedia.org/wiki/Tug_of_war" targe=
t=3D"_blank">http://en.wikipedia.org/wiki/Tug_of_war</a><br>
&gt; &gt;&gt;<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div>

--001a11c309462d9d8404f1318c9e--

From geoff.mulligan@nist.gov  Wed Jan 29 10:22:53 2014
Return-Path: <geoff.mulligan@nist.gov>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 397B41A03D4; Wed, 29 Jan 2014 10:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WjFoCBxYALQ8; Wed, 29 Jan 2014 10:22:50 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0241.outbound.protection.outlook.com [207.46.163.241]) by ietfa.amsl.com (Postfix) with ESMTP id 06A9E1A03CB; Wed, 29 Jan 2014 10:22:49 -0800 (PST)
Received: from BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) by BLUPR09MB054.namprd09.prod.outlook.com (10.255.211.148) with Microsoft SMTP Server (TLS) id 15.0.859.15; Wed, 29 Jan 2014 18:22:45 +0000
Received: from BLUPR09MB054.namprd09.prod.outlook.com ([10.255.211.148]) by BLUPR09MB054.namprd09.prod.outlook.com ([169.254.9.198]) with mapi id 15.00.0859.020; Wed, 29 Jan 2014 18:22:45 +0000
From: "Mulligan, Geoff" <geoff.mulligan@nist.gov>
To: Ned Freed <ned.freed@mrochek.com>
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Topic: Third party disclosures and NDAs (Re: Problem with new Note Well )
Thread-Index: AQHPG3klyCBjqxHw+E6Dqsh/YOVH+ZqYyr7pgAGx/bGAAYnplQ==
Date: Wed, 29 Jan 2014 18:22:45 +0000
Message-ID: <db83aff680884b6789f9a981db6e4e9e@BLUPR09MB054.namprd09.prod.outlook.com>
References: <CALaySJ+5+a1P0a-tPEVdmmxXztDmHyT2AHWzBYm8Exn8MEG+cQ@mail.gmail.com> <1032B807-2417-449B-ADE3-E06F19729664@cisco.com> <F7D64379-1865-403E-AF91-E714713E6591@harvard.edu> <CAHBDyN4CnAHRbraX470Ch8VnQ2s7_bvR0z7nXmrMaRqp4GgHOA@mail.gmail.com> <B33242B8-7E1C-47FA-941D-2D9C2B8EA9EC@vigilsec.com> <A11F1D86-3F0E-4838-9463-7A521D70C2DC@cisco.com> <20140123175052.CC016E8F3D@ackroyd.harvard.edu> <77A6F1D3-9192-4A08-B03C-784B2B3F8A54@harvard.edu> <52E3EBA9.4050005@nist.gov> <CB2D10B9-DAD4-4C47-B984-A55D136C3126@piuha.net> <126fb3003777478a93ac346b525150af@BLUPR09MB054.namprd09.prod.outlook.com>, <01P3ONLTEKWA0000AS@mauve.mrochek.com>
In-Reply-To: <01P3ONLTEKWA0000AS@mauve.mrochek.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [129.6.33.54]
x-forefront-prvs: 01068D0A20
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(189002)(199002)(47736001)(47976001)(74366001)(46102001)(74706001)(4396001)(53806001)(56816005)(90146001)(49866001)(50986001)(33646001)(86362001)(85852003)(93516002)(93136001)(51856001)(81686001)(81816001)(76576001)(76796001)(76786001)(54356001)(92566001)(94316002)(74316001)(69226001)(76482001)(74876001)(56776001)(81542001)(87936001)(19580405001)(80976001)(74502001)(47446002)(87266001)(83322001)(77982001)(59766001)(19580395003)(85306002)(551944002)(63696002)(81342001)(79102001)(74662001)(80022001)(65816001)(2656002)(83072002)(31966008)(54316002)(66066001)(94946001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR09MB054; H:BLUPR09MB054.namprd09.prod.outlook.com; CLIP:129.6.33.54; FPR:; InfoNoRecordsMX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: nist.gov
X-Mailman-Approved-At: Thu, 30 Jan 2014 08:05:54 -0800
Cc: IETF WG Chairs <wgchairs@ietf.org>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 18:22:53 -0000

Great.  I can understand the "Encouraged !=3D required".  I had understood =
from previous messages that  I would be required.=0A=
=0A=
I'm happy now - well at least about this.=0A=
=0A=
Geoff=0A=
=0A=
=0A=
Geoff Mulligan | Presidential Innovation Fellow | Executive Office of the P=
resident | 301.975.6283=0A=
=0A=
________________________________________=0A=
From: Ned Freed <ned.freed@mrochek.com>=0A=
Sent: Tuesday, January 28, 2014 1:31 PM=0A=
To: Mulligan, Geoff=0A=
Cc: Jari Arkko; IETF WG Chairs; ietf@ietf.org Mailing List=0A=
Subject: RE: Third party disclosures and NDAs (Re: Problem with new Note We=
ll )=0A=
=0A=
> So because I know of IPR that someone else has and is not disclosing and=
=0A=
> because I cannot legally disclose it - I can't continue to participate in=
 the=0A=
> discussion doesn't seem right.  I'm not the holder of the IPR that isn't =
being=0A=
> disclosed, but I'm penalized.=0A=
=0A=
As I have pointed out several times now, that's incorrect. Section 6.1.3 of=
=0A=
BCP 79 discusses "IPR of Others", and says:=0A=
=0A=
   If a person has information about IPR that may Cover IETF=0A=
   Contributions, but the participant is not required to disclose=0A=
   because they do not meet the criteria in Section 6.6 (e.g., the IPR=0A=
   is owned by some other company), such person is encouraged to notify=0A=
   the IETF by sending an email message to ietf-ipr@ietf.org.  Such a=0A=
   notice should be sent as soon as reasonably possible after the person=0A=
   realizes the connection.=0A=
=0A=
And the referenced section 6.6 says:=0A=
=0A=
   6.6.  When is a Disclosure Required?=0A=
=0A=
   IPR disclosures under Sections 6.1.1. and 6.1.2 are required with=0A=
   respect to IPR that is owned directly or indirectly, by the=0A=
   individual or his/her employer or sponsor (if any) or that such=0A=
   persons otherwise have the right to license or assert.=0A=
=0A=
Encouraged !=3D required.=0A=
=0A=
The wrinkle here - and why I think you're getting some odd answers to your=
=0A=
questions - is that you're not being clear about what role the "someone els=
e"=0A=
you're talking about has in the IETF. If the "someone else" is not=0A=
participating in the IETF, then there's no problem, other than possibly you=
r=0A=
own conscience.=0A=
=0A=
If the "someone else" is participating while meeting the disclosure=0A=
requirements, then once again there's no problem since the disclosure has=
=0A=
already been done and there's no need for you to repeat it.=0A=
=0A=
But if they are participating and not disclosing, then there's a big proble=
m,=0A=
and in that case it may indeed suck to be you. My advice in such cases woul=
d be=0A=
to consult an attorney with substantive expertise in IP law as to what your=
=0A=
obligations are.=0A=
=0A=
I do expect such cases to be quite rare though.=0A=
=0A=
=0A=
                                Ned=0A=

From mstjohns@comcast.net  Thu Jan 30 09:28:18 2014
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCCA1A03F3 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 09:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.637
X-Spam-Level: 
X-Spam-Status: No, score=-0.637 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-9Pg-tAt3Uj for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 09:28:16 -0800 (PST)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB431A03C7 for <ietf@ietf.org>; Thu, 30 Jan 2014 09:28:16 -0800 (PST)
Received: from omta22.westchester.pa.mail.comcast.net ([76.96.62.73]) by qmta06.westchester.pa.mail.comcast.net with comcast id LGvd1n0021ap0As56HUCsP; Thu, 30 Jan 2014 17:28:12 +0000
Received: from Mike-T530ssd.comcast.net ([68.34.113.195]) by omta22.westchester.pa.mail.comcast.net with comcast id LHUC1n00p4D0RQL3iHUCuZ; Thu, 30 Jan 2014 17:28:12 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 30 Jan 2014 12:28:17 -0500
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, IETF discussion list <ietf@ietf.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: When is an idea a good idea?
In-Reply-To: <52E80FA9.5020704@gmail.com>
References: <52E80FA9.5020704@gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_161434436==.ALT"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391102892; bh=9W/qMf5FepNHg4aY53MknlUR4s1bkFu8DNkmMGFe8/8=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=fqV4/jyDNTAgD04JWNK+b5Wt20ZXJt0+DftuOm6xH6FkiZVDc0pIDska4KX+St13+ OD3Y2Vg41cDoQmqPpwMAXZUZRSq1oco/RVnypebQvmKk1N4BxQcmU87rpeNQVXW41x D9H8zUSsNkSosZ59/XuFgFZ2d5PGT9sEwaqiVg3XLr+L58xqOpbIK4FluqDFLshZPM hDjDeUKctfnHg1NDHcW18BRRObDyLVP/i0gaPNB+NV42LzqGU9ObU5nfivp5AaTfdC GBk6/taVRp6WoyE/ubRPpNol/LYNQSQIOCLrJY/+FY9cbF9PeJrsVTfWovHjnyOWBU lfeXDkMbIPJxQ==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 17:28:18 -0000

--=====================_161434436==.ALT
Content-Type: text/plain; charset="us-ascii"

Comments at the end.

At 03:14 PM 1/28/2014, Spencer Dawkins wrote:

>So, if you don't intend for your draft to be used on the global Internet, please say so! As per <http://tools.ietf.org/html/rfc2026#section-3.3>http://tools.ietf.org/html/rfc2026#section-3.3, it's not necessary to put an Applicability Statement in a different draft; just a section that says (another actual example) "this has been tested using these parameters on a lightly-loaded LAN, and it works there", that is more helpful than a tug of war(*) about whether something is a good idea or a bad idea in all situations, in front of a live studio audience.
>


To add to your list of possible limiters:

Subnet Scaling:  How large of a subnet will this work with before blowing up?  (mesh routing protocols, multicast security stuff etc).

Field of Use:  What was this designed to do?  What can this do without fear?  What shouldn't this do?  (e.g. DNS being used as a swiss army knife because its a global database implementation, TLS being used as the only security protocol including link layer for mesh).

Layer Violations:  What layer violations are acceptable for this protocol without breaking the model?  Does this assume a specific LLP (e.g. TCP using the IP address in a pseudo-header as part of the header checksum calculation)?

Convention Violations:  What violations of normal IETF and network standards convention does this protocol depend on?  (e.g.  current discussion in TLS about using little-endian on-the-wire representation for Curve22519 suites instead of the normal big-endian).  

Global vs Common vs Limited:  Is this protocol designed to be deployed in all or almost all internet devices (Global e.g. IP, UDP, TCP, DNS), in many devices - generic types (Common HTTP client and server, smtp, pop/imap), or in specific limited numbers or classes of devices (Limited - smart energy protocols, sensor node protocols - things like thermostats, street lights, bridge sensors, security systems).

Static vs Dynamic:  Is this protocol designed for use with clusters of internet nodes that can self-organize (dynamic) and change over time, or for clusters that are set-up/configured and remain relatively stable?

*sigh*  It might be Taxonomy time....

Mike


--=====================_161434436==.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<body>
Comments at the end.<br><br>
At 03:14 PM 1/28/2014, Spencer Dawkins wrote:<br><br>
<blockquote type=cite class=cite cite="">So, if you don't intend for your
draft to be used on the global Internet, please say so! As per
<a href="http://tools.ietf.org/html/rfc2026#section-3.3">
http://tools.ietf.org/html/rfc2026#section-3.3</a>, it's not necessary to
put an Applicability Statement in a different draft; just a section that
says (another actual example) &quot;this has been tested using these
parameters on a lightly-loaded LAN, and it works there&quot;, that is
more helpful than a tug of war(*) about whether something is a good idea
or a bad idea in all situations, in front of a live studio
audience.<br><br>
</blockquote><br><br>
To add to your list of possible limiters:<br><br>
Subnet Scaling:&nbsp; How large of a subnet will this work with before
blowing up?&nbsp; (mesh routing protocols, multicast security stuff
etc).<br><br>
Field of Use:&nbsp; What was this designed to do?&nbsp; What can this do
without fear?&nbsp; What shouldn't this do?&nbsp; (e.g. DNS being used as
a swiss army knife because its a global database implementation, TLS
being used as the only security protocol including link layer for
mesh).<br><br>
Layer Violations:&nbsp; What layer violations are acceptable for this
protocol without breaking the model?&nbsp; Does this assume a specific
LLP (e.g. TCP using the IP address in a pseudo-header as part of the
header checksum calculation)?<br><br>
Convention Violations:&nbsp; What violations of normal IETF and network
standards convention does this protocol depend on?&nbsp; (e.g.&nbsp;
current discussion in TLS about using little-endian on-the-wire
representation for Curve22519 suites instead of the normal
big-endian).&nbsp; <br><br>
Global vs Common vs Limited:&nbsp; Is this protocol designed to be
deployed in all or almost all internet devices (Global e.g. IP, UDP, TCP,
DNS), in many devices - generic types (Common HTTP client and server,
smtp, pop/imap), or in specific limited numbers or classes of devices
(Limited - smart energy protocols, sensor node protocols - things like
thermostats, street lights, bridge sensors, security systems).<br><br>
Static vs Dynamic:&nbsp; Is this protocol designed for use with clusters
of internet nodes that can self-organize (dynamic) and change over time,
or for clusters that are set-up/configured and remain relatively
stable?<br><br>
*sigh*&nbsp; It might be Taxonomy time....<br><br>
Mike<br>
</body>
<br>
</html>

--=====================_161434436==.ALT--


From dhc@dcrocker.net  Thu Jan 30 09:40:50 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28B381A044F for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 09:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SC8L7gQ3O5xO for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 09:40:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 23EA81A03F3 for <ietf@ietf.org>; Thu, 30 Jan 2014 09:40:49 -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 s0UHeVAK019458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 Jan 2014 09:40:34 -0800
Message-ID: <52EA8E76.6010400@dcrocker.net>
Date: Thu, 30 Jan 2014 09:40:06 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Re: When is an idea a good idea?
References: <52E80FA9.5020704@gmail.com> <74C96AE6-BD0C-4618-83E2-7D9D4F9C11F8@cisco.com>
In-Reply-To: <74C96AE6-BD0C-4618-83E2-7D9D4F9C11F8@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 30 Jan 2014 09:40:34 -0800 (PST)
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 17:40:50 -0000

On 1/29/2014 9:56 PM, Fred Baker (fred) wrote:
> Speaking for myself, I expect any solution that exists to be used on the open Internet.


Including DHCP and OSPF?

The point that efforts, which start with a limited usage scope, 
typically expand to the open Internet is an important one.  Moving from 
open Internet to controlled intranet is typically pretty easy, because 
the latter is faster and maybe more reliable.  Moving in the reverse 
direction is typically disastrous.

However the counter-examples I'm suggesting demonstrate that there 
really are legitimate cases of declaring limited scope as part of he 
design effort.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From alexey.melnikov@isode.com  Thu Jan 30 10:19:20 2014
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A3891A0295; Thu, 30 Jan 2014 10:19:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3b03o9xTxmWd; Thu, 30 Jan 2014 10:19:17 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.3.217.251]) by ietfa.amsl.com (Postfix) with ESMTP id 249EE1A0072; Thu, 30 Jan 2014 10:19:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1391105953; d=isode.com; s=selector; i=@isode.com; bh=QinOrxgtHNxOO+bEz5+TFPJ1uFCHTJqxEUBpsLGo1sw=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=XAkv+AH+1F4qMMBg2HdzY3laOWzkKAK9WEWseB4iEi4btkVv23CxduOywX/aBpkhGwoPRv 873akNwAMeGGF17RRIBZ40SfmM9mkQO1J5k39NRSnpISF2HqXQuxIDvy3VrS2XHzLnMnUJ UPQOpjmnehYoptL/dMjHYtofYJ+KaKs=;
Received: from [172.16.1.29] (richard.isode.com [62.3.217.249])  by waldorf.isode.com (submission channel) via TCP with ESMTPA  id <UuqXnwAIP7-M@waldorf.isode.com>; Thu, 30 Jan 2014 18:19:13 +0000
Message-ID: <52EA97A5.6080006@isode.com>
Date: Thu, 30 Jan 2014 18:19:17 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
References: <8D3D17ACE214DC429325B2B98F3AE712026F1621C1@MX15A.corp.emc.com> <52E65878.9030906@cisco.com> <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712026F162227@MX15A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "dcridland@arcode.com" <dcridland@arcode.com>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 18:19:20 -0000

Hi David,

On 27/01/2014 14:20, Black, David wrote:
> Hi Eliot,
>
> Regarding line length:
>
>> As the draft indicates, this is problematic for the two extensions in
>> question. We have discussed this limitation in the working group, and
>> nobody seems to be concerned.  That's due to two factors, I think:
>> first, RFC 2683 is not normative (informational).  I am unaware of any
>> strict line length limitation in RFC 3501, for instance.  Instead, there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
> The latter two sentences would be good to add to the draft in some form.
>
> My primary concern is what happens if the client sends a rather long
> line to a server that isn't prepared to cope, and the latter sentence
> would address it.  That could be accompanied by some sort of statement
> that servers that implement this extension need to be prepared to cope
> with longer lines.
I added some text on this issue. It will appear in -10 which I will post 
shortly.
> I'll leave the downref as a process concern for you (WG chair) and Barry (AD)
> to work out.
>
> Thanks,
> --David
>
>> -----Original Message-----
>> From: Eliot Lear [mailto:lear@cisco.com]
>> Sent: Monday, January 27, 2014 8:01 AM
>> To: Black, David; Alexey Melnikov (alexey.melnikov@isode.com);
>> dcridland@arcode.com; General Area Review Team (gen-art@ietf.org)
>> Cc: Barry Leiba (barryleiba@computer.org);ietf@ietf.org;imapext@ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
>>
>> Hi Dave,
>>
>> First, thank you for your review.  I personally appreciate to the time
>> you put in to all of your reviews.
>>
>> On 1/27/14, 3:06 AM, Black, David wrote:
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>>
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please resolve these comments along with any other Last Call comments
>>> you may receive.
>>>
>>> Document: draft-ietf-qresync-rfc5162bis-09
>>> Reviewer: David L. Black
>>> Review Date: January 26, 2014
>>> IETF LC End Date: January 27, 2014
>>>
>>> Summary:
>>> This draft is basically ready for publication, but has minor issues that
>>> should be fixed before publication.
>>>
>>> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
>>> (IMAP Quick Mailbox Resynchronization) into a single document and makes
>>> a few minor updates.  It also updates the command line length
>>> recommendation in RFC 2683 to support the longer command lines that
>>> can occur with these extensions.
>>>
>>> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
>>> they look reasonable.  I found one minor issue that should be relatively
>>> easy to address.
>>>
>>> Minor Issues:
>>>
>>> The command line length change in Section 4 applies to all IMAP commands,
>>> and hence affects old servers, including those that don't implement either
>>> of the extensions in this draft. That raises a backwards compatibility
>>> concern - what happens when a new client sends a > 1000 character command
>>> line to an old server that isn't expecting more than 1000 characters?
>> As the draft indicates, this is problematic for the two extensions in
>> question. We have discussed this limitation in the working group, and
>> nobody seems to be concerned.  That's due to two factors, I think:
>> first, RFC 2683 is not normative (informational).  I am unaware of any
>> strict line length limitation in RFC 3501, for instance.  Instead, there
>> is a requirement for strict syntax parsing.  If the client blows it in
>> any way, the server SHOULD return an error with a BAD response.
>>
>> This having been said, while the working group has discussed this
>> matter, it would be good to hear any additional voices of concern, in
>> the interests of interoperability.
>>
>> This takes us to your next point:
>>
>>> One possibility would be to apply the larger length recommendation only
>>> after the client determines that the server supports at least one of
>>> these extensions.
>>>
>>> Nits/editorial comments:
>>>
>>> The update to RFC 2683 would be easier to find from the table of contents
>>> if the title of Section 4 were changed to "Long Command Lines (Update to
>>> RFC 2683)".
>>>
>>> idnits 2.13.01 got confused by the command line examples, and flagged a
>>> downref:
>>>
>>>    ** Downref: Normative reference to an Informational RFC: RFC 2683
>>>
>>> That downref appears to be ok and intended, as noted in the shepherd's
>>> writeup.
>> This will be addressed in a forthcoming update.  Barry has "educated" us
>> that really this is NOT an update to RFC2683, where the advice given in
>> that document is superceded by a specific option.  As such, this error
>> will evaporate.
>>
>>


From rcallon@juniper.net  Thu Jan 30 10:27:23 2014
Return-Path: <rcallon@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6271A0260; Thu, 30 Jan 2014 10:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 69tFcQ6bpdi4; Thu, 30 Jan 2014 10:27:21 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 0B37B1A0054; Thu, 30 Jan 2014 10:27:19 -0800 (PST)
Received: from mail111-co9-R.bigfish.com (10.236.132.237) by CO9EHSOBE040.bigfish.com (10.236.130.103) with Microsoft SMTP Server id 14.1.225.22; Thu, 30 Jan 2014 18:27:16 +0000
Received: from mail111-co9 (localhost [127.0.0.1])	by mail111-co9-R.bigfish.com (Postfix) with ESMTP id 3F772740321;	Thu, 30 Jan 2014 18:27:16 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z579ehzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hz1de098h1033IL8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h9a9j1155h)
Received-SPF: pass (mail111-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rcallon@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(479174003)(13464003)(24454002)(377454003)(51704005)(199002)(189002)(49866001)(87266001)(74316001)(81342001)(80022001)(66066001)(90146001)(33646001)(85852003)(85306002)(59766001)(77982001)(31966008)(47976001)(47446002)(50986001)(87936001)(2656002)(94316002)(65816001)(74366001)(56816005)(4396001)(74876001)(94946001)(63696002)(93136001)(86362001)(2171001)(74706001)(74502001)(51856001)(81542001)(76796001)(54316002)(81686001)(81816001)(53806001)(56776001)(80976001)(76482001)(19580405001)(54356001)(46102001)(69226001)(15975445006)(19580395003)(76576001)(76786001)(83072002)(47736001)(79102001)(74662001)(83322001)(92566001)(93516002)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB633; H:CO2PR05MB636.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:; InfoNoRecordsA:1; MX:1; LANG:en; 
Received: from mail111-co9 (localhost.localdomain [127.0.0.1]) by mail111-co9 (MessageSwitch) id 1391106434111587_17146; Thu, 30 Jan 2014 18:27:14 +0000 (UTC)
Received: from CO9EHSMHS025.bigfish.com (unknown [10.236.132.240])	by mail111-co9.bigfish.com (Postfix) with ESMTP id 164ABA00046; Thu, 30 Jan 2014 18:27:14 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS025.bigfish.com (10.236.130.35) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 30 Jan 2014 18:27:14 +0000
Received: from CO2PR05MB633.namprd05.prod.outlook.com (10.141.199.12) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.395.1; Thu, 30 Jan 2014 18:27:12 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) by CO2PR05MB633.namprd05.prod.outlook.com (10.141.199.12) with Microsoft SMTP Server (TLS) id 15.0.859.15; Thu, 30 Jan 2014 18:27:10 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) by CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) with mapi id 15.00.0859.020; Thu, 30 Jan 2014 18:27:09 +0000
From: Ross Callon <rcallon@juniper.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Joe Touch <touch@isi.edu>, "EXT - joelja@bogus.com" <joelja@bogus.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPGTj803Ue20svMUem0bxV/kZZIZqYyqAAgAACKoCAACGRgIAAAT2AgAAHPgCABKMSEA==
Date: Thu, 30 Jan 2014 18:27:09 +0000
Message-ID: <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.com>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com>
In-Reply-To: <52E6B128.8060306@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 0107098B6C
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 18:27:23 -0000

+1 to what Joel said. It is clear that Joe's view of "fast enough" for a ho=
st interface is not the same as my customer's view of "fast enough" for a c=
ore router (nor should it be the same -- routers have to be faster than hos=
t interfaces).=20

More important is the issue of what can we get vendors to implement, which =
is probably better worded as what can we get network operators to push vend=
ors to implement. If you are talking about fundamentally changing the inter=
nal data path for packets within a router or changing the data path into an=
d out of specific chips to carry significantly more information, then we ar=
e talking about at least hundreds of millions and probably billions of doll=
ars of equipment that needs to be replaced. This needs a very compelling ju=
stification before it is actually going to happen.=20

Ross

-----Original Message-----
From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Joel M. Halpern
Sent: Monday, January 27, 2014 2:19 PM
To: Joe Touch; EXT - joelja@bogus.com; stbryant@cisco.com
Cc: mpls@ietf.org; IETF discussion list
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

Yes Joe, routers could ahve been built to do those calcualtions at that=20
performance scale.
There are however two major problems:

1) That is not how routers are built.
2) The target performance scale is rather higher.

So could someone build an ASIC to do what you want?  Probably.  Is there=20
any reason in the world to expect operators to pay the significant extra=20
cost for such?  Not that I can see.
And even if we could and they would, that is not the world into which we=20
are deploying these tunnels.

Yours,
Joel

On 1/27/14 1:53 PM, Joe Touch wrote:
>
>
> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>> Those same mechanisms have provided hardware checksum support for a
>>> very long time.
>>
>> The new header and the payload are actually in different parts of the
>> forwarding complex until they hit the output queue, you can't checksum
>> data you don't have.
>
> You can (and some do) the checksum component parts when things go into
> memory; the partial sums can be added as the parts are combined in the
> output queue.
>
> I appreciate that we're all taking about what might be done, but the
> reality is that there are many 'transparent TCP proxies' that have to do
> this, so there's clearly a solution, and it clearly runs fast enough.
>
> Joe
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls




From vesely@tana.it  Thu Jan 30 10:53:00 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE0E1A046D for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 10:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.957
X-Spam-Level: 
X-Spam-Status: No, score=-2.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSa7MnLhvbeD for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 10:52:58 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id AB5811A0435 for <ietf@ietf.org>; Thu, 30 Jan 2014 10:52:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1391107973; bh=Lv85kmelvjjLdPhRL+9GkwedfEhQO4UEWxYfUF+8zE4=; l=3389; h=Date:From:To:CC:References:In-Reply-To; b=Wl6/i5eXK9ObcHmBeRJUjeMGaBl2NHxCZ5njXkN8Pl0PPhmu8d9xn3b856DNEI5nI 4GSc1VpohTPyfATwxPahuLmpeWc6ENlW5IedIZSaxcs3e5dTRNTk4MrmHkVcpIlhY6 NnkUkgTa6fsrRf1JfTvym4CBIZu2VnGwWcaWsQGc=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Thu, 30 Jan 2014 19:52:53 +0100 id 00000000005DC035.0000000052EA9F85.000017E5
Message-ID: <52EA9F85.6080804@tana.it>
Date: Thu, 30 Jan 2014 19:52:53 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: IAB <iab@iab.org>
Subject: Re: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
In-Reply-To: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 18:53:00 -0000

On Wed 29/Jan/2014 17:16:56 +0100 IAB Chair wrote:
> This is a call for review of "Technical Considerations for Internet
> Service Blocking and Filtering" prior to potential approval as an
> IAB stream RFC.
> 
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-filtering-considerations/

Albeit it purports to keep clear of (un)ethical considerations, the
document seems to be oriented toward government-imposed restrictions,
recounting how it would be better to move filtering to collaborative
endpoints rather than disrupting Internet operation, since bad actors
can circumvent filtering anyway.  I fully agree, but I think that a
general purpose document on this subject might have touched on such
points as password management, user identification, and outbound port
25 blocking.

Some minor comments, in top-down order:

1. *Introduction*, par 3

                          As noted in [RFC4084], some Internet service
   providers impose restrictions on which applications their customers
   may use and which traffic they allow on their networks.

To avoid confusion, I'd s/impose restrictions/perform filtering/,
since RFC 4084 says about Firewalled Internet Connectivity:

                  It is distinguished from the models above by the
   fact that any filtering or blocking services are ultimately
   performed at customer request, rather than being imposed as
   service restrictions.

Alternatively, that snippet could refer to "Section 3 of [RFC4084]".


2. *Filtering Examples*, par 3 (Web Filtering)

The second half of that paragraph is rather lengthy and obscure --the
explanation in Section 5 is much clearer.  It could be shortened for
readability, for example:

OLD:
   To block access to content made accessible via HTTPS, filtering
   systems thus must either block based on network- and
   transport-layer headers (IP address and/or port), or else obtain a
   trust anchor certificate that is trusted by endpoints (and thus act
   as a man in the middle).  These filtering systems often take the
   form of "portals" or "enterprise proxies."  These portals present
   their own HTTPS certificates that are invalid for any given domain
   according to normal validation rules, but may still be trusted if
   the user installs a security exception.  (See further discussion in
   Section 5.)

NEW:
   To block access to content made accessible via HTTPS, filtering
   systems thus must either block based on network- and
   transport-layer headers (IP address and/or port), or act as a man
   in the middle by requiring the user to install security exceptions.
   The latter filtering systems often take the form of "portals" or
   "enterprise proxies", presenting their own, dynamically generated
   HTTPS certificates.  (See further discussion in Section 5.)


3.1. *Entities that set blocking policies*

   Parties that institute blocking policies include governments,
   enterprises, network operators, application providers, and
   individual end users.

Which of those terms includes Spamhaus?  I'd propose to add
"reputation trackers".


3.4. *Components used for blocking*, par 1

   Broadly speaking, the process of a delivering an Internet service
   involves three different components:

s/a delivering/delivering/


4.3.5. *Examples*, par 3

s/e-mail/email/


6. *Conclusion*

s/Because it least/Because it is least/

Ale

From coppens.ndayiragije@yahoo.com  Wed Jan 29 08:38:30 2014
Return-Path: <coppens.ndayiragije@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660801A0375 for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vt6iSVRC16XM for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 08:38:28 -0800 (PST)
Received: from nm6.bullet.mail.ne1.yahoo.com (nm6.bullet.mail.ne1.yahoo.com [98.138.90.69]) by ietfa.amsl.com (Postfix) with ESMTP id 712921A03A7 for <ietf@ietf.org>; Wed, 29 Jan 2014 08:38:25 -0800 (PST)
Received: from [98.138.226.176] by nm6.bullet.mail.ne1.yahoo.com with NNFMP; 29 Jan 2014 16:38:22 -0000
Received: from [98.138.87.6] by tm11.bullet.mail.ne1.yahoo.com with NNFMP; 29 Jan 2014 16:38:22 -0000
Received: from [127.0.0.1] by omp1006.mail.ne1.yahoo.com with NNFMP; 29 Jan 2014 16:38:22 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 350656.84073.bm@omp1006.mail.ne1.yahoo.com
Received: (qmail 99489 invoked by uid 60001); 29 Jan 2014 16:38:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1391013502; bh=fjOq5p/n7yulkMBEjWJAxHyAMUfJGXX9OV78/Q+2RJc=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=iYInPurZDpZManvZ1u3k9HoNleUyrS9x5TqrptA+kQby+Ia375ojzpOGyolujrdSNnfWsAcTXhaSEkqnU8+gk5NaiQRRCis+iVOjRVfoR8eZA8LNtFsj0sscVvWsmYr6wUuund3Jxy9hh2cNOLMkkg5QTOJtECDimdAf5LAkRWA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=5HVEQ7s6WtSz5g7ZNDTVDTf83kR/vR5x3lEs2g/tz6Nq64r3gmXm6W7pOQQfuBEiWfk0kt2HqxMF1i2PnjrfTK2LOrOOXVID4gsXbya5lIa+iUmP5BcACL9YTcEEYLu00RKzzHSkfrV8agwaL1PNBsU00USHbrPz9vyCUss1s0M=;
X-YMail-OSG: Lymc.TwVM1kxI.9DgTdHsfj1BP2mfxt.2zatqvjMbTLBxkb jESzuQiYutIzXpa9lCk7UThwnh3IqX.K390ufUpqFd6aR45oJt1aG5IJ3eWW a6Kgw5MR3XcUP1t_MxMUb8di7dS2OAYA.h6hx9ux7TMwqpCAN13nEKC70wml 3qq.4ioZrZaG.LwR4OwVRGkMdKEtsLJVbnan8ZGG3_BWt6T20cWkb4KGtse4 dTMUlsNV6_k.U5Vc13lnpwyfx.xQEjvEo.RiBMumScmrplwGftfmPJjM4gJP GEgP0Aum1yTkg.2hUJoAo4Y.3uQxeB6LlFf17E5o04OVcOVpiLOpoVrd4seZ bDp8d.mpY_jLnYlXo3aiFpgdNt09109ZWo4xllHpdRFz6IDocS9fcFVQJIix 8qH_Nu6FGuWNOAbkwMwXK5NII4MNh3vjRrYyC8OrKuglPpFN3IF7WyU_jv74 ArnjK2iWWOtWQqlvNjMFpveesdL_Egx67cCYJzCxKx0sFEwk9iJwYOLeMPpz KjG9tmzIzP05exHM350arW99jZNJFfCS.bSBvm1kyI.2G6as3Zg9VfLs-
Received: from [41.79.226.2] by web125306.mail.ne1.yahoo.com via HTTP; Wed, 29 Jan 2014 08:38:22 PST
X-Rocket-MIMEInfo: 002.001, RGVhciBNYWRhbS8gU2lyOwoKVG8gaW5mb3JtIHlvdSB0aGF0IEkgY29uZmlybSBteSBpbnRlcmVzdCBpbiBoYXZpbmcgYSBtZW50b3IgZHVyaW5nIG15IHN0YXkgaW4gVUshCgpJIHRoYW5rIHlvdSBhbHNvIGZvciB5b3VyIGtpbmQgYXNzaXN0YW5jZSBhbmQgZ3VpZGFuY2UhCsKgCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KTm9zIHNpbmPDqHJlcyBzYWx1dGF0aW9uczsKTWUuIElyLiBDb3BwZW5zIFBhc3RldXIgTkQBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.174.629
References: <20140128172138.28200.99163.idtracker@ietfa.amsl.com>
Message-ID: <1391013502.78982.YahooMailNeo@web125306.mail.ne1.yahoo.com>
Date: Wed, 29 Jan 2014 08:38:22 -0800 (PST)
From: Coppens Pasteur NDAYIRAGIJE <coppens.ndayiragije@yahoo.com>
Subject: Re: [89-1st-timers] Invitation to Participate in Mentoring Program
To: "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
In-Reply-To: <20140128172138.28200.99163.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-2016055526-280606418-1391013502=:78982"
X-Mailman-Approved-At: Thu, 30 Jan 2014 11:03:37 -0800
Cc: "89-1st-timers@ietf.org" <89-1st-timers@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Coppens Pasteur NDAYIRAGIJE <coppens.ndayiragije@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 16:38:30 -0000

---2016055526-280606418-1391013502=:78982
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Madam/ Sir;=0A=0ATo inform you that I confirm my interest in having a =
mentor during my stay in UK!=0A=0AI thank you also for your kind assistance=
 and guidance!=0A=A0=0A----------------------------------------------------=
------------------------=0ANos sinc=E8res salutations;=0AMe. Ir. Coppens Pa=
steur NDAYIRAGIJE=0ASp=E9cialiste en G=E9nie des Technologies de l'Informat=
ion,=0AAssistant Technique du SETIC=A0Charg=E9 du Suivi des=A0Travaux=A0=0A=
de Construction=A0de l'Infrastructure Nationale=A0du R=E9seau=A0=0Ade Base=
=A0=E0 Large Bande du Burundi=0A=0Aet Pr=E9sident du BurundiX A.S.B.L.=A0=
=0A=0AMobile: (+257) 79 365 000=0A=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0=A0(+257) =
78 365 000=0A=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0=A0(+257) 76 365 000=0AEmail:=
=A0coppens.ndayiragije@yahoo.com=0A=0A=0A=0AOn Tuesday, January 28, 2014 5:=
23 AM, IETF Chair <chair@ietf.org> wrote:=0A =0AAll,=0A=0AAt IETF 89 we wil=
l once again offer the IETF Mentoring Program. The goal=0Aof the IETF Mento=
ring Program is to match IETF participants who may be new=0Aor otherwise in=
 need of guidance with experienced IETF mentors. As a=0Amentoring participa=
nt, your mentor will personally introduce you to the=0AIETF community, help=
 you find your way around the IETF & the meeting,=0Aexplain things, and int=
roduce you to other attendees you might like to=0Ameet. Basically, your men=
tor will be your personal buddy during the=0Ameeting week, and possibly aft=
erwards.=0A=0AUnlike in the past, at IETF 89 we will accept requests for me=
ntors from=0Aanyone who wants one, regardless of how many meetings they hav=
e attended=0Apreviously. We cannot guarantee that every request will be hon=
ored, but we=0Awill do our best.=0A=0AIf you wish to participate in the IET=
F Mentoring Program, you can follow=0Athe sign-up procedures described in t=
he program FAQ:=0A=0Ahttps://www.ietf.org/resources/mentoring-program.html=
=0A=0AAfter you follow the sign-up procedure, we will introduce you to your=
=0Amentor by email prior to IETF 89, and invite you to meet up in person at=
=0Athe IETF Meet & Greet event on Sunday afternoon in London. From there on=
,=0Ayou and your mentor decide on when and where to meet during the rest of=
=0Athe week and afterwards.=0A=0AYou are of course free to withdraw from th=
e program at any time and for=0Aany reason, no questions asked, should a ne=
ed arise. But I sincerely=0Abelieve the IETF Mentoring Program will be a gr=
eat way for new=0Aparticipants to get introduced to the IETF by an experien=
ced participant=0Awith matching interest.=0A=0ARegards,=0AJari Arkko=0AIETF=
 Chair=0A_______________________________________________=0A89-1st-timers ma=
iling list=0A89-1st-timers@ietf.org=0Ahttps://www.ietf.org/mailman/listinfo=
/89-1st-timers
---2016055526-280606418-1391013502=:78982
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:ti=
mes new roman, new york, times, serif;font-size:14pt"><div><span>Dear Madam=
/ Sir;</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 19px; font=
-family: 'times new roman', 'new york', times, serif; background-color: tra=
nsparent; font-style: normal;"><span><br></span></div><div style=3D"color: =
rgb(0, 0, 0); font-size: 19px; font-family: 'times new roman', 'new york', =
times, serif; background-color: transparent; font-style: normal;"><span>To =
inform you that I confirm my interest in having a mentor during my stay in =
UK!</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 19px; font-fa=
mily: 'times new roman', 'new york', times, serif; background-color: transp=
arent; font-style: normal;"><span><br></span></div><div style=3D"color: rgb=
(0, 0, 0); font-size: 19px; font-family: 'times new roman', 'new york', tim=
es, serif; background-color: transparent; font-style: normal;"><span>I than=
k
 you also for your kind assistance and guidance!</span></div><div></div><di=
v>&nbsp;</div><div><div class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt=
;"><span style=3D"font-size: 12pt; font-family: Garamond, serif;">---------=
-------------------------------------------------------------------</span><=
/div><div class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;"><b><span st=
yle=3D"font-size: 12pt; font-family: Garamond, serif;">Nos sinc=E8res salut=
ations;</span></b><span style=3D"font-size: 12pt; font-family: Garamond, se=
rif;"></span></div><div class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt=
;"><b><span style=3D"font-size: 12pt; font-family: Garamond, serif;">Me. Ir=
. Coppens Pasteur NDAYIRAGIJE</span></b><span style=3D"font-size: 12pt; fon=
t-family: Garamond, serif;"></span></div><div class=3D"MsoNormal" style=3D"=
margin-bottom:0.0001pt;"><b><span style=3D"font-size: 12pt; font-family: Ga=
ramond, serif;">Sp=E9cialiste en G=E9nie des Technologies de l'Information,=
</span></b><span
 style=3D"font-size: 12pt; font-family: Garamond, serif;"></span></div><div=
 class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;"><b><span style=3D"fo=
nt-size: 12pt; font-family: Garamond, serif;">Assistant Technique du SETIC&=
nbsp;Charg=E9 du Suivi des&nbsp;</span></b><b><span style=3D"font-size: 12p=
t; font-family: Garamond, serif;">Travaux&nbsp;</span></b></div><div class=
=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;"><b><span style=3D"font-siz=
e: 12pt; font-family: Garamond, serif;">de Construction&nbsp;de l'Infrastru=
cture Nationale&nbsp;</span></b><b><span style=3D"font-size: 12pt; font-fam=
ily: Garamond, serif;">du R=E9seau&nbsp;</span></b></div><div class=3D"MsoN=
ormal" style=3D"margin-bottom:0.0001pt;"><b><span style=3D"font-size: 12pt;=
 font-family: Garamond, serif;">de Base&nbsp;=E0 Large Bande du Burundi</sp=
an></b></div><div class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;"><sp=
an style=3D"font-size: 12pt; font-family: Garamond, serif;"></span></div><d=
iv class=3D"MsoNormal"
 style=3D"margin-bottom:0.0001pt;"><b><span style=3D"font-size: 12pt; font-=
family: Garamond, serif;"><br></span></b><b><span style=3D"font-size: 12pt;=
 font-family: 'Bookman Old Style', serif;">et Pr=E9sident du BurundiX A.S.B=
.L.&nbsp;</span></b></div><div class=3D"MsoNormal" style=3D"margin-bottom:0=
.0001pt;"><b><span style=3D"font-size: 12pt; font-family: Garamond, serif;"=
><br></span></b><b><span style=3D"font-size: 12pt; font-family: Garamond, s=
erif;">Mobile: (+257) 79 365 000</span></b></div><div class=3D"MsoNormal" s=
tyle=3D"margin-bottom:0.0001pt;"><span style=3D"font-size: 12pt; font-famil=
y: Garamond, serif;"></span></div><div class=3D"MsoNormal" style=3D"margin-=
bottom:0.0001pt;"><b><span style=3D"font-size: 12pt; font-family: Garamond,=
 serif;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;(+=
257) 78 365 000</span></b><span style=3D"font-size: 12pt; font-family: Gara=
mond, serif;"></span></div><div class=3D"MsoNormal" style=3D"margin-bottom:=
0.0001pt;"><b><span
 style=3D"font-size: 12pt; font-family: Garamond, serif;">&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;(+257) 76 365 000</span></b>=
<span style=3D"font-size: 12pt; font-family: Garamond, serif;"></span></div=
><div class=3D"MsoNormal" style=3D"margin-bottom:0.0001pt;"><b><span style=
=3D"font-size: 12pt; font-family: Garamond, serif;">Email:&nbsp;</span></b>=
<span style=3D"font-size: 12pt; font-family: Garamond, serif;"><a rel=3D"no=
follow" target=3D"_blank" href=3D"mailto:coppens.ndayiragije@yahoo.com"><b>=
<span style=3D"color:blue;">coppens.ndayiragije@yahoo.com</span></b></a></s=
pan></div></div><div class=3D"yahoo_quoted" style=3D"display: block;"> <br>=
 <br> <div style=3D"font-family: 'times new roman', 'new york', times, seri=
f; font-size: 14pt;"> <div style=3D"font-family: HelveticaNeue, 'Helvetica =
Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; font-size: 12pt;"> <d=
iv dir=3D"ltr"> <font size=3D"2" face=3D"Arial"> On Tuesday, January 28, 20=
14 5:23 AM, IETF Chair
 &lt;chair@ietf.org&gt; wrote:<br> </font> </div>  <div class=3D"y_msg_cont=
ainer">All,<br><br>At IETF 89 we will once again offer the IETF Mentoring P=
rogram. The goal<br>of the IETF Mentoring Program is to match IETF particip=
ants who may be new<br>or otherwise in need of guidance with experienced IE=
TF mentors. As a<br>mentoring participant, your mentor will personally intr=
oduce you to the<br>IETF community, help you find your way around the IETF =
&amp; the meeting,<br>explain things, and introduce you to other attendees =
you might like to<br>meet. Basically, your mentor will be your personal bud=
dy during the<br>meeting week, and possibly afterwards.<br><br>Unlike in th=
e past, at IETF 89 we will accept requests for mentors from<br>anyone who w=
ants one, regardless of how many meetings they have attended<br>previously.=
 We cannot guarantee that every request will be honored, but we<br>will do =
our best.<br><br>If you wish to participate in the IETF Mentoring
 Program, you can follow<br>the sign-up procedures described in the program=
 FAQ:<br><br><a href=3D"https://www.ietf.org/resources/mentoring-program.ht=
ml" target=3D"_blank">https://www.ietf.org/resources/mentoring-program.html=
</a><br><br>After you follow the sign-up procedure, we will introduce you t=
o your<br>mentor by email prior to IETF 89, and invite you to meet up in pe=
rson at<br>the IETF Meet &amp; Greet event on Sunday afternoon in London. F=
rom there on,<br>you and your mentor decide on when and where to meet durin=
g the rest of<br>the week and afterwards.<br><br>You are of course free to =
withdraw from the program at any time and for<br>any reason, no questions a=
sked, should a need arise. But I sincerely<br>believe the IETF Mentoring Pr=
ogram will be a great way for new<br>participants to get introduced to the =
IETF by an experienced participant<br>with matching interest.<br><br>Regard=
s,<br>Jari Arkko<br>IETF
 Chair<br>_______________________________________________<br>89-1st-timers =
mailing list<br><a ymailto=3D"mailto:89-1st-timers@ietf.org" href=3D"mailto=
:89-1st-timers@ietf.org">89-1st-timers@ietf.org</a><br><a href=3D"https://w=
ww.ietf.org/mailman/listinfo/89-1st-timers" target=3D"_blank">https://www.i=
etf.org/mailman/listinfo/89-1st-timers</a><br><br><br></div>  </div> </div>=
  </div> </div></body></html>
---2016055526-280606418-1391013502=:78982--

From antony@it.bw  Wed Jan 29 22:25:14 2014
Return-Path: <antony@it.bw>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07BD61A041A for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 22:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.812
X-Spam-Level: 
X-Spam-Status: No, score=0.812 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FILL_THIS_FORM=0.001, HTML_MESSAGE=0.001, T_DOS_OUTLOOK_TO_MX_IMAGE=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MPPFmiDdx99h for <ietf@ietfa.amsl.com>; Wed, 29 Jan 2014 22:25:10 -0800 (PST)
Received: from mx2.botsnet.bw (mx2.botsnet.bw [168.167.71.195]) by ietfa.amsl.com (Postfix) with ESMTP id 6D3131A02F3 for <ietf@ietf.org>; Wed, 29 Jan 2014 22:25:06 -0800 (PST)
From: "Tony Chigaazira" <antony@it.bw>
To: <ietf@ietf.org>
Subject: IETF 89 London - Enquiry
Date: Thu, 30 Jan 2014 08:24:56 +0200
Message-ID: <019701cf1d83$fed5a7d0$fc80f770$@it.bw>
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----=_NextPart_000_0198_01CF1D94.C260E8D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8dg+Rv/gUCFHU4R261kNvbSHtHJQ==
Content-Language: en-za
X-Mailman-Approved-At: Thu, 30 Jan 2014 11:03:37 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 06:25:14 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0198_01CF1D94.C260E8D0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0199_01CF1D94.C260E8D0"


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

I confirm that as a first timer I need a mentor. May I please know the dress
code as well. 

 

Tony Chigaazira

Executive Secretary CRASA

 Description: cid:22E0EA05-D985-4733-9A28-72AD44F6FDDE

WEBSITE:  <http://www.crasa.org/> www.crasa.org

TEL:    +267 3158468 

DIRECT:   +267 3158469

FAX:  +267 3181171

MOBILE:  +267 71711379

EMAIL (BUSINESS):    <mailto:antony@it.bw> antony@it.bw

EMAIL (PERSONAL):  <mailto:antony.chigaazira@gmail.com>
antony.chigaazira@gmail.com

Plot 138,  Unit 2

Gaborone International Finance Park 

PO Box AD 135 ADD, 

Gaborone

Botswana

Description: Description: Description: Description: cid:3325239253_1243893

The information transmitted in this e-mail is intended only for the person
or entity to which it is addressed and may contain confidential and or
privileged material. Should you have received this e-mail in error please
notify the sender and delete all copies of the e-mail. Unauthorised use,
disclosure or copying of any part of this e-mail, or any similar action, is
prohibited. No opinion expressed or implied by the sender necessarily
constitutes the opinion of CRASA. This e-mail does not constitute a
guarantee or proof of the facts mentioned herein. No employee or
intermediary is authorised to conclude a binding agreement on behalf of
CRASA by e-mail without the express written confirmation by a duly
authorised representative of CRASA

 


------=_NextPart_001_0199_01CF1D94.C260E8D0
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)"><!--[if !mso]><style>v\:* =
{behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-ZA link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>I confirm =
that as a first timer I need a mentor. May I please know the dress code =
as well. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZW'>Tony =
Chigaazira</span></b><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span =
lang=3DEN-ZW style=3D'font-size:10.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZW'>Executive =
Secretary CRASA</span></i></b><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZW'>&nbsp;</span></b=
><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><img width=3D110 height=3D78 =
id=3D"Picture_x0020_2" src=3D"cid:image001.png@01CF1D94.C1E77310" =
alt=3D"Description: =
cid:22E0EA05-D985-4733-9A28-72AD44F6FDDE"><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>WEBSITE: <a =
href=3D"http://www.crasa.org/"><span =
style=3D'color:blue'>www.crasa.org</span></a></span></b><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>TEL:&nbsp;&nbsp;=
 </span></b><span lang=3DEN-ZW =
style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>&nbsp;+267</span=
><span lang=3DEN-ZW style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZA'> </span><span =
style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZA'>3158468</span><s=
pan style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'> </span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>DIRECT: =
</span></b><span lang=3DEN-ZW =
style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>&nbsp; +267 =
3158469</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>FAX:</span></b><=
span lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>&nbsp; +267 =
3181171</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>MOBILE: =
</span></b><span lang=3DEN-ZW =
style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>&nbsp;+267 =
71711379</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>EMAIL =
(BUSINESS):</span></b><span lang=3DEN-ZW =
style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>&nbsp;&nbsp; =
</span><u><span lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times =
New Roman","serif";color:#0070C0;mso-fareast-language:EN-ZW'><a =
href=3D"mailto:antony@it.bw"><span =
style=3D'color:blue'>antony@it.bw</span></a></span></u><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>EMAIL</span></b>=
<span lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'> <b>(PERSONAL): =
</b><a href=3D"mailto:antony.chigaazira@gmail.com"><span =
style=3D'color:blue'>antony.chigaazira@gmail.com</span></a></span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>Plot 138,&nbsp; =
Unit 2</span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>Gaborone =
International Finance Park </span><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>PO Box AD 135 =
ADD, </span><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#17365D;mso-fareast-language:EN-ZW'>Gaborone</span><=
span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span =
lang=3DEN-ZW style=3D'font-size:9.0pt;font-family:"Times New =
Roman","serif";color:#1F497D;mso-fareast-language:EN-ZW'>Botswana</span><=
/b><span style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><i><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";color:red;mso-fareast-language:EN-ZA'><img border=3D0 =
width=3D369 height=3D64 id=3D"Picture_x0020_4" =
src=3D"cid:image002.jpg@01CF1D94.C1E77310" alt=3D"Description: =
Description: Description: Description: =
cid:3325239253_1243893"></span></i></b><span =
style=3D'font-size:12.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span =
lang=3DEN-ZW style=3D'font-size:8.0pt;font-family:"Times New =
Roman","serif";mso-fareast-language:EN-ZW'>The information transmitted =
in this e-mail is intended only for the person or entity to which it is =
addressed and may contain confidential and or privileged material. =
Should you have received this e-mail in error please notify the sender =
and delete all copies of the e-mail. Unauthorised use, disclosure or =
copying of any part of this e-mail, or any similar action, is =
prohibited. No opinion expressed or implied by the sender necessarily =
constitutes the opinion of <b><span =
style=3D'color:#365F91'>CRASA</span></b>. This e-mail does not =
constitute a guarantee or proof of the facts mentioned herein. No =
employee or intermediary is authorised to conclude a binding agreement =
on behalf of <b><span style=3D'color:#365F91'>CRASA</span></b> by e-mail =
without the express written confirmation by a duly authorised =
representative of <b><span =
style=3D'color:#365F91'>CRASA</span></b></span><span =
style=3D'mso-fareast-language:EN-ZA'><o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_001_0199_01CF1D94.C260E8D0--

------=_NextPart_000_0198_01CF1D94.C260E8D0
Content-Type: image/png;
	name="image001.png"
Content-Transfer-Encoding: base64
Content-ID: <image001.png@01CF1D94.C1E77310>

iVBORw0KGgoAAAANSUhEUgAAAG4AAABOCAYAAADB9yPNAAAAAXNSR0IArs4c6QAAAAlwSFlzAAAS
dAAAEnQB3mYfeAAAABl0RVh0U29mdHdhcmUATWljcm9zb2Z0IE9mZmljZX/tNXEAADlkSURBVHhe
5X0HfFRl1v4zLZNJMum9k0pCIIRA6KDSFLCv2LDv6tq3fOu66+7fT3d11W/12/+qq2LDLgriooAg
XYoQakISQkjvvWfSZvJ/zntnAF1cg4K4v/8NQzIzd+be+573nPOc55zzXuMQN/yHb729vWhra4PR
YIC3rw/0/Ont74OnpwccdgcGBgZgdneHjtfpcDgAnQ56Pv6TN+OP9eRlPulOMbglxcWoratFTU0N
YqJj4O3tjXfffRveViuqqqsxc+ZMeHl64cDBg3jgtw8iNycHWzZvwQy+fnD/flx1zdWwcl/X1tzc
BA8PD1gsHj/WoTjlef1oBSdn29DQiNzcQ6ivr0PxsWLMu/BCfL7uM2zatAmxsSMwe/ZsDA4O4MDe
bNxz333YuWMH1vf2YHzmBGzbvAnzL5qPdWvWoKSkGEY3I7Zs3IRrrrv2+EDs2rkTbyx9DRHh4fiv
Bx5EdXUNem02pKaNgl6v/1EL8twLTgy102qJSTOZTGrARNuy9+zGX/7yGOZQQFs2b0ZnVwfiRoxA
Z3sHvL08UFVehmnUpMwJWRTwYYxMScHYcRmYNHEKmlvasOKjFejp7sYNN9+MxqZGGE0G/O/T/4NJ
k6fCQLP6+9/+BgkJcVi3LgdZkyYjLCyC7/+Vk2EQs+fMxpVXXQWz2R1Go/Er2u/yLefS2J57wfHq
xT8dO3pUaVNcfALN2TVqxo9JHw0DBTjQP4Drb7gRHR3tmDZ9BkJCQhEaEoxQDvSIuHhMnjoV/T09
cKMfg167pAcefAB9Pd1qIuhNfJ3b3DlzUVtTxf08UFlZjYcefgR+vt748INlKCwspDk9Dz22HmWC
x6SnIy8vDx+vXMlzisPcufMQzddlQonAzjUwOKeCq6ysVL5p2bL3sXL5cqQkJWLzpo0ceyOuWrQI
UVEx+NNjjyN5ZAqFFXLcdKWNTEZLazvaOzpw6NAh2AYG0U4tFNwhvrHH1qu0xJ3aMjTkgG7IDl8f
H3hRS62e7vCyuGFS1jgYnAKdMm0GWlqaISBn4qQpuJbmVPa/7dablUn2tnrjT488ggsvvAg/4Xkp
i3CODek5EVwHB1y2gwcPYB/N4bTp0+Hv541Bhx0xsbFwM7sdHxbRgsHebuTn5qC0phE1jS2oaupE
c1c/2vuB3kFqJNzBXxxN4kmdEXYZVv4zUGh2SlMHB4yohNtQPzxNDj50CLSaER3oichgX8RHR9AE
x0Hn5o5f/fpX6thdYpapzQa9gRhVh+bGRmWqP/xwGfIOH8ZPrvwJ0saknzPxnVXBncoX5OTk4rE/
PYIAf38EBPpjzerViIqJwT33/wodnZ2YPGkifHx90d7ahJzDBThYWI5jdR2o7dKh1+AFuHlCZw6H
0cMMg6/mfyx6E3/L8MoR+VvM69Ag7IN6uBmGMKTXYXDAAcegHT2D/egc6EcVTWv2sW4Y8yrh5ShE
iPdWJIb7YnxqPEaNTISXty/+/Oc/Y092Nk34Oiy8+GJqrBWPPPwwNW8eXn3lJSTSEtx1173HhSeB
1Q8VZZxVwZ1sTnZs34HDublIz0hHf38/fP18kZycQh/kjglZkzBmzBj09nShvKIS761ch33H6lA3
YIHDKwQWayTM/ma4G9yVGTXpaBMpJB1HSkzhEAZBNYNBRMfB66NghnQGWD2MGOgdxJBBR+EaKHSe
kZhPnQcffjStdvTb+WkKtbyvG0WlTViXtxfh7tuRGR+CmVPHI2v8OGRNnKSEs3b1Gtxz731oaqjH
5+vXI4mCW7NmNfr6+jCH/tPLixPrB9rOquDkGppoYlat+idKS0sxSIEV5OXg5ltvQWtLKxbfeJO6
zM72Fny+cQs27StAQW0fBrzC4BE6GX6Mr4zUHNEkHc2gjkLSO3o1DyP/qEnaDOd/FBifws79Q7zN
mJwcgjGRXlh3qAa7jnbAy0zBUeAi2CEKjCKnKdXByC+wu/M9dwrSh4+heDR2deKDohp8mrsO6WFm
zJuShsz0NFy0YL463/37snlsA+IJpP7x/POwEBTl5Rwier0FERGRyld6enqqfU8Vi54J2Z5hwclw
OFEXR0hmdA7jsJdffBEvLlmCivJyvPbyEmRkZBKhRaO/uwObd+zGml15KGozQRcQi4BUahdhu4Px
mc7RrwlMmA76KQmtdNQrJSX1uhyNL1IAMAySLbEjNcqKaybHIMxHG7hFk93oD4+hpN5G4THUEC3V
voF/ioYO8RsoSApcXnPwP28vT3j7jUa/LRF76quwZ/lejN68DxdOGY3zZ0zGOMaJY9LH4tlnn0Vg
YAAn0wAO0+/t2bOHYOllzJk7FzNnzDwT8vnG7zjDgjuBthobGvC3Z55GGoPZRVdfjaeeegqj00bj
H0teQVh4GPbu2Ym31+1GYYsB7kHJCEqNoMB4ngN90A1QPAK7xbxx0+s1AWmCElWT/xUaUWIU2Q3q
LBi098KX5jHUR4P/IpRATwtumB6LlzYWoal9CF5ubhSQnQISFRVTS2HJF1BiSnDyOZFefw/N8hDC
o0cQtcYit6kG+asOYtOXh3DlRTMxdmwG7rjj59i8ZQtWvP8OfeBCTCfI8rRYkDJypJogGvQ8O/jz
XwQnFysB6NeDzuFNH4IC+pe33liKiMhoXDBrNp5/7jmaxltxGVFYbHQU0Von/u+Lr2NTfjMcYaOp
YTSLAizsg/RHdoUsRcPMAucpFSUqpV0iHzGZrqGQ1+WhRfB9tj6khluQEOaD59Yfxdz0CCSHePMT
DsQGWHH91BF4Y2spQ4V+uEtsx8+pH/6m/AhgZKwldFBwlOcxRN/FeTTUo/bx9Q+Gwy8IB5uqcOi1
DViQcQSLr5yPBfPnY9rUaTSNFo6ZCfMXXvwvQ/VN9N3wxvTUe/2L4ISEFfAgzMLp2meB+a8seQkv
vPA87r33ftxx553wDwyCGwdqBBmP7N278eKKzahABILS5sCdYEFvH4BjwIB+xmJCmkQHeHBgDWhq
60GfQwd3EaoCi0IdnxCc0jnl43QUxgAiA/SYMyEYB4qa0dwxgLX7qxA4YwQCOKCypUX4YfF0O1bs
qkI3AYuJ1+dwmkqHTABOWPuQgT51CP1UOzvJ6SROhMQQKwY4JkW1XShrpBYGRkMfEI4Vhw/iYPHL
uP3KWTT9Gc7R1TS4v6+XCJlAi65B6LQwPs709i+CE4G5HOu/P9jJ3IFmDgRuh9M5P/HUX/HJP1di
B7nDCy6YxalsxxtvvYtlu0pgislCTEgUzWEHdITr/RKA6R1Ii7Fi+sgAJIV6w81oQGFNC1Zk16HL
NqQEqRdfpDTMCbmdvwfkmAEmXJwVjgPlzQj2tWDRpHhsOFyND7+soKbFw+quXWZ6VCCOVndgx9Eu
mCl0WkIKS7yngBvRNj2FRB2lyT1vlD8uzoiAj4cm+O7efhTWtuPTQ7U42sh4M20iuc1y/PGVNbh9
TgUuueQiXocbbAz+X37pBWzfugUBAQEqK/HgQ38848L7Hj7uhO0WDV1PukoY+8iICCQkJiIra4Ji
3LvamvHc6+/h82MDCEybC28ZiL4eDpYJAwQg3l4GJHNmj43xQ2qkH3zcNa5yfFwIDlV1YntBG82m
Mx4jxB+i2TRIiC1jTY3RESlmJgdQy/qRXdCKmekh6Oy1MWTQo7C8G+t9a3DpuEhUt3Tji4IGlApI
ceNEEDVWbkgLIRzUNpkcHX2DGBNrxVWTRsDMSWynQMXfunHyGI06jIz2JOpkGqmrDyFRI9DqHUDT
/AUq65tx2w1XMdPACUhgMkg7++XO7TBxDEz0qydvZ8J0fg/BnTiVvMO5eOWlF+HPoLq2rp4w/0Zc
v/gG9HS04dH/+xr2tlkRkTENbkK49xPOk92Q2CtjhAWXjI9BQ1s33txWgU8stbhqSiQmjAhUfmts
lA+6aQbbuwcYm9FUcmBN/JxDfJ6YSf6YjGbsLeokn+mAPwPkw8XtKKzsoiYb4W+1oKCsE209JaTI
+tDSaVfcpRtVTROW5jfVPz7p7utHjL8el2VFK6GpkIFC6x2wY+n2UuwubIYHtVeOazHwk302+DF2
c0ufg5V5O9H4/Bv49e3XEXVmYvSY0ThMrnMuMxp67rtyxXLFEAUFh5y2CzqV5TsjgksiioqlD8s7
nIMnn/4bxo3LREtTA/7096XI7w1F5KgMGAmZFVrjzDYYHLg4MxAXjYmirzEiwt8ThdSENdk1hO1d
FFyQGF5k8ncGH9XNnXh3RyVauzWzKYG2jj5PMSUUoJ1CM8pzzmy9Q09wxThbYgdO9CGa46q6PphI
Pvt6CKIkgyIjocykgBA+19mREGpCgMUTY+OCEenDAJ3mXUCRTKCtBTXYXdQGDxOthdqfZpYARrhR
x2AvwZUJUenTsD0/G4PPv4Xf3rUYVt8APPrnx7Bv/148/uij2Ju9R6WXbrz5VgQFyfV9v+17Ca6o
6ChWLP8Q112/GBcuWIiQsHCkEyZ30Dw+8dxS5PWGICplLK+OMZloiwqaBSfSX3FgDRSabO5EkFdy
luv1dmqJCa09GqyXEECGrplmydbrgBdnuwTMCv87fZw8M9H0abaTATa/1+ymIUYBLkM8qGilOqpK
9ovm8pQEPJI1Eb8pYGTArkccKa9QPwklxARrocjhmlZszW2AlZpqoqkUkyoAzi6hifNchhyD/B4D
J+gk7Mjbg2deegsP3H2LovIkRyg8Z8bYsdi+fRvGT5iAmeddoL5bw8PfbfvOgmtrbSVfx2B63HiV
N8thpvkPf3iY03gAf3/1Hexv9+UszCIusSmh0VooZoOqQVCiw+oD9cp3zRkVpTTASmbj2slxWHWg
As+tO0KTZUVcqBcCGZNtLWhWMZ1wkgLNVZAgA6fMpRKjFtXx+dchkwhLoL4KvNVD4nVqi/oApwaf
uzmMqG8awIct1QjxbcIIIlurRYf6bgcOl7VRKw3wMJO8ZqiiNtFu+ldGgzQgNJkUpDwkEI9NycTW
nC/g/+Z7uPfnP8UVzOk1NjcTA6zFImYWfH39UFlViahIArTvJjP1qe8suPz8fBTmF2ABs8xrmGUe
Ra7R5GbCm2+8ic2lOkSMm8IZ3S0skyY0gfMy2BwkE486YHcjZG+At8WMiTRPIj0xZ3NGRTJ+qkJO
cSeONfQqFkXMn6f4Fs0yOpGlcP6awJReOhGnJjlqM5Gq0ginJJWVPll43EsjvgTVDtF3udEvOjjI
dmYf2pRBHWJIYKJhtpjcxLNqB5aDSvrIeWQxvUqQ/G23U5ScYOGjpuKTA58j/ONPceUVl+HW225D
JhO8hYVH8ORf/sIQKQAPMxcYFMzr/o7bsAXnmskyUA0kWSWpOY9CW/raq0gfNwGLF9+InTQFH+4o
RnDGxZwRNB+8ENEUMUfi5OXhoq48+Xo/zdOa7Gr4Mj+WHOarLsFKVJkWYUVFYzdnOk0jCWITHwM0
aw76HTeaKxk0g5DIJrN6X6F5PgTyiK+zkX2R1wZFrSh0GWbxSw5FSJ/QPL2YPCVQcV0S9Bv4/Xq4
8zOUmaLsROAS7wmvKcIRMOPgDFIEmXCdfFXpIf0hFZOaN0hfSGA0chqWfr6BpEM4MsdnkRoLxEsv
bVKJ27amZrz3zju475e//I5i+w4aJxdTWVXBuo+N1BwTLlt0HRYuWIAGFvBIcK2Pn6p8kZ3x1ZCB
85WzWTTCoGA8L5ZOXa/yZqSfKARbPxHXnipcM43miL5qx5F6FFV1830LZzpHgsezGwaQGR1I7TOj
qqUHFqMb4yuevFuvek8mvXgkMV16fn+Ytx/Kam2oaGDCjs8FY4hpUw9lNZ0hgDKVMiEEcPDzIiUx
Q3Ku8pzvKyZHgnPlD/k9fEOnJoQDg4pyke+SBwESPy/Tys7UkdXPB13hGXh1+edISkzAiPhEpoMW
4M3XXqcgmXWYmHVcaN8lPBi2xrnscWNjM1Z/shrBnEFiksLJO4q/eWP5atQZIhEZEkYsMiAxNQyE
3YIA9bxixXrIb7FM8lAOT0/fYUCnzYEVRI0msx6thOxuFJD4PwfhoY/FHaNig2DTl6G4vRkBfsFo
7mnBZ6U5yG8qI7DQILsMrs3eDz+9O/5x1S/hybydg4lTfqUCLGJmNS0S/VMBnDoHpUfyurpAThLF
WWrZCANtvFhHQZ4iGJGr67lYAHniUMJ2qi3/ktcVBGKGIDgqHoUHKvHhx2tw602LyWdeAitDlsbG
Bvzz45U4VlyExTfc/J3Cg2EL7sSs4IwODcGSF1/CLBbxZI4bxwwAS+DyGkhjnQ8TY54+zlKzSdIm
/HqlaSIwDYUJKhR0KYG0lrHWwZvUF8M1JjnJ2lCQlBmDc4HoXggP7MPG8s/w2qGNaOhsIoXlix6a
wra+LgXnRYvETMpgORj0zk/Mgie1Ve9lRh95y95+ljWQx5S8m1ysNzPfBjIcPeRF+0gA9FOaKnHE
7/CkhRhkqNLD1wfo78RKSNghHoyXg0Eeb4DmP8jXTeX62rps6OhxMM7T87vIbXLChvnzdb7W3Em+
F30ITszA6i/X47xJRxCXPBKBLMFY+sbruPyyy7Hry52sZ0nElClTTxthDltwMuh7iB5/98ADSGXc
dsNNNynBOQb7sGL1Zgz5x7Ge0ZskcjdSIsxIi/PHpkNNNBsyMTUymDGt8iV9nOESBJsU2tSCaSGU
NVQ4hN6+IcQFeSEjyYpfr30ZK/N3spzBk9pjQq2tQ00Ei8njpKJWDVjb3SzIa67Cr9e9iskxIxHv
G8b0TijimTStbO5TSFHn0YnGjkZE+fnTP7pT2AaS2xQIzay7Oyk4omKLmw+D9V4UlLfS3Bt53gKq
hLVxoJvX68tJkRLqg9Y+N3T2C0lNoXFiCDkwk3nA5m47Pj9cgwIyP/1GL7T6JuKDNRvwIGtqIsgs
+RBZpo4eg7yCAiZnP1WCO12EOWzBiSExsxZk1CipOTSoyqpRTNPs37cX2eWdCMyYochVI33O3LHx
vNABtHX3wtvdU6FK8RucrKy4GqQPJCdo4yCy1lHl2hRZLKUFA/BikBsZ6YOkGCOWHV6NTwv3wt1i
ZQkC83U8Bw/GUSdvCtUT74u/EQ1p6e/Gh3nbsCJ/G49jRgIz6JenTcdlydMR6ReA32x4Cx/lbEV8
YBRiAkIR7uGPEC9/pXG5R4upbT2YEJKAa8ZexEnoheJmVorxAkjE0IIMwdvojpKqPuSWVyKJidpw
1q1U1bWiicT2tdNGINTXygcwKsIXa3Iq8c6uGniFxmL3sQomkfORwjG7mGUQTz/9lAoJLpg95zsB
lGELTuI2YffHkMrxskrFFNP0tPufbcuGwz8ebgwFeiio2CAzRkX7srCmD2mRniiusak4SMyjJ8HH
heQSI/0sWLm7liaPJlWCcA74AP+ODvBCYpQZuQ278cr6PdhWfkTxfO4Sv7mwv+ZRTjh2ec7vpoUT
CdLM6ghcmETlTn2cKfubK3Bgy1tYdXQ3c3M+2FN9FO00j3tqSWFVFSkfZyKaFN/VT1M3xMdW93xk
RKaTd4yArqWXmk2zycmhsn88XSOPZSZZMH1kINLC/LC0tQsNun4Ek2JzpZK7aaJLGpgSosm1enmj
1hKKz3fs1QR36aUkCcz4kqZyNWtuvFlRlsnk7Olswxacr58fUkalYePn69Bw4CDZ8EtYYVyNg6zT
CEgex7ibdR4c3egAH/oK+irCvjvnJONQRQvNFGseiSBHkURO5oWKliRFdSGbNBIlxzTSABKDrUhJ
MOKZHW9ied52dHLQvYwkaAlUFFXmFNip2QbX+1qoIJv8704tdSfyFWSYTUEJIray5sRKk3r8+5yo
UsoiPPh6D7MAKeGxiPQKxkGmctwEoAh6lI1mXlWMSfkKNX8nSeuiynbUtduYrE1wUmravpvyarGz
sJV0GE0s3YFnUBT2H9uD+roahISGkx7MI7/ap6zWuwwNpP7mdGpWhiU4ASZFRUXw8fahqUxDZcUa
hbq27zmITgNNDc2h3t7D+cg8F+kr51UyJjNjWlLYSTqiDWoXswnNnKVGvZmapkMoa0QyU6x4avur
eH3fJpipMf4UmgBPAQRqKJxO4Jt8gWjd8d2c46w+KREIz9XHrAlLCUxRXyf2VyBEEKLoHwe6or0B
FR0VJLlHYmNejaK/OO9UCaAKKESYVL3SOpa/93bh8onhSAiSfgT5Bj2ONbbj85w6EtFuvMZBZuZt
8PAPQV2lJwoKWFFGwUXFRLPupgnz5s3Dl7t2ooXsyhkXnFzUkSNHsIu8W2tzgypVszBBub+gFEb/
GDpnCbQlUDahvKmbDptxjCoRcI33V/XkQEkz92OgSh8nLPuMtGB8kP8JluzdpBo2xDRKqEyZaknU
s7xph9CyD26ceLVdrXh08ztYdvUfkJUQjC+PsXydGQ0dyWiZCTKhDAKkGCZMTPTB3FGhx6eBjWh4
zf5qdJFblbhUSASxRO4mhjfU4v35x1jiMJVVYXNQWlKCAjJQ1157LfGD+bSuclgaJ0xJZ3sby75D
kJqaTMFdiobaKlQ09cA9ksUyAqh59ZIyqSZ6W8mE6ZXMZ3keP5kTDRR5lY0MslsZq1moCcwAJPqh
oD0Xz2xZTn9GpoTBtRSxCuEhdJkzxj2tizrdnUVZXdopEMjH7IH9NSX4r/VL8PgFtyJzwA+HyttV
sdKgIj5lRknG3sSQwME8Xw1GR/vBl21de1hWmF/ZQ6GZ1bhI2KMXE8ug3MM3mCmncnSRdfLzZ+Yj
k6HCqlXsaSClRl8YEuqaAN9+BcMSXEVFBV5gGdq4jHEIDp2m0vrFpZXULBMBhzZTJMA20CxI5e9O
5scaOwoxOjYQccHUICbievrszD630Of1sI6DfoZVWdLP5utjwj+2bkZjXydNMf2fRMnyfdovBTx+
iE0dhv+JposbsDLF81HOdgKWXrxw8W8UY1PdKekhLdiW/SzM+Ta2D2BVdj32FbdhRLgXDpU1k72R
1BXDE84+g9S28CGBvYC65qoh8qFt8KHgjLQ20qSSPDKVCpF6Wpc5LMGJwO66+262JC1FxoRMhfSq
mfHtM3nBW7C+zFdnQG0SeE/bXtIwiDKaVS+3BgIE1nHQmduJLj2pVZ4mIafoJUgqD3ImNhPCy2dE
WNrsP7ebaJ/Qchb62k2luTjaVsrcYALqyIJAJxkKok+SCxLXSVWEAWbUtgGlJKd1FJoXX5PQR5XC
O69G/KqYw2Y9u4xYKSBVAh6eVnYKrUdNbS36CFQmsW9B0Plwtm8VnBxw2bL3eIDPkMYYLpTqLNC5
kW1McPdWRUVCrMprigsUMplHNpENUTLls16aChGohXZeWBG5HOEV3PnZQUMfGrrbWGTMARnOGf9A
+4jCu9Fs97KU4fGN7+Evc3+GrLggbKV/FoQsZl6sgV1MIbXLnaZTLAjjcYYA5GmPZyY0flQr6iUA
ciOBXlWjBDqB7WFJCYmsT9mKL7Zuw9I33xp2xmAYgmOqgw2GXR1dhKwjOVOSeVAHmlo7GUyHq2Bc
T3pE0jbCjsgJi2kQalmkKU5cCVM0kRcpdfwiYAMdfWKUH/ZX72aQW6v8m0twP5B1/LdTQCV7eUIS
ImwsZnfr+hfx2mUPIsPmjZzKFmYCxBvaVVAuP5J9kJyB+HrhPbV4Tig9WhfXpBYXQLpN6lVks7Gl
q4ptXwH+Afg5LZqEXMPdvlVwMuiCgCLCI1BdUw1pvU2Mj6VJYG2ieOuToLXKiSnuVROWa665BCG/
ha6SdIuFDEpCKAPxL8vQ0c/aDRbZCBj5oXzacAZIw8LkUr18sLU0H3/fvRz3TrgSft7B2FvSgnYi
R1XCTg1j+4FKIUl5u10QKCe3gZaIFOzxTcJRA4FIH2kz2Qb5uRtZth7OyoHGxiYWW9UihmHCcLZv
FZyw3++88xY2s7b/4ssuZeUWW5pYA9nHg7qa/E4+0LeZO8Wc04baBlhRRU4vzo99bwQkgiQNvOBz
7+G+OmyiOULXWTmxluzbiE0lB3Fb5lxclDkTOw43o7Cul/GqBVFeTB4HMRlLYe082k7CWRXHn9hE
C2UykxDoZJeshAjiz/pZkbbuszXsWvoMv3vooTMgOGfoJT7s2usWcybpsH/vPjbHz1AZX03TnM5X
qcpXTvOUk0YmpWQJ9PQHQzSxhyraMDthMhaNKcAHOTvhwwZCF0kxnFn3Q+0jVyomX6xFTkM5nt7+
T0yNHYVZaeEUWjM8vYZQ3FOMY30dmBU7iTxmJ4Tykuy5aiNybYq30zRTxm6AClBVVU0GqoGszgAD
deYPh7l9s8ad5Gik46a7s4PNh36qwFPK083M8jpI84tpcznf4/TGVyeai/RQJ+tKw0j5Qhmrt0Ks
QfgTY6VjbQ04UFsGX7b5/qhQivNatDojPfzdfVTO7b5VL2NWfIYq199dlINdxXlYkDwRo/0m0ndp
iVhV1uAyQeJC+MROIt1KTlZwghebS6RtWii9TRvWf6Xr9tvkNwxTaSc/uV71ts2exxpBshrK9TJJ
qXI2KhlGVkBlmZWD+5dxl3PXzl8r1tGyxoTHNBsHmDoJ9gnDg9Mvxw3v/xWdrFX0ZgCsintOcfYn
hwvif06917dd9um/Lzoi+iLgysZK5101R7G3rkhl9eW5oOILU6YyrtPxGgbUQgHshDhpEoqlkS6k
PqaoZJiMqKurxktLXkRTfT2Sk5IwnQsRDHf7ZsG5LCEFcS9rIyT9IPSMnXSWFLT6+lgx2NzrJIC1
AdQIXsHDLsyiCUiQ8de1UclYCmw4EAerWjFt5Dg8eP6VeOaLVWixMRiXdJDAZ7WfE7RI3osz3Mac
mc650IwH23/dJMNwEkg6KZHwb8dBKZHzOjXkJ1+jBdfaGWtoWOmK5BOVpZOqMT38WKE8QKpPTk5v
M9B0JmJkYAq2ZrcSuMlJSw7v+HA4z4M7U3Dezt45T/b/hbFA1o/ZgclsHDkzXKXTVAqEFxu87P33
aOeNKGTyL210GsKDg6A7UqVK1oQ9lwFwaYOKYbipDLWEAU5tU7Udkh7hvsL3Ka2jTWli+fiu/C5c
l3IVkgJi8MTWD5BbXyYoRvOnaryk9kOHIHcr0oKj4M/ShHZWRec3V9Kf2FSnjIy3WfVs/3tr65qT
Sot4Tv2cDEJmu6lyBaMCTwrWEzT1DdH3SC0JT1gshGTsXQIXAqGfBILUgF2XPhsdLSbUtzN/R4JC
CptUT4LzOhV7Qknq2L4VH5GgLmnD+nXYu3ePIu8/bW1jZ+7E4Src8MrzyivKFSPwW6Kevz75BFfr
OYToUBbvDFIDiS4NLOwQwlWy2zLbVBmcDJ5SvhN/S0+a+GdngbCmJHxuYl1AY4+NKK2flcQTGC/F
YXn+RtT1dCLYw1fly1r5t0VnRlZkKuL9YxlfsfaRDMya0h347w3vknlgAR2F3DFg4+taUes3bTKI
UkdiJziwsJ8t3jsQfu4sJRf/LQG18+SH+McAhSelEh22btR3tanJovrOJYqz61gi34NrR7MV2j8d
6/Y0MWonuU4KaIipBK1CzAVOmF1nHYplyMbVJFhLSjezm/m4awj8/NnzvvT1pU7rNLwo9lt9nFz8
qNRRWLXyIzz7v//LqlyeHG11fGwk+UbW9NN0uklftWZEtKnuOrYISuW7RMOUt9ZK4fgwUMiimYPC
tkj9ImdzP6WYXdzIZKwvroj/iaqAFk2Seks9B4MRBMlashPs4GG5B3Ssd1g08kIOfDRaCKvFq/xj
72rsYrJU+uu0OPKrm9SMSHl5CGtXEiLCWa/prjSuk838bZ3tWpGry7lS4UV/PZkTjAkIYeomQvng
EhIGdd3tsBFFLkgejzsyb6TFaOc59KnzZXOrwBDNUAg+EcvD17vbGhHqwZoVfz8VAweFhmH5Bx+q
kGAO11E5ndWMhiU4Wevj5ltuxWFWK6ezlNpK/+YfFMZqYw/kdrbQNkcqx62xCNQ+JT+tAEeEpbk4
TbSqstH1vio7FT/Iz0jzvTNpWd4kyUk31SFjEBZeUkakmVS/gPSB09mYaBI7OavbSUlFeyQhxCx1
KsxA873dHxUqUley4a5NJkkvNceXvnNceDw11h21XNmhkoPpIclVAiIf0lHORmV1jmIZZNCFVK/r
aKGgehHg4YPxUUkoY4dqqLcVd4+/CQVHdSqdJVTYIOM4DaDJRJVJItdMX0nCore1HgnRofDk2i6N
TU1cCCcWYSHhbJr0VfU7p7N9u+CcSNHbx5eNDMxu07E++/e/4bHHnkBWWiz2bqmCIyIOpsEuUjta
q5I4es0XaMWiyv9pcFILtlXikpejHJ2Uv4lg6cMITcW/iFuz07cM0Jyo0jqZDFKvQgEL6y4zQkyd
1I/ZmD2vkgpiqmMAE7cycQQbuNCmiE7OoZeDnuIXhjExiWxQZCFPbTk7VUOQzEnXxnVUegnTpRVZ
+gKUpsokFBfF83HjdfnQp4azNLCtsw2bju7HjZmzcX/WVdiyvw0F9U1s4CdiZIGvaLNyCeoh4Y9c
J+ktuhR01WPsyLGKdTIRWpaVFqvVlKbNPA8XX3Lp6chtGD7OCTQaCFDWr12Hvzz5JHZ9sQMbWMIw
h+tdvbPxBbbx9tBPMSRQZlFrEJTfqkxVahZFeCI2mcGCJakNdA9qgNQgCbjhTmKm1FXKtHfuI5+T
UnGnl9fMDwWuJocsQKN2cCjg0K/rxj8LdqFbShSca4KJWbaxo2Z0WCwyQuPwRVEuWXoTpsSloryl
gT3oNRSKhYlOC/u3zUzsSg2MRt2JL7RRoD30a+Lnqrk4jpXv/3zShTg/egq2HGghX+tATKAZNew9
kD4RqXoWUKbGggcni6uI+E5ShWEs4E1PSVKx3waunSL7xMXHc/WG+NPybzIG365xznkwlVVdG7i2
x+9/93t0s497xvnncW3IAIyL8cWWmmPwSEwnYupUqFGrDha+0gWvNSSmTCSFJLWkLhOqqGVNEZVJ
VVlmVc/ofE3KxtVEcNG2Ug4u5INWZKvydhwg6WK1MMcyONDNkIUVzgQoUp4uQktlvcfY8ASszdvN
ho5Q1j4G4svyAgIfPyQFRqoViAQx08jxs9R0Yf75Y2LYI1XTXuQXhYv05ror3kYLZkfNgKPHC402
LiPFgtDECB9qfjfNex8b/l1NIJpbGKTFkDHpIeMyNykEQVx/rIQrAT7+2KNstwrBL371X7hoPrtZ
T3MbtuDcmEu67fbbceDAAVWil5AQrw41Z0YWtr62jgU/KTArrlFjC5SQFISU36JlIkgxP5pg5C0H
R11e1yA/L1KELVXDyjUJs04zKghNVRdrlftKaNQoVTrA71GBP3/a2ZpV3Qw8MuenPJ4By4/sUc0a
IRZvTIwcic+P7KNpDEWETwA2Fuxjo38cPEkmdBItism2MR8mNZ6iHUJtydZLcCTmWlqqpFchkMjz
oQuuQ0udO9bm1CCN1WxtPKujtR0qidrBJRMZ2SjWRIQmk01KD3u6mRHvrcV5U2SdFNbYsCd8yatL
Wdq4T/Vh2AiMLIzpTsZ13ybHYQtObHZcXJx6nLylEnFmRu/CvoojiEwcDQfjFPEpEny6Wpl0YjJk
LBTHqcVwYk6GqHoq/yrzW5kZgeliKRUUcwrUGdzLUxEqv0MNpGic1FIqdCrASI/i2m6MsPvimfn3
Q+/+At7P3oR5iROQ11CpOkzjAyOwvfAgbp84n7Bf/GOfAjGd9HHBzL5XdjajjmBLkOMAZ5aY0DgW
+YRa/VHRUofUgGhEs27Ebu3C9NRAdrm2IZxFQh21LSzUZRFQUCC6KzRSQesOkqnGyubaPMyI8+I6
mOlq6GRh0/HsH5CHq3DpdPsHhi24f12BQXP/7swSXz5rMpeQWMcmhzjVriQ1/6JNmropMahN+qml
YULza6I5Wvm32FQjnZ4W32mRn9JSHkAEIiSAEq/MZPkOETzflNmsmA3RTD6MPJY0IhJo446MBThS
U65mf2ljBS4gbN9dls+F18Jwx8QFCGYgLyFID0GLsPs9FGIdE7qCPMU39RNkiAZK4VKUTxDLL0Q7
u9Q6KaNjA7hklB67Crl4KZf9iAzyQFmbEdG+HlyZTxLDdq0XUOeGbi5zZWkvwtU3X3NKJfrKuJ6G
yg1bcKdWXc2kSIhwwaiDWF18CJFpk1SZHkvpYZLWKApQul5kTxGEXXGbUmCqDbj4Nol5RJPUOnW8
YvWaaJGyuWI6lXNU/tGV61MUlbOtV128BNUKsAzhWH0rk7SBuC7jPCzL2QF/lgj0kCbrJssRwAzE
G3vWY+HILJLaxShsrUEdO2hDqFWSGs0MT8J8CtnduYLfkaZqvJC9hkxOOWstA3D3pAWcZCQbOZea
2cTf0EFtpa/X94Sgm6Np9XZDQ5cgbO7A+K/h8C5cn5WI+KSUb7N+zrjp23eTPb6H4E6Et5IcvPby
C3Hwr0vRUl/LxoZwVgRz5oqpEM1x2nyVaHRiTJVolJBB3nMiSplwcvba6xJKiE/U2n2V2RHt0xLr
2kO+Tf3t+qQ2kdp62OTRH4DzRqTjpS/XYgS1rJr1L1EUjiDEKprDPRVHsbvuKF7PXssQxwpfMjEX
xY7FxNhkBtEG+qpeLNm5mk2ah1DUXk9/N4hKksLRfoFYGD+L67C0s9cA7O0zo7XDzpYvKRzqR6Af
e/YE3PD7aisLkWRpweULr9Kk4Qythieaf7/X9xDcV784JCIaP7tsBv787hfo9bmISExYEWqRSIXT
U6X2Oeiqd1OCWqVVWi+48nnO9iYV/zB2koiAVd5q5Tvxh6K1EuBrpDCFKByoaLImKy2wUOZJSs9Z
WsFu1rh4L5pBd9VX10BWxJ+ZbG9ns8i++mOMy4KIGi0ELEHwYZ/4T6csQASXv5Dty9KD+D+b31at
W1Y2s6QFxyizJ00f0itXXNtJQOJDzrafFW29DCdYkiAdOjKJzF5cforJ0ppDuONn8+EXEKT8vuY0
vtr78F2FeMYEJycwlWmJq9gM8Xb2dkRlzFIrLYi/UNUYFJpRTJtUG4q1VEhNGVAlWNEkFfvxuoXa
ErSoeEOnZMRMKpTmdJ2a4DTNkz+0+g71cRUneXoaaB672GbFVZIEwIi/5GcnRyWjtK2OjxZMjE/l
ig8EG/RngUYG2E6hybVo58YP8ZeJZsFGM+slvKZfOCuYO1jF1oUgkhK9bjWs3GpGojFddeyAHUCD
g61oz9uMn88dw/I7rYFRg1gybc/MdkYFJ6e3+OqfsHTvZWw7vBMRo6cJt3G8DkOLtVXl4omz19bj
VUG7+A2FSJ3LEyrhyXsqINYEpflvMb9iQmVgtRBCtFBeH6Rz9aH5igjXYSPrRJpJThtJDvRzEnlQ
88J8ArGvpph1kg2o43K+YxiUH6w7htreTuRWlyKKqxvJNiN2DJ6cdxteoimt7m5lDWkvQslvxngH
IftIF7iKFSramhguNKsFCvpZ3mUnUmUYjtrc7bh4jB+uuGTB8etUIjtTUuO3nlHBiZlzY43+fbcs
Qtdzr2MvY6nIlCwYyT4YGQ/JUhPCLsjcE5CirYagARGHmD9qhtIkFQPJeySWlWadSAWpNJFzDDQ+
UBOkGhQeXxoSA70tOEz/taMkT91jQOB9IOM5objaSR740jwmMjSQyXJh3FhUs1eglWHMU9uWo3Wg
B7NjRytOc/G4WdhXX4omNmuMDgjD3ZmXItwzgoNWweLWFuSzv2BGYipbuTxZhsFMRrAJVTm7MDFs
CHfddj393umVlZ+OLp5RwWljx/gnMBS/vuMGPPHC2zhckI2wlElk9btUz5xIToCHgsviu5T28GXh
ImkOhdNX7zvTcKJpKrEp8F80VjEm4s+c4YMYIJdzU7LWcbUfE7bThx1urEYsmxsrmutUjYgfmyNT
uY5YEPNf0iPQz1RQODXQM1dauyoAPx2e2PYh3j2wmTFbJJf/bSKaLMFPx87HpOAJCDAFoaalC1nJ
vijsrEc04uGtC4AfSzo2lO1Af/ExZHDiLrrxepgt0oamWYSzsZ1BwTkzb07fEBwWid/fdROeWfI2
snO/QFjqZAbBTNwo4pgJGErGzRnHCezXMKpapFddq4QLIkjpTTvuCiXGo5ZoFcLcT/k2qd1U0a4y
opI/a+6wYWbCOPbXFRB8cD0xrh3WTdL64yO7sa30MLMaIeoWLrKvZBzcmSnwIjipbKrn8h0eqhx+
e9UReJAJuivrcswMm0L2vw95ZdU0w27oMJcgp/Egl/AOQLwXM/A8j8NbCjBvhBHXLr6SVKC/mmwa
8j072xkUnKYFJ2+BzDf9/v6f4YVX38QGrvvhl6otxCkNEFJEOyDgQ1FaWo/4EJ2aYsC0EJz7iFZp
Ps6VbnGtbqKOJO/zl9ZALwLXjn+guAnT3cPwwPRF+ODwFgKQUOwrO4Ip8aOxLn+PylBbKBRhR6S2
0Uy2/rz4dFVRXdfZqoDIkL4fd05YgPnxF3ApxQa0MNFrMjD7YO5i7JfP3FsXok0p7AVkmfraD7Eg
wRd333oN3NltJNuZgyGnFvwZFNxXD7Bzx3Y0Mee0kOmK3/ziLoS/9wGXPVyHnshM+IZEcy0RG0MA
ap/0VguiVBerAQzV+ylEtXyliyITEyl/nzSTT8wTVxynzfBBsh3rc2px+YQIxVPaqFm7uCBcYZ0w
KOPYlJKLUWEjyPJY1Ap+Rmp3B7XSi8T0KBLSLd1dyIwYgfunXIZPspk07eznqn+smZQFABxu8DfH
sHQkCiOMgSj54lNcmxWDqxddoUotZM1Oud/P2d7OuOBkdZ3333sHaz/9VC3KIoto33jTzbj++uuQ
ELcTr6zczHRKDQLi0ql9Xlxg26Y4SK1U06m1lIhqERTA4kzMqhXPBcQog+hcNchpilwBuGuwhLmR
ZTS+PNaMtOQIJj3XYjJ51O1Fh9RMmMZMRnZZIYtcLYhm2YKgWU8KTcBRW3+XWsR7QfIklNT2UIhs
+ueiObIcvkyKkjZm4HviEd1dDn3XASxeOBXjuYp7J5feX8r79Eg1svR2Z3HNrrFckULKHM7Gdsa/
VfjHg7yTlA/T80/+z9P45S/uxzO8X82fuJLcxMlTEBcbjWWr1mND7np0ho1BUHgM0R0ZeFJSKsh2
siVqBQZBngryS+CtJWaVMZQKKvWHpmnHzZKLQZGXGbi3st8h3CuKWQITtuYfxDwuDrqDgfV+Mhrj
ohNQS1K5iJSWhT7OU9qL+Xkru4bumLwAQYYorOG6YgNSEMHJ2MPyOxvrSAeaKhDQV4kxUV644Iqr
uLyTtqxTGSfoRhb/SOVWPisFzOQ209LH/OcITpr9fvf7h3hrsHdwzz13q2V9rcya//r++5DJKqar
WQB6zx03YeKuXfhg4z7kHiqBRwT7n+mHmPVSRUdScSWco6BLYVxEWgpJKjQp46sFxq4wQPZV23Hb
KR7SwLVQdMgt7sZD592CX332HFbn7cCskRNYslBPwpnZDNJXiawjaWV2oJHMijc166ckDvTdEXjr
UBkbO7gSHwuZhEftI+1lainDGB8Hpp8/HomjRrPwtQ/P/f3vzJzbcedddyGS/RWyQuzfnv3HsLtu
vqs2nlGNcw4fFxxl98kdd2Lbtm2w0V+88/ab7PipV030He3tXJTsp5gweRrGjZ+Azdu+wD+3HeQ6
lWzUD0xg12aAYuIV2yL1Gyo14sx4qyIQLa+ngnaxcUqAriOfGAajsDAc8M35TZhvjMLfFtyDG5Y9
hvf3bcAkroEyKiwGNR3NKGmtZc7OE9eOmYb0wLHo6/LEwWY23XPxAT351hZWWNsaSghEujGHN5CQ
Zevlpkp1tTV4/PHH2HyfhjFc2vH5557FpGlcQoQC/T6Lqw1XkGdUcC5MKYG4kZp2waxZ6gIt1DhR
BllpYAovTu6dIwlEubHCbK6Ufv6M6di4eRs27S3E0WIHOixBMDP+8rD6kaWn8ZQ0EYUoJkvLDmja
ddzXKXZFCwe0TSOz1YMvfZZbgfujUvDXhbfg0S0rUE9h2RiUpwSFY2FSJmJ4J5E4v5FckMaOw+xQ
tHWxE6ehBkbWiCQxqF4wMQ2zZkzh1zK3xjtvrfp0NW+E0YBGViA7UlKRnb0bzQRit9x6m4rpfojt
jArOdcIuWC4CDGULkTxkmzxlGhl1d64Q3oFHH/lvrjrQwrT9AkxhWcTcuXPUYz9v4rcntxAH2Ala
V8ubPZh9YWaQ7EEQ4U4Yb2A8JmhUaC7l9RT6dIUiLs3TSuOc0Z5axXxPSS1XPErAI9PuIawnLcb4
q5Q97J3UsIpKB3ZmF3P9rQbG4B2IYcVYQKI3xo06Hxn0U7IV5OdhF1dHkEo3T4KaY7xz5PTpM3gT
jDKu2ZmJX/7yV6pX8Ifazorgvi5A13MRmmyf8JYt5aVliGFh6KqPP1LaUl5WrjhNKXUXE9pcX4Oj
JRU4eKQMR6oLUFcyhHp4YYjUldHiwwSuhbWnXLOLxTtKARV3dsJkyl/CsshLci+rTeQXd5eyf4YW
1Mxe9QB3LhQ30IniylzUN9RxiSg3pHMB77HJoxAXGYZAEgjy4f37D6g7aX284kNWGk9QPRQJCQlc
3X02V8SLx11cpv9cbGdVcN90QdJC29nawbss5ihE18QV+dasWYs03nFx69YtrKOfTu2bi8nM602e
mMmaDBvXRWnBsdIqFFbUcsXxUt6RcYA5MxbhcDmKQc70Ial3UTOeZlIIUVVDrt2CTIJ9O9MzLTS1
vIsAtZ7QxdONGujHm/1FE1RMVF2hnt4SPGtDspI3/Nu9a7tChZERUby3QR8O5x/BH/74MM1sHyby
RklW1lW6NteUOVtMydfH8pwILikpmbM2US16I2UOb735BgfTggvmzKM2fqzW7T/Ee8tNnTYD0+gT
e1k9JhXCE8aOxnkzpqlrsBM4NPA2MNLX0MkinZa2Tq4KRG5eRo6+SNVyUIONsvorIbovheJHMjg8
LEQdSzEcqiRC26Qi+913ltE813KN6etRU12FNfRlcjPcsbKqeXqGul3njPPPP+V8/KEE5jr4ORGc
HFwSqMnJ0k8O3PuLX7BOcwM+XfUJ2ts6MJ2dK59wVbm5XHWnj+XZDz34Wy4dPJq3KWPBKgWdSiSX
xLs2RtLUhlEb/t0m4YV8h9TGyP1SawiWEhJCUHS0SAENMX+yyQ0I3+ZyhKKoO7jS7Q0kDabPPA8L
Fl6iVnX/sW3nTHAnD0QYwcsNvFeBaJAgTVn/o14W4/zoI7zMOxLL4miXX3Elnufdo76gKY1LSsAS
3gpG1ky+nWFH0bGjZCyqVZagoaGJcDyIq0OEoIJ+U7o+bczJeXEhtDYG5Nu/2IaLWcco5jSX9wVI
Zamh3C+86FgR6a9B3H77HbyFZ7tqeXriqf+hH/3qzR5+LAL8UQjONRjBJy0u/ceH/xvHaEpLS0vU
ynLhDG6t7CO7/c67cOVPFuGztWsh9wR/nwuYrWehbiZv0Ce3OetnwnMMzZpksOUmDbG8habcqEma
OmQBgiQKvYM5uXWffcami1B1S00R3Ki0MXiE7E4WSYKzRVOdSaH/qAR38oV50LRJsCsP2cRnyW2/
JDHaT3BwyaWXqfLtqKhoplGsSrDePt70eWQ4qCX+Af7kELMQT18axvfKysp4o1rSa/RrU+k35d6r
sr/c/002qXH8T9p+tIL7+iBKbHg8uCXSO7lJ4j7GUALdL1q4UN0JUjRM1oCczdYlmQCnuivX1LN8
Y76zPQn+YwT3lYH4GvZ2Bb5W1kzK4/+H7T9TcD809v4RzoT/B1p4oLRxaWokAAAAAElFTkSuQmCC

------=_NextPart_000_0198_01CF1D94.C260E8D0
Content-Type: image/jpeg;
	name="image002.jpg"
Content-Transfer-Encoding: base64
Content-ID: <image002.jpg@01CF1D94.C1E77310>

/9j/4AAQSkZJRgABAQEAeAB4AAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0a
HBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIy
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCABAAXEDASIA
AhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQA
AAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3
ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWm
p6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEA
AwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSEx
BhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElK
U1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3
uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+ikL
BVLMQAOSTUUN3bzsVinjdh1AbmldXsBNRRWJq3izR9FmEN5cnzD1WNSxX646UpSUd2VGMpu0Vdm3
VW61KzssfabmOLJwNx70yy1O01WxN1p9xHPGQcMp7+hrxjxXrz3y/Z3RkkQsshJzvbNYYjEqlG61
ud2AwEsVUcXolv5HuYIYAggg9CKWuV+Hl/Lf+D7Vpm3SR5QnOcgdK6qtoT54qXc5K9J0asqb6OxB
eXcVjaSXM7bY4xljXEeI9auhpi3DXZt1lIMccY6L7n1q3401Jd0VhuIiT95cEdh2Fedane3niHUl
tLRDIpwsSqO3vXDisRa8InsZbgVK1Wei3d+x3Hw61q8u5rmwnkMsUS7kY9vavQK5rwb4XTw5p7eZ
813Ngyt6egFdLXVhozjSSnuedj6lOpiJSpLQKKKK3OMKKKKACiiigAooooAKKKKACiiigAooooAK
KKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigAooooAKKKKACiiigDlfHc9/DpFsLGGWXzLl
Ul8o8qpzz9M1HHpcavbzYdrmFQDKpxn1z7V0d7IF2KUVh1+Y8Cqc10fJISaEsAflIIGK8zGRjVfJ
KVkvvNVP3UrHP3fi+KC9ht2nf5vvj09K868bapcHStZaxjZ7i7ZVYr94AcYFbPinTJLm6aXy8KDl
WjOQBXGajNcRxsJDkbcDH+eteXTnUjVVpN26M0p1ZU7yS30Oh+CNxqFnqEljcl/LmjyUY9CO+PWr
nj/RjpuryNEgEM4Mq8fnU/w3ntdMd72+ciR1Crx90H1rpPibBFd+Hre9iYOFkwCOQQRXpSkquHk3
umd+W4t/XU+ktH925J8KnT/hFmhTP7uU5B9+a6zVdRTTbNpWwX6IuepryHwP4sXw4Z7aaFngmO4F
f4Mf0qTXPE13r2opBZbmkf8Adrt4zn0qVj4woJR1kdNfLKlXGSlJWi9bjb7ULnXr1tNsUaW4ml3P
Jnr/AIAV6T4Y8J2fh22+VRJdPgvIfX0FR+EPCsPh6wVpEVr2QZkf09hXS104XDOP7yp8T/A48fjl
P9xQ0gvxGSyCKJ5G+6ilj+FZEHiS2nSR/KlQJCZhuH3lHWtW6RpLSZFGWZGAHqcVx1tol+lrIiW8
kRazeKUO4O9j0C+grqnKSeh5LubreIYksYrpracLMyrGuOWJqaXWUjlWAW8r3BUuYlHKr6msL+y7
ubRrCzWzuI2hmQyb5BnA6kHNaDWd1puvG+iikuoJIBEwBy6kdznrUqUguyx/wkdo8Nu8CSStOzKq
KOQV6g0f8JFbNDaSRRyyG6YqiqOQR1rFTw5eMluH3xmS4kmcxtgxbhxzSSaZfeTpiyWDt9jlYP5D
BSy9mH1pc8xXZ019qcWn2Au5o5NpIGwDnJ4qkfEluuUME3niURGLHIJ5FJrtpPf6CsMELiQuh2E8
qAefyqrqHh4mO1jtfN3NOHnm3/N065qpOV9B6l9PENm8NvIok/fSmEDHKsOoNNi8SWM1ldXKb8Wz
7JEx8w/+tWUul34gsbY2oC2l2SZFIHmLg/P9ar3fh2//ALLjlto9t2SyTRAjDoWJBPuKnmmK7N3/
AISCL7dJaG2n3pH5pO3jbjrSReJLGS5s4DuRrpS0ZYcfSoTYXP8AbV1N5Z8qSzEanPVsdKz7Xw9c
TwQwXUWwLbFd/GUcNkEe9VeY9TbfXrVIpGw5ZJvICAcs3tVm0vvtSSHyJY3jOCjjBrl7XR9Vghhu
54RJc292zmNSP3ikAZHvxW1oyX32u8luVlSCRgYUlbLD1ojKTeoJjf8AhJIR9s3206C0GZSV6VZm
1u2gkgjYMWmiMy4HYDJrJudKvHTxBshJ+1EeTkj5uBUU+gTJc2bwRyOotJEkLPnDEcClzTDU1o/E
EE8tvFBFLJJNGJdoH3VJxk1Yv9Uj0+S3jaOSR522oqDJrnpNOvltNLjt7OSK/gVAZkIChf4lNaOv
2Vxc3Onyx28kywuS4ibaenrT5pWYamrc30dpp0l7MrKkabmXHNVJ/ENlBpltqDFjDcEBMDnmqt7Y
X1xZOY5JGR1UC1kA+XkZ5rKm8PX62V3bBVkihObQdyTyaJSl0QanS3Gr2ttf2tnIT5lyPkOOB9ah
ufEFpay3UciyZt2RXwvUt0xWRe6NqN6txdg+XMpQxRcc7fftnmo7/TNQuP7SmW1bdO8DhMjnbjP5
UnKQXZ14OQD60tQ2srTQBnheFhwUfGR+VTVsMKKKKACiiigAooooAKKKKACiiigAooooAKKKKAK1
7bG5iwuNw6Zrn5tNuFBDrjB+9g4xXU1ja9r9no8AjmYmeYFYowMljXFisNTmnOTsXCMpPlirnJX2
lSRFjGW8tmB2ocgn6ViS6NNNceXJbIC54JWtLQdQvEH9miISzzStJNOzZMfsFrsm+wRzILhJoyFx
ll4b3NeXSwjrR50ypxcEr9ehxGn2MaeZYEI0jffT+IAe9ZutS6npelXOjXS+Zp7OHtpweR6g16Lb
6foS3RljlTzT0y2CKy/Evhe71G332s4lSIfLbg43e+axeBxdG/JrF7o2wU6VOtGpPpqeQKjqxKnD
L/Ktjwxq1tomtx3lxB5yLnkdQT3rcs/CkzQGS70maJYlPmHzcDFdHo3gjQNT06C98qcbh91m6UsP
hqzqLl0a11PpKmZ4adF86dnoFz8ULFYs21pJI56BjgD61iR/EzVBdb5LeBoc8ooOcV1Mnw30N1YK
syFh2fpRp/w80qyuEldnmEZyqt0/H1r1nDGN6s8+FbKoRfuNvzOqt5hcW0cwBUSKGAI5GalpFAVQ
qjAAwBS16R4D30CmSypBE0khwq9TT6yPEUmNOEIzmZwgx196icuWLkBbj1SzlnWFJcu/3eODVW1v
2a9v3mmAtoWCrnoDVZIvtNzb/Z4mW2tFzuK4LNjtVKS2uP7MhlKPh7kySjGSBnjiueVWe4joodQt
ppHRXIZV3EMMcetRjV7NnVFkJ3HapA4J9qyL6BDYSXEImcu6rI7D5tvoPaph/pGp2rJA6WlvGXU7
epqvayvYDUj1K2luDCjFmHBYD5R+NNXVLRpRGshO5toYD5SfTNY8SzN/aSWaP5Eq71LDBV+4FS6X
bW8623mec7wjhGXCoaFVm2kBuTzxW0RlmcIg7moE1O1cOTJs2Dc28YwPWqWuxyE2koRpIY5QZEUd
vWoNUKX1tDPDExiWUeYduCVFVOq02l0GalvqVtcuUjc7gNwDDGR6iozrNiqqfN4Y4yB0+tZshe5v
ZL2CJhBBCVQEYLt7VGbF49JsbZI2Z55Q8pI6dzmpdafRAbUmpW0dwINzNIcZCDOM+tNjugbq5Zrh
PJiABX+6fes4EjxAJLVXw6lZwy4Ax0NUmhn/ALOaV43VZ7rdJtHO3/Ck60vzA0rrVfPmtYLORg0k
nLbeCo61c/tS0Eoj83OW27scZ9M1lOs13fuYoGiiit2EJIxkmk0q3hkggSYTFovm8sjChh3pRqT5
vURrvqloknlmXL79m0DJzT769SxtWncE4HAHc1Q0S1XZPdSRYkmkJyw5xTvEG42UcYUlHkAcgZwK
055ezchkV3qrtY2kkZMLzSAHPYd60INRtZxIUl4i++W4xVCeD7XrFmNh8mCMuTjjnoKoXFtcz299
OInUSTKCoHJQelZupOLb3/4CEb0OpW084hRjvIyoIxuHqKluLqK1VTK2NxwoHJJ9qoabDbyzC5Xz
XdV2qXGAo9BVXU0ddbhnlaRLcJhXQZ2tWntJKHMxmmNUtDEZPMwA/lkEchvShNUtHeVRLzEu5uO3
qKyprCN/sNvDG/lyS+bIzdTj1qaK2M+q3zmLZGkQij44P0pe0newjSF/bmGKUP8ALKcJx1qvHfIj
3MstwpgWTYvH3T6VnaVDO0Ky3ETKtorBFPdvWoUtJW0yzgKMGnuDJJx0+tT7WTSdhm3/AGtZbJH8
4bYztJx1PoPWnRajbSxyOHI8oZcMMFfwrO1GBINQsZGj/wBEiByFHG7tkVUuIrmVL+7WJl+0ERxq
RyR605VZxbX9bAbSatZySxRpLlpfu8Ukur2UJYPLyrbWwOhqhJa+Xe6fbxxny7eMuxx3xVM20j6X
Kfs7ede3HORyoz/Kh1Zq+gjej1K1luBCkmWIyOODTTqtoJAnmZBbZuA+Xd6ZrOntpXvnSCMqsFsV
jIGAWNRaXBBJDAk3nNJCN3llcKGFHtZ3tYDWl1Wzh8zdL9w4YAZxUV5q8VsbdVVnMxG3A4x61li3
kXRru48ljcXbkbccgE4qw0fk6rp8To/lwxcEDI3Uvaza+78wNb7bD/t/98mip8D0FFdFpdwK99eR
WFo9zNny064rnLrxZo8sSzyW5l2/dcoCUz3rI1Cz8Xa/qktq/wDomng4JJ4Yf1NV9c8NXNp9jsbO
B5lkI8x0GAOetcVapWkv3ei80epSw+HjaNSV3vo9Erd+5taDqOm2sc1xHDvuJWLuyLyF7A1Jf+MP
lMdvaEuRwZOlZS6V5Li3gDKidQDyT6mrI0dtg2q3vmnT5qdNQj0PLnNyk2jk76aS7maeQ5kY54re
0myv4tBn1KG5uWmTmONGz+lPl0MtjbGScHjFdF4biktYjCR8vbPenCDvqKGkrtXOQn1zxbeafMJb
Ei12Yd2XHFaXhzxb/Z2mw2upWc0aLwkwT5SPeu21CyTULCa0dmRZFwWU8iqOl6DDY6OumzsbqIZ5
kFJYapGrzqT26nprE0XR5JQS12V9vXuX7K+t9RtUubZ98TdDirFQ2trDZW6wW8YjiXoo7VNXar21
PPla75dgooopiCqtxZi4u7eYuQISTt7GrVFJpPRgFFFFMAooooAKKKKACjtiiigAooooAKMDGMUU
UAFFFFABRRRQAUUUUAFFFFABiiiigAooooAOvWiiigAooooAKKKKACiiigAooooA/9k=

------=_NextPart_000_0198_01CF1D94.C260E8D0--



From touch@isi.edu  Thu Jan 30 11:29:58 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46A61A044E; Thu, 30 Jan 2014 11:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dEkV6TGX2E2N; Thu, 30 Jan 2014 11:29:56 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id D67B51A0296; Thu, 30 Jan 2014 11:29:56 -0800 (PST)
Received: from [10.120.113.83] (guest-wireless-upc-nat-206-117-88-007.usc.edu [206.117.88.7]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s0UJStth025549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 Jan 2014 11:28:57 -0800 (PST)
Message-ID: <52EAA7F7.1010502@isi.edu>
Date: Thu, 30 Jan 2014 11:28:55 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Ross Callon <rcallon@juniper.net>, "Joel M. Halpern" <jmh@joelhalpern.com>, "EXT - joelja@bogus.com" <joelja@bogus.com>, "stbryant@cisco.com" <stbryant@cisco.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.com>
In-Reply-To: <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.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: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 19:29:58 -0000

I think we agree that if the router needs faster, then the router gets 
faster.

Where we disagree is whether the "bull in the china shop" gets to ignore 
the rules of the road to get what it wants.

I.e., I won't disagree on what router vendors want or what they're 
willing to support (though I will disagree on what hardware can do, 
based on experience).

I will disagree that routers get to run roughshod over the rest of us to 
do it.

Simple solution -- don't use UDP.

Joe

On 1/30/2014 10:27 AM, Ross Callon wrote:
> +1 to what Joel said. It is clear that Joe's view of "fast enough" for a host interface is not the same as my customer's view of "fast enough" for a core router (nor should it be the same -- routers have to be faster than host interfaces).
>
> More important is the issue of what can we get vendors to implement, which is probably better worded as what can we get network operators to push vendors to implement. If you are talking about fundamentally changing the internal data path for packets within a router or changing the data path into and out of specific chips to carry significantly more information, then we are talking about at least hundreds of millions and probably billions of dollars of equipment that needs to be replaced. This needs a very compelling justification before it is actually going to happen.
>
> Ross
>
> -----Original Message-----
> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of Joel M. Halpern
> Sent: Monday, January 27, 2014 2:19 PM
> To: Joe Touch; EXT - joelja@bogus.com; stbryant@cisco.com
> Cc: mpls@ietf.org; IETF discussion list
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
>
> Yes Joe, routers could ahve been built to do those calcualtions at that
> performance scale.
> There are however two major problems:
>
> 1) That is not how routers are built.
> 2) The target performance scale is rather higher.
>
> So could someone build an ASIC to do what you want?  Probably.  Is there
> any reason in the world to expect operators to pay the significant extra
> cost for such?  Not that I can see.
> And even if we could and they would, that is not the world into which we
> are deploying these tunnels.
>
> Yours,
> Joel
>
> On 1/27/14 1:53 PM, Joe Touch wrote:
>>
>>
>> On 1/27/2014 10:48 AM, joel jaeggli wrote:
>>> On 1/27/14, 8:48 AM, Joe Touch wrote:
>>>> Those same mechanisms have provided hardware checksum support for a
>>>> very long time.
>>>
>>> The new header and the payload are actually in different parts of the
>>> forwarding complex until they hit the output queue, you can't checksum
>>> data you don't have.
>>
>> You can (and some do) the checksum component parts when things go into
>> memory; the partial sums can be added as the parts are combined in the
>> output queue.
>>
>> I appreciate that we're all taking about what might be done, but the
>> reality is that there are many 'transparent TCP proxies' that have to do
>> this, so there's clearly a solution, and it clearly runs fast enough.
>>
>> Joe
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>

From jnc@mercury.lcs.mit.edu  Thu Jan 30 11:32:05 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A4651A0451; Thu, 30 Jan 2014 11:32:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XVv_hmBleDt; Thu, 30 Jan 2014 11:32:04 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1527C1A044E; Thu, 30 Jan 2014 11:32:03 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7BBD018C1C1; Thu, 30 Jan 2014 14:32:00 -0500 (EST)
To: ietf@ietf.org, mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Message-Id: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu>
Date: Thu, 30 Jan 2014 14:32:00 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 19:32:05 -0000

    > From: Joe Touch <touch@isi.edu>

    > Simple solution -- don't use UDP.

Yes, because if we use a different protocol, any potential congestion will
magically disappear!

	Noel

From prvs=01008e54e0=johnl@iecc.com  Thu Jan 30 12:18:37 2014
Return-Path: <prvs=01008e54e0=johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 726001A046E for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:18:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FosdoOQN7c0B for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:18:36 -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 F28E01A046D for <ietf@ietf.org>; Thu, 30 Jan 2014 12:18:35 -0800 (PST)
Received: (qmail 66243 invoked from network); 30 Jan 2014 20:18:29 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 30 Jan 2014 20:18:29 -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; s=52eab395.xn--30v786c.k1401; i=johnl@user.iecc.com; bh=CaXOV6QsmqJ6MkI+Fejfkti0tMwe9d1wJ8FB4fdBJxg=; b=DH3BWXyh1NR/W5YCFJbIKJA0qMkwH+f7hrWeE5PfbrwXb4kY4Zr6pS/TOlbNWtq54OzNekZ59bOGJeFkiGoqPTeO+exkO1uCexzfe2itlZnyzxdPZ/hyJ/kYHCdLmqsvyuaShxgGVAl1IRTrkSrocB6SYnR8TTP78RStMi3lV+hBYEZov8b37SCIsAbKKVzhtWtxtpA3V+eGQ1xbfJFSSFO+uPFyx6i/FLYl/C6rm6anCNwF8cUnhVAn7ajfcyPd
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; s=52eab395.xn--30v786c.k1401; olt=johnl@user.iecc.com; bh=CaXOV6QsmqJ6MkI+Fejfkti0tMwe9d1wJ8FB4fdBJxg=; b=rCBZ78+UYYTVthCRuT7ctprFl27KEdjlYx+Nx4nqasR4MlYEvG52GWDRUhQ2CYeLoocgf4OC6JRpoZyD01pFnVGx2lisf0nDiLgM+W4H1efzFtWDV+pjY7IXiyoKax4ctn1K3j1LlLao9WNX2pTTDEEdrvK2gNBphfxF7g5MReTkuOgumjg0l4Zw2PKC07OYwiSy09KWL6jQIXM17TBS4g7DB60RErqbK3lHvHDQkjhR3v3xmLk1FHKUP9hviBjf
Date: 30 Jan 2014 20:18:07 -0000
Message-ID: <20140130201807.16038.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF 89 London - Enquiry
In-Reply-To: <019701cf1d83$fed5a7d0$fc80f770$@it.bw>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: antony@it.bw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:18:37 -0000

>I confirm that as a first timer I need a mentor. May I please know the dress
>code as well. 

It's, ah, quite informal.  Tee shirts and sandals are common when the
weather is warm enough.  Wear whatever you want.

The only people who wear suits are vendor salesmen and Vint Cerf.

R's,
John

From scott.brim@gmail.com  Thu Jan 30 12:21:14 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D901A046D; Thu, 30 Jan 2014 12:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKI4IW1gk-B3; Thu, 30 Jan 2014 12:21:12 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 976B01A044E; Thu, 30 Jan 2014 12:21:12 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so4241019oah.3 for <multiple recipients>; Thu, 30 Jan 2014 12:21:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=lX84fSBDCsmb1d6Cc5ErFgVjr8He8AVteXkOmKgaEr4=; b=dy4yoH1CHUGeSiqy4bxUXkDrZItbCs18n159xckfq4j67CUxAll6cne9TbexjT5M3k mQofUY5fJyUT9bwhXe41xyHEn/dTBIpoIQLjGcs1zvt3TAvGv6iYlgG3tJ+VYbYl+p73 VTC6jw7rz8BkEofJ+SuzXyHfgUMRhlX9sHVy5rZMzCdcswdqtTxPYL9vby7nea6woIA6 shuhhZYZsAS9DI6ahxX+W0CQ1DDlG/1HUM10rpi3Q6DzDhgO6DNtFwXifO4LOMPzErmY aA8ViboiyjKWEjd26zdHxM9yC3B8NeETl/4B/G6soRgLi+shm6M/UAZlptvpUjY34XQA /Cdg==
X-Received: by 10.60.56.200 with SMTP id c8mr1922947oeq.80.1391113269117; Thu, 30 Jan 2014 12:21:09 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 30 Jan 2014 12:20:47 -0800 (PST)
In-Reply-To: <52EAA7F7.1010502@isi.edu>
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.com> <52EAA7F7.1010502@isi.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 30 Jan 2014 15:20:47 -0500
Message-ID: <CAPv4CP9JURzh44XtX5Q418ZBfcBAVctyGK6hEVjj8tp-97bs4g@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=089e015370943f8b6904f135ccb0
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:21:14 -0000

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

There are two topics that should be separate: checksums and congestion
control.

On Thu, Jan 30, 2014 at 2:28 PM, Joe Touch <touch@isi.edu> wrote:

> I think we agree that if the router needs faster, then the router gets
> faster.
>

That's in response to Ross, about checksums.


> Where we disagree is whether the "bull in the china shop" gets to ignore
> the rules of the road to get what it wants.
>

congestion


> I.e., I won't disagree on what router vendors want or what they're willing
> to support (though I will disagree on what hardware can do, based on
> experience).
>

checksums


> I will disagree that routers get to run roughshod over the rest of us to
> do it.
>
> Simple solution -- don't use UDP.


congestion.

Joe, do I understand correctly that you've conceded about checksums and now
you want to talk about congestion again?

swb

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

<div dir=3D"ltr">There are two topics that should be separate: checksums an=
d congestion control.<div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jan 30, 2014 at 2:28 PM, Joe Touch <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:touch@isi.edu" target=3D"_blank">touch@isi.edu</a>&gt;</span> w=
rote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I think we agree that if the router needs fa=
ster, then the router gets faster.<br></blockquote><div><br></div><div>That=
&#39;s in response to Ross, about checksums.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Where we disagree is whether t=
he &quot;bull in the china shop&quot; gets to ignore the rules of the road =
to get what it wants.<br>

</blockquote><div><br></div><div>congestion</div><div>=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">I.e., I won&#39;t disagree on what router vendors want o=
r what they&#39;re willing to support (though I will disagree on what hardw=
are can do, based on experience).<br>

</blockquote><div><br></div><div>checksums</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
I will disagree that routers get to run roughshod over the rest of us to do=
 it.<br>
<br>
Simple solution -- don&#39;t use UDP.</blockquote><div><br></div><div>conge=
stion.</div><div><br></div><div>Joe, do I understand correctly that you&#39=
;ve conceded about checksums and now you want to talk about congestion agai=
n?=A0</div>

<div><br></div><div>swb</div></div></div></div>

--089e015370943f8b6904f135ccb0--

From david.black@emc.com  Thu Jan 30 12:24:39 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06F4D1A044E; Thu, 30 Jan 2014 12:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YmNPA31DayuB; Thu, 30 Jan 2014 12:24:36 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4C71A03F0; Thu, 30 Jan 2014 12:24:36 -0800 (PST)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0UKOTBt031367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 30 Jan 2014 15:24:30 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s0UKOTBt031367
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1391113471; bh=WVx5XHAyyR0SQ7H1BQsduE8FabE=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=AzQw1ZHolXzXzlSPkEWUvyaTU1c2uC0964OET88zeBK2UnTda2ZUp5MyiFZdaZ0+y n14Ql1j768f2zLWUcuSwFb6k3G/SUSK97hzQ6oO/d+2Eb+srq30lewJiuDl2rcjO1/ lpVgCJ9cAC92brg+u+2oeEuDSMhWPvvnqQ8xFnz0=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s0UKOTBt031367
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd06.lss.emc.com (RSA Interceptor); Thu, 30 Jan 2014 12:24:15 -0800
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s0UKODpT009711 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 30 Jan 2014 15:24:14 -0500
Received: from mx15a.corp.emc.com ([169.254.2.218]) by mxhub34.corp.emc.com ([::1]) with mapi; Thu, 30 Jan 2014 15:24:13 -0500
From: "Black, David" <david.black@emc.com>
To: "Alexey Melnikov (alexey.melnikov@isode.com)" <alexey.melnikov@isode.com>,  "dcridland@arcode.com" <dcridland@arcode.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Thu, 30 Jan 2014 15:24:12 -0500
Subject: Gen-ART review of draft-ietf-qresync-rfc5162bis-10
Thread-Topic: Gen-ART review of draft-ietf-qresync-rfc5162bis-10
Thread-Index: Ac8d+TzKew/VpFHeS7+t6IS3cG+bfg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE71202704EC4E5@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
X-RSA-Classifications: public
Cc: "Black, David" <david.black@emc.com>, "Barry Leiba \(barryleiba@computer.org\)" <barryleiba@computer.org>, "ietf@ietf.org" <ietf@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:24:39 -0000

The -10 version of this draft addresses all of the items noted in the
Gen-ART review of the -09 version.  It's ready for publication.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Sunday, January 26, 2014 9:07 PM
> To: Alexey Melnikov (alexey.melnikov@isode.com); dcridland@arcode.com; Ge=
neral
> Area Review Team (gen-art@ietf.org)
> Cc: Black, David; Barry Leiba (barryleiba@computer.org); imapext@ietf.org=
;
> ietf@ietf.org
> Subject: Gen-ART review of draft-ietf-qresync-rfc5162bis-09
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-qresync-rfc5162bis-09
> Reviewer: David L. Black
> Review Date: January 26, 2014
> IETF LC End Date: January 27, 2014
>=20
> Summary:
> This draft is basically ready for publication, but has minor issues that
> should be fixed before publication.
>=20
> This draft consolidates RFC 4551 (IMAP Conditional STORE) and RFC 5162
> (IMAP Quick Mailbox Resynchronization) into a single document and makes
> a few minor updates.  It also updates the command line length
> recommendation in RFC 2683 to support the longer command lines that
> can occur with these extensions.
>=20
> As this is an update, I checked the diffs against RFC 4551 and RFC 5162;
> they look reasonable.  I found one minor issue that should be relatively
> easy to address.
>=20
> Minor Issues:
>=20
> The command line length change in Section 4 applies to all IMAP commands,
> and hence affects old servers, including those that don't implement eithe=
r
> of the extensions in this draft. That raises a backwards compatibility
> concern - what happens when a new client sends a > 1000 character command
> line to an old server that isn't expecting more than 1000 characters?
>=20
> One possibility would be to apply the larger length recommendation only
> after the client determines that the server supports at least one of
> these extensions.
>=20
> Nits/editorial comments:
>=20
> The update to RFC 2683 would be easier to find from the table of contents
> if the title of Section 4 were changed to "Long Command Lines (Update to
> RFC 2683)".
>=20
> idnits 2.13.01 got confused by the command line examples, and flagged a
> downref:
>=20
>   ** Downref: Normative reference to an Informational RFC: RFC 2683
>=20
> That downref appears to be ok and intended, as noted in the shepherd's
> writeup.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From touch@isi.edu  Thu Jan 30 12:30:27 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E13F21A0467; Thu, 30 Jan 2014 12:30:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQQlbbMCkwTs; Thu, 30 Jan 2014 12:30:26 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5C89D1A046D; Thu, 30 Jan 2014 12:30:26 -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 s0UKTLZH022449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 30 Jan 2014 12:29:21 -0800 (PST)
Message-ID: <52EAB621.5010403@isi.edu>
Date: Thu, 30 Jan 2014 12:29:21 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <201401240320.s0O3KsR9013700@maildrop2.v6ds.occnc.com> <52E2BBC0.2030203@isi.edu> <52E68C12.2050308@cisco.com> <98034F7E-47CF-4ABE-A199-A9DB4DACBC2E@isi.edu> <52E6AA0B.1050600@bogus.com> <52E6AB15.2080907@isi.edu> <52E6B128.8060306@joelhalpern.com> <47d85636e70c4d6f86f199a274bcdcb0@CO2PR05MB636.namprd05.prod.outlook.com> <52EAA7F7.1010502@isi.edu> <CAPv4CP9JURzh44XtX5Q418ZBfcBAVctyGK6hEVjj8tp-97bs4g@mail.gmail.com>
In-Reply-To: <CAPv4CP9JURzh44XtX5Q418ZBfcBAVctyGK6hEVjj8tp-97bs4g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "mpls@ietf.org" <mpls@ietf.org>, IETF discussion list <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:30:28 -0000

On 1/30/2014 12:20 PM, Scott Brim wrote:
> There are two topics that should be separate: checksums and congestion
> control.

Agreed.

> On Thu, Jan 30, 2014 at 2:28 PM, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>
>     I think we agree that if the router needs faster, then the router
>     gets faster.
>
> That's in response to Ross, about checksums.

Also about the complaint that routers run to fast to run any sort of 
congestion algorithm, including circuit breakers (which is clearly false).

>     Where we disagree is whether the "bull in the china shop" gets to
>     ignore the rules of the road to get what it wants.
>
> congestion

Yes, in the sense that incorrect checksums should be checked at the 
egress only anyway, and thus ignoring them would only impact the network 
after the egress.

No, in the sense that anything that peeks inside a UDP header has the 
right to want to check whether that data is uncorrupted - that includes 
things like NATs.

>     I.e., I won't disagree on what router vendors want or what they're
>     willing to support (though I will disagree on what hardware can do,
>     based on experience).
>
> checksums

Both, as per above.

>     I will disagree that routers get to run roughshod over the rest of
>     us to do it.
>
>     Simple solution -- don't use UDP.
>
> congestion.

Both. If you want the benefits of UDP, pay the penalty. If you don't 
want the penalty, don't use UDP.

I don't buy the claims that there's a need here to eat cake and have it too.

> Joe, do I understand correctly that you've conceded about checksums and
> now you want to talk about congestion again?

I'm talking about the overall argument, which has circled back to "we 
need to do what vendors are willing to do", rather than "vendors need to 
play nice in the Internet that they're making money off of".

Joe

From grmocg@gmail.com  Thu Jan 30 12:39:37 2014
Return-Path: <grmocg@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBB791A046D for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:39:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ltv0aCtl_nAj for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:39:36 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3E01A0475 for <ietf@ietf.org>; Thu, 30 Jan 2014 12:39:36 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp4so4083831obc.30 for <ietf@ietf.org>; Thu, 30 Jan 2014 12:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gDfJcKY1mFSzB6HEV4DSZFS6jpidjtdlPvNLAAo4JV8=; b=WWuQ1VpEUBb4trK8AmeRmib9mV+NE5Kg6Ht3W/Tlt/iMwoUuLPrYhjpGaG6KmtpTQq cCEpW+0/wzxyQU6aVcYlTJ+98sZrCZew625AzUxbDILu8rHF8trBu0qNWsXqqyjcSwxE zBnHYQl5cLzKfi2n8gb8vo4fxUXD59OaVnBAElZfCjWp8oA9XcGGYZhRB35Kvp7NH07n C9pkD8X4V1/ODH+pByXqj0VIZi9D1QTfUPSOYvfWmyaBQpQfaEpdHmCrcejehma8K+WV RE7rox/KjTMFytqJsbMynKnVeBGAsCj54AfXYiGOu/cvdvGXZuwwSihqJymuMB783YQ5 kAwA==
MIME-Version: 1.0
X-Received: by 10.60.45.105 with SMTP id l9mr2886350oem.53.1391114372680; Thu, 30 Jan 2014 12:39:32 -0800 (PST)
Received: by 10.76.100.103 with HTTP; Thu, 30 Jan 2014 12:39:32 -0800 (PST)
In-Reply-To: <20140130201807.16038.qmail@joyce.lan>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan>
Date: Thu, 30 Jan 2014 12:39:32 -0800
Message-ID: <CAP+FsNfF2vN=4TT8idkKxSpVxdMBFwxPVOL1FFpA2gddrPZUVQ@mail.gmail.com>
Subject: Re: IETF 89 London - Enquiry
From: Roberto Peon <grmocg@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e0149ce3c06900d04f1360edf
Cc: antony@it.bw, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:39:38 -0000

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

Almost true.
.. almost.

-=R


On Thu, Jan 30, 2014 at 12:18 PM, John Levine <johnl@taugh.com> wrote:

>
> >I confirm that as a first timer I need a mentor. May I please know the
> dress
> >code as well.
>
> It's, ah, quite informal.  Tee shirts and sandals are common when the
> weather is warm enough.  Wear whatever you want.
>
> The only people who wear suits are vendor salesmen and Vint Cerf.
>
> R's,
> John
>

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

<div dir=3D"ltr">Almost true.<div>.. almost.</div><div><br></div><div>-=3DR=
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Thu, Jan 30, 2014 at 12:18 PM, John Levine <span dir=3D"ltr">&lt;<a href=
=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.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"><br>
&gt;I confirm that as a first timer I need a mentor. May I please know the =
dress<br>
&gt;code as well.<br>
<br>
</div>It&#39;s, ah, quite informal. =A0Tee shirts and sandals are common wh=
en the<br>
weather is warm enough. =A0Wear whatever you want.<br>
<br>
The only people who wear suits are vendor salesmen and Vint Cerf.<br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br></div>

--089e0149ce3c06900d04f1360edf--

From scott.brim@gmail.com  Thu Jan 30 12:55:28 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EEE1A04CC for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4257N4YzV22r for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 12:55:27 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 48CF91A046E for <ietf@ietf.org>; Thu, 30 Jan 2014 12:55:27 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id wp4so4110758obc.16 for <ietf@ietf.org>; Thu, 30 Jan 2014 12:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vrYP2YWABWyTyUCPRZd4p0ffPjdo5hQ6SkbTVNauZqs=; b=FQ1wIroBkRv43UGtxHUPGB00tUC3oMkVMDQ5r6mviJb8yVoNGeInBT8gm+Xfh+LDWl GgBgpjYnGet/Y3dAe9qeunioIHlLKwJXfMFPCMD26dapA4WdeW9ANej77wcj90phmbsQ +qrg0eraNzWWSoXJQ5IOFYmiiZmjRfVZoQ/hfQP4e9rnZhWeLl5s8CZadMCI/zb+kh0y vawQG/wy4+dNuGipkNVsR2eK41lnqwDoIuaELSwnXHUmlY2b6+zHqK/Z6O+npVm69ajN vmKbYE5kFThMnH7HbKvsaGW/jKI36/02ztGQaZ9PPWY/8ODOlzKGtrQKSyW0aFQkqdv0 cVzA==
X-Received: by 10.60.165.72 with SMTP id yw8mr2180406oeb.71.1391115323890; Thu, 30 Jan 2014 12:55:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Thu, 30 Jan 2014 12:55:03 -0800 (PST)
In-Reply-To: <20140130201807.16038.qmail@joyce.lan>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 30 Jan 2014 15:55:03 -0500
Message-ID: <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com>
Subject: Re: IETF 89 London - Enquiry
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=047d7b41904bb8e38604f136463b
Cc: antony@it.bw, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 20:55:28 -0000

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

On Thu, Jan 30, 2014 at 3:18 PM, John Levine <johnl@taugh.com> wrote:

> The only people who wear suits are vendor salesmen and Vint Cerf.
>

and Bob Moskowitz.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jan 30, 2014 at 3:18 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">

<div class=3D"im"><span style=3D"color:rgb(34,34,34)">The only people who w=
ear suits are vendor salesmen and Vint Cerf.</span></div></blockquote><div>=
<br></div><div>and Bob Moskowitz.=A0</div></div></div></div>

--047d7b41904bb8e38604f136463b--

From alissa@cooperw.in  Thu Jan 30 13:17:38 2014
Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38DE01A04FC for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 13:17:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kiSkAITQLO1s for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 13:17:35 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by ietfa.amsl.com (Postfix) with ESMTP id C0D2E1A04F1 for <ietf@ietf.org>; Thu, 30 Jan 2014 13:17:35 -0800 (PST)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 2D84020ACB; Thu, 30 Jan 2014 16:17:30 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 30 Jan 2014 16:17:30 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=date :subject:from:to:cc:message-id:references:in-reply-to :mime-version:content-type:content-transfer-encoding; s=mesmtp; bh=YfEtOtEvr5wL5TWnpUpjApR/Q1o=; b=PuK1srmXJ9xoAD6978sSAgKoBLS/ uPZO4o9Ygro+0CDmiinu9qqhyxUm3NB/u9XHWppAUOQUTRUqOZ8BFyFzqDAc75F8 CjChbiVHmbVE2n+jxXlfP8Bsswu8HHvg5TckfI0CWQcn0PHYOAv0N+dM58pQrB18 AGUHqi+9U7vEPRw=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:subject:from:to:cc:message-id :references:in-reply-to:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=YfEtOtEvr5wL5TWnpUpjAp R/Q1o=; b=aBYmx3jtXTQnmSHvtxN1JLTyU6Xlf8sdoIj29upnThpzzGRVHznBO7 6G3C+zj9Xtf5ZbGEIdGhyrGTniF2o3VKVQi9VY8d4LCsFmScA4Ie/eZlzLG99QeP GOpOaB6ztP08niS1zILeKOWM6O1yPOFfEa6x4VJnnfSO5/pNa6F+0=
X-Sasl-enc: JxD+35BWv/jtbpJgCJS+Z+bs1/7mvVI7oZGKLWjlGVka 1391116649
Received: from [171.68.18.48] (unknown [171.68.18.48]) by mail.messagingengine.com (Postfix) with ESMTPA id CC22C680377; Thu, 30 Jan 2014 16:17:28 -0500 (EST)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Thu, 30 Jan 2014 13:17:25 -0800
Subject: Re: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
From: Alissa Cooper <alissa@cooperw.in>
To: Alessandro Vesely <vesely@tana.it>, IAB <iab@iab.org>
Message-ID: <CF100132.F260%alissa@cooperw.in>
Thread-Topic: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org> <52EA9F85.6080804@tana.it>
In-Reply-To: <52EA9F85.6080804@tana.it>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 21:17:38 -0000

Hi Alessandro,

Thanks for your comments. I have one question below.

On 1/30/14 10:52 AM, "Alessandro Vesely" <vesely@tana.it> wrote:

>On Wed 29/Jan/2014 17:16:56 +0100 IAB Chair wrote:
>> This is a call for review of "Technical Considerations for Internet
>> Service Blocking and Filtering" prior to potential approval as an
>> IAB stream RFC.
>> 
>> The document is available for inspection here:
>> https://datatracker.ietf.org/doc/draft-iab-filtering-considerations/
>
>Albeit it purports to keep clear of (un)ethical considerations, the
>document seems to be oriented toward government-imposed restrictions,
>recounting how it would be better to move filtering to collaborative
>endpoints rather than disrupting Internet operation, since bad actors
>can circumvent filtering anyway.  I fully agree, but I think that a
>general purpose document on this subject might have touched on such
>points as password management, user identification, and outbound port

Could you expand a bit about what you feel is missing as regards to
password management and user identification?

Thanks,
Alissa


>25 blocking.
>
>Some minor comments, in top-down order:
>
>1. *Introduction*, par 3
>
>                          As noted in [RFC4084], some Internet service
>   providers impose restrictions on which applications their customers
>   may use and which traffic they allow on their networks.
>
>To avoid confusion, I'd s/impose restrictions/perform filtering/,
>since RFC 4084 says about Firewalled Internet Connectivity:
>
>                  It is distinguished from the models above by the
>   fact that any filtering or blocking services are ultimately
>   performed at customer request, rather than being imposed as
>   service restrictions.
>
>Alternatively, that snippet could refer to "Section 3 of [RFC4084]".
>
>
>2. *Filtering Examples*, par 3 (Web Filtering)
>
>The second half of that paragraph is rather lengthy and obscure --the
>explanation in Section 5 is much clearer.  It could be shortened for
>readability, for example:
>
>OLD:
>   To block access to content made accessible via HTTPS, filtering
>   systems thus must either block based on network- and
>   transport-layer headers (IP address and/or port), or else obtain a
>   trust anchor certificate that is trusted by endpoints (and thus act
>   as a man in the middle).  These filtering systems often take the
>   form of "portals" or "enterprise proxies."  These portals present
>   their own HTTPS certificates that are invalid for any given domain
>   according to normal validation rules, but may still be trusted if
>   the user installs a security exception.  (See further discussion in
>   Section 5.)
>
>NEW:
>   To block access to content made accessible via HTTPS, filtering
>   systems thus must either block based on network- and
>   transport-layer headers (IP address and/or port), or act as a man
>   in the middle by requiring the user to install security exceptions.
>   The latter filtering systems often take the form of "portals" or
>   "enterprise proxies", presenting their own, dynamically generated
>   HTTPS certificates.  (See further discussion in Section 5.)
>
>
>3.1. *Entities that set blocking policies*
>
>   Parties that institute blocking policies include governments,
>   enterprises, network operators, application providers, and
>   individual end users.
>
>Which of those terms includes Spamhaus?  I'd propose to add
>"reputation trackers".
>
>
>3.4. *Components used for blocking*, par 1
>
>   Broadly speaking, the process of a delivering an Internet service
>   involves three different components:
>
>s/a delivering/delivering/
>
>
>4.3.5. *Examples*, par 3
>
>s/e-mail/email/
>
>
>6. *Conclusion*
>
>s/Because it least/Because it is least/
>
>Ale



From chelliot@gmail.com  Thu Jan 30 13:18:37 2014
Return-Path: <chelliot@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F16811A04FD for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 13:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIWRrVQJ-pwQ for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 13:18:35 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8855C1A04F8 for <ietf@ietf.org>; Thu, 30 Jan 2014 13:18:35 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id q8so3036455lbi.0 for <ietf@ietf.org>; Thu, 30 Jan 2014 13:18:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=UnH1JM8AG/nvC75kWzmIOm293UObwuY74F1slXcol6w=; b=O+6pqcQV+wTCK+4JtxL9Z7uSCjs6stAHv2n3W2LsrGsa2mbBAYCpLWmQJUiQGuOLl2 R67ZOMxc2aSnggrNQT4/ouLpfkeIEELLjGH0DzvJornKcpdOCgcZFg7l4eTvp89c+qBq yii5Rekon3WN5JyCfL4NZNLARMiAPNjBfDwowgCF2PcNw0q31gt4MvllDy8EEQXhzDbM rhz4dR5wcvUCRgSPsaR22X17EZa6Jlka5qcxNgNaMPVTXEKw3B/QHJ4RGOkeP0jmiOs0 jKL8Tgwft9nnRYD5ItFAsJyQg+lNLKnVfpBTYmXq4W0ZYRbvLomWI73byLM4E8kYs0cA tpvg==
MIME-Version: 1.0
X-Received: by 10.112.180.72 with SMTP id dm8mr7406056lbc.28.1391116711490; Thu, 30 Jan 2014 13:18:31 -0800 (PST)
Sender: chelliot@gmail.com
Received: by 10.114.65.11 with HTTP; Thu, 30 Jan 2014 13:18:31 -0800 (PST)
In-Reply-To: <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com>
Date: Thu, 30 Jan 2014 16:18:31 -0500
X-Google-Sender-Auth: dGWPkpPI7jHJmAKyTAeSm45DNmU
Message-ID: <CAO_Rpc+m0menyb7_SBvnptQx=PaP2EU_dz_h9bHZ4B=Lqed+2w@mail.gmail.com>
Subject: Re: IETF 89 London - Enquiry
From: Chris Elliott <chelliot@pobox.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=089e011836be6df8b304f13699e4
Cc: "antony@it.bw" <antony@it.bw>, John Levine <johnl@taugh.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chelliot@pobox.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 21:18:37 -0000

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

On Thursday, January 30, 2014, Scott Brim <scott.brim@gmail.com> wrote:

> On Thu, Jan 30, 2014 at 3:18 PM, John Levine <johnl@taugh.com<javascript:_e(%7B%7D,'cvml','johnl@taugh.com');>
> > wrote:
>
>> The only people who wear suits are vendor salesmen and Vint Cerf.
>>
>
> and Bob Moskowitz.
>

And Henrik Levkowetz!


-- 
Chris Elliott
chelliot@pobox.com

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

<br><br>On Thursday, January 30, 2014, Scott Brim &lt;<a href=3D"mailto:sco=
tt.brim@gmail.com">scott.brim@gmail.com</a>&gt; wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jan 30, 2014 at 3:18 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"j=
avascript:_e(%7B%7D,&#39;cvml&#39;,&#39;johnl@taugh.com&#39;);" target=3D"_=
blank">johnl@taugh.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><span style=3D"color:rgb(34,34,34)">The only people who wear suits are=
 vendor salesmen and Vint Cerf.</span></div></blockquote><div><br></div><di=
v>and Bob Moskowitz.=A0</div></div></div></div></blockquote><div><br></div>
<div>And Henrik Levkowetz!<span></span>=A0</div><br><br>-- <br>Chris Elliot=
t<br><a href=3D"mailto:chelliot@pobox.com">chelliot@pobox.com</a><br><br>

--089e011836be6df8b304f13699e4--

From gdaley@au.logicalis.com  Thu Jan 30 14:45:03 2014
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95611A04DD; Thu, 30 Jan 2014 14:45:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.442
X-Spam-Level: 
X-Spam-Status: No, score=-1.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iRSOL6yHGQeQ; Thu, 30 Jan 2014 14:45:01 -0800 (PST)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id 44D5C1A04DA; Thu, 30 Jan 2014 14:45:00 -0800 (PST)
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([203.8.7.161]) by smtp2.au.logicalis.com with ESMTP; 31 Jan 2014 09:44:57 +1100
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([fe80::68b7:8880:fefb:f742%12]) with mapi id 14.02.0347.000; Fri, 31 Jan 2014 09:44:54 +1100
From: Greg Daley <gdaley@au.logicalis.com>
To: 'Noel Chiappa' <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>,  "mpls@ietf.org" <mpls@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPHfHxZzPPQlRcgk6ua2U45NfiYJqd1tSw
Date: Thu, 30 Jan 2014 22:44:54 +0000
Message-ID: <72381AF1F18BAE4F890A0813768D992817FDAB19@sdcexchms.au.logicalis.com>
References: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu>
In-Reply-To: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.196.186]
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 22:45:03 -0000

>     > From: Joe Touch <touch@isi.edu>
>=20
>     > Simple solution -- don't use UDP.
>=20
> Yes, because if we use a different protocol, any potential congestion wil=
l
> magically disappear!

Isn't that protocol called DCCP? (per RFC 4340 and 5348)

It would be interesting and potentially feasible to outline MPLS over DCCP =
(given a solid use case), but it would be one of the few (9) named applicat=
ion bindings for this protocol today:

http://www.iana.org/assignments/service-names-port-numbers/service-names-po=
rt-numbers.txt

Of course, in order to get the protocols to pass legacy firewall inspection=
, UDP encapsulation may be required, and companies would have to actually i=
mplement the protocol...

Greg Daley
gdaley@au.logicalis.com

From spencerdawkins.ietf@gmail.com  Thu Jan 30 15:30:39 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 994E31A0513 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 15:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gIGssuYnZUJ for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 15:30:38 -0800 (PST)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 64E6B1A04F4 for <ietf@ietf.org>; Thu, 30 Jan 2014 15:30:38 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so4236504obb.7 for <ietf@ietf.org>; Thu, 30 Jan 2014 15:30:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; bh=Dyo8c0up66E/epTdfTMXbeFBqxcN2SiC1kTex8bv5zM=; b=qjQ00AJJtjNWL8/W37+mssaKYin1xI5sJuXB3bymzUJOhFH+8VMtBCdxWBhiqCD0Tr 40enZcTYvA8IMwxfFjFFmEU0RnmjZ6HpVvZDMihBREKXAMfnlI8ldPawXGXvUbIxjz72 W6bMbikHSy9Nb3xqFIIZlF+4Msbojw9t+1uEzWD7t8aUnjsDEH8R6beF5CvcfsE5Tl0t 89Iu7YmyoSI3KLAp4X7IdSFCCnvWc8oMiD1yAJ0caPtOrfMWzwACDdzXvCXmVRtX/74X ouRd55+BeCWl9Pi0nCPA5waoIyZbzNdteySB/ZtTUnwpGyvPVLMcaoZdrzc+E+WAtGHD 7gVQ==
X-Received: by 10.182.43.161 with SMTP id x1mr13652601obl.5.1391124634922; Thu, 30 Jan 2014 15:30:34 -0800 (PST)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id o6sm44729089oel.4.2014.01.30.15.30.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 30 Jan 2014 15:30:34 -0800 (PST)
Message-ID: <52EAE098.20302@gmail.com>
Date: Thu, 30 Jan 2014 17:30:32 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: chelliot@pobox.com, Scott Brim <scott.brim@gmail.com>
Subject: Re: IETF 89 London - Enquiry
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com> <CAO_Rpc+m0menyb7_SBvnptQx=PaP2EU_dz_h9bHZ4B=Lqed+2w@mail.gmail.com>
In-Reply-To: <CAO_Rpc+m0menyb7_SBvnptQx=PaP2EU_dz_h9bHZ4B=Lqed+2w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------050705070203060309010307"
Cc: "antony@it.bw" <antony@it.bw>, John Levine <johnl@taugh.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jan 2014 23:30:39 -0000

This is a multi-part message in MIME format.
--------------050705070203060309010307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


On 01/30/2014 03:18 PM, Chris Elliott wrote:
>
>
> On Thursday, January 30, 2014, Scott Brim <scott.brim@gmail.com 
> <mailto:scott.brim@gmail.com>> wrote:
>
>     On Thu, Jan 30, 2014 at 3:18 PM, John Levine <johnl@taugh.com
>     <javascript:_e(%7B%7D,'cvml','johnl@taugh.com');>> wrote:
>
>         The only people who wear suits are vendor salesmen and Vint Cerf.
>
>
>     and Bob Moskowitz.
>
>
> And Henrik Levkowetz!

I THINK he wears suits, but almost every time I've seen Henrik at an 
IETF meeting, he was wearing a vest, like he'd left his jacket someplace 
because he was hands-on working ...

Spencer

--------------050705070203060309010307
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-cite-prefix">On 01/30/2014 03:18 PM, Chris Elliott
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAO_Rpc+m0menyb7_SBvnptQx=PaP2EU_dz_h9bHZ4B=Lqed+2w@mail.gmail.com"
      type="cite"><br>
      <br>
      On Thursday, January 30, 2014, Scott Brim &lt;<a
        moz-do-not-send="true" href="mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&gt;
      wrote:<br>
      <blockquote class="gmail_quote" style="margin:0 0 0
        .8ex;border-left:1px #ccc solid;padding-left:1ex">
        <div dir="ltr">
          <div class="gmail_extra">
            <div class="gmail_quote">On Thu, Jan 30, 2014 at 3:18 PM,
              John Levine <span dir="ltr">&lt;<a moz-do-not-send="true"
                  href="javascript:_e(%7B%7D,'cvml','johnl@taugh.com');"
                  target="_blank">johnl@taugh.com</a>&gt;</span> wrote:<br>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                <div><span style="color:rgb(34,34,34)">The only people
                    who wear suits are vendor salesmen and Vint Cerf.</span></div>
              </blockquote>
              <div><br>
              </div>
              <div>and Bob Moskowitz.&nbsp;</div>
            </div>
          </div>
        </div>
      </blockquote>
      <div><br>
      </div>
      <div>And Henrik Levkowetz!<span></span><br>
      </div>
    </blockquote>
    <br>
    I THINK he wears suits, but almost every time I've seen Henrik at an
    IETF meeting, he was wearing a vest, like he'd left his jacket
    someplace because he was hands-on working ...<br>
    <br>
    Spencer<br>
  </body>
</html>

--------------050705070203060309010307--

From geoff.ietf@mulligan.com  Thu Jan 30 19:39:34 2014
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3DD51A0528 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 19:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lzdh3kqZY5fa for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 19:39:33 -0800 (PST)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 247291A0526 for <ietf@ietf.org>; Thu, 30 Jan 2014 19:39:32 -0800 (PST)
Received: from [192.168.1.3] (pool-96-255-136-243.washdc.fios.verizon.net [96.255.136.243]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id B996F241D0 for <ietf@ietf.org>; Thu, 30 Jan 2014 20:39:22 -0700 (MST)
Message-ID: <52EB1AF0.2000506@mulligan.com>
Date: Thu, 30 Jan 2014 20:39:28 -0700
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 89 London - Enquiry
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com>
In-Reply-To: <CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------000902040903090508050308"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 03:39:34 -0000

This is a multi-part message in MIME format.
--------------000902040903090508050308
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hey, I wore a suit to the last IETF. I've been accused of being a 
salesman, but never a vendor.

         Geoff

On 01/30/2014 01:55 PM, Scott Brim wrote:
> On Thu, Jan 30, 2014 at 3:18 PM, John Levine <johnl@taugh.com 
> <mailto:johnl@taugh.com>> wrote:
>
>     The only people who wear suits are vendor salesmen and Vint Cerf.
>
>
> and Bob Moskowitz.


--------------000902040903090508050308
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hey, I wore a suit to the last IETF. I've been accused of being a
    salesman, but never a vendor.<br>
    <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; Geoff<br>
    <br>
    <div class="moz-cite-prefix">On 01/30/2014 01:55 PM, Scott Brim
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAPv4CP-k-iZ3aBCJZ_LA=AJpu_ZsC09SSviDUvfXw73kh5cJ8A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">On Thu, Jan 30, 2014 at 3:18 PM, John
            Levine <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:johnl@taugh.com" target="_blank">johnl@taugh.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="im"><span style="color:rgb(34,34,34)">The only
                  people who wear suits are vendor salesmen and Vint
                  Cerf.</span></div>
            </blockquote>
            <div><br>
            </div>
            <div>and Bob Moskowitz.&nbsp;</div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------000902040903090508050308--

From narten@us.ibm.com  Thu Jan 30 21:53:12 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6F9A1A0551 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 21:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.637
X-Spam-Level: 
X-Spam-Status: No, score=-4.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, TO_IN_SUBJ=2.799] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZlJYzfY0CO2 for <ietf@ietfa.amsl.com>; Thu, 30 Jan 2014 21:53:10 -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 9A6AB1A0543 for <ietf@ietf.org>; Thu, 30 Jan 2014 21:53:10 -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>; Fri, 31 Jan 2014 00:53:06 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 31 Jan 2014 00:53:03 -0500
Received: from b01cxnp22034.gho.pok.ibm.com (b01cxnp22034.gho.pok.ibm.com [9.57.198.24]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 7B0EDC90026 for <ietf@ietf.org>; Fri, 31 Jan 2014 00:53:00 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s0V5r3QD8126872 for <ietf@ietf.org>; Fri, 31 Jan 2014 05:53:03 GMT
Received: from d01av01.pok.ibm.com (localhost [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s0V5r2pk027138 for <ietf@ietf.org>; Fri, 31 Jan 2014 00:53:02 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s0V5r2g5027114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 31 Jan 2014 00:53:02 -0500
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s0V5r163017888 for <ietf@ietf.org>; Fri, 31 Jan 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s0V5r1J1017837 for ietf@ietf.org; Fri, 31 Jan 2014 00:53:01 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201401310553.s0V5r1J1017837@rotala.raleigh.ibm.com>
Date: Fri, 31 Jan 2014 00:53:01 -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-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14013105-7182-0000-0000-000009B7F300
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 05:53:13 -0000

Total of 121 messages in the last 7 days.
 
script run at: Fri Jan 31 00:53:01 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  6.61% |    8 |  7.82% |    92436 | spencerdawkins.ietf@gmail.com
  6.61% |    8 |  6.47% |    76473 | touch@isi.edu
  4.13% |    5 |  4.50% |    53193 | scott.brim@gmail.com
  4.13% |    5 |  3.84% |    45402 | curtis@ipv6.occnc.com
  2.48% |    3 |  4.99% |    59054 | adrian@olddog.co.uk
  4.13% |    5 |  2.59% |    30673 | dhc@dcrocker.net
  2.48% |    3 |  3.10% |    36600 | keith.drage@alcatel-lucent.com
  3.31% |    4 |  1.92% |    22664 | chair@ietf.org
  2.48% |    3 |  2.72% |    32164 | abdussalambaryun@gmail.com
  2.48% |    3 |  2.21% |    26128 | geoff.mulligan@nist.gov
  0.83% |    1 |  3.71% |    43923 | antony@it.bw
  2.48% |    3 |  2.05% |    24223 | brian.e.carpenter@gmail.com
  2.48% |    3 |  1.95% |    23054 | john-ietf@jck.com
  2.48% |    3 |  1.94% |    22883 | presnick@qti.qualcomm.com
  2.48% |    3 |  1.77% |    20964 | ned+ietf@mauve.mrochek.com
  1.65% |    2 |  2.07% |    24510 | bclaise@cisco.com
  1.65% |    2 |  2.03% |    24025 | david.black@emc.com
  1.65% |    2 |  1.65% |    19540 | hsantos@isdg.net
  1.65% |    2 |  1.60% |    18868 | kre@munnari.oz.au
  1.65% |    2 |  1.40% |    16569 | alexey.melnikov@isode.com
  1.65% |    2 |  1.34% |    15892 | fluffy@cisco.com
  1.65% |    2 |  1.33% |    15691 | l.wood@surrey.ac.uk
  1.65% |    2 |  1.32% |    15616 | lars@netapp.com
  1.65% |    2 |  1.30% |    15423 | narten@us.ibm.com
  1.65% |    2 |  1.19% |    14127 | stephen.farrell@cs.tcd.ie
  1.65% |    2 |  1.18% |    13902 | gdaley@au.logicalis.com
  1.65% |    2 |  1.15% |    13633 | lear@cisco.com
  1.65% |    2 |  1.13% |    13393 | iab-chair@iab.org
  0.83% |    1 |  1.78% |    21045 | trammell@tik.ee.ethz.ch
  0.83% |    1 |  1.51% |    17842 | hallam@gmail.com
  0.83% |    1 |  1.51% |    17804 | coppens.ndayiragije@yahoo.com
  0.83% |    1 |  1.42% |    16831 | warren@kumari.net
  0.83% |    1 |  1.30% |    15384 | daedulus@btconnect.com
  0.83% |    1 |  1.23% |    14490 | edc@google.com
  0.83% |    1 |  1.18% |    14007 | synp71@live.com
  0.83% |    1 |  1.16% |    13665 | d3e3e3@gmail.com
  0.83% |    1 |  1.12% |    13281 | chris.dearlove@baesystems.com
  0.83% |    1 |  1.11% |    13153 | rlb@ipv.sx
  0.83% |    1 |  0.94% |    11129 | rcallon@juniper.net
  0.83% |    1 |  0.93% |    10972 | farmer@umn.edu
  0.83% |    1 |  0.88% |    10399 | mstjohns@comcast.net
  0.83% |    1 |  0.88% |    10384 | gtw@gtwassociates.com
  0.83% |    1 |  0.82% |     9743 | alissa@cooperw.in
  0.83% |    1 |  0.78% |     9242 | dave@cridland.net
  0.83% |    1 |  0.78% |     9180 | housley@vigilsec.com
  0.83% |    1 |  0.75% |     8842 | vesely@tana.it
  0.83% |    1 |  0.71% |     8444 | joelja@bogus.com
  0.83% |    1 |  0.68% |     7992 | fred@cisco.com
  0.83% |    1 |  0.67% |     7976 | mark.tinka@seacom.mu
  0.83% |    1 |  0.65% |     7733 | wesley.george@twcable.com
  0.83% |    1 |  0.63% |     7454 | john@jlc.net
  0.83% |    1 |  0.61% |     7196 | chelliot@pobox.com
  0.83% |    1 |  0.58% |     6806 | grmocg@gmail.com
  0.83% |    1 |  0.57% |     6736 | wood@isoc.org
  0.83% |    1 |  0.57% |     6723 | geoff.ietf@mulligan.com
  0.83% |    1 |  0.56% |     6649 | jmh@joelhalpern.com
  0.83% |    1 |  0.56% |     6601 | dwm@xpasc.com
  0.83% |    1 |  0.52% |     6148 | worley@ariadne.com
  0.83% |    1 |  0.52% |     6147 | barryleiba@computer.org
  0.83% |    1 |  0.49% |     5819 | johnl@taugh.com
  0.83% |    1 |  0.48% |     5701 | jari.arkko@piuha.net
  0.83% |    1 |  0.47% |     5539 | steve@shinkuro.com
  0.83% |    1 |  0.37% |     4323 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |  121 |100.00% |  1182403 | Total


From daedulus@btconnect.com  Fri Jan 31 01:45:30 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C541A041B for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 01:45:30 -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=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oA3INVa_JIIN for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 01:45:28 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe001.messaging.microsoft.com [216.32.180.184]) by ietfa.amsl.com (Postfix) with ESMTP id C3FA61A0388 for <ietf@ietf.org>; Fri, 31 Jan 2014 01:45:28 -0800 (PST)
Received: from mail42-co1-R.bigfish.com (10.243.78.230) by CO1EHSOBE035.bigfish.com (10.243.66.100) with Microsoft SMTP Server id 14.1.225.22; Fri, 31 Jan 2014 09:45:24 +0000
Received: from mail42-co1 (localhost [127.0.0.1])	by mail42-co1-R.bigfish.com (Postfix) with ESMTP id 38B1F40053E; Fri, 31 Jan 2014 09:45:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT004.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -15
X-BigFish: PS-15(zz98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL8275bh8275dh1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24ach24d7h2516h304l1d11m1155h)
Received: from mail42-co1 (localhost.localdomain [127.0.0.1]) by mail42-co1 (MessageSwitch) id 1391161522348357_2973; Fri, 31 Jan 2014 09:45:22 +0000 (UTC)
Received: from CO1EHSMHS005.bigfish.com (unknown [10.243.78.232])	by mail42-co1.bigfish.com (Postfix) with ESMTP id 4B63180048;	Fri, 31 Jan 2014 09:45:22 +0000 (UTC)
Received: from DB3PRD0710HT004.eurprd07.prod.outlook.com (157.56.253.85) by CO1EHSMHS005.bigfish.com (10.243.66.15) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 31 Jan 2014 09:45:20 +0000
Received: from pc6 (81.159.188.189) by pod51017.outlook.com (10.255.75.39) with Microsoft SMTP Server (TLS) id 14.16.411.0; Fri, 31 Jan 2014 09:45:07 +0000
Message-ID: <005201cf1e68$817cb720$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Scott Brim <scott.brim@gmail.com>
References: <52E80FA9.5020704@gmail.com><52E83926.1060909@gmail.com><52E9222C.4060601@gmail.com><04fa01cf1dc5$48731c60$4001a8c0@gateway.2wire.net> <CAPv4CP8G9hNGZWwEHxDVnNo7AtXs6kuZmnPCh5dCaO9H_+i=Vw@mail.gmail.com>
Subject: Re: When is an idea a good idea?
Date: Fri, 31 Jan 2014 09:40:34 +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: [81.159.188.189]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 09:45:30 -0000

----- Original Message -----
From: "Scott Brim" <scott.brim@gmail.com>
To: "t. p." <daedulus@btconnect.com>
Cc: "IETF discussion list" <ietf@ietf.org>; "Spencer Dawkins"
<spencerdawkins.ietf@gmail.com>
Sent: Thursday, January 30, 2014 3:16 PM

> Tom: but MPLS could be used anywhere. It isn't designed in a way that
using
> it would be dangerous.

Mmmm ... let me see

Congestion control - nil
Security - nil
Management - not much until the recent ITU-T inspired effort.

Yup, let it rip on the open Internet, no dangers there. I am sure the
IESG would agree:-)

Tom Petch

>
> Fred: but there will always be environments that would benefit from
special
> optimizations, such as cellular or satellite or high-performance
computing.
> It's reasonable for us to standardize for the special needs of those
> environments too - they need interoperability and they use IP.
>
> Scott
> On Jan 30, 2014 9:17 AM, "t.p." <daedulus@btconnect.com> wrote:
>
> > ----- Original Message -----
> > From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
> > To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> > Cc: "IETF discussion list" <ietf@ietf.org>
> > Sent: Wednesday, January 29, 2014 3:45 PM
> > > I'm replying to Brian and to Scott here ...
> > >



From stbryant@cisco.com  Fri Jan 31 02:51:03 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA4A1A058B; Fri, 31 Jan 2014 02:51:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id odH1GPIMrj2I; Fri, 31 Jan 2014 02:51:01 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 72D3C1A058A; Fri, 31 Jan 2014 02:51:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=297; q=dns/txt; s=iport; t=1391165458; x=1392375058; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=WLw1m40bAC4ADWAux+tfJOfXLMXnpv01Y7nByMDXTVs=; b=NNMLL+H7waam64l/J6PltDoG3LcnJoNtMhpn1x0ODr7Uf2ac5LrcIYA0 zZGwJ/2YRJ98jl+GnlJVYPdXPmkjvAz5uYwM4vkRDVN9rqNyJr7YFbvY+ F9/xPilQuqSdkRcKzDMcxuHqTspuvy1hxC7WXW8fgexP+wXsQKYa/rNKG s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFABZ/61KQ/khM/2dsb2JhbABZDoJ+vkWBBRZ0giUBAQEEOEARCw4KCRYECwkDAgECAUUGAQwGAgEBiAHNBBePCYQ4AQOUQoNohkiLWYFvfz8
X-IronPort-AV: E=Sophos;i="4.95,757,1384300800";  d="scan'208";a="4468290"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 31 Jan 2014 10:50:57 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s0VAouVv014647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 10:50:56 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s0VAosI7009570; Fri, 31 Jan 2014 10:50:55 GMT
Message-ID: <52EB800E.2090102@cisco.com>
Date: Fri, 31 Jan 2014 10:50:54 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Greg Daley <gdaley@au.logicalis.com>, "'Noel Chiappa'" <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
References: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu> <72381AF1F18BAE4F890A0813768D992817FDAB19@sdcexchms.au.logicalis.com>
In-Reply-To: <72381AF1F18BAE4F890A0813768D992817FDAB19@sdcexchms.au.logicalis.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.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 10:51:03 -0000

On 30/01/2014 22:44, Greg Daley wrote:
> Of course, in order to get the protocols to pass legacy firewall 
> inspection, UDP encapsulation may be required, and companies would 
> have to actually implement the protocol... Greg Daley 
> gdaley@au.logicalis.com 
So UDP/DCCP/MPLS ?

Stewart

From l.wood@surrey.ac.uk  Fri Jan 31 03:34:28 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87FCE1A057D; Fri, 31 Jan 2014 03:34:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jVwg-BqMVcg; Fri, 31 Jan 2014 03:34:26 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.141]) by ietfa.amsl.com (Postfix) with ESMTP id 11FFB1A0590; Fri, 31 Jan 2014 03:34:25 -0800 (PST)
Received: from [85.158.136.51:7852] by server-5.bemta-5.messagelabs.com id 44/0D-32749-D3A8BE25; Fri, 31 Jan 2014 11:34:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-49.messagelabs.com!1391168061!19463993!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24193 invoked from network); 31 Jan 2014 11:34:21 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-11.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 31 Jan 2014 11:34:21 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 31 Jan 2014 11:34:20 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <gdaley@au.logicalis.com>, <jnc@mercury.lcs.mit.edu>, <ietf@ietf.org>, <mpls@ietf.org>
Date: Fri, 31 Jan 2014 11:32:31 +0000
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: Ac8ecmlbdUqQeAUTQQSU8IsB6dbYxwABbdgM
Message-ID: <290E20B455C66743BE178C5C84F1240847E63346FE@EXMB01CMS.surrey.ac.uk>
References: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu> <72381AF1F18BAE4F890A0813768D992817FDAB19@sdcexchms.au.logicalis.com>, <52EB800E.2090102@cisco.com>
In-Reply-To: <52EB800E.2090102@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
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.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 11:34:28 -0000

RFC 6773. which requires a full udp checksum for nat traversal.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@ci=
sco.com]
Sent: 31 January 2014 10:50
To: Greg Daley; 'Noel Chiappa'; ietf@ietf.org; mpls@ietf.org
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulati=
ng MPLS in UDP) to Proposed Standard

On 30/01/2014 22:44, Greg Daley wrote:
> Of course, in order to get the protocols to pass legacy firewall
> inspection, UDP encapsulation may be required, and companies would
> have to actually implement the protocol... Greg Daley
> gdaley@au.logicalis.com
So UDP/DCCP/MPLS ?

Stewart

From vesely@tana.it  Fri Jan 31 03:35:22 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 910141A0588 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 03:35:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.957
X-Spam-Level: 
X-Spam-Status: No, score=-2.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CvRI0p-LxIyp for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 03:35:21 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id D75B11A057D for <ietf@ietf.org>; Fri, 31 Jan 2014 03:35:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1391168116; bh=d+ZEwPWKj691JqihJUFkyqVa+2mKRuk59JuEY8Uzp9s=; l=2119; h=Date:From:To:CC:References:In-Reply-To; b=vCkgzX9ZdNCv/5tX5dOkfxy5IrF6eiZcT2+VQfhN26VyqTanPtVIK+lHpKrgpHRyV sTV01XLYe6rkzvl2VSnsLyZPr8BFaVFRKxICBBsqJBvIKcNK4uvizBdDQV1Mmebpvh kKivZ4m3Sk6QiZkx+CMufX6U1rt/OVNMWAmDUvGg=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Fri, 31 Jan 2014 12:35:16 +0100 id 00000000005DC033.0000000052EB8A74.0000388E
Message-ID: <52EB8A74.6010307@tana.it>
Date: Fri, 31 Jan 2014 12:35:16 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: Alissa Cooper <alissa@cooperw.in>
Subject: Re: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org> <52EA9F85.6080804@tana.it> <CF100132.F260%alissa@cooperw.in>
In-Reply-To: <CF100132.F260%alissa@cooperw.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 11:35:22 -0000

Hi

On Thu 30/Jan/2014 22:17:25 +0100 Alissa Cooper wrote:
> On 1/30/14 10:52 AM, "Alessandro Vesely" <vesely@tana.it> wrote:
>> On Wed 29/Jan/2014 17:16:56 +0100 IAB Chair wrote:
>>> 
>>> The document is available for inspection here:
>>> https://datatracker.ietf.org/doc/draft-iab-filtering-considerations/
>>
>> Albeit it purports to keep clear of (un)ethical considerations, the
>> document seems to be oriented toward government-imposed restrictions,
>> recounting how it would be better to move filtering to collaborative
>> endpoints rather than disrupting Internet operation, since bad actors
>> can circumvent filtering anyway.  I fully agree, but I think that a
>> general purpose document on this subject might have touched on such
>> points as password management, user identification, and outbound port
> 
> Could you expand a bit about what you feel is missing as regards to
> password management and user identification?

Blocking dictionary attacks is an obvious requirement for any server
endpoint.  Perhaps that topic is not really /missing/, since it is so
obvious and apparently overworked.  However, most of the applications
which log authentication failures don't support tracking the number of
failed attempts against a given password.  Thus, policies blindly
require passwords to be changed after T days, irrespectively of the
entropy that a password had and the amount of it that could have been
eroded by failed attempts.  So maybe that topic is not as overworked
as it may appear.

Upon authentication, a user-id qualifies an endpoint.  Together with a
realm-id, it makes a global identifier.  Email address confirmation
can be considered a kind of rendezvous service, which users can block
by discarding the request.  The exchange of marketing profile data
between unscrupulous operators, often based on email addresses, is a
kind of abusive or objectionable communication.  Disposable addresses
are an example of a mechanism to block that indirectly.  They require
endpoint-based support at both ends, which is rather uncommon.

Thank you for your interest
Ale

From bclaise@cisco.com  Fri Jan 31 03:53:48 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 082A51A0589 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 03:53:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.035
X-Spam-Level: 
X-Spam-Status: No, score=-10.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HM7y0R2DWSjM for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 03:53:45 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 666691A0588 for <ietf@ietf.org>; Fri, 31 Jan 2014 03:53:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15721; q=dns/txt; s=iport; t=1391169221; x=1392378821; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=lzbtIfMSZtjqJ2MjXsIPYze2kKjPXIyo/foSYgck90w=; b=YsSL4v8cJt7ttblHtnjPwL6dC/SgBeZJvlavChZbqjox7jzt7+TS9n4Q VCHiCLqz0NfDJSymHKuuXHb/4iPTsY8ECVzXuFOl498rmOUm7QPcjPBPL CBzUoMASz5U3Qxto+AQYohzRDZX32gXkH04PDGJRhq+9lXplpFlMZlPCw E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYFAGyO61KQ/khR/2dsb2JhbABZgkhEOL4NgQQWdIIlAQEBAwFuCg0ECxEEAQEBCRYEBAcJAwIBAgE0CQgHDAYCAQEXh2IIDcx3F44gCgEGAVcGhDIEmCqBMoUWhBaHQ4FvgT87gSwBCBc
X-IronPort-AV: E=Sophos;i="4.95,757,1384300800"; d="scan'208,217";a="4471395"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-1.cisco.com with ESMTP; 31 Jan 2014 11:53:39 +0000
Received: from [10.60.67.88] (ams-bclaise-8917.cisco.com [10.60.67.88]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s0VBrdAt026829; Fri, 31 Jan 2014 11:53:39 GMT
Message-ID: <52EB8EC3.3050904@cisco.com>
Date: Fri, 31 Jan 2014 12:53:39 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, ietf@ietf.org
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
In-Reply-To: <033501cf1c1a$80089fd0$8019df70$@olddog.co.uk>
Content-Type: multipart/alternative; boundary="------------070804050904050204010203"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 11:53:48 -0000

This is a multi-part message in MIME format.
--------------070804050904050204010203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 28/01/2014 12:17, Adrian Farrel wrote:
> Thanks Benoit,
>
> And I am not much concerned with the process here as with the meaning of the
> IETF last call.
>
> Reading the document, I don't understand what would happen if I found something
> that I thought should be different. It looks to me that this is a record of what
> has been implemented and deployed. That is fine and good, but I don't see what
> my review is supposed to give as input.
>
> It seems to me that either this is an IETF document describing some IPFIX
> widgets (drop all the Cisco stuff, get the WG to agree they want the feature,
> and let the IETF do a proper review probably as Standards Track) or it is a
> record of what Cisco did (continue to publish it, but don't ask for review of
> the content).
If I would have to chose between, this is closer to the later.
I meant closer, because there is an important clarification here: the 
review of BCP 184 "Guidelines for Authors and Reviewers of IP Flow 
Information Export (IPFIX) Information Elements" must be done. And the 
best way to have reviews from more people, not only the IPFIX IE 
doctors, was to present the work to the IPFIX WG (this was done several 
times).
So you should see this document as a clean up of the range 1-127, which 
was allocated to NetFlow v9 at the time, while the IPFIX information 
elements were standardized. That lead to some IPFIX information elements 
being deprecated in that range, because there were better standardized 
solutions:
- samplingInterval, samplingAlgorithm, classNamestandardized in PSAMP
- layer2packetSectionOffset, layer2packetSectionSize, 
layer2packetSectionData standardized in 
draft-ietf-ipfix-data-link-layer-monitoring-08 
<https://datatracker.ietf.org/doc/draft-ietf-ipfix-data-link-layer-monitoring/> 
(recently in RFC editor queue)

What would have been really wrong is to try to publish the draft years 
ago, via the ISE, and pushing proprietary information elements.

Regarding one of your question in the different email: The question 
might arise as to whether this document is supposed to update 3954.

Not sure that question makes sense.
NetFlow is a confusing term as it covers at the same time the Metering 
Process, the Exporting Process, and Information Elements (In IPFIX, 
there are clear distinctions between those terms). This draft doesn't 
update RFC 3954: there is no NetFlow 9.x. This draft updates the 
information model (read the IPFIX information elements) used by IPFIX 
and NetFlow v9 export protocol.

Regards, Benoit

>
> Joel points out that it is valuable to check that the publication of this
> document doesn't break anything else. I think that is a fine answer to my
> question and would ask that, in future, when the scope or intent of a last call
> is limited, that limit be explicitly called out in the last call so that no-one
> waste review effort. I also think that when the RFC is published it should not
> use boilerplate that says the document is a product of the IETF if the IETF did
> not have the opportunity to edit the technical content. It would be better to
> say that the IETF had consensus to publish the document but that it is not a
> product of the IETF.
>
> Cheers,
> Adrian
>
>> -----Original Message-----
>> From: Benoit Claise [mailto:bclaise@cisco.com]
>> Sent: 28 January 2014 00:15
>> To: adrian@olddog.co.uk; ietf@ietf.org
>> Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
>> Information Elements reused in IPFIX) to Informational RFC
>>
>> Adrian,
>>
>> Not an answer to the process question, but some background information
>> on this draft.
>> This draft, which is now 3 years old, has been evolving with the IPFIX
>> standardization.
>> For example, looking at
>> http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt,
>> you can see the interaction with the IPFIX WG document
>> ietf-ipfix-data-link-layer-monitoring: now that
>> ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the
>> draft has been simplified, and some IPFIX Information Elements in the
>> range 1-127 became deprecated.
>> This explains why the draft has been presented and reviewed multiple
>> times in the IPFIX WG, and also why it would benefit from a wider review
>> than the independent stream.
>>
>> Regards, Benoit (as draft author)
>>
>>
>>> Hi,
>>>
>>> I have a process question on this last call which is not clear from the last
>>> call text.
>>>
>>> Are we being asked to consider whether publication of this document is
> useful,
>>> or are we being asked for IETF consensus on the *content* of the document?
>>>
>>> It seems from the document that the content is descriptive of something
>>> implemented by a single vendor. I applaud putting that information into the
>>> public domain, but I don't understand the meaning of IETF consensus with
>> respect
>>> to this document.
>>>
>>> Thanks,
>>> Adrian
>>>
>>>> -----Original Message-----
>>>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
>> The
>>>> IESG
>>>> Sent: 21 January 2014 12:33
>>>> To: IETF-Announce
>>>> Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
>>>> Information Elements reused in IPFIX) to Informational RFC
>>>>
>>>>
>>>> The IESG has received a request from an individual submitter to consider
>>>> the following document:
>>>> - 'Cisco Specific Information Elements reused in IPFIX'
>>>>     <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>
>>>> Abstract
>>>>
>>>>
>>>>      This document describes some additional Information Elements of Cisco
>>>>      Systems, Inc. that are not listed in RFC3954.
>>>>
>>>>
>>>>
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>>>>
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>> .
>>>
> .
>


--------------070804050904050204010203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 28/01/2014 12:17, Adrian Farrel
      wrote:<br>
    </div>
    <blockquote cite="mid:033501cf1c1a$80089fd0$8019df70$@olddog.co.uk"
      type="cite">
      <pre wrap="">Thanks Benoit,

And I am not much concerned with the process here as with the meaning of the
IETF last call.

Reading the document, I don't understand what would happen if I found something
that I thought should be different. It looks to me that this is a record of what
has been implemented and deployed. That is fine and good, but I don't see what
my review is supposed to give as input.

It seems to me that either this is an IETF document describing some IPFIX
widgets (drop all the Cisco stuff, get the WG to agree they want the feature,
and let the IETF do a proper review probably as Standards Track) or it is a
record of what Cisco did (continue to publish it, but don't ask for review of
the content).</pre>
    </blockquote>
    If I would have to chose between, this is closer to the later.<br>
    I meant closer, because there is an important clarification here:
    the review of BCP 184 "Guidelines for Authors and Reviewers of IP
    Flow Information Export (IPFIX) Information Elements" must be done.&nbsp;
    And the best way to have reviews from more people, not only the
    IPFIX IE doctors, was to present the work to the IPFIX WG (this was
    done several times).<br>
    So you should see this document as a clean up of the range 1-127,
    which was allocated to NetFlow v9 at the time, while the IPFIX
    information elements were standardized. That lead to some IPFIX
    information elements being deprecated in that range, because there
    were better standardized solutions: <span class="m_h"><br>
      - samplingInterval</span>, <span class="m_h">samplingAlgorithm, </span><span
      class="m_h">className</span><span class="m_h"> standardized in
      PSAMP</span><br>
    - <span class="m_h">layer2packetSectionOffset</span><span
      class="m_h"></span>, <span class="m_h">layer2packetSectionSize</span>,
    <span class="m_h">layer2packetSectionData</span> standardized in <a
href="https://datatracker.ietf.org/doc/draft-ietf-ipfix-data-link-layer-monitoring/">draft-ietf-ipfix-data-link-layer-monitoring-08</a>
    (recently in RFC editor queue)<br>
    <br>
    What would have been really wrong is to try to publish the draft
    years ago, via the ISE, and pushing proprietary information
    elements. <br>
    <br>
    Regarding one of your question in the different email: <span
      style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;mso-bidi-font-family:&quot;Times
      New Roman&quot;;color:#1F497D">The question might arise as to
      whether this document is supposed to update 3954.<o:p></o:p></span><span
      class="h1"></span><span class="h1"></span><br>
    <br>
    Not sure that question makes sense.<br>
    NetFlow is a confusing term as it covers at the same time the
    Metering Process, the Exporting Process, and Information Elements
    (In IPFIX, there are clear distinctions between those terms). This
    draft doesn't update RFC 3954: there is no NetFlow 9.x. This draft
    updates the information model (read the IPFIX information elements)
    used by IPFIX and NetFlow v9 export protocol. <br>
    <br>
    Regards, Benoit<br>
    <br>
    <blockquote cite="mid:033501cf1c1a$80089fd0$8019df70$@olddog.co.uk"
      type="cite">
      <pre wrap="">

Joel points out that it is valuable to check that the publication of this
document doesn't break anything else. I think that is a fine answer to my
question and would ask that, in future, when the scope or intent of a last call
is limited, that limit be explicitly called out in the last call so that no-one
waste review effort. I also think that when the RFC is published it should not
use boilerplate that says the document is a product of the IETF if the IETF did
not have the opportunity to edit the technical content. It would be better to
say that the IETF had consensus to publish the document but that it is not a
product of the IETF.

Cheers,
Adrian

</pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Benoit Claise [<a class="moz-txt-link-freetext" href="mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]
Sent: 28 January 2014 00:15
To: <a class="moz-txt-link-abbreviated" href="mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>; <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>
Subject: Re: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco Specific
Information Elements reused in IPFIX) to Informational RFC

Adrian,

Not an answer to the process question, but some background information
on this draft.
This draft, which is now 3 years old, has been evolving with the IPFIX
standardization.
For example, looking at
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt">http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt</a>,
you can see the interaction with the IPFIX WG document
ietf-ipfix-data-link-layer-monitoring: now that
ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the
draft has been simplified, and some IPFIX Information Elements in the
range 1-127 became deprecated.
This explains why the draft has been presented and reviewed multiple
times in the IPFIX WG, and also why it would benefit from a wider review
than the independent stream.

Regards, Benoit (as draft author)


</pre>
        <blockquote type="cite">
          <pre wrap="">Hi,

I have a process question on this last call which is not clear from the last
call text.

Are we being asked to consider whether publication of this document is
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">useful,
</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">or are we being asked for IETF consensus on the *content* of the document?

It seems from the document that the content is descriptive of something
implemented by a single vendor. I applaud putting that information into the
public domain, but I don't understand the meaning of IETF consensus with
</pre>
        </blockquote>
        <pre wrap="">respect
</pre>
        <blockquote type="cite">
          <pre wrap="">to this document.

Thanks,
Adrian

</pre>
          <blockquote type="cite">
            <pre wrap="">-----Original Message-----
From: IETF-Announce [<a class="moz-txt-link-freetext" href="mailto:ietf-announce-bounces@ietf.org">mailto:ietf-announce-bounces@ietf.org</a>] On Behalf Of
</pre>
          </blockquote>
        </blockquote>
        <pre wrap="">The
</pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <pre wrap="">IESG
Sent: 21 January 2014 12:33
To: IETF-Announce
Subject: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt; (Cisco Specific
Information Elements reused in IPFIX) to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'Cisco Specific Information Elements reused in IPFIX'
   &lt;draft-yourtchenko-cisco-ies-09.txt&gt; 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2014-02-18. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


    This document describes some additional Information Elements of Cisco
    Systems, Inc. that are not listed in RFC3954.




The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/">http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/">http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/</a>


No IPR declarations have been submitted directly on this I-D.
</pre>
          </blockquote>
          <pre wrap="">
.

</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
.

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------070804050904050204010203--

From chris.dearlove@baesystems.com  Fri Jan 31 05:23:36 2014
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA0CC1A058D for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 05:23:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.103
X-Spam-Level: 
X-Spam-Status: No, score=-4.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-5, RDNS_NONE=0.793] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBnVN2BMkKea for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 05:23:35 -0800 (PST)
Received: from ukmta1.baesystems.com (unknown [20.133.0.55]) by ietfa.amsl.com (Postfix) with ESMTP id 5DED61A0522 for <ietf@ietf.org>; Fri, 31 Jan 2014 05:23:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,757,1384300800"; d="scan'208";a="409938245"
Received: from unknown (HELO baemasmds017.greenlnk.net) ([10.15.207.104]) by baemasmds003ir.sharelnk.net with ESMTP; 31 Jan 2014 13:23:31 +0000
X-IronPort-AV: E=Sophos;i="4.95,757,1384300800"; d="scan'208";a="40003281"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds017.greenlnk.net with ESMTP; 31 Jan 2014 13:23:31 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.106]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0174.001; Fri, 31 Jan 2014 13:23:31 +0000
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF 89 London - Enquiry
Thread-Topic: IETF 89 London - Enquiry
Thread-Index: Ac8dg+Rv/gUCFHU4R261kNvbSHtHJQAdH6+AACO+twA=
Date: Fri, 31 Jan 2014 13:23:30 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan>
In-Reply-To: <20140130201807.16038.qmail@joyce.lan>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Cc: "antony@it.bw" <antony@it.bw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 13:23:37 -0000

Sm9obiBMZXZpbmUNCj4gSXQncywgYWgsIHF1aXRlIGluZm9ybWFsLiAgVGVlIHNoaXJ0cyBhbmQg
c2FuZGFscyBhcmUgY29tbW9uIHdoZW4gdGhlIHdlYXRoZXIgaXMgd2FybSBlbm91Z2guDQoNCkxv
bmRvbi4gTWFyY2guIEV4cGVjdCByYWluLiAoVGhlIE1hcmNoIHdhcyBhbG1vc3QgcmVkdW5kYW50
IHRoZXJlLikNCg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioKVGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFy
ZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVuZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUg
cHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2Ug
ZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hv
dWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBmb3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9y
CmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
Cg==


From tjc@ecs.soton.ac.uk  Fri Jan 31 05:51:22 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81D581A0522 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 05:51:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.986
X-Spam-Level: 
X-Spam-Status: No, score=-0.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.535, SPF_NEUTRAL=0.779] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HIMHcYEnlQ3k for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 05:51:21 -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 A639B1A0193 for <ietf@ietf.org>; Fri, 31 Jan 2014 05:51:20 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s0VDpDmG003971; Fri, 31 Jan 2014 13:51:13 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s0VDpDmG003971
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1391176273; bh=GqQYZIaz94sXTIoP+iAO9ic0G5c=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=eDFMGkCFXXkV0hxE30g6huWVsRnlgfSxeI+B08E1odOpclLNBZUBA0Sa8M+ReaL5y FMYV1Bd2um4fk6VPm4hgIrMr4Xc1qX+kx1lQQEZhFhYsWzxJ5mezJgX4nD6rd8ypsV 4EbHirQnzXR3sw5mi7T6Q1Qa494LCgU+4IXVbGj8=
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 q0UDpD0959631864So ret-id none; Fri, 31 Jan 2014 13:51:13 +0000
Received: from [172.17.242.165] ([147.67.4.98]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s0VDp49I008600 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 31 Jan 2014 13:51:05 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Enquiry
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net>
Date: Fri, 31 Jan 2014 13:51:03 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
X-Mailer: Apple Mail (2.1827)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q0UDpD095963186400; tid=q0UDpD0959631864So; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s0VDpDmG003971
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "antony@it.bw" <antony@it.bw>, John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 13:51:22 -0000

On 31 Jan 2014, at 13:23, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:

> John Levine
>> It's, ah, quite informal.  Tee shirts and sandals are common when the =
weather is warm enough.
>=20
> London. March. Expect rain. (The March was almost redundant there.)

Indeed. Large chunks of England are underwater=85 it=92s been raining =
for some time.

Tim=

From fred@cisco.com  Fri Jan 31 06:01:03 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B71B1A0193 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 06:01:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.035
X-Spam-Level: 
X-Spam-Status: No, score=-110.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yOOSpSBorT33 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 06:00:59 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id A62C71A02C5 for <ietf@ietf.org>; Fri, 31 Jan 2014 06:00:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4422; q=dns/txt; s=iport; t=1391176856; x=1392386456; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CCuKsApaZm6rJUMKmunFywQRoXnYuCihFgRTpnNqut0=; b=HcZoHxV7yta6lRk/lY7VptxOk3os/bEZFJaflx8OPQ6OhYr+T5+K8aQ9 wbqHXbEaNFTcTCUGJSK1FzJuvxx/61BFqPle394yLXbuQMD8kVwaxatvf o00sB99qu/0Kq/Xy6GvmiZt754pyyQx9NFFcF+y1Yomdjv6LJBlUdErrh U=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4GALur61KtJXG9/2dsb2JhbABZgkhEOAlIBr04gQcWdIIlAQEBAwF5BQsCAQgECjgyJQEBBA4FCQWHbwgIBcw6F44uVAeDJIEUBJA/gTKGOYxhhUCDLYIq
X-IronPort-AV: E=Sophos;i="4.95,758,1384300800";  d="asc'?scan'208,217";a="16986162"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-3.cisco.com with ESMTP; 31 Jan 2014 14:00:55 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s0VE0tgF007156 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 Jan 2014 14:00:55 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.227]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Fri, 31 Jan 2014 08:00:55 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Tony Chigaazira <antony@it.bw>
Subject: Re: IETF 89 London - Enquiry
Thread-Topic: IETF 89 London - Enquiry
Thread-Index: Ac8dg+Rv/gUCFHU4R261kNvbSHtHJQBO0IKA
Date: Fri, 31 Jan 2014 14:00:55 +0000
Message-ID: <FA5ED3FF-8601-41FB-A627-7422BF5956EA@cisco.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw>
In-Reply-To: <019701cf1d83$fed5a7d0$fc80f770$@it.bw>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.222.2]
Content-Type: multipart/signed; boundary="Apple-Mail=_AF137548-6AD7-4CCC-82EB-DF46AE52A733"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 14:01:03 -0000

--Apple-Mail=_AF137548-6AD7-4CCC-82EB-DF46AE52A733
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_1EE91422-D619-46CA-A00D-B8000EEEE10D"


--Apple-Mail=_1EE91422-D619-46CA-A00D-B8000EEEE10D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Jan 30, 2014, at 1:24 AM, Tony Chigaazira <antony@it.bw> wrote:

> May I please know the dress code as well.

There is a brief overview of the IETF at http://www.ietf.org/tao.html, =
which you may be interested to read. You should likely also plan to =
attend the newcomer's tutorial on Sunday afternoon.

The dress code is spelled out pretty explicitly in that document - =
http://www.ietf.org/tao.html#rfc.section.3.4.

Since attendees must wear their name tags, they must also wear shirts or =
blouses. Pants or skirts are also highly recommended. Seriously though, =
many newcomers are often embarrassed when they show up Monday morning in =
suits, to discover that everybody else is wearing T-shirts, jeans =
(shorts, if weather permits) and sandals. There are those in the IETF =
who refuse to wear anything other than suits. Fortunately, they are well =
known (for other reasons) so they are forgiven this particular =
idiosyncrasy. The general rule is "dress for the weather" (unless you =
plan to work so hard that you won't go outside, in which case, "dress =
for comfort" is the rule!).



--Apple-Mail=_1EE91422-D619-46CA-A00D-B8000EEEE10D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Jan 30, 2014, at 1:24 AM, Tony Chigaazira &lt;<a =
href=3D"mailto:antony@it.bw">antony@it.bw</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
style=3D"font-family: Calibri, sans-serif; font-size: 15px; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px; display: inline !important; float: none; =
">May I please know the dress code as =
well.</span></blockquote></div><br>
There is a brief overview of the IETF at&nbsp;<a =
href=3D"http://www.ietf.org/tao.html">http://www.ietf.org/tao.html</a>, =
which you may be interested to read. You should likely also plan to =
attend the newcomer's tutorial on Sunday =
afternoon.<div><br></div><div>The dress code is spelled out pretty =
explicitly in that document - <a =
href=3D"http://www.ietf.org/tao.html#rfc.section.3.4">http://www.ietf.org/=
tao.html#rfc.section.3.4</a>.</div><div><br></div><div><p =
id=3D"rfc.section.3.4.p.1" style=3D"margin-left: 2em; font-family: =
verdana, helvetica, arial, sans-serif; font-size: 13px; ">Since =
attendees must wear their name tags, they must also wear shirts or =
blouses. Pants or skirts are also highly recommended. Seriously though, =
many newcomers are often embarrassed when they show up Monday morning in =
suits, to discover that everybody else is wearing T-shirts, jeans =
(shorts, if weather permits) and sandals. There are those in the IETF =
who refuse to wear anything other than suits. Fortunately, they are well =
known (for other reasons) so they are forgiven this particular =
idiosyncrasy. The general rule is "dress for the weather" (unless you =
plan to work so hard that you won't go outside, in which case, "dress =
for comfort" is the rule!).</p></div><div><br></div></body></html>=

--Apple-Mail=_1EE91422-D619-46CA-A00D-B8000EEEE10D--

--Apple-Mail=_AF137548-6AD7-4CCC-82EB-DF46AE52A733
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFS66yXbjEdbHIsm0MRAh8RAJwIVpmUd8+pIBFkE74zEe0Whb/iTwCgki0A
gn5hcFL8WnDhrhk9H9eR+a0=
=ctSx
-----END PGP SIGNATURE-----

--Apple-Mail=_AF137548-6AD7-4CCC-82EB-DF46AE52A733--

From elwynd@dial.pipex.com  Fri Jan 31 07:06:01 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 661811A1DBD for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 07:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-AAAsm4TG9V for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 07:05:59 -0800 (PST)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id E240A1A03CC for <ietf@ietf.org>; Fri, 31 Jan 2014 07:05:58 -0800 (PST)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1W9Ff8-0005le-H3; Fri, 31 Jan 2014 15:05:49 +0000
Subject: Re: IETF 89 London - Enquiry
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
Content-Type: text/plain; charset="windows-1251"
Date: Fri, 31 Jan 2014 15:05:44 +0000
Message-Id: <1391180744.24761.1834.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Cc: "antony@it.bw" <antony@it.bw>, John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 15:06:01 -0000

On Fri, 2014-01-31 at 13:51 +0000, Tim Chown wrote:
> On 31 Jan 2014, at 13:23, Dearlove, Christopher (UK) <chris.dearlove@baes=
ystems.com> wrote:
>=20
> > John Levine
> >> It's, ah, quite informal.  Tee shirts and sandals are common when the =
weather is warm enough.
> >=20
> > London. March. Expect rain. (The March was almost redundant there.)
>=20
> Indeed. Large chunks of England are underwater=85 it=92s been raining for=
 some time.
>=20
> Tim

But in the best traditions of the interactions of British Politics and
British Weather, a Minister for Floods will have been appointed just in
time for the floods to disappear and we will be experiencing the start
of a months long heat wave and drought by then.  Never take anything for
granted!=20

Elwyn=20

PS
Green wellies are de rigueur in place of sandals for flood wear in the
UK.  Could have done with them back at IETF 65 in Dallas!

/E


From andrew.hutton@unify.com  Fri Jan 31 07:25:03 2014
Return-Path: <andrew.hutton@unify.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E58081A0276 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 07:25:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L27Vt5DVk0HW for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 07:25:00 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id A20E41A020C for <ietf@ietf.org>; Fri, 31 Jan 2014 07:25:00 -0800 (PST)
Received: from MCHP01HTC.global-ad.net (unknown [172.29.42.234]) by mx11.unify.com (Server) with ESMTP id 5F43C1EB85DF; Fri, 31 Jan 2014 16:24:56 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.100]) by MCHP01HTC.global-ad.net ([172.29.42.234]) with mapi id 14.03.0174.001; Fri, 31 Jan 2014 16:24:56 +0100
From: "Hutton, Andrew" <andrew.hutton@unify.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
Subject: RE: IETF 89 London - Enquiry
Thread-Topic: IETF 89 London - Enquiry
Thread-Index: AQHPHouQtjEd/YC3iE2xyfJ8Aa/NvZqe88Yw
Date: Fri, 31 Jan 2014 15:24:55 +0000
Message-ID: <9F33F40F6F2CD847824537F3C4E37DDF17CE0511@MCHP04MSX.global-ad.net>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "antony@it.bw" <antony@it.bw>, John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 15:25:04 -0000

> >> It's, ah, quite informal.  Tee shirts and sandals are common when
> the weather is warm enough.
> >
> > London. March. Expect rain. (The March was almost redundant there.)
>=20
> Indeed. Large chunks of England are underwater... it's been raining for
> some time.

If it's still raining in March then you might need a wetsuit.

Andy

From scott.brim@gmail.com  Fri Jan 31 08:56:24 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 018E01A1F48; Fri, 31 Jan 2014 08:56:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SavwqCutpbsG; Fri, 31 Jan 2014 08:56:22 -0800 (PST)
Received: from mail-oa0-x22e.google.com (mail-oa0-x22e.google.com [IPv6:2607:f8b0:4003:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E973C1A0522; Fri, 31 Jan 2014 08:56:21 -0800 (PST)
Received: by mail-oa0-f46.google.com with SMTP id n16so5414742oag.5 for <multiple recipients>; Fri, 31 Jan 2014 08:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=uZcH2uyBv5uVi0PGuq3jz/NpzpjG7R4y7boTuRbudNE=; b=ALGuhcIAojg3hQv4mBS+Q8W2OfvVe5pG+aiaZbKCJrEQb/x2W+2nc4C7lOi/4xrWX9 ftI9LC86G3raG7Z0Uq7SgBiLwrUl//YUYboV9yPTqS1nx4H8//L3zLpDNezFh893PT+y CSj26v3bai897OiWewJKj03Q10jsH57iRyuVIbKyI0hQAppks/cO4CElMdLrRfjy4Q1D T0394wK0jBFb0rdu28n4QMVI/G4YGg6CL5vOvwjUvwswpBZ+xdosF6Up0FCehfonwAdj bo4LXKrc1LpRB4hIdIAcXzIGCIJRynTi3ZhrkKoz8J6tkNBcUEI0rbb3ebTdrhGZpTug u3PA==
X-Received: by 10.182.142.229 with SMTP id rz5mr17533036obb.12.1391187378207;  Fri, 31 Jan 2014 08:56:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 31 Jan 2014 08:55:58 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 31 Jan 2014 11:55:58 -0500
Message-ID: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
Subject: GEN-ART telechat review of draft-farrell-perpass-attack-05
To: gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 16:56:24 -0000

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

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

Document: draft-farrell-perpass-attack-05
Reviewer: Scott Brim
Review Date: 2014-02-01
IETF LC End Date: 2013-12-31
IESG Telechat date: 2014-02-06

Summary: This draft is ready for publication as a BCP.

Major issues:

Minor issues:

Nits/editorial comments:

Two comments:

First, there are good arguments for publication as Informational , but
since it incrementally adds to BCP 72, it should be incorporated
there, so BCP is slightly better.

Second, the only significant difference from -04 was the removal of
"and be prepared to justify their decisions". There was a lot of
discussion that led to this, and some concern that the statement on
architectural considerations is not strongly enough worded without it.
However, see the previous paragraph (both paragraphs are below).  I
believe that these two paragraphs, taken together, do what is desired.

   Those developing IETF specifications need to be able to describe how
   they have considered PM, and, if the attack is relevant to the work
   to be published, be able to justify related design decisions.  This
   does not mean a new "pervasive monitoring considerations" section is
   needed in IETF documentation.  It means that, if asked, there needs
   to be a good answer to the question "is pervasive monitoring relevant
   to this work and if so how has it been considered?"

   In particular, architectural decisions, including which existing
   technology is re-used, may significantly impact the vulnerability of
   a protocol to PM.  Those developing IETF specifications therefore
   need to consider mitigating PM when making these architectural
   decisions.  Getting adequate, early review of architectural decisions
   including whether appropriate mitigation of PM can be made is
   important.  Revisiting these architectural decisions late in the
   process is very costly.

Scott

From dhc@dcrocker.net  Fri Jan 31 09:22:50 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EADE61A1F62; Fri, 31 Jan 2014 09:22:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XUb-uyZnMHSW; Fri, 31 Jan 2014 09:22:45 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 62E5F1A0448; Fri, 31 Jan 2014 09:22:45 -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 s0VHMaT9006590 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 31 Jan 2014 09:22:40 -0800
Message-ID: <52EBDBC0.5000304@dcrocker.net>
Date: Fri, 31 Jan 2014 09:22:08 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>, gen-art <gen-art@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org, IETF discussion list <ietf@ietf.org>
Subject: Re: GEN-ART telechat review of draft-farrell-perpass-attack-05
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
In-Reply-To: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@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.66]); Fri, 31 Jan 2014 09:22:40 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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, 31 Jan 2014 17:22:50 -0000

On 1/31/2014 8:55 AM, Scott Brim wrote:
> First, there are good arguments for publication as Informational , but
> since it incrementally adds to BCP 72, it should be incorporated
> there, so BCP is slightly better.


It does?

It does not say it does.

So that linkage is something the reviewer is creating.

At the least, a claim that it does "add to" BCP 72 invites further 
debate about the nature and implications of the update.

Again, making this a BCP confuses the nature of the document with those 
that give substantive operational guidance.

This document does exactly what it should:  It defines the topic and it 
says the IETF considers the topic important.  It calls for practices, 
but doesn't -- and shouldn't -- define them.

The job of providing substantive details about IETF practices associated 
with the topic will come later.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From hartmans@mit.edu  Fri Jan 31 09:39:05 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B1B1A0431; Fri, 31 Jan 2014 09:39:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ws8XLzI7WUw4; Fri, 31 Jan 2014 09:39:05 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 013971A043A; Fri, 31 Jan 2014 09:39:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id A7D8520655; Fri, 31 Jan 2014 12:35:50 -0500 (EST)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38UyD3o8NwUb; Fri, 31 Jan 2014 12:35:50 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 31 Jan 2014 12:35:50 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id BFB9680BEB; Fri, 31 Jan 2014 12:38:59 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: GEN-ART telechat review of draft-farrell-perpass-attack-05
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com>
Date: Fri, 31 Jan 2014 12:38:59 -0500
In-Reply-To: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com> (Scott Brim's message of "Fri, 31 Jan 2014 11:55:58 -0500")
Message-ID: <tslmwic59vw.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-farrell-perpass-attack.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 17:39:06 -0000

Thanks Scott.
In the interest of being clear about my position, I support publication
of 04 but do not support publication of 05.

I think all the discussion that is useful has happened and all that
remains is the consensus call from the sponsoring AD.

From sm@elandsys.com  Fri Jan 31 09:45:07 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3CA41A0576; Fri, 31 Jan 2014 09:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.135
X-Spam-Level: 
X-Spam-Status: No, score=-1.135 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PNZjO0Gc_Mkd; Fri, 31 Jan 2014 09:45:05 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CA91A0459; Fri, 31 Jan 2014 09:45:05 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.128.87]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s0VHikTE019026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 31 Jan 2014 09:44:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1391190300; bh=wPuGcILnFFq1H6Ev74W3lAwxNnc1/Yen6C4+pRopDHQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fUJTs3WnkmuD3FmtUGts6FGQ8ynUn0AlrcbYyy3YAomg4g5l8sZPT7LDSn341KBfH sMc/Gs3CtKIJn1dF8mSP4zJcsYMqDmVcpsP7+lGHJGDfuofZ9r9qfvEDRbdEmwH4Sr R8VpSlbdD+PQlMPWkCNIsZQrgmWJBgH44j5RCD94=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1391190300; i=@elandsys.com; bh=wPuGcILnFFq1H6Ev74W3lAwxNnc1/Yen6C4+pRopDHQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iGREhd1kel1XsFQE9Gt6VIfmI2lBFHuITBwnnHq0Xv4zrCfytdu+aNfbwp7ERy+qy CMrnlR4wtOWLv9mzMzNPBzuSkWL8r8GN0MHMkBhAAnTQMi0oKrIfKv2PP2AYbxHzS5 0NlGzct3/+z0pQmA8hsZR8Bi7l8nc7yqkKmN4IP0=
Message-Id: <6.2.5.6.2.20140131000347.0b2edab0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 31 Jan 2014 08:30:03 -0800
To: iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
In-Reply-To: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 17:45:07 -0000

Hello,
At 08:16 29-01-2014, IAB Chair wrote:
>This is a call for review of "Technical Considerations for Internet
>Service Blocking and Filtering" prior to potential approval as an
>IAB stream RFC.

 From Section 4.1.3 of draft-iab-filtering-considerations-06:

   "If voice communication based on SIP [RFC3261] is blocked,
    users are likely to use proprietary protocols that allow them to talk
    to each other.  Some filtering systems are only capable of
    identifying IPv4 traffic and therefore by shifting to IPv6 users may
    be able to evade filtering.  Using IPv6 with header options, using
    multiple layers of tunnels, or using encrypted tunnels can also make
    it more challenging for blocking systems to find transport ports
    within packets, making port-based blocking more difficult.  Thus
    distribution and mobility can hamper efforts to block communications
    in a number of ways."

There is a case of SIP being blocked at=20
http://www.onsip.com/blog/2013/07/02/in-depth-verizon-blocks-sip-traffic-usi=
ng-alg=20
I gather that the argument in the first sentence=20
(see quoted text) is that users will use=20
Skype.  For what it i worth, there is an article=20
at=20
http://www.itwebafrica.com/telecommunications/335-africa/229496-skype-is-not=
-banned-in-ethiopia=20
about a country which discussed a draft=20
legislation allegedly affecting Skype.    There=20
is a case of a provider charging more money to=20
unblock VoIP (=20
http://forum.vodafone.co.uk/t5/Pay-monthly-services/VoIP-SIP-Skype-Etc/td-p/=
729923=20
).  In my opinion, blocking voice traffic=20
nowadays does not necessarily cause a shift to=20
proprietary protocols as a proprietary service=20
can still use a non-proprietary protocol.

Section 4.1.3 is about efficacy and how easy is=20
it to avoid being blocked.  In 2003, it was the=20
view of the then-IAB that [filtering] or=20
[preventing] the transmission of traffic based on=20
the service identification within the traffic=20
flow will have a limited effect.  As mentioned in=20
the quoted text, the adversary, the user in this=20
case, can use "non-well-knownness" ports to evade=20
filtering.  It was also mentioned that SIP can=20
use dynamically allocated service identifiers.

Thinking aloud, I would say that the first=20
paragraph in Section 4.1.3 discusses about=20
efficacy from a service end-point=20
perspective.  The second paragraph might be more=20
about the efficacy of blocking by=20
intermediaries.  It is argued that the adversary=20
will use a different port or encrypt the=20
traffic.  As a side-note, the user cannot shift=20
to IPv6 or the user would be using IPv6 as a=20
tunnel.  The question is how effective is port=20
blocking.  I would use the following description:

    "Services may be tunneled within other services, proxied by a
     collaborating external host (e.g., an anonymous redirector),
     or simply run over an alternate port (e.g., port 8080 vs port
     80 for HTTP).  Another means of circumvention is alteration of
     the service behavior to use a dynamic port negotiation phase,
     in order to avoid use of a constant port address."

and have the encryption discussion in a separate paragraph.

What the people with the authority would like to=20
have is an affective blocking mechanism.  Are=20
there any references about attempts to side-step=20
what is being discussed in that paragraph?

 From Section 4.2.1:

   "For residential or consumer networks with many egress points, the
    first challenge to obtaining this traffic is simply gaining access to
    the constituent packets.  The Internet is designed to deliver packets
    hop-by-hop from source to destination -- not to any particular point
    along the way.  In practice, inter-network routing is often
    asymmetric, and for sufficiently complex local networks, intra-
    network traffic flows can be asymmetric as well [asymmetry]."

As the "asymmetry" reference is to a pay-to-view=20
paper I was unable to read it.  I suggest finding=20
a reference which the reader can access for free.

The first sentence mentions the challenge of=20
gaining access to the user's packets.  The second=20
sentence discusses about the Internet being=20
designed for hop-by-hop delivery, and it is=20
followed by a mention of the asymmetry of=20
inter-network routing.  There is a (old) visual=20
illustration of connectivity for North America at=20
http://infosthetics.com/archives/cybergeography_book6.jpg=20
My guess is that a visual illustration for the=20
rest of the world would show a lower number of egress points.

I'll use=20
http://www.renesys.com/wp-content/uploads/2013/09/Sudan_Internet.png=20
as an example.  It's not that difficult to gain=20
access access to the packets as the in-country=20
network is not that complex.  Is the discussion=20
in Section 4.2.1 using a "clich=E9" [1]?  I would=20
look at (network-based blocking) scope from a=20
collateral damage [2] vantage point.

 From Section 4.2.4:

   "In sum, network-based blocking is only effective in a fairly
    constrained set of circumstances.  First, the traffic needs to flow
    through the network in such a way that the intermediary device has
    access to any communications it intends to block."

Is network-based blocking good enough to do the=20
job?  Given the extent of deployment of such=20
measures I find it difficult to argue that it is=20
only effective in a fairly constrained set of circumstances.

 From the Conclusion section:

   "Because it least likely to create technical or architectural
    problems, endpoint-based blocking is the form of Internet service
    blocking that is least harmful to the Internet."

What are the architectural problems?  I am asking=20
the question as it is the sort of question that=20
comes up in discussions about blocking traffic.  Section 3.4 mentions that:

   "In the next section, blocking systems designed according to each of
    the three patterns -- network services, rendezvous services, and
    endpoints -- are evaluated for their technical and architectural
    implications."

A quick glance through Section 4 shows the following:

   "From an architectural perspective, however, they may create many of
    the same problems as network-based filtering conducted without
    consent."

   "If cooperation can be achieved, endpoint-based blocking can be much
    more effective than other approaches because it is so coherent with
    the Internet's architectural principles."

As a note, the document does not reference RFC 1958.

Regards,
S. Moonesamy

1. a phrase or opinion that is overused and betrays a lack of original=
 thought.
2.=20
http://www.sigcomm.org/sites/default/files/ccr/papers/2012/July/2317307-2317=
311.pdf=20


From andrewf@plixer.com  Fri Jan 31 10:14:38 2014
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99F471A03C3 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 10:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_37=0.6, J_CHICKENPOX_38=0.6, RP_MATCHES_RCVD=-0.535] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H1bA4zHLe0kY for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 10:14:37 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 380DA1A043A for <ietf@ietf.org>; Fri, 31 Jan 2014 10:14:37 -0800 (PST)
Received: from [10.1.15.178] (64.140.243.154) by mx1.plixer.com (10.1.5.1) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 31 Jan 2014 13:14:33 -0500
Message-ID: <52EBE809.9000502@plixer.com>
Date: Fri, 31 Jan 2014 13:14:33 -0500
From: Andrew Feren <andrewf@plixer.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 18:14:38 -0000

Hi all,

I don't currently have an opinion on the proper process, but I do have a
few last call comments.


"5.3.  IEs assigned for NetFlow v9 compatibility

   ElementId: 105..126

   These element IDs are not covered by this draft and left "as is",
   i.e. for Netflow v9 compatibility."

should be

"5.3.  IEs assigned for NetFlow v9 compatibility

   ElementId: 105..127

   These element IDs are not covered by this draft and left "as is",
   i.e. for NetFlow v9 compatibility."

[change summary : 126 -> 127  and Netflow -> NetFlow ]


Despite the fact that Appendix B change 07 says its semantics were
changed to 'identifier' based on my comments semantics for
ipv4RouterSc(43) should be 'default'.  To be fair I don't think I
originally specified what the semantics should be just that they
shouldn't be ipv4address.

Finally one nit that I'm somewhat ambivalent about.  I'd not abbreviate
"Shortcut" to "Sc" in ipv4RouterSc.

With the above changes the document looks good to me.

-Andrew

On 01/21/2014 07:33 AM, The IESG wrote:
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Cisco Specific Information Elements reused in IPFIX'
>   <draft-yourtchenko-cisco-ies-09.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 2014-02-18. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes some additional Information Elements of Cisco
>    Systems, Inc. that are not listed in RFC3954.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>


From avri@acm.org  Fri Jan 31 14:11:35 2014
Return-Path: <avri@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C09571A04E0 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 14:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AWXNgF1aigXq for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 14:11:33 -0800 (PST)
Received: from atl4mhob16.myregisteredsite.com (atl4mhob16.myregisteredsite.com [209.17.115.54]) by ietfa.amsl.com (Postfix) with ESMTP id D30C31A04D6 for <ietf@ietf.org>; Fri, 31 Jan 2014 14:11:32 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob16.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s0VMBRvr026303 for <ietf@ietf.org>; Fri, 31 Jan 2014 17:11:27 -0500
Received: (qmail 14024 invoked by uid 0); 31 Jan 2014 22:11:27 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 31 Jan 2014 22:11:27 -0000
Message-ID: <52EC1F8D.6000109@acm.org>
Date: Fri, 31 Jan 2014 17:11:25 -0500
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 89 London - Enquiry
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <9F33F40F6F2CD847824537F3C4E37DDF17CE0511@MCHP04MSX.global-ad.net>
In-Reply-To: <9F33F40F6F2CD847824537F3C4E37DDF17CE0511@MCHP04MSX.global-ad.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140131-1, 01/31/2014), Outbound message
X-Antivirus-Status: Not-Tested
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 22:11:36 -0000

On 31-Jan-14 10:24, Hutton, Andrew wrote:
>>>> It's, ah, quite informal.  Tee shirts and sandals are common when
>> the weather is warm enough.
>>>
>>> London. March. Expect rain. (The March was almost redundant there.)
>>
>> Indeed. Large chunks of England are underwater... it's been raining for
>> some time.
>
> If it's still raining in March then you might need a wetsuit.

or at least golashes

avri

From rdroms.ietf@gmail.com  Fri Jan 31 14:12:39 2014
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F82D1A0583 for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 14:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5oqMHcRJuhJl for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 14:12:38 -0800 (PST)
Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id BDFAF1A04D6 for <ietf@ietf.org>; Fri, 31 Jan 2014 14:12:37 -0800 (PST)
Received: by mail-qa0-f54.google.com with SMTP id i13so6998932qae.41 for <ietf@ietf.org>; Fri, 31 Jan 2014 14:12:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=pqhvgygLfKRe85AaCugIM4pqqE9iOO73Ch4khPWQFWI=; b=yaaA3Ff7uDIMttXZhqDqD9miiBmb/S11LhQpw6qjHaBQY9yID8vMdgAFEvViRpNIA+ R8i6YTYiNX803x2/u6o8TQOtEK2cCjjfT/SZ2yOPoICSqMbiANH2xBtGwwR+MCuM5K7C qR36b946p9Y9c9OSVrCrYvZUalOyV0xablaIDjsnxR0oI0HK+/8kWOx/dfYkEU2T8Sj5 OE91qSxD0hYMsQgjo44kS9OpOk00kJFSosK3jXf3e+L3BHcMCBj5x0A9OJqSQUJNuvAc fopi8er147r1KCQY6w2TJ4qg9WHNtxtyQu9oSozqC1xYBPY3Gqn7PwPQQAkKkquU8wy5 PfYQ==
X-Received: by 10.140.25.142 with SMTP id 14mr33590175qgt.83.1391206353821; Fri, 31 Jan 2014 14:12:33 -0800 (PST)
Received: from [10.86.255.146] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id 72sm15327946qgv.19.2014.01.31.14.12.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 Jan 2014 14:12:32 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF 89 London - Enquiry
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <52EC1F8D.6000109@acm.org>
Date: Fri, 31 Jan 2014 17:12:29 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <AAA0E387-DBF0-4047-A203-98EDAA25477F@gmail.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <9F33F40F6F2CD847824537F3C4E37DDF17CE0511@MCHP04MSX.global-ad.net> <52EC1F8D.6000109@acm.org>
To: "ietf@ietf.org IETF discussion" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 22:12:39 -0000

On Jan 31, 2014, at 5:11 PM 1/31/14, Avri Doria <avri@acm.org> wrote:

> 
> 
> On 31-Jan-14 10:24, Hutton, Andrew wrote:
>>>>> It's, ah, quite informal.  Tee shirts and sandals are common when
>>> the weather is warm enough.
>>>> 
>>>> London. March. Expect rain. (The March was almost redundant there.)
>>> 
>>> Indeed. Large chunks of England are underwater... it's been raining for
>>> some time.
>> 
>> If it's still raining in March then you might need a wetsuit.
> 
> or at least golashes

Wellies.

- Ralph

> 
> avri


From abdussalambaryun@gmail.com  Fri Jan 31 17:02:56 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4677F1ACCE8; Fri, 31 Jan 2014 17:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gpt5uh54tFlD; Fri, 31 Jan 2014 17:02:55 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) by ietfa.amsl.com (Postfix) with ESMTP id F3A001ACCDE; Fri, 31 Jan 2014 17:02:54 -0800 (PST)
Received: by mail-yk0-f172.google.com with SMTP id 200so3104114ykr.3 for <multiple recipients>; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qqPs2UxS5NFXugh/pnaXT2o0UkmIcxKPEmBp4CPEFSo=; b=qZByQkUK2Dc4/mk9wB9Xmtx0MOG24BUuzXBjXGPIksVgNP2VcWYviTbKd7ju4Wg67N L6ByksrirIkhJ1qxdtuQLGdnIICg4ZhA5NiILJEKRxu4vbk6sCEglWHCbj+64wdnnsjp SwkDoVuHsXCQ8gFFBz0m/yoJ+62FpwW3Ghq+LpsO5UFYknoxq/iS0lxEPoDKlgRtaay6 yK03PmfMY5SVxgmdK5HBYzeYNF6z91PIBszloUQZwakaxN4x56nI7uhBrkUtcYcOJd6Q O4HKDOAMVxPPb9c51pNegSCyXDZe3eUsND9NWJf2jFi8WUi/1bTlhy8Gyp9uEChj6vYv 8FMg==
MIME-Version: 1.0
X-Received: by 10.236.100.173 with SMTP id z33mr21608894yhf.9.1391216571064; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
Received: by 10.170.220.213 with HTTP; Fri, 31 Jan 2014 17:02:51 -0800 (PST)
In-Reply-To: <tslmwic59vw.fsf@mit.edu>
References: <CAPv4CP_2_pF_Rp8Ee37p7vTAgxkJrAV-wZQfiN_pJ=umxXXgAg@mail.gmail.com> <tslmwic59vw.fsf@mit.edu>
Date: Sat, 1 Feb 2014 02:02:51 +0100
Message-ID: <CADnDZ89Tr-DOA100QeszaafW3ZyThAM0UX=xWN7zzYx8rERhnQ@mail.gmail.com>
Subject: Re: GEN-ART telechat review of draft-farrell-perpass-attack-05
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: multipart/alternative; boundary=20cf3005e01886256f04f14dd9cc
Cc: gen-art <gen-art@ietf.org>, IETF discussion list <ietf@ietf.org>, "draft-farrell-perpass-attack.all@tools.ietf.org" <draft-farrell-perpass-attack.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Feb 2014 01:02:56 -0000

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

On Friday, January 31, 2014, Sam Hartman wrote:

> Thanks Scott.
> In the interest of being clear about my position, I support publication
> of 04 but do not support publication of 05.


I don't know why you object 05.

>
> I think all the discussion that is useful has happened and all that
> remains is the consensus call from the sponsoring AD.
>

The AD should read all comments from the community of practical
statements and AD to follow/sponsor reasonable statements/discussions or
policies, not sponsoring best future plan as best current practice ( it may
be initial plan for BCP).

IMHO, the AD powers are not to be used against reasonable engineering
discussions/requests only if that AD has done sound reasonable
engineering replies.

AB

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

<br><br>On Friday, January 31, 2014, Sam Hartman  wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">Thanks Scott.<br>
In the interest of being clear about my position, I support publication<br>
of 04 but do not support publication of 05.</blockquote><div><br></div><div=
>I don&#39;t know why you object 05.=A0=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">

<br>
I think all the discussion that is useful has happened and all that<br>
remains is the consensus call from the sponsoring AD.<br>
</blockquote><div><br></div><div>The AD should read all comments from the c=
ommunity of practical statements=A0and AD=A0to follow/sponsor=A0reasonable =
statements/discussions=A0or policies,=A0not sponsoring best future plan as =
best current practice ( it may be initial plan for BCP).</div>
<div><br></div><div>IMHO, the AD powers are not to be used against reasonab=
le engineering discussions/requests=A0only if that AD=A0has done sound=A0re=
asonable engineering=A0replies.=A0</div><div><br></div><div>AB</div>

--20cf3005e01886256f04f14dd9cc--

From agenda@ietf.org  Fri Jan 31 17:31:13 2014
Return-Path: <agenda@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3EA1ACCE2; Fri, 31 Jan 2014 17:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1CWOWVY6Law0; Fri, 31 Jan 2014 17:31:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8621ACCDF; Fri, 31 Jan 2014 17:31:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Agenda <agenda@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 89 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140201013111.9751.31078.idtracker@ietfa.amsl.com>
Date: Fri, 31 Jan 2014 17:31:11 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 Feb 2014 01:31:13 -0000

The IETF 89 Preliminary Agenda has been posted. The final agenda will be published on Friday, February 7th, 2014.

https://datatracker.ietf.org/meeting/89/agenda.html 
https://datatracker.ietf.org/meeting/89/agenda.txt 

More information regarding IETF 89 in London, England is located here: https://www.ietf.org/meeting/89/index.html 

Thank you! 

IETF Secretariat 

From randy@psg.com  Fri Jan 31 17:35:46 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5111ACCDE for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 17:35:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nCtHbdc0C7EK for <ietf@ietfa.amsl.com>; Fri, 31 Jan 2014 17:35:46 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 03F451ACCDC for <ietf@ietf.org>; Fri, 31 Jan 2014 17:35:46 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1W9PUj-0002DX-4E; Sat, 01 Feb 2014 01:35:41 +0000
Date: Sat, 01 Feb 2014 10:35:40 +0900
Message-ID: <m2iosz398z.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: IETF 89 London - Enquiry
In-Reply-To: <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Feb 2014 01:35:47 -0000

> Large chunks of England are underwater=E2=80=A6=20

oh, you meant the weather ...
