Re: [core] [Yot] YANG notification within CoMI

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 09 June 2018 13:20 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6D7130DFF; Sat, 9 Jun 2018 06:20:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 fdpJdIBWjtN5; Sat, 9 Jun 2018 06:20:57 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1512129C6B; Sat, 9 Jun 2018 06:20:57 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1AFFA20090; Sat, 9 Jun 2018 09:34:32 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 421953100; Sat, 9 Jun 2018 09:18:03 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4030F2E8A; Sat, 9 Jun 2018 09:18:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Michel Veillette <Michel.Veillette@trilliant.com>
cc: Peter van der Stok <stokcons@bbhmail.nl>, Andy Bierman <andy@yumaworks.com>, Alexander Pelov <a@ackl.io>, "Eric Voit \(evoit\)" <evoit@cisco.com>, Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "yot\@ietf.org" <yot@ietf.org>, Core <core@ietf.org>
In-Reply-To: <DM5PR06MB2777CAB016D2789C4F1DD67F9A7B0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <DM5PR06MB2777CAB016D2789C4F1DD67F9A7B0@DM5PR06MB2777.namprd06.prod.outlook.com>
X-Mailer: MH-E 8.6; nmh 1.7+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, 09 Jun 2018 09:18:03 -0400
Message-ID: <14497.1528550283@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/xPr9LtKDi2LAki4768mj-L7OotM>
Subject: Re: [core] [Yot] YANG notification within CoMI
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Jun 2018 13:21:00 -0000

Why would a COMI client be behind a load balancer?

(I can't understand why some ports on such a machine might be subject to
load balancing, but why the CoMI communications?)

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [