You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Mirko Raner (JIRA)" <ji...@apache.org> on 2012/09/26 00:22:08 UTC
[jira] [Created] (NET-481) Commons TFTP does not support RFCs 2347
and 2349
Mirko Raner created NET-481:
-------------------------------
Summary: Commons TFTP does not support RFCs 2347 and 2349
Key: NET-481
URL: https://issues.apache.org/jira/browse/NET-481
Project: Commons Net
Issue Type: Improvement
Components: TFTP
Affects Versions: 3.1, 1.4
Reporter: Mirko Raner
Priority: Minor
Commons TFTP does not implement RFC 2347 (TFTP Option Extension) and RFC 2349 (TFTP Timeout Interval and Transfer Size Options).
Implementing these two RFCs involves a new packet type (OACK) as well as additional optional header fields in existing read and write request packets.
We recently had to do this work for an internal project and are considering to contribute our patches back to the project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NET-481) Commons TFTP does not support RFCs
2347 and 2349
Posted by "Sebb (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NET-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465223#comment-13465223 ]
Sebb commented on NET-481:
--------------------------
Sounds like a useful enhancement. Could you provide a sample patch?
> Commons TFTP does not support RFCs 2347 and 2349
> ------------------------------------------------
>
> Key: NET-481
> URL: https://issues.apache.org/jira/browse/NET-481
> Project: Commons Net
> Issue Type: Improvement
> Components: TFTP
> Affects Versions: 1.4, 3.1
> Reporter: Mirko Raner
> Priority: Minor
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Commons TFTP does not implement RFC 2347 (TFTP Option Extension) and RFC 2349 (TFTP Timeout Interval and Transfer Size Options).
> Implementing these two RFCs involves a new packet type (OACK) as well as additional optional header fields in existing read and write request packets.
> We recently had to do this work for an internal project and are considering to contribute our patches back to the project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira