Skip to main content

IPR Search

The material posted as IPR disclosures should be viewed as originating from the source of that information, and any issue or question related to the material should be directed to the source rather than the IETF. There is no implied endorsement or agreement by the IETF, the IESG or any other IETF entities with any of the material.

Back

Document IPR search results
draft-ietf-tcpm-rfc793bis

Total number of IPR disclosures found: 0.

Total number of documents searched: 22.

Date ID Statement
Results for RFC 1948 ("Defending Against Sequence Number Attacks")
No IPR disclosures have been submitted directly on RFC 1948.
Results for draft-rfced-info-bellovin ("Defending Against Sequence Number Attacks"), which was obsoleted by draft-ietf-tcpm-rfc1948bis ("Defending against Sequence Number Attacks")
No IPR disclosures have been submitted directly on draft-rfced-info-bellovin.
Results for RFC 761 ("DoD standard Transmission Control Protocol"), which was obsoleted by RFC 793 ("Transmission Control Protocol")
No IPR disclosures have been submitted directly on RFC 761.
Results for RFC 793 ("Transmission Control Protocol"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 793.
Results for draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-ietf-tcpm-rfc793bis.
Results for draft-ananth-tcpm-persist ("Clarification of sender behaviour in persist condition."), which was replaced by draft-ietf-tcpm-persist ("TCP Sender Clarification for Persist Condition")
No IPR disclosures have been submitted directly on draft-ananth-tcpm-persist.
Results for RFC 9293 ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 9293.
Results for draft-ietf-tcpm-persist ("TCP Sender Clarification for Persist Condition"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-ietf-tcpm-persist.
Results for draft-ietf-tcpm-urgent-data ("On the Implementation of the TCP Urgent Mechanism"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-ietf-tcpm-urgent-data.
Results for RFC 879 ("The TCP Maximum Segment Size and Related Topics"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 879.
Results for RFC 6093 ("On the Implementation of the TCP Urgent Mechanism"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 6093.
Results for draft-xiao-tcp-prec ("TCP Processing of the IPv4 Precedence Field"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-xiao-tcp-prec.
Results for RFC 2873 ("TCP Processing of the IPv4 Precedence Field"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 2873.
Results for RFC 6429 ("TCP Sender Clarification for Persist Condition"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 6429.
Results for STD 7 ("Transmission Control Protocol"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on STD 7.
Results for draft-eddy-rfc793bis ("Transmission Control Protocol Specification"), which was replaced by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-eddy-rfc793bis.
Results for draft-ietf-tcpm-tcpmss ("TCP Options and Maximum Segment Size (MSS)"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-ietf-tcpm-tcpmss.
Results for draft-ietf-tcpm-rfc1948bis ("Defending against Sequence Number Attacks"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on draft-ietf-tcpm-rfc1948bis.
Results for RFC 6528 ("Defending against Sequence Number Attacks"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 6528.
Results for draft-gont-tcpm-urgent-data ("On the implementation of TCP urgent data"), which was replaced by draft-ietf-tcpm-urgent-data ("On the Implementation of the TCP Urgent Mechanism")
No IPR disclosures have been submitted directly on draft-gont-tcpm-urgent-data.
Results for RFC 6691 ("TCP Options and Maximum Segment Size (MSS)"), which was obsoleted by draft-ietf-tcpm-rfc793bis ("Transmission Control Protocol (TCP)")
No IPR disclosures have been submitted directly on RFC 6691.
Results for draft-gont-tcpm-rfc1948bis ("Defending Against Sequence Number Attacks"), which was replaced by draft-ietf-tcpm-rfc1948bis ("Defending against Sequence Number Attacks")
No IPR disclosures have been submitted directly on draft-gont-tcpm-rfc1948bis.
Date ID Statement
2004-05-17 421 Cisco's Statement about IPR Claimed in draft-ietf-tcpm-tcpsecure

Back