
From carlsonj@workingcode.com  Thu Jun  3 13:57:33 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6EFD13A6A33 for <pppext@core3.amsl.com>; Thu,  3 Jun 2010 13:57:33 -0700 (PDT)
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_50=0.001, GB_I_INVITATION=-2, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id et57LZ+EgerV for <pppext@core3.amsl.com>; Thu,  3 Jun 2010 13:57:32 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 1F8153A6A2A for <pppext@ietf.org>; Thu,  3 Jun 2010 13:57:32 -0700 (PDT)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o53Kv767022501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pppext@ietf.org>; Thu, 3 Jun 2010 16:57:07 -0400 (EDT)
Message-ID: <4C081723.7000408@workingcode.com>
Date: Thu, 03 Jun 2010 16:57:07 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: pppext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Subject: [Pppext] IETF 78 - Meeting and Sponsorship Information
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jun 2010 20:57:33 -0000

I've been asked to forward this message along to the working group so
that folks know about the sponsorship opportunities.  Note that I know
of no requests to have the PPP Extensions working group meet, nor do I
have any current plans to hold working group meetings in Maastricht.



78th IETF Meeting
Maastricht, Netherlands
July 25-30, 2010

1. Sponsorship Opportunities
2. Registration Types
3. Visas and Letters of Invitation
4. Accommodations & Breakfast Information
5. IETF 79 (Beijing) Visa Information

1) Sponsorship Opportunities
There are still sponsorship opportunities and benefits for high profile
company/organizational exposure at the upcoming IETF meeting in
Maastricht, Netherlands from July 25-30, 2010.  All sponsorship fees go
directly to fund the operations of the IETF.  See the options at:
http://www.ietf.org/meeting/78/index.html "Sponsorship Opportunities"
under "General."  Each of the sponsorship options provide extended and
repeat exposure at this weeklong meeting.

Please contact Drew Dvorshak, dvorshak@isoc.org, with any questions
and/or to reserve your organization's spot.  Thanks in advance for
supporting the critical work of the IETF!

2) Register online at:  http://www.ietf.org/meetings/78/

3) Letters of Invitation and Visas
Letters of Invitation
After you complete the meeting registration process, you will be given the
option to request a letter of invitation. You can request the Letter of
Invitation as soon as you finish registration, or at a later time by
following the link provided in the confirmation email.

Visas
Please check the Netherlands Ministry of Foreign Affairs site
(http://www.minbuza.nl/en/Services/Consular_Services/Visa) for list of
countries with visa exemptions.

We recommend you give yourself at least one month to complete the visa
process.

4) Accommodations & Breakfast Information
http://www.ietf.org/meeting/78/hotel.html

5) If you want to start planning for your trip to IETF 79 in Beijing, we
have visa information online here:
http://www.ietf.org/meeting/79/visa.html

Only 52 days until IETF 78!

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

From d3e3e3@gmail.com  Fri Jun  4 18:36:49 2010
Return-Path: <d3e3e3@gmail.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 922D53A680E for <pppext@core3.amsl.com>; Fri,  4 Jun 2010 18:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.042
X-Spam-Level: 
X-Spam-Status: No, score=-0.042 tagged_above=-999 required=5 tests=[AWL=-0.044, BAYES_50=0.001, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01YbyxVN7zfn for <pppext@core3.amsl.com>; Fri,  4 Jun 2010 18:36:48 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 585823A6803 for <pppext@ietf.org>; Fri,  4 Jun 2010 18:36:48 -0700 (PDT)
Received: by wyf23 with SMTP id 23so1311947wyf.31 for <pppext@ietf.org>; Fri, 04 Jun 2010 18:36:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=pa1GYk1lG1ZiHtDrco4oNtjCYF3lOnrPKZpppbzE+ac=; b=h0TSN249JLx/h5A942bhfXf0SLdYOfpbTXepXxL63f6eWdXOBktMPYg0ghtG7jIbi3 hT3qaqykOJ6H+LlMiA6yuFBMcsnl2gcaaAPJ5pYJumabAzRniad5kg9QW4jfBZd+If0a Iu4m3ZWwBpWIYEaL3iRrHuijkFbXKKjJof2F0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=URb6VM2/Y5qZi87M5B0kM0mepcx4YqmfYYg7DBl7wgK525aQpWCutHVP9P42DdongM REMyW/EU20a+xoofa47O9960aNoPnSIwehVSmio6ectG12AeyPxn76zIsAcYuBMQEdQh FeQS9v5TBQeFSMEjhzSmwfVWJOVIR4VWmCaHo=
MIME-Version: 1.0
Received: by 10.216.86.19 with SMTP id v19mr255254wee.89.1275701791251; Fri,  04 Jun 2010 18:36:31 -0700 (PDT)
Received: by 10.216.229.210 with HTTP; Fri, 4 Jun 2010 18:36:31 -0700 (PDT)
In-Reply-To: <4BFFAB96.6080606@workingcode.com>
References: <20100527164502.B487E3A6AFA@core3.amsl.com> <AANLkTikjeRk-3f7NCs6UoqRzNJRGPMvvk2TngTM6fthG@mail.gmail.com> <4BFFAB96.6080606@workingcode.com>
Date: Fri, 4 Jun 2010 21:36:31 -0400
Message-ID: <AANLkTimCFGB8tPJauq7AZF8W9hCP1MrmoSSs0J-TUOO2@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: multipart/alternative; boundary=0016e6d99bfe1b5e0004883e7809
Cc: pppext@ietf.org
Subject: Re: [Pppext] I-D Action:draft-ietf-pppext-trill-protocol-01.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2010 01:36:49 -0000

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

On Fri, May 28, 2010 at 7:40 AM, James Carlson <carlsonj@workingcode.com>wrote:

> On 05/27/10 23:45, Donald Eastlake wrote:
> > Hi,
> >
> > Although I am not a PPP expert, I think this draft looks pretty good.
> > Now that TRILL has been approved as a Proposed Standard,  I think this
> > draft should be advanced.
> >
> > However, I do have a question on one sentence:
> > In Section 3 on Page 4, numbered item 2, the following sentence occurs:
> >                If the peer is an RBridge, then there is no need to
> >       pass unencapsulated frames nor to any TRILL-ignorant peer to be
> >       concerned about.
> >
> > I assume that most of the end of this sentence shouldn't be there...
>
> I think there's just an extra word in the sentence (s/nor to/nor/).  It
> reads better as:
>
>        If the peer is an RBridge, then there is no need to
>         pass unencapsulated frames, as the link can have no TRILL-
>         ignorant peer to be concerned about.
>
> The point of sending unencapsulated is to make sure that TRILL-ignorant
> nodes are able to see the traffic.  But, since this is point-to-point,
> we can be certain that "everyone" (i.e., the one guy we're sending to)
> knows TRILL.


OK, that one word fix makes sense to me.

Thanks,
Donald

--
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
>

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

<div class=3D"gmail_quote">On Fri, May 28, 2010 at 7:40 AM, James Carlson <=
span dir=3D"ltr">&lt;<a href=3D"mailto:carlsonj@workingcode.com">carlsonj@w=
orkingcode.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On 05/27/10 23:45, Donald Eastlake wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt; Although I am not a PPP expert, I think this draft looks pretty good.<=
br>
&gt; Now that TRILL has been approved as a Proposed Standard, =A0I think th=
is<br>
&gt; draft should be advanced.<br>
&gt;<br>
&gt; However, I do have a question on one sentence:<br>
&gt; In Section 3 on Page 4, numbered item 2, the following sentence occurs=
:<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0If the peer is an RBridge, then there i=
s no need to<br>
&gt; =A0 =A0 =A0 pass unencapsulated frames nor to any TRILL-ignorant peer =
to be<br>
&gt; =A0 =A0 =A0 concerned about.<br>
&gt;<br>
&gt; I assume that most of the end of this sentence shouldn&#39;t be there.=
..<br>
<br>
</div>I think there&#39;s just an extra word in the sentence (s/nor to/nor/=
). =A0It<br>
reads better as:<br>
<div class=3D"im"><br>
 =A0 =A0 =A0 =A0If the peer is an RBridge, then there is no need to<br>
</div> =A0 =A0 =A0 =A0pass unencapsulated frames, as the link can have no T=
RILL-<br>
<div class=3D"im"> =A0 =A0 =A0 =A0ignorant peer to be concerned about.<br>
<br>
</div>The point of sending unencapsulated is to make sure that TRILL-ignora=
nt<br>
nodes are able to see the traffic. =A0But, since this is point-to-point,<br=
>
we can be certain that &quot;everyone&quot; (i.e., the one guy we&#39;re se=
nding to)<br>
knows TRILL.</blockquote><div><br></div><div>OK, that one word fix makes se=
nse to me.=A0</div><div><br></div><div>Thanks,</div><div>Donald</div><div><=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex;">
<font color=3D"#888888">
--<br>
James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 &lt;<a href=
=3D"mailto:carlsonj@workingcode.com">carlsonj@workingcode.com</a>&gt;<br>
</font></blockquote></div><br>

--0016e6d99bfe1b5e0004883e7809--

From carlsonj@workingcode.com  Tue Jun 29 04:45:21 2010
Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4062A3A6ACA for <pppext@core3.amsl.com>; Tue, 29 Jun 2010 04:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYANUKWapeGj for <pppext@core3.amsl.com>; Tue, 29 Jun 2010 04:45:20 -0700 (PDT)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 23E5E3A6AC9 for <pppext@ietf.org>; Tue, 29 Jun 2010 04:45:19 -0700 (PDT)
Received: from [75.150.68.97] (carlson [75.150.68.97]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id o5TBjC32003740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pppext@ietf.org>; Tue, 29 Jun 2010 07:45:12 -0400 (EDT)
Message-ID: <4C29DCC7.7060407@workingcode.com>
Date: Tue, 29 Jun 2010 07:45:11 -0400
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100214 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: pppext@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Subject: [Pppext] draft-ietf-pppext-trill-protocol-01.txt
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jun 2010 11:45:21 -0000

Has anyone else read this?  Are there any other comments on it?

http://www.ietf.org/id/draft-ietf-pppext-trill-protocol-01.txt

I'd like to get this draft moving forward, and it would help if there
were other eyes on the text.

Thanks.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
