Re: [Ietf-message-headers] Configuration-Context header registration request

Andrii Berezovskyi <> Thu, 14 October 2021 13:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3667F3A0900 for <>; Thu, 14 Oct 2021 06:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7H1fWk-UqM8U for <>; Thu, 14 Oct 2021 06:39:58 -0700 (PDT)
Received: from ( [IPv6:2001:6b0:1:1200:250:56ff:fead:963e]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A4A053A08EB for <>; Thu, 14 Oct 2021 06:39:57 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4HVVrV1P3FzPR46 for <>; Thu, 14 Oct 2021 15:39:54 +0200 (CEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 4HVVrV1P3FzPR46
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.922.13; Thu, 14 Oct 2021 15:39:53 +0200
Received: from ([]) by ([]) with mapi id 15.02.0922.013; Thu, 14 Oct 2021 15:39:53 +0200
From: Andrii Berezovskyi <>
To: "" <>
Thread-Topic: [Ietf-message-headers] Configuration-Context header registration request
Thread-Index: AQHXwQD43SY392r570CilDYw+xLkKw==
Date: Thu, 14 Oct 2021 13:39:53 +0000
Message-ID: <>
Accept-Language: en-GB, en-US, sv-SE
Content-Language: en-GB
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Ietf-message-headers] Configuration-Context header registration request
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Oct 2021 13:40:05 -0000

My apologies, I just checked the web archive to ensure my letter was received and noticed that the process for registration has changed, as indicated by Julian Reschke. I will follow and to file a correct application. Thank you.


On 2021-10-14, 15:34, "Ietf-message-headers on behalf of Andrii Berezovskyi" < on behalf of> wrote:


    OASIS Open Services for Lifecycle Collaboration (OSLC) Open Project (OP) would like to submit the following registration request:

    Header field name: Configuration-Context

    Applicable protocol: http (RFC 2616 and its successors)

        provisional (in active use since ca. 2009, OASIS OSLC Configuration Management specification is standards-track, standard status will be requested for the header once OASIS Standard version is reached for the specification)

    Author/Change controller:
        OASIS (can be Chet Ensign or the OASIS OSLC OP Project Governing Board (PGB) itself)

    Specification document(s): (ABNF definition in §4, Part 3; Project Specification Draft 01 approved by a vote on 2021-10-02)

    Related information: for tracking this request on the OSLC side.

    Answers to the considerations in

    1) The header is a single value.
    2) The header only has defined semantics for requests.
    3) Servers do not store the header on PUT requests. However, server PUT behavior may vary under different header values.
    4) Field semantics do not change depending on context, the field itself defines a context.
    5) The field does not affect the HTTP connection, no need to include it in the 'Connection' header.
    6) Intermediaries SHALL NOT modify or delete this field, it's inseparable from the request body. In rare cases, intermediaries (proxies) may set a default value for compatibility reasons.
    7) Yes, it makes sense to include this header in the Vary response header field.
    8) This header is not useful in trailers.
    9) The header is ought to be preserved in redirects.
    10) The header does not introduce additional security considerations. However, its nature is to denote a context and it may be used to correlate the belonging of multiple resources to a single context.

    Thank you kindly for your time and the consideration of our application.

    Best regards,
    Andrew Berezovskyi

    OSLC OP PGB co-chair

    Ietf-message-headers mailing list