maintain the table is not ideal. Instead, let's create an IANA registry for
it, populate it with existing values, and make the libpcap group the Expert
Review.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
n them a bit to give a slightly stable document to
point at, or at least to argue why no existing type works for them.
Then they get the number, and if we are lucky, we also have a stable link to
their format. With IANA Expert Review, we could essentially do exactly the
same thing --- just that IANA
x27;s not just a format at rest anymore.
I am not subscribed to the opsawg list, I'm sure.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
way to handle this sort of thing is to create a
> table that MUD/ANIMA controllers simply download when they see the URL. It
> might look something like this:
When you say ANIMA controller, I think you mean the JRC?
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consul
de them with a sensible URL to point at, and it
wouldn't be at /.well-known/sbom.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
tom petch wrote:
> web should be https not http
There are lots of reasons why a self-hosted SBOM might have to be HTTP.
> On 02.09.22 18:57, internet-dra...@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Int
m not sure that
there is enough here to actually create interoperable implementations.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
Michael Richardson wrote:
> I have read draft-ietf-opsawg-service-assurance-architecture at the
> request of a few people. This is not part of any directorate review
> (that I remember, or that shows up in my review list). If it's useful
> for me to plug this
BOM at a vendor hosted location.
> The reminder of the security section, addresses other threats, such as
> an attacker with control of the devices providing false information in
> the SBOM, or an attacker hijacking the manufacturer publishing site
The SBOM is usually
I've read the document, and I would say that it looks great.
Adopt it, and WGLC it already. I don't see anything left to do.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP
Benoit Claise wrote:
> Thanks for your review.
> And sorry for the delay: I was not too sure how to react to this
> review. Another review after WGLC, to be integrated in IETF LC?
> Document
meh, sorry.
> On 9/13/2022 12:45 AM, Michael Richardson wrote:
Benoit Claise wrote:
> If you speak about RFC 7942, it mentions:
>We recommend that the Implementation Status section should be
> removed from Internet-Drafts before they are published as RFCs.
> So isn't sufficient to have this information in the write-up. You can
> wr
Jean Quilbeuf wrote:
> Dear All, This update addresses comments from Michael Richardson.
Confirmed! Thank you.
Tianran has asked me to update some things in the writeup, which I'll do
Wednesday.
___
OPSAWG mailing list
OPSAWG@ietf.o
unconfigured devices which have not been onboarded with
an administrative credential should not answer queries about their SBOM.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
O
nt from scratch. All good ideas, but the barn doors have been open
for a decade, and the horses are long gone. This document simply tries to
keep the horses from jumping off cliffs.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottaw
ts are not new, have already been adopted, reviewed, but there
does not seem to be a path towards WGLC yet.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP sig
cification defining DHCPv6-Options could
> suggest that implementations SHOULD support 64K RADIUS packets.
Does Radius over TCP relax any of the 4K issue?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
sig
by me making
> editorial comments. AFAICT the I-D has not had a YANG Doctor
> review.
Seems that this should have happened.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
internet-dra...@ietf.org wrote:
> A diff from the previous version is available at:
>
https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-service-assurance-yang-09
I've updated the shepherd review to note the change to health-score.
--
Michael Richardson , Sandelman Sof
us, Thanks in
advance.
> -Qin (On behalf of the team)
>
> Alternatives:
> ----
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP si
WG to process the document.
All three documents can be found at: https://github.com/pcapng/pcapng
if there are pull requests that someone would like to make when they do their
review.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP
>>>>> OPSAWG on behalf of Michael Richardson
>>>>> writes:
> That is not what I see in the Datatracker.
Not important :-)
The previous adoption call was botched, and I stated what I expect the desired
states to be.
Do you object to the plan?
--
Michae
y to mark it's intended status as BCP, and that's
correct.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing li
Henk Birkholz wrote:
> This internet draft updates RFC8520. The authors believe the
I think that this document needs to be Proposed Standard.
It normatively updates RFC8520, which I believe went through as AD Sponsored,
which itself is PS.
--
Michael Richardson. o O ( IPv6
annot
> produce a specification to its usual standards, how far should it go?
> In passing, 65000 appears in two ranges.
Yes. [32678,65000) then.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.as
t the WG will listen to your requests, and you think that the WG will
publish the document without changes?
Do you understand that the authors/maintainers of the web site are in fact the
authors of the document?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman So
Carsten Bormann wrote:
> More fundamentally, I’m having a problem with arguments of the form
> “The website did such a good job we can’t move the registration
> function to IANA”. (If we have a problem with IANA registrations, we
> should identify it and address it.)
Thank you f
Tiru, Thank you for the WGLC comments!
I will post a new revision this week with revisions.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
itors' copy of internet drafts stored on github, does not actually publish
any names.
Instead a wildcard exists to answer.
github would be unable to provision all infinity of possible names into the PTR
records.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Sof
NS in IoT devices
> Authors : Michael Richardson
> Wei Pan
> Filename: draft-ietf-opsawg-mud-iot-dns-considerations-07.txt
> A diff from the previous version is available at:
>
https://author-tools.ietf.org/iddiff?url2=draft-ietf-opsawg-mud-iot-dns
mud-iot-dns-considerations-07&url2=draft-ietf-opsawg-mud-iot-dns-considerations-08&difftype=--html
This is includes RFC9019 fix. Are there any other WGLC comments?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ott
The descriptions on the website also have links to external
> specifications; those should be preserved, in some fashion, in the
> I-D.
I guess that we need to do a detailed review of each entry.
Perhaps there will be entries which WG members have better references, even.
--
M
G*, and I wish we could call it PCAPv2 instead.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@
Carsten Bormann wrote:
> On 2023-01-24, at 23:56, Guy Harris wrote:
>>
>>> I still hate the name PCAP *NG*, and I wish we could call it PCAPv2
instead.
> Why don’t we call it TLS?
Yes, I acknowledge the sillyness of that.
> (SCNR. Renaming well-known standards at the occ
Guy Harris wrote:
> On Jan 24, 2023, at 2:02 PM, Michael Richardson
wrote:
>> With this document adoption, we finally have all the PCAP related
documents
>> in the DT. One thing that was mentioned to me is that the PCAPNG
document
>> has an IANA Re
PcapNG could be "Packages of Network and Generics."
or...?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG ma
entually decide they have re-organize
things. We should have some way to deal with that.
The reason we need to write a new standard for this is because we need to set
expectations for the MUD Controller and MUD file provider to agree on how to
do this process.
--
Michael Richardson. o O ( IP
psulation point?
If it would make sense to apply rules to the outer one, would it be easier to
just have more than one tunnel?
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signatu
f March 2023).
Shouldn't this go to https://datatracker.ietf.org/rg/qirg/about/ instead?
I don't understand why opsawg would be a place for this liaison.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signatur
Henk Birkholz wrote:
> "No, I'm not aware of any IPR that applies to this draft."
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
Henk Birkholz wrote:
> "No, I'm not aware of any IPR that applies to this draft."
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
the WG) agreed to that a long time ago.
I updated the document to reflect that, and add BCP14 terminology.
I believe that Henk updated the DT to reflect that status as well.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signatu
ETF change control.
(When we started this work back in 2012, the story for pcapng was different)
I would like to rename "PCAP NG" as something less "NG".
I'd suggest PCAP 2022 or something like that.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelm
IESG Approval.
Now, linktypes "highest" level is Specification Required.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSA
7;t be mixed with
> the historic ones.
We allocated a few chunks for private use years ago, and they could be in use
internally somewhere, so we don't want to change that. But, maybe we should
mark them as deprecated?
--
Michael Richardson. o O ( IPv6 IøT consulting
Will documents like draft-havel-opsawg-digital-map and
draft-davis-opsawg-some-refinements-to-rfc8345 move to IVY once it is
chartered?
(Not sure if the ML will change names)
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
ould probably undo that and allow for 32-bits types, if someone felt that
32768->65000 was really not enough FCFS space)
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
cker.ietf.org/doc/html/draft-havel-opsawg-digital-map-00#name-network-inventory-ivy-propo
okay. I don't really understand why a digital map isn't part of the
inventory problem, but it's not really my problem.
I'm just concerned about opsawg overwork.
--
Michael Rich
shepherd for other people's documents, then why would they
shepherd for your documents?
(all sausage is good if you pick the right mustard!)
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signatur
Thank you for the comments, I'll try to get a new document out next week.
I'm sorry that the grammar was poor, and I'll re-edit again.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
D
; Identifying the IoT device type empowers the attacker to launch
> targeted attacks to the IoT device (e.g., Attacker can advantage of
> the device vulnerability).
> can take advantage of any known vulnerabilities on the device.
fixed.
> (33) p 12, sec 7.
mp;difftype=--html
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
k in Progress, Internet-Draft, draft-ietf-
> dnsop-terminology-ter-02, 3 August 2020,
> <https://www.ietf.org/archive/id/draft-ietf-dnsop-
terminology-ter-02.txt> .
RFC8499bis now, and I think it should be normative.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
ersion of the doc)
> once you have text for the other issues that you have flagged as github
> issues.
Now posting -10 based upon Med's feedback in this thread.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
Eliot Lear wrote:
> On 23.10.2023 17:27, Michael Richardson wrote:
>> Maybe someone else can explain it back to me in a better way.
> The fundamental issue is this:
> * If you are permitting an IP address in an ACL based on a name in a
> MUD file, t
ight bulb might burn only a few
dozen addresses, while serving thousands of bulb's need to ask about software
updates.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
to the device, and specifically do not want
the liability. Even enterprises that do forced TLS inspection are apparently
recognizing that they MUST exempt banking and health traffic; or face serious
legal consequences.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Soft
I'd kill sessions
because the DNS name timed out. Maybe, I'd have an upper limit on session
state duration, but does violate the end to end principal. Still, it happens
all the time with NAT44.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
implementations might decide differently, but
this document is not about that part.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
___
OPSAWG mail
Hi, the three PCAP I-Ds have been stable for sometime now.
draft-ietf-opsawg-pcap-03- going to Historic.
draft-ietf-opsawg-pcaplinktype - Standards Track to create Registry
draft-ietf-opsawg-pcapng-01 - going to Informational.
Can we WGLC them, and find shepherds for them?
--
Michael
what that is; the entry for it on
> the tcpdump.org link-layer header types page at
> https://www.tcpdump.org/linktypes.html
> has a link to a description of the format.
okay, so let's include that link.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT
l that a 2.0
could be done.
> On 15.11.2023 10:33, Michael Richardson wrote:
>> Hi, the three PCAP I-Ds have been stable for sometime now.
>>
>> draft-ietf-opsawg-pcap-03- going to Historic.
>> draft-ietf-opsawg-pcaplinktype - Standards Track
neT48DBzmGq3e5M_bwOok/?
I would do a final pass to import linktypes.html just before WGLC, and then
update linktypes.html to note that new document exists.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TR
e
registries that potentially required any kind of IETF actions to fill them.
Now, we've changed the IANA Considerations since then, but that's where we
were a few years ago.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
onsiderations since then, but
>> that's where we were a few years ago.
> OK, but these are IETF WG documents, not on the ISE stream. So I don’t
> think this information is relevant (if it were, we’d need to advance it
> from rumor level to some authorita
t way is the draft unclear about how things would go forward?
I don't know that we can effectively deprecate anything; but we could
certainly try.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Descripti
rt, which I'll post this week.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
to the IESG.
> Thanks to the authors, contributors, WG, and our shepherd, mcr.
The downrefs that were supposed to be added for RFC9092 were not done, and
I'm unclear who/what will add the right ones for the update.
--
Michael Richardson , Sandelman Software Works
-=
when RFC9092 went through Last Call,
and some of
those references are occuring again.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signature.asc
Description: PGP signature
___
Rob Wilton (rwilton) wrote:
> If you can remind me after the AD review and perhaps put them in the
> shepherd writeup (whoever the shepherd is) that would help me check
> that they are listed correctly for this bis document.
Done.
> I have to confess that I'm not completely bought in
another set of abbreviations?
inb-OAM, oob-OAM.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG
16, followed by the TLS major version 0x03.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https
changes in this version, it is awaiting shepherd write-up.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.or
ber of arenas, including up-coming proof-of-transit work.
Nits:
* OAM is not expanded in the introduction, and the RFC6191 reference needs to
come earlier.
* Section 2 starts off talking about history, and then gets into defining new
terms. I thought I was going to learn more about in-band/out-of-ba
;d welcome a citation from radio and/or SS7 telephony!
I don't have a good one; I didn't live through that.
Fidonet, Xmodem->Zmodem to UUCP to IP for me :-)
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
ite up.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
dents; but perhaps at first, one might not even know what
kind of thing happened.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
OPSA
on
> required type, e.g., 300-32767 that won't be mixed with the historic ones.
It's grandfathered as far as I'm concerned.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP si
Thus,"
fixed.
> Section: 9, draft text: Prior to the standardization of the process in
> this document, if a device was infiltrated by malware, and said malware
> wished to make accesses beyond what the current MUD file allowed, the
> the malware would have to: Warning:
> distributed denial of service attack resulting in high costs to those
> customers, or such an attack could potentially include writing content.
> Warning: It appears that hyphens are missing. Suggested change:
> "denial-of-service"
okay.
> Section: 6, draf
f DNS in IoT devices
> Authors: Michael Richardson Wei Pan Name:
> draft-ietf-opsawg-mud-iot-dns-considerations-11.txt Pages: 17 Dates:
> 2024-02-08
> Abstract:
>This document details concerns about how Internet of Things devices
> use IP addresses and
er RFC
editor thinks)
>> The ADD WG has written [I-D.ietf-add-dnr] and [I-D.ietf-add-ddr] to
>> provided.
> Same here.
Already fixed in -11 I think.
https://author-tools.ietf.org/iddiff?url1=draft-ietf-opsawg-mud-iot-dns-considerations-11&url2=draft-ietf-ops
n't get this suggestion.
RW> The suggestion is to use “outside the
RW> service facility” rather than “outside of …” Thanks, Rob
Now reads:
} It is probably undesirable to perform any upgrade to an airplane outside the
service facility.
As the changes
usiness with consulting people is a courtesy :-)
So, Benoit and Mohammed (NMOP chairs) can just do this.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
none of the
existing rules ought apply, and effectively, this is a new, unauthorized
device. It also will break any existing WPA keying, so the device would have
to do some rekeying, perhaps even onboard again.
> There is some discussion of the device identity issue in
> the security
hope to hear from you soonish if you are happy or unhappy with these
changes, and I'll post a new version on Friday March 1.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|IoT architect [
] m...
thout bound, it is unlikely to be a burden.
A site with thousands of similar devices could keep a common list of URLs.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
___
ort (upward flowing, from IoT device to SUIT status tracker),
it has somewhat less connection to what's actually running on the device.
It does, however, provide a palette of URLs that are valid.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software W
UD file (and
signature) 1000 times.
If you really had a problem with the number of URLs stored, which I don't
think anyone will really have.
I don't think we need to keep track of malicious URLs that we ignored.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandel
Michael Richardson wrote:
> Why would this be a challenge? The MUD manager is unlikely to be a
> non-constrained device. (even if it's in a home router, which I've
Argh. ENOCOFFEE: too many negatives in a row
_The MUD manager is not constrained_
--
Michael Ric
and classes of
> device" -> "For some users and classes of devices"
check.
https://github.com/IETF-OPSAWG-WG/draft-ietf-opsawg-mud-iot-dns-considerations/pull/14/files
--
] Never tell me the odds! | ipv6 mesh networks [
] Mi
Rob Wilton (rwilton) wrote:
> The TD;LR is I think that your latest changes are good and I’ll send
> -12 to IETF LC.
I think that I got the rest of your nits as well in the version I posted
yesterday.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman So
quot;, but could use some formal
> description.
Ugh. I don't think we have any RFC that defines it. It's not in 8499bis.
Maybe someone else has an idea for a good reference.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and W
now
+that the list was complete.
+
+But, due to the above problems, a strong recommendation is to avoid using
+tailored responses as part of the names in the MUD file.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Wo
MUD file)
upgrades.examples.com-- tailored response name (put into firmware)
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|IoT architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails
More IESG members seem to have read your discuss comments rather than
abstract for the document, that clearly the document needs to be rewritten.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
n additional protocol work to resolve any
> issues.
I didn't know what lacunae are.
dictionary.com told me: noun
An empty space or a missing part; a gap.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software
r definition of allowed local access, and it could specify
access to the update server. That is not done by DNS exactly, and we
probably have work to do here.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa an
might read this once.
https://author-tools.ietf.org/iddiff?url1=draft-ietf-opsawg-mud-iot-dns-considerations-12&url2=draft-ietf-opsawg-mud-iot-dns-considerations-13&difftype=--html
Looks like this might also contain some xml2rfc version based changes, e.g.:
as s3.amazonaws.com). vs as &
y do it, then they set some defaults and arrange backups)
It sounds like you've become a BOF co-chair.
Was that intended?
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =- *I*LIKE*TRAINS*
signatur
1 - 100 of 348 matches
Mail list logo
