Results of IETF-conflict review for draft-tcs-coap-no-response-option-17

The IESG <iesg-secretary@ietf.org> Mon, 18 July 2016 07:12 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 671A412D0F9; Mon, 18 Jul 2016 00:12:50 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: <draft-tcs-coap-no-response-option@ietf.org>, "Nevil Brownlee" <rfc-ise@rfc-editor.org>, <rfc-ise@rfc-editor.org>
Subject: Results of IETF-conflict review for draft-tcs-coap-no-response-option-17
X-Test-IDTracker: no
X-IETF-IDTracker: 6.28.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160718071250.12457.28716.idtracker@ietfa.amsl.com>
Date: Mon, 18 Jul 2016 00:12:50 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/8HTHllMKiF0zxxHtYqZ6N0rFxsM>
Cc: iana@iana.org, The IESG <iesg@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jul 2016 07:12:50 -0000

The IESG has completed a review of draft-tcs-coap-no-response-option-17
consistent with RFC5742.


The IESG has no problem with the publication of 'CoAP option for no
server-response' <draft-tcs-coap-no-response-option-17.txt> as an
Informational RFC.


The IESG has concluded that this work is related to IETF work done in the
CORE Working Group, but this relationship does not prevent publishing.

The IESG would also like the Independent Submissions Editor to review the
comments in the datatracker related to this document and determine
whether or not they merit incorporation into the document. Comments may
exist in both the ballot and the history log.

The IESG review is documented at:
https://datatracker.ietf.org/doc/conflict-review-tcs-coap-no-response-option/

A URL of the reviewed Internet Draft is:
https://datatracker.ietf.org/doc/draft-tcs-coap-no-response-option/

The process for such documents is described at
https://www.rfc-editor.org/indsubs.html 

Thank you,

The IESG Secretary