[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

GRE Extensions (Modified)

To: Gopal Dommety <gdommety@cisco.com>
Subject: GRE Extensions (Modified)
From: Pete McCann <mccap@research.bell-labs.com>
Date: Fri, 17 Mar 2000 09:16:36 -0600 (CST)
Cc: gre@ops.ietf.org, udlr@sophia.inria.fr, msdp@antc.uoregon.edu, ipsec@lists.tislabs.com, MOBILE-IP@STANDARDS.NORTELNETWORKS.COM, l2tp@ipsec.org, tsgp@3gpp2.org, tsga@3gpp2.org
In-Reply-To: <200003170853.AAA15902@omega.cisco.com>
References: <200003170853.AAA15902@omega.cisco.com>
Sender: owner-ipsec@lists.tislabs.com


The sequence number should definitely be per key!  That way we can
tunnel multiple streams, one per key.  Each needs its own sequencing.

-Pete

Gopal Dommety <gdommety@cisco.com> (GD) writes:

GD> Hello:
GD> I have changed the sequence no  to be 4 bytes.  The changes request by
GD> most have been made.

GD> A remining issue is regarding  the behaviour when both sequence no and
GD> the Key are present. There are two options:

GD> 1. Have sequence no  per Key.  This will give  better granularity with
GD>    added complexity of implementation.

GD> 2. Sequence no for the tunnel irrespective of the Key.

References:

GRE Extensions (Modified)

From: Gopal Dommety <gdommety@cisco.com>

Prev by Date: GRE Extensions (Modified)
Next by Date: Re: GRE Extensions (Modified)
Prev by thread: GRE Extensions (Modified)
Next by thread: Re: GRE Extensions (Modified)
Index(es):
- Main
- Thread