I am pleased to go with:
The IESG has concluded that publication could potentially disrupt the
IETF work done in WG and recommends not publishing the
document at this time.
I'm OK with this as well.
Jari
___
Ietf mailing list
Ietf@ietf.org
https://
Thank you for your review. Can you point me to any standards track
IETF documents which might need normative reference to this document?
One example: draft-lee-sip-dns-sd-uri-03
Henning
___
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailm
John Levine wrote:
>> For instance, what would happen if mail servers provided feedback to
>> both senders (on a per message basis in the form of NDNs)
>
> Well, since 95% of all mail is spam, and all the spam has fake return
> addresses, you'd increase the amount of bogus NDNs by more than an
> o
Greetings!
The IANA will be holding "Office Hours" at the IETF-73 in Minneapolis.
This will continue to give everyone an opportunity to discuss IANA
Considerations in your documents, requests for registrations in existing
registries or any other questions you may have.
The IANA will have a table
In message <[EMAIL PROTECTED]>, Florian Weimer writes:
> * Stephane Bortzmeyer:
>
> > Second question, the document indeed standardizes many things which
> > are not in common use but does not point towards a rationale, so some
> > choices are puzzling. Why TXT records to point to an URL and not
Names of people attending SIP / SIPPING who requested before noon
Saturday were encoded in NYC and handed to "Omer Boyaci"
<[EMAIL PROTECTED]>.
The names are located here : http://groups.google.com/group/ietfrfid/files
You dont need to login but if its inconvenient email me to request
status of y
* Mark Andrews:
> In message <[EMAIL PROTECTED]>, Florian Weimer writes:
>> * Stephane Bortzmeyer:
>>
>> > Second question, the document indeed standardizes many things which
>> > are not in common use but does not point towards a rationale, so some
>> > choices are puzzling. Why TXT records to p
Florian Weimer wrote:
> The expectation is that error messages generated from TXT records
> contain the actual IP addresses which triggered the DNSBL lookups. As
> a result, if you list a /16 (say), you need publish 65,536 different
> TXT records.
>
> Currently, these records are synthesized usi
* Mark Andrews:
>> >> The lack of a macro capability also means that it's basically
>> >> impossible to secure DNSBL zones with DNSSEC when they contain larger
>> >> chunks of address space; see the example in section 2.1.
>> >
>> >How so?
>>
>> The expectation is that error messages generate
>The expectation is that error messages generated from TXT records
>contain the actual IP addresses which triggered the DNSBL lookups. As
>a result, if you list a /16 (say), you need publish 65,536 different
>TXT records.
Some do, some don't. In any event I agree that DNSSEC is not ideally
suite
* Chris Lewis:
> Florian Weimer wrote:
>
>> The expectation is that error messages generated from TXT records
>> contain the actual IP addresses which triggered the DNSBL lookups. As
>> a result, if you list a /16 (say), you need publish 65,536 different
>> TXT records.
>>
>> Currently, these re
* Mark Andrews:
>> I didn't say it was a DNSSEC problem. I just wanted to note it's
>> impossible to secure some existing DNSBL zones using DNSSEC without
>> sacrificing some of the functionality which is mentioned in section
>> 2.1 in the draft.
>
> I still don't believe your claim.
I can
Florian Weimer wrote:
> I can't sign a thousand million RRsets and serve it in a DoS-resilient
> manner, even with John's partitioning idea (which is rather neat,
> thanks!).
I may have to keep that in mind if I ever DNSSEC our internal composite
DNSBL zone, which has probably near 500M IPs liste
In message <[EMAIL PROTECTED]>, Florian Weimer writes:
> * Mark Andrews:
>
> >> >> The lack of a macro capability also means that it's basically
> >> >> impossible to secure DNSBL zones with DNSSEC when they contain larger
> >> >> chunks of address space; see the example in section 2.1.
> >> >
>
In message <[EMAIL PROTECTED]>, Florian Weimer writes:
> * Mark Andrews:
>
> > In message <[EMAIL PROTECTED]>, Florian Weimer writes:
> >> * Stephane Bortzmeyer:
> >>
> >> > Second question, the document indeed standardizes many things which
> >> > are not in common use but does not point toward
Greetings, quick update...
Streaming got off to a good start with the iepg meeting this (sunday
morning). commencing Monday all 8 parallel tracks will be broadcast
starting with the at 0900 CST and continue until Friday the 21st at 1515
CST.
The links for streaming sources and the schedule are av
16 matches
Mail list logo
