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

Re: traffic type header

To: ipsec@TIS.COM, smb@research.att.com
Subject: Re: traffic type header
From: braden@isi.edu
Date: Sun, 3 Mar 96 12:16:08 PST
Cc: braden@isi.edu, minshall@ipsilon.com
MMDF-Warning: Parse error in original version of preceding line at neptune.TIS.COM
Posted-Date: Sun, 3 Mar 96 12:16:08 PST
Sender: ipsec-request@neptune.tis.com


  *> From smb@research.att.com Mon Feb 26 19:49:50 1996
  *> From: smb@research.att.com
  *> To: ipsec@tis.com
  *> Subject: traffic type header
  *> Cc: braden@ISI.EDU, minshall@ipsilon.com
  *> Date: Mon, 26 Feb 96 22:44:47 EST
  *> Content-Length: 1551
  *> X-Lines: 36
  *> 
  *> The suggestion has been made that we should have an optional traffic type header.
  *> That is, we need something that will disclose protocol and port numbers.  The
  *> purpose would be (a) to permit traffic measurements, and (b) to permit routers
  *> to optimize their handling of certain kinds of traffic.

and (c) support integrated services, in particular RSVP.

Bob Braden

Prev by Date: Re: (IMPORTANT) Call for AH-MD5 and ESP-DES to move forward
Next by Date: Re: An observation or two
Prev by thread: bump-in-the-stack encryptor paper
Next by thread: Re: An observation or two
Index(es):
- Main
- Thread