Subject: Re: [Dots] [core] Webex details for today's virtual Interim

From: "Konda, Tirumaleswar Reddy" <[email-masked]>
Date: Thu, 13 Sep 2018 06:56:39 +0000

Responding to the Open questions:

* Would it be useful to have a general-purpose content format for

providing details of an alternate server, or is the information too

DOTS-specific?

Response> The information is DOTS-specific, the response conveys both the alternate DOTS server domain name and its IP addresses to handle the DDoS attack scenario where the DOTS client cannot reach the DNS server to resolve the alternate DOTS server domain.

* Should a more specific media type than "application/cbor" be used?

Response> Yes, DOTS signal channel draft has been updated to use specific media type ("application/dots+cbor")

Open questions:

* Is {elective, safe to forward, not part of the cache key} the right choice?

Response> Yes, will update hop-limit option.

* Is {elective, safe to forward, part of the cache key} the better choice?

Response>  RFC7252 says responses of 5.xx class are cacheable, do you see the need to explicitly say 5.06 error response is part of the cache key ?

* Is there a better number than 5.06? (HTTP 506 is: Variant Also

Negotiates [RFC2295])

Response> SIP uses 483 (Too many hops), but I don’t see any equivalent error response in HTTP.

Cheers,
-Tiru

Cheers,
-Tiru

From: core <[email-masked]> On Behalf Of Carsten Bormann
Sent: Wednesday, September 12, 2018 8:02 PM
To: Core <[email-masked]>
Subject: [core] Webex details for today's virtual Interim

I’m starting to understand this Webex thing.

Here are the Webex details for the meeting today (which starts in a bit less than half an hour).

Agenda so far:

— Content-Format 62 (multipart-core) is allocated
— finishing touches for draft-boucadair-core-hop-limit (In working group adoption call); any other continuation of the previous interim
    — minutes from previous interim:  https://datatracker.ietf.org/meeting/interim-2018-core-02/materials/minutes-interim-2018-core-02-201808291500
— way forward with stateless proxies as needed for 6tisch, specifically draft-hartke-core-stateless: Approach A or B (or something unknown yet?)

Grüße, Carsten

Virtual Interim

Wednesday, September 12, 2018

3:00 pm  |  Greenwich Time (Reykjavik, GMT)  |  1 hr

Meeting number (access code): 317 115 178

Meeting password: constrained

Add to Calendar<https://ietf.webex.com/ietf/j.php?MTID=mdac039703be597b24cf19d2a6f602489>

When it's time, join the meeting<https://ietf.webex.com/ietf/j.php?MTID=m4a9735d0db3ce49f3f697a2679b57817>.

Join by phone

1-650-479-3208 Call-in toll number (US/Canada)

Can't join the meeting?<https://collaborationhelp.cisco.com/article/WBX000029055>

IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session.