Re: [Pppext] Review of draft-bberry-rfc4938bis-00.txt

Frank Solensky <fsolensky@juniper.net> Mon, 01 December 2008 15:51 UTC

Return-Path: <pppext-bounces@ietf.org>
X-Original-To: pppext-archive@megatron.ietf.org
Delivered-To: ietfarch-pppext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7D1E03A6AD0; Mon, 1 Dec 2008 07:51:31 -0800 (PST)
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 E10E33A6AD0 for <pppext@core3.amsl.com>; Mon, 1 Dec 2008 07:51:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3mEKm2e2TWQd for <pppext@core3.amsl.com>; Mon, 1 Dec 2008 07:51:29 -0800 (PST)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by core3.amsl.com (Postfix) with ESMTP id 14D483A6A6D for <pppext@ietf.org>; Mon, 1 Dec 2008 07:51:28 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKSTQH8ZOZsoX925jjV6sIjH/Apzvpug0b@postini.com; Mon, 01 Dec 2008 07:51:25 PST
Received: from p-emfe01-sac.jnpr.net (66.129.254.72) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server id 8.1.311.2; Mon, 1 Dec 2008 07:48:40 -0800
Received: from p-emsmtp03.jnpr.net ([66.129.254.54]) by p-emfe01-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Dec 2008 07:48:40 -0800
Received: from emailwf1.jnpr.net ([10.10.2.33]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 1 Dec 2008 07:48:39 -0800
Received: from emailwf2.jnpr.net ([10.10.2.32]) by emailwf1.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 1 Dec 2008 10:48:38 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 1 Dec 2008 10:48:37 -0500
Message-ID: <0BC95DB6A6B8CE4FA9BD494477FAFE6A017D3FC7@emailwf2.jnpr.net>
In-Reply-To: <491C9E43.3090406@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Pppext] Review of draft-bberry-rfc4938bis-00.txt
Thread-Index: AclF2DSEDr+LkjljR2m1baxNbV2MtgN85JIg
References: <491C9E43.3090406@cisco.com>
From: Frank Solensky <fsolensky@juniper.net>
To: "Mark Townsley" <townsley@cisco.com>, <pppext@ietf.org>, <draft-bberry-rfc4938bis@tools.ietf.org>
X-OriginalArrivalTime: 01 Dec 2008 15:48:38.0645 (UTC) FILETIME=[4700FA50:01C953CC]
Subject: Re: [Pppext] Review of draft-bberry-rfc4938bis-00.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: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pppext-bounces@ietf.org
Errors-To: pppext-bounces@ietf.org

Just the concern I had mentioned in September about including options in
the session packets.  As Stan Ratliff noted, though, that was already in
4938 so there's no clean way to fix that.  

> -----Original Message-----
> From: pppext-bounces@ietf.org [mailto:pppext-bounces@ietf.org] On
Behalf
> Of Mark Townsley
> Sent: Thursday, November 13, 2008 4:38 PM
> To: pppext@ietf.org; draft-bberry-rfc4938bis@tools.ietf.org
> Subject: [Pppext] Review of draft-bberry-rfc4938bis-00.txt
> 
> 
> pppext folks,
> 
> draft-bberry-rfc4938bis-00.txt has been submitted to the RFC Editor as
> an independent submission, thus not an IETF consensus document in any
> way. However, as with other pppoe documents, I would like pppext to
take
> a look at it and provide any comments to the authors here.  Unless I
> hear otherwise from the authors or a revision is needed and not ready
in
> time, the document will be on the Dec 4 IESG telechat, so please
submit
> any comments by that time.
> 
> Thanks in advance all,
> 
> - Mark
> _______________________________________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/listinfo/pppext
_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www.ietf.org/mailman/listinfo/pppext