Content deleted Content added
m BOT - updating merge tag |
m Anohthterwikipedian moved page Security Parameter Index to Security Parameters Index: Requested by Datalouie at WP:RM/TR: The RFCs (at least the modern / non-obsolete ones) consistently write out SPI as "Security Parameters Index", note the plural Parameters. The Wikipedia IPSec article also does so, except when referring to this SPI article specifically. |
||
| (33 intermediate revisions by 29 users not shown) | |||
Line 1:
{{Multiple issues|
{{More citations needed|date=January 2017}}
{{Notability|date=February 2015}}
}}
The '''Security Parameter Index''' (SPI) is an identification tag added to the header while using [[
The SPI (as per RFC 4301) is a required part of an IPsec [[Security Association]] (SA) because it enables the receiving system to select the SA under which a received packet will be processed.{{Ref RFC|4301}} An SPI has only local significance, since it is defined by the creator of the SA; an SPI is generally viewed as an opaque bit string. However, the creator of an SA may interpret the bits in an SPI to facilitate local processing.
This works like port numbers in TCP and UDP connections. What it means is that there could be different SAs used to provide security to one connection. An SA could therefore act as a set of rules.
{{compu-stub}}▼
Carried in [[IPsec#Encapsulating Security Payload|Encapsulating Security Payload (ESP)]] header or [[IPsec#Authentication Header|Authentication Header (AH)]], its length is 32 bits.<ref>{{Cite journal|url=https://tools.ietf.org/html/rfc4303#section-2.1|title = IP Encapsulating Security Payload (ESP)|date = December 2005|last1 = Kent|first1 = Stephen| doi=10.17487/RFC4303 |url-access = subscription}}</ref>
==References==
{{Reflist}}
[[Category:IPsec]]
[[Category:Internet protocols]]
| |||