RE: [L2tpext] Why 2 AVPs?

"Glen Zorn" <gwz@cisco.com> Fri, 07 June 2002 02:52 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28808 for <l2tpext-archive@odin.ietf.org>; Thu, 6 Jun 2002 22:52:14 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17318; Thu, 6 Jun 2002 22:39:19 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id WAA17291 for <l2tpext@optimus.ietf.org>; Thu, 6 Jun 2002 22:39:17 -0400 (EDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27981 for <l2tpext@ietf.org>; Thu, 6 Jun 2002 22:38:45 -0400 (EDT)
Received: from GWZW2K (sjc-vpn1-730.cisco.com [10.21.98.218]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id TAA16489; Thu, 6 Jun 2002 19:38:46 -0700 (PDT)
Reply-To: gwz@cisco.com
From: Glen Zorn <gwz@cisco.com>
To: Wei Luo <luo@cisco.com>, l2tpext@ietf.org
Subject: RE: [L2tpext] Why 2 AVPs?
Date: Thu, 06 Jun 2002 19:38:42 -0700
Message-ID: <LMEEIEAEKIEGIECKAPBHIEGDCJAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
In-Reply-To: <3D00123A.8351D38D@cisco.com>
Content-Transfer-Encoding: 7bit
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
X-BeenThere: l2tpext@ietf.org
Content-Transfer-Encoding: 7bit

Wei Luo [mailto://luo@cisco.com] writes:

> At one point, people wanted to have the session DS AVP carried in
> control channel messages as well to indicate the specified DS value
> should be applied to all sessions of the same control channel.  Whereas,
> the control connection DS AVP is solely for the control channel.
> Therefore, there was a need to differentiate the two.  That idea didn't
> fly too long however, but we left them as they are for clarity purpose.

OK.  The reason I'm asking is that I'm working on an update to RFC 2868 that
includes a DS-related attribute, so the question is, should there be 1
attribute or 2?

>
> ---Wei
>
> > -------- Original Message --------
> > Subject: [L2tpext] Why 2 AVPs?
> > Date: Wed, 5 Jun 2002 23:03:28 -0700
> > From: "Glen Zorn" <gwz@cisco.com>
> > Reply-To: <gwz@cisco.com>
> > To: <l2tpext@ietf.org>
> >
> > Just looking at draft-ietf-l2tpext-ds-05.txt and wondering why
> there are two
> > identical AVPs defined, since the only differences between them
> seem to be
> > semantic & they occur is disjunct sets of messages...
> >
> > _______________________________________________
> > L2tpext mailing list
> > L2tpext@ietf.org
> > https://www1.ietf.org/mailman/listinfo/l2tpext
>
> _______________________________________________
> L2tpext mailing list
> L2tpext@ietf.org
> https://www1.ietf.org/mailman/listinfo/l2tpext
>
>



_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext