
From nobody Thu Mar  8 07:30:51 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49E04126CD6 for <dnssd@ietfa.amsl.com>; Thu,  8 Mar 2018 07:30:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 SlYFaz50V_GV for <dnssd@ietfa.amsl.com>; Thu,  8 Mar 2018 07:30:47 -0800 (PST)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 825AE126FDC for <dnssd@ietf.org>; Thu,  8 Mar 2018 07:30:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1520523042; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding; bh=bj0ofgqTgsIER/PuDGcwaWUyt7SzgrqACrDuGA36EeE=; b=Q4IywOe6imLquNcTOts6DcCwE0cCxJdCK2LqnQqVO6eH9qMHhvcjtvLtwjwiIYyJ3leVX+rQXo1xPCUfwtOAGNJcRqqklOVUYElBXE6GBv3SlFrRWjJKLTgzbDkb2mnxXABZEyRM2FIJwnRArgN7v+M4Z5+vTPXtZuyTUkjQn5w=
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-ve1eur03lp0143.outbound.protection.outlook.com [213.199.154.143]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-76-pm1pwkxaO42cdQLDjrnOiw-1; Thu, 08 Mar 2018 15:30:39 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB450.eurprd07.prod.outlook.com (10.242.113.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.567.6; Thu, 8 Mar 2018 15:30:36 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::953d:47a:3277:f42b]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::953d:47a:3277:f42b%5]) with mapi id 15.20.0588.001; Thu, 8 Mar 2018 15:30:36 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: IETF 101, draft meeting agenda
Thread-Index: AQHTtvJof/61boVcPUyXcSopbTeg9A==
Date: Thu, 8 Mar 2018 15:30:36 +0000
Message-ID: <E2D681B4-3B6B-43F2-9444-88BAF838DE29@jisc.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:a88:d510:1101:118a:2821:75bd:181f]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB450; 7:eC374FREtJ0RiopfzFYuAAHV5tQJBj3SD1spFoErN3VGmv3zVH5rQQ7IOMyKL7zS7/CjFjysw2ccKjxpbZtlPFGYv3HKh0N+KqwpJSQw6kM71oJwwz3GNC5V6WeH9Hf1+EOuSdh9y7dc5Id6TPV5ACllVSojY1pX5Qj/uFTSGFogyf14OGViAESA/GqDJsLbr6S5tU6UDlK3Cb+vLE5zeEYLAL1FbQG4wrDL07aPuJTQfgas2fg1by5eC6PARKJm; 20:6u4syQXDY8eIvL8lYS4NbQwtcLnacX+Eq1NWI4QUc7sc0fFaVpN2mUenNBYsjrlUEqBrwATO6f9pCzxqenhYBFGrbWlStN45OT8CX1tUZT3XMR2Wc00fAgHmJvgCRcH1xFFHuJcW4wporDqQdpmdmsVc+25r8JrJ6v5e3PP8yu4=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2c108bf7-7072-49cf-c3f0-08d585098a9c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:AM3PR07MB450; 
x-ms-traffictypediagnostic: AM3PR07MB450:
x-microsoft-antispam-prvs: <AM3PR07MB45004E43FCB96D900D68308D6DF0@AM3PR07MB450.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(209352067349851)(100405760836317); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(3002001)(3231220)(944501244)(52105095)(93006095)(93001095)(10201501046)(6041288)(20161123562045)(20161123564045)(20161123558120)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:AM3PR07MB450; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB450; 
x-forefront-prvs: 060503E79B
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39850400004)(376002)(346002)(366004)(39380400002)(22804003)(189003)(199004)(6916009)(6116002)(2906002)(33656002)(2501003)(316002)(786003)(97736004)(5250100002)(25786009)(5640700003)(5660300001)(105586002)(6436002)(68736007)(3280700002)(6306002)(186003)(53936002)(6512007)(57306001)(6486002)(6506007)(74482002)(2900100001)(59450400001)(102836004)(86362001)(305945005)(966005)(7736002)(50226002)(478600001)(72206003)(14454004)(3660700001)(36756003)(99286004)(83716003)(81156014)(2351001)(46003)(8936002)(8676002)(82746002)(81166006)(106356001)(1730700003); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB450; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
x-microsoft-antispam-message-info: ngjbjIpmEPDWAYqFj31lBzJoWCacD6iwiV3j5Q6k2t5spPUNEYxw+XYexdxBbpzTlS9gOU5svUJuAjf72OsdtfV2D/6nHVemBAIoqbeBMSpiVMtizC6koheOq9JOHs12eMIhfrQgsLa0hNjQmLSt/5+nEO05S/FQRbRdqn6yy1l+Yqbdu+9im5+LPHUmcg/PZKsxe+Mw9Bpx7JPnD93g0E3EqRXff/Yo0MHb06myyPhrkWEmzyeA2cf4JRWACN1A3b3dxLR26Zs6qvqj8aigXOi0XWfx12wuP0lyFcP/VavRaucwUmD2BJDZ9aITelTPACWt/MB0S8tGorQanjYvfw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <1F4013006C12BE43A833757B66F75F59@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 2c108bf7-7072-49cf-c3f0-08d585098a9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2018 15:30:36.8621 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB450
X-MC-Unique: pm1pwkxaO42cdQLDjrnOiw-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/bQ6oIyN8jNtQ5xVqtQ6aE-YfgME>
Subject: [dnssd] IETF 101, draft meeting agenda
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2018 15:30:49 -0000

SGksDQoNClRoZSBkcmFmdCBtZWV0aW5nIGFnZW5kYSBmb3Igb3VyIHNlc3Npb24gaW4gTG9uZG9u
IGlzIGJlbG93LiAgUGxlYXNlIGZlZWwgZnJlZSB0byBjb21tZW50LCBiYXNoLCBldGMuLi4NCg0K
SXQncyBhbHNvIG9ubGluZSBhdCBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcv
MTAxL21hdGVyaWFscy9hZ2VuZGEtMTAxLWRuc3NkDQoNClRpbSANCg0KLS0tLS0NCg0KRE5TU0Qg
V0cgQWdlbmRhDQoNCklFVEYxMDEsIExvbmRvbg0KVGh1cnNkYXksIDIybmQgTWFyY2ggMjAxOA0K
QnVja2luZ2hhbSBSb29tIDA5OjMwIC0gMTI6MDAgbG9jYWwgdGltZQ0KDQpDaGFpcnPigJkgSW50
cm9kdWN0aW9uCQkJCQkJCUNoYWlycywgNSBtaW5zDQoNClN0YXR1cyByZXBvcnQgb24gRE5TIFN0
YXRlZnVsIE9wZXJhdGlvbnMJCQlTdHVhcnQgQ2hlc2hpcmUsIDE1IG1pbnMNCmh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRuc29wLXNlc3Npb24tc2lnbmFsLTA1DQoNClN0
YXR1cyByZXBvcnQgYW5kIG5leHQgc3RlcHMgb24gRE5TIFB1c2ggRGlzY292ZXJ5IFByb3h5IA0K
LSBpbiByZXNwb25zZSB0byBETlMgU3RhdGVmdWwgT3BlcmF0aW9ucyBjaGFuZ2VzCQlTdHVhcnQg
Q2hlc2hpcmUsIDIwIG1pbnMNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LWRuc3NkLXB1c2gtMTMNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWRu
c3NkLWh5YnJpZC0wNw0KDQpVcGRhdGUgdG8gTXVsdGljYXN0IEROUyBEaXNjb3ZlcnkgUmVsYXkJ
CQlUZWQgTGVtb24sICAyMCBtaW5zDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQt
c2N0bC1kbnNzZC1tZG5zLXJlbGF5LTAzDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaWV0Zi1ob21lbmV0LXNpbXBsZS1uYW1pbmctMDENCg0KQ29SRSBSZXNvdXJjZSBEaXNjb3Zl
cnk6IEROUy1TRCBtYXBwaW5nCQkJVEJELCAxNSBtaW5zDQpodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtaWV0Zi1jb3JlLXJkLWRucy1zZC0wMQ0KDQpGdXR1cmUgb2YgJ3BhcmtlZCcg
ZG9jdW1lbnRzCQkJCQlDaGFpcnMsIDEwIG1pbnMNCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1jaGVzaGlyZS1kbnNzZC1yb2FkbWFwLTAwDQpodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtc2N0bC1zZXJ2aWNlLXJlZ2lzdHJhdGlvbi0wMA0KaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LXNjdGwtZGlzY292ZXJ5LWJyb2tlci0wMA0KaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWNoZXNoaXJlLWVkbnMwLW93bmVyLW9wdGlvbi0wMQ0KDQpE
TlMtU0QgUHJpdmFjeSByZXF1aXJlbWVudHMgYW5kIHNjb3BpbmcgZGlzY3Vzc2lvbg0KLSBhaW0g
dG8gYWdyZWUgY29uc2Vuc3VzIG9uIHByb2JsZW1zIHRvIGJlIHNvbHZlZAkJQWxsLCA2MCBtaW5z
DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1kbnNzZC1wcml2YWN5LTAz
IChTZWN0aW9uIDIpDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2hlc2hpcmUt
ZG5zc2QtcHJpdmFjeS1jb25zaWRlcmF0aW9ucy0wMQ0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9o
dG1sL2RyYWZ0LWh1aXRlbWEtZG5zc2QtcHJpdmFjeXNjYWxpbmctMDANCgkJCQkJCQkNClN1bW1h
cnkgb2YgYWN0aW9ucyBhbmQgY2xvc2UJCQkJCUNoYWlycywgNSBtaW5zDQoNCg0K


From nobody Thu Mar  8 21:20:33 2018
Return-Path: <mellon@fugue.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109AA126D05 for <dnssd@ietfa.amsl.com>; Thu,  8 Mar 2018 21:20:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 Iy7FivvM2L8G for <dnssd@ietfa.amsl.com>; Thu,  8 Mar 2018 21:20:23 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D48DC120227 for <dnssd@ietf.org>; Thu,  8 Mar 2018 21:20:22 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id a23so9506868qtn.0 for <dnssd@ietf.org>; Thu, 08 Mar 2018 21:20:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:cc:to; bh=RiaiTGOiRkPI27FxlzsxZDpk44Rw6osNxcRoYt0HkvU=; b=cuvQt6cT+oIa4BCjUsgYjX6w0L+0X2UL4JB+og4940sjZoTGfqoDLTxm0s2OfSuNpH ZNaTrkP18Bka0qKGLhuiCxYeiKMiKL5kRfFoas39gJtJqkGpuNexYvWY8YEnzw1CdhXm ZL0n02UNoZAfTryf3n+aEyGYemsKmQTdE9TSlGIJsJH6oz/+8E5/pJsgxp38nJUjZ/4N oUZODIrdJ6/+iYLfqP2fpXTHJYBYWTaym8iPYHOJi3qsTsQdZ4Pzo7yM5Y0m6wZ2R5fL m550qniGNOgcdh9L0t+SQGgwSHUVPhqU7cSUK8Kq3gjpjab1SxOysEXMy6QdU5jfuIHL 8ElA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=RiaiTGOiRkPI27FxlzsxZDpk44Rw6osNxcRoYt0HkvU=; b=K3tRPkDkHUBeHD5kRwpthrBv6vF8MhNWe3R9pns7bRBGjO1EEUlZX0UOC2UD7NPkos a4R2U/URyDy4xbIwGRtygv99WIIxEW/JCZcZ8tDo9FfrBRhjSH3KAyeVSggcrYkr1DbJ tsuQXR393eMFz+u1+2e969MOHQ75upzpu1EaR3h9cnO/Gh4C1CY1Z+m06nL+bvhtYC1E hx7BLHoG+gARV8vZ+JD82kAVLDVopdtjfq5th+mTf3XFMZyJpbBK604WvUyzEc98a5tn N9an0Vp8jDpwuJWOkLgfF2vViUHrEdN5YAvphmz6kctCXdHnRk6fVn3IjjTELMzYhFBz /jUQ==
X-Gm-Message-State: AElRT7GRkSQD4A8jQQcknTo8L/qcCCs040GQ1avvT5cIhK/RWhEZm3yM m7EpvLqnpA6QiE49Fy7i4nApfw==
X-Google-Smtp-Source: AG47ELs4umZ5ncHAqNSa+W6bwtMXhLd1JdebHYyY+hfpu+LQ9u6Y4PLghspoXwzUoXpXz9PY/zwnCw==
X-Received: by 10.237.46.33 with SMTP id j30mr44769340qtd.26.1520572821322; Thu, 08 Mar 2018 21:20:21 -0800 (PST)
Received: from cavall.lan (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id i185sm167668qkd.30.2018.03.08.21.20.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Mar 2018 21:20:20 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE66BBF5-AD99-490B-8875-EC6628E610CA"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Message-Id: <676A8EDD-2F6D-4A48-82BA-508DE275B20F@fugue.com>
Date: Fri, 9 Mar 2018 00:20:19 -0500
Cc: dnssd@ietf.org
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/PGUxjzK9_-R8Hgerglr8PMyak2s>
Subject: [dnssd] WGLC Updates to draft-ietf-dnsop-session-signal
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2018 05:20:28 -0000

--Apple-Mail=_EE66BBF5-AD99-490B-8875-EC6628E610CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

We have updated draft-ietf-dnsop-session-signal to address the points =
raised during the working group last call, which ended on 2/23.  We've =
already received comments on the new version from Paul Hoffman (thanks =
for that) and will address those as well in a later update.

I've included links to the messages we received during last call and a =
log of the changes we made based on the points raised in those messages =
below.   Thanks to everyone for the thorough reviews=E2=80=94we got lots =
of helpful comments!

---

Jan Komissar: =
https://mailarchive.ietf.org/arch/msg/dnssd/v48k8QbOSN-HtDRFRf20csoq1ZY

1: Should we require TLS?
=20
We entertained this idea, and it would simplify the protocol work, but =
it seems like an overreach for this document.   If we require TLS, we =
are effectively making that a requirement for any DNS-over-TCP =
connection for which session signaling would be useful.   We do not =
believe that we have working group consensus on this point, and =
therefore can't make this move in this document.   If the working group =
wants to require TLS for DNS TCP connections, that should be done in a =
separate document.

Ed Lewis
 https://mailarchive.ietf.org/arch/msg/dnsop/CQ_qRzpm_omXivdY7eELQq-fX5I
 https://mailarchive.ietf.org/arch/msg/dnsop/Iig2nnIvBFsjG5FafKXgpdtBDTw

2: Is the term "session" inappropriate here?

The consensus appears to be that using a different term in order to =
accommodate the OSI layering model, which isn't actually in use, seems =
unnecessary.   We will add text to the document to explicitly state that =
this isn't session in the OSI sense.  Numerous other comments were made =
that asked for clarification on the basis of the assumption that we were =
talking about an OSI-model session; these are all addressed by =
clarifying that we are not.

3: The endpoints - is that the stub resolver and authoritative server =
(on in=E2=80=A8 DNSSEC terms) the signer and the validator?

The text here explicitly refers to a connection between client and =
server; to clarify it to "stub resolver and authoritative server" would =
not be correct, since there are many other "clients" and "servers."   =
For example a full-service cache is a "server" to the stub resolver, and =
a "client" to an authoritative server or upstream forwarder.  RFC 7766 =
currently uses the terms "client" and "server" in the same way, and it's =
not clear how we could further clarify this.

4: This section (4.1) intermingles text on whether or not each DSO =
request elicits a response or not and the process of DSO "session" =
establishment.  With proper editing, these should be separated to lessen =
confusion.

This has been clarified

5: (Section 4.1.1) Requirements (first MUST) and recommendations to =
operate in a certain way tend to become dated quickly.  Instead of =
placing requirements on clients to act good, let the server refuse =
workload.  I am thinking of the issue surrounding the iterations in =
NSEC3 and recent surveys of operators. Despite the documents saying a =
low value is better, operators use high values.

This text is quote from RFC 7766, so updating it would require an update =
to RFC7766.

6: This phrase is confusing and unnecessary "this is a fatal error".  =
The logic to that point is clear that the situation doesn't happen and =
the  prescribed behavior ("close the connection") makes sense.

The term "fatal error" is used throughout the document to mean an error =
that precludes further communication on the connection.   The =
terminology section has been updated to clarify.  =20

7: This is clumsy, when describing the RCODE: "generally set to zero on =
transmission, and silently ignored on reception, except".

This text has been clarified.

8: Perhaps these are not "unacknowledged requests" but "subsequent =
responses".

We had a debate about what the right phrase was to use and settled on =
"unacknowledged messages."   The document has been updated to use this =
phrase consistently, which should lessen the confusion.   "Subsequent =
responses" doesn't really work because an unacknowledged message isn't =
really a response.

9: Do not do name compression!  No No No No.

The reason we don't say this is that TLVs can tunnel DNS messages, and =
this text would require us to uncompress the message before encoding it =
in a TLV.

We have changed the text to be slightly more generic: the content of a =
TLV is opaque and subject to definition of that TLV.   We no longer =
mention DNS name compression at all=E2=80=94since TLVs are opaque blobs, =
no requirements can be placed on what they look like.

10: Unrecognized primary: "I would have thought this would warrant =
tearing down the connection given the words earlier that this ought =
never happen."

We agree, and the document has been updated accordingly.

11:   "The namespaces of 16-bit MESSAGE IDs are disjoint in each =
direction.   For example, it is *not* an error for both client and =
server to send a request message with the same ID."   This will, =
someday, confuse a young and inexperienced DNS hosting engineer.

The reason we wrote this in the spec is so that a young engineer won't =
make that mistake.

We have added some text to clarify that the directionality of the =
message can be considered an extra bit.   There is no way for the server =
and client to know that the other isn't using the same message ID as =
they are composing the message, and the tracking required to prevent =
clashes that theoretically could be prevented would impose a huge amount =
of complexity=E2=80=94this really isn't at all analogous to the key_id =
example.

12: There will be a need to fight cruft, or garbage collect.  Inactive =
objects tend to be forgotten while still using up resources.

If you've got buggy client software that forgets to cancel some =
operation it's going to forget to stop sending renewals as well.  This =
is one reason for having keepalives.

13: I thought that if a connection ends, the DSO session ends.

Correct.

We have changed "reconnect" to "make a new session" which means a new =
connection as well.

14: Sometimes a client can't distinguish this: "If reconnecting to the =
same server," as some server processes have multiple addresses and =
names."

We have stolen the following text from DNS Push and flipped it around to =
change the emphasis:

DNS Updates and DNS Push Notifications may be handled on different ports =
on the same target host, in which case they are not considered to be the =
"same server" for the purposes of this specification, and communications =
with these two ports are handled independently.

The issue is that it's actually a hard problem for the client to know =
that two servers are the same server.   This definition is sufficiently =
constrained that we can imagine a client successfully implementing.   =
Matching IP addresses is too hard.   As a server operator, if you want =
servers to share connections it's your job to set up the server with the =
same host and ports.   The opposite is also true.

15: "The RECOMMENDED value is 10 seconds." Probably a bad idea to codify =
this because implementations will set it to 10 and not scatter it when =
it should be.  (Like closing out many connections in a load-shedding =
panic.)

Instead could say that it's recommended that servers set this value to =
ten seconds when they want the client to reconnect, and refer back to =
the session that has the more general text about this (5.6.1.1).

The text has been updated as suggested=E2=80=94thanks!

Paul Hoffman:
 https://mailarchive.ietf.org/arch/msg/dnsop/PUlnpSfGvZo6cZge476SEWUR7tM

16: The document should explicitly list which protocols are currently =
acceptable, and say that the list can change in the future based on =
standards-track documents.

We do not agree that this should be restricted to standards-track =
documents.   That said, we took the text that Paul kindly provided and =
tweaked it.  Updates to DSO obviously still have to be standards-track.

Paul also sent us comments on the post-WGLC -06 update, which have not =
yet been addressed as of now.  Thanks very much for the quick response, =
Paul!

Stephane Bortzmeyer:
 https://mailarchive.ietf.org/arch/msg/dnssd/NFtd5RGIJhbOnb4Q_dWLwfZmkYg

17: My personal feeling is that it is complicated, with a lot of =
details. May be separating in two documents, one for the base DSO =
concept and one for the standards TLV (with their detailed behavior) =
would have been better.

We don't see any working group consensus on this point, and it seems =
unnecessary.

18: There is a discussion about a possible Privacy section =
<https://github.com/raybellis/draft-bellis-dnsop-session-signal/pull/36> =
for which I suggest the following text: [...]

We started with Stephane's text, and wound up with this:

   When designing new DSO TLVs, the potential for data in the TLV to be
   used as a tracking identifier should be taken into consideration, and
   should be avoided when not required.

   When used without TLS or similar cryptographic protection, a
   malicious entity maybe able to inject a malicious Retry Delay
   Unacknowledged Message into the data stream, specifying an
   unreasonably large RETRY DELAY, causing a denial-of-service attack
   against the client.

This is now in the Security Considerations section, rather than in a =
separate Privacy Considerations section.   We could make it a separate =
section if there is a strong desire to do so, but it seemed unnecessary.

19:  "There are a myriad of other potential use cases for DSO given the =
versatility and extensibility of this specification."   I don't really =
like this sort of sentence. Either we have ideas about these potential =
use cases and we should write them down, or we don't and we should avoid =
this sort of very general words (after all, human imagination being what =
it is, we can be sure surprising use cases will be found.)

We agree and have removed this text.

20:  "If the RCODE is set to any value other than NOERROR (0) or =
DSONOTIMP  (tentatively 11), then the client should assume that the =
server does  not support DSO."  (Why "should" in lower case?) RFC 1035 =
being very clear that the rcode from a non-DSO server must be NOTIMP =
(this is also said in section 4.2.1 of the draft), I suggest to change =
that to: [...]

We actually think it should be MUST.

We believe the text otherwise says essentially the same thing as =
Stephane's text, except that Stephane's text actually places new =
requirements on non-conforming servers.   We therefore prefer the =
current text.

21: It seems to me that the draft uses "response-requiring messages" as =
a synonym of "acknowledged request messages" (and =
"non-response-requiring messages" as a synonym of "unacknowledged =
request messages"). If I'm correct, it would be better to state it =
clearly in the terminology section.

There's a linquistic ambiguity here.  We wrote "response-requiring" =
rather than "acknowledged" because "acknowledged" could mean "has been =
acknowledged" or "requires acknowledgment," whereas "response-requiring" =
is unambiguous.

So we prefer to keep the text as is.

22: Since there are only four combinations, I do not find this table =
useful.

The idea is that this table is a template for future modifications, so =
we want to have it there as a way of priming that.

23: Last, RFC 5226 (IANA considerations section) is now replaced by RFC =
8126

Fixed, thanks!

Bernie Volz
 https://mailarchive.ietf.org/arch/msg/dnsop/56NcwNBSY1K26tD424Z1sJtQqWU

24: Section 1: Not sure why Stateful is capitalized in the following =
line: "transport protocol.  Each Stateful operation is communicated in =
its"

Stuart coincidentally had already changed this text to say "each DSO =
operation" rather than "each stateful operation," so problem solved. :)

25: Section 2: You probably should update this to the text in =
https://tools.ietf.org/html/rfc8174 and update the references =
accordingly.

The text now references both RFC 2119 and RFC 8174.

26: Section 3: Do you want to add anything about Section 6 (and perhaps =
later sections)?

We concluded that this paragraph was actually unnecessary, so rather =
than adding a mention of section 6, we deleted the paragraph!

27: Section 4.2.2.3 (and perhaps other places similar text exists): When =
a connection is aborted because of an invalid message, is there any =
recommendation to be added about retrying? If the client terminates the =
connection, it would likely not be wise for it to immediately retry and =
repeat the operation as that can lead to an endless loop? Should some =
recommended backoff technique be provided? Or some other connection rate =
limiting warning?

Good point, client should not reconnect immediately after a fatal error. =
  There is no good answer here.

We have added some text in the terminology section that talks about the =
implications of fatal errors.   A fatal error means you are not =
following the spec.   It is still possible that a non-DSO connection =
would work.   How the client navigates this is beyond our ability to =
specify.   The new text says that the client shouldn't try to reconnect =
to the same server instance for at least an hour

28: Section 4.2.3, last paragraph: What should happen if a EDNS(0) TCP =
Keepalive option does appear? Should the connection be terminated? The =
message ignored?

This has already been specified.   Document already says ARCOUNT must be =
zero for DSO messages.   We have added text saying that if an EDNS(0) =
keepalive option appears within a DSO session, it's a fatal error and is =
treated accordingly.

29: Section 4.3: first paragraph: This text kind of conflicts with the =
text in 4.2.1 which says that whether a message is acknowledged or =
unacknowledged is determined only by the specification for the Primary =
TLV. I understand this may not be worth addressing, but perhaps a =
reference to 4.2.1 is worth considering?

We have updated and significantly clarified this section, and we believe =
that this point has been addressed.

30: Section 6.1: INACTIVITY TIMEOUT and KEEPALIVE INTERVAL. Is mention =
0xffffffff (infinite) worth adding to this text?

We have added a separate paragraph about 0xfffffffe in section 5.4.2.  =
Would probably be redundant to add it here as well.   We also deleted =
sections 7.3 and 7.4, which were redundant.

31: Section 6.2.1: If a client were to receive a new RCODE but does not =
understand it (older version), should there be a statement as to how the =
client should react? Should it treat the unknown error code as if =
NOERROR were sent?

We have updated this to say that all nonzero errors should be taken as =
if NOERROR were sent and treat them as routine shutdown.

32: Section 9: Seems a bit light, but OK if it ends up being acceptable. =
For example, while it probably means you have bigger problems, but large =
timer values (such as in the Retry Delay TLV) could be a denial of =
service vector. Though if the server does that, it probably isn=E2=80=99t =
who you wanted to be talking to anyway and you should have used TLS.   =
Perhaps also saying that if DNS over TLS isn=E2=80=99t used (just plan =
TCP), then it may be possible for a man-in-the-middle to inject messages =
(such as with a large Retry Delay TLV)?

We do not see an action here that doesn't already apply to TCP and TLS.

33: While there seems not be a solid definition of what the =
=E2=80=9CUpdates=E2=80=9D means in the RFC header, it always seems to me =
that =E2=80=9CUpdates=E2=80=9D means you are changing something in those =
documents, rather than just extending them with new capabilities within =
the original documents framework.

The point of [updates] here is to flag to readers of the earlier =
specifications that they should read this specification as well.   There =
has been some agreement in the working group that this should be here.  =
In a future world where DSO is pretty common, then we have changed RFC =
7766, and it would be problematic for an implementer to not implement =
this specification as well.


--Apple-Mail=_EE66BBF5-AD99-490B-8875-EC6628E610CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><span=
 id=3D"docs-internal-guid-3f7738fa-0930-dc5d-e6ec-b2f79ab27522" =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><font face=3D"Arial" class=3D""><span =
style=3D"font-size: 14.666666984558105px; white-space: pre-wrap;" =
class=3D"">We have updated draft-ietf-dnsop-session-signal to address =
the points raised during the working group last call, which ended on =
2/23.  We've already received comments on the new version from Paul =
Hoffman (thanks for that) and will address those as well in a later =
update.</span></font></div><div style=3D"line-height: 1.38; margin-top: =
0pt; margin-bottom: 0pt;" class=3D""><font face=3D"Arial" class=3D""><span=
 style=3D"font-size: 14.666666984558105px; white-space: pre-wrap;" =
class=3D""><br class=3D""></span></font></div><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><font =
face=3D"Arial" class=3D""><span style=3D"font-size: =
14.666666984558105px; white-space: pre-wrap;" class=3D"">I've included =
links to the messages we received during last call and a log of the =
changes we made based on the points raised in those messages below.   =
Thanks to everyone for the thorough reviews=E2=80=94we got lots of =
helpful comments!</span></font></div><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><font face=3D"Arial" =
class=3D""><span style=3D"font-size: 14.666666984558105px; white-space: =
pre-wrap;" class=3D""><br class=3D""></span></font></div><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><font face=3D"Arial" class=3D""><span style=3D"font-size: =
14.666666984558105px; white-space: pre-wrap;" =
class=3D"">---</span></font></div><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><font face=3D"Arial" =
class=3D""><span style=3D"font-size: 14.666666984558105px; white-space: =
pre-wrap;" class=3D""><br class=3D""></span></font></div><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">Jan Komissar: <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnssd/v48k8QbOSN-HtDRFRf20cs=
oq1ZY" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnssd/v48k8QbOSN-HtDRFRf2=
0csoq1ZY</a></span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">1: Should =
we require TLS?</span></div><p dir=3D"ltr" =
style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D""> </span></p><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We =
entertained this idea, and it would simplify the protocol work, but it =
seems like an overreach for this document. &nbsp;&nbsp;If we require =
TLS, we are effectively making that a requirement for any DNS-over-TCP =
connection for which session signaling would be useful. &nbsp;&nbsp;We =
do not believe that we have working group consensus on this point, and =
therefore can't make this move in this document.   If the working group =
wants to require TLS for DNS TCP connections, that should be done in a =
separate document.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">Ed =
Lewis</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnsop/CQ_qRzpm_omXivdY7eELQq=
-fX5I" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnsop/CQ_qRzpm_omXivdY7eE=
LQq-fX5I</a></span></div><div style=3D"line-height: 1.38; margin-top: =
0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
</span><span style=3D"font-size: 10.5pt; font-family: Arial; color: =
rgb(97, 97, 97); background-color: rgb(255, 255, 255); =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D""><a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnsop/Iig2nnIvBFsjG5FafKXgpd=
tBDTw" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnsop/Iig2nnIvBFsjG5FafKX=
gpdtBDTw</a></span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">2: Is the =
term "session" inappropriate here?</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The consensus appears to be that using a different =
term in order to accommodate the OSI layering model, which isn't =
actually in use, seems unnecessary. &nbsp;&nbsp;We will add text to the =
document to explicitly state that this isn't session in the OSI sense.  =
Numerous other comments were made that asked for clarification on the =
basis of the assumption that we were talking about an OSI-model session; =
these are all addressed by clarifying that we are not.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">3: The =
endpoints - is that the stub resolver and authoritative server (on in=E2=80=
=A8 DNSSEC terms) the signer and the validator?</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">The text =
here explicitly refers to a connection between client and server; to =
clarify it to "stub resolver and authoritative server" would not be =
correct, since there are many other "clients" and "servers." =
&nbsp;&nbsp;For example a full-service cache is a "server" to the stub =
resolver, and a "client" to an authoritative server or upstream =
forwarder.  RFC 7766 currently uses the terms "client" and "server" in =
the same way, and it's not clear how we could further clarify =
this.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">4: This =
section (4.1) intermingles text on whether or not each DSO request =
elicits a response or not and the process of DSO "session" =
establishment. &nbsp;With proper editing, these should be separated to =
lessen confusion.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">This has =
been clarified</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">5: (Section =
4.1.1) Requirements (first MUST) and recommendations to operate in a =
certain way tend to become dated quickly. &nbsp;Instead of placing =
requirements on clients to act good, let the server refuse workload.  I =
am thinking of the issue surrounding the iterations in NSEC3 and recent =
surveys of operators. Despite the documents saying a low value is =
better, operators use high values.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">This text is quote from RFC 7766, so updating it =
would require an update to RFC7766.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">6: This phrase is confusing and unnecessary "this =
is a fatal error". &nbsp;The logic to that point is clear that the =
situation doesn't happen and the &nbsp;prescribed behavior ("close the =
connection") makes sense.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The term "fatal error" is used throughout the =
document to mean an error that precludes further communication on the =
connection. &nbsp;&nbsp;The terminology section has been updated to =
clarify.   </span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">7: This is =
clumsy, when describing the RCODE: "generally set to zero on =
transmission, and silently ignored on reception, =
except".</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">This text =
has been clarified.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">8: Perhaps =
these are not "unacknowledged requests" but "subsequent =
responses".</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We had a =
debate about what the right phrase was to use and settled on =
"unacknowledged messages." &nbsp;&nbsp;The document has been updated to =
use this phrase consistently, which should lessen the confusion.   =
"Subsequent responses" doesn't really work because an unacknowledged =
message isn't really a response.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">9: Do not do name compression! &nbsp;No No No =
No.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">The reason =
we don't say this is that TLVs can tunnel DNS messages, and this text =
would require us to uncompress the message before encoding it in a =
TLV.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
changed the text to be slightly more generic: the content of a TLV is =
opaque and subject to definition of that TLV. &nbsp;&nbsp;We no longer =
mention DNS name compression at all=E2=80=94since TLVs are opaque blobs, =
no requirements can be placed on what they look like.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">10: =
Unrecognized primary: "I would have thought this would warrant tearing =
down the connection given the words earlier that this ought never =
happen."</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We agree, =
and the document has been updated accordingly.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">11: =
&nbsp;&nbsp;"The namespaces of 16-bit MESSAGE IDs are disjoint in each =
direction. &nbsp;&nbsp;For example, it is *not* an error for both client =
and server to send a request message with the same ID." &nbsp;&nbsp;This =
will, someday, confuse a young and inexperienced DNS hosting =
engineer.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">The reason =
we wrote this in the spec is so that a young engineer won't make that =
mistake.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
added some text to clarify that the directionality of the message can be =
considered an extra bit. &nbsp;&nbsp;There is no way for the server and =
client to know that the other isn't using the same message ID as they =
are composing the message, and the tracking required to prevent clashes =
that theoretically </span><span style=3D"font-size: 11pt; font-family: =
Arial; font-style: italic; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" =
class=3D"">could</span><span style=3D"font-size: 11pt; font-family: =
Arial; font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D""> be prevented would impose a huge amount of =
complexity=E2=80=94this really isn't at all analogous to the =
</span><span style=3D"font-size: 11pt; font-family: &quot;Courier =
New&quot;; font-variant-ligatures: normal; font-variant-east-asian: =
normal; font-variant-position: normal; vertical-align: baseline; =
white-space: pre-wrap;" class=3D"">key_id</span><span style=3D"font-size: =
11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
example.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">12: There =
will be a need to fight cruft, or garbage collect. &nbsp;Inactive =
objects tend to be forgotten while still using up =
resources.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">If you've =
got buggy client software that forgets to cancel some operation it's =
going to forget to stop sending renewals as well. &nbsp;This is one =
reason for having keepalives.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">13: I thought that if a connection ends, the DSO =
session ends.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" =
class=3D"">Correct.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
changed "reconnect" to "make a new session" which means a new connection =
as well.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">14: =
Sometimes a client can't distinguish this: "If reconnecting to the same =
server," as some server processes have multiple addresses and =
names."</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
stolen the following text from DNS Push and flipped it around to change =
the emphasis:</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">DNS Updates =
and DNS Push Notifications may be handled on different ports on the same =
target host, in which case they are not considered to be the "same =
server" for the purposes of this specification, and communications with =
these two ports are handled independently.</span></div><br class=3D""><div=
 style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The issue is that it's actually a hard problem for =
the client to know that two servers are the same server. =
&nbsp;&nbsp;This definition is sufficiently constrained that we can =
imagine a client successfully implementing.   Matching IP addresses is =
too hard. &nbsp;&nbsp;As a server operator, if you want servers to share =
connections it's your job to set up the server with the same host and =
ports.   The opposite is also true.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">15: "The RECOMMENDED value is 10 seconds." =
Probably a bad idea to codify this because implementations will set it =
to 10 and not scatter it when it should be. &nbsp;(Like closing out many =
connections in a load-shedding panic.)</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">Instead could say that it's recommended that =
servers set this value to ten seconds when they </span><span =
style=3D"font-size: 11pt; font-family: Arial; font-style: italic; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">want</span><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> the client =
to reconnect, and refer back to the session that has the more general =
text about this (5.6.1.1).</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The text has been updated as =
suggested=E2=80=94thanks!</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">Paul Hoffman:</span></div><div style=3D"line-height:=
 1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnsop/PUlnpSfGvZo6cZge476SEW=
UR7tM" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnsop/PUlnpSfGvZo6cZge476=
SEWUR7tM</a></span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">16: The =
document should explicitly list which protocols are currently =
acceptable, and say that the list can change in the future based on =
standards-track documents.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">We do not agree that this should be restricted to =
standards-track documents. &nbsp;&nbsp;That said, we took the text that =
Paul kindly provided and tweaked it.  Updates to DSO obviously still =
have to be standards-track.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">Paul also sent us comments on the post-WGLC -06 =
update, which have not yet been addressed as of now. &nbsp;Thanks very =
much for the quick response, Paul!</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">Stephane Bortzmeyer:</span></div><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D""> <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnssd/NFtd5RGIJhbOnb4Q_dWLwf=
ZmkYg" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnssd/NFtd5RGIJhbOnb4Q_dW=
LwfZmkYg</a></span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">17: My =
personal feeling is that it is complicated, with a lot of details. May =
be separating in two documents, one for the base DSO concept and one for =
the standards TLV (with their detailed behavior) would have been =
better.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We don't =
see any working group consensus on this point, and it seems =
unnecessary.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">18: There =
is a discussion about a possible Privacy section &lt;<a =
href=3D"https://github.com/raybellis/draft-bellis-dnsop-session-signal/pul=
l/36" =
class=3D"">https://github.com/raybellis/draft-bellis-dnsop-session-signal/=
pull/36</a>&gt; for which I suggest the following text: =
[...]</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We started =
with Stephane's text, and wound up with this:</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;When designing new DSO TLVs, the potential for data in the =
TLV to be</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;used as a tracking identifier should be taken into =
consideration, and</span></div><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;should be avoided when not required.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;When used without TLS or similar cryptographic protection, =
a</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;malicious entity maybe able to inject a malicious Retry =
Delay</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;Unacknowledged Message into the data stream, specifying =
an</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;unreasonably large RETRY DELAY, causing a denial-of-service =
attack</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> =
&nbsp;&nbsp;against the client.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">This is now in the Security Considerations =
section, rather than in a separate Privacy Considerations section. =
&nbsp;&nbsp;We could make it a separate section if there is a strong =
desire to do so, but it seemed unnecessary.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">19: =
&nbsp;"There are a myriad of other potential use cases for DSO given the =
versatility and extensibility of this specification." &nbsp;&nbsp;I =
don't really like this sort of sentence. Either we have ideas about =
these potential use cases and we should write them down, or we don't and =
we should avoid this sort of very general words (after all, human =
imagination being what it is, we can be sure surprising use cases will =
be found.)</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We agree =
and have removed this text.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">20: &nbsp;"If the RCODE is set to any value other =
than NOERROR (0) or DSONOTIMP &nbsp;(tentatively 11), then the client =
should assume that the server does  not support DSO." &nbsp;(Why =
"should" in lower case?) RFC 1035 being very clear that the rcode from a =
non-DSO server must be NOTIMP (this is also said in section 4.2.1 of the =
draft), I suggest to change that to: [...]</span></div><br class=3D""><div=
 style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">We actually think it should be =
MUST.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We believe =
the text otherwise says essentially the same thing as Stephane's text, =
except that Stephane's text actually places new requirements on =
non-conforming servers. &nbsp;&nbsp;We therefore prefer the current =
text.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">21: It =
seems to me that the draft uses "response-requiring messages" as a =
synonym of "acknowledged request messages" (and "non-response-requiring =
messages" as a synonym of "unacknowledged request messages"). If I'm =
correct, it would be better to state it clearly in the terminology =
section.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">There's a =
linquistic ambiguity here. &nbsp;We wrote "response-requiring" rather =
than "acknowledged" because "acknowledged" could mean "has been =
acknowledged" or "requires acknowledgment," whereas "response-requiring" =
is unambiguous.</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">So we =
prefer to keep the text as is.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">22: Since there are only four combinations, I do =
not find this table useful.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The idea is that this table is a template for =
future modifications, so we want to have it there as a way of priming =
that.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">23: Last, =
RFC 5226 (IANA considerations section) is now replaced by RFC =
8126</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">Fixed, =
thanks!</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">Bernie =
Volz</span></div><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""> <a =
href=3D"https://mailarchive.ietf.org/arch/msg/dnsop/56NcwNBSY1K26tD424Z1sJ=
tQqWU" =
class=3D"">https://mailarchive.ietf.org/arch/msg/dnsop/56NcwNBSY1K26tD424Z=
1sJtQqWU</a></span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">24: Section =
1: Not sure why Stateful is capitalized in the following line: =
"transport protocol. &nbsp;Each Stateful operation is communicated in =
its"</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">Stuart =
coincidentally had already changed this text to say "each DSO operation" =
rather than "each stateful operation," so problem solved. =
:)</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">25: Section =
2: You probably should update this to the text in <a =
href=3D"https://tools.ietf.org/html/rfc8174" =
class=3D"">https://tools.ietf.org/html/rfc8174</a> and update the =
references accordingly.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">The text now references both RFC 2119 and RFC =
8174.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">26: Section =
3: Do you want to add anything about Section 6 (and perhaps later =
sections)?</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We =
concluded that this paragraph was actually unnecessary, so rather than =
adding a mention of section 6, we deleted the paragraph!</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">27: Section =
4.2.2.3 (and perhaps other places similar text exists): When a =
connection is aborted because of an invalid message, is there any =
recommendation to be added about retrying? If the client terminates the =
connection, it would likely not be wise for it to immediately retry and =
repeat the operation as that can lead to an endless loop? Should some =
recommended backoff technique be provided? Or some other connection rate =
limiting warning?</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">Good point, =
client should not reconnect immediately after a fatal error. =
&nbsp;&nbsp;There is no good answer here.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">We have added some text in the terminology section =
that talks about the implications of fatal errors. &nbsp;&nbsp;A fatal =
error means you are not following the spec.   It is still possible that =
a non-DSO connection would work. &nbsp;&nbsp;How the client navigates =
this is beyond our ability to specify.   The new text says that the =
client shouldn't try to reconnect to the same server instance for at =
least an hour</span></div><br class=3D""><div style=3D"line-height: =
1.38; margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">28: Section =
4.2.3, last paragraph: What should happen if a EDNS(0) TCP Keepalive =
option does appear? Should the connection be terminated? The message =
ignored?</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">This has =
already been specified. &nbsp;&nbsp;Document already says ARCOUNT must =
be zero for DSO messages. &nbsp;&nbsp;We have added text saying that if =
an EDNS(0) keepalive option appears within a DSO session, it's a fatal =
error and is treated accordingly.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">29: Section 4.3: first paragraph: This text kind =
of conflicts with the text in 4.2.1 which says that whether a message is =
acknowledged or unacknowledged is determined only by the specification =
for the Primary TLV. I understand this may not be worth addressing, but =
perhaps a reference to 4.2.1 is worth considering?</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
updated and significantly clarified this section, and we believe that =
this point has been addressed.</span></div><br class=3D""><div =
style=3D"line-height: 1.38; margin-top: 0pt; margin-bottom: 0pt;" =
class=3D""><span style=3D"font-size: 11pt; font-family: Arial; =
font-variant-ligatures: normal; font-variant-east-asian: normal; =
font-variant-position: normal; vertical-align: baseline; white-space: =
pre-wrap;" class=3D"">30: Section 6.1: INACTIVITY TIMEOUT and KEEPALIVE =
INTERVAL. Is mention 0xffffffff (infinite) worth adding to this =
text?</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
added a separate paragraph about 0xfffffffe in section 5.4.2. =
&nbsp;Would probably be redundant to add it here as well.   We also =
deleted sections 7.3 and 7.4, which were redundant.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">31: Section =
6.2.1: If a client were to receive a new RCODE but does not understand =
it (older version), should there be a statement as to how the client =
should react? Should it treat the unknown error code as if NOERROR were =
sent?</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We have =
updated this to say that all nonzero errors should be taken as if =
NOERROR were sent and treat them as routine shutdown.</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">32: Section =
9: Seems a bit light, but OK if it ends up being acceptable. For =
example, while it probably means you have bigger problems, but large =
timer values (such as in the Retry Delay TLV) could be a denial of =
service vector. Though if the server does that, it probably isn=E2=80=99t =
who you wanted to be talking to anyway and you should have used TLS. =
&nbsp;&nbsp;Perhaps also saying that if DNS over TLS isn=E2=80=99t used =
(just plan TCP), then it may be possible for a man-in-the-middle to =
inject messages (such as with a large Retry Delay TLV)?</span></div><br =
class=3D""><div style=3D"line-height: 1.38; margin-top: 0pt; =
margin-bottom: 0pt;" class=3D""><span style=3D"font-size: 11pt; =
font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">We do not =
see an action here that doesn't already apply to TCP and =
TLS.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">33: While =
there seems not be a solid definition of what the =E2=80=9CUpdates=E2=80=9D=
 means in the RFC header, it always seems to me that =E2=80=9CUpdates=E2=80=
=9D means you are changing something in those documents, rather than =
just extending them with new capabilities within the original documents =
framework.</span></div><br class=3D""><div style=3D"line-height: 1.38; =
margin-top: 0pt; margin-bottom: 0pt;" class=3D""><span style=3D"font-size:=
 11pt; font-family: Arial; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D"">The point =
of [updates] here is to flag to readers of the earlier specifications =
that they should read this specification as well. &nbsp;&nbsp;There has =
been some agreement in the working group that this should be here.  In a =
future world where DSO is pretty common, then we have changed RFC 7766, =
and it would be problematic for an implementer to not implement this =
specification as well.</span></div><div class=3D""><span =
style=3D"font-size: 11pt; font-family: Arial; font-variant-ligatures: =
normal; font-variant-east-asian: normal; font-variant-position: normal; =
vertical-align: baseline; white-space: pre-wrap;" class=3D""><br =
class=3D""></span></div></span></body></html>=

--Apple-Mail=_EE66BBF5-AD99-490B-8875-EC6628E610CA--


From nobody Tue Mar 20 09:21:40 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77439127137 for <dnssd@ietfa.amsl.com>; Tue, 20 Mar 2018 09:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 pqvcZjy0weo1 for <dnssd@ietfa.amsl.com>; Tue, 20 Mar 2018 09:21:36 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3CE4126C0F for <dnssd@ietf.org>; Tue, 20 Mar 2018 09:21:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521562894; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding; bh=dOZipJF8D1bdQ8B/1jeuUec/wUkICtay5j3Fr3Nc2wM=; b=A5sBqEQrSNat0YkpTZexCTtMVJFe+Re4MWO8lRJnHcuaCi9/zVfa1vn0RBWSJIamsYOSI2ZGEhPi9gRVw8zC3YnLIr+pzaOAkA8YRmX9iDbjcG8yn5DHOrL+wx/iJ1sXmBBlVTZ4g9h97QvyD9dc8Dxf6f0cqlRLOJsarBQhCpk=
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-db5eur03lp0088.outbound.protection.outlook.com [94.245.120.88]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-52-ougvZ3i4OFaeRVRbSEdN0A-1; Tue, 20 Mar 2018 16:21:32 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB0992.eurprd07.prod.outlook.com (10.161.110.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Tue, 20 Mar 2018 16:21:30 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Tue, 20 Mar 2018 16:21:30 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: Minute taker and jabber relay for dnssd WG session?
Thread-Index: AQHTwGeBeIep+r1J9Uy+MqEc5ohW6w==
Date: Tue, 20 Mar 2018 16:21:30 +0000
Message-ID: <02470539-74B0-41F8-A62B-956AD463C5BA@jisc.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:67c:370:128:54c5:43a7:16fb:4dbb]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB0992; 7:o72IYaUNu+QRwLDo+FLemS8vxTGgizc1UB2S4M73Jph4PRyN8Jw5YYnhYDShbiqYxtt5q1Cm4xCfBz04RAohphUkEB8R2lFoY02nJEbSVvs6nWjaNKCxmAR+YVzbRYo3UsFo0PMV1J0sBad4kWuUECTpa5mLSj49F1QDtDJS0bp3+YskFA8WN59C6YpI9yRgM4CX4YHwAcTG5jxpmcWzItnhjCYWEztQeF1JmLJojjO/cQT2vd/oB+NL3Gtj1wEU; 20:oJBdUR+Z4bI0spoCjiRvf1sDJ/s6dNyuNh+6Cy/DsB4YkyGJciidrpnUp+Bja2pjznazdrbNtAJsTOQn/B8l9qeebshe1OACKnORbd9FMNKnfCnXXWJufxP9H9VuCoCQdDFx/ZHr/bykv+yDxUnLco2hrSsojutnoBTFzqVS6dM=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: c042e7a2-a4ae-454b-1ed6-08d58e7ea3b5
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB0992; 
x-ms-traffictypediagnostic: VI1PR07MB0992:
x-microsoft-antispam-prvs: <VI1PR07MB0992CADCC01E33E9986BD64BD6AB0@VI1PR07MB0992.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(3231221)(944501244)(52105095)(93006095)(93001095)(10201501046)(6041310)(20161123564045)(20161123560045)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011); SRVR:VI1PR07MB0992; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB0992; 
x-forefront-prvs: 061725F016
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(366004)(396003)(376002)(39380400002)(346002)(279900001)(189003)(199004)(50226002)(57306001)(7736002)(5250100002)(74482002)(186003)(93376004)(6506007)(966005)(2906002)(2501003)(19625305001)(33656002)(72206003)(3660700001)(305945005)(102836004)(105586002)(478600001)(99286004)(2900100001)(6116002)(14454004)(6486002)(6436002)(81156014)(83716003)(46003)(6306002)(2351001)(6512007)(316002)(786003)(53936002)(8936002)(3280700002)(82746002)(97736004)(1730700003)(5640700003)(81166006)(6916009)(68736007)(36756003)(86362001)(8676002)(5660300001)(106356001)(25786009)(5003080100003)(15302535012); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB0992; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
x-microsoft-antispam-message-info: 36wS45VKzX1kros2aBmEnCsLHmhNye+5My5sutmFY6kNMkfQfwmhFDPgZMtDU7P2BX5hZYvHt/WjxAun7g1E8kIiqlGmZ+C3LbdnuMo9y0UTdwJu/UAp5fzXd+BjUc+5q83xy52opKqTpnDRITXZMizR53Za5RO9sIwxBIADzy7HEbis90eoD3wA4Ng0844vmLkFK04pkiOrpsRfV1G4WLKjJxRj4E/Cs1psJq7ZLMzLAL7QWmuAfFCagjblwNwrvRQfGqNajfDAG5YSkGCmL1ZowbfM914kAsHzwSvvBup8EZ1H7ZMhua9bsKoWbuHL3/GoDrsEfDwzLh1J44QSHw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <A2EE3AA925303D4DB3D84E4AC57DC776@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: c042e7a2-a4ae-454b-1ed6-08d58e7ea3b5
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2018 16:21:30.5591 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB0992
X-MC-Unique: ougvZ3i4OFaeRVRbSEdN0A-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/UEIC9Z8uoYz3lu4t4M33i7huEaE>
Subject: [dnssd] Minute taker and jabber relay for dnssd WG session?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2018 16:21:38 -0000

Hi,

David and I would welcome any volunteers to act as a minute taker or a jabb=
er relay for our WG session on Thursday.

The Etherpad is pre-populated with agenda items at
http://etherpad.tools.ietf.org:9000/p/notes-ietf-101-dnssd?useMonospaceFont=
=3Dtrue

If the minute-taker uses that, other attendees can assist with notes, esp. =
getting their own names spelt correctly, which can be tricky!

Many thanks,
Tim=20




From nobody Wed Mar 21 01:06:21 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE2F12D958 for <dnssd@ietfa.amsl.com>; Wed, 21 Mar 2018 01:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.288
X-Spam-Level: 
X-Spam-Status: No, score=-4.288 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 ncgMsZDd5mfp for <dnssd@ietfa.amsl.com>; Wed, 21 Mar 2018 01:06:07 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C21312D954 for <dnssd@ietf.org>; Wed, 21 Mar 2018 01:06:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521619562; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=TfGTZtyuSzTvkYvRNe0Q1DoN93cCDDWzfemKCCqzd3Y=; b=C3RaRWHq8lBV/RhfnWEetbsGit339kprmhXv3XlpYEZ+gEL1jCpZXzmiL5+wjXbKN3mVSgVsBjRKYZRi3WJzhcDY24UeOQbq6lT+kcazv/6BAP8VuZMep8UTdZg7RRcRhYHxBBaTPKk3XlSsAyPt39H64HXeu41JtNH/jXlmvKI=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0240.outbound.protection.outlook.com [213.199.154.240]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-15-pEIPmVeZPlmdL0KhltC4Tw-1; Wed, 21 Mar 2018 08:06:00 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB3184.eurprd07.prod.outlook.com (10.175.243.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Wed, 21 Mar 2018 08:05:56 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Wed, 21 Mar 2018 08:05:56 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: [dnssd] Minute taker and jabber relay for dnssd WG session?
Thread-Index: AQHTwGeBuueidWCly0eIojzbSp8UDKPZWUuAgAD8xYA=
Date: Wed, 21 Mar 2018 08:05:55 +0000
Message-ID: <12F94B50-D7B6-41E9-AED7-0294B16DC9A3@jisc.ac.uk>
References: <02470539-74B0-41F8-A62B-956AD463C5BA@jisc.ac.uk> <AA5603DB-28B5-46CA-91ED-25C5B0FC6E96@gmail.com>
In-Reply-To: <AA5603DB-28B5-46CA-91ED-25C5B0FC6E96@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [188.29.164.192]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB3184; 7:GGeRcKfIiHZMCZtQN63akA26JPqnNYB368TKkOWMHgZWP+iUxir/6i2Jj8fjLwxHi+WtFV1i0DUFeU5GAdRFwwAlVsY5ez7I0vt47Pcho1BeFQH0bU92KH3lTjk/zTNFVYMif+TZ/WQMcSctYxKK9thyWWyGVaYxfv/i/kuU7SbG1pVMGgvGJDgrXKioIsHW6t6IpWD8Nc1OU687RrmK6dQuy1xIR1k0k3AucaWwfGXf+fd56jky+ri39TZFmFI4; 20:owioGZZaIie0OWgvPENiEX25Xws1bsOV/WH4gkMhi4GAyICYwPdVqD6UZlq2NWk8hq5d/jWPNRuUcyBkL3bUQRnDdj9wEBvVx/vAM+0Ij+RKrQ2uKbXUnvsPmlLXH9tGC799U+YIGWSndrFg4xjfqlZk26AFVIL24tDRZlOOVYs=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 7aaba024-7beb-4aff-5d82-08d58f029301
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(7168020)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB3184; 
x-ms-traffictypediagnostic: VI1PR07MB3184:
x-microsoft-antispam-prvs: <VI1PR07MB3184CE40D19C254CF3E625DBD6AA0@VI1PR07MB3184.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(274715658323672);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231221)(944501320)(52105095)(6041310)(20161123562045)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:VI1PR07MB3184; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB3184; 
x-forefront-prvs: 0618E4E7E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(39850400004)(366004)(396003)(39380400002)(279900001)(199004)(189003)(57306001)(74482002)(8936002)(83716003)(76176011)(97736004)(2501003)(229853002)(5250100002)(786003)(14454004)(6506007)(86362001)(316002)(186003)(99286004)(966005)(55236004)(102836004)(6246003)(53546011)(72206003)(68736007)(6486002)(50226002)(478600001)(26005)(8676002)(36756003)(1730700003)(19625305001)(66066001)(6436002)(3280700002)(3660700001)(7736002)(106356001)(82746002)(2900100001)(33656002)(81156014)(53936002)(5660300001)(81166006)(6916009)(6512007)(5640700003)(305945005)(2906002)(105586002)(2950100002)(3846002)(2351001)(6306002)(6116002)(25786009); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB3184; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
x-microsoft-antispam-message-info: cx0l30EoiW6hg5G91u6qBFqpoC4UOBFLRfGMGc1aPzhEKd7UoSNRQr5u4b/LyMRGhC7dN/e6hqHN0XwhH+UjM8RfzLqSGJ9prVniQhcgzdGGXEX3klidYn5P37yd7l/mHa1JQxneeKO+oWUkHWKHbd/XsOByMOo4r0JVYhRp0OIz0o0AJHmvfQOdRPyUSaMvaWax97Rmc1OrV+PkHwEBgJNFnQxMJed0/rGYoL8GfNENNaArO3VdWrAeUauT3Lu/dJlCxTFaNlUo1QViVVQYJpSJMXNkZ7+C6mqgdlBgRETMjueJ0d7GavJlQi4cOIzTqrO+OOoojgTZUMvSX/pj/g==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <F4A0B13DFBD6564FA9E83246DD1235DC@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 7aaba024-7beb-4aff-5d82-08d58f029301
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Mar 2018 08:05:56.0121 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB3184
X-MC-Unique: pEIPmVeZPlmdL0KhltC4Tw-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/R7exqSwwqGb1Icsr-KlsZBR1S5o>
Subject: Re: [dnssd] Minute taker and jabber relay for dnssd WG session?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 08:06:11 -0000

Hi,

We have a volunteer for minutes; many thanks (again!) Tim Wicinski.

Best wishes,
Tim

> On Mar 20, 2018, at 16:21, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
>>=20
>> Hi,
>>=20
>> David and I would welcome any volunteers to act as a minute taker or a j=
abber relay for our WG session on Thursday.
>>=20
>> The Etherpad is pre-populated with agenda items at
>> http://etherpad.tools.ietf.org:9000/p/notes-ietf-101-dnssd?useMonospaceF=
ont=3Dtrue
>>=20
>> If the minute-taker uses that, other attendees can assist with notes, es=
p. getting their own names spelt correctly, which can be tricky!
>>=20
>> Many thanks,
>> Tim=20



Tim=20




From nobody Wed Mar 21 12:45:03 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 94188126C25; Wed, 21 Mar 2018 12:45:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnssd@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152166150255.21304.14362467095011002448@ietfa.amsl.com>
Date: Wed, 21 Mar 2018 12:45:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/B52_HjINDP0K4lNoJWd4ne80Q9A>
Subject: [dnssd] I-D Action: draft-ietf-dnssd-push-14.txt
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 19:45:03 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Extensions for Scalable DNS Service Discovery  WG of the IETF.

        Title           : DNS Push Notifications
        Authors         : Tom Pusateri
                          Stuart Cheshire
	Filename        : draft-ietf-dnssd-push-14.txt
	Pages           : 35
	Date            : 2018-03-21

Abstract:
   The Domain Name System (DNS) was designed to return matching records
   efficiently for queries for data that are relatively static.  When
   those records change frequently, DNS is still efficient at returning
   the updated results when polled, as long as the polling rate is not
   too high.  But there exists no mechanism for a client to be
   asynchronously notified when these changes occur.  This document
   defines a mechanism for a client to be notified of such changes to
   DNS records, called DNS Push Notifications.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnssd-push/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnssd-push-14
https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-push-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-push-14


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Mar 21 12:57:11 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 69DBD12711E; Wed, 21 Mar 2018 12:57:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dnssd@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152166222939.21312.12894635789364073858@ietfa.amsl.com>
Date: Wed, 21 Mar 2018 12:57:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/4IK9ZLyjyNtkZYogdhbBUa05d98>
Subject: [dnssd] I-D Action: draft-ietf-dnssd-hybrid-08.txt
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2018 19:57:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Extensions for Scalable DNS Service Discovery  WG of the IETF.

        Title           : Discovery Proxy for Multicast DNS-Based Service Discovery
        Author          : Stuart Cheshire
	Filename        : draft-ietf-dnssd-hybrid-08.txt
	Pages           : 37
	Date            : 2018-03-21

Abstract:
   This document specifies a network proxy that uses Multicast DNS to
   automatically populate the wide-area unicast Domain Name System
   namespace with records describing devices and services found on the
   local link.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dnssd-hybrid/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-dnssd-hybrid-08
https://datatracker.ietf.org/doc/html/draft-ietf-dnssd-hybrid-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dnssd-hybrid-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Mar 21 20:09:43 2018
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 463951200C1 for <dnssd@ietfa.amsl.com>; Wed, 21 Mar 2018 20:09:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, WEIRD_PORT=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 KQkYgmXMIn0c for <dnssd@ietfa.amsl.com>; Wed, 21 Mar 2018 20:09:39 -0700 (PDT)
Received: from mail-wm0-x22f.google.com (mail-wm0-x22f.google.com [IPv6:2a00:1450:400c:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 423261241F8 for <dnssd@ietf.org>; Wed, 21 Mar 2018 20:09:39 -0700 (PDT)
Received: by mail-wm0-x22f.google.com with SMTP id r82so13441126wme.0 for <dnssd@ietf.org>; Wed, 21 Mar 2018 20:09:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=EPO0nSuCdPewAumdbdOm2wokg3kaaFhx6HxfOp0yMyA=; b=t32ve9NYfOAkCiIlsgSbYlaS09YYhrDZqjo7bHq0f5+RdrMdPCipNMubkZu1wTgwZw ZduJA30LUdka6jezh469PCVs+5N5+H2kU0woGpXCuOFkaotrka0KUfhmt5k/+tKVwo+e 0YmkWwiTriwIUr7Tz3PqWdRpo/+MeYoDszQEWUPsxCf8ca4L0eNfWyPIq3yIUZLUv5EG QhXiZLHQujf55OBpaldX5lN9W++N3OFqnYck1E8i3+hqJpi0ybhETq9zDlXwLRyUG9TB t1qKVEZAfL89NHUsxt1UgpjerkPMNnQr1HBo1SefvYGWhM1unEWq8YNa4HaISXCw+XmM Ha2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=EPO0nSuCdPewAumdbdOm2wokg3kaaFhx6HxfOp0yMyA=; b=TU9kESYjRLv0h+X2tiF9xlmDlLrfERIjDb1Gp/0PEHK3AAJLQHkVKH9TUTghAfloBF eRaQKcKSHPrWwLfCeOyrZdIvGC7zm+hEIksCzCOkP0g2cViCEpirhKhjqcGIJNHlwBa7 B5xMK/vep3/cMhOTXYJxp9CfAl/OegrYkkQUtIvka8urEBni4ChNJTRB5VivNMPjxEec cjkSXD+k5gmvqXoDSYOHVpKQIfgteWZ9C11cSjXhNr7R2JnhPcHwOYHSIu1ptInXp0DT wV5FSCc+fwdhpk8ri4IL/J2++lcGGWTNP06Gz7M5UsYH6A9VcACF5sC9fE0zy5W4WYRM zsuQ==
X-Gm-Message-State: AElRT7EHF/eicxorn87MRCWlEYFOh8LcVjvZkbKaU3t/Xo4Ray5vx0tJ S28vVqEoCVbZhDMIUxGl53Nm+xTQjBnPvClr8Hw=
X-Google-Smtp-Source: AG47ELtxPe9Vh39cxIlLPZF7cw2HStKU6cKDYqoZLElxSONvPKKMXZsHOq7T0zT7PL1DeSt43OlqZxhSZb+B9dgnkJc=
X-Received: by 10.28.36.134 with SMTP id k128mr4609263wmk.2.1521688177708; Wed, 21 Mar 2018 20:09:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.154.52 with HTTP; Wed, 21 Mar 2018 20:09:37 -0700 (PDT)
In-Reply-To: <12F94B50-D7B6-41E9-AED7-0294B16DC9A3@jisc.ac.uk>
References: <02470539-74B0-41F8-A62B-956AD463C5BA@jisc.ac.uk> <AA5603DB-28B5-46CA-91ED-25C5B0FC6E96@gmail.com> <12F94B50-D7B6-41E9-AED7-0294B16DC9A3@jisc.ac.uk>
From: tjw ietf <tjw.ietf@gmail.com>
Date: Thu, 22 Mar 2018 03:09:37 +0000
Message-ID: <CADyWQ+GRELs2mHe0Mr=7GRkyUJptAadrUqycWavBjNPPCXO=RQ@mail.gmail.com>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Content-Type: multipart/alternative; boundary="001a1147dcb64a96f50567f7a3b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/YU18kAxDkksxB6khtNjAzk1DDQg>
Subject: Re: [dnssd] Minute taker and jabber relay for dnssd WG session?
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 03:09:41 -0000

--001a1147dcb64a96f50567f7a3b8
Content-Type: text/plain; charset="UTF-8"

All

Something's come up and I need to bow out - alerted the chairs just a bit
ago, so if someone could do me a solid and take over I would be most
grateful

Tim(#2)


On Wed, Mar 21, 2018 at 8:05 AM, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:

> Hi,
>
> We have a volunteer for minutes; many thanks (again!) Tim Wicinski.
>
> Best wishes,
> Tim
>
> > On Mar 20, 2018, at 16:21, Tim Chown <Tim.Chown@jisc.ac.uk> wrote:
> >>
> >> Hi,
> >>
> >> David and I would welcome any volunteers to act as a minute taker or a
> jabber relay for our WG session on Thursday.
> >>
> >> The Etherpad is pre-populated with agenda items at
> >> http://etherpad.tools.ietf.org:9000/p/notes-ietf-101-
> dnssd?useMonospaceFont=true
> >>
> >> If the minute-taker uses that, other attendees can assist with notes,
> esp. getting their own names spelt correctly, which can be tricky!
> >>
> >> Many thanks,
> >> Tim
>
>
>
> Tim
>
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>

--001a1147dcb64a96f50567f7a3b8
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div>All</div><div><br></div><div>Something&#39;s come=
 up and I need to bow out - alerted the chairs just a bit ago, so if someon=
e could do me a solid and take over I would be most grateful</div><div><br>=
</div><div>Tim(#2)</div><div><br></div></div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Wed, Mar 21, 2018 at 8:05 AM, Tim Chown <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:Tim.Chown@jisc.ac.uk" target=3D"_blank"=
>Tim.Chown@jisc.ac.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">Hi,<br>
<br>
We have a volunteer for minutes; many thanks (again!) Tim Wicinski.<br>
<br>
Best wishes,<br>
Tim<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On Mar 20, 2018, at 16:21, Tim Chown &lt;<a href=3D"mailto:Tim.Chown@j=
isc.ac.uk">Tim.Chown@jisc.ac.uk</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; David and I would welcome any volunteers to act as a minute taker =
or a jabber relay for our WG session on Thursday.<br>
&gt;&gt;<br>
&gt;&gt; The Etherpad is pre-populated with agenda items at<br>
&gt;&gt; <a href=3D"http://etherpad.tools.ietf.org:9000/p/notes-ietf-101-dn=
ssd?useMonospaceFont=3Dtrue" rel=3D"noreferrer" target=3D"_blank">http://et=
herpad.tools.ietf.<wbr>org:9000/p/notes-ietf-101-<wbr>dnssd?useMonospaceFon=
t=3Dtrue</a><br>
&gt;&gt;<br>
&gt;&gt; If the minute-taker uses that, other attendees can assist with not=
es, esp. getting their own names spelt correctly, which can be tricky!<br>
&gt;&gt;<br>
&gt;&gt; Many thanks,<br>
&gt;&gt; Tim<br>
<br>
<br>
<br>
Tim<br>
<br>
<br>
<br>
______________________________<wbr>_________________<br>
dnssd mailing list<br>
<a href=3D"mailto:dnssd@ietf.org">dnssd@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnssd" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/dnssd</a><br>
</div></div></blockquote></div><br></div>

--001a1147dcb64a96f50567f7a3b8--


From nobody Thu Mar 22 02:52:03 2018
Return-Path: <adam@nostrum.com>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 27ED7126C19; Thu, 22 Mar 2018 02:51:56 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dnssd-hybrid@ietf.org, Tim Chown <tim.chown@jisc.ac.uk>, dnssd-chairs@ietf.org, tim.chown@jisc.ac.uk, dnssd@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.76.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152171231615.5580.3669709250792886120.idtracker@ietfa.amsl.com>
Date: Thu, 22 Mar 2018 02:51:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/uMFTJRdeuTi8eLHJIHNsAD_5ITA>
Subject: [dnssd] Adam Roach's No Objection on draft-ietf-dnssd-hybrid-08: (with COMMENT)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 09:51:56 -0000

Adam Roach has entered the following ballot position for
draft-ietf-dnssd-hybrid-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dnssd-hybrid/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for addressing my DISCUSS and comments.



From nobody Thu Mar 22 03:20:09 2018
Return-Path: <swmike@swm.pp.se>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22141200C5 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 03:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 9Y04FoG4xBQe for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 03:20:07 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A30DD12D876 for <dnssd@ietf.org>; Thu, 22 Mar 2018 03:20:07 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id CF81AB0; Thu, 22 Mar 2018 11:20:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1521714005; bh=XV3S49K0zzEuWlpofIWZEj66XWOPi3RhPN1XgIqGcQ8=; h=Date:From:To:Subject:From; b=Mwghxa8BNl8F5qVAe6tj02tearWb4aT262lzDyNdLfE6crquZ0uUYZd8MFWuOKvkH nhGCHRv1yFAdMQAgOQjB6SW4/zPnGpBsBT381AIJ67Amf6Uo3t9/nEz8OO0S1ZLvBf kMLNn5LWA20zrD3X1qOsPpdDLk/p6T8J0vpvRMQ4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CE00F9F for <dnssd@ietf.org>; Thu, 22 Mar 2018 11:20:05 +0100 (CET)
Date: Thu, 22 Mar 2018 11:20:05 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: dnssd@ietf.org
Message-ID: <alpine.DEB.2.20.1803221117340.20609@uplift.swm.pp.se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/30kLdUUEzgkEmteSLr6OBIa8iH8>
Subject: [dnssd] multicast wifi draft mentioned in the session today
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 10:20:09 -0000

https://tools.ietf.org/html/draft-ietf-mboned-ieee802-mcast-problems-01

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Mar 22 04:41:22 2018
Return-Path: <christopherwood07@gmail.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572A1124235 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 04:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 F2DmI-0Fq9mn for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 04:41:19 -0700 (PDT)
Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E60D112420B for <dnssd@ietf.org>; Thu, 22 Mar 2018 04:41:18 -0700 (PDT)
Received: by mail-yw0-x236.google.com with SMTP id c20so2699017ywa.2 for <dnssd@ietf.org>; Thu, 22 Mar 2018 04:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=WCa3KSE7cOjPtvMZ0MeJTws/waMPDaNqxAdjm4GX0ns=; b=cQA00W90JraZjpDbbElUsmhzbQd/KBMOAAKS+7H0UZu0aB6M2wI1ienLwfl4V5rsc9 V/30Hopq5NHlr/QboHDyuMgWUj4pCITxHl8WXH3hvUdg6eAGpb86cgc1y3SqtkrS2UOh GR7P1icYoIbAFVVzsthbflkWOzyuhYPOJjqmldbT3q70yLFUU7s+YOuXb63V/FrE93A+ xuyoz+IYStjbrVyt7Fb8dxcpLuzwsbkwabhW1i6n+86srTzYeF5uCheLgfvE5Dz70ikO lcGkE39B3n404NBvSUDNbOWp5ZwHiHJJcLutmQhu0qgaG30uLThmoQV3TFoBScz04DM7 VkwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=WCa3KSE7cOjPtvMZ0MeJTws/waMPDaNqxAdjm4GX0ns=; b=EgawVMUjlSzy/7I+ZU8ShIvyndFYThc1zG40vhldWwPqy4gNt6EHHSvWFiisJZIQ4X 5QV5ssAXV5NeXbpTR1YScCPJT1rmY8fDSQZyNi8gu547Y7oF2p3lmzqp9ETda7LPQ7xD zoKMK7QBkxfkf3PngyCU+iq/CBZSW+3xOVg2jfJWwXNiIxcLEIAEK9TauabRdIlBF6Fx lLMTPIKfCW3UGRYBfOaUy/KwMBX6PWXDO2r0FbFSH3yOEj86EFOiwfF/OOqSmXRtwj4b Mil2joYfOfLrw5RzCSsq9UrNalYlkykks18FTYC7B8by3n8rhFYTmDoaFSKjs+jNIz4j T3yg==
X-Gm-Message-State: AElRT7G7flCEoVtVJeZQNzX1ensjr921lyKFvJOotlBQDgDu/jAkXRKo 64yQ/NTn+thz2K/CcRNKCR9AZVVkhE1THVPmujCCDTVG
X-Google-Smtp-Source: AG47ELtZkeR5P0E90fk/LnP04tkwVfQnQYFRzOg7XEKL4AXQZ3HXmPp5j+ljqHxEVVF6u/B0wo/aIHiXBSKQbFnha3g=
X-Received: by 10.13.240.197 with SMTP id z188mr13945863ywe.79.1521718877845;  Thu, 22 Mar 2018 04:41:17 -0700 (PDT)
MIME-Version: 1.0
From: Christopher Wood <christopherwood07@gmail.com>
Date: Thu, 22 Mar 2018 11:41:07 +0000
Message-ID: <CAO8oSXkx_0jDwpjVrwLF6DCzEpoHVja1dDXXbKCRhpCBkSU3ew@mail.gmail.com>
To: dnssd@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/-5wJMTxT7Ygo8DE19QaigmUGmUU>
Subject: [dnssd] "Privacy, Discovery, and Authentication for the Internet of Things"
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 11:41:20 -0000

Wu, David J., et al. "Privacy, discovery, and authentication for the
internet of things." European Symposium on Research in Computer Security.
Springer, Cham, 2016.

https://arxiv.org/pdf/1604.06959.pdf%22

Best,
Chris


From nobody Thu Mar 22 04:42:05 2018
Return-Path: <dthaler@microsoft.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E09B8124235 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 04:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 Qv3R8LYO-pHK for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 04:42:02 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0709.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe49::709]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236B012420B for <dnssd@ietf.org>; Thu, 22 Mar 2018 04:42:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=3aM8PGSKLOuzSbyYnrIfq0URGkMqsWiBODwbw67ZJ54=; b=Mmmn/ElS/nq01PlK0FkefoM/3rAhGqhwTa4nEGyNtgRIo2tkNO3MPq9kCAzxf+GFV66BvCVP4j4tWDsmedvvr5stMRL7MZLIJcZXvQ8IBdSpDwmNU0Tg3kk6bYH25p6thHEbZe6WNtMmET/H5/+RO/1JYBJpkzwttE8O0GQkvCs=
Received: from CY4PR21MB0774.namprd21.prod.outlook.com (10.173.192.20) by CY4PR21MB0150.namprd21.prod.outlook.com (10.173.189.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.0; Thu, 22 Mar 2018 11:42:00 +0000
Received: from CY4PR21MB0774.namprd21.prod.outlook.com ([fe80::41f5:f274:8793:f7b1]) by CY4PR21MB0774.namprd21.prod.outlook.com ([fe80::41f5:f274:8793:f7b1%8]) with mapi id 15.20.0631.007; Thu, 22 Mar 2018 11:42:00 +0000
From: Dave Thaler <dthaler@microsoft.com>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: Affiliation Hiding Authentication
Thread-Index: AdPB0Y72MKVOEgqxTU+Ie1jkxiFzRg==
Date: Thu, 22 Mar 2018 11:42:00 +0000
Message-ID: <CY4PR21MB07741C803F556D4EAE76D157A3A90@CY4PR21MB0774.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=dthaler@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-03-22T11:41:58.7966162Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [31.133.149.159]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR21MB0150; 7:5GIqkMx+uhrcgn7L1Wk60HuFYsP0bbERAalUYePfsmmgqggCTtQUy2Hk7o7y8/5rZGGk64gQlNb4HeH/vG6dOeQtuG9pR0PGY+gCacX3UF/JZho7e7zJHPhqhavKFksNmDDPT8c39WtbNa733vHUbrUc5pNMNqxPi3cyGI/VFObF4psnl9WZjTJQKVbpbdgAxjkGGaT0YSTvHksxwO69bRM1hfLy0ZuB49OVrOSZBbvy5zkWDi/FBJR/J2gQdEst; 20:GGj0FFp8eOt3Kx59L6gbg9WStTJlZunalHGyFFwn7ILSB19qpE7aiM6u7KfpkjX3zDN0yaYN5RTp2NNG1pKyeEHRWmRRGcrqQFq1mkroeBivoDbo5AbeS8wc8ViUcOwirVMrj3R9Xc4bL1n0Ur95Dg8msZh/Lbii2bhW4U1VEwE=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 03c7afdd-dbb1-47ca-860d-08d58fe9ecc4
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7193020); SRVR:CY4PR21MB0150; 
x-ms-traffictypediagnostic: CY4PR21MB0150:
x-microsoft-antispam-prvs: <CY4PR21MB0150DA2391B457BF670CDCD5A3A90@CY4PR21MB0150.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(120809045254105)(21748063052155); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(61425038)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231221)(944501327)(52105095)(6055026)(61426038)(61427038)(6041310)(20161123560045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(6072148)(201708071742011); SRVR:CY4PR21MB0150; BCL:0; PCL:0; RULEID:; SRVR:CY4PR21MB0150; 
x-forefront-prvs: 0619D53754
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39380400002)(366004)(346002)(39860400002)(396003)(199004)(189003)(5250100002)(2501003)(97736004)(14454004)(790700001)(6116002)(3846002)(186003)(102836004)(6506007)(6346003)(26005)(33656002)(966005)(10290500003)(478600001)(81156014)(1730700003)(8676002)(3480700004)(8936002)(81166006)(7736002)(74316002)(7116003)(5660300001)(2351001)(106356001)(2900100001)(105586002)(25786009)(53936002)(236005)(6436002)(5640700003)(6306002)(54896002)(9686003)(55016002)(3280700002)(8990500004)(7696005)(99286004)(10090500001)(316002)(5630700001)(606006)(86362001)(66066001)(3660700001)(6916009)(68736007)(86612001)(2906002)(22452003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0150; H:CY4PR21MB0774.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com; 
x-microsoft-antispam-message-info: FvhXWBzAiyOzCu9er4IaHNgOJ0dkSb6yIzzuniNlst/DqFR+oBq//06w8l83hDSvcNS5aj4q9gY03xikVrHVExF7mixT6jxt6RWV0fuebzdykhlry9DZZJfB+kqsgKfZ4D+SdSKKwes7jW1Jefh9LSmjKGORxu5Z1C9PebHU1BfcIOxP8/TLgBSrdHxiu0i5AC3WLc7s/rHNr5vHwNlIukkVH5w1IFKgUsliXBOoohwHBGLK/92IxbsXNtxRwQPXTrc/dX8/2YRdkt+fIt/a3atGOTY94Kzexw26Oo1ExLgg55hBG5QvfJHCPC2b2KFf07E6WaYBJ/jnAb6ym/oy5w==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR21MB07741C803F556D4EAE76D157A3A90CY4PR21MB0774namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 03c7afdd-dbb1-47ca-860d-08d58fe9ecc4
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 11:42:00.2945 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0150
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/72Ev2OOBHECSc-9NDoBOlZsxWzA>
Subject: [dnssd] Affiliation Hiding Authentication
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 11:42:04 -0000

--_000_CY4PR21MB07741C803F556D4EAE76D157A3A90CY4PR21MB0774namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

For the 2 slide intro and pointers to key work in this area, see
IETF 99 T2TRG meeting:
Slides 17-18 of https://www.ietf.org/proceedings/99/slides/slides-99-t2trg-=
chair-slides-00.pdf
That's the main link to look at.

For the mail to the CFRG list on the topic:
https://mailarchive.ietf.org/arch/msg/cfrg/AXBngLPD1FFSJcqFm7_GU7RzBMM

It was also brought up at the IETF 97 CoRE WG meeting.
Slide 194 of https://datatracker.ietf.org/meeting/97/materials/slides-97-co=
re-consolidated-slides-06

Dave

--_000_CY4PR21MB07741C803F556D4EAE76D157A3A90CY4PR21MB0774namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">For the 2 slide intro and pointers to key work in th=
is area, see
<o:p></o:p></p>
<p class=3D"MsoNormal">IETF 99 T2TRG meeting:<o:p></o:p></p>
<p class=3D"MsoNormal">Slides 17-18 of <a href=3D"https://www.ietf.org/proc=
eedings/99/slides/slides-99-t2trg-chair-slides-00.pdf">
https://www.ietf.org/proceedings/99/slides/slides-99-t2trg-chair-slides-00.=
pdf</a><o:p></o:p></p>
<p class=3D"MsoNormal">That&#8217;s the main link to look at.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For the mail to the CFRG list on the topic:<o:p></o:=
p></p>
<p class=3D"MsoNormal"><a href=3D"https://mailarchive.ietf.org/arch/msg/cfr=
g/AXBngLPD1FFSJcqFm7_GU7RzBMM">https://mailarchive.ietf.org/arch/msg/cfrg/A=
XBngLPD1FFSJcqFm7_GU7RzBMM</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It was also brought up at the IETF 97 CoRE WG meetin=
g.<o:p></o:p></p>
<p class=3D"MsoNormal">Slide 194 of <a href=3D"https://datatracker.ietf.org=
/meeting/97/materials/slides-97-core-consolidated-slides-06">
https://datatracker.ietf.org/meeting/97/materials/slides-97-core-consolidat=
ed-slides-06</a>
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dave<o:p></o:p></p>
</div>
</body>
</html>

--_000_CY4PR21MB07741C803F556D4EAE76D157A3A90CY4PR21MB0774namp_--


From nobody Thu Mar 22 08:05:02 2018
Return-Path: <christian@amsuess.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005ED12D890; Thu, 22 Mar 2018 08:05:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] 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 S1L-4K6MU-Sl; Thu, 22 Mar 2018 08:05:00 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0109B12D88D; Thu, 22 Mar 2018 08:04:56 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id 2C16049632; Thu, 22 Mar 2018 16:04:55 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 60C0D61; Thu, 22 Mar 2018 16:04:54 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2001:67c:370:128:d1a4:586c:a5dc:33d8]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id EB20C3A; Thu, 22 Mar 2018 16:04:53 +0100 (CET)
Received: (nullmailer pid 17491 invoked by uid 1000); Thu, 22 Mar 2018 15:04:52 -0000
Date: Thu, 22 Mar 2018 15:04:52 +0000
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: dnssd@ietf.org
Cc: draft-ietf-core-rd-dns-sd@ietf.org
Message-ID: <20180322150452.GA17015@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd"
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/xj4VKBDOoeYYiGHi7fivE0FNQVk>
Subject: [dnssd] CoRE Resource Directory interop events
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 15:05:02 -0000

--ZPt4rx8FFjLCG7dd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello DNSSD working group,

as pointed out in today's session, there are inteoperability events
planned for the CoRE Resource Directory, which has an integration point
under development with DNSSD in the ietf-core-rd-dns-sd draft.

The first event is being planned for in about two weeks (see thread on
[1]). We will likely not have any RD or RD client that does a DNSSD
export, but nonetheless invite interested parties to join us and have a
look at actual Resource Directories.

There will be a follow-up interop based on the experience gathered in
the first one probably around June, on which I hope to have RD-DNS-SD
implementations as well. The invitation mail for that will go to this
list as well, and I hope to have more experienced DNSSD implementors
participating in that.

Thanks for the input in the meeting, and best regards
Christian


[1]: https://mailarchive.ietf.org/arch/msg/core/x4o88wF_JYUu4oJlZbEM-ZaRhIU

PS: Please keep me in To or Cc when replying, as I am not regularly reading
the dnssd list.

--=20
You don't use science to show that you're right, you use science to
become right.
  -- Randall Munroe

--ZPt4rx8FFjLCG7dd
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEECM1tElX6OodcH7CWOY0REtOkveEFAlqzxg8ACgkQOY0REtOk
veHMww/9ERSUHFm6ykIfjEnE6WfhFnpZZSrVE+sons/EFPeaqKXajlGwMvVP6yD5
IjEGMTM5/ImuJ8S1XakFdqDGpkv18rhSjxDScVegqpKGe0sVL+koyuu/i5pBb0+t
s8G+ZC/qXftVZY4Enskq77gzIHadJsSpRe1QhrNy2a8aDD1nt87oEyqHPKQR1i4t
6VgCRM74pkwn8mw+PH7r3cpNe7WOxNQbgK5cjcxuUlhyjCqzCwf6XcA7zNyy2O89
BFutzW1ZK5VtOBkY121M4aldawTzjtYBodZ9K0VynaFsiOQbh0r4jO99TfjiOsb1
mteDerPFSb/QyfLHqSyoKhYbewRvoDKAhWJQWUCCMuAkR2Cs4+Q6v4GvewSYXs70
LoLsIWN7mgUWyDLVPvK7cIOUloSKz/oo+/wSneZTY/ZBD795YnrloUCjlAbjYzrE
HrPWCchDLJ4ePLESGk0WGAsnDeWUfKoMtVqf8Gpx15U8WL33C1wDVpdQ2saOeMNc
727rg42hE7T/UXYQsy5CJHIbviC68tbKVPvHcQ4HbghBTPePq7TuQ6adf+ma0WFv
/XZ4U4RTBU4HJ6a/agmUv+/HVcDlVCWE3xw9d4yu/+FPwVfkEtEmYvWqaN7Thtiq
y3mccFxF+llJ4f+Trf61v4mHy4kzfmT+KqD3mY74WRdt4l6kZBw=
=5t9l
-----END PGP SIGNATURE-----

--ZPt4rx8FFjLCG7dd--


From nobody Thu Mar 22 08:08:52 2018
Return-Path: <mellon@fugue.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C5F12D883 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 08:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
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 oUT_I7B1PSjh for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 08:08:48 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 187C912D96A for <dnssd@ietf.org>; Thu, 22 Mar 2018 08:08:46 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id s18so9042584wrg.9 for <dnssd@ietf.org>; Thu, 22 Mar 2018 08:08:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Tc3AvWywCy7AyT2oV5bsoj6ChbG441bJRSUSMhubdjg=; b=dZ1N6yOyKBHJo+MCQhKQwhR52gEmQzAnQ8uHrS4oxA68GJBJrnCC6TSIZhaBi2i1jK U0Rh8eNw3j9kaQOoWs7A2oab71eTd8WYGRORYtqEYjQFWi3+DweGrLO8BTchbf5PDxEI +Euc+T/wl5fSZsAR7c9AgYehB+cKji9QLLuiTWfe1p398JyFBaYngJiJERYkSUTpVROx UzgmfNaNPpTaxnFHNlHdHWX1DikZzrfeRKHDGoQS1/WECHql4Idr8pJvizHf5Erusrj2 +LUYHWngPSqpeUPdW4dyD3Q6xQ9RC+BgGl1mhpmAq4nn4SIYRIFzhYFSNbT2FSzPRU+H GR1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Tc3AvWywCy7AyT2oV5bsoj6ChbG441bJRSUSMhubdjg=; b=cG+fMIeSiDKAcGK1zsq22R2O2pmOIgyU09B6fvSzi6FNIS/LXnD2mCCJv83KtxQK4d SSi2tc/4cIg9cBX+TmQ45TMzFHiM3q8+ZfnvvII3XPfUzxuCrrg5lhUCzFHeM4tOKdMs QimBah2LKVo4zC+zjJvo0wA4fYYyWAYdgr0HzSgVyHAvTR995pBveI/g/qnut6B9+ab7 uWUI5EwUDokC/EmV6PInR4FrCGU+a1TU55NA6kNe53r/JA5W+7fH1J6/6Tv2j7pGxfzD z9rqhSAHxcgM3+bbnr4cOMNNRCLBVh7SgI0zzgb98T4TorjawWFQ6hI/RzK7BEd/3vEa QJ9A==
X-Gm-Message-State: AElRT7EUG61QuYOkzfBo1K8hzNKQofH90NqjUnObZi4GcZzGnjWNdJ2r MSUkWMprhhSlupZUk/dHzIBE2Q==
X-Google-Smtp-Source: AG47ELsqr5BkHAX1ydQV3b8eSJLtc0u85gb59OMlhhx+e9GO7QrqiCU+vxqyAav9Egr5s4essDaoHA==
X-Received: by 10.223.176.253 with SMTP id j58mr20084587wra.269.1521731324585;  Thu, 22 Mar 2018 08:08:44 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:1998:2c6a:185d:e5b4:7ae1? ([2001:67c:370:1998:2c6a:185d:e5b4:7ae1]) by smtp.gmail.com with ESMTPSA id x128sm5450807wmg.20.2018.03.22.08.08.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Mar 2018 08:08:43 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <995F4070-31DE-4FF9-A1A8-1AB0C360B7EF@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6CCC3D17-9A0C-4FE4-9BB2-850A50CD62A4"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Thu, 22 Mar 2018 15:08:42 +0000
In-Reply-To: <20180322150452.GA17015@hephaistos.amsuess.com>
Cc: dnssd@ietf.org, draft-ietf-core-rd-dns-sd@ietf.org
To: =?utf-8?Q?Christian_Ams=C3=BCss?= <christian@amsuess.com>
References: <20180322150452.GA17015@hephaistos.amsuess.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/MkuS273xFM2PcD4rb1fewBqViWc>
Subject: Re: [dnssd] CoRE Resource Directory interop events
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 15:08:51 -0000

--Apple-Mail=_6CCC3D17-9A0C-4FE4-9BB2-850A50CD62A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Mar 22, 2018, at 3:04 PM, Christian Ams=C3=BCss =
<christian@amsuess.com> wrote:
> There will be a follow-up interop based on the experience gathered in
> the first one probably around June, on which I hope to have RD-DNS-SD
> implementations as well. The invitation mail for that will go to this
> list as well, and I hope to have more experienced DNSSD implementors
> participating in that.

Thanks for this.   It would be good if this interop could not clash with =
the Thread meeting in Austin, if possible.   That's June 26-28; probably =
would be nice to avoid the days around that as well. :)


--Apple-Mail=_6CCC3D17-9A0C-4FE4-9BB2-850A50CD62A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">On =
Mar 22, 2018, at 3:04 PM, Christian Ams=C3=BCss &lt;<a =
href=3D"mailto:christian@amsuess.com" =
class=3D"">christian@amsuess.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">There will be a follow-up interop based =
on the experience gathered in</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">the first one =
probably around June, on which I hope to have RD-DNS-SD</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">implementations as well. The invitation mail for =
that will go to this</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">list as well, and I =
hope to have more experienced DNSSD implementors</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">participating in =
that.</span></div></blockquote></div><br class=3D""><div class=3D"">Thanks=
 for this. &nbsp; It would be good if this interop could not clash with =
the Thread meeting in Austin, if possible. &nbsp; That's June 26-28; =
probably would be nice to avoid the days around that as well. =
:)</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_6CCC3D17-9A0C-4FE4-9BB2-850A50CD62A4--


From nobody Thu Mar 22 10:12:15 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9980012EAFF for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 OqjeBfrSTsFk for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:12:08 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D216212EB35 for <dnssd@ietf.org>; Thu, 22 Mar 2018 10:11:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521738718; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=LNThkZD8y5Y16f8udWEoEhk7ThQmTUt6G+lBcORrzz4=; b=ABI70MkZa44Bxo4XgOWxGb/Y25cxA8lM8FIxK9Ryl+5VGndZeThF3KcsQ1sOvkorxxx5K/ezQBUEWEKYjyI0XAfm0A2cx/voc1qp0FzHL+xVml9l4hC/ZFF6u96FISWQ0kKkIywBIoO14nqe+OSirw7V5Oj5wmgz0lxlvkGZLZY=
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-ve1eur03lp0145.outbound.protection.outlook.com [213.199.154.145]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-104-bsnJAN1sOkGrD3TzGsZTGw-1; Thu, 22 Mar 2018 17:11:55 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB0813.eurprd07.prod.outlook.com (10.161.107.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.5; Thu, 22 Mar 2018 17:11:53 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Thu, 22 Mar 2018 17:11:53 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: WG Adoption call: draft-sctl-dnssd-mdns-relay-04
Thread-Index: AQHTwgDfNE3IhOu0iU6kaE8gbB5KPA==
Date: Thu, 22 Mar 2018 17:11:53 +0000
Message-ID: <A0846F10-E10B-4E4A-8EE9-28341A51C4E1@jisc.ac.uk>
References: <152166197761.21207.125081055720989702@ietfa.amsl.com>
In-Reply-To: <152166197761.21207.125081055720989702@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [31.133.149.60]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB0813; 7:x9qPJStVEC5U2CDBufI450kqRxF9Rq6LtRCmlKxLJSCJzhnM93ioEO5y8pGLMjzC0xNuXbCT+ZANzo4EXF001q4dOCPLtY/1j7HgenT1n4Dy5GG7yPWF9PlaYtcm6Zg4XPoJqG3K0K/Bj8zrqqL7EjIao/mmIv9dRq/UFZl/esvdhzNK76Nb9DsB5FrBy42Wvlv4GNVSPrKOFBKxIAiIBCpu10eZPoByLO+4EXwS+SHw4+7pp5kl/uHGhh6ysmcs; 20:E1a42fIMekdJB9+O4PYlE3TMW741g0TVJxKVInEnijT13JKxaxZqHXCMKCMzjSD+9ASEl30z2UvPvddVpJURx7wi4GgDbFuFP9pobWCR0ndIpg+1sGGPLormXYmZuVf3hhl3iR/xSw3uBjqF7a57p+RoI6GvK0DCX7x5MbeILnI=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: f50a6329-9779-4b1e-2c80-08d590180272
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB0813; 
x-ms-traffictypediagnostic: VI1PR07MB0813:
x-microsoft-antispam-prvs: <VI1PR07MB08134988BDA9503DDC4B5668D6A90@VI1PR07MB0813.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231221)(944501327)(52105095)(93006095)(93001095)(10201501046)(3002001)(6041310)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR07MB0813; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB0813; 
x-forefront-prvs: 0619D53754
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39850400004)(396003)(346002)(376002)(39380400002)(366004)(377424004)(189003)(199004)(6486002)(478600001)(6306002)(446003)(6512007)(83716003)(2900100001)(74482002)(5640700003)(3660700001)(6436002)(25786009)(66066001)(316002)(53936002)(786003)(72206003)(966005)(57306001)(305945005)(2501003)(6916009)(5890100001)(5250100002)(33656002)(86362001)(14454004)(7736002)(3280700002)(106356001)(8936002)(53546011)(6506007)(8676002)(76176011)(50226002)(59450400001)(6116002)(97736004)(81166006)(1730700003)(99286004)(2351001)(26005)(186003)(81156014)(102836004)(36756003)(3846002)(2906002)(82746002)(68736007)(105586002)(5660300001)(11346002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB0813; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
x-microsoft-antispam-message-info: ypaRpVZOTkyvZwG46Yynxtwuw/1/xggiolJVSUQkWGXaZcAuV3EvE4UsD+Wv7nXXnowJcuWzbfsfKqOyWuoCwL9o3Qn55BzpZGNqb2pSXhy3ZnzanaYCN6V0P+RxAUuPFj7TumRYBEM7nwxLeEzsud0+MQdUG8ga6XPdctSgnPYSPKpGm09l6rNMWLx2xZ4uBRacR8cmEkVrjXSIOX3N04gRwV24pfN052C0zo/ob2AzjM3rHnsa6FK2fiFXBWMaQXE0/d0AxaDoNt34vIVahSk2aZsNOItQE8VUAAKtAp37WNGPwA0K8fE+a4zYJNyYUwcrow6IC/kQs38W2JQYaA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <BE2A128E6471E745B8F5B51B508197A1@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: f50a6329-9779-4b1e-2c80-08d590180272
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 17:11:53.6507 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB0813
X-MC-Unique: bsnJAN1sOkGrD3TzGsZTGw-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/it6pYs1d08UhLIyOitaZKiybhb8>
Subject: [dnssd] WG Adoption call: draft-sctl-dnssd-mdns-relay-04
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 17:12:13 -0000

Hi,

In the dnssd WG meeting today we agreed adoption of draft-sctl-dnssd-mdns-r=
elay-04 (see below) as a WG item subject to confirmation on the list.

If you were not at the meeting, please indicate support or any objection to=
 the adoption by Thursday 29th March.

Ted's slides from today's discussion can be found at https://datatracker.ie=
tf.org/meeting/101/materials/slides-101-dnssd-dns-sd-discovery-relay-01

Tim=20

> On 21 Mar 2018, at 19:52, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
>=20
>        Title           : Multicast DNS Discovery Relay
>        Authors         : Stuart Cheshire
>                          Ted Lemon
> =09Filename        : draft-sctl-dnssd-mdns-relay-04.txt
> =09Pages           : 20
> =09Date            : 2018-03-21
>=20
> Abstract:
>   This document extends the specification of the Discovery Proxy for
>   Multicast DNS-Based Service Discovery.  It describes a lightweight
>   relay mechanism, a Discovery Relay, which allows Discovery Proxies to
>   provide service on multicast links to which they are not directly
>   attached.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-sctl-dnssd-mdns-relay/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-sctl-dnssd-mdns-relay-04
> https://datatracker.ietf.org/doc/html/draft-sctl-dnssd-mdns-relay-04
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-sctl-dnssd-mdns-relay-04
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Thu Mar 22 10:18:30 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 951BF126CC7 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 Vka1xRodmGZ2 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:18:21 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D0DB126D45 for <dnssd@ietf.org>; Thu, 22 Mar 2018 10:18:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521739099; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=obpu3++LZk2/j6DlcbYm76qN7GbVtx/HhauAdTnbxHs=; b=RtAbCy+WLgQW3Tec0CPt5mm3flgiPyMrjpob94UQ1qwAH4N1NQb71tTkrmTkyPKTdXsXfP+mmzVWUYmOmtoRyTG3CMYxuAWyXJjaHTmv4nSoIMxG1xQOf2XeEm6E1tcKLiuwY1X/K0KCO8LEM12tehWArYLGJOqiTnHcip9figg=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0239.outbound.protection.outlook.com [213.199.154.239]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-113-O0QEvZfFObulYWWJWh9p1Q-1; Thu, 22 Mar 2018 17:18:16 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB1022.eurprd07.prod.outlook.com (10.161.111.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Thu, 22 Mar 2018 17:18:13 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Thu, 22 Mar 2018 17:18:13 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: WG adoption call: draft-cheshire-dnssd-roadmap-01
Thread-Index: AQHTwgHBgiFR3VmZ40aGekLH6PKkFQ==
Date: Thu, 22 Mar 2018 17:18:12 +0000
Message-ID: <26D6FE7F-0A4C-4953-8C54-BE5C9769D545@jisc.ac.uk>
References: <152166103312.21353.10731419347307517445@ietfa.amsl.com>
In-Reply-To: <152166103312.21353.10731419347307517445@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:67c:1232:144:1011:5110:cdc1:1efe]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1022; 7:Zd6LRh1B3NFq3CqOTiJw8I6s8K8ZEBkcjR/JelHkv11WLzXRM7eK95ZAiF2dqmGkgzdFXGyw+DHxVrnE7HmnVhmPDy+VPJC7W+YGeG8rbAImXwqsN6ON/rGelqyioRrugbX5T9CFkrUe9lfukvFcF57Nw0nK0wtl669YyQ5keBejN2QC36ArCtxZ/eRTHhwahEZdmQnXFYiMBd8uYJVOpuzKlSCLgm9sfzKL/rTmqABomQL/Nxypk4UL9BrC3E30; 20:4XOjoDJNXf1gef42Pn7C+d0VPBajNIILPBcmYzpjneiORJEYjcdZzw0u3JpHbY43w5eSKEbagGbmY71xpZkQrhUHK1c/mOJGRJ2ZkrjyFawCkwIetCPyFxqNGF4Re39E8wQ8VC+WlXAUe1gpC/yzKw0S+WnDQ3o9OwKQ4HQOW7g=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 14e29dc6-9913-4f37-695e-08d59018e49b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1022; 
x-ms-traffictypediagnostic: VI1PR07MB1022:
x-microsoft-antispam-prvs: <VI1PR07MB10226565F0B82881B1F4D29ED6A90@VI1PR07MB1022.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231221)(944501327)(52105095)(3002001)(10201501046)(6041310)(20161123560045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:VI1PR07MB1022; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1022; 
x-forefront-prvs: 0619D53754
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(39380400002)(39850400004)(396003)(346002)(376002)(377424004)(199004)(189003)(6512007)(81156014)(8936002)(8676002)(82746002)(68736007)(1730700003)(83716003)(102836004)(50226002)(25786009)(57306001)(3660700001)(186003)(2900100001)(46003)(446003)(86362001)(478600001)(81166006)(6116002)(2906002)(33656002)(2501003)(72206003)(6916009)(36756003)(105586002)(966005)(786003)(316002)(5660300001)(53546011)(76176011)(14454004)(3280700002)(6306002)(2351001)(6436002)(99286004)(5640700003)(59450400001)(106356001)(74482002)(6486002)(305945005)(7736002)(97736004)(5250100002)(6506007)(53936002)(11346002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1022; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
x-microsoft-antispam-message-info: /pE/vLFSP/r+TsEWcAc12HRppjpvaSRvsHgqmYNQwZLRj4TfTBRwp1nfOVY2KjTQKcMsXSma1TIL30Kt+0PGTkjoMEGAkuYNlk4zy87sCiu+Iy6gYPFEWfFV8XBrmTJQDR9XthscWP5geL36GmEOK1KqA9UtW8IjW/LNQ6Gyk/sw4caSa8XNbedchYtD0+tcgUxTDZjr411X54IQ6l0PDfA/AYrd/HJtwBCyOd+CQSuNCLPvRTXCT+4vYbtUcGsj+Nw93vNgWXZ4M25TQrr1IkSJxKQJq1A6p6OkD+dFPfQZqIW2j4JWCOf+7ryTLktqznn4A7YQNFbrdyE/C1qMGg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <94562DC544A7A545A14095C17E84AD32@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 14e29dc6-9913-4f37-695e-08d59018e49b
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 17:18:12.4923 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1022
X-MC-Unique: O0QEvZfFObulYWWJWh9p1Q-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/4_tvTpZaW0eAcnMosv1UGNlFTrk>
Subject: [dnssd] WG adoption call: draft-cheshire-dnssd-roadmap-01
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 17:18:25 -0000

Hi,

In the dnssd WG meeting today we agreed adoption of draft-cheshire-dnssd-ro=
admap-01 (see below) as a WG item subject to confirmation on the list.  The=
 documents explains the components of the DNS-SD model, and how they relate=
.  Note that adoption doesn't necessarily mean we'll need to publish the do=
cument, but the feeling in the room was that it's a useful document to show=
 the direction of travel of the WG, and as an intro to the components for a=
nyone new to the WG.

If you were not at the meeting, please indicate support or any objection to=
 the adoption by Thursday 29th March.

The roadmap document now includes an Appendix, "IETF Terminal Room Printer =
Discovery Walk-through", explaining how DNS-based service discovery works f=
or the printer in the IETF terminal room.

Tim=20

> On 21 Mar 2018, at 19:37, internet-drafts@ietf.org wrote:
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
>=20
>=20
>        Title           : Service Discovery Road Map
>        Author          : Stuart Cheshire
> =09Filename        : draft-cheshire-dnssd-roadmap-01.txt
> =09Pages           : 19
> =09Date            : 2018-03-21
>=20
> Abstract:
>   Over the course of several years, a rich collection of technologies
>   has developed around DNS-Based Service Discovery, described across
>   multiple documents.  This "Road Map" document gives an overview of
>   how these related but separate technologies (and their documents) fit
>   together, to facilitate service discovery in various environments.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-cheshire-dnssd-roadmap/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-cheshire-dnssd-roadmap-01
> https://datatracker.ietf.org/doc/html/draft-cheshire-dnssd-roadmap-01
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-cheshire-dnssd-roadmap-01
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From nobody Thu Mar 22 10:34:23 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D245126D45 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 vgnMonkMFPwg for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 10:34:17 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9069126579 for <dnssd@ietf.org>; Thu, 22 Mar 2018 10:34:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521740055; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=Y2zPpSYbif+1YdSM2c5edV/bvHkFEsL984jh5rrsIgY=; b=PbwmCAebZfvvTviqTWTGRstbrylWAL27kZrpQyV6VZkhTUDePJLlgAn3CLARR3QbOkOel7FMpYc/BV5uYg417L7nnQ5LpsQtln88ZQVB5Hs5e/54ytiOuQblZUyfNm2QDzXpS9Ai7yqDD1W7ZE7i1LauPGJqEScVjIh9GF7g2O8=
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-am5eur02lp0143.outbound.protection.outlook.com [213.199.180.143]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-67-C8qhc-BINBibhrHCbkMThA-1; Thu, 22 Mar 2018 17:34:12 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB1312.eurprd07.prod.outlook.com (10.164.92.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.609.6; Thu, 22 Mar 2018 17:34:07 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Thu, 22 Mar 2018 17:34:07 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Ted Lemon <mellon@fugue.com>
CC: =?utf-8?B?Q2hyaXN0aWFuIEFtc8O8c3M=?= <christian@amsuess.com>, "dnssd@ietf.org" <dnssd@ietf.org>, "draft-ietf-core-rd-dns-sd@ietf.org" <draft-ietf-core-rd-dns-sd@ietf.org>
Thread-Topic: [dnssd] CoRE Resource Directory interop events
Thread-Index: AQHTwe8wvXst4damwUy3AD9uyeQYcqPcW3UAgAAooAA=
Date: Thu, 22 Mar 2018 17:34:07 +0000
Message-ID: <254E18B1-CC8C-42D9-80BC-6FC06A186C4E@jisc.ac.uk>
References: <20180322150452.GA17015@hephaistos.amsuess.com> <995F4070-31DE-4FF9-A1A8-1AB0C360B7EF@fugue.com>
In-Reply-To: <995F4070-31DE-4FF9-A1A8-1AB0C360B7EF@fugue.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:67c:1232:144:1011:5110:cdc1:1efe]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1312; 7:m7ZW2L4l4zudgZmI4KqY9c6EQdEt61Qf5xw93HrmtVsmD2fv77TD396JjVoYPPASZuSL0ZdyWgsr2l/PKbgOON9AN1Z7QZPXOvPkOfbQ2QRR9CfRQmmaewIKozmRF60JPMmpCrPn2gvaF8t72eGT+22KEMjxzRNllUYeggUkQpMDfGTT6LxeXG8U6mcrTzPBZg9bXQ/8d8ZeAXaqV86evSaOAsiyH5ONIZq8GEZTi2IN7z424686+WzK3Sa39irh; 20:PQcWmdh083poUkErQO+eYtraJkIeEczGRhxOhBpkojNKBN4VHPa9c10O0ySyvLTtrMKq/0z1+tyZL0+arSsIGstS21KESia8apWyFIt1xzs/OLH/Un5e0EIzokTE++BTuOMUOiyyPlDUUKvrpbJl+r+xUtHjtGjho/QL9hqwyKk=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 2f65f9e8-8c59-4c40-d73b-08d5901b1d4e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1312; 
x-ms-traffictypediagnostic: VI1PR07MB1312:
x-microsoft-antispam-prvs: <VI1PR07MB1312BF017E1C0C8AB3BCCE9CD6A90@VI1PR07MB1312.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(231250463719595);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231221)(944501327)(52105095)(6041310)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:VI1PR07MB1312; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1312; 
x-forefront-prvs: 0619D53754
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(366004)(346002)(396003)(39380400002)(39850400004)(189003)(199004)(5250100002)(4326008)(186003)(2906002)(2900100001)(105586002)(14454004)(33656002)(54906003)(6512007)(25786009)(6486002)(74482002)(81166006)(5660300001)(81156014)(8936002)(11346002)(50226002)(68736007)(3660700001)(102836004)(6246003)(3280700002)(6116002)(46003)(36756003)(7736002)(97736004)(83716003)(53936002)(99286004)(8676002)(229853002)(53546011)(316002)(6916009)(478600001)(6436002)(6506007)(57306001)(786003)(106356001)(76176011)(72206003)(446003)(305945005)(82746002)(86362001); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1312; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
x-microsoft-antispam-message-info: 9vwei8gAUG52xo9iRz+F/1BwiOFINgTsfu6IfsYra4U64fsfMEu3LG7bVSlA2kSTXJz6eBgpEveDmyhW3lo9oywMqS8mOJcdrR9aLSyuY+xoXhMwAtrZAkVy/S2hohn8lC9bXWxJ8zZpxUaLSJh8rSyDdPkawQaeTGWZR7VeBWqsaZ9Mcsq6GRVmNwGxbfSO0BTdhwlBXY7BM4pLJSMPTbZYLigc3Qm3ctoPxBW9+JTtH/+wp/xdSVxLG/18y0h/tGCtMD0rg7YWfVzlQdt9U1llurIv16eojH13bCTJp0Z5W684OjCKwdh07JVr9Mb9SM0D6YJnvw+06BFSwvZ7qg==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <DB91976DE0999D409E3B55B37C0924CE@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 2f65f9e8-8c59-4c40-d73b-08d5901b1d4e
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 17:34:07.1766 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1312
X-MC-Unique: C8qhc-BINBibhrHCbkMThA-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/_07PhD-mO8cQZtRLYgntVEqULKw>
Subject: Re: [dnssd] CoRE Resource Directory interop events
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 17:34:22 -0000

PiBPbiAyMiBNYXIgMjAxOCwgYXQgMTU6MDgsIFRlZCBMZW1vbiA8bWVsbG9uQGZ1Z3VlLmNvbT4g
d3JvdGU6DQo+IA0KPiBPbiBNYXIgMjIsIDIwMTgsIGF0IDM6MDQgUE0sIENocmlzdGlhbiBBbXPD
vHNzIDxjaHJpc3RpYW5AYW1zdWVzcy5jb20+IHdyb3RlOg0KPj4gVGhlcmUgd2lsbCBiZSBhIGZv
bGxvdy11cCBpbnRlcm9wIGJhc2VkIG9uIHRoZSBleHBlcmllbmNlIGdhdGhlcmVkIGluDQo+PiB0
aGUgZmlyc3Qgb25lIHByb2JhYmx5IGFyb3VuZCBKdW5lLCBvbiB3aGljaCBJIGhvcGUgdG8gaGF2
ZSBSRC1ETlMtU0QNCj4+IGltcGxlbWVudGF0aW9ucyBhcyB3ZWxsLiBUaGUgaW52aXRhdGlvbiBt
YWlsIGZvciB0aGF0IHdpbGwgZ28gdG8gdGhpcw0KPj4gbGlzdCBhcyB3ZWxsLCBhbmQgSSBob3Bl
IHRvIGhhdmUgbW9yZSBleHBlcmllbmNlZCBETlNTRCBpbXBsZW1lbnRvcnMNCj4+IHBhcnRpY2lw
YXRpbmcgaW4gdGhhdC4NCj4gDQo+IFRoYW5rcyBmb3IgdGhpcy4gICBJdCB3b3VsZCBiZSBnb29k
IGlmIHRoaXMgaW50ZXJvcCBjb3VsZCBub3QgY2xhc2ggd2l0aCB0aGUgVGhyZWFkIG1lZXRpbmcg
aW4gQXVzdGluLCBpZiBwb3NzaWJsZS4gICBUaGF0J3MgSnVuZSAyNi0yODsgcHJvYmFibHkgd291
bGQgYmUgbmljZSB0byBhdm9pZCB0aGUgZGF5cyBhcm91bmQgdGhhdCBhcyB3ZWxsLiA6KQ0KDQpT
ZWNvbmRlZC4gSXQncyBsaWtlbHkgdGhhdCB0aGUgcmVjaGFydGVyaW5nIHdvcmsgZGlzY3Vzc2Vk
IHRvZGF5IHdpbGwgaW5jbHVkZSBzb21lIGZvcm0gb2Ygd29yZGluZyBvbiBjb2xsYWJvcmF0aW9u
IC8gaW50ZXJvcGVyYXRpb24gd2l0aCBvdGhlciBTRCBwcm90b2NvbHMsIHNvIGFueSBwYXJ0aWNp
cGF0aW9uIGZyb20gdGhlIFdHIGluIHRoZSBldmVudCBDaHJpc3RpYW4gaGFzIGZvcndhcmRlZCB3
b3VsZCBiZSB3ZWxjb21lZCBieSB0aGUgY2hhaXJzLg0KDQpUaW0=


From nobody Thu Mar 22 11:40:30 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801E212E883 for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 11:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 7tOGTFKkryuq for <dnssd@ietfa.amsl.com>; Thu, 22 Mar 2018 11:40:18 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33E09126DCA for <dnssd@ietf.org>; Thu, 22 Mar 2018 11:40:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1521744016; h=from:subject:date:message-id:to:mime-version:content-type:content-transfer-encoding; bh=qNGTQzmTtaJhn1MUWR6AdbLwGzgO2F0///we6RNJWks=; b=Qgq6LCazGwZ672awzfg5lKxLbV+gtRIB+EhaSUCbU+tUh+shDZezOisB8Lz9+0T8XkXHRFBDBa6q23sEZhpNclFxVXHJlJdkSYW/NG2pJIMqGdyCrrhUWLlDx2MDKhzo6IVGf12Ybeyn+oztkvAopD3c5qouEcJYpdKZoj3/bvc=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0177.outbound.protection.outlook.com [213.199.154.177]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-5-hQ0Rj4yoN1qpdoj89u-JWg-1; Thu, 22 Mar 2018 18:40:13 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB1566.eurprd07.prod.outlook.com (10.165.239.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.5; Thu, 22 Mar 2018 18:40:10 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::9d46:b69d:ec4:831e%6]) with mapi id 15.20.0588.013; Thu, 22 Mar 2018 18:40:10 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: Draft minutes of IETF 101 WG meeting
Thread-Index: AQHTwg008e3M2yT2r0GuvKsGe7jW8g==
Date: Thu, 22 Mar 2018 18:40:09 +0000
Message-ID: <1541B199-D8CD-412F-89E7-A96BB2D8B680@jisc.ac.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:67c:1232:144:1011:5110:cdc1:1efe]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1566; 7:KP3H48KpAAqxzU6PgnJloInrl2JY/UgxpW1+dhHox5JJP0U/E0MXadN9DakctMpo4AAP2S3qKGV+HUhs0ylKuuDMcE8RKYvj1/+Le78Mqln0W5830fEecpGiz7OqWTu+Ez0G6QPZInWP1J/2iAsJBzuj/hIR6CweISmhP1zRJib04nIZcavZN9AHhuQwSFIpCE6kA9YEDHRMqtDMnnWm48h7GRsGjjQh73LoW3fDH42GTh5hUomIG5/NvVSVTqn6; 20:9XJWwWdI+ImtQI6VVhmSMK8AJxftPtFJfBRMXlZEll0QBdinS8BOt6iYsm8Cgo6LCQW1sJfO/r8H7clUvV/tX/+n2Wgu9BPa1gCWkHrXhV9rVobooHxC0hrsjDSHRBQZuSn6PYSBysRq456q4gPxd1RGMQrOoUQQWzdTdzsbRik=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 293cc36d-47fe-46b5-63c7-08d59024574d
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1566; 
x-ms-traffictypediagnostic: VI1PR07MB1566:
x-microsoft-antispam-prvs: <VI1PR07MB1566A7BA9F65D27BD61CBE17D6A90@VI1PR07MB1566.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506)(120809045254105)(192374486261705)(131327999870524); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231221)(944501327)(52105095)(6041310)(20161123558120)(20161123564045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR07MB1566; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1566; 
x-forefront-prvs: 0619D53754
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(376002)(346002)(396003)(366004)(39850400004)(199004)(189003)(57704003)(86362001)(25786009)(7736002)(50226002)(305945005)(97736004)(83716003)(5640700003)(2906002)(6486002)(81156014)(14454004)(3280700002)(99286004)(106356001)(8936002)(53936002)(2900100001)(5660300001)(2501003)(5890100001)(8676002)(478600001)(5250100002)(6916009)(59450400001)(6506007)(82746002)(74482002)(57306001)(105586002)(1730700003)(68736007)(786003)(46003)(6436002)(2351001)(6116002)(33656002)(6512007)(6306002)(966005)(316002)(36756003)(3660700001)(81166006)(102836004)(186003)(72206003); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1566; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
x-microsoft-antispam-message-info: AvJEZ6Xam7Semw0ll962upPgjQ3IHvbumU+VUJiok/f0Nz8SxPmgCKJ5J1XQ0ccfj+3HRUgiyUKqfY/CxBBPF5FQBwALV0d3e3/cxyqseT2fZ+Nglbf4lGtr6fKzzWiLaRHlKV6JT6uwWkoyZykB5PRbqU3CO4o/2Hs5euFBHaOxSVrBR2D47cFBlgxU9saAreGFNI+gxuvJx8qL4IOzUDPUrpOyjta7dVOwhLwC0IoCr1Ii3cAGSHLAxuVTx48VK8CUAmP7OhBSgZ1vmkFAcvPQs87Kr7pA0pyQLBtLKGZlYw1Ce97mJ2N2W33JuzB4+AtBG36xxj9DUuu0/61lug==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <FDA0D22554E03B4E94E49D0289E11922@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 293cc36d-47fe-46b5-63c7-08d59024574d
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Mar 2018 18:40:09.9611 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1566
X-MC-Unique: hQ0Rj4yoN1qpdoj89u-JWg-1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/tTUx7x2gtdLcHk81hPrTg8G7-lU>
Subject: [dnssd] Draft minutes of IETF 101 WG meeting
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 18:40:26 -0000

SGksDQoNClBsZWFzZSByZXZpZXcgdGhlIGRyYWZ0IG1pbnV0ZXMgYnkgVGh1cnNkYXkgMjl0aCBN
YXJjaC4NCg0KU2VlOiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvMTAxL21h
dGVyaWFscy9taW51dGVzLTEwMS1kbnNzZC0wMA0KDQpBbHNvIGF0dGFjaGVkIGJlbG93Lg0KDQpN
YW55IHRoYW5rcyBhZ2FpbiB0byBCYXJiYXJhIGZvciB0YWtpbmcgbWludXRlcywgYW5kIE1pa2Fl
bCBmb3IgSmFiYmVyIHNjcmliaW5nLg0KDQpUaW0gDQoNCg0KDQpETlNTRCBXRyBNaW51dGVzDQoN
CklFVEYxMDEsIExvbmRvbg0KVGh1cnNkYXksIDIybmQgTWFyY2ggMjAxOA0KQnVja2luZ2hhbSBS
b29tIDA5OjMwIC0gMTI6MDAgbG9jYWwgdGltZQ0KDQpDaGFpcnM6IERhdmlkIFNjaGluYXppLCBU
aW0gQ2hvd24NCk5vdGVzOiBCYXJiYXJhIFN0YXJrDQpKYWJiZXI6IE1pa2FlbCBBYnJhaGFtc3Nv
bg0KDQotLS0tLS0tDQpDaGFpcnMgSW50cm9kdWN0aW9uDQpUaW0gQ2hvd24gcHJlc2VudGVkIHRo
ZSBDaGFpcnMnIHNsaWRlcw0KaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzEw
MS9tYXRlcmlhbHMvc2xpZGVzLTEwMS1kbnNzZC1jaGFpcnMtc2xpZGVzLTA0DQpUaGVyZSB3YXMg
bm8gYmFzaGluZyBvZiB0aGUgYWdlbmRhLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpTdGF0
dXMgUmVwb3J0cw0KU3R1YXJ0IENoZXNoaXJlIHByZXNlbnRlZCBETlNTRCBEb2N1bWVudCBTdGF0
dXMgVXBkYXRlDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvMTAxL21hdGVy
aWFscy9zbGlkZXMtMTAxLWRuc3NkLWRucy1zdGF0ZWZ1bC1vcGVyYXRpb25zLXB1c2gtYW5kLWRp
c2NvdmVyeS1icm9rZXItdXBkYXRlLTAwDQoNClRpbTogYW55IHF1ZXN0aW9ucyBvbiBETlMgcHVz
aD8NClRodW1icyB1cCBmcm9tIEFuZHJldyBTdWxsaXZhbg0KVGltOiBBbnkgY29tbWVudHM/IDxU
aGVyZSB3ZXJlIG5vIGNvbW1lbnRzLj4NClRpbTogSXMgdGhlcmUgYW55IHJlYXNvbiB0byBob2xk
IHRoZSBkb2N1bWVudHMgdXA/IERvIHdlIG5lZWQgbW9yZSBpbXBsZW1lbnRhdGlvbiBleHBlcmll
bmNlPw0KU3R1YXJ0OiBUZWQgYW5kIEkgYXJlIHdvcmtpbmcgb24gaW1wbGVtZW50YXRpb24uIFdl
IGV4cGVjdCB0byBoYXZlIGNvZGUgcnVubmluZyBhdCB0aGUgTW9udHJlYWwgaGFja2F0aG9uLg0K
VGltOiBBbnlvbmUgZWxzZSBpbXBsZW1lbnRpbmc/IDxzb21lIGhhbmRzIHdlcmUgcmFpc2VkPg0K
U3R1YXJ0OiBUaGVyZSBpcyBhIHRlYW0gYXQgQ2lzY28gdGhhdCBoYXZlIGFuIGltcGxlbWVudGF0
aW9uLiBBbmQgTWFyY3VzIFN0ZWluYmVyZyBoYXMgYmVlbiB3b3JraW5nIG9uIGFuIGltcGxlbWVu
dGF0aW9uLg0KVGltOiBPSywgc28gaW1wbGVtZW50YXRpb25zIGNhbiBwcm9jZWVkIGluIHBhcmFs
bGVsIHdpdGggSUVURiBwcm9jZXNzDQoNClRpbTogSG93IG1hbnkgYXJlIGluIGZhdm9yIG9mIGFk
b3B0aW5nIHRoZSByb2FkbWFwIGRvY3VtZW50IGFzIGEgV0cgdGV4dD8gPGFsbCBodW1zIHdlcmUg
aW4gZmF2b3I+DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClVwZGF0ZSB0byBNdWx0aWNhc3Qg
RE5TIERpc2NvdmVyeSBSZWxheSwgDQphbmQgU2ltcGxlIEhvbWVuZXQgTmFtaW5nIGFuZCBTRCBB
cmNoaXRlY3R1cmUNCg0KVGVkIExlbW9uIHByZXNlbnRlZCBETlMtU0QgRGlzY292ZXJ5IFJlbGF5
DQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL21lZXRpbmcvMTAxL21hdGVyaWFscy9zbGlk
ZXMtMTAxLWRuc3NkLWRucy1zZC1kaXNjb3ZlcnktcmVsYXktMDENCg0KVGltOiBIYXMgYW55b25l
IHJlYWQgaXQ/IDxub3QgbWFueSBoYW5kcz4NClRpbTogV2lsbCBhbnlvbmUgcmVhZCBpdD8gPHNv
bWUgaGFuZHMgd2VyZSByYWlzZWQ+DQpTdHVhcnQ6IEkgdGhpbmsgaXQncyBhIGZhaXJseSBuZXcg
ZG9jdW1lbnQgc28gcGVvcGxlIGhhdmVuJ3QgaGFkIG11Y2ggb2YgYSBjaGFuY2UgdG8gcmVhZCBp
dCB5ZXQuIEJ1dCBJIHRoaW5rIGl0J3MgZ29vZC4gSSBhcHByZWNpYXRlIGVmZm9ydHMgZnJvbSBw
ZW9wbGUgaW4gQ2lzY28gdG8gZG8gaW1wbGVtZW50YXRpb25zLiBJIHRoaW5rIGl0IG1ha2VzIGEg
bG90IG9mIHNlbnNlIGFuZCB0aGF0IG1heSBiZSB3aHkgd2UgaGF2ZW4ndCByZWNlaXZlZCBtdWNo
IGZlZWRiYWNrLiBJdCBmaXRzIG5hdHVyYWxseS4NCk1pa2FlbDogRG8geW91IGtub3cgd2hhdCB2
ZXJzaW9uIG9mIE9wZW5XUlQgeW91J2xsIGJlIHdvcmtpbmcgaW4/DQpUZWQ6IEl0J3MgZWFzeSB0
byBpbnRlZ3JhdGUgaW50byBhbnl0aGluZy4NCk1pa2FlbDogR29vZCB0byBtYWtlIGl0IHN0YWJs
ZSBzZXBhcmF0ZSBmcm9tIE9wZW5XUlQuDQpUZWQ6IEdvb2QgZmVlZGJhY2suDQoNClRpbTogQWxs
IGluIGZhY29yIG9mIGFkb3B0aW5nIGFzIFdHIGl0ZW0/IDxhbGwgaHVtcyB3ZXJlIGluIGZhdm9y
LCBub25lIGFnYWluc3Q+DQoNClNpbXBsZSBIb21lbmV0IE5hbWluZyBBcmNoaXRlY3R1cmUNClRl
ZCBMZW1vbiBwcmVzZW50ZWQgU2ltcGxlIEhvbWVuZXQgTmFtaW5nIEFyY2hpdGVjdHVyZQ0KaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzEwMS9tYXRlcmlhbHMvc2xpZGVzLTEw
MS1kbnNzZC1zaW1wbGUtaG9tZW5ldC1uYW1pbmctYXJjaGl0ZWN0dXJlLTAxDQoNClRpbTogTm90
ZSB0aGlzIGlzIGFscmVhZHkgYSBob21lbmV0IFdHIGl0ZW0uIEdvaW5nIGJhY2sgdG8gc2xpZGUg
Ik91ciBhc2sgZm9yIEROU1NEIFdHIi4gQW55IHRob3VnaHRzIG9uIHRoZXNlPyBVbmljYXN0L211
bHRpY2FzdCBwb3NpdGlvbj8NClN0dWFydDogSSB3YW50ZWQgdG8gZXhwYW5kIG9uIHNvbWV0aGlu
ZyBUZWQgbWVudGlvbmVkLiBIb21lIGF1dG9tYXRpb24sIElvVCBhcmUgaW5jcmVhc2luZ2x5IHBv
cHVsYXIgaW4gaG9tZXMuIFdoZW4geW91IGhhdmUgYSBtZXNoIGl0IGdldHMgcmVhbGx5IGhhcmQg
dG8gbXVsdGljYXN0LiBQZXJzb25hbGx5LCB0aGlzIGlzIGFuIGFyZWEgSSB0aGluayBpcyBpbXBv
cnRhbnQgYW5kIHdpbGwgYmUgd29ya2luZyBvbi4gV2Ugd2lsbCBuZWVkIHRoaXMuDQpNaWthZWw6
IFllcyB3ZSBzaG91bGQgbW92ZSBhd2F5IGZyb20gbXVsdGljYXN0LiBUaGVyZSBhcmUgbXVsdGlj
YXN0IGlzc3VlcyB3aXRoIHJhZGlvcy4NClN0dWFydDogWW91IG1ha2UgYSBnb29kIHBvaW50LiBX
ZSB3aWxsIGhhdmUgY2FzZXMgd2hlcmUgdGhlcmUgaXMgb2xkIGFuZCBuZXcsIGFuZCBtZXNoIHdp
dGggYWxsIG5ldy4gV2UgbmVlZCB0byBoYXZlIGEgc29sdXRpb24gcmVhZHkuDQoNClRpbTogTWF5
YmUgaXQncyB0aW1lIHRvIHJlbmV3IG91ciBjaGFydGVyIGFuZCBhbmQgc29tZSBpdGVtcyBvbiB0
aGlzPw0KVGVycnkgTWFuZGVyc29uOiA8YXMgQUQ+IEknbSB3aWxsaW5nIHRvIGxpc3RlbiB0byB0
aGUgV0cgbWVtYmVycyBhbmQgYWRkIHRoaXMuDQpNaWthZWw6IFdlIG5lZWQgdG8gbWFrZSBzdXJl
IHdlJ3JlIG5vdCByZWR1Y2luZyBvciBpbXBhY3RpbmcgdGhlIGV4cGVyaWVuY2Ugb3RoZXJzIGFy
ZSB0cnlpbmcgdG8gY3JlYXRlLg0KVGltOiBUaGlzIGNhbiBjb21wbGVtZW50IHdvcmsgaW4gQ29S
RSwgZXRjLg0KU3R1YXJ0OiA8dG8gVGltPiBQbGVhc2Ugc2VuZCBlbWFpbCB0byBsaXN0IHdpdGgg
bGluayB0byBDaGFybGllIFBlcmtpbnMgd29yay4NCg0KVGltOiBXZSB3aWxsIHRha2Ugd29yayBv
biBjaGFydGVyIHRvIHRoZSBsaXN0LiBBcyBmb3IgdGhpcyBkcmFmdCwgaG93IG1hbnkgaGF2ZSBy
ZWFkPyA8bm90IG1hbnkgaGFuZHM+IEl0IG1heSBiZSBlYXJseSBmb3IgYWRvcHRpb24/IEJ1dCBp
dCB3b3VsZCBiZSBnb29kIGZvciBwZW9wbGUgdG8gcmV2aWV3Pw0KDQpTdHVhcnQ6IEkgYWdyZWUg
aXQncyBub3QgdGltZSBmb3IgYWRvcHRpb24gYnV0IGRpc2N1c3Npb24gb24gY2hhcnRlciBpcyBn
b29kLg0KVGVkOiBJIGRpZG4ndCB3YW50IHRvIGdldCB0b28gZGVlcCBpbnRvIGFkb3B0aW9uIGRp
c2N1c3Npb24uIEROUy1TRCBoYXMgZG9uZSBhIGdvb2Qgam9iIGF0IGFkZHJlc3NpbmcgbWFjaGlu
ZXJ5IG9mIGhvdyB0byBnZXQgaW50ZXJjb25uZWN0ZWQgZGV2aWNlcyB0byBqdXN0IHdvcmsuIEVz
cGVjaWFsbHkgZm9yIEVEVUNBVVNFIGNhc2UuDQpUaW06IEl0IHdvdWxkIGJlIGdvb2QgdG8gaGF2
ZSBlcXVpdmFsZW50IHZpZXdwb2ludCB0byB3aGF0IHlvdSBhcmUgZG9pbmcgaW4gaG9tZW5ldCBm
b3IgZW50ZXJwcmlzZS4NCg0KVGltOiBBZ3JlZW1lbnQgd2FzIHRvIHdvcmsgb24gdXBkYXRlIHRv
IGNoYXJ0ZXIuIEFmdGVyIHRoYXQgd2Ugd2lsbCBzZWUgd2hpY2ggZG9jdW1lbnQgd2UgbmVlZCB0
byBhZG9wdC4NCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkNvUkUgUmVzb3VyY2UgRGlzY292ZXJ5
OiBETlMtU0QgbWFwcGluZw0KS2VycnkgTHlubiByZW1vdGVseSBwcmVzZW50ZWQgQ29SRSBSRCBh
bmQgRE5TLVNEIG1hcHBpbmcNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy8x
MDEvbWF0ZXJpYWxzL3NsaWRlcy0xMDEtZG5zc2QtY29yZS1yZC1hbmQtZG5zLXNkLW1hcHBpbmct
MDENCg0KS2Vycnk6IDxzcGVha2luZyB0byB0aGUgdGl0bGUgc2xpZGU+IFRoaXMgaXMgdG8gaGFy
bW9uaXplIHdvcmsgYmVpbmcgZG9uZSBpbiBDb1JFIHdpdGggRE5TLVNELg0KDQpEYXZlIFRoYWxl
cjogSG93IGRvIHlvdSBkZXJpdmUgc3RydWN0dXJlIGZyb20gaW5mbyBpbiBPSUM/DQpLZXJyeTog
SSBkb24ndCBrbm93LiBXZSdyZSBqdXN0IHN0YXJ0aW5nLiBJZiB3ZSBjb3VsZCBoYXZlIGZlZGVy
YXRlZCBuYW1lIHNjaGVtZSBpdCBjb3VsZCBoZWxwIHVzIGF2b2lkIGhhdmluZyB0byBkb2N1bWVu
dCBzZXBhcmF0ZWx5Lg0KRGF2ZTogSSBkb24ndCBrbm93IHdoeSB5b3Ugd291bGQgbmVlZCB0aGF0
Lg0KVGVkOiBIYXZlIHlvdSBjb25zaWRlcmVkIGFkdmVydGlzaW5nIENvUkUgYXMgYSBETlMtU0Qg
c2VydmljZT8gLS0gaWYgSSB3ZXJlIHRoaW5raW5nICBhYm91dCBob3cgdG8gZ2V0IENvUkUgYW5k
IEROUy1TRCB0b2dldGhlciwgSSB3b3VsZCBkbyBpdCBhbm90aGVyIHdheS4NCktlcnJ5OiBJdCdz
IGNsZWFyIGl0IHdvdWxkIGJlIGdvb2QgdG8gaGF2ZSBtb3JlIGludGVyYWN0aW9uLiBXZSB3aWxs
IGhhdmUgaW50ZXJvcC4NCkNocmlzdGlhbiBBbXPDvHNzOiBJbnRlcm9wIHBsYW5zIGFyZSBub3Qg
eWV0IHNldCBpbiBzdG9uZSwgYnV0IGl0IHdpbGwgYmUgdmlydHVhbCwgaW4gQXByaWwNCktlcnJ5
OiBKdXN0IHRvIGFkdmVydGlzZSBzb21ldGhpbmcgYXMgYmVpbmcgQ29SRSBvciBDb0FQIGNhcGFi
bGUgbWF5IG5vdCBoZWxwLg0KU3R1YXJ0OiBZZXMgd2UgY291bGQgaGVscCB3aXRoIGNvbW11bmlj
YXRpb24uIEtleSBjaGFsbGVuZ2UgaXMgdGhlIG1hcHBpbmcgb2Ygc2VydmljZXMsIG5lZWQgY29t
bW9uIHZvY2FidWxhcnkgdG8gZGVzY3JpYmUgc2VydmljZXMuDQpDaHJpc3RpYW4gQTogb25lIHVz
ZSBjYXNlIHdlJ3JlIGNvbnNpZGVyaW5nIGlzIGEgZ3JvdXAgb2YgcmVzb3VyY2UgdHlwZXMgdGhh
dCBhcmUgb2ZmZXJlZCBvdmVyIEhUVFAgLSBhZHZlcnRpc2UgdGhlbSBvdmVyIEROU1NEIHRvIGFs
bG93IG5vbi1jb3JlIGRldmljZXMgdG8gaW50ZXJvcGVyYXRlDQpCYXJiYXJhOiBXZSBoYXZlIHNv
bWV0aGluZyBhdCBCcm9hZGJhbmQgZm9ydW0gdGhhdCB1c2VzIENvQVAgYnV0IGRvZXNuJ3QgZG8g
RE5TLVNEIHRoaXMgd2F5LiBJdCBkb2VzIGhhdmUgc3BlY2lmaWMgRE5TLVNEIG5hbWluZyBzY2hl
bWUuIEkgd2lsbCBzZW5kIHlvdSBsaW5rIHRvIGluZm8uDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpETlMtU0QgUHJpdmFjeSByZXF1aXJlbWVudHMgYW5kIHNjb3BpbmcgZGlzY3Vzc2lvbg0KQ2hy
aXN0aWFuIEh1aXRlbWEgcHJlc2VudGVkIEROUy1TRCBQcml2YWN5IFNjZW5hcmlvcw0KaHR0cHM6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9tZWV0aW5nLzEwMS9tYXRlcmlhbHMvc2xpZGVzLTEwMS1k
bnNzZC1kbnMtc2QtcHJpdmFjeS1zY2VuYXJpb3MtMDANCg0KU3R1YXJ0OiBZb3UgY2FuJ3QgYXNz
dW1lIGRldmljZXMgaW4gU2NlbmFyaW8gMiB3ZXJlIHNldCB1cCBieSBzYW1lIHBlb3BsZS4NCkNo
cmlzdGlhbiBIOiBZb3UgYXJlIHJpZ2h0LiBTYW1lIHJlcXVpcmVtZW50IGJ1dCBub3Qgc2FtZSBz
Y2VuYXJpby4NCg0KQ2hyaXN0aWFuIEh1aXRlbWEgcHJlc2VudGVkIEROUy1TRCBQcml2YWN5IFNj
YWxpbmcNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy8xMDEvbWF0ZXJpYWxz
L3NsaWRlcy0xMDEtZG5zc2QtZG5zLXNkLXByaXZhY3ktc2NhbGluZy0wMA0KDQpEYXZlIFRoYWxl
cjogSXQgd291bGQgYmUgdXNlZnVsIHRvIHN0YXRlIGNvbXBhcmF0aXZlIENQVSByZXF1aXJlbWVu
dHMgLyBzcGVlZHMgb2Ygc29sdXRpb25zLg0KQ2hyaXN0aWFuIEg6IFllcw0KDQpEYXZpZCBTOiBU
aGFuayB5b3UuIEknZCBsaWtlIHRvIG5vdyBzZWUgaWYgd2UgY2FuIGZpZ3VyZSBvdXQgcmVxdWly
ZW1lbnRzLiBXaGF0IGRvIHdlIHdhbnQgdG8gc29sdmUuIFdoYXQgZG9uJ3Qgd2Ugd2FudCB0byBz
b2x2ZS4gVGhlcmUgYXJlIG1hbnkgY29tcHJvbWlzZXMgYW5kIG9wdGlvbnMgaGVyZS4NCkNocmlz
IFdvb2Q6IFRoZXJlIGFyZSBuZXdlciBmbGF2b3JzIG9mIGNyeXB0b2dyYXBoeSB0aGF0IGNvdWxk
IGJlIGFwcGxpY2FibGUgaGVyZS4gTWF5YmUgd2Ugc2hvdWxkIG1lbnRpb24gdGhhdC4NCkRhdmlk
IFM6IFRoYXQncyBzb21ldGhpbmcgd2Ugc2hvdWxkIGNvbnNpZGVyLiBQbGVhc2UgPHRvIENocmlz
PiBzZW5kIGluZm8gdG8gbGlzdC4NClN0dWFydDogV2UgZG8gbm90IHdpc2ggdG8gcnVsZSBhbnl0
aGluZyBvdXQganVzdCB5ZXQuIEkgdGhpbmsgdGhpcyBpcyBhIHJlbGF0aXZlbHkgbmV3IGFyZWEu
DQpLZXJyeTogSSB0cmllZCB0byB1bmRlcnN0YW5kIHdoYXQgbWV0YWRhdGEgaXMgZXhwb3NlZCBi
eSByb2FtaW5nIGNsaWVudC4gWW91IGNhbid0IGNsb2FrIHRoZSBJUCBhZGRyZXNzLiBXaWxsIHRo
aXMgYmUgYWJvdXQgY2xvYWtpbmcgd2hhdCB0aGUgY2xpZW50IHdhbnRzIGFuZCB3aGF0IGl0IGdl
dHMgYmFjaz8gQW5kIGRvIHdlIHdhbnQgdG8gYWRkcmVzcyB0aGF0IHRoZSBjbGllbnQgc2hvdWxk
IG9ubHkgYmUgZG9pbmcgd2hhdCB0aGUgdXNlciB3YW50cy4NCkNocmlzdGlhbiBIOiA8ZGVzY3Jp
YmVkIHdoYXQgaGVhZGVyIGVsZW1lbnRzIHNob3VsZCBiZSBpbiB0aGUgY2xlYXI+IFRyeWluZyB0
byBwcm90ZWN0IG1ldGFkYXRhIGluIEROUy1TRCBwcm90b2NvbC4NCkNocmlzIFdvb2Q6IFRoZXJl
IHdpbGwgYmUgbmV3IHRoaW5ncyB0aGF0IGhhdmUgbm90IGdvbmUgdGhyb3VnaCB0aGlzIHByb2Nl
c3MuDQpUaW06IFdlIGhhdmUgaGFkIGEgc2VjdXJpdHkgcmV2aWV3IG9mIENocmlzdGlhbidzIGlu
aXRpYWwgcGFpcmluZyBkb2MsIGJ1dCBub3QgYSBicm9hZGVyIHZpZXcgb24gdGhlIHRvcGljIGFz
IGEgd2hvbGUgZnJvbSB0aGVtDQpDaHJpc3RpYW46IFdlIGFyZSBwcm90ZWN0aW5nIHRoZSBtZXRh
ZGF0YQ0KRGF2aWQ6IFllcyANCkRhdmUgVGhhbGVyOiBEaXNjb3ZlcnkgaXMgb25seSBoYWxmIHRo
ZSBwcm9ibGVtLiBJIGNhbiBkaXNjb3ZlciB5b3UgYW5kIG9wZW4gYSBjaGFubmVsLCBidXQgYXJl
IGJvdGggc2lkZXMgcHJpdmF0ZT8gIFRoaXMgdG9waWMsIGFzIHNlY3JldCBoYW5kc2hha2luZyBw
cm90b2NvbCByZXNlYXJjaCwgYWthIGFmZmlsaWF0ZSBoaWRpbmcgYXV0aGVudGljYXRpb24sIGhh
cyBiZWVuIGFyb3VuZCBmb3IgeWVhcnMsIGJ1dCBubyBzdGFuZGFyZGlzZWQgcHJvdG9jb2xzLiBO
ZWVkIHRvIG1ha2Ugc3VyZSB3ZSBwcmVzZXJ2ZSB0aGUgaWRlbnRpdHkgb2YgYm90aCBzaWRlcy4g
SSBoYXZlIGluZm8gSSBjYW4gc2VuZCBwb2ludGVycyB0by4NCkRhdmlkIFM6IFllcyBwbGVhc2Ug
c2VuZC4NClRpbTogTmVlZCB0byBhbnN3ZXIgc29tZSBvZiB0aGUgcXVlc3Rpb25zIGluIENocmlz
dGlhbidzIHNsaWRlIGRlY2suDQpDaHJpc3RpYW4gSDogVGhlcmUgaXMgYSBkZWVwZXIgdGhvdWdo
dCB0aGF0IEkgaGF2ZSBub3QgYnJvdWdodCBoZXJlLg0KRGF2aWQgUzogRG8gd2UgaGF2ZSBhIHJl
cXVpcmVtZW50IHRoYXQgcHJpdmF0ZSBkaXNjb3ZlcnkgY2FuIGxlYWQgdG8gYm9vdHN0cmFwPw0K
Q2hyaXN0aWFuIEg6IFdlIGhhdmUgYWRkZWQgc29sdXRpb24gdG8gcHJvdGVjdCBoYW5kc2hha2Uu
DQpEYXZpZCBTOiBPbiBmaXJzdCBvbmUgPGl0ZW0gaW4gZGFzaCBsaXN0IG9uIEROUy1TRCBQcml2
YWN5IERpc2N1c3Npb24gc2xpZGU+IGRvZXMgYW55b25lIGhhdmUgYW4gb3BpbmlvbiBvbiB0aGUg
dG9waWM/DQpTdHVhcnQ6IE9uIGZpcnN0IG9uZSwgbXkgYW5zd2VyIGlzIHByb2JhYmx5IHllcy4g
T24gMm5kIHRoZSBhbnN3ZXIgbWF5IGJlIG5vLg0KVG9tIFB1c2F0ZXJpOiBDaHJpc3RpYW4gc2Vl
bXMgdG8gYmUgd29ya2luZyBpbmRlcGVuZGVudGx5IG9mIHdoYXQgeW91IGRlc2NyaWJlLiBJdCBt
aWdodCBiZSBva2F5IHRvIGhhdmUgYSBzdWJzZXQgb2YgdGhlIHByaXZhY3kgcnVsZXMuDQpEYXZp
ZCBTOiBZZXMsIHRoYXQgbWlnaHQgYmUgcG9zc2libGUuDQpNaWthZWw6IFdoYXQgdHJ1c3RzIHdo
YXQ/DQpEYXZpZCBTOiBJZiBJIHRydXN0IHlvdSBJIGFsbG93IHlvdSB0byBkaXNjb3ZlciBtZS4g
QnV0IHdobyBhcmUgeW91PyBQZXJzb24/IERldmljZT8NCk1pa2FlbDogWWVzLg0KRGF2ZSBSb2Jp
bjogV2hhdCdzIHRoZSBwb2ludCBpbiBoYXZpbmcgdGhpcyBzZWNyZXQgYXBwbGljYXRpb24gdGhh
dCBpcyBjbGVhcmx5IGlkZW50aWZpZWQgYnkgdGhlIGlkZW50aXR5IG9mIHRoZSBkZXZpY2U/IFBy
b2JsZW0gaXMgd2l0aCBkZXZpY2UgdGhhdCBoYXMgbXVsdGlwbGUgaW5kZXBlbmRlbnQgYXBwbGlj
YXRpb25zLg0KRGF2aWQgUzogSXQgZGVwZW5kcyBvbiB3aGF0IHlvdSBtZWFuIGJ5IGhpZGluZy4g
PHByb3ZpZGVkIGFuIGV4YW1wbGUgb2YgcHJpbnRlciB0YWxraW5nIHRvIG1lZGljYWwgZGV2aWNl
Pg0KRGF2ZSBSOiBJIGNhbiB0ZWxsIGJ5IGJlaGF2aW9yIHdobyB5b3UgYXJlIHRhbGtpbmcgdG8u
DQpTdHVhcnQ6IEltYWdpbmUgZXZlcnkgYXBwbGljYXRpb24gaGFzIGl0cyBvd24gSVAgYWRkcmVz
cy4gV2luZG93cyBoYXMgZ29vZCBNQUMgYWRkcmVzcyByYW5kb21pemF0aW9uLiBXZSBuZWVkIGFk
ZGl0aW9uYWwgcnVsZSBjaGFuZ2VzIGJ5IHJlZ3VsYXRvcnMgb24gdXNpbmcgdGhlc2UgdG9vbHMu
IA0KQ2hyaXN0aWFuOiBUaGlzIHdpbGwgZXZvbHZlIChJUCBhbmQgTUFDICdyYW5kb21pc2F0aW9u
JykNCkRhbmllbCBLYWlzZXIgPHJlbGF5ZWQgZnJvbSBqYWJiZXI+OiBTaG91bGQgYSBtZWRpY2Fs
IGRldmljZSByZWFsbHkgam9pbiBhIHB1YmxpYyBXaUZpIG5ldHdvcmsgZm9yIGNvbW11bmljYXRp
bmcgd2l0aCwgZS5nLiwgYSBwaG9uZT8NCk1pa2FlbDogV2hlbiBJIGNvbWUgaGVyZSBJIHNvbWV0
aW1lcyBzZWUgbXkgcHJpbnRlciBhdCBob21lLiBXaHkgZG9lcyBpdCBkbyB0aGF0PyBJcyB0aGlz
IHByaXZhY3kgb3IgcG9saWN5PyBJdCBuZWVkcyB0byBiZSBncmFudWxhci4gSSB3YW50IHRvIHNo
YXJlIHNvbWUgdGhpbmdzIGFuZCBub3Qgb3RoZXJzLg0KRGF2aWQgUzogV2UgbmVlZCB0byBuYWls
IGRvd24gc29tZSBvZiB0aGlzIHNvIHdlIGNhbiBkZWZpbmUgc29sdXRpb24uDQoNClRpbTogVGhl
cmUgYXJlIHZhcmlvdXMgZHJhZnRzLiBIb3cgc2hvdWxkIHdlIGNhcHR1cmUgdGhlc2UgaXNzdWVz
IGdvaW5nIGZvcndhcmQ/IFB1dCBpbnRvIG9uZSBkcmFmdCBkcmF3aW5nIGZyb20gdGhlc2UgMyBz
b3VyY2VzPyBXaG8gd291bGQgYmUgd2lsbGluZyB0byBoZWxwIHdyaXRlPyA8Q2hyaXMgV29vZCwg
VGVkIExlbW9uIGFuZCBTdHVhcnQgQ2hlc2hpcmUgcmFpc2VkIGhhbmRzPg0KDQpOb3JtZW4gS293
YWxld3NraSBkZXNjcmliZWQgJ3BlcnNvbmFsIGNsb3VkJyBkZXZpY2UgcHJpdmFjeSBiYXNlZCBv
biBzb21lIEVVIHByb2plY3Qgd29yaw0KQ2hyaXN0aWFuIEg6IEkgYW0gY29uY2VybmVkIHdpdGgg
dGhpcyBzY2VuYXJpby4NCk5vcm1lbjogT3RoZXIgY29uY2VwdHMgc2hvdWxkIGJlIGxvb2tlZCBh
dC4NCg0KRGF2aWQgUzogQXJlIHRoZXJlIHByZWZlcmVuY2VzIGFzIHRvIHN0YXJ0IGZyb20gb25l
IG9mIHRoZSBleGlzdGluZyBkb2NzIG9yIHN0YXJ0IG5ldz8gVEJELg0KDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tDQpXcmFwdXANCg0KVGltOiBBY3Rpb25zOg0KMS4gQWRvcHRlZCByb2FkbWFwIC0t
IGNoZWNrIHdpdGggbGlzdC4gDQoyLiBBZG9wdGVkIGRpc2NvdmVyeSByZWxheSAtLSBjaGVjayB3
aXRoIGxpc3Q7IEJhcmJhcmEgdG8gcmV2aWV3DQozLiBDb250aW51ZSB3b3JrIG9uIHNsZWVwIHBy
b3h5IGFuZCBkaXNjb3ZlcnkgYnJva2VyDQo0LiBXRyB0byByZXZpZXcgY2hhcnRlciB3aXRoIGEg
dmlldyB0byB1cGRhdGUgLS0gZGlzY3VzcyBvbiBsaXN0IHRvIHNlZSB3aGF0IGdvZXMgaW4gYW5k
IG91dCBvZiBjaGFydGVyOyBlLmcuLCBwcml2YWN5LCB1bmljYXN0L211bHRpY2FzdCwgQ29BUCBp
bnRlcm9wDQo1LiBDb250aW51ZSB0byBoYXJtb25pemUgd2l0aCBvdGhlciBncm91cHMgb24gQ29S
RSB3b3JrOyBzZWVrIHRvIGhhdmUgV0cgcHJlc2VuY2UgYXQgQXByaWwgQ29SRSBSRCBpbnRlcm9w
DQo2LiBOZWVkIHZvbHVudGVlcnMgdG8gcHJvZHVjZSBndWlkYW5jZSBvbiBuYW1pbmcgYXJjaGl0
ZWN0dXJlIGZvciBlbnRlcnByaXNlIGxpa2Ugd29yayBkb25lIGluIGhvbWVuZXQuDQo3LiBOZWVk
IHRvIHB1bGwgdG9nZXRoZXIgYSBuZXcgcHJpdmFjeSByZXF1aXJlbWVudHMgZHJhZnQNCg0KDQo=


From nobody Mon Mar 26 04:24:08 2018
Return-Path: <tim.chown@jisc.ac.uk>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C7B1127137 for <dnssd@ietfa.amsl.com>; Mon, 26 Mar 2018 04:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 dHJpIMCeKihA for <dnssd@ietfa.amsl.com>; Mon, 26 Mar 2018 04:24:04 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [146.101.78.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C000C12711E for <dnssd@ietf.org>; Mon, 26 Mar 2018 04:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1522063441; h=from:subject:date:message-id:to:cc:mime-version:content-type:content-transfer-encoding:in-reply-to:references; bh=9AzKwfUhPYHsWy0VAWKrLbVRdTr1Pdzv0Nhc+rTbBZA=; b=g1oykrbwk5V1Kip0sPeeA1PiToRDLasv4aiL1JRCk/suXfaGcBIx2iNpC+AfGp4QH5Y5RUO7Ls41GiyY0KRtTrd9nlBu9s5dLoKxejOMweYRKfeBiS6yf30G1GA3eu9WijxxUYRDu25KDHMpbEXtt1WusCtITQCKoEjsSDsU35c=
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01lp0175.outbound.protection.outlook.com [213.199.154.175]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-137-xbegttNFPkq1n628mfo-yw-1; Mon, 26 Mar 2018 12:23:59 +0100
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com (10.161.108.21) by VI1PR07MB1293.eurprd07.prod.outlook.com (10.164.92.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.631.5; Mon, 26 Mar 2018 11:23:55 +0000
Received: from VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::4011:38b1:3ecf:4201]) by VI1PR07MB0879.eurprd07.prod.outlook.com ([fe80::4011:38b1:3ecf:4201%4]) with mapi id 15.20.0631.009; Mon, 26 Mar 2018 11:23:55 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Mikael Abrahamsson <swmike@swm.pp.se>
CC: "dnssd@ietf.org" <dnssd@ietf.org>
Thread-Topic: [dnssd] multicast wifi draft mentioned in the session today
Thread-Index: AQHTwcdjJZ+BAAPcFkOS643diSUJ0KPiZkkA
Date: Mon, 26 Mar 2018 11:23:55 +0000
Message-ID: <CBE8EB5F-7A2A-4BCE-8162-BE6DE2C1AEEE@jisc.ac.uk>
References: <alpine.DEB.2.20.1803221117340.20609@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.20.1803221117340.20609@uplift.swm.pp.se>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.5.20)
x-originating-ip: [2001:a88:d510:1101:e818:5578:8bd0:47af]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; VI1PR07MB1293; 7:3Il7ac+iBx5jCMv1TPqU1p1X3prA4ezMKNUCE3T/KDa0zOrl4nIDNNHDNkJBhLxEjD3LRnFrM8fkALcCHRYLAfeqMUvWJJDUTFlzc0xTchEKrwjaJ1gjrCi81gMaFQCOoz/TpGgDE+IGZ4si9nheWowumc9hD15mYfIp+reQvlFY1R3ttH7iYezqj0byPQvCuQhFefloZ2opxg3E5AK/FbbCb0LHHRv4B/5nTysiUd93NQfwhMhjJxZKU+jS5q+J; 20:5iQ/gHThDbr8tGESAr7Yk5pA4jJl4YT6E8SicwuXBfNF80ZK0admXfN6W/nTO/fsOgeRF+jcpBjQ/cR1A5/tOxvSb93lr5C4bYnLsif+gs0vwb1b/rFrkmG3BX4FykpJvUwXiIpX40DjSlb7P4xHCFgSryLV3A5ULHF5lmzZlxw=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 0195fba1-5bb0-46c8-7963-08d5930c0fd0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:VI1PR07MB1293; 
x-ms-traffictypediagnostic: VI1PR07MB1293:
x-microsoft-antispam-prvs: <VI1PR07MB1293491C45EE837CD2C2C1A7D6AD0@VI1PR07MB1293.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231221)(944501327)(52105095)(6041310)(20161123560045)(20161123558120)(20161123564045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(6072148)(201708071742011); SRVR:VI1PR07MB1293; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1293; 
x-forefront-prvs: 06237E4555
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(346002)(366004)(39850400004)(396003)(376002)(189003)(199004)(68736007)(6916009)(478600001)(2900100001)(4326008)(2906002)(7736002)(316002)(786003)(3280700002)(3660700001)(82746002)(83716003)(5250100002)(6246003)(305945005)(966005)(57306001)(86362001)(5660300001)(33656002)(14454004)(229853002)(6116002)(50226002)(6506007)(102836004)(53546011)(72206003)(74482002)(446003)(99286004)(6306002)(6512007)(81166006)(81156014)(46003)(6436002)(76176011)(8936002)(36756003)(186003)(53936002)(2616005)(106356001)(6486002)(25786009)(105586002)(11346002)(8676002)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR07MB1293; H:VI1PR07MB0879.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
x-microsoft-antispam-message-info: Qk7X5l2jw7mUaBLo8nACORLFJe95EYuLT62t6nXohbDFIOwKgrPtPIchgYo9gqSTnumDia3kiGcerN9T5XPGHacVzUQKNbOknQcqW7DW/Nu6TJMBmbqXbuUrQSBVw6qLY0HH10q4FGly/bgDOjKn7imfkXJUXPPl5It0D6qXc5lHPKbKTOOyNvZwr+4GsaI5NpSD9q1L3Z0q6H4rGI1qmkpFbfsFL1KwzmZ68OJ9qI+Kxh8UeLN/Ld0T41UcIRey41LPoZXAMBFzqVCYjjxwpKwh+DGopLtdZxAMDZibDoi7tYKcAEO54xllZIvRtRUvLYM7VlJYmC8OV66KPyEAtw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <18245B7B10A6D746AFD0B5B78A17B5E9@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-Network-Message-Id: 0195fba1-5bb0-46c8-7963-08d5930c0fd0
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Mar 2018 11:23:55.6223 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1293
X-MC-Unique: xbegttNFPkq1n628mfo-yw-1
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/MHYMe4FIU3wUhCbIHmZoz8Qx7i0>
Subject: Re: [dnssd] multicast wifi draft mentioned in the session today
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2018 11:24:06 -0000

> On 22 Mar 2018, at 10:20, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>=20
> https://tools.ietf.org/html/draft-ietf-mboned-ieee802-mcast-problems-01

Thanks Mikael.

The context here is the rationale to move towards future service discovery =
work using unicast protocols, as proposed in draft-sctl-service-registratio=
n-00. While the above draft focuses on WiFi, similar issues apply in mesh n=
etworking technologies that may be used, particularly in home networks.

One outcome of the WG meeting was to revisit our charter, where we can incl=
ude this area explicitly, alongside the relatively new work on privacy.  Th=
e chairs will push discussions on the charter, and the scope of that privac=
y work, forward after the Easter break.

Tim

