[Anima-signaling] what is M_REQ_SYN?
Michael Richardson <mcr+ietf@sandelman.ca> Sun, 09 October 2016 02:26 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: anima-signaling@ietfa.amsl.com
Delivered-To: anima-signaling@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5DFD129442 for <anima-signaling@ietfa.amsl.com>; Sat, 8 Oct 2016 19:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.897
X-Spam-Level:
X-Spam-Status: No, score=-4.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-2.996, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ml9jBuc0xEj5 for <anima-signaling@ietfa.amsl.com>; Sat, 8 Oct 2016 19:26:47 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11392129468 for <anima-signaling@ietf.org>; Sat, 8 Oct 2016 19:26:46 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 95A482009E; Sat, 8 Oct 2016 22:40:47 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9DA286392D; Sat, 8 Oct 2016 22:26:44 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>, anima-signaling <anima-signaling@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Sat, 08 Oct 2016 22:26:44 -0400
Message-ID: <30942.1475980004@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima-signaling/RGBwF1EOuwJaE4K2yUDSyjAAs1k>
Subject: [Anima-signaling] what is M_REQ_SYN?
X-BeenThere: anima-signaling@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list for the signaling design team of the ANIMA WG <anima-signaling.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima-signaling/>
List-Post: <mailto:anima-signaling@ietf.org>
List-Help: <mailto:anima-signaling-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima-signaling>, <mailto:anima-signaling-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Oct 2016 02:26:48 -0000
Section 3.7.5 neglects to say what REQ_SYN does. Maybe that is said elsewhere... It also implies (probably old working) that perhaps one would not set a negotiation timer when one uses REQ_SYN by talking about REQ_NEG only... 3.7.5. Request Messages In fragmentary CDDL, Request Negotiation and Request Synchronization messages follow the patterns: request-negotiation-message = [M_REQ_NEG, session-id, objective] request-synchronization-message = [M_REQ_SYN, session-id, objective] -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- [Anima-signaling] what is M_REQ_SYN? Michael Richardson
- Re: [Anima-signaling] what is M_REQ_SYN? Brian E Carpenter