No abstract

No abstract

Dedicated Short-Range Communications (DSRC) has been designed to support vehicular communications. In the U.S., DSRC operates in the 5.9 GHz licensed spectrum band. Its physical (PHY) and medium access control (MAC) layers, defined in the IEEE 802.11p standard, are based on the IEEE 802.11 family of Wi-Fi standards. Vehicular communication environments differ significantly from the sparse and low-velocity nomadic use cases of a typical Wi-Fi deployment. Thus, there are many challenges to adapt Wi-Fi technologies to support the unique requirements of vehicular communications such as achieving high and reliable performance in highly mobile, often densely populated, and frequently non-line-of-sight environments. The automotive and the communications industries, academia, and governments around the world have been devoting tremendous efforts to address these challenges, and significant achievements have been made. Remaining challenges can be addressed by the future versions of DSRC. In this paper, we investigate the current technologies used by DSRC to support vehicle safety communications, analyze existing and possible DSRC performance enhancements that can be realized in the near term, and provide a few initial thoughts on the DSRC evolution path.

Routing protocols have been extended over time to use cryptographic mechanisms to ensure that data received from a neighboring router has not been modified in transit and actually originated from an authorized neighboring router.

No abstract

No abstract

Considerations in Validating the Path in BGP Status of This MemoThis memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. IESG NoteAfter consultation with the RPSEC WG, the IESG thinks that this work is related to IETF work done in WG RPSEC, but this does not prevent publishing.This RFC is not a candidate for any level of Internet Standard. The IETF disclaims any knowledge of the fitness of this RFC for any purpose and in particular notes that the decision to publish is not based on IETF review for such things as security, congestion control, or inappropriate interaction with deployed protocols. The RFC Editor has chosen to publish this document at its discretion. Readers of this document should exercise caution in evaluating its value for implementation and deployment. See RFC 3932 for more information. AbstractThis document examines the implications of hop-by-hop forwarding, route aggregation, and route filtering on the concept of validation within a BGP Autonomous System (AS) Path.

This document describes a backward-compatible technique that may be used by OSPF (Open Shortest Path First) implementations to advertise a router's unavailability to forward transit traffic or to lower the preference level for the paths through such a router. This document obsoletes RFC 3137. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6987. Retana, et al.