search for: rfc

FYI, the Ogg Opus encapsulation is now RFC 7845: https://tools.ietf.org/html/rfc7845 -------- Forwarded Message -------- Subject: [codec] RFC 7845 on Ogg Encapsulation for the Opus Audio Codec Date: Fri, 29 Apr 2016 19:47:28 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc-dist at rfc-editor.org CC: drafts-...

FYI, the Opus RTP payload format is now RFC7587: https://tools.ietf.org/html/rfc7587 Cheers, Jean-Marc -------- Forwarded Message -------- Subject: [payload] RFC 7587 on RTP Payload Format for the Opus Speech and Audio Codec Date: Tue, 30 Jun 2015 16:33:17 -0700 (PDT) From: rfc-editor at rfc-editor.org To: ietf-announce at ietf.org, rfc...

Hello list, I notice that the dialplan method SIPAddHeader is not working : in dialplan : /exten => s,n,SIPAddHeader(Privacy: id)/ in SIP invite no trace of this header : /INVITE sip:0473 at sip.domain.be SIP/2.0 Via: SIP/2.0/UDP 192.168.1.106:5063;branch=z9hG4bK-5b2b1b97 From: "VC" <sip:voip2 at sip.domain.be>;tag=729476652f511c67o2 To: <sip:0473 at sip.domain.be>

A new RFC was published today, RFC 3601: Abstract: "This memo describes the full set of notations needed to represent a text string in a Dial Sequence. A Dial Sequence is normally composed of Dual Tone Multi Frequency (DTMF) elements, plus separators and additional "actions" (suc...

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and...

Hi everyone, We finally made it! Opus is now standardized by the IETF as RFC 6716 (http://tools.ietf.org/html/rfc6716). See the announcements at: https://hacks.mozilla.org/2012/09/its-opus-it-rocks-and-now-its-an-audio-codec-standard/ http://www.xiph.org/press/2012/rfc-6716/ Feel free to spread those around :-) We're also releasing both 1.0.0 (same code as the RFC) and...

Greetings List,Trying to interconnect with a new provider.. the require a?compliance?with?RFC 3261 ?so knowing less than needed about RFC documentations.. i would like to know if Asterisk is actually in compliance with?RFC 3261 or not..?Can any one help with this? Regards -- Tarek Sawah Integrated Digital Systems CCNA, MCSE, RHCE, VoIP USA: +1 347 562 2308 _________________...

Since Jakob had expressed some concerns regarding machine-generated files, I asked him by email about his views on this RFC. Here are the emails that we exchanged in attach. Anyone feel free to jump in via the mailing-list. TIA -- Evandro Menezes Austin, TX emenezes at codeaurora.org Qualcomm Innovation Center, Inc is a member of the Code Aurora Forum -------------- next part -------------- An e...

...11.5.253]] [FirstClass IMAP4rev1 server v8.262 at mail.ares.school.da.org ready] ?Can't do /authuser with this server When I try to connect to the mailbox: {ares.school.da.org:143/imap/user="fbeck"}Inbox I am prompted with a password which is accepted. mtest response is: IMAP4rev1 (RFC 3501) server ares.school.da.org Mutually-supported SASL mechanisms: CRAM-MD5 Supported standard extensions: Access Control lists (RFC 2086) Multiple namespaces (RFC 2342) Extended UID behavior (RFC 2359) Implementation identity negotiation (RFC 2971) LIST children announcement (RFC 3348) Suppo...

...how_bug.cgi?id=1647 mackyle at gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mackyle at gmail.com --- Comment #2 from mackyle at gmail.com --- RFC 6668 [1] (2012-07) updated RFC 4253 adding the SHA-256 data integrity algorithm as a new recommended algorithm. FIPS 186-4 [2] (2013-07) section 4.2 includes the same DSA parameters as FIPS 186-3: L = 1024, N = 160 L = 2048, N = 224 L = 2048, N = 256 L = 3072, N = 256 And it would seem that t...

...how_bug.cgi?id=1647 mackyle at gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mackyle at gmail.com --- Comment #2 from mackyle at gmail.com --- RFC 6668 [1] (2012-07) updated RFC 4253 adding the SHA-256 data integrity algorithm as a new recommended algorithm. FIPS 186-4 [2] (2013-07) section 4.2 includes the same DSA parameters as FIPS 186-3: L = 1024, N = 160 L = 2048, N = 224 L = 2048, N = 256 L = 3072, N = 256 And it would seem that t...

Here's the bug and proposed patch. It's pretty trivial. https://bugzilla.mindrot.org/show_bug.cgi?id=1856 Quoting RFC-2474: A replacement header field, called the DS field, is defined, which is intended to supersede the existing definitions of the IPv4 TOS octet [RFC791] and the IPv6 Traffic Class octet [IPv6]. [...] The structure of the DS field shown above is incompatible with the existing definition of the...

This document: http://www.iana.org/assignments/dhcpv6-parameters/dhcpv6-parameters.xml Has the same (plus expanded) list of cpu arch values for parameter 0x93. This list matches RFC 4578 except for values 7 and 9 which are EFI ByteCode and x86-64. Turns out RFC 4578 is wrong https://www.rfc-editor.org/errata_search.php?rfc=4578 And 00:07 *is* the correct value for 64-bit x86 clients and the comment on the wiki should be updated. See: http://www.syslinux.org/wiki/index.php...

...> > > https://lkml.org/lkml/2018/7/3/33 > > > > Both of ping and netperf worked as expected. > > > > v1 -> v2: > > - Use READ_ONCE() to read event off_wrap and flags together (Jason); > > - Add comments related to ccw (Jason); > > > > RFC (v6) -> v1: > > - Avoid extra virtio_wmb() in virtqueue_enable_cb_delayed_packed() > > when event idx is off (Jason); > > - Fix bufs calculation in virtqueue_enable_cb_delayed_packed() (Jason); > > - Test the state of the desc at used_idx instead of last_used_idx > &...

There is no hash algorithm associated with SSH keys. The key format for RSA keys is always ?ssh-rsa?, and it is capable of being used with any of the available signature algorithms (ssh-rsa for SHA-1 and rsa-sha2-256 or rsa-sha2-512 for SHA-2). See section 3 in https://www.rfc-editor.org/rfc/rfc8332: rsa-sha2-256 RECOMMENDED sign Raw RSA key rsa-sha2-512 OPTIONAL sign Raw RSA key These algorithms are suitable for use both in the SSH transport layer [RFC4253 <https://www.rfc-editor.org/rfc/rfc4253>] for server authentic...

Mark and Ed received word today that the long-awaited RFC for IAX2 has been approved by the IETF, and is now published: http://www.rfc-editor.org/authors/rfc5456.txt Thanks to Ed Guy, Mark Spencer, Brian Capouch, Frank Miller, and Kenny Shumard! Lots of revisions and discussions have paid off. JT --- John Todd email:jtodd at...

...ple folks who are already *using* LTO to find a proposal they're happy with. Until you do that, you are unlikely to make much progress. Philip On 08/12/2015 09:13 AM, Teresa Johnson wrote: > Ping. Explicitly adding a few more people who commented on the earlier > (high-level) ThinLTO RFC. I removed the body of the RFC here since the > original was large and had trouble getting through the mailer. I also > updated the patch mentioned below so that it was emailed to > llvm-commits properly. > > Thanks, > Teresa > > On Mon, Aug 3, 2015 at 11:59 AM, Teresa Jo...

I apologize up-front if this is the wrong list for this question. Can OpenSSH be made to work with the MODP Groups in RFC 5114? ?The RFC itself makes a comment in section 3.4 that mentions that RFC 4419 extended the original SSH model to allow Diffie-Hellman parameters to be transmitted as part of the key exchange messages, but I'm not clear how that works with OpenSSH's moduli file. Do I add the MODP Groups...

Hello all, I'm currently wondering whether Dovecot submission proxy service supports RFC 8314 ? 3.3 as well, which means implicit TLS for SMTP submission. https://github.com/dovecot/core/blob/2cbbe9b4829adb184c83dbf780316f4144559054/doc/example-config/conf.d/10-master.conf#L48 from Git master just mentions port 587 like this: service submission-login { inet_listener submission {...

On Thu, Aug 14, 2008 at 9:14 PM, Silvia Pfeiffer wrote: > The IETF has a final draft of our RFC at > ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes > from 3534 to 5334 - funny!). Didn't we decide YUV4MPEG should be 8 octets as well? -r