Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

Locator

Contact

Ask a Question

Toll Free Numbers

Media Contact

Locator

Hospitals and Clinics

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

Enter your search text

site map [a-z]

More VA

Health
Benefits
Burials & Memorials
About VA
1. Inside VA
2. Budget and Performance
Resources
Media Room
1. Inside the Media Room
2. National Observances
3. Special Events
Locations
Contact Us

TRM

VA TRM Home
Search VA TRM
Technology/Standard List
TRM Reports
Submit Idea to Improve TRM
TRM Glossary
Site Map

VA Technical Reference Model v 24.11

Layer Two Tunneling Protocol (L2TP)

TAGGED ENTRIES

Deselected entries will be removed from the current tag.

Tag Definition

UNSAVED CHANGES

General
Decision
Reference
Component
Category
Analysis

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Layer Two Tunneling Protocol (L2TP) specifies multi-protocol access via point-to-point protocol (PPP). L2TP facilitates the tunneling of PPP packets across an intervening network in a way that is as transparent as possible to both end-users and applications.
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.10
Decision Date:	10/25/2024 at 15:59:20 UTC
Aliases:	RFC 3931; RFC 2661
Introduced By:	TRMSP
Standards Body:	Internet Engineering Task Force (IETF)

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Industry Standard, obtained from the vendor (or from the release source).

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
RFC 2661	08/01/1999
RFC 3931	03/01/2005
RFC 5641	08/01/2009

Current Decision Matrix (10/22/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VAIT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported.

Legend:

White	Authorized: The technology/standard has been authorized for use.
Yellow	Authorized w/ Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Authorized w/ Constraints (POA&M): This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Authorized w/ Constraints (DIVEST): VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unauthorized may be found on the Decision tab for the specific entry.
Black	Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Authorized w/ Constraints (PLANNING/EVALUATION): The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology authorized with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology authorized with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

Any major.minor version that is not listed in the VA Decision Matrix is considered Authorized w/ Constraints (POA&M).

Release	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4	Q1	Q2	Q3	Q4
<Past	CY2019				CY2020				CY2021				Future>
RFC 2661	DIVEST	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
RFC 3931	Approved	Approved	DIVEST	DIVEST	DIVEST	DIVEST	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved	Unapproved
RFC 5641	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved	Approved
Note:	At the time of writing, version RFC 5641 is the most current version, released 08/01/2009.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description

Standard Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Source	Name	Description
No components have been identified for this entry.

VA Categories

View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Security Network Security	Network Intrusion Detection and Prevention

Technologies/Standards Relationships

Implemented By/Verified With:

No technologies have been identified with this standard.

Comparable Standards:

No comparable entries have been identified.

Associated Standards:

Point-to-Point Protocol (PPP) - Authorized w/ Constraints

General Analysis

Adoption Benefits

This is a well-documented standard.
This standard specifies multi-protocol access via point-to-point protocol (PPP).
This standard facilitates the tunneling of point-to-point protocol (PPP) packets across an intervening network in a way that is as transparent as possible to both end-users and applications.

Adoption Risks

There are known Common Vulnerabilities and Exposures (CVEs) associated with this standard. Please see https://nvd.NIST.gov/vuln/search for more details.
There are Threat & Assessment Analysis Portal (TAAP) bulletins associated with this standard.

- The information contained on this page is accurate as of the Decision Date (10/25/2024 at 15:59:20 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (10/22/2024)

References

Standard Components

VA Categories

View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (10/22/2024)

References

Standard Components

VA Categories View the VA Categorization Framework

Technologies/Standards Relationships

Implemented By/Verified With:

Comparable Standards:

Associated Standards:

General Analysis

Adoption Benefits

Adoption Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework