Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header
Rakesh writes: > Can I just know on INVITE request if I get the below characters then is it > OK as per ABNF grammar? Please note I am not asking about the header > rather I need to know the correctness of the character that has appeared on > INVITE request. Looking at the hex dump that you provided: It contains 43 bytes of FF, followed by the following text, followed by CR LF: X-BroadWorks-DNC: network-address="sip:+34937817016@mt;user=phone";user-id="937817...@mfe.telefonica.net" That text looks like a header that might be used in SIP requests. But it is a non-standard header, you can tell because it starts with "X-". It is probably defined by BroadWorks. Without knowing how BroadWorks has defined the header, and the operational environment in which it was used, there's no way to know whether it is valid. Dale ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header
Rakesh, I still don't understand your question. What you show below appears to be garbage that happens to include a few fragments that resemble sip URIs. Did you receive this on a port where you expect to receive sip messages? If so, this clearly doesn't conform to the ABNF syntax of a sip message. Thanks, Paul On 2/6/19 5:12 AM, Rakesh wrote: Hi, Further to add to the last this is what I am looking for the bold part *ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff * 0010 * ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff* 0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0020 ff ff ff ff ff ff ff ff ff ff ff 58 2d 42 72 6f ÿÿÿX-xro 0030 61 64 57 6f 72 6b 73 2d 44 4e 43 3a 20 6e 65 74 : net 0040 77 6f 72 6b 2d 61 64 64 72 65 73 73 3d 22 73 69 work-address="si 0050 70 3a 2b 33 34 39 33 37 38 31 37 30 31 36 40 6d p:@xx.yyy.net 0070 74 3b 75 73 65 72 3d 70 68 6f 6e 65 22 3b 75 73 t;user=phone";us 0080 65 72 2d 69 64 3d 22 39 33 37 38 31 37 30 31 36 er-id="" 0090 40 6d 66 65 2e 74 65 6c 65 66 6f 6e 69 63 61 2e @xx.yyy. 00a0 6e 65 74 22 0d 0a net".. ÿÿÿX-xro 0030 61 64 57 6f 72 6b 73 2d 44 4e 43 3a 20 6e 65 74 : net 0040 77 6f 72 6b 2d 61 64 64 72 65 73 73 3d 22 73 69 work-address="si 0050 70 3a 2b 33 34 39 33 37 38 31 37 30 31 36 40 6d p:@xx.yyy.net 0070 74 3b 75 73 65 72 3d 70 68 6f 6e 65 22 3b 75 73 t;user=phone";us 0080 65 72 2d 69 64 3d 22 39 33 37 38 31 37 30 31 36 er-id="" 0090 40 6d 66 65 2e 74 65 6c 65 66 6f 6e 69 63 61 2e @xx.yyy. 00a0 6e 65 74 22 0d 0a net".. [image: image.png] BR/// Rakesh Kumar Mohanty On Wed, Feb 6, 2019 at 3:21 PM Rakesh wrote: Hi Expert, Can I just know on INVITE request if I get the below characters then is it OK as per ABNF grammar? Please note I am not asking about the header rather I need to know the correctness of the character that has appeared on INVITE request. [truncated]\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\37 Expert Info (Note/Undecoded): Unrecognised SIP header (���) [image: image.png] [image: image.png] BR/// Rakesh Kumar Mohanty ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
Re: [Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header
Hi, Further to add to the last this is what I am looking for the bold part *ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff * 0010 * ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff* 0020 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0010 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 0020 ff ff ff ff ff ff ff ff ff ff ff 58 2d 42 72 6f ÿÿÿX-xro 0030 61 64 57 6f 72 6b 73 2d 44 4e 43 3a 20 6e 65 74 : net 0040 77 6f 72 6b 2d 61 64 64 72 65 73 73 3d 22 73 69 work-address="si 0050 70 3a 2b 33 34 39 33 37 38 31 37 30 31 36 40 6d p:@xx.yyy.net 0070 74 3b 75 73 65 72 3d 70 68 6f 6e 65 22 3b 75 73 t;user=phone";us 0080 65 72 2d 69 64 3d 22 39 33 37 38 31 37 30 31 36 er-id="" 0090 40 6d 66 65 2e 74 65 6c 65 66 6f 6e 69 63 61 2e @xx.yyy. 00a0 6e 65 74 22 0d 0a net".. ÿÿÿX-xro 0030 61 64 57 6f 72 6b 73 2d 44 4e 43 3a 20 6e 65 74 : net 0040 77 6f 72 6b 2d 61 64 64 72 65 73 73 3d 22 73 69 work-address="si 0050 70 3a 2b 33 34 39 33 37 38 31 37 30 31 36 40 6d p:@xx.yyy.net 0070 74 3b 75 73 65 72 3d 70 68 6f 6e 65 22 3b 75 73 t;user=phone";us 0080 65 72 2d 69 64 3d 22 39 33 37 38 31 37 30 31 36 er-id="" 0090 40 6d 66 65 2e 74 65 6c 65 66 6f 6e 69 63 61 2e @xx.yyy. 00a0 6e 65 74 22 0d 0a net".. [image: image.png] BR/// Rakesh Kumar Mohanty On Wed, Feb 6, 2019 at 3:21 PM Rakesh wrote: > Hi Expert, > > Can I just know on INVITE request if I get the below characters then is > it OK as per ABNF grammar? Please note I am not asking about the header > rather I need to know the correctness of the character that has appeared on > INVITE request. > > > [truncated]\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\37 > Expert Info (Note/Undecoded): Unrecognised SIP header > (���) > > [image: image.png] > [image: image.png] > > BR/// > > Rakesh Kumar Mohanty > ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[Sip-implementors] RFC ABNF grammar check for Truncated unrecognized header
Hi Expert, Can I just know on INVITE request if I get the below characters then is it OK as per ABNF grammar? Please note I am not asking about the header rather I need to know the correctness of the character that has appeared on INVITE request. [truncated]\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\377\37 Expert Info (Note/Undecoded): Unrecognised SIP header (���) [image: image.png] [image: image.png] BR/// Rakesh Kumar Mohanty ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
[Sip-implementors] [Deadline Approaching - Call for Workshop Proposals]: 24th European Symposium on Research in Computer Security (ESORICS 2019)
[apologies for cross-posting] == CALL for WORKSHOP PROPOSALS: ESORICS 2019 24th European Symposium on Research in Computer Security University of Luxembourg, Luxembourg, September 23-27, 2019 Website: https://esorics2019.uni.lu/workshops/ == Overview ESORICS is the annual European research event in Computer Security. The Symposium started in 1990 and has been held in several European countries, attracting a wide international audience from both the academic and industrial communities. Proposals are solicited for Workshops to be held in conjunction with ESORICS 2019. A Workshop should aim at providing a forum on emerging topics of high interest to the security and privacy community. In the Workshop selection, particular consideration will be paid to: * Its potential interest for the security and privacy community * Its novelty with respect to other forums, especially with respect to other ESORICS workshops. * Its likely impact on the target community, including likely high participation. A workshop can be either one day or two days in length. Important Dates * Workshop proposals due: February 8, 2019 * Notification of decision: March 15, 2019 Submitting a Workshop Proposal To submit a proposal send an email to the Workshop Chair with with the information requested in the application form: * Joaquin Garcia-Alfaro (jgalf...@ieee.org) The following application form should be used. (also available in Word format at http://j.mp/ESORICS19wsh) == ESORICS 2019 - WORKSHOP APPLICATION FORM: - Title of the Workshop: - Duration (maximum 2 days): - Draft "Call for Papers", articulating the workshop's scope and topics: - Brief summary and justification for the workshop, including anticipated benefits to the ESORICS community: - Planned activities: - Expected number of participants: - Workshop organizers: * PC Chair(s): * General Chair(s): - Workshop deadlines: * Submission deadline: * Notification to authors: * Camera-ready versions: - Planned publication of Workshop proceedings: - Data of last three years for the workshop (if applicable): * Number of submissions: * Number of accepted papers: * Number of participants: * Publication of proceedings: * Venue (co-location): == ___ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
