From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Feb 18 2005 - 23:37:47 GMT-3
<rfc2385>
2.0 Proposal
Every segment sent on a TCP connection to be protected against
spoofing will contain the 16-byte MD5 digest produced by applying the
MD5 algorithm to these items in the following order:
1. the TCP pseudo-header (in the order: source IP address,
destination IP address, zero-padded protocol number, and
segment length)
2. the TCP header, excluding options, and assuming a checksum of
zero
3. the TCP segment data (if any)
4. an independently-specified key or password, known to both TCPs
and presumably connection-specific
</rfc2385>
http://www.internetworkexpert.com/rfc/rfc2385.txt
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> nettable_walker
> Sent: Friday, February 18, 2005 5:37 PM
> To: ccielab@groupstudy.com
> Subject: how is the BGP authintication hash created ?
>
> Can someone point me to the URL for this ?
>
> Thanks,
>
> R
>
>
This archive was generated by hypermail 2.1.4 : Thu Mar 03 2005 - 08:51:23 GMT-3