Lines Matching refs:IP
6 COMMERCIAL IP SECURITY OPTION (CIPSO 2.2)
13 IP Security Option (CIPSO). This draft reflects the version as approved by
37 IP datagrams to be labeled with security classifications. This option
110 including the type and length fields. With the current IP header length
146 information relevant to the data in the IP packet. Each tag begins with
154 be guaranteed if CIPSO is not the first IP option.
180 restrictions are based on the current IP limitation of 40 octets for all
181 IP options. If the IP header is later expanded, then the length and count
183 provided for IP options.
229 including the type and length fields. With the current IP header length
315 including the type and length fields. With the current IP header length
378 including the type and length fields. With the current IP header length
432 host is defined to be the origination or destination system for an IP
433 datagram. A CIPSO gateway provides IP routing services between two or more
434 IP networks and may be required to perform label translations between
437 router is a dedicated IP router that routes IP datagrams between two or more
438 IP networks.
496 particular IP network address. All CIPSO labels within datagrams destined
497 for the particular IP network MUST use the specified DOI identifier. All
502 particular IP host address. All CIPSO labels within datagrams destined for
503 the particular IP host will use the specified DOI identifier. All CIPSO
554 outgoing IP datagrams. Just providing the correct CIPSO label format
577 recognized the IP datagram is discarded and an ICMP "parameter problem"
603 IP packet because it is too large to fit in the IP options area.
624 assigned to that network port and associated with all unlabeled IP
677 ensure that at least one DOI is common within an IP network to allow for
678 broadcasting of IP datagrams.
693 a. Use the CIPSO label of the original IP datagram
712 IP Security Option at the INTEROP 89, Commercial IPSO Workshop.
737 RFC 1038, "Draft Revised IP Security Option", M. St. Johns, IETF, January