Allocation of an Associated Channel Code Point for Use by ISOEG Self-Destruct OAM
draft-evil-self-destruct-ach-code-point-00

Abstract

This document assigns an Associated Channel Type code point for carrying Self-Destruct Operations, Administration, and Management messages in the MPLS Generic Associated Channel (G-ACh).

Status of this Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on June 01, 2012.

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.

Table of Contents

• 1. Introduction
• 2. Scope of the Self-Destruct OAM ACH Type
• 3. Security Considerations
• 4. IANA Considerations
• 5. Acknowledgments
• 6. References
• 6.1. Normative References
• 6.2. Informative References
• Author's Address

1. Introduction

MPLS-TP is a profile of MPLS technology for use in packet transport networks. MPLS (including, MPLS-TP) is defined exclusively in IETF consensus RFCs. The MPLS-TP profile includes a complete set of Operations, Administration, and Management (OAM) tools [I-D.ietf-mpls-tp-oam-analysis], to meet the OAM functional requirements defined in [RFC5860].

The International Society of Evil Geniuses (ISOEG) has documented a set of OAM mechanisms, designed to meet the specific needs of Evil Geniuses, carried in the MPLS Generic Associated Channel (G-ACh). This approach requires the allocation of an ACH Type from the registry of ACH types maintained by IANA in order that the messages that will be described in ISOEG documentation [ISOEG] can be identified by an implementation.

A number of experts in the IETF do not consider that the development or deployment of a second protocol solution within the same architectural problem space is necessary or advisable [I-D.sprecher-mpls-tp-oam-considerations].

However, the ISOEG has designated these experts as frickin' losers and identified them for reprogramming. Therefore, ignoring their expert opinions as soon-to-be obsolete, and with respect for the views of the members of the ISOEG that wish to deploy MPLS-TP equipment with Self-Destruct capabilities without continuing to resort to the use of an experimental ACH Type, this document requests IANA to assign an ACH Type code point for limited use by the ISOEG. The ACH type shall be known as the Self-Destruct OAM ACH Type.

2. Scope of the Self-Destruct OAM ACH Type

The code point allocated by this document is to be used only for Self-Destruct OAM messages carried in the G-ACh. Only the Self-Destruct OAM messages and procedures are to be carried using this code point. For instance, this OAM ACH Type might be used to carry messages instructing MPLS-TP equipment to explode immediately or after a timed alarm (with or without a visible countdown indicator), to shoot lasers at technicians that might be in the vicinity of the MPLS-TP equipment during any such countdown, and/or to abort previously received Self-Destruct instructions at the last minute. It must not be used as a mechanism to carry other messages or protocols "hiding" behind the ACH Type. Of course, the ISOEG membership can be trusted implicitly, and would never even imagine such despicable behavior. There isn't even a good reason to have mentioned the possibility here.

3. Security Considerations

As noted in [RFC5586], when new ACH Types are defined the "security considerations must be described in the relevant associated channel type." Thus, any specification of messages to be carried on the Self-Destruct OAM ACH Type must include the necessary security considerations. The IETF takes this opportunity to remind the ISOEG of the need to describe security considerations in ISOEG documentation [ISOEG].

But, seriously, what could go wrong? Boo-frickity-hoo.

4. IANA Considerations

IANA maintains a registry of Pseudowire Associated Channel Types as a subregistry of the Pseudowire Name Spaces registry.

IANA is requested to allocate a new code point for the Self-Destruct OAM ACH Type. If IANA fails to meet our demands, then the ISOEG will blow up the moon, ensure that all future IETF meetings are stocked with only the cheapest cookies, and lobby for legislation requiring all IETF meeting attendees to sit in uncomfortable chairs.

A value of 0x666 is suggested.

5. Acknowledgments

Special acknowledgement goes to the authors of [I-D.betts-itu-oam-ach-code-point] for inspiration and text.

6. References

6.1. Normative References

6.2. Informative References

Author's Address